Method and device for measuring frequency in wireless communication system

By performing frequency measurement and rapid reporting for user equipment in RRC idle or inactive mode of 5G system, the problem of low frequency measurement efficiency in IoT environment is solved, and the rapid configuration of carrier aggregation and dual connection is realized, improving network performance and Battery life.

CN113728672BActive Publication Date: 2024-11-12SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080031414.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-05-21
Filing Date
2020-04-22
Publication Date
2024-11-12
Estimated Expiration
2040-04-22

AI Technical Summary

Technical Problem

In 5G communication systems, especially in IoT environments, it is difficult for the prior art to effectively perform frequency measurement and rapid reporting, affecting the configuration efficiency of carrier aggregation and dual connections.

Method used

By providing frequency measurement configuration information to the user equipment (UE) in RRC idle mode or RRC inactive mode, starting the timer, performing frequency measurements when the timer expires, and quickly reporting measurement results when the network is connected, so The base station can quickly configure carrier aggregation or dual connections.

Benefits of technology

Improves the efficiency and accuracy of frequency measurement, ensures rapid configuration of carrier aggregation and dual connections in 5G systems, and improves network performance and battery life of user equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113728672B_ABST
    Figure CN113728672B_ABST
Patent Text Reader

Abstract

A method for performing measurement performed by a user equipment (UE), comprising receiving measurement configuration information for measurement in an idle mode or an inactive mode from a base station, starting a timer based on the measurement configuration information, and performing measurement in the idle mode or the inactive mode while the timer is running, wherein when the timer expires in the idle mode or the inactive mode, the measurement configuration information is deleted.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for measuring and reporting frequency in a wireless communication system. Background Art

[0002] In order to meet the growing demand for wireless data services after the commercialization of the fourth generation (4G) communication system, efforts have been made to develop an improved fifth generation (5G) communication system or a quasi-5G communication system. For this reason, the 5G communication system or the quasi-5G communication system is referred to as a "super 4G network communication system" or a "post-evolution (LTE) system". The 5G communication system defined in the Third Generation Partnership Project (3GPP) is referred to as a new radio (NR) system. In order to achieve high data rates, it is considered to implement the 5G communication system in an ultra-high frequency millimeter wave (mmW) band (e.g., a 60 GHz band). In the 5G communication system, in order to reduce the propagation path loss and increase the propagation distance of the ultra-high frequency millimeter wave band, technologies such as beamforming, massive multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antennas are studied and applied to the NR system. Furthermore, in order to improve the network of the system, in the 5G communication system, the development of technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, mobile networks, cooperative communications, coordinated multi-point (CoMP), and interference cancellation is being carried out. Furthermore, in the 5G communication system, advanced coding modulation (ACM) schemes such as hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM) modulation (FQAM) or sliding window superposition coding (SWSC) are being developed, as well as enhanced network access schemes such as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), or sparse code multiple access (SCMA).

[0003] The Internet is evolving from a human-centric connection network to the Internet of Things (IoT), through which humans create and consume information, and distributed elements such as objects exchange and process information through the Internet of Things. Internet of Everything (IoE) technology is emerging, which is a technology that combines IoT technology and big data processing technology through connection with cloud servers. In order to realize IoT, technical elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology and security technology are required, so technologies for inter-object connection such as sensor networks, machine-to-machine (M2M) communication or machine type communication (MTC) have been studied recently. In the IoT environment, intelligent Internet technology (IT) services can be provided that collect and analyze data generated by connected objects and create new value in human life. IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart home appliances and advanced medical services through the fusion and integration of existing information technology (IT) and various industries.

[0004] Various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, M2M communications, or MTC are implemented by 5G communication technologies such as beamforming, MIMO, or array antennas. Cloud RAN, as an application of big data processing technology, can be an example of the fusion of 5G technology and IoT technology.

[0005] As wireless communication systems develop to provide various services, methods for efficiently providing these services are needed. Summary of the invention

[0006] [Technical solution]

[0007] According to one aspect of the exemplary embodiments, there is provided a communication method in wireless communication.

[0008] [Beneficial Effects]

[0009] Aspects of the present disclosure provide an efficient communication method in a wireless communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description in conjunction with the accompanying drawings, wherein like reference numerals represent like components:

[0011] Figure 1A is a diagram showing a structure of a Long Term Evolution (LTE) system according to an embodiment of the present disclosure;

[0012] Figure 1B is a diagram showing a radio protocol architecture in an LTE system according to an embodiment of the present disclosure;

[0013] Figure 1C is a diagram showing a structure of a next generation mobile communication system according to an embodiment of the present disclosure;

[0014] Figure 1D is a diagram showing a radio protocol architecture of a next generation mobile communication system according to an embodiment of the present disclosure;

[0015] Figure 1E is a diagram for describing a process of configuring carrier aggregation by a user equipment (UE) in a next generation mobile communication system according to an embodiment of the present disclosure;

[0016] Figure 1F is a diagram for describing a method in which a UE performs early frequency measurement and makes a fast frequency measurement result report in a next generation mobile communication system according to an embodiment of the present disclosure;

[0017] Figure 1H is a diagram for describing a method in which a UE performs early frequency measurement and makes a fast frequency measurement result report in a next generation mobile communication system according to an embodiment of the present disclosure;

[0018] Fig. 1I is a diagram for describing a radio access network (RAN) notification area update procedure according to an embodiment of the present disclosure;

[0019] Figure 1J is a diagram for describing a RAN notification area update process according to an embodiment of the present disclosure;

[0020] Figure 1K is a diagram for describing a process in which a radio resource control (RRC) inactive UE falls back to an RRC idle mode due to an instruction of a next generation Node B (gNB) according to an embodiment of the present disclosure;

[0021] Figure 1L is a diagram for describing an operation of a terminal performing RRC idle mode or RRC inactive mode frequency measurement and reporting a measurement result according to an embodiment of the present disclosure;

[0022] Figure 1M is a block diagram showing the structure of a terminal according to an embodiment of the present disclosure;

[0023] Figure 1N is a block diagram showing the structure of a base station according to an embodiment of the present disclosure;

[0024] Figure 2A is a diagram showing the structure of an LTE system according to an embodiment of the present disclosure;

[0025] Figure 2B is a diagram showing a radio protocol architecture in an LTE system according to an embodiment of the present disclosure;

[0026] Figure 2C is a diagram showing a structure of a next generation mobile communication system according to an embodiment of the present disclosure;

[0027] Figure 2D is a diagram showing a radio protocol architecture of a next generation mobile communication system according to an embodiment of the present disclosure;

[0028] Figure 2E is a diagram for describing a process in which a gNB configures whether to perform uplink data compression when a UE configures a network connection according to an embodiment of the present disclosure;

[0029] Figure 2F is a diagram for describing a data structure and a process for performing uplink data compression according to an embodiment of the present disclosure;

[0030] Figure 2G is a diagram for describing an uplink data compression method according to an embodiment of the present disclosure;

[0031] Figure 2H is a diagram for describing a decompression failure occurring in an uplink data compression method according to an embodiment of the present disclosure;

[0032] Fig.2I is a diagram for describing a packet data convergence protocol (PDCP) control packet data unit (PDU) format applicable to a verification and fault handling method according to an embodiment of the present disclosure;

[0033] Figure 2J is a diagram for describing terminal operations of receiving a PDCP layer according to an embodiment of the present disclosure;

[0034] Figure 2K is a block diagram showing a structure of a terminal according to an embodiment of the present disclosure; and

[0035] Figure 2L is a block diagram showing the structure of a base station according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0036] Provided are an apparatus and method for efficiently providing a service in a mobile communication system.

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

[0038] According to an embodiment of the present disclosure, a method for performing measurements performed by a user equipment (UE) includes: receiving measurement configuration information for measuring in an idle mode or an inactive mode from a base station; starting a timer based on the measurement configuration information; and performing measurements in the idle mode or the inactive mode while the timer is running, wherein when the timer expires in the idle mode or the inactive mode, the measurement configuration information is deleted.

[0039] The method may further include: sending a radio resource control (RRC) resume request message to the base station; receiving a response message to the RRCResumeRequest message; and determining whether to continue to perform the measurement based on the response message.

[0040] Determining whether to continue to perform measurement in the idle mode based on the response message may include, when the response message is an RRC setup message or an RRC resume message, stopping a running timer and deleting the measurement configuration information.

[0041] Determining whether to continue performing the measurement in the idle mode based on the response message may include continuing performing the measurement in the idle mode or the inactive mode when the response message is an RRC reject message.

[0042] The method may further include: receiving a UEinformationRequest message for requesting a measurement result; sending a UEinformation response message including the measurement result; and discarding the measurement result.

[0043] The method may also include maintaining configuration information of a master cell group (MCG) Scell ​​or a secondary cell group (SCG), wherein the response message includes information indicating whether to reconstruct the configuration information of the Scell ​​or SCG, and wherein the configuration information of the Scell ​​or SCG is released or reconstructed based on the information indicating whether to reconstruct the configuration information of the Scell ​​or SCG.

[0044] The method may further include: performing a cell reselection process; and when a cell selected based on the cell reselection process is not a validity area, stopping the timer and discarding the measurement configuration information.

[0045] The method may further include: performing a cell reselection procedure; and when a cell selected based on the cell reselection procedure is a cell using another radio access technology (RAT), stopping a running timer and discarding the measurement configuration information.

[0046] The method may further include maintaining the running timer and maintaining the measurement configuration information when the UE transitions from the inactive mode to the idle mode.

[0047] The method may further include, when the UE fails to find a cell to camp on or fails to select a cell, not stopping a running timer or not deleting the measurement configuration information.

[0048] According to another embodiment of the present disclosure, a user equipment (UE) for performing measurements in an idle mode or an inactive mode includes: a transceiver; and a processor, which is coupled to the transceiver and configured to receive measurement configuration information for measuring in the idle mode or the inactive mode from a base station, start a timer based on the measurement configuration information, perform measurements in the idle mode or the inactive mode while the timer is running, and remove the measurement configuration information when the timer expires in the idle mode or the inactive mode.

[0049] The processor may be further configured to send a radio resource control (RRC) resume request message to the base station, receive a response message to the RRCResumeRequest message, and determine whether to continue to perform the measurement based on the response message.

[0050] The processor may be further configured to, when the response message is an RRC setup message or an RRC resume message, stop the running timer and discard the measurement configuration information.

[0051] The processor may be further configured to: when the response message is an RRC reject message, continue to perform the measurement in an idle mode or an inactive mode.

[0052] The processor may be further configured to receive a UEinformationRequest message for requesting a measurement result, send a UEinformation response message including the measurement result, and discard the measurement result.

[0053] The processor may be further configured to maintain master cell group (MCG) Scell ​​or secondary cell group (SCG) configuration information, wherein the response message includes information indicating whether the reconstruction is to reconstruct the Scell ​​or SCG configuration information, wherein the Scell ​​configuration information is released or reconstructed based on the information indicating whether the reconstruction is to reconstruct the Scell ​​or SCG configuration information.

[0054] The processor may be further configured to: perform a cell reselection process; and when a cell selected based on the cell reselection process is not a validity area, stop the timer and discard the measurement configuration information.

[0055] The processor may be further configured to: perform a cell reselection procedure; and when a cell selected based on the cell reselection procedure is a cell using another radio access technology (RAT), stop the running timer and discard the measurement configuration information.

[0056] The processor may be further configured to maintain the running timer and maintain the measurement configuration information when the UE transitions from the inactive mode to the idle mode.

[0057] The processor may be further configured to not stop a running timer or not remove measurement configuration information when the UE fails to find a cell to camp on or fails to select a cell.

[0058] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used in this patent document: the terms "include" and "comprising" and their derivatives mean including but not limited to; the term "or" is inclusive, referring to and / or; the phrases "associated with" and "associated with" and their derivatives may mean including, included, interconnected with, containing, contained within, connected to or connected with, coupled to or coupled with, communicable with, cooperating with, interleaved, juxtaposed, adjacent, bound to or bound with, having, having the property of, etc.; and the term "controller" means any device, system, or part thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or a combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0059] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and is contained in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data, or parts thereof suitable for implementation in appropriate computer-readable program codes. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical or other communication links that send temporary electrical or other signals. A non-transitory computer-readable medium includes a medium that can permanently store data, and a medium that can store data and then rewrite data, such as a rewritable optical disc or an erasable storage device.

[0060] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most, instances, such definitions apply to past as well as future tense uses of the defined words and phrases.

[0061] [Invention Mode]

[0062] The following discussion Figures 1A to 2L The various embodiments used to describe the principles disclosed in this patent document are merely exemplary and should not be interpreted in any way to limit the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0063] Throughout the disclosure, the expression "at least one of a, b, or c" means only a, only b, only c, both a and b, both a and c, both b and c, all of a, b, and c, or variations thereof.

[0064] Examples of the terminal may include a User Equipment (UE), a Mobile Station (MS), a cellular phone, a smart phone, a computer, and a multimedia system capable of performing a communication function.

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

[0066] Throughout the specification, a layer may also be referred to as an entity.

[0067] The working principle of the present disclosure will be described in detail with reference to the accompanying drawings. While describing the present disclosure, detailed descriptions of related well-known functions or configurations that may obscure the main points of the present disclosure are omitted. The terms used herein are defined in consideration of the functions in the present disclosure, but these terms may vary according to the intentions of users or operators, precedents, etc. Therefore, the terms used herein must be defined based on the meaning of the terms and the descriptions in the full text of the specification.

[0068] Hereinafter, the terms indicating connection nodes, network entities, messages, interfaces between network entities, and various identification information used in the following description are exemplified for convenience of explanation. Therefore, the present disclosure is not limited to the terms to be described later, but other terms indicating objects having the same technical meaning may be used.

[0069] Hereinafter, for convenience of explanation, the present disclosure uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard. However, the present disclosure is not limited to the above terms and names and may also be applied to systems complying with other standards.

[0070] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. While describing the present disclosure, detailed descriptions of related well-known functions or configurations that may obscure the main points of the present disclosure are omitted. The terms used herein are defined in consideration of the functions in the present disclosure, but these terms may vary according to the intentions of users or operators, precedents, etc. Therefore, the terms used herein must be defined based on the meaning of the terms and the descriptions in the entire specification. In the following, a base station as an entity for allocating resources to a terminal may include at least one of an eNode B, a Node B, a base station (BS), a radio access unit, a base station controller, or a node on a network. In the present disclosure, for ease of explanation, eNB may be used interchangeably with gNB. That is, a base station described as an eNB may refer to a gNB. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, a downlink (DL) refers to a wireless link for sending signals from a base station to a terminal, and an uplink (UL) refers to a wireless link for sending signals from a terminal to a base station. In addition, although the LTE / LTE Advanced (LTE-A) system is described below as an example, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. For example, the embodiments of the present disclosure may be applied to fifth generation (5G) mobile communication technologies (e.g., 5G New Radio (NR)) developed after LTE-A. In addition, the embodiments of the present disclosure may also be applied to other communication systems by making some changes or modifications therein without departing from the spirit and scope of the present disclosure.

[0071] In order to support services with high data rates and low latency in the next generation mobile communication system, the base station needs to quickly configure carrier aggregation (CA) or dual connectivity (DC) in the terminal. However, in order to configure such technology in the terminal, the frequency measurement result of the terminal may be required. Therefore, a method for receiving a fast frequency measurement result report of the terminal may be required.

[0072] When a radio resource control (RRC) idle mode terminal that configures and performs fast frequency measurement in RRC idle mode transitions to RRC inactive mode for some reason, or when an RRC inactive mode terminal that configures and performs fast frequency measurement in RRC inactive mode transitions to RRC idle mode, an effective method for determining whether to continue frequency measurement, stop frequency measurement, or perform different processes according to the cause of the state transition may be required.

[0073] An embodiment of the present disclosure provides a method in which an RRC idle mode or RRC inactive mode terminal can quickly report frequency measurement results to a base station in a next generation mobile communication system. According to an embodiment of the present disclosure, a base station can quickly configure carrier aggregation or dual connection in a terminal. Specifically, according to an embodiment of the present disclosure, a terminal can perform frequency measurement based on frequency configuration information pre-configured before configuring a network connection. According to an embodiment of the present disclosure, a terminal can immediately report frequency measurement results when configuring a network connection. Therefore, a base station according to an embodiment of the present disclosure can quickly configure carrier aggregation (CA) or dual connection (DC) in a terminal. In addition, when an RRC idle mode terminal that configures and performs early frequency measurement in RRC idle mode switches to RRC inactive mode for some reason, or when an RRC inactive mode terminal that configures and performs early frequency measurement in RRC inactive mode switches to RRC idle mode, an embodiment of the present disclosure can provide a method for effectively measuring frequency or a method for processing frequency configuration information and frequency measurement results.

[0074] The present disclosure may provide a method in which an RRC inactive mode terminal may perform frequency measurement before configuring an RRC connection to a network, and may make a fast frequency measurement result report when or immediately after configuring the RRC connection, so that a base station may quickly configure carrier aggregation (CA) or dual connectivity (DC) in the terminal.

[0075] The specific methods provided by the present disclosure can be summarized as follows.

[0076] In an embodiment of the present disclosure, a terminal in RRC connection mode can receive an RRCRelease message from a base station and can release the RRC connection. In this case, when the terminal receives frequency measurement configuration information and an indication of switching to RRC idle mode or RRC inactive mode, the terminal can perform frequency measurement in RRC idle mode or RRC inactive mode for a configured duration or time. However, information about a list of frequencies to be measured may not be included in the frequency measurement configuration information. In this case, when a cell reselection process is performed, if frequency measurement configuration information for frequency measurement of a terminal in RRC idle mode or RRC inactive mode is broadcast in a resident cell, the terminal can receive the information and can perform frequency measurement. The value of the first timer indicating the time when the terminal will perform frequency measurement can be configured based on the configured duration or time. When the duration or time to perform frequency measurement is configured in the RRCRelease message, the terminal can start the timer based on the value of the first timer. Since the time of the first timer that the terminal can perform frequency measurement from the time point when the RRCRelease message is received is limited, the battery power of the terminal can be saved.

[0077] In another method, when the terminal receives a list of frequencies to be measured in the frequency configuration information, the terminal can start the first timer. For example, when the terminal receives the RRCRelease message and the frequency configuration information includes the value of the first timer but does not include the frequency measurement list, the terminal can receive the frequency measurement list from the system information. In this case, when the terminal receives the frequency measurement list from the system information, the terminal can start the first timer. In this case, because the terminal must restart the first timer every time the terminal receives new system information, it may not be very good in saving the battery power of the terminal. However, even when the terminal moves and connects to another cell, the terminal can make a fast frequency measurement result report. When the first timer expires, the terminal can release or discard the frequency configuration information received from the RRCRelease message or system information, and can stop the frequency measurement result.

[0078] In addition, the base station can define and configure the value of the second timer by using the RRCRelease message to indicate how long the frequency measurement result value measured by the terminal is valid. For example, when the terminal receives the RRCRelease message, for the second timer running based on the value of the second timer, the terminal can store and use the timer value. The second timer can start when the terminal receives the RRCRelease message, and the terminal can determine that the frequency measurement result measured when the second timer expires is invalid and can discard the frequency measurement result. That is, the terminal may not report the frequency measurement result to the base station. In another method, the second timer can be started when the first timer expires or stops. This is because, since the frequency measurement result can be continuously updated while performing the frequency measurement, the terminal can start the second timer from the time point when the first timer expires or stops and the frequency measurement stops to indicate the effective duration of the most recent frequency measurement result. The terminal can determine that the frequency measurement result measured when the second timer expires is invalid, and the frequency measurement result can be discarded. That is, the terminal may not report the frequency measurement result to the base station. In another embodiment, the terminal can define and use the function of the second timer to be performed by the first timer.

[0079] A terminal in RRC idle mode or RRC inactive mode and receiving a RRCRelease message can perform frequency measurement based on the frequency configuration information received from the RRCRelease message or the frequency configuration information received from the system information. When a network connection is required due to the generation of uplink data or the reception of a paging message, the terminal can determine whether a fast frequency measurement result can be reported in the system information of the resident cell, and the random access process can be completed. In addition, the terminal can send message 3 (RRCSetupRequest or RRCResumeRequest) to the base station, and can receive message 4 (RRCSetup or RRCResume) from the base station in response to message 3. When the terminal sends message 5 (RRCSetupComplete or RRCResumeComplete) to the base station, the terminal can notify the presence of a fast frequency measurement result in message 5 through an indicator. In this case, the base station can send a separate message to the terminal for requesting a frequency measurement result, and the terminal can configure a separate message including a frequency measurement result in response to the message of the base station, and can send the separate message to the base station, and can release and discard the stored frequency measurement result and frequency measurement configuration information.

[0080] The present disclosure may also provide a method for more quickly measuring and reporting the frequency of the RRC inactive mode. When the terminal performs frequency measurement in the RRC inactive mode and needs to connect to the network for some reason, the terminal may perform and complete the random access process and then may send message 3 (e.g., RRCResumeRequest) to the base station. When the base station sends message 4 (e.g., RRCResume) to the terminal, the base station may cause an indicator indicating that the terminal will report the frequency measurement result to be included in message 4 (e.g., RRCResume). In another method, the indicator may be omitted because message 4 itself may indicate that the terminal will report the frequency measurement result. In this case, the terminal may recognize the indicator of message 4, may cause the frequency measurement result to be included in message 5 (e.g., RRCResumeComplete), and may send message 5. Because the RRC inactive mode terminal may restore or activate the security process (encryption and decryption or integrity protection and verification) of the signaling radio bearer SRB1 when sending the RRCResumeRequest message, the RRC inactive mode terminal may increase the security level when receiving message 4 and receive message 4, and may increase the security level when reporting the frequency measurement result of message 5 and report the frequency measurement result of message 5. In addition, the base station may cause the carrier aggregation configuration or dual connection configuration information to be included in the RRC message by using the above information, and may send the RRC message so that the terminal may quickly restart, change, or newly configure the carrier aggregation or dual connection.

[0081] Furthermore, the present disclosure may provide an efficient signaling method, in which a network or a base station may more efficiently configure or update frequency measurement configuration information in a terminal having mobility in an RRC inactive mode.

[0082] The most significant difference between an RRC idle mode terminal and an RRC inactive mode terminal is that an RRC inactive mode terminal can store terminal contexts in a base station and a terminal and can quickly configure a connection by reusing the terminal context, and an RRC inactive mode terminal can update an area in which the RRC inactive mode must be maintained from the network by periodically updating the RAN notification area.

[0083] In an embodiment of the present disclosure, when an RRC connected mode terminal receives frequency measurement configuration information and an indication of releasing the RRC connection and switching to the RRC inactive mode from a base station, in the RRC inactive mode, the terminal may perform frequency measurement within a configured duration or time. When the RRC inactive mode terminal leaves the configured RAN notification area, the RRC inactive mode terminal may configure a network connection to perform a RAN notification area update (RNAU) procedure.

[0084] In this case, according to an embodiment of the present disclosure, for a terminal that performs network connection to update a RAN notification area, the base station may configure or update a new frequency measurement configuration, or may instruct the terminal to maintain frequency measurement. The base station may retrieve the terminal context from the source base station through a connection recovery identifier indicated by the terminal in message 3) (RRCResumeRequest), and may determine whether the terminal is to perform frequency measurement configuration in RRC inactive mode. In another method, when the terminal sends message 3 to update the RAN notification area, the terminal may cause an indicator indicating that frequency measurement will be performed in RRC inactive mode, timer T331 expires or is running, or new frequency configuration information needs to be included in message 3, and message 3 may be sent to the base station to indicate the information to the base station. When the base station determines whether the terminal can perform frequency measurement in RRC inactive mode and then sends an RRC message (e.g., RRCRelease message) including information for updating the RAN notification area to the terminal, the base station may cause the new frequency measurement configuration information to be included in the RRC message, and may send and configure the RRC message. The new frequency measurement configuration information may include configuration information such as a list of frequencies to be measured, a list of physical cell identifiers, a measurement duration, or a validity area for the measurement (eg, a list of cell identifiers).

[0085] When the terminal receives the RRCRelease message during the RAN notification area update process, if the message includes fast frequency measurement configuration information, the terminal can release or discard (remove or delete) the stored frequency measurement configuration information or frequency measurement results, and can perform frequency measurement by storing, updating and applying new fast frequency measurement configuration information. In another method, when only the frequency measurement duration or the value of the timer is configured in the fast frequency measurement configuration information, the terminal can restart (or start) the timer based on the value, and can continue to perform the frequency measurement configuration while maintaining the existing frequency configuration information. Alternatively, the terminal can start the timer based on the value, can release or delete the existing frequency configuration information, can receive system information from the resident cell through the cell reselection process, and when the frequency configuration information is included in the received information, can perform frequency measurement by applying the frequency configuration information. In another method, the base station can define a new indicator in the RRCRelease message, and can indicate whether to continue to perform frequency measurement, stop frequency measurement, or release frequency measurement configuration information by using the existing frequency measurement configuration information. In another method, the terminal may release the existing frequency configuration information only when the frequency measurement configuration information is included in the RRCRelease message, and may maintain and apply the existing frequency configuration information when the frequency configuration information is not included in the RRCRelease message.

[0086] In addition, according to an embodiment of the present disclosure, when the base station or cell to which the terminal is connected can support RRC idle mode or inactive mode frequency measurement, or when the system information can indicate support for RRC idle mode or inactive mode frequency measurement, and when the frequency measurement result can be reported to the base station, the terminal can stop the timer for RRC idle mode or inactive mode frequency measurement (i.e., T331), and can discard or release the frequency measurement configuration information or discard the frequency measurement result.

[0087] In addition, according to an embodiment of the present disclosure, an RRC inactive mode or RRC idle mode terminal may configure a separate area (e.g., a validity area) for performing frequency measurement. That is, according to an embodiment of the present disclosure, the terminal may perform frequency measurement in RRC inactive mode or RRC idle mode only within the validity area, and when outside the validity area, the terminal may stop the timer, may release the frequency measurement configuration information, may discard the frequency measurement result, or may stop the frequency measurement. The validity area may be indicated by a list of physical cell identifiers or a list of RAN notification area indicators. An embodiment of the present disclosure may provide a method for separately configuring a validity area and a RAN notification area in an RRC inactive mode terminal, and a method for allowing an RRC inactive mode terminal to use a RAN notification area instead of a validity area (or use a validity area instead of a RAN notification area) by using an indicator to reduce the burden on the terminal and reduce signaling overhead. This is because, when a separate validity area is indicated to the terminal, the terminal may have the burden of maintaining and updating a tracking area, maintaining and updating a RAN notification area, and maintaining and managing a validity area.

[0088] In addition, according to an embodiment of the present disclosure, when frequency measurement configuration information is indicated to an RRC inactive mode or RRC idle mode terminal, the base station may configure a separate timer according to a frequency configuration group or a radio access technology, or for each frequency, cell, or beam. That is, according to an embodiment of the present disclosure, a duration or timer value indicating how long frequency measurement will be performed for an LTE frequency (each frequency or cell) may be configured separately, a duration or timer value indicating how long frequency measurement will be performed for an NR frequency (each frequency, cell, or beam) may be configured separately, and a separate timer and a separate duration may be configured for each frequency configuration group.

[0089] In addition, an embodiment of the present disclosure may provide a method for processing frequency measurement configuration information or frequency measurement results according to a state change of an RRC inactive mode and determining whether to continue to perform a frequency measurement operation. That is, an embodiment of the present disclosure may specifically provide a terminal operation when the terminal is converted from an RRC inactive mode to an RRC idle mode.

[0090] Figure 1A is a diagram showing a structure of an LTE system according to an embodiment of the present disclosure.

[0091] See also Figure 1AThe radio access network of the LTE system may include evolved node Bs (ENBs) (node ​​Bs or base stations) 1a-05, 1a-10, 1a-15, and 1a-20, a mobility management entity (MME) 1a-25, and a serving gateway (S-GW) 1a-30. A user equipment (UE) 1a-35 may be connected to an external network through the ENBs 1a-05, 1a-10, 1a-15, and 1a-20 and the S-GW 1a-30.

