Method and device for transmitting dsr in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. The present disclosure relates to a method performed by a terminal in a wireless communication system, and a device for performing same, the method comprising the steps of: identifying a physical uplink control channel (PUCCH) resource for a scheduling request (SR) when the SR is pending; identifying whether the PUCCH resource overlaps with an uplink data channel resource and a sidelink resource for which simultaneous transmission with an SR is not allowed; and identifying the PUCCH resource as a prioritized resource when the PUCCH resource does not overlap with the uplink data channel resource and the sidelink resource, wherein an uplink shared channel (UL-SCH) resource of a configured uplink grant that is not available for use is not included in the uplink data channel resource for identifying overlap.

Description

DSR transmission method and device in a wireless communication system

[0001] The present invention relates to the operation of a terminal and a base station in a wireless communication system. More specifically, the present invention relates to a method and device for transmitting a Delay Status Report (DSR) for low-latency data transmission in a wireless communication system.

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

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

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

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

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

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

[0008] The present disclosure provides improved operation of terminals and base stations in wireless communication systems. The present disclosure also provides an improved method for low-latency data transmission in wireless communication systems.

[0009] In order to solve the above problem, one embodiment of the present disclosure provides a method performed by a terminal in a wireless communication system, comprising the steps of: if a scheduling request (SR) is pending, checking a physical uplink control channel (PUCCH) resource for the SR; checking whether the PUCCH resource overlaps with an uplink data channel resource and a sidelink resource that are not allowed to be transmitted simultaneously with the SR; and if the PUCCH resource does not overlap with the uplink data channel resource and the sidelink resource, identifying the PUCCH resource as a prioritized resource, and providing a method in which an uplink shared channel (UL-SCH) resource of a configured uplink grant that is not available for use is not included in the uplink data channel resource for checking the overlap.

[0010] In addition, one embodiment of the present disclosure provides a terminal in a wireless communication system, wherein, if a transceiver and an SR (scheduling request) are pending, a control unit for checking a PUCCH (physical uplink control channel) resource for the SR is included, checking whether the PUCCH resource overlaps with an uplink data channel resource and a sidelink resource that do not allow simultaneous transmission with the SR, and identifying the PUCCH resource as a prioritized resource if the PUCCH resource does not overlap with the uplink data channel resource and the sidelink resource, and a UL-SCH (uplink shared channel) resource of a configured uplink grant that is not available for use is not included in the uplink data channel resource for checking the overlap.

[0011] According to various embodiments of the present disclosure, improved operation of terminals and base stations in a wireless communication system can be provided.

[0012] Additionally, various embodiments of the present disclosure may provide improved methods for low-latency data transmission in wireless communication systems.

[0013] Additionally, according to various embodiments of the present disclosure, an improved DSR transmission method for low-latency data transmission in a wireless communication system can be provided.

[0014] FIG. 1 is a diagram illustrating the structure of an NR system according to one embodiment of the present disclosure.

[0015] FIG. 2 is a diagram illustrating a wireless protocol structure in an NR system according to one embodiment of the present disclosure.

[0016] FIG. 3 is a diagram illustrating a procedure in which a base station sets settings for a medium access control (MAC) layer device (MAC Entity) of a terminal using an RRC (radio resource control) message when the terminal establishes a connection with a network according to one embodiment of the present disclosure.

[0017] FIG. 4 is a diagram illustrating an operation of a terminal indicating a CG (configured grant) PUSCH (physical uplink shared channel) TO (transmission occasion) that will not be used in the future through an unused transmission occasion (UTO)-UCI according to one embodiment of the present disclosure.

[0018] FIG. 5 is a diagram illustrating the structure of a DSR MAC CE (medium access control control element) according to one embodiment of the present disclosure.

[0019] FIG. 6 is a diagram illustrating a CG operation in which autonomous transmission (AutonomousTx) is set according to one embodiment of the present disclosure.

[0020] FIG. 7 is a diagram illustrating operations of a terminal and a base station related to a CG operation in which AutonomousTx is set according to one embodiment of the present disclosure.

[0021] FIG. 8 is a diagram illustrating enhancedSkipUplinkDynamic / skipUplinkTxDynamic operation of a terminal according to one embodiment of the present disclosure.

[0022] FIG. 9 is a diagram illustrating operations of a terminal and a base station according to an enhancedSkipUplinkDynamic / skipUplinkTxDynamic operation according to one embodiment of the present disclosure.

[0023] FIG. 10 is a diagram illustrating a configuration of a terminal according to an embodiment of the present disclosure.

[0024] FIG. 11 is a diagram illustrating a configuration of a base station according to an embodiment of the present disclosure.

[0025] The operating principles of the present disclosure are described in detail below with reference to the attached drawings. In the following description of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0026] In the following description of the present invention, detailed descriptions of known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present invention. Hereinafter, embodiments of the present invention will be described with reference to the attached drawings.

[0027] The operating principles of the present invention are described in detail with reference to the attached diagram. The terms described below are defined based on their functions within the present invention. These terms may vary depending on the intent or custom of the user or operator, and therefore their definitions should be determined based on the overall content of this specification.

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

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

[0030] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided solely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification.

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

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

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

[0034] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A (long term evolution-advanced) may be included here, and the 5G below may also be a concept that includes the existing LTE (long term evolution), LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems through some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.

[0035] In the following description, terms used to identify connection nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0036] For convenience of explanation below, some terms and names defined in the 3rd generation partnership project (3GPP) LTE (long term evolution) standard and / or 3GPP NR (new radio) standard may be used. However, the present disclosure is not limited to the above terms and names, and can be equally applied to systems conforming to other standards.

[0037] Certain terms used in the following description are provided to aid in understanding the present disclosure, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the present disclosure.

[0038] FIG. 1 is a diagram illustrating the structure of an NR system according to one embodiment of the present disclosure.

[0039] Referring to FIG. 1, the wireless communication system may be configured with at least one of multiple base stations (e.g., gNB (100), ng-eNB (110), ng-eNB (120), or gNB (130)), an access and mobility management function (AMF) (140), and a user plane function (UPF) (150). The wireless communication system is not limited to the configuration illustrated in FIG. 1 and may include more or fewer components.

[0040] According to one embodiment of the present disclosure, a user equipment (hereinafter referred to as UE, terminal or terminal) (160) can access an external network through at least one of the base stations (100, 110, 120, 130) or UPF (150).

[0041] In FIG. 1, base stations (100, 110, 120, or 130) may serve as access nodes of a cellular network and provide wireless access to terminals accessing the network. For example, base stations (100, 110, 120, 130) may collect at least one state information, such as a buffer state, an available transmission power state, or a channel state, of terminals to perform scheduling in order to service user traffic. Base stations may support connections between terminals and a core network (CN). CN of NR may mean 5th Generation Core Network (5GC).

[0042] The gNB (100, 130) can control multiple cells. The gNB (100, 130) can apply an adaptive modulation and coding (AMC) method that determines a modulation scheme and channel coding rate according to the channel conditions of the terminal.

[0043] The core network can be a device responsible for various control functions, including mobility management for terminals. The core network can be connected to multiple base stations. Furthermore, 5GC can be integrated with existing LTE systems.

[0044] In a wireless communication system, a user plane (UP) related to transmission of actual user data and a control plane (CP) such as connection management can be configured separately. gNB (100) and gNB (130) can use UP and CP technologies defined in NR technology. ng-eNB (110) and ng-eNB (120) can use UP and CP technologies defined in LTE technology.

[0045] AMF (140) can perform mobility management functions for a terminal. AMF (140) is a device responsible for control functions and can be connected to multiple base stations.

[0046] UPF (150) may refer to a gateway device that provides data transmission. The NR wireless communication system may include a session management function (SMF). The SMF may manage packet data network connections, such as PDU (protocol data unit) sessions provided to terminals.

[0047] FIG. 2 is a diagram illustrating a wireless protocol structure in an NR system according to an embodiment of the present disclosure.

[0048] Referring to FIG. 2, the wireless protocol of the NR system may be composed of at least one of SDAP (service data adaptation protocol) (200), PDCP (packet data convergence protocol) (210), RLC (radio link control) (220), MAC (medium access control) (230), or PHY (physical) (240) at the terminal.

[0049] The wireless protocol of the NR system may be composed of at least one of SDAP (290), PDCP (280), RLC (270), MAC (260), or PHY (250) at the base station.

[0050] In the following, the terms SDAP for SDAP layer, PDCP for PDCP layer, RLC for RLC layer, MAC for MAC layer, PHY for PHY layer, and RRC for RRC layer may be used interchangeably and have the same meaning.

[0051] The SDAP (200 or 290) can carry user data. The SDAP (200 or 290) can perform at least one of the following operations: mapping a quality of service (QoS) flow to a specific data radio bearer (DRB) for the uplink and downlink, marking a QoS flow ID (Identifier) ​​for the uplink and downlink, or mapping a reflective QoS flow to a data bearer for uplink SDAP PDUs. The SDAP configuration corresponding to each DRB can be provided from a higher RRC layer. However, this is only one embodiment, and the operation or function of the SDAP is not limited to the above example.

[0052] PDCP (210 or 280) can perform compression and / or decompression of IP (internet protocol) headers, etc. In addition, PDCP (210 or 280) can provide at least one of the following functions: in-order and / or out-of-order delivery, reordering, duplicate detection, retransmission, encryption, or decryption. However, this is only one embodiment, and the operation or function of PDCP is not limited to the above example.

[0053] The RLC (220 or 270) can reassemble the PDCP PDU into an appropriate size. The RLC (220 or 270) can provide at least one of the following functions: in-order and / or out-of-order delivery function, automatic repeat request (ARQ) function, joining, segmentation, reassembly function, re-segmentation function, reordering function, duplicate detection function, or error detection function. However, this is only an example, and the operation or function of the RLC is not limited to the above example.

[0054] The MAC (230 or 260) can be connected to multiple RLC layer devices configured in one device. The MAC (230 or 260) can perform at least one of an operation of multiplexing RLC protocol data units (PDUs) into MAC PDUs or an operation of demultiplexing RLC PDUs from MAC PDUs. The MAC can provide at least one of a mapping function, a scheduling information reporting function, a hybrid automatic repeat request (HARQ) function, a priority control function between logical channels, a priority control function between terminals, an MBMS (multimedia broadcast and multicast service) service confirmation function, a transmission format selection function, or a padding function. However, this is only one embodiment, and the operation or function of the MAC is not limited to the above example.

[0055] The PHY (240 or 250) can generate OFDM (orthogonal frequency division multiplexing) symbols by channel coding and modulating upper layer data, and transmit the OFDM symbols through a wireless channel. The PHY (240 or 250) can demodulate OFDM symbols received through a wireless channel, perform channel decoding, and transmit them to the upper layer. The PHY layer can use HARQ for additional error correction. The receiver can transmit 1 bit to indicate whether or not it has received a packet transmitted by the transmitter. The 1 bit information can be HARQ ACK (acknowledgement) or NACK (negative acknowledgment) information.

[0056] Downlink HARQ ACK or NACK information for uplink data transmission can be transmitted via the physical hybrid-ARQ indicator channel (PHICH) in LTE. In NR, the need for retransmission or new transmission can be determined through UE scheduling information on the physical downlink control channel (PDCCH), which transmits downlink or uplink resource allocation, etc. This is because NR can apply asynchronous HARQ.

[0057] Uplink HARQ ACK (acknowledgement) or NACK (negative acknowledgment) information for downlink data transmission can be transmitted via a physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH). PUCCH can be transmitted in the uplink of a primary cell (PCell). If the UE supports it, PUCCH can be transmitted in a secondary cell (SCell). For example, if the UE supports it, PUCCH can be transmitted in the uplink of an SCell from the UE to the base station. Here, SCell can refer to a physical uplink control channel (PUCCH) SCell.

[0058] The RRC layer may be located above the PDCP layer of the terminal and base station. The RRC layer can transmit and receive access and / or measurement-related configuration control messages for radio resource control.

[0059] The physical layer may be composed of at least one frequency or at least one carrier. A technology that simultaneously sets and uses multiple frequencies may refer to carrier aggregation (CA). A single carrier may be used for communication between a terminal and a base station (eNB or gNB). When CA technology is used, a primary carrier and at least one secondary carrier may be used for communication between the terminal and the base station. In this case, the data transmission amount may increase according to the increased number of secondary carriers. A cell within a base station using a primary carrier in LTE or NR may refer to a primary cell or PCell. A cell within a base station using a secondary carrier in LTE or NR may refer to a secondary cell or SCell.

[0060] FIG. 3 is a diagram illustrating a procedure in which a base station sets settings for a MAC layer device of a terminal using an RRC message when a terminal establishes a connection with a network according to an embodiment of the present invention.

[0061] Referring to FIG. 3, in the present disclosure, a terminal can establish a connection with a network by switching from RRC idle mode (RRC_IDLE) to RRC connected mode (RRC_CONNECTED). The terminal can establish uplink or downlink transmission synchronization with a base station through a random access process. The terminal can transmit an RRCSetupRequest message to the base station (step 300). The RRCSetupRequest message can include an identifier of the terminal or a reason for establishing a connection (e.g., EstablishmentCause). The base station can transmit an RRCSetup message to the terminal so that the terminal can establish an RRC connection (step 305).

