Method and apparatus for uplink transmission and reception in a wireless communication system

By identifying and configuring the uplink bandwidth portion (BWP) of multicast and broadcast services in 5G communication systems, the resources of the Physical Uplink Control Channel (PUCCH) are determined, solving the resource configuration problem of base stations sending feedback to multiple user equipments and improving data transmission performance.

CN116671200BActive Publication Date: 2026-11-17SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202180088760.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-12-31
Filing Date
2021-12-23
Publication Date
2026-11-17
Estimated Expiration
2041-12-23

AI Technical Summary

Technical Problem

In 5G communication systems, when base stations send multicast, multicast, and broadcast services to multiple user devices, it is necessary to effectively configure the frequency and time resources of uplink feedback in order to improve data transmission performance. However, existing technologies have not been able to effectively solve this problem.

Method used

A method and apparatus are provided to determine the resources of the Physical Uplink Control Channel (PUCCH) by identifying uplink bandwidth portions (BWP) associated with multicast and broadcast services, and to send feedback to a base station through these resources, including configuring the feedback resources based on offsets of downlink control information (DCI) and higher-layer signaling.

Benefits of technology

It improved data transmission performance, ensured effective feedback transmission, and met the needs of multicast, broadcast, and other services in 5G communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116671200B_ABST
    Figure CN116671200B_ABST
Patent Text Reader

Abstract

A method for operating a terminal in a wireless communication system is provided. The method includes: identifying an uplink bandwidth portion (BWP) associated with a multicast and broadcast service (MBS) configured for the terminal; determining resources for transmitting a physical uplink control channel (PUCCH) in the uplink BWP associated with the MBS; and transmitting the PUCCH to a base station using the determined resources.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to a wireless communication system. More specifically, this disclosure relates to a method and apparatus for sending and receiving feedback in data communications targeting multicast, broadcast, or physical layer. Background Technology

[0002] To meet the growing demand for wireless data services following the commercialization of fourth-generation (4G) communication systems, efforts are underway to develop fifth-generation (5G) or pre-5G communication systems. For this purpose, 5G or pre-5G communication systems are referred to as 'super-4G network' communication systems or 'post-Long Term Evolution (post-LTE)' systems. To achieve high data rates, implementing 5G communication systems in ultra-high frequency millimeter-wave (mmWave) bands (e.g., the 60 GHz band) is being considered. To reduce path loss of radio waves and increase transmission distance in the ultra-high frequency bands used for 5G communication systems, various technologies are being researched, such as beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO. To improve system networks used in 5G communication systems, various technologies have been developed, such as evolved small cells, advanced small cells, cloud radio access networks (Cloud-RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and interference cancellation. Furthermore, for 5G communication systems, advanced coding and modulation (ACM) technologies such as hybrid frequency shift keying (FSK) and orthogonal amplitude modulation (QAM) (FQAM) and sliding window superposition coding (SWSC) have been developed, as well as advanced access technologies such as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA).

[0003] The Internet has evolved from a human-based network of connections where humans create and consume information to the Internet of Things (IoT), in which distributed elements, such as objects, exchange information with each other to process it. The Internet of Everything (IoE) technology has emerged, in which IoT technology is combined with technologies for processing big data, for example, by connecting to cloud servers. To realize IoT, various technological elements are required, such as sensing technologies, wired / wireless communication and network infrastructure, service interface technologies, and security technologies. Therefore, in recent years, technologies related to sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) for connecting objects have been researched. In the IoT environment, intelligent Internet technology (IT) services can be provided to collect and analyze data obtained from connected objects to create new value in human life. With the convergence and integration of existing information technology (IT) and various industries, IoT can be applied to a wide range of fields, such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Various attempts are underway to apply 5G communication systems to IoT networks. For example, technologies related to sensor networks, M2M communication, and MTC are being implemented using 5G communication technologies such as beamforming, MIMO, and array antennas. The application of Cloud-RAN as a big data processing technology is another example of the convergence of 5G communication and IoT technologies.

[0005] Furthermore, low-density parity-check (LDPC) codes can be used to efficiently transmit data in new radio (NR) systems. Additionally, there are two methods for transmitting parity bits generated by LDPC coding: the fully buffered rate-matching (FBRM) method can include transmitting all parity bits generated by LDPC coding, and the finite-buffered rate-matching (LBRM) method can involve limiting the number of parity bits that can be transmitted.

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

[0007] A base station (BS) can provide multicast, multicast, and broadcast services by sending the same data to multiple user equipments (UEs). Sending feedback from the UE to the BS can help improve data transmission performance; the feedback is about multicast / multicast data received by the UE. To enable the UE to send feedback to the BS, configuration of frequency and timing resources for uplink (UL) feedback transmission may be required, and configuration of the UL bandwidth portion (BWP) for feedback transmission may also be required. Aspects of this disclosure at least address the aforementioned problems and / or disadvantages and provide at least the advantages described below. Therefore, an aspect of this disclosure is to provide a method and apparatus for configuring resources and BWP for sending feedback about downlink (DL) data (Physical Downlink Shared Channel (PDSCH)) for multicast / multicast / broadcast transmission. Attached Figure Description

[0008] The above and other aspects, features, and advantages of certain embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, wherein:

[0009] Figure 1 This is a diagram illustrating the basic time-frequency domain structure of a radio resource domain in a novel radio (NR) system according to an embodiment of the present disclosure, in which data or control channels are transmitted in the downlink (DL) or uplink (UL).

[0010] Figure 2 This is a diagram illustrating an example of a control resource set (CORESET) transmitted in a fifth-generation (5G) communication system according to an embodiment of the present disclosure;

[0011] Figure 3 The distribution of data for enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC) according to embodiments of the present disclosure is shown throughout the system frequency band.

[0012] Figure 4 This is a diagram illustrating an example of how a system frequency band is divided and allocated with eMBB, URLLC, and mMTC data according to an embodiment of the present disclosure;

[0013] Figure 5 An example is shown of the process of dividing a transport block (TB) into multiple code blocks and adding cyclic redundancy check (CRC) to it according to an embodiment of the present disclosure;

[0014] Figure 6 This is a diagram illustrating how the synchronization signal (SS) and physical broadcast channel (PBCH) in an NR system according to an embodiment of the present disclosure are mapped to the frequency and time domains;

[0015] Figure 7This is a diagram illustrating symbols that can be transmitted on an SS / PBCH block according to an embodiment of the present disclosure, depending on the subcarrier spacing;

[0016] Figure 8 This is a diagram illustrating the user equipment (UE) processing time according to a timed advance in a 5G or NR system when a UE receives a first signal and sends a second signal in response to the first signal, according to an embodiment of the present disclosure;

[0017] Figure 9 This is a diagram illustrating an example of a base station (BS) in a 5G system scheduling multiple data packets according to a time slot and transmitting the data, receiving Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback on the data, and performing a retransmission in response to the feedback, according to an embodiment of the present disclosure.

[0018] Figure 10 This is a diagram illustrating an example of multicasting where the same control information and data are sent from a BS to multiple UEs according to embodiments of this disclosure;

[0019] Figure 11 This is a diagram illustrating an example of a bandwidth portion (BWP) configured in the UL and DL according to an embodiment of the present disclosure;

[0020] Figure 12 This is a diagram illustrating examples of a UL BWP configured for UE1, a UL BWP configured for UE2, and a UL BWP typically configured for both UEs for multicast and broadcast services (MBS) according to embodiments of this disclosure;

[0021] Figure 13 This is a diagram illustrating an example of the location of the Physical Uplink Control Channel (PUCCH) resource in a BWP configured for MBS according to an embodiment of this disclosure;

[0022] Figure 14 This is a diagram illustrating the internal structure of a UE according to an embodiment of the present disclosure; and

[0023] Figure 15 This is a diagram illustrating the internal structure of a BS according to an embodiment of the present disclosure.

[0024] Throughout the accompanying drawings, the same reference numerals will be understood to refer to the same parts, components, and structures. Detailed Implementation

[0025] A base station (BS) can provide multicast, multicast, and broadcast services by sending the same data to multiple user equipments (UEs). Sending feedback from the UE to the BS can help improve data transmission performance; the feedback is about multicast / multicast data received by the UE. To enable the UE to send feedback to the BS, configuration of frequency and timing resources for uplink (UL) feedback transmission may be required, as well as configuration of the UL bandwidth portion (BWP) for feedback transmission may be needed. Aspects of this disclosure at least address the aforementioned problems and / or disadvantages and provide at least the advantages described below. Therefore, an aspect of this disclosure is to provide a method and apparatus for configuring resources and BWP for sending feedback about downlink (DL) data (Physical Downlink Shared Channel (PDSCH)) used for multicast / multicast / broadcast.

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

[0027] According to an aspect of this disclosure, a method for operating a terminal in a wireless communication system is provided. The method includes: identifying an uplink bandwidth portion (BWP) associated with a multicast and broadcast service (MBS) configured for the terminal; determining resources for transmitting a physical uplink control channel (PUCCH) in the uplink BWP associated with the MBS; and transmitting the PUCCH to a base station using the determined resources.

[0028] According to another aspect of this disclosure, a terminal for a wireless communication system is provided. The terminal includes a transceiver and at least one processor, the at least one processor being configured to: identify an uplink bandwidth portion (BWP) associated with a multicast and broadcast service (MBS) configured for the terminal; determine resources for transmitting a physical uplink control channel (PUCCH) in the uplink BWP associated with the MBS; and transmit the PUCCH to a base station via the transceiver using the determined resources.

[0029] According to another aspect of this disclosure, a method for operating a terminal in a wireless communication system is provided. The method includes: identifying an uplink bandwidth portion (BWP) associated with a multicast and broadcast service (MBS) configured for the terminal; determining resources for transmitting a physical uplink control channel (PUCCH) in the uplink BWP associated with the MBS; and transmitting the PUCCH to a base station using the determined resources.

[0030] The method may further include receiving an indication of whether the uplink BWP associated with the MBS is an indicator configured for the terminal.

[0031] Determining the resources used for sending PUCCH may include determining the resources used for sending PUCCH based on the bit field values ​​of the downlink control information (DCI).

[0032] PUCCH can include Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) information for downlink data to be sent to multiple terminals, and the bit field value of DCI can indicate whether the HARQ-ACK information includes only NACK, or includes ACK or NACK.

[0033] The PUCCH may include HARQ-ACK information for downlink data to be jointly transmitted to multiple terminals, and determining the resources for transmitting the PUCCH may include determining the resources for transmitting the PUCCH based on at least one of the frame number or slot index in which the HARQ-ACK information will be transmitted.

[0034] The PUCCH may include HARQ-ACK information for downlink data to be sent to multiple terminals, and determining the resources for sending the PUCCH may include determining the resources for sending the PUCCH based on at least one of the frame number or time slot index in which the downlink data is sent.

[0035] Determining the resources used for sending PUCCH may include determining the resources used for sending PUCCH based on at least one of the terminal's initial uplink BWP, the terminal's currently active uplink BWP, or the uplink BWP associated with the MBS configured for the terminal.

[0036] Determining the resources used to send PUCCH may include determining the resources used to send PUCCH based on an offset indicated by higher-layer signaling.

[0037] Determining the resources used to send PUCCH may include: determining the resources used to send PUCCH based on an offset indicated by DCI, which is typically sent to multiple terminals including the terminal.

[0038] Determining the resources used to send PUCCH may include: determining the resources used to send PUCCH based on the group membership index configured for the terminal.

[0039] According to another aspect of this disclosure, a terminal for a wireless communication system is provided. The terminal includes a transceiver and at least one processor, the at least one processor being configured to: identify an uplink bandwidth portion (BWP) associated with a multicast and broadcast service (MBS) configured for the terminal; determine resources for transmitting a physical uplink control channel (PUCCH) in the uplink BWP associated with the MBS; and transmit the PUCCH to a base station via the transceiver using the determined resources.

[0040] At least one processor may be further configured to receive via a transceiver an indicator of whether the uplink BWP associated with the MBS is configured for the terminal.