[0092] In 1a in FIG. 1, each of ENBs 1a-05, 1a-10, 1a-15, and 1a-20 may correspond to an existing Node B of a Universal Mobile Telecommunications System (UMTS). Each ENB may be connected to UE 1a-35 via a radio channel and may perform more complex functions than an existing Node B. Because all user traffic data including real-time services such as Voice over Internet Protocol (VoIP) are served by a shared channel in an LTE system, an entity for collecting and scheduling buffer status information, available transmission power status information, and channel status information of UEs may be required. And each of ENBs 1a-05 to 1a-20 may be used as such an entity. One ENB may generally control multiple cells. For example, in order to achieve a data rate of 100Mbps, an LTE system may use orthogonal frequency division multiplexing (OFDM) with a bandwidth of 20MHz as a radio access technology. In addition, adaptive modulation and coding (AMC) for determining a modulation scheme and a channel coding rate according to the channel state of UE 1A-35 may be applied. The S-GW 1a-30 is an entity for providing a data bearer, and may generate or remove a data bearer under the control of the MME 1a-25. The MME 1a-25, which is an entity for performing various control functions and a mobility management function on the UE 1a-35, may be connected to a plurality of ENBs.

[0093] Figure 1B is a diagram showing a radio protocol architecture in an LTE system according to an embodiment of the present disclosure.

[0094] See also Figure 1B The wireless protocol architecture of the LTE system includes the packet data convergence protocol (PDCP) layers 1b-05 and 1b-40, the radio link control (RLC) layers 1b-10 and 1b-35, and the medium access control (MAC) layers 1b-15 and 1b-30 for the UE and ENB, respectively. The PDCP layers 1b-05 and 1b-40 may be responsible for, for example, IP header compression / decompression. The main functions of each PDCP layer can be summarized as follows.

[0095] -Header compression and decompression: Robust Header Compression (ROHC) only

[0096] -Transfer user data

[0097] - In-sequence delivery of upper layer packet data units (PDUs) during PDCP re-establishment for RLC Acknowledged Mode (AM)

[0098] - For split bearers in DC (supports RLC AM only): PDCP PDU routing for transmission and PDCP PDU reordering for reception

[0099] - Duplicate detection of lower layer service data units (SDUs) during PDCP re-establishment for RLC AM

[0100] - Retransmit PDCP SDUs at handover and, for split bearers in DC, retransmit PDCP PDUs during PDCP data recovery for RLC AM

[0101] -Encryption and decryption

[0102] - Timer-based SDU discard in uplink

[0103] Each of the RLC layers 1b-10 and 1b-35 may perform an automatic repeat request (ARQ) operation by reconfiguring a PDCP packet data unit (PDU) to an appropriate size. The main functions of each RLC layer may be summarized as follows.

[0104] -Transmission of upper layer PDU

[0105] - Error correction via ARQ (for AM data transmission only)

[0106] - Concatenation, segmentation and reassembly of RLC SDUs (only for Unacknowledged Mode (UM) and AM data transmission)

[0107] - Re-segmentation of RLC data PDU (for AM data transmission only)

[0108] - Reordering of RLC data PDUs (only for UM and AM data transmission)

[0109] - Duplicate detection (for UM and AM data transmission only)

[0110] -Protocol error detection (for AM data transmission only)

[0111] -RLC SDU discard (only for UM and AM data transmission)

[0112] -RLC reconstruction

[0113] The MAC layers 1b-15 and 1b-30 are connected to various RLC layers configured in one UE and can multiplex RLC PDUs into MAC PDUs and demultiplex RLC PDUs from MAC PDUs. The main functions of each MAC layer can be summarized as follows.

[0114] - Mapping between logical channels and transport channels

[0115] - Multiplexing / demultiplexing MAC SDUs belonging to one or different logical channels into / from a transport block (TB) on a transport channel delivered to the physical layer

[0116] -Dispatch information report

[0117] - Error correction through Hybrid ARQ (HARQ)

[0118] - Priority handling between logical channels of a UE

[0119] - Prioritization between UEs through dynamic scheduling

[0120] -Multimedia Broadcast / Multicast Service (MBMS) logo

[0121] -Transmission format selection

[0122] -filling

[0123] Each of the physical (PHY) layers 1b-20 and 1b-25 can channel-code and modulate upper layer data into OFDM symbols and send the OFDM symbols through a radio channel, or demodulate and channel-decode OFDM symbols received through a radio channel and deliver the OFDM symbols to an upper layer.

[0124] Figure 1C is a diagram showing a structure of a next-generation mobile communication system (e.g., an NR system or a 5G communication system) according to an embodiment of the present disclosure.

[0125] See also Figure 1C , a radio access network of a next generation mobile communication system (e.g., NR or 5G system) may include a new radio node B (NR gNB or NR base station) 1c-10 and a new radio core network (NR CN) 1c-05. A new radio user equipment (NR UE) 1c-15 may be connected to an external network through the NR gNB 1c-10 and the NR CN 1c-05.

[0126] exist Figure 1C,NRgNB 1c-10 corresponds to the evolved Node B (eNB) of the existing LTE system. NR gNB 1c-10 can be connected to NR UE 1c-15 through a wireless channel and can provide better services than the existing Node B. Because all user service data are served through shared channels in the next generation mobile communication system, an entity for collecting and scheduling the buffer status information, available transmission power status information and channel status information of the UE may be required, and NR gNB 1c-10 can be used as such an entity. One NR gNB can generally control multiple cells. The next generation mobile communication system can currently have a bandwidth greater than the maximum bandwidth of the existing LTE to achieve ultra-high data rates, orthogonal frequency division multiplexing (OFDM) can be used as a radio access technology, and beamforming technology can be used in addition. In addition, adaptive modulation and coding (AMC) for determining the modulation scheme and channel coding rate according to the channel state of the NRUE 1c-15 can be applied. NR CN 1c-05 can perform functions such as mobility support, bearer configuration, and quality of service (QoS) configuration. NR CN 1c-05, which is an entity for performing various control functions and mobility management functions on NRUE 1c-15, can be connected to multiple base stations. In addition, the next-generation mobile communication system can cooperate with the existing LTE system, and NR CN 1c-05 can be connected to MME 1c-25 through a network interface. MME 1c-25 can be connected to eNB 1c-30, which is an existing base station.

[0127] Figure 1D is a diagram illustrating a radio protocol architecture of a next generation mobile communication system according to an embodiment of the present disclosure.

[0128] See also Figure 1D The radio protocol architecture of the next generation mobile communication system may include NR Service Data Adaptation Protocol (SDAP) layers 1d-01 and 1d-45, NR PDCP layers 1d-05 and 1d-40, NR RLC layers 1d-10 and 1d-35, and NR MAC layers 1d-15 and 1d-30 for UE and NR gNB.

[0129] The main functions of each of the NR SDAP layers 1d-01 and 1d-45 may include some of the following functions.

[0130] -Transmission of user plane data

[0131] - Mapping between QoS flows and Data Radio Bearers (DRBs) for both DL and UL

[0132] - Marking QoS flow identifier (ID) in DL and UL packets

[0133] -Reflective QoS flow to DRB mapping for UL SDAP PDU

[0134] For the SDAP layer, information indicating whether to use the header of the SDAP layer or the function of the SDAP layer can be configured for the UE by using a radio resource control (RRC) message per PDCP layer, per bearer, or per logical channel. When configuring the SDAP header, the SDAP layer can instruct the UE to update or reconfigure the uplink and downlink QoS flows and data bearer mapping information by using a 1-bit non-access stratum (NAS) reflected QoS indicator and a 1-bit access stratum (AS) reflected QoS indicator of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used as data processing priority information or scheduling information to smoothly support services.

[0135] The main functions of each of the NR PDCP layers 1d-05 and 1d-40 may include some of the following functions.

[0136] -Header compression and decompression: ROHC only

[0137] -Transfer user data

[0138] - In-sequence delivery of upper layer PDUs

[0139] - Out-of-order delivery of upper layer PDUs

[0140] - Reordering of received PDCP PDUs

[0141] - Duplicate detection of lower layer SDU

[0142] -Retransmission of PDCP SDU

[0143] -Encryption and decryption

[0144] - Timer-based SDU discard in uplink

[0145] In the above description, the reordering function of the NR PDCP layer may refer to a function of reordering the PDCP PDU received from the lower layer based on the PDCP sequence number (SN), and may include a function of delivering the reordered data to the upper layer in sequence or out of sequence, a function of recording the lost PDCP PDU by reordering the received PDCP PDU, a function of reporting the status information of the lost PDCP PDU to the transmitter, and a function of requesting retransmission of the lost PDCP PDU.

[0146] The main functions of each of the NR RLC layers 1d-10 and 1d-35 may include some of the following functions.

[0147] -Transmission of upper layer PDU

[0148] - In-sequence delivery of upper layer PDUs

[0149] - Out-of-order delivery of upper layer PDUs

[0150] - Error correction via ARQ

[0151] - Concatenation, segmentation and reassembly of RLC SDU

[0152] - Re-segmentation of RLC data PDUs

[0153] - Reordering of RLC data PDUs

[0154] - Duplicate detection

[0155] -Protocol error detection

[0156] RLC SDU discarded

[0157] RLC Reconstruction

[0158] In the above description, the in-sequence delivery function of the NR RLC layer may refer to a function of sequentially delivering RLC SDUs received from a lower layer to an upper layer, and may include at least one of the following functions: a function of reassembling a plurality of RLC SDUs segmented from one RLC SDU and delivering the reassembled RLC SDU when the segmented RLC SDU is received, a function of reordering the received RLC PDU based on the RLC SN or the PDCP SN, a function of recording lost RLC PDUs by reordering the received RLC PDUs, a function of reporting status information of lost RLC PDUs to a transmitter, a function of requesting retransmission of lost RLC PDUs, a function of delivering only the RLC SDUs preceding the lost RLC SDUs to the upper layer in sequence when there are lost RLC SDUs, and a function of delivering all RLC SDUs received before the timer is started in sequence to the upper layer despite the presence of lost RLC SDUs when a certain timer expires, or a function of delivering all RLC SDUs received until the current time in sequence to the upper layer despite the presence of lost RLC SDUs when a certain timer expires. In addition, the NR RLC layer may process the RLC PDU in the order of reception (in the order of arrival regardless of the SN) and deliver the RLC PDU to the PDCP layer out of order (out of order delivery), or reassemble the segmented RLC PDUs received or stored in the buffer into a whole RLC PDU, process it, and deliver the RLC PDU to the PDCP layer. The NR RLC layer may not have a cascading function, and the cascading function may be performed by the NR MAC layer, or may be replaced by a multiplexing function of the NR MAC layer.

[0159] In the above description, the out-of-order delivery function of the NR RLC layer refers to a function of directly delivering the RLC SDU received from the lower layer to the upper layer out of order, and may include a function of reassembling multiple RLC SDUs segmented from one RLC SDU when a segmented RLC SDU is received and delivering the reassembled RLC SDU, and a function of recording a lost RLC PDU and reordering the received RLC PDU by storing the RLC SN or PDCP SN of the received RLC PDU.

[0160] Each of the NR MAC layers 1d-15 and 1d-30 can be connected to multiple NR RLC layers configured for one UE, and the main functions of each NR MAC layer can include some of the following functions.

[0161] - Mapping between logical channels and transport channels

[0162] -Multiplexing / demultiplexing of MAC SDU

[0163] -Dispatch information report

[0164] - Error correction through HARQ

[0165] - Priority handling between logical channels of a UE

[0166] - Prioritization between UEs through dynamic scheduling

[0167] -MBMS service logo

[0168] -Transmission format selection

[0169] -filling

[0170] Each of the NR PHY layers 1d-20 and 1d-25 can channel-code and modulate upper layer data into OFDM symbols and send the OFDM symbols through a radio channel, or can demodulate and channel-decode OFDM symbols received through a radio channel and deliver the OFDM symbols to an upper layer.

[0171] In the next generation mobile communication system, the UE may perform frequency measurement while performing a cell reselection process in RRC idle mode. The frequency measurement performed by the UE when performing the cell reselection process may refer to intra-frequency measurement, serving cell measurement, or primary cell (Pcell) measurement of a frequency broadcast in a camped cell or a frequency configured by a gNB. However, in addition to intra-frequency measurement or serving cell measurement, the UE may not perform inter-frequency measurement and may not report the frequency measurement results to the network separately.

[0172] That is, when the UE finds a suitable cell by performing a cell reselection procedure, camps on a suitable cell, and then transitions to an RRC connected mode by performing an RRC connection configuration procedure, the gNB may perform configuration of measurements on the RRC connected mode UE. In this case, the gNB may configure at least one of the following for the UE: which frequencies (e.g., a frequency list) or which frequency bands to measure, in what order to use the priority of each frequency to perform the measurement, which beam to measure, which filtering method is used to measure the strength of the frequency when measuring the frequency (e.g., L1 filtering, L2 filtering, L3 filtering, or a calculation method using a coefficient), which event or condition is used to start the measurement when measuring the frequency, which criterion is used to perform the measurement compared to the current serving cell (or the frequency currently camped on), which event or condition is used to report the measured frequency result, which criterion or condition is to be satisfied to report the frequency compared to the current serving cell (or the frequency currently camped on), or which period is used to report the frequency measurement result. The UE may measure the corresponding frequency according to the frequency configuration configured by the gNB, and may report the frequency measurement result to the gNB according to the corresponding event or condition. The gNB can determine whether to apply frequency carrier aggregation or dual connectivity to the UE by using the frequency measurement results received from the UE.

[0173] An embodiment of the present disclosure may provide a method in which a UE may perform frequency measurement in an RRC idle mode or an RRC inactive mode before transitioning to an RRC connected mode, indicate the measurement result to a gNB when the UE may configure a network connection, and may quickly report the frequency measurement result by entering an RRC connected mode in a next generation mobile communication system. Based on the method, the gNB may quickly configure frequency carrier aggregation or dual connectivity in the UE based on the result of the measurement by the UE in the RRC idle mode or the RRC inactive mode.

[0174] Specifically, when the gNB converts an RRC connected mode UE configured with a network connection to an RRC idle mode or an RRC inactive mode, the gNB may configure frequency information of the frequency to be measured in the RRC idle mode or the RRC inactive mode, and time (or duration) information of the frequency to be measured by the UE in the RRC idle mode or the RRC inactive mode, or area information (or a list of cells) of the area in which the UE is to measure the frequency in the RRC idle mode or the RRC inactive mode in the RRC message, and may instruct the UE to perform frequency measurement in the RRC idle mode or the RRC inactive mode. In addition, whenever the UE moves, the UE may read the system information of the new resident cell by performing a cell reselection operation. The UE may perform a process of determining whether to continue or end frequency measurement in the RRC idle mode or the RRC inactive mode, extend the measurement duration (e.g., restart the timer), report the frequency measurement result, or discard the frequency measurement result according to the system information. The next generation mobile communication system according to an embodiment of the present disclosure may provide efficient UE operation through the above-mentioned operation.

[0175] Examples of the bearers of the present disclosure may include a signaling radio bearer (SRB) and a data radio bearer (DRB). An UMDRB may refer to a DRB using an RLC layer operating in an unacknowledged mode (UM), and an AM DRB may refer to a DRB using an RLC layer operating in an acknowledged mode (AM).

[0176] Figure 1E is a diagram for describing a process of UE configuring carrier aggregation in a next generation mobile communication system according to an embodiment of the present disclosure.

[0177] See also Figure 1E , a process of configuring a UE to switch from an RRC idle mode or an RRC inactive mode to an RRC connected mode and carrier aggregation in a next generation mobile communication system will be described.

[0178] For specific reasons, the gNB may convert an RRC connected mode UE configured with a network connection to an RRC idle mode or an RRC inactive mode. In an embodiment of the present disclosure, the specific reasons may include a lack of scheduling resources of the gNB, or suspending data transmission / reception to / from the UE for a specific period of time.

[0179] In operation 1e-05, the gNB may send an RRCRelease (RRC release) message to the UE, and may indicate the UE to be in RRC idle mode or RRC inactive mode. The gNB may indicate the UE to transition to RRC inactive mode by using an indicator (suspend-config) in the RRCRelease message, and when the indicator (suspend-config) is not included in the RRCRelease message, the UE may transition to RRC idle mode. Therefore, in operation 1e-10, the UE may transition to RRC idle mode or RRC inactive mode.

[0180] When a network connection is required for some reason, in operations 1e-15 and 1e-20, the UE transitioning to RRC idle mode or RRC inactive mode may perform a random access procedure and may receive a random access response. In addition, in operations 1e-25 to 1e-40, the UE may request an RRC connection configuration and may perform an RRC connection configuration by receiving an RRC message.

[0181] More specifically, in operation 1e-25, the UE may establish backward transmission synchronization with the gNB through a random access procedure, and may send an RRCSetupRequest message to the gNB. The RRCSetupRequest message may include a cause (establishmentCause) for configuring a connection to the UE's identifier.

[0182] In operation 1e-30, the gNB may send an RRCSetup message so that the UE configures the RRC connection. The RRCSetup message may include at least one of configuration information for each logical channel, configuration information for each bearer, configuration information of the PDCP layer, configuration information of the RLC layer, or configuration information of the MAC layer.

[0183] The gNB may assign a bearer identifier (e.g., an SRB identifier or a DRB identifier) ​​to each bearer by using an RRCSetup message, and may indicate the PDCP layer configuration, RLC layer configuration, MAC layer configuration, and PHY layer configuration for each bearer. In addition, the gNB may configure the length of the PDCP sequence number used in the PDCP layer (e.g., 12 bits or 18 bits) for each bearer, and may configure the length of the RLC sequence number used in the RLC layer (e.g., 16 bits, 12 bits, or 18 bits) in the RRCConnectionSetup message. In addition, the gNB may indicate whether to use the header compression and decompression protocol for each bearer in the uplink or downlink of the PDCP layer, and may indicate whether to perform integrity protection or authentication procedures in the RRCConnectionSetup message. In addition, the gNB may indicate whether to perform an out-of-order delivery function in the PDCP layer.

[0184] At operation 1e-40, the UE configuring the RRC connection may send an RRCSetupComplete message to the gNB. The RRCSetupComplete message may include a SERVICE REQUEST message, which is a control message by which the UE requests an access and mobility management function (AMF) or a mobility management entity (MME) for bearer configuration for a service. The gNB may send a SERVICE REQUEST message included in the RRCConnectionSetupComplete message to the AMF or MME, and the AMF or MME may determine whether to provide the service requested by the UE.

[0185] When the AMF or MME determines to provide the service requested by the UE, the AMF or MME may send an INITIALCONTEXT SETUP REQUEST message to the gNB. The INITIALCONTEXT SETUP REQUEST message may include information such as quality of service (QoS) information to be applied when configuring a data radio bearer (DRB) and security-related information (e.g., security keys or security algorithms) to be applied to the DRB.

[0186] In operation 1e-45, the gNB may send / receive a SecurityModeCommand message and a SecurityModeComplete message to configure security with the UE, and when the security configuration is completed, the gNB may send an RRCConnectionReconfiguration message to the UE.

[0187] The gNB may assign a bearer identifier (e.g., an SRB identifier or a DRB identifier) ​​to each bearer by using an RRCConnectionReconfiguration message, and may indicate the PDCP layer configuration, RLC layer configuration, MAC layer configuration, and PHY layer configuration for each bearer. In addition, the gNB may configure the length of the PDCP sequence number used in the PDCP layer (e.g., 12 bits or 18 bits) for each bearer, and may configure the length of the RLC sequence number used in the RLC layer (e.g., 6 bits, 12 bits, or 18 bits) in the RRCConnectionReconfiguration message. In addition, the gNB may indicate whether to use a header compression and decompression protocol for each bearer in the uplink or downlink of the PDCP layer, and may indicate whether to perform integrity protection or authentication procedures in the RRCConnectionSetup message. In addition, the gNB may indicate whether to perform an out-of-order delivery function in the PDCP layer.

[0188] Moreover, the RRCConnectionReconfiguration message may include configuration information of the DRB to process user data. In operation 1e-45, the UE may configure the DRB by applying the information and may send an RRCConnectionReconfigureComplete message to the gNB.

[0189] In operation 1e-50, the gNB that completes the DRB configuration with the UE may send an INITIAL CONTEXT SETUP COMPLETE message to the AMF or MME, and the connection may be completed.

[0190] When the above process is completed, the UE can send / receive data to / from the gNB through the core network. According to some embodiments of the present disclosure, the data transmission process generally includes three steps: RRC connection configuration, security configuration, and DRB configuration.

[0191] In addition, in operation 1e-65, for some reason, the gNB may send an RRCConnectionReconfiguration message to the UE to newly add or change the configuration. The gNB may configure frequency configuration information (e.g., a list of frequencies to be measured, a duration for measuring the frequencies, conditions for measuring the frequencies, conditions for measuring and reporting the frequencies, and a cell identifier for reporting the frequencies) of the frequencies to be measured by the UE by using the RRCConnectionReconfiguration message.

[0192] The UE may perform frequency measurement according to the frequency measurement configuration information. In operation 1e-60, when a specific condition is met (for example, when the strength of the signal of a specific frequency is greater than a given value (for example, a threshold), or when the strength of the signal of the current serving cell (frequency) is less than a given value (for example, a threshold)), the UE may report the frequency measurement result to the gNB.

[0193] In operation 1e-65, when the gNB receives the frequency measurement result, the gNB may cause the Scell ​​configuration information to be included in the RRCReconfiguration message based on the frequency measurement result, may send the RRCReconfiguration message to the UE, may configure an additional Scell, and may configure carrier aggregation in the UE. In addition, the gNB may cause the secondary cell group configuration information to be included in the RRCReconfiguration message, may send the RRCReconfiguration message to the UE, and may configure dual connectivity in the UE. When the gNB configures carrier aggregation in the UE, in operations 1e-70 to 1e-75, the gNB may transition the configured Scell ​​to an active or inactive or idle state by using a MAC control element (CE).

[0194] According to an embodiment of the present disclosure, the process of gNB configuring carrier aggregation or dual connectivity in UE can be summarized as follows. First, when the UE configures a connection to the gNB and the gNB configures frequency measurement configuration information in the RRC connected mode UE, the UE can perform frequency measurement based on the frequency measurement configuration information and can report the measurement result to the gNB. The gNB can configure configuration information for additional Scell ​​in an RRC message to configure carrier aggregation in the UE based on the frequency measurement result of the UE, and can activate, idle, or deactivate the Scell ​​by sending a MAC CE. In addition, the gNB can configure additional cell group configuration information based on the frequency measurement result of the UE to configure dual connectivity in the UE.

[0195] When the gNB configures carrier aggregation or dual connectivity in the UE as described above, if the UE first enters the RRC connected mode, receives frequency configuration information, performs frequency measurement, and needs to report the frequency measurement, the measurement report may be performed very late, and the carrier aggregation or dual connectivity may be configured very late. Therefore, in order to solve this problem, an embodiment of the present disclosure may enable the UE to effectively perform frequency measurement in the RRC idle mode or the RRC inactive mode, and report the frequency measurement result once the network connection is configured.

[0196] Figure 1F is a diagram for describing a method in which a UE performs early frequency measurement and makes a fast frequency measurement result report in a next generation mobile communication system according to an embodiment of the present disclosure.

[0197] Specifically, refer to Figure 1F According to an embodiment of the present disclosure, the UE can perform early frequency measurement in RRC idle mode or RRC inactive mode, and can make a fast frequency measurement result report.

[0198] In the first embodiment of the present disclosure, when the gNB configures frequency measurement configuration information for enabling the UE to perform frequency measurement in RRC idle mode or RRC inactive mode through an RRCRelease message in the UE, the gNB may configure multiple frequency measurement groups, and the UE may perform frequency measurement in RRC idle mode or RRC inactive mode.

[0199] In addition, an embodiment of the present disclosure may provide a method in which, when the gNB indicates frequency measurement configuration information to an RRC inactive mode or RRC idle mode UE, the gNB may configure a separate frequency measurement list or a separate timer according to a frequency configuration group or a radio access technology (or for each cell or each beam). That is, an embodiment of the present disclosure may provide a method in which a separate timer may be configured according to each frequency configuration group, and a separate duration may be configured according to each frequency configuration group, by configuring a duration or a timer value for frequency measurement to be performed for LTE frequency (for each frequency or each cell), and configuring a duration or a timer value for frequency measurement to be performed for NR frequency (for each frequency, each cell, or each beam). That is, according to an embodiment of the present disclosure, a timer may be run for each frequency group, and frequency measurement may be performed until the timer expires. When a separate timer may be configured for each radio access technology, each cell, or each cell beam, the frequency measurement duration may vary according to frequency characteristics, beam characteristics, or cell characteristics, thereby optimizing battery consumption of the UE.

[0200] In the first embodiment of the present disclosure, a UE capable of performing frequency measurement and making a fast frequency measurement result report in an RRC idle mode or an RRC inactive mode may correspond to one or more of the following UEs.

[0201] 1. All UEs with the capability to support the method of performing early frequency measurement and fast frequency measurement result reporting in RRC idle mode or RRC inactive mode

[0202] 2. A UE that is in RRC idle mode or inactive mode and receives configuration information indicating that frequency measurement is to be performed in RRC idle mode or RRC inactive mode when the UE is transitioned from RRC connected mode to RRC idle mode or RRC inactive mode by the gNB through an RRC message. For example, a UE that is configured with frequency configuration information for performing frequency measurement in RRC idle mode or RRC inactive mode, measurement duration (e.g., timer value), or area configuration information (e.g., a list of cell identifiers) for performing frequency measurement

[0203] See also Figure 1F , in operation 1f-05, a UE in RRC connected mode may be transitioned to RRC idle mode or RRC inactive mode by the gNB due to some reason (e.g., no data transmission / reception for a certain period of time).

[0204] In operation 1f-10, when the gNB converts the mode of the UE, the gNB may send an RRC message. For example, the gNB may send an RRCRelease message (indicating a transition to RRC idle mode) or an RRCRelease message (indicating a transition to RRC inactive mode) including a suspend-config. When the UE performs fast (early) frequency measurement in RRC idle mode or RRC inactive mode, the RRC message may include the following information or some information to be applied.

[0205] - Frequency configuration information of the frequencies to be measured in RRC idle mode or RRC inactive mode

[0206] 1. Frequency configuration information

[0207] A. LTE frequency measurement information group or list (Evolved Universal Terrestrial Radio Access (EUTRA) frequency configuration information / list / group)

[0208] i. The LTE frequency measurement information group or list may include frequency measurement configuration information (early measurement settings), such as which frequencies or frequency bands are to be measured (e.g., a frequency list), which order is to be used to perform measurements by configuring the priority of each frequency, which filtering method is to be used to measure the strength of the frequency when measuring the frequency (e.g., L1 filtering, L2 filtering, L3 filtering method, or a calculation method using a coefficient), which event or condition is used to start measurement when measuring the frequency, which criterion (e.g., when the signal strength is equal to or greater than the indicated threshold) is used to perform and report the measurement compared to the current serving cell (or the frequency currently camped on), which event or condition is used to report the measured frequency results, which criterion or condition is to be met to report the frequency compared to the current serving cell (or the frequency currently camped on), or which period will be used to report the frequency measurement results.

[0209] B.NR frequency measurement information group or list (NR frequency configuration information / list / group)

[0210] i. The NR frequency measurement information group or list may include frequency measurement configuration information (early measurement settings), such as which frequencies or which frequency bands are to be measured (e.g., a frequency list), which order is to be used to perform measurements by configuring the priority of each frequency (each synchronization signal block (SSB)), SSB transmission resources (frequency and time resources, beam identifier or beam indicator), or SSB identifier information of each frequency, which filtering method is used to measure the strength of the frequency when measuring the frequency (e.g., L1 filtering, L2 filtering, L3 filtering method, or calculation method using coefficients), which event or condition is used to start measurement when measuring the frequency, which criterion (e.g., when the strength of the signal is equal to or greater than an indicated threshold) is used to perform and report measurement compared to the current serving cell (or the frequency currently camped on), which event or condition will be used to report the measured frequency results, which criterion or condition is to be met to report the frequency compared to the current serving cell (or the frequency currently camped on), or which period will be used to report the frequency measurement results.

[0211] 2. The timer value (e.g., T331) for performing frequency measurement or the duration for performing frequency measurement in RRC idle mode or RRC inactive mode, or the timer for LTE frequency and the timer for NR frequency can be configured separately. Since the LTE frequency characteristics (low frequency band) and the NR frequency characteristics (high frequency band) are different from each other, the battery power of the UE can be saved by adjusting the frequency measurement time of the UE separately. For example, when it is indicated in RRCRelease that the frequency is measured in RRC idle mode or RRC inactive mode, the frequency measurement can be performed when the timer is started and running, and the frequency measurement can be stopped when the timer expires.