[0062] For example, the RRCSetup message may include MAC layer device configuration information (e.g., MAC-CellGroupConfig) for each Cell Group (e.g., at least one of a master cell group (MCG) or a secondary cell group (SCG)) belonging to the Cell Group. The MAC-CellGroupConfig configuration information may include at least one of the following information:

[0063] - lch-BasedPrioritization: If this field is present, the corresponding MAC entity of the UE is configured with prioritization between overlapping grants and between scheduling request and overlapping grants based on LCH priority, see TS 38.321. The network does not configure lch-BasedPrioritization with enhancedSkipUplinkTxDynamic simultaneously nor lch-BasedPrioritization with enhancedSkipUplinkTxConfigured simultaneously.

[0064] - skipUplinkTxDynamic, enhancedSkipUplinkTxDynamic, enhancedSkipUplinkTxConfigured: If set to true, the UE skips UL transmissions as described in TS 38.321. If the UE is configured with enhancedSkipUplinkTxDynamic or enhancedSkipUplinkTxConfigured with value true, REPETITION_NUMBER (as specified in TS 38.321 [3], clause 5.4.2.1) of the corresponding PUSCH transmission of the uplink grant shall be equal to 1.

[0065] - dsr-ConfigToAddModList: List of LCG (logical channel group)-specific DSR configurations to add or modify.

[0066] - dsr-ConfigToReleaseList: List of LCG-specific DSR configurations to release.

[0067] 일례로, LCG (logical channel group) 별 DSR 설정(LCG-specific DSR configurations)은 아래 표 1과 같이 설정될 수 있다.

[0068] LCG-DSR-Config-r18 ::= SEQUENCE {lcg-Id-r18 LCG-Id-r18,remainingTimeThreshold-r18 INTEGER (1..64)}LCG-Id-r18 ::= INTEGER (0..maxLCG-ID)

[0069] For example, the RRCSetup message contains information about each Cell Group (e.g. MCG or

[0070] For example, the RRCSetup message may include, for each Cell Group (e.g., at least one of MCG or SCG), configuration information for a serving cell (which may be a Serving Cell, SpCell, or SCell) belonging to the Cell Group. For example, the serving cell configuration information (e.g., ServingCellConfig) may include at least one of the following information:

[0071] - tdd-UL-DL-ConfigurationDedicated: UE-specific Uplink / Downlink TDD configuration.

[0072] - uplinkBWP-ToAddModList(list of BWP-Uplink): The additional bandwidth parts for uplink to be added or modified. In case of TDD uplink- and downlink BWP with the same bandwidthPartId are considered as a BWP pair and must have the same center frequency.

[0073] - uplinkBWP-ToReleaseList: The additional bandwidth parts for uplink to be released.

[0074] - cellDTXDRX-Config: Used to configure cell DTX(discontinuous transmission) / DRX(discontinuous reception) for the serving cell, as specified in TS 38.321 [3]. A maximum of two cell DTX / DRX patterns can be configured per MAC entity for different serving cells. The two configured patterns are aligned, that the start and slot offset are common and the periodicity of one pattern is an integer multiple of the other.

[0075] 일례로, 셀 DTX / DRX 설정 정보(cellDTXDRX-Config)는 아래 정보 중 적어도 하나를 포함할 수 있다.

[0076] - cellDTXDRX-CycleStartOffset: cellDTXDRX-Cycle in ms and cellDTXDRX-StartOffset in multiples of 1 ms. The configured cellDTXDRX-Cycle is an integer multiple of configured drx-longCycle or vice versa.

[0077] - cellDTXDRX-onDurationTimer: Value in multiples of 1 / 32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on.

[0078] - cellDTXDRX-SlotOffset: Value in 1 / 32 ms. Value 0 corresponds to 0 ms, value 1 corresponds to 1 / 32 ms, value 2 corresponds to 2 / 32 ms, and so on.

[0079] - cellDTXDRXactivationStatus: Initial activation status of cell DTX / DRX indicating whether the UE shall activate the configuration according to the received parameters. This field is only used upon setup of a cell DTX / DRX configuration.

[0080] - cellDTXDRXconfigType: Indicates whether the configuration is for cell DTX only, cell DRX only, or joint cell DTX / DRX configuration.

[0081] 일례로, BWP-Uplink 설정 정보는 아래 정보 중 적어도 하나를 포함할 수 있다.

[0082] - bwp-Id: An identifier for this bandwidth part. Other parts of the RRC configuration use the BWP-Id to associate themselves with a particular bandwidth part. The network configures the BWPs with consecutive IDs from 1. The Network does not include the value 0, since value 0 is reserved for the initial BWP.

[0083] - bwp-Common(BWP-UplinkCommon): configure the common parameters of an uplink BWP. They are "cell specific" and the network ensures the necessary alignment with corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides the common parameters via dedicated signalling.

[0084] - bwp-Dedicated(BWP-UplinkDedicated): configure the dedicated (UE specific) parameters of an uplink BWP.

[0085] 일례로, bwp-Dedicated 설정 정보에는 아래 설정 정보 중 적어도 하나를 포함할 수 있다.

[0086] - configuredGrantConfig: A Configured-Grant of type1 or type2. It may be configured for UL or SUL but in case of type1 not for both at a time. Except for reconfiguration with sync, the NW does not reconfigure configuredGrantConfig when there is an active configured uplink grant Type 2 (see TS 38.321). However, the NW may release the configuredGrantConfig at any time. Network can only configure configured grant in one BWP using either this field or configuredGrantConfigToAddModList.

[0087] - configuredGrantConfigToAddModList: Indicates a list of one or more configured grant configurations to be added or modified for one BWP. Except for reconfiguration with sync, the NW does not reconfigure a Type 2 configured grant configuration when it is active (see TS 38.321). The network configures multiple CG configurations for one BWP with either all configurations or no configuration configured with cg-RetransmissionTimer-r16.

[0088] 일례로, configured grant(CG) 설정 정보(configuredGrantConfig)는 아래 정보 중 적어도 하나를 포함할 수 있다.

[0089] - nrofHARQ-Processes: The number of HARQ processes configured. It applies for both Type 1 and Type 2. See TS 38.321, clause 5.4.1. If the UE is configured with nrofHARQ-Processes-v1700, the UE shall ignore nrofHARQ-Processes (without suffix).

[0090] - periodicity: Periodicity for UL transmission without UL grant for type 1 and type 2 (see TS 38.321, clause 5.8.2).

[0091] - autonomousTx: If this field is present, the Configured Grant configuration is configured with autonomous transmission, see TS 38.321.

[0092] - harq-ProcID-Offset2: Indicates the offset used in deriving the HARQ process IDs, see TS 38.321, clause 5.4.1. This field is not configured together with cg-RetransmissionTimer-r16. If the field harq-ProcID-Offset2-v1700 is present, the UE shall ignore the harq-ProcID-Offset2-r16.

[0093] - nrofSlotsInCG-Period: Number of consecutive slots for CG PUSCH transmission occasions in a period of a single CG PUSCH configuration, see TS 38.214, clause 6.1. The network does not configure this field for operation on shared spectrum.

[0094] - nrofBitsInUTO-UCI: Indicates the number of bits in the UTO-UCI bitmap (see TS 38.212, clause 6.2.7, 6.3.2, TS 38.213, clause 9.3.1, TS 38.214, clause 5.2.3). When this field is configured, UTO-UCI is enabled for the UE.

[0095] A terminal that has established an RRC connection can enter RRC_CONNECTED mode. The terminal can send an RRCSetupComplete message to the base station (step 310).

[0096] If the base station does not know the capabilities of the terminal that is currently establishing a connection, or if it wants to determine the capabilities of the terminal, it can send a message (e.g., UECapabilityEnquiry) to the terminal to inquire about the capabilities of the terminal (step 315).

[0097] The terminal may transmit a message reporting its capabilities (e.g., UECapabilityInformation) to the base station (step 320). The terminal capability reporting message may include an indicator indicating whether the terminal supports DSR-related functions.

[0098] The base station can determine whether the terminal supports DSR-related functions based on a message reporting the terminal's capabilities received from the terminal. If the terminal supports DSR-related functions, the base station can transmit or deliver DSR-related function configuration information to the terminal via an RRC message (e.g., an RRCReconfiguration message (at least one of 335 or 350)).

[0099] The base station may send a SecurityModeCommand message to the terminal to establish security with the terminal (step 325). The terminal may send a SecurityModeComplete message to the base station (step 330). Once the security setting is complete, the base station may send an RRCReconfiguration message to the terminal (step 335).

[0100] For example, the RRCReconfiguration message may include, for each Cell Group (e.g., at least one of MCG or SCG), MAC layer device configuration information (e.g., MAC-CellGroupConfig) belonging to that Cell Group.

[0101] For example, the information included in the MAC-CellGroupConfig configuration information refers to the description of the previously mentioned MAC-CellGroupConfig.

[0102] For example, for LCG-specific DSR configurations per logical channel group (LCG), refer to the description in Table 1. For example, the RRCReconfiguration message may include, for each Cell Group (e.g., at least one of MCG (Master Cell Group) or SCG (Secondary Cell Group)), configuration information of a serving cell (which may be a Serving Cell, SpCell or SCell) belonging to the corresponding Cell Group. Information included in the serving cell configuration information (e.g., ServingCellConfig) refers to the description of the aforementioned ServingCellConfig.

[0103] For example, cellDTXDRX-Config may contain various information, and for specific details, refer to the description of cellDTXDRX-Config mentioned above.

[0104] For example, BWP-Uplink configuration information may include various information, and for specific details, refer to the BWP-Uplink configuration information mentioned above.

[0105] For example, the bwp-Dedicated configuration information may include various information, and for specific details, refer to the bwp-Dedicated configuration information mentioned above.

[0106] For example, the configured grant (CG) configuration information (configuredGrantConfig) may include various information, and for specific details, refer to the CG configuration information mentioned above.

[0107] A typical data transmission process can consist of three steps: RRC connection establishment, security establishment, and DRB establishment. The base station can send an RRCReconfiguration message to the terminal to establish, add, or change new settings (step 350).

[0108] For example, the RRCReconfiguration message may include, for each Cell Group (e.g., at least one of MCG or SCG), MAC layer device configuration information (e.g., MAC-CellGroupConfig) belonging to that Cell Group.

[0109] For example, the MAC-CellGroupConfig configuration information may contain various information, see the description of the MAC layer device configuration information mentioned above.

[0110] LCG-specific DSR configurations are described in Table 1.

[0111] For example, the RRCReconfiguration message may include, for each Cell Group (e.g., at least one of the Master Cell Group (MCG) or the Secondary Cell Group (SCG)), configuration information of a serving cell (which may be a Serving Cell, SpCell or SCell) belonging to the Cell Group. For example, the serving cell configuration information (e.g., ServingCellConfig) may include various information, see the description of the serving cell configuration information mentioned above.

[0112] For example, cellDTXDRX-Config can contain various information, see the description of cellDTXDRX-Config mentioned above.

[0113] For example, the BWP-Uplink configuration information may include various information, see the description of the BWP-Uplink configuration information mentioned above.

[0114] For example, the bwp-Dedicated configuration information may contain various information, see the description of the bwp-Dedicated configuration information mentioned above.

[0115] For example, the configured grant (CG) configuration information (configuredGrantConfig) can contain various information, see the description of the CG configuration information mentioned above.

[0116] In one embodiment of the present disclosure, the terminal can perform at least one of MAC layer device configuration of each Cell Group, serving cell configuration, Uplink BWP configuration of each serving cell, and Configured Grant configuration of each Uplink BWP by an RRC message (e.g., RRCReconfiguration). The terminal can perform data transmission and reception (e.g., at least one of step 345 or step 355) by applying the configuration.

[0117] FIG. 4 is a diagram illustrating an operation of a terminal indicating a CG PUSCH TO that will not be used in the future through an unused transmission occasion (UTO)-UCI according to one embodiment of the present disclosure.

[0118] In one embodiment of the present disclosure, a terminal may multiplex UTO-UCI into a CG PUSCH transmission and transmit it to a base station. If the base station sets nrofBitsInUTO-UCI / nrof_UTO_UCI of the corresponding CG to OUTO-UCI through a specific CG-PUSCH configuration (ConfiguredGrantConfig) of the terminal, the terminal may multiplex and transmit a UTO-UCI (Bitmap) composed of OUTO-UCI bits into each CG-PUSCH transmission of the corresponding CG. Each bit of the UTO-UCI expressed by the OUTO-UCI bitmap may have a one-to-one mapping relationship with each subsequent CG-PUSCH TO in ascending order of start time.

[0119] In one embodiment of the present disclosure, in an unpaired spectrum operation (e.g., TDD), future OUTO-UCI CG-PUSCH TOs indicated by the UTO-UCI may exclude invalid CG-PUSCH TOs. For example, an invalid CG-PUSCH TO may refer to a CG-PUSCH TO that satisfies at least one of the following conditions.

[0120] - If tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedidicated is provided, it may refer to a CG PUSCH TO that conflicts with the DL (Downlink) symbol indicated by that setting.

[0121] - If ssb-PositionsInBurst is provided, it may indicate a CG PUSCH TO that conflicts with the symbol of the SSB corresponding to the SSB index indicated by that setting.

[0122] - If Cell DRX is set and activated in the Serving Cell to which the BWP to which the CG is set belongs, it can refer to a CG PUSCH TO that does not overlap with the Cell DRX Active Period (overlapping with the Cell DRX Non-Active Period).

[0123] In one embodiment of the present disclosure, bit=0 of UTO-UCI may mean that the UE can transmit a CG PUSCH in the CG PUSCH TO indicated by the bit. Bit=1 of UTO-UCI may indicate that the UE does not transmit a CG PUSCH in the CG PUSCH TO indicated by the bit. For example, if the UE sets a specific bit of UTO-UCI to 1 to indicate that it does not transmit a CG PUSCH in the CG-PUSCH TO indicated by the bit, the UE may also set the UTO-UCI bit indicating the CG-PUSCH TO to 1 in the UTO-UCI multiplexed for subsequent CG-PUSCH transmissions, and may not transmit the CG-PUSCH in the corresponding CG-PUSCH TO.

[0124] In one embodiment of the present disclosure, when determining whether to use a specific Configured Uplink Grant for PUSCH transmission, the MAC layer device of the terminal may consider the size of data in a buffer that can be transmitted via available CG Occasion and other uplink-shared channel (UL-SCH) resources. The MAC layer device may indicate the decision to the lower layer (PHY) so that the lower layer can use it for the UTO-UCI (TS 38.213, Section 9.3) operation / process / procedure performed by the lower layer.

[0125] In one embodiment of the present disclosure, when cellDTXDRX-Config is set for a specific Serving Cell, the terminal may set cell DRX for the corresponding Serving Cell if cellDTXDRXconfigType is set to drx or dtxdrx. Once set, Cell DRX may be activated or deactivated in the following cases.

[0126] - When receiving an instruction to activate or deactivate cell DRX from the lower layer (PHY) for cell DRX operation (see TS 38.213)

[0127] - When configured by upper layer (RRC): 1) If cell DRX is configured and cellDTXDRXactivationStatus is set to activated, cell DRX operation can be activated at the moment of receiving cell DRX configuration. 2) If cell DRX is configured and cellDTXDRXactivationStatus is set to deactivated, cell DRX operation can be deactivated at the moment of receiving cell DRX configuration. 3) If CellDTXDRX-Config is released, cell DRX operation can be deactivated and all configurations can be released.

