Method and apparatus for transmitting and receiving data within measurement gap in next generation mobile communication system

Abstract

The present disclosure provides a control signal processing method in a wireless communication system, the control signal processing method comprising the steps of: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting, to the base station, a second control signal generated on the basis of the processing.

Description

Method and device for transmitting and receiving data within the measurement gap in a next-generation mobile communication system

[0001] The present disclosure relates to operations of a terminal and a base station in a wireless communication system, and more particularly, to a method and device for a terminal and a base station to transmit and receive data within a Measurement GAP.

[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 meet 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] When such 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 disclosure provides, through various embodiments, a device and method capable of effectively providing a delay-sensitive data transmission service in a wireless communication system.

[0009] The technical problems to be achieved in the embodiments of the present disclosure 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 disclosure belongs from the description below.

[0010] The present disclosure, for solving these problems, is characterized by a method performed by a terminal in a wireless communication system, comprising: a step of receiving Measurement Gap (MG) setting information from a base station; a step of limiting data transmission and reception operations in an activated Measurement Gap based on the Measurement Gap setting information; a step of receiving, from the base station, an indicator indicating ignoring the activated Measurement Gap; and a step of ignoring the activated Measurement Gap and monitoring a PDCCH to transmit and receive data based on the indicator.

[0011] The present disclosure for solving these problems is a method performed by a base station in a wireless communication system, comprising the steps of: transmitting, to a terminal, measurement gap (MG) setting information, wherein the measurement gap setting information is related to a restriction of data transmission and reception operations in an activated measurement gap; and transmitting, to the terminal, an indicator indicating disregard of the activated measurement gap, wherein the indicator is related to disregarding the activated measurement gap and transmitting data through a PDCCH.

[0012] The present disclosure for solving these problems comprises a terminal in a wireless communication system, comprising: a transceiver for transmitting and receiving signals; and a control unit, wherein the control unit receives measurement gap (MG) setting information from a base station, and, based on the Measurement Gap setting information, restricts data transmission and reception operations in an activated Measurement Gap, receives an indicator for indicating disregard of the activated Measurement Gap from the base station, and, based on the indicator, monitors a PDCCH while disregarding the activated Measurement Gap to transmit and receive data.

[0013] The present disclosure for solving these problems comprises a base station in a wireless communication system, comprising: a transceiver for transmitting and receiving signals; and a control unit, wherein the control unit transmits Measurement Gap (MG) setting information to a terminal, the Measurement Gap setting information being related to a limitation of a data transmission and reception operation, and transmits and receives an indicator for instructing the terminal to ignore an activated Measurement Gap, and the indicator is characterized in that the activated Measurement Gap is ignored and data is transmitted through a PDCCH.

[0014] The present disclosure provides a device and method capable of effectively providing a delay-sensitive data transmission service in a wireless communication system.

[0015] The effects that can be obtained from the present disclosure are not limited to the effects mentioned in the various embodiments, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0016] The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings.

[0017] FIG. 1 is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0018] FIG. 2 is a diagram illustrating a wireless protocol structure in a long term evolution (LTE) and new radio (NR) system according to an embodiment of the present disclosure.

[0019] FIG. 3 is a diagram illustrating a configuration of an application data unit (ADU) unit PDU (protocol data unit) set according to one embodiment of the present disclosure.

[0020] FIG. 4 is a diagram illustrating a signaling procedure between a terminal and a base station for transmitting and receiving data sensitive to delay time within a Measurement GAP in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0021] FIG. 5 is a diagram illustrating an example of an operation for transmitting and receiving data sensitive to delay time when a Measurement GAP period set for a terminal and a C-DRX activation period overlap according to an embodiment of the present disclosure.

[0022] FIG. 6 is a diagram illustrating an example of an operation for transmitting and receiving data sensitive to delay time when a Measurement GAP section set for a terminal and a Configured Grant (CG) and Semi-Persistent Scheduling (SPS) transmission time overlap according to an embodiment of the present disclosure.

[0023] FIG. 7 is a diagram illustrating an example of an operation for transmitting and receiving downlink data based on Dynamic Grant (DG) when the arrival time of downlink data sensitive to delay time and the Measurement GAP period set for a terminal according to one embodiment of the present disclosure overlap.

[0024] FIG. 8 is a diagram illustrating an example of an operation for transmitting and receiving uplink data based on Dynamic Grant (DG) when the arrival time of uplink data sensitive to delay time and the Measurement GAP period set for a terminal according to one embodiment of the present disclosure overlap.

[0025] FIG. 9 is a diagram illustrating the internal structure of a terminal according to an embodiment of the present disclosure.

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

[0027] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Furthermore, in describing the present disclosure, if a detailed description of a related known function or configuration is determined to unnecessarily obscure the gist of the present disclosure, such detailed description will be omitted. Furthermore, the terms described below are defined in consideration of their functions in 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 contents throughout this specification. Embodiments of the present invention will be described below with reference to the attached drawings.

[0028] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described in detail below 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 disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the invention, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[0029] 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).

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

[0031] Here, the term '~ unit' 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 '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Therefore, as an example, the '~ unit' 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 '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. Furthermore, in an embodiment, the '~part' may include one or more processors.

[0032] 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. Hereinafter, embodiments of the present disclosure will be described with reference to the attached drawings.

[0033] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, 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 with equivalent technical meanings may be used.

[0034] In the following description, the terms "physical channel" and "signal" may be used interchangeably with data or control signals. For example, while PDSCH (physical downlink shared channel) refers to a physical channel through which data is transmitted, PDSCH can also be used to refer to data. That is, in the present disclosure, the expression "transmitting a physical channel" can be interpreted equivalently to the expression "transmitting data or a signal through a physical channel."

[0035] Hereinafter, in the present disclosure, upper signaling refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of the physical layer, or a terminal transmits a signal to a base station using an uplink data channel of the physical layer. Upper signaling can be understood as radio resource control (RRC) signaling or a media access control (MAC) control element (CE).

[0036] For the convenience of explanation below, this disclosure uses terms and names defined in the 3rd Generation Partnership Project NR (New Radio) or 3rd Generation Partnership Project Long Term Evolution (LTE) standards. However, this disclosure is not limited by the above terms and names, and can be equally applied to systems conforming to other standards. In this disclosure, gNB may be used interchangeably with eNB for the convenience of explanation. That is, a base station described as an eNB may represent a gNB. In addition, the term terminal may represent not only a mobile phone, an MTC device, an NB-IoT device, a sensor, but also other wireless communication devices.

[0037] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNodeB (gNB), an eNode B (eNB), a NodeB, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Of course, the present invention is not limited to the above examples.

[0038] In particular, the present disclosure can be applied to 3GPP NR (5th generation mobile communication standard). Furthermore, the present disclosure can be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. In the present disclosure, eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as eNB may represent a gNB. Furthermore, the term "terminal" may refer to other wireless communication devices, as well as mobile phones, NB-IoT devices, and sensors.

[0039] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.

[0040] As a representative example of a broadband wireless communication system, the LTE system adopts the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink (DL) and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink (UL). The uplink refers to a wireless link in which a terminal (User Equipment; UE or MS; Mobile Station) transmits data or control signals to a base station (eNode B or BS; Base Station), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above multiple access method distinguishes the data or control information of each user by allocating and operating the time-frequency resources to be transmitted for each user so that they do not overlap, that is, so as to achieve orthogonality.

[0041] As the future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0042] In some embodiments, eMBB may aim to provide data rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB should be able to provide a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, a 5G communication system may need to provide an increased user-perceived data rate while simultaneously providing the peak data rate. To meet these requirements, a 5G communication system may require improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology. Furthermore, while current LTE transmits signals using a maximum 20 MHz transmission bandwidth in the 2 GHz band, a 5G communication system may utilize a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band, thereby meeting the data rates required by the 5G communication system.

[0043] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC may require support for large-scale terminal connections within a cell, improved terminal coverage, improved battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements, which may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC should be comprised of low-cost terminals, and since frequent battery replacement is unlikely, extremely long battery lifespans, such as 10 to 15 years, may be required.