[0041] At least one processor can be further configured to determine the resources used for transmitting PUCCH based on the bit field value of downlink control information (DCI).

[0042] PUCCH can include Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) information for downlink data to be sent to multiple terminals, and the bit field value of DCI can indicate whether the HARQ-ACK information includes only NACK, or includes ACK or NACK.

[0043] The PUCCH may include HARQ-ACK information for downlink data to be sent to multiple terminals, and at least one processor may be configured to determine the resources for sending the PUCCH based on at least one of the frame number or slot index in which the HARQ-ACK information will be sent.

[0044] The PUCCH may include HARQ-ACK information for downlink data to be sent to multiple terminals, and at least one processor may be configured to determine the resources for sending the PUCCH based on at least one of the frame number or slot index in which the downlink data is sent.

[0045] At least one processor can be configured to determine the resources for sending PUCCH based on at least one of the terminal's initial uplink BWP, the terminal's currently active uplink BWP, or the uplink BWP associated with an MBS configured for the terminal.

[0046] At least one processor can be configured to determine the resources used to send PUCCH based on an offset indicated by higher-level signaling.

[0047] At least one processor can be configured to determine the resources for sending PUCCH based on an offset indicated by DCI, which is typically sent to multiple terminals including the terminal.

[0048] At least one processor can be configured to determine the resources used to send PUCCH based on the group membership index configured for the terminal.

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

[0050] The mode of the present invention

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

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

[0053] It should be understood that, unless the context explicitly states otherwise, the singular forms “a / an” and “the” include plural references. Therefore, for example, a reference to “component surface” includes a reference to one or more such surfaces.

[0054] Throughout the disclosure, the expression “at least one of a, b, or c” indicates only a, only b, only c, both a and b, both a and c, both b and c, all a, b, and c, or variations thereof.

[0055] Examples of terminals may include user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, multimedia system capable of performing communication functions, etc.

[0056] In this disclosure, the controller may also be referred to as a processor.

[0057] Throughout the specification, a layer (or layer device) may also be referred to as an entity.

[0058] As a new fifth-generation (5G) communication technology, the new radio (NR) access technology is designed to allow the free multiplexing of various services in time and frequency resources, enabling reference signals, waveform / digital parameter sets, etc., to be dynamically or freely allocated according to the requirements of the corresponding service. In wireless communication, optimized data transmission through measuring channel quality and interference is crucial for providing the best service to user equipment (UE). Therefore, accurate measurement of channel state is required. However, unlike fourth-generation (4G) communication, where channel and interference characteristics do not change drastically according to frequency resources, in the case of 5G channels, channel and interference characteristics change significantly according to service, necessitating support for a subset of frequency resource groups (FRGs) to separately measure channel and interference characteristics. The types of services supported in NR systems can be categorized into categories including enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), ultra-reliable low-latency communication (URLLC) services, etc. eMBB can be a service for high-speed transmission of large amounts of data, mMTC can be a service for minimum power consumption and access for multiple UEs, and URLLC can be a service for high reliability and low latency. Different requirements can be applied depending on the type of service to be applied to the UE.

[0059] Thus, multiple services can be provided to a user in a communication service, and in order to provide multiple services to a user, a method and apparatus for providing services according to their respective characteristics within the same duration are required.

[0060] In this document, embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings.

[0061] In the following description of embodiments, descriptions of techniques well-known in the art and not directly related to this disclosure have been omitted. This is to clearly convey the essential points of this disclosure by omitting unnecessary explanations.

[0062] For the same reason, some components in the accompanying drawings are exaggerated, omitted, or shown schematically. Furthermore, the size of each component does not perfectly reflect its actual size. In the accompanying drawings, identical or corresponding components are indicated by the same reference numerals.

[0063] The advantages and features of this disclosure, as well as methods for achieving these advantages and features, can be more readily understood by referring to the following detailed description of embodiments and accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concepts of this disclosure to those skilled in the art, and this disclosure will be defined only by the appended claims. Throughout the specification, the same reference numerals denote the same components.

[0064] It should be understood that each block shown in the flowchart, and combinations of blocks shown in the flowchart, can be implemented by computer program instructions. Computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, such that instructions executed by the processor of the computer or other programmable data processing apparatus generate an entity for performing the function specified in the flowchart block. Computer program instructions can also be stored in a computer-executable or computer-readable storage medium that can direct the computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-executable or computer-readable storage medium can produce an article of manufacture including an instruction entity that performs the function specified in the flowchart block. Computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be executed on the computer or other programmable apparatus to produce a computer-implemented process, such that instructions executed on the computer or other programmable apparatus provide operations for implementing the function specified in the flowchart block.

[0065] Furthermore, each block shown in the flowchart can represent a module, segment, or section of code, which includes one or more executable instructions for performing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may appear out of order. For example, in fact, depending on the functionality involved, two blocks shown consecutively may be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order.

[0066] As used in this embodiment, the term "~unit" refers to a software or hardware component that performs certain tasks, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC). However, the term "~unit" is not intended to be limited to software or hardware. A "~unit" may be configured to reside in addressable storage media or may be configured to operate one or more processors. Thus, for example, a "~unit" may include components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided in components and "~units" may be combined into fewer components and "~units," or may be further separated into additional components and "~units." Furthermore, components and "~units" may be implemented to operate one or more central processing units (CPUs) in a device or secure multimedia card. Additionally, in embodiments, a "~unit" may include one or more processors.

[0067] Wireless communication systems have evolved from early voice-centric services to broadband systems offering high-speed, high-quality packet data services, such as High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE or Evolved Universal Terrestrial Radio Access (E-UTRA)), LTE-Advanced (LTE-A) of the 3GPP, High-Speed ​​Packet Data (HRPD) and Ultra Mobile Broadband (UMB) of 3GPP2, and the IEEE 802.16e standard. Furthermore, 5G or NR communication standards are being defined as 5G wireless communication systems.

[0068] As a representative example of a broadband wireless communication system, the NR system employs Orthogonal Frequency Division Multiplexing (OFDM) schemes in both the downlink (DL) and uplink (UL). More specifically, it uses Cyclic Prefix OFDM (CP-OFDM) in the DL and both CP-OFDM and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the UL. UL refers to the radio link through which the UE (or MS) transmits data or control signals to the base station (BS) (or next-generation node B (gNode B, gNB)), and DL refers to the radio link through which the BS transmits data or control signals to the UE. These multiple access schemes identify the data or control information of different users by allocating and managing time-frequency resources used to carry user data or control information in a way that does not overlap with each other (i.e., achieving orthogonality between them).

[0069] The NR system employs a Hybrid Automatic Repeat Request (HARQ) scheme, which retransmits data at the physical layer when decoding fails during the initial transmission. The HARQ scheme instructs the receiver to send a decoding failure indication message (e.g., a negative acknowledgment (NACK)) to the transmitter when it fails to decode data correctly, allowing the transmitter to retransmit the data at its physical layer. The receiver can then combine the retransmitted data with the previously decoded but failed data, thereby improving data reception performance. Furthermore, when the receiver correctly decodes the data, the transmitter sends a decoding success indication message (e.g., an acknowledgment (ACK)) to allow the transmitter to send new data.

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

[0071] refer to Figure 1 The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The smallest transmission unit in the time domain is an OFDM symbol, and N symbOFDM symbols 102 are aggregated to form a time slot 106. The subframe length is defined as 1.0 ms, and radio frame 114 is defined as 10 ms. The smallest transmission unit in the frequency domain is a subcarrier, and the bandwidth of the entire system transmission bandwidth is composed of a total of N. BW Each subcarrier consists of 104 elements. One frame can be defined as 10 ms. One subframe can be defined as 1 ms, and therefore, one frame can consist of a total of 10 subframes. One time slot can consist of 14 OFDM symbols (i.e., the number of symbols per time slot). =14). A subframe can consist of one or more time slots, and the number of time slots in each subframe can vary depending on the configuration value μ of the subcarrier spacing. Figure 2 Let's illustrate the cases where the subcarrier spacing configuration value μ = 0 and μ = 1. When μ = 0, one subframe can consist of one time slot, and when μ = 1, one subframe can consist of two time slots. In other words, the number of time slots per subframe depends on the subcarrier spacing configuration value μ. The number of time slots per frame can vary, and therefore the number of time slots per frame. It can be changed. Based on the configuration value μ for each subcarrier spacing. and It can be defined in Table 1 below.

[0072] [Table 1]

[0073]

[0074] Prior to a Radio Resource Control (RRC) connection, the UE can receive configuration information regarding the Initial Bandwidth Part (BWP) for initial connection from the BS via the Master Information Block (MIB). More specifically, to receive system information for initial access via the MIB during the initial access phase (which may correspond to the Remaining System Information (RMSI) or System Information Block 1 (SIB1)), the UE can receive configuration information regarding the Control Resource Set (CORESET) and search space in which the Physical Downlink Control Channel (PDCCH) can be transmitted. The CORESET and search space configured by the MIB can each be considered as ID 0. The BS can notify the UE of configuration information regarding CORESET#0 via the MIB, such as frequency allocation information, time allocation information, parameter sets, etc. Furthermore, the BS can notify the UE of the listening period and timing configuration information for CORESET#0 via the MIB, i.e., configuration information regarding search space#0. The UE can consider the frequency domain configured as CORESET#0 and obtained from the MIB as the initial BWP for initial access. Here, the identifier (ID) of the initial BWP can be considered as 0.

[0075] The MIB can include the following information. However, the MIB is not limited to this.

[0076] [Table 2]

[0077]

[0078] [Table 3]

[0079]

[0080]

[0081] In the method of configuring the BWP, the UE can receive configuration information about the initial BWP via the MIB during the initial access phase before RRC connection. More specifically, the UE can configure a CORESET for the DL control channel from the MIB of the Physical Broadcast Channel (PBCH), through which downlink control information (DCI) for scheduling System Information Blocks (SIBs) can be transmitted. Here, the bandwidth of the CORESET configured by the MIB can be regarded as the initial BWP, and the UE can receive the Physical Downlink Shared Channel (PDSCH) through which the SIBs are transmitted via the configured initial BWP. The initial BWP can be used for other System Information (OSI), paging and random access, and for receiving SIBs.

[0082] When one or more BWPs are configured for a UE, the BS can indicate BWP handover by using the BWP indicator in the DCI.

[0083] The basic unit of a resource in the time-frequency domain is a resource element (RE) 112, which can be indicated by OFDM symbols and subcarrier indices. A resource block (RB) 108 (also known as a physical resource block (PRB)) is formed by N in the frequency domain. RB The system is defined by 110 consecutive subcarriers. Typically, the smallest unit of data transmission is the RB unit. In NR systems, typically N... symb =14 and N RB =12, and N BW The data rate is proportional to the bandwidth of the system's transmission band. The data rate can be increased proportionally to the number of RBs scheduled for the UE.

[0084] In NR systems, Frequency Division Duplex (FDD) systems, which identify DL and UL by frequency, can differ in DL and UL transmission bandwidths. Channel bandwidth indicates the radio frequency (RF) bandwidth corresponding to the system transmission bandwidth. Each indication in Tables 4 and 5 shows some correspondence between system transmission bandwidth, subcarrier spacing, and channel bandwidth defined for frequency bands below and above 6 GHz in NR systems. For example, the transmission bandwidth of an NR system with a 100 MHz channel bandwidth and a 30 kHz subcarrier spacing consists of 273 RBs. The N / A below can be a combination of bandwidth subcarriers not supported in the NR system. Table 4 below indicates the configuration for Frequency Range 1 (FR1), and Table 5 indicates the configuration for FR2.

[0085] [Table 4]

[0086]

[0087] [Table 5]

[0088]

[0089] In an NR system, the frequency range can be defined by dividing it into FR1 and FR2, as shown in Table 6 below.

[0090] [Table 6]

[0091] Frequency range name Corresponding frequency range FR1 450MHz-7125MHz FR2 24250MHz-52600MHz