[0128] In one embodiment of the present disclosure, when cell DRX is set and activated for a specific Serving Cell, the cell DRX Active Period of the Cell may mean the time period below.

[0129] - The time period during which the celldtxdrx-onDurationTimer associated with the Serving Cell is running.

[0130] For example, for a specific Serving Cell, if cell DRX is set and activated, the non-cell DRX Active Period (Non-active Period, 400) of the Cell may mean one of the time periods below.

[0131] - A time period during which the celldtxdrx-onDurationTimer associated with the Serving Cell is not running.

[0132] - Any other time period other than the Cell DRX Active Period of the Serving Cell

[0133] In one embodiment of the present disclosure, when cell DRX is activated for a specific Serving Cell, a MAC layer device of a terminal may perform at least one of the following operations during a period other than a cell DRX Active Period (Non-Active Period).

[0134] - The physical layer may not be instructed to transmit SR (scheduling request) through PUCCH resources.

[0135] - SR_COUNTER may not be incremented.

[0136] - Sr-ProhibitTimer may not start.

[0137] - All Configured Uplink Grants and associated HARQ information may not be forwarded to the HARQ entity.

[0138] - The HARQ process associated with the Configured Uplink Grant may not trigger a new transmission or retransmission.

[0139] - Periodic CSI set on PUCCH and semi-persistent CSI set on PUSCH may not be reported.

[0140] - If an emergency service is initiated by the upper layer and the cell is a SpCell (special cell), Random Access can be initiated.

[0141] If a specific Serving Cell has cell DRX activated, the MAC layer device of the UE may not forward the CG and associated HARQ information to the HARQ entity when the Cell is in a time interval other than the cell DRX Active Period, and may not trigger a new transmission or retransmission in the HARQ process associated with the CG. Therefore, if the CG PUSCH TO does not overlap, or does not fully overlap, or does not partially overlap with the cell DRX Active Period in the PHY layer, the CG PUSCH may not be transmitted to the corresponding CG PUSCH TO. Therefore, when indicating whether to transmit the CG PUSCH to a specific CG PUSCH TO through UTO-UCI, there may be several methods to consider whether it overlaps with the cell DRX active period of the corresponding Serving Cell.

[0142] - Method 1-1: When Cell DRX is set and activated for a specific Serving Cell, the UE may regard a CG PUSCH TO that does not overlap with the Cell DRX Active Period (overlapping with the Cell DRX Non-Active Period) as an invalid CG PUSCH TO. When Cell DRX is set and activated for a specific Serving Cell, the UE may regard a CG PUSCH TO that overlaps (fully and / or partially) with the Cell DRX Active Period as a valid CG PUSCH TO. Therefore, the invalid CG PUSCH TO may be excluded from the CG PUSCH TO indicated by the UTO-UCI to reduce signaling overhead. For example, the CG PUSCH TO may be regarded as an invalid CG PUSCH TO only when it fully overlaps with the Cell DRX Non-Active Period. That is, if some symbols of the CG PUSCH TO overlap with the Cell DRX Active Period, the CG PUSCH TO can be regarded as a valid CG PUSCH TO. As another example, only when the CG PUSCH TO fully overlaps with the Cell DRX Active Period (all symbols overlap with the Cell DRX Active Period), it can be regarded as a valid CG PUSCH TO, and in all other cases, it can be regarded as an invalid CG PUSCH TO. That is, if one or more symbols overlap with the Cell DRX Non-Active Period, the CG PUSCH TO can be regarded as an invalid CG PUSCH TO. Referring to FIG. 4, the UE can regard the CG PUSCH TO (420, 425) overlapping with the Cell DRX Non-Active Period as an invalid CG PUSCH TO.Therefore, when the UTO-UCI (405) transmitted in the CG PUSCH (410) indicates 011, the three bits of 011 can indicate whether to use three subsequent valid CG PUSCH TOs (415, 430, 435). That is, invalid CG PUSCH TOs (420, 425) may not be indicated by the UTO-UCI. For example, the UTO-UCI of a specific CG can only indicate the CG PUSCH TO that overlaps with the Cell DRX Active Period when Cell DRX is set and activated in the Cell to which the BWP to which the CG is set belongs. For example, the UTO-UCI of a specific CG may not indicate a CG PUSCH TO that does not overlap with the Cell DRX Active Period (overlapping with the Non-Active Period) when Cell DRX is configured and activated in the Cell to which the BWP to which the CG is configured belongs. For example, the above operation may be performed only when a parameter / field value / signaling that activates / configures / indicates the corresponding function is configured / exists in an RRC message (e.g., RRCReconfiguration) transmitted by the base station to the terminal.

[0143] - Method 1-2: When Cell DRX is set and activated for a specific Serving Cell, the UE may regard a CG PUSCH TO that does not overlap with the Cell DRX Active Period (overlapping with the Cell DRX Non-Active Period) as a valid CG PUSCH TO, and therefore, the CG PUSCH TO may also be included in the CG PUSCH TO indicated by UTO-UCI. For example, when the MAC layer device of the UE determines whether to use a specific Configured Uplink Grant for PUSCH transmission, in addition to the above-mentioned conditions, if the CG PUSCH transmission corresponding to the Configured Uplink Grant does not overlap with the Cell DRX Active Period (overlapping with the Non-Active Period), the Configured Uplink Grant may be determined not to be used (Unused). Accordingly, the MAC layer device can notify (Indication) the lower layer so that the decision can be used for the UTO-UCI (TS 38.213, Section 9.3) operation / process / procedure performed by the lower layer (PHY). Referring to FIG. 4, the CG PUSCH TO (420, 425) overlapping with the cell DRX Non-Active Period can be regarded as a valid CG PUSCH TO, but the UE can inform the base station that it does not use the CG PUSCH TO by setting the corresponding bit to 1 through the UTO-UCI. For example, the UTO-UCI transmitted by the UE can set the CG PUSCH TO that does not overlap with the Cell DRX Active Period (overlapping with the Non-Active Period) to 1 (Unused) when the Cell DRX is set and activated in the Serving Cell to which the BWP to which the CG is set belongs. For example, the MAC layer device of the terminal can notify the above settings to the lower layer (PHY).For example, when Cell DRX is set and activated in the Serving Cell to which the BWP to which the corresponding CG is set belongs, the UE implementation can determine how to report the UTO-UCI transmitted by the UE for the CG PUSCH TO that does not overlap with the Cell DRX Active Period (overlapping with the Non-Active Period). This embodiment can prevent the UE implementation from increasing its complexity due to Cell DRX when determining the UTO-UCI.

[0144] - Method 1-3: It is possible to restrict the simultaneous activation of UTO-UCI function (e.g. nrofBitsInUTO-UCI configuration) and Cell DRX function (e.g. cellDTXDRX-Config) via RRC message for a specific Serving Cell of a terminal. This embodiment can prevent the terminal implementation from increasing in complexity due to Cell DRX.

[0145] When deciding whether to use a specific Configured Uplink Grant for PUSCH transmission, the MAC layer device of the UE may consider the size of data in the transmittable buffer via the available CG Occasion and other UL-SCH resources, and whether the PUSCH transmission / Occasion of the corresponding CG overlaps with the cell DRX active / non-active period (if Cell DRX is enabled for the Cell to which the BWP with the configured CG belongs). The MAC layer device may indicate the decision to the lower layer so that it can use the UTO-UCI (TS 38.213, clause 9.3) operation / process / procedure performed by the lower layer (PHY).

[0146] The configuration for processing such UTO-UCI can be combined with various embodiments of the present disclosure.

[0147] FIG. 5 is a diagram illustrating the structure of a DSR MAC CE according to an embodiment of the present disclosure.

[0148] A terminal can report the size of delay-critical data in the buffer and the minimum remaining time for each LCG to the base station by transmitting a DSR (Delay Status Report) MAC CE. For example, the DSR MAC CE may include the following fields:

[0149] - LCGi(500, 501, 502, 503, 504, 505, 506, 507): This field indicates whether delay information (remaining time field and buffer size field) of LCG (logical channel group) i is present. An LCGi field value of 1 may mean that delay information of LCG i is reported. An LCGi field value of 0 may mean that delay information of LCG i is not reported.

[0150] - Remaining Time (510, 514): Indicates the PDCP discardTimer remaining time / value of the data with the shortest remaining time / value of the PDCP discard timer among the PDCP SDUs buffered in the corresponding LCG, based on the first symbol transmission time of the initial transmission of PUSCH including DSR MAC CE (first PUSCH transmission). For example, the PDCP SDUs buffered in the corresponding LCG may be considered only if they are buffered in the corresponding LCG and have never been transmitted via MAC PDU or have never had delay information reported via DSR. Setting the Remaining Time field value to r may mean that the range of the Remaining Time is (r, r+1] msec.

[0151] - BT(508, 512): This field may be present only if the corresponding LCG has additionalBSR-TableAllowed set. Otherwise, this field is reserved. If present, a value of 1 in this field may indicate that the corresponding Buffer Size field value was set using Table 6.1.3.1-3 of TS 38.321, and a value of 0 in this field may indicate that it was set using Table 6.1.3.1-2 of TS 38.321.

[0152] - Buffer Size (511, 515): This field can indicate the total delay-critical UL data size of the associated RLC and PDCP layer devices after the MAC PDU is created, as determined by the data size calculation method of the RLC and PDCP layer devices defined in Section 5.5 (RLC) of TS 38.322 and Section 5.6 (PDCP) of TS 38.323. The value of this field can have a byte unit, and the length of this field can be 8 bits.

[0153] The structure of the DSR MAC CE of FIG. 5 is merely an example, and the structure of the DSR MAC CE in the present invention is not necessarily limited to the structure of FIG. 5, and may be configured in various forms that include the fields of the DSR MAC CE described in FIG. 5. Such a configuration of the DSR MAC CE may be applied to various embodiments of the present disclosure in which the DSR MAC CE is used.

[0154] FIG. 6 is a diagram illustrating a CG operation in which autonomous transmission (AutonomousTx) is set, as an embodiment of the present disclosure.

[0155] In one embodiment of the present disclosure, a MAC layer device of a terminal can determine an available configured uplink grant as follows.

[0156] If a specific CG is associated with a multi-PUSCH CG, one or more of the following conditions may need to be met for the CG to be considered available for use:

[0157] - There must not have been an instruction to the lower layer yet to not use the corresponding CG for PUSCH transmission (Unused).

[0158] - The CG / CG-PUSCH TO must be a valid CG / CG-PUSCH TO (satisfying the validity condition). For example, the validity condition of the CG / CG-PUSCH TO may include one or more of the grounds for determining a valid CG / CG-PUSCH TO presented in the present disclosure. For example, if Cell DRX is set and activated in the serving cell to which the BWP where the CG is set belongs, the CG / CG-PUSCH TO can be considered valid or available only when it overlaps with the Cell DRX Active Period. For example, if Cell DRX is set and activated in a Serving Cell to which a BWP with the corresponding CG belongs, a CG / CG-PUSCH TO that does not overlap with the Cell DRX Active Period (overlapping with the Non-Active Period) may be regarded as an Invalid CG / CG-PUSCH TO or not available CG / CG-PUSCH TO. For example, an Invalid CG / CG-PUSCH TO may not be considered an Available CG. For example, only a Valid CG / CG-PUSCH TO may be regarded as an Available CG / CG-PUSCH TO.

