Method and apparatus for setting transmission bit index or transmission time point according to channel condition in wireless communication system
The method and device for setting transmission bit indices and PUSCH opportunities in wireless communication systems adapt to varying channel conditions by using subband non-overlapping full duplex configuration, enhancing the reliability and efficiency of uplink data and control information transmission.
Patent Information
- Application Number
- PCT/KR2024/006380
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-05-10
- Publication Date
- 2024-11-21
AI Technical Summary
Current wireless communication systems face challenges in efficiently setting transmission bit indices and PUSCH transmission opportunities, particularly in varying channel conditions, which affect the reliability and performance of uplink data and control information transmission.
A method and device that involve receiving subband non-overlapping full duplex configuration information from a base station, determining the appropriate transmission opportunity based on redundancy version sequence information, and applying RV index 0 to the PUSCH transmission opportunity, enabling effective transmission of uplink data and control information under different channel environments.
This approach enhances the system's ability to adapt to changing channel conditions, ensuring reliable and efficient transmission of uplink data and control information, thereby improving overall communication performance.
Smart Images

Figure KR2024006380_21112024_PF_FP_ABST
Abstract
Description
Method and device for setting transmission bit index or transmission time according to channel conditions in a wireless communication system
[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method and device for setting a bit index for transmission or reception by a terminal. Furthermore, the present disclosure relates to a method and device for setting uplink control information (UCI) transmission opportunities for multiplexing uplink data.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.
[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.
[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.
[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.
[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It could serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing this technology.
[0008] As described above and with the development of wireless communication systems, various services have become available, and methods for providing these services smoothly are required.
[0009] The disclosed embodiments aim to provide a device and method capable of effectively providing a service in a mobile communication system. Specifically, a method and device are proposed for setting a bit index transmitted or received by a terminal, and a method and device for setting a PUSCH for multiplexing UCI when multiplexing UCI with uplink data are also proposed.
[0010] According to at least one embodiment of the present disclosure, a method is provided by a terminal of a communication system,
[0011] The method comprises: receiving subband non-overlapping full duplex (SBFD) configuration information from a base station, wherein the SBFD configuration information includes time resource information including SBFD resources; receiving physical uplink shared channel (PUSCH) transmission configuration information from the base station, wherein the configuration information includes resources and redundancy version (RV) sequence information corresponding to a plurality of PUSCH transmission opportunities; determining whether resources corresponding to the plurality of PUSCH transmission opportunities correspond to a first transmission opportunity or a second transmission opportunity based on the PUSCH repetition transmission configuration information; and transmitting uplink data on a PUSCH by applying an RV index 0 in a PUSCH transmission opportunity corresponding to the first transmission opportunity based on an RV sequence indicated by an offset and the RV sequence information.
[0012] In addition, in a method performed by a base station of a communication system, the method comprises: a step of transmitting SBFD (subband non-overlapping full duplex) configuration information to a terminal, wherein the SBFD configuration information includes time resource information including SBFD resources; a step of transmitting PUSCH (physical uplink shared channel) repetitive transmission configuration information to the terminal, wherein the configuration information includes resource and redundancy version (RV) sequence information corresponding to a plurality of PUSCH transmission opportunities; and a step of receiving uplink data to which an RV index 0 is applied on a PUSCH in a PUSCH transmission opportunity corresponding to a first transmission opportunity, wherein the RV index 0 of the uplink data is related to an RV sequence indicated by an offset and the RV sequence information.
[0013] In a terminal of a communication system, the terminal comprises a transceiver; and a control unit configured to receive SBFD (subband non-overlapping full duplex) configuration information from a base station, the SBFD configuration information including time resource information including SBFD resources, receive PUSCH (physical uplink shared channel) repetitive transmission configuration information from the base station, the configuration information including resources and redundancy version (RV) sequence information corresponding to a plurality of PUSCH transmission opportunities, and determine whether resources corresponding to the plurality of PUSCH transmission opportunities correspond to a first transmission opportunity or a second transmission opportunity based on the PUSCH repetitive transmission configuration information, and transmit uplink data on a PUSCH by applying an RV index 0 in a PUSCH transmission opportunity corresponding to the first transmission opportunity based on an RV sequence indicated by an offset and the RV sequence information.
[0014] In addition, in a base station of a communication system, a transceiver; transmits SBFD (subband non-overlapping full duplex) configuration information to a terminal, the SBFD configuration information including time resource information including SBFD resources, transmits PUSCH (physical uplink shared channel) repetitive transmission configuration information to the terminal, the configuration information including resources and redundancy version (RV) sequence information corresponding to a plurality of PUSCH transmission opportunities, and includes a control unit configured to receive uplink data to which an RV index 0 is applied on a PUSCH in a PUSCH transmission opportunity corresponding to a first transmission opportunity, wherein the RV index 0 of the uplink data is related to an RV sequence indicated by an offset and the RV sequence information.
[0015] The embodiments described in this disclosure provide devices and methods capable of effectively providing services in a mobile communication system. Specifically, according to the embodiments of this disclosure, a terminal can effectively transmit uplink data and control information under a given channel environment, even when the uplink channel environment may vary depending on the situation.
[0016] FIG. 1 is a diagram illustrating a basic structure of a time-frequency domain in a wireless communication system according to one embodiment of the present disclosure.
[0017] FIG. 2 is a diagram illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.
[0018] FIG. 3 is a diagram illustrating an example of setting a control region of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.
[0019] FIG. 4 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.
[0020] FIG. 5 is a diagram illustrating an example of frequency axis resource allocation of a PDSCH in a wireless communication system according to one embodiment of the present disclosure.
[0021] FIG. 6 is a diagram illustrating an example of time axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.
[0022] FIG. 7 is a diagram illustrating an example of time axis resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure.
[0023] FIG. 8 is a diagram illustrating examples of PUSCH repetition transmission types A and B according to an embodiment of the present disclosure.
[0024] FIG. 9 is a diagram illustrating examples of single transmission and repeated transmission of TBoMS (TB processing over multi-slots) according to an embodiment of the present disclosure.
[0025] FIG. 10 is a diagram illustrating an example of a starting point of a transmission bit string determined by a redundancy version (RV) according to an embodiment of the present disclosure.
[0026] FIG. 11 is a diagram illustrating a transmission bit string determined by RV during PUSCH repetitive transmission and TBoMS operation according to an embodiment of the present disclosure.
[0027] FIG. 12 is a diagram illustrating an example of allocating time-axis resources in an SBFD system according to an embodiment of the present disclosure.
[0028] FIG. 13 is a diagram illustrating an example of allocation of PUSCH transmission resources in an SBFD system according to an embodiment of the present disclosure.
[0029] FIG. 14 is a diagram illustrating an example of a transmission that may occur when transmitting one TB through multiple transmissions in an SBFD system according to an embodiment of the present disclosure.
[0030] FIG. 15 is a diagram illustrating another example of a transmission that may occur when transmitting one TB through multiple transmissions in an SBFD system according to an embodiment of the present disclosure.
[0031] FIG. 16 is a diagram illustrating an example of an operation of a terminal performing UCI multiplexing when PUSCH transmission for the same TB occurs in multiple transmission opportunities according to an embodiment of the present disclosure.
[0032] FIG. 17 is a diagram illustrating an example of operation of a terminal in a wireless communication system in which different channel conditions are expected for each transmission for one TB according to an embodiment of the present disclosure.
[0033] FIG. 18 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.
[0034] FIG. 19 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.
[0035] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.
[0036] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to ensure that the gist of the present disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanations.
[0037] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.
[0038] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present disclosure, and these may vary depending on the intention or custom of the user or operator. Therefore, their definitions should be made based on the contents throughout the specification.
[0039] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (base station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (user equipment), an MS (mobile station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, the downlink (DL) refers to a wireless transmission path of a signal transmitted from the base station to the terminal, and the uplink (UL) refers to a wireless transmission path of a signal transmitted from the terminal to the base station. In addition, although the LTE or LTE-A system may be described below as an example, the embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and the 5G below may also be a concept that includes the existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems through some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.
[0040] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).
[0041] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.
[0042] Here, the term '~ unit' used in this embodiment means software or hardware components such as FPGA (field programmable gate array) or ASIC (application specific integrated circuit), and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Accordingly, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.
[0043] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.
[0044] As a representative example of the above broadband wireless communication system, the LTE system adopts the OFDM (orthogonal frequency division multiplexing, which can be used interchangeably with CP-OFDM (cyclic prefix-orthogonal frequency division multiplexing)) method in the downlink, and the SC-FDMA (single carrier frequency division multiple access, which can be used interchangeably with DFTS-OFDM (discrete Fourier transform-spread-orthogonal frequency division multiplexing)) method in the uplink. The above multiple access method typically allocates and operates time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so that orthogonality is established, thereby enabling each user's data or control information to be distinguished.
[0045] As a future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low-latency communication (URLLC).
[0046] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, 5G communication systems must provide not only the peak data rate but also the increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher frequency bands.
[0047] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the Internet of Things, mMTC requires support for large-scale terminal connection within a cell, improved terminal coverage, improved battery life, and reduced terminal costs. The Internet of Things provides communication functions by attaching various sensors and various devices, so a large number of terminals (e.g., 1,000,000 terminals / km) are required within a cell. 2 ) must be able to support. Furthermore, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements of buildings, due to the nature of the service, and thus may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be composed of low-cost terminals, and because it is difficult to frequently replace the terminal's battery, a very long battery life time, such as 10 to 15 years, may be required.
[0048] Finally, URLLC refers to a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, services such as remote control of robots or machinery, industrial automation, unmanaged aerial vehicles, remote health care, and emergency alerts can be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds and at the same time, a 10 -5The following packet error rate (PER) requirements apply. Therefore, for services supporting URLLC, 5G systems must provide a smaller Transmit Time Interval (TTI) than other services. Simultaneously, design considerations may require the allocation of extensive resources in the frequency band to ensure communication link reliability.
[0049] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.
[0050] Hereinafter, a / b can be understood as at least one of a or b.
[0051] Below, the frame structure of the 5G system is described in more detail with reference to drawings.
[0052] Figure 1 is a diagram illustrating the basic structure of the time-frequency domain, which is a radio resource domain in which data or control channels are transmitted in a 5G system.
[0053] The horizontal axis of Figure 1 represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time and frequency domains is a resource element (RE, 101), which can be defined as 1 OFDM symbol (102) on the time axis and 1 subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can constitute one resource block (RB, 104). One subframe (110) on the time axis can include multiple OFDM symbols (102). For example, the length of one subframe can be 1 ms.
[0054] FIG. 2 is a diagram illustrating an example of a frame, subframe, and slot structure in a 5G system.
[0055] Figure 2 illustrates an example of a structure of a frame (frame, 200), a subframe (subframe, 201), and a slot (slot, 202). One frame (200) can be defined as 10 ms. One subframe (201) can be defined as 1 ms, and therefore one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot =14. 1 subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In the example of Fig. 2, the cases where the subcarrier spacing setting value μ = 0 (204) and μ = 1 (205) are illustrated. When μ = 0 (204), 1 subframe (201) may be composed of one slot (202), and when μ = 1 (205), 1 subframe (201) may be composed of two slots (203). That is, the number of slots per subframe ( ) may vary, and accordingly the number of slots per frame ( ) may vary. Depending on the subcarrier spacing setting μ and can be defined as shown in Table 1 below.
[0056] μ 0141011142022144043148084141601651432032
[0057] Next, we will specifically explain downlink control information (DCI) in the 5G system.
[0058] In a 5G system, scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is transmitted from a base station to a terminal via DCI. The terminal can monitor a fallback DCI format and a non-fallback DCI format for the PUSCH or PDSCH. The fallback DCI format may consist of fixed fields defined between the base station and the terminal, and the non-fallback DCI format may include configurable fields.
[0059] DCI can be transmitted over the physical downlink control channel (PDCCH) after going through the channel coding and modulation process. A cyclic redundancy check (CRC) is attached to the DCI message payload, and the CRC can be scrambled with a radio network temporary identifier (RNTI) corresponding to the identity of the UE. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control command, or random access response. That is, the RNTI is not transmitted explicitly, but is included in the CRC calculation process. When the UE receives a DCI message transmitted over the PDCCH, it verifies the CRC using the assigned RNTI. If the CRC verification result is correct, the UE knows that the message was transmitted to the UE.
[0060] For example, a DCI scheduling a PDSCH for system information (SI) may be scrambled with SI-RNTI. A DCI scheduling a PDSCH for a random access response (RAR) message may be scrambled with RA-RNTI. A DCI scheduling a PDSCH for a paging message may be scrambled with P-RNTI. A DCI notifying a slot format indicator (SFI) may be scrambled with SFI-RNTI. A DCI notifying a transmit power control (TPC) may be scrambled with TPC-RNTI. A DCI scheduling a UE-specific PDSCH or PUSCH may be scrambled with C-RNTI (cell RNTI).
[0061] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI can include, for example, the information in Table 2.
[0062] - Identifier for DCI formats - [1] bit- Frequency domain resource assignment - [ ] bits- Time domain resource assignment - X bits- Frequency hopping flag - 1 bit.- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- TPC command for scheduled PUSCH - [2] bits- UL / SUL indicator (uplink / supplementary UL indicator) - 0 or 1 bit
[0063] DCI format 0_1 can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 with the CRC scrambled with C-RNTI can include, for example, the information in Table 3 below.
[0064] - Carrier indicator - 0 or 3 bits- UL / SUL indicator - 0 or 1 bit- Identifier for DCI formats - [1] bits- Bandwidth part indicator - 0, 1, or 2 bits- Frequency domain resource assignment- For resource allocation type 0 bits- For resource allocation type 1, bits- Time domain resource assignment -1, 2, 3, or 4 bits- VRB-to-PRB mapping (virtual resource block-to-physical resource block mapping) - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- Frequency hopping flag - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- 1st downlink assignment index (first downlink allocation index)- 1 or 2 bits○ 1 bit for semi-static HARQ-ACK codebook (semi-static HARQ-ACK In case of codebook);○ 2 bits for dynamic HARQ-ACK codebook with single HARQ-ACK codebook(When dynamic HARQ-ACK codebook is used with single HARQ-ACK codebook).- 2nd downlink assignment index (2nd downlink assignment index) - 0 or 2 bits○ 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks(When dynamic HARQ-ACK codebook is used with two HARQ-ACK sub-codebooks);○ 0 bit otherwise.TPC command for scheduled PUSCH - 2 bits- SRS resource indicator (SRS resource indicator) -. or bits○ bits for non-codebook based PUSCH transmission; ○ bits for codebook based PUSCH transmission. - Precoding information and number of layers - up to 6 bits - Antenna ports - up to 5 bits - SRS request - 2 bits - CSI request - 0, 1, 2, 3, 4, 5, or 6 bits - CBG transmission information - 0, 2, 4, 6, or 8 bits - PTRS-DMRS association (Phase tracking reference signal-demodulation reference signal relationship) - 0 or 2 bits - beta_offset indicator - 0 or 2 bits - DMRS sequence initialization - 0 or 1 bit
[0065] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI can include, for example, the information in Table 4 below.
[0066] - Identifier for DCI formats - [1] bit- Frequency domain resource assignment -[ ] bits- Time domain resource assignment - X bits- VRB-to-PRB mapping - 1 bit.- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- Downlink assignment index - 2 bits- TPC command for scheduled PUCCH - [2] bits- PUCCH resource indicator (physical uplink control channel, PUCCH) - 3 bits- PDSCH-to-HARQ feedback timing indicator (PDSCH-to-HARQ feedback timing indicator) - [3] bits
[0067] DCI format 1_1 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI can include, for example, the information in Table 5 below.
[0068] - Carrier indicator - 0 or 3 bits- Identifier for DCI formats - [1] bits- Bandwidth part indicator - 0, 1 or 2 bits- Frequency domain resource assignment○ For resource allocation type 0, bits○ For resource allocation type 1, bits- Time domain resource assignment -1, 2, 3, or 4 bits- VRB-to-PRB mapping - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- PRB bundling size indicator - 0 or 1 bit - Rate matching indicator - 0, 1, or 2 bits - ZP CSI-RS trigger - 0, 1, or 2 bits For transport block 1 (for the first transport block): - Modulation and coding scheme - 5 bits - New data indicator - 1 bit - Redundancy version - 2 bits For transport block 2 (for the second transport block): - Modulation and coding scheme - 5 bits - New data indicator - 1 bit - Redundancy version - 2 bits - HARQ process number - 4 bits - Downlink assignment index - 0 or 2 or 4 bits - TPC command for scheduled PUCCH - 2 bits - PUCCH resource indicator - 3 bits - PDSCH-to-HARQ_feedback timing indicator - 3 bits - Antenna ports - 4, 5, or 6 bits- Transmission configuration indication - 0 or 3 bits- SRS request - 2 bits- CBG transmission information - 0, 2, 4, 6, or 8 bits- CBG flushing out information - 0 or 1 bit- DMRS sequence initialization - 1 bit.
[0069] Below, the downlink control channel in a 5G communication system will be described in more detail with reference to drawings.
[0070] FIG. 3 is a diagram illustrating an example of a control region (control resource set, CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. FIG. 3 illustrates an example in which two control regions (control region #1 (301), control region #2 (302)) are set within a UE bandwidth part (UE bandwidth part, 310) on the frequency axis and within one slot (320) on the time axis. The control regions (301, 302) may be set to specific frequency resources (303) within the entire UE bandwidth part (310) on the frequency axis. The time axis may be set to one or more OFDM symbols, which may be defined as the control region length (control resource set duration, 304). Referring to the example illustrated in FIG. 3, control region #1 (301) is set to a control region length of two symbols, and control region #2 (302) is set to a control region length of one symbol.
[0071] In the aforementioned 5G system, the control region can be established by the base station to the terminal via higher-layer signaling (e.g., system information, master information block (MIB), radio resource control (RRC) signaling). Establishing a control region for the terminal means providing information such as the control region identifier, the frequency location of the control region, and the symbol length of the control region. For example, this information may include the information in Table 6.
[0072] ControlResourceSet ::= SEQUENCE {-- Corresponds to L1 parameter 'CORESET-ID' controlResourceSetId ControlResourceSetId,(Control domain identifier (Identity)) frequencyDomainResources BIT STRING (SIZE (45)),(Frequency axis resource allocation information) duration INTEGER (1..maxCoReSetDuration),(Time axis resource allocation information) cce-REG-MappingType CHOICE {(CCE-to-REG mapping method) interleaved SEQUENCE {reg-BundleSize ENUMERATED {n2, n3, n6},(REG bundle size) precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs}, interleaverSize ENUMERATED {n2, n3, n6}(interleaver size) shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL(Interleaved Shift)},nonInterleaved NULL},tci-StatesPDCCH SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL,(QCL setting information)tci-PresentInDCI ENUMERATED {enabled} OPTIONAL, -- Need S}
[0073] In Table 6, the tci-StatesPDCCH (simply named TCI (transmission configuration indication) state) configuration information may include information on one or more SS / PBCH block (synchronization signal / physical broadcast channel block, synchronization signal block (SSB)) indices or CSI-RS (channel state information reference signal) indices that are in a quasi-co-located (QCL) relationship with the DMRS transmitted in the corresponding control region.
[0074] FIG. 4 is a diagram illustrating an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in a 5G system. According to FIG. 4, the basic unit of time and frequency resources that constitute a control channel can be referred to as a REG (resource element group, 403), and a REG (403) can be defined as 1 OFDM symbol (401) on the time axis and 1 PRB (physical resource block, 402) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (403) to constitute a downlink control channel allocation unit.
[0075] As illustrated in FIG. 4, if the basic unit to which a downlink control channel is allocated in a 5G system is called a CCE (control channel element, 404), 1 CCE (404) can be composed of multiple REGs (403). Taking the REG (403) illustrated in FIG. 4 as an example, the REG (403) can be composed of 12 REs, and if 1 CCE (404) is composed of 6 REGs (403), 1 CCE (404) can be composed of 72 REs. When a downlink control region is set, the region can be composed of multiple CCEs (404), and a specific downlink control channel can be mapped to one or multiple CCEs (404) and transmitted according to the aggregation level (AL) within the control region. CCEs (404) within the control area are distinguished by numbers, and the numbers of the CCEs (404) can be assigned according to a logical mapping method.
[0076] The basic unit of the downlink control channel illustrated in FIG. 4, that is, the REG (403), may include both the REs to which the DCI is mapped and the area to which the demodulation reference signal (DMRS, 405), which is a reference signal for decoding the REs, is mapped. As shown in FIG. 4, three DMRSs (405) may be transmitted within one REG (403). The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 depending on the aggregation level, and different numbers of CCEs may be used to implement link adaptation of the downlink control channel. For example, when AL = L, one downlink control channel may be transmitted through L CCEs. The terminal must detect a signal without knowing information about the downlink control channel, and a search space representing a set of CCEs is defined for blind decoding. A search space is a set of downlink control channel candidates, consisting of CCEs that a terminal must attempt to decode at a given aggregation level. Since there are multiple aggregation levels, each of which can be a set of 1, 2, 4, 8, or 16 CCEs, a terminal can have multiple search spaces. A search space set can be defined as the set of search spaces at all configured aggregation levels.
[0077] Search spaces can be categorized into common search spaces and UE-specific search spaces. A certain group of UEs, or all UEs, can search the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling of system information or paging messages. For example, PDSCH scheduling allocation information for transmitting SIBs, including cell operator information, can be received by searching the common search space of the PDCCH. In the case of the common search space, since a certain group of UEs, or all UEs, must receive the PDCCH, it can be defined as a set of pre-arranged CCEs. Scheduling allocation information for UE-specific PDSCH or PUSCH can be received by searching the UE-specific search space of the PDCCH. The UE-specific search space can be defined UE-specifically as a function of the UE's identity and various system parameters.
[0078] In a 5G system, parameters for a search space for PDCCH can be configured from a base station to a terminal via higher-layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can configure the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring occasion for each symbol within the slot for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the corresponding search space, the control region index to be monitored for the search space, etc. to the terminal. For example, the information in Table 7 can be included.
[0079] SearchSpace ::= SEQUENCE {-- Identity of the search space. SearchSpaceId = 0 identifies the SearchSpace configured via PBCH (MIB) or ServingCellConfigCommon.searchSpaceId SearchSpaceId,(search space identifier)controlResourceSetId ControlResourceSetId,(control space identifier)monitoringSlotPeriodicityAndOffset CHOICE {(monitoring slot level period)sl1 NULL,sl2 INTEGER (0..1),sl4 INTEGER (0..3),sl5 INTEGER (0..4),sl8 INTEGER (0..7),sl10 INTEGER (0..9),sl16 INTEGER (0..15),sl20 INTEGER (0..19)} OPTIONAL,duration(monitoring length) INTEGER (2..2559)monitoringSymbolsWithinSlot BIT STRING (SIZE (14)) OPTIONAL,(슬롘 내 나이스 심보)nrofCandidates SEQUENCE {(집성 별보 PDCCH 이리군 수)aggregationLevel1 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, aggregationLevel2 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel4 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel8 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel16 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}},searchSpaceType CHOICE {(தமாற்க்குக்க்கு திய்தை)-- Configures this search space as common search space (CSS) and DCI formats to monitor.common SEQUENCE {(공통이이국이)}ue-Specific SEQUENCE {(단말-특정이스국)-- Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1.formats ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1},...}.
[0080] Depending on the configuration information, the base station may configure one or more search space sets for the terminal. In some embodiments, the base station may configure search space set 1 and search space set 2 for the terminal, and may configure the terminal to monitor DCI format A scrambled with X-RNTI in search space set 1 in a common search space, and may configure the terminal to monitor DCI format B scrambled with Y-RNTI in search space set 2 in a terminal-specific search space.
[0081] According to the configuration information, one or more search space sets may exist in a common search space or a terminal-specific search space. For example, search space set #1 and search space set #2 may be configured as a common search space, and search space set #3 and search space set #4 may be configured as terminal-specific search spaces.
[0082] In the common search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these.
[0083] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI
[0084] - DCI format 2_0 with CRC scrambled by SFI-RNTI
[0085] - DCI format 2_1 with CRC scrambled by INT-RNTI
[0086] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI
[0087] - DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI
[0088] In a terminal-specific search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these examples.
[0089] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI
[0090] - DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI
[0091] The RNTIs specified may follow the definitions and uses below.
[0092] C-RNTI (cell RNTI): For terminal-specific PDSCH scheduling purposes
[0093] TC-RNTI (temporary cell RNTI): For terminal-specific PDSCH scheduling purposes
[0094] CS-RNTI (configured scheduling RNTI): Used for semi-statically configured terminal-specific PDSCH scheduling.
[0095] RA-RNTI (random access RNTI): Used for PDSCH scheduling in the random access phase.
[0096] P-RNTI (paging RNTI): Used for scheduling PDSCH where paging is transmitted.
[0097] SI-RNTI (system information RNTI): Used for scheduling PDSCH where system information is transmitted.
[0098] INT-RNTI (interruption RNTI): Used to indicate whether pucturing is in progress for PDSCH.
[0099] TPC-PUSCH-RNTI (transmit power control for PUSCH RNTI): Used to indicate power control commands for PUSCH.
[0100] TPC-PUCCH-RNTI (transmit power control for PUCCH (physical uplink control channel) RNTI): Used to indicate power control commands for PUCCH
[0101] TPC-SRS-RNTI (transmit power control for SRS(sounding reference signal) RNTI): Used to indicate power control commands for SRS
[0102] The aforementioned specified DCI formats may follow definitions such as those in the examples in Table 8.
[0103] DCI formatUsage0_0Scheduling of PUSCH in one cell0_1Scheduling of PUSCH in one cell1_0Scheduling of PDSCH in one cell1_1Scheduling of PDSCH in one cell2_0Notifying a group of UEs of the slot format2_1Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE2_2Transmission of TPC commands for PUCCH and PUSCH2_3Transmission of a group of TPC commands for SRS transmissions by one or more UEs
[0104] In a 5G system, the search space of aggregation level L in CORESET p and search space set s can be expressed as in the following mathematical expression 1.
[0105] [Mathematical Formula 1]
[0106]
[0107] - L: Integration level
[0108] - n CI : Carrier Index
[0109] - n CCE,p : Total number of CCEs present in CORESET p
[0110] - : slot index
[0111] - : Number of PDCCH candidates for aggregation level L
[0112] - = 0, ..., -1: PDCCH candidate index of aggregation level L
[0113] - l = 0, ..., L -1
[0114] - , Y p,-1 = nRNTI≠0, A p = 39827 for p mod 3 = 0, A p = 39829 for p mod 3 = 1, A p = 39839 for p mod 3 = 2, D= 65537
[0115] - n RNTI : Terminal identifier
[0116] The value can be 0 for a common search space.
[0117] In the case of a terminal-specific search space, the value may correspond to a value that changes depending on the terminal's identity (C-RNTI or ID set to the terminal by the base station) and the time index.
[0118] In a 5G system, since multiple search space sets can be configured with different parameters (e.g., parameters in Table 7), the set of search space sets monitored by a terminal at each point in time can be different. For example, if search space set #1 is configured with an X-slot period and search space set #2 is configured with a Y-slot period and X and Y are different, the terminal can monitor both search space set #1 and search space set #2 in a specific slot, or can monitor either search space set #1 or search space set #2 in a specific slot.
[0119] FIG. 5 is a diagram illustrating an example of frequency-axis resource allocation of PDSCH or PUSCH in a wireless communication system according to one embodiment of the present disclosure.
[0120] FIG. 5 is a diagram illustrating three frequency axis resource allocation methods, type-0 (500), type-1 (505), and dynamic switch (510), which can be set through an upper layer in an NR wireless communication system.
[0121] Referring to FIG. 5, if the terminal is configured to use only type-0 resource allocation through upper layer signaling (500), some downlink control information (DCI) that allocates PDSCH / PUSCH to the terminal is N RBG Contains a bitmap consisting of N bits. RBG refers to the number of RBGs (resource block groups) determined as shown in Table 9 below according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, and data is transmitted to the RBG indicated as 1 by the bitmap.
[0122] Bandwidth Part SizeConfiguration 1Configuration 21-362437-724873-144816145-2751616
[0123] The size of the BWP is the number of RBs included in the BWP. More specifically, when type-0 resource allocation is instructed, the length of the frequency domain resource assignment (FDRA) field of the DCI received by the terminal is the number of RBGs (N RBG ) and Here, the first RBG is It contains RBs of the dog, and the last RBG is On the other hand, Contains the RBs of the dog, otherwise, It contains RBs of RBs. The remaining RBGs contain P RBs, where P is the number of nominal RBGs determined according to Table 9.
[0124] If the terminal is configured to use only type-1 resource allocation through upper layer signaling (505), the DCI that allocates PDSCH / PUSCH to the terminal It contains frequency band resource allocation information (FDRA) consisting of bits. Here, is the number of RBs included in the BWP. Through this, the base station can set the starting VRB (520) and the length of frequency axis resources (525) allocated continuously therefrom.
[0125] If a terminal is configured to use both type-0 resource allocation and type-1 resource allocation through upper layer signaling (510), some DCIs that allocate PDSCH / PUSCH to the terminal include frequency-axis resource allocation information composed of bits of a larger value (535) among the payload (515) for configuring type-0 resource allocation and the payload (520, 525) for configuring type-1 resource allocation. Conditions for this will be explained later. At this time, one bit may be added to the first part (MSB) of the frequency-axis resource allocation information in the DCI, and if the bit has a value of '0', it may indicate that type-0 resource allocation is used, and if the bit has a value of '1', it may indicate that type-1 resource allocation is used.
[0126] Below, a time domain resource allocation method for data channels in a 5G system is described.
[0127] The base station can configure a table for time-domain resource allocation information for PDSCH and PUSCH to the terminal via higher-layer signaling (e.g., RRC signaling). For PDSCH, a table with up to maxNrofDL-Allocations=16 entries can be configured, and for PUSCH, a table with up to maxNrofUL-Allocations=16 entries can be configured. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to a time interval in slot units between a time point at which a PDCCH is received and a time point at which a PDSCH scheduled by the received PDCCH is transmitted, denoted as K0, or scheduling offset), PDCCH-to-PUSCH slot timing (corresponding to a time interval in slot units between a time point at which a PDCCH is received and a time point at which a PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information about the position and length of a start symbol for which a PDSCH or PUSCH is scheduled within a slot, a mapping type of the PDSCH or PUSCH, etc. For example, information such as Table 10 or Table 11 below may be transmitted from a base station to a terminal.
[0128] PDSCH-TimeDomainResourceAllocationList information elementPDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocationPDSCH-TimeDomainResourceAllocation ::= SEQUENCE {k0 INTEGER(0..32) OPTIONAL, -- Need S(PDCCH-to-PDSCH timing, in slot units)mappingType ENUMERATED {typeA, typeB},(PDSCH mapping type)startSymbolAndLength INTEGER (0..127)(PDSCH start symbol and length)}
[0129] PUSCH-TimeDomainResourceAllocationinformation elementPUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation ::= SEQUENCE {k2 INTEGER(0..32) OPTIONAL, -- Need S(PDCCH-to-PUSCH timing, in slot units)mappingType ENUMERATED {typeA, typeB},(PUSCH mapping type)startSymbolAndLength INTEGER (0..127)(PUSCH start symbol and length)}
[0130] The base station may notify the terminal of one of the entries in the table for the time domain resource allocation information described above via L1 signaling (e.g., DCI) (e.g., indicated by the 'Time Domain Resource Allocation' field in the DCI). The terminal may obtain the time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.
[0131] FIG. 6 is a diagram illustrating an example of time axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.
[0132] Referring to FIG. 6, the base station uses the upper layer to set the subcarrier spacing (SCS) (μ) of the data channel and the control channel. PDSCH , μ PDCCH ), scheduling offset (K0) value, and the time axis position of the PDSCH resource can be indicated according to the OFDM symbol start position (600) and length (605) within a slot dynamically indicated through DCI.
[0133] FIG. 7 is a diagram illustrating an example of time-domain resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure.
[0134] Referring to Fig. 7, when the subcarrier spacing of the data channel and the control channel is the same (700, μ PDSCH = μ PDCCH ), the slot numbers for data and control are the same, so the base station and the terminal can generate a scheduling offset according to the predetermined slot offset K0. On the other hand, if the subcarrier spacing of the data channel and the control channel are different (705, μ PDSCH ≠ PDCCH), since the slot numbers for data and control are different, the base station and the terminal can generate a scheduling offset according to a predetermined slot offset K0 based on the subcarrier spacing of the PDCCH.
[0135] Next, the scheduling method for PUSCH transmission is described. PUSCH transmission can be dynamically scheduled by UL grant in DCI (this method may be referred to as dynamic grant, DG) or can operate by configured grant (CG) Type 1 or Type 2. Dynamic scheduling indication for PUSCH transmission is possible in DCI format 0_0 or 0_1.
[0136] Configured grant Type 1 PUSCH transmission can be semi-statically configured by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant of Table 13 through higher layer signaling, without receiving UL grant in DCI. Configured grant Type 2 PUSCH transmission can be semi-persistently scheduled by UL grant in DCI after receiving configuredGrantConfig not including rrc-ConfiguredUplinkGrant of Table 12 through higher layer signaling. When PUSCH transmission operates by configured grant, parameters applied to PUSCH transmission are applied through configuredGrantConfig of higher layer signaling of Table 12, except dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, scaling of UCI-OnPUSCH provided by pusch-Config of Table 13. If the terminal has been provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of Table 12, the terminal applies tp-pi2BPSK in pusch-Config of Table 13 to PUSCH transmission operated by the configured grant.
[0137] ConfiguredGrantConfig ::= SEQUENCE {frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S,cg-DMRS-Configuration DMRS-UplinkConfig,mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH} OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},rbg-Size ENUMERATED {config2} OPTIONAL, -- Need SpowerControlLoopToUse ENUMERATED {n0, n1},p0-PUSCH-Alpha P0-PUSCH-AlphaSetId,transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need SnrofHARQ-Processes INTEGER(1..16),repK ENUMERATED {n1, n2, n4, n8},repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need Rperiodicity ENUMERATED {sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14,sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14,sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14,sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12,sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12,sym1280x12, sym2560x12},configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need Rrrc-ConfiguredUplinkGrant SEQUENCE {timeDomainOffset INTEGER (0..5119),timeDomainAllocation INTEGER (0..15),frequencyDomainAllocation BIT STRING (SIZE(18)),antennaPort INTEGER (0..31),dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need RprecodingAndNumberOfLayers INTEGER (0..63),srs-ResourceIndicator INTEGER (0..15) OPTIONAL, -- Need RmcsAndTBS INTEGER (0..31),frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need RpathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1),...} OPTIONAL, -- Need R...}.
[0138] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission is the same as the antenna port for SRS transmission. PUSCH transmission can follow a codebook-based or non-codebook-based transmission method, respectively, depending on whether the value of txConfig in the upper signaling, pusch-Config in Table 13, is 'codebook' or 'nonCodebook'.
[0139] As described above, PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically configured by configured grant. If the UE is instructed to schedule PUSCH transmission via DCI format 0_0, the UE performs beam configuration for PUSCH transmission using pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the minimum ID within the activated uplink BWP within the serving cell, and the PUSCH transmission is based on a single antenna port. The UE does not expect scheduling for PUSCH transmission via DCI format 0_0 within a BWP where a PUCCH resource including pucch-spatialRelationInfo is not configured. If the UE does not configure txConfig in pusch-Config of Table 13, the UE does not expect to be scheduled with DCI format 0_1.
[0140] PUSCH-Config ::= SEQUENCE {dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need StxConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need Sdmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mdmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mpusch-PowerControl PUSCH-PowerControl OPTIONAL, -- Need MfrequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need SfrequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1..maxNrofPhysicalResourceBlocks-1)OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList} OPTIONAL, -- Need Mpusch-AggregationFactor ENUMERATED { n2, n4, n8} OPTIONAL, -- Need Smcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need StransformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need ScodebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}OPTIONAL, -- Cond codebookBasedmaxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBasedrbg-Size ENUMERATED { config2} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need Mtp-pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need S...}.
[0141] Next, we describe codebook-based PUSCH transmission. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically based on a configured grant. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 or semi-statically configured via a configured grant, the UE determines a precoder for PUSCH transmission based on the SRI (SRS resource indicator), TPMI (transmission precoding matrix indicator), and transmission rank (the number of PUSCH transmission layers).
[0142] At this time, the SRI can be given through the field SRI in the DCI or configured through the upper signaling srs-ResourceIndicator. The UE is configured with at least one SRS resource when transmitting a codebook-based PUSCH, and can be configured with up to two. When the UE receives an SRI through the DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. In addition, the TPMI and transmission rank can be given through the fields precoding information and number of layers in the DCI or configured through the upper signaling precodingAndNumberOfLayers. The TPMI is used to indicate the precoder applied to the PUSCH transmission. If the UE is configured with one SRS resource, the TPMI is used to indicate the precoder to be applied to the configured one SRS resource. When a terminal is configured with multiple SRS resources, TPMI is used to indicate the precoder to be applied in the SRS resource indicated through SRI.
[0143] The precoder to be used for PUSCH transmission is selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the upper layer signaling, SRS-Config. In codebook-based PUSCH transmission, the UE determines the codebook subset based on the TPMI and codebookSubset in the upper layer signaling, pusch-Config. The codebookSubset in the upper layer signaling, pusch-Config, can be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability (which can be mixed with UE capability) reported by the UE to the base station. If the UE reports 'partialAndNonCoherent' as the UE capability, the UE does not expect the value of codebookSubset in the upper layer signaling to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the terminal reports 'nonCoherent' as the terminal capability, the terminal does not expect the value of the upper signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in the upper signaling SRS-ResourceSet points to two SRS antenna ports, the terminal does not expect the value of the upper signaling codebookSubset to be set to 'partialAndNonCoherent'.
[0144] The terminal can be configured with one SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource within the SRS resource set can be indicated via SRI. If multiple SRS resources are configured within the SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', the terminal expects that the value of nrofSRS-Ports in the upper signaling SRS-Resource is set to the same value for all SRS resources.
[0145] The terminal transmits to the base station one or more SRS resources included in the SRS resource set in which the usage value is set to 'codebook' according to upper signaling, and the base station selects one of the SRS resources transmitted by the terminal and instructs the terminal to perform PUSCH transmission using transmission beam information of the corresponding SRS resource. At this time, in codebook-based PUSCH transmission, the SRI is used as information for selecting an index of one SRS resource and is included in the DCI. Additionally, the base station includes in the DCI information indicating a TPMI and rank to be used by the terminal for PUSCH transmission. The terminal performs PUSCH transmission by applying the indicated rank and the precoder indicated by the TPMI based on the transmission beam of the corresponding SRS resource using the SRS resource indicated by the SRI.
[0146] Next, we describe non-codebook-based PUSCH transmission. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically based on a configured grant. If at least one SRS resource is configured within an SRS resource set in which the usage value in the upper signaling, SRS-ResourceSet, is set to 'nonCodebook', the UE can be scheduled for non-codebook-based PUSCH transmission via DCI format 0_1.
[0147] For an SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'nonCodebook', the UE can be configured with one connected NZP CSI-RS resource (non-zero power CSI-RS). The UE can perform calculations on a precoder for SRS transmission through measurements on the NZP CSI-RS resources connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission at the UE is less than 42 symbols, the UE does not expect information on the precoder for SRS transmission to be updated.
[0148] If the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS is indicated by the SRS request field in DCI format 0_1 or 1_1. At this time, if the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence of the connected NZP CSI-RS is indicated when the value of the SRS request field in DCI format 0_1 or 1_1 is not '00'. At this time, the DCI must not indicate cross-carrier or cross-BWP scheduling. In addition, if the value of the SRS request indicates the presence of an NZP CSI-RS, the NZP CSI-RS is located in the slot in which the PDCCH including the SRS request field is transmitted. At this time, the TCI states set for the scheduled subcarriers are not set to QCL-TypeD.
[0149] If a periodic or semi-persistent SRS resource set is configured, the associated NZP CSI-RS can be indicated through the associatedCSI-RS in the upper layer signaling SRS-ResourceSet. For non-codebook-based transmission, the UE does not expect the upper layer signaling spatialRelationInfo for SRS resources and the associatedCSI-RS in the upper layer signaling SRS-ResourceSet to be configured together.
[0150] When multiple SRS resources are configured, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. At this time, the SRI can be indicated through the SRI field in the DCI or can be configured through the srs-ResourceIndicator, which is a higher-order signaling. Similar to the codebook-based PUSCH transmission described above, when the UE is provided with an SRI through the DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including the SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be simultaneously transmitted in the same symbol within one SRS resource set and the maximum number of SRS resources are determined by the UE capability reported by the UE to the base station. At this time, the SRS resources that the UE simultaneously transmits occupy the same RB. The UE configures one SRS port for each SRS resource. Only one SRS resource set with the usage value set to 'nonCodebook' in the upper signaling SRS-ResourceSet can be set, and up to four SRS resources for non-codebook based PUSCH transmission can be set.
[0151] The base station transmits one NZP-CSI-RS associated with an SRS resource set to the terminal, and the terminal calculates a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the result measured upon reception of the NZP-CSI-RS. When the terminal transmits one or more SRS resources within the SRS resource set of which usage is set to 'nonCodebook' to the base station, the terminal applies the calculated precoder, and the base station selects one or more SRS resources from the received one or more SRS resources. At this time, in non-codebook based PUSCH transmission, the SRI represents an index that can express a combination of one or more SRS resources, and the SRI is included in the DCI. At this time, the number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers of the PUSCH, and the terminal transmits the PUSCH by applying the precoder applied to the SRS resource transmission to each layer.
[0152] Hereinafter, the PUSCH repetition transmission technique in 5G systems is described. PUSCH repetition transmission in 5G systems is a transmission technique that can ensure uplink transmission reliability by retransmitting one transport block (TB) multiple times, and can have two types: Type A and Type B. In the case of PUSCH repetition Type A, only one repetition can occur in one slot, and one TB is retransmitted in multiple slots. The locations of the time resources used in each slot are all the same. In the case of PUSCH repetition Type B, repeated transmission can occur using mini-slots in one slot, and more than one repeated transmission can occur in one slot. In the case of Type B, the UE receives only the location of the time resource of the first nominal repetition from the base station, and the locations of the time resources in which the remaining repetitions are transmitted can be determined based on the location of the time resource of the first nominal repetition and the uplink / downlink indication direction of the symbols. If a nominal repetition crosses a slot boundary, such as due to an invalid symbol or a DL / UL transition, it is divided into multiple actual repetitions. Therefore, the number of actual repetitions may be greater than the number of nominal repetitions.
[0153] In the present disclosure, for convenience, a transmission occasion for PUSCH repetitive transmission may be defined as follows. For PUSCH repetitive transmission type A, a total of n transmission opportunities may be available, satisfying n=0,1,...,K-1. Here, K represents the number of repetitive transmissions for the same TB. For PUSCH repetitive transmission type B, a total of n transmission opportunities may be available, satisfying n=0,1,...,(actual number of repetitions-1). The number of actual repetitions may be equal to or greater than the nominal number of repetitions (=K).
[0154] When a TB is repeatedly transmitted K times using PUSCH repetition type A, the UE performs the (n+1)th retransmission at the nth transmission opportunity (n=0, 1, 2, ..., K-1). For example, when the UE performs K=5 PUSCH repetition transmissions, the TB performs the initial transmission when n=0 and the 5th repetition transmission when n=4. When a TB is repeatedly transmitted K times using PUSCH repetition type B, the UE performs the (n+1)th actual repetition at the nth transmission opportunity (n=0, 1, ..., (the number of actual repetitions-1)). For example, when the UE performs k=2 PUSCH repetition transmissions, where each nominal repetition is divided into 2 actual repetitions, resulting in a total of 4 actual repetitions, the first actual repetition is performed when n=0 and the 4th actual transmission is performed when n=3. For PUSCH repetitive transmissions, each transmission opportunity can be a time interval during which TB is transmitted once.
[0155] FIG. 8 is a diagram illustrating examples of PUSCH repetition types A and B in a wireless communication system. (a) (820) is an example of retransmitting the same TB (800) three times (801, 802, 803) through PUSCH resources allocated in three slots using PUSCH repetition type A (i.e., K=3), and the locations of time resources where PUSCH is transmitted within each slot are the same. The terminal has a total of three transmission opportunities with n=0, 1, and 2. (b) (830) is an example of retransmitting the same TB (810) twice using PUSCH repetition type B (K=2), and the first nominal repetition was divided into two actual repetitions, 805 and 806, due to the slot boundary. Similarly, the second nominal repetition was also divided into two actual repetitions, 807 and 808, due to the slot boundary. That is, the total transmission opportunity is 4 times, with n=0, 1, 2, 3. The above PUSCH transmission is performed through the resources allocated within the slot.
[0156] Below, we describe the TBoMS (TB processing over multiple slots) transmission technique in 5G communication systems. TBoMS is a technique for improving uplink data channel coverage in 5G systems, transmitting a single TB across multiple slots. The size of a TB is calculated based on the total number of slots N over which a single TB is transmitted. In TBoMS, the transmission opportunity n can have a value between 0 and N K-1, where K represents the number of repeated transmissions of the TB. A single TB is transmitted over N transmission opportunities.
[0157] FIG. 9 is a diagram illustrating an example of TBoMS transmission in a 5G system. According to FIG. 9, (a) (920) is a diagram illustrating an example of TBoMS PUSCH transmission in a 5G system, in which one TB (900) is transmitted (901, 902, 903) across multiple slots corresponding to n=0, 1, 2. Compared to PUSCH repetitive transmission, TBoMS can reduce the CRC ratio and obtain channel coding gain using a lower code rate and improve channel coverage by allocating one TB instead of allocating small multiple TBs to uplink transmission resources of multiple slots. Compared to transmission using a single slot, TBoMS can obtain power boosting gain and improve channel coverage by reducing the number of frequency axis resources used in one slot. (b)(930) illustrates an example of repeated transmission of TBoMS, in which one TB (910) is transmitted over three slots, and this is repeated twice. Therefore, in the case of (b)(930), a total of six slots are used for TBoMS transmission, and the transmission opportunities of n=0,1,2 from slots m to m+2 correspond to the first transmission (901, 902, 903), and the transmission opportunities of n=3,4,5 from slots m+3 to m+5 correspond to the second transmission (904, 905, 906).
[0158] Next, we describe the redundancy version (RV) applied to retransmission in 5G communication systems. Retransmission in 5G systems can operate based on soft combining, which increases packet reliability by storing the received packet in buffer memory, combining it with the retransmitted packet, and then determining whether there are any errors again when an error occurs in the received packet and cannot be decoded. The methods for combining the previously received packet with the retransmitted packet can be broadly divided into chase combining (CC) and incremental redundancy (IR). According to chase combining, the transmitter applies the same rate matching pattern for both initial transmission and retransmission, transmitting the same physical layer bits. With incremental redundancy, the transmitter can apply different rate-matching patterns and transmit different physical layer bits in the initial and retransmissions. Additional parity bits may be transmitted through the retransmissions, potentially altering the effective code rate of each transmission. Therefore, incremental redundancy may require more parity bits for decoding than chase combining, potentially requiring larger buffer memory.
[0159] The rate matching output of a data channel in a 5G system can be determined by a redundancy version (RV) from 0 to 3. The input of rate matching is a length N. cbThe code block (CB) of the LDPC code is stored in a circular buffer, and bits of a fixed length can be selected from the starting point determined by the RV. The index k0 of the starting bit determined by the RV is the base graph (BG) and lifting size Z of the LDPC code. C Depending on the value, it can be determined as shown in Table 14 below. The detailed operation principle of rate matching for LDPC code follows Section 5.4.2 of TS 38.212.
[0160] rv id k0- LDPC graph 12k0- LDPC graph 10001 2 3
[0161] Fig. 10 is a diagram illustrating an example in which a code block encoded with an LDPC code is stored in a circular buffer. In Fig. 10, the starting point k0 of a bit string that varies according to each RV is illustrated (1010, 1011, 1012, 1013). In the case of uplink transmission, the terminal can select a bit string to be transmitted by applying a different RV for each transmission opportunity (n) according to the RV sequence. The x+1th value in each sequence means the RV value used when n mod 4 = x is satisfied for each transmission opportunity n. For example, the terminal may be instructed with an RV sequence of {0, 2, 3, 1} through DCI or an upper layer message, in which case the terminal may transmit a selected bit string from RV0 (1010) (1002) in the first transmission opportunity (n=0), and in subsequent transmission opportunities, may sequentially transmit a selected bit string from RV2 (1012) (1003), a selected bit string from RV3 (1013) (1004), and a selected bit string from RV (1011)1 (1005) to the base station. When the terminal operates with DG PUSCH repeated transmission, the terminal may transmit rv id The RV sequence can be determined by receiving, for example, rv id If =0, {0, 2, 3, 1} is the RV sequence set to the terminal, and rv id In the case of =2, {2, 3, 1, 0} is the RV sequence set to the terminal. The terminal determines the starting point of the bits stored in the circular buffer based on the RV value at each transmission opportunity and transmits data to the base station. Similarly, the base station can refer to the RV value for each transmission, align the position of the received bit string in the circular buffer, store it, and then perform decoding based on soft combining.
[0162] When transmitting DG PUSCH, the base station transmits rv through DCI idThe RV sequence determined by the value is defined as in Table 15 below in Section 6.1.2 of TS 38.214. N is the number of slots used to determine TBS, which is indicated by numberOfSlotsTBoMS in case of TBoMS and 1 in case of PUSCH repetition. K indicates the number of times the same TB is repeatedly transmitted. In case of PUSCH repetition transmission type A, transmission opportunity n can have values of 0, 1,...N K-1. For example, when a terminal transmits rv through DCI id = 2 is received and a total of 3 repetitions are performed with PUSCH repetition type A, the actual RV values applied to each transmission opportunity n={0, 1, 2} are {2, 3, 1} in order, and therefore the starting point of the bits transmitted in TB for each transmission opportunity can be determined in the order of RV2, RV3, and RV1. In the case of PUSCH repetition transmission type B, the transmission opportunity n can have values of 0, 1, ..., (the number of actual repetitions-1). Here, the number of actual repetitions means the sum of the actual repetitions for the entire nominal repetitions when the nominal repetitions in PUSCH repetition transmission type B are separated due to slot boundaries or invalid symbols and transmitted through multiple actual repetitions.
[0163] rv id indicated by the DCI scheduling the PUSCHrv id to be applied to n th transmission occasion (repetition Type A) or TB processing over multiple slots) or n thactual repetition (repetition Type B)((n-(n mod N)) / N) mod 4 = 0((n-(n mod N)) / N) mod 4 = 1((n-(n mod N)) / N) mod 4 = 2((n-(n mod N)) / N) mod 4 = 300231223103310211023
[0164] LDPC code is a type of systematic code in which the information bit (systematic bit) string that enters the encoder's input is output without any transformation in the code block. When transmission starts from RV0 and RV3, the information bit (1001) stored in the circular buffer can be included in the transmission bit string. RVs that include information bits in the transmission bit string, such as RV0 (1010) and RV3 (1013), and can be successfully decoded with just a single transmission are called self-decodable RVs.
[0165] FIG. 11 is a diagram illustrating an example of a transmission bitstream of a terminal according to an RV set by the terminal when performing PUSCH repetition and TBoMS in a 5G system. According to FIG. 11, (a)(1160) illustrates an example of a transmission bitstream that varies according to RVs (1150, 1151, 1152, 1153) from 0 to 3 within a single TB (1100).
[0166] (b)(1170) is an example for PUSCH repetition type A, in which one TB (1100) is repeatedly transmitted four times (1101, 1102, 1103, 1104) in transmission opportunities of n=0, 1, 2, 3 of a total of four slots from slot m to m+3. In this example, it is assumed that the RV sequence set by the terminal through DCI or a higher layer message is {0, 2, 3, 1}. Therefore, in slot m, which is a transmission opportunity of n=0, a bit string selected starting from RV0 (1150) is transmitted through the allocated resource (1101). Subsequently, in slots m+1, m+2, and m+3, bit strings selected starting from RV2 (1122), RV3 (1123), and RV1 (1121) are transmitted in that order through the allocated resource (1102, 1103, 1104).
[0167] (c)(1180) is an example for PUSCH repetition type B, in which the terminal performs two nominal repetitions for one TB (1100). The first nominal repetition is divided into two actual repetitions, 1111 and 1112, by the slot boundary, and the second nominal repetition is divided into two actual repetitions, 1113 and 1114, by the slot boundary. Therefore, a total of four actual repetitions can be performed, n=0, 1, 2, 3. Since the RV sequence set by the terminal is {0, 2, 3, 1}, in the first actual repetition (n=0), a bit string selected starting from RV0 (1120) is transmitted. Subsequently, in the second, third, and fourth actual repetitions, bit strings selected starting from RV2 (1122), RV3 (1123), and RV1 (1124) are sequentially transmitted.
[0168] (d)(1190) is an example for TBoMS, where one TB (1100) is transmitted over three slots from slot m to m+2 through resources allocated to transmission opportunities n=0, 1, 2 (1120, 1121, 1122), and the same TB is retransmitted over three slots from slot m+3 to m+5 through resources allocated to transmission opportunities n=3, 4, 5 (1130, 1131, 1132). From slots m to m+2 (n=0, 1, 2) corresponding to initial transmission, RV0 is applied for rate matching, and from slots m+3 to m+5 (n=3, 4, 5) corresponding to retransmission, RV2 is applied for rate matching.
[0169] In TBoMS, the index k0 of the transmission bit for each transmission opportunity follows the previously defined Table 14 when it corresponds to the first slot among all slots in which one TB is transmitted. For slots other than the first slot, k0 = (k'0 + H + τ) mod N cb k0 can be set along . In this case, k'0 has length N cb Indicates the bit index that started transmission in the previous slot among the input codewords, H is the number of bits actually transmitted in the previous slot when not assuming uplink control information (UCI) multiplexing, and τ is the number of filler bits whose actual transmission is omitted in the previous slot when not assuming UCI multiplexing. The detailed setting method follows TS 38.212 Section 6.2.5 as shown in Table 16. As an example, the length N of the codeword encoded using base graph 2 cbIt can be assumed that the TBoMS has 14,400 bits, the length of the information bits is 2,880 bits, the 2,617th bit to the 2,880th bit within the information bits are set as filler bits, the number of slots N used for TBoMS is 5, and each slot can transmit 1,728 bits. If the RV sequence set by the terminal through DCI or upper layer message is {0, 2, 3, 1}, RV0 can be used for TBoMS initial transmission (n=0, 1, 2, 3, 4), and the starting bit index k0 at each transmission opportunity is {0, 1728, 3720, 5448, 7176}. If the same terminal performs the second iteration of TBoMS transmission (n=5, 6, 7, 8, 9), RV2 can be used for transmission, and the transmission start bit index k0 for each transmission opportunity is equal to {7200, 8928, 10656, 12384, 14112}.
[0170] k0 as given by Table 5.4.2.1-2 according to the value of and LDPC base graph if the slot is the first slot within the slots allocated for the transmission of TB processing over multiple slots, and setting k0= (k'0+ H + τ)mod N cb if the slot is a slot except for the first one within the N S slots, where N S is the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI, k'0denotes the index of starting coded bit in the previous slot within the NS slots, H is the total number of coded bits available for transmission of the transport block in the previous slot within the N S slots assuming no UCI multiplexing, and τ denotes the number of skipped filler bits if any in the previous slot within the slots according to Clause 5.4.2.1 by assuming no UCI multiplexing.
[0171] Below, we describe subband non-overlapping full duplex (SBFD) in 5G systems.
[0172] Meanwhile, 3GPP is discussing SBFD as a new full-duplex communication method based on NR. SBFD is a technology that expands the uplink coverage of a terminal by utilizing a portion of downlink resources as uplink resources in the TDD (time division duplex) spectrum of frequencies below 6 GHz or above 6 GHz, thereby receiving uplink transmissions from terminals equivalent to the increased uplink resources, and reduces feedback delay by receiving feedback from the terminals regarding downlink transmissions in the expanded uplink resources. In the present disclosure, a terminal that receives information on whether SBFD is supported from a base station and can perform uplink transmissions in a portion of downlink resources may be conveniently referred to as an SBFD terminal (SBFD-capable UE). The following methods may be considered for defining the SBFD method in the standard and for an SBFD terminal to determine whether SBFD is supported in a specific cell (or frequency, frequency band).
[0173] First method. In addition to the frame structure type of the existing unpaired spectrum (or TDD) or paired spectrum (or FDD (frequency division duplex)), another frame structure type (e.g., frame structure type 2) may be introduced to define the above SBFD. The above frame structure type 2 may be defined as being supported in the specific frequency or frequency band, or the base station may indicate to the terminal whether SBFD is supported as system information. The SBFD terminal may receive the system information including whether SBFD is supported and determine whether SBFD is supported in the specific cell (or frequency, frequency band).
[0174] Second method. Whether SBFD is additionally supported in a specific frequency or frequency band of an existing unpaired spectrum (or TDD) can be indicated without defining a new frame structure type. In the second method, whether SBFD is additionally supported in a specific frequency or frequency band of an existing unpaired spectrum can be defined, or the base station can indicate to the terminal whether SBFD is supported as system information. The SBFD terminal can receive the system information including whether SBFD is supported and determine whether SBFD is supported in the specific cell (or frequency, frequency band).
[0175] In the first and second methods described above, information on whether SBFD is supported may be information that indirectly indicates whether SBFD is supported by additionally setting a portion of downlink resources as uplink resources in addition to the settings for TDD UL-DL resource configuration information indicating downlink slot (or symbol) resources and uplink slot (or symbol) resources of TDD (for example, SBFD resource configuration information in FIG. 13 described below), or may be information that directly indicates whether SBFD is supported.
[0176] In the present disclosure, the SBFD terminal can obtain cell synchronization by receiving a synchronization signal block during the initial cell access for connecting to a cell (or base station). The process for obtaining cell synchronization may be the same for the SBFD terminal and the existing TDD terminal. Thereafter, the SBFD terminal can determine whether the cell supports SBFD through a MIB acquisition process, a SIB acquisition process, or a random access process.
[0177] The system information for transmitting information on whether the above SBFD is supported may be system information transmitted separately from the system information for terminals supporting other versions of the standard within the cell (e.g., existing TDD terminals), and the SBFD terminal may determine whether SBFD is supported by obtaining all or part of the system information for the existing TDD terminal and the separately transmitted system information. If the SBFD terminal obtains only the system information for the existing TDD terminal or obtains system information on non-support of SBFD, the cell (or base station) may determine that it supports only TDD.
[0178] If the information on whether the above SBFD is supported is included in the system information for a terminal supporting a different version of the standard (e.g., an existing TDD terminal), the information on whether the above SBFD is supported may be inserted at the very end so as not to affect the acquisition of system information by the existing TDD terminal. If the SBFD terminal does not obtain the information on whether the above SBFD is supported inserted at the very end, or obtains information that SBFD is not supported, the SBFD terminal can determine that the cell (or base station) only supports TDD.
[0179] If the information on whether the SBFD is supported is included in the system information for a terminal supporting a different version of the standard (e.g., an existing TDD terminal), the information on whether the SBFD is supported may be transmitted through a separate PDSCH so as not to affect the acquisition of system information by the existing TDD terminal. That is, a terminal that does not support SBFD can receive a first SIB (or SIB1) including existing TDD-related system information from a first PDSCH. A terminal that supports SBFD can receive a first SIB (or SIB) including existing TDD-related system information from a first PDSCH, and a second SIB including SBFD-related system information from a second PDSCH. Here, the first PDSCH and the second PDSCH can be scheduled as the first PDCCH and the second PDCCH, and the CRCs of the first PDCCH and the second PDCCH can be scrambled with the same RNTI (e.g., SI-RNTI). The search space for monitoring the second PDCCH can be obtained from the system information of the first PDSCH, and if it is not obtained (i.e., the system information of the first PDSCH does not include information about the search space), the second PDCCH can be received in the same search space as the search space of the first PDCCH.
[0180] As described above, when the SBFD terminal determines that the cell (or base station) supports only TDD, the SBFD terminal can perform random access procedures and transmit and receive data / control signals in the same manner as a conventional TDD terminal.
[0181] The base station may configure separate random access resources for each of an existing TDD terminal or an SBFD terminal (e.g., an SBFD terminal supporting duplex communication and an SBFD terminal supporting half-duplex communication), and transmit configuration information (control information or configuration information indicating time-frequency resources that can be used for PRACH) for the random access resources to the SBFD terminal through system information. The system information for transmitting information for the random access resources may be separately transmitted system information that is distinct from system information for terminals supporting different versions of standards within a cell (e.g., an existing TDD terminal).
[0182] The base station may be able to distinguish whether the TDD terminal supporting different versions of the standard performs random access or the SBFD terminal performs random access by setting separate random access resources for the TDD terminal and the SBFD terminal supporting different versions of the standard. For example, the separate random access resource set for the SBFD terminal may be a resource that the existing TDD terminal determines to be a downlink time resource, and the SBFD terminal performs random access through an uplink resource (or a separate random access resource) set to a part of the frequency of the downlink time resource, so that the base station may determine that the terminal attempting random access through the uplink resource is an SBFD terminal.
[0183] Alternatively, the base station may set a common random access resource for all terminals within the cell without setting a separate random access resource for the SBFD terminal. In this case, configuration information for the random access resource may be transmitted to all terminals within the cell through system information, and the SBFD terminal that has received the system information may perform random access to the random access resource. Thereafter, the SBFD terminal may complete the random access process and proceed to the RRC connection mode for transmitting and receiving data with the cell. After the RRC connection mode, the SBFD terminal may receive an upper or physical signal from the base station that can determine that some frequency resources of the downlink time resources are set as uplink resources, and may perform an SBFD operation, for example, transmit an uplink signal from the uplink resources.
[0184] When the SBFD terminal determines that the cell supports SBFD, the terminal may transmit capability information including at least one or more of whether the terminal supports SBFD, whether full-duplex communication or half-duplex communication is supported, and the number of transmit or receive antennas it has (or supports), to the base station, thereby informing the base station that the terminal attempting to connect is an SBFD terminal. Alternatively, when half-duplex communication support is a mandatory implementation for the SBFD terminal, whether or not the half-duplex communication is supported may be omitted from the capability information. The SBFD terminal's report on the capability information may be reported to the base station through a random access procedure, may be reported to the base station after the random access procedure is completed, or may be reported to the base station after proceeding to an RRC connection mode for transmitting and receiving data with the cell.
[0185] The above SBFD terminal may support half-duplex communication, which performs only uplink transmission or downlink reception at a time, like a conventional TDD terminal, or may support full-duplex communication, which performs both uplink transmission and downlink reception at a time. Accordingly, whether the above half-duplex communication or full-duplex communication is supported may be reported to the base station by the SBFD terminal through a capability report, and after the report, the base station may configure the SBFD terminal to transmit and receive using half-duplex communication or full-duplex communication. When the SBFD terminal reports the capability for half-duplex communication to the base station, since a duplexer generally does not exist, a switching gap may be required to change the RF between transmission and reception when operating in FDD or TDD.
[0186] FIG. 12 is a diagram illustrating an example of SBFD operation in a TDD band of a wireless communication system to which the present disclosure is applied.
[0187] According to Fig. 12, (a)(1240) illustrates a case where TDD is operated in a specific frequency band. In a cell where TDD is operated, a base station can transmit and receive signals including data / control information in a downlink slot (or symbol), an uplink slot (or symbol) (1201), and a flexible slot (or symbol) based on settings for TDD UL-DL resource configuration information indicating downlink slot (or symbol) resources and uplink slot (or symbol) resources of a conventional TDD terminal or an SBFD terminal.
[0188] In Fig. 12, it is assumed that the DDDSU slot format is set according to the TDD UL-DL resource configuration information. Here, 'D' is a slot composed entirely of downlink symbols, 'U' is a slot composed entirely of uplink symbols, and 'S' is a slot that is not 'D' or 'U', that is, a slot that includes a downlink symbol or an uplink symbol or a flexible symbol. Here, for convenience, it can be assumed that S is composed of 12 downlink symbols and 2 flexible symbols. In addition, the DDDSU slot format can be repeated according to the TDD UL-DL resource configuration information. That is, the repetition period of the TDD configuration is 5 slots (5 ms for 15 kHz SCS, 2.5 ms for 30 kHz SCS, etc.).
[0189] Next, cases in which SBFD is operated together with TDD in a specific frequency band are shown in (b)(1250), (c)(1260) to (d)(1270).
[0190] (b) Referring to (1250), the terminal can set a portion of the frequency band of the cell as a frequency band (1210) capable of uplink transmission. This band can be called an uplink subband (UL subband). And the uplink subband (UL subband) can be applied to all symbols of all slots. The terminal can transmit an uplink channel or signal scheduled for all symbols (1212) within the subband (UL subband). However, the terminal cannot transmit an uplink channel or signal in a band other than the subband (UL subband).
[0191] Referring to (c)(1260), the terminal may set some of the frequency bands of the cell as a frequency band (1220) capable of uplink transmission, and may set a time region in which the frequency band is activated. Here, this frequency band may be called an uplink subband (UL subband). In (c)(1260), the uplink subband (UL subband) is deactivated in the first slot, and the uplink subband (UL subband) may be activated in the remaining slots. Accordingly, the terminal may transmit an uplink channel or signal in the uplink subband (UL subband) (1222) of the remaining slots. Therefore, although the uplink subband (UL subband) is activated in units of slots here, whether it is activated or not may be set in units of symbols.
[0192] (d)(1270), the terminal can be configured with time-frequency resources capable of uplink transmission. The terminal can configure one or more time-frequency resources as time-frequency resources capable of uplink transmission. For example, some frequency bands (1232) of the first and second slots can be configured as time-frequency resources capable of uplink transmission. In addition, some frequency bands (1233) of the third slot and some frequency bands (1234) of the fourth slot can be configured as time-frequency resources capable of uplink transmission.
[0193] In the following description, a time-frequency resource capable of uplink transmission within a downlink symbol or slot may be referred to as an SBFD resource. Furthermore, a symbol within a downlink symbol for which an uplink subband is configured may be referred to as an SBFD symbol. Furthermore, a time-frequency resource capable of downlink reception within an uplink symbol or slot may be referred to as an SBFD resource. Furthermore, a symbol within an uplink symbol for which a downlink subband is configured may be referred to as an SBFD symbol.
[0194] For convenience, in the present disclosure, a band in which downlink channels or signals can be received, excluding uplink sub-bands, is referred to as a downlink sub-band. A terminal can configure at most one uplink sub-band per symbol, and at most two downlink sub-bands. For example, a terminal can be configured with one of {uplink sub-band, downlink sub-band}, {downlink sub-band, uplink sub-band}, or {first downlink sub-band, uplink sub-band, second downlink sub-band} in the frequency domain.
[0195] The above SBFD terminal can be configured with time resources capable of SBFD operation from the base station, and some slots or some symbols within the configured period can be configured as SBFD slots or SBFD symbols for SBFD operation. The terminal can transmit a signal on an uplink channel through an uplink subband within the configured SBFD time resources. The configured period can be a period of a TDD structure used in a conventional wireless communication system, an SSB transmission period of a base station, a frame period (e.g., 10 ms), an integer multiple of a frame period (e.g., 20 ms), or a period of a frame structure type newly defined for SBFD operation. SBFD time resource allocation can be performed by additionally indicating whether SBFD is supported in the TDD structure, or by defining a slot type dedicated to SBFD operation in addition to downlink, uplink, and special slots, and using this in a conventional TDD time resource allocation process. When additionally indicating whether SBFD is supported in the conventional TDD structure, the SBD time resource setting cycle may be a multiple of the TDD time resource setting cycle for time alignment with the TDD system. In this case, within the SBFD setting cycle, after indicating SBFD time resources within the TDD setting cycle length, whether SBFD is supported may be determined for each TDD setting cycle length unit.
[0196] The above SBFD terminal can perform uplink transmission in an uplink (U) symbol or an SBFD symbol in a 5G system. In addition to the interference that occurs in a conventional TDD system, in the SBFD system, additional interference for full-duplex communication operation may occur. For example, in a base station performing full-duplex communication using the SBFD operation, a downlink signal transmitted through a downlink subband may cause self-interference with uplink reception occurring simultaneously through an uplink subband in the same sector of the same base station, and the downlink signal may cause inter-sector cross link interference (inter-sector CLI) between adjacent sectors with uplink reception occurring simultaneously through an uplink subband in an adjacent sector of the same base station. In addition, in the base station operating the SBFD, downlink transmission through the downlink subband may cause cross-link interference (inter-gNB cross link interference, inter-gNB CLI) between adjacent base stations with respect to uplink reception occurring simultaneously in the uplink subband of the base station of the adjacent cell.
[0197] Therefore, the terminal can expect a better signal-to-noise ratio (SNR) for the signal transmitted in the U symbol or slot than in the SBFD symbol or slot, which may cause more interference, and as described above, differences in channel conditions may occur depending on the type of time resource. In the following description, in order to represent the channel conditions according to the type of time resource, a time interval in which a relatively better channel and a better SNR can be expected may be referred to as a first time interval, and a time resource in which a relatively worse channel and a worse SNR can be expected may be referred to as a second time interval. The unit of the time interval may be a symbol, a slot, or a specific time interval used for transmission in one transmission occasion. In the following disclosure, for convenience, a transmission opportunity for transmitting data in the first time interval is referred to as a first transmission opportunity, and a transmission opportunity for transmitting data in the second time interval is referred to as a second transmission opportunity. Similar names may be used for symbols and slots.
[0198] In summary, in the present disclosure, for PUSCH repetition type A and TBoMS, when the number of slots used for TBS calculation is N and the number of TBs repeatedly transmitted is K, the transmission opportunity n is defined for 0, 1, ..., N K-1. In the present disclosure, for PUSCH repetition type B, nominal repetition occurs as many times as the number of repetitive transmissions set by the base station K. Each nominal repetition can be divided into multiple actual repetitions due to slot boundaries or invalid symbols, etc., and the total number of actual repetitions that occurred for K nominal repetitions is K actual If we define , the transmission opportunity n is 0, 1, ..., K actual-1 is defined. In this case, the transmission opportunity in the first time interval can be regarded as the first transmission opportunity, and the transmission opportunity in the second time interval can be regarded as the second transmission opportunity. The first and second time intervals mentioned above can be applied not only to the SBFD system, but also to a system in which the difference in channel conditions for each time interval can be predicted in advance at the base station. The following embodiment can be applied to a system in which there is a difference in the expected SNR in different transmission opportunities and in which there is a difference in the amount of information contained in a bit depending on the index of the transmission bit.
[0199] FIG. 13 is a diagram illustrating an example that may occur when performing PUSCH transmission through an uplink subband and UL slot within an SBFD slot in an SBFD system.
[0200] Since the UL slot may have better channel conditions compared to the SBFD slot, the time interval used for uplink transmission within the UL slot may be viewed as the first time interval, and the time interval used for uplink transmission within the SBFD slot may be viewed as the second time interval.
[0201] Referring to FIG. 13, when 4 repetition transmissions are performed using PUSCH repetition type A as in (a)(1320), and the SBFD slot setting at this time is {XXXU, X = SBFD slot, U = UL slot}, the n=3 transmission opportunity in which the 4th repetition (1303) occurs corresponds to the first transmission opportunity, and the other n=0,1,2 transmission opportunities (1300, 1301, 1302) correspond to the second transmission opportunities. When the SBFD time resource as in (a)(1320) is set and the terminal transmits one TB over 4 slots using TBoMS, the bit string transmitted in the n=3 transmission opportunity (1303) of the last slot can be transmitted in the first time interval, and the remaining bit strings can be transmitted in the second time interval (1300, 1301, 1302). As in the example above, two types of transmission opportunities may intersect for a single TB. Alternatively, as in (b)(1330), all transmission opportunities may occur only within the same type of time interval. In (b)(1330), SBFD uplink subbands are configured for four slots, and transmission opportunities at 1310, 1311, and 1312 all correspond to the second transmission opportunity.
[0202] When transmitting the above LDPC-encoded codeword, the type of time interval over which the information bits are transmitted can affect the LDPC code's decoding performance. By transmitting the information bits over a better channel, the transmitter can increase the signal-to-noise ratio (SNR) at the receiver, making the received signal clearer and improving error correction capabilities. Therefore, transmitting as many information bits as possible over the first time interval rather than the second time interval can improve LDPC code encoding performance and system performance.
[0203] The following embodiments disclose various methods for setting the starting point of a transmission bit in a system in which there is a difference in channel conditions for each specific time interval, such as the first and second time intervals, and in a case in which there is a difference in the amount of information for each bit string, such as an LDPC code.
[0204] The terminal applies the RV sequence to each transmission opportunity, which is determined by the DCI or upper layer message. id can be determined. The base station or the upper layer may redefine the RV sequence to be set to the terminal or change the order of the RV sequence in consideration of the time point when the first transmission opportunity with better SNR appears when there is a difference in channel conditions according to the transmission opportunities, such as the first and second transmission opportunities (the first transmission opportunity may be a transmission opportunity (PUSCH repetition type A or TBoMS) or an actual transmission (PUSCH repetition type B) included in the first time interval, and the second transmission opportunity may be a transmission opportunity (PUSCH repetition type A or TBoMS) or an actual transmission (PUSCH repetition type B) included in the second time interval). For example, the base station may define a new RV sequence or change the order of the RV sequence so that self-decodable RV0 or RV3 is transmitted when the first transmission opportunity among all transmission opportunities in which TB is transmitted is present.
[0205] In the present disclosure, the start position of the transmission bit set may be calculated by the terminal, the base station, and the upper layer with reference to the timing of the first transmission opportunity, and may be used for data transmission and reception, or may be calculated by the base station and the upper layer with reference to it and then indicated to the terminal. At this time, the terminal may be indicated the start position of the transmission bit through at least one of the DCI, MAC-CE, or RRC message. The terminal may transmit data from the start position of the set transmission bit, and the base station may store the received data with reference to the start position of the set transmission bit, and then attempt error correction of the received data based on a soft combining operation. In the following, the PUSCH repeated transmission may be understood as at least one of repeated transmission according to the DG, repeated transmission according to the CG, or TBoMS transmission. The embodiments disclosed below describe methods for the terminal to set the RV for each transmission opportunity during uplink transmission with reference to the timing of the first transmission opportunity. In the n'th transmission opportunity corresponding to the first transmission opportunity, the base station may indicate an RV sequence such that RV0 or RV3 capable of self-decoding is set. When multiple first transmission opportunities exist, the following methods may be performed for the pth first transmission opportunity (where p is a specific natural number). For convenience, the present disclosure describes an example of a method for setting RV0 for the first transmission opportunity that appears first; the same method may be applied to a first transmission opportunity of a specific order other than the first, or to an RV order other than RV0, or to the starting point of a newly defined bit.
[0206] <Example 1>
[0207] This embodiment proposes a method for setting the RV value by modifying the content of the DCI or upper layer message depending on when the first transmission opportunity appears during a PUSCH repeat transmission. In the first transmission opportunity among all transmission opportunities in which a TB is transmitted, RV0 is set to rv id The RV sequence can be set up via DCI and upper layer messages to be used.
[0208] Method 1: When performing PUSCH repetitive transmission, the total transmission opportunities for TB transmission in the SBFD system are n=0, 1, ..., N K-1 or n=0, 1, ..., K actual In the n'th transmission opportunity corresponding to the first transmission opportunity among the first transmission opportunities, the base station can instruct the RV sequence so that self-decryption is possible RV0 is set. Table 17 is an example of setting the RV sequence so that RV0 can be set in the n'th transmission opportunity.
[0209] n' mod 4rv id in DCIRV sequence00{0, 2, 3, 1}11{1, 0, 2, 3}23{3, 1, 0, 2}32{2, 3, 1, 0}
[0210] In case of DG PUSCH, rv transmitted as DCI id This can be done by changing the rv received by the terminal as DCI. id The RV sequence to be used in repeated transmission can be determined by referring to Table 18, for example, according to the value. For example, the base station can determine the RV sequence to be used in repeated transmission through DCI. id=2 can be instructed to the terminal. In this case, if n' = 3 is satisfied, the terminal can use the RV sequence of {2, 3, 1, 0}. In the case of CG PUSCH, if the SBFD resource configuration is static or semi-static, the base station can define a sequence in which RV0 can be set at the n'th transmission opportunity as shown in Table 17 through a message of a higher layer, or can define a new sequence rather than an existing sequence and instruct the terminal to do so.
[0211] rv id indicated by the DCI scheduling the PUSCHrv id to be applied to n th transmission occasion (repetition Type A) or n th actual repetition (repetition Type B)n mod 4 = 0n mod 4 = 1n mod 4 = 2n mod 4 = 300231223103310211023
[0212] As a method 2, in the SBFD system, the base station may configure the RV sequence so that RV0 is always configured for the n'th transmission opportunity, which corresponds to the first transmission opportunity among transmission opportunities within a certain period, such as a period of one SBFD time resource configuration or a TDD slot configuration period. In this case, the RV sequence may be configured separately for each period. More specifically, the terminal may distinguish slots in which PUSCH is repeatedly transmitted by the TDD slot configuration period. That is, the PUSCH repeated transmission slots are identified among the slots within one TDD slot configuration period. The terminal may obtain the transmission opportunity index of the PUSCH repeated transmission slots within the slots of one TDD slot configuration period and may assign the index in time order to the PUSCH repeated transmission slots among the slots within one TDD slot configuration period. Here, the index may start from 0 and increase sequentially. In addition, the terminal may assign an index separately and independently to the PUSCH repeated transmission slots among the slots within different TDD slot configuration periods. The terminal may determine the RV sequence based on the index. When the terminal determines the RV sequence, if there is a first transmission opportunity among the slots within a specific TDD slot setting cycle, RV0 can be set for the first transmission opportunity.
[0213] As a method 3, the cycles of the RV sequence can be applied independently for different types of transmission opportunities.
[0214] Figure 14 is a diagram illustrating an example of time resources that may appear when one TB is transmitted over multiple transmission opportunities in an SBFD system.
[0215] According to Fig. 14, in the case of (a)(1470), when n=2 among the total transmission opportunities n=0, 1, 2, 3, and 4 located in slots 1402, 1403, 1404, 1406, and 1407 according to method 1, (1410) corresponds to the first transmission opportunity. Since n' mod 4 = 2 is established, the base station can instruct the terminal to the RV sequence in which the third value is 0 through a DCI or a higher layer message. For example, a sequence of {3, 1, 0, 2} can be used in the terminal, and the rv actually applied for the total transmission opportunity id The sequence becomes {3, 1, 0, 2, 3}, and at the first transmission opportunity, n=2(1410), RV0 is used for transmission.
[0216] (b) In the case of (1475), the RV sequence {2, 3, 1, 0} can be used according to method 1 for the first transmission opportunity (n=3, 1430) among the transmission opportunities of n=0, 1, 2, 3, and 4 located in slots 1421, 1422, 1423, 1424, and 1425. In this case, the actual applied rv for the entire transmission opportunity id RV0 is set for the first transmission opportunity n=3(1430) in the order {2, 3, 1, 0, 2}.
[0217] (c)(1480) For the first transmission opportunity (n=0, 1450) among transmission opportunities n=0, 1, 2, 3, 4 and 5 located in slots 1444, 1445, 1446, 1447, 1448, 1449, if method 1 is followed, the terminal can use the RV sequence of {0 2, 3, 1}. Therefore, the rv that is actually applied for the entire transmission opportunity id In order, RV0 is set for the first transmission opportunity, n=0 (1450), and RV2 is set for the second transmission opportunity, n=5 (1451).
[0218] In this case, method 2 is applied, so that it is possible to check n' corresponding to the first transmission opportunity for each transmission opportunity within one TDD period. In this case, in the first TDD period (1455) of (c)(1480), since n'=0 for the first first transmission opportunity, the base station can instruct the terminal to the RV sequence of {0, 2, 3, 1}. In the second TDD period (1456), the transmission opportunities belonging to the first period are not considered, and the base station checks the index of the first transmission opportunity only among the transmission opportunities belonging to the second TDD period. That is, in the second TDD period (1456), transmission opportunities of n=0, 1, 2, 3, and 4 are located in slots 1445, 1446, 1447, 1448, and 1449, and for the first 1st transmission opportunity (1451) of slot 1449, n'=4 is calculated, and the base station can indicate the sequence {0, 2, 3, 1} corresponding to n'=4, and the terminal can use the RV sequence of {0, 2, 3, 1} in the second TDD period. In order to set the index of the transmission bit, the transmission opportunities of the existing n=0, 1, 2, 3, 4, and 5 were divided into n=0 in the first TDD period, and n=0, 1, 2, 3, and 4 in the second TDD period, but all of the above transmissions are for the same TB. This distinction between transmission opportunities may not be valid for purposes other than setting the index of a transmission bit during the transmission process.
[0219] In summary, when using method 2, the actual applied rv for the entire transmission opportunity idare in the order of {0, 0, 2, 3, 1, 0}, where the first RV index 0 is applied within the first TDD cycle (1455), and the second to sixth RV indices 0, 2, 3, 1, 0 are applied within the second TDD cycle (1456). This allows RV0 to be set for both the first transmission opportunities 1450 and 1451 that occur first within each TDD cycle.
[0220] Alternatively, the RV sequence cycle can be applied independently to the first transmission opportunity and the second transmission opportunity, following method 3. For example, consider a case where the RV sequence {0, 3, 0, 3} is applied to the first transmission opportunity, and the RV sequence {0, 2, 3, 1} is applied to the second transmission opportunity. In this case, the rv actually applied to the entire transmission opportunity of (c)(1480) id are {0, 0, 2, 3, 1, 3} in order. That is, RV0 and RV3 are used for the first and sixth transmission opportunities (1450, 1451), respectively. In the above embodiment, in addition to {0, 2, 3, 1}, various RV sequences used in existing standards or newly defined sequences such as {0, 3, 2, 1} may be used.
[0221] Instead of receiving the intended RV sequence via DCI or a higher layer message as in Methods 1, 2, and 3, the RV to be used for each transmission opportunity may be determined by the terminal. For example, the terminal may first confirm the location of the first transmission opportunity during uplink transmission and then determine the RV to be used for the first transmission opportunity. The terminal may report this fact to the base station, or the base station and higher layers (RRC or MAC layer) may refer to the time resource settings and PUSCH transmission settings to confirm the location of the first transmission opportunity in advance. Furthermore, the base station or higher layers may anticipate a change in the RV sequence or RV index based on the confirmed location of the first transmission opportunity and receive uplink data.
[0222] For example, when CG PUSCH repetitive transmission is performed and the SBFD time resource setting is irregular, the transmission RV may be determined by the terminal. Fig. 14 (d) (1485) illustrates an example of a case where CG PUSCH repetitive transmission is set. It is assumed that the period is 4 slots and PUSCH repetition type A with K=2 is performed in each period, and a total of 3 CG PUSCH transmissions are illustrated (1470, 1471, 1472). Here, each CG PUSCH can be repeatedly transmitted in K=2 consecutive slots, and the RV value of each slot can be set in the upper layer parameter repK-RV.
[0223] If the RV sequence defined by the upper layer parameter repK-RV is {0, 2, 3, 1}, then for PUSCH repetitions of K=2, rv of {0, 2} id is used. For the second CG PUSCH transmission (1471), the first transmission opportunity is the first slot of K=2 repetitions. Therefore, rv in the first transmission opportunity id = 0 can be set. However, for the 3rd CG PUSCH transmission (1472), rv is set at the first transmission opportunity. id=2 can be set. According to the above example, RV0 is not set at the first transmission opportunity for each transmission of CG PUSCH.
[0224] In this case, the terminal can set RV0 for the first transmission opportunity of each CG PUSCH transmission by applying different RV sequences to each CG PUSCH transmission. For example, in the case of the third CG PUSCH transmission (1472), since the first transmission opportunity is the second slot, n' can be determined as 1. Since the first transmission opportunity of the second CG PUSCH transmission (1471) is the first slot, n' can be determined as 0. Here, n' can use the index of the repeated transmission of each CG PUSCH transmission. That is, the index of the first repeated transmission of each CG PUSCH transmission is 0 and can increase in time order. Since n' is 1 for the third CG PUSCH transmission (1472), the terminal can use {1, 0, 2, 3}, which is a sequence in which RV0 is set for the second slot. Additionally, the terminal may ensure that all RV indices within the RV sequence consist of only self-decodable RV indices, such as {0, 0, 0, 0} or {0, 3, 0, 3}.
[0225] The terminal may consider an individual sequence cycle for the first transmission opportunity, or may overwrite the existing RV configuration so that RV0 or RV3 is always transmitted for the first transmission opportunity. If the terminal changes the RV-related configuration on its own depending on the timing of the first transmission opportunity during CG PUSCH repetitive transmission, the information required for this change may be agreed upon in advance between the terminal and the base station via RRC signaling or MAC-CE. In this case, the terminal may not report the changed RV-related configuration to the base station, or may report only some information excluding the pre-agreed content to the base station. The base station may calculate the index of the received bit by referring to the reception of the CG PUSCH repetitive transmission with reference to the pre-agreed content, or may additionally calculate the index of the received bit with reference to the information reported by the base station.
[0226] FIG. 15 is a diagram illustrating an example in which an embodiment of the present invention is applied according to SBFD time resource settings.
[0227] According to FIG. 15, (a)(1540) illustrates an example of SBFD time resource configuration that may occur when performing uplink transmission using transmission opportunities of n=0, 1, ..., 5. This example may also be used as an example of PUSCH repetition type A or TBoMS. A total of three transmission opportunities, n=0, 1, 4, correspond to the first transmission opportunity, and the above embodiment may be applied by setting n'=0, 1, or 4. In case that consecutive first transmission opportunities occur, such as n=0, 1, an RV sequence in which self-decodable RVs appear consecutively, such as {0, 3, 1, 2}, may be used so that both self-decodable RV indices are applied to the first transmission opportunity. This RV sequence may be configured by the base station or the terminal.
[0228] (b)(1550) is a diagram illustrating an example of time resource configuration in an SBFD system that may correspond to PUSCH repetition type B. The first transmission opportunity among a total of four transmission opportunities with n=0, 1, 2, and 3 is n=3(1530), so n'=2. Since n' mod 4 = 2, the base station can instruct the terminal to an RV sequence in which the third value is 0 through a DCI or a higher layer message. For example, a sequence of {3, 1, 0, 2} can be used by the terminal, and the rv actually applied for the entire transmission opportunity id are {3, 1, 0} in order, and RV0 is used for transmission at the first transmission opportunity n=2 (1530). Alternatively, the terminal may select RV0 at the transmission opportunity n=2. For example, when the existing RV sequence set by DCI or upper layer message is {0, 2, 3, 1}, the actually applied rv id can be {2, 3, 0} in order. Alternatively, the terminal can apply an RV index that can be self-decrypted only in the transmission opportunity corresponding to the first transmission opportunity without changing the entire set RV sequence. In this case, the actually applied rv id can be {0, 2, 0 (or 3)} in that order.
[0229] <Example 2>
[0230] This embodiment proposes a method for setting the RV value according to the time point at which the first transmission opportunity occurs during repeated PUSCH transmission. The offset value rv is set based on the time point at which the first transmission opportunity occurs. offset , and the corresponding offset value may be used to determine the RV sequence. For example, the RV indexes applied to each PUSCH repeated transmission are n and rv, depending on the value of the RV field included in the DCI. offset It can be decided according to .
[0231] For example, when operating with DG PUSCH repeat transmission, rv received as DCI id and rv offset The RV sequence can be determined according to Table 19 below with reference to rv offset may be predetermined, set by upper layer signaling, or / and determined based on the value of the RV field included in the DCI. This embodiment is similar to the embodiment 1 above in that the total transmission opportunities n=0, 1, ..., N K-1 or n=0, 1, ..., K actual - Applies to 1 or to transmission opportunities that fall within a certain period, such as a period of one SBFD time resource setting in an SBFD system or a TDD slot setting period, and rv for each said certain period. offset A value can be set. The offset value can be directly calculated by the terminal and base station, or can be calculated first on one side and then transmitted to the other. For convenience, n' refers to the transmission opportunity index of the first transmission opportunity within a given period, for example. Alternatively, for various embodiments, n' can be defined as the index of the second, not the first, or the first transmission opportunity in any order.
[0232] rv id indicated by the DCI scheduling the PUSCHrv id to be applied to n th transmission occasion (repetition Type A or Type B)(n+rv offset )mod 4 = 0(n+rv offset ) mod 4 = 1(n+rv offset ) mod 4 = 2(n+rv offset ) mod 4 = 300231223103310211023
[0233] The terminal modifies (n+rv) for n transmission opportunities. offset, 4)+1st value can be selected and used from the RV sequence. In case of DG PUSCH, the RV sequence is the rv received by the terminal as DCI. id It may vary depending on the value and follows Table 15 above. rv id If =0, {0, 2, 3, 1}. rv id If =2, {2, 3, 1, 0}, rv id If =3, {3, 1, 0,2}, rv id If =1, {1, 0, 2, 3} become RV sequences respectively. In the case of CG PUSCH, the terminal can receive the RV sequence to be used from the upper layer message. In this case, rv offset The value can be determined to set a specific RV (e.g., RV0) value at the transmission opportunity of n'. For any RV sequence, the terminal sets rv offset The value is (n'+ rv offset ) mod 4 = "First RV0 index in a RV sequence". Here, First RV0 index in a RV sequence represents the index where RV0 appears in an RV sequence (or the index indicating the position or order where RV0 is located in an RV sequence), and is a parameter that is 0 if the RV sequence is {0, 2, 3, 1} and 1 if the RV sequence is {1, 0, 2, 3}. For example, rv offset The value can be obtained as follows:
[0234] [Equation 2]
[0235] rv offset = (First RV0 index in RV sequence - (n' mod 4)) mod 4
[0236]
[0237] For example, if the RV sequence of {0, 2, 3, 1} is set as a higher layer message, rv offset=(0-(n' mod 4) mod 4 can be determined as follows. If the terminal is set to the RV sequence of {0, 3, 0, 3}, the terminal is rv offset = (0 - (n' mod 4)) mod 4 can also be used. Note that for the RV sequence {0, 3, 0, 3}, it can also be viewed as the RV sequence {0, 3}, in which case, rv offset = (First RV0 index in RV sequence - (n' mod 2)) mod 2 = (0-(n' mod 2))mod 2.
[0238] rv offset The formula for calculating may be determined differently depending on the RV sequence used by the terminal and the value of n'. Alternatively, the offset value may be transmitted to the terminal through DCI or a higher layer message, or the terminal may check n' and calculate and use it.
[0239] For example, in case of (a)(1470) in Fig. 14, n' = 2. When the RV sequence set to the terminal for PUSCH repetitive transmission is {0, 2, 3, 1}, rv according to the above mathematical expression 2 offset =(0 - (2 mod 4)) mod 4 = 2 is calculated. Therefore, the terminal can select the mod(n+2, 4)+1th value from the RV sequence of {0, 2, 3, 1}. Accordingly, the actual RV value used for each transmission opportunity is {3, 1, 0, 2, 3}, and in the first transmission opportunity (1410), uplink data according to RV0 for n=2 (1410) can be transmitted.
[0240] Similarly, in the case of (b)(1475) of Fig. 14, n'=3. Assuming that the RV sequence set to the terminal for PUSCH repetitive transmission is {3, 1, 0, 2}, rv according to the above example offset =(2 - (3 mod 4)) mod 4 according to rv offset= can be calculated as 3. Therefore, the terminal can select the mod(n+3, 4)+1th value for each n in the sequence {3, 1, 0, 2}. The RV values applied to each transmission opportunity can be organized as {2, 3, 1, 0, 2}, and RV0 can be used for n=3 (1430) corresponding to the first transmission opportunity.
[0241] In case of (c)(1480) of Fig. 14, considering the index of the first transmission opportunity for the total transmission opportunities n=0, 1, ..., 5, n'=0. If the RV sequence set in the terminal is {0, 2, 3, 1}, then rv according to the above example offset =(0-(n' mod 4)) mod 4 =0, and therefore the terminal can select and use the mod(n+0, 4)+1th value from the sequence for each transmission opportunity n, and therefore the RV values used for actual transmission can be {0, 2, 3, 1, 0, 2}. In this case, RV2 is used for n=5.
[0242] If we consider the first transmission opportunity index as n' for a transmission opportunity within a TDD cycle, not the entire transmission opportunity, then n'=0 for the first TDD cycle (1455), and n'=4 for the second TDD cycle (1456). Assuming that the sequence set in the terminal is {2, 3, 1, 0}, then according to the above example, rv offset = (3-(n' mod 4)) mod , so for the first period rv offset For this 3rd, second cycle, rv offsetThis can be calculated as 3. Therefore, within the first TDD cycle, for n=0, if the mod(0+3, 4)+1= 4th value is selected from the sequence {2, 3, 1, 0}, then RV0 is set at n=0. Within the second TDD cycle, starting from n=0 and independently indexing the transmission opportunities again, the RV value set at the transmission opportunity of n'=4, which corresponds to the first transmission opportunity, is RV0, which is the mod(4+3, 4)+1=4th value of the {2, 3, 1, 0} sequence. Therefore, if the RV sequence used for actual transmission is organized for the entire transmission opportunity n, it can be {0, 0, 2, 3, 1, 0}. In the above sequence, the first 0 is the RV value set for the transmission opportunity within the first TDD cycle (1455), and the second 0 to the sixth 0 are the RV values set for the transmission opportunity within the second TDD cycle (1456).
[0243] Figure 14 (d)(1485) is a diagram illustrating an example when the terminal is set to K=2 CG PUSCH repetition type A of period 4. In the case of the third CG PUSCH transmission (1472), when n'=1 and the RV sequence set to the terminal as a higher layer message is {0, 2, 3, 1}, rv according to the above example offset =(0-(n' mod 4)) mod 4 =3, and therefore the terminal can select the mod(n+3, 4)+1th value within the {0, 2, 3, 1} sequence as the RV value at each transmission opportunity n. Therefore, in this case, the RV sequence actually used in the 3rd CG PUSCH repetition can be {1, 0}.
[0244] In Fig. 15, (b)(1550) illustrates an example of PUSCH repetition type B. The first transmission opportunity among a total of four transmission opportunities corresponds to the actual transmission n=3(1530), so n'=3. If the RV sequence set in the terminal is {0, 2, 3, 1}, then according to the above example, rvoffset =(0-(n' mod 4))mod4=1, and the RV value set at each transmission opportunity of n is the mod(n+1, 4)+1th value of the {0, 2, 3, 1} sequence, which becomes {2, 3, 1, 0} in order, and RV0 is set at the transmission opportunity of n'.
[0245] When performing repeated transmissions with DG PUSCH, the offset value can be used directly as specified in Table 18 below. The offset value is the rv value that the terminal receives as DCI. id and can be determined by the value of n', for example, similar to the example above, for any RV sequence (n'+ rv offset ) mod 4 = "First RV0 index in a RV sequence". Examples of offset values that can be used in Table 19 for DG PUSCH are summarized in Table 20. For example, if a terminal performing DG PUSCH repetition type A transmits rv as DCI id Assuming that =0 is received and n'=2, rv offset = (0-(2 mod 4)) mod 4 = 2, and therefore the RV value to be used for each n can be determined according to Table 20 below (Table 21 is organized based on Tables 19 and 20 according to the above example).
[0246] rv id indicated by the DCI scheduling the PUSCHrv offset 0(0-(n' mod 4)) mod 42(3-(n' mod 4)) mod 43(2-(n' mod 4)) mod 41(1-(n' mod 4)) mod 4
[0247] rv id indicated by the DCI scheduling the PUSCHrv id to be applied to nth transmission occasion (repetition Type A, n'=2)(n+2)mod 4 = 0(n+2) mod 4 = 1(n+2) mod 4 = 2(n+2) mod 4 = 300231
[0248] Alternatively, the offset value may be considered as in Table 22 during DG PUSCH operation.
[0249] rv id indicated by the DCI scheduling the PUSCHrv id to be applied to n th transmission occasion (repetition Type A or Type B)n mod 4 = 0n mod 4 = 1n mod 4 = 2n mod 4 = 30(0+rv offset ) mod 4(2+rv offset ) mod 4(3+rv offset ) mod 4(1+rv offset ) mod 42(2+rv offset ) mod 4(3+rv offset ) mod 4(1+rv offset ) mod 4(0+rv offset ) mod 43(3+rv offset ) mod 4(1+rv offset ) mod 4(0+rv offset ) mod 4(2+rv offset ) mod 41(1+rv offset ) mod 4(0+rv offset ) mod 4(2+rv offset ) mod 4(3+rv offset ) mod 4
[0250] The terminal sets a specific offset value (rv) to the RV value. offset) can be used to change the RV value and set a specific RV value (e.g., RV0) for the first transmission opportunity. If the first transmission opportunity overlaps with the n'th PUSCH repetitive transmission, then, referring to Table 18, if the RV value of n' mod 4 is X, (X + rv offset ) rv to satisfy mod 4 = 0 offset This can be determined. That is, rv offset can be determined as follows:
[0251] rv offset = (4 - X) mod 4
[0252] For example, in case of receiving SBFD time resource setting such as (a)(1470) in Fig. 14, n'=2. rv transmitted as DCI for DG PUSCH operation id If is 2, X is 1, and rv offset can be determined as 3. Therefore, the RV sequence used can be {1, 2, 0, 3} according to Table 21. Therefore, the RV values used for the entire transmission opportunity can be {1, 2, 0, 3, 1} in order. Therefore, RV0 can be set for the first transmission opportunity where n'=2.
[0253] In another embodiment, the RV value may be set using an RV sequence obtained by using different offset values of the same RV sequence for each of the first and second transmission opportunities. For the purpose of explaining this embodiment, for convenience, the RV sequence is referred to as {RV a , RV b , RB c , RV d}. The indices of the PUSCH repetitions belonging to the first transmission opportunity can be assigned in chronological order starting from 0. The indices of the PUSCH repetitions belonging to the second transmission opportunity can be assigned in chronological order starting from 0. Here, the indices of the PUSCH repetitions belonging to the first transmission opportunity and the indices of the PUSCH repetitions belonging to the second transmission opportunity can be assigned independently. The RV sequence of the PUSCH repetitions belonging to the first transmission opportunity can be determined as follows.
[0254] [Equation 3]
[0255] {(RV a + rv offset1 ) mod 4, (RV b + rv offset1 ) mod 4, (RV c + rv offset1 ) mod 4, (RV d + rv offset1 ) mod 4}
[0256] rv here offset1 is an offset value for PUSCH repetitions belonging to the first transmission opportunity. The RV sequence of PUSCH repetitions belonging to the second transmission opportunity can be determined as follows.
[0257] [Equation 4]
[0258] {(RV a + rv offset2 ) mod 4, (RV b + rv offset2 ) mod 4, (RV c + rv offset2 ) mod 4, (RV d + rv offset2 ) mod 4}
[0259] rv here offset2 is the offset value for PUSCH repetitions belonging to the second transmission opportunity. Note that rv offset1 Mainland RV offset2 can be 0.
[0260] In another embodiment, the same RV sequence may be used for the first and second transmission opportunities, but different offsets may be used when selecting the RV values used in n transmission opportunities, thereby making the RV values used in each transmission opportunity different. For the purpose of explaining this embodiment, the RV sequence may be referred to as {RV a , RV b , RB c , RV d}. The indices of PUSCH repetitions belonging to the first transmission opportunity can be assigned in chronological order from 0 and are denoted as n. The indices of PUSCH repetitions belonging to the second transmission opportunity can be assigned in chronological order from 0 and are denoted as m. Here, for the first transmission opportunities, {RV a , RV b , RB c , RV d} mod(n+rv) within the sequence offset1 , 4)+1st value can be selected as RV value. In case of second transmission opportunities, {RV a , RV b , RB c , RV d} mod(m+rv) within the sequence offset2 , 4)+1st value can be selected as RV value. rv offset1 Mainland RV offset2 can be 0.
[0261] The above offset values may be determined by the base station or a higher layer and then indicated to the terminal. Alternatively, the terminal, base station, or higher layer may independently determine the location of n', calculate it, and use it for data transmission and reception. The above offset values may be calculated in various ways with reference to the timing of the first transmission opportunity and used to determine the starting location of the transmitted data.
[0262] <Example 3>
[0263] In the third embodiment, a method for setting a transmission bit index according to the timing of the first transmission opportunity in TBoMS is described. When transmitting uplink data using TBoMS, the terminal selects and transmits bits within one TB equal to the length of bits that can be transmitted in each transmission opportunity, starting with k0 determined based on Table 16 above. The terminal sets the rv id Although the length of the information bits transmitted in the first transmission opportunity can be increased by adjusting k0 of the first transmission opportunity (n=0) by a value, it may be difficult to maximize the length of the information bits transmitted in the first transmission opportunity because k0 can have one of at most four values. Therefore, the following method is proposed to solve this problem.
[0264] The TB to be output when TBoMS is in operation is of length N cb It is stored in the circular buffer of and reads from the buffer as many bits as can be transmitted in the corresponding transmission opportunity starting from 0 calculated for each transmission opportunity and transmits them to the base station. Below, a method is proposed to maximize the information bits transmitted in the pth first transmission opportunity among the total transmission opportunities when TBoMS operates. For convenience, p is assumed to be 1 in the embodiment below. Therefore, a method is proposed to maximize the information bits transmitted in the first first transmission opportunity among the total transmission opportunities when TBoMS operates. At this time, it is assumed that the RV value set by the terminal operating as TBoMS is RV0. In the case where TBoMS performs repetitive transmission, setting various RVs rather than setting only a single RV can further improve the decoding capability. Therefore, a method of maximizing the information bits transmitted in the first first transmission opportunity when RV0 is transmitted is proposed. This setting method can also be applied to other RVs.
[0265] For example, when a terminal transmits one TB across N slots with TBoMS, it first sets k0 to rv in the DCI or upper layer message for the uplink slot corresponding to the first transmission opportunity among all slots. id is calculated according to Table 14. And among the other slots, for uplink data transmission in slots preceding the very first first transmission opportunity, the value of k0 is k0 = (N cb + k'0- H prior - τ prior )mod N cb Indicates the bit index at which transmission will begin in the next slot among the LO code words, and H prior represents the number of bits that can actually be transmitted in the current slot when UCI multiplexing is not assumed, and τ represents the number of filler bits whose actual transmission in the current slot will be omitted when UCI multiplexing is not assumed. In addition, for uplink data transmission in slots after the very first first transmission opportunity corresponding to the remaining slots, k0 = (k'0 + H + τ) mod N cb can be calculated as . In this case, k'0 is the length N cb Among the input code words, H represents the bit index that started transmission in the previous slot, H represents the number of bits actually transmitted in the previous slot when UCI multiplexing is not assumed, and τ represents the number of filler bits whose actual transmission is omitted in the previous slot when UCI multiplexing is not assumed. In this case, the above method can also be applied to the second, or any integer p-th, first transmission opportunity other than the first.
[0266] For example, a terminal that has received time resource settings such as (b)(1475) of Fig. 14 sends rv through DCI or a higher layer message. id Assume that the TBoMS operation is performed after RV0 is set. At this time, the length of the code word encoded using base graph 2 is N. cbIt can be assumed that the number of bits is 14,400, the length of the information bits is 2,880 bits, the 2,617th bit to the 2,880th bit within the information bits are set as filler bits, the number of slots N used for TBoMS is 5, and 1,728 bits can be transmitted for each slot. If RV0 is set, k0 = 0 calculated according to Table 14, and the terminal can set k0 = 0 for the transmission opportunity of n = 3 corresponding to the very first transmission opportunity. At this time, for the transmission opportunity of n = 2, k0 = 12,672 can be calculated, for the transmission opportunity of n = 1, k0 = 10,944 can be calculated, for the transmission opportunity of n = 0, k0 = 9,216 can be calculated, and for the transmission opportunity of n = 4, k0 = 1,728 can be calculated. This allows maximizing the information bits transmitted in the first transmission opportunity when RV0 is set.
[0267] The above method is N cb Another method may include using a circular buffer of length and starting transmission from the first transmission opportunity of the desired sequence number.
[0268] Another way is to calculate the total number of bits H that can be transmitted during TBoMS operation. total The starting index of the bits transmitted in the first transmission opportunity during TBoMS operation can also be adjusted by using a circular buffer of length. Assuming the same situation as the above example, the terminal transmits a total of 8,640 information bits from bit index 0 to 8,903 of the entire code word on the uplink, of which 264 filler bits are excluded from the actual transmission. The terminal transmits H from 0 to 8,903. total = After storing the information bits in a circular buffer of 8,904, let n' be the transmission opportunity index corresponding to the very first transmission opportunity, H total - Σ n<n'TBoMS can be performed by reading bits from the index of (H+τ). For example, if n'=2, the terminal sets 8904-(1728*2+0)=5448 to k0 in the slot corresponding to n=0, and for the subsequent slots, k0= (k'0+ H + τ)mod H total can be set. Therefore, for each transmission opportunity, the starting bit index is {5448, 7176, 0, 1728, 3720} in order. When RV0 is used for TBoMS operation, the terminal can maximize the information bits in the first transmission opportunity.
[0269] <Example 4>
[0270] Next, a method for transmitting UCI at the first transmission opportunity when UCI is multiplexed on PUSCH is described. In an NR system, a PUCCH can be defined to transmit uplink control information (UCI) including at least one of hybrid automatic repeat request acknowledgment (HARQ-ACK), channel state information (CSI), scheduling request (SR), and beam-related information. UCI is generally transmitted through PUCCH, but UCI can also be transmitted through physical uplink shared channel (PUSCH) upon request or instruction from the network. In this case, UCI can be transmitted together with data or only UCI can be transmitted without data, which is called UCI multiplexing. In a system where the first transmission opportunity or the second transmission opportunity described above exists, UCI can be multiplexed for repeated PUSCH transmission. In this case, just as the information bits in the LDPC encoded code word were transmitted preferentially in the first transmission opportunity rather than the second transmission opportunity, the terminal can transmit control information that may significantly affect system performance preferentially in the first transmission opportunity rather than the second transmission opportunity.
[0271] FIG. 16 is a diagram illustrating an example of selecting a PUSCH repetition that multiplexes UCI when performing PUSCH repetitive transmission using n=0,1,2, and 3. Resources scheduled for PUCCH and resources for PUSCH repetitive transmission may overlap. FIG. 16 (a) (1630) is a diagram illustrating a UE searching for whether a first transmission opportunity exists for all transmission opportunities (1601, 1602, 1603, 1604). If a first transmission opportunity does not exist in the above range (1600), the UE may multiplex UCI to the PUSCH according to the conventional operation, and if a first transmission opportunity exists in the above range, the UE may preferentially multiplex UCI in the first transmission opportunity. In this case, if there are multiple first transmission opportunities, the UE may select one of the first transmission opportunities. In this example, for convenience, an example in which the UE selects the first transmission opportunity that appears first within the time range searched by the UE is described. In (a)(1630), n=3 is assumed as the first transmission opportunity, and other transmission opportunities are assumed as second transmission opportunities. Therefore, the terminal can multiplex UCI on the PUSCH transmitted in the transmission opportunity of n=3 among the multiple transmission opportunities.
[0272] In Fig. 16 (b) (1640), when the above-mentioned overlap occurs, the terminal can identify the timing of the first transmission opportunity among the subsequent transmission opportunities starting from the transmission opportunity of the PUSCH repeated transmission in which the overlap first occurs (1612) (1612, 1613, 1614). If the first transmission opportunity does not exist in the above-mentioned range (1610), the terminal can multiplex UCI onto the PUSCH following the conventional operation, and if the first transmission opportunity exists in the above-mentioned range, the terminal can preferentially multiplex UCI onto the first transmission opportunity. Accordingly, the terminal can perform UCI multiplexing on the PUSCH transmitted in the transmission opportunity (1614) of n=3 corresponding to the first transmission opportunity.
[0273] PUCCH and PUSCH can operate based on different SCSs. Figure 16 (c) (1650) schematically illustrates an example in which PUCCH is scheduled with an SCS of 15 kHz and PUSCH is scheduled with an SCS of 30 kHz. The UE can search for the first transmission opportunity only for transmission opportunities of repeated PUSCH transmissions that overlap with the PUCCH (1622, 1623). If the first transmission opportunity exists within the above range (1620), the UE can preferentially multiplex UCI onto the PUSCH transmitted in the first transmission opportunity. If the first transmission opportunity does not exist within the above range, the UE can multiplex UCI onto the PUSCH following the conventional operation. In (c) (1650), the transmission opportunity of n=2 can be assumed to be the first transmission opportunity and the transmission opportunity of n=1 can be assumed to be the second transmission opportunity. Therefore, the UE can select the transmission opportunity of n=2 to perform UCI multiplexing.
[0274] At this time, overlap between PUCCH and PUSCH can occur at the symbol or slot level. For example, overlap between two resources scheduled for PUCCH and PUSCH can occur for an entire slot or only for some slots within a slot. When determining the starting point of the search (for transmission opportunities to multiplex UCI) as in (b)(1640) or the search range as in (c)(1650), the UE can consider repeated PUSCH transmission opportunities that overlap with PUCCH on a symbol-by-symbol basis, and / or consider repeated PUSCH transmission opportunities that overlap with PUCCH on a slot-by-slot basis.
[0275] The description of the above example assumes that the cell where the terminal performs UCI multiplexing is an SBFD cell. When the terminal performs uplink transmission to multiple cells, the terminal can operate simultaneously for the conventional TDD and SBFD cells, and in such a case, the terminal can preferentially select the conventional TDD cell to perform UCI multiplexing.
[0276] FIG. 17 is a diagram illustrating the operation of a terminal in a wireless communication system according to the present disclosure.
[0277] According to FIG. 17, a terminal receives SBFD slot configuration information from a base station using at least one combination of system information, upper layer signaling, MAC CE, or DCI (1710). The SBFD slot configuration information may include at least one of information about the uplink subband described above and information about the time resource for which the uplink subband is configured. Based on the received SBFD slot configuration information, the terminal may perform the SBFD operation as described above. In addition, although not illustrated, the terminal may report terminal capability information related to whether it can support the SBFD operation to the base station. The detailed contents of the terminal capability information may follow the contents described above.
[0278] If the terminal performs the SBFD operation, the terminal determines whether the resources on which the repeated PUSCH transmissions on the uplink (which may include at least one of the repetitions of the DG PUSCH, the repetitions of the CG PUSCH, and the TBoMS) are performed are performed on the same type of time resources (1720). Specifically, the terminal may determine whether each transmission opportunity of the repeated PUSCH transmissions is a first transmission opportunity included in a first time interval or a second transmission opportunity included in a second time interval. This determination may be based on the SBFD configuration information.
[0279] If the terminal does not perform uplink repetitive transmission in the same type of time resource, the terminal determines a bit sequence to be transmitted for each slot based on at least one combination of the embodiments described above (1740). Specifically, the terminal determines a bit sequence of uplink data to be transmitted in a specific slot based on at least one of whether the specific slot corresponds to a first transmission opportunity or a second transmission opportunity, an index of the first first transmission opportunity among a plurality of transmission opportunities, an RV sequence set by a base station, or uplink data scheduling information including an RV index. At this time, the starting point of the RV index and / or bit sequence applied by the terminal to the uplink data may be determined according to an embodiment of the present invention.
[0280] The terminal can transmit a bit sequence determined for each slot to the base station (1750).
[0281] If the terminal does not perform the SBFD operation, or if the repetition of PUSCH transmission is performed in the same type of time resource, the terminal determines the bit sequence to be transmitted for each slot based on the uplink data scheduling information and transmission opportunity according to at least one combination of upper layer signaling, MAC CE, and DCI (via a control channel) instructed by the base station. Specifically, the terminal can determine the bit sequence of uplink data to be transmitted based on at least one of the number of repeated transmissions, the number of slots for transmitting one TB, and / or the configured RV sequence or RV index (1730). In addition to the above operation, the terminal may also multiplex UCI on the uplink data, and the UCI multiplexing may be performed according to the method described above.
[0282] The above flowchart illustrates exemplary methods that can be implemented according to the principles of the present disclosure, and various modifications may be made to the methods depicted in the flowcharts herein. For example, although depicted as a series of steps, various steps in each drawing may overlap, occur in parallel, occur in different orders, or occur multiple times. In other instances, steps may be omitted or replaced with other steps.
[0283] As described above, when a terminal performs SBFD operation and a transmission opportunity occurs in an uplink symbol or slot corresponding to the first transmission opportunity among transmission opportunities for transmitting one TB, the start index of the transmission bit can be set with reference to the various disclosed embodiments, and the number of information bits in the first transmission opportunity can be maximized.
[0284] FIG. 18 is a diagram illustrating the operation of a base station in a wireless communication system according to the present disclosure.
[0285] The base station transmits SBFD slot configuration information to the terminal using at least one combination of system information, upper layer signaling, MAC CE, or DCI (1800). The SBFD slot configuration information may include at least one of information about the uplink subband described above and information about the time resource for which the uplink subband is configured. The base station may perform the SBFD operation as described above based on the uplink (downlink) resources related to the SBFD slot configuration information. In addition, although not illustrated, the base station may receive terminal capability information related to whether the terminal can support the SBFD operation. The detailed contents of the terminal capability information may follow the contents described above.
[0286] If the base station and the terminal perform the SBFD operation, the base station can determine whether the resources on which the repeated PUSCH transmissions on the uplink (which may include at least one of the repetition of the DG PUSCH, the repetition of the CG PUSCH, and the TBoMS) are performed are performed on the same type of time resources (1810). Specifically, the base station can determine whether each transmission opportunity of the repeated PUSCH transmissions is a first transmission opportunity included in a first time interval or a second transmission opportunity included in a second time interval. This determination may be based on the uplink (downlink) resources related to the SBFD configuration information.
[0287] If the base station does not receive an uplink repetitive transmission in the same type of time resource, the base station may predict a bit sequence to be transmitted for each slot based on at least one combination of the embodiments described above (1820). Specifically, the base station may predict a bit sequence of uplink data to be transmitted in a specific slot based on at least one of: whether the specific slot corresponds to a first transmission opportunity or a second transmission opportunity; an index of the first first transmission opportunity among a plurality of transmission opportunities; an RV sequence set by the base station; or an uplink data scheduling configuration including the RV index. In this case, the starting point of the RV index and / or bit sequence applied to the uplink data may be determined according to an embodiment of the present invention.
[0288] Thereafter, the base station can receive a bit sequence corresponding to uplink data for each slot from the terminal (1830). In addition, the uplink data may be multiplexed with UCI, and the UCI multiplexing may be performed according to the method described above.
[0289] If the base station and the terminal do not perform the SBFD operation, or if the base station performs uplink repetitive transmission from the terminal in the same type of time resource, the base station can receive from the terminal a bit sequence corresponding to uplink data generated in a conventional manner in each slot (1840).
[0290] The above description illustrates exemplary methods that can be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated herein. For example, although depicted as a series of steps, various steps in each drawing may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.
[0291] In the above invention, PUSCH repetitive transmission is performed for each slot, and each transmission opportunity is described and illustrated as being located in each slot, but this is for describing an embodiment, and the invention is not limited by this technology.
[0292] FIG. 19 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.
[0293] Referring to FIG. 19, the terminal may include a transceiver, which refers to a terminal receiving unit (1900) and a terminal transmitting unit (1910), a memory (not shown), and a terminal processing unit (1905), or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (1900, 1910), the memory, and the terminal processing unit (1905) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.
[0294] A transceiver unit can transmit and receive signals to and from a base station. The signals may include control information and data. To this end, the transceiver unit may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is merely one embodiment of the transceiver unit, and the components of the transceiver unit are not limited to the RF transmitter and RF receiver.
[0295] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit a signal output from the processor through the wireless channel.
[0296] Memory can store programs and data necessary for the terminal's operation. Furthermore, memory can store control information or data included in signals transmitted and received by the terminal. Memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.
[0297] Additionally, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiments. For example, the processor can receive DCI consisting of two layers and control components of the terminal to simultaneously receive multiple PDSCHs. There may be multiple processors, and the processors can perform component control operations of the terminal by executing programs stored in memory.
[0298] FIG. 20 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.
[0299] Referring to FIG. 20, the base station may include a transceiver, which refers to a base station receiver (2030) and a base station transmitter (2010), a memory (not shown), and a base station processor (2005), or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver (2000, 2010), the memory, and the base station processor (2005) of the base station may operate. 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 the components described above. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.
[0300] The transceiver can transmit and receive signals with the terminal. Here, the signals may include control information and data. To this end, the transceiver may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.
[0301] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit the signal output from the processor through the wireless channel.
[0302] The memory can store programs and data necessary for the operation of the base station. Furthermore, the memory can store control information or data included in signals transmitted and received by the base station. The memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.
[0303] The processor can control a series of processes to enable the base station to operate according to the aforementioned embodiments of the present disclosure. For example, the processor can configure two layers of DCIs containing allocation information for multiple PDSCHs and control each component of the base station to transmit them. There may be multiple processors, and the processors can perform component control operations of the base station by executing programs stored in memory.
[0304] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0305] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.
[0306] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.
[0307] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.
[0308] In the specific embodiments of the present disclosure described above, components included in the invention are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.
[0309] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples to easily explain the technical contents of the present disclosure and to help the understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of the present disclosure are possible. In addition, each of the above embodiments can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment can be combined with each other to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above embodiments have been presented based on an FDD LTE system, other modifications based on the technical idea of the above embodiments can be implemented with other systems such as a TDD LTE system, 5G, or NR system.
[0310] Meanwhile, the order of description in the drawings explaining the method of the present invention does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel.
[0311] Alternatively, the drawings illustrating the method of the present invention may omit some components and include only some components within a scope that does not harm the essence of the present invention.
[0312] In addition, the method of the present invention may be implemented by combining some or all of the contents included in each embodiment within a scope that does not harm the essence of the invention.
[0313] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only, and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will appreciate that the present disclosure can be readily modified into other specific forms without altering the technical spirit or essential characteristics of the present disclosure. The scope of the present disclosure is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included within the scope of the present disclosure.
Claims
1. In a method performed by a terminal of a communication system, A step of receiving SBFD (subband non-overlapping full duplex) configuration information from a base station, wherein the SBFD configuration information includes time resource information including SBFD resources; A step of receiving PUSCH (physical uplink shared channel) transmission configuration information from the base station, wherein the configuration information includes resource and redundancy version (RV) sequence information corresponding to a plurality of PUSCH transmission opportunities; A step of checking whether the resource corresponding to the plurality of PUSCH transmission opportunities corresponds to the first transmission opportunity or the second transmission opportunity based on the PUSCH transmission configuration information; and A method characterized by comprising a step of transmitting uplink data on a PUSCH by applying an RV index 0 to a PUSCH transmission opportunity corresponding to the first transmission opportunity based on an RV sequence indicated by an offset and the RV sequence information.
2. In paragraph 1, A method characterized in that the first transmission opportunity corresponds to a PUSCH transmission opportunity on an uplink symbol, and the second transmission opportunity corresponds to a PUSCH transmission opportunity on a symbol including SBFD resources.
3. In paragraph 1, A method characterized in that the above offset is identified based on the position of 0 among the RV sequences indicated by the RV sequence information and the number of the PUSCH transmission opportunity corresponding to the first transmission opportunity.
4. In paragraph 2, A method characterized in that an offset for a PUSCH transmission opportunity corresponding to the first transmission opportunity and an offset for a PUSCH transmission opportunity corresponding to the second transmission opportunity are calculated separately.
5. In a method performed by a base station of a communication system, A step of transmitting SBFD (subband non-overlapping full duplex) configuration information to a terminal, wherein the SBFD configuration information includes time resource information including SBFD resources; A step of transmitting PUSCH (physical uplink shared channel) transmission configuration information to the terminal, wherein the configuration information includes resource and redundancy version (RV) sequence information corresponding to a plurality of PUSCH transmission opportunities; Including a step of receiving uplink data with RV index 0 applied on a PUSCH in a PUSCH transmission opportunity corresponding to a first transmission opportunity, A method characterized in that the RV index 0 of the above uplink data is related to an RV sequence indicated by the offset and the RV sequence information.
6. In paragraph 5, A method characterized in that the first transmission opportunity corresponds to a PUSCH transmission opportunity on an uplink symbol, and the second transmission opportunity corresponds to a PUSCH transmission opportunity on a symbol including SBFD resources.
7. In paragraph 5, A method characterized in that the above offset is based on a position of 0 among the RV sequences indicated by the RV sequence information and the number of the PUSCH transmission opportunity corresponding to the first transmission opportunity.
8. In paragraph 6, A method characterized in that an offset for a PUSCH transmission opportunity corresponding to the first transmission opportunity and an offset for a PUSCH transmission opportunity corresponding to the second transmission opportunity are separately identified.
9. At the terminal of the communication system, Transmitter and receiver; and Receive SBFD (subband non-overlapping full duplex) configuration information from a base station, wherein the SBFD configuration information includes time resource information including SBFD resources, Receive PUSCH (physical uplink shared channel) transmission configuration information from the base station, wherein the configuration information includes resource and redundancy version (RV) sequence information corresponding to multiple PUSCH transmission opportunities, Based on the above PUSCH transmission configuration information, it is checked whether the resource corresponding to the plurality of PUSCH transmission opportunities corresponds to the first transmission opportunity or the second transmission opportunity, and A terminal characterized by including a control unit configured to transmit uplink data on a PUSCH by applying RV index 0 to a PUSCH transmission opportunity corresponding to the first transmission opportunity based on an RV sequence indicated by an offset and the RV sequence information.
10. In paragraph 9, A terminal, characterized in that the first transmission opportunity corresponds to a PUSCH transmission opportunity on an uplink symbol, and the second transmission opportunity corresponds to a PUSCH transmission opportunity on a symbol including SBFD resources.
11. In paragraph 9, A terminal characterized in that the above offset is identified based on the position of 0 among the RV sequences indicated by the RV sequence information and the number of the PUSCH transmission opportunity corresponding to the first transmission opportunity.
12. In paragraph 10, A terminal characterized in that an offset for a PUSCH transmission opportunity corresponding to the first transmission opportunity and an offset for a PUSCH transmission opportunity corresponding to the second transmission opportunity are calculated separately.
13. In the base station of the communication system, Transmitter and receiver; Transmit SBFD (subband non-overlapping full duplex) configuration information to the terminal, wherein the SBFD configuration information includes time resource information including SBFD resources, Transmitting PUSCH (physical uplink shared channel) transmission configuration information to the terminal, wherein the configuration information includes resource and redundancy version (RV) sequence information corresponding to multiple PUSCH transmission opportunities, and Including a control unit configured to receive uplink data with RV index 0 applied on a PUSCH in a PUSCH transmission opportunity corresponding to the first transmission opportunity, A base station, characterized in that the RV index 0 of the above uplink data is related to an RV sequence indicated by the offset and the RV sequence information.
14. In paragraph 13, A base station, characterized in that the first transmission opportunity corresponds to a PUSCH transmission opportunity on an uplink symbol, and the second transmission opportunity corresponds to a PUSCH transmission opportunity on a symbol including SBFD resources.
15. In paragraph 13, A base station, characterized in that the above offset is based on the position of 0 among the RV sequences indicated by the RV sequence information and the number of the PUSCH transmission opportunity corresponding to the first transmission opportunity.
Citation Information
Patent Citations
Quality quantification method and system based on user response data of youtube video
KR1020240153008A
Uplink configured grant configuration determination for a user equipment device
WO2022036369A1
Sidelink resource pool configuration
WO2022221857A1
Sidelink resource scheduling
WO2022221859A1
Configuration information sending method and apparatus, and redundancy version RV value determining method and apparatus
WO2022236604A1