[0212] 3. Validity area information for performing frequency measurement in RRC idle mode or RRC inactive mode. For example, when a list of physical cell identifiers (PCIDs) is indicated and the UE is in a cell indicated in the validity area information, the frequency measurement may be performed, and when the UE is outside the validity area information, the frequency measurement may be stopped. For example, when the UE is outside the validity area information, the timer may be stopped and the frequency measurement may be stopped. In addition, in another method, when the UE transitions to the RRC inactive mode, the gNB may determine whether to use the RAN notification area as the validity area by using an indicator. For example, when the gNB indicates to the UE transitioning to the RRC inactive mode that the RAN notification area is used as the validity area through an indicator, the UE may perform frequency measurement within the RAN notification area while maintaining the RRC inactive mode within the RAN notification area. In another method, the gNB may indicate that the validity area is used as the RAN notification area through an indicator. In another method, even when there is no indicator in the RRC inactive mode, the UE may operate by regarding the RAN notification area as the validity area, and in the RRC active mode, the gNB may configure a separate validity area in the UE. Since both the RAN notification area and the validity area are indicated by using a cell identifier list in an RRC message, signaling overhead can be reduced by the above method, and since the UE does not need to manage the validity area separately, the burden on the UE can be reduced.

[0213] 4. A measurement reporting threshold may be configured, and multiple frequencies in the configured frequency group having a signal strength greater than the threshold may be reported.

[0214] In addition, the gNB may define and configure the value of the second timer in the RRCRelease message, and may indicate how long the frequency measurement result value measured by the UE is valid. For example, for the second timer running based on the value of the second timer, the UE may store and use the timer value when receiving the RRCRelease message. The second timer may be started when the UE receives the RRCRelease message, and when the second timer expires, the UE may determine that the measured frequency measurement result is invalid and may discard the measured frequency measurement result. That is, the UE may not report to the gNB. In another method, the second timer may be started when the first timer expires or stops. This is because, since the frequency measurement result can be updated while performing the frequency measurement, the effective duration of the latest frequency measurement result can be indicated by starting the second timer from the time point when the first timer expires or stops to stop the frequency measurement. When the second timer expires, the UE may determine that the measured frequency measurement result is invalid and may discard the measured frequency measurement result. That is, the UE may not report to the gNB. In another method, the UE or the gNB may define and use the first timer to perform the function of the second timer.

[0215] When the RRCRelease message is received and the fast frequency measurement configuration information is included, the UE may release or discard the stored frequency measurement configuration information or the frequency measurement result, and may perform frequency measurement by storing, updating and applying the new fast frequency measurement configuration information. In another method, when only the frequency measurement duration or the timer value is configured in the fast frequency measurement configuration information, the UE may restart the timer based on the value, and may continue the frequency measurement configuration while maintaining the existing frequency configuration information. Alternatively, the UE may start the timer based on the value, may release the existing frequency configuration information, may receive the system information in the cell where it resides through the cell reselection process, and may perform frequency measurement by applying the frequency configuration information when there is frequency configuration information. In another method, the gNB may define a new indicator in the RRCRelease message, and may indicate whether to continue the frequency measurement, stop the frequency measurement, or release the frequency measurement configuration information by using the existing frequency measurement configuration information. In another method, the UE may release the existing frequency configuration information only when the frequency measurement configuration information is included in the RRCRelease message, and when there is no frequency configuration information, the UE may maintain and apply the existing frequency configuration information.

[0216] In operation 1f-30, when the UE performs early frequency measurement in RRC idle mode or RRC inactive mode, the condition for starting the frequency measurement may satisfy at least one of the following conditions.

[0217] 1. When the UE receives an RRCRelease message including an indicator for performing frequency measurement in RRC idle mode or RRC inactive mode, and configures a duration for measuring the frequency (e.g., a timer value) and frequency information of the frequency to be measured, the UE may start a timer and may perform frequency measurement based on the frequency information.

[0218] 2. When the UE receives the RRCRelease message, including an indicator for performing frequency measurement in RRC idle mode or RRC inactive mode, and configuring the duration (e.g., timer value) for measuring the frequency, but not including the frequency information of the frequency to be measured, the UE may start the timer, and when the frequency information of the frequency to be measured in the RRC idle mode or RRC inactive mode is broadcast in the system information, the UE may perform frequency measurement according to the frequency information. When the UE may move to another cell, if the frequency information of the frequency to be measured in the RRC idle mode or RRC inactive mode is broadcast in the system information of the new cell where it resides, the UE may perform frequency measurement according to the new frequency information.

[0219] That is, when the frequency measurement configuration information for performing frequency measurement in RRC idle mode or RRC inactive mode is not configured in the RRCRelease message, if the frequency configuration information for frequency measurement in RRC idle mode or RRC inactive mode is broadcast in the system information, the UE can perform frequency measurement in RRC idle mode or RRC inactive mode based on the frequency configuration information.

[0220] Referring to operation 1f-12, when the UE moves and camps on a new cell, the UE may update the frequency measurement information to the frequency configuration information for RRC idle mode or RRC inactive mode frequency measurement broadcast in the new cell, and may perform frequency measurement again.

[0221] However, when frequency measurement configuration information for performing frequency measurement in RRC idle mode or RRC inactive mode is configured in the RRCRelease message, the UE may perform frequency measurement by preferentially applying the frequency measurement configuration information configured in the RRCRRese message to the RRC idle mode or RRC inactive mode frequency measurement information broadcast in the system information. That is, when frequency measurement configuration information for performing frequency measurement in RRC idle mode or RRC inactive mode is configured in the RRCRelease message, the UE may not reflect or consider, or may discard, the frequency configuration information broadcast in the system information.

[0222] As described above, the UE may start fast (early) frequency measurement according to at least one of the above conditions. In operation 1f-35, the UE may send message 3 (RRCSetupRequest or RRCResumeRequest (RRC recovery request)) to the gNB while performing frequency measurement. In operation 1f-40, the UE may receive message 4 (e.g., RRCSetup or RRCResume (RRC recovery)) from the gNB in ​​response to message 3, and may determine that the random access procedure has been successful. In operation 1f-45, the UE may transition to RRC connected mode.

[0223] When an indicator indicating support for RRC idle mode or RRC inactive mode frequency measurement or an indicator indicating that RRC idle mode or RRC inactive mode frequency measurement results can be received is broadcast in received system information (e.g., SIB2) before a connection is configured in the current cell, the UE may notify the gNB through the indicator that there are frequency measurement results measured in the RRC idle mode or RRC inactive mode in message 5 (e.g., RRCSetupComplete or RRCResumeComplete (RRC recovery complete)).

[0224] In operation 1f-50, when the UE sends message 5 (e.g., RRCSetupComplete or RRCResumeComplete), the UE may cause an indicator indicating that early frequency measurement has been performed in RRC idle mode or RRC inactive mode and that there is a frequency measurement result to be reported to be included in message 5, and message 5 may be sent. In message 5, a new indicator may be defined in message 5 to indicate the presence of a fast frequency measurement result, or an indicator indicating the presence of previously defined UE information in an RRC message (RRCSetupComplete or RRCResumeComplete) may be reused. In another method, in system information, an indicator may be defined and used as an indicator indicating LTE frequency measurement support or NR frequency measurement support. In addition, when message 5 indicates that there is a frequency measurement result measured in RRC idle mode or RRC inactive mode, an indicator of the measurement result of the LTE frequency and an indicator of the measurement result of the NR frequency may be defined and indicated, respectively.

[0225] In operation 1f-55, when the gNB determines through the indicator in message 5 that the UE has performed early frequency measurement in RRC idle mode or RRC inactive mode and there is a measurement result to be reported, the gNB may send a message to the UE to report the measurement result so as to quickly receive the frequency measurement result report. For example, the gNB may request the UE for frequency measurement result information by newly defining and using a UEinformationRequest message as a DL dedicated control channel (DCCH) message.

[0226] In operation 1f-65, when the UE receives the message, the UE may quickly report the fast (early) frequency measurement result to the gNB. For example, when the UE receives the message, the UE may report the frequency measurement result by newly defining and using the UE information response message as a UL-DCCH message. The frequency measurement result may include a serving cell / frequency measurement result (e.g., NR-SS reference signal received power / reference signal received quality (RSRP / RSRQ)) that the UE can measure, a serving cell / frequency neighboring cell / frequency measurement result, a neighboring cell / frequency measurement result, and an indication of a cell / frequency measurement result to be measured. In another method, the gNB may request the UE for frequency measurement result information by defining and using an indicator in an RRCReconfiguration message. When the UE receives the message, the UE may quickly report the early frequency measurement (early measurement) result to the gNB. For example, when the UE receives the message, the UE may report the frequency measurement result by using an RRCReconfigurationComplete message, and in another method, the UE may report the frequency measurement result by defining and using a new field for reporting the frequency measurement result in the UL-DCCH message.

[0227] The condition for causing the UE to stop early frequency measurement in the RRC idle mode or inactive mode may include at least one of the following conditions.

[0228] 1. After notifying the gNB that the system information of the current cell supports fast frequency measurement result reporting and there is a measurement result report in an RRC message (e.g., Message 5), or when notifying the gNB that the system information of the current cell supports fast frequency measurement result reporting and there is a measurement result report in an RRC message (e.g., Message 5)

[0229] 2. When the UE configures a network connection while performing RRC idle mode or RRC inactive mode frequency measurement, when the timer is stopped and the measurement is stopped when an RRCSetup message or an RRCResume message as Message 4 is received, and when the gNB is notified that the system information of the current cell supports fast frequency measurement result reporting and there is a measurement result report in an RRC message (e.g., Message 5)

[0230] 3. When the measurement report timer (e.g., T331) expires

[0231] 4. When the UE is outside the area indicated by the RRC idle mode or RRC inactive mode frequency measurement area information configured in the RRCRelease message

[0232] In operation 1f-60, the UE may stop RRC idle mode or RRC inactive mode frequency measurement (idle mode / inactive mode measurement) according to at least one of the above conditions.

[0233] The UE may perform measurement on frequencies measurable by the UE (ie, frequencies supported in the fast frequency configuration-related information), and in this case, the UE may select frequencies to be measured preferentially according to the configured priority.

[0234] As described below, embodiments of the present disclosure may provide detailed UE operations for reporting frequency measurement results of the first embodiment, wherein the UE performs and reports early frequency measurement in an RRC idle mode or an RRC inactive mode.

[0235] -When receiving the RRCSetup message or the RRCResume message as message 4, the UE may perform the following operations.

[0236] 1. When system information (e.g., SIB2) broadcasts or includes an indicator (idle or inactive mode measurement) indicating that RRC idle mode or RRC inactive mode frequency measurement can be supported, and the UE has a frequency measurement result measured in RRC idle mode or RRC inactive mode,

[0237] A. The UE may cause an indicator (Idle or Inactive Measavailable) indicating the presence of RRC idle mode or RRC inactive mode frequency measurement results to be included in the RRCSetupComplete message or the RRCResumeComplete message as message 5. Thus, the UE may indicate the presence of RRC idle mode or RRC inactive mode frequency measurement information to be reported to the gNB through the message.

[0238] B. Since the frequency measurement result is to be reported, the UE may stop the timer (eg, T331) for RRC idle mode or RRC inactive mode frequency measurement. The UE may stop the frequency measurement and may discard the frequency measurement configuration information.

[0239] Figure 1H 1 is a diagram for describing a method for a UE to perform early frequency measurement and make a fast frequency measurement result report in a next generation mobile communication system according to an embodiment of the present disclosure. Specifically, Figure 1H is a diagram illustrating a second embodiment, in which a UE may perform early frequency measurement (early measurement) and may make a fast frequency measurement result report (fast measurement report) in RRC idle mode or RRC inactive mode.

[0240] The description of the first embodiment can be applied to the second embodiment of the present disclosure. In addition, when the gNB configures frequency measurement configuration information for enabling the UE to perform frequency measurement in RRC idle mode or RRC inactive mode through the RRCRelease message in the UE, the gNB can configure multiple frequency measurement groups. In the method of this embodiment of the present disclosure, the UE can perform frequency measurement in RRC idle mode or RRC inactive mode, and can send message 3 to the gNB when configuring the network connection, and the gNB can perform measurement report indication in message 4 (e.g., RRCResume) when sending message 4 in response to message 3, and can make a frequency measurement result report in message 5 (e.g., RRCResumeComplete). Therefore, compared with the first embodiment, the frequency measurement result report can be made quickly, and the measurement result after the security level is increased can be reported. This is because the RRC inactive mode UE activates the security algorithm of SRB1 from the time point of sending message 3. That is, messages 4 and 5 can be encrypted and integrity protected with new security keys in the PDCP layer, and can be sent.

[0241] In RRC idle mode or RRC inactive mode, the UE may perform frequency measurement, may store the measurement result, may perform random access, and then may send message 3 (e.g., RRCSetupRequest or RRCResumeRequest). When the gNB sends message 4 (e.g., RRCSetup or RRCResume) to the UE, the gNB may enable an indicator to report the frequency measurement result to be included in message 4, and may send message 4. In another method, since message 4 itself may indicate that the UE will report the frequency measurement result, the indicator may be omitted.

[0242] The UE may report the frequency measurement result in message 5 (e.g., RRCSetupComplete or RRCResumeComplete). Since the RRC inactive mode UE may resume or activate the security process (encryption and decryption or integrity protection and authentication) of the signaling radio bearer SRB1 when sending the RRCResumeRequest message, the RRC inactive mode UE may increase the security level when receiving message 4 and receive message 4, and may increase the security level when reporting the frequency measurement result of message 5 and report the frequency measurement result of message 5. In addition, the gNB may include the carrier aggregation configuration or dual connectivity configuration information in the RRC message by using the above information, and may send the RRC message so that the UE may quickly restart, change, or newly configure the carrier aggregation or dual connectivity.

[0243] See also Figure 1H ,RRC connected mode UE may receive frequency measurement configuration information and an indication to release the RRC connection and transition to RRC idle mode or RRC inactive mode from the gNB. In this case, the UE may perform frequency measurement in the RRC idle mode or RRC inactive mode for a configured duration or time. However, when there is no information about a list of frequencies to be measured in the frequency measurement configuration information, if frequency measurement configuration information for frequency measurement of RRC idle mode or RRC inactive mode UE is broadcast in the camped cell and a cell reselection procedure is performed at the same time, the UE may receive the information and may perform frequency measurement.

[0244] When the UE receives the RRC Release message and switches to the RRC inactive mode, in order to effectively handle the secondary cell (Scell) configured for carrier aggregation and the secondary cell group (SCG) configured for dual connectivity, the UE may perform at least one of the following methods.

[0245] Method 1: The UE may release the configuration information of the SCell and the configuration information of the SCG. When configuring the connection later, the gNB may quickly configure the information about the Scell ​​for carrier aggregation or the SCG for dual connectivity in the UE through the RRCResume message or the RRCReconfiguration message based on the fast frequency measurement result report. According to method 1, since the UE does not need to maintain the configuration information of the SCell or the configuration information of the SCG, it may be advantageous in consideration of the memory, and since the gNB does not need to retrieve the existing configuration information of the Scell ​​or the SCG from the source gNB, the implementation may be facilitated.

[0246] Method 2: The UE may store the configuration information of the SCell or the configuration information of the SCG, and may suspend the bearer configuration or transmission of the Scell ​​or the SCG. When configuring the connection later, the gNB allows the UE to reuse the information about the Scell ​​for carrier aggregation or the SCG for dual connectivity through the RRCResume message or the RRCReconfiguration message based on the fast frequency measurement result report, and may only update some configuration information (incremental configuration), or may perform a completely new configuration. According to method 2, because the UE maintains the configuration information of the SCell or the configuration information of the SCG, the gNB can use the existing configuration information of the Scell ​​or the SCG, thereby reducing the signaling overhead. In addition, the UE can quickly apply and start carrier aggregation or dual connectivity. Even when the RRC inactive mode UE resumes the connection, the configuration information for the SCell or the configuration information for the CG may not be released or discarded, and the gNB may indicate to maintain or discard the configuration information for the Scell ​​or the configuration information for the SCG by defining an indicator in the RRCResume message. In another method, the gNB may indicate to maintain or discard the configuration information for the Scell ​​or the configuration information for the SCG by using a full configuration information indicator (fullConfig). In another method, when the gNB sends an RRCRelease message to the UE to convert the RRC connected mode UE to the RRC inactive mode, the gNB may indicate to maintain or discard the SCell (master cell group (MCG) or SCG) or SCG configuration information in the RRCRelease message. Therefore, the UE may maintain the Scell ​​or SCG configuration information according to the indicator of the RRCRelease message, and may maintain the Scell ​​or SCG configuration information even when the RRC connection recovery process is initiated, and may apply the configuration information according to the indication of the gNB (e.g., RRC message). For example, when there is no indication of the SCell or SCG configuration information in the RRCRelease message, the UE may release the Scell ​​or SCG configuration information. When there is an indicator to maintain, store or discard MCG SCell configuration information or SCGPSCell or SCell configuration information, the UE can store and maintain the configuration information accordingly, and can even apply the configuration information during the RRC connection recovery process, and can apply the configuration according to the indication (RRC message) of the gNB. The configuration information for Scell ​​or the configuration information for SCG can refer to PDCP layer configuration information, SDAP layer configuration information, RLC layer information, MAC layer information or PHY layer configuration information, and can indicate part or all of this information.In another method, because the RRC inactive mode UE moves while performing the RAN notification area update procedure, it is possible to indicate in the RRCRelease message received in the RAN notification area update procedure whether to maintain or discard the Scell ​​or SCG configuration information. This is because when the RAN notification area update procedure is performed, the gNB can receive the context of the resumption identifier, so that the UE configuration information can be detected. In another method, when the RRC inactive UE performs the RRC connection resumption procedure with the gNB, if the UE sends the RRCResumeRequest message for some reason (for example, the UE context cannot be retrieved), but the gNB indicates a fallback in the response of the RRCSetup message, the UE may discard the configuration information for the Scell ​​or the configuration information for the SCG. This is because the gNB may not retrieve the UE context, so the gNB may not determine the configuration information for the Scell ​​or the configuration information for the SCG stored in the UE. The configuration information for the Scell ​​or the configuration information for the SCG may refer to the PDCP layer configuration information, the SDAP layer configuration information, the RLC layer information, the MAC layer information, or the PHY layer configuration information, and some or all of these information may be indicated. The gNB can use the existing SCell information or SCG information stored in the UE, through the RRCResume message or RRCReconfiguration message in the RRC connection recovery process, and apply the above method to quickly configure carrier aggregation or dual connectivity in the UE. When configuring dual connectivity, the gNB can cause the preamble information and frequency information required for random access to the SCG to be included, and the preamble information and frequency information can be notified to the UE. In addition, the gNB can indicate the activation of the Scell ​​or SCG in the RRCResume message or RRCReconfiguration message, and can also indicate fast channel measurement information (short channel status information (CSI) report or non-periodic CSI report).

[0247] When an RRC connection to the network needs to be configured, the UE may indicate the presence of the results of frequency measurements in RRC idle mode or RRC inactive mode when configuring the connection to the gNB.

[0248] When reconfiguring a network connection in RRC idle mode or RRC inactive mode, if the UE supports early reporting of frequency measurement results in a cell used to configure the current connection, the UE may prepare frequency measurement results. Referring to operation 1h-35, the UE may perform random access as in operations 1h-20 to 1h-25, and then may send message 3 (e.g., RRCSetupRequest or RRCResumeRequest) to the gNB.

[0249] In operation 1h-40, the gNB may enable an indicator to report the frequency measurement result to be included in message 4 (e.g., RRCSetup or RRCResume) in order to quickly configure carrier aggregation or dual connectivity, and may send message 4 to the UE. In this case, in another method, since message 4 sent by the gNB itself may indicate that the frequency measurement result is to be reported, the indicator may be omitted.