[0159] If a particular CG is not associated with a multi-PUSCH CG, one or more of the following conditions may need to be met for the CG to be considered available for use:

[0160] - There must not have been an instruction to the lower layer yet to not use the corresponding CG for PUSCH transmission (Unused).

[0161] - The CG / CG-PUSCH TO must be a valid CG / CG-PUSCH TO (satisfying the validity condition). For example, the validity condition of the CG / CG-PUSCH TO may include one or more of the grounds for determining a valid CG / CG-PUSCH TO presented in the present disclosure. For example, if Cell DRX is set and activated in the Serving Cell to which the BWP where the CG is set belongs, the CG / CG-PUSCH TO can be considered valid or available only when it overlaps with the Cell DRX Active Period. For example, if Cell DRX is set and activated in a Serving Cell to which a BWP with the corresponding CG belongs, a CG / CG-PUSCH TO that does not overlap with the Cell DRX Active Period (overlapping with the Non-Active Period) may be regarded as an Invalid CG / CG-PUSCH TO or not available CG / CG-PUSCH TO. For example, an Invalid CG / CG-PUSCH TO may not be considered an Available CG. For example, only a Valid CG / CG-PUSCH TO may be regarded as an Available CG / CG-PUSCH TO.

[0162] In one embodiment of the present disclosure, all CG / CG-PUSCH TOs except for Valid CG / CG-PUSCH TOs may be considered as Invalid CG / CG-PUSCH TOs. In one embodiment of the present disclosure, all CG / CG-PUSCH TOs except for Invalid CG / CG-PUSCH TOs may be considered as Valid CG / CG-PUSCH TOs.

[0163] In one embodiment of the present disclosure, a MAC layer device of a terminal configured with lch-basedPrioritization may operate as follows when a lower layer (PHY) can perform a corresponding (Associated) PUSCH transmission for each Configured Uplink Grant transmitted to a HARQ entity.

[0164] 1> if this uplink grant is a configured uplink grant:

[0165] 2> if there is no overlapping PUSCH duration of another configured uplink grant which was not already de-prioritized, in the same BWP, whose priority is higher than the priority of the uplink grant; and

[0166] 2> if there is no overlapping PUSCH duration of an uplink grant addressed to CS-RNTI with NDI = 1 or C-RNTI which was not already de-prioritized, in the same BWP, whose priority is higher than or equal to the priority of the uplink grant; and

[0167] 2> if there is no overlapping PUCCH resource with an SR transmission which was not already de-prioritized and the simultaneous transmission of the SR and the uplink grant is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups, and the priority of the logical channel that triggered the SR is higher than the priority of the uplink grant:

[0168] 3> The CG may be a prioritized uplink grant.

[0169] 3> Other overlapping Uplink Grants, if present, may be considered as de-prioritized uplink grant(s).

[0170] 3> If the de-prioritized uplink grant is a CG with autonomousTx configured and the corresponding PUSCH transmission has already started:

[0171] 4> The configuredGrantTimer of the corresponding HARQ Process of the corresponding de-prioritized uplink grant can be stopped.

[0172] 4> The cg-RetransmissionTimer of the corresponding HARQ Process of the corresponding de-prioritized uplink grant can be stopped.

[0173] 3> consider the other overlapping SR transmission(s), if any, as a de-prioritized SR transmission(s), except for the SR transmission(s) whose simultaneous transmission is allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups.

[0174] 본 개시의 일 실시예로, HARQ 개체(Entity)는 각 Uplink Grant에 대해 아래와 같이 동작할 수 있다.

[0175] 1> identify the HARQ process associated with this grant, and for each identified HARQ process:

[0176] 2> if the received grant was not addressed to a Temporary C-RNTI on PDCCH, and the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this TB of this HARQ process; or

[0177] 2> if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or

[0178] 2> if the uplink grant is part of a bundle of the configured uplink grant, and may be used for initial transmission according to clause 6.1.2.3 of TS 38.214, and if no MAC PDU has been obtained for this bundle:

[0179] 3> if this uplink grant is a configured grant configured with autonomousTx; and

[0180] 3> if the previous configured uplink grant, in the BWP, for this HARQ process was not prioritized; and

[0181] 3> if a MAC PDU had already been obtained for this HARQ process; and

[0182] 3> if the uplink grant size matches with size of the obtained MAC PDU; and

[0183] 3> if none of PUSCH transmission(s) of the obtained MAC PDU has been completely performed:

[0184] 4> consider the MAC PDU has been obtained.

[0185] 3> else if the MAC entity is not configured with lch-basedPrioritization; or

[0186] 3> if this uplink grant is a prioritized uplink grant:

[0187] 4> obtain the MAC PDU to transmit from the Multiplexing and assembly entity, if any;

[0188] 3> if a MAC PDU to transmit has been obtained:

[0189] 4> if the uplink grant is not a configured grant configured with autonomousTx; or

[0190] 4> if the uplink grant is a prioritized uplink grant:

[0191] 5> deliver the MAC PDU and the uplink grant and the HARQ information of the TB to the identified HARQ process;

[0192] 5> instruct the identified HARQ process to trigger a new transmission;

[0193] 3> else (if a MAC PDU to transmit has not been obtained):

[0194] 4> flush the HARQ buffer of the identified HARQ process.

[0195] In one embodiment of the present disclosure, when enhancedSkipUplinkTxDynamic is set in the MAC layer device of the terminal, the terminal (MAC layer device of the terminal) may not generate a MAC PDU in the following cases.

[0196] 1> if the MAC entity is configured with enhancedSkipUplinkTxDynamic with value true and the grant indicated to the HARQ entity was addressed to a C-RNTI, or if the MAC entity is configured with enhancedSkipUplinkTxConfigured with value true and the grant indicated to the HARQ entity is a configured uplink grant:

[0197] 2> if there is no UCI to be multiplexed on this PUSCH transmission as specified in TS 38.213 [6]; and

[0198] 2> if there is no aperiodic CSI requested for this PUSCH transmission as specified in TS 38.212 [9]; and

[0199] 2> if the MAC PDU includes zero MAC SDUs; and

[0200] 2> if the MAC PDU includes only the periodic BSR and there is no data available for any LCG, or the MAC PDU includes only the padding BSR:

[0201] 3> not generate a MAC PDU for the HARQ entity.

[0202] In one embodiment of the present disclosure, when the MAC layer device of the terminal has skipUplinkTxDynamic set, the terminal (the MAC layer device of the terminal) may not generate a MAC PDU in the following cases.

[0203] 1> else if the MAC entity is configured with skipUplinkTxDynamic with value true and the grant indicated to the HARQ entity was addressed to a C-RNTI, or the grant indicated to the HARQ entity is a configured uplink grant:

[0204] 2> if there is no aperiodic CSI requested for this PUSCH transmission as specified in TS 38.212 [9]; and

[0205] 2> if the MAC PDU includes zero MAC SDUs; and

[0206] 2> if the MAC PDU includes only the periodic BSR and there is no data available for any LCG, or the MAC PDU includes only the padding BSR:

[0207] 3> not generate a MAC PDU for the HARQ entity.

[0208] In one embodiment of the present disclosure, the priority of an Uplink Grant can be determined as follows.

[0209] - For the MAC entity configured with lch-basedPrioritization, priority of an uplink grant is determined by the highest priority among priorities of the logical channels that are multiplexed (i.e. the MAC PDU to transmit is already stored in the HARQ buffer) or have data available that can be multiplexed (i.e. the MAC PDU to transmit is not stored in the HARQ buffer) in the MAC PDU, according to the mapping restrictions as described in clause 5.4.3.1.2 of TS 38.321. The priority of an uplink grant for which no data for logical channels is multiplexed or can be multiplexed in the MAC PDU is lower than either the priority of an uplink grant for which data for any logical channels is multiplexed or can be multiplexed in the MAC PDU or the priority of the logical channel triggering an SR.

[0210] - For the MAC entity configured with lch-basedPrioritization, if the corresponding PUSCH transmission of a configured uplink grant is cancelled by CI-RNTI as specified in clause 11.2A of TS 38.213 or cancelled by a high PHY-priority PUCCH transmission as specified in clause 9 of TS 38.213, this configured uplink grant is considered as a de-prioritized uplink grant. If this de-prioritized uplink grant is configured with autonomousTx, the configuredGrantTimer for the corresponding HARQ process of this de-prioritized uplink grant shall be stopped if it is running. If this de-prioritized uplink grant is configured with autonomousTx, the cg-RetransmissionTimer for the corresponding HARQ process of this de-prioritized uplink grant shall be stopped if it is running.

[0211] 도 6은 본 개시의 일 실시예에 따른, AutonomousTx가 설정된 CG의 동작을 도시한 도면이다.

[0212] Referring to FIG. 6, a terminal may perform PUSCH transmission to a specific CG (600). AutonomousTx may be configured for the CG. The CG may be canceled by a CI-RNTI (radio network temporary identifier) ​​or a high PHY-priority PUCCH transmission. After the PUSCH transmission of the CG has already started, at time 620, it may overlap with a PUSCH transmission of another CG with a higher priority belonging to the same BWP, a Dynamic Grant (uplink grant addressed to CS-RNTI with NDI = 1 or C-RNTI) PUSCH transmission, or a PUCCH transmission of SR, and thus may not be completely transmitted. The base station may not completely receive the CG PUSCH transmission (600). In addition, the base station may not detect the presence of the CG PUSCH transmission (600). The base station may not recognize that the corresponding CG PUSCH transmission (600) has started. The terminal has already obtained the MAC PDU for the CG PUSCH transmission (600), and the corresponding MAC PDU may include the DSR MAC CE (610). At this time, the corresponding DSR MAC CE (610) may set the value of the Remaining Time field based on the time point (T1) at which the first symbol of the PUSCH transmission (600) including the DSR MAC CE is transmitted. At this time, the expiration time of the discard timer indicated by the Remaining Time field may be T3, which is the value indicated by the Remaining Time added to the time point T1.

[0213] After the above CG PUSCH (600) transmission fails, the terminal can retransmit the MAC PDU acquired in the CG PUSCH transmission (600) through the CG PUSCH transmission (630) in the next CG PUSCH TO corresponding to the HARQ Process ID corresponding to the CG PUSCH transmission. At this time, the DSR MAC CE (635) included in the CG PUSCH transmission (630) may have the same field value as the DSR MAC CE (610) transmitted in the CG PUSCH transmission (600). That is, the Remaining Time field value of the DSR MAC CE (635) may be a value that sets T1 as the reference time. After the base station receives the DSR MAC CE (635), the expiration time of the discard timer indicated by the Remaining Time field of the corresponding MAC CE can be interpreted as T4, which is the time indicated by the Remaining Time field plus the reference time T2, based on the first symbol transmission time (T2) of the CG PUSCH transmission (630). In other words, if the remaining time of delay-critical data is misinterpreted, uplink resources may be wasted, or uplink scheduling may not be performed at an appropriate time.

[0214] The following methods may exist as a way to solve the above-mentioned problem.

[0215] - Method 2-1: The base station can specify the operation of the terminal (e.g., Multiplexing of MAC CE operation) so that the DSR MAC CE cannot be included in the MAC PDU transmitted through the CG for which AutonomousTx is configured / the PUSCH resource of the corresponding CG / the MAC PDU transmitted through the PUSCH resource. After the PUSCH transmission of the CG for which AutonomousTx is configured starts, if it is de-prioritized in the aforementioned case, the transmission may not be completely performed. At this time, if a MAC PDU including the DSR MAC CE is being transmitted, there is a possibility that the MAC PDU may be retransmitted in the next transmission of the corresponding HARQ Process, so there is a possibility that the base station may not be sure of the point in time of the remaining time of the DSR MAC CE. If the DSR MAC CE is restricted from being included in the MAC PDU transmitted through the PUSCH transmission of the CG for which AutonomousTx is configured, the above problem can be prevented from occurring.

[0216] - Method 2-2: The base station may include an indicator in the configuration information of an RRC message (e.g., ConfiguredGrantConfig of RRCReconfiguration) that instructs the UE to enable or disable the inclusion of DSR MAC CE in MAC PDUs transmitted through a specific CG / PUSCH resource of the CG / PUSCH resource of the CG. When the UE configures a MAC PDU transmitted through the CG / PUSCH resource of the CG / PUSCH resource of the CG / PUSCH resource of the CG instructed to enable or disable the inclusion of DSR MAC CE in the MAC PDU, the UE may include the DSR MAC CE in the MAC PDU if there is a pending DSR. Alternatively, when the terminal configures a MAC PDU transmitted through a CG / PUSCH resource of the corresponding CG / PUSCH resource that has been instructed not to include a DSR MAC CE through the above-mentioned indicator, the terminal may not include a DSR MAC CE in the MAC PDU even if a pending DSR exists.

[0217] - Method 2-3: When the base station sets the CG settings (e.g., ConfiguredGrantConfig) to the terminal via an RRC message, if the MAC layer device of the Cell Group to which a specific CG belongs includes (at least one) DSR-related settings (e.g., LCG-DSR-Config) or if DSR is set for the Cell Group / MAC entity, it can be specified that AutonomousTx cannot be set for the CG.