[0092] The ranges of FR1 and FR2 can be varied and applied differently. For example, the frequency range of FR1 can be varied from 450MHz to 6000MHz.

[0093] Next, the synchronization signal (SS) / PBCH block of the 5G communication system will be described.

[0094] The SS / PBCH block can indicate a physical layer channel block consisting of a primary SS (PSS), secondary SS (SSS), and PBCH. More specifically, the SS / PBCH block can be defined as follows.

[0095] -PSS: The signal used as a reference for DL ​​time / frequency synchronization can provide some information about the cell ID.

[0096] -SSS: The signal used as a reference for DL ​​time / frequency synchronization can provide additional cell ID information not provided by PSS. Furthermore, SSS can be used as a reference signal for demodulation in PBCH.

[0097] -PBCH: It can provide basic system information requested by the UE for transmitting or receiving data and control channels. Basic system information may include search space-related control information indicating radio resource mapping information for control channels, scheduling control information for individual data channels regarding system transmission, etc.

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

[0099] The UE can detect the PSS and SSS during the initial access phase and can decode the PBCH. The UE can obtain the MIB from the PBCH and can be configured with CORESET#0 (which may correspond to a control area with control area index 0). The UE can assume that the selected SS / PBCH block and the demodulation reference signal (DMRS) transmitted in CORESET#0 are quasi-co-located (QCL) and can perform listening on CORESET#0. The UE can receive system information based on the DL control information transmitted in CORESET#0. The UE can obtain configuration information related to the random access channel (RACH) required for initial access from the received system information. Considering the selected SS / PBCH index, the UE can send a physical RACH (PRACH) to the BS, and upon receiving the PRACH, the BS can obtain information about the index of the SS / PBCH block selected by the UE. Through this process, the BS can identify which SS / PBCH block the UE selects from the SS / PBCH blocks, and the UE listens on CORESET#0 associated with the selected SS / PBCH block.

[0100] Next, we will describe the DCI of the 5G system in detail.