[0044] Finally, URLLC is a cellular-based wireless communication service used for specific purposes (mission-critical), such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, the communication provided by URLLC may need to provide very low latency (ultra-low latency) and very high reliability (ultra-reliability). For example, a service supporting URLLC may have to satisfy an air interface latency of less than 0.5 milliseconds and may also have a requirement for a packet error rate (PER) of 10-5 or less. Therefore, for services supporting URLLC, 5G systems may be required to provide a smaller Transmit Time Interval (TTI) than other services, while simultaneously allocating a wide range of resources in the frequency band to ensure the reliability of the communication link.

[0045] The three services considered in the aforementioned 5G communication system—eMBB, URLLC, and mMTC—can be multiplexed and transmitted in a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters may be used between the services. However, the aforementioned mMTC, URLLC, and eMBB are merely examples of different service types, and the service types applicable to this disclosure are not limited to the aforementioned examples.

[0046] Furthermore, while embodiments of the present disclosure are described below using LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communication) systems as examples, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. Furthermore, the embodiments of the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

[0047] FIG. 1 is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0048] Referring to FIG. 1, as illustrated, a wireless access network of a wireless communication system (hereinafter, a next-generation mobile communication system (New Radio, NR or 5G)) may include a next-generation base station (New Radio Node B, hereinafter, gNB) (1-10) and an AMF (1-05, New Radio Core Network Access Management Function). A user terminal (New Radio User Equipment, hereinafter, NR UE or terminal) (1-15) accesses an external network through the gNB (1-10) and the AMF (1-05).

[0049] In Fig. 1, the gNB (1-10) may correspond to an eNB (Evolved Node B) (1-30) of an existing LTE (Long Term Evolution) system. The gNB (1-10) is connected to an NR UE (1-15) via a wireless channel and may provide a service superior to that of an existing Node B (1-20).

[0050] According to one embodiment of the present disclosure, in a next-generation mobile communication system, since all user traffic is serviced through a shared channel, a device is required to collect status information such as the buffer status of UEs, available transmission power status, and channel status, and perform scheduling. This is handled by gNBs (1-10). A single gNB can typically control multiple cells.

[0051] According to one embodiment of the present disclosure, in order to implement ultra-high-speed data transmission compared to existing LTE, it may have a bandwidth greater than the existing maximum bandwidth, and additionally beamforming technology may be used with orthogonal frequency division multiplexing (hereinafter referred to as OFDM) as a wireless access technology.

[0052] In addition, according to one embodiment of the present disclosure, an adaptive modulation and coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel condition of the terminal may be applied. AMF (1-05) may perform functions such as mobility support, bearer setup, and QoS (quality of service) setup. AMF is a device that is responsible for various control functions as well as mobility management functions for the terminal and may be connected to multiple base stations. In addition, the next-generation mobile communication system may also be interoperable with the existing LTE system, and AMF (1-05) may be connected to MME (1-25) through a network interface. MME (1-25) may be connected to eNB (1-30), which is an existing base station. A terminal that supports LTE-NR Dual Connectivity may transmit and receive data while maintaining a connection to not only gNB (1-10) but also eNB (1-30) (1-35).

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

[0054] Referring to FIG. 2, the wireless protocol of the NR system may be composed of SDAP (service data adaptation protocol) (2-05)(2-10), PDCP (packet data convergence protocol) (2-15)(2-20), radio link control (RLC) (2-25)(2-30), and MAC (medium access control) (2-35)(2-40) in the terminal and gNB, respectively. SDAP (2-05)(2-10) may perform an operation to map each QoS flow to a specific DRB (data radio bearer), and the SDAP configuration corresponding to each DRB may be provided from a higher layer (e.g., RRC layer).

[0055] According to one embodiment of the present disclosure, PDCP (2-15) (2-20) may perform operations such as IP header compression and / or restoration, and may additionally perform a re-ordering operation on data packets to provide an in-order delivery service to upper layers. In addition, RLC (2-25) (2-30) may reconfigure PDCP PDUs into an appropriate size. MAC (2-35) (2-40) may be connected to multiple RLC layer devices configured in one terminal, and may perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The physical (PHY) layer (2-45)(2-50) can channel code and modulate upper layer data, create OFDM (orthogonal frequency-division multiplexing) symbols and transmit them through a wireless channel, or demodulate OFDM symbols received through a wireless channel, decode the channel, and transmit them to a higher layer.

[0056] In addition, according to one embodiment of the present disclosure, the PHY layer (2-45)(2-50) can use HARQ (hybrid automatic repeat request) for additional error correction, and the receiver can transmit whether or not a packet transmitted by the transmitter has been received with 1 bit. Information on whether or not the packet received by the receiver from the transmitter has been received can be referred to as HARQ ACK / NACK information. In the case of an LTE system, downlink HARQ ACK / NACK information for uplink data transmission can be transmitted through a physical hybrid-arq indicator channel (PHICH). In the case of an NR system, downlink HARQ ACK / NACK information for uplink data transmission can be transmitted through a physical dedicated control channel (PDCCH), which is a channel through which downlink and / or uplink resource allocation, etc. are transmitted, and the base station can determine whether retransmission is necessary or whether a new transmission can be performed through scheduling information of the terminal.

[0057] Unlike LTE, the reason why the base station in the NR system determines whether retransmission is necessary or a new transmission can be performed based on the scheduling information of the terminal may be because NR applies asynchronous HARQ. Uplink HARQ ACK / NACK information for downlink data transmission can be transmitted via the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH). The PUCCH can generally be transmitted in the uplink of the PCell (primary cell), which will be described later. However, if the terminal supports it, HARQ ACK / NACK information for the SCell (secondary cell), which will be described later, can be transmitted, and in this case, the SCell can be referred to as a PUCCH SCell.

[0058] Although not shown in this drawing, an RRC (radio resource control) layer may exist above the PDCP layer of each terminal and base station, and the RRC layer can exchange connection and measurement-related setting control messages for radio resource control.

[0059] Meanwhile, the PHY layer (2-45)(2-50) may be composed of one or more frequencies and / or carriers, and the technology that sets and uses multiple frequencies simultaneously may be referred to as carrier aggregation (CA). CA technology refers to a technology that additionally uses a primary carrier and one or more secondary carriers instead of using only one carrier for communication between a terminal and a base station (e.g., eNB or gNB), and by using CA technology, the transmission capacity can be increased by the number of secondary carriers. Meanwhile, in LTE and NR systems, a cell within a base station that uses a primary carrier may be referred to as a primary cell or PCell, and a cell within a base station that uses a secondary carrier may be referred to as a secondary cell or SCell.

[0060] FIG. 3 is a diagram illustrating an application data unit (ADU) unit PDU set configuration according to one embodiment of the present disclosure.

[0061] Referring to FIG. 3, various types of traffic can be categorized into ADUs, which are units of information that can be distinguished at the application level. According to one embodiment, an ADU may be a single photo or picture, a single frame of video data, or a single unit of audio data. An ADU may be categorized into PDU sets (3-10), and a PDU set (3-10) may be divided into at least one PDU (3-01, 3-02, 3-03, 3-04, 3-05, 3-06) according to its size and transmitted.

[0062] For example, when using the MPEG (moving picture experts group) standard video compression technology in video traffic, a PDU set can be composed of one of the following: 1) a combination of multiple PDUs corresponding to one I (intra)-frame (3-30), 2) a combination of multiple PDUs corresponding to one B (bidirectional)-frame (3-40), or 3) a combination of multiple PDUs corresponding to one P (predicted)-frame (3-50).

[0063] According to one embodiment of the present disclosure, an I-frame (3-20) can represent a complete photo or picture (3-21) as an independent frame regardless of the presence or absence of other frames. The P-frame and B-frame (3-22) are frames that represent change information of the previous I-frame (3-20), and if the I-frame (3-20) is not received normally, it may be difficult to normally represent the photo or picture (3-23) that was intended to be expressed by the P-frame and B-frame (3-22). In addition, in the case of the B-frame, since it is stored as data that infers the movement between the two frames by referencing both frames between the I-frame and the P-frame, not only the I-frame in front but also the P-frame behind must be received normally in order for the photo or picture that was intended to be expressed by the B-frame to be normally represented.