[0218] - Method 2-4: When the HARQ entity of the terminal transmits a CG PUSCH with AutonomousTx set, if there is an existing (already created) MAC PDU that was not deprioritized in the previous CG PUSCH transmission (same HARQ Process) and the MAC PDU includes a DSR MAC CE, the terminal may create a new MAC PDU and transmit it. Alternatively, only if the already created MAC PDU does not include a DSR MAC CE, the already created MAC PDU may be transmitted without creating a new MAC PDU. For example, if the remaining time indicated by the Remaining Time field of the DSR MAC CE included in the already created MAC PDU is still valid (for example, if the discard Timer corresponding to the Remaining Time has not expired), the already created MAC PDU may be transmitted without creating a new MAC PDU. For example, a HARQ entity of a terminal can operate as follows.

[0219] 1> identify the HARQ process associated with each grant, and for each identified HARQ process:

[0220] 2> if the received grant was not addressed to a Temporary C-RNTI on PDCCH, and the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this TB of this HARQ process; or

[0221] 2> if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or

[0222] 2> if the uplink grant is part of a bundle of the configured uplink grant, and may be used for initial transmission according to clause 6.1.2.3 of TS 38.214, and if no MAC PDU has been obtained for this bundle:

[0223] 3> if this uplink grant is a configured grant configured with autonomousTx; and

[0224] 3> if the previous configured uplink grant, in the BWP, for this HARQ process was not prioritized; and

[0225] 3> if a MAC PDU had already been obtained for this HARQ process; and

[0226] 3> if the uplink grant size matches with size of the obtained MAC PDU; and

[0227] 3> if none of PUSCH transmission(s) of the obtained MAC PDU has been completely performed; and

[0228] 3> if the obtained MAC PDU does not include DSR MAC CE:

[0229] 4> consider the MAC PDU has been obtained.

[0230] - Method 2-5: When transmitting a CG PUSCH with AutonomousTx set, if there is an already created MAC PDU that was not prioritized in the previous CG (same HARQ Process) PUSCH transmission and the MAC PDU includes DSR, when transmitting the already created MAC PDU, the UE can modify the DSR MAC CE of the MAC PDU based on the current situation and then transmit it. For example, the MAC entity / HARQ entity of the UE can operate as follows.

[0231] 1> identify the HARQ process associated with each grant, and for each identified HARQ process:

[0232] 2> if the received grant was not addressed to a Temporary C-RNTI on PDCCH, and the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this TB of this HARQ process; or

[0233] 2> if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or

[0234] 2> if the uplink grant is part of a bundle of the configured uplink grant, and may be used for initial transmission according to clause 6.1.2.3 of TS 38.214, and if no MAC PDU has been obtained for this bundle:

[0235] 3> if this uplink grant is a configured grant configured with autonomousTx; and

[0236] 3> if the previous configured uplink grant, in the BWP, for this HARQ process was not prioritized; and

[0237] 3> if a MAC PDU had already been obtained for this HARQ process; and

[0238] 3> if the uplink grant size matches with size of the obtained MAC PDU; and

[0239] 3> if none of PUSCH transmission(s) of the obtained MAC PDU has been completely performed:

[0240] 4> consider the MAC PDU has been obtained. If a DSR MAC CE is already included in the MAC PDU, the content of the DSR can be modified according to this uplink grant / current delay status / current buffer status. Or, it is up to UE implementation how to handle the DSR content.

[0241] - Method 2-6: When transmitting a CG PUSCH with AutonomousTx set, if there is a MAC PDU that was already created and was not prioritized in the previous CG (same HARQ Process) PUSCH transmission, and if the MAC PDU includes DSR, the UE can remove / exclude the DSR MAC CE from the MAC PDU when transmitting the already created MAC PDU. For example, the MAC entity / HARQ entity of the UE can operate as follows.

[0242] 1> identify the HARQ process associated with each grant, and for each identified HARQ process:

[0243] 2> if the received grant was not addressed to a Temporary C-RNTI on PDCCH, and the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this TB of this HARQ process; or

[0244] 2> if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or

[0245] 2> if the uplink grant is part of a bundle of the configured uplink grant, and may be used for initial transmission according to clause 6.1.2.3 of TS 38.214, and if no MAC PDU has been obtained for this bundle:

[0246] 3> if this uplink grant is a configured grant configured with autonomousTx; and

[0247] 3> if the previous configured uplink grant, in the BWP, for this HARQ process was not prioritized; and

[0248] 3> if a MAC PDU had already been obtained for this HARQ process; and

[0249] 3> if the uplink grant size matches with size of the obtained MAC PDU; and

[0250] 3> if none of PUSCH transmission(s) of the obtained MAC PDU has been completely performed:

[0251] 4> consider the MAC PDU has been obtained. If a DSR MAC CE is already included in the MAC PDU, the DSR MAC CE is excluded / removed / deleted / discarded from the MAC PDU. Or, it is up to UE implementation whether to exclude / remove / delete / discard the DSR MAC CE.

[0252] - Method 2-7: The MAC layer device of a terminal for which lch-basedPrioritization is set may operate so that, if a DSR MAC CE is included in a PUSCH of a CG for which AutonomousTX is set (or regardless of whether AutonomousTx is set) and which has already started or is scheduled to start transmission, the corresponding CG PUSCH transmission is always prioritized. Alternatively, if a DSR MAC CE is included in a PUSCH transmission of a CG for which AutonomousTX is set (or regardless of whether AutonomousTx is set) and which has already started or is scheduled to start transmission, the corresponding CG PUSCH transmission may operate so that it is not de-prioritized by an SR transmitted through another CG / DG (Dynamic Grant) / PUCCH. For example, if a DSR MAC CE is included in a MAC PDU transmitted (already created) or scheduled to be transmitted (created) through a CG for which AutonomousTx is configured (or regardless of whether AutonomousTx is configured), the priority of the CG may be determined to be higher than an Uplink Grant (Configured Grant, Dynamic Grant) without another DSR MAC CE or an SR (Scheduling Request) transmitted through PUCCH. For example, the Priority-related operation may be performed only when a CG PUSCH transmission including the DSR MAC CE has already started. In one embodiment of the present disclosure, a MAC layer device of a terminal for which lch-basedPrioritization is configured may operate as follows for each CG delivered to a HARQ entity when a lower layer (PHY) can perform the corresponding (Associated) PUSCH transmission.

[0253] 1> if this uplink grant is a configured uplink grant:

[0254] 2> if there is no overlapping PUSCH duration of another configured uplink grant which was not already de-prioritized, in the same BWP, whose priority is higher than the priority of the uplink grant or the other configured uplink grant is configured with autonomousTx and / or includes DSR MAC CE and / or already started the PUSCH transmission; and

[0255] 2> if there is no overlapping PUSCH duration of an uplink grant addressed to CS-RNTI with NDI = 1 or C-RNTI which was not already de-prioritized, in the same BWP, whose priority is higher than or equal to the priority of the uplink grant; and

[0256] 2> if there is no overlapping PUCCH resource with an SR transmission which was not already de-prioritized and the simultaneous transmission of the SR and the uplink grant is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups, and the priority of the logical channel that triggered the SR is higher than the priority of the uplink grant:

[0257] 3> The CG can be prioritized as an uplink grant.

[0258] 3> Other overlapping Uplink Grants, if any, may be considered as de-prioritized uplink grant(s).

[0259] 3> If the de-prioritized uplink grant is a CG with autonomousTx configured and the corresponding PUSCH transmission has already started:

[0260] 4> The configuredGrantTimer of the corresponding HARQ Process of the corresponding de-prioritized uplink grant can be stopped.

[0261] 4> The cg-RetransmissionTimer of the corresponding HARQ Process of the corresponding de-prioritized uplink grant can be stopped.

[0262] 3> consider the other overlapping SR transmission(s), if any, as a de-prioritized SR transmission(s), except for the SR transmission(s) whose simultaneous transmission is allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups.

[0263] - Method 2-8: A new MAC CE (e.g., Reference Time MAC CE) indicating the reference time of the Remaining Time field of DSR can be included in the same MAC PDU as the DSR, or a new Reference Time field can be added to the DSR MAC CE (a field / bit indicating the presence of the field can be added), so that the terminal can explicitly indicate the reference time used when setting the Remaining Time field when reporting the DSR to the base station. For example, the Reference Time MAC CE or Reference Time field value can indicate the reference time to be indicated as one or more combinations of absolute time (e.g., part or all of a UTC time field) and / or System Frame Number and / or Frame Number and / or Subframe Number and / or Slot Number and / or Symbol Number. For example, when the UE constructs a MAC PDU to be transmitted / to be transmitted via PUSCH transmission of a CG with AutonomousTx configured (or regardless of whether AutonomousTx is configured), if a DSR MAC CE is included, the UE may also include a Reference Time MAC CE in the MAC PDU. For example, when the UE constructs a MAC PDU to be transmitted / to be transmitted via PUSCH transmission of a CG with AutonomousTx configured (or regardless of whether AutonomousTx is configured), if a DSR MAC CE is included, the UE may also include a Reference Time field in the DSR MAC CE. For example, the MAC entity / HARQ entity of the UE may operate as follows.

[0264] 1> identify the HARQ process associated with each grant, and for each identified HARQ process:

[0265] 2> if the received grant was not addressed to a Temporary C-RNTI on PDCCH, and the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this TB of this HARQ process; or

[0266] 2> if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or

[0267] 2> if the uplink grant is part of a bundle of the configured uplink grant, and may be used for initial transmission according to clause 6.1.2.3 of TS 38.214, and if no MAC PDU has been obtained for this bundle:

[0268] 3> if this uplink grant is a configured grant configured with autonomousTx; and

[0269] 3> if the previous configured uplink grant, in the BWP, for this HARQ process was not prioritized; and

[0270] 3> if a MAC PDU had already been obtained for this HARQ process; and

[0271] 3> if the uplink grant size matches with size of the obtained MAC PDU; and

[0272] 3> if none of PUSCH transmission(s) of the obtained MAC PDU has been completely performed:

[0273] 4> consider the MAC PDU has been obtained. If a DSR MAC CE is included in the MAC PDU, a reference time MAC CE is added to the MAC PDU or a reference time field if added to the DSR MAC CE of the MAC PDU. Or, it is up to UE implementation whether to add reference time MAC CE or reference time field.

[0274] FIG. 7 is a diagram illustrating operations of a terminal and a base station related to a CG operation in which AutonomousTx is set according to one embodiment of the present disclosure.

[0275] Referring to FIG. 7, at step 710, the terminal may receive CG PUSCH configuration information from the base station. The CG PUSCH configuration information may include the information described in the aforementioned embodiment. Additionally, when performing the embodiment of FIG. 6, the information may include information configured by the base station to the terminal.

[0276] In operation 720, the terminal may decide to transmit the first CG-based PUSCH. The terminal may configure a MAC PDU and transmit it to a lower layer.

[0277] In operation 730, the first CG-based PUSCH transmission may be canceled. The first CG-based PUSCH transmission may be canceled due to CI-RNTI or high PHY-priority PUCCH transmission. Even if the first CG-based PUSCH transmission is canceled, the MAC PDU generated for the first CG-based PUSCH transmission is stored in the terminal's buffer.

[0278] Thereafter, in the next CG PUSCH TO (second CG) corresponding to the HARQ process ID corresponding to the first CG PUSCH transmission, the terminal may decide to transmit (retransmit) the MAC PDU stored in the buffer according to the cancellation of the first CG PUSCH transmission, and may configure the MAC PDU (operation 740). At this time, as described in the embodiment of FIG. 6, the MAC PDU may be reconfigured according to various methods. Through this, the problem of the base station misinterpreting the remaining time, resulting in wasted uplink resources or reduced uplink scheduling efficiency, can be solved.

[0279] In operation 750, the terminal can perform a second CG-based PUSCH transmission. The terminal can transmit the MAC PDU acquired in operation 740 to the base station.

[0280] In operation 760, the base station can process the MAC PDU obtained from the terminal. As described in FIG. 6, the MAC PDU corresponds to a MAC PDU generated using an improved method, thereby preventing the base station from misinterpreting the remaining time or reducing the efficiency of uplink scheduling.

[0281] For specific operations not described in Fig. 7, refer to the description of the corresponding configuration in the description of Fig. 6.

[0282] FIG. 8 is a diagram illustrating enhancedSkipUplinkDynamic / skipUplinkTxDynamic operation of a terminal according to one embodiment of the present disclosure.

[0283] Referring to Figure 8, the following situations may occur between the base station and the terminal.

[0284] - The base station allocates UL Dynamic Grant (addressed to C-RNTI) to the terminal for initial transmission (800).

[0285] - The MAC layer device of the terminal does not generate a MAC PDU to be transmitted to the UL Grant allocated by the base station when the enhancedSkipUplinkDynamic-r16 / skipUplinkTxDynamic is set (810).

[0286] - The base station cannot distinguish whether the MAC PDU to be transmitted to the UL Grant (800) allocated by the terminal was not generated or whether the MAC PDU was generated but PUSCH transmission failed (815).

[0287] - The base station allocates UL DG (addressed to C-RNTI with NDI not toggled) for retransmission in case of PUSCH transmission failure (820).