[0101] Scheduling information for UL data (or physical UL data channel (Physical Uplink Shared Channel (PUSCH)) or DL ​​data (or physical DL data channel (Physical Downlink Shared Channel (PDSCH))) in a 5G system can be sent from the BS to the UE. The UE can listen for DCI formats for backoff and for non-backoff regarding the PUSCH or PDSCH. The DCI format for backoff can be configured with predefined fixed fields between the BS and the UE, and the DCI format for non-backoff can include configurable fields. In addition, the DCI can include various formats, and depending on the format, the DCI can indicate whether it is a DCI for power control, a DCI for notifying slot format indicators (SFI), etc.

[0102] DCI messages can be channel-coded and modulated, and then transmitted via the PDCCH, which serves as the physical DL control channel. Cyclic Redundancy Check (CRC) can be added to the payload of the DCI message, and can be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the UE's identity. Different RNTIs can be used depending on the purpose of the DCI message, such as the transmission of UE-specific data, power control commands, random access responses, etc. That is, the RNTI may not be explicitly transmitted, but can be included in the CRC calculation process and transmitted. When a DCI message transmitted on the PDCCH is received, the UE can check the CRC using the assigned RNTI, and as a result of the check, if the CRC is correct, the UE can identify the corresponding message to be sent. The PDCCH can be mapped and transmitted in the CORESET configured for the UE.

[0103] For example, the DCI used for scheduling PDSCH regarding System Information (SI) can be scrambled by SI-RNTI. The DCI used for scheduling PDSCH regarding Random Access Response (RAR) can be scrambled by RA-RNTI. The DCI used for scheduling PDSCH regarding paging messages can be scrambled by P-RNTI. The DCI used for notifying Slot Format Indicator (SFI) can be scrambled by SFI-RNTI. The DCI used for notifying Transmission Power Control (TPC) can be scrambled by TPC-RNTI. The DCI used for scheduling UE-specific PDSCH or PUSCH can be scrambled by Cell RNTI (C-RNTI). The fact that the RNTI value is scrambled into the DCI likely means that the RNTI value is added to the CRC bits of the DCI using an XOR operation (0+0=0, 1+0=1, 1+1=0). The XOR operation can be a modulo-2 operation. When the number of bits in the DCI's CRC differs from the number of bits in the RNTI, the operation can be performed using either the least significant bit (LSB) or the most significant bit (MSB) with the longer bit count. For example, if the DCI's CRC is 24 bits and the RNTI is 16 bits, the RNTI can be scrambled to the 16 bits of the CRC's LSB.

[0104] DCI format 0_0 can be used as a backoff DCI for scheduling PUSCH, and in this respect, its CRC can be scrambled by C-RNTI. The DCI format 0_0 with CRC scrambled by C-RNTI can include several pieces of information. However, this disclosure is not limited thereto.

[0105] -DCI format identifier——[1] bits

[0106] -Frequency domain resource assignment-- Bit

[0107] -Time Domain Resource Assignment - Xbit

[0108] -Frequency hopping flag - 1 bit

[0109] -Modulation and coding scheme -5 bits

[0110] -New data indicator -1 bit

[0111] -Redundant version - 2 bits

[0112] -HARQ process ID - 4 bits

[0113] - Transmission Power Control (TPC) command for PUSCH scheduling - 2 bits

[0114] -UL / Supplemental UL (SUL) indicator - 0 or 1 bit

[0115] DCI format 0_1 ​​can be used as a non-back-off DCI for scheduling PUSCH, and in this respect, its CRC can be scrambled by C-RNTI. The DCI format 0_1 ​​with CRC scrambled by C-RNTI can include several pieces of information. However, this disclosure is not limited thereto.

[0116] - Carrier indicator — 0 or 3 bits

[0117] -UL / SUL indicator - 0 or 1 bit

[0118] -DCI format identifier——[1] bits

[0119] -BWP indicator - 0, 1, or 2 bits

[0120] -Frequency domain resource allocation

[0121] For resource allocation type 0, Bit

[0122] For resource allocation type 1, Bit

[0123] -Time-domain resource allocation - 1, 2, 3, or 4 bits

[0124] - Virtual Resource Block (VRB) to Physical Resource Block (PRB) mapping - 0 or 1 bit, used only for resource allocation type 1.

[0125] • If only resource allocation type 0 is configured, then it is 0 bits;

[0126] Otherwise, it is 1 bit.

[0127] - Frequency hopping flag - 0 or 1 bit, used only for resource allocation type 1.

[0128] • If only resource allocation type 0 is configured, then it is 0 bits;

[0129] Otherwise, it is 1 bit.

[0130] -Modulation and coding scheme -5 bits

[0131] -New data indicator -1 bit

[0132] -Redundant version - 2 bits

[0133] -HARQ process ID - 4 bits

[0134] - First downlink assignment index - 1 or 2 bits

[0135] • For semi-static HARQ-ACK codebooks, it is 1 bit;

[0136] • For dynamic HARQ-ACK codebooks with a single HARQ-ACK codebook, it is 2 bits.

[0137] - Second downlink assignment index - 0 or 2 bits

[0138] • For dynamic HARQ-ACK codebooks with two HARQ-ACK subcodebooks, the value is 2 bits;

[0139] Otherwise, it is 0 bits.

[0140] - TPC command for PUSCH used for scheduling - 2 bits

[0141] -SRS resource indicator or Bit

[0142] • For non-codebook-based PUSCH transmission, Bit;

[0143] • For codebook-based PUSCH transmission, Bit.

[0144] -Precoding information and number of layers-Up to 6 bits

[0145] - Antenna port - Maximum 5 bits

[0146] - Detect Reference Signal (SRS) Request - 2 bits

[0147] - Channel State Information (CSI) Request - 0, 1, 2, 3, 4, 5, or 6 bits

[0148] - Code Block Group (CBG) transmission information - 0, 2, 4, 6, or 8 bits

[0149] - Phase Tracking Reference Signal (PTRS) - DMRS Correlation - 0 or 2 bits.

[0150] -beta_offset indicator — 0 or 2 bits

[0151] -DMRS sequence initialization - 0 or 1 bit

[0152] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, and in this respect, its CRC can be scrambled by C-RNTI. The DCI format 1_0 with CRC scrambled by C-RNTI can include several pieces of information. However, this disclosure is not limited thereto.

[0153] -DCI format identifier——[1] bits

[0154] -Frequency domain resource allocation-- Bit

[0155] -Time Domain Resource Assignment - Xbit

[0156] -VRB to PRB mapping - 1 bit.

[0157] -Modulation and coding scheme -5 bits

[0158] -New data indicator -1 bit

[0159] -Redundant version - 2 bits

[0160] -HARQ process ID - 4 bits

[0161] - Downlink assignment index - 2 bits

[0162] - TPC commands used for scheduling PUCCH - [2] bits

[0163] -Physical Uplink Control Channel (PUCCH) Resource Indicator- 3 bits

[0164] -PDSCH-to-HARQ feedback timing indicator — [3] bits

[0165] DCI format 1_1 can be used as a non-back-off DCI for scheduling PDSCH, and in this respect, its CRC can be scrambled by C-RNTI. The DCI format 1_1 with CRC scrambled by C-RNTI can include several pieces of information. However, this disclosure is not limited thereto.

[0166] - Carrier indicator — 0 or 3 bits

[0167] -DCI format identifier——[1] bits

[0168] -BWP indicator - 0, 1, or 2 bits

[0169] -Frequency domain resource allocation

[0170] For resource allocation type 0, Bit

[0171] For resource allocation type 1, Bit

[0172] -Time-domain resource allocation - 1, 2, 3, or 4 bits

[0173] -VRB to PRB mapping - 0 or 1 bit, only used for resource allocation type 1.

[0174] • If only resource allocation type 0 is configured, then it is 0 bits;

[0175] Otherwise, it is 1 bit.

[0176] -PRB bundle size indicator - 0 or 1 bit

[0177] - Rate Matching Indicator - 0, 1, or 2 bits

[0178] -Zero Power (ZP) CSI Reference Signal (RS) Trigger -0, 1, or 2 bits

[0179] For Transport Block (TB) 1:

[0180] -Modulation and coding scheme -5 bits

[0181] -New data indicator -1 bit

[0182] -Redundant version - 2 bits

[0183] For Transport Block (TB) 2:

[0184] -Modulation and coding scheme -5 bits

[0185] -New data indicator -1 bit

[0186] -Redundant version - 2 bits

[0187] -HARQ process ID - 4 bits

[0188] - Downlink assignment index - 0, 2, or 4 bits

[0189] - TPC command used for scheduling PUCCH - 2 bits

[0190] -PUCCH resource indicator - 3 bits

[0191] -PDSCH-to-HARQ_feedback timing indicator — 3 bits

[0192] - Antenna port - 4, 5, or 6 bits

[0193] -Transmission configuration indication - 0 or 3 bits

[0194] -SRS Request - 2 bits

[0195] -CBG transmission information—0, 2, 4, 6, or 8 bits:

[0196] -CBG Clear Message - 0 or 1 bit

[0197] -DMRS sequence initialization - 1 bit

[0198] The following section will now describe a method for allocating time-domain resources to data channels in a 5G communication system.

[0199] The BS can configure the UE using tables of time-domain resource allocation information for PDSCH and PUSCH via higher-layer signaling (e.g., RRC signaling). For example, the BS can configure a table for PDSCH consisting of a maximum of 16 entries (maxNrofDL-Allocations) and a table for PUSCH consisting of a maximum of 16 entries (maxNrofUL-Allocations). For example, the time-domain resource allocation information may include PDCCH-PDSCH time slot timing (corresponding to the time interval of the time slot unit between the time when the PDCCH is received and the time when the PDSCH scheduled by the received PDCCH is transmitted, and marked as K0), PDCCH-PUSCH time slot timing (corresponding to the time interval of the time slot unit between the time when the PDCCH is received and the time when the PUSCH scheduled by the received PDCCH is transmitted, and marked as K2), information about the position and length of the start symbol in the time slot on which the PDSCH or PUSCH is scheduled, the mapping type of the PDSCH or PUSCH, etc. For example, the BS can notify the UE of multiple pieces of information as shown in Tables 7 and 8 below. However, this disclosure is not limited thereto.

[0200] [Table 7]

[0201]

[0202]

[0203] [Table 8]

[0204]

[0205] The BS can notify the UE of one of the entries in a table regarding time-domain resource allocation information via L1 signaling (e.g., DCI). (For example, it can instruct the use of the 'time-domain resource allocation' field in the DCI). The UE can obtain time-domain resource allocation information about the PDSCH or PUSCH based on the DCI received from the BS.

[0206] The DL control channel in a 5G communication system will now be described in detail below with reference to the accompanying drawings.

[0207] Figure 2 This is a diagram illustrating an example of a core set transmitted in a 5G communication system according to an embodiment of the present disclosure, wherein the DL control channel is transmitted. (See reference...) Figure 2 The following embodiment is illustrated: A UE BWP 210 is configured on the frequency axis, and two CORESETs (CORESET#1 201 and CORESET#2 202) are configured in a time slot 220 on the time axis. CORESETs 201 and 202 can be configured as specific frequency resources 203 within the entire UE BWP 210 on the frequency axis. CORESETs 201 and 202 can be configured as one or more OFDM symbols on the time axis and can be defined as the duration of the control resource set 204. Reference Figure 2 For example, CORESET#1 201 can be configured for the duration of a control resource set for two symbols, and CORESET#2 202 can be configured for the duration of a control resource set for one symbol.

[0208] In a 5G communication system, the CORESET can be configured for the UE by the BS via higher-layer signaling (e.g., system information, MIB, or RRC signaling). Configuring the UE with a CORESET may mean providing information such as the CORESET's identity, frequency location, and symbol duration. For example, higher-layer signaling may include multiple pieces of information as shown in Table 9 below. However, this disclosure is not limited thereto.

[0209] [Table 9]

[0210]

[0211] In Table 9, the tci-StatesPDCCH (referred to as Transmission Configuration Indicator (TCI) state) configuration information may include information about one or more SS / PBCH block indices that have a quasi-co-address (QCL) relationship with the DMRS or Channel State Information Reference Signal (CSI-RS) index transmitted in the corresponding CORESET.

[0212] For example, DCI format 1_1, which is scheduling control information (DL authorization) regarding DL data, may include multiple control messages. However, this disclosure is not limited thereto.

[0213] - Carrier Indicator: Indicates on which carrier the data scheduled by the DCI will be transmitted—0 or 3 bits

[0214] -DCI format identifier: Indicates the DCI format, and in particular, is used to identify whether the corresponding DCI is used for DL ​​or UL. -[1] bits

[0215] - Bandwidth Partial Indicator: Indicated during BWP switching – 0, 1, or 2 bits.

[0216] - Frequency domain resource assignment: This is the resource assignment information used to indicate frequency domain resource assignment, and the resource to be indicated varies depending on whether the resource assignment type is 0 or 1.

[0217] - Time-domain resource assignment: This is resource assignment information used to indicate time-domain resource allocation, and can be indicated via higher-level signaling or a configuration from a predefined PDSCH time-domain resource assignment list—1, 2, 3, or 4 bits.

[0218] -VRB to PRB mapping: Indicates the mapping relationship between VRP and PRB - 0 or 1 bit

[0219] -PRB Bundle Size Indicator: Indicates the PRB bundle size that will be applied assuming the same precoding—0 or 1 bit.

[0220] - Rate Matching Indicator: Indicates which rate matching group among those configured for PDSCH via higher-layer signaling will be applied—0, 1, or 2 bits.

[0221] -ZP CSI-RS trigger: Triggers ZP CSI-RS – 0, 1, or 2 bits

[0222] - Transport Block (TB) Configuration Information: Indicates the modulation and coding scheme (MCS), new data indicator (NDI), and redundancy version (RV) for one or two TBs.

[0223] -MCS: Indicates the modulation scheme and coding rate used in data transmission. That is, it can indicate the coding rate value used to notify the transport block size (TBS) and channel coding information, as well as whether it is quadrature phase shift keying (QPSK), 16 quadrature amplitude modulation (QAM), 64QAM, or 256QAM.

[0224] -NDI: Indicates whether it is an initial HARQ transmission or a retransmission.

[0225] -RV: Indicates a redundant version of HARQ.

[0226] - HARQ process number: Indicates the HARQ process number to be applied to PDSCH - 4 bits

[0227] - Downlink Assignment Index: This is an index used to generate a dynamic HARQ-ACK codebook for reporting HARQ-ACKs on the PDSCH—0, 2, or 4 bits.

[0228] - TPC command for PUCCH scheduling: Power control information to be applied to the PUCCH used to report HARQ-ACKs about PDSCH - 2 bits

[0229] -PUCCH Resource Indicator: This indicates the resources of the PUCCH used to report HARQ-ACKs on the PDSCH—3 bits.

[0230] -PDSCH-to-HARQ_feedback timing indicator: This is a configuration information (3 bits) indicating in which time slot the PUCCH used to report HARQ-ACKs about the PDSCH will be sent.

[0231] - Antenna Port: Information indicating the antenna port of the PDSCH DMRS and DMRS Code Division Multiple Access (CDM) group in which PDSCH is not transmitted—4, 5, or 6 bits.

[0232] - Transmission Configuration Indication: This indicates the beam information of the PDSCH—0 or 3 bits.

[0233] -SRS Request: This is a 2-bit message requesting the SRS to send.

[0234] -CBG transmission information: This indicates which data from which CBG will be transmitted via PDSCH when CBG-based retransmission is configured—0, 2, 4, 6, or 8 bits.

[0235] -CBG Clear Information: This indicates whether a previously received CBG by the UE can be used in a HARQ combination—0 or 1 bit.

[0236] -DMRS sequence initialization: Indicates DMRS sequence initialization parameters - 1 bit

[0237] For data transmissions via PDSCH or PUSCH, time-domain resource allocation can be indicated by using information about the time slot on which the PDSCH / PUSCH is transmitted, and S as the position of the start symbol in that time slot, and L as the number of symbols to which the PDSCH / PUSCH is mapped. S can be the relative position from the start of the time slot, L can be a consecutive number of symbols, and S and L can be determined according to the start and length indicator values ​​(SLIV) as defined in Equation 1 below.

[0238] if (L-1)≤7 then

[0239] SLIV = 14·(L-1) + S

[0240] else

[0241] SLIV = 14·(14-L+1)+(14-1-S)

[0242] where 0<L≤14-S---Equation 1

[0243] In an NR system, a UE can be configured via RRC with a single line of information (e.g., the information can be configured in the form of a table) including the SLIV value, PDSCH / PUSCH mapping type, and the time slot on which the PDSCH / PUSCH is transmitted. The DCI's time-domain resource allocation then indicates the index value of the configured table, and by doing so, the BS can send the UE the SLIV value, PDSCH / PUSCH mapping type, and the time slot on which the PDSCH / PUSCH is transmitted.

[0244] In NR systems, PDSCH mapping types are defined as Type A and Type B. In PDSCH mapping type A, the first symbol in the DMRS symbol is located in the second or third OFDM symbol of the time slot. In PDSCH mapping type B, the first symbol in the DMRS symbol is located in the first OFDM symbol in the time domain resources allocated for PDSCH transmission.

[0245] DL data can be transmitted on the PDSCH, which serves as the physical channel for transmitting DL data. The PDSCH can be transmitted after the duration of the control channel transmission, and scheduling information, such as the specific mapping position or modulation scheme in the frequency domain, can be determined based on the DCI transmitted on the PDCCH.

[0246] The BS can inform the UE of the modulation scheme applied to the PDSCH to be transmitted and the size of the data to be transmitted (transmission block size (TBS)) by configuring the MCS in the control information of the DCI. According to embodiments of this disclosure, the MCS may consist of 5 bits, or may consist of fewer or more than 5 bits. The TBS corresponds to the size of the data (transmission block (TB)) to be transmitted by the BS before the channel coding for error correction is applied.

[0247] In this disclosure, a TB may include a Media Access Control (MAC) header, a MAC Control Element (MAC CE), one or more MAC Service Data Units (MAC SDUs), and padding bits. Alternatively, a TB may refer to a data unit or MAC Protocol Data Unit (MAC PDU) delivered from the MAC layer to the physical layer.

[0248] The modulation schemes supported by the NR system are QPSK, 16QAM, 64QAM, or 256QAM, with modulation orders (Qm) corresponding to 2, 4, 6, and 8, respectively. That is, each symbol of 2 bits can be transmitted in QPSK, each symbol of 4 bits in 16QAM, each symbol of 6 bits in 64QAM, and each symbol of 8 bits in 256QAM.

[0249] Figure 3 and Figure 4 The illustration shows the allocation of multiple data streams in frequency-time resources for eMBB, URLLC, and mMTC services considered in 5G or NR systems, according to various embodiments of the present disclosure.

[0250] refer to Figure 3 and Figure 4 This illustrates how frequency and time resources are allocated for information transmission in each system.

[0251] Figure 3 This illustrates the allocation of data for eMBB, URLLC, and mMTC across the entire system frequency band. First, Figure 3This illustrates the allocation of data for eMBB, URLLC, and mMTC across the entire system frequency band 300. When eMBB 301 and mMTC 309 are allocated in a specific frequency band and transmitted, multiple URLLC data entries 303, 305, and 307 can be transmitted when multiple URLLC data entries 303, 305, and 307 are transmitted, without transmitting or clearing the allocation portion for eMBB 301 or mMTC 309. Because URLLC in service requires reduced latency, URLLC data can be allocated to portions 303, 305, and 307 of the resource 301 to which eMBB is allocated and can be transmitted. Clearly, when URLLC is additionally allocated and transmitted on the resource to which eMBB is allocated, eMBB data may not be transmitted on overlapping frequency-time resources, and therefore, the transmission performance of eMBB data may be degraded. That is, in the above situation, eMBB data transmission failure may occur due to the allocation of URLLC.

[0252] Figure 4 This is a diagram illustrating an example where system frequency bands are divided and allocated eMBB, URLLC, and mMTC data. (Reference) Figure 4 The entire system frequency band 400 can be divided, and services and data can be transmitted in each of sub-bands 402, 404, and 406. Configuration information associated with the sub-bands can be pre-configured and sent from the BS to the UE via higher-layer signaling. Alternatively, the BS or network node can randomly divide the sub-bands and provide services without sending sub-band configuration information to the UE separately. Figure 4 It is shown that sub-band 402 is used for the transmission of eMBB data 408, sub-band 404 is used for the transmission of URLLC data 410, 412m and 414, and sub-band 406 is used for the transmission of mMTC data 418.

[0253] For the purpose of describing the methods and apparatus proposed in the various embodiments of this disclosure, the terminology of physical channels and signals in NR systems may be used. However, the content of this disclosure can be applied not only to NR systems but also to wireless communication systems.

[0254] In this document, various embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the description of this disclosure, detailed explanations of related technologies are omitted where it is believed that such detailed explanations might unnecessarily obscure the essence of the present disclosure. The terminology used in the document is defined in consideration of the functions used in this disclosure and may be changed according to the intent or common practice of the user or operator. Therefore, the definitions of terms are to be understood based on the entire description of this disclosure.

[0255] In this disclosure, DL refers to the radio transmission path of a signal to be transmitted from the BS to the UE, and UL refers to the radio transmission path of a signal to be transmitted from the UE to the BS.

[0256] Although the NR system is described as an example in the following description, embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Furthermore, embodiments of this disclosure can also be applied to other communication systems with partial modifications without significantly departing from the scope of this disclosure based on the determination of a person skilled in the art.

[0257] In this disclosure, the conventional terms for physical channels and signals may be used interchangeably with data or control signals. For example, PDSCH refers to the physical channel through which data is transmitted, but in this disclosure, PDSCH may refer to data.

[0258] In the following, in this disclosure, higher-layer signaling refers to a method of transmitting signals from the BS to the UE using the physical layer's DL data channel or from the UE to the BS using the physical layer's UL data channel, and may also be referred to as RRC signaling or MAC CE.

[0259] Figure 5 An example is shown of a process in which a TB is divided into multiple code blocks and CRCs are added to them, according to an embodiment of the present disclosure.

[0260] refer to Figure 5 A TB 501, which will be transmitted in UL or DL, may have a CRC 503 appended to its header or tail. The CRC 503 may have 16 bits, 24 bits, or a prefix number of bits, or may have bits that vary depending on channel conditions, and may be used to determine whether channel coding was successful. At operation 505, the block of TB 501 to which the CRC 503 is added may be divided into multiple code blocks (CBs) 507, 509, 511, and 513. Here, the maximum size of the divided CBs 507, 509, 511, and 513 may be prefixed, and in this case, the last CB 513 may have a smaller size than the other CBs 507, 509, and 511. However, this is merely an example, and according to another embodiment of this disclosure, 0, a random value, or 1 may be inserted into the last CB 513, such that the length of the last CB 513 may be synchronized with the lengths of the other CBs 507, 509, and 511.

[0261] Furthermore, at operation 515, CRC 517, 519, 521, and 523 can be added to CB 507, 509, 511, and 513, respectively. The CRC can have 16 bits, 24 bits, or a prefix number of bits, and can be used to determine whether the channel coding was successful.

[0262] TB 501 and loop generator polynomials can be used to generate CRC 503, and loop generator polynomials can be defined in various ways. For example, suppose the loop generator polynomial for a 24-bit CRC is g. CRC24A (D)=D 24 +D 23 +D 18 +D 17 +D 14 +D 11 +D 10 +D 7 +D 6 +D 5 +D 4 +D 3 +D+1, and L=24, for TB data a0, a1, a2, a3, ..., a A-1 , CRCp0, p1, p2, p3, ..., p L-1 It can be determined as a value with a remainder of 0, which is achieved by a0D A+L-1 +a1D A+L-2 +...+a A-1 D L +p0D L-1 +p1D L-2 +...+p L-2 D 1 +p L-1 Divide by g CRC24A (D) is obtained. In the example above, the CRC length L can be determined to be any of various lengths including 12, 16, 24, 32, 40, 48, 64, etc.

[0263] After the CRC is added to TB in the above process, TB+CRC can be divided into N CBs (e.g., CBs 507, 509, 511, and 513). At operation 515, CRCs 517, 519, 521, and 523 can be added to the divided CBs 507, 509, 511, and 513, respectively. The CRCs added to CBs can have different lengths than those added to TB, or different cyclic generator polynomials can be used to generate the CRCs. Furthermore, depending on the type of channel code to be applied to the CBs, CRC 503 added to TB 501 and CRCs 517, 519, 521, and 523 added to CBs 507, 509, 511, and 513 can be omitted. For example, when LDPC codes instead of turbo codes are to be applied to CB 507, 509, 511 and 513, CRC 517, 519, 521 and 523 to be added to CB 507, 509, 511 and 513 can be omitted.

[0264] As another example, even when LDPC is applied, CRC 517, 519, 521, and 523 can be added to CB507, 509, 511, and 513. Furthermore, when polarity codes are used, CRC can be added or omitted.

[0265] As referenced above Figure 5 The maximum length of a CB can be determined based on the type of channel coding to be applied, and the TB to be transmitted and the CRC to be added to the TB can be divided into multiple CBs according to the maximum length of the CB. In the LTE system, the CRC for the CB is added to the divided CB, and the data bits of the CB and the CRC are encoded by the channel code to determine the coded bits, and each of the coded bits is rate-matched in a predetermined manner so that the number of bits can be determined.

[0266] [TB Size (TBS) Determination Scheme]

[0267] In NR systems according to various embodiments of this disclosure, the TB size (TBS) for UL and DL can be calculated using the following process. Here, the definitions of the key parameters conform to the 3GPP standard rule TS 38.214.

[0268] Step 1: N′ RE It is the number of REs allocated to each PRB in the PDSCH mapping within the allocated resources.

[0269] N′ RE It can be calculated as Here, It is 12, and It can indicate the number of OFDM symbols assigned to the PDSCH. Indicates the number of REs for each PRB occupied by DMRS in the same CDM group. This indicates the number of REs per PRB occupied by overhead configured by higher-level signaling, and can be configured as one of 0, 6, 12, and 18. Then, N is the total number of REs allocated to the PDSCH. RE It can be calculated. N RE Calculated as N RE =min(156, N′) RE )·n PRB And n PRB Indicates the number of PRBs allocated to the UE.

[0270] Step 2: N as temporary information bits inf o can be calculated as N RE ·R·Q m ·v. Here, R represents the bit rate, Q... m The value indicates the modulation order, and this information can be delivered using a table predefined by the MCS bit field of the DCI. Furthermore, v indicates the number of layers allocated. If N info If the value is ≤3824, then TBS can be calculated using step 3. Otherwise, TBS can be calculated using step 4.

[0271] Step 3: N′ info It can be done by using and The equation is used for calculation. TBS can be determined as not less than N′ in Table 10 below. info The value closest to N′ info The value of .

[0272] [Table 10]

[0273] index TBS index TBS index TBS index TBS 1 24 31 336 61 1288 91 3624 2 32 32 352 62 1320 92 3752 3 40 33 368 63 1352 93 3824 4 48 34 384 64 1416 5 56 35 408 65 1480 6 64 36 432 66 1544 7 72 37 456 67 1608 8 80 38 480 68 1672 9 88 39 504 69 1736 10 96 40 528 70 1800 11 104 41 552 71 1864 12 112 42 576 72 1928 13 120 43 608 73 2024 14 128 44 640 74 2088 15 136 45 672 75 2152 16 144 46 704 76 2216 17 152 47 736 77 2280 18 160 48 768 78 2408 19 168 49 808 79 2472 20 176 50 848 80 2536 21 184 51 888 81 2600 22 192 52 928 82 2664 23 208 53 984 83 2728 24 224 54 1032 84 2792 25 240 55 1064 85 2856 26 256 56 1128 86 2976 27 272 57 1160 87 3104 28 288 58 1192 88 3240 29 304 59 1224 89 3368 30 320 60 1256 90 3496

[0274] Step 4: N′ info It can be done by using and The equation is used to calculate TBS. TBS can be calculated based on the value N′ of equation 2 below. info It is determined by the pseudocode. The following C corresponds to the number of code blocks included in a TB.

[0275]

[0276] [LBRM Solution]

[0277] In an NR system, when a CB is input to an LDPC encoder, parity bits are added to the CB, which can then be output. In this respect, the number of parity bits can vary depending on the LDPC basemap. For a given input, the method of transmitting all parity bits generated by the LDPC encoder can be called full buffered rate matching (FBRM), and the method where the number of transmittable parity bits is limited can be called finite buffered rate matching (LBRM). When resources are allocated for data transmission, the output of the LDPC encoder is generated as a circular buffer, and the bits in the generated buffer are repeatedly transmitted as many times as the allocated resources, and the length of the circular buffer can be N. cb .

[0278] When the number of parity bits generated by LDPC encoding is N, in the FBRM scheme, N cb =N. In LBRM, N cb =min(N, N) ref ), N ref pass Given, and R LBRM It can be determined to be 2 / 3. To obtain TBS... LBRM The method described above for calculating TBS is used, and the calculation can be performed based on the assumption that the UE supports the maximum number of layers and the maximum modulation order in the corresponding cell. When the MCS table supporting 256QAM is configured for at least one BWP in the corresponding cell, the maximum modulation order Q... m It can be assumed to be 8, and when not configured, it can be assumed to be 6 (64QAM), and the bitrate can be assumed to be 948 / 1024 of the maximum bitrate, N. RE It can be assumed to be N RE =156·n PRB And n PRB It can be assumed to be n PRB,LBRM n PRB,LBRM It can be given in Table 11 below.