[0250] In operation 1h-50, when the UE receives message 4, the UE may simultaneously send and report the frequency measurement result (and message 5 (e.g., RRCSetupComplete or RRCResumeComplete). Network connection configuration may be performed, and when the gNB sends message 4 (e.g., RRCSetup or RRCResume) or an RRCReconfiguration message to the UE, the gNB may cause carrier aggregation configuration information or dual connectivity configuration information to be included in message 4 or the RRCReconfiguration message, so that the UE may quickly restart, change, or newly configure carrier aggregation or dual connectivity. In another method, when the gNB sends a plurality of frequency configuration information, information for Scell, or information for SCG in the RRCResume message, the UE may select a better frequency or SCG based on the frequency measurement result (e.g., a better frequency or SCG may be selected based on a condition configured by the gNB (e.g., whether the signal strength is equal to or greater than a given value)), and may report information about the frequency, Scell, or SCG that satisfies the given condition in the RRCResumeComplete message. Alternatively, the UE may directly perform a connection by performing a random access procedure on a frequency, Scell, or SCG that meets a given condition. When the connection to the gNB or cell to which the UE is connected is completed, the gNB may notify the source gNB that the UE is connected. The source gNB may request connection authorization from multiple different target gNBs, and when the timer runs and the UE does not access within a certain period of time, each target gNB may determine that the connection has failed, or the source gNB may instruct the UE to configure a connection to another target gNB or may directly instruct the cancellation of the connection authorization.

[0251] The condition for causing the UE to stop early frequency measurement in the RRC idle mode or inactive mode may include at least one of the following conditions.

[0252] 1. After notifying the gNB that the system information of the current cell supports fast frequency measurement result reporting in Message 3, or when notifying the gNB that the system information of the current cell supports fast frequency measurement result reporting in Message 3

[0253] 2. When the UE receives a frequency measurement result report indication in Message 4 during the random access procedure for configuring a network connection while performing RRC idle mode or RRC inactive mode frequency measurement, it stops the timer and stops the measurement, and notifies the gNB that the system information of the current cell supports fast frequency measurement result reporting and that there is a measurement result report in the RRC message (e.g., Message 5)

[0254] 3. When the measurement result report is to be made via message 5

[0255] 4. When the measurement report timer (e.g., T331) expires

[0256] 5. When the UE is outside the area indicated by the RRC idle mode or RRC inactive mode frequency measurement area information configured in the RRCRelease message

[0257] The UE may stop RRC idle mode or RRC inactive mode frequency measurement (idle mode / inactive mode measurement) according to at least one of the above conditions.

[0258] In an embodiment of the present disclosure, the UE may perform measurement on a frequency measurable by the UE (ie, a frequency supported in the fast frequency configuration related information), and in this case, the UE may select a frequency to be measured preferentially according to a configured priority.

[0259] According to the second method of the method of quickly performing and reporting frequency measurement in RRC idle mode or RRC inactive mode, a detailed UE operation of reporting frequency measurement results may be provided as follows.

[0260] When receiving a random access response and receiving Message 4 from the gNB, the UE may perform the following operations.

[0261] 1. When system information (e.g., SIB2) broadcasts or includes an indicator (idle or inactive mode measurement) indicating that RRC idle mode or RRC inactive mode frequency measurement can be supported, and the UE has a frequency measurement result measured in RRC idle mode or RRC inactive mode

[0262] A. The UE may include the RRC idle mode or RRC inactive mode frequency measurement result in message 5 (RRCSetupRequest message or RRCResumeRequest message). In another method, the UE may multiplex the RRC message (e.g., message 5) and the frequency measurement result in the MAC layer, and may send the RRC message and the frequency measurement result. Therefore, the UE may report the RRC idle mode or RRC inactive mode frequency measurement information to the gNB through the message.

[0263] B. Since the frequency measurement result is to be reported, the UE may stop the timer (eg, T331) for RRC idle mode or RRC inactive mode frequency measurement. The UE may stop the frequency measurement and may discard the frequency measurement configuration information and the frequency measurement result.

[0264] Embodiments of the present disclosure may provide an efficient signaling method in which a network or gNB may more efficiently configure or update frequency measurement configuration information in a UE with mobility in an RRC deactivated mode.

[0265] The most significant differences between RRC idle mode UE and RRC deactivated mode UE are that RRC deactivated mode UE can store UE context in gNB and UE and can quickly configure connection by reusing UE context, and RRC deactivated mode UE can update the area where RRC deactivated mode must be maintained from the network by periodically updating RAN notification area.

[0266] According to an embodiment of the present disclosure, when an RRC connected mode UE receives frequency measurement configuration information and an indication to release the RRC connection from the gNB and transition to the RRC deactivated mode, the UE may perform frequency measurement for a configured duration or time in the RRC deactivated mode. When the RRC deactivated mode UE moves out of the configured RAN notification area, the RRC deactivated mode UE may configure a connection to the network to perform a RAN Notification Area Update (RNAU) procedure. In this case, according to an embodiment of the present disclosure, for the UE that performs a connection to the network to update the RAN notification area, the gNB may configure or update a new frequency measurement configuration, or may instruct the UE to maintain the frequency measurement.

[0267] In detail, the present disclosure may provide two procedures for updating the RAN notification area.

[0268] Fig. 1I It is a schematic diagram for describing a RAN notification area update process according to an embodiment of the present disclosure.

[0269] In operation 1i-20, when the RRC deactivated mode UE moves out of the RAN notification area, the RRC deactivated mode UE may perform a random access procedure to perform a RAN notification area update procedure, and may send message 3 (e.g., RRCResumeRequest (RRC resume request)) to the gNB to connect to the network.

[0270] The gNB may identify the UE's connection resumption identifier in message 3 to retrieve the UE context from the source gNB and may identify the connection resumption cause in message 3 to determine that the UE needs to update the RAN notification area.

[0271] In operation 1i-25, the gNB may send message 4 (e.g., RRC Resume (RRC Resume)) to the UE to update the RAN notification area so that the UE may transition to RRC connected mode.

[0272] In operation 1i-35, the UE may send message 5 and may indicate that the connection has been correctly established. In operation 1i-40, the gNB may cause the new RAN notification area to be included in the RRCRelease (RRC release) message to update the RAN notification area, may send the RRCRelease message to the UE, and may instruct the UE to re-transition to the RRC deactivation mode. When the UE receives the RRCRelease message, the UE may identify and reflect the new RAN notification area information, may maintain mobility, and may transition to the RRC deactivation mode.

[0273] Figure 1J is a schematic diagram for describing a RAN notification area update process according to an embodiment of the present disclosure.

[0274] In operation 1j-20, when the RRC deactivated mode UE moves out of the RAN notification area, the RRC deactivated mode UE may perform a random access procedure to perform a RAN notification area update procedure, and may send a message 3 (e.g., RRCResumeRequest) to the gNB to perform a connection to the network.

[0275] The gNB may identify the UE's connection resumption identifier in message 3 to retrieve the UE context from the source gNB and may identify the connection resumption cause in message 3 to determine that the UE needs to update the RAN notification area.

[0276] In operation 1j-40, the gNB may include the new RAN notification area in the RRCRelease message to update the RAN notification area, may send the RRCRelease message to the UE, and may instruct the UE to maintain the RRC deactivation mode. When the UE receives the RRCRelease message, the UE may identify and reflect the new RAN notification area information, may maintain mobility, and may maintain the RRC deactivation mode. Fig. 1I Compared with the RAN notification area update method, the RAN notification area update procedure can reduce signaling overhead and may not require the UE's state transition. That is, the UE can perform the RAN notification area update procedure while maintaining the RRC deactivated mode.

[0277] In the above-mentioned RAN notification area update process, the gNB can retrieve the UE context from the source gNB through the connection resumption identifier indicated by the UE in message 3 (RRC resume request), and can determine whether the UE is to perform frequency measurement configuration in RRC deactivated mode. In addition, the UE can indicate that the connection resumption cause (resumeCause) is to update the RAN notification area in message 3. In another method, when the UE sends message 3 to update the RAN notification area, the UE can cause an indicator indicating that frequency measurement is performed in RRC deactivated mode, timer T331 expires or is running, or new frequency configuration information needs to be included in message 3, and message 3 can be sent to the gNB to indicate the information to the gNB.

[0278] As described with reference to operations 1i-40 and 1j-40, when the gNB determines whether the UE can perform frequency measurement in the RRC deactivated mode and then sends an RRC message (e.g., an RRCRelease message) including information for updating the RAN notification area to the UE, the gNB may cause new frequency measurement configuration information to be included in the RRC message, and may send and configure the RRC message. The new frequency measurement configuration information may include configuration information such as a list of frequencies to be measured, a list of physical cell identifiers, or a measurement duration, or a validity area for measurement (e.g., a cell identifier list). Therefore, when the RRC deactivated mode UE moves and passes through coverage supported by another cell or gNB, the UE and the gNB according to an embodiment of the present disclosure may newly update or change the frequency measurement configuration information in the RRC deactivated mode through the RAN notification area update process, and the UE with mobility may quickly report the frequency measurement configuration information when configuring a connection to the network later, and may quickly configure dual connectivity or carrier aggregation.

[0279] In addition, an embodiment of the present disclosure may provide a process in which, when the gNB or cell to which the UE is connected may support RRC idle mode or deactivation mode frequency measurement, when information may indicate support for RRC idle mode or deactivation mode frequency measurement, and when the frequency measurement result may be reported to the gNB, the UE may stop timer T331 for RRC idle mode or deactivation mode frequency measurement, and may discard or release the frequency measurement configuration information or discard the frequency measurement result.

[0280] In addition, in an embodiment of the present disclosure, an RRC deactivation mode or RRC idle mode UE may configure a separate area (e.g., a validity area) for performing frequency measurement in an RRCRelease message. That is, the UE may perform frequency measurement in an RRC deactivation mode or an RRC idle mode only within a valid area, and when outside the valid area, the UE may stop a timer, may release frequency measurement configuration information, may discard frequency measurement results, or may stop frequency measurement. The validity area may be indicated by a physical cell identifier list or a RAN notification area indicator list. An embodiment of the present disclosure may provide a method for separately configuring a validity area and a RAN notification area in an RRC deactivation mode UE, and a method for allowing an RRC deactivation mode UE to use a RAN notification area instead of a validity area (or use a validity area instead of a RAN notification area) by using an indicator so as to reduce the burden on the UE and reduce signaling overhead. This is because when a separate validity area is indicated to the UE, the UE may have the burden of maintaining and updating a tracking area, maintaining and updating a RAN notification area, and maintaining and managing a validity area. That is, when the UE receives the RRCRelease message and receives information for transitioning the UE to the RRC deactivation mode, when there is frequency measurement configuration information and there is an indicator, or when it is indicated to use the RAN notification area, the UE can transition to the RRC deactivation mode and can perform frequency measurement by considering the RAN notification area as a validity area. When the UE receives the RRCRelease message and receives information for transitioning the UE to the RRC deactivation mode, when there is frequency measurement configuration information and there is no indicator, when it is not indicated to use the RAN notification area, or when a separate validity area is configured and indicated, the UE can transition to the RRC deactivation mode, can perform frequency measurement by considering the validity area, and can manage the mobility of the RRC deactivation mode according to the RAN notification area.

[0281] Embodiments of the present disclosure may provide efficient UE operations performed by a UE that is capable of measuring frequency measurements or is configured to perform frequency measurements in an RRC deactivation mode in a RAN notification area update procedure (e.g., a first and a second RAN notification area update procedure).

[0282] - When the UE sends Message 3 to perform the RAN Notification Area Update procedure and receives the RRCRelease message in the first RAN Notification Area Update procedure or the second RAN Notification Area Update procedure

[0283] - Or, when the UE receives the RRCRelease message

[0284] 1. When the UE receives the RRCRelease message, including frequency measurement configuration information, information about the frequency measurement duration, and no frequency measurement list information,

[0285] A. The UE may configure the frequency measurement time as a timer value and may drive the timer.

[0286] B. The UE may perform a frequency measurement procedure based on previously stored information (information indicated in a previous RRCRelease message or information indicated in the last received system information). In another method, the UE may determine that the existing stored frequency measurement information is invalid information, may discard the existing stored frequency measurement information, may perform a cell reselection procedure, and may receive new frequency measurement information from the system information. When the UE receives the frequency measurement information, the UE may start frequency measurement.

[0287] 2. When a RRCRelease message including frequency measurement configuration information is received, and there is information about the frequency measurement duration and frequency information of the frequency to be measured,

[0288] A. The UE may configure the frequency measurement duration as a timer value and may drive the timer.

[0289] B. The UE may determine that the existing stored information is invalid information, may discard the existing stored information, may receive new frequency measurement information included in the RRCRelease message, may store the new frequency measurement information, and may perform frequency measurement. When the frequency measurement is stopped, the UE may resume the frequency measurement, and when the frequency measurement is never stopped, the UE may restart the frequency measurement.

[0290] - When the UE performs frequency measurement in RRC deactivated mode, when the UE sends Message 3 and receives the RRCRelease message to perform the RAN notification area update procedure, that is, when the UE receives the RRCRelease message in a state where the RRC deactivated mode is maintained and no RRC mode state transition occurs

[0291] - In addition, when the UE performs frequency measurement in RRC deactivated mode, when the UE sends Message 3 and receives the RRCRelease message to perform the RAN Notification Area Update procedure

[0292] 1. When there is no new frequency measurement configuration information in the RRCRelease message,

[0293] A. The UE may continue to perform frequency measurement based on the existing frequency configuration information.

[0294] 2. When there is new frequency measurement configuration information in the RRCRelease message,

[0295] A. The UE may discard or release the existing frequency measurement configuration information or frequency measurement result.

[0296] B. The UE may configure the duration or timer value included in the new frequency measurement configuration information, and may initialize and drive the timer again.

[0297] C. When there is a frequency measurement list in the frequency measurement configuration information,

[0298] i. The UE may perform frequency measurement on the frequency measurement list.

[0299] D. When there is no frequency measurement list in the frequency measurement configuration information,

[0300] i. The UE may perform a cell reselection procedure, and when frequency measurement information exists in the system information of the camped cell, the UE may receive and store the frequency measurement information and may perform frequency measurement.

[0301] In another method, when the UE performs frequency measurement in the RRC deactivation mode, when the UE sends message 3 to perform the RAN notification area update process, the UE can stop the frequency measurement and can receive the RRCRelease message, and when there is no new frequency measurement information, the UE can resume the frequency measurement based on the existing frequency measurement information. In addition, when there is new frequency measurement information in the RRCRelease message, the UE can resume the frequency measurement based on the new frequency measurement information.

[0302] In another method, when the RRCRelease message is received and the fast frequency measurement configuration information is included, the UE may release or discard the stored frequency measurement configuration information or the frequency measurement result, and may perform frequency measurement by storing, updating and applying the new fast frequency measurement configuration information. In another method, when only the frequency measurement duration of the timer value is configured in the fast frequency measurement configuration information, the UE may restart the timer based on the value, and may continue the frequency measurement configuration while maintaining the existing frequency configuration information. Alternatively, the UE may start the timer based on the value, may release the existing frequency configuration information, may receive the system information in the camped cell through the cell reselection process, and may perform frequency measurement by applying the frequency configuration information when there is frequency configuration information. In another method, the gNB may define a new indicator in the RRCRelease message, and may indicate whether to continue the frequency measurement, stop the frequency measurement, or release the frequency measurement configuration information by using the existing frequency measurement configuration information. In another method, the UE may release the existing frequency configuration information only when the frequency measurement configuration information is included in the RRCRelease message, and when there is no frequency configuration information, the UE may maintain and apply the existing frequency configuration information.

[0303] In another approach, the following embodiments of the present disclosure are possible.

[0304] When the UE sends message 3 to perform the RAN Notification Area Update procedure and receives the RRCRelease message in response to message 3 in the first RAN Notification Area Update procedure or the second RAN Notification Area Update procedure

[0305] - Or, when the UE receives the RRCRelease message

[0306] 1. When the UE receives the RRCRelease message including frequency measurement configuration information, there is information about the frequency measurement duration and there is no frequency measurement list information, or when a new indicator is included to maintain the frequency measurement information or frequency measurement result and continue the frequency measurement,

[0307] A. The UE may configure the frequency measurement duration as a timer value and may drive the timer again. In addition, when the timer is running, the UE may stop the timer, may initialize the timer, may configure the value configured in the RRC message as the timer value, and may restart the timer again.

[0308] B. The UE may perform a frequency measurement procedure based on previously stored information (information indicated in a previous RRCRelease message or information indicated in the last received system information). In another method, the UE may determine that the existing stored frequency measurement information or frequency measurement result is invalid information, may discard the existing stored frequency measurement information or frequency measurement result, may perform a cell reselection procedure, and may receive new frequency measurement information from the system information. When the UE receives the frequency measurement information, the UE may start frequency measurement.

[0309] 2. When the RRCRelease message is received, including the frequency measurement configuration information, and there is information about the frequency measurement duration and frequency information of the frequency to be measured, or when an indicator to keep the frequency measurement information or the frequency measurement result and continue the frequency measurement is included,

[0310] A. The UE may configure the frequency measurement duration as a timer value and may drive the timer. In addition, when the timer is running, the UE may stop the timer, may initialize the timer, may configure the value configured in the RRC message as the timer value, and may restart the timer again.

[0311] B. The UE may determine that the existing stored frequency measurement information or frequency measurement result is invalid information, may discard the existing stored frequency measurement information or frequency measurement result, and may perform frequency measurement by receiving and storing new frequency measurement information included in the RRCRelease message. When the frequency measurement is stopped, the UE may resume the frequency measurement, and when the frequency measurement is never stopped, the UE may restart the frequency measurement.

[0312] 3. When the RRCRelease message is received and there is no frequency measurement configuration information, when no new indicator is included to keep the frequency measurement information or frequency measurement result and continue the frequency measurement, or when no new indicator is included to release or discard the frequency measurement information or frequency measurement result and stop the frequency measurement,

[0313] A. The UE may determine that the existing stored frequency measurement information or frequency measurement result is invalid information and may discard the existing stored frequency measurement information or frequency measurement result, and when the timer for frequency measurement is running, the UE may stop the timer.

[0314] Embodiments of the present disclosure may provide a method for performing a frequency measurement operation when an RRC deactivated mode UE attempts to resume connection to a network and falls back to an RRC idle mode due to an instruction from a gNB.

[0315] Figure 1K1 is a schematic diagram for describing a process in which an RRC deactivated UE falls back to an RRC idle mode due to an instruction from a gNB according to an embodiment of the present disclosure. Figure 1K , a first embodiment of performing a frequency measurement operation when an RRC deactivated mode UE attempts to resume connection to the network and falls back to RRC idle mode due to an instruction from a gNB is as follows.

[0316] As in operation 1k-20, the UE may send message 3 to perform the RAN notification area update procedure while performing frequency measurement in the RRC deactivated mode, and as in operation 1k-40, the gNB may send an RRCSetup message as message 4. As in operation 1k-45, when the UE may need to cancel the connection recovery procedure or transition from the RRC deactivated mode to the RRC idle mode,

[0317] 1. The UE may stop the timer for frequency measurement, may discard the frequency measurement configuration information or the frequency measurement result, and may stop the frequency measurement. In addition, the UE may discard the frequency measurement result. That is, when the RRC deactivated mode UE falls back, the implementation of the UE and the gNB may be facilitated by the method that the UE discards and releases all previously configured information.

[0318] A second embodiment of performing a frequency measurement operation when an RRC deactivated mode UE attempts to resume connection to the network and falls back to RRC idle mode due to instructions from the gNB may be as follows.

[0319] - As in operation 1k-20, the UE may send message 3 to perform the RAN notification area update procedure while performing frequency measurement in the RRC deactivated mode. As in operation 1k-40, the gNB may send the RRCSetup message as message 4. As in operation 1k-45, when the UE may need to cancel the connection recovery procedure or transition from the RRC deactivated mode to the RRC idle mode,

[0320] 1. As in the above-mentioned embodiment of the present disclosure, the UE may indicate the presence of a frequency measurement result and may report the frequency measurement result. That is, the UE may continue to use the measurement result effectively. Whether the frequency measurement result is valid may be determined by the gNB. For example, the gNB may operate as follows.

[0321] A. When system information (e.g., SIB2) broadcasts or includes an indicator (idle or deactivated mode measurement) indicating that RRC idle mode or RRC deactivated mode frequency measurement can be supported, and the UE has a frequency measurement result measured in the RRC idle mode or RRC deactivated mode,

[0322] i. The UE may cause an indicator indicating that frequency measurement has been performed in RRC idle mode or RRC deactivated mode, and in operation k1-50, include the frequency measurement result in message 5 (RRCSetupComplete). Therefore, the UE may indicate that there is RRC idle mode or RRC deactivated mode frequency measurement information to be reported to the gNB through the above message.

[0323] ii. Since the frequency measurement result is to be reported, the UE may stop the timer (eg, T331) for RRC idle mode or RRC deactivation mode frequency measurement. The UE may stop the frequency measurement and may discard the frequency measurement configuration information or the frequency measurement result.

[0324] In the above-mentioned embodiments of the present disclosure, the frequency measurement configuration information may be configured as different information elements (IEs) for RRC idle mode and RRC deactivation mode. That is, depending on the RRC mode to which the UE is switched, the gNB may cause different configuration information to be included and may indicate frequency measurement. In addition, the UE may store the results measured in the RRC idle mode and the RRC deactivation mode in different variables and may report the results differently. Because the RRC idle mode and the RRC deactivation mode are different from each other in the process of configuring a connection to the network and specific operations, the configuration information (frequency measurement list, timer value (duration) or validity area) and the configuration result report variable may be managed more efficiently, respectively.

[0325] Embodiments of the present disclosure may provide a fast frequency measurement operation and method for effectively processing frequency configuration information or frequency measurement results when a UE in RRC deactivation mode switches to RRC idle mode for some reason. Embodiments of the present disclosure may provide certain reasons for causing the state transition of the UE and an effective method corresponding to the certain reasons. In addition, embodiments of the present disclosure may provide a method for performing a frequency measurement operation when an RRC idle mode UE accesses another radio access technology.

[0326] 1. When an RRC deactivated mode UE configured with fast frequency measurement configuration information is received in a paging message, when a System Architecture Evolution (SAE)-Temporary Mobile Subscriber Identity (S-TMSI), 5G-S-TMSI or International Mobile Subscriber Identity (IMSI) is received in a paging message instead of a deactivated radio network temporary identifier (I-RNTI), the RRC deactivated mode UE may need to perform a state transition, that is, when the RRC deactivated mode terminal may need to transition from the RRC deactivated mode to the RRC idle mode

[0327] A. Method 1: Even after transitioning to RRC idle mode, the UE may continue to perform frequency measurement based on the previously configured fast frequency measurement configuration information. Therefore, when a connection to the network is performed later, the UE may quickly report the frequency measurement result. In this case, the previously configured fast frequency measurement configuration information may include a value of a first timer indicating the time at which the UE is to perform frequency measurement, and the UE may not stop the first timer (e.g., T331) when transitioning from RRC deactivation mode to RRC idle mode. That is, by continuously driving the first timer, the UE may continue to perform frequency measurement even when a state transition occurs while the first timer is running. When the first timer expires, the UE may release or discard the frequency measurement information or the frequency measurement result (the frequency measurement result may be discarded by the second timer). In another method, when transitioning from RRC deactivation mode to RRC idle mode, the UE may continue to perform frequency measurement results by restarting the first timer (e.g., T331) based on the duration value configured in the RRCRelease message.

[0328] B. Method 2: The UE may discard the UE context when transitioning to the RRC idle mode, may stop the timer for frequency measurement while the timer is running, and may determine that the previously configured frequency measurement information or frequency measurement result is no longer valid, and may discard the previously configured frequency measurement information or frequency measurement result. Because the UE context is discarded, the UE may determine that the existing configuration is invalid. In another method, the UE may only discard the frequency measurement information, and may use the frequency measurement result for reporting later.

[0329] 2. When an RRC deactivated mode UE configured with fast frequency measurement configuration information may perform an RRC connection recovery procedure to configure a connection to the network, an RRCResumeRequest message as message 3 may be sent, an RRCSetup message in response to message 3 may be received, and a state transition may need to be performed, i.e., when the RRC deactivated mode UE falls back to the RRC idle mode

[0330] A. Method 1: The UE may discard the UE context when transitioning to the RRC idle mode, may stop the timer for frequency measurement while the timer is running, and may determine that the previously configured frequency measurement information or frequency measurement result is no longer valid, and may discard the previously configured frequency measurement information or frequency measurement result. Because the UE context is discarded, the UE may determine that the existing configuration is invalid. In another method, the UE may only discard the frequency measurement information, and may use the frequency measurement result for reporting later. In this case, the previously configured fast frequency measurement configuration information may include the value of the first timer indicating the time when the UE is to perform the frequency measurement, and when transitioning from the RRC deactivation mode to the RRC idle mode, the UE may not stop the first timer (e.g., T331). That is, by continuously driving the first timer, the UE can keep performing frequency measurement even when a state transition occurs while the first timer is running. When the first timer expires, the UE may release or discard the frequency measurement information or frequency measurement result (the frequency measurement result may be discarded by the second timer). In another method, when transitioning from the RRC deactivation mode to the RRC idle mode, the UE may keep performing the frequency measurement result by restarting the first timer (eg, T331) based on the duration value configured in the RRCRelease message.

[0331] B. Method 2: The UE may discard the UE context, but may not discard the frequency measurement result when transitioning to RRC idle mode, and may make a report to the gNB so that the gNB uses the frequency measurement result. For example, when the UE sends RRCSetupComplete as message 5, the UE may define an indicator of the RRCSetupComplete message indicating the presence of the measurement result, and may indicate the presence of the measurement result to the gNB by using the indicator. The UE may release the frequency measurement configuration information. In addition, when a separate frequency measurement result request message (e.g., UEInformationRequest) is received from the gNB, the UE may cause the frequency measurement result (e.g., UEInformationResponse) to be included in a separate response message, may send the separate response message to the gNB, and may discard the stored frequency measurement result.

[0332] 3. When the T319 timer run by the RRC deactivated mode UE configured with fast frequency measurement configuration information expires, that is, when the UE must transition to RRC idle mode due to the expiration of the T319 timer (the T319 timer starts when message 3 (e.g., RRCResumeRequest) is sent, and stops when message 4 (e.g., RRCResume or RRCSetup or RRCRelease) is received).

[0333] A. Method 1: Even after transitioning to RRC idle mode, the UE may continue to perform frequency measurement based on the previously configured fast frequency measurement configuration information. Therefore, when a connection to the network is performed later, the UE may quickly report the frequency measurement result. The previously configured fast frequency measurement configuration information may include a value of a first timer indicating the time at which the UE is to perform frequency measurement, and the UE may not stop the first timer (e.g., T331) when transitioning from RRC deactivation mode to RRC idle mode. That is, by continuously driving the first timer, the UE may continue to perform frequency measurement even when a state transition occurs while the first timer is running. When the first timer expires, the UE may release or discard the frequency measurement information or the frequency measurement result (the frequency measurement result may be discarded by the second timer). In another method, when transitioning from RRC deactivation mode to RRC idle mode, the UE may continue to perform frequency measurement results by restarting the first timer (e.g., T331) based on the duration value configured in the RRCRelease message.

[0334] B. Method 2: The UE may discard the UE context when transitioning to the RRC idle mode, may stop the timer for frequency measurement while the timer is running, and may determine that the previously configured frequency measurement information or frequency measurement result is no longer valid, and may discard the previously configured frequency measurement information or frequency measurement result. Because the UE context is discarded, the UE may determine that the existing configuration is invalid. In another method, the UE may only discard the frequency measurement information, and may use the frequency measurement result for reporting later.

[0335] 4. When an RRC deactivated mode UE configured with fast frequency measurement configuration information fails to find a suitable cell when performing cell reselection in the RRC deactivated state, waits for an acceptable cell to provide only limited services, and transitions to RRC idle mode

[0336] A. Method 1: Even after transitioning to RRC idle mode, the UE may continue to perform frequency measurement based on the previously configured fast frequency measurement configuration information. Therefore, when a connection to the network is performed later, the UE may quickly report the frequency measurement result. The previously configured fast frequency measurement configuration information may include a value of a first timer indicating the time at which the UE is to perform frequency measurement, and the UE may not stop the first timer (e.g., T331) when transitioning from RRC deactivation mode to RRC idle mode. That is, by continuously driving the first timer, the UE may continue to perform frequency measurement even when a state transition occurs while the first timer is running. When the first timer expires, the UE may release or discard the frequency measurement information or the frequency measurement result (the frequency measurement result may be discarded by the second timer). In another method, when transitioning from RRC deactivation mode to RRC idle mode, the UE may continue to perform frequency measurement results by restarting the first timer (e.g., T331) based on the duration value configured in the RRCRelease message.

[0337] B. Method 2: The UE may discard the UE context when transitioning to the RRC idle mode, and may stop the timer for frequency measurement while the timer is running, and may determine that the previously configured frequency measurement information or frequency measurement result is no longer valid, and may discard the previously configured frequency measurement information or frequency measurement result. Because the UE context is discarded, the UE may determine that the existing configuration is invalid. In another method, the UE may only discard the frequency measurement information, and may use the frequency measurement result for reporting later.

[0338] 5. When the RRC deactivated mode UE configured with fast frequency measurement configuration information performs the RRC connection recovery procedure to configure a connection to the network, a RRCResumeRequest message as message 3 is sent, and a RRCResume message in response to message 3 is received, but the RRC deactivated mode UE may not follow the configuration of the RRCResume message, or may not apply the configuration information (e.g., in the RRC deactivated mode UE, the RRC deactivated mode UE may not follow the configuration of the RRCResume message, or may not apply the configuration information). UE context recovery is generally not performed in the gNB or UE, so the RRC deactivated mode UE may need to perform a state transition, that is, when the RRC deactivated mode UE may need to transition to the RRC idle mode

[0339] A. Method 1: The UE may discard the UE context when transitioning to RRC idle mode, may stop the timer for frequency measurement while the timer is running, and may determine that the previously configured frequency measurement information or frequency measurement result is no longer valid, and may discard the previously configured frequency measurement information or frequency measurement result. Because the UE context is discarded, the UE may determine that the existing configuration is invalid. In another method, the UE may only discard the frequency measurement information, and may use the frequency measurement result for reporting later. The previously configured fast frequency measurement configuration information may include the value of the first timer indicating the time when the UE is to perform frequency measurement, and when transitioning from RRC deactivation mode to RRC idle mode, the UE may not stop the first timer (e.g., T331). That is, by continuously driving the first timer, the UE can keep performing frequency measurement even when a state transition occurs while the first timer is running. When the first timer expires, the UE may release or discard the frequency measurement information or frequency measurement result (the frequency measurement result may be discarded by the second timer). In another method, when transitioning from the RRC deactivation method to the RRC idle mode, the UE may continue to perform frequency measurement results by restarting the first timer (eg, T331) based on the duration value configured in the RRCRelease message.

[0340] B. Method 2: The UE may discard the UE context, but may not discard the frequency measurement result when transitioning to RRC idle mode, and may make a report to the gNB so that the gNB uses the measurement result. For example, when the UE sends RRCSetupComplete as message 5, the UE may define an indicator of the RRCSetupComplete message indicating the presence of the measurement result, and may indicate the presence of the measurement result to the gNB by using the indicator. The UE may release the frequency measurement configuration information. In addition, when a separate frequency measurement result request message (e.g., UEInformationRequest) is received from the gNB, the UE may cause the frequency measurement result (e.g., UEInformationResponse) to be included in a separate response message, may send the separate response message to the gNB, and may discard the stored frequency measurement result.

[0341] 6. When an RRC deactivated mode UE configured with fast frequency measurement configuration information reselects a cell using another radio access technology while performing a cell reselection procedure, camps on the cell (in the case of inter-RAT reselection), and may need to transition to RRC idle mode

[0342] A. Method 1: Even after transitioning to RRC idle mode, the UE may continue to perform frequency measurement based on the previously configured fast frequency measurement configuration information. Therefore, when a connection to the network is performed later, the UE may quickly report the frequency measurement result. The previously configured fast frequency measurement configuration information may include a value of a first timer indicating the time at which the UE is to perform frequency measurement, and the UE may not stop the first timer (e.g., T331) when transitioning from RRC deactivation mode to RRC idle mode. That is, by continuously driving the first timer, the UE may continue to perform frequency measurement even when a state transition occurs while the first timer is running. When the first timer expires, the UE may release or discard the frequency measurement information or the frequency measurement result (the frequency measurement result may be discarded by the second timer). In another method, when transitioning from RRC deactivation mode to RRC idle mode, the UE may continue to perform frequency measurement results by restarting the first timer (e.g., T331) based on the duration value configured in the RRCRelease message.

[0343] B. Method 2: The UE may discard the UE context when transitioning to the RRC idle mode, may stop the timer for frequency measurement while the timer is running, and may determine that the previously configured frequency measurement information or frequency measurement result is no longer valid, and may discard the previously configured frequency measurement information or frequency measurement result. Because the UE context is discarded, the UE may determine that the existing configuration is invalid. In another method, the UE may only discard the frequency measurement information, and may use the frequency measurement result for reporting later.

[0344] C. Method 3:

[0345] i. when another radio access technology used by a cell selected or camped on by the UE through a cell reselection procedure and on which the UE is camped is an LTE system connected to a 5G Core Network (CN) or an LTE system or NR system connected to an Evolved Packet Core (EPC),

[0346] 1. Even after switching to RRC idle mode, the UE can keep performing frequency measurement based on the previously configured fast frequency measurement configuration information. Therefore, when a connection to the network is performed later, the UE can quickly report the frequency measurement result. The previously configured fast frequency measurement configuration information may include the value of the first timer indicating the time when the UE is to perform frequency measurement, and when switching from RRC deactivation mode to RRC idle mode, the UE may not stop the first timer (e.g., T331). That is, by continuously driving the first timer, the UE can keep performing frequency measurement even when a state transition occurs while the first timer is running. When the first timer expires, the UE may release or the frequency measurement information or the frequency measurement result (the frequency measurement result may be discarded by the second timer). In another method, when switching from RRC deactivation mode to RRC idle mode, the UE may keep performing frequency measurement results by restarting the first timer (e.g., T331) based on the duration value configured in the RRCRelease message.

[0347] ii. Otherwise, when another radio access technology used by the cell selected or camped on by the UE through the cell reselection procedure is a system other than the LTE system connected to the 5G CN or the LTE system or NR system connected to the EPC (e.g., Universal Mobile Telecommunications System (UMTS) or a second generation (2G) system), or when another radio access technology used by the cell selected or camped on by the UE through the cell reselection procedure is UMTS (3G) or Global System for Mobile Communications (GSM) Edge Radio Access Network (GERAN) (2G),

[0348] 1. The UE may discard the UE context when transitioning to the RRC idle mode, may stop the timer for frequency measurement while the timer is running, and may determine that the previously configured frequency measurement information or frequency measurement result is no longer valid, and may discard the previously configured frequency measurement information or frequency measurement result. Because the UE context is discarded, the UE may determine that the existing configuration is invalid. In another method, the UE may only discard the frequency measurement information, and may use the frequency measurement result for reporting later.

[0349] 7. When the RRC deactivated mode UE configured with fast frequency measurement configuration information performs an RRC connection recovery procedure to configure a connection to the network, an RRCResumeRequest message is sent as message 3, an RRCReject message or an RRCRelease message is received in response to message 3, and a state transition needs to be performed, i.e., when the RRC deactivated mode UE returns to the RRC idle mode

[0350] A. Method 1: The UE may discard the UE context when transitioning to RRC idle mode, may stop the timer for frequency measurement while the timer is running, and may determine that the previously configured frequency measurement information or frequency measurement result is no longer valid, and may discard the previously configured frequency measurement information or frequency measurement result. In this case, because the UE context is discarded, the UE may determine that the existing configuration is invalid. In another method, the UE may only discard the frequency measurement information, and may use the frequency measurement result for reporting later. The previously configured fast frequency measurement configuration information may include the value of the first timer indicating the time when the UE is to perform frequency measurement, and when transitioning from RRC deactivation mode to RRC idle mode, the UE may not stop the first timer (e.g., T331). That is, by continuously driving the first timer, the UE can keep performing frequency measurement even when a state transition occurs while the first timer is running. When the first timer expires, the UE may release or discard the frequency measurement information or frequency measurement result (the frequency measurement result may be discarded by the second timer). In another method, when transitioning from the RRC deactivation mode to the RRC idle mode, the UE may keep performing the frequency measurement result by restarting the first timer (eg, T331) based on the duration value configured in the RRCRelease message.

[0351] B. Method 2: The UE may discard the UE context when transitioning to the RRC idle mode, may stop the timer (e.g., the first timer) for frequency measurement while the timer is running, and may determine that the previously configured frequency measurement information or frequency measurement result is no longer valid, and may discard the previously configured frequency measurement information or frequency measurement result. In this case, because the UE context is discarded, the UE may determine that the existing configuration is invalid. In another method, the UE may only discard the frequency measurement information, and may use the frequency measurement result for reporting later.

[0352] The following embodiments of the present disclosure provide a method for performing a fast frequency measurement operation when an LTE or NR RRC idle mode UE is connected to another radio access technology.

[0353] 8. When another radio access technology used by a cell selected or camped on by an RRC idle mode UE through a cell reselection procedure (inter-RAT reselection) is a system other than an LTE system connected to a 5G CN or an LTE system connected to an EPC or an NR system (e.g., UMTS or 2G system), or when another radio access technology used by a cell selected or camped on by an RRC idle mode UE is UMTS (3G) or GERAN (2G),

[0354] A. The RRC idle mode UE may stop a timer (eg, a first timer) for frequency measurement while the timer is running, and may determine that previously configured frequency measurement information or a frequency measurement result is no longer valid, and may discard the previously configured frequency measurement information or a frequency measurement result.

[0355] Figure 1L It is a schematic diagram for describing the operation of a terminal performing RRC idle mode or RRC deactivation mode frequency measurement and reporting the measurement result according to an embodiment of the present disclosure.

[0356] Referring to 1L, when the terminal receives the RRC message, the terminal may drive a timer for RRC idle mode or RRC deactivation mode frequency measurement.

[0357] In operation 11-05, the terminal may determine whether frequency measurement configuration information for RRC idle mode or RRC deactivation mode frequency measurement exists in the RRC message.

[0358] In operation 11-10, the terminal may perform RRC idle mode or RRC deactivation mode frequency measurement based on the frequency measurement configuration information. When there is no frequency measurement configuration information for RRC idle mode or RRC deactivation mode frequency measurement in the RRC message, the terminal may receive frequency measurement information from system information and may perform RRC idle mode or RRC deactivation mode frequency measurement. In the case of an RRC deactivation mode terminal, an RRC message may be received during a RAN notification area update process, and frequency measurement may be continuously performed by the newly configured frequency measurement information whenever a RAN notification area update process is performed. When the terminal performs frequency measurement, the terminal may store the measurement result.

[0359] When there is an indicator indicating that RRC idle mode or RRC deactivation mode frequency measurement can be supported in the system information of the cell configuring the connection to the network, when configuring the connection to the network, the terminal can send message 3. When the base station can cause the indicator to indicate that the frequency measurement result is included in message 4 and can send message 4, the terminal can stop the timer in operations 11-15.

[0360] Furthermore, in operation 11-20, the terminal may include the RRC idle mode or RRC deactivation mode frequency measurement result in message 5, and may send message 5. When the measurement result is successfully delivered to the base station, the terminal may discard the measurement result.

[0361] Figure 1M is a block diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.

[0362] Reference Figure 1M, the terminal may include a radio frequency (RF) processor 1m-10, a baseband processor 1m-20, a memory 1m-30, and a controller 1m-40.

[0363] The RF processor 1m-10 can perform functions of sending / receiving signals through a radio channel, such as frequency band conversion or amplification of signals. That is, the RF processor 1m-10 can up-convert the baseband signal provided from the baseband processor 1m-20 into an RF band signal, and then can transmit the RF band signal through an antenna, and can down-convert the RF band signal received through the antenna into a baseband signal. For example, the RF processor 1m-10 may include a transmitting filter, a receiving filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), and an analog-to-digital converter (ADC). Although in Figure 1M Only one antenna is shown in the figure, and the terminal may include multiple antennas. Moreover, the RF processor 1m-10 may include multiple RF chains. In addition, the RF processor 1m-10 can perform beamforming. For beamforming, the RF processor 1m-10 can adjust the phase and size of each signal sent / received through multiple antennas or antenna elements. Moreover, the RF processor 1m-10 can perform MIMO and can receive multiple layers during MIMO operation. The RF processor 1m-10 can perform receive beam scanning by appropriately configuring multiple antennas or antenna elements, or can adjust the direction and beam width of the receive beam under the control of the controller 1m-40 so that the receive beam is coordinated with the transmit beam.