[0288] - The terminal generates a new MAC PDU and transmits it because the HARQ Buffer of the HARQ Process of the UL Grant (820) allocated by the base station is empty. The MAC PDU includes a DSR MAC CE (830). The Remaining Time field of the DSR MAC CE is set based on the first symbol transmission time (T2) of the PUSCH transmission (830).

[0289] - The base station may determine that the received MAC PDU is a retransmission, and may incorrectly determine the point in time based on the Remaining Time field of the DSR MAC CE included in the MAC PDU as the first symbol transmission time (T1) of the PUSCH of the UL Grant allocated for the initial transmission.

[0290] In one embodiment of the present disclosure, the terminal may operate as follows.

[0291] - If the base station allocates a UL Dynamic Grant (addressed to C-RNTI) to the terminal for retransmission (NDI not toggled), the terminal may not include the DSR MAC CE in the MAC PDU when the HARQ Buffer of the HARQ Process of the corresponding UL Grant is empty and a new MAC PDU is configured (even if a pending DSR exists). Alternatively, the base station may include an indicator in the DCI indicating whether or not the MAC PDU transmitted through the corresponding UL Grant can include the DSR MAC CE. In this case, the terminal may include the DSR MAC CE in the MAC PDU transmission based on the UL Grant that can include the DSR MAC CE as indicated by the indicator in the corresponding DCI, or may exclude the DSR MAC CE in the MAC PDU transmission based on the UL Grant that cannot include the DSR MAC CE. Alternatively, the terminal may transmit an additional Reference Time MAC CE indicating the reference time used when setting the Remaining Time of DSR or include the Reference Time field in the DSR MAC CE. Alternatively, when the terminal configures the MAC PDU and includes the DSR MAC CE, when setting the Remaining Time field (if the UL Grant (CG or DG) is a UL Grant resource for retransmission (NDI not toggled)), it may always set it based on the first symbol transmission time of the PUSCH of the UL Grant most recently allocated for the initial transmission (NDI toggled) of the corresponding HARQ Process.Referring to FIG. 8, the Remaining Time field of the DSR MAC CE transmitted for the first time through the PUSCH (830) may be set based on T1 (the first symbol transmission time of the PUSCH resource allocated for the initial transmission of the most recent HARQ Process) rather than T2.

[0292] For example, a HARQ entity of a terminal can operate as follows.

[0293] - For each uplink grant, the HARQ entity shall:

[0294] 1> identify the HARQ process associated with this grant, and for each identified HARQ process:

[0295] 2> if the received grant was not addressed to a Temporary C-RNTI on PDCCH, and the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this TB of this HARQ process; or

[0296] 3> else if the MAC entity is not configured with lch-basedPrioritization; or

[0297] 3> if this uplink grant is a prioritized uplink grant:

[0298] 4> obtain the MAC PDU to transmit from the Multiplexing and assembly entity, if any;

[0299] 2> if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty:

[0300] 3> Option 1: ignore the uplink grant (MAC PDU를 생성하지 않음으로써 DSR MAC CE 관련 이슈를 차단)

[0301] 3> Option 2: obtain the MAC PDU to transmit from the Multiplexing and assembly entity, if any; if the MAC PDU includes DSR MAC CE, ignore the uplink grant or exclude the DSR MAC CE from the MAC PDU multiplexing.(MAC PDU 새로 생성 시, DSR MAC CE 포함하지 않도록 제한)

[0302] 3> Option 3: obtain the MAC PDU to transmit from the Multiplexing and assembly entity, if any; if the obtained MAC PDU includes DSR MAC CE or there is at least one pending DSR, add reference time MAC CE to the MAC PDU or add reference time field to the DSR MAC CE during the MAC PDU multiplexing.

[0303] 3> Option 4: obtain the MAC PDU to transmit from the Multiplexing and assembly entity, if any; if the obtained MAC PDU includes DSR MAC CE or there is at least one pending DSR, the remaining time field of the DSR MAC CE is set based on the time of the first symbol of the most recent PUSCH transmission allocated by new / initial transmission of the associated HARQ process / HARQ process ID.

[0304] FIG. 9 is a diagram illustrating operations of a terminal and a base station related to enhancedSkipUplinkDynamic / skipUplinkTxDynamic operations according to one embodiment of the present disclosure.

[0305] Referring to FIG. 9, at step 900, the terminal may receive a first UL dynamic grant from the base station. This is a grant allocated for the terminal's initial transmission and may be addressed by a C-RNTI.

[0306] If enhancedSkipUplinkDynamic-r16 / skipUplinkTxDynamic is set in the terminal, the terminal (MAC layer device of the terminal) does not generate a MAC PDU to be transmitted based on the first UL dynamic grant (step 910).

[0307] At step 920, the base station can transmit a second UL dynamic grant to the terminal. Since the base station cannot determine at step 910 whether the terminal did not generate a MAC PDU or whether there was a transmission failure, the base station can allocate the second UL dynamic grant to the terminal in case of a transmission failure.

[0308] At step 930, the terminal can generate a MAC PDU based on the second UL dynamic grant. At this time, to solve the problem raised in FIG. 8, the MAC PDU proposed in FIG. 8 can be generated.

[0309] At step 940, the terminal can transmit the generated MAC PDU to the base station.

[0310] In operation 950, the base station can process the received MAC PDU. The MAC PDU is processed according to the method proposed in the embodiment of the present disclosure, which can resolve problems such as the base station misinterpreting the remain time field, misunderstanding the reference time, or poor uplink scheduling efficiency.

[0311] In one embodiment of the present disclosure, if at least one SR (Scheduling Request) is pending, the MAC layer device of the terminal may operate as follows for each pending SR.

[0312] 1> if the MAC entity has no valid PUCCH resource configured for the pending SR; and

[0313] 1> if there is no ongoing LTM cell switch; and

[0314] 1> if rach-lessHO is not configured:

[0315] 2> initiate a Random Access procedure on the SpCell and cancel the pending SR.

[0316] 1> else, for the SR configuration corresponding to the pending SR:

[0317] 2> when the MAC entity has an SR transmission occasion on the valid PUCCH resource for SR configured; and

[0318] 2> if sr-ProhibitTimer is not running at the time of the SR transmission occasion; and

[0319] 2> if the PUCCH resource for the SR transmission occasion does not overlap with a measurement gap:

[0320] 3> if the PUCCH resource for the SR transmission occasion overlaps with neither a UL-SCH resource not provided by configured uplink grant considered not available for use, whose simultaneous transmission with the SR is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups nor an SL-SCH resource; or

[0321] 4> consider the SR transmission as a prioritized SR transmission.

[0322] In one embodiment of the present disclosure, the criteria for determining whether an uplink grant is available for use by a MAC layer device of a terminal is configured may be as follows.

[0323] 1> if the configured uplink grant is associated with a multi-PUSCH configured grant:

[0324] 2> if configured uplink grant has not been indicated to the lower layers as to be unused for PUSCH transmission; and

[0325] 2> if the configured uplink grant meets the validity conditions specified in the clause 6.1 in TS 38.214:

[0326] 3> consider the configured uplink grant available for use;

[0327] 1> else if the configured uplink grant has not been indicated to lower layers as to be unused for PUSCH transmission:

[0328] 2> consider the configured uplink grant available for use.

[0329] In one embodiment of the present disclosure, the criteria by which a MAC layer device of a terminal determines that a configured uplink grant is not available for use may be as follows.

[0330] 1> if the configured uplink grant is associated with a multi-PUSCH configured grant:

[0331] 2> if configured uplink grant has been indicated to the lower layers as to be unused for PUSCH transmission; or

[0332] 2> if the configured uplink grant does not meet the validity conditions specified in the clause 6.1 in TS 38.214:

[0333] 3> consider the configured uplink grant not available for use;

[0334] 1> else if the configured uplink grant has been indicated to lower layers as to be unused for PUSCH transmission:

[0335] 2> consider the configured uplink grant not available for use.

[0336] In one embodiment of the present disclosure, if at least one SR (Scheduling Request) is pending, the MAC layer device of the terminal may operate as follows for each pending SR.

[0337] 1> if the MAC entity has no valid PUCCH resource configured for the pending SR; and

[0338] 1> if there is no ongoing LTM cell switch; and

[0339] 1> if rach-lessHO is not configured:

[0340] 2> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel the pending SR.

[0341] 1> else, for the SR configuration corresponding to the pending SR:

[0342] 2> when the MAC entity has an SR transmission occasion on the valid PUCCH resource for SR configured; and

[0343] 2> if sr-ProhibitTimer is not running at the time of the SR transmission occasion; and

[0344] 2> if the PUCCH resource for the SR transmission occasion does not overlap with a measurement gap:

[0345] 3> if the PUCCH resource for the SR transmission occasion overlaps with neither a UL-SCH resource provided by available uplink grant for use whose simultaneous transmission with the SR is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups nor an SL-SCH resource; or

[0346] 3> if the MAC entity is able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource; or

[0347] 3> if the MAC entity is configured with lch-basedPrioritization, and the PUCCH resource for the SR transmission occasion does not overlap with the PUSCH duration of an uplink grant received in a Random Access Response or with the PUSCH duration of an uplink grant addressed to Temporary C-RNTI or with the PUSCH duration of a MSGA payload, and the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5 overlaps with any other UL-SCH resource(s), and the physical layer can signal the SR on one valid PUCCH resource for SR, and the priority of the logical channel that triggered SR is higher than the priority of the uplink grant(s) for any UL-SCH resource(s) where the uplink grant was not already de-prioritized and its simultaneous transmission with the SR is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCHgroups, and the priority of the uplink grant is determined as specified in clause 5.4.1; or.

[0348] 3> if both sl-PrioritizationThres and ul-PrioritizationThres are configured and the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5 overlaps with any UL-SCH resource(s) carrying a MAC PDU, and the value of the priority of the triggered SR determined as specified in clause 5.22.1.5 is lower than sl-PrioritizationThres and the value of the highest priority of the logical channel(s) in the MAC PDU is higher than or equal to ul-PrioritizationThres and any MAC CE prioritized as described in clause 5.4.3.1.3 is not included in the MAC PDU and the MAC PDU is not prioritized by upper layer according to TS 23.287

[0019] ; or

[0349] 3> if an SL-SCH resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and either transmission on the SL-SCH resource is not prioritized as described in clause 5.22.1.3.1a or the priority value of the logical channel that triggered SR is lower than ul-PrioritizationThres, if configured; or

[0350] 3> if an SL-SCH resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and the priority of the triggered SR determined as specified in clause 5.22.1.5 is higher than the priority of the MAC PDU determined as specified in clause 5.22.1.3.1a for the SL-SCH resource; or

[0351] 3> if an SL-PRS resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and either transmission on the SL-PRS resource is not prioritized as described in clause 5.22.1.3.1a or 5.22.1.3.1b or the priority value of the logical channel that triggered SR is lower than ul-PrioritizationThres, if configured; or

[0352] 3> if an SL-PRS resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and the priority of the triggered SR determined as specified in clause 5.22.1.5 is higher than the priority of the MAC PDU and SL-PRS, if available, determined as specified in clause 5.22.1.3.1a for the SL-PRS resource:

[0353] 4> consider the SR transmission as a prioritized SR transmission.

[0354] 4> consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s), except for the overlapping uplink grant(s) whose simultaneous transmission is allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups;

[0355] 4> if the de-prioritized uplink grant(s) is a configured uplink grant configured with autonomousTx whose PUSCH has already started:

[0356] 5> stop the configuredGrantTimer for the corresponding HARQ process of the de-prioritized uplink grant(s);

[0357] 5> stop the cg-RetransmissionTimer for the corresponding HARQ process of the de-prioritized uplink grant(s).

[0358] 4> if SR_COUNTER < sr-TransMax:

[0359] 5> instruct the physical layer to signal the SR on one valid PUCCH resource for SR;

[0360] 5> if LBT failure indication is not received from lower layers:

[0361] 6> increment SR_COUNTER by 1;

[0362] 6> start the sr-ProhibitTimer.

[0363] 5> else if lbt-FailureRecoveryConfig is not configured:

[0364] 6> increment SR_COUNTER by 1.

[0365] 4> else:

[0366] 5> notify RRC to release PUCCH for all Serving Cells;

[0367] 5> notify RRC to release SRS for all Serving Cells;

[0368] 5> clear any configured downlink assignments and uplink grants;

[0369] 5> clear any PUSCH resources for semi-persistent CSI reporting;

[0370] 5> if rach-lessHO is not configured:

[0371] 6> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel all pending SRs.

[0372] 3> else:

[0373] 4> consider the SR transmission as a de-prioritized SR transmission.

[0374] In one embodiment of the present disclosure, if at least one SR (Scheduling Request) is pending, the MAC layer device of the terminal may operate as follows for each pending SR.

[0375] 1> if the MAC entity has no valid PUCCH resource configured for the pending SR; and

[0376] 1> if there is no ongoing LTM cell switch; and

[0377] 1> if rach-lessHO is not configured:

[0378] 2> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel the pending SR.

[0379] 1> else, for the SR configuration corresponding to the pending SR:

[0380] 2> when the MAC entity has an SR transmission occasion on the valid PUCCH resource for SR configured; and

[0381] 2> if sr-ProhibitTimer is not running at the time of the SR transmission occasion; and