[0279] [Table 11]

[0280]

[0281] [Maximum Data Rate]

[0282] In NR systems according to various embodiments of this disclosure, the maximum data rate supported by the UE can be determined by using the following Equation 3.

[0283]

[0284] In Equation 3 above, J can indicate the number of carriers grouped due to carrier aggregation (CA), Rmax = 948 / 1024. It can indicate the maximum number of floors. It can indicate the maximum modulation order, f (j) The scaling index can be specified, and μ can indicate the subcarrier spacing. The UE can report a value among 1, 0.8, 0.75, and 0.4 as f. (j) And μ can be given in Table 12 below.

[0285] [Table 12]

[0286] μ <![CDATA[Δf=2 μ ·15[kHz]]]> Cyclic prefix 0 15 normal 1 30 normal 2 60 normal 3 120 Normal, expansion 4 240 normal

[0287] also, Indicates the average OFDM symbol length, It can be done through Calculated, and Indicates the maximum number of RBs in BW(j). OH (j) The overhead value is indicated; it can be given as 0.14 in the DL for FR1 (band equal to or less than 6 GHz) and 0.18 in the UL, and as 0.08 in the DL for FR2 (band greater than 6 GHz) and 0.10 in the UL. The maximum data rate in the DL of a cell with a 100 MHz frequency bandwidth in a 30 kHz subcarrier spacing can be calculated using Equation 3 as shown in Table 13 below.

[0288] [Table 13]

[0289]

[0290] On the other hand, the actual data rate that can be measured by the UE can be a value obtained by dividing the data amount by the data transmission time. This can correspond to the value of TBS in 1TB transmission, or the value obtained by dividing the sum of TBS by the transmission time interval (TTI) length in 2TB transmission. For example, based on the assumptions of the calculations in Table 13, the maximum data rate in the DL of a cell with a frequency bandwidth of 100MHz in a 30kHz subcarrier spacing can be determined based on the number of allocated PDSCH symbols, as shown in Table 14 below.

[0291] [Table 14]

[0292]

[0293] The maximum data rate supported by the UE can be identified based on Table 13, and the actual data rate after the allocated TBS can be identified via Table 14. Here, there may be cases where the actual data rate is greater than the maximum data rate according to the scheduling information.

[0294] In wireless communication systems, specifically in NR systems, the data rate that a UE can support can be defined between the BS and the UE. The data rate can be calculated using the maximum bandwidth, maximum modulation order, maximum number of layers, etc., supported by the UE. However, the calculated data rate may differ from the value calculated from the lengths of the TBS and TTI used in actual data transmission.

[0295] Therefore, a UE can be assigned a TBS greater than the value corresponding to the data rate supported by the UE, and to prevent this, the scheduling of TBS can be limited according to the data rate supported by the UE.

[0296] Figure 6 This is a diagram illustrating the mapping of the synchronization signal (SS) and PBCH in an NR system according to an embodiment of the present disclosure to the frequency and time domains. Reference Figure 6 The primary synchronization signal (PSS) 701, secondary synchronization signal (SSS) 703 and PBCH 705 are mapped to 4 OFDM symbols, and PSS 701 and SSS 703 are mapped to 12 RBs, and PBCH 7050 is mapped to 20 RBs. Figure 6 The diagram illustrates how the frequency band of 20 RBs changes according to the subcarrier spacing (SCS). The resource area on which PSS, SSS, and PBCH are transmitted can be referred to as the SS / PBCH block. Furthermore, the SS / PBCH block can be referred to as the SSB block.

[0297] Figure 7 This is a diagram illustrating symbols that can be transmitted on an SS / PBCH block according to an embodiment of the present disclosure, depending on the subcarrier spacing.

[0298] refer to Figure 7 The subcarrier spacing can be configured to 15kHz, 30kHz, 120kHz, 240kHz, etc., and the position of the symbol that can be located on the SS / PBCH block (or SSB block) can be determined according to each subcarrier spacing. Figure 7 This shows the location of the SSB block within a 1ms interval, which can be transmitted based on the subcarrier interval. The location of the SSB block transmission can be configured for the UE via system information or dedicated signaling.