[0064] For ease of explanation, the embodiments of the present disclosure may explain the configuration of a PDU set by exemplifying a case in which MPEG standard video compression technology is used in video traffic. However, the contents of the present disclosure are not limited to the configuration of a PDU set in video traffic, and can be applied to all PDU set configurations composed of general ADU units.

[0065] According to an embodiment of the present disclosure, an XR traffic flow for a specific XR (extended reality) service may be composed of a combination of data (e.g., PDUs, PDU sets, etc.) having different quality of service (QoS) requirements. For example, when video traffic coded in MPEG is transmitted for a specific XR service, several types of PDU sets having different QoS requirements (e.g., delay, reliability, etc.) corresponding to I-frame / B-frame / P-frame may constitute a single XR traffic flow.

[0066] According to one embodiment of the present disclosure, in order to service an XR traffic flow composed of data having various QoS requirements, a network may map the XR traffic flow to one or more QoS flows. As described above, when one or more QoS flows are used to service a specific XR traffic flow, data constituting the same XR traffic flow may be transmitted through different QoS flows according to the QoS requirements. At this time, the different QoS flows may be mapped to different DRBs or may be mapped to the same DRB. In addition, PDU sets transmitted through the same QoS flow may have different priorities. For example, in the case of the video traffic, a PDU set corresponding to an I-frame may have a relatively higher priority than a PDU set corresponding to a B-frame or a P-frame. The importance of each PDU set can be expressed as a number from 0 to 8, or {True, false} or {0, 1}, and in the case of downlink data, the UPF (User Plane Function) can include the importance information in the GTP-U header, and the base station can consider the importance when transmitting the PDU set in the downlink. In addition, in the case of the uplink, the importance information can be transmitted from the application layer of the terminal to the lower layer (e.g., SDAP, PDCP, RLC, MAC) through the terminal internal interface, or the importance information can be included in the SDAP / PDCP / RLC header, etc. For example, the MAC layer can check the importance of the data included in the RLC PDU through the RLC header information of the RLC PDU, and in this case, the importance of the data can be ultimately determined by the importance of the PDU set that the data constitutes.

[0067] The following embodiments of the present invention were written under the assumption that a lower importance value of a PDU set indicates a higher importance, but the same method can also be applied to cases where a higher importance value of a PDU set indicates a higher importance. However, in this case, only the method of comparing the importance values ​​of each PDU set to determine relative importance may change.

[0068] FIG. 4 is a diagram illustrating a signaling procedure between a terminal and a base station for transmitting and receiving data sensitive to delay time within a Measurement GAP in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0069] Referring to FIG. 4, a terminal (4-01) can exchange terminal capability information related to an operation of transmitting and receiving delay-sensitive data within a Measurement GAP (hereinafter, referred to as MG) section with a base station (4-03) through a UECapabilityExchange procedure (4-01). Thereafter, the base station can configure the terminal to transmit and receive delay-sensitive data within the Measurement GAP section through an RRCReconfiguration procedure (4-12). Thereafter, the terminal can perform an RRM (Radio Resource Management) / POS (Positioning) measurement operation and other data transmission and reception operations (e.g., C-DRX (Connected-Mode Discontinuous Reception), Configured grant scheduling, Semi-persistent scheduling, Dynamic grant scheduling, etc.) within the MG according to the base station configuration. At this time, if the MG section overlaps with the time point when transmission and reception of delay-sensitive data is required, the terminal may transmit and receive delay-sensitive data within the previously set MG section in at least one of the methods described in the embodiments of FIGS. 5, 6, 7, and 8 according to the base station settings. The specific procedures for each step are as follows.

[0070] In step 4-10, the terminal (4-01) and the base station (4-03) can exchange terminal capability information through the UECapabilityExchange procedure. At this time, the terminal can report to the base station whether it supports an operation (the operation described in the embodiments of FIGS. 5, 6, 7, and 8) that enables data transmission and reception when the transmission and reception time of data sensitive to MG section and delay time overlaps.

[0071] In step 4-12, the base station (4-03) can transmit the configuration information necessary for the terminal to perform data transmission and reception and RRM / POS measurement operations in the RRC_CONNECTED state through the RRCReconfiguration procedure. More specifically, the base station can instruct the terminal to measure the signal strength of neighboring cells other than the serving cell for mobility support or to measure a downlink reference signal (e.g., a Positioning Reference Signal) for location estimation. If the terminal cannot exchange data and control signals with the serving cell while performing the configured measurement operation, the base station can set a period (i.e., Measurement GAP) that forces the terminal to perform only the required RRM / POS measurement operation without exchanging data and control signals with the serving cell. In addition, the base station can transmit additional configurations related to the data transmission and reception operation of the terminal (e.g., C-DRX configuration, CG / SPS configuration, etc.) to the terminal.

[0072] In step 4-15, the terminal can perform required RRM / Positioning-related measurements within the MG (Measurement GAP) interval according to the base station settings in step 4-12, and perform required user data transmission and reception operations in the remaining intervals. At this time, the user data transmission and reception operations may include uplink / downlink data transmission and reception operations in the active interval when C-DRX operates in the RRC_CONNECTED state, uplink data transmission operations using Configured grants, downlink data reception operations using Semi-persistent Scheduling, and uplink / downlink data transmission and reception operations using Dynamic grants. In order for the terminal to perform only required RRM and Positioning-related measurement operations within the MG interval, other transmission and reception operations except for transmission and reception operations related to the Random Access procedure may be prohibited within the MG interval. This can be described in the specification as shown in Table 1 below.

[0073] [Table 1]

[0074]

[0075] However, when considering data that is sensitive to transmission delay time, such as XR service data, a restriction that always prevents the terminal from transmitting and receiving user data within the MG section may cause a degradation of the user-perceived service performance. As an example of an embodiment to prevent such performance degradation, when the MG (Measurement GAP) section set for RRM / Positioning-related measurements overlaps with the transmission and reception operation time of delay-sensitive data, methods for allowing the terminal to transmit and receive delay-sensitive data within the previously set MG section can be described as in the embodiments of FIGS. 5, 6, 7, and 8 below.

[0076] FIG. 5 is a diagram illustrating an example of an operation for transmitting and receiving data sensitive to delay time when a Measurement GAP period set for a terminal and a C-DRX activation period overlap according to an embodiment of the present disclosure.

[0077] Referring to FIG. 5, the base station can set the MG (Measurement GAP) required for RRM / positioning-related measurements for the terminal and the C-DRX operation to reduce energy consumed for PDCCH monitoring in the RRC_CONNECTED state. For reference, the terminal can continuously monitor the downlink control channel (PDCCH) to transmit and receive data in the RRC_CONNECTED state. However, such continuous PDCCH monitoring operation may unnecessarily increase the energy consumption of the terminal. Therefore, the base station can set the C-DRX operation so that the terminal does not normally perform PDCCH monitoring operation but periodically wakes up and monitors the PDCCH to determine whether the base station has data to transmit to it. When the base station sets the C-DRX operation, the terminal reduces energy consumption by not performing PDCCH monitoring in the DRX Inactive period most of the time and transitions to the DRX active period at specific cycles (drx-longCycle or drx-shortCycle) to transmit and receive data. The above terminal can transmit and receive user data while transitioning to the DRX active section at specific intervals and monitoring the PDCCH for a minimum specific time (e.g., On duration timer). After data transmission and reception in the DRX active state is completed and a specific time (Inactivity timer) elapses, the terminal transitions back to the DRX Inactive section so as not to perform the PDCCH monitoring operation, thereby reducing energy consumption.

[0078] When MG and C-DRX operations are set together for a terminal as in 5-01, a situation (5-08) may occur where the MG section (5-02) and the DRX active section (or DRX On duration section, 5-05) collide depending on the values ​​of the set MG occurrence cycle (5-03) and C-DRX cycle (5-06). As in Table 1 above, if data transmission and reception operations of the terminal are prohibited in the MG section, when the MG section and the C-DRX active section overlap (5-08), the base station cannot transmit data to the terminal even though it has data to transmit. Therefore, the transmission latency of downlink data to be transmitted to the terminal may increase. This increase in downlink data transmission latency may significantly reduce user satisfaction when the user uses a service that is sensitive to data transmission delay time, such as XR. Therefore, in an embodiment of the present invention, methods for enabling a terminal to transmit and receive data when an MG section and a C-DRX active section (C-DRX on duration section) overlap are described as follows.