[0382] 2> if the PUCCH resource for the SR transmission occasion does not overlap with a measurement gap:

[0383] 3> if the PUCCH resource for the SR transmission occasion overlaps with neither a UL-SCH resource provided by uplink grant available for use whose simultaneous transmission with the SR is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups nor an SL-SCH resource; or

[0384] 3> if the MAC entity is able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource; or

[0385] 3> if the MAC entity is configured with lch-basedPrioritization, and the PUCCH resource for the SR transmission occasion does not overlap with the PUSCH duration of an uplink grant received in a Random Access Response or with the PUSCH duration of an uplink grant addressed to Temporary C-RNTI or with the PUSCH duration of a MSGA payload, and the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5 overlaps with any other UL-SCH resource(s), and the physical layer can signal the SR on one valid PUCCH resource for SR, and the priority of the logical channel that triggered SR is higher than the priority of the uplink grant(s) for any UL-SCH resource(s) where the uplink grant was not already de-prioritized and its simultaneous transmission with the SR is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCHgroups, and the priority of the uplink grant is determined as specified in clause 5.4.1; or.

[0386] 3> if both sl-PrioritizationThres and ul-PrioritizationThres are configured and the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5 overlaps with any UL-SCH resource(s) carrying a MAC PDU, and the value of the priority of the triggered SR determined as specified in clause 5.22.1.5 is lower than sl-PrioritizationThres and the value of the highest priority of the logical channel(s) in the MAC PDU is higher than or equal to ul-PrioritizationThres and any MAC CE prioritized as described in clause 5.4.3.1.3 is not included in the MAC PDU and the MAC PDU is not prioritized by upper layer according to TS 23.287

[0019] ; or

[0387] 3> if an SL-SCH resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and either transmission on the SL-SCH resource is not prioritized as described in clause 5.22.1.3.1a or the priority value of the logical channel that triggered SR is lower than ul-PrioritizationThres, if configured; or

[0388] 3> if an SL-SCH resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and the priority of the triggered SR determined as specified in clause 5.22.1.5 is higher than the priority of the MAC PDU determined as specified in clause 5.22.1.3.1a for the SL-SCH resource; or

[0389] 3> if an SL-PRS resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and either transmission on the SL-PRS resource is not prioritized as described in clause 5.22.1.3.1a or 5.22.1.3.1b or the priority value of the logical channel that triggered SR is lower than ul-PrioritizationThres, if configured; or

[0390] 3> if an SL-PRS resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and the priority of the triggered SR determined as specified in clause 5.22.1.5 is higher than the priority of the MAC PDU and SL-PRS, if available, determined as specified in clause 5.22.1.3.1a for the SL-PRS resource:

[0391] 4> consider the SR transmission as a prioritized SR transmission.

[0392] 4> consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s), except for the overlapping uplink grant(s) whose simultaneous transmission is allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups;

[0393] 4> if the de-prioritized uplink grant(s) is a configured uplink grant configured with autonomousTx whose PUSCH has already started:

[0394] 5> stop the configuredGrantTimer for the corresponding HARQ process of the de-prioritized uplink grant(s);

[0395] 5> stop the cg-RetransmissionTimer for the corresponding HARQ process of the de-prioritized uplink grant(s).

[0396] 4> if SR_COUNTER < sr-TransMax:

[0397] 5> instruct the physical layer to signal the SR on one valid PUCCH resource for SR;

[0398] 5> if LBT failure indication is not received from lower layers:

[0399] 6> increment SR_COUNTER by 1;

[0400] 6> start the sr-ProhibitTimer.

[0401] 5> else if lbt-FailureRecoveryConfig is not configured:

[0402] 6> increment SR_COUNTER by 1.

[0403] 4> else:

[0404] 5> notify RRC to release PUCCH for all Serving Cells;

[0405] 5> notify RRC to release SRS for all Serving Cells;

[0406] 5> clear any configured downlink assignments and uplink grants;

[0407] 5> clear any PUSCH resources for semi-persistent CSI reporting;

[0408] 5> if rach-lessHO is not configured:

[0409] 6> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel all pending SRs.

[0410] 3> else:

[0411] 4> consider the SR transmission as a de-prioritized SR transmission.

[0412] In one embodiment of the present disclosure, if at least one SR (Scheduling Request) is pending, the MAC layer device of the terminal may operate as follows for each pending SR.

[0413] 1> if the MAC entity has no valid PUCCH resource configured for the pending SR; and

[0414] 1> if there is no ongoing LTM cell switch; and

[0415] 1> if rach-lessHO is not configured:

[0416] 2> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel the pending SR.

[0417] 1> else, for the SR configuration corresponding to the pending SR:

[0418] 2> when the MAC entity has an SR transmission occasion on the valid PUCCH resource for SR configured; and

[0419] 2> if sr-ProhibitTimer is not running at the time of the SR transmission occasion; and

[0420] 2> if the PUCCH resource for the SR transmission occasion does not overlap with a measurement gap:

[0421] 3> if the PUCCH resource for the SR transmission occasion overlaps with neither an available UL-SCH resource provided by uplink grant available for use whose simultaneous transmission with the SR is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups nor an SL-SCH resource; or

[0422] 3> if the MAC entity is able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource; or

[0423] 3> if the MAC entity is configured with lch-basedPrioritization, and the PUCCH resource for the SR transmission occasion does not overlap with the PUSCH duration of an uplink grant received in a Random Access Response or with the PUSCH duration of an uplink grant addressed to Temporary C-RNTI or with the PUSCH duration of a MSGA payload, and the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5 overlaps with any other UL-SCH resource(s), and the physical layer can signal the SR on one valid PUCCH resource for SR, and the priority of the logical channel that triggered SR is higher than the priority of the uplink grant(s) for any UL-SCH resource(s) where the uplink grant was not already de-prioritized and its simultaneous transmission with the SR is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCHgroups, and the priority of the uplink grant is determined as specified in clause 5.4.1; or.

[0424] 3> if both sl-PrioritizationThres and ul-PrioritizationThres are configured and the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5 overlaps with any UL-SCH resource(s) carrying a MAC PDU, and the value of the priority of the triggered SR determined as specified in clause 5.22.1.5 is lower than sl-PrioritizationThres and the value of the highest priority of the logical channel(s) in the MAC PDU is higher than or equal to ul-PrioritizationThres and any MAC CE prioritized as described in clause 5.4.3.1.3 is not included in the MAC PDU and the MAC PDU is not prioritized by upper layer according to TS 23.287

[0019] ; or

[0425] 3> if an SL-SCH resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and either transmission on the SL-SCH resource is not prioritized as described in clause 5.22.1.3.1a or the priority value of the logical channel that triggered SR is lower than ul-PrioritizationThres, if configured; or

[0426] 3> if an SL-SCH resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and the priority of the triggered SR determined as specified in clause 5.22.1.5 is higher than the priority of the MAC PDU determined as specified in clause 5.22.1.3.1a for the SL-SCH resource; or

[0427] 3> if an SL-PRS resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and either transmission on the SL-PRS resource is not prioritized as described in clause 5.22.1.3.1a or 5.22.1.3.1b or the priority value of the logical channel that triggered SR is lower than ul-PrioritizationThres, if configured; or

[0428] 3> if an SL-PRS resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and the priority of the triggered SR determined as specified in clause 5.22.1.5 is higher than the priority of the MAC PDU and SL-PRS, if available, determined as specified in clause 5.22.1.3.1a for the SL-PRS resource:

[0429] 4> consider the SR transmission as a prioritized SR transmission.

[0430] 4> consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s), except for the overlapping uplink grant(s) whose simultaneous transmission is allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups;

[0431] 4> if the de-prioritized uplink grant(s) is a configured uplink grant configured with autonomousTx whose PUSCH has already started:

[0432] 5> stop the configuredGrantTimer for the corresponding HARQ process of the de-prioritized uplink grant(s);

[0433] 5> stop the cg-RetransmissionTimer for the corresponding HARQ process of the de-prioritized uplink grant(s).

[0434] 4> if SR_COUNTER < sr-TransMax:

[0435] 5> instruct the physical layer to signal the SR on one valid PUCCH resource for SR;

[0436] 5> if LBT failure indication is not received from lower layers:

[0437] 6> increment SR_COUNTER by 1;

[0438] 6> start the sr-ProhibitTimer.

[0439] 5> else if lbt-FailureRecoveryConfig is not configured:

[0440] 6> increment SR_COUNTER by 1.

[0441] 4> else:

[0442] 5> notify RRC to release PUCCH for all Serving Cells;

[0443] 5> notify RRC to release SRS for all Serving Cells;

[0444] 5> clear any configured downlink assignments and uplink grants;

[0445] 5> clear any PUSCH resources for semi-persistent CSI reporting;

[0446] 5> if rach-lessHO is not configured:

[0447] 6> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel all pending SRs.

[0448] 3> else:

[0449] 4> consider the SR transmission as a de-prioritized SR transmission.

[0450] In one embodiment of the present disclosure, if at least one SR (Scheduling Request) is pending, the MAC layer device of the terminal may operate as follows for each pending SR.

[0451] 1> if the MAC entity has no valid PUCCH resource configured for the pending SR; and

[0452] 1> if there is no ongoing LTM cell switch; and

[0453] 1> if rach-lessHO is not configured:

[0454] 2> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel the pending SR.

[0455] 1> else, for the SR configuration corresponding to the pending SR:

[0456] 2> when the MAC entity has an SR transmission occasion on the valid PUCCH resource for SR configured; and

[0457] 2> if sr-ProhibitTimer is not running at the time of the SR transmission occasion; and

[0458] 2> if the PUCCH resource for the SR transmission occasion does not overlap with a measurement gap:

[0459] 3> if the PUCCH resource for the SR transmission occasion overlaps with neither an available UL-SCH resource provided by available uplink grant for use, whose simultaneous transmission with the SR is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups nor an SL-SCH resource; or

[0460] 3> if the MAC entity is able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource; or

[0461] 3> if the MAC entity is configured with lch-basedPrioritization, and the PUCCH resource for the SR transmission occasion does not overlap with the PUSCH duration of an uplink grant received in a Random Access Response or with the PUSCH duration of an uplink grant addressed to Temporary C-RNTI or with the PUSCH duration of a MSGA payload, and the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5 overlaps with any other UL-SCH resource(s), and the physical layer can signal the SR on one valid PUCCH resource for SR, and the priority of the logical channel that triggered SR is higher than the priority of the uplink grant(s) for any UL-SCH resource(s) where the uplink grant was not already de-prioritized and its simultaneous transmission with the SR is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCHgroups, and the priority of the uplink grant is determined as specified in clause 5.4.1; or.

[0462] 3> if both sl-PrioritizationThres and ul-PrioritizationThres are configured and the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5 overlaps with any UL-SCH resource(s) carrying a MAC PDU, and the value of the priority of the triggered SR determined as specified in clause 5.22.1.5 is lower than sl-PrioritizationThres and the value of the highest priority of the logical channel(s) in the MAC PDU is higher than or equal to ul-PrioritizationThres and any MAC CE prioritized as described in clause 5.4.3.1.3 is not included in the MAC PDU and the MAC PDU is not prioritized by upper layer according to TS 23.287

[0019] ; or

[0463] 3> if an SL-SCH resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and either transmission on the SL-SCH resource is not prioritized as described in clause 5.22.1.3.1a or the priority value of the logical channel that triggered SR is lower than ul-PrioritizationThres, if configured; or

[0464] 3> if an SL-SCH resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and the priority of the triggered SR determined as specified in clause 5.22.1.5 is higher than the priority of the MAC PDU determined as specified in clause 5.22.1.3.1a for the SL-SCH resource; or

[0465] 3> if an SL-PRS resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and either transmission on the SL-PRS resource is not prioritized as described in clause 5.22.1.3.1a or 5.22.1.3.1b or the priority value of the logical channel that triggered SR is lower than ul-PrioritizationThres, if configured; or

[0466] 3> if an SL-PRS resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and the priority of the triggered SR determined as specified in clause 5.22.1.5 is higher than the priority of the MAC PDU and SL-PRS, if available, determined as specified in clause 5.22.1.3.1a for the SL-PRS resource:

[0467] 4> consider the SR transmission as a prioritized SR transmission.

[0468] 4> consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s), except for the overlapping uplink grant(s) whose simultaneous transmission is allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups;

[0469] 4> if the de-prioritized uplink grant(s) is a configured uplink grant configured with autonomousTx whose PUSCH has already started:

[0470] 5> stop the configuredGrantTimer for the corresponding HARQ process of the de-prioritized uplink grant(s);

[0471] 5> stop the cg-RetransmissionTimer for the corresponding HARQ process of the de-prioritized uplink grant(s).

[0472] 4> if SR_COUNTER < sr-TransMax:

[0473] 5> instruct the physical layer to signal the SR on one valid PUCCH resource for SR;

[0474] 5> if LBT failure indication is not received from lower layers:

[0475] 6> increment SR_COUNTER by 1;

[0476] 6> start the sr-ProhibitTimer.

[0477] 5> else if lbt-FailureRecoveryConfig is not configured:

[0478] 6> increment SR_COUNTER by 1.

[0479] 4> else:

[0480] 5> notify RRC to release PUCCH for all Serving Cells;