[0299] Typically, the UE is located far from the BS, and therefore, signals transmitted from the UE can be received by the BS after a propagation delay. Propagation delay is a value obtained by dividing the path of radio waves delivered from the UE to the BS by the speed of light, and typically, it can be a value obtained by dividing the distance between the UE and the BS by the speed of light. In embodiments of this disclosure, when the UE is located 100 km from the BS, the signal transmitted from the UE is received by the BS after 0.34 ms. Conversely, the signal transmitted from the BS is received by the UE after 0.34 ms. As mentioned above, the arrival time of a signal transmitted from the UE to the BS can vary depending on the distance between the UE and the BS. Therefore, when multiple UEs located in different locations transmit signals simultaneously, the arrival time of the signal to the BS may vary. To address this issue and allow signals transmitted from multiple UEs to arrive at the BS simultaneously, the timing of the UE transmitting the UL signal can vary depending on the location of each UE. In 5G, NR, and LTE systems, this is referred to as timing advance.

[0300] Figure 8 This is a diagram illustrating the UE processing time according to a timing advance in a 5G or NR system when a UE receives a first signal and sends a second signal in response to the first signal, according to an embodiment of the present disclosure.

[0301] The UE processing time, based on the timed advance, will now be described in detail below. (Reference) Figure 8 When the BS sends a UL scheduling grant (UL grant) or DL ​​control signal and data (DL grant and DL data) to the UE in time slot n902, the UE can receive the UL grant or DL ​​grant and DL data in time slot n904. Here, the UE can receive the signal after a propagation delay (Tp) 910 compared to the time the BS sends the signal. In embodiments of this disclosure, when the UE receives the first signal in time slot n904, the UE sends a second signal corresponding to it in time slot n+4906. When the UE sends a signal to the BS, in order to ensure that the signal arrives at the BS at a specific time, when the time slot in which the UE receives the reference signal is n, the UE can send a HARQ ACK / NACK regarding the UL data or DL ​​data in time slot 906, which is a timing advance (TA) 912 before time slot n+4908, in order to ensure that the signal arrives at the BS at a specific time. Therefore, in embodiments of this disclosure, at operation 914, the time when the UE can receive the UL grant and send the UL data or receive the DL data and prepare to deliver the HARQ ACK or NACK can be the time corresponding to the three time slots excluding TA.

[0302] To determine the aforementioned timing, the BS can calculate the absolute value of the TA (Temporal Transfer) of the UE. The BS can calculate the absolute value of the TA by adding the change in the value of the TA delivered by higher-layer signaling to the value of the TA first delivered to the UE during the random access process at initial access, or by subtracting the change in the value of the TA delivered by higher-layer signaling from the value of the TA first delivered to the UE during the random access process at initial access. In this disclosure, the absolute value of the TA can correspond to the value obtained by subtracting the start time of the nth TTI (Time Trial) received by the UE from the start time of the nth TTI (Time Trial) sent by the UE.

[0303] One of the key performance indicators for cellular wireless communication systems is packet data latency. Therefore, in LTE systems, signal transmission and reception are performed in subframes with a time interval (TTI) of 1 ms. LTE systems operating in this manner can support UEs with TTIs shorter than 1 ms (short TTI UEs). In 5G or NR systems, the TTI can be shorter than 1 ms. Short TTI UEs are suitable for LTE voice (VoLTE) services or services such as remote control, where latency is critical. Furthermore, short TTI UEs can be entities capable of implementing mission-critical IoT on top of cellular communications.

[0304] In a 5G or NR system according to embodiments of this disclosure, when the BS transmits a PDSCH including DL data, the DCI used for scheduling the PDSCH can indicate a K1 value corresponding to the timing information of the HARQ-ACK information transmitted by the UE regarding the PDSCH. If there is no indication that the HARQ-ACK information including timing advance should be transmitted before symbol L1, the HARQ-ACK information including timing advance can be transmitted from the UE to the BS at a time point equal to or after symbol L1. If there is an indication that the HARQ-ACK information including timing advance should be transmitted earlier than symbol L1, the HARQ-ACK message may not be valid HARQ-ACK information in the HARQ-ACK transmission from the UE to the BS.

[0305] The symbol L1 can be a cyclic prefix (CP) on which the time point T is from the last time point of PDSCH. proc,1 The first symbol that follows. T proc,1 It can be calculated using the following equation 4.

[0306] T proc,1 =((N1+d) 1,1 +d 1,2 (2048+144)·κ2 -μ )·T c Equation 4

[0307] In equation 4 above, N1, d 1,1 d 1,2 κ, μ and T C It can be defined as follows.

[0308] - When the HARQ-ACK message is sent via PUCCH (UL control channel), d 1,1 =0, and when the HARQ-ACK message is sent via PUSCH (UL shared channel or data channel), d 1,1 =1.

[0309] - In cases where the UE is configured with multiple active configuration carriers or carriers, the maximum timing difference between the carriers can be reflected in the second signal transmission.

[0310] - In the case of PDSCH mapping type A, i.e., when the first DMRS symbol position is the third or fourth symbol of the time slot, when the position index i of the last symbol of the PDSCH is less than 7, it is defined as d. 1,2 =7-i.

[0311] - In the case of PDSCH mapping type B, i.e., when the first DMRS symbol position is the first symbol of the PDSCH, when the length of the PDSCH is 4 symbols, d 1,2 =3, and when the length of PDSCH is 2 symbols, d 1,2 =3+d, where d refers to the number of symbols on which the PDSCH and the control signals used to schedule the PDSCH are overlapped.

[0312] -N1 is defined according to μ as shown in Table 15 below. M = 0, 1, 2, 3 indicate subcarrier spacing of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively.

[0313] [Table 15]

[0314]

[0315] - Depending on the UE capabilities, the value of N1 provided in Table 15 above can be different.

[0316] T c =1 / (Δf) max ·N f ), Δf max =480.10 3 Hz, N f =4096, κ=T s / T c =64,T s =1 / (Δf) ref ·Nf,ref ),

[0317] Δf rcf =15·10 3 Hz, N f,rer -2048

[0318] The definition is as above.

[0319] Furthermore, in a 5G or NR system according to an embodiment of this disclosure, when the BS sends control information including UL authorization, the BS may indicate a K2 value corresponding to the timing information of the UE transmitting UL data or PUSCH through it.

[0320] In the absence of any indication that the PUSCH information including timing advance should be sent before symbol L2, the PUSCH including timing advance may be sent from the UE to the BS at a time point equal to or after symbol L2. If it is indicated that the PUSCH including timing advance should be sent before symbol L2, the UE may ignore the UL authorization control information from the BS.

[0321] Symbol L2 can be from the last time point T of the PDCCH including scheduling authorization. proc,2 The CP of the PUSCH symbol that must be sent next must begin with the first symbol on it. proc,2 It can be calculated using the following equation 5.

[0322] T proc,2 =((N2+d 2,1 (2048+144)·κ2 -μ )·T c ---Equation 5

[0323] In equation 5 above, N2 and d 2,1 κ, μ and T C It can be defined as follows.

[0324] - In the case where the first symbol assigned to PUSCH includes only DMRS, d 2,1 =0, and in addition, d 2,1 =1.

[0325] - In cases where the UE is configured with multiple active configuration carriers or carriers, the maximum timing difference between the carriers can be reflected in the second signal transmission.

[0326] -N2 is defined according to μ as shown in Table 16 below. M = 0, 1, 2, 3 indicate subcarrier spacing of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively.

[0327] [Table 16]

[0328] μ <![CDATA[PUSCH preparation time N2 [symbol]]]> 0 10 1 12 2 23 3 36

[0329] - Depending on the UE capabilities, the value of N2 provided in Table 16 above can be different.

[0330] T c =1 / (Δf) max ·N f ), Δf max =480.10 3 Hz, N f =4096, κ=T s / T c =64,T s =1 / (Δf) rcf ·N f,ref ),

[0331] αf rcf =15·10 3 Hz, N f,ref -2048

[0332] The definition is as above.

[0333] [Bandwidth Component (BWP)]

[0334] According to embodiments of this disclosure, a 5G or NR system can configure a Baseband Window (BWP) within a carrier to allow a specific UE to perform transmission and reception within the configured BWP. This can be implemented to reduce UE power consumption. The Baseband Window (BS) can configure multiple BWPs and can change the active BWP in the control information. The time period during which the UE is allowed to switch BWPs can be defined as shown in Table 17 below.

[0335] [Table 17]

[0336]

[0337] In Table 17, frequency range 1 refers to a frequency band equal to or less than 6 GHz, and frequency range 2 refers to a frequency band greater than 6 GHz. In the above embodiments of this disclosure, type 1 and type 2 may be determined based on UE capabilities. In the above embodiments of this disclosure, scenarios 1, 2, 3, and 4 may be given as shown in Table 18.

[0338] [Table 18]

[0339] Changes in main frequency Variation in masterless frequency Variation in frequency bandwidth Scene 3 Scene 2 Variation in frequency bandwidth Scene 1 Scenario 4 when the subcarrier spacing is changed

[0340] Figure 9This is a diagram illustrating an example according to an embodiment of the present disclosure, in which a BS schedules multiple data packets (e.g., TB) according to a time slot and transmits the data, receives HARQ-ACK feedback on the data, and performs a retransmission in response to the feedback. Reference Figure 9 TB1 is initially transmitted in time slot 0, and the ACK / NACK feedback in response is transmitted in time slot 4. If the initial transmission of TB1 fails and a NACK is received, a retransmission of TB1 can be performed in time slot 8. The timing of the ACK / NACK feedback transmission and the timing of the retransmission can be predetermined or determined based on control information and / or values ​​indicated by higher-layer signaling. Figure 9 This illustrates an example where TB1 through TB8 are sequentially scheduled to time slots starting from time slot 0 and transmitted. This could correspond to, for example, a situation where HARQ process IDs 0 through 7 are assigned to TB1 through TB8 respectively, and TB1 through TB8 are transmitted. If the number of HARQ process IDs available to the BS and UE is only 4, then the sequential transmission of the 8 different TBs may not be performed.

[0341] [Multicast]

[0342] Figure 10 This is a diagram illustrating an example of multicasting from BS 1101 to multiple UEs according to embodiments of this disclosure.

[0343] refer to Figure 10 BS 1101 can inform multiple UEs 1103, 1105, 1107, and 1111 of the G1-RNTI for receiving multicast control information via SIB or preset information, and UEs 1103, 1105, 1107, and 1111 can receive multicast control information by using the G1-RNTI. The G1-RNTI can be scrambled with the CRC of the multicast control information (DCI) and transmitted. Figure 10 In this context, UE 1109 can be a UE that accesses BS 1101 and is assigned a C-RNTI from BS 1101. Furthermore, UE 1111 can be a UE that accesses BS 1101 and is also a UE that is assigned a C-RNTI from BS 1101 and knows the G1-RNTI used for multicast. As described above, when the same control information and data are transmitted and one or more UEs can receive the transmitted control information and data, this situation can be referred to as multicast. Furthermore, as in... Figure 10 In cases where a specific UE, such as UE 1109 and UE 1111, is assigned a UE-specific RNTI value and only that specific UE can receive control information and data by using the RNTI value, this situation can be referred to as unicast.

[0344] A UE can be configured to receive control and data channels for multicast from transmitter A and control or data channels for unicast from transmitter B. In the current embodiment of this disclosure, transmitter A and transmitter B can be the same transmitter or different transmitters. In this disclosure, transmitter A and transmitter B can be a BS, or a vehicle or a regular UE. The case where the transmitter is a BS corresponds to the case where multicast and unicast data transmissions are delivered from the BS (i.e., delivered via a Uu link). In the case where the transmitter is a vehicle or a regular UE, multicast and unicast transmissions can be sidelink transmissions. Here, the transmitter is a UE referred to as the leader node or anchor node in the group, and can perform multicast transmissions to different UEs in the group, and can receive control information from different UEs. Furthermore, embodiments of this disclosure can be modified as if transmitter A were a vehicle and transmitter B were a BS, and can be applied. Embodiments of this disclosure are described by assuming that transmitter A and transmitter B are a single transmitter, but embodiments of this disclosure can be modified and applied to cases where transmitter A and transmitter B are different transmitters.