[0364] The baseband processor 1m-20 can convert between baseband signals and bit streams according to the physical layer specifications of the system. For example, during data transmission, the baseband processor 1m-20 can generate complex symbols by encoding and modulating the transmission bit stream. In addition, during data reception, the baseband processor 1m-20 can reconstruct the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 1m-10. For example, according to the orthogonal frequency division multiplexing (OFDM) method, during data reception, the baseband processor 1m-20 can generate complex symbols by encoding and modulating the transmission bit stream, the complex symbols can be mapped to subcarriers, and OFDM symbols can be configured by inverse fast Fourier transform (IFFT) and cyclic prefix (CP) insertion. In addition, during data reception, the baseband processor 1m-20 can segment the baseband signal provided from the RF processor 1m-10 into OFDM symbols, the signal mapped to the subcarrier can be reconstructed by fast Fourier transform (FFT), and then the received bit stream can be reconstructed by demodulating and decoding the signal.

[0365] As described above, the baseband processor 1m-20 and the RF processor 1m-10 can send and receive signals. Therefore, the baseband processor 1m-20 and the RF processor 1m-10 can be referred to as a transmitter, a receiver, a transceiver, or a communicator. In addition, at least one of the baseband processor 1m-20 or the RF processor 1m-10 may include multiple communication modules that support a variety of different radio access technologies. In addition, at least one of the baseband processor 1m-20 or the RF processor 1m-10 may include different communication modules to process signals of different frequency bands. For example, different radio access technologies may include LTE networks and NR networks. Moreover, different frequency bands may include ultra-high frequency (SHF) (e.g., 2.5 GHz or 5 GHz) bands and millimeter wave (mmWave) (e.g., 60 GHz) bands.

[0366] The memory 1m-30 may store basic programs, application programs, and data such as configuration information for operating the terminal. The memory 1m-30 may provide the stored data according to a request of the controller 1m-40.

[0367] The controller 1m-40 can control the overall operation of the terminal. For example, the controller 1m-40 can send / receive signals through the baseband processor 1m-20 and the RF processor 1m-10. In addition, the controller 1m-40 can write data to the memory 1m-40 and read data from the memory 1m-40. To this end, the controller 1m-40 may include at least one processor. For example, the controller 1m-40 may include a communication processor (CP) for controlling communication and an application processor (AP) for controlling an upper layer such as an application.

[0368] Figure 1N is a block diagram showing the structure of a base station (eg, a transmit receive point (TRP)) according to an embodiment of the present disclosure.

[0369] like Figure 1N As shown, the base station may include an RF processor 1n-10, a baseband processor 1n-20, a backhaul communicator 1n-30, a memory 1n-40, and a controller 1n-50.

[0370] The RF processor 1n-10 can perform functions of transmitting / receiving signals through a radio channel, such as frequency band conversion or amplification of signals. That is, the RF processor 1n-10 can up-convert the baseband signal provided from the baseband processor 1n-20 into an RF band signal, which can then be transmitted through an antenna, and can down-convert the RF band signal received through an antenna into a baseband signal. For example, the RF processor 1n-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC. Although in Figure 1NOnly one antenna is shown in the figure. In this case, the first connection node may include multiple antennas. In addition, the RF processor 1n-10 may include multiple RF chains. In addition, the RF processor 1n-10 can perform beamforming. For beamforming, the RF processor 1n-10 can adjust the phase and size of each signal sent / received through multiple antennas or antenna elements. The RF processor 1n-10 can perform downlink MIMO operations by sending one or more layers.

[0371] The baseband processor 1n-20 can convert between baseband signals and bit streams according to the physical layer specification of the first radio access technology. For example, during data transmission, the baseband processor 1n-20 can generate complex symbols by encoding and modulating the transmission bit stream. In addition, during data reception, the baseband processor 1n-20 can reconstruct the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 1n-10. For example, according to the OFDM method, during data transmission, the baseband processor 1n-20 can generate complex symbols by encoding and modulating the transmission bit stream, the complex symbols can be mapped to subcarriers, and then the OFDM symbols can be configured by IFFT and CP insertion. In addition, during data reception, the baseband processor 1n-20 can segment the baseband signal provided from the RF processor 1n-10 into OFDM symbols, the signal mapped to the subcarrier can be reconstructed by FFT, and then the received bit stream can be reconstructed by demodulating and decoding the signal. As described above, the baseband processor 1n-20 and the RF processor 1n-10 can send and receive signals. Therefore, the baseband processor 1n-20 and the RF processor 1n-10 can be referred to as a transmitter, a receiver, a transceiver, a communicator, or a wireless communicator.

[0372] The backhaul communicator 1n-30 may provide an interface for communicating with other nodes in the network.

[0373] The memory 1n-40 may store basic programs, application programs, and data such as configuration information for operating a base station. In particular, the memory 1n-40 may store information about bearers assigned to connected terminals and measurement results reported from connected terminals. In addition, the memory 1n-40 may store standard information for determining whether to provide or stop multiple connectivity to a terminal. The memory 1n-40 may provide stored data according to a request from the controller 1n-50.

[0374] The controller 1n-50 may control the overall operation of the base station. For example, the controller 1n-50 may send / receive signals through the RF processor 1n-10 and the baseband processor 1n-20 or the backhaul communicator 1n-30. In addition, the controller 1n-50 may write data to the memory 1n-40 and read data from the memory 1n-40. To this end, the controller 1n-50 may include at least one processor.

[0375] In wireless communication systems, high frequency bands and wide bandwidths are used for downlinks, so that a large amount of transmission resources can be ensured. Moreover, because a large number of antennas can be physically installed and used for base stations, beamforming gain and high signal strength can be achieved, and therefore more data can be sent to the terminal in the downlink by using the same frequency / time resources. However, since the terminal has a physically smaller size and high frequency band and wide bandwidth are not easy to use for uplinks, a bottleneck phenomenon may occur in uplink transmission resources compared to downlink transmission resources. Moreover, because the maximum transmission power level of the terminal is much smaller than the maximum transmission power level of the base station, a reduction in the coverage of uplink data transmission occurs. Therefore, it is necessary to use transmission resources effectively by compressing uplink data.

[0376] A method of compressing uplink data may be a method of performing data compression serially based on previous data. Therefore, when one data in a series of compressed data is lost or discarded, or experiences decompression failure, decompression may fail for all data after the data is lost or discarded or experiences decompression failure.

[0377] Whenever data is received from an upper layer, the transmitting PDCP layer may drive a PDCP discard timer for each data, may perform an uplink compression process when an uplink compression process is configured, may configure an uplink data compression (UDC) header, may perform encryption on data for which uplink data compression is performed, and may generate a PDCP packet data unit (PDU) by allocating a PDCP sequence number and configuring a PDCP header. When the PDCP discard timer expires, the transmitting PDCP layer may assume that the data corresponding to the PDCP discard timer is no longer valid and may discard the data.

[0378] Therefore, once the transmitting PDCP layer discards previously generated data (e.g., PDCP PDU) due to expiration of the PDCP discard timer, one of a series of compressed data is discarded, and thus continuous data decompression failures may occur in the receiving PDCP layer due to the discarded or lost compressed data.

[0379] An embodiment of the present disclosure may provide a process in which a transmitting PDCP layer (terminal or base station) in a wireless communication system compresses and transmits data in an uplink or downlink, and a receiving PDCP layer (base station or terminal) receives and decompresses the data. In addition, an embodiment of the present disclosure may provide a method for supporting a data transmission / reception process (such as a specific header format) in which a transmitter end compresses and transmits data, and a receiver end decompresses the data, a method for solving a decompression failure, and a method for solving a problem when the transmitting PDCP layer discards data due to a PDCP discard timer. In addition, the method may be applied to a process in which a base station compresses downlink data and sends the compressed downlink data to a terminal, and the terminal receives and decompresses the compressed downlink data. According to an embodiment of the present disclosure, because the transmitter end compresses and transmits data, more data can be transmitted and coverage can be improved.

[0380] Furthermore, when a data decompression error occurs in the reception PDCP layer or when processing received compressed data, embodiments of the present disclosure may provide efficient operation of the reception PDCP layer according to an indicator of a user data compression header.

[0381] The working principle of the present disclosure will be described in detail with reference to the accompanying drawings. While describing the present disclosure, detailed descriptions of related well-known functions or configurations that may obscure the main points of the present disclosure are omitted. The terms used herein are defined in consideration of the functions in the present disclosure, but these terms may vary according to the intentions of users or operators, precedents, etc. Therefore, the terms used herein must be defined based on the meaning of the terms and the descriptions in the full text of the specification.

[0382] Furthermore, while describing the present disclosure, detailed descriptions on related well-known functions or configurations that may obscure the gist of the present disclosure are omitted. Embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings.

[0383] Hereinafter, for the convenience of explanation, the terms indicating connection nodes, the terms indicating network entities, the terms indicating messages, the terms indicating interfaces between network entities, and the terms indicating various identification information used in the following description are exemplified. Therefore, the present disclosure is not limited to the terms to be described later, but other terms indicating objects having the same technical meaning may be used.

[0384] In the following, for ease of explanation, the present disclosure uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard. However, the present disclosure is not limited to the above terms and names, and can also be applied to systems that comply with other standards. In the present disclosure, for ease of explanation, eNB may be used interchangeably with gNB. That is, a base station described as an eNB may refer to a gNB.

[0385] Figure 2A is a schematic diagram showing the structure of an LTE system according to an embodiment of the present disclosure.

[0386] Reference Figure 2A ,The radio access network of the LTE system may include Evolved Node B (ENB) (Node B or base station) 2a-05, 2a-10, 2a-15 and 2a-20, Mobility Management Entity (MME) 2a-25 and Serving Gateway (S-GW) 2a-30. User Equipment (UE) 2a-35 may be connected to an external network through ENB 2a-05, 2a-10, 2a-15 and 2a-20 and S-GW 2a-30.

[0387] exist Figure 2A In the present invention, ENB 2a-05, 2a-10, 2a-15 and 2a-20 may correspond to the existing Node B of UMTS. Each ENB may be connected to UE 2a-35 via a radio channel and may perform more complex functions than the existing Node B. Because all user traffic data including real-time services such as Voice over IP (VoIP) over Internet Protocol are served through a shared channel in the LTE system, an entity for collecting and scheduling buffer status information, available transmission power status information and channel status information of the UE may be required, and each of ENB 2a-05 to 2a-20 may be used as such an entity. One ENB may generally control multiple cells. For example, in order to achieve a data rate of 100Mbps, the LTE system may use orthogonal frequency division multiplexing (OFDM) with a bandwidth of 20MHz as a radio access technology. In addition, adaptive modulation and coding (AMC) for determining a modulation scheme and a channel coding rate according to the channel state of the UE 2a-35 may be applied. The S-GW 2a-30 is an entity for providing a data bearer, and may generate or remove a data bearer under the control of the MME 2a-25. The MME 2a-25, which is an entity for performing various control functions and a mobility management function on the UE 2a-35, may be connected to a plurality of ENBs.

[0388] Figure 2B is a schematic diagram showing a radio protocol architecture in an LTE system according to an embodiment of the present disclosure.

[0389] Reference Figure 2B,The wireless protocol architecture of the LTE system includes the Packet Data Convergence Protocol (PDCP) layers 2b-05 and 2b-40, the Radio Link Control (RLC) layers 2b-10 and 2b-35, and the Medium Access Control (MAC) layers 2b-15 and 2b-30 for the UE and ENB respectively. The PDCP layers 2b-05 and 2b-40 may be responsible for IP header compression / decompression, for example. The main functions of each PDCP layer can be summarized as follows.

[0390] -Header compression and decompression: ROHC only

[0391] -Transfer user data

[0392] - In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM

[0393] - For split bearers in DC (supports RLC AM only): PDCP PDU routing for transmission and PDCP PDU reordering for reception

[0394] - Duplicate detection of lower layer SDUs during PDCP re-establishment for RLC AM

[0395] - Retransmit PDCP SDUs at handover and, for split bearers in DC, retransmit PDCP PDUs during PDCP data recovery for RLC AM

[0396] -Encryption and decryption

[0397] - Timer-based SDU discard in uplink

[0398] Each of the RLC layers 2b-10 and 2b-35 may perform an ARQ operation by reconfiguring a PDCP packet data unit (PDU) to an appropriate size. The main functions of each RLC layer may be summarized as follows.

[0399] -Transmission of upper layer PDU

[0400] - Error correction via ARQ (for AM data transmission only)

[0401] - Concatenation, segmentation and reassembly of RLC SDU (only for UM and AM data transmission)

[0402] - Re-segmentation of RLC data PDU (only for AM data transmission)

[0403] - Reordering of RLC data PDUs (only for UM and AM data transmission)

[0404] - Duplicate detection (for UM and AM data transmission only)

[0405] -Protocol error detection (for AM data transmission only)

[0406] -RLC SDU discard (only for UM and AM data transmission)

[0407] -RLC reconstruction

[0408] The MAC layers 2b-15 and 2b-30 are connected to various RLC layers configured in one UE and can multiplex RLC PDUs into MAC PDUs and demultiplex RLC PDUs from MAC PDUs. The main functions of each MAC layer can be summarized as follows.

[0409] - Mapping between logical channels and transport channels

[0410] - Multiplexing or demultiplexing MAC SDUs belonging to one or different logical channels into or from a transport block (TB) delivered to the physical layer on a transport channel

[0411] -Dispatch information report

[0412] - Error correction through HARQ

[0413] - Priority handling between logical channels of a UE

[0414] - Prioritization between UEs through dynamic scheduling

[0415] -MBMS service logo

[0416] -Transmission format selection

[0417] -filling

[0418] Each of the physical (PHY) layers 2b-20 and 2b-25 can channel encode and modulate upper layer data into OFDM symbols and send the OFDM symbols through a radio channel, or demodulate OFDM symbols received through a radio channel, decode the channel, and deliver the OFDM symbols to an upper layer.

[0419] Figure 2C is a schematic diagram showing a structure of a next generation mobile communication system according to an embodiment of the present disclosure.

[0420] Reference Figure 2C, the radio access network of the next generation mobile communication system (e.g., NR or 5G system) may include a new wireless node B (NR gNB or NR base station) 2c-10 and a new radio core network (NR CN) 2c-05. The new wireless user equipment (NR UE) 2c-15 may be connected to an external network through the NR gNB 2c-10 and the NR CN 2c-05.

[0421] exist Figure 2C In the present invention, NR gNB 2c-10 corresponds to the evolved Node B (eNB) of the existing LTE system. NR gNB 2c-10 can be connected to NR UE 2c-15 through a radio channel and can provide better services than the existing Node B. Because all user service data are served through shared channels in the next generation mobile communication system, an entity for collecting and scheduling the buffer status information, available transmission power status information and channel status information of the UE may be required, and NR NB2c-10 can be used as such an entity. One NR gNB 2c-10 can generally control multiple cells. The next generation mobile communication system can currently have a bandwidth greater than the maximum bandwidth of the existing LTE to achieve ultra-high data rates, orthogonal frequency division multiplexing (OFDM) can be used as a radio access technology, and beamforming technology can be used in addition. In addition, adaptive modulation and coding (AMC) for determining the modulation scheme and channel coding rate according to the channel state of the NR UE 2c-15 can be applied. NRCN 2c-05 can perform functions such as mobility support, bearer configuration and QoS configuration. NR CN 2c-05, which is an entity for performing various control functions and mobility management functions on NR UE 2c-15, is connected to multiple base stations. In addition, the next-generation mobile communication system can cooperate with the existing LTE system, and NR CN 2c-05 can be connected to MME 2c-25 through a network interface. MME 2c-25 can be connected to eNB 2c-30, which is an existing base station.

[0422] Figure 2D is a schematic diagram showing a radio protocol architecture of a next generation mobile communication system according to an embodiment of the present disclosure.

[0423] Reference Figure 2D , the radio protocol architecture of the next generation mobile communication system may include NR PDCP layers 2d-05 and 2d-40, NR RLC layers 2d-10 and 2d-35, and NR MAC layers 2d-15 and 2d-30 in the UE and the NR gNB. The main functions of each of the NR PDCP layers 2d-05 and 2d-40 may include some of the following functions.

[0424] -Header compression and decompression: ROHC only

[0425] -Transfer user data

[0426] - Sequential delivery of upper layer PDUs

[0427] - Out-of-order delivery of upper layer PDUs

[0428] - Reordering of received PDCP PDUs

[0429] - Duplicate detection of lower layer SDU

[0430] -Retransmission of PDCP SDU

[0431] -Encryption and decryption

[0432] - Timer-based SDU discard in uplink

[0433] In the above description, the reordering function of the NR PDCP layer may refer to a function of reordering PDCP PDUs received from a lower layer based on a PDCP sequence number (SN), and may include a function of delivering the reordered data to an upper layer in sequence or out of sequence, a function of recording lost PDCP PDUs by reordering received PDCP PDUs, a function of reporting status information of lost PDCP PDUs to a transmitter, and a function of requesting retransmission of lost PDCP PDUs.

[0434] The main functions of NR RLC layers 2d-10 and 2d-35 may include some of the following functions.

[0435] -Transmission of upper layer PDU

[0436] - Sequential delivery of upper layer PDUs

[0437] - Out-of-order delivery of upper layer PDUs

[0438] - Error correction via ARQ

[0439] - Concatenation, segmentation and reassembly of RLC SDU

[0440] - Re-segmentation of RLC data PDUs

[0441] - Reordering of RLC data PDUs

[0442] - Duplicate detection

[0443] -Protocol error detection

[0444] -RLC SDU discarded

[0445] -RLC reconstruction

[0446] In the above description, the sequential delivery function of the NR RLC layer may refer to a function of sequentially delivering RLC SDUs received from a lower layer to an upper layer, and may include at least one of the following functions: a function of reassembling a plurality of RLC SDUs segmented from one RLC SDU, and a function of delivering the reassembled RLC SDU when a segmented RLC SDU is received, a function of reordering the received RLC PDU based on the RLCSN or the PDCP SN, a function of recording lost RLC PDUs by reordering the received RLC PDUs, a function of reporting status information of lost RLC PDUs to a transmitter, a function of requesting retransmission of lost RLC PDUs, a function of delivering only the RLC SDUs before the lost RLC SDU to the upper layer when the lost RLC SDU exists, a function of delivering all RLC SDUs received before the timer is started to the upper layer when there is a lost RLC SDU when a certain timer expires, or a function of delivering all RLC SDUs received until the current time to the upper layer when there is a lost RLC SDU when a certain timer expires. In addition, the NR RLC layer may process the RLC PDU in the order of reception (in the order of arrival regardless of the SN) and deliver the RLC PDU to the PDCP layer out of order (regardless of the sequence delivery order), or reassemble the segmented RLC PDU received or stored in the buffer into a whole RLC PDU, and process and deliver the RLC PDU to the PDCP layer. The NR RLC layer may not have a cascading function, and the cascading function may be performed by the NR MAC layer, or may be replaced by a multiplexing function of the NR MAC layer.

[0447] The out-of-order delivery function of the NR RLC layer refers to a function of directly delivering the RLC SDU received from the lower layer to the upper layer out of order, and may include a function of reassembling multiple RLC SDUs segmented from one RLC SDU when a segmented RLC SDU is received and delivering the reassembled RLC SDU, and a function of recording lost RLC PDUs by storing the RLC SN or PDCP SN of the received RLC PDU and reordering the received RLC PDUs.

[0448] Each of the NR MAC layers 2d-15 and 2d-30 can be connected to multiple NR RLC layers configured for one UE, and the main functions of each NR MAC layer may include some of the following functions.

[0449] - Mapping between logical channels and transport channels

[0450] -Multiplexing / demultiplexing of MAC SDU

[0451] -Dispatch information report

[0452] - Error correction through HARQ

[0453] - Priority handling between logical channels of a UE

[0454] - Prioritization between UEs through dynamic scheduling

[0455] -MBMS service logo

[0456] -Transmission format selection

[0457] -filling

[0458] Each of the NR PHY layers 2d-20 and 2d-25 can channel encode and modulate upper layer data into OFDM symbols and send the OFDM symbols through a radio channel, or can demodulate OFDM symbols received through a radio channel, decode the channel, and deliver the OFDM symbols to an upper layer.

[0459] An embodiment of the present disclosure may provide a process in which a terminal in a wireless communication system compresses and sends data in an uplink, and a base station decompresses the data. In addition, an embodiment of the present disclosure may provide a method in which a transmitter end compresses and sends data, and a receiver end decompresses the data (e.g., a specific header format) to support a data transmission / reception process, or provide a method for resolving decompression failures. In addition, a method according to an embodiment of the present disclosure is applied to a process in which a base station compresses a downlink and sends the compressed downlink data to a terminal, and the terminal receives and decompresses the compressed downlink data. According to an embodiment of the present disclosure, because the transmitter end compresses and transmits data, more data can be transmitted and coverage can be improved.

[0460] Figure 2E It is a schematic diagram for describing a process in which a gNB configures whether to perform uplink data compression when a UE configures a connection to a network according to an embodiment of the present disclosure.

[0461] Reference Figure 2E In this embodiment of the present disclosure, a process in which a UE switches from an RRC idle mode or an RRC deactivation (light connection) mode to an RRC connected mode and configures a connection to a network will be described. In addition, a process for configuring whether to perform uplink data compression (UDC) will be described.

[0462] In operation 2e-01, when a UE that transmits / receives data in RRC connected mode does not transmit / receive data for a certain period of time or for a certain reason, the gNB may send an RRC connection release message to the UE so that the UE switches to RRC idle mode. When a UE that is not currently connected to the network (hereinafter referred to as an idle mode UE) has data to transmit, the UE may perform an RRC connection establishment procedure with the gNB.

[0463] In operation 2e-05, the UE may establish backward transmission synchronization with the gNB through a random access procedure, and may send an RRCConnectionRequest message to the gNB. The RRCConnectionRequest message may include an identifier of the UE, an establishment cause, etc.

[0464] In operation 2e-10, the gNB may send an RRCConnectionSetup message so that the UE configures the RRC connection. The RRCConnectionSetup message may include information indicating whether an uplink data compression (UDC) method or a downlink data compression method is used for each logical channel (logical channel configuration), each bearer, or each PDCP entity (PDCP configuration). In addition, in more detail, the RRCConnectionSetup message may indicate whether an uplink data compression (UDC) method is used, which UDC method is only for which IP flow or which QoS flow in each logical channel, each bearer, or each PDCP entity (or Service Data Adaptation Protocol (SDAP) entity) (for example, information about IP flows or QoS flows to use or not use the uplink data compression method may be configured in the SDAP entity, so that the SDAP entity may indicate whether the PDCP entity uses the uplink data compression method for each QoS flow. Alternatively, the PDCP entity itself may check each QoS flow and may determine whether to apply the uplink data compression method). In addition, when the gNB may indicate the use of an uplink data compression method, the gNB may indicate an identifier of a predefined library or dictionary to be used in the uplink data compression method or a buffer size to be used in the uplink data compression method.

[0465] Furthermore, the RRCConnectionSetup message may include an uplink decompression setup or release command. In addition, when the gNB configures the uplink data compression method to be used, the gNB may always configure the uplink data compression method using an RLC AM bearer (due to the lossless mode of the ARQ function and the retransmission function) and may not configure using a header compression protocol (e.g., ROHC protocol). Furthermore, the RRCConnectionSetup message may include RRC connection configuration information. The RRC connection may be referred to as a signaling radio bearer (SRB) and may be used to send / receive RRC messages that are control messages between the UE and the gNB.

[0466] In operation 2e-15, the UE configuring the RRC connection may send an RRCConnectionSetupComplete message to the gNB. When the gNB does not know or does not want to check the UE capabilities of the UE configuring the current connection, the gNB may send a UE capability query message. The UE may send a UE capability report message. The UE capability report message may include an indicator indicating whether the UE is capable of using an uplink data compression (UDC) method or a downlink data compression method. The RRCConnectionSetupComplete message may include a SERVICE REQUEST message, which is a control message used to request the MME to configure a bearer for a certain service.

[0467] In operation 2e-20, the gNB may send a SERVICE REQUEST message included in an RRCConnectionSetupComplete message to the MME, and the MME may determine whether to provide the service requested by the UE.

[0468] When the MME determines to provide the service requested by the UE, at operation 2e-25, the MME may send an INITIALCONTEXT SETUP REQUEST message to the gNB. The INITIALCONTEXT SETUP REQUEST message may include QoS information to be applied to configure a data radio bearer (DRB) or security information (e.g., a security key or a security algorithm) to be applied to the DRB.

[0469] In operations 2e-30 and 2e-35, the gNB may exchange SecurityModeCommand messages and SecurityModeComplete messages to configure the security mode with the UE.