[0079] - Method 1 (5-10, introducing non-integer value as MG cycle): In the current specification, the C-DRX cycle (5-16, drx-shortCycle or drx-longCycle) can be set to a non-integer value in ms considering the non-integer cycle characteristics of XR traffic. However, since the MG cycle (5-13, mgrp) can only be set to an integer value in ms, if the C-DRX cycle is set to a non-integer value, collisions between MG and C-DRX cannot be avoided. Therefore, in order to avoid collisions between the MG section and the C-DRX active section, the MG cycle (5-13, mgrp) can also be set to a non-integer value. More specifically, in order to prevent the MG section and the C-DRX active section from overlapping, the MG cycle can be set to a multiple of the C-DRX cycle. For example, the MG period value can be set to a multiple of {(1001 / 240) msec, (25 / 6) msec, (40 / 3) msec, (125 / 6) msec, (200 / 9) msec, (250 / 9) msec, (100 / 3) msec, (400 / 3) msec}. Of course, the base station can avoid collisions by sending new MG settings to the terminal whenever a collision is expected between the MG and C-DRX, but this is inefficient in terms of signaling load. Essentially, to avoid collisions between the MG period and the C-DRX active period, the MG period should also be able to be set to a non-integer value in ms. For this purpose, a new field (e.g., mgrpExt_rXY) for setting the MG period to a non-integer value can be newly introduced in the Measurement Gap configuration (GapConfig IE).Additionally, a new UE capability variable may be introduced to indicate whether the terminal can support an MG cycle set to a non-integer value. If the terminal reports that it can support an MG cycle of a non-integer value through the UE capability variable, the base station may receive pattern information (e.g., cycle information) of XR traffic from the core network and set the MG cycle and C-DRX cycle of the non-integer value based on the pattern information. The method 1 (5-10) may be used together with the following methods 2 (5-20) and 3 (5-30), and may also be used together with the methods proposed in the embodiments of FIGS. 6, 7, and 8.

[0080] - Method 2 (5-20, Allowing data transmission and reception in overlapping sections): The base station can configure the terminal to monitor PDCCH and transmit and receive data even in the section where the MG section (5-22) and the C-DRX active section (5-25, or C-DRX on duration section) overlap. To indicate the above operation, a new indicator (e.g., allowTxRxDrxOnDuration) is introduced and can be configured to the terminal through the RRCReconfiguration procedure (4-12) of FIG. 4. At this time, the indicator can be configured per MAC-CellGroup (MAC-CellGroupConfig), per Gap (GapConfig), or per DRX (DRX-Config). In addition, a UE capability variable is newly defined to indicate whether the terminal supports the above operation, and the terminal can report the corresponding UE capability variable to the base station through the UECapabilityExchange procedure (4-10) of FIG. 4. When the terminal is configured to monitor PDCCH and transmit / receive data even in the overlapping section of the MG section (5-22) and the C-DRX active section (5-25, or C-DRX on duration section) (in other words, when allowTxRxDrxOnDuration is configured), the terminal can perform data transmission / reception even within the MG section, and this can be described in the specification as shown in Table 2 below.

[0081] [Table 2]

[0082]

[0083] - Method 3 (5-30, ignoring MG overlapping with C-DRX active section): When the MG section (5-32) and the C-DRX active section (5-35, or C-DRX on duration section) overlap, the base station can configure the terminal to ignore (skip) the MG (i.e., temporarily deactivate the MG). To indicate the above operation, a new indicator (e.g., allowTxRxDrxOnDuration) may be introduced and configured to the terminal through the RRCReconfiguration procedure (4-12) of FIG. 4. At this time, the indicator may be configured per MAC-CellGroup (MAC-CellGroupConfig), per Gap (GapConfig), or per DRX (DRX-Config). In addition, a UE capability variable is newly defined to indicate whether the terminal supports the above operation, and the terminal can report the UE capability variable to the base station through the UECapabilityExchange procedure (4-10) of FIG. 4. When the MG section (5-32) and the C-DRX active section (5-35, or C-DRX on duration section) overlap, and the terminal is set to ignore (skip) the MG (i.e., when allowTxRxDrxOnDuration is set), the terminal can ignore the MG (i.e., temporarily deactivate the MG) and perform data transmission and reception in the C-DRX active section, which can be described in the specification as shown in Table 3 below.

[0084]

[0085] FIG. 6 is a diagram illustrating an example of an operation for transmitting and receiving data sensitive to delay time when a Measurement GAP section set for a terminal and a Configured Grant (CG) and Semi-Persistent Scheduling (SPS) transmission time overlap according to an embodiment of the present disclosure.

[0086] Referring to FIG. 6, the base station can configure the MG (6-05, Measurement GAP) required for RRM / positioning-related measurements for the terminal, transmission resources (6-03, Configured Grant) for periodically transmitting uplink data in the RRC_CONNECTED state, and transmission resources (6-04, Semi-Persistent Scheduling) for periodically transmitting downlink data. For reference, the base station can dynamically allocate PUSCH / PDSCH resources for uplink and downlink data transmission and reception to the terminal in the RRC_CONNECTED state. To this end, the base station transmits DCI (Downlink Control Information) containing scheduling information for PUSCH and PDSCH transmission resources to the terminal via PDCCH, and the terminal can receive the DCI to check the PUSCH / PDSCH resources used for uplink data transmission and downlink data reception. This dynamic allocation (Dynamic Grant) method may cause a shortage of PDCCH resources because PDCCH resources are used for DCI transmission for each scheduling. To this end, if periodic uplink and downlink data transmission is required, the base station can configure transmission resources (6-03, Configured Grant) for periodically transmitting uplink data and transmission resources (6-04, Semi-Persistent Scheduling) for periodically transmitting downlink data to the terminal through the RRCReconfiguration procedure (4-12) of FIG. 4. In this case, the terminal can transmit uplink data on the PUSCH resource set to CG and receive downlink data on the PDSCH resource set to SPS without PDCCH monitoring.

[0087] When MG (6-05) and CG (6-03) or SPS (6-04) are set together for the terminal as in 6-00, a situation may occur (6-07, 6-08) where the MG section (6-05) and the data transmission / reception timing according to the CG or SPS settings conflict. If the data transmission / reception operation of the terminal is prohibited in the MG section as in Table 1 above, when the data transmission / reception timing according to the MG section and the CG and SPS settings overlap, the terminal and base station cannot transmit data even though there is data to be transmitted. Therefore, the transmission latency of the uplink and downlink data to be transmitted / received by the terminal may increase. This increase in the downlink data transmission latency may significantly reduce user satisfaction when the user uses a service that is sensitive to data transmission latency, such as XR. Therefore, in an embodiment of the present invention, methods for enabling a terminal to transmit and receive data when the data transmission and reception times according to the MG section and CG and SPS settings overlap are described below. The methods below may be complementary to each other, and multiple methods may be used together.

[0088] - Method 1 (Allowing data transmission according to CG settings within the MG section): The base station can configure the terminal to transmit uplink data on PUSCH resources according to the CG settings when the MG section (6-05) and the data transmission timing according to the CG settings overlap. To indicate the above operation, a new indicator (e.g., allowCG-MG) may be introduced and configured to the terminal through the RRCReconfiguration procedure (4-12) of FIG. 4. At this time, the indicator may be configured per MAC-CellGroup unit (MAC-CellGroupConfig), per Gap unit (GapConfig), per CG unit (CG-Config), per DRB unit, or per QoS flow unit. In addition, a UE capability variable may be newly defined to indicate whether the terminal supports the above operation, and the terminal may report the corresponding UE capability variable to the base station through the UECapabilityExchange procedure (4-10) of FIG. 4. When the data transmission timing according to the MG section (6-05) and the CG setting overlap, if the terminal is configured to transmit uplink data on the PUSCH resource according to the CG setting (in other words, when allowCG-MG is configured), the terminal can perform uplink data transmission according to the CG setting even within the MG section, and this can be described in the specification as shown in Table 4 below.