[0345] To receive control and data channels for multicast / broadcast / multicast, a UE can be configured with an RNTI value corresponding to a unique ID (hereinafter, interchangeable with RNTI (group RNTI, G-RNTI) or group common RNTI, group identifier, or multicast and broadcast service (MBS) RNTI), or can receive RNTI values ​​from a BS in the group or from different UEs (which may be the leader node). The UE can receive control channels for multicast using the G-RNTI value and can receive data channels based on the control channels. In embodiments of this disclosure, control channels for data scheduling can be interchanged with PDCCH or Physical Side Link Control Channel (PSCCH), data channels can be interchanged with PDSCH or Physical Side Link Shared Channel (PSSCH), and feedback channels can be interchanged with PUCCH or PSCCH. Furthermore, the control information for scheduling to be received by the UE can be described as DCI, but can be referred to differently.

[0346] In other words, for example, data for multicast and control information for scheduling data for multicast can be transmitted using G-RNTI. In embodiments of this disclosure, the G-RNTI value or a portion thereof can be scrambled to the CRC of the control information (DC) and channel coding can be applied to it. The RNTI can be different from the UE-specific RNTI for transmitting unicast data and can be configured for multiple UEs. The format of the DCI can be different from the format of the DCI for scheduling data for unicast.

[0347] In this disclosure, the scenario where one UE sends data to multiple UEs, or where a BS sends the same data to multiple UEs, can be referred to as multicast or multi-channel broadcast, and multicast and multicast can be used interchangeably. Furthermore, in this disclosure, data can indicate transport blocks delivered on shared channels such as PDSCH, PUSCH, PSSCH, etc. Considering the FBRM in the DL or sidelink of a 5G NR system, multicast or MBS can be supported. However, the types of UEs receiving multicast or MBS can be diverse, and therefore, some UEs without sufficient buffers may have difficulty operating the soft buffer or may experience performance degradation. Therefore, in cases where some multicast or multicast services or broadcast services (hereinafter, for convenience, referred to as MBS) are provided, LBRM can be applied to stably provide services to multiple diverse UEs.

[0348] This disclosure provides an LBRM scheme for MBS in DL or sidelinks.

[0349] First, the current PDSCH LBRM scheme in 5G NR is as described below in [Traditional Rate Matching Configuration Based on PDSCH-LBRM]. However, the definitions of the main parameters and the table numbers referenced in [Traditional Rate Matching Configuration Based on PDSCH-LBRM] conform to the 3GPP standard rule TS 38.212.

[0350] [Traditional rate matching configuration based on PDSCH-LBRM]

[0351] The codes d0, d1, ..., d from section 5.3.2 N-1 The subsequent bit sequence is written into the r-th coded block of length N. cb In the circular buffer, where N is defined in clause 5.3.2.

[0352] For the r-th code block, if I LBRM =0, then let N be... cb =N, otherwise let N be. cb =min(N,N) ref ),in R LBRM =2 / 3, TBS LBRM This is determined according to section 5.1.3.2 of [TS 38.214] for DL-SCH / PCH, with the following assumptions:

[0353] - The maximum number of layers for a TB for DL-SCH / PCH is given by the minimum of X and 4, where

[0354] - If the higher-level parameter maxMIMO-Layers of the PDSCH-ServingCellConfig of the serving cell is configured, then X is given by that parameter.

[0355] - Otherwise, X is given by the maximum number of PDSCH layers supported by the UE for the serving cell.

[0356] - If the higher-level parameter mcs-Table given by the pdsch-Config of at least one DL BWP of the serving cell is set to 'qam256', then the maximum modulation order Qm is assumed to be 8 for DL-SCH; otherwise, the maximum modulation order Qm is assumed to be 6 for DL-SCH.

[0357] - The maximum coding rate is 948 / 1024;

[0358] -n PRB =n PRB,LBRM This is given in Table 5.4.2.1-1, where, if no other downlink bandwidth portion is configured for the UE, then n for DL-SCH PRB,LBRM The value is determined based on the initial downlink bandwidth portion;

[0359] -N RE =156·n PRB ;

[0360] -C is the number of code blocks in the transport block as determined in Clause 5.2.2.

[0361] [Table 19]

[0362] n PRB,LBRM value

[0363]

[0364] Based on the previous section [Traditional Rate Matching Configuration Based on PDSCH-LBRM], to identify or determine the TBSLBRM when LBRM is applied, the maximum number of layers for a TB can be determined based on the parameter maxMIMO-Layers included in the PDSCH-ServingCellConfig of higher-layer signaling or by the maximum number of layers supported by the UE with respect to PDSCH. Here, its value cannot exceed 4. Furthermore, the modulation order can be determined based on the parameter mcs-Table included in the pdsch-Config of higher-layer signaling or a predetermined value (e.g., 6). Considering services such as MBS, this method may be suitable for situations where LBRM is applied to a specific UE, but may not be suitable for situations where LBRM is applied to multiple UEs.

[0365] Figure 11This is a diagram illustrating an example of a BWP configured in the UL and DL according to an embodiment of the present disclosure.

[0366] refer to Figure 11 A separate BWP can be configured for MBS service, or alternatively, special frequency resources can be configured for MBS in a BWP configured separately for the UE. The BWP for DL ​​and the UL for MBS can be configured via SIB, or alternatively, via UE-specific RRC signaling.

[0367] In embodiments of this disclosure, the UE may receive DL data (PDSCH) and control channel (PDCCH) for DL ​​transmission in an initial BWP, a UE-specific BWP, or a BWP configured for MBS, and may, in response, transmit UL feedback via PUCCH or PUSCH in the initial BWP, a UE-specific BWP, or a BWP configured for MBS.

[0368] This disclosure provides a method in which, when providing MBS services to a UE, the UE uses a UL BWP configured for MBS or a UE-specific BWP to send feedback to the BS regarding DL data or UL control information (UCI).

[0369] [First Embodiment]

[0370] A first embodiment of this disclosure provides a method and a UE, through which the UE selects a BWP for transmitting UCI.

[0371] Figure 12 This is a diagram illustrating examples of a UL BWP configured for UE1, a UL BWP configured for UE2, and a UL BWP for MBS configured for both UEs according to embodiments of this disclosure.

[0372] refer to Figure 12 In the example, the BWP used for MBS is included in the frequency domain of UE2's BWP, but not in the frequency domain of UE1's BWP. In embodiments of this disclosure, each UE may use a UE-specific BWP configured for itself, or a BWP configured for MBS, to send HARQ-ACK feedback information via UL regarding PDCCH or PDSCH transmitted via DL.

[0373] The BWP in which the HARQ-ACK feedback information will be sent can be determined based on priority. In embodiments of this disclosure, when a BWP for the MBS is configured, the HARQ-ACK feedback can be sent using the BWP for the MBS via PUCCH, and when a BWP for the MBS is not configured, the HARQ-ACK feedback can be sent using a UE-specific configured BWP via PUCCH or PUSCH. In another embodiment of this disclosure, if the PUSCH is sent in a UE-specific BWP when the HARQ-ACK feedback for the MBS is sent via the DL, the HARQ-ACK feedback can be sent using the PUSCH sent in the UE-specific BWP, even if the BWP for the MBS is configured. In another embodiment of this disclosure, the BS can configure the UE regarding which UL BWP to send the HARQ-ACK feedback information in via specific bit fields or combinations of bit field values ​​of the DL DCI.

[0374] If none of the BWPs configured for MBS for the UE are included in the frequency range of the currently active UE-specific configured ULBWP, the UE may need a specific time period to switch the active BWP in order to send HARQ-ACK feedback information in the BWP for MBS. Therefore, when none of the BWPs configured for MBS for the UE are included in the frequency range of the currently active UE-specific configured UL BWP, if the time when HARQ-ACK feedback information must be sent in the BWP for MBS is earlier than the predetermined time—that is, without giving the UE a certain value or more processing time—the feedback may not be sent in the BWP for MBS. In this case, the feedback transmission may not be performed in the BWP for MBS; instead, the UE can send HARQ-ACK feedback for MBS in the currently active UL BWP.

[0375] [Second Embodiment]

[0376] A second embodiment of this disclosure provides a method and a UE, through which the UE transmits a UCI in a BWP configured for the MBS, and the BS receives the UCI.

[0377] When a UE sends a HARQ-ACK feedback in a BWP configured for the MBS, the UE needs to select the frequency and time resources to which the PUCCH is mapped. PUCCH resources can be shared by the UE, or different PUCCH resources can be used by the UE to send feedback. PUCCH resources can be determined based on one of the following methods or a combination of at least two of these methods.

[0378] - Method 1: A method that uses specific bit field values ​​of the DCI. For example, the PUCCH resource can be determined based on the DCI, which indicates whether only a NACK or an ACK or NACK is sent via the PUCCH.

[0379] Method 2: A method using the C-RNTI value. This may involve using some bits of the C-RNTI, and for example, possibly 1 or 2 bits of the LSB. Alternatively, conversely, 2 bits of the MSB of the C-RNTI can be used.

[0380] - Method 3: A method using frame number, slot index, etc. The frame number or slot index can be the frame number or slot index at the time when the PUCCH is sent, or alternatively, it can be the frame number or slot index at the time when the PDSCH corresponding to the HARQ-ACK is sent.

[0381] - Method 4: A method that uses whether the BWP for MBS is configured.

[0382] - Method 5: A method using the frequency domain of the UE-specific BWP as the currently active or initial BWP and the frequency domain of the BWP for MBS.

[0383] -Method 6: A method using the time period required for the UE to perform BWP handover and the time points when the PDSCH and PUCCH are sent.

[0384] Method 7: A method using offset values ​​configured by higher-level signaling (MAC CE or RRC signaling)

[0385] Method 8: A method using offset values ​​sent via group public DCI

[0386] Method 9: A method using cell ID

[0387] Figure 13 This is a diagram showing an example of the location of the PUCCH resource in a BWP configured for MBS.

[0388] For example, a PUCCH resource can be determined according to the following equation 6 or 7.

[0389]

[0390]

[0391] In equations 6 and 7, N ID It can indicate a group membership index, or it can be a value determined by C-RNTI, etc. The group membership index can be a value configured for the UE or indicated to the UE. It can indicate the number of PUCCH resources configured in MBS BWP. It can indicate the PRB to which the PUCCH is mapped, and and The number of PRBs and symbols that can be sent on the PUCCH can be indicated separately.

[0392] The LBRM-based parameter configuration and determination methods provided in the various embodiments of this disclosure can perform decoding only when the BS and UE, or the transmitter and receiver, maintain the same configuration or a predefined configuration. Furthermore, new configuration and determination methods can be derived from various combinations of the parameter configuration and determination methods described in the embodiments of this disclosure.

[0393] The transmitter, receiver, and processor of the UE and BS used to execute various embodiments of this disclosure are respectively located in Figure 14 and Figure 15 The following are illustrated. In various embodiments of this disclosure, methods for transmitting and receiving multicast and unicast control information and data, performed by a UE or BS, are described, and in order to perform these methods, the receiver, processor, and transmitter of the BS and UE must operate according to each embodiment of this disclosure. When embodiments of this disclosure are applied to data transmission and reception in a side link, the BS in the following operations can be a UE performing transmission in the side link or a conventional BS. The UE in the following operations can be a UE performing transmission or reception in a side link.

[0394] In detail, Figure 14 This is a block diagram illustrating the internal structure of a UE according to an embodiment of the present disclosure. Figure 14 As shown, a UE according to embodiments of the present disclosure may include a UE receiver 1600, a UE transmitter 1604, and a UE processor 1602. In embodiments of the present disclosure, the UE receiver 1600 and the UE transmitter 1604 may be collectively referred to as a transceiver. The transceiver may transmit signals to or receive signals from the BS. The signals may include control information and data. For this purpose, the transceiver may include an RF transmitter for up-converting and amplifying the frequency of the signal to be transmitted, and an RF receiver for low-noise amplification and down-converting the frequency of the received signal. Furthermore, the transceiver may receive signals via a wireless channel and output signals to the UE processor 1602, and may also transmit signals output from the UE processor 1602 via a wireless channel. The UE processor 1602 may include a controller for controlling a series of processes to allow the UE to operate according to various embodiments of the present disclosure.