[0470] In operation 2e-40, when the security mode is fully configured, the gNB may send an RRCConnectionReconfiguration message to the UE. The RRCConnectionReconfiguration message may include information indicating whether an uplink data compression (UDC) method or a downlink data compression method is used for each logical channel (logical channel configuration), each bearer, or each PDCP entity (PDCP configuration). In addition, in more detail, the RRCConnectionReconfiguration message may indicate whether an uplink data compression (UDC) method is used, which UDC method is only for which IP flow or which QoS flow in each logical channel, each bearer, or each PDCP entity (or SDAP entity) (for example, information about IP flows or QoS flows using or not using the uplink data compression method may be configured in the SDAP entity, so that the SDAP entity may indicate whether the PDCP entity uses the uplink data compression method for each QoS flow. Alternatively, the PDCP entity itself may check each QoS flow and may determine whether to apply the uplink data compression method). In addition, when the gNB may indicate the use of an uplink data compression method, the gNB may indicate an identifier of a predefined library or dictionary to be used in the uplink data compression method or a buffer size to be used in the uplink data compression method. Moreover, the RRCConnectionReconfiguration message may include an uplink decompression setup or release command. In addition, when the gNB configures the uplink data compression method to be used, the gNB may always configure the uplink data compression method using an RLC AM bearer (due to the lossless mode of the ARQ function and the retransmission function) and may not configure it using a header compression protocol (e.g., the ROHC protocol).

[0471] In addition, the RRCConnectionReconfiguration message may include DRB configuration information for processing user data, and in operation 2e-45, the UE may configure the DRB by applying the DRB configuration information, and may send an RRCConnectionReconfiguration CompletionReconfiguration message to the gNB.

[0472] In operation 2e-50, the gNB, which has fully configured the DRB with the UE, may send an INITIALCONTEXT SETUP COMPLETE message to the MME.

[0473] In operations 2e-55 and 2e-60, the MME receiving the INITIAL CONTEXT SETUP COMPLETE message may exchange an S1 BEARER SETUP message and an S1 BEARER SETUP RESPONSE message with the S-GW to configure the S1 bearer. The S1 bearer is a data transmission connection configured between the S-GW and the gNB and may correspond to the DRB in a one-to-one manner.

[0474] When the above process is completed, in operations 2e-65 and 2e-70, the UE can send data to the gNB through the S-GW and receive data from the gNB. The general data transmission process may include three steps: RRC connection configuration, security configuration, and DRB configuration.

[0475] In addition, in operation 2e-75, the gNB may send an RRCConnectionReconfiguration message to the UE to update, add, or change the configuration for some reason. The RRCConnectionReconfiguration message may include information indicating whether an uplink data compression (UDC) method or a downlink data compression method is used for each logical channel (logical channel configuration), each bearer, or each PDCP entity (PDCP configuration). In addition, in more detail, the RRCConnectionReconfiguration message may indicate whether an uplink data compression (UDC) method is used, and the UDC method is only used for which IP flow or which QoS flow in each logical channel, each bearer, or each PDCP entity (or SDAP entity) (for example, information about IP flows or QoS flows using or not using the uplink data compression method can be configured in the SDAP entity, so that the SDAP entity can indicate whether the PDCP entity uses the uplink data compression method for each QoS flow. Alternatively, the PDCP entity itself can check each QoS flow and can determine whether to apply the uplink data compression method). In addition, when the gNB may indicate the use of an uplink data compression method, the gNB may indicate an identifier of a predefined library or dictionary to be used in the uplink data compression method or a buffer size to be used in the uplink data compression method. Moreover, the RRCConnectionReconfiguration message may include an uplink decompression setup or release command. In addition, when the gNB configures the uplink data compression method to be used, the gNB may always configure the uplink data compression method using an RLC AM bearer (due to the lossless mode of the ARQ function and the retransmission function) and may not configure it using a header compression protocol (e.g., the ROHC protocol).

[0476] Figure 2F is a schematic diagram illustrating a data structure and a process of performing uplink or downlink data compression according to an embodiment of the present disclosure.

[0477] Uplink data 2f-05 may be generated as data corresponding to services such as video upload, photo upload, web browser, and voice over LTE (VoLTE). The data generated in the application layer may be processed by a network data transport layer such as Transmission Control Protocol and Internet Protocol (TCP / IP) or User Datagram Protocol (UDP), headers 2f-10 and 2f-15 may be configured, and may be delivered to the PDCP layer. When the PDCP layer receives data (PDCP SDU) from an upper layer, the PDCP layer may perform the following process.

[0478] When the uplink data compression method is configured to be used by the PDCP layer in the RRC message, such as Figure 2E As shown in operations 2e-10, 2e-40 or 2e-75, the PDCP layer may perform an uplink data compression method for the PDCP SDU represented by 2f-20, and may compress the uplink data. In addition, the PDCP layer may configure a UDC header (a header for compressing uplink data) 2f-25, may perform encryption on compressed data other than the UDC header, may perform integrity protection when configured, may configure a PDCP header 2f-30, and may configure a PDCP PDU. The PDCP layer according to an embodiment of the present disclosure may include a UDC compression / decompression entity, may determine whether to perform a UDC process on each data configured in an RRC message, and may use a UDC compression / decompression entity. At the transmitter end, the transmitting PDCP layer may perform data compression by using a UDC compression entity, and at the receiver end, the receiving PDCP layer may perform data decompression by using a UDC decompression entity.

[0479] When the terminal compresses downlink data as well as uplink data, it can be applied Figure 2F Furthermore, the description of uplink data may be applied to downlink data.

[0480] Figure 2G It is a schematic diagram for describing an uplink data compression method according to an embodiment of the present disclosure.

[0481] In more detail, Figure 2GIt is a schematic diagram for describing an uplink data compression algorithm based on DEFLATE. The uplink data compression algorithm based on DEFLATE is a lossless compression algorithm. The uplink data compression algorithm based on DEFLATE can basically compress uplink data by combining Huffman coding with the LZ77 algorithm. The LZ77 algorithm may include an operation of performing a search for recurrence of data in a sliding window, and when recurrence is found in the sliding window, data compression is performed by representing the repeated data in the sliding window as a position and length. In the uplink data compression (UDC) method, the sliding window is called a buffer and can be set to 8 kilobytes or 32 kilobytes. That is, the sliding window or buffer can record 8192 or 32768 characters, recurring data can be found, and data compression can be performed by representing the repeated data as a position and length. Therefore, since the LZ77 algorithm is a sliding window method, that is, because the previously encoded data is updated in the buffer and then the next data is encoded immediately, continuous data slices can have correlations therebetween. Therefore, only when the previously encoded data is decoded normally, the next data can be decoded normally. Codes expressed as positions and lengths and compressed using the LZ77 algorithm can be further compressed by Huffman coding. Huffman coding can be designed to search for repeated characters and perform compression again by assigning short codes to more frequent characters and long codes to less frequent characters. Huffman coding is a prefix coding and is an optimal coding method by which all codes are uniquely decodable.

[0482] Reference Figure 2G The transmitter can encode the original data 2g-05 by using the LZ77 algorithm (2g-10), can update the buffer (2g-15), and can configure the UDC header by generating a checksum bit for the content (or data) of the buffer. The receiver can use the checksum bit to determine whether the buffer status is valid.

[0483] The code encoded by using the LZ77 algorithm can be compressed again by using Huffman coding and can be sent as uplink data (2g-25). The receiver end can perform a decompression process on the compressed data received from the transmitter end in a manner opposite to that of the transmitter end. That is, the receiver end can perform Huffman decoding (2g-30), can update the buffer (2g-35), and can determine whether the updated buffer is valid by using the checksum bit of the UDC header. When it is determined that there is no error in the checksum bit, the receiver end can decompress the data by performing decoding using the LZ77 algorithm (2g-40), can reconstruct the original data, and can deliver the decompressed data to the upper layer (2g-45).

[0484] Because the LZ77 algorithm is a sliding window method, that is, because the previously encoded data is updated in the buffer and then the encoding is immediately performed on the next data as described above, the continuous data slices can have correlation therebetween. Therefore, only when the previously encoded data is decoded normally, the next data can be decoded normally. Therefore, the receiving PDCP layer can check the PDCP sequence number of the PDCP header, can check the UDC header (for example, check the indicator indicating whether data compression is performed), and can perform a data decompression process on the compressed data in ascending order of the PDCP sequence number.

[0485] According to an embodiment of the present disclosure, the process of the gNB configuring uplink data compression (UDC) for the UE and the process of the UE performing uplink data compression can be as follows.

[0486] Reference Figure 2EAs shown in operation 2e-10, 2e-40, or 2e-75, the gNB may configure or release uplink data compression for a logical channel or bearer that configures an RLC AM mode in the UE through an RRC message. In addition, the gNB may reset the UDC entity (or protocol) of the PDCP layer of the UE by using an RRC message. When the gNB may reset the UDC entity (or protocol), this may mean that the gNB may reset the UDC buffer for uplink data compression of the UE so as to achieve synchronization between the UDC buffer of the UE and the UDC buffer for uplink data decompression of the gNB. In the operation of resetting the buffer of the UDC entity, a new PDCP control PDU may be defined, and the transmitter end (gNB) may reset the UDC buffer of the receiver end (UE) through the PDCP control PDU instead of the RRC message to achieve synchronization of user data compression and decompression between the transmitter end and the receiver end. In addition, whether to perform uplink data compression may be determined for each bearer, each logical channel, or each PDCP layer by using an RRC message. In more detail, whether to perform uplink data decompression can be configured for each IP flow (or QoS flow) in one bearer, logical channel or PDCP layer by using the above-mentioned message.

[0487] In addition, by using an RRC message, the gNB can configure the PDCP discard timer value in the UE. The PDCP discard timer value for data without uplink data compression and the PDCP discard timer value for data with uplink data compression applied can be configured separately.

[0488] When the UE is configured to perform uplink data compression on a specific bearer, logical channel or PDCP layer (or on a QoS flow of a specific bearer, logical channel or PDCP layer) by using an RRC message, the UE can reset the buffer in the UDC entity of the PDCP layer according to the configuration, and can prepare the uplink data compression process. When data (PDCPSDU) is received from the upper layer, when the UE is configured to perform uplink data compression on the PDCP layer, the UE can perform uplink data compression on the received data. When the UE is configured to perform uplink data compression on a specific QoS flow of the PDCP layer, the UE can determine whether to perform uplink data compression by checking the indication of the upper SDAP layer or the QoS flow identifier, and can perform uplink data compression. When performing uplink data compression (UDC) and updating the buffer according to the uplink data compression, the UE can configure the UDC buffer. When performing uplink data compression (UDC), the PDCP SDU received from the upper layer can be compressed into UDC data (UDC block) with a smaller size. The UE can configure the UDC header for the compressed UDC data. The UDC header may include an indicator indicating whether uplink data compression is performed or not performed (eg, indicating that UDC is applied when a 1-bit indicator of the UDC header is 0, and that UDC is not applied when the 1-bit indicator is 1).

[0489] A case where uplink data compression is not applied may include a case where a PDCP SDU data structure received from an upper layer is not a repetitive data structure and thus data compression cannot be performed by using a UDC method (eg, DEFLATE algorithm).

[0490] When the UE performs uplink data compression (UDC) on data (PDCP SDU) received from an upper layer and updates the UDC buffer, the PDCP layer at the receiver end can calculate a checksum bit to check the validity of the updated UDC buffer, and can cause the calculated checksum bit to be included in the UDC buffer (the checksum bit can have a certain length. For example, 4 bits).

[0491] The transmitting PDCP layer may reset the transmitting UDC buffer, and may define and configure 1 bit in the UDC header 2i-02 of the first data to which UDC compression is newly applied after the transmitting UDC buffer is reset, to instruct the receiving PDCP layer to reset the receiving UDC buffer, and to newly perform UDC decompression from the data in which the UDC header 2i-02 is configured using the reset receiving UDC buffer. For example, the PDCP layer may define such as Fig.2IIn addition, the transmitting PDCP layer in which the UDC compression process is configured can indicate whether the UDC compression process is applied or not applied to the data received from the upper layer by defining a 1-bit indicator (e.g., FU field 2i-10) of the UDC header 2i-02.

[0492] The UE may perform ciphering on the data with or without uplink data decompression applied, may perform integrity protection when configured, and may deliver the data to lower layers.

[0493] Figure 2H is a view for describing a decompression failure occurring in an uplink or downlink data compression method according to an embodiment of the present disclosure.

[0494] As reference Figure 2G As described, an uplink data compression (UDC) algorithm (e.g., a DEFLATE algorithm (used to perform an LZ77 algorithm and then perform Huffman coding)) can be a method of updating previously compressed data in a buffer when performing data compression at the transmitter end, comparing the data with data to be compressed subsequently based on the buffer, searching for a repetitive structure, and compressing the repetitive structure into a position and a length.

[0495] Therefore, even when the receiver side performs decompression, the receiver side may have to perform decompression in the same compression order as that performed by the transmitter side in order to successfully perform decompression. For example, when the transmitter side has performed UDC compression on data of PDCP sequence numbers 1, 3, 4, and 5 and has not performed UDC compression on data of PDCP sequence number 2 (2h-05), the receiver side may have to perform decompression on the received data in the order of PDCP sequence numbers 1, 3, 4, and 5 in the PDCP layer in order to successfully perform decompression.

[0496] When the transmitter side performs UDC compression, because the UDC header indicates UDC compression, the receiver side can determine whether UDC compression has been applied by checking the UDC header. When the data of PDCP sequence number 3 (2h-15) is lost during the execution of a series of UDC decompression operations, all subsequent UDC decompression operations will fail. That is, UDC decompression cannot be performed on the data of PDCP sequence numbers 4 and 5 (2h-10). Therefore, lost data (packets) should not be generated during the uplink decompression process, and the receiver side may have to perform decompression in the same order as the UDC compression performed by the transmitter side. Therefore, it may be necessary to use the RLC AM mode without loss and retransmission function.

[0497] However, due to the PDCP discard timer of the PDCP layer, lost data may also be generated. That is, the PDCP layer may drive a timer for each data (packet or PDCP SDU) received from a higher layer by using a PDCP discard timer value configured in an RRC message. When the timer expires, the data corresponding to the timer is discarded. Therefore, when the timer of the data on which UDC compression is performed expires, the data may be discarded, and thus UDC decompression performed by the receiver end on the subsequent UDC compressed data segment may fail.

[0498] As described with reference to the 2G figure, according to an uplink data compression (UDC) algorithm (e.g., a DEFLATE algorithm (for performing an LZ77 algorithm and then performing Huffman coding)), the transmitter end may perform uplink data compression, and then a checksum bit may be generated by using the current content of the buffer, and the UDC header may be configured. The transmitter end may update the buffer by using the original data of the compressed data, may compare the data with the data to be subsequently compressed based on the buffer, may search for a repeated structure, and may compress the repeated structure into a position and a length. The checksum bit in the UDC header is used to determine the validity of the current buffer state before the UDC entity (or function) of the PDCP layer of the receiver end performs data decompression. That is, before the receiver end performs data decompression, the receiver end verifies the validity of the current UDC buffer of the receiver end by using the checksum bit of the UDC header, and when there is no checksum error, the receiver end may perform data decompression, and when a checksum failure occurs, the receiver end may not perform data decompression, and may report the checksum failure to the transmitter end to recover the data.

[0499] In an embodiment of the present disclosure, even when the receiver end performs decompression, the receiver end may have to perform decompression in the same compression order as that performed by the transmitter end in order to successfully perform decompression. For example, when the transmitter end has performed UDC compression on data of PDCP sequence numbers 1, 3, 4, and 5 and has not yet performed UDC compression on data of PDCP sequence number 2, the receiver end may have to perform decompression on the received data in the order of PDCP sequence numbers 1, 3, 4, and 5 in the PDCP layer in order to successfully perform decompression. When the transmitter end performs UDC compression, because the UDC header indicates UDC compression, the receiver end can determine whether UDC compression has been applied by checking the UDC header. When a checksum failure occurs for data of PDCP sequence number 3 during the execution of a series of UDC decompression operations, all subsequent UDC decompression operations may fail. That is, UDC decompression cannot be successfully performed on data of PDCP sequence numbers 4 and 5.

[0500] The embodiments of the present disclosure may provide the following checksum failure processing method for resolving checksum failure.

[0501] Fig.2I It is a diagram for describing a PDCP control PDU format applicable to a checksum failure handling method according to an embodiment of the present disclosure.

[0502] exist Fig.2I In the D / C field, the D / C field may be a field for identifying general data or PDCP layer control information (PDCP control PDU) in the PDCP layer, and the PDU type field may be a field for indicating the type of PDCP layer control information. According to the checksum failure processing method of an embodiment of the present disclosure, for feedback such as 2i-01, a 1-bit indicator (FE field) indicating whether a checksum failure occurs may be defined and used. When the value of the 1-bit indicator is 0, it may indicate that UDC decompression is usually performed, and when the value of the 1-bit indicator is 1, it may indicate that a checksum failure occurs during UDC decompression, and the UDC buffer of the transmission PDCP layer will be reset.

[0503] In an embodiment of the present disclosure, a new PDCP control PDU may be defined by assigning a reserved value (e.g., 011 or a reserved value between 100 and 111) to a PDU type to define a 2i-01 format, and the PDCP control PDU having the defined PDU type may be used as feedback for indicating a checksum failure.

[0504] [Table 1]

[0505] Bit Description

[0506] 000PDCP status report

[0507] 001 Inserted ROHC feedback packet

[0508] 010 LWA Status Report

[0509] 011 UDC checksum failure feedback

[0510] 100-111 Reserved

[0511] use Fig.2I An embodiment of a method for handling checksum failure of a PDCP control PDU is as follows.

[0512] When a receiver end (e.g., a base station) fails to check the checksum of a received UDC buffer for data on which uplink data decompression is to be performed, the receiver end may indicate that a checksum failure has occurred by sending a PDCP control PDU to the terminal. A new PDCP control PDU may be defined and used as a PDCP control PDU, or an existing PDCP control PDU may be changed and used as a PDCP control PDU, which is achieved by defining a new indicator in the changed existing PDCP control PDU. In another method, an indicator indicating that a UDC buffer is reset due to a checksum failure may be defined instead of a PDCP sequence number to indicate a checksum failure.

[0513] Operation of the receiver end: When a checksum failure occurs, the receiver end may directly reset the receiving UDC buffer. The receiver end may reorder the newly received data segments based on the PDCP sequence number, and then may check the UDC headers of the data segments in the ascending order of the PDCP sequence number. In this case, when all the multiple data segments are received in the order of the PDCP sequence number without gaps in the ascending order of the PDCP sequence number, because it is indicated that the transmitting UDC buffer has been reset due to the UDC checksum failure, the receiver end may discard the data segments that do not include the indicator indicating the reset of the receiving UDC buffer and have performed UDC compression and process the data segments whose UDC headers do not include the indicator indicating that the transmitting UDC buffer has been reset due to the UDC checksum failure and have not performed UDC compression, and deliver the processed data segments to a higher layer. According to the data whose UDC header includes the indicator indicating that the transmitting UDC buffer has been reset due to the UDC checksum failure and the receiving UDC buffer is to be reset, the receiver end may reset the receiving UDC buffer and may restart the decompression of the compressed data segments in the ascending order of the PDCP sequence number.

[0514] Operations at the transmitter end: When the transmitter end (terminal) receives the PDCP control PDU, the transmitter end can reset the transmit UDC buffer, can discard the data segments (such as PDCP PDU) that have not been transmitted among the data segments that have performed UDC compression before resetting the transmit UDC buffer, can perform uplink data compression (UDC) again on the original data segments (such as PDCP SDU) of the data segments that have not been transmitted based on the reset transmit UDC buffer, can update the UDC buffer, can include the checksum bit in the UDC header, perform encryption on the UDC header and the data part, can generate a PDCP header, can configure the PDCP PDU, and can transmit the PDCP PDU to a lower layer.

[0515] In addition, the transmitter end may include an indicator indicating that the transmission buffer has been reset or an indicator indicating that the reception buffer has been reset in the UDC header or the PDCP header of the newly configured PDCP PDU and may transmit the PDCP PDU, and may newly allocate PDCP sequence numbers that have not yet been transmitted in ascending order (i.e., when data encrypted using a PDCP count value and a security key and then transmitted is encrypted again using the same encryption PDCP count value and security key and then retransmitted, the risk of hacker attacks is increased, and therefore the transmitter end may comply with the rule of performing encryption and transmission once for one PDCP count value). In another method, when the transmitter end receives an indication indicating that a checksum failure has occurred, the transmitter end may reset the transmission UDC buffer, may perform new UDC compression only on the PDCP PDU to be newly configured or data whose PDCP sequence number is equal to or greater than the PDCP sequence number of data that has not yet been transmitted to a lower layer, and may transmit the data to a lower layer. In addition, the transmitter end may include an indicator indicating that the transmit UDC buffer has been reset (or an indicator indicating that the receive UDC buffer has been reset) in the PDCP header or the UDC header of the newly configured PDCP PDU, and may transmit the data (i.e., when data encrypted using a PDCP count value and a security key and then sent is encrypted again using the same PDCP count value and security key and then retransmitted, the risk of hacker attacks is increased, so the transmitter end may comply with the rule of performing encryption and transmission once for one PDCP count value).

[0516] However, due to the PDCP discard timer of the PDCP layer, a checksum failure may occur. That is, the PDCP layer may drive a timer for each data (packet or PDCP SDU) received from a higher layer by using a PDCP discard timer value configured in an RRC message. When the timer expires, the data corresponding to the timer may be discarded. Therefore, when the timer of the data on which UDC compression is performed expires, a portion of the UDC compressed data may be discarded, and thus the UDC decompression performed by the receiver end on the subsequent UDC compressed data segment may fail.

[0517] A first embodiment for preventing data loss when data on which UDC compression has been performed is discarded due to a PDCP discard timer in a transmission PDCP layer and reducing checksum-failed data in a receiver end may be provided as follows.

[0518] Operation at the transmitter end: When the uplink data compression process is configured and data that has not been sent and has been UDC compressed is discarded due to expiration of the PDCP discard timer, the transmitting PDCP layer may send data whose PDCP sequence number is greater than the PDCP sequence number of the discarded data and has been UDC compressed, and may discard all remaining data (e.g., data whose PDCP sequence number is greater than the next PDCP sequence number of the discarded data, which has been subjected to user data compression and is stored without being sent). In addition, when the data has been transmitted to the lower layer, the transmitting PDCP layer may send an indicator for discarding the data to the lower layer. The transmitting PDCP layer may stop data transmission until a PDCP control PDU indicating that a checksum failure has occurred is received. This is because, apparently, since part of the UDC compressed data or data corresponding to an intermediate sequence number of a sequential sequence number or data is discarded, a checksum failure may occur in the receiving PDCP layer for data (e.g., PDCP PDU) whose user data compression has been performed and whose PDCP sequence number is greater than the PDCP sequence number of the discarded data. Therefore, it can be expected that when sending data corresponding to the next PDCP sequence number of the discarded data, the receiving PDCP layer checks the checksum failure and sends the PDCP control PDU.

[0519] Therefore, the transmitting PDCP layer may reset the transmitting UDC buffer for user data compression upon or before receiving the PDCP control PDU indicating that a checksum failure has occurred (or in the case where the transmitting UDC buffer has been reset, the transmitting UDC buffer may not be reset), may apply the user data compression process again from the original data (e.g., PDCP SDU) of the data whose PDCP discard timer has not expired and has not been transmitted, or may apply the user data compression process from the original data (e.g., PDCP SDU) of the data whose PDCP discard timer has not expired and was last transmitted (transmitted data corresponding to the next PDCP sequence number of the discarded data), and may cipher, generate, and prepare data (e.g., PDCP PDU) in ascending order starting from a new PDCP sequence number or the first PDCP sequence number that has not been transmitted. After receiving the PDCP control PDU indicating that a checksum failure has occurred, the transmitting PDCP layer may restart the transmission of the newly generated and prepared data (e.g., PDCP PDU). That is, the transmitting PDCP layer may transfer the data to a lower layer.

[0520] In an embodiment of the present disclosure, a PDCP SDU may indicate original data received by a transmitting PDCP layer from a higher layer, and a PDCP PDU may indicate data to be sent to a lower layer after data processing by the transmitting PDCP layer. The data processing may include header compression, user layer data compression, encryption or integrity protection and verification configured in the PDCP layer. In addition, a PDCP PDU generated by performing data processing on a PDCP SDU may be data different from a PDCP SDU, the PDCP SDU may be stored even if the PDCP PDU is discarded, and the PDCP SDU may be discarded only by a PDCP data discard timer.

[0521] Therefore, when the user data compression process is configured, when a part of data that has been previously generated and on which user data compression has been performed is discarded due to the PDCP discard timer, because the data is regenerated from data that has not been transmitted or from the last transmitted data (transmitted data corresponding to the next PDCP sequence number of the discarded data), a checksum failure that may occur in data whose PDCP sequence number is greater than the PDCP sequence number of the discarded data can be reduced, and data loss can be prevented,

[0522] -When the receiving end (base station) detects a checksum failure of the receiving UDC buffer for the data on which uplink data decompression is to be performed, the receiving end may indicate that the checksum failure has occurred by sending a PDCP control PDU to the terminal. A new PDCP control PDU may be defined and used as the PDCP control PDU, or an existing PDCP control PDU may be changed and used as the PDCP control PDU, which is achieved by defining a new indicator in the changed existing PDCP control PDU. In another method, an indicator for resetting the UDC buffer due to the occurrence of a checksum failure may be defined instead of the PDCP sequence number to indicate the checksum failure.

[0523] -Operation of the receiver end: When a checksum failure occurs, the receiver end may directly reset the UDC buffer. The receiver end may reorder the newly received data segments based on the PDCP sequence number, and then may check the UDC header of the data segment in the ascending order of the PDCP sequence number. In this case, when all the multiple data segments are received in the order of the PDCP sequence number without gaps in the ascending order of the PDCP sequence number, because it is indicated that the transmission UDC buffer has been reset due to the UDC checksum failure, the receiver end may discard the data segment that does not include an indication for resetting the reception UDC buffer and has performed UDC compression, and may process the data segment whose UDC header does not include an indicator indicating that the transmission UDC buffer has been reset due to the UDC checksum failure and has not performed UDC compression, and deliver the processed data segment to a higher layer. According to the data whose UDC header includes an indicator indicating that the transmission UDC buffer has been reset due to the UDC checksum failure and the reception UDC buffer is to be reset, the receiver end may reset the reception UDC buffer and may restart decompressing the compressed data segments in the ascending order of the PDCP sequence number.

[0524] The second embodiment for preventing data loss when data on which UDC compression has been performed is discarded due to a PDCP discard timer in a transmission PDCP layer and reducing checksum-failed data in a receiver end may be provided as follows.

[0525] In order to solve these problems, in the second embodiment, when the first data that has not been transmitted and has been UDC compressed is discarded due to the expiration of the PDCP discard timer, the transmitting PDCP layer in which the UDC compression process is configured may discard the first data, and may discard all the second data (e.g., PDCP PDU) whose PDCP sequence number is greater than the PDCP sequence number of the first data and has not been transmitted, which has been UDC compressed and stored. This is because when one of the data to which UDC compression is continuously applied is lost, UDC decompression failure may occur in the receiving PDCP layer for the data to which UDC compression is applied after the discarded data, and all the data may be discarded.

[0526] After discarding the first data, the transmitting PDCP layer may prepare a new UDC compression process by resetting the transmitting UDC buffer. When the UDC buffer may be reset, it may be indicated that the values ​​of the UDC buffer are all reset to 0. In another method, when the predetermined information (predetermined dictionary) is configured in the RRC message, it may be indicated that the predetermined information is input and reset to the value of the UDC buffer.

[0527] Because the transmitting PDCP layer has not yet transmitted the original data (e.g., PDCP SDU) of the second data (e.g., PDCP PDU) after the transmission UDC buffer is reset, the transmitting PDCP layer may reapply the UDC compression process to the original data of the second data (e.g., PDCP SDU, or original data received from a higher layer without applying data processing in the PDCP layer) by using the reset transmission UDC buffer. Each UDC header may be generated and configured, and then data transmission may be performed by applying encryption or integrity protection.

[0528] In addition, the transmitting PDCP layer may indicate to reset the receiving UDC buffer of the receiving PDCP layer by using a 1-bit indicator in the UDC header of the first data (PDCP PDU), wherein after resetting the transmitting UDC buffer, the UDC compression process is first applied to the first data (PDCP PDU) to perform data processing. This is because the receiving PDCP layer may not know about which data UDC compression is newly performed after the transmitting UDC is reset, and therefore the transmitting PDCP layer may indicate the data by using the 1-bit indicator of the UDC buffer, so that the receiving PDCP layer checks the 1-bit indicator, resets the receiving UDC buffer, and performs the UDC decompression process starting from the data by using the reset receiving UDC buffer. Therefore, when the 1-bit indicator in the UDC header of the receiving data (e.g., PDCP PDU) may indicate to reset the receiving UDC buffer, the receiving PDCP layer may know that the transmitting UDC buffer has been reset and new UDC compression has been applied to the data. Therefore, the receiving PDCP layer may reset the receiving UDC buffer and may apply the UDC decompression process starting from the data by using the reset receiving UDC buffer.