[0089] [Table 4]

[0090]

[0091] Additionally, uplink transmission according to the CG setting may be allowed within the MG section only when the uplink data to be transmitted through the CG setting is important. In this case, whether the uplink data is important can be determined based on the PSI (PDU Set importance) or logical channel priority value corresponding to the uplink data. More specifically, the base station sets a threshold for comparing the PSI and logical channel priority to the terminal, and the terminal can determine the uplink data to be important if the PSI and logical channel priority value corresponding to the uplink data to be transmitted through the CG are lower than the threshold. Alternatively, the terminal may determine the importance of the uplink data based on its internal implementation without the threshold setting process of the base station.

[0092] Additionally, uplink transmission according to the CG configuration may be allowed within the MG section only when delay-critical data is multiplexed in the PUSCH transmission through the CG configuration. Alternatively, uplink transmission according to the CG configuration may be allowed within the MG section only when data of a logical channel (LCH) having delay-critical data is multiplexed in the PUSCH transmission through the CG configuration. In this case, whether specific data is delay-sensitive data may be determined based on a remaining time value corresponding to the uplink data. The remaining time value corresponding to the uplink data may mean the time remaining until the expiration of a discard timer associated with a PDCP PDU corresponding to the data.

[0093] More specifically, the base station can set a threshold value for comparison of remaining time to the terminal, and the terminal can determine the uplink data as delay-critical data if the remaining time value corresponding to the uplink data is lower than the threshold value.

[0094] The remainingTimeThreshold-r18 value, which was previously set for the DSR (Delay Status Report) operation per logical channel group, may be reused as the above threshold value. Alternatively, a new threshold value may be used.

[0095] The above threshold value can be set to the terminal through the RRCReconfiguration procedure (4-12) of FIG. 4, and the above threshold value can be set per cell group, cell, logical channel group, logical channel, or CG.

[0096] Additionally, uplink transmission according to the CG configuration may be permitted within the MG section only when the Delay Status Report (DSR) is multiplexed in the PUSCH transmission (CG PUSCH transmission) through the above CG configuration. For reference, the DSR may be used by the terminal to report to the base station the delay time status information of data waiting for uplink transmission when uplink transmission data that is sensitive to delay time is generated.

[0097] After receiving the DSR transmitted by the terminal, the base station can determine the delay time status of delay-sensitive data waiting to be transmitted within the terminal, and can quickly schedule the transmission resources (UL grant) required for uplink transmission.

[0098] Therefore, when DSR is included in PUSCH transmission through the CG setting of the terminal, the delay time in uplink transmission can be reduced by allowing uplink transmission according to the CG setting even within the MG section.

[0099] Additionally, the terminal can determine whether the data is important data that must be transmitted within the MG section based on the QoS Flow to which the uplink data corresponds (or is coming down).

[0100] For example, a base station can configure specific QoS Flows for terminals to which important data (e.g., XR traffic) is mapped, and the terminal can determine that uplink data transmitted through the corresponding QoS Flows is important data (e.g., XR traffic). Alternatively, even without base station configuration, the terminal can determine that uplink data transmitted through specific QoS Flows is important data depending on its internal implementation.

[0101] Additionally, for XR services, there may be a requirement that multiple types of traffic (e.g., video information, audio information, location information, other sensor information, etc., hereinafter referred to as “multi-modal traffic”) generated at the same time for the same XR service must all arrive together within a certain time range. Therefore, if a specific uplink data belongs to multi-modal traffic, the terminal may determine that the uplink data is important data that must be transmitted within the MG section.

[0102] The terminal's operation of determining whether specific uplink data belongs to multi-modal traffic can be left to the terminal's internal implementation. Alternatively, the base station can configure the terminal to determine whether data transmitted from a specific QoS flow, DRB, RLC, or LCH (logical channel) belongs to specific multi-modal traffic, and the terminal can determine whether each uplink data belongs to multi-modal traffic based on the configuration.

[0103] - Method 1-1 (6-10, delayed CG transmission immediately after MG section): When the MG section (6-15) and the data transmission timing according to the CG configuration overlap (6-16), the base station can determine that the terminal cannot transmit uplink data on the PUSCH resource according to the CG configuration (i.e., the N+1-th CG transmission cannot be performed). Thereafter, so that the terminal can perform the unfinished CG transmission within the MG section, the base station allocates a UL grant (6-17) for delayed CG transmission immediately after the MG section to the terminal, and the terminal can use the UL grant resource to perform the pending N+1-th CG transmission (6-18, i.e., the MAC PDU transmission that was not transmitted in the N+1-th CG transmission). To indicate the above operation, a new indicator (e.g., allowDelayedCG-MG) may be introduced and configured to the terminal through the RRCReconfiguration procedure (4-12) of FIG. 4. At this time, the indicator may be configured per MAC-CellGroup unit (MAC-CellGroupConfig), per Gap unit (GapConfig), per CG unit (CG-Config), per DRB unit, or per QoS flow unit. More specifically, when the base station configures the indicator (e.g., allowDelayedCG-MG), when a Configured grant occurs in the MG section (6-16), the terminal may determine that the configured grant resource is available and may transmit the configured uplink grant and associated HARQ information to the HARQ entity. After that, the HARQ entity may generate the configured grant and the MAC PDU to be transmitted therethrough and transmit them to the corresponding HARQ process.Afterwards, the HARQ process stores the MAC PDU in the HARQ buffer and can also store the UL grant received from the HARQ entity. Afterwards, the HARQ entity generates a transmission, but if the UL grant resource overlaps with the MG section, the transmission cannot be instructed to the actual physical layer and the HARQ process enters a pending state. In other words, when a configured grant occurs in the MG section (6-17), the terminal can generate a MAC PDU for the CG transmission and store it in the HARQ process buffer, but the actual transmission may not occur. At this time, the base station can determine that the terminal cannot perform CG transmission within the MG section and that the MAC PDU is pending. Therefore, in order for the terminal to transmit the MAC PDU as quickly as possible, the base station can provide the terminal with uplink resources (6-17) through DCI addressed with C-RNTI or CS-RNTI immediately after the MG section has passed. At this time, the DCI may include an HARQ process ID corresponding to a CG that was not transmitted within the previous MG section. After receiving the UL grant, the terminal may transfer the UL grant and HARQ information to the HARQ process indicated by the HARQ process ID and instruct the HARQ process to (re)transmit. Thereafter, the HARQ process instructed to transmit may instruct the physical layer to transmit (6-18) the corresponding MAC PDU. In addition, a UE capability variable is newly defined to indicate whether the terminal supports the operation, and the terminal may report the UE capability variable to the base station through the UECapabilityExchange procedure (4-10) of FIG. 4.

[0104] - Method 2 (Allowing data transmission according to SPS settings within the MG section): When the MG section (6-05) and the data transmission timing according to the SPS settings overlap (6-08), the base station can configure the terminal to receive downlink data from the PDSCH resource according to the SPS settings. To indicate the above operation, a new indicator (e.g., allowSPS-MG) may be introduced and configured to the terminal through the RRCReconfiguration procedure (4-12) of FIG. 4. At this time, the indicator may be configured per MAC-CellGroup unit (MAC-CellGroupConfig), per Gap unit (GapConfig), per SPS unit (SPS-Config), per DRB unit, or per QoS flow unit. In addition, a UE capability variable is newly defined to indicate whether the terminal supports the above operation, and the terminal can report the corresponding UE capability variable to the base station through the UECapabilityExchange procedure (4-10) of FIG. 4. When the data transmission timing according to the MG section (6-05) and the SPS setting overlap (6-08), if the terminal is configured to receive downlink data from the PDSCH resource according to the SPS setting (in other words, when allowSPS-MG is configured), the terminal can perform downlink data reception according to the SPS setting even within the MG section, and this can be described in the specification as shown in Table 5 below.

[0105] [Table 5]

[0106]

[0107] FIG. 7 is a diagram illustrating an example of an operation for transmitting and receiving downlink data based on Dynamic Grant (DG) when the arrival time of downlink data sensitive to delay time and the Measurement GAP period set for a terminal according to one embodiment of the present disclosure overlap.