[0481] 5> notify RRC to release SRS for all Serving Cells;

[0482] 5> clear any configured downlink assignments and uplink grants;

[0483] 5> clear any PUSCH resources for semi-persistent CSI reporting;

[0484] 5> if rach-lessHO is not configured:

[0485] 6> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel all pending SRs.

[0486] 3> else:

[0487] 4> consider the SR transmission as a de-prioritized SR transmission.

[0488] In one embodiment of the present disclosure, if at least one SR (Scheduling Request) is pending, the MAC layer device of the terminal may operate as follows for each pending SR.

[0489] 1> if the MAC entity has no valid PUCCH resource configured for the pending SR; and

[0490] 1> if there is no ongoing LTM cell switch; and

[0491] 1> if rach-lessHO is not configured:

[0492] 2> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel the pending SR.

[0493] 1> else, for the SR configuration corresponding to the pending SR:

[0494] 2> when the MAC entity has an SR transmission occasion on the valid PUCCH resource for SR configured; and

[0495] 2> if sr-ProhibitTimer is not running at the time of the SR transmission occasion; and

[0496] 2> if the PUCCH resource for the SR transmission occasion does not overlap with a measurement gap:

[0497] 3> if the PUCCH resource for the SR transmission occasion overlaps with neither a UL-SCH resource other than / except that provided by configured uplink grant unavailable / not available for use, whose simultaneous transmission with the SR is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups nor an SL-SCH resource; or

[0498] 3> if the MAC entity is able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource; or

[0499] 3> if the MAC entity is configured with lch-basedPrioritization, and the PUCCH resource for the SR transmission occasion does not overlap with the PUSCH duration of an uplink grant received in a Random Access Response or with the PUSCH duration of an uplink grant addressed to Temporary C-RNTI or with the PUSCH duration of a MSGA payload, and the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5 overlaps with any other UL-SCH resource(s), and the physical layer can signal the SR on one valid PUCCH resource for SR, and the priority of the logical channel that triggered SR is higher than the priority of the uplink grant(s) for any UL-SCH resource(s) where the uplink grant was not already de-prioritized and its simultaneous transmission with the SR is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCHgroups, and the priority of the uplink grant is determined as specified in clause 5.4.1; or.

[0500] 3> if both sl-PrioritizationThres and ul-PrioritizationThres are configured and the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5 overlaps with any UL-SCH resource(s) carrying a MAC PDU, and the value of the priority of the triggered SR determined as specified in clause 5.22.1.5 is lower than sl-PrioritizationThres and the value of the highest priority of the logical channel(s) in the MAC PDU is higher than or equal to ul-PrioritizationThres and any MAC CE prioritized as described in clause 5.4.3.1.3 is not included in the MAC PDU and the MAC PDU is not prioritized by upper layer according to TS 23.287

[0019] ; or

[0501] 3> if an SL-SCH resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and either transmission on the SL-SCH resource is not prioritized as described in clause 5.22.1.3.1a or the priority value of the logical channel that triggered SR is lower than ul-PrioritizationThres, if configured; or

[0502] 3> if an SL-SCH resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and the priority of the triggered SR determined as specified in clause 5.22.1.5 is higher than the priority of the MAC PDU determined as specified in clause 5.22.1.3.1a for the SL-SCH resource; or

[0503] 3> if an SL-PRS resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and either transmission on the SL-PRS resource is not prioritized as described in clause 5.22.1.3.1a or 5.22.1.3.1b or the priority value of the logical channel that triggered SR is lower than ul-PrioritizationThres, if configured; or

[0504] 3> if an SL-PRS resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and the priority of the triggered SR determined as specified in clause 5.22.1.5 is higher than the priority of the MAC PDU and SL-PRS, if available, determined as specified in clause 5.22.1.3.1a for the SL-PRS resource:

[0505] 4> consider the SR transmission as a prioritized SR transmission.

[0506] 4> consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s), except for the overlapping uplink grant(s) whose simultaneous transmission is allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups;

[0507] 4> if the de-prioritized uplink grant(s) is a configured uplink grant configured with autonomousTx whose PUSCH has already started:

[0508] 5> stop the configuredGrantTimer for the corresponding HARQ process of the de-prioritized uplink grant(s);

[0509] 5> stop the cg-RetransmissionTimer for the corresponding HARQ process of the de-prioritized uplink grant(s).

[0510] 4> if SR_COUNTER < sr-TransMax:

[0511] 5> instruct the physical layer to signal the SR on one valid PUCCH resource for SR;

[0512] 5> if LBT failure indication is not received from lower layers:

[0513] 6> increment SR_COUNTER by 1;

[0514] 6> start the sr-ProhibitTimer.

[0515] 5> else if lbt-FailureRecoveryConfig is not configured:

[0516] 6> increment SR_COUNTER by 1.

[0517] 4> else:

[0518] 5> notify RRC to release PUCCH for all Serving Cells;

[0519] 5> notify RRC to release SRS for all Serving Cells;

[0520] 5> clear any configured downlink assignments and uplink grants;

[0521] 5> clear any PUSCH resources for semi-persistent CSI reporting;

[0522] 5> if rach-lessHO is not configured:

[0523] 6> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel all pending SRs.

[0524] 3> else:

[0525] 4> consider the SR transmission as a de-prioritized SR transmission.

[0526] In one embodiment of the present disclosure, among the expressions for the configured uplink grant in the MAC layer device of the terminal, not available for use, unused, or unused for PUSCH transmission can all express the same meaning.

[0527] For specific operations not described in Fig. 10, refer to the description of the corresponding operations in Fig. 8.

[0528] FIG. 10 is a diagram showing the configuration of a terminal according to an embodiment of the present disclosure.

[0529] Referring to FIG. 10, the terminal includes an RF (Radio Frequency) processing unit (10-10), a baseband processing unit (10-20), a storage unit (10-30), and a control unit (10-40). The control unit (10-40) may further include a multi-connection processing unit (10-42).

[0530] The RF processing unit (10-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (10-10) up-converts the baseband signal provided from the baseband processing unit (10-20) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (10-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. In the drawing, only one antenna is shown, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (10-10) may include multiple RF chains. Furthermore, the RF processing unit (10-10) may perform beamforming. For the above beamforming, the RF processing unit (10-10) can adjust the phase and size of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit can perform MIMO and receive multiple layers when performing the MIMO operation.

[0531] The baseband processing unit (10-20) above performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (10-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (10-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (10-10). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (10-20) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processing unit (10-20) divides the baseband signal provided from the RF processing unit (10-10) into OFDM symbol units, restores signals mapped to subcarriers through FFT (fast Fourier transform), and then restores the received bit string through demodulation and decoding.

[0532] The baseband processing unit (10-20) and the RF processing unit (10-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (10-20) and the RF processing unit (10-10) may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit (10-20) and the RF processing unit (10-10) may include a plurality of communication modules to support a plurality of different wireless access technologies. In addition, at least one of the baseband processing unit (10-20) and the RF processing unit (10-10) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include a wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), etc. Additionally, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band and a millimeter wave (mm wave) (e.g., 60GHz) band.

[0533] The storage unit (10-30) stores data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (10-30) can store information related to a second access node that performs wireless communication using a second wireless access technology. In addition, the storage unit (10-30) provides the stored data at the request of the control unit (10-40).

[0534] The control unit (10-40) controls the overall operations of the terminal. For example, the control unit (10-40) transmits and receives signals through the baseband processing unit (10-20) and the RF processing unit (10-10). In addition, the control unit (10-40) records and reads data in the storage unit (10-30). For this purpose, the control unit (10-40) may include at least one processor. For example, the control unit (10-40) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs.

[0535] FIG. 11 is a diagram showing the configuration of a base station according to an embodiment of the present disclosure.

[0536] Referring to Fig. 11, the base station is configured to include an RF processing unit (11-10), a baseband processing unit (11-20), a backhaul communication unit (11-30), a storage unit (11-40), and a control unit (11-50). The control unit (11-50) may further include a multi-connection processing unit (11-52).

[0537] The RF processing unit (11-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (11-10) up-converts the baseband signal provided from the baseband processing unit (11-20) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (11-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. In the drawing, only one antenna is shown, but the first access node may have multiple antennas. In addition, the RF processing unit (11-10) may include multiple RF chains. Furthermore, the RF processing unit (11-10) may perform beamforming. For the above beamforming, the RF processing unit (11-10) can adjust the phase and size of each signal transmitted and received through multiple antennas or antenna elements. The RF processing unit can perform a downlink MIMO operation by transmitting one or more layers.

[0538] The baseband processing unit (11-20) above performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (11-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (11-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (11-10). For example, in the case of OFDM, when transmitting data, the baseband processing unit (11-20) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (11-20) divides the baseband signal provided from the RF processing unit (11-10) into OFDM symbol units, restores the signals mapped to subcarriers through FFT operation, and then restores the received bit string through demodulation and decoding. The baseband processing unit (11-20) and the RF processing unit (11-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (11-20) and the RF processing unit (11-10) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0539] The above backhaul communication unit (11-30) provides an interface for performing communication with other nodes within the network. That is, the backhaul communication unit (11-30) converts a bit string transmitted from the base station to another node, such as an auxiliary base station or core network, into a physical signal, and converts a physical signal received from the other node into a bit string.

[0540] The storage unit (11-40) stores data such as basic programs, application programs, and configuration information for the operation of the base station. In particular, the storage unit (11-40) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (11-40) can store information that serves as a basis for determining whether to provide or terminate multiple connections to a terminal. In addition, the storage unit (11-40) provides the stored data at the request of the control unit (11-50).

[0541] The control unit (11-50) controls the overall operations of the base station. For example, the control unit (11-50) transmits and receives signals through the baseband processing unit (11-20) and the RF processing unit (11-10) or through the backhaul communication unit (11-30). In addition, the control unit (11-50) records and reads data in the storage unit (11-40). For this purpose, the control unit (11-50) may include at least one processor.

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

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

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

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

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

[0547] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples to easily explain the technical contents of the present disclosure and to help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the respective embodiments may be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and another embodiment may be combined with each other to operate a base station and a terminal. In addition, the embodiments of the present disclosure are applicable to other communication systems, and other modifications based on the technical idea of ​​the embodiments may also be implemented.

Claims

1. In a method performed by a terminal in a wireless communication system, If SR (scheduling request) is pending, a step of checking PUCCH (physical uplink control channel) resources for the SR; A step of checking whether the above PUCCH resource overlaps with uplink data channel resources and sidelink resources that do not allow simultaneous transmission with SR; and If the PUCCH resource does not overlap with the uplink data channel resource and the sidelink resource, a step of identifying the PUCCH resource as a prioritized resource is included. A method in which UL-SCH (uplink shared channel) resources of configured uplink grants that are not available for use are not included in the above uplink data channel resources for checking overlap.

2. In paragraph 1, A method of identifying a configured uplink grant other than an available configured uplink grant as an unavailable configured uplink grant.

3. In paragraph 2, A method for identifying a configured grant (CG) that is associated with multiple PUSCHs and satisfies a validity condition as an available configured uplink grant, in which UTO-UCI (unused transmission occasion - uplink control information) is set, and a lower layer is not instructed to not be used for PUSCH (physical uplink shared channel) transmission.

4. In paragraph 2, A method for identifying a CG that is not associated with multiple PUSCHs, with an available configured uplink grant, when UTO-UCI is set and a lower layer is not instructed not to use it for PUSCH transmission.

5. In paragraph 3, A method for indicating to the lower layer whether the CG for which the UTO-UCI is set is used for the PUSCH transmission.

6. In paragraph 1, A method for identifying the PUCCH resource as a prioritized resource even if the above-mentioned unavailable configured uplink grant overlaps with the PUCCH resource.

7. In a wireless communication system, at the terminal, Transmitter and receiver; and If SR (scheduling request) is pending, check the PUCCH (physical uplink control channel) resource for the SR, Check whether the above PUCCH resource overlaps with uplink data channel resources and sidelink resources that do not allow simultaneous transmission with SR. If the PUCCH resource does not overlap with the uplink data channel resource and the sidelink resource, a control unit is included that identifies the PUCCH resource as a prioritized resource, A terminal whose UL-SCH (uplink shared channel) resource of a configured uplink grant that is not available for use is not included in the above uplink data channel resource for checking overlap.

8. In paragraph 7, A terminal that identifies a configured uplink grant other than an available configured uplink grant as an unavailable configured uplink grant.

9. In paragraph 8, A terminal that identifies a CG (configured grant) that is associated with multiple PUSCHs and satisfies a validity condition as an available configured uplink grant, for which UTO-UCI (unused transmission occasion - uplink control information) is set, and a lower layer is not indicated to be unused for PUSCH (physical uplink shared channel) transmission.

10. In paragraph 8, A terminal that identifies a CG that is not associated with multiple PUSCHs as an available configured uplink grant, for which UTO-UCI is set and for which lower layers are not instructed not to use it for PUSCH transmission.

11. In paragraph 9, A terminal for which, for a CG for which the above UTO-UCI is set, it is indicated to the lower layer whether the CG is used for the PUSCH transmission.

12. In paragraph 7, A terminal that identifies the PUCCH resource as a prioritized resource even if the above-mentioned unavailable set uplink grant overlaps with the PUCCH resource.

Images