[0529] According to the second embodiment of the present disclosure, when a user data compression process is configured, when a portion of data that has been previously generated and has been subjected to user data compression is discarded due to a PDCP discard timer, because data whose PDCP sequence number is greater than the PDCP sequence number of the discarded data and to which UDC compression is applied is not transmitted, decompression failure or checksum failure that may occur in a receiving PDCP layer can be reduced, and waste of transmission resources can be reduced. In addition, because data is regenerated from data that has never been transmitted or from last transmitted data (transmitted data corresponds to the next PDCP sequence number of the discarded data), data loss can be prevented.

[0530] In addition, because the transmitting PDCP layer can immediately reset the transmitting UDC buffer and can restart UDC compression without waiting for PDCP control data (PDCP control PDU) for resetting the transmitting UDC buffer sent from the receiving PDCP layer due to a checksum failure, the transmission waiting time can be reduced. Because a checksum failure or a decompression failure does not occur in the receiving PDCP layer, the receiving PDCP layer may not need to generate and send PDCP control data, and can reset the receiving UDC buffer and newly start UDC decompression according to a 1-bit indicator of the UDC header indicated in the transmitting PDCP layer. Therefore, the second embodiment of the present disclosure may be a terminal-based transmitting / receiving UDC buffer reset method using a 1-bit indicator of the UDC header.

[0531] The detailed operation of the second embodiment of the present disclosure is as follows.

[0532] - Operation at the transmitter end: When the uplink data compression process is configured and data that has not been transmitted and has been subjected to UDC compression is discarded due to expiration of the PDCP discard timer, the transmitting PDCP layer may discard all data (e.g., PDCP PDUs) whose PDCP sequence numbers are greater than the PDCP sequence numbers of the discarded data, or PDCP PDUs that have been generated as PDCP PDUs to which user data compression is applied and stored but have not been transmitted. In addition, when the data has been transmitted to a lower layer, the transmitting PDCP layer may send an indicator of discarded data to the lower layer. The transmitting PDCP layer may reset a buffer (UDC buffer) for user data compression, may assign a PDCP sequence number to the data starting from the original data of the first data that has not been transmitted (e.g., PDCP SDU), may perform user data compression again in ascending order from a new PDCP sequence number or a PDCP sequence number that has not been transmitted, and may perform encryption. In addition, when a UDC header of the first data to which UDC compression is first applied after the transmit UDC buffer is reset is generated, in order to indicate that the transmit buffer for user data compression has been reset, or in order to indicate that the receive UDC buffer at the receiver end is reset, the transmit PDCP layer may define and indicate a new 1-bit indicator (e.g., Fig.2I 2i-05). When the receiver checks the 1-bit indicator of the UDC header, the receiver can know that the receiving buffer for user data decompression may have to be reset. In another method, the FR bit can be used to indicate that the sending buffer for user data compression has been reset, and the receiver can indicate that the receiving buffer for user data decompression may have to be reset. That is, the terminal can reset the sending and receiving UDC buffers.

[0533] - The transmitting PDCP layer may immediately transmit the newly generated and prepared data sequentially or in ascending order of the PDCP sequence number starting from the data whose UDC header indicates that the transmit buffer for user data compression has been reset and the receiver indicates that the receive buffer for data decompression has been reset. That is, the transmitting PDCP layer may deliver the data to the lower layer.

[0534] According to the second embodiment, the terminal itself can trigger a process of resetting the transmission and reception UDC buffers by using a 1-bit indicator of the UDC header before the checksum fails. Therefore, when the user data compression process is configured, when a part of the data that has been previously generated and whose user data compression has been performed is discarded due to the PDCP discard timer, because the data is regenerated from the data that has not yet been sent, the checksum failure that may occur in the data whose PDCP sequence number is greater than the PDCP sequence number of the discarded data can be reduced, and data loss can be prevented.

[0535] Operation at the receiver end: When the UDC header of the received data indicates that the sending buffer for user data compression has been reset and even the receiving side indicates that the receiving buffer for user data decompression may have to be reset, the receiver end can reset the receiving UDC buffer, can perform decryption and user data decompression on the received data in ascending order of the PDCP sequence number, and can deliver the data to a higher layer.

[0536] Embodiments of the present disclosure may provide efficient detailed operations of the transmission and reception PDCP layer of a bearer in which a user data compression process (uplink data compression or downlink data compression) is configured.

[0537] A first embodiment of effective operation of the transmission and reception PDCP layers of a bearer in which a user data compression process is configured is as follows. For example, the operation of the transmission PDCP layer of a terminal or a base station according to an embodiment of the present disclosure is as follows.

[0538] The transmitting PDCP layer may use a first count variable that maintains a count value to be assigned to data to be transmitted next during data processing, and the first count variable may be referred to as TX_NEXT.

[0539] The operation of the transmitting PDCP layer of the present disclosure is as follows.

[0540] The transmitting PDCP layer may operate a PDCP data discard timer when receiving data (eg, PDCP SDU) from a higher layer, and may discard the data when the PDCP data discard timer expires.

[0541] - The transmitting PDCP layer may assign a count value corresponding to TX_NEXT to data received from a higher layer. The initial value TX_NEXT may be set to 0, and TX_NEXT may maintain a count value of the next data (PDCP SDU) to be transmitted.

[0542] When a header compression protocol (ROHC) is configured in the transmitting PDCP layer, the transmitting PDCP layer may perform header compression on data.

[0543] When the user data compression protocol (uplink data compression / downlink data compression (UDC / DDC)) is configured in the transmit PDCP layer

[0544] 1. When user data compression can be applied to data received from a higher layer, the transmitting PDCP layer may generate a user data compression header (UDC header or DDC header) and may configure a 1-bit indicator in the user data compression header indicating that user data compression has been applied to the data, and when user data compression is not applied to the data, the transmitting PDCP layer may generate a user data compression header and may configure a 1-bit indicator in the user data compression header indicating that user data compression has not been applied. When user data compression is applied, the transmitting PDCP layer may apply compression to the data.

[0545] 2. When an error indicating that a checksum failure has occurred is received from the receiving PDCP layer at the receiver end, the transmitting PDCP layer can reset the transmitting user data compression buffer (UDC / DDC buffer) of the user data compression protocol, and can indicate the data that is first compressed after resetting the transmitting user data compression buffer by using a 1-bit indicator in the user data compression header of the first data to which the new user data compression is applied.

[0546] 3. When the sending user data compression buffer needs to be reset due to a PDCP discard timer or a protocol error, the sending PDCP layer of the sending end may reset the sending user data compression buffer and may indicate the data that is first compressed after the sending user data compression buffer is reset by using a 1-bit indicator in the user data compression header of the first data to which user data compression is newly applied. In addition, the sending PDCP layer may instruct the reset of the receiving user data compression buffer of the receiving PDCP layer of the receiving end by using an indicator.

[0547] -When integrity protection is configured in the transmission PDCP layer, the transmission PDCP layer may generate a PDCP header and may perform integrity protection on the PDCP header and data by using the count value of TX_NEXT allocated to the data and a security key.

[0548] -The transmit PDCP layer may perform an encryption process on the data by using the count value of TX_NEXT assigned to the data and the security key. The transmit PDCP layer may configure the least significant bit (LSB) of the PDCP sequence number length from the count value of TX_NEXT to the PDCP sequence number. The transmit PDCP layer may also encrypt the user data compression header (UDC header / DDC header) during the encryption process.

[0549] The transmitting PDCP layer may increase the count value of TX_NEXT by 1, may combine the processed data with the PDCP header, and may transmit the data together with the PDCP header to a lower layer.

[0550] The operation of the receiving PDCP layer of the terminal or base station according to an embodiment of the present disclosure is as follows.

[0551] The receiving PDCP layer may use the PDCP sequence number length (e.g., 12 bits or 18 bits) configured by the base station in the RRC, may check the PDCP sequence number of the received data (e.g., PDCP PDU), and may drive the receiving window. The receiving window is set to half the size of the PDCP sequence number space (e.g., 2^(PDCP SN length - 1)) and is used to identify valid data. That is, the receiving PDCP layer may determine data received outside the receiving window as invalid data and may discard the data. The reason why the data arrives outside the receiving window is that the data arrives very late due to retransmission from the RLC layer of the lower layer or HARQ retransmission from the MAC layer. In addition, the receiving PDCP layer may drive the PDCP t-reordering timer as well as the receiving window.

[0552] When a PDCP sequence number gap occurs in the receiving PDCP layer based on the PDCP sequence number, the PDCP t-reordering timer may be triggered. When data corresponding to the PDCP sequence number gap does not arrive until the PDCP t-reordering timer expires, the receiving PDCP layer may transmit the data to a higher layer in ascending order of the count value or the PDCP sequence number, and may move the receiving window. Therefore, when data corresponding to the PDCP sequence number gap arrives after the PDCP t-reordering timer expires, the data is not data within the receiving window, and thus the receiving PDCP layer may discard the data.

[0553] The specific process of receiving the PDCP layer is as follows. That is, the operation of receiving the PDCP layer of the terminal or base station according to the present disclosure is as follows.

[0554] The receiving PDCP layer may maintain and manage three counting variables when processing the received data. The receiving PDCP layer may use a second counting value that maintains a counting value of the next expected received data (e.g., PDCP SDU) when processing the received data, and the second counting variable may be referred to as RX_NEXT. The receiving PDCP layer may use a third counting value that maintains a counting value of the first data (e.g., PDCP SDU) that has not been delivered to a higher layer when processing the received data, and the third counting variable may be referred to as RX_DELIV. The receiving PDCP layer may use a fourth counting variable that maintains a counting value of the data (e.g., PDCP SDU) that triggers the PDCP t-reordering timer when processing the received data, and the fourth counting variable may be referred to as RX_REORD. The receiving PDCP layer may use a fifth counting variable that maintains a counting value of the currently received data (e.g., PDCP SDU) when processing the received data, and the fifth counting variable may be referred to as RCVD_COUNT. The PDCP t-reordering timer may use a counting variable as described in reference to FIG. Figure 1E The timer value or interval configured in the RRC message in the higher layer (RRC layer) is described as follows. The PDCP t-Reordering Timer can be used to detect lost PDCP PDUs, and only one timer is run at a time.

[0555] In addition, the terminal in the operation of receiving the PDCP layer may define and use the following variables.

[0556] -HFN: Indicates the hyperframe number (HFN) of the window state variable.

[0557] -SN: Indicates the sequence number (SN) of the window state variable.

[0558] -RCVD_SN: indicates the PDCP sequence number included in the header of the received PDCP PDU.

[0559] -RCVD_HFN: indicates the HFN value of the received PDCP PDU calculated by the receiving PDCP layer.

[0560] The operation of the receiving PDCP layer of the terminal or base station according to an embodiment of the present disclosure is as follows.

[0561] When receiving a PDCP PDU from a lower layer, the receiving PDCP layer may determine a count value of the received PDCP PDU as follows.

[0562] When received RCVD_SN ≤ SN(RX_DELIV) - window size, Equation 1 results in:

[0563] 1. RCVD_HFN = HFN(RX_DELIV) + 1 (Equation 1).

[0564] - On the other hand, when RCVD_SN is such that RCVD_SN > SN(RX_DELIV) + window size, Equation 2 can result in:

[0565] 1. RCVD_HFN = HFN(RX_DELIV) - 1 (Equation 2).

[0566] - In other cases, Equation 3 can result in:

[0567] 1. RCVD_HFN = HFN(RX_DELIV) (Equation 3).

[0568] - RCVD_COUNT can be determined as RCVD_COUNT = [RCVD_HFN, RCVD_SN].

[0569] After determining the count value of the received PDCP PDU, the receiving PDCP layer can update the window state variables as follows and can process the PDCP PDU.

[0570] - The receiving PDCP layer can decrypt the PDCP PDU by using the RCVD_COUNT value and can perform integrity verification.

[0571] 1. When the integrity verification fails, the receiving PDCP layer can indicate the integrity verification failure to the higher layer and can discard the received PDCP data PDU (the data part of the PDCP PDU).

[0572] - When RCVD_COUNT < RX_DELIV, or when a PDCP PDU with the RCVD_COUNT value has been received previously (cases of packet obsolescence, expiration, or outside the window, or cases of duplicate packets) (when integrity protection is configured and the PDCP PDU with the RCVD_COUNT value was successful in the previous integrity protection).

[0573] 1. The receiving PDCP layer can discard the received PDCP data PDU (the data part of the PDCP PDU).

[0574] When the received PDCP PDU is not discarded, the receiving PDCP layer can operate as follows.

[0575] - The receiving PDCP layer can store the processed PDCP SDU in the receive buffer.

[0576] - When RCVD_COUNT >= RX_NEXT,

[0577] 1.RX_NEXT can be updated to RCVD_COUNT+1.

[0578] - When the out-of-order delivery indicator (outOfOrderDelivery) is configured (indicating out-of-order delivery operation),

[0579] 1. The receiving PDCP layer may deliver the PDCP SDU to higher layers.

[0580] -When RCVD_COUNT is the same as RX_DELIV

[0581] 1.- (Although the User Data Compression Protocol (UDC / DDC) or the Header Compression Protocol (e.g., ROHC) is configured), when the header decompression process has not been previously applied (i.e., when compression has not been performed on the higher layer header or data)

[0582] A. When the user data compression protocol is configured and the user data has been compressed (when the indicator of the user data compression header is checked and the indicator indicates that the user data has been compressed)

[0583] i. When the User Data Compression Header may indicate that the transmit UDC buffer has been reset and may indicate the first data of a new application of User Data Compression (by checking the FR bit).

[0584] A) The receiving PDCP layer may reset the receiving user data compression protocol buffer.

[0585] B) When the checksum field of the user data compression header is checked, a checksum check process is performed, and no checksum error occurs,

[0586] ① The receiving PDCP layer can decompress the data.

[0587] C) Otherwise, when checking the checksum field of the user data compression header, performing the checksum check process, and a checksum error occurs,

[0588] ① The receiving PDCP layer may discard the data, and may generate a PDCP control PDU, and send the PDCP control PDU to the transmitting PDCP layer at the transmitter end to indicate that a checksum error has occurred. The receiving PDCP layer may instruct the lower layer to discard the data (e.g., PDCP PDU) previously generated and transmitted to the lower layer, and the lower layer may discard the data that has not yet been transmitted. The receiving PDCP layer may not generate an additional PDCP control PDU until data indicating that the sending user data compression buffer has been reset and the first data to which user data compression is newly applied is received from subsequently received data, thereby preventing unnecessary PDCP control PDU transmission.

[0589] ② The receiving PDCP layer may discard all data to which the user data compression process is applied, among the subsequently received data, whose count value or PDCP sequence number is smaller than the count value or PDCP sequence number of the following data, indicating that the sending user data compression buffer has been reset and the first data to which user data compression is newly applied, by using a 1-bit indicator of the user data compression header.

[0590] ii. On the other hand, when the user data compression header does not indicate that the UDC buffer has been reset and does not indicate the first data of the new application of user data compression (by checking the FR bit)

[0591] A) When the checksum field of the user data compression header is checked, the checksum check process is performed, and no checksum error occurs,

[0592] ① The receiving PDCP layer can decompress the data.

[0593] B) Otherwise, when checking the checksum field of the user data compression header, performing the checksum check process, and a checksum error occurs,

[0594] ① The receiving PDCP layer may discard the data, and may generate a PDCP control PDU, and send the PDCP control PDU to the transmitting PDCP layer at the transmitter end to indicate that a checksum error has occurred. The receiving PDCP layer may instruct the lower layer to discard the data (e.g., PDCP PDU) previously generated and transmitted to the lower layer, and the lower layer may discard the data that has not yet been transmitted. The receiving PDCP layer may not generate an additional PDCP control PDU until data indicating that the sending user data compression buffer has been reset and the first data to which user data compression is newly applied is received from subsequently received data, thereby preventing unnecessary PDCP control PDU transmission.

[0595] ② The receiving PDCP layer may discard all data to which the user data compression process is applied, among the subsequently received data, whose count value or PDCP sequence number is smaller than the count value or PDCP sequence number of the following data, indicating that the sending user data compression buffer has been reset and the first data to which user data compression is newly applied, by using a 1-bit indicator of the user data compression header.

[0596] B. When the user data compression protocol is configured and the user data is not compressed (when the indicator of the user data compression header can be checked and the indicator can indicate that the user data is not compressed),

[0597] i. The receiving PDCP layer may not perform decompression on the data and may remove the user data compression header.

[0598] C. On the other hand, when the user data compression protocol is not configured and the header compression protocol (e.g., ROHC) is configured,

[0599] i. The receiving PDCP layer may perform decompression on the higher layer header (TCP / IP or UDP header) of the data.

[0600] 2. The receiving PDCP layer may deliver the data to higher layers in the order of the count values.

[0601] A. The receiving PDCP layer may deliver all consecutive PDCP SDUs from COUNT = RX_DELIV to higher layers.

[0602] 3. The receiving PDCP layer may update RX_DELIV to a count value of the first PDCP SDU not delivered to higher layers, where the count value is equal to or greater than the current RX_DELIV.

[0603] - When t-reorder timer is running and RX_DELIV is equal to or greater than RX_REORD,

[0604] 1. The receiving PDCP layer may stop and reset the t-Reordering timer.

[0605] - When the t-reorder timer is not running (including the case where the t-reorder timer is stopped under the above conditions) and RX_DELIV is less than RX_NEXT,

[0606] 1. The receiving PDCP layer may update RX_REORD to RX_NEXT.

[0607] 2. The receiving PDCP layer may start the t-reordering timer.

[0608] When the PDCP t-reordering timer expires, the receiving PDCP layer may operate as follows.

[0609] - (despite the configuration of the User Data Compression protocol (UDC / DDC) or the header compression protocol (e.g., ROHC)), when no header decompression process has been previously applied (i.e., when no compression has been performed on higher layer headers or data)

[0610] 1. When the user data compression protocol is configured and the user data has been compressed (when the indicator of the user data compression header is checked and indicates that the user data has been compressed)

[0611] A. When checking the checksum field of the user data compression header, performing the checksum check process, and no checksum error occurs

[0612] i. The receiving PDCP layer may perform decompression on the data.

[0613] B. Otherwise, when the checksum field of the user data compression header is checked, the checksum verification process is performed, and a checksum error occurs.

[0614] i. The receiving PDCP layer may discard the data, and may generate a PDCP control PDU, and send the PDCP control PDU to the transmitting PDCP layer at the transmitter end to indicate that a checksum error has occurred. The receiving PDCP layer may instruct the lower layer to discard the data (e.g., PDCP PDU) previously generated and transmitted to the lower layer, and the lower layer may discard the data that has not yet been transmitted. The receiving PDCP layer may not generate an additional PDCP control PDU until data indicating that the transmit user data compression buffer has been reset and the first data to which user data compression is newly applied is received from subsequently received data, thereby preventing unnecessary PDCP control PDU transmission.

[0615] ii. The receiving PDCP layer may discard all subsequently received data to which the user data compression process is applied, whose count value or PDCP sequence number is smaller than the count value or PDCP sequence number of the following data, indicating that the sending user data compression buffer has been reset and the first data to which user data compression is newly applied, indicated by using a 1-bit indicator of the user data compression header.

[0616] 2. When the user data compression protocol is configured and the user data is not compressed (when the indicator of the user data compression header can be checked and the indicator can indicate that the user data is not compressed),

[0617] A. The receiving PDCP layer may not perform decompression on the data and may remove the user data compression header.

[0618] 3. On the other hand, when the user data compression protocol is not configured and the header compression protocol (e.g., ROHC) is configured,

[0619] A. The receiving PDCP layer may perform decompression on the higher layer header (TCP / IP or UDP header) of the data.

[0620] - The receiving PDCP layer delivers data to higher layers in the order of count values.

[0621] 1. The receiving PDCP layer may deliver all PDCP SDUs with a count value less than RX_REORD.

[0622] 2. The receiving PDCP layer may deliver all PDCP SDUs with consecutive count values ​​starting from RX_REORD.

[0623] - The receiving PDCP layer may update RX_DELIV to a count value of the first PDCP SDU not sent to higher layers, where the count value is equal to or greater than RX_REORD.

[0624] -When RX_DELIV is less than RX_NEXT,

[0625] 1. The receiving PDCP layer may update RX_REORD to RX_NEXT.

[0626] 2. The receiving PDCP layer may start the t-reordering timer.

[0627] When the PDCP t-reordering timer expires, another receiving PDCP layer according to an embodiment of the present disclosure may operate as follows.

[0628] - (despite the configuration of the User Data Compression protocol (UDC / DDC) or the header compression protocol (e.g., ROHC)), when no header decompression process has been previously applied (i.e., when no compression has been performed on higher layer headers or data)

[0629] 1. When the user data compression protocol is configured and the user data has been compressed (when the indicator of the user data compression header is checked and the indicator indicates that the user data has been compressed),

[0630] A. The receiving PDCP layer may discard the data, and may generate a PDCP control PDU, and send the PDCP control PDU to the transmitting PDCP layer at the transmitter end to indicate that a checksum error has occurred. The receiving PDCP layer may instruct the lower layer to discard the data (e.g., PDCP PDU) previously generated and transmitted to the lower layer, and the lower layer may discard the data that has not yet been transmitted. The receiving PDCP layer may not generate an additional PDCP control PDU until data indicating that the transmit user data compression buffer has been reset and the first data to which user data compression is newly applied is received from subsequently received data, thereby preventing unnecessary PDCP control PDU transmission.

[0631] B. The receiving PDCP layer may discard all subsequently received data to which the user data compression process is applied, whose count value or PDCP sequence number is less than the count value or PDCP sequence number of the following data, which indicates that the sending user data compression buffer has been reset and the first data to which user data compression is newly applied is indicated by using a 1-bit indicator of the user data compression header.

[0632] 2. When the user data compression protocol is configured and the user data is not compressed (when the indicator of the user data compression header can be checked and the indicator can indicate that the user data is not compressed),

[0633] A. The receiving PDCP layer may not perform decompression on the data and may remove the user data compression header.

[0634] 3. On the other hand, when the user data compression protocol is not configured and the header compression protocol (e.g., ROHC) is configured,

[0635] A. The receiving PDCP layer may perform decompression on the higher layer header (TCP / IP or UDP header) of the data.

[0636] - The receiving PDCP layer delivers data to higher layers in the order of count values.

[0637] 1. The receiving PDCP layer may deliver all PDCP SDUs with a count value less than RX_REORD.

[0638] 2. The receiving PDCP layer may deliver all PDCP SDUs with consecutive count values ​​starting from RX_REORD.

[0639] - The receiving PDCP layer may update RX_DELIV to a count value of the first PDCP SDU not sent to the higher layer, where the count value is equal to or greater than RX_REORD.

[0640] -When RX_DELIV is less than RX_NEXT,

[0641] 1. The receiving PDCP layer may update RX_REORD to RX_NEXT.

[0642] 2. The receiving PDCP layer may start the t-reordering timer.

[0643] When the PDCP t-reordering timer expires, another receiving PDCP layer according to an embodiment of the present disclosure may operate as follows.

[0644] - (despite the configuration of the User Data Compression protocol (UDC / DDC) or the header compression protocol (e.g., ROHC)), when the header decompression process has not been previously applied (i.e., when compression has not been performed on higher layer headers or data)

[0645] 1. When the user data compression protocol is configured and the user data has been compressed (when the indicator of the user data compression header is checked and the indicator indicates that the user data has been compressed),

[0646] A. The receiving PDCP layer may discard the data.

[0647] 2. When the user data compression protocol is configured and the user data has not been compressed (when the indicator of the user data compression header is checked and the indicator indicates that the user data has not been compressed)

[0648] A. The receiving PDCP layer may not perform decompression on the data and may remove the user data compression header.

[0649] 3. On the other hand, when the user data compression protocol is not configured and the header compression protocol (e.g., ROHC) is configured,

[0650] A. The receiving PDCP layer may perform decompression on the higher layer header (TCP / IP or UDP header) of the data.

[0651] - The receiving PDCP layer may deliver the data to higher layers in the order of the count values.

[0652] 1. The receiving PDCP layer may deliver all PDCP SDUs with a count value less than RX_REORD.

[0653] 2. The receiving PDCP layer may deliver all PDCP SDUs with consecutive count values ​​starting from RX_REORD.

[0654] - The receiving PDCP layer may update RX_DELIV to a count value of the first PDCP SDU not sent to higher layers, where the count value is equal to or greater than RX_REORD.

[0655] -When RX_DELIV is less than RX_NEXT,

[0656] 1. The receiving PDCP layer may update RX_REORD to RX_NEXT.

[0657] 2. The receiving PDCP layer may start the t-reordering timer.

[0658] Embodiments of the present disclosure may provide efficient detailed operations of the transmission and reception PDCP layer of a bearer in which a user data compression process (uplink data compression or downlink data compression) is configured.

[0659] A second embodiment of effective operation of the transmission and reception PDCP layers of a bearer configured with a user data compression process is as follows. That is, the operation of the transmission PDCP layer of a terminal or a base station according to an embodiment of the present disclosure is as follows.

[0660] The transmitting PDCP layer may use a first count variable that maintains a count value to be assigned to data to be transmitted next during data processing, and the first count variable may be referred to as TX_NEXT.

[0661] The operation of the transmitting PDCP layer of the present disclosure is as follows.

[0662] The transmitting PDCP layer may operate a PDCP data discard timer when receiving data (eg, PDCP SDU) from a higher layer, and may discard the data when the PDCP data discard timer expires.

[0663] - The transmitting PDCP layer may assign a count value corresponding to TX_NEXT to data received from a higher layer. The initial value TX_NEXT may be set to 0, and TX_NEXT may maintain a count value of the next data (PDCP SDU) to be transmitted.

[0664] When a header compression protocol (ROHC) is configured in the transmitting PDCP layer, the transmitting PDCP layer may perform header compression on data.

[0665] When the user data compression protocol (uplink data compression / downlink data compression (UDC / DDC)) is configured in the transmit PDCP layer

[0666] 1. When user data compression can be applied to data received from a higher layer, the transmitting PDCP layer may generate a user data compression header (UDC header or DDC header) and may configure a 1-bit indicator in the user data compression header indicating that user data compression has been applied to the data, and when user data compression is not applied to the data, the transmitting PDCP layer may generate a user data compression header and may configure a 1-bit indicator in the user data compression header indicating that user data compression has not been applied. When user data compression is applied, the transmitting PDCP layer may apply compression to the data.

[0667] 2. When an error indicating that a checksum failure has occurred is received from the receiving PDCP layer at the receiver end, the transmitting PDCP layer can reset the transmitting user data compression buffer (UDC / DDC buffer) of the user data compression protocol, and can indicate the data that is first compressed after resetting the transmitting user data compression buffer by using a 1-bit indicator in the user data compression header of the first data to which the new user data compression is applied.

[0668] 3. When the sending user data compression buffer needs to be reset due to a PDCP discard timer or a protocol error, the sending PDCP layer of the sending end may reset the sending user data compression buffer and may indicate the data that is first compressed after the sending user data compression buffer is reset by using a 1-bit indicator in the user data compression header of the first data to which user data compression is newly applied. In addition, the sending PDCP layer may instruct the reset of the receiving user data compression buffer of the receiving PDCP layer of the receiving end by using an indicator.

[0669] -When integrity protection is configured in the transmission PDCP layer, the transmission PDCP layer may generate a PDCP header and may perform integrity protection on the PDCP header and data by using the count value of TX_NEXT allocated to the data and a security key.

[0670] -The transmit PDCP layer may perform an encryption process on the data by using the count value of TX_NEXT assigned to the data and the security key. The transmit PDCP layer may configure the least significant bit (LSB) of the PDCP sequence number length from the count value of TX_NEXT to the PDCP sequence number. The transmit PDCP layer may also encrypt the user data compression header (UDC header / DDC header) during the encryption process.

[0671] The transmitting PDCP layer may increase the count value of TX_NEXT by 1, may combine the processed data with the PDCP header, and may transmit the data together with the PDCP header to a lower layer.

[0672] The operation of the receiving PDCP layer of the terminal or base station according to an embodiment of the present disclosure is as follows.