[0108] Referring to FIG. 7, the base station can set the MG (6-05, Measurement GAP) required for RRM / positioning-related measurements for the terminal and dynamically allocate resources (PUSCH / PDSCH resources) for data transmission and reception while avoiding the corresponding MG section. To this end, the base station transmits DCI (Downlink Control Information) containing scheduling information for PUSCH and PDSCH transmission resources to the terminal via the PDCCH, and the terminal can receive the DCI and check the PUSCH / PDSCH resources used for uplink data transmission and downlink data reception.

[0109] When MG is set for a terminal as in 7-00, downlink data to be transmitted to the terminal may arrive at the base station (7-01) just before the start of the MG section (7-02) or during the MG section. At this time, if the terminal's data transmission and reception operation is prohibited in the MG section as in Table 1, the base station cannot transmit the data immediately even though there is data to be transmitted, and can transmit the data (7-03) only after the MG section ends. Therefore, the transmission waiting time for the downlink data to be received by the terminal may increase. This increase in the downlink data transmission waiting time may significantly reduce the user's service satisfaction when the user uses a service that is sensitive to data transmission delay time, such as XR. Therefore, in an embodiment of the present invention, when the MG section and the arrival time of the delay-sensitive downlink data overlap, methods are described below to enable the base station and the terminal to transmit and receive data without delay. The methods below may be complementary, and multiple methods may be used together.

[0110] - Method 1 (7-00, instructing the terminal to ignore (skip) the MG): If downlink data to be transmitted to the terminal arrives just before the occurrence of the MG section (7-07) configured for the terminal, the base station can instruct (7-04) the terminal to ignore the next MG section (7-07, the MG section that will occur shortly). DCI or MAC CE, etc. can be used as the instructor. At this time, the instructor can be set per MAC-CellGroup unit (MAC-CellGroupConfig), per Gap unit (GapConfig), per DRB unit, or per QoS flow unit. If the terminal is instructed to skip the next MG section (i.e., temporarily deactivate the MG) through the instructor, the terminal can ignore the MG section (i.e., temporarily deactivate it) and transmit and receive (7-05) necessary data. To configure the above operation, a new indicator (e.g., dynamicSkipMG) is introduced and can be configured to the terminal through the RRCReconfiguration procedure (4-12) of FIG. 4. In addition, a new UE capability variable is defined to indicate whether the terminal supports the above operation, and the terminal can report the corresponding UE capability variable to the base station through the UECapabilityExchange procedure (4-10) of FIG. 4.

[0111] - Method 2 (7-10, Selective Reception Based on Downlink Data Priority): When downlink data to be transmitted to a terminal arrives within an MG period, the terminal can selectively receive the data based on the priority or importance of the downlink data. A new type of MG (or window) can be defined for the above operation. The base station can set a new type of MG to the terminal. When downlink data to be transmitted to the terminal arrives (7-13) within the set MG period (7-17), the base station can transmit to the terminal DCI (7-14) including information on the priority (e.g., PHY-priority) or importance (e.g., PDU Set Importance, PSI) of the data. The terminal can monitor the PDCCH within the new type of MG or window period and receive the DCI transmitted by the base station. If the terminal determines that the corresponding downlink data is important based on the priority or importance information included in the DCI, the terminal may receive the downlink data on the PDSCH resource indicated by the DCI (7-15). If the downlink data is determined to be unimportant, the terminal may perform the RRC / positioning measurement operation required within the MG without receiving the data. In other words, the priority of the RRM / positioning measurement operation within the newly defined MG section may be lower than that of PDCCH monitoring and receiving important data (e.g., URLLC or XR traffic) on the PDSCH, and higher than that of other data transmissions (unimportant data transmissions) on the PDSCH.For reference, the operation of determining whether the data scheduled through the DCI is important data to be received based on the priority (e.g., PHY-priority) or importance (e.g., PDU Set Importance, PSI) information included in the DCI may be left to the implementation of the terminal. Alternatively, the base station may set a specific threshold, and the terminal may determine that the data scheduled through the DCI is important data to be received when the priority and importance values ​​included in the DCI are lower than the threshold (here, it is assumed that a lower value indicates a higher importance. In the opposite case, it should be modified to 'when the priority and importance values ​​are greater than the threshold'). Alternatively, the base station may set a list of priority and importance values ​​of data to be received by the terminal, and the terminal may determine whether to receive the data based on the list. The priority or importance threshold and list may be set per MAC-CellGroup (MAC-CellGroupConfig) or per Gap (GapConfig). In addition, a UE capability variable is newly defined to indicate whether the terminal supports the above operation, and the terminal can report the UE capability variable to the base station through the UECapabilityExchange procedure (4-10) of FIG. 4.

[0112] FIG. 8 is a diagram illustrating an example of an operation for transmitting and receiving uplink data based on Dynamic Grant (DG) when the arrival time of uplink data sensitive to delay time and the Measurement GAP period set for a terminal according to one embodiment of the present disclosure overlap.

[0113] Referring to FIG. 8, the base station can set the MG (8-02, Measurement GAP) required for RRM / positioning-related measurements for the terminal and dynamically allocate resources (PUSCH / PDSCH resources) for data transmission and reception while avoiding the MG section. When the terminal has uplink data to transmit, it can transmit a BSR (Buffer Status Report) or DSR (Delay status Report) to the base station to be allocated PUSCH resources for transmitting the uplink data. For reference, in the case of BSR, when there is uplink data waiting to be transmitted, it can be used to request uplink resources for transmitting the same by reporting the amount of the data waiting to be transmitted to the base station. In addition, in the case of DSR, when data sensitive to transmission delay (e.g., URLLC and XR data) is waiting to be transmitted, it can be used to request uplink resources (for transmission) in a short time by reporting the amount of the data waiting to be transmitted and delay time information to the base station. Additionally, if there are no PUSCH resources for transmitting the BSR and DSR, the terminal can request uplink transmission resources for BSR and DSR transmission by transmitting a Scheduling Request (SR).

[0114] When MG is set for a terminal as in 8-00, downlink data to be transmitted to the terminal may arrive at the base station (8-01) just before the start of the MG section (8-02) or during the MG section. At this time, if the terminal's data transmission and reception operation is prohibited in the MG section as in Table 1, the base station cannot transmit the data immediately even though there is data to be transmitted, and can transmit the data (8-03) only after the MG section ends. Therefore, the transmission waiting time for the downlink data to be received by the terminal may increase. This increase in the downlink data transmission waiting time may significantly reduce the user's service satisfaction when the user uses a service that is sensitive to data transmission delay time, such as XR. Therefore, in an embodiment of the present invention, when the MG section and the arrival time of the delay-sensitive downlink data overlap, methods are described below to enable the base station and the terminal to transmit and receive data without delay. The methods below may be complementary, and multiple methods may be used together.

[0115] Method 1 (8-00, Selective Transmission Based on Uplink Data Importance): When uplink data to be transmitted by the terminal arrives within the MG section, the terminal can selectively transmit the data depending on the importance of the uplink data. If important uplink data (e.g., URLLC or XR data) to be transmitted arrives (8-06) within the MG section (8-07), the terminal can ignore the MG (or deactivate the MG) and transmit and receive the necessary data (8-05). If the uplink data is determined to be unimportant, the terminal can perform the RRC / positioning measurement operation required within the MG without receiving the data. For reference, the terminal can determine whether the data is important data to be transmitted within the MG section based on the importance of the uplink data to be transmitted (e.g., PDU set importance), the priority of the logical channel on which the data is transmitted, or the remaining time of the data (meaning the time remaining until the discard timer associated with the PDCP PDU corresponding to the data expires). The specific operation by which the terminal determines whether the uplink data is important data that must be transmitted within the MG section can be left to the implementation of the terminal. Alternatively, the base station may set a specific threshold value, and the terminal may determine that the data is important data that must be transmitted within the MG section when the importance value of the uplink data to be transmitted is lower than the threshold value (here, it is assumed that a lower value means a higher importance. In the opposite case, it should be modified to 'when the priority and importance values ​​are greater than the threshold value'). Alternatively, the base station may set a list of importance values ​​of data that the terminal must transmit within the MG section to the terminal, and the terminal may decide whether to transmit the data based on the list.

