Method and apparatus for configured grant (CG) and semi-persistent scheduling (SPS) operation considering dtx / drx operation of base station in next-generation mobile communication system
By aligning SPS and CG data transmission with the non-active periods of cell DTX/DRX, the method reduces base station power consumption, addressing the inefficiencies in existing DTX/DRX methods and enhancing energy efficiency.
Patent Information
- Application Number
- PCT/KR2024/006450
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-11
- Filing Date
- 2024-05-13
- Publication Date
- 2024-11-14
AI Technical Summary
The existing base station power consumption is high due to continuous transmission and reception operations, which is not efficiently managed by current discontinuous transmission/discontinuous reception (DTX/DRX) methods, particularly when resources set by configured grant (CG) and semi-persistent scheduling (SPS) conflict with non-active periods (NAP) of cell DTX/DRX.
A method and device that adjust SPS and CG settings to avoid data transmission during the non-active periods (NAP) of cell DTX/DRX, by receiving configuration information from the base station and omitting data transmission during these periods, thereby reducing power consumption.
This approach effectively reduces power consumption by optimizing data transmission and reception operations to align with the non-active periods of cell DTX/DRX, enhancing energy efficiency in base station operations.
Smart Images

Figure KR2024006450_14112024_PF_FP_ABST
Abstract
Description
Method and device for operating CONFIGURED GRANT (CG) and SEMI-PERSISTENT SCHEDULING (SPS) considering DTX / DRX operation of base station in next-generation mobile communication system
[0001] The present disclosure relates to a method for reducing power consumption of a base station and a method for transmitting and receiving data between a terminal and a base station.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.
[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.
[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.
[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.
[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.
[0008] The present invention aims to provide a method and device for processing a case where a non-active period (NAP) of cell DTX / DRX and a resource set by semi-persistent scheduling (SPS) or configured grant (CG) collide when applying a cell DTX / DRX (discontinuous transmission / discontinuous reception) method for reducing power consumption of a base station.
[0009] The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.
[0010] In order to solve the above problem, a method performed by a terminal of a wireless communication system according to an embodiment of the present invention may include the steps of: receiving from a base station at least one of SPS (semi-persistent scheduling) configuration information related to repetitive transmission of data according to SPS or CG configuration information related to repetitive transmission of data according to CG (configured grant); receiving from the base station at least one of cell discontinuous transmission (DTX) configuration information or cell discontinuous reception (DRX) configuration information; and receiving from the base station, based on the SPS configuration information and the cell DTX configuration information, a subset of SPS data to be repetitively transmitted, which does not overlap with a non-active period (NAP) of a cell DTX, or transmitting, based on the CG configuration information and the cell DRX configuration information, a subset of uplink data to be repetitively transmitted according to CG, which does not overlap with a NAP of a cell DRX, to the base station.
[0011] According to an embodiment, the SPS setting information or the CG setting information may be received by being included in an RRC (radio resource control) message.
[0012] According to an embodiment, a subset of SPS data overlapping with the NAP of the cell DTX among the SPS data to be repeatedly transmitted may not be monitored, and a subset of uplink data overlapping with the NAP of the cell DRX among the uplink data to be repeatedly transmitted according to the CG may be omitted from transmission to the base station.
[0013] According to an embodiment, the RV (redundancy version) value of each SPS data included in the subset of the SPS data may be determined based on which SPS data is valid.
[0014] According to an embodiment, the RV value of each uplink data included in the subset of the uplink data may be determined based on which uplink data is valid.
[0015] In addition, a method performed by a base station of a wireless communication system according to an embodiment of the present invention for solving the above-described problem may include the steps of transmitting to a terminal at least one of SPS (semi-persistent scheduling) configuration information related to repetitive transmission of data according to SPS or CG configuration information related to repetitive transmission of data according to CG (configured grant); transmitting to the terminal at least one of cell discontinuous transmission (DTX) configuration information or cell discontinuous reception (DRX) configuration information; and transmitting to the terminal, based on the SPS configuration information and the cell DTX configuration information, a subset of SPS data to be repetitively transmitted, which does not overlap with a non-active period (NAP) of a cell DTX, or receiving, based on the CG configuration information and the cell DRX configuration information, a subset of uplink data to be repetitively transmitted according to a CG, which does not overlap with a NAP of a cell DRX, from the terminal.
[0016] According to an embodiment, a subset of SPS data overlapping with the NAP of the cell DTX among the SPS data to be repeatedly transmitted may be omitted from transmission to the terminal, and a subset of uplink data overlapping with the NAP of the cell DRX among the uplink data to be repeatedly transmitted according to the CG may not be received from the terminal.
[0017] In addition, a terminal of a wireless communication system according to an embodiment of the present invention for solving the above-described problem comprises: a transceiver; And the control unit may include a control unit that receives at least one of SPS configuration information related to repetitive transmission of data according to SPS (semi-persistent scheduling) or CG configuration information related to repetitive transmission of data according to CG (configured grant) from a base station through the transceiver, receives at least one of cell discontinuous transmission (DTX) configuration information or cell discontinuous reception (DRX) configuration information from the base station through the transceiver, and receives, from the base station through the transceiver, based on the SPS configuration information and the cell DTX configuration information, a subset of SPS data to be repetitively transmitted that does not overlap with a non-active period (NAP) of cell DTX, or transmits, to the base station through the transceiver, based on the CG configuration information and the cell DRX configuration information, a subset of uplink data to be repetitively transmitted according to CG that does not overlap with a NAP of cell DRX.
[0018] In addition, a base station of a wireless communication system according to an embodiment of the present invention for solving the above-described problems comprises: a transceiver; And the control unit may include a control unit that transmits to the terminal through the transceiver at least one of SPS configuration information related to the repetitive transmission of data according to SPS (semi-persistent scheduling) or CG configuration information related to the repetitive transmission of data according to CG (configured grant), and transmits to the terminal through the transceiver at least one of cell discontinuous transmission (DTX) configuration information or cell discontinuous reception (DRX) configuration information, and transmits to the terminal through the transceiver a subset of SPS data to be repetitively transmitted, which does not overlap with a non-active period (NAP) of cell DTX, from among the SPS configuration information and the cell DTX configuration information, or receives, from the terminal through the transceiver, a subset of uplink data to be repetitively transmitted according to CG, which does not overlap with a NAP of cell DRX, based on the CG configuration information and the cell DRX configuration information.
[0019] The present invention can provide a processing method and device when a resource set by NAP and SPS or CG of cell DTX / DRX collides when applying a cell DTX / DRX method for reducing power consumption of a base station.
[0020] The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.
[0021] FIG. 1 is a diagram illustrating the structure of an NR system according to one embodiment of the present disclosure.
[0022] FIG. 2 is a diagram illustrating a wireless protocol structure in an NR system according to an embodiment of the present disclosure.
[0023] FIG. 3 is a diagram illustrating Cell DTX / DRX operation according to one embodiment of the present disclosure.
[0024] FIG. 4 is a diagram illustrating SPS setup and transmission / reception operations between a base station and a terminal according to one embodiment of the present disclosure.
[0025] FIG. 5 is a diagram illustrating CG settings and related transmission and reception operations between a base station and a terminal according to one embodiment of the present disclosure.
[0026] FIG. 6 is a diagram illustrating a criterion for determining whether a PUSCH TO allocated to a CG or a PDSCH TO allocated to an SPS is valid, according to one embodiment of the present disclosure.
[0027] FIG. 7 is a diagram illustrating a criterion for determining whether a PUSCH TO allocated to a CG or a PDSCH TO allocated to an SPS is valid when bundling is used according to an embodiment of the present disclosure.
[0028] FIG. 8 is a diagram illustrating criteria for determining whether a specific PDSCH or PDSCH Bundle allocated to an SPS is valid / invalid according to an embodiment of the present disclosure.
[0029] FIG. 9 is a diagram showing the configuration of a terminal according to an embodiment of the present disclosure.
[0030] FIG. 10 is a diagram illustrating a configuration of a network entity according to an embodiment of the present disclosure.
[0031] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the attached drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present disclosure will be omitted.
[0032] 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.
[0033] 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.
[0034] 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.
[0035] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams 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 flow diagram 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 flow diagram 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).
[0036] 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.
[0037] 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.
[0038] 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 5G UE, 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 may be included here, and the 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems through some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.
[0039] 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.
[0040] 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.
[0041] FIG. 1 is a diagram illustrating the structure of an NR system according to one embodiment of the present disclosure.
[0042] Referring to FIG. 1, the wireless communication system may be composed of multiple base stations (e.g., gNB (100), ng-eNB (110), ng-eNB (120), gNB (130)), an Access and Mobility Management Function (AMF) (140), and a User Plane Function (UPF) (150). Of course, the wireless communication system is not limited to the configuration illustrated in FIG. 1 and may include more or fewer components.
[0043] According to one embodiment of the present disclosure, a user equipment (hereinafter referred to as UE or terminal) (160) can access an external network through base stations (100, 110, 120, 130) and UPF (150).
[0044] In Fig. 1, base stations (100, 110, 120, 130) can 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) can collect status information such as buffer status, available transmission power status, and channel status of terminals (160) to schedule the status information and support connections between terminals and a core network (CN; in particular, the CN of NR is referred to as 5GC) in order to service user traffic.
[0045] In Fig. 1, the gNB (100, 130) can control multiple cells, and an adaptive modulation and coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel status of the terminal (160) can be applied.
[0046] The core network (CN) (140, 150) is a device that handles various control functions as well as mobility management functions for terminals (160) and can be connected to multiple base stations (100, 110, 120, 130). In addition, 5GC can also be linked with the existing LTE system.
[0047] Meanwhile, 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 may be configured separately. The gNB (100) and gNB (130) of FIG. 1 may use the UP and CP technologies defined in NR technology, and the ng-eNB (110) and ng-eNB (120), although connected to 5GC, may use the UP and CP technologies defined in LTE (Long Term Evolution) technology.
[0048] AMF (140) is a device that is responsible for various control functions as well as mobility management functions for terminals (160) and can be connected to multiple base stations (100, 110, 120, 130).
[0049] UPF (150) may refer to a type of gateway device that provides data transmission. Although not illustrated in FIG. 1, the NR wireless communication system may also include a Session Management Function (SMF). The SMF can manage packet data network connections, such as protocol data unit (PDU) sessions, provided to the terminal (160).
[0050] FIG. 2 is a diagram illustrating a wireless protocol structure in an NR system according to an embodiment of the present disclosure.
[0051] Referring to FIG. 2, the wireless protocol of the NR system may be composed of SDAP (Service Data Adaptation Protocol) (200) (290), PDCP (Packet Data Convergence Protocol) (210) (280), RLC (Radio Link Control) (220) (270), MAC (Medium Access Control) (230) (260), and PHY (Physical) (240) (250) in the terminal and the base station, respectively.
[0052] SDAP (Service Data Adaptation Protocol) (200) (290) can perform operations for transmitting user data, mapping QoS flows to specific DRBs for uplink and downlink, marking QoS flow IDs for uplink and downlink, and mapping reflective QoS flows to data bearers for uplink SDAP PDUs. SDAP settings corresponding to each DRB can be provided from a higher RRC layer. Of course, the functions of SDAP (200) (290) are not limited to the above examples.
[0053] PDCP (Packet Data Convergence Protocol) (210) (280) can handle operations such as IP header compression / decompression. Furthermore, PDCP (210) (280) can provide sequential and out-of-order transmission functions, reordering, duplicate detection, retransmission, encryption, and decryption functions. Of course, the functions of PDCP (210) (280) are not limited to the above examples.
[0054] Radio Link Control (220)(270) can reconfigure PDCP Protocol Data Units (PDUs) to an appropriate size. Furthermore, RLC (220)(270) can provide sequential and out-of-order transmission functions, and can provide ARQ functions, concatenation, segmentation, reassembly functions, re-segmentation functions, reordering functions, duplicate detection functions, and error detection functions. Of course, the functions of RLC (220)(270) are not limited to the above examples.
[0055] The MAC (230) (260) is connected to multiple RLC layer devices configured in a terminal, and can perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. In addition, the MAC (230) (260) can provide a mapping function, a scheduling information reporting function, a HARQ function, a priority control function between logical channels, a priority control function between terminals, an MBMS service confirmation function, a transmission format selection function, and a padding function. Of course, the functions of the MAC (230) (260) are not limited to the above examples.
[0056] The physical (PHY) layer (240)(250) can perform operations such as channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer. In addition, the physical layer also uses HARQ (Hybrid ARQ) for additional error correction, and the receiving end can transmit 1 bit information on whether or not a packet transmitted by the transmitting end has been received. The 1 bit information is called HARQ ACK / NACK information.
[0057] Downlink HARQ ACK / NACK information for uplink data transmission is transmitted through the physical hybrid-ARQ indicator channel (PHICH) physical channel in the case of LTE, and in the case of NR, whether retransmission is necessary or new transmission can be performed through the UE's scheduling information in the physical downlink control channel (PDCCH), which is a channel through which downlink / uplink resource allocation, etc. are transmitted. This is because NR applies asynchronous HARQ. Uplink HARQ ACK / NACK information for downlink data transmission can be transmitted through the physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH). PUCCH is generally transmitted in the uplink of the PCell, which will be described later, but if the UE supports it, the base station may additionally transmit it to the SCell, which will be described later, to the UE, and this is called the PUCCH SCell.
[0058] Although not shown in Figure 2, an RRC (Radio Resource Control) layer exists above the PDCP layer of each terminal and base station, and the RRC layer can transmit and receive connection and measurement-related setting control messages for radio resource control.
[0059] Meanwhile, the physical layer can be composed of one or more frequencies / carriers, and the technology that sets and uses multiple frequencies simultaneously is called carrier aggregation (CA). CA technology can dramatically increase the transmission capacity by using the primary carrier and one or more secondary carriers in addition to a single carrier for communication between a terminal (or User Equipment, UE) and a base station (eNB or gNB). Meanwhile, in LTE / NR, a cell within a base station that uses a primary carrier is called a primary cell or PCell (Primary Cell), and a cell within a base station that uses a secondary carrier is called a secondary cell or SCell (Secondary Cell).
[0060] FIG. 3 is a diagram for explaining Cell DTX / DRX for reducing base station power consumption according to one embodiment of the present disclosure.
[0061] In mobile communication systems, base stations must provide services to numerous terminals within their service area, resulting in significant power consumption. Therefore, Network Energy Saving (NES) technologies are being discussed to reduce the power consumption of these base stations. For example, the following candidate technologies are being proposed in the NR standard.
[0062] - Cell DTX / DRX (discontinuous transmission / discontinuous reception)
[0063] - NES-aware CHO (conditional handover)
[0064] -SSB(SS / PBCH block: synchronization signal physical broadcast channel)-less / SIB(system information block)-less Cell
[0065] - Cell (Re)Selection enhancement
[0066] - UE WUS (Wake-up signal)
[0067] - UE Assistance Information for NES
[0068] Among these, Cell DTX / DRX is a technology that periodically turns on or off data transmission and reception at the base station. Cell DTX is a technology that turns data transmission on and off at the base station in the downlink, and Cell DRX is a technology that turns data reception on and off at the base station in the uplink. During the period when the base station data transmission and reception are turned off, the power consumption of the base station can be significantly reduced.
[0069] Referring to FIG. 3, when Cell DTX or Cell DRX is executed, the base station can perform a predetermined operation corresponding to the period for each Cell DTX or Cell DRX cycle (300) consisting of an Active Period (AP) (310) and a Non-Active Period (NAP) (320). During the Cell DTX AP period (310), the base station can perform normal transmission operations, and during the Cell DTX NAP period (320), the base station may not perform normal transmission operations. During the Cell DRX AP period (310), the base station can perform normal reception operations, and during the Cell DRX NAP period (320), the base station may not perform normal reception operations. For example, during the Cell DTX NAP (320), a Downlink (DL) resource periodically scheduled for a specific terminal can be prevented from being used by the corresponding terminal through semi-persistence scheduling (SPS). For example, during Cell DRX NAP (320), a configured grant (including CG, CG Type 1, and Type 2) can be used to prevent a specific terminal from using the periodically scheduled Uplink (UL) resources.
[0070] Accordingly, the base station may not transmit / receive data during the NAP (320) of the Cell DTX / DRX. In one embodiment of the present disclosure, the base station may transmit DTX / DRX-related configuration information of a specific Cell to the terminal via an RRC message. After receiving the DTX / DRX-related configuration information of a specific Cell in the RRC layer, the terminal may transmit the configuration information to a lower layer (such as PDCP, RLC, MAC, PHY, etc.) via internal signaling. In one embodiment of the present disclosure, after receiving the DTX / DRX configuration information of a specific Cell, the terminal may set a DTX / DRX-related timer of the corresponding Cell based on the configuration information. In one embodiment of the present disclosure, the Cell DTX / DRX-related timer managed by the terminal may be a timer indicating the remaining time of the AP or NAP.
[0071] In one embodiment of the present disclosure, the terminal can determine the AP (310) or the NAP (320) based on the status of the DTX / DRX AP or NAP Timer of the corresponding Cell. For example, in the case of the Cell DTX / DRX AP Timer, the Timer may start at the start time of the Cell DTX / DRX AP (310) and expire at the expiration time of the Cell DTX / DRX AP (310). In addition, the size of the Cell DTX / DRX AP (310) or the size of the corresponding Cell DTX / DRX AP Timer may be set to the terminal through RRC signaling. For example, the expiration time of the Cell DTX / DRX AP Timer may become the start time of the corresponding Cell DTX / DRX NAP (320). For example, one Cell DTX / DRX NAP (320) and one Cell DTX / DRX AP (310) may constitute one Cell DTX / DRX Periodicity (300). As another example, in the case of Cell DTX / DRX NAP Timer, the Timer may start at the start time of Cell DTX / DRX NAP (320) and expire at the expiration time of Cell DTX / DRX NAP (320). For example, the size of Cell DTX / DRX NAP (320) or the size of the corresponding NAP Timer may be set directly to the terminal by the NW through RRC signaling, or may be set to the remaining value obtained by subtracting the size (or on-duration) of the AP set through RRC signaling from the Cell DTX / DRX Periodicity (300) set by the NW through RRC signaling.
[0072] In the present disclosure, a method for determining whether to use DL or UL resources allocated by a base station to a specific terminal through SPS or CG when the resources partially overlap with Cell DTX / DRX NAP (320) and related terminal operations are proposed.
[0073] FIG. 4 is a diagram illustrating SPS setup and transmission / reception operations between a base station and a terminal according to one embodiment of the present disclosure.
[0074] When a base station transmits a PDSCH (physical downlink shared channel) of a specific TB (transport block) to a terminal, the base station must allocate and notify the terminal in advance of the time / frequency resources used to transmit the PDSCH. The terminal monitors the allocated and notified time / frequency resources, and at this time, the terminal can process the PDSCH received through the resources to determine whether reception of the corresponding TB was successful. Typically, the base station can allocate and notify the terminal of the corresponding PDSCH time / frequency resources by transmitting DCI (downlink control information) via PDCCH in advance each time the base station transmits a PDSCH. However, if the base station periodically allocates the same size of time / frequency resources to the terminal and transmits the PDSCH due to traffic characteristics, the base station can allocate the PDSCH resources via DCI only once, instead of transmitting the DCI to the terminal every time, and can configure the terminal to continuously use the same size of time / frequency resources periodically thereafter. The base station can configure the above operation via SPS. The base station can set the periodicity of periodically allocated PDSCH resources through SPS settings. Furthermore, the base station can transmit a DCI satisfying specific conditions to allocate / announce the time / frequency resources for the first PDSCH and periodically allocate time / frequency resources of the same size, starting with the first PDSCH, according to the SPS period.
[0075] Referring to FIG. 4, a base station (NW) can provide SPS-related settings (400) to a terminal (UE) through a specific information element (IE) (e.g., SPS-Config) of an RRC message.
[0076] A base station can perform SPS activation by transmitting (410) DCI that satisfies specific conditions defined in the standard to a terminal. Periodic PDSCH resources allocated to SPS can only be used after SPS activation.
[0077] A base station can periodically allocate PDSCH resources to a terminal via SPS. For example, the base station can allocate the same resources to multiple adjacent slots starting from the slot where the PDSCH resource is located with a single PDSCH resource allocation to the terminal, thereby enabling the terminal to receive multiple PDSCHs in multiple adjacent slots (PDSCH bundle). The base station can configure the terminal to perform the above operation by setting the pdsch-AggregationFactor to a value greater than 1 in the SPS configuration (e.g., configured for a specific SPS with SPS-Config) or the PDSCH configuration (e.g., configured for all SPSs with PDSCH-Config) via an RRC message. If the corresponding field is set in both SPS-Config and PDSCH-Config, the pdsch-AggregationFactor of a specific SPS can be set based on the value set in the SPS-Config of the corresponding SPS. An SPS in which the pdsch-AggregationFactor is set to a value greater than 1 can have multiple PDSCH Transmission Occasions (TOs) in consecutive slots the number of times set by the pdsch-AggregationFactor, starting from the corresponding PDSCH resource, for each periodically allocated PDSCH resource. In this case, multiple PDSCH TOs (420, 421)(430, 431) can be referred to as a PDSCH Bundle. Multiple PDSCH TOs (420, 421)(430, 431) belonging to a PDSCH Bundle can all be used to transmit and receive (420, 421)(430, 431) a PDSCH having a specific RV (redundancy version) value generated from the same TB. The nth (n starts from 0) PDSCH TO belonging to a specific PDSCH Bundle can apply the corresponding RV value according to a predefined rule based on n mod 4.For example, the RV value can be determined in advance as shown in [Table 1] below.
[0078] n mod 4 = 0n mod 4 = 1n mod 4 = 2n mod 4 = 30231
[0079] A terminal for which a PDSCH Bundle is configured can receive multiple PDSCHs transmitted by a base station from multiple PDSCH TOs of a specific PDSCH Bundle and then use all of the received PDSCHs to determine whether reception of the corresponding TB (Transport Block) was successful. A terminal for which a PDSCH Bundle is not configured can determine whether reception of the corresponding TB was successful after receiving one PDSCH. Whether reception of the terminal was successful can be transmitted to the base station through HARQ Feedback (ACK or NACK) (422, 432). The HARQ Feedback can be included in uplink control information (UCI) and transmitted to the base station. The resource location on the time axis of the corresponding HARQ Feedback can be determined by taking into account the Offset value determined through the DCI used when activating SPS, based on the location on the time axis of the corresponding PDSCH TO.
[0080] The difference in time between two consecutive PDSCH resource allocations allocated to SPS (e.g., the difference between 430 and 420) can be determined by the Periodicity value set in SPS-Config.
[0081] FIG. 5 is a diagram illustrating CG settings and related transmission and reception operations between a base station and a terminal according to one embodiment of the present disclosure.
[0082] In order for a terminal to transmit a PUSCH of a specific TB, the time / frequency resources used to transmit the PUSCH must be allocated and notified in advance by the base station. The terminal can transmit the PUSCH using the allocated and notified time / frequency resources. Typically, when UL data is generated, the terminal notifies the base station of the size of the UL data through a BSR (buffer status report), and the base station can allocate and notify the terminal of the corresponding UL grant through DCI. If the UL traffic characteristics cause the base station to periodically allocate the same size of time / frequency resources to the terminal so that the terminal transmits the PUSCH, it may be more efficient for the base station to allocate the PUSCH resources to the terminal only once through DCI rather than allocating resources through BSR and DCI every time, and to configure the terminal to continue to use the same size of time / frequency resources periodically thereafter. The base station can configure the above operation through CG. The base station can configure the CG for the terminal through an RRC message. The CG configuration may include information for configuring the period of the PUSCH resources. The base station can set CG Type 1 through CG configuration. CG Type 1 can cause periodic PUSCH resource allocation as soon as the CG is set with an RRC message. When CG Type 1 is set, the terminal can transmit uplink data on the PUSCH resources allocated according to the CG Type 1 configuration without receiving a separate DCI. CG Type 2 can cause periodic PUSCH resource allocation only when the CG is set with an RRC message and the corresponding CG is activated with a specific DCI. When CG Type 2 is set, the terminal can transmit uplink data on the PUSCH resources allocated with CG Type 2 after receiving the activation message with the DCI.
[0083] The base station can configure the periodicity of periodically allocated PUSCH resources through CG configuration (e.g., ConfiguredGrantConfig). In addition, the base station can transmit a DCI satisfying specific conditions to allocate / notify the time / frequency resources of the first PUSCH of CG Type 2 and periodically allocate time / frequency resources of the same size, starting from the first PUSCH, according to the CG period.
[0084] Referring to FIG. 5, the base station can provide CG-related settings (500) to the terminal through a specific IE (e.g., ConfiguredGrantConfig) of an RRC message.
[0085] According to an embodiment, the base station can perform the corresponding CG activation by transmitting (510) DCI that satisfies specific conditions defined in the standard. In the case of CG Type 2, the periodic PUSCH resources allocated to the CG can be used only after CG activation.
[0086] A base station can periodically allocate PUSCH resources to a terminal through a CG. For example, the base station can configure the terminal to transmit multiple PUSCHs in multiple adjacent slots, starting from the slot where the corresponding PUSCH resource is located, with a single PUSCH resource allocation (PUSCH bundle), by allocating the same resources to the terminal. The base station can configure this operation by setting the size of the PUSCH Bundle (e.g., repK) to a value greater than 1 in a CG configuration (e.g., configured for a specific CG with ConfiguredGrantConfig) or a PUSCH configuration (e.g., configured for all CGs with PUSCH-Config) via an RRC message. A CG configured with a PUSCH Bundle can have multiple PUSCH Transmission Occasions (TOs) in consecutive slots for a configured number of times, starting from the corresponding PUSCH resource, for each periodically allocated PUSCH resource. At this time, multiple PUSCH TOs (520, 521)(530, 531) can be referred to as a PUSCH Bundle. Multiple PUSCH TOs belonging to a PUSCH Bundle can all be used to transmit and receive (520, 521)(530, 531) a PUSCH having a specific RV value generated from the same TB. If repK is set to a value greater than 1, all PUSCHs belonging to the PUSCH Bundle can be set to RV 0 if repK-RV is not set. The base station can set repK-RV via an RRC message. repK-RV can be one of (0,2,3,1), (0,3,0,3), (0,0,0,0). If repK-RV is set, the nth (n starts from 1) PUSCH TO belonging to a specific PUSCH Bundle can set the kth term of repK-RV to the RV value.n and k can be correlated based on a predefined rule. For example, n and k can have the relationship k = (mod(n-1,4)+1).
[0087] In one embodiment of the present disclosure, TO may be PUSCH TO or PDSCH TO. For example, Bundle may mean PDSCH Bundle or PUSCH Bundle. NAP may be Cell DTX NAP or Cell DRX NAP. A specific TO being valid may mean that, if the TO is a PDSCH TO, the UE should monitor a corresponding resource in the corresponding PDSCH TO, and may mean that, if the TO is a PUSCH TO, the UE can transmit a PUSCH in the corresponding PUSCH TO. Conversely, a specific TO being invalid may mean that, if the TO is a PDSCH TO, the UE does not need to monitor a corresponding resource in the corresponding PDSCH TO, and may mean that, if the TO is a PUSCH TO, the UE cannot transmit a PUSCH in the corresponding PUSCH TO.
[0088] In one embodiment of the present disclosure, when expressing a correlation on the time axis between a TO and a NAP in the present disclosure, if the TO is a PDSCH TO, the corresponding NAP may be a Cell DTX NAP, and if the TO is a PUSCH TO, the corresponding NAP may be a Cell DRX NAP. In one embodiment of the present disclosure, when expressing a correlation on the time axis between a TO and an AP in the present disclosure, if the TO is a PDSCH TO, the corresponding AP may be a Cell DTX AP, and if the TO is a PUSCH TO, the corresponding AP may be a Cell DRX AP.
[0089] As an embodiment of the present disclosure, all thresholds mentioned in the present disclosure may be defined in advance in the standard or may be set by the base station to the terminal in an RRC message.
[0090] FIG. 6 is a diagram illustrating a criterion for determining whether a PUSCH TO allocated to a CG or a PDSCH TO allocated to an SPS is valid, according to one embodiment of the present disclosure.
[0091] Referring to FIG. 6, if a specific TO does not overlap with a NAP, but the slot to which the TO belongs partially overlaps with a NAP (600, 610), the terminal can determine whether the TO is valid by one of the following.
[0092] - Option 1: The TO may be valid.
[0093] - Option 2: The TO may be invalid.
[0094] - Option 3: A TO may be valid if the difference between the start time of the TO and the expiration time of the nearest NAP immediately preceding it is greater than a certain threshold, and / or if the difference between the expiration time of the TO and the start time of the nearest NAP immediately preceding it is greater than a certain threshold. Conversely, if the above conditions are not met, the TO may be invalid.
[0095] - Option 4: If the base station is configured for a specific function, the validity of the TO can be determined by one of Option 1 to Option 3. If the function is not configured, the validity of the TO can be determined by one of Option 1 to Option 3. The function can be configured per terminal, per cell, per BWP (Bandwidth Part), or per CG / SPS.
[0096] Referring to FIG. 6, when a specific TO partially overlaps with a NAP (620, 630), the terminal can determine whether the TO is valid by one of the following.
[0097] - Option 1: The TO may be valid.
[0098] - Option 2: The TO may be invalid.
[0099] - Option 3: If the first symbol of a TO does not overlap with a NAP, the TO may be valid. Conversely, if the first symbol of a TO overlaps with a NAP, the TO may be invalid.
[0100] - Option 4: If the last symbol of a TO does not overlap with a NAP, the TO may be valid. Conversely, if the last symbol of a TO overlaps with a NAP, the TO may be invalid.
[0101] - Option 5: If the base station is configured for a specific function, the validity of the TO can be determined by one of Option 1 to Option 4. If the function is not configured, the validity of the TO can be determined by one of Option 1 to Option 4. The function can be configured per terminal, per cell, per BWP (Bandwidth Part), or per CG / SPS.
[0102] For example, a TO may be valid if the difference between the start time of a TO and the expiration time of the nearest NAP immediately preceding it is greater than a certain threshold, and / or if the difference between the expiration time of the TO and the start time of the nearest NAP immediately preceding it is greater than a certain threshold. Conversely, if the above conditions are not met, the TO may be invalid.
[0103] For example, if all symbols in a specific TO overlap with NAP, the TO may be invalid. For example, if all symbols in a specific TO overlap with AP, the TO may be valid.
[0104] For example, if a specific TO is valid, it can be considered to belong to AP. For example, if a specific TO is invalid, it can be considered to belong to NAP.
[0105] For example, if all symbols of a specific TO overlap with NAP, the TO can be considered to belong to NAP. For example, if all symbols of a specific TO overlap with AP, the TO can be considered to belong to AP.
[0106] FIG. 7 is a diagram illustrating criteria for determining whether a PUSCH TO allocated to a CG or a PDSCH TO allocated to an SPS is valid when bundling is used according to an embodiment of the present disclosure.
[0107] For example, if all TOs within a PDSCH Bundle or PUSCH Bundle belong to an AP, all TOs within that bundle may be valid. For example, if all TOs within a PDSCH Bundle or PUSCH Bundle belong to an NAP, all TOs within that bundle may be invalid.
[0108] Referring to FIG. 7, when at least one TO among TOs belonging to a PDSCH Bundle or a PUSCH Bundle belongs to an AP and at least one TO belongs to a NAP, the method for determining whether each TO is valid / invalid may be one of the following methods.
[0109] - Option 1: All TOs (700, 710, 720, 730, 740, 750) of the bundle can be valid.
[0110] - Option 2: All TOs (700, 710, 720, 730, 740, 750) of the bundle can be invalid.
[0111] - Option 3: TOs belonging to AP (700, 710, 750) among TOs of the bundle may be valid, and TOs belonging to NAP (720, 730, 740) may be invalid.
[0112] - Option 4: Based on the first TO among the TOs of the Bundle,
[0113] ■ Option 4-1: If the first TO belongs to AP, all TOs (700, 710, 720) in the Bundle may be valid. Conversely, if the first TO belongs to NAP, all TOs (730, 740, 750) in the Bundle may be invalid.
[0114] ■ Option 4-2: If the first TO belongs to AP, all TOs (700, 710, 720) in the bundle can be valid. Conversely, if the first TO belongs to NAP, among the TOs in the bundle, only the TOs (750) in AP can be valid, and the TOs (730, 740) in NAP can be invalid.
[0115] ■ Option 4-3: If the first TO belongs to AP, only TOs (700, 710) belonging to AP among TOs in the Bundle can be valid, and TOs (720) belonging to NAP can be invalid. Conversely, if the first TO belongs to NAP, all TOs (730, 740, 750) in the Bundle can be invalid.
[0116] ■ Option 4-4: If the first TO belongs to the AP, then among the TOs in the Bundle, only the TOs (700, 710) in the AP can be valid, and the TO (720) in the NAP can be invalid. Conversely, if the first TO belongs to the NAP, then among the TOs in the Bundle, only the TO (750) in the AP can be valid, and the TOs (730, 740) in the NAP can be invalid.
[0117] - Option 5: If the base station is configured for a specific function, the validity of the TO can be determined by one of Option 1 to Option 4. If the function is not configured, the validity of the TO can be determined by one of Option 1 to Option 4. The function can be configured per terminal, per cell, per BWP (Bandwidth Part), or per CG / SPS.
[0118] In one embodiment of the present disclosure, if some TOs belonging to a specific Bundle are valid and some are invalid, the RV value of a specific valid TO may be determined based on which TO it is among all TOs belonging to the Bundle. For example, if the Bundle is a PDSCH Bundle and the TO is the nth TO (n starts from 0), the RV of the TO may be set to a value corresponding to n mod 4 among the values defined in [Table 2] below.
[0119] n mod 4 = 0n mod 4 = 1n mod 4 = 2n mod 4 = 30231
[0120] In one embodiment of the present disclosure, if some of TOs belonging to a specific Bundle are valid and some are invalid, the RV value of a specific valid TO may be determined based on which valid TO the TO is among all valid TOs belonging to the Bundle. For example, if the Bundle is a PUSCH Bundle, if the TO is the nth active TO among all active TOs (n starts from 1), the RV value of the TO may be set to the kth value of repK-RV. n and k may have a correlation based on a predefined rule. For example, n and k may have a relationship of k = (mod(n-1,4)+1). For example, if the Bundle is a PDSCH Bundle, if the TO is the nth active TO among all active TOs (n starts from 0), the RV of the TO may be set to a value corresponding to n mod 4 among the values defined in [Table 3] below.
[0121] n mod 4 = 0n mod 4 = 1n mod 4 = 2n mod 4 = 30231
[0122] In one embodiment of the present disclosure, in a CG where startingFromRV0 is set to On via an RRC message, initial transmission of a TB transmitted via a PUSCH Bundle allocated to the CG may be possible only in a TO corresponding to RV 0 among the Bundles. For example, in a CG where startingFromRV0 is set to Off via an RRC message, initial transmission of a TB transmitted via a PUSCH Bundle allocated to the CG may be possible only in the first TO among the Bundles.
[0123] In one embodiment of the present disclosure, in a CG where startingFromRV0 is set to On via an RRC message, if some of TOs belonging to a specific PUSCH Bundle are valid and some are invalid, initial transmission of a TB transmitted through the PUSCH Bundle may be possible only from a valid TO corresponding to RV 0 among the Bundle. For example, in a CG where startingFromRV0 is set to Off via an RRC message, if some of TOs belonging to a specific PUSCH Bundle are valid and some are invalid, initial transmission of a TB transmitted through the PUSCH Bundle may be possible only from a first valid TO among the Bundle.
[0124] FIG. 8 is a diagram illustrating criteria for determining whether a specific PDSCH or PDSCH Bundle allocated to an SPS is valid / invalid according to one embodiment of the present disclosure.
[0125] Referring to FIG. 8, for example, if the base station determines that all or part of the TO (800) of the PDSCH or PDSCH Bundle allocated through SPS is valid based on the above-mentioned criteria, if all or part of the symbols of the corresponding HARQ Feedback (810) transmission resources overlap with the NAP, all TOs (800) of the corresponding PDSCH or PDSCH Bundle may be invalid. For example, if the base station sets a specific function, the terminal may operate as described above. The function may be set per terminal, per cell, per BWP (Bandwidth Part), or per CG / SPS.
[0126] For example, if the base station determines that the entire or partial TO (800) of the PDSCH or PDSCH Bundle allocated through SPS is valid based on the above-mentioned criteria, even if the entire symbol or partial symbol of the corresponding HARQ Feedback (810) transmission resource overlaps with the NAP, the entire or partial TO of the PDSCH or PDSCH Bundle can be valid, and the HARQ Feedback (810) can be transmitted and received normally. For example, if the base station sets a specific function, the terminal can operate as described above. The function can be set per terminal, per cell, per BWP (Bandwidth Part), or per CG / SPS.
[0127] Figure 9 is a drawing showing the configuration of a terminal according to one embodiment of the present invention.
[0128] Referring to FIG. 9, a terminal according to an embodiment of the present invention may include a transceiver unit (920) and a control unit (910) that controls the overall operation of the terminal. In addition, the transceiver unit (920) may include a transmitter unit (925) and a receiver unit (923).
[0129] The transmitter / receiver unit (920) can transmit and receive signals with other network entities.
[0130] The control unit (910) can control the terminal to perform any one of the operations described above. Meanwhile, the control unit (910) and the transceiver unit (920) do not necessarily have to be implemented as separate modules, and can of course be implemented as a single component in the form of a single chip. In addition, the control unit (910) and the transceiver unit (920) can be electrically connected. In addition, for example, the control unit (910) can be a circuit, an application-specific circuit, or at least one processor. In addition, the operations of the terminal can be realized by providing a memory device storing the corresponding program code in any component within the terminal.
[0131] FIG. 10 is a diagram showing the configuration of a network entity according to one embodiment of the present invention.
[0132] The network entity of the present invention is a concept that includes a network function according to the system implementation.
[0133] Referring to FIG. 10, a network entity according to an embodiment of the present invention may include a transceiver (1020) and a control unit (1010) that controls the overall operation of the network entity. In addition, the transceiver (1020) may include a transmitter (1025) and a receiver (1023).
[0134] The transmitter / receiver unit (1020) can transmit and receive signals with other network entities.
[0135] The control unit (1010) can control the network entity to perform any one of the operations described above. Furthermore, the control unit (1010) and the transceiver unit (1020) do not necessarily have to be implemented as separate modules, and may be implemented as a single component in the form of a single chip. Furthermore, the control unit (1010) and the transceiver unit (1020) may be electrically connected. For example, the control unit (1010) may be a circuit, an application-specific circuit, or at least one processor. Furthermore, the operations of the network entity may be realized by providing a memory device storing the corresponding program code in any component within the network entity.
[0136] The above network entity may be any one of a base station, AMF, SMF, etc.
[0137] It should be noted that the configuration diagrams, example diagrams of control / data signal transmission methods, example diagrams of operating procedures, and configuration diagrams illustrated in the above FIGS. 1 to 10 are not intended to limit the scope of the present disclosure. That is, not all components, entities, or operational steps described in the above FIGS. 1 to 10 should be construed as essential components for carrying out the disclosure, and the disclosure may be implemented without detriment to its essence even if only some components are included.
[0138] The operations of the network entity or terminal described above can be realized by providing a memory device storing the corresponding program code within any component of the network entity or terminal device. That is, the control unit of the network entity or terminal device can execute the operations described above by reading and executing the program code stored in the memory device using a processor or CPU (Central Processing Unit).
[0139] The various components and modules of the network entity, base station or terminal device described in this specification may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates and application-specific semiconductors.
[0140] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.
Claims
1. A method performed by a terminal of a wireless communication system, A step of receiving, from a base station, at least one of SPS setting information related to repetitive transmission of data according to SPS (semi persistent scheduling) or CG setting information related to repetitive transmission of data according to CG (configured grant); A step of receiving at least one of cell DTX (discontinuous transmission) setting information or cell DRX (discontinuous reception) setting information from the base station; and A method comprising: receiving, from the base station, a subset of SPS data to be repeatedly transmitted, which do not overlap with a non-active period (NAP) of a cell DTX, based on the SPS configuration information and the cell DTX configuration information; or transmitting, to the base station, a subset of uplink data to be repeatedly transmitted according to a CG, which do not overlap with a NAP of a cell DRX, based on the CG configuration information and the cell DRX configuration information.
2. In paragraph 1, A method characterized in that the above SPS setting information or the above CG setting information is received while being included in an RRC (radio resource control) message.
3. In paragraph 1, A method characterized in that a subset of SPS data to be repeatedly transmitted among the SPS data overlapping with the NAP of the cell DTX is not monitored, and a subset of uplink data to be repeatedly transmitted according to the CG, which overlaps with the NAP of the cell DRX, is omitted from transmission to the base station.
4. In paragraph 1, The RV (redundancy version) value of each SPS data included in the subset of the above SPS data is determined based on which SPS data is valid. A method characterized in that the RV value of each uplink data included in a subset of the above uplink data is determined based on which uplink data is valid.
5. A method performed by a base station of a wireless communication system, A step of transmitting to a terminal at least one of SPS setting information related to repetitive transmission of data according to SPS (semi persistent scheduling) or CG setting information related to repetitive transmission of data according to CG (configured grant); A step of transmitting at least one of cell DTX (discontinuous transmission) setting information or cell DRX (discontinuous reception) setting information to the terminal; and A method comprising: transmitting to the terminal, based on the SPS configuration information and the cell DTX configuration information, a subset of SPS data to be repeatedly transmitted, which do not overlap with a non-active period (NAP) of the cell DTX, from among the SPS data to be repeatedly transmitted; or, based on the CG configuration information and the cell DRX configuration information, receiving from the terminal, a subset of uplink data to be repeatedly transmitted according to a CG, which do not overlap with a NAP of the cell DRX.
6. In paragraph 5, A method characterized in that the above SPS setting information or the above CG setting information is transmitted while being included in an RRC (radio resource control) message.
7. In paragraph 5, A method characterized in that, among the SPS data to be repeatedly transmitted, a subset of SPS data overlapping with the NAP of the cell DTX is omitted from transmission to the terminal, and, among the uplink data to be repeatedly transmitted according to the CG, a subset of uplink data overlapping with the NAP of the cell DRX is not received from the terminal.
8. In paragraph 5, The RV (redundancy version) value of each SPS data included in the subset of the above SPS data is determined based on which SPS data is valid. A method characterized in that the RV value of each uplink data included in a subset of the above uplink data is determined based on which uplink data is valid.
9. In the terminal of a wireless communication system, Transmitter and receiver; and A terminal including a control unit which receives, from a base station through the transceiver, at least one of SPS configuration information related to repetitive transmission of data according to SPS (semi persistent scheduling) or CG configuration information related to repetitive transmission of data according to CG (configured grant), and receives, from the base station through the transceiver, at least one of cell DTX (discontinuous transmission) configuration information or cell DRX (discontinuous reception) configuration information, and receives, from the base station through the transceiver, a subset of SPS data to be repetitively transmitted, which does not overlap with a non-active period (NAP) of the cell DTX, based on the SPS configuration information and the cell DTX configuration information, or transmits, to the base station through the transceiver, a subset of uplink data to be repetitively transmitted according to the CG, which does not overlap with a NAP of the cell DRX.
10. In paragraph 9, A terminal characterized in that the above SPS setting information or the above CG setting information is received by being included in an RRC (radio resource control) message.
11. In paragraph 9, A terminal characterized in that, among the SPS data to be repeatedly transmitted, a subset of SPS data overlapping with the NAP of the cell DTX is not monitored, and among the uplink data to be repeatedly transmitted according to the CG, a subset of uplink data overlapping with the NAP of the cell DRX is omitted from transmission to the base station.
12. In paragraph 9, The RV (redundancy version) value of each SPS data included in the subset of the above SPS data is determined based on which SPS data is valid. A terminal, characterized in that the RV value of each of the uplink data included in the subset of the above uplink data is determined based on which uplink data is valid.
13. In a base station of a wireless communication system, Transmitter and receiver; and A base station comprising a control unit which transmits to a terminal through the transceiver at least one of SPS configuration information related to repetitive transmission of data according to SPS (semi persistent scheduling) or CG configuration information related to repetitive transmission of data according to CG (configured grant), and transmits to the terminal through the transceiver at least one of cell DTX (discontinuous transmission) configuration information or cell DRX (discontinuous reception) configuration information, and transmits to the terminal through the transceiver a subset of SPS data to be repetitively transmitted, which does not overlap with a non-active period (NAP) of a cell DTX, based on the SPS configuration information and the cell DTX configuration information, or receives, from the terminal through the transceiver, a subset of uplink data to be repetitively transmitted according to CG, which does not overlap with a NAP of a cell DRX, based on the CG configuration information and the cell DRX configuration information.
14. In paragraph 13, The above SPS setting information or the above CG setting information is transmitted by being included in an RRC (radio resource control) message, A base station, characterized in that, among the SPS data to be repeatedly transmitted, a subset of SPS data overlapping with the NAP of the cell DTX is omitted from transmission to the terminal, and, among the uplink data to be repeatedly transmitted according to the CG, a subset of uplink data overlapping with the NAP of the cell DRX is not received from the terminal.
15. In paragraph 13, The RV (redundancy version) value of each SPS data included in the subset of the above SPS data is determined based on which SPS data is valid. A base station, characterized in that the RV value of each uplink data included in a subset of the above uplink data is determined based on which uplink data is valid.
Citation Information
Patent Citations
Method for operating sensor assembly and electronic device supporting the same
KR1020210054149A
Method and Apparatus for receiving or transmitting signal in wireless communication system
KR102074289B1
Enhanced Wireless Device and Wireless Network Processes
US20220094484A1
Enhanced resource allocation for multicast broadcast services
WO2022065495A1
Cited By
Semi-persistent scheduling enhancement
US12771651B2
Semi-persistent scheduling enhancement
US20240333656A1