[0673] The receiving PDCP layer may use the PDCP sequence number length (e.g., 12 bits or 18 bits) configured by the base station in the RRC, may check the PDCP sequence number of the received data (e.g., PDCP PDU), and may drive the receiving window. The receiving window may be set to half the size of the PDCP sequence number space (e.g., 2^(PDCP SN length - 1)) and may be used to identify valid data. That is, the receiving PDCP layer may determine data received outside the receiving window as invalid data and may discard the data. The reason why the data arrives outside the receiving window is that the data arrives very late due to retransmission from the RLC layer of the lower layer or HARQ retransmission from the MAC layer. In addition, the receiving PDCP layer may drive the PDCP t-reordering timer as well as the receiving window.

[0674] When a PDCP sequence number gap occurs in the receiving PDCP layer based on the PDCP sequence number, the PDCP reordering timer may be triggered. When data corresponding to the PDCP sequence number gap does not arrive until the PDCP t-reordering timer expires, the receiving PDCP layer may deliver the data to a higher layer in ascending order of the count value or the PDCP sequence number, and may move the receiving window. Therefore, when data corresponding to the PDCP sequence number gap arrives after the PDCP t-reordering timer expires, the data is not data within the receiving window, and thus the receiving PDCP layer may discard the data.

[0675] The specific process of receiving the PDCP layer according to the embodiment of the present disclosure is as follows. That is, the operation of receiving the PDCP layer of the terminal or base station according to the embodiment of the present disclosure is as follows.

[0676] The receiving PDCP layer may maintain and manage three counting variables when processing the received data. The receiving PDCP layer may use a second counting value that maintains a counting value of the next expected received data (e.g., PDCP SDU) when processing the received data, and the second counting variable may be referred to as RX_NEXT. The receiving PDCP layer may use a third counting value that maintains a counting value of the first data (e.g., PDCP SDU) that has not been delivered to a higher layer when processing the received data, and the third counting variable may be referred to as RX_DELIV. The receiving PDCP layer may use a fourth counting variable that maintains a counting value of the data (e.g., PDCP SDU) that triggers the PDCP-t reordering timer when processing the received data, and the fourth counting variable may be referred to as RX_REORD. The receiving PDCP layer may use a fifth counting variable that maintains a counting value of the currently received data (e.g., PDCP SDU) when processing the received data, and the fifth counting variable may be referred to as RCVD_COUNT. The PDCP reordering timer may be used as described in reference Figure 1E The timer value or interval configured in the RRC message in the higher layer (RRC layer) is described as follows. The PDCP t-Reordering Timer can be used to detect lost PDCP PDUs, and only one timer is run at a time.

[0677] In addition, the terminal in the operation of receiving the PDCP layer may define and use the following variables.

[0678] -HFN: Indicates the hyperframe number (HFN) of the window state variable.

[0679] -SN: Indicates the sequence number (SN) of the window state variable.

[0680] -RCVD_SN: indicates the PDCP sequence number included in the header of the received PDCP PDU.

[0681] -RCVD_HFN: indicates the HFN value of the received PDCP PDU calculated by the receiving PDCP layer.

[0682] The operation of the reception PDCP layer of the terminal or base station according to an embodiment of the present disclosure is as follows: When receiving a PDCP PDU from a lower layer, the reception PDCP layer may determine a count value of the received PDCP PDU as follows.

[0683] When received RCVD_SN ≤ SN(RX_DELIV) - window size, Equation 1 results in:

[0684] 1. RCVD_HFN=HFN(RX_DELIV)+1 (Equation 1).

[0685] - On the other hand, when RCVD_SN > SN(RX_DELIV) + window size, Equation 2 can result in:

[0686] 1. RCVD_HFN = HFN(RX_DELIV) - 1 (Equation 2).

[0687] - In other cases, Equation 3 can result in:

[0688] 1. RCVD_HFN = HFN(RX_DELIV) (Equation 3).

[0689] - RCVD_COUNT can be determined as RCVD_COUNT = [RCVD_HFN, RCVD_SN].

[0690] After determining the count value of the received PDCP PDU, the receiving PDCP layer can update the window state variable as follows and can process the PDCP PDU.

[0691] - The receiving PDCP layer can decrypt the PDCP PDU by using the RCVD_COUNT value and can perform integrity verification.

[0692] 1. When the integrity verification fails,

[0693] The receiving PDCP layer can indicate to the higher layer that the integrity verification fails and can discard the received DPCP data PDU (the data part of the PDCP PDU).

[0694] - When RCVD_COUNT < RX_DELIV, or when a PDCP PDU with the RCVD_COUNT value has been received previously (cases of packet obsolescence, expiration, or outside the window, or cases of duplicate packets) (when integrity protection is configured and the PDCP PDU with the RCVD_COUNT value was successful in the previous integrity protection).

[0695] 1. The receiving PDCP layer can discard the received PDCP data PDU (the data part of the PDCP PDU).

[0696] When the received PDCP PDU is not discarded, the receiving PDCP layer can operate as follows.

[0697] - The receiving PDCP layer can store the processed PDCP SDU in the receive buffer.

[0698] - When RCVD_COUNT >= RX_NEXT,

[0699] 1.RX_NEXT can be updated to RCVD_COUNT+1.

[0700] - When the out-of-order delivery indicator (outOfOrderDelivery) is configured (indicating out-of-order delivery operation),

[0701] 1. The receiving PDCP layer may deliver the PDCP SDU to higher layers.

[0702] -When RCVD_COUNT is the same as RX_DELIV

[0703] 1.- (Although the User Data Compression Protocol (UDC / DDC) or the Header Compression Protocol (e.g., ROHC) is configured), when the header decompression process has not been previously applied (i.e., when compression has not been performed on the higher layer header or data)

[0704] A. When the user data compression protocol is configured and the user data has been compressed (when the indicator of the user data compression header is checked and indicates that the user data has been compressed)

[0705] i. When the User Data Compression header may indicate that the UDC buffer has been reset and may indicate the first data of a new application of User Data Compression (by checking the FR bit).

[0706] A) The receiving PDCP layer may reset the receiving user data compression protocol buffer.

[0707] B) When the checksum field of the user data compression header is checked, a checksum check process is performed, and no checksum error occurs,

[0708] ① The receiving PDCP layer can decompress the data.

[0709] C) Otherwise, when checking the checksum field of the user data compression header, performing the checksum check process, and a checksum error occurs,

[0710] ① The receiving PDCP layer may discard the data, and may generate a PDCP control PDU, and send the PDCP control PDU to the transmitting PDCP layer at the transmitter end to indicate that a checksum error has occurred. The receiving PDCP layer may instruct the lower layer to discard the data (e.g., PDCP PDU) previously generated and transmitted to the lower layer, and the lower layer may discard the data that has not yet been transmitted. The receiving PDCP layer may not generate an additional PDCP control PDU until data indicating that the sending user data compression buffer has been reset and the first data to which user data compression is newly applied is received from subsequently received data, thereby preventing unnecessary PDCP control PDU transmission.

[0711] ② The receiving PDCP layer may discard all data to which the user data compression process is applied, among the subsequently received data, whose count value or PDCP sequence number is smaller than the count value or PDCP sequence number of the following data, indicating that the sending user data compression buffer has been reset and the first data to which user data compression is newly applied, by using a 1-bit indicator of the user data compression header.

[0712] ii. On the other hand, when the user data compression header does not indicate that the UDC buffer has been reset and does not indicate the first data of the new application of user data compression (by checking the FR bit)

[0713] A) When the checksum field of the user data compression header is checked, the checksum checking process is performed, and no checksum error occurs.

[0714] ① The receiving PDCP layer can decompress the data.

[0715] B) Otherwise, when checking the checksum field of the user data compression header, performing the checksum check process, and a checksum error occurs,

[0716] ① The receiving PDCP layer may discard the data, and may generate a PDCP control PDU, and send the PDCP control PDU to the transmitting PDCP layer at the transmitter end to indicate that a checksum error has occurred. The receiving PDCP layer may instruct the lower layer to discard the data (e.g., PDCP PDU) previously generated and transmitted to the lower layer, and the lower layer may discard the data that has not yet been transmitted. The receiving PDCP layer may not generate an additional PDCP control PDU until data indicating that the sending user data compression buffer has been reset and the first data to which user data compression is newly applied is received from subsequently received data, thereby preventing unnecessary PDCP control PDU transmission.

[0717] ② The receiving PDCP layer may discard all data to which the user data compression process is applied, among the subsequently received data, whose count value or PDCP sequence number is smaller than the count value or PDCP sequence number of the following data, indicating that the sending user data compression buffer has been reset and the first data to which user data compression is newly applied, by using a 1-bit indicator of the user data compression header.

[0718] B. When the user data compression protocol is configured and the user data is not compressed (when the user data compression header can be checked and the indicator can indicate that the user data is not compressed),

[0719] i. The receiving PDCP layer may not perform decompression on the data and may remove the user data compression header.

[0720] C. On the other hand, when the user data compression protocol is not configured and the header compression protocol (e.g., ROHC) is configured,

[0721] i. The receiving PDCP layer may perform decompression on the higher layer header (TCP / IP or UDP header) of the data.

[0722] 2. The receiving PDCP layer may deliver the data to higher layers in the order of the count values.

[0723] A. The receiving PDCP layer may deliver all consecutive PDCP SDUs from COUNT = RX_DELIV to higher layers.

[0724] 3. The receiving PDCP layer may update RX_DELIV to a count value of the first PDCP SDU not sent to a higher layer, where the count value is equal to or greater than the current RX_DELIV.

[0725] - When t-reorder timer is running and RX_DELIV is equal to or greater than RX_REORD,

[0726] 1. The receiving PDCP layer may stop and reset the t-Reordering timer.

[0727] - When the t-reorder timer is not running (including the case where the t-reorder timer is stopped under the above conditions) and RX_DELIV is less than RX_NEXT,

[0728] 1. The receiving PDCP layer may update RX_REORD to RX_NEXT.

[0729] 2. The receiving PDCP layer may start the t-reordering timer.

[0730] When the PDCP t-reordering timer expires, the receiving PDCP layer may operate as follows.

[0731] - (despite the configuration of the User Data Compression protocol (UDC / DDC) or the header compression protocol (e.g., ROHC)), when no header decompression process has been previously applied (i.e., when no compression has been performed on higher layer headers or data)

[0732] 1. When the user data compression protocol is configured and the user data has been compressed (when the indicator of the user data compression header is checked and indicates that the user data has been compressed)

[0733] A. When the User Data Compression header may indicate that the UDC buffer has been reset and may indicate the first data of a new application of User Data Compression (by checking the FR bit),

[0734] i. The receiving PDCP layer may reset the receiving user data compression protocol buffer.

[0735] ii. When the checksum field of the user data compression header is checked, the checksum check process is performed, and no checksum error occurs,

[0736] The receiving PDCP layer may perform decompression on the data.

[0737] iii. Otherwise, when the checksum field of the user data compression header is checked, the checksum verification process is performed, and a checksum error occurs.

[0738] A) The receiving PDCP layer may discard the data, and may generate a PDCP control PDU, and send the PDCP control PDU to the transmitting PDCP layer at the transmitter end to indicate that a checksum error has occurred. The receiving PDCP layer may instruct the lower layer to discard the data (e.g., PDCP PDU) previously generated and transmitted to the lower layer, and the lower layer may discard the data that has not yet been transmitted. The receiving PDCP layer may not generate an additional PDCP control PDU until data indicating that the transmit user data compression buffer has been reset and the first data to which user data compression has been newly applied is received from subsequently received data, thereby preventing unnecessary PDCP control PDU transmission.

[0739] B) The receiving PDCP layer may discard all subsequently received data to which the user data compression process is applied, whose count value or PDCP sequence number is less than the count value or PDCP sequence number of the following data, which indicates that the sending user data compression buffer has been reset and the first data to which user data compression is newly applied is indicated by using a 1-bit indicator of the user data compression header.

[0740] B. On the other hand, when the User Data Compression Header does not indicate that the sending UDC buffer has been reset and does not indicate the first data of the new application of User Data Compression (by checking the FR bit).

[0741] i. When the checksum field of the user data compression header is checked, the checksum check process is performed, and no checksum error occurs.

[0742] A) The receiving PDCP layer may perform decompression on the data.

[0743] ii. Otherwise, when checking the checksum field of the user data compression header, performing the checksum verification process, and a checksum error occurs,

[0744] A) The receiving PDCP layer may discard the data, and may generate a PDCP control PDU, and send the PDCP control PDU to the transmitting PDCP layer at the transmitter end to indicate that a checksum error has occurred. The receiving PDCP layer may instruct the lower layer to discard the data (e.g., PDCP PDU) previously generated and transmitted to the lower layer, and the lower layer may discard the data that has not yet been transmitted. The receiving PDCP layer may not generate an additional PDCP control PDU until data indicating that the transmit user data compression buffer has been reset and the first data to which user data compression has been newly applied is received from subsequently received data, thereby preventing unnecessary PDCP control PDU transmission.

[0745] B) The receiving PDCP layer may discard all subsequently received data to which the user data compression process is applied, whose count value or PDCP sequence number is less than the count value or PDCP sequence number of the following data, which indicates that the sending user data compression buffer has been reset and the first data to which user data compression is newly applied is indicated by using a 1-bit indicator of the user data compression header.

[0746] 2. When the user data compression protocol is configured and the user data is not compressed (when the indicator of the user data compression header can be checked and can indicate that the user data is not compressed),

[0747] A. The receiving PDCP layer may not perform decompression on the data and may remove the user data compression header.

[0748] 3. On the other hand, when the user data compression protocol is not configured and the header compression protocol (e.g., ROHC) is configured,

[0749] A. The receiving PDCP layer may perform decompression on the higher layer header (TCP / IP or UDP header) of the data.

[0750] - The receiving PDCP layer may deliver the data to higher layers in the order of the count values.

[0751] 1. The receiving PDCP layer may deliver all PDCP SDUs with a count value less than RX_REORD.

[0752] 2. The receiving PDCP layer may deliver all PDCP SDUs with consecutive count values ​​starting from RX_REORD.

[0753] - The receiving PDCP layer may update RX_DELIV to a count value of the first PDCP SDU not sent to higher layers, where the count value is equal to or greater than RX_REORD.

[0754] -When RX_DELIV is less than RX_NEXT,

[0755] 1. The receiving PDCP layer may update RX_REORD to RX_NEXT.

[0756] 2. The receiving PDCP layer may start the t-reordering timer.

[0757] Figure 2J is a diagram for describing a terminal operation of receiving a PDCP layer according to an embodiment of the present disclosure.

[0758] In operation 2j-05, the receiving PDCP layer of the terminal can receive data from the lower layer.

[0759] In operations 2j-10 and 2j-20, when the user data compression protocol (UDC / DDC) is configured and the user data has been compressed (when the indicator of the user data compression header is checked and indicates that the user data has been compressed), and when the user data compression header can indicate that the sending UDC buffer has been reset and can indicate the first data of the newly applied user data compression (by checking the FR bit), in operation 2j-25, the receiving PDCP layer can reset the receiving user data compression protocol buffer. When the checksum field of the user data compression header is checked, the checksum check process is performed, and no checksum error occurs in operation 2j-30, in operation 2j-35, the receiving PDCP layer can perform decompression on the data. Otherwise, when the checksum field of the user data compression header is checked, the checksum check process is performed, and a checksum error occurs, in operation 2j-45, the receiving PDCP layer can discard the data, and can generate a PDCP control PDU, and send the PDCP control PDU to the sending PDCP layer at the transmitter end to indicate that a checksum error has occurred. The receiving PDCP layer may instruct the lower layer to discard data (e.g., PDCP PDU) previously generated and transmitted to the lower layer, and the lower layer may discard data that has not been transmitted. The receiving PDCP layer may not generate an additional PDCP control PDU until data indicating that the transmit user data compression buffer has been reset and the first data to which user data compression is newly applied is indicated by using a 1-bit indicator of the user data compression header from subsequently received data, thereby preventing unnecessary PDCP control PDU transmission. The receiving PDCP layer may discard all data to which the user data compression process is applied in the subsequently received data, the count value or PDCP sequence number of which is less than the count value or PDCP sequence number of the following data, the above data indicating that the transmit user data compression buffer has been reset and the first data to which user data compression is newly applied is indicated by using a 1-bit indicator of the user data compression header.

[0760] Otherwise, in operations 2j-20 to 2j-30, when the user data compression header does not indicate that the sending UDC buffer has been reset and does not indicate the first data of the newly applied user data compression (by checking the FR bit), and when the checksum field of the user data compression header is checked, the checksum check process is performed, and no checksum error occurs, in operation 2j-35, the receiving PDCP layer may perform decompression on the data. Otherwise, when the checksum field of the user data compression header is checked, the checksum check process is performed, and a checksum error occurs in operation 2j-30, in operation 2j-45, the receiving PDCP layer may discard the data, and may generate a PDCP control PDU, and send the PDCP control PDU to the sending PDCP layer at the transmitter end to indicate that a checksum error has occurred. The receiving PDCP layer may instruct the lower layer to discard the data (e.g., PDCP PDU) previously generated and transmitted to the lower layer, and the lower layer may discard the data that has not yet been transmitted. The receiving PDCP layer may not generate an additional PDCP control PDU until data indicating that the transmit user data compression buffer has been reset and first data to which user data compression is newly applied is indicated by using a 1-bit indicator of a user data compression header is received from subsequently received data, thereby preventing unnecessary PDCP control PDU transmission. The receiving PDCP layer may discard all data to which the user data compression process is applied in the subsequently received data, whose count value or PDCP sequence number is less than the count value or PDCP sequence number of the following data, the above data indicating that the transmit user data compression buffer has been reset and first data to which user data compression is newly applied is indicated by using a 1-bit indicator of a user data compression header.

[0761] In operation 2j-10, when the user data compression protocol is configured and the user data is not compressed (when the indicator of the user data compression header can be checked and can indicate that the user data is not compressed), the receiving PDCP layer may not perform decompression on the data and may remove the user data compression header in operation 2j-15. In operation 2j-40, the receiving PDCP layer may deliver the data to a higher layer.

[0762] Figure 2K is a block diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.

[0763] See also Figure 2K The terminal may include a radio frequency (RF) processor 2k-10, a baseband processor 2k-20, a memory 2k-30 and a controller 2k-40.

[0764] The RF processor 2k-10 can perform functions of sending / receiving signals through a radio channel, such as frequency band conversion or amplification of signals. That is, the RF processor 2k-10 can up-convert the baseband signal provided from the baseband processor 2k-20 into an RF band signal, and then can transmit the RF band signal through an antenna, and can down-convert the RF band signal received through the antenna into a baseband signal. For example, the RF processor 2k-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), and an analog-to-digital converter (ADC). Although in Figure 2K Only one antenna is shown, and the terminal may include multiple antennas. Moreover, the RF processor 2k-10 may include multiple RF chains. In addition, the RF processor 2k-10 can perform beamforming. For beamforming, the RF processor 2k-10 can adjust the phase and size of each signal sent / received through multiple antennas or antenna elements. Moreover, the RF processor 2k-10 can perform MIMO, and can receive multiple layers during MIMO operation. The RF processor 2k-10 can perform receive beam scanning by appropriately configuring multiple antennas or antenna elements, or can adjust the direction and beam width of the receive beam under the control of the controller 2k-40 so that the receive beam is coordinated with the transmit beam.

[0765] The baseband processor 2k-20 can convert between baseband signals and bit streams according to the physical layer specifications of the system. For example, during data transmission, the baseband processor 2k-20 can generate complex symbols by encoding and modulating the transmission bit stream. In addition, during data reception, the baseband processor 2k-20 can reconstruct the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 2k-10. For example, according to the orthogonal frequency division multiplexing (OFDM) method, during data reception, the baseband processor 2k-20 can generate complex symbols by encoding and modulating the transmission bit stream, the complex symbols can be mapped to subcarriers, and OFDM symbols can be configured by inverse fast Fourier transform (IFFT) and cyclic prefix (CP) insertion. In addition, during data reception, the baseband processor 2k-20 can segment the baseband signal provided from the RF processor 2k-10 into OFDM symbols, the signal mapped to the subcarrier can be reconstructed by fast Fourier transform (FFT), and then the received bit stream can be reconstructed by demodulating and decoding the signal.

[0766] As described above, the baseband processor 2k-20 and the RF processor 2k-10 can send and receive signals. Therefore, the baseband processor 2k-20 and the RF processor 2k-10 can be referred to as a transmitter, a receiver, a transceiver or a communicator. In addition, at least one of the baseband processor 2k-20 or the RF processor 2k-10 may include a plurality of communication modules supporting a plurality of different wireless access technologies. In addition, at least one of the baseband processor 2k-20 or the RF processor 2k-10 may include different communication modules to process signals of different frequency bands. For example, different wireless access technologies may include an LTE network and an NR network. Moreover, different frequency bands may include ultra-high frequency (SHF) (e.g., 2.5 GHz or 5 GHz) bands, and millimeter wave (mmWave) (e.g., 60 GHz) bands.

[0767] The memory 2k-30 can store basic programs, application programs, and data such as configuration information for operating the terminal. The memory 2k-30 can provide the stored data according to the request of the controller 2k-40.

[0768] The controller 2k-40 can control the entire operation of the terminal. For example, the controller 2k-40 can send / receive signals through the baseband processor 2k-20 and the RF processor 2k-10. In addition, the controller 2k-40 can write data to the memory 2k-30 and read data from the memory 2k-30. To this end, the controller 2k-40 may include at least one processor. For example, the controller 2k-40 may include a communication processor (CP) for controlling communication and an application processor (AP) for controlling a higher layer such as an application.

[0769] Figure 2L is a block diagram showing the structure of a base station (e.g., TRP) according to an embodiment of the present disclosure.

[0770] See also Figure 2L , the base station may include an RF processor 21 - 10, a baseband processor 21 - 20, a backhaul communicator 21 - 30, a memory 21 - 40, and a controller 21 - 50.

[0771] The RF processor 21-10 may perform functions such as frequency band conversion or amplification of signals for transmitting / receiving signals through a radio channel. That is, the RF processor 21-10 may up-convert a baseband signal provided from the baseband processor 21-20 into an RF band signal, which may then be transmitted through an antenna, and may down-convert an RF band signal received through an antenna into a baseband signal. For example, the RF processor 21-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC. Although in Figure 2LAn antenna is shown in the figure, and the first connection node may include multiple antennas. Moreover, the RF processor 21-10 may include multiple RF chains. In addition, the RF processor 21-10 can perform beamforming. For beamforming, the RF processor 21-10 can adjust the phase and size of each signal sent / received through multiple antennas or antenna elements. The RF processor 21-10 can perform downlink MIMO operations by sending one or more layers.

[0772] The baseband processor 21-20 can convert between a baseband signal and a bit stream according to the physical layer specification of the first radio access technology. For example, during data transmission, the baseband processor 21-20 can generate complex symbols by encoding and modulating the transmission bit stream. In addition, during data reception, the baseband processor 21-20 can reconstruct the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 21-10. For example, according to the OFDM method, during data transmission, the baseband processor 21-20 can generate complex symbols by encoding and modulating the transmission bit stream, the complex symbols can be mapped to subcarriers, and then OFDM symbols can be configured by IFFT and CP insertion. In addition, during data reception, the baseband processor 21-20 can segment the baseband signal provided from the RF processor 21-10 into OFDM symbols, the signal mapped to the subcarrier can be reconstructed by FFT, and then the received bit stream can be reconstructed by demodulating and decoding the signal. As described above, the baseband processor 21-20 and the RF processor 21-10 can send and receive signals. Therefore, the baseband processor 21-20 and the RF processor 21-10 may be referred to as a transmitter, a receiver, a transceiver, a communicator, or a wireless communicator.

[0773] Backhaul communicators 21 - 30 may provide an interface for communicating with other nodes in the network.

[0774] The memory 21-40 may store basic programs, applications, and data such as configuration information for operating the base station. In particular, the memory 21-40 may store information about the bearer assigned to the connected terminal and measurement results reported from the connected terminal. In addition, the memory 21-40 may store standard information for determining whether to provide or stop multiple connectivity to the terminal. The memory 21-40 may provide stored data according to a request from the controller 21-50.

[0775] The controller 21-50 may control the overall operation of the base station. For example, the controller 21-50 may send / receive signals through the RF processor 21-10 and the baseband processor 21-20 or the backhaul communicator 21-30. In addition, the controller 21-50 may write data to the memory 21-40 and read data from the memory 21-40. To this end, the controller 21-50 may include at least one processor.

[0776] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method for performing measurement by a user equipment UE, the method include: receiving a radio resource control RRC release message from a base station BS, the RRC release message comprising measurement configuration information for measurement in at least one of an idle mode or an inactive mode; Starting a first timer based on the measurement configuration information; performing the measuring while the first timer is running; as well as When a cell using a different radio access technology RAT is selected during the cell reselection process, the first timer is stopped and the measurement configuration information is released.

2. The method according to claim 1, wherein the method further comprises include: Based on receiving a paging message including identification information of the UE, The first timer is kept running and the inactive mode is switched to the idle mode.

3. The method according to claim 1, wherein the method further comprises Based on sending the RRC recovery request message, starting a second timer; Based on the expiration of the second timer, The first timer is kept running and the inactive mode is switched to the idle mode.

4. The method according to claim 1, wherein the method further comprises include: In case the UE fails to find a suitable cell during the cell reselection process and camps on an acceptable cell in the inactive mode, The first timer is kept running and the inactive mode is switched to the idle mode.

5. The method according to claim 1, wherein the method further comprises include: In a case where the cell selected based on the cell reselection process is outside the validity area, the first timer is stopped and the measurement configuration information is released.

6. The method according to claim 1, wherein the method further comprises include: In case an RRC resume message is received and the configuration information included in the RRC resume message is not applicable, the first timer is kept running and the inactive mode is transitioned to the idle mode.

7. The method of claim 6, wherein the method further comprises include: storing configuration information about the primary cell group MCG secondary cell Scell ​​or secondary cell group SCG based on the RRC release message, and The configuration information about the MCG Scell ​​or the SCG is released or restored based on whether the RRC restore message includes information indicating restoration of the configuration information about the MCG Scell ​​or the SCG.

8. The method according to claim 7, in, The method further comprises: Based on receiving the RRC setup message, discarding the configuration information about the MCG Scell ​​or the SCG.

9. The method according to claim 1, wherein the RRC release message includes information indicating whether to release the stored configuration information, in, Starting the first timer based on the measurement configuration information includes: The preset measurement configuration information is released, and the first timer is started based on the measurement configuration information.

10. A user equipment UE for performing measurement, the UE include: Transceiver; as well as at least one processor in combination with the transceiver and configured to: receiving a radio resource control RRC release message from a base station BS, the RRC release message comprising measurement configuration information for measurement in at least one of an idle mode or an inactive mode, Starting a first timer based on the measurement configuration information, performing the measurements while the first timer is running, and When a cell using a different radio access technology RAT is selected during the cell reselection process, the first timer is stopped and the measurement configuration information is released.

11. The UE of claim 10, wherein the at least one processor is further configured to: Based on receiving a paging message including identification information of the UE, The first timer is kept running and the inactive mode is switched to the idle mode.

12. The UE of claim 10, wherein the at least one processor is further configured to: Based on sending the RRC recovery request message, starting a second timer, Based on the expiration of the second timer, the first timer is kept running and the inactive mode is transitioned to the idle mode.

13. The UE of claim 10, wherein the at least one processor is further configured to: In case that the UE fails to find a suitable cell during the cell reselection process and camps on an acceptable cell in the inactive mode, the first timer is kept running and the UE is transitioned from the inactive mode to the idle mode.

14. The UE of claim 10, wherein the at least one processor is further configured to: In a case where the cell selected based on the cell reselection process is outside the validity area, the first timer is stopped and the measurement configuration information is released.

15. The UE of claim 10, wherein the at least one processor is further configured to: In case an RRC resume message is received and the configuration information included in the RRC resume message is not applicable, the first timer is kept running and the inactive mode is transitioned to the idle mode.

16. The UE of claim 15, wherein the at least one processor is further configured to: storing configuration information about the primary cell group MCG secondary cell Scell ​​or secondary cell group SCG based on the RRC release message, and The configuration information about the MCG Scell ​​or the SCG is released or restored based on whether the RRC restore message includes information indicating restoration of the configuration information about the MCG Scell ​​or the SCG.

17. The UE of claim 16, wherein the at least one processor is further configured to: discard the configuration information about the MCG Scell ​​or the SCG based on receiving an RRC setup message.

18. The UE according to claim 10, wherein the RRC release message includes information indicating whether to release the stored configuration information, and The at least one processor is further configured to release preset measurement configuration information, and start the first timer based on the measurement configuration information.