[0116] Alternatively, the base station may set a specific remaining time threshold value to the terminal, and when the remaining time value corresponding to the uplink data to be transmitted is less than the threshold value, the terminal may recognize the data as delay-critical data and determine that it is important data that must be transmitted within the MG section.

[0117] The remainingTimeThreshold-r18 value, which was previously set for the DSR (Delay Status Report) operation per logical channel group, may be reused as the above threshold value. Alternatively, a new threshold value may be used.

[0118] The above threshold value can be set to the terminal through the RRCReconfiguration procedure (4-12) of FIG. 4, and the above threshold value can be set per cell group, cell, logical channel group, logical channel, or CG.

[0119] Additionally, the terminal can determine whether the data is important data that must be transmitted within the MG section based on the QoS Flow to which the uplink data corresponds (or is coming down).

[0120] For example, a base station can configure specific QoS Flows for terminals to which important data (e.g., XR traffic) is mapped, and the terminal can determine that uplink data transmitted through the corresponding QoS Flows is important data (e.g., XR traffic). Alternatively, even without base station configuration, the terminal can determine that uplink data transmitted through specific QoS Flows is important data depending on its internal implementation.

[0121] Additionally, for XR services, there may be a requirement that multiple types of traffic (e.g., video information, audio information, location information, other sensor information, etc.) generated at the same time for the same XR service must all arrive together within a certain time range. Therefore, if a terminal determines that specific uplink data belongs to multi-modal traffic, it can determine that the uplink data is important data that must be transmitted within the MG section.

[0122] The operation of the terminal to determine whether specific uplink data belongs to multi-modal traffic can be left to the internal implementation of the terminal. Alternatively, the base station can configure the terminal to determine whether data transmitted from a specific QoS flow, DRB, RLC, or LCH (logical channel) belongs to specific multi-modal traffic, and the terminal can determine whether each uplink data belongs to multi-modal traffic based on the configuration.

[0123] Additionally, when SR transmission is triggered for DSR transmission in the MG section, the UE can ignore (or deactivate) the MG and perform an operation for uplink data transmission. If the UE decides to transmit uplink data within the MG section, it can transmit SR to request uplink transmission resources or trigger a random access procedure. To configure the above-described operation, a new indicator (e.g., dynamicSkipMG) is introduced and can be configured to the UE through the RRCReconfiguration procedure (4-12) of FIG. 4. The indicator can be configured per MAC-CellGroup (MAC-CellGroupConfig) or per Gap (GapConfig). In addition, a UE capability variable is newly defined to indicate whether the UE supports the above operation, and the UE can report the UE capability variable to the base station through the UECapabilityExchange procedure (4-10) of FIG. 4.

[0124] Additionally, if SR transmission is triggered by a logical channel (LCH) containing delay-critical data in the MG section, the terminal may ignore (or deactivate) the MG and perform an operation for uplink data transmission. In this case, whether specific data is delay-sensitive data may be determined based on a remaining time value corresponding to the uplink data. The remaining time value corresponding to the uplink data may mean the time remaining until the discard timer associated with the PDCP PDU corresponding to the data expires.

[0125] More specifically, the base station can set a threshold value for comparison of remaining time to the terminal, and the terminal can determine the uplink data as delay-critical data if the remaining time value corresponding to the uplink data is lower than the threshold value.

[0126] The remainingTimeThreshold-r18 value, which was previously set for the DSR (Delay Status Report) operation per logical channel group, may be reused as the above threshold value. Alternatively, a new threshold value may be used.

[0127] The above threshold value can be set to the terminal through the RRCReconfiguration procedure (4-12) of FIG. 4, and the above threshold value can be set per cell group, cell, logical channel group, logical channel, or CG.

[0128] When a terminal decides to transmit uplink data within the MG section, it can transmit an SR to request uplink transmission resources or trigger a random access procedure. To configure the above-described behavior, a new indicator (e.g., delayCriticalSkipMG) can be introduced and configured to the terminal through the RRCReconfiguration procedure (4-12) of FIG. 4.

[0129] The above directive (e.g., delayCriticalSkipMG) can be set on a per MAC-CellGroup basis (MAC-CellGroupConfig) or per Gap basis (GapConfig).

[0130] In addition, a UE capability variable is newly defined to indicate whether the terminal supports the above operation, and the terminal can report the UE capability variable to the base station through the UECapabilityExchange procedure (4-10) of FIG. 4.

[0131] - Method 2 (8-10, Terminal ignores MG): If the uplink data to be transmitted arrives (8-16) just before the occurrence of the configured MG section (8-17), the terminal can ignore (or deactivate) the next MG section (8-17, the MG section that will occur shortly). Then, an indicator (8-14) indicating the deactivation of the corresponding MG can be transmitted to the base station. The indicator can be a UCI or MAC CE or an RRC message. Afterwards, the terminal can ignore (skip) the next MG section (i.e., temporarily deactivate the corresponding MG) and transmit and receive (8-15) the required data. To configure the above operation, a new indicator (e.g., dynamicSkipMG) can be introduced and configured to the terminal through the RRCReconfiguration procedure (4-12) of FIG. 4. The above indicator can be set on a MAC-CellGroup basis (MAC-CellGroupConfig) or a Gap basis (GapConfig). In addition, a UE capability variable is newly defined to indicate whether the terminal supports the above operation, and the terminal can report the corresponding UE capability variable to the base station through the UECapabilityExchange procedure (4-10) of FIG. 4.

[0132] Additionally, the terminal may perform the MG ignore (or deactivate) operation only when it determines that the uplink data to be transmitted is important. In this case, the terminal may determine whether the uplink data to be transmitted is important data as described in Method 1 (8-00).

[0133] FIG. 9 is a diagram illustrating the internal structure of a terminal according to an embodiment of the present disclosure.