[0395] The aforementioned controller for controlling the operation of the UE according to various embodiments of this disclosure may perform the following operations.

[0396] In a communication or broadcast system, a UE (or terminal) can receive signals corresponding to data transmitted from a transmitter or BS, and then appropriately decode the signals based on a channel coding scheme after a proper demodulation process. To perform decoding, the UE must determine the exact same rate matching scheme performed by the transmitter or BS. Therefore, the UE can identify whether LBRM is applied based on instructions regarding LBRM. Here, because the parameter configuration for LBRM operation can vary depending on whether it is unicast (or data transmission to one UE) or multicast / multicast (or data transmission to multiple UEs), an operation to identify whether it is a unicast or multicast transmission can be added. Furthermore, the UE can determine or identify whether it is unicast or multicast / multicast via separate higher-layer signaling or based on a separate indicator transmitted from the BS. When the UE must perform an LBRM operation corresponding to that performed by the transmitter in unicast (or data transmission to one UE), the UE can perform the LBRM operation corresponding to that performed by the transmitter based on a first configuration. And when the UE must perform an LBRM operation corresponding to that performed by the transmitter in multicast / multi-cast (or data transmission to multiple UEs), the UE can perform the LBRM operation corresponding to that performed by the transmitter based on a second configuration. Here, at least one of the parameters corresponding to the first configuration may be different from the parameters corresponding to the second configuration, or at least one of the values ​​of the parameters corresponding to the first configuration may be different from the values ​​of the parameters corresponding to the second configuration. Detailed schemes regarding the first and second configurations can be determined based on appropriate combinations of the operations of the first embodiment, the second embodiment, or each embodiment.

[0397] For convenience, an operation performed by the receiver (e.g., UE) and corresponding to the LBRM of the transmitter (e.g., BS) can be referred to as an LBRM operation. In other words, the receiver's LBRM operation can indicate an operation corresponding to the transmitter's LBRM. Furthermore, while the LBRM operation performed by the BS is an operation performed at the bit level, an operation performed by the receiver and corresponding to the LBRM performed by the transmitter can be performed, corresponding to values ​​generated or determined based on demodulation. For example, when the likelihood ratio (LR) or log-likelihood ratio (LLR) value corresponding to a given transmitted bit is determined by demodulation based on the received signal, the receiver's LBRM operation can be performed based on the LR or LLR value of the given bit or other message values ​​corresponding to it. Therefore, after the LBRM is performed by the receiver, the transmitted data can be determined or reconstructed by performing channel coding decoding based on values ​​corresponding to a bit sequence (e.g., LR or LLR) that is determined or identifiable based on the LBRM and transmitted from the transmitter.

[0398] Figure 15This is a block diagram illustrating the internal structure of a BS according to an embodiment of the present disclosure. Reference Figure 15 According to embodiments of the present disclosure, a BS may include a BS receiver 1701, a BS transmitter 1705, and a BS processor 1703. In embodiments of the present disclosure, the BS receiver 1701 and the BS transmitter 1705 may be collectively referred to as a transceiver. The transceiver may transmit signals to or receive signals from the UE. Signals may include control information and data. For this purpose, the transceiver may include an RF transmitter for up-converting and amplifying the frequency of the signal to be transmitted, and an RF receiver for low-noise amplification and down-converting the frequency of the received signal. Furthermore, the transceiver may receive signals via a wireless channel and output signals to the BS processor 1703, and may also transmit signals output from the BS processor 1703 via a wireless channel. The BS processor 1703 may include a controller for controlling a series of processes to allow the BS to operate according to various embodiments of the present disclosure.

[0399] The aforementioned controller for controlling the operation of the BS according to various embodiments of this disclosure may perform the following operations.

[0400] In a communication or broadcast system, the BS can first appropriately encode the data to be transmitted based on a channel coding scheme. Then, the BS can determine whether to perform LBRM on the encoded data. Here, because the parameter configuration for LBRM operation can vary depending on whether it is unicast (or data transmission to a single UE) or multicast / multi-cast (or data transmission to multiple UEs), an operation to identify whether it is a unicast or multicast / multicast transmission can be added. Furthermore, the BS can indicate to the UE whether it is unicast or multicast / multicast via separate higher-layer signaling or indicators. If the BS must perform LBRM in the case of unicast (or data transmission to a single UE), the BS can perform LBRM based on a first configuration; and if the BS must perform LBRM in the case of multicast / multicast (or data transmission to multiple UEs), the BS can perform LBRM based on a second configuration. Here, at least one of the parameters corresponding to the first configuration may differ from the parameter corresponding to the second configuration, or at least one of the values ​​of the parameter corresponding to the first configuration may differ from the value of the parameter corresponding to the second configuration. Detailed schemes regarding the first and second configurations can be determined based on appropriate combinations of the operations of the first embodiment, the second embodiment, or each embodiment. After the LBRM is executed, the BS can send a bit sequence to the UE (or terminal) by applying appropriate modulation to it, which is determinable or identifiable based on the LBRM.

[0401] While this disclosure has been shown and described with reference to various embodiments thereof, those skilled in the art will understand that various changes, forms, and details may be made therein without departing from the spirit and scope of this disclosure as defined by the appended claims and their equivalents. Furthermore, embodiments may be combined to implement when necessary. For example, first and second embodiments may be combined and applied. Additionally, other modifications to the technical concepts based on embodiments of this disclosure may be applied to LTE systems, 5G systems, etc.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: The system receives configuration information associated with multicast and broadcast service MBS resources within the downlink bandwidth portion (BWP) for receiving the physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH) from the base station via the system information block (SIB), and receives downlink control information (DCI) associated with the hybrid automatic repeat request acknowledgment (HARQ-ACK) of the PDSCH from the base station. Based on the configuration information associated with MBS resources, receive PDCCH and PDSCH from the base station; and Based on DCI, the physical uplink control channel PUCCH associated with the HARQ-ACK of PDSCH is transmitted on the uplink BWP. In the case where the uplink BWP configured for MBS is configured through configuration information associated with MBS resources, the uplink BWP is determined between the terminal-specific uplink BWP and the uplink BWP configured for MBS based on the DCI bit field. The DCI bit field indicates whether only a negative acknowledgment (NACK) or an acknowledgment (ACK / NACK) is sent via PUCCH. In cases where the uplink BWP configured for MBS is not configured using configuration information associated with MBS resources, the uplink BWP is determined to be a terminal-specific uplink BWP.

2. The method according to claim 1, in, Configuration information associated with MBS resources includes terminal-specific BWPs, and Among them, PDCCH and PDSCH are received in the terminal-specific BWP.

3. The method according to claim 1, in, Configuration information associated with MBS resources includes the BWP configured for MBS, and PDCCH and PDSCH are received in the BWP configured for MBS.

4. The method according to claim 1, further comprising: Receive configuration information associated with the terminal's initial BWP from the base station; and Based on the configuration information associated with the terminal's initial BWP, the PDCCH and PDSCH are received from the base station.

5. The method according to claim 1, further comprising: Receive configuration information for HARQ-ACK from PDSCH; and Based on the configuration information of PDSCH HARQ-ACK, determine the priority of PUCCH associated with PDSCH HARQ-ACK.

6. A method performed by a base station in a wireless communication system, the method comprising: The system information block (SIB) sends configuration information associated with multicast and broadcast service MBS resources within the downlink bandwidth portion (BWP) received by the physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH) to the terminal, and sends downlink control information (DCI) associated with the hybrid automatic repeat request acknowledgment (HARQ-ACK) of the PDSCH to the terminal. Based on the configuration information associated with MBS resources, send PDCCH and PDSCH to the terminal; and Based on DCI, the physical uplink control channel PUCCH associated with the HARQ-ACK of PDSCH is received on the uplink BWP. In the case where the uplink BWP configured for MBS is configured through configuration information associated with MBS resources, the uplink BWP is determined between the terminal-specific uplink BWP and the uplink BWP configured for MBS based on the DCI bit field. The DCI bit field indicates whether only a negative acknowledgment (NACK) or an acknowledgment (ACK / NACK) is sent via PUCCH. In cases where the uplink BWP configured for MBS is not configured using configuration information associated with MBS resources, the uplink BWP is determined to be a terminal-specific uplink BWP.

7. The method according to claim 6, in, Configuration information associated with MBS resources includes terminal-specific BWPs, and PDCCH and PDSCH are sent in terminal-specific BWPs.

8. The method according to claim 6, in, Configuration information associated with MBS resources includes the BWP configured for MBS, and PDCCH and PDSCH are sent in the BWP configured for MBS.

9. The method according to claim 6, further comprising: Send configuration information associated with the terminal's initial BWP to the terminal; and Based on the configuration information associated with the initial BWP of the terminal, PDCCH and PDSCH are sent to the terminal.

10. A terminal for a wireless communication system, the terminal comprising: transceiver; and At least one processor is configured as follows: The system receives configuration information associated with multicast and broadcast service MBS resources within the downlink bandwidth portion (BWP) for receiving the physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH) from the base station via the system information block (SIB), and receives downlink control information (DCI) associated with the hybrid automatic repeat request acknowledgment (HARQ-ACK) of the PDSCH from the base station. Based on the configuration information associated with MBS resources, receive PDCCH and PDSCH from the base station; and Based on DCI, the physical uplink control channel PUCCH associated with the HARQ-ACK of PDSCH is transmitted on the uplink BWP. In the case where the uplink BWP configured for MBS is configured through configuration information associated with MBS resources, the uplink BWP is determined between the terminal-specific uplink BWP and the uplink BWP configured for MBS based on the DCI bit field. The DCI bit field indicates whether only a negative acknowledgment (NACK) or an acknowledgment (ACK / NACK) is sent via PUCCH. In cases where the uplink BWP configured for MBS is not configured using configuration information associated with MBS resources, the uplink BWP is determined to be a terminal-specific uplink BWP.

11. The terminal according to claim 10, in, Configuration information associated with MBS resources includes terminal-specific BWPs, and Among them, PDCCH and PDSCH are received in the terminal-specific BWP.

12. The terminal according to claim 10, in, Configuration information associated with MBS resources includes the BWP configured for MBS, and PDCCH and PDSCH are received in the BWP configured for MBS.

13. The terminal according to claim 10, wherein, The at least one processor is further configured to: Receive configuration information associated with the terminal's initial BWP from the base station; and Based on the configuration information associated with the terminal's initial BWP, the PDCCH and PDSCH are received from the base station.

14. The terminal according to claim 10, wherein, The at least one processor is further configured to: Receive configuration information for HARQ-ACK from PDSCH; and Based on the configuration information of PDSCH HARQ-ACK, determine the priority of PUCCH associated with PDSCH HARQ-ACK.

15. A base station for a wireless communication system, the base station comprising: transceiver; and At least one processor is configured as follows: The system information block (SIB) sends configuration information associated with multicast and broadcast service MBS resources within the downlink bandwidth portion (BWP) received by the physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH) to the terminal, and sends downlink control information (DCI) associated with the hybrid automatic repeat request acknowledgment (HARQ-ACK) of the PDSCH to the terminal. Based on the configuration information associated with MBS resources, send PDCCH and PDSCH to the terminal; and Based on DCI, the physical uplink control channel PUCCH associated with the HARQ-ACK of PDSCH is received on the uplink BWP. In the case where the uplink BWP configured for MBS is configured through configuration information associated with MBS resources, the uplink BWP is determined between the terminal-specific uplink BWP and the uplink BWP configured for MBS based on the DCI bit field. The DCI bit field indicates whether only a negative acknowledgment (NACK) or an acknowledgment (ACK / NACK) is sent via PUCCH. In cases where the uplink BWP configured for MBS is not configured using configuration information associated with MBS resources, the uplink BWP is determined to be a terminal-specific uplink BWP.