[0134] Referring to FIG. 9, the terminal includes an RF (Radio Frequency) processing unit (9-10), a baseband processing unit (9-20), a storage unit (9-30), and a control unit (9-40). Of course, the present invention is not limited to the above example, and the terminal may include fewer or more components than those illustrated in FIG. 9. The RF processing unit (9-10) may perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (9-10) up-converts a baseband signal provided from the baseband processing unit (9-20) into an RF band signal and then transmits it through an antenna, and down-converts an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (9-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 Fig. 9, only one antenna is illustrated, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (9-10) may include multiple RF chains. Furthermore, the RF processing unit (9-10) may perform beamforming. For beamforming, the RF processing unit (9-10) may adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit (9-10) may perform MIMO (multi-input multi-output) and may receive multiple layers when performing MIMO operation. The RF processing unit (9-10) may appropriately set multiple antennas or antenna elements under the control of the control unit (9-40) to perform reception beam sweeping, or adjust the direction and beam width of the reception beam so that the reception beam is coordinated with the transmission beam.

[0135] The baseband processing unit (9-20) can perform 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 (9-20) can generate complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (9-20) can restore the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (9-10). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (9-20) can generate complex symbols by encoding and modulating a transmission bit stream, map the complex symbols to subcarriers, and then configure 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 (9-20) divides the baseband signal provided from the RF processing unit (9-10) into OFDM symbol units, restores signals mapped to subcarriers through FFT (fast Fourier transform) operation, and then restores the received bit string through demodulation and decoding.

[0136] The baseband processing unit (9-20) and the RF processing unit (9-10) can transmit and receive signals as described above. The baseband processing unit (9-20) and the RF processing unit (9-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 (9-20) and the RF processing unit (9-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 (9-20) and the RF processing unit (9-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. In addition, 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. The terminal may transmit and receive signals with the base station using the baseband processing unit (9-20) and the RF processing unit (9-10), and the signals may include control information and data.

[0137] The storage unit (9-30) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (9-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 (9-30) can provide the stored data upon request from the control unit (9-40). In addition, the storage unit (9-30) may be configured with multiple memories. According to one embodiment, the storage unit (9-30) may store a program for performing the split bearer operation method of the present disclosure.

[0138] The control unit (9-40) can control the overall operations of the terminal. For example, the control unit (9-40) can transmit and receive signals through the baseband processing unit (9-20) and the RF processing unit (9-10). In addition, the control unit (9-40) can record and read data in the storage unit (9-40). For this purpose, the control unit (9-40) can include at least one processor. For example, the control unit (9-40) can include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. In addition, at least one component within the terminal can be implemented as a single chip. In addition, according to one embodiment of the present disclosure, the control unit (9-40) can include a multi-connection processing unit (9-42) that performs processing for operating in a multi-connection mode.

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

[0140] Referring to FIG. 10, the base station may include an RF processing unit (10-10), a baseband processing unit (10-20), a backhaul communication unit (10-30), a storage unit (10-40), and a control unit (10-50). Of course, the present invention is not limited to the above example, and the base station may include fewer or more components than the configuration illustrated in FIG. 10.

[0141] The RF processing unit (10-10) can perform 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) can up-convert a baseband signal provided from the baseband processing unit (10-20) into an RF band signal and transmit it through an antenna, and down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (10-10) can include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. In Fig. 10, only one antenna is illustrated, but the base station can be equipped with multiple antennas. In addition, the RF processing unit (10-10) can include multiple RF chains. Furthermore, the RF processing unit (10-10) can perform beamforming. For beamforming, the RF processing unit (10-10) can adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. The RF processing unit (10-10) can perform a downlink MIMO operation by transmitting one or more layers. The RF processing unit (10-10) can perform reception beam sweeping by appropriately setting multiple antennas or antenna elements under the control of the control unit, or can adjust the direction and beam width of the reception beam so that the reception beam is coordinated with the transmission beam.

[0142] The baseband processing unit (10-20) can perform 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 (10-20) can generate complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (10-20) can restore 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 OFDM, when transmitting data, the baseband processing unit (10-20) can generate complex symbols by encoding and modulating a transmission bit stream, map the complex symbols to subcarriers, and then configure OFDM symbols through IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (10-20) can divide the baseband signal provided from the RF processing unit (10-10) into OFDM symbol units, restore the signals mapped to subcarriers through FFT operation, and then restore the received bit string through demodulation and decoding. The baseband processing unit (10-20) and the RF processing unit (10-10) can 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 transmitting unit, a receiving unit, a transceiver unit, a communication unit, or a wireless communication unit. The base station can transmit and receive signals with the terminal using the baseband processing unit (10-20) and the RF processing unit (10-10), and the signals may include control information and data.

[0143] The backhaul communication unit (10-30) can provide an interface for communicating with other nodes within the network. That is, the backhaul communication unit (10-30) can convert a bit string transmitted from a primary base station to another node, such as an auxiliary base station or core network, into a physical signal, and can convert a physical signal received from another node into a bit string.

[0144] The storage unit (10-40) can store data such as basic programs, application programs, and configuration information for the operation of the base station. In particular, the storage unit (10-40) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (10-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 (10-40) can provide stored data at the request of the control unit (10-50). The storage unit (10-40) can also store a program for performing the split bearer operation method of the present disclosure.

[0145] The control unit (10-50) can control the overall operations of the base station. For example, the control unit (10-50) can transmit and receive signals through the baseband processing unit (10-20) and the RF processing unit (10-10) or through the backhaul communication unit (10-30). In addition, the control unit (10-50) can record and read data in the storage unit (10-40). For this purpose, the control unit (10-50) can include at least one processor. In addition, at least one component of the base station can be implemented as a single chip. In addition, at least one component of the base station can be implemented as a single chip. In addition, each component of the base station can operate to perform the embodiments of the present disclosure described above.

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

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

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

[0149] Additionally, the program may be stored in 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 performing 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 performing an embodiment of the present disclosure.

[0150] In the specific embodiments of the present disclosure described above, components included in the invention are expressed in the singular or plural form, 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 the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0151] 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 in a wireless communication system, A step of receiving measurement gap (MG) setting information from a base station; A step of limiting data transmission and reception operations in an activated Measurement Gap based on the above Measurement Gap setting information; A step of receiving an instruction from the base station to ignore the activated Measurement Gap; and A method characterized by including a step of monitoring a PDCCH and transmitting and receiving data based on the above indicator while ignoring the activated Measurement Gap.

2. In paragraph 1, The above instructions are indicated through Dynamic Control Information (DCI). A method characterized in that the above indicator is set in units of Medium Access Control (MAC)-Cell Group, Gap, Data Radio Bearer (DRB), or Quality of Service (QoS) flow.

3. In paragraph 1, A method further comprising the step of receiving a Radio Resource Control (RRC) message including configuration information (Dynamic Skip Measurement Gap) for ignoring the activated Measurement Gap based on the indicator from the base station.

4. In paragraph 1, A method characterized in that it further comprises a step of transmitting and receiving terminal capability information indicating that the terminal can support an operation of receiving data while ignoring the activated Measurement Gap to the base station.

5. In a method performed by a base station in a wireless communication system, A step of transmitting measurement gap (MG) setting information to a terminal, wherein the Measurement Gap setting information is related to restrictions on data transmission and reception operations in an activated Measurement Gap; and A step of transmitting an instruction to the terminal to indicate that the activated Measurement Gap should be ignored, A method characterized in that the above instruction is related to transmitting data via PDCCH while ignoring the activated Measurement Gap.

6. In paragraph 5, The above instructions are indicated through Dynamic Control Information (DCI). A method characterized in that the above indicator is set in units of Medium Access Control (MAC)-Cell Group, Gap, Data Radio Bearer (DRB), or Quality of Service (QoS) flow.

7. In paragraph 5, A method characterized in that it further comprises the step of transmitting a Radio Resource Control (RRC) message including configuration information (Dynamic Skip Measurement Gap) to the terminal to set the Measurement Gap activated based on the indicator to be ignored.

8. In paragraph 5, A method characterized in that it further comprises the step of receiving terminal capability information indicating that the terminal can support an operation of receiving data while ignoring the activated Measurement Gap.

9. In a terminal in a wireless communication system, A transceiver for transmitting and receiving signals; and It includes a control unit, wherein the control unit is: Receive measurement gap (MG) setting information from the base station, Based on the above Measurement Gap setting information, data transmission and reception operations are restricted in the activated Measurement Gap. Receive an instruction from the above base station to ignore the activated Measurement Gap, and A terminal characterized in that, based on the above indicator, data is transmitted and received by monitoring the PDCCH while ignoring the activated Measurement Gap.

10. In paragraph 9, The above instructions are indicated through Dynamic Control Information (DCI). A terminal characterized in that the above indicator is set per Medium Access Control (MAC)-Cell Group unit, per Gap unit, per Data Radio Bearer (DRB) unit, or per Quality of Service (QoS) flow unit.

11. In paragraph 9, the control unit, A terminal characterized in that it receives a Radio Resource Control (RRC) message including configuration information (Dynamic Skip Measurement Gap) for ignoring the activated Measurement Gap based on the indicator from the base station.

12. In paragraph 9, the control unit, A terminal characterized in that it transmits and receives terminal capability information indicating that the terminal can support an operation of receiving data while ignoring an activated Measurement Gap to the base station.

13. In a base station in a wireless communication system, A transceiver for transmitting and receiving signals; and It includes a control unit, wherein the control unit is: Transmits measurement gap (MG) setting information to the terminal, and the Measurement Gap setting information is related to restrictions on data transmission and reception operations in the activated Measurement Gap. To the above terminal, transmit an instruction indicating that the activated Measurement Gap should be ignored, A base station characterized in that the above indicator ignores the activated Measurement Gap and transmits data through the PDCCH.

14. In paragraph 13, The above instructions are indicated through Dynamic Control Information (DCI). A base station characterized in that the above indicator is set per Medium Access Control (MAC)-Cell Group unit, per Gap unit, per Data Radio Bearer (DRB) unit, or per Quality of Service (QoS) flow unit.

15. In paragraph 13, the control unit, Receive terminal capability information indicating that the terminal can support an operation of transmitting and receiving data while ignoring the activated Measurement Gap from the terminal; A base station characterized in that it transmits a Radio Resource Control (RRC) message including configuration information (Dynamic Skip Measurement Gap) to the terminal to set the Measurement Gap activated based on the indicator to be ignored.

Images