Method and apparatus for wireless communication in a wireless communication system

Abstract

An operation method of a transmitting apparatus is provided, including: receiving a service data adaptation protocol (SDAP) header configuration and a header compression configuration through higher layer signaling; and when a SDAP entity receives first data from an upper layer, generating a SDAP header and transmitting second data obtained by adding the generated SDAP header to the first data to a packet data convergence protocol (PDCP) entity, the generating and the transmitting being performed by the SDAP entity, performing header compression on an upper layer header of the second data except for the SDAP header by the PDCP entity, performing encryption on data of the second data except for the SDAP header by the PDCP entity, generating a PDCP header, and transmitting third data obtained by adding the generated PDCP header to the encrypted data to a lower layer, the generating and the transmitting being performed by the PDCP entity.

Description

[0001] This application is a divisional application of the invention patent application filed on January 10, 2019, with application number 201980007804.5. Technical Field

[0002] This disclosure relates to methods and apparatus for wireless communication in wireless communication systems. Background Technology

[0003] To meet the growing demand for wireless data traffic following the commercialization of 4G communication systems, considerable effort has been made to develop pre-5G or 5G communication systems. This is one reason why "5G communication systems" or "pre-5G communication systems" are referred to as "super 4G network communication systems" or "post-long-term evolution (LTE) systems." To achieve high data transmission rates, 5G communication systems are being developed in ultra-high frequency bands (millimeter wave (mmWave)), such as the 60 GHz band. To reduce spurious radio waves in such ultra-high frequency bands and increase the transmission distance of radio waves in 5G communication systems, various technologies are being researched, such as beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO. To improve the system network of 5G communication systems, various technologies have been developed, such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multi-points (CoMP), and interference cancellation. Furthermore, other technologies have been developed for 5G communication systems, such as hybrid modulation of frequency-shift keying (FSK) and quadrature amplitude modulation (QAM) (FSK and QAM, FQAM) as advanced coding modulation (ACM) schemes, as well as sliding window superposition coding (SWSC), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) schemes.

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

[0005] Various attempts are underway to apply 5G communication systems to IoT networks. For example, 5G communication technologies (including beamforming, MIMO, and array antennas) are being used to implement technologies related to sensor networks, M2M communication, and MTC. Cloud RAN, as an application of the aforementioned big data processing technologies, can be seen as an example of the integration of 5G communication and IoT technologies.

[0006] The above information is provided for background information purposes only to aid in understanding this disclosure. No determination or assertion is made as to whether any of the foregoing items can be applied as prior art with respect to this disclosure. Summary of the Invention

[0007] Technical solution

[0008] According to one aspect of this disclosure, a method of operating a transmitting device in a wireless communication system is provided. The method includes: configuring a higher-layer signaling receive service data adaptation protocol (SDAP) header and configuring header compression; and when an SDAP entity receives first data from an upper layer, generating an SDAP header and transmitting second data obtained by adding the generated SDAP header to the first data to a Packet Data Convergence Protocol (PDCP) entity, wherein the generation and transmission are performed by the SDAP entity, the PDCP entity performs header compression on the upper-layer header of the second data excluding the SDAP header, the PDCP entity encrypts the second data excluding the SDAP header and generates a PDCP header, and transmits third data obtained by adding the generated PDCP header to the encrypted data to a lower layer, wherein the generation and transmission are performed by the PDCP entity.

[0009] Beneficial effects

[0010] It provides apparatus and methods for effectively providing communication in wireless communication systems. Attached Figure Description

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

[0012] Figure 1A This is a diagram of the time-frequency domain transmission structure of the downlink (DL) radio resource area for a Long Term Evolution (LTE) system, an Advanced LTE (LTE-A) system, or a similar system, according to embodiments of this disclosure.

[0013] Figure 1B This is a diagram of the time-frequency domain transmission structure of the uplink (UL) radio resource area of ​​an LTE system, LTE-A system, or similar system, according to embodiments of the present disclosure.

[0014] Figure 2A This is a diagram illustrating the configuration of a Long Term Evolution (LTE) system according to an embodiment of the present disclosure;

[0015] Figure 2B This is a diagram illustrating the radio protocol architecture in an LTE system according to an embodiment of the present disclosure.

[0016] Figure 2C This is a diagram illustrating the configuration of a novel mobile communication system according to an embodiment of the present disclosure;

[0017] Figure 2D This is a diagram illustrating the radio protocol architecture of a novel mobile communication system according to embodiments of the present disclosure;

[0018] Figure 2EThis is a diagram illustrating a process performed by a base station to indicate whether uplink data compression (UDC) should be performed when a terminal establishes a connection to a network, according to an embodiment of the present disclosure.

[0019] Figure 2F This is a diagram illustrating the process and data structures for performing a UDC according to embodiments of the present disclosure;

[0020] Figure 2G This is a diagram used to describe a UDC method according to an embodiment of the present disclosure;

[0021] Figure 2H The process and data structure for performing Robust Header Compression (ROHC) according to embodiments of the present disclosure are illustrated;

[0022] Figure 2I An embodiment according to this disclosure is shown, wherein a Service Data Access Protocol (SDAP) entity generates an SDAP header for data received from an upper layer, and a Packet Data Convergence Protocol (PDCP) entity applies integrity protection to the SDAP header without performing an encryption process;

[0023] Figure 2J An embodiment according to this disclosure is shown, wherein the SDAP entity generates an SDAP header for data received from the upper layer, and the PDCP entity does not perform the process of integrity protection and encryption of the SDAP header;

[0024] Figure 2K This illustrates the advantages of a base station structure implemented by applying an SDAP header that is not subject to encryption or integrity protection, according to embodiments of the present disclosure.

[0025] Figure 2L This illustrates the advantages of processing that can be obtained from base stations and user equipment (UEs) by applying SDAP headers that are not subject to encryption and integrity protection, according to embodiments of the present disclosure.

[0026] Figure 2M The present disclosure illustrates an embodiment in which an SDAP entity generates an SDAP header for data received from an upper layer, and a PDCP entity does not perform integrity protection and encryption on the SDAP header and does not perform encryption on the Message Authentication Code-I (MAC-I) used for integrity.

[0027] Figure 2N This illustrates the advantages of processing that can be obtained from a base station and UE by applying an SDAP header that is not subject to encryption and integrity protection and by not encrypting the MAC-I, according to one embodiment.

[0028] Figure 2OThe present disclosure illustrates an embodiment in which an SDAP entity generates an SDAP header for data received from an upper layer, and a PDCP entity performs header compression (i.e., ROHC), applies integrity protection to the SDAP header, and does not perform encryption on the SDAP header.

[0029] Figure 2P An embodiment according to this disclosure is shown, wherein the SDAP entity generates an SDAP header for data received from the upper layer, and the PDCP entity performs header compression (i.e., ROHC), and does not perform integrity protection and encryption processes on the SDAP header;

[0030] Figure 2Q This illustrates the advantages of processing that can be obtained from a base station and a UE by applying an SDAP header that is not subject to encryption and integrity protection, according to embodiments of the present disclosure.

[0031] Figure 2R The illustration shows an embodiment according to the present disclosure, wherein the SDAP entity generates an SDAP header for data received from the upper layer, and the PDCP entity performs header compression (i.e., ROHC), without performing integrity protection and encryption on the SDAP header, and without performing encryption on the MAC-I.

[0032] Figure 2S The embodiments of the present disclosure illustrate the advantages of processing that can be obtained from the base station and UE by applying SDAP headers that are not encrypted and protected for integrity, by applying ROHC, and by implementing processing without MAC-I encryption.

[0033] Figure 2T The present disclosure illustrates an embodiment in which an SDAP entity generates an SDAP header for data received from an upper layer, and a PDCP entity performs UDC, applies integrity protection to the UDC header, performs encryption on the UDC header, applies integrity protection to the SDAP header, and does not perform encryption on the SDAP header.

[0034] Figure 2U The present disclosure illustrates an embodiment in which an SDAP entity generates an SDAP header for data received from an upper layer, and a PDCP entity performs UDC, applies integrity protection to the UDC header without encrypting the UDC header, applies integrity protection to the SDAP header without encrypting the SDAP header.

[0035] Figure 2VThe present invention illustrates an embodiment of the present disclosure in which an SDAP entity generates an SDAP header for data received from an upper layer, and a PDCP entity performs a UDC, does not apply integrity protection to the UDC header, does not encrypt the UDC header, encrypts the MAC-I, does not apply integrity protection to the SDAP header, and does not encrypt the SDAP header.

[0036] Figure 2W This illustrates the advantages of processing obtained by the base station and UE from embodiments of the present disclosure, which can be achieved by applying SDAP headers and UDC headers that are not subject to encryption and integrity protection.

[0037] Figure 2X The present disclosure illustrates an embodiment in which an SDAP entity generates an SDAP header for data received from an upper layer, and a PDCP entity performs UDC, without applying integrity protection to the UDC header, without encrypting the UDC header, without applying integrity protection to the SDAP header, without encrypting the SDAP header, and without encrypting the MAC-I.

[0038] Figure 2Y The embodiments of the present disclosure illustrate the advantages of processing obtained by the base station and UE through the application of SDAP headers and UDC headers that are not subject to encryption and integrity protection, through the implementation of UDC, and through unencrypted MAC-I.

[0039] Figure 2Z This illustration shows the operation of a logical channel, bearer, or SDAP / PDCP entity transmitting and receiving SDAP / PDCP entities configured with integrity protection when an SDAP header without integrity protection and encryption is applied to an SDAP / PDCP entity, according to an embodiment of the present disclosure.

[0040] Figure 2AA The configuration of a UE according to an embodiment of this disclosure is shown;

[0041] Figure 2AB The configuration of a base station according to an embodiment of the present disclosure is shown;

[0042] Figure 3A This is a diagram illustrating the configuration of an LTE system according to an embodiment of the present disclosure;

[0043] Figure 3B This is a diagram illustrating the radio protocol architecture in an LTE system according to an embodiment of the present disclosure.

[0044] Figure 3C This is a diagram used to illustrate carrier aggregation (CA) in a UE according to embodiments of the present disclosure;

[0045] Figure 3D This is a diagram used to illustrate the concept of multiple connectivity in LTE and New Radio (NR) according to embodiments of this disclosure;

[0046] Figure 3E A method for transmitting an uplink according to the configuration and type of the uplink, according to an embodiment of the present disclosure, is illustrated;

[0047] Figure 3F The illustration shows a message flow between a UE and a base station to which the UE reports power headroom (PHR) simultaneously, while dual connectivity is established between different radio access technologies (RATs) according to an embodiment of the present disclosure.

[0048] Figure 3G This is a diagram illustrating the UE's operation flow when a UE reports a PHR while dual connectivity is established between different RATs according to an embodiment of this disclosure; and

[0049] Figure 3H This is a block diagram illustrating the configuration of a UE in a wireless communication system according to an embodiment of the present disclosure.

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

[0051] The aspects of this disclosure will at least address the aforementioned problems and / or disadvantages, and provide at least the following advantages. Therefore, one aspect of this disclosure will provide an apparatus and method capable of efficiently providing communication in a wireless communication system.

[0052] Other aspects will be set forth in part in the description which follows, and will also be apparent in part from the description, or may be learned by practicing the embodiments presented in this disclosure.

[0053] According to one aspect of this disclosure, a method of operating a transmitting device in a wireless communication system is provided. The method includes: configuring a Higher Layer Signaling Receive Service Data Adaptation Protocol (SDAP) header and configuring header compression; and when an SDAP entity receives first data from an upper layer, generating an SDAP header and transmitting second data obtained by adding the generated SDAP header to the first data to a Packet Data Convergence Protocol (PDCP) entity, wherein the generation and transmission are performed by the SDAP entity, the PDCP entity performs header compression on the upper layer header of the second data excluding the SDAP header, the PDCP entity encrypts the second data excluding the SDAP header and generates a PDCP header, and transmits third data obtained by adding the generated PDCP header to the encrypted data to a lower layer, wherein the generation and transmission are performed by the PDCP entity.

[0054] According to another aspect of this disclosure, a method for operating a receiving device in a wireless communication system is provided. The method includes: when a PDCP entity receives first data from a lower layer, receiving SDAP header configuration and header compression configuration via higher-layer signaling; the PDCP entity reading and removing PDCP headers and SDAP headers from the first data; the PDCP entity decrypting the data obtained by removing the PDCP headers and SDAP headers from the first data; and the PDCP entity sending second data obtained by decompressing the headers of the decrypted data to the upper layer.

[0055] According to another aspect of this disclosure, a transmitting apparatus in a wireless communication system is provided. The apparatus includes: a transceiver configured to receive SDAP header configuration and header compression configuration via higher-layer signaling; and a controller configured to, when an SDAP entity receives first data from an upper layer, control the SDAP entity to generate an SDAP header, transmit second data obtained by adding the generated SDAP header to the first data to a PDCP entity, control the PDCP entity to perform header compression on the upper-layer header of the second data (excluding the SDAP header), encrypt the data of the second data (excluding the SDAP header) to generate a PDCP header, and transmit third data obtained by adding the generated PDCP header to the encrypted data to a lower layer.

[0056] According to another aspect of this disclosure, a receiving apparatus in a wireless communication system is provided. The apparatus includes: a transceiver configured to receive an SDAP header configuration and a header compression configuration via higher-layer signaling; and a controller configured to, when a PDCP entity receives first data from a lower layer, control the PDCP entity to read and remove a PDCP header and an SDAP header from the first data, perform decryption on the data obtained by removing the PDCP header and the SDAP header from the first data, and send second data obtained by performing header decompression on the decrypted data to an upper layer.

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

[0058] Implementation

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

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

[0061] In describing embodiments of this disclosure, technical content known in the relevant art and not directly related to this disclosure will not be provided. By omitting redundant descriptions, the essence of this disclosure will remain unambiguous and can be clearly explained.

[0062] For the same reason, and for clarity, components may be shown enlarged, omitted, or schematically in the accompanying drawings. Furthermore, the size of each component does not perfectly reflect its actual size. In the drawings, the same reference numerals denote the same elements.

[0063] As used herein, the term "and / or" includes any and all combinations of one or more of the related listed items. When an expression such as "at least one of..." follows a list of elements, it modifies the entire list of elements and does not modify any individual element in the list.

[0064] The advantages and features of one or more embodiments of this disclosure, as well as methods of implementing them, can be more readily understood through the following detailed description with reference to the embodiments and accompanying drawings. In this regard, embodiments of this disclosure may take different forms and should not be construed as limited to the description set forth herein. Rather, these embodiments of this disclosure are provided to make this disclosure thorough and complete, and to fully convey the concept of embodiments of this disclosure to those skilled in the art, and this disclosure is limited only by the appended claims.

[0065] Here it will be understood that combinations of blocks in a flowchart or process flowchart can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or another programmable data processing device, the instructions, executed by the processor of the computer or other programmable data processing device, create units for performing the functions described in the flowchart(s). The computer program instructions can be stored in a computer-usable or computer-readable storage medium capable of directing the computer or other programmable data processing device to perform its functions in a particular manner, and therefore the instructions stored in the computer-usable or computer-readable storage medium can also produce an article of art comprising instruction units for performing the functions described in the flowchart(s). The computer program instructions can also be loaded into the computer or other programmable data processing device, and therefore, instructions for operating the computer or other programmable data processing device by generating a process executed by the computer when a series of operations are performed in the computer or said other programmable data processing device can provide operations for performing the functions described in the flowchart(s).

[0066] Furthermore, each block may represent a portion of a module, segment, or code that includes one or more executable instructions for performing a specified logical function(s). It should also be noted that in some alternative implementations, the functions mentioned in a block may occur out of order. For example, two blocks shown consecutively may actually execute substantially simultaneously, or these blocks may sometimes execute in reverse order according to their respective functions.

[0067] Here, the term "unit" as used in embodiments of this disclosure refers to a software component or hardware component, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), that performs a specific function. However, the term "unit" is not limited to software or hardware. A "unit" may be formed in an addressable memory medium or may be formed to operate one or more processors. Thus, for example, the term "unit" may refer to components such as software components, object-oriented software components, class components, and task components, and may include processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, or variables. The functionality provided by components and "units" may be associated with a smaller number of components and "units," or may be divided into additional components and "units." Furthermore, components and "units" may be specifically implemented as reproducing one or more central processing units (CPUs) in a device or secure multimedia card. Additionally, in embodiments, a "unit" may include at least one processor.

[0068] In the following description, terms are provided for ease of description, including terms for identifying access nodes, referring to network entities, referring to messages, indicating interfaces between network entities, and indicating individual identification information. Therefore, this disclosure is not limited to the following terms, and other terms may be used to refer to objects with equivalent technical meanings.

[0069] For ease of description, this disclosure uses terms and names defined in the 3GPP LTE standard, or terms and names modified based on said terms and names. However, this disclosure is not limited to the terms and names and can be applied equivalently to systems conforming to other standards.

[0070] Figure 1 is a diagram of the time-frequency domain transmission structure of a DL radio resource area in an LTE system or similar system according to an embodiment of the present disclosure.

[0071] Referring to Figure 1, the horizontal axis represents the time domain within the radio resource area, and the vertical axis represents the frequency domain within the radio resource area. In the time domain, the smallest transmission unit is an OFDM symbol, and N is aggregated. symbOFDM symbols 1a-02 are used to form a time slot 1a-06, and two time slots are combined to form a subframe 1a-05. The length of a time slot can be 0.5 ms, and the length of a subframe can be 0.1 ms. Radio frame 1a-14 is a time-domain interval consisting of 10 subframes. The smallest transmission unit in the frequency domain is a subcarrier, and the total transmission bandwidth of the entire system consists of N. RB DL It consists of 1a-04 subcarriers. However, this specific value can vary depending on the system.

[0072] In the time-frequency domain, the basic unit of a resource is a resource element (RE) 1a-12, which can be indicated by OFDM symbol indices and subcarrier indices. A resource block (RB) 1a-08 or PRB is defined as N in the time domain. symb A series of consecutive OFDM symbols 1a-02 and N in the frequency domain RB A series of consecutive subcarriers 1a-10. Therefore, an RB 108 consists of N in one time slot. symb XN RB It consists of RE 1a-12.

[0073] Generally, the smallest unit of data transmission is RB, and in LTE systems, generally, N symb It is 7, and N RB It is 2, and N BW and N RB It can be proportional to the system's transmission bandwidth. However, systems other than LTE can use different values. The data rate increases proportionally to the number of scheduled RBs.

[0074] In LTE systems, six transmission bandwidths can be defined and operated. In FDD systems where DL and UL are divided and operated by frequency, the transmission bandwidths of DL and UL may differ from each other. Channel bandwidth indicates the radio frequency (RF) bandwidth corresponding to the system transmission bandwidth. [Table 1] presents the correspondence between system transmission bandwidth and channel bandwidth defined in LTE systems. For example, in an LTE system with a channel bandwidth of 10 MHz, the transmission bandwidth consists of 50 RBs.

[0075] [Table 1]

[0076] <![CDATA[Channel bandwidth BW Channel [MHz]]]> 1.4 3 5 10 15 20 <![CDATA[Transmission Bandwidth Configuration N RB > 6 15 25 50 75 100

[0077] DL control information can be transmitted within the first N OFDM symbols of a subframe. Generally, N = {1, 2, 3}. Therefore, the value N can be changed for each subframe depending on the amount of control information to be transmitted in the current subframe. The control information may include a control channel transmission interval indicator indicating how many OFDM symbols the control information is transmitted over, scheduling information regarding DL data or UL data, and HARQ ACK / NACK signals.

[0078] In LTE systems, scheduling information for DL ​​data or UL data is transmitted from the BS to the terminal via downlink control information (DCI). DCI is defined in various formats and can indicate, based on each format, whether the scheduling information is UL data scheduling information (UL grant) or DL ​​data scheduling information (DL grant), whether the DCI is a compact DCI with small control information size, whether spatial multiplexing using multiple antennas is applied, or whether the DCI is used for power control. For example, DCI format 1, as scheduling control information for DL ​​data (DL grant), can include at least the following control information:

[0079] - Resource Allocation Type 0 / 1 Flag: Indicates whether the resource allocation type is Type 0 or Type 1. Type 0 allocates resources in units of resource block groups (RBGs) through the application of bitmap types. In LTE systems, the basic unit of scheduling is an RB, expressed as time-domain and frequency-domain resources, and an RBG consists of multiple RBs that are considered the basic unit of scheduling in Type 0. Type 1 allocates specific RBs within an RBG.

[0080] -RB Allocation: Indicates the allocation of RBs for data transmission. The resources expressed are determined based on system bandwidth and resource allocation methods.

[0081] - Modulation and coding scheme (MCS): Indicates the modulation method used for data transmission and the size of the transport block (TB) of data to be transmitted.

[0082] -HARQ process number: Indicates the process number of HARQ.

[0083] - New data indicator: Indicates whether the HARQ transfer is an initial transfer or a retransmission.

[0084] - Redundant version: Indicates a redundant version of HARQ.

[0085] - Transmit power control (TPC) commands for the physical uplink control channel (PUCCH): These are commands that indicate the transmit power control of the PUCCH, which acts as the UL control channel.

[0086] After the channel coding and modulation process, DCI can be transmitted via the Physical Downlink Control Channel (PDCCH) (or control information, used interchangeably below) as the DL Physical Control Channel or Enhanced PDCCH (EPDCCH) (or Enhanced Control Information, used interchangeably below).

[0087] Generally, a DCI (Digital Channel Interchange) is independently scrambled for each terminal using a specific radio network temporary identifier (RNTI) or terminal identifier, cyclic redundancy check (CRC) is added, channel-coded, and then configured as an independent PDCCH (Programmable Channel Controlled Controller) to be transmitted. In the time domain, the PDCCH is mapped and transmitted for the control channel transmission interval. The mapping position of the PDCCH in the frequency domain is determined by the identifier (ID) of each terminal, and the PDCCH can be transmitted across the entire system's transmission frequency band.

[0088] DL data can be transmitted via the physical downlink shared channel (PDSCH), which serves as the physical channel for transmitting DL data. The PDSCH can be transmitted after the control channel transmission interval, and scheduling information (such as the specific mapping position or modulation method in the frequency domain) can be included in the DCI to be transmitted via the PDSCH.

[0089] The BS informs the terminal of the modulation method to be applied to the PDSCH to be transmitted and the transport block size (TBS) to be transmitted by using the MCS in the control information that constitutes the DCI. The MCS can consist of 5 bits or another number of bits. The TBS corresponds to the size before the channel coding for error correction is applied to the TB to be transmitted by the BS.

[0090] According to an embodiment, the TB may include a MAC header, a MAC CE, at least one MAC service data unit (SDU), and padding bits. Furthermore, the TB may indicate a unit of data sent from the MAC layer to the physical layer or a MAC protocol data unit (PDU).

[0091] The supported modulation methods in LTE systems are quadrature phase shift keying (QPSK), 16 quadrature amplitude modulation (16QAM), or 64QAM, with corresponding modulation orders (Qm) of 2, 4, and 6. In QPSK modulation, 2 bits per symbol can be transmitted; in 16QAM, 4 bits per symbol; and in 64QAM, 6 bits per symbol. Furthermore, depending on system modifications, 256QAM or higher modulation methods can be used.

[0092] Figure 1B This is a diagram of the time-frequency domain transmission structure of the UL radio resource area of ​​an LTE system or similar system according to an embodiment of this disclosure.

[0093] refer to Figure 1B The horizontal axis represents the time domain within the radio resource area, and the vertical axis represents the frequency domain within the radio resource area. Radio frame 1b-14 is the time domain interval. In the time domain, the smallest transmission unit is SC-FDMA symbol 1b-02, and N is aggregated. symbUL SC-FDMA symbols are used to form a time slot 1b-06. Two time slots are combined to form a subframe 1b-05. The smallest transmission unit in the frequency domain is a subcarrier, and the total transmission bandwidth of the entire system consists of N symbols. RB UL It consists of 1b-04 subcarriers. N RB UL It can have a value proportional to the system's transmission bandwidth.

[0094] In the time-frequency domain, the basic unit of a resource is RE 1b-12, which can be defined as an SC-FDMA symbol index and subcarrier index. RB pair 1b-08 is defined as N in the time domain. symb N in a consecutive SC-FDMA symbol and frequency domain RB 1b-10 consecutive subcarriers. Therefore, an RB consists of N symb XN RB It consists of 1 RE. Generally, the smallest transmission unit for data or control information is the RB unit. A PUCCH can be mapped on the frequency domain corresponding to one RB and transmitted for one subframe.

[0095] In LTE systems, the timing relationship between the PDCCH (Physical Channel for transmitting DL data) or the PDCCH / EPDCCH (including semi-persistent scheduling, SPS release) released by the PDCCH / EPDCCH and the UL (Ultra-Low Utility Channel, PUCCH, or PUSCH) through which the corresponding HARQACK / NACK is transmitted can be defined. As an example, in an LTE system operating as FDD, the HARQ ACK / NACK corresponding to the PDSCH transmitted in the (n-4)th subframe, or the PDCCH / EPDCCH (including SPS release), is transmitted by the PUCCH or PUSCH in the nth subframe.

[0096] In LTE systems, DL HARQ employs an asynchronous HARQ method, where the data retransmission time is not fixed. When a HARQ NACK is received from the terminal relative to the initial data sent by the BS, the BS freely determines the transmission time of the retransmitted data through scheduling operations. The terminal buffers data identified as erroneous in response to the HARQ operation as the result of decoding the received data, and then combines it with the next retransmitted data.

[0097] When the terminal receives a PDSCH containing DL data sent from the BS in subframe n, it sends HARQ ACK or NACK control information, including DL data, to the BS via PUCCH or PUSCH in subframe n+k. k can be defined differently depending on the LTE system's FDD or Time Division Duplex (TDD) configuration and subframe configuration. As an example, in an FDD LTE system, k is fixed at 4. On the other hand, in a TDD LTE system, k can be changed according to the subframe configuration and subframe number. During data transmission across multiple carriers, the value of k can be applied differently depending on the TDD configuration of each carrier.

[0098] In LTE systems, unlike DL HARQ, UL HARQ employs a synchronous HARQ method where data transmission time is fixed. The UL / DL timing relationship between the Physical Uplink Shared Channel (PUSCH), the physical channel used to transmit UL data, the PDCCH, the preceding DL control channel, and the Physical Hybrid Indicator Channel (PHICH), the physical channel through which DL HARQ ACK / NACK corresponding to the PUSCH is transmitted, can be fixed by the following rules.

[0099] When the terminal receives a PDCCH containing UL scheduling control information sent from the BS in subframe n, or a PHICH that sends DL HARQ ACK / NACK via it, the terminal sends UL data corresponding to the control information via PUSCH in subframe n+k. k can be defined differently depending on whether the LTE system is FDD or TDD and its configuration. As an example, in an FDD LTE system, k is fixed at 4. On the other hand, in a TDD LTE system, k can be changed according to the subframe configuration and subframe number.

[0100] In an FDD LTE system, when the BS sends UL scheduling approval or DL ​​control signals and data to the terminal in subframe n, the terminal receives UL scheduling approval or DL ​​control signals and data in subframe n. First, upon receiving UL scheduling approval in subframe n, the terminal sends UL data in subframe n+4. Upon receiving DL control signals and data in subframe n, the terminal sends HARQ ACK or NACK relative to the DL data in subframe n+4. Therefore, the preparation time for the terminal to receive UL scheduling approval and send UL data, or to receive DL data and send HARQ ACK or NACK, is 3ms corresponding to the three subframes. Additionally, when the terminal receives a PHICH carrying DL HARQ ACK / NACK from the BS in subframe i, the PHICH corresponds to the PUSCH sent by the terminal in subframe ik. k is defined differently depending on whether the LTE system is FDD or TDD and its configuration. As an example, in an FDD LTE system, k is fixed at 4. On the other hand, in a TDD LTE system, k can be changed according to the subframe configuration and subframe number. During data transmission over multiple carriers, the k value can be applied differently depending on the TDD configuration of each carrier.

[0101] The wireless communication system has been described above with reference to the LTE system; however, the embodiments are not only applicable to LTE systems but also to various other wireless communication systems, such as NR and 5G systems. When the embodiments are applied to another wireless communication system, the value of k can be changed, even in systems using modulation methods corresponding to FDD.

[0102] In 5G or NR access technology systems, which are new communication systems, various services are designed to be freely multiplexed on time and frequency resources. Therefore, waveforms, parameter sets, reference signals, etc., can be dynamically or freely allocated according to the needs of the corresponding service. To provide optimal service to terminals in wireless communication, data transmission optimized through channel quality and interference measurements is crucial; therefore, accurate measurement of channel states is essential. However, unlike 4G communication, where channel and interference characteristics do not change significantly based on frequency resources, in 5G or NR systems, channel and interference characteristics may change significantly depending on the service. This necessitates support for subsets in the Frequency Resource Group (FRG) to segment and measure channel and interference characteristics. Simultaneously, the service types supported in 5G or NR systems can be categorized into eMBB, mMTC, and URLLC. Here, eMBB can be a service for high-speed transmission of large amounts of data, mMTC can be a service for minimizing terminal power consumption and facilitating access for multiple terminals, and URLLC can be a service for high reliability and low latency. Different requirements can be applied based on the service type applied to the terminal.

[0103] In this way, multiple services can be provided to users in a communication system, and methods and apparatus are needed to provide multiple services in the same time zone in order to provide multiple services to users.

[0104] Figure 2A This is a diagram illustrating the configuration of an LTE system according to an embodiment of the present disclosure.

[0105] refer to Figure 2A The radio access network of the LTE system consists of multiple evolved Node Bs (hereinafter referred to as eNBs, Node Bs, or base stations) 2a-05, 2a-10, 2a-15, and 2a-20, a Mobility Management Entity (MME) 2a-25, and a Service Gateway (S-GW) 2a-30. User equipment (hereinafter referred to as UEs or terminals) 2a-35 accesses the external network via eNBs 2a-05, 2a-10, 2a-15, and 2a-20, and S-GW 2a-30.

[0106] exist Figure 2AIn this context, eNBs 2a-05, 2a-10, 2a-15, and 2a-20 correspond to Node Bs in the Universal Mobile Telecommunications System (UMTS). Each of eNBs 2a-05, 2a-10, 2a-15, and 2a-20 is connected to UE 2a-35 and performs more complex functions compared to Node Bs. In LTE systems, all user traffic, including real-time services such as Voice over Internet Protocol (VoIP), is provided through a shared channel. Therefore, a device is needed to acquire and schedule multiple state information of the UE (including buffer status, available transmission power status, channel status, etc.), and eNBs 2a-05, 2a-10, 2a-15, and 2a-20 correspond to this device. Typically, one eNB controls multiple cells. For example, to achieve a transmission speed of 100 Mbps, the LTE system uses Orthogonal Frequency Division Multiplexing (OFDM) as the radio access technology in a 20 MHz bandwidth. Furthermore, the LTE system uses AMC technology to determine the modulation scheme and channel coding rate based on the UE's channel state. The S-GW 2a-30 is a device configured to provide data bearers and generates or removes data bearers in response to the control of the MME 2a-25. The MME2a-25 performs mobility management functions for the UE, as well as various control functions for the UE, and connects to multiple eNBs.

[0107] Figure 2B This is a diagram illustrating the radio protocol architecture in an LTE system according to an embodiment of the present disclosure.

[0108] refer to Figure 2B In both the UE and LTE eNB, the radio protocol of the LTE system can consist of Packet Data Convergence Protocol (PDCP) 2b-05 and 2b-40, Radio Link Control (RLC) 2b-10 and 2b-35, Media Access Control (MAC) 2b-15 and 2b-30, and Physical Layer (PHY) 2b-20 and 2b-25. PDCP 2b-05 and 2b-40 can perform operations such as IP header compression / decompression. The main functions of PDCP 2b-05 and 2b-40 are summarized below.

[0109] - Header compression and decompression (ROHC only).

[0110] -Transmission of user data.

[0111] - Sequential transfer of upper-layer packet data units (PDUs) during the PDCP reconstruction process of RLC AM.

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

[0113] - Duplicate detection of lower-level service data units (SDUs) during the PDCP reconstruction process of RLC AM.

[0114] - PDCP SDU for retransmission function during switching and for separate bearers in DC, and PDCP PDU for PDLC data recovery process for RLC AM.

[0115] - Encryption and decryption functions.

[0116] - Timer-based SDU dropping in the uplink.

[0117] RLC 2b-10 and 2b-35 reconfigure PDCP PDUs to an appropriate size to perform Automatic Repeat Request (ARQ) operations, etc. The main functionalities of RLC 2b-10 and 2b-35 are summarized below.

[0118] -Transmission of upper-layer PDUs.

[0119] - Error correction via ARQ (only for Acknowledgment mode (AM) data transmission).

[0120] - Serialization, segmentation, and reassembly of RLC SDUs (only for unacknowledged mode (UM) and AM data transmission).

[0121] - Resegmentation of RLC data PDUs (for AM data transmission only).

[0122] - Reordering of RLC data PDUs (only for UM and AM data transfers).

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

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

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

[0126] -RLC reconstruction.

[0127] MAC 2b-15 and 2b-30 connect to multiple RLC entities configured in a UE and perform operations such as multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC 2b-15 and 2b-30 are summarized below.

[0128] - Mapping between logical channels and transport channels.

[0129] - Multiplexing MAC SDUs belonging to one or different logical channels into transport blocks (TBs) that are passed to the physical layer on the transport channel / Demultiplexing MAC SDUs belonging to one or different logical channels from transport blocks (TBs) passed from the physical layer on the transport channel.

[0130] - Scheduling information report.

[0131] - Error correction via HARQ.

[0132] Priority processing between logical channels of a UE.

[0133] - Prioritization among UEs through dynamic scheduling.

[0134] -MBMS service identifier.

[0135] -Select the transmission format.

[0136] -filling.

[0137] PHY 2b-20 and 2b-25 perform channel coding and modulation of upper-layer data and transmit OFDM symbols over a wireless channel by converting the upper-layer data into OFDM symbols, or perform demodulation and channel decoding of OFDM symbols received over a wireless channel and transmit the decoded data to the upper layer.

[0138] Figure 2C This is a diagram illustrating the configuration of a novel mobile communication system according to an embodiment of the present disclosure.

[0139] refer to Figure 2C The new mobile communication system's radio access network (hereinafter referred to as New Radio (NR) or 5G) consists of a new radio node B (hereinafter referred to as NR gNB or NR base station) 2c-10 and a new radio core network (hereinafter referred to as NR CN) 2c-05. New radio user equipment (hereinafter referred to as NR UE or terminal) 2c-15 accesses external networks through NR gNB 2c-10 and NR CN 2c-05.

[0140] exist Figure 2CIn NR, the NR gNB 2c-10 corresponds to the Evolved Node B (eNB) of the LTE system. Compared to the eNB according to existing technology, the NR gNB 2c-10 connects to the NR UE 2c-15 via a radio channel and can provide superior service. In NR, all user services are provided through a shared channel; therefore, a device is needed to acquire and schedule multiple state information of the UE (including buffer status, available transmission power status, channel status, etc.), and the NR gNB 2c-10 corresponds to this device. Typically, one NR gNB 2c-10 controls multiple cells. Compared to existing LTE systems, it can provide bandwidth greater than the maximum bandwidth of existing LTE to achieve high-speed data transmission, and beamforming technology can be added to radio access technologies such as OFDM.

[0141] In addition, NR uses AMC technology to determine the modulation scheme and channel coding rate based on the UE's channel state. NRCN 2c-05 performs functions supporting mobility, configuring bearers, and configuring Quality of Service (QoS). NR CN 2c-05 is a device configured to perform not only mobility management functions for the UE but also various control functions for the UE, and is connected to multiple NBs. Furthermore, NR can interoperate with LTE systems, and NR CN 2c-05 is connected to MME 2c-25 via a network interface. MME 2c-25 is connected to eNB 2c-30, which serves as an existing base station.

[0142] Figure 2D This is a diagram illustrating the radio protocol architecture of a novel mobile communication system according to an embodiment of the present disclosure.

[0143] refer to Figure 2D The radio protocol of the new mobile communication system consists of NR Service Data Access Protocol (SDAP) 2d-01 and 2d-45, NR PDCP 2d-05 and 2d-40, NR RLC 2d-10 and 2d-35, and NR MAC 2d-15 and 2d-30.

[0144] The main functions of NR SDAP 2d-01 and 2d-45 may include some of the following functions.

[0145] -Transmission of user plane data.

[0146] - Used for mapping between Quality of Service (QoS) streams and data bearers for both downlink and uplink.

[0147] - Mark the QoS flow identifier (ID) in both downlink and uplink data packets.

[0148] - Mapping of reflected QoS flows to data bearers for uplink SDAP PDUs.

[0149] Regarding SDAP entities, the UE can be configured via Radio Resource Control (RRC) messages to use either the SDAP entity header or the functionality of the SDAP entity per PDCP entity, per bearer, or per logical channel. When the SDAP header is configured, it can instruct the UE to update or reconfigure the mapping information regarding QoS flows and data bearers for both uplink and downlink by using a 1-bit indicator of Non-Access Stratum (NAS) reflected QoS configuration and a 1-bit indicator of Access Stratum (AS) reflected QoS configuration. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used for data processing priority ordering, scheduling information, etc., in supporting smooth service.

[0150] The main functions of NR PDCP 2d-05 and 2d-40 may include some of the following functions.

[0151] - Header compression and decompression (ROHC only).

[0152] -Transmission of user data.

[0153] - The upper-layer PDUs are passed in sequence.

[0154] - The upper-layer PDUs are passed out of order.

[0155] - Used for reordering received PDCP PDUs.

[0156] - Duplicate detection of lower-level SDUs.

[0157] -Retransmission of PDCP SDU.

[0158] - Encryption and decryption functions.

[0159] - Timer-based SDU dropping in the uplink.

[0160] In the above text, the reordering for receiving NR PDCP 2d-05 and 2d-40 can refer to the function of reordering the order of PDCP PDUs received from the lower layer based on the PDCP sequence number (SN), and can include the following functions: transmitting data to the upper layer in the reordered order, or transmitting data directly regardless of the order, reordering the order and recording lost PDCP PDUs, sending a status report about lost PDCP PDUs to the transmitter, and requesting the retransmission of lost PDCP PDUs.

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

[0162] -Transmission of upper-layer PDUs.

[0163] - The upper-layer PDUs are transmitted in sequence.

[0164] - The upper-layer PDUs are transmitted out of order.

[0165] - Error correction via ARQ.

[0166] - Serialization, segmentation, and reassembly of RLC SDUs.

[0167] - Resegmentation of RLC data PDUs.

[0168] - Reordering of RLC data PDUs.

[0169] - Duplicate detection function.

[0170] - Protocol error detection.

[0171] -RLC SDU discarded.

[0172] -RLC reconstruction.

[0173] In this regard, the sequential delivery of NR RLC 2d-10 and 2d-35 can refer to the function of sequentially transmitting RLC Service Data Units (SDUs) received from the lower layer to the upper layer, and can include the following functions: when an RLC SDU that has been segmented into multiple RLC SDUs is received, the function of reassembling and transmitting multiple RLC SDUs; the function of reordering received RLC PDUs according to the RLC Sequence Number (SN) or PDCP SN; the function of reordering the sequence and recording lost RLC PDUs; the function of sending a status report on lost RLC PDUs to the transmitter; and the function of requesting retransmission of lost RLC PDUs. When there is a lost RLC SDU, sequential transmission may include the function of sequentially transmitting only the RLC SDUs preceding the lost RLC SDU to the upper layer, and even when there is a lost RLC SDU, when the preset timer expires, it may include the function of sequentially transmitting all RLC SDUs received before the preset timer starts to the upper layer, or it may include the function of sequentially transmitting all RLC SDUs received to date to the upper layer when the timer expires, even when there is a lost RLC SDU. Additionally, NR RLC 2d-10 and 2d-35 can process RLC PDUs in the order of reception (arrival order, regardless of sequence number order) and can transmit RLC PDUs to NR PDCP 2d-05 and 2d-40, regardless of order (out-of-order transmission). In the case of fragmentation, NR RLC 2d-10 and 2d-35 can receive fragments stored in a buffer, or fragments to be received later, reconstruct the fragment into an RLCPDU, then process the RLC PDU and transmit it to NR PDCP 2d-05 and 2d-40. NR RLC 2d-10 and 2d-35 may not include cascading functionality. Cascading functionality can be performed by NR MAC 2d-15 and 2d-30, or it can be replaced by the multiplexing functionality of NR MAC 2d-15 and 2d-30.

[0174] Out-of-order delivery in NR RLC 2d-10 and 2d-35 can refer to the function of directly transmitting RLC SDUs received from a lower layer to an upper layer (regardless of order). When receiving an RLC SDU that has been segmented into multiple RLC SDUs, out-of-order delivery can include the function of reassembling and transmitting multiple RLC SDUs. Furthermore, out-of-order delivery can include storing and sorting the RLC SN or PDCP SN of the received RLC PDUs, as well as recording lost RLC PDUs.

[0175] NR MAC 2d-15 and 2d-30 can connect to multiple NR RLC entities configured in a single UE, and the main functions of NRMAC 2d-15 and 2d-30 may include some of the following functions.

[0176] - Mapping between logical channels and transport channels.

[0177] - MAC SDU multiplexing / demultiplexing.

[0178] - Scheduling information reporting function.

[0179] - Error correction via HARQ.

[0180] Priority processing between logical channels of a UE.

[0181] - Prioritization among UEs through dynamic scheduling.

[0182] -MBMS service identifier.

[0183] -Select the transmission format.

[0184] -filling.

[0185] PHY 2d-20 and 2d-25 perform channel coding and modulation of upper-layer data and transmit OFDM symbols over a wireless channel by converting the upper-layer data into OFDM symbols, or perform demodulation and channel decoding of OFDM symbols received over a wireless channel and transmit the decoded data to the upper layer.

[0186] In new mobile communication systems, data bearers transmitting data can perform integrity protection and authentication. The PDCP layer, which processes data sent to / received by the data bearer, performs highly complex encryption and decryption, and the integrity protection and authentication processes also require high complexity. Therefore, to reduce the complexity of data processing, an efficient integrity protection and authentication process is needed.

[0187] This disclosure provides a method for reducing data processing complexity in a wireless communication system relative to a signaling radio bearer or data radio bearer (DRB) in which integrity protection and integrity verification are configured.

[0188] Figure 2E This is a diagram illustrating a process performed by the gNB to indicate whether uplink data compression (UDC) should be performed when a UE establishes a connection to the network, according to an embodiment of the present disclosure.

[0189] Figure 2EThis illustrates the process by which a base station (gNB) requests a UDC when a UE in RRC idle mode or RRC inactive (or lightly connected) mode switches to RRC connected mode and establishes a connection to the network.

[0190] refer to Figure 2EWhen a UE transmitting and receiving data in RRC connection mode fails to transmit or receive data for some reason or within a certain period of time, the gNB sends an RRCConnectionRelease message to the UE to switch to RRC idle mode (Operation 2e-01). Subsequently, when a UE that has not yet established a connection with the base station (hereinafter referred to as the idle mode UE) has data to transmit, the idle mode UE performs an RRC connection establishment procedure with the gNB. The idle mode UE establishes reverse transmission synchronization with the gNB through a random access procedure and sends an RRCConnectionRequest message to the gNB (Operation 2e-05). The RRCConnectionRequest message may include the identifier of the idle mode UE, the reason for establishment, etc. The gNB sends an RRCConnectionSetup message, causing the idle mode UE to establish an RRC connection (Operation 2e-10). The RRCConnectionSetup message may include information indicating whether UDC is used for each logical channel (LogicalChannelConfig), each bearer, or each PDCP layer (PDCP-Config). More specifically, for each logical channel, each bearer, or each PDCP layer (or each Serving Data Access Protocol (SDAP) layer), the RRCConnectionSetup message can indicate which IP flow or QoS flow the UDC method will be used for. (The RRCConnectionSetup message can configure the SDAP layer with information about which IP flow or QoS flow will use or not use the UDC method, and the SDAP layer can then instruct the PDCP layer whether to use the UDC method for each QoS flow. Alternatively, the PDCP layer can autonomously examine each QoS flow and then determine whether to apply the UDC method to it.) In this regard, when instructed to use the UDC method, the identifier of the predefined library or dictionary to be used in the UDC method or the size of the buffer to be used in the UDC method can be indicated. Additionally, the RRCConnectionSetup message may include uplink data decompression settings or release commands. In this regard, when configured to use UDC, the UE can always be configured with an RLC AM bearer (lossless mode due to ARQ or retransmission functionality) and may not be configured with a header compression protocol (e.g., Robust Header Compression (ROHC) protocol). Additionally, the RRCConnectionSetup message may include information indicating whether to use the functionality of the SDAP entity or whether to use the SDAP header for each logical channel (LogicalChannelConfig), each bearer, or each PDCP device (PDCP-Config).The RRCConnectionSetup message may include information indicating whether to apply ROHC (IP Packet Header Compression) to each logical channel (LogicalChannelConfig), each bearer, or each PDCP device (PDCP-Config), and configures whether ROHC is applied to the corresponding uplink and downlink using various indicators. However, ROHC and UDC cannot be configured simultaneously in one PDCP entity, one logical channel, or one bearer, and UDC can be configured in no more than two bearers. Additionally, the RRCConnectionSetup message may include information indicating whether to apply integrity protection and integrity verification to each logical channel (LogicalChannelConfig), each bearer, or each PDCP device (PDCP-Config), and can configure integrity protection and integrity verification considering the maximum data transmission rate of the corresponding PDCP entity, the corresponding bearer, or the corresponding logical channel. When configuring UDC, header compression (ROHC), or integrity protection in each logical channel, each bearer, or each PDCP device, its use can be configured for each in the uplink and downlink. That is, it can be configured to use it for the uplink but not for the downlink, or vice versa. Additionally, the RRCConnectionSetup message may include RRC connection configuration information. An RRC connection can refer to a signaling radio bearer (SRB) and can be used when sending and receiving RRC messages, which are control messages between the UE and the gNB. The UE establishes an RRC connection and then sends an RRCConnectionSetupComplete message to the gNB (Operation 2e-15). If the gNB is unaware of or wishes to check the capabilities of the currently connected UE, it may send a UE capability inquiry message. The UE may send a UE capability report message. The UE capability report message may include an indicator indicating whether the UE can use the UDC method, ROHC, or integrity protection. The RRCConnectionSetupComplete message may include control messages, such as a SERVICE REQUEST message used by the UE to request the MME to configure a bearer for a specific service.

[0191] The gNB sends a SERVICE REQUEST message, included in the RRCConnectionSetupComplete message, to the MME (Operation 2e-20), and the MME determines whether to provide the service requested by the UE. As a result of this determination, when the MME decides to provide the service requested by the UE, the MME sends an INITIAL CONTEXT SETUP REQUEST message to the gNB (Operation 2e-25). The INITIAL CONTEXT SETUP REQUEST message includes QoS information to be applied when configuring the Data Radio Bearer (DRB), security information to be applied to the DRB (e.g., security keys, security algorithms, etc.), etc.

[0192] The gNB exchanges SecurityModeCommand (2e-30) and SecurityModeComplete (2e-35) messages with the UE to configure the security mode. After the security mode is fully configured, the gNB sends an RRCConnectionReconfiguration (2e-40) message to the UE. The RRCConnectionReconfiguration message may include information indicating whether the UDC method is used for each logical channel (LogicalChannelConfig), each bearer, or each PDCP layer (PDCP-Config). More specifically, for each logical channel, each bearer, or each PDCP layer (or each SDAP layer), the RRCConnectionReconfiguration message can indicate which IP flow or QoS flow the UDC method will be used for. (The RRCConnectionReconfiguration message can be configuration information for the SDAP layer regarding which IP flow or QoS flow will use or not use the UDC method, and the SDAP layer can then instruct the PDCP layer whether to use the UDC method for each QoS flow. Alternatively, the PDCP layer can autonomously examine each QoS flow and then determine whether to apply the UDC method to it.) In this regard, when instructed to use the UDC method, the identifier of the predefined library or dictionary to be used in the UDC method or the size of the buffer to be used in the UDC method can be indicated. Additionally, the RRCConnectionReconfiguration message can include uplink data decompression settings or release commands. In this regard, when configured to use UDC, the UE can always be configured with an RLC AM bearer (lossless mode due to ARQ or retransmission functions) and may not be configured with a header compression protocol (e.g., ROHC). In addition, the RRCConnectionReconfiguration message may include information indicating whether to apply the functionality of the SDAP entity or whether to use the SDAP header for each logical channel (LogicalChannelConfig), each bearer, or each PDCP device (PDCP-Config). The RRCConnectionReconfiguration message may also include information indicating whether to apply ROHC (IP Packet Header Compression) to each logical channel (LogicalChannelConfig), each bearer, or each PDCP device (PDCP-Config), and configure whether to apply ROHC to the corresponding uplink and downlink using appropriate indicators.However, ROHC and UDC cannot be configured simultaneously in a single PDCP entity, logical channel, or bearer, and UDC can be configured in no more than two bearers. Additionally, the RRCConnectionReconfiguration message may include information indicating whether integrity protection and integrity verification are applied to each logical channel (LogicalChannelConfig), each bearer, or each PDCP device (PDCP-Config), and integrity protection and integrity verification can be configured considering the maximum data transmission rate of the corresponding PDCP entity, corresponding bearer, or corresponding logical channel. When configuring UDC, Header Compression (ROHC), or integrity protection in each logical channel, each bearer, or each PDCP device, its use can be configured for each in the uplink and downlink. That is, it can be configured to use it in the uplink but not in the downlink, or vice versa. Furthermore, the RRCConnectionReconfiguration message may include setting information about the DRB for processing user data, and the UE sets the DRB using this setting information and sends an RRCConnectionReconfigurationComplete message to the gNB (Operation 2e-45).

[0193] The gNB completes the DRB setup with the UE, then sends an INITIAL CONTEXT SETUP COMPLETE message (operation 2e-50) to the MME. The MME receives this message and then exchanges an S1 BEARERSETUP message (2e-55) and an S1 BEARER SETUP RESPONSE message (2e-60) with the S-GW to set up the S1 bearer. The S1 bearer indicates the data transmission connection established between the S-GW and the gNB and corresponds to the DRB one-to-one. When the above process is complete, the UE and gNB transmit and receive data via the S-GW (operations 2e-65 and 2e-70). The general data transmission process described above includes three steps: RRC connection setup, security setup, and DRB setup. The gNB can send an RRCConnectionReconfiguration message to the UE to perform, add, or change the UE's configuration (operation 2e-75). The RRCConnectionReconfiguration message may include information indicating whether the UDC method is used for each logical channel (LogicalChannelConfig), each bearer, or each PDCP layer (PDCP-Config). More specifically, for each logical channel, each bearer, or each PDCP layer (or each SDAP layer), the RRCConnectionReconfiguration message may indicate which IP flow or QoS flow the UDC method will be used for. (The RRCConnectionReconfiguration message can configure information to the SDAP layer regarding which IP flow or QoS flow will use or not use the UDC method, and the SDAP layer can then instruct the PDCP layer whether to use the UDC method for each QoS flow. Alternatively, the PDCP layer can autonomously examine each QoS flow and then determine whether to apply the UDC method to it.) In this regard, when instructed to use the UDC method, the identifier of the predefined library or dictionary to be used in the UDC method or the size of the buffer to be used in the UDC method may be indicated. Additionally, the RRCConnectionReconfiguration message may include uplink data decompression settings or release commands. In this respect, when configured to use UDC, it can always be configured with RLC AM bearer (lossless mode due to ARQ or retransmission functions) and can be unconfigured with header compression protocols (e.g., ROHC protocol).Additionally, the RCConnectionReconfiguration message may include information indicating whether to apply the functionality of the SDAP entity or whether to use the SDAP header for each logical channel (LogicalChannelConfig), each bearer, or each PDCP device (PDCP-Config). The RCConnectionReconfiguration message may also include information indicating whether to apply ROHC (IP Packet Header Compression) to each logical channel (LogicalChannelConfig), each bearer, or each PDCP device (PDCP-Config), and configure whether to apply ROHC to the corresponding uplink and downlink using appropriate indicators. However, ROHC and UDC cannot be configured simultaneously in one PDCP entity, one logical channel, or one bearer, and UDC can be configured in no more than two bearers. Furthermore, the RCConnectionReconfiguration message may include information indicating whether to apply integrity protection and integrity authentication to each logical channel (LogicalChannelConfig), each bearer, or each PDCP device (PDCP-Config), and can configure integrity protection and integrity authentication taking into account the maximum data transmission rate of the corresponding PDCP entity, the corresponding bearer, or the corresponding logical channel. When configuring UDC, Header Compression (ROHC), or Integrity Protection in each logical channel, each bearer, or each PDCP device, its use can be configured for each in the uplink and downlink. That is, it can be configured to use it in the uplink but not in the downlink, or not in the uplink but in the downlink.

[0194] Figure 2F This is a diagram illustrating the process and data structure for performing a UDC according to an embodiment of the present disclosure.

[0195] exist Figure 2F In this process, uplink data 2f-05 can be generated into data corresponding to services including video transmission, photo transmission, web browsing, and Voice over LTE (VoLTE). Multiple data items generated in the application layer can be processed by network data transmission layers such as Transmission Control Protocol and Internet Protocol (TCP / IP) or User Datagram Protocol (UDP) to configure each of headers 2f-10 and 2f-15, and multiple data items can be transmitted to the PDCP layer. When the PDCP layer receives data (PDCP SDU) from the upper layer, it can perform the procedures described below.

[0196] exist Figure 2EIn the PDCP layer, when RRC messages 2e-10, 2e-40, or 2e-75 indicate the use of UDC, the PDCP layer performs UDC 2f-22 on the PDCP SDU as shown in 2f-20 to compress uplink data. The UDC header (header for compressed uplink data) 2f-25 can be configured, and integrity protection can be performed when configured to do so. Encryption can be performed, and the PDCP header 2f-30 can be configured to generate the PDCP SDU. The PDCP entity, including the means for processing UDC (UDC compressor / UDC decompressor), determines whether to perform the UDC 2f-22 procedure for each data based on the configuration of the RRC message and uses the UDC compressor / UDC decompressor. The sending end performs data compression 2f-22 using the UDC compressor in its PDCP layer, while the receiving end performs data decompression using the UDC decompressor in its PDCP layer.

[0197] Figure 2F This process can be applied not only to uplink data compression but also to downlink data compression, which is performed by the UE. Furthermore, the description of uplink data can be applied equally to downlink data.

[0198] Figure 2G This is a diagram used to describe an embodiment of the UDC according to the present disclosure.

[0199] Figure 2G The DEFLATE-based UDC algorithm is shown, which is a lossless compression algorithm. Based on the DEFLATE-based UDC algorithm, uplink data can essentially be compressed using a combination of the LZ77 algorithm and Huffman coding.

[0200] According to the LZ77 algorithm, the operation of finding repeated occurrences of data within a sliding window is performed. When a repeated occurrence is found within the sliding window, data compression is performed by representing the repeated data within the sliding window as its position and length. The sliding window, referred to as a buffer in the UDC method, can be set to 8 kilobytes or 32 kilobytes. That is, the sliding window or buffer can record 8192 characters or 32768 characters, find repeated occurrences of data, and perform data compression by representing the repeated data as its position and length. Therefore, since the LZ77 algorithm is a sliding window scheme, meaning that subsequent data may be correlated after the previously encoded data in the buffer is updated, subsequent data can only be decoded normally if the previously encoded data is decoded normally. In this regard, the code compressed using the LZ77 algorithm and represented as position and length is compressed again using the Huffman coding algorithm. According to the Huffman coding algorithm, repeated characters can be found and data compression can be performed again by assigning the shortest code to the most frequent character and the longest code to the least frequent character. Huffman coding is a prefix coding algorithm and an optimal coding scheme, through which all codes can be uniquely decoded.

[0201] As described above, the sending end can encode the original data 2g-05 using the LZ77 algorithm (2g-10), update the buffer 2g-15, and configure the UDC header by generating a checksum bit for the buffer's contents (or data). The receiving end can use the checksum bit to determine the validity of the buffer state. The sending end can compress the code encoded using the LZ77 algorithm using Huffman coding (2g-20) and send the compressed data as uplink data (2g-25). The receiving end can perform decompression on the compressed data received from the sending end in the reverse manner. That is, based on the checksum bit of the UDC header, the receiving end can perform Huffman decoding (2g-30), update the buffer (2g-35), and check the validity of the updated buffer. After confirming that there are no errors in the checksum bit, the receiving end can decompress the data to reconstruct the original data by performing decoding using the LZ77 algorithm (2g-40) and pass the decompressed data to the upper layer (2g-45).

[0202] As mentioned above, since the LZ77 algorithm uses a sliding window scheme, subsequent data may be correlated because they are encoded immediately after the previously encoded data in the buffer is updated. Therefore, subsequent data can only be decoded normally if the previously encoded data has been decoded correctly. Thus, the PDCP layer at the receiving end can check the PDCP sequence number in the PDCP header, check the UDC header (checking the indicator indicating whether data compression has been performed), and perform data decompression on the compressed UDC data in ascending order of the PDCP sequence number.

[0203] Figure 2H The process and data structure for performing ROHC according to embodiments of the present disclosure are shown.

[0204] exist Figure 2F In this process, uplink data 2h-05 can be generated into data corresponding to services including video transmission, photo transmission, web browsing, VoLTE, etc. Multiple data items generated in the application entity can be processed through the network data transmission layer (e.g., TCP / IP or UDP) to configure each of the headers 2h-10 and 2h-15, and multiple data items can be transmitted to the PDCP layer. When the PDCP layer receives data (PDCP SDU) from the upper layer, it can perform the procedures described below.

[0205] exist Figure 2E In the PDCP layer, when RRC messages 2e-10, 2e-40, or 2e-75 indicate the use of ROHC, the PDCP layer performs ROHC on the PDCP SDU as shown in 2h-20 to compress the header of the received upper-layer data 2h-15 and generate a compressed header 2h-25. Integrity protection can be performed when configured to perform integrity verification, encryption can be performed, and the PDCP header 2h-30 can be configured to generate the PDCP PDU. The PDCP entity, including the header compressor / decompressor, determines whether to perform header compression on each piece of data based on the configuration of the RRC message and uses the header compressor / decompressor. At the sending end, the sending PDCP entity performs data compression using the header compressor, while at the receiving end, the receiving PDCP entity performs data decompression using the header decompressor.

[0206] Figure 2H This process can be applied not only to the compression of uplink data headers but also to the compression of downlink data headers, and this compression is performed by the UE. Furthermore, the description of uplink data can be applied equally to downlink data.

[0207] Figure 2IAn embodiment according to this disclosure is shown, wherein the SDAP entity generates an SDAP header for data received from the upper layer, and the PDCP entity applies integrity protection to the SDAP header without performing an encryption process.

[0208] exist Figure 2I In the case where an RRC message is configured to use the functionality of an SDAP entity or uses an SDAP header and is configured to perform integrity protection and integrity verification, such as... Figure 2E The RRC messages shown (see 2e-10, 2e-40, or 2e-75) allow the SDAP entity to generate and configure SDAP headers, as shown in 2i-05, when receiving data from the upper layer, and to transmit these headers to the PDCP entity. When integrity protection is configured, the PDCP entity can perform integrity protection 2i-10 on the PDCP SDUs (SDAP header and IP packets 2i-05) received from the upper-layer SDAP entity and can calculate the Message Authentication Code (MAC-I) for integrity. When calculating MAC-I 2i-15, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and the data portion (where integrity protection has been applied) can be input values ​​to the integrity protection algorithm. As shown in 2i-25, the calculated MAC-I can be concatenated to the end of the data. The MAC-I can have a certain size, such as 4 bytes. In addition to the SDAP header (2i-30), the PDCP entity can perform encryption on MAC-I connected to 2i-25 (2i-20), generate and configure the PDCP header and connect it to encrypted data that has already been connected to the SDAP header (2i-35), and transmit the data to the lower layer. Then, the RLC entity and MAC entity can perform data processing (2i-40 and 2i-45).

[0209] The receiving end removes the MAC and RLC headers, then transmits the data to the PDCP layer. The receiving end's PDCP entity reads and removes the PDCP header, and decrypts the data portion (excluding the SDAP header). Afterward, the receiving end's PDCP entity performs integrity verification on the SDAP header, upper-layer header (TCP / IP header), and data portion, and calculates the calculated MAC-I (X-MAC). When the X-MAC is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and the data portion (which has undergone integrity protection) can be input values ​​for the integrity protection algorithm. The receiving end's PDCP entity checks if the X-MAC value is equal to the MAC-I value concatenated to the end of the data. When the two values ​​are equal, integrity verification succeeds; however, when the X-MAC and MAC-I values ​​are not equal, integrity verification fails. Therefore, the receiving end's PDCP entity discards the data and must report the integrity verification failure to the upper layer (e.g., the RRC layer).

[0210] Figure 2J An embodiment according to this disclosure is shown, wherein the SDAP entity generates an SDAP header for data received from the upper layer, and the PDCP entity does not perform a process of integrity protection and encryption on the SDAP header.

[0211] exist Figure 2J In the case where an RRC message is configured to use the functionality of an SDAP entity or uses an SDAP header and is configured to perform integrity protection and integrity verification, such as... Figure 2EThe RRC messages shown (see 2e-10, 2e-40, or 2e-75) allow the SDAP entity to generate and configure SDAP headers, as shown in 2i-05, when receiving data from the upper layer, and to transmit these headers to the PDCP entity. When integrity protection is configured, the PDCP entity can perform integrity protection 2i-10 on only the data (IP packets) of the PDCP SDU (SDAP header and IP packets 2i-05) received from the upper-layer SDAP entity, excluding the SDAP header, and can calculate MAC-I 2j-15. When calculating MAC-I, the PDCPCOUNT value, uplink or downlink indicator, bearer indicator, security key, and the data portion (where integrity protection has been applied) can be input values ​​to the integrity protection algorithm. As shown in 2j-20, the calculated MAC-I can be concatenated to the end of the data. MAC-I can have a certain size, such as 4 bytes. In addition to the SDAP header (2i-30), the PDCP entity can perform encryption 2j-25 on 2j-20 concatenated to MAC-I, generate and configure the PDCP header and concatenate it to the data (2j-35), and transmit the data to the lower layer. Then, the RLC entity and MAC entity can perform data processing (2j-40 ​​and 2j-45). A feature of embodiments of this disclosure is that MAC-I is also encrypted.

[0212] The receiving end removes the MAC and RLC headers and transmits the data to the PDCP layer. The receiving end's PDCP entity reads and removes the PDCP and SDAP headers, and decrypts the data portion (excluding the SDAP header). In this respect, the MAC-I is also decrypted. Afterward, the receiving end's PDCP entity performs integrity verification on the upper-layer header (TCP / IP header) and the data portion, and calculates the calculated MAC-I (X-MAC). When the X-MAC is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and the (integrity-protected) data portion can be input values ​​for the integrity protection algorithm. The receiving end's PDCP entity checks if the X-MAC value is equal to the MAC-I value concatenated to the end of the data. When the two values ​​are equal, integrity verification succeeds; however, when the X-MAC and MAC-I values ​​are not equal, integrity verification fails. Therefore, the receiving end's PDCP entity discards the data and must report the integrity verification failure to the upper layer (e.g., the RRC layer).

[0213] In this way, configuring the base station implementation can be simplified when encryption or integrity protection is not performed on the SDAP header, especially in a separate Central Unit (CU) - Distributed Unit (DU) structure. When the CU does not encrypt the SDAP header, the DU can check QoS information by reading the SDAP header and apply the QoS information to scheduling, thus matching and adjusting QoS may be advantageous. Moreover, the aforementioned features can offer advantages in data processing during UE and base station configuration.

[0214] Figure 2K This illustrates the advantages of a base station structure implemented according to embodiments of the present disclosure by applying an SDAP header that is not subject to encryption or integrity protection.

[0215] When Figure 2K When implementing a base station as described above, to reduce initial facility and maintenance costs, upper-layer entities (e.g., PDCP entities and their upper-layer counterparts) can be implemented in the CU, and lower-layer entities (e.g., RLC entities and their lower-layer counterparts) can be implemented in multiple DUs connected to the CU. In such a CU-DU separate structure, when referring to this disclosure... Figure 2J When an SDAP header without encryption or integrity protection via PDCP entity 2k-05 is applied, as described, multiple DU 2k-15s can read SDAP header 2k-10. Because SDAP header 2k-10 is not encrypted or integrity protected, QoS information can be checked and applied to the scheduling of DU 2k-15s. Therefore, since each of the DU 2k-15s can use the QoS information in SDAP header 2k-10 to allocate transport resources and perform scheduling, matching and adjusting the QoS of each service can be advantageous.

[0216] Figure 2L This illustrates the advantages of processing that can be obtained from a base station and a UE by applying an SDAP header that is not subject to encryption and integrity protection, according to embodiments of the present disclosure.

[0217] exist Figure 2L In the implementation of UE and base station, the SDAP entity and PDCP entity can be unified into a single entity (2l-01). This is because logically, the SDAP entity is the upper-layer entity of the PDCP entity. Therefore, when data 2l-05 is received from the upper application layer, if the RRC message is configured to use the functions of the SDAP entity or use the SDAP header and as shown in the example... Figure 2E When integrity protection is configured in the RRC message shown (see 2e-10, 2e-40, or 2e-75), and the SDAP entity receives data from the upper layer, as follows: Figure 2JIn 2j-05, the SDAP entity must generate and configure the SDAP header. However, the encryption or integrity protection process is a highly complex operation in the implementation of the UE and base station, which can be performed by applying a hardware (HW) accelerator. Hardware accelerators gain significant advantages in processing repetitive and sequential processes. However, when the SDAP entity configures the SDAP header and is configured to perform integrity protection whenever the SDAP entity receives data from an upper-layer entity, interruptions to the HW accelerator may occur when the integrity protection and encryption processes, PDCP header generation, and PDCP header concatenation with the SDAP header are performed on data portions other than the SDAP header. This is because the SDAP header is generated before the integrity protection and encryption processes are performed during this process.

[0218] Therefore, this disclosure describes a method for implementing an SDAP header that is not subject to integrity protection and encryption, and for implementing an entity through a unified SDAP entity and PDCP entity. Specifically, when receiving data from the upper application layer, each time data is received, the integrity protection process (21-10) can be performed continuously and repeatedly, the MAC-I can be calculated and then concatenated to the end of the data (21-15), the encryption process can be performed on the MAC-I and the data to which integrity protection is applied (21-20), the PDCP header and SDAP header can be generated simultaneously (21-25), and then concatenated to the data to which integrity protection and encryption are performed, before the data is transmitted to the lower layer. The generation of the PDCP header and SDAP header can be processed in parallel with the integrity protection process or the encryption process. In this respect, when generating headers in parallel, the SDAP header, PDCP header, RLC header, or MAC header can be generated together, and these headers can be concatenated at once to the beginning of data that has already undergone complete data processing and is ready for transmission (the configuration of the MAC PDU can be prepared). Furthermore, the receiving end can separate and read the SDAP header, PDCP header, RLC header, or MAC header from the data in one go, identify the information corresponding to each layer, and process the data in the reverse order of the data processing performed by the sending end. Therefore, the HW accelerator can be applied continuously and repeatedly, and since there are no interruptions such as SDAP header generation between them, the efficiency of data processing can be improved. Additionally, when integrity protection is configured, the HW accelerator can be applied to integrity protection as described regarding the encryption process before performing the encryption process, thus allowing integrity protection to be performed repeatedly. That is, integrity protection can be performed, and then the encryption process can be performed.

[0219] The receiving end's PDCP entity can be implemented as a single entity using a unified SDAP entity and PDCP entity, as described in 2l-01. That is, when data is received from the lower layer (RLC layer), if the RRC message is configured to use the SDAP entity's functionality or uses the SDAP header, as shown... Figure 2E The RRC messages shown (see 2e-10, 2e-40, or 2e-75) allow one entity in the SDAP and PDAP entities to read and remove both the PDCP and SDAP headers at once, and the decryption or decryption process can be repeatedly applied to the data. Additionally, when integrity protection is configured, after performing the decryption process, the HW accelerator can be applied to integrity verification as described regarding the decryption process, thus allowing integrity verification to be performed repeatedly. That is, the decryption process can be performed, and then integrity verification can be performed.

[0220] Figure 2M The present disclosure illustrates an embodiment in which the SDAP entity generates an SDAP header for data received from the upper layer, and the PDCP entity does not perform integrity protection and encryption on the SDAP header and does not perform encryption on the MAC-I.

[0221] exist Figure 2M In the case where an RRC message is configured to use the functionality of an SDAP entity or uses an SDAP header and is configured to perform integrity protection and integrity verification, such as... Figure 2EThe RRC messages shown (see 2e-10, 2e-40, or 2e-75) allow the SDAP entity to generate and configure SDAP headers, as shown in 2m-05, when receiving data from the upper layer, and to transmit these headers to the PDCP entity. When integrity protection is configured, the PDCP entity can perform integrity protection (2m-10) on only the data (IP packets) of the PDCP SDU (SDAP header and IP packets 2m-05) received from the upper-layer SDAP entity, excluding the SDAP header, and can calculate the MAC-I. When calculating the MAC-I, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and the (integrity-protected) data portion can be input values ​​to the integrity protection algorithm. As shown in 2m-20, the calculated MAC-I can be concatenated to the end of the data. The MAC-I can have a certain size, such as 4 bytes. In addition to the SDAP header and MAC-I (2m-30 and 2m-35), the PDCP entity can encrypt the MAC-I concatenated to 2m-25, generate and configure the PDCP header and concatenate it to the data (2m-40), and transmit the data to the lower layer. Then, the RLC entity and MAC entity can perform data processing (2j-40 ​​and 2j-45). An embodiment of this disclosure is characterized by not encrypting the MAC-I. When the MAC-I is not encrypted, as will be described below, further advantages in data processing can be obtained.

[0222] The receiving end removes the MAC and RLC headers, then transmits the data to the PDCP layer. The receiving end's PDCP entity reads and removes the PDCP and SDAP headers, and decrypts the data portion (excluding the SDAP header and MAC-I at the end). At this point, the MAC-I is not decrypted. Afterward, the receiving end's PDCP entity performs integrity verification on the upper-layer headers (TCP / IP header) and the data portion (excluding the SDAP header), and calculates the calculated MAC-I (X-MAC). When the X-MAC is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and the data portion (which has undergone integrity protection) can be input values ​​for the integrity protection algorithm. The receiving end's PDCP entity checks whether the X-MAC value is equal to the MAC-I value concatenated to the end of the data. Integrity verification succeeds when the two values ​​are equal, but fails when the values ​​of X-MAC and MAC-I are not equal. Therefore, the PDCP entity at the receiving end discards the data and must report the integrity verification failure to the upper layer (e.g., the RRC layer).

[0223] In this way, when no encryption or integrity protection is performed on the SDAP header, the configuration of the base station implementation can be simplified, especially in a separate CU-DU structure. When the CU does not encrypt the SDAP header, the DU can check the QoS information by reading the SDAP header and apply the QoS information to scheduling, thus matching and adjusting QoS may be advantageous. Moreover, the aforementioned features can have advantages in data processing in the configuration of the UE and the base station. In addition, when MAC-I is not encrypted, as will be described below, further advantages in data processing can be obtained.

[0224] Figure 2N This illustrates the advantages of processing that can be obtained from a base station and UE by applying an SDAP header that is not subject to encryption and integrity protection and by not encrypting the MAC-I, according to one embodiment.

[0225] exist Figure 2N In the implementation of UE and base station, the SDAP entity and PDCP entity can be unified into a single entity (2n-01). This is because logically, the SDAP entity is the upper-layer entity of the PDCP entity. Therefore, when receiving data 2n-05 from the upper application layer, if the RRC message is configured to use the functions of the SDAP entity or use the SDAP header and as shown in the example... Figure 2E When integrity protection is configured in the RRC message shown (see 2e-10, 2e-40, or 2e-75), and the SDAP entity receives data from the upper layer, as follows: Figure 2J In 2j-05, the SDAP entity must generate and configure the SDAP header. However, the encryption or integrity protection process is a highly complex operation in the implementation of the UE and base station, which can be performed by its application hardware (HW) accelerator. The HW accelerator gains a high advantage in processing repetitive and continuous processes. However, when the SDAP entity configures the SDAP header and is configured to perform integrity protection whenever the SDAP entity receives data from the upper-layer entity, interruptions to the HW accelerator may occur when the integrity protection and encryption processes, the generation of the PDCP header, and the concatenation of the PDCP header with the SDAP header are performed on the data portion other than the SDAP header. This is because the operation of generating the SDAP header before performing the integrity protection and encryption processes may occur.

[0226] Therefore, this disclosure describes a method for implementing an SDAP header and an unencrypted MAC-I without integrity protection and encryption, and for implementing an entity through a unified SDAP entity and PDCP entity. Specifically, when receiving data from the upper application layer, each time data is received, the integrity protection process (2n-10) can be executed continuously and repeatedly, the MAC-I (2n-20 and 2n-25) can be calculated, and the encryption process can be performed on the data for which integrity protection is applied (2n-30). The PDCP header, SDAP header, and MAC-I can be generated simultaneously and then concatenated to the data for which integrity protection and encryption are performed, after which the data can be transmitted to the lower layer (2n-35). In other words, the generated header can be concatenated to the beginning of the data, and the MAC-I can be concatenated to the end of the data. The generation of the PDCP header, SDAP header, and MAC-I can be processed in parallel with the integrity protection process or the encryption process. In this respect, when generating headers in parallel, SDAP, PDCP, RLC, or MAC headers can be generated together, and these headers can be concatenated at once to the beginning of data that has already undergone complete data processing and is ready for transmission (the MAC PDU configuration may be ready). MAC-I can be concatenated to the end of data that has already undergone complete data processing. Furthermore, the receiving end can separate and read the SDAP, PDCP, RLC, or MAC headers from the data at once, identify the information corresponding to each layer, and process the data in the reverse order of the data processing performed by the sending end. Therefore, the HW accelerator can be applied continuously and repeatedly, and since there are no interruptions such as SDAP header generation between them, the efficiency of data processing can be improved. Additionally, when integrity protection is configured, the HW accelerator can be applied to integrity protection as described regarding the encryption process before performing the encryption process, thus allowing integrity protection to be performed repeatedly. That is, integrity protection can be performed, and then the encryption process can be performed.

[0227] The receiving end's PDCP entity can be implemented as a single entity using a unified SDAP entity and PDCP entity, as described in 2l-01. That is, when data is received from the lower layer (RLC layer), if the RRC message is configured to use the SDAP entity's functionality or uses the SDAP header, as shown... Figure 2EThe RRC messages shown (see 2e-10, 2e-40, or 2e-75) allow one entity in the SDAP and PDAP entities to read and remove both the PDCP and SDAP headers at once, and the process of applying neither encryption nor decryption to the data can be repeated. Additionally, when integrity protection is configured, after performing the decryption process, the HW accelerator can be applied to integrity verification as described regarding the decryption process, thus allowing integrity verification to be performed repeatedly. That is, the decryption process can be performed, and then integrity verification can be performed.

[0228] Figure 2O The present disclosure illustrates an embodiment in which an SDAP entity generates an SDAP header for data received from an upper layer, and a PDCP entity performs header compression (i.e., ROHC), applies integrity protection to the SDAP header, and does not perform encryption on the SDAP header.

[0229] exist Figure 2O In the case where an RRC message is configured to use the functionality of an SDAP entity or use an SDAP header, is configured to perform integrity protection and integrity verification, or is configured to perform ROHC on the uplink or downlink, such as... Figure 2E The RRC message shown (see 2e-10, 2e-40, or 2e-75) allows the SDAP entity to generate and configure the SDAP header as described in 2o-05 when receiving data from the upper layer, and can then transmit the SDAP header to the PDCP entity. The PDCP entity performs ROHC on the upper-layer header (e.g., IP datagram header) of the received PDCP SDU (2o-10). When integrity protection is configured, the PDCP entity can perform integrity protection 2o-20 on the PDCP SDU (SDAP header and IP packet 2o-05) received from the upper-layer SDAP entity and for which ROHC has been applied, and can calculate MAC-I (2o-25). When calculating MAC-I, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and (integrity-protected) data portion can be input values ​​to the integrity protection algorithm. As shown in 2o-30, the calculated MAC-I can be concatenated to the end of the data. The MAC-I can have a certain size, such as 4 bytes. In addition to the SDAP header (2o-40), the PDCP entity can perform encryption (2o-35) on the MAC-I concatenated to 2o-30, generate and configure the PDCP header and concatenate it to the data (2o-45), and transmit the data to the lower layer. Then, the RLC entity and the MAC entity can perform data processing.

[0230] The receiving end removes the MAC and RLC headers, then transmits the data to the PDCP layer. The receiving end's PDCP entity reads and removes the PDCP header, and decrypts the data portion (excluding the SDAP header). Afterward, the receiving end's PDCP entity performs integrity verification on the SDAP header, upper-layer header (TCP / IP header), and data portion, and calculates the X-MAC. When the X-MAC is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and the data portion (which has undergone integrity protection) can be input values ​​for the integrity protection algorithm. The receiving end's PDCP entity checks if the X-MAC value is equal to the MAC-I value concatenated to the end of the data. When the two values ​​are equal, integrity verification succeeds; however, when the X-MAC and MAC-I values ​​are not equal, integrity verification fails. Therefore, the receiving end's PDCP entity discards the data and must report the integrity verification failure to the upper layer (e.g., the RRC layer). Once integrity verification is complete, the ROHC decompression process can be performed on the upper-layer header (e.g., IP packet header), and the reconstructed upper-layer data can be transmitted to the upper layer.

[0231] Figure 2P An embodiment according to this disclosure is shown, wherein the SDAP entity generates an SDAP header for data received from the upper layer, and the PDCP entity performs header compression (i.e., ROHC), and does not perform integrity protection and encryption processes on the SDAP header.

[0232] exist Figure 2P In the case of an RRC message being configured to use SDAP entity functions or use SDAP headers, configured to perform integrity protection and integrity verification, and configured to perform ROHC on the uplink or downlink, the RRC message will behave as follows: Figure 2EAs shown (see 2e-10, 2e-40, or 2e-75), when the SDAP entity receives data from the upper layer, it can generate and configure the SDAP header as described in 2p-05, and can transmit the SDAP header to the PDCP entity. The PDCP entity performs ROHC 2p-10 on the upper-layer header (e.g., IP datagram header) of the received PDCP SDU (2p-15). When integrity protection is configured, the PDCP entity can perform integrity protection 2p-20 on only the data (IP packets) of the PDCP SDU (SDAP header and IP packets 2p-25) received from the upper-layer SDAP entity, excluding the SDAP header, and ROHC can be applied to the data. MAC-I (2p-30) can also be calculated. When MAC-I is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and the data portion (where integrity protection has been applied) can be input values ​​to the integrity protection algorithm. As shown in 2p-35, the calculated MAC-I can be concatenated to the end of the data. The MAC-I can have a certain size, such as 4 bytes. In addition to the SDAP header (2p-45), the PDCP entity can perform encryption on 2p-35 (2p-40) to which the MAC-I is concatenated, generate and configure the PDCP header and concatenate it to the data (2p-50), and transmit the data to the lower layer. Then, the RLC entity and the MAC entity can perform data processing. A feature of embodiments of this disclosure is that the MAC-I is also encrypted.

[0233] As described above, in addition to the SDAP header of the PDCP SDU received from the upper layer, the PDCP entity can apply only the ROHC to the upper-layer header of the SDAP entity (e.g., IP packet header). The PDCP SDU may include the SDAP header, the upper-layer header of the SDAP entity (e.g., IP packet header), and the upper-layer data of the SDAP entity (IP packet data). In this way, because the ROHC is not applied to the SDAP header, the degree of freedom in base station implementation can be increased, and the processing complexity of the UE can be reduced.

[0234] The receiving end removes the MAC and RLC headers and transmits the data to the PDCP layer. The receiving end's PDCP entity reads and removes the PDCP and SDAP headers, and decrypts the data portion (excluding the SDAP header). In this respect, the MAC-I is also decrypted. Afterward, the receiving end's PDCP entity performs integrity verification on the upper-layer headers (TCP / IP header) and the data portion (excluding the SDAP header), and calculates the calculated MAC-I (X-MAC). When the X-MAC is calculated, the PDCPCOUNT value, uplink or downlink indicator, bearer indicator, security key, and the (integrity-protected) data portion can be input values ​​for the integrity protection algorithm. The receiving end's PDCP entity checks whether the X-MAC value is equal to the MAC-I value concatenated to the end of the data. Integrity verification succeeds when the two values ​​are equal, but fails when the values ​​of X-MAC and MAC-I are unequal. Therefore, the receiving PDCP entity discards the data and must report the integrity verification failure to the upper layer (e.g., the RRC layer). Once integrity verification is complete, the ROHC decompression process can be performed on the upper-layer header (e.g., the IP packet header), and the reconstructed upper-layer data can be transmitted to the upper layer.

[0235] In this way, the configuration of the base station implementation can be simplified when no encryption or integrity protection is performed on the SDAP header, especially in a CU-DU split structure. When the CU does not encrypt the SDAP header, the DU can check the QoS information by reading the SDAP header and apply the QoS information to scheduling, thus matching and adjusting QoS may be advantageous. Moreover, the aforementioned features can have advantages in data processing in the configuration of the UE and the base station.

[0236] Furthermore, as mentioned above, not performing ROHC on the SDAP header simplifies the configuration of the base station implementation, especially in a CU-DU separate structure. When the CU does not encrypt the SDAP header, the DU can check QoS information by reading the SDAP header and apply the QoS information to scheduling, thus matching and adjusting QoS may be advantageous. Moreover, the aforementioned features can offer advantages in data processing during UE and base station configuration.

[0237] Figure 2Q This illustrates the advantages of processing that can be obtained from a base station and a UE by applying an SDAP header that is not subject to encryption and integrity protection, according to embodiments of the present disclosure.

[0238] exist Figure 2QIn the implementation of UE and base station, the SDAP entity and PDCP entity can be unified into a single entity (2q-01). This is because logically, the SDAP entity is the upper-layer entity of the PDCP entity. Therefore, when receiving data 2q-05 from the upper application layer, if the RRC message is configured to use the SDAP entity's functionality or uses the SDAP header and as shown in... Figure 2E When integrity protection is configured in the RRC message shown (see 2e-10, 2e-40, or 2e-75), and the SDAP entity receives data from the upper layer, as follows: Figure 2J In 2j-05, the SDAP entity must generate and configure the SDAP header. However, the encryption or integrity protection process is a highly complex operation in the implementation of the UE and base station, which can be performed by applying an HW accelerator. The HW accelerator gains significant advantages from repetitive and continuous processes. However, when the SDAP entity configures the SDAP header and is configured to perform integrity protection whenever the SDAP entity receives data from an upper-layer entity, the HW accelerator may be interrupted when the integrity protection and encryption processes, the generation of the PDCP header, and the concatenation of the PDCP header with the SDAP header are performed on the data portion other than the SDAP header. This interruption occurs because the SDAP header is generated before the integrity protection and encryption processes are performed.

[0239] Therefore, this disclosure describes a method for implementing an SDAP header that is not subjected to integrity protection and encryption, and for implementing an entity by unifying the SDAP entity and the PDCP entity. Specifically, when receiving data from the upper application layer, whenever data is received, ROHC 2q-10 can be continuously and repeatedly performed on the upper-layer header portion (e.g., IP packet header) of the received PDCP SDU. Then, as shown in 2q-20, an integrity protection process can be performed on the PDCP SDU with applied header compression, MAC-I can be calculated (2q-25), and then MAC-I can be concatenated to the end of the data (2q-30). An encryption process can be performed on MAC-I and the integrity-protected data (2q-35). The PDCP header and SDAP header can be generated simultaneously (2q-40) and then concatenated to the integrity-protected and encrypted data, after which the data can be transmitted to the lower layer. The generation of the PDCP header and SDAP header can be processed in parallel with the integrity protection process or the encryption process. In this respect, when generating headers in parallel, SDAP, PDCP, RLC, or MAC headers can be generated together, and these headers can be concatenated at once to the beginning of data that has already undergone complete data processing and is ready for transmission (the MAC PDU configuration may be ready). MAC-I can be concatenated to the end of data that has already undergone complete data processing. Furthermore, the receiving end can separate and read the SDAP, PDCP, RLC, or MAC headers from the data at once, identify the information corresponding to each layer, and process the data in the reverse order of the data processing performed by the sending end. Therefore, the HW accelerator can be applied continuously and repeatedly, and since there are no interruptions such as SDAP header generation between them, the efficiency of data processing can be improved. Additionally, when integrity protection is configured, the HW accelerator can be applied to integrity protection as described regarding the encryption process before performing the encryption process, thus allowing integrity protection to be performed repeatedly. That is, integrity protection can be performed, and then the encryption process can be performed.

[0240] The receiving end's PDCP entity can be implemented as a single entity using a unified SDAP entity and PDCP entity, as described in 2q-01. That is, when data is received from the lower layer (RLC layer), if the RRC message is configured to use the SDAP entity's functionality or uses the SDAP header, as shown in [example code]. Figure 2EThe RRC message shown (see 2e-10, 2e-40, or 2e-75) allows one entity in the SDAP and PDAP entities to read and remove the PDCP and SDAP headers at once, and the decryption or decryption process can be repeatedly applied to the data. Additionally, when integrity protection is configured, after performing the decryption process, the HW accelerator can be applied to integrity verification as described regarding the decryption process, thus allowing integrity verification to be performed repeatedly. That is, the decryption process can be performed, and then integrity verification can be performed. When integrity verification is complete, the ROHC decompression process can be performed on the upper-layer header (e.g., IP packet header), and the reconstructed upper-layer data can be transmitted to the upper layer.

[0241] Figure 2R The present disclosure illustrates an embodiment in which an SDAP entity generates an SDAP header for data received from an upper layer, and a PDCP entity performs header compression (i.e., ROHC), without performing integrity protection and encryption on the SDAP header, and without performing encryption on the MAC-I.

[0242] exist Figure 2R In the case of an RRC message being configured to use SDAP entity functions or use SDAP headers, configured to perform integrity protection and integrity verification, and configured to perform ROHC on the uplink or downlink, the RRC message will behave as follows: Figure 2EAs shown (see 2e-10, 2e-40, or 2e-75), when the SDAP entity receives data from the upper layer, it can generate and configure the SDAP header as described in 2r-05, and can transmit the SDAP header to the PDCP entity. The PDCP entity performs ROHC 2r-10 on the upper-layer header (e.g., IP packet header) of the received PDCP SDU. When integrity protection is configured, the PDCP entity can perform integrity protection 2r-20 on only the data (IP packets) of the PDCP SDU (SDAP header and IP packets 2r-15) received from the upper-layer SDAP entity, and ROHC is applied to the data, and MAC-I can be calculated. When MAC-I 2r-30 is calculated, the PDCPCOUNT value, uplink or downlink indicator, bearer indicator, security key, and the data portion (with integrity protection applied) 2r-25 can be input values ​​for the integrity protection algorithm. As shown in 2r-35, the calculated MAC-I can be concatenated to the end of the data. The MAC-I can have a certain size, such as 4 bytes (or 4 bits). The PDCP entity can perform encryption on 2r-40 (excluding the SDAP header) and the portion excluding the MAC-I (2r-45), can generate and configure the PDCP header and concatenate it to the data (2r-50), and can transmit the data to the lower layer. Then, the RLC entity and the MAC entity can perform data processing. A feature of embodiments of this disclosure is that the MAC-I is also encrypted. When the MAC-I is not encrypted, the advantages in data processing can be further obtained as described below.

[0243] As described above, in addition to the SDAP header of the PDCP SDU received from the upper layer, the PDCP entity can apply only the ROHC to the upper-layer header of the SDAP entity (e.g., IP packet header). The PDCP SDU may include the SDAP header, the upper-layer header of the SDAP entity (e.g., IP packet header), and the upper-layer data of the SDAP entity (IP packet data). In this way, because the ROHC is not applied to the SDAP header, the degree of freedom in base station implementation can be increased, and the processing complexity of the UE can be reduced.

[0244] The receiving end removes the MAC and RLC headers and transmits the data to the PDCP layer. The receiving end's PDCP entity reads and removes the PDCP and SDAP headers, and decrypts the data portion (excluding the SDAP header and the MAC-I at the end). In this respect, the MAC-I is not decrypted. Afterward, the receiving end's PDCP entity performs integrity verification on the upper-layer headers (TCP / IP header) and the data portion (excluding the SDAP header), and calculates the calculated MAC-I (X-MAC). When the X-MAC is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and the data portion (which has undergone integrity protection) can be input values ​​for the integrity protection algorithm. The receiving end's PDCP entity checks whether the X-MAC value is equal to the MAC-I value concatenated to the end of the data. Integrity verification succeeds when the two values ​​are equal, but fails when the values ​​of X-MAC and MAC-I are unequal. Therefore, the receiving PDCP entity discards the data and must report the integrity verification failure to the upper layer (e.g., the RRC layer). Once integrity verification is complete, the ROHC decompression process can be performed on the upper-layer header (e.g., the IP packet header), and the reconstructed upper-layer data can be transmitted to the upper layer.

[0245] In this way, when no encryption or integrity protection is performed on the SDAP header, the configuration of the base station implementation can be simplified, especially in a separate CU-DU structure. When the CU does not encrypt the SDAP header, the DU can check the QoS information by reading the SDAP header and apply the QoS information to scheduling, thus matching and adjusting QoS may be advantageous. Moreover, the aforementioned features can have advantages in data processing in the configuration of the UE and the base station. When the MAC-I is not encrypted as described above, the advantages in data processing can be further obtained as follows.

[0246] Furthermore, as mentioned above, not performing ROHC on the SDAP header simplifies the configuration of the base station implementation, especially in a separate CU-DU structure. When the CU does not encrypt the SDAP header, the DU can check QoS information by reading the SDAP header and apply the QoS information to scheduling, thus matching and adjusting QoS may be advantageous. Moreover, the aforementioned features can offer advantages in data processing during UE and base station configuration.

[0247] Figure 2S The embodiments of the present disclosure illustrate the advantages of processing that can be obtained from the base station and UE by applying SDAP headers that are not encrypted and protected for integrity, by applying ROHC, and by implementing MAC-I encryption.

[0248] exist Figure 2S In the implementation of UE and base station, the SDAP entity and PDCP entity can be unified into a single entity (2s-01). Logically, the SDAP entity is the upper-layer entity of the PDCP entity. Therefore, when receiving data 2s-01 from the upper application layer, if the RRC message is configured to use the SDAP entity's functionality or uses the SDAP header and is configured with integrity protection, and if... Figure 2E In the RRC message shown (see 2e-10, 2e-40, or 2e-75), when configured to perform ROHC on the uplink or downlink, the SDAP entity receives data from the upper layer, as follows: Figure 2J In 2j-05, the SDAP entity must generate and configure the SDAP header. However, the encryption or integrity protection process is a highly complex operation in the implementation of the UE and base station, which can be performed by applying an HW accelerator. The HW accelerator gains a high advantage in processing repetitive and continuous processes. However, when the SDAP entity configures the SDAP header and is configured to perform integrity protection whenever the SDAP entity receives data from an upper-layer entity, the HW accelerator may be interrupted when the integrity protection and encryption processes, the generation of the PDCP header, and the concatenation of the PDCP header with the SDAP header are performed on the data portion other than the SDAP header. This interruption may occur because the SDAP header is generated before the integrity protection and encryption processes are performed.

[0249] Therefore, this disclosure describes a method for implementing an SDAP header without integrity protection and encryption, implementing an unencrypted MAC-I, and implementing an entity through a unified SDAP entity and PDCP entity. Specifically, when receiving data from the upper application layer (2s-05), each time data is received, ROHC (2s-10) can be continuously and repeatedly performed on the upper-layer header portion of the received PDCP SDU (e.g., IP packet header), an integrity protection process can be performed (2s-15), MAC-I can be calculated on the data (2s-20) (2s-25 and 2s-30), and an encryption process (2s-40) can be performed on the data with applied integrity protection (2s-35). The PDCP header, SDAP header, and MAC-I can be generated simultaneously and then concatenated to the data with integrity protection and encryption, after which the data can be transmitted to the lower layer (2s-45). In other words, the generated header can be concatenated to the beginning of the data, and the MAC-I can be concatenated to the end of the data. The generation of PDCP headers, SDAP headers, and MAC-I can be processed in parallel with the integrity protection or encryption processes. In this respect, when generating headers in parallel, SDAP, PDCP, RLC, or MAC headers can be generated together, and these headers can be concatenated at once to the beginning of data that has already undergone complete data processing and is ready for transmission (the MAC PDU configuration may be ready). MAC-I can be concatenated to the end of data that has already undergone complete data processing. Furthermore, the receiving end can separate and read the SDAP, PDCP, RLC, or MAC headers from the data at once, identify the information corresponding to each layer, and process the data in the reverse order of the data processing performed by the sending end. Therefore, the HW accelerator can be applied continuously and repeatedly, and data processing efficiency can be improved because there are no interruptions such as SDAP header generation between them. Additionally, when integrity protection is configured, the HW accelerator can be applied to integrity protection as described regarding the encryption process before performing the encryption process, thus allowing integrity protection to be performed repeatedly. That is, integrity protection can be performed, and then the encryption process can be performed.

[0250] The receiving end's PDCP entity can be implemented as a single entity using a unified SDAP entity and PDCP entity, as described in 2l-01. That is, when data is received from the lower layer (RLC layer), if the RRC message is configured to use the SDAP entity's functionality or uses the SDAP header, as shown... Figure 2EThe RRC message shown (see 2e-10, 2e-40, or 2e-75) allows one entity in the SDAP and PDAP entities to read and remove both the PDCP and SDAP headers at once, and the process of applying neither encryption nor decryption to the data can be repeated. Additionally, when integrity protection is configured, after performing the decryption process, the HW accelerator can be applied to integrity verification as described regarding the decryption process, thus allowing integrity verification to be performed repeatedly. That is, the decryption process can be performed, followed by integrity verification. When integrity verification is complete, the ROHC decompression process can be performed on the upper-layer headers (e.g., IP packet headers), and the reconstructed upper-layer data can be transmitted to the upper layer.

[0251] Figure 2T The present disclosure illustrates an embodiment in which an SDAP entity generates an SDAP header for data received from an upper layer, and a PDCP entity performs UDC, applies integrity protection to the UDC header, performs encryption on the UDC header, applies integrity protection to the SDAP header, and does not perform encryption on the SDAP header.

[0252] exist Figure 2T In the case of an RRC message being configured to use the functionality of an SDAP entity or use an SDAP header, being configured to perform integrity protection and integrity verification, or being configured to perform UDC on the uplink or downlink, such as... Figure 2EAs shown in the RRC message (see 2e-10, 2e-40, or 2e-75), when the SDAP entity receives data from the upper layer, the SDAP entity can generate and configure the SDAP header as in 2t-05, and can transmit the SDAP header to the PDCP entity. The PDCP entity performs UDC (2t-10) on a portion of the received PDCP SDU except for the SDAP header (e.g., the IP datagram header). The PDCP entity can then calculate the checksum field based on the current UDC buffer 2t-15, configure the UDC header, and concatenate the UDC header to the beginning of the SDAP header, as shown in 2t-20. When integrity protection is configured, the PDCP entity can perform integrity protection 2t-25 on 2t-20 (including the UDC header, SDAP header, and UDC block) received from the upper-layer SDAP entity, with UDC applied and concatenated with the UDC header, and can calculate MAC-I (2t-35) from the data 2t-30. When the MAC-I is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and (integrity-protected) data portion can be input values ​​for the integrity protection algorithm. As shown in 2t-40, the calculated MAC-I can be concatenated to the end of the data. The MAC-I can have a certain size, such as 4 bytes. In addition to the SDAP header, the PDCP entity can perform encryption on the concatenated MAC-I in 2t-40 (2t-45), generate and configure the PDCP header and concatenate it to the data (2t-50), and transmit the data to the lower layer. Then, the RLC and MAC entities can perform data processing.

[0253] The receiving end removes the MAC and RLC headers, then transmits the data to the PDCP layer. The receiving end's PDCP entity reads and removes the PDCP header, and decrypts the data portion (excluding the SDAP header). Afterward, the receiving end's PDCP entity performs integrity verification on the SDAP header, upper-layer header (TCP / IP header), and data portion, and calculates the X-MAC. When the X-MAC is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and the data portion (which has undergone integrity protection) can be input values ​​for the integrity protection algorithm. The receiving end's PDCP entity checks if the X-MAC value is equal to the MAC-I value concatenated to the end of the data. When the two values ​​are equal, integrity verification succeeds; however, when the X-MAC and MAC-I values ​​are not equal, integrity verification fails. Therefore, the receiving end's PDCP entity discards the data and must report the integrity verification failure to the upper layer (e.g., the RRC layer). Once integrity verification is complete, you can check for checksum failure by reading the UDC header from the upper-layer data, perform the UDC decompression process, and transmit the reconstructed upper-layer data to the upper layer.

[0254] Figure 2U The present invention illustrates an embodiment of the present disclosure in which an SDAP entity generates an SDAP header for data received from an upper layer, and a PDCP entity performs UDC, applies integrity protection to the UDC header, does not encrypt the UDC header, applies integrity protection to the SDAP header, and does not encrypt the SDAP header.

[0255] exist Figure 2U In the case of an RRC message being configured to use the functionality of an SDAP entity or use an SDAP header, being configured to perform integrity protection and integrity verification, or being configured to perform UDC on the uplink or downlink, such as... Figure 2EAs shown in the RRC message (see 2e-10, 2e-40, or 2e-75), when the SDAP entity receives data from the upper layer, the SDAP entity can generate and configure the SDAP header as in 2u-05, and can transmit the SDAP header to the PDCP entity. The PDCP entity performs UDC (2u-10) on a portion of the received PDCP SDU except for the SDAP header (e.g., the IP datagram header). The PDCP entity can then calculate the checksum field 2u-15 based on the current UDC buffer, configure the UDC header, and concatenate the UDC header to the beginning of the SDAP header, as shown in 2u-20. When integrity protection is configured, the PDCP entity can perform integrity protection 2u-25 on 2u-20 (including the UDC header, SDAP header, and UDC block) received from the upper-layer SDAP entity, with UDC applied and concatenated with the UDC header, and can calculate MAC-I (2u-35) on data 2u-30. When the MAC-I is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and (integrity-protected) data portion can be input values ​​for the integrity protection algorithm. As shown in 2u-40, the calculated MAC-I can be concatenated to the end of the data. The MAC-I can have a certain size, such as 4 bytes. In addition to the UDC header and SDAP header, the PDCP entity can perform encryption on the 2u-40 concatenated with the MAC-I (2u-45), generate and configure the PDCP header and concatenate it to the data (2u-50), and transmit the data to the lower layer. Then, the RLC entity and MAC entity can perform data processing.

[0256] The receiving end removes the MAC and RLC headers, then transmits the data to the PDCP layer. The receiving end's PDCP entity reads and removes the PDCP header, and decrypts the data portion (excluding the SDAP header). Afterward, the receiving end's PDCP entity performs integrity verification on the SDAP header, upper-layer header (TCP / IP header), and data portion, and calculates the X-MAC. When the X-MAC is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and the data portion (which has undergone integrity protection) can be input values ​​for the integrity protection algorithm. The receiving end's PDCP entity checks if the X-MAC value is equal to the MAC-I value concatenated to the end of the data. When the two values ​​are equal, integrity verification succeeds; however, when the X-MAC and MAC-I values ​​are not equal, integrity verification fails. Therefore, the receiving end's PDCP entity discards the data and must report the integrity verification failure to the upper layer (e.g., the RRC layer). Once integrity verification is complete, you can check for checksum failure by reading the UDC header from the upper-layer data, perform the UDC decompression process, and transmit the reconstructed upper-layer data to the upper layer.

[0257] Figure 2V The present invention illustrates an embodiment of the present disclosure in which an SDAP entity generates an SDAP header for data received from an upper layer, and a PDCP entity performs a UDC, does not apply integrity protection to the UDC header, does not encrypt the UDC header, encrypts the MAC-I, does not apply integrity protection to the SDAP header, and does not encrypt the SDAP header.

[0258] exist Figure 2V In the case of an RRC message being configured to use the functionality of an SDAP entity or use an SDAP header, being configured to perform integrity protection and integrity verification, or being configured to perform UDC on the uplink or downlink, such as... Figure 2EAs shown in the RRC message (see 2e-10, 2e-40, or 2e-75), when the SDAP entity receives data from the upper layer, the SDAP entity can generate and configure the SDAP header as in 2v-05, and can transmit the SDAP header to the PDCP entity. The PDCP entity performs UDC (2v-10) on a portion of the received PDCP SDU except for the SDAP header (e.g., the IP datagram header). The PDCP entity can then calculate the checksum field 2v-15 based on the current UDC buffer, configure the UDC header, and concatenate the UDC header to the beginning of the SDAP header, as shown in 2v-20. When integrity protection is configured, the PDCP entity can perform integrity protection 2v-25 on 2v-20 (including the UDC header, SDAP header, and UDC block) received from the upper-layer SDAP entity, with UDC applied and concatenated with the UDC header, and can calculate MAC-I (2v-35) from data 2v-30. When the MAC-I is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and the data portion (which has undergone integrity protection) can be input values ​​for the integrity protection algorithm. As shown in 2v-40, the calculated MAC-I can be concatenated to the end of the data. The MAC-I can have a certain size, such as 4 bytes. In addition to the UDC header and SDAP header, the PDCP entity can perform encryption on the 2v-40 concatenated with the MAC-I (2v-45), generate and configure the PDCP header and concatenate it to the data (2v-50), and transmit the data to the lower layer. Then, the RLC entity and MAC entity can perform data processing.

[0259] The receiving end removes the MAC and RLC headers, then transmits the data to the PDCP layer. The receiving end's PDCP entity reads and removes the PDCP header, and decrypts the data portion (excluding the SDAP header). Afterward, the receiving end's PDCP entity performs integrity verification on the SDAP header, upper-layer header (TCP / IP header), and data portion, and calculates the X-MAC. When the X-MAC is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and the data portion (which has undergone integrity protection) can be input values ​​for the integrity protection algorithm. The receiving end's PDCP entity checks if the X-MAC value is equal to the MAC-I value concatenated to the end of the data. When the two values ​​are equal, integrity verification succeeds; however, when the X-MAC and MAC-I values ​​are not equal, integrity verification fails. Therefore, the receiving end's PDCP entity discards the data and must report the integrity verification failure to the upper layer (e.g., the RRC layer). Once integrity verification is complete, you can check if a checksum failure has occurred by reading the UDC header, perform UDC decompression on the upper-layer data, and transmit the reconstructed upper-layer data to the upper layer.

[0260] Figure 2W This illustrates the advantages of processing obtained by the base station and UE from embodiments of the present disclosure, which can be achieved by applying SDAP and UDC headers that are not subject to encryption and integrity protection.

[0261] exist Figure 2W In the implementation of UE and base station, the SDAP entity and PDCP entity can be unified into a single entity (2w-01). This is because logically, the SDAP entity is the upper-layer entity of the PDCP entity. Therefore, when receiving data 2w-05 from the upper application layer, if the RRC message is configured to use the SDAP entity's functionality or uses the SDAP header and is configured with integrity protection, and if... Figure 2E In the RRC message shown (see 2e-10, 2e-40, or 2e-75), when the SDAP entity receives data from the upper layer, if the use of UDC is configured for uplink or downlink, as shown in the example, Figure 2JIn 2j-05, the SDAP entity must generate and configure the SDAP header. However, the encryption or integrity protection process is a highly complex operation in the implementation of the UE and base station, which can be performed by applying an HW accelerator. The HW accelerator gains a high advantage in processing repetitive and continuous processes. However, when the SDAP entity configures the SDAP header and is configured to perform integrity protection and UDC whenever the SDAP entity receives data from the upper-layer entity, the following processes may be executed: performing the UDC process, generating and concatenating the UDC header, performing integrity protection and encryption processes on the data portion other than the SDAP and UDC headers, generating the PDCP header, and concatenating the PDCP header with the SDAP header. This can lead to interruptions to the HW accelerator due to the operation of generating the UDC and SDAP headers before performing the integrity protection and encryption processes.

[0262] Therefore, this disclosure describes a method for implementing an SDAP header that is not subjected to integrity protection and encryption, and for implementing an entity through a unified SDAP entity and PDCP entity. Specifically, when receiving data from the upper application layer, each time data is received, UDC (2w-10) can be continuously and repeatedly performed on the upper-layer header portion (e.g., IP packet header) of the received PDCP SDU, generating 2w-15. Then, as shown in 2w-20, an integrity protection process (2w-25) can be performed on the PDCP SDU with applied header compression, MAC-I (2w-35) can be calculated and then concatenated to the end of the data (2w-30), an encryption process (2w-45) can be performed on the MAC-I and the data with applied integrity protection (2w-40), the PDCP header, SDAP header, and MAC-I can be generated simultaneously (2w-50), and then concatenated to the data with integrity protection and encryption performed, after which the data can be transmitted to the lower layer. The generation of PDCP, UDC, and SDAP headers can be processed in parallel with the integrity protection or encryption processes. In this respect, when generating headers in parallel, SDAP, PDCP, UDC, RLC, or MAC headers can be generated together, and these headers can be concatenated at once at the beginning of data that has already undergone complete data processing and is ready for transmission (MAC PDU configuration may be ready). Furthermore, the receiving end can separate and read the SDAP, PDCP, UDC, RLC, or MAC headers from the data at once, identify the information corresponding to each layer, and process the data in the reverse order of the data processing performed by the sending end. Therefore, the HW accelerator can be applied continuously and repeatedly, and data processing efficiency can be improved because there are no interruptions such as the generation of UDC and SDAP headers between them. Additionally, when integrity protection is configured, the HW accelerator can be applied to integrity protection as described regarding the encryption process before performing the encryption process, thus allowing integrity protection to be performed repeatedly. That is, integrity protection can be performed, and then the encryption process can be performed.

[0263] The receiving end's PDCP entity can be implemented as a single entity using a unified SDAP entity and PDCP entity, as described in 2w-01. That is, when data is received from the lower layer (RLC layer), if the RRC message is configured to use the SDAP entity's functionality or uses the SDAP header, as shown in [example code]. Figure 2EThe RRC messages shown (see 2e-10, 2e-40, or 2e-75) allow one entity in the SDAP and PDAP entities to read and remove the PDCP and SDAP headers at once, and the decryption or decryption process can be repeatedly applied to the data. Additionally, when integrity protection is configured, after performing the decryption process, the HW accelerator can be applied to integrity verification as described regarding the decryption process, thus allowing integrity verification to be performed repeatedly. That is, the decryption process can be performed, followed by integrity verification. When integrity verification is complete, a checksum failure can be checked by reading the UDC header from the upper-layer data, the UDC decompression process can be performed on the upper-layer data, and the reconstructed upper-layer data can be transmitted to the upper layer.

[0264] Figure 2X The present disclosure illustrates an embodiment in which an SDAP entity generates an SDAP header for data received from an upper layer, and a PDCP entity performs UDC, without applying integrity protection to the UDC header, without encrypting the UDC header, without applying integrity protection to the SDAP header, without encrypting the SDAP header, and without encrypting the MAC-I.

[0265] exist Figure 2X In the case of an RRC message being configured to use the functionality of an SDAP entity or use an SDAP header, being configured to perform integrity protection and integrity verification, or being configured to perform UDC on the uplink or downlink, such as... Figure 2EAs shown in the RRC message (see 2e-10, 2e-40, or 2e-75), when the SDAP entity receives data from the upper layer, the SDAP entity can generate and configure the SDAP header as in 2x-05, and can transmit the SDAP header to the PDCP entity. The PDCP entity performs UDC (2x-10) on a portion of the received PDCP SDU except for the SDAP header (e.g., the IP datagram header). The PDCP entity can then calculate the checksum field 2x-15 based on the current UDC buffer, configure the UDC header, and concatenate the UDC header to the beginning of the SDAP header, as shown in 2x-20. When integrity protection is configured, the PDCP entity can perform integrity protection on 2x-25 (including the UDC header, SDAP header, and UDC block) received from the upper-layer SDAP entity, with UDC applied and concatenated with the UDC header, and can calculate MAC-I (2x-30 and 2x-35). When the MAC-I is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and (integrity-protected) data portion can be input values ​​for the integrity protection algorithm. As shown in 2x-40, the calculated MAC-I can be concatenated to the end of the data. The MAC-I can have a certain size, for example, 4 bytes. In addition to the UDC header and SDAP header, the PDCP entity can perform encryption on the 2x-40 concatenated with the MAC-I (2x-40 and 2x-45), generate and configure the PDCP header and concatenate it to the data (2x-50), and transmit the data to the lower layer. Then, the RLC entity and MAC entity can perform data processing. An embodiment of this disclosure is characterized in that the MAC-I is not encrypted. When the MAC-I is not encrypted, the advantages in data processing can be further obtained as described below.

[0266] The receiving end removes the MAC and RLC headers, then transmits the data to the PDCP layer. The receiving end's PDCP entity reads and removes the PDCP header, and decrypts the data portion (excluding the UDC header, SDAP header, and the MAC-I at the end). For this purpose, MAC-I decryption is not performed. Afterward, the receiving end's PDCP entity performs integrity verification on the upper-layer headers (TCP / IP header) and the data portion (excluding the UDC and SDAP headers), and calculates the X-MAC. When the X-MAC is calculated, the PDCP COUNT value, uplink or downlink indicator, bearer indicator, security key, and the (integrity-protected) data portion can be input values ​​for the integrity protection algorithm. The receiving end's PDCP entity checks whether the X-MAC value is equal to the MAC-I value concatenated to the end of the data. Integrity verification succeeds when the two values ​​are equal, but fails when the values ​​of X-MAC and MAC-I are unequal. Therefore, the PDCP entity at the receiving end discards the data and must report the integrity verification failure to the upper layer (e.g., the RRC layer). When integrity verification is complete, a checksum failure can be checked by reading the UDC header, a UDC decompression process can be performed on the upper-layer data, and the reconstructed upper-layer data can be transmitted to the upper layer.

[0267] In this way, when encryption or integrity protection is not performed on the UDC header and SDAP header, the configuration of the base station implementation can be simplified, especially in a separate CU-DU structure. When the CU does not encrypt the SDAP header, the DU can check the QoS information by reading the SDAP header and apply the QoS information to scheduling, thus matching and adjusting QoS may be advantageous. Moreover, the aforementioned features can have advantages in data processing in the configuration of the UE and the base station. Furthermore, when MAC-I is not encrypted, the advantages in data processing can be further obtained as described below.

[0268] Figure 2Y The embodiments shown in this disclosure demonstrate the advantages of processing obtained by the base station and UE through the application of SDAP headers and UDC headers that are not subject to encryption and integrity protection, through the implementation of UDC, and through unencrypted MAC-I.

[0269] exist Figure 2Y In the implementation of UE and base station, the SDAP entity and PDCP entity can be unified into a single entity (2y-01). This is because logically, the SDAP entity is the upper-layer entity of the PDCP entity. Therefore, when receiving data 2s-01 from the upper application layer, if the RRC message is configured to use the SDAP entity's functionality or uses the SDAP header and is configured with integrity protection, and if... Figure 2EWhen the RRC message shown (see 2e-10, 2e-40, or 2e-75) is configured to perform UDC on the uplink or downlink, and the SDAP entity receives data from the upper layer, as follows: Figure 2J In 2j-05, the SDAP entity must generate and configure the SDAP header. However, the encryption or integrity protection process is a highly complex operation in the implementation of the UE and base station, which can be performed by applying an HW accelerator. The HW accelerator gains a high advantage in processing repetitive and continuous processes. However, when the SDAP entity configures the SDAP header and is configured to perform integrity protection and UDC whenever the SDAP entity receives data from the upper-layer entity, the following processes may be executed: performing the UDC process, generating and concatenating the UDC header, performing integrity protection and encryption processes on the data portion other than the SDAP and UDC headers, generating the PDCP header, and concatenating the PDCP header with the SDAP header. This can lead to interruptions to the HW accelerator due to the operation of generating the UDC and SDAP headers before performing the integrity protection and encryption processes.

[0270] Therefore, this disclosure describes a method for implementing UDC and SDAP headers without integrity protection and encryption, implementing an unencrypted MAC-I, and implementing an entity through a unified SDAP entity and PDCP entity. Specifically, when receiving data from the upper application layer (2y-05), each time data is received, UDC (2y-10) can be continuously and repeatedly performed on the upper-layer header portion (e.g., IP packet header) of the received PDCP SDU; an integrity protection process (2y-25) can be performed on data (2y-15); a MAC-I (2y-35 and 2y-45) can be calculated on data (2y-20); and an encryption process can be performed on data (2y-30) with applied integrity protection. The PDCP header, SDAP header, and MAC-I can be generated simultaneously and then concatenated to the data with integrity protection and encryption. Data (2y-40) can then be transmitted to the lower layer (2y-50). In other words, the generated header can be concatenated to the beginning of the data, and the MAC-I can be concatenated to the end of the data. The generation of PDCP headers, SDAP headers, and MAC-I can be processed in parallel with integrity protection or encryption processes. In this respect, when generating headers in parallel, SDAP, PDCP, UDC, RLC, or MAC headers can be generated together and concatenated at the beginning of data that has undergone complete data processing and is ready for transmission (the MAC PDU configuration may be ready). MAC-I can be concatenated at the end of data that has undergone complete data processing. Furthermore, the receiving end can separate and read the SDAP, PDCP, UDC, RLC, or MAC headers from the data at once, identifying the information corresponding to each layer, and processing the data in the reverse order of the data processing performed by the sending end. Therefore, the HW accelerator can be applied continuously and repeatedly, and data processing efficiency can be improved because there are no interruptions such as the generation of UDC and SDAP headers between them. Additionally, when integrity protection is configured, the HW accelerator can be applied to integrity protection as described regarding the encryption process before the encryption process is executed, thus allowing integrity protection to be performed repeatedly. That is, integrity protection can be performed, and then the encryption process can be performed.

[0271] The receiving end's PDCP entity can be implemented as a single entity using a unified SDAP entity and PDCP entity, as described in 2l-01. That is, when data is received from the lower layer (RLC layer), if the RRC message is configured to use the SDAP entity's functionality or uses the SDAP header, as shown... Figure 2EThe RRC message shown (see 2e-10, 2e-40, or 2e-75) allows one entity in the SDAP and PDAP entities to read and remove the PDCP header, UDC header, and SDAP header at once, and to repeatedly apply decryption or ciphertext to the data. Additionally, when integrity verification is complete, a checksum failure can be checked by reading the UDC header, a UDC decompression process can be performed on the upper-layer data, and the reconstructed upper-layer data can be transmitted to the upper layer. That is, the header of the received data can be read and removed, the MAC-1 at the end of the data can be read and removed, decryption can be performed on the data portion, and integrity verification can be performed. When integrity verification is complete, a UDC decompression process can be performed on the upper-layer header (e.g., IP packet header), and the reconstructed upper-layer data can be transmitted to the upper layer.

[0272] Figure 2Z The present disclosure illustrates the operation of a logical channel, bearer, or SDAP / PDCP entity transmitting and receiving SDAP / PDCP entities configured with integrity protection when an SDAP header without integrity protection and encryption is applied to an SDAP / PDCP entity.

[0273] exist Figure 2ZIn the context of UE and base station implementation, the SDAP entity and PDCP entity can be unified into a single entity (2z-01). This disclosure provides a method for cases where integrity protection is configured. This method is used to implement an SDAP header that is not encrypted and to implement a single entity by unifying the SDAP and PDCP entities. That is, when receiving data from the upper application layer (2z-05), integrity protection can be applied to the data each time data is received (2z-10), the encryption process can be executed continuously and repeatedly (2z-15), the PDCP header and SDAP header can be executed simultaneously (2z-20), the PDCP header and SDAP header can be concatenated to the encrypted data, and the encrypted data can be transmitted to the lower layer. The generation of the PDCP header and SDAP header can be processed in parallel with the integrity protection process or the encryption process. In this respect, when generating headers in parallel, SDAP, PDCP, UDC, RLC, or MAC headers can be generated together, and these headers can be concatenated at once at the beginning of data that has already undergone complete data processing and is ready for transmission (the MAC PDU configuration may be ready). Furthermore, the receiving end can separate and read the SDAP, PDCP, UDC, RLC, or MAC headers from the data at once, identifying the information corresponding to each layer, and processing the data in the reverse order of the data processing performed at the sending end. Therefore, the HW accelerator can be applied continuously and repeatedly, and since there are no interruptions such as SDAP header generation between them, data processing efficiency can be improved. The HW accelerator can be applied to the UDC process.

[0274] The receiving end's PDCP entity 2z-02 can apply the method to situations where integrity protection is configured. This method is used to implement a single entity by unifying the SDAP entity and the PDCP entity. That is, when data is received from the lower layer (RLC layer) (2z-25), and when configured to use the SDAP entity's functionality or SDAP header in the RRC message, such as... Figure 2E The RRC message shown (see 2e-10, 2e-40 or 2e-75) allows one entity in the SDAP and PDAP entities to read and remove the PDCP header and SDAP header at once (2z-30), and to repeatedly apply the decryption process to the data (2z-35), to repeatedly apply the integrity verification process to the data, and to transmit the data to the upper layer (2z-40).

[0275] Figure 2AA The configuration of a UE according to an embodiment of the present disclosure is shown.

[0276] refer to Figure 2AAThe UE includes a radio frequency (RF) processor 2aa-10, a baseband processor 2aa-20, a storage device 2aa-30, and a controller 2aa-40.

[0277] RF processor 2aa-10 performs functions including signal frequency band conversion and amplification to transmit and receive signals via a wireless channel. Specifically, RF processor 2aa-10 up-converts the baseband signal provided by baseband processor 2aa-20 to an RF band signal, receives the RF band signal via an antenna, and down-converts the received RF band signal back to a baseband signal. For example, RF processor 2aa-10 may include a transmit filter, receive filter, amplifier, mixer, oscillator, digital-to-analog converter (DAC), analog-to-digital converter (ADC), etc. Although... Figure 2AA Only one antenna is shown, but the UE may include multiple antennas. Furthermore, the RF processor 2aa-10 may include multiple RF chains. Additionally, the RF processor 2aa-10 can perform beamforming. For beamforming, the RF processor 2aa-10 can adjust the phase and amplitude of individual signals transmitted and received via multiple antennas or antenna elements. Moreover, the RF processor 2aa-10 can perform massive MIMO and can receive signals from multiple layers simultaneously while performing MIMO operation. The RF processor 2aa-10 can perform receive beam scanning by appropriately configuring multiple antennas or antenna elements under the control of the controller 2aa-40, or it can adjust the direction and width of the receive beam to coordinate the receive beam with the transmit beam.

[0278] The baseband processor 2aa-20 performs the conversion function between baseband signals and bit strings according to the system's physical layer specifications. For example, in data transmission, the baseband processor 2aa-20 generates complex symbols by encoding and modulating the transmitted bit string. Additionally, in data reception, the baseband processor 2aa-20 reconstructs the received bit string by demodulating and decoding the baseband signal provided from the RF processor 2aa-10. For example, when transmitting data according to an OFDM scheme, the baseband processor 2aa-20 generates complex symbols by encoding and modulating the transmitted bit string, maps the complex symbols to subcarriers, and configures the OFDM symbols by performing an inverse fast Fourier transform (IFFT) operation and inserting a cyclic prefix (CP). Furthermore, in data reception, the baseband processor 2aa-20 can divide the baseband signal provided from the RF processor 2aa-10 into OFDM symbol units, recover the signal mapped to the subcarrier by performing a fast Fourier transform (FFT) operation, and then reconstruct the received bit string by demodulating and decoding the signal.

[0279] Baseband processor 2aa-20 and RF processor 2aa-10 transmit and receive signals as described above. Therefore, baseband processor 2aa-20 and RF processor 2aa-10 can be referred to as transmitters, receivers, transceivers, or communicators. Furthermore, at least one of baseband processor 2aa-20 and RF processor 2aa-10 may include multiple communication modules to support different wireless access technologies. Moreover, at least one of baseband processor 2aa-20 and RF processor 2aa-10 may include different communication modules configured to support multiple different wireless access technologies. Furthermore, at least one of baseband processor 2aa-20 and RF processor 2aa-10 may include different communication modules configured to process signals in different frequency bands. For example, different wireless access technologies may include LTE networks, NR networks, etc. Examples of different frequency bands may include ultra-high frequency (SHF) bands (e.g., 2.5 GHz or 5 GHz) and millimeter-wave bands (e.g., 60 GHz).

[0280] Storage device 2aa-30 can store data such as default programs, application programs, and configuration information for UE operation. Storage device 2aa-30 provides the stored data in response to requests from controller 2aa-40.

[0281] Controller 2aa-40 controls the overall operation of the UE. For example, controller 2aa-40 transmits and receives signals via baseband processor 2aa-20 and RF processor 2aa-10. Additionally, controller 2aa-40 records and reads data stored in storage device 2aa-30. For this purpose, controller 2aa-40 may include at least one processor. For example, controller 2aa-40 may include a communication processor (CP) configured to perform communication control and an application processor (AP) configured to control upper-layer applications such as applications. According to embodiments of this disclosure, controller 2aa-40 includes a multi-connection processor 2aa-42 configured to perform processing for operation in a multi-connection mode.

[0282] Figure 2AB The configuration of a base station according to an embodiment of the present disclosure is shown.

[0283] refer to Figure 2AB The base station includes an RF processor 2ab-10, a baseband processor 2ab-20, a communicator 2ab-30, a storage device 2ab-40, and a controller 2ab-50.

[0284] RF processor 2ab-10 performs functions including signal frequency band conversion and amplification to transmit and receive signals via a wireless channel. Specifically, RF processor 2ab-10 up-converts the baseband signal provided by baseband processor 2ab-20 into an RF band signal, receives the RF band signal via an antenna, and down-converts the received RF band signal back into a baseband signal. For example, RF processor 2ab-10 may include a transmit filter, receive filter, amplifier, mixer, oscillator, DAC, ADC, etc. Although... Figure 2AB Only one antenna is shown, but a base station may include multiple antennas. Furthermore, the RF processor 2ab-10 may include multiple RF chains. Additionally, the RF processor 2ab-10 can perform beamforming. For beamforming, the RF processor 2ab-10 can adjust the phase and amplitude of individual signals transmitted and received via multiple antennas or antenna elements. Moreover, the RF processor 2ab-10 can perform sub-MIMO operations by transmitting one or more layers.

[0285] The baseband processor 2ab-20 performs the conversion function between baseband signals and bit strings according to the physical layer specification of the first radio access technology. For example, in data transmission, the baseband processor 2ab-20 generates complex symbols by encoding and modulating the transmitted bit string. Additionally, in data reception, the baseband processor 2ab-20 reconstructs the received bit string by demodulating and decoding the baseband signal provided from the RF processor 2ab-10. For example, when transmitting data according to an OFDM scheme, the baseband processor 2ab-20 generates complex symbols by encoding and modulating the transmitted bit string, maps the complex symbols to subcarriers, and configures the OFDM symbols by performing an IFFT operation and inserting a cyclic prefix (CP). Furthermore, in data reception, the baseband processor 2ab-20 can divide the baseband signal provided from the RF processor 2ab-10 into OFDM symbol units, recover the signal mapped to the subcarriers by performing an FFT operation, and then reconstruct the received bit string by demodulating and decoding the signal. The baseband processor 2ab-20 and the RF processor 2ab-10 transmit and receive signals as described above. Therefore, the baseband processor 2ab-20 and the RF processor 2ab-10 can be referred to as transmitters, receivers, transceivers, communicators, or wireless communicators.

[0286] The communicator 2ab-30 provides an interface for performing communication with other nodes in the network.

[0287] Storage device 2ab-40 stores data such as default programs, application programs, and configuration information for base station operation. Specifically, storage device 2ab-40 can store information about bearers assigned to connected UEs, measurement results reported by connected UEs, etc. Furthermore, storage device 2ab-40 can store information that determines whether to provide or stop multiple connections to the UE. Moreover, storage device 2ab-40 can provide the stored data in response to requests from controller 2ab-50.

[0288] Controller 2ab-50 controls all operations of the base station. For example, controller 2ab-50 transmits and receives signals via baseband processor 2ab-20 and RF processor 2ab-10 or via communicator 2ab-30. Additionally, controller 2ab-50 can record data to / from storage device 2ab-40 and read data from storage device 2ab-40. For this purpose, controller 2ab-50 may include at least one processor. According to embodiments of this disclosure, controller 2ab-50 includes a multi-connection processor 2aa-52 configured to perform processing for operation in a multi-connection mode.

[0289] Figure 3A This is a diagram showing the configuration of an LTE system.

[0290] refer to Figure 3A The wireless communication system consists of multiple base stations (also known as "eNBs") 3a-05, 3a-10, 3a-15, and 3a-20, MME 3a-25, and S-GW 3a-30. User equipment (hereinafter referred to as UE or terminal) 3a-35 accesses the external network via eNBs 3a-05, 3a-10, 3a-15, and 3a-20, as well as S-GW 3a-30.

[0291] eNBs 3a-05, 3a-10, 3a-15, and 3a-20, acting as access nodes in a cellular network, provide radio access to UEs accessing the network. Specifically, to serve user services, eNBs 3a-05, 3a-10, 3a-15, and 3a-20 collect and schedule multiple status information, including the UE's buffer status, available transmission power status, channel status, etc., and then support the connection between the UE and the core network (CN). The MME 3a-25 is configured to perform not only mobility management functions for the UE but also various control functions for the UE and is connected to multiple base stations. The S-GW 3a-30 is configured to provide data bearer functionality. In addition, MME 3a-25 and S-GW 3a-30 can also be configured to perform authentication, bearer management, etc. for UEs accessing the network, and process packets received from eNB 3a-05, 3a-10, 3a-15 and 3a-20, or packets to be sent to eNB 3a-05, 3a-10, 3a-15 and 3a-20.

[0292] Figure 3B This is a diagram illustrating the radio protocol architecture in an LTE system.

[0293] The NR system has a protocol architecture that is very similar to that of the LTE system.

[0294] refer to Figure 3BThe radio protocol in an LTE system consists of PDCP3b-05 and 3b-40, RLC3b-10 and 3b-35, and MAC3b-15 and 3b-30 in the corresponding UE and eNB. PDCP3b-05 and 3b-40 perform operations including IP header compression / decompression, and RLC3b-10 and 3b-35 reconfigure PDCP Packet Data Units (PDCP PDUs) to an appropriate size. MAC3b-15 and 3b-30 connect to multiple RLC layers configured in a UE and can perform operations such as multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. PHY layers 3b-20 and 3b-25 perform channel coding and modulation of upper-layer data and transmission of OFDM symbols over the radio channel by converting upper-layer data into OFDM symbols, or perform demodulation and channel decoding of OFDM symbols received over the radio channel and transmission of the decoded data to the upper layer. To perform additional error correction, PHY layers 3b-20 and 3b-25 use Hybrid Automatic Repeat Request (HARQ or HARQ), and the receiver sends 1 bit indicating an acknowledgment (ACK) or negative acknowledgment (NACK) regarding a packet transmitted from the sender. This is called HARQ ACK / NACK information. Downlink HARQ ACK / NACK information regarding uplink transmissions can be sent via the Physical Hybrid ARQ Indicator Channel (PHICH) physical channel, and uplink HARQ ACK / NACK information regarding downlink transmissions can be sent via the Physical Uplink Control Channel (PUCCH) physical channel or the Physical Uplink Shared Channel (PUSCH) physical channel.

[0295] Despite Figure 3B Although not shown, each Radio Resource Control (RRC) layer exists as an upper layer of the PDCP layers 3b-05 and 3b-40 of the UE and eNB, and the RRC layer can exchange configuration control messages related to access and measurement to control radio resources.

[0296] PHY layer 3b-20 or 3b-25 can include one or more frequencies / carriers, and the technique for simultaneously setting up and using multiple frequencies in a single base station is called carrier aggregation (CA). According to CA, instead of using only one carrier for communication between the UE and the base station (i.e., the E-UTRAN Node B (eNB)), a primary carrier and multiple secondary carriers can be used, thus greatly increasing the transmission capacity by the number of secondary carriers. In LTE and NR systems, the cell served by the base station using the primary carrier is called the primary cell (PCell), and the cell served by the base station using secondary carriers is called the secondary cell (SCell). The technique for extending CA is called dual connectivity (DC). According to DC, the UE simultaneously connects to both the primary base station (i.e., the primary E-UTRAN Node B (MeNB)) and the secondary base station (i.e., the secondary E-UTRAN Node B (SeNB)) to use radio resources, and the cell served by the MeNB is called the primary cell group (MCG), while the cell served by the SeNB is called the secondary cell group (SCG). Each group has a representative cell; in this respect, the representative cell of the MCG is called the primary cell (PCell), and the representative cell of the SCG is called the primary-secondary cell (PSCell). When using NR, the MCG uses LTE technology, while the SCG uses NR; therefore, the UE can use both LTE and NR technologies simultaneously.

[0297] In LTE and NR systems, the UE sends a Power Headroom Report (PHR) to the eNB based on certain conditions. The PHR indicates the difference between the maximum transmit power and the actual transmit power, which is set in the UE and estimated by the UE. The estimated transmit power is calculated based on the values ​​used when the UE transmits the actual uplink (the resulting value is called the real value), but when the UE does not transmit the actual uplink, the estimated transmit power is calculated according to a specific equation defined in the standard rules (the resulting value is called the imaginary value). When the eNB receives the PHR, it can determine the UE's maximum available transmit power. When using CA (Carrier Access), the PHR is sent to each of the multiple secondary carriers.

[0298] Figure 3C This is a diagram used to describe CA in UE.

[0299] refer to Figure 3CIn a base station, multiple carriers are typically transmitted and received across several frequency bands. For example, according to related technologies, when base station 3c-05 transmits carrier 3c-15 at primary frequency f1 and carrier 3c-10 at primary frequency f3, a UE transmits and receives data using one of the two carriers. However, a UE with CA (Carrier Response) functionality can utilize multiple carriers to transmit and receive data simultaneously. Base station 3c-05 can allocate more carriers to UE 3c-30 with CA functionality based on conditions, thereby increasing the transmission rate of UE 3c-30.

[0300] When assuming that a cell typically consists of a forward carrier and a backward carrier transmitted / received from a base station, CA can be understood as the UE simultaneously transmitting and receiving data through multiple cells. By doing so, the maximum transmission rate increases proportionally to the number of aggregated carriers.

[0301] In the following, in this disclosure, the expression "UE receives data via a random forward carrier" or "UE transmits data via a random backward carrier" has the same meaning as "transmits and receives data via a control channel and a data channel provided by a cell corresponding to the main frequency and frequency bandwidth of the specified carrier." Furthermore, in the following, for ease of description, this disclosure will now be described with reference to an LTE system; however, this disclosure can be applied to various wireless communication systems that support CA.

[0302] Even when CA is performed or not, backtransmission (i.e., transmission from the UE to the base station) causes interference with backtransmissions in other cells; therefore, the backtransmission output must be maintained at an appropriate level. To this end, when the UE performs a backtransmission, it calculates the backtransmission output using a specific function and performs the backtransmission based on the calculated output. For example, the UE can calculate the requested backtransmission output value by inputting scheduling information such as the amount of allocated transmission resources, the modulation and coding scheme (MCS) level to be applied, and input values ​​such as path loss values ​​for estimating channel states into the specific function, and perform the backtransmission by applying the calculated value of the requested backtransmission output. The value of the backtransmission output applicable to the UE is limited by the UE's maximum transmission value, and when the requested value of the calculated backtransmission output exceeds the UE's maximum transmission value, the UE performs backtransmission based on the maximum transmission value. In this case, the quality of the backtransmission may degrade because the backtransmission output is insufficient. The base station can perform scheduling to prevent the requested transmission output from exceeding the maximum transmission value. However, there are almost no parameters (including path loss) that cannot be detected by the base station. Therefore, the UE sends a PHR when necessary to report the status of the UE's available transmission output (power margin (PH)) to the base station.

[0303] Factors affecting available transmission output include: 1) the amount of allocated transmission resources; 2) the MCS to be applied to backward transmission; 3) the path loss of the associated forward carrier; and 4) the accumulated value of output adjustment commands, etc. Among these factors, the path loss (hereinafter referred to as PL) or the accumulated value of output adjustment commands can vary depending on the backward carrier. Therefore, when multiple backward carriers are aggregated in a UE, it is reasonable to configure the transmission of a PHR for each of the backward carriers. However, for efficient transmission of PHRs, a backward carrier can report the PHs of multiple backward carriers. According to an operating strategy, PHs can be requested by carriers that do not actually send PUSCHs. Therefore, in this case, it is more efficient for a backward carrier to report all PHs of multiple backward carriers. For this purpose, the existing PHR must be extended. Multiple PHs to be included in a PHR can be configured according to a predetermined order.

[0304] When the PL of the normally connected forward carrier changes to exceed a preset reference value, a PHR is triggered either when the PHR disable timer expires or when a preset time has elapsed since the PHR was generated. Even when a PHR is triggered, the UE will not immediately send the PHR and will remain in standby mode until backward transmission resources are allocated to it. This is because the PHR is not information that should be processed quickly.

[0305] Figure 3D This is a diagram used to describe the concept of multiple connectivity in LTE and NR.

[0306] By using DC technology, the UE can connect to two base stations simultaneously and use radio resources, and Figure 3D The illustration shows a scenario where UE 3d-05 simultaneously connects to macro base station 3d-00 using LTE technology and to small cell base station 3d-10 using NR technology. This is called E-UTRAN-NR dual connectivity (EN-DC). Macro base station 3d-00 is referred to as primary E-UTRAN node B (MeNB) 3d-00, and small cell base station 3d-10 is referred to as secondary 5G node B (SgNB) 3d-10. Multiple small cells can exist within the service coverage area of ​​MeNB 3d-00, and MeNB 3d-00 can connect to multiple SgNB 3d-10s via wired backhaul network 3d-15. The group of serving cells provided by MeNB 3d-00 is referred to as primary cell group (MCG) 3d-20, and one serving cell in MCG 3d-20 is, of course, the primary cell (PCell) 3d-25 with all functions (such as connection establishment, connection reconstruction, handover, etc., previously performed by existing cells). In PCell 3d-25, the uplink control channel has PUCCH. The serving cell other than PCell 3d-25 is referred to as the secondary cell (SCell) 3d-30. Figure 3DThe diagram illustrates a scenario where MeNB 3d-00 provides one SCell 3d-30 and SgNB 3d-10 provides three SCells. The serving cells provided by SgNB 3d-10 are called the secondary cell group (SCG) 3d-40. When UE 3d-05 sends / receives data to / from MeNB 3d-00 and SgNB 3d-10, MeNB 3d-00 issues commands to SgNB 3d-10 to add, change, and remove serving cells provided by SgNB 3d-10. To issue these commands, MeNB 3d-00 can configure UE 3d-05 to measure serving cells and neighboring cells. Based on the configuration information, UE 3d-05 must report the measurement results to MeNB 3d-00. In order for SgNB3d-10 to effectively send and receive data to / from UE3d-05, SgNB 3d-10 requires a serving cell similarly used as PCell 3d-25 of MCG 3d-20, and in this disclosure, the serving cell is referred to as the primary SCell (PSCell) 3d-35. PSCell 3d-35 is set as one of the serving cells of SCG 3d-40 and is characterized by having a PUCCH as an uplink control channel. UE 3d-05 uses the PUCCH to transmit HARQ ACK / NACK information, channel state information (CSI) information, scheduling requests (SR), etc., to the base station.

[0307] This disclosure provides a method for reporting the remaining transmission power (power margin) of a UE to a base station, the method being performed by a UE that simultaneously transmits and receives data using multiple radio access technologies (RATs) in a wireless communication system.

[0308] According to this disclosure, the UE accurately reports the available transmission power to each of the base stations, so that the base stations can correctly perform uplink scheduling.

[0309] Figure 3E A method for transmitting an uplink according to the configuration and type of the uplink, according to an embodiment of the present disclosure, is illustrated.

[0310] exist Figure 3EExample 1 corresponds to the following scenario: Two serving cells, PCell 3e-01 and SCell 3e-03, are configured for the UE, and the UE performs uplink transmissions according to the base station's scheduling. In this scenario, due to limitations in the transmission method and RF structure, the UE cannot simultaneously transmit PUCCH and PUSCH in one serving cell. Therefore, the UE transmits a PUSCH (3e-05) containing embedded PUCCH information. Specifically, the UE transmits PUCCH information in PCell 3e-01, or, if no PUSCH is available in PCell 3e-01, in the SCell with the lowest index. The PHR message is transmitted as part of the PUSCH; therefore, in this scenario, the UE is required to report only the maximum transmission power P from each serving cell. CMAX,c The power margin value obtained by subtracting the transmission power, which is consumed by sending PUSCH (3e-05 and 3e-07), is called Type 1 power margin.

[0311] Similarly, Example 2 corresponds to the following scenario: two serving cells, PCell 3e-11 and SCell 3e-13, are configured for the UE, and the UE performs uplink transmissions according to the base station's scheduling. In this scenario, the UE has the ability to transmit PUCCH and PUSCH simultaneously in a serving cell, or to transmit PUSCH and PUCCH separately using an uplink transmission technique that allows simultaneous transmission in one of these cells. In this regard, in the PCell (or, when PUCCH can be transmitted in the SCell, applied to the SCell), considering the transmission power consumed not only by PUSCH transmission (3e-17) but also by PUCCH transmission (3e-15), the UE is required to report the maximum transmission power P from the PCell. CMAX,c The power margin obtained by subtracting both the PUSCH and PUCCH transmission values. This is called Type 2 power margin.

[0312] When the UE reports Type 1 or Type 2 power headroom, it does so using either a single-entry PHR format 3e-21 or a multi-entry PHR format 3e-31. When dual connectivity is configured, the UE reports power headroom using the multi-entry PHR format 3e-31. In this regard, power headroom is reported as shown in formats such as 3e-41, 3e-51, and 3e-61, and when required, the corresponding P... CMAX,c Values ​​(see 3e-43, 3e-53, and 3e-63). When the UE reports power headroom, it uses a 6-bit field, such as... Figure 3EAs shown, and in LTE, this field has values ​​as shown in the table below. This table is called [Table 2].

[0313] [Table 2]

[0314] Report value Measured mass value (dB) POWER_HEADROOM_0 -23≤PH<-22 POWER_HEADROOM_1 -22≤PH<-21 POWER_HEADROOM_2 -21≤pH<-20 POWER_HEADROOM_3 -20≤PH<-19 POWER_HEADROOM_4 -19≤PH<-18 POWER_HEADROOM_5 -18≤PH<-17 … … POWER_HEADROOM_57 34≤pH<35 POWER_HEADROOM_58 35≤pH<36 POWER_HEADROOM_59 36≤PH<37 POWER_HEADROOM_60 37≤PH<38 POWER_HEADROOM_61 38≤PH<39 POWER_HEADROOM_62 39≤pH<40 POWER_HEADROOM_63 pH≥40

[0315] In NR, the frequency range is roughly specified as the following two frequency ranges based on the frequency coverage area of ​​the base station operation.

[0316] [Table 3]

[0317] Frequency range specification Corresponding frequency range FR1 450MHz–6000MHz FR2 24250MHz–52600MHz

[0318] Base stations operating in FR1 and those operating in FR2 can request significantly different transmission power from the UE to operate in each of the base stations. Therefore, a table different from [Table 2] for LTE can be defined based on the frequency range (i.e., based on each of FR1 and FR2).

[0319] For example, for a PHR report for a base station operating in FR1 in an NR base station, the following [Table 4] can be used (because the FR1 in Table 4 is not significantly different from the frequency range of LTE, for convenience, the same table as [Table 2] for LTE is shown; however, [Table 4] may have different values).

[0320] [Table 4]

[0321] Report value Measured mass value (dB) POWER_HEADROOM_0 -23≤PH<-22 POWER_HEADROOM_1 -22≤PH<-21 POWER_HEADROOM_2 -21≤pH<-20 POWER_HEADROOM_3 -20≤PH<-19 POWER_HEADROOM_4 -19≤PH<-18 POWER_HEADROOM_5 -18≤PH<-17 … … POWER_HEADROOM_57 34≤pH<35 POWER_HEADROOM_58 35≤pH<36 POWER_HEADROOM_59 36≤PH<37 POWER_HEADROOM_60 37≤PH<38 POWER_HEADROOM_61 38≤PH<39 POWER_HEADROOM_62 39≤pH<40 POWER_HEADROOM_63 pH≥40

[0322] As another example, the following [Table 5] can be used for PHR reports for NR base stations operating in FR1.

[0323] [Table 5]

[0324]

[0325]

[0326] Therefore, when the UE reports the PHR for each cell that is currently configured and activated by the base station, even if the UE uses the same PH report field with a multi-entry PHR format according to the RAT and the operating frequency of the corresponding serving cell, the UE generates a value based on a table according to the type of the corresponding serving cell and reports that value to the base station.

[0327] In EN-DC, the LTE base station acting as a MeNB and the NR base station acting as an SgNB may not recognize each other's operating frequencies. This is because the MeNB and SgNB can be designed to operate independently to ensure their independent operation. Therefore, when the UE reports a PHR to the LTE base station acting as a MeNB, the frequency range of the LTE serving cell and its corresponding PHR reporting table are only related to Table 2, and the UE performs the reporting according to Table 2. In the EN-DC case, when the UE reports a PHR, the UE must report the serving cell of the SgNB (i.e., the NR base station). In this respect, the LTE base station receiving the PHR does not know the frequency information of the serving cell of the NR base station; therefore, the UE reports the PHR according to Table 2. For example, when the calculated frequency of the NR serving cell belongs to FR2 and the PH value is 45dB, the UE uses the value of POWER_HEADROOM_58 to report to the NR base station. However, when the UE reports to the LTE base station, the UE uses the value of POWER_HEADROOM_63. When the UE reports a PHR report to the SgNB (i.e., the NR base station), and the PH value is 45dB, the UE reports the exact value by using the value of POWER_HEADROOM_58.

[0328] The scenario of dual connectivity between NR base stations is called NR-DC. Even in this case, the NR base station acting as a MgNB and the NR base station acting as an SgNB may not be able to recognize each other's operating frequencies. This is because the MeNB and SgNB can be designed to operate independently to ensure independent operation between them. In this case, when the UE reports a PHR for a serving cell included in the base stations it is currently reporting to, the UE reports the PHR according to the frequency operating range (FR1 or FR2). However, when the serving cell is not included in the base stations it is currently reporting to (i.e., when reporting a PHR to the MCG for the serving cell of the SCG, or when reporting a PHR to the SCG for the serving cell of the MCG), the UE reports the PHR value to the base station according to Table 4 (i.e., FR1). Alternatively, the UE can notify the base station separately whether the corresponding value is related to Table 4 of FR1 or Table 5 of FR2 by using one of the R bits 3e-39 reserved in the multi-entry PHR format, thus allowing the UE to notify the base station of the precise value.

[0329] Figure 3F The illustration shows a message flow between UE3f-01 and LTE eNB 3f-03, to which the UE reports PHR, while dual connectivity is established between different RATs according to an embodiment of the present disclosure.

[0330] When UE 3f-01 is in an idle state, it scans its surrounding environment and selects an appropriate LTE base station (or cell), namely LTE eNB 3f-03. When UE 3f-01 determines that it wants to access the cell, it sends an access request message (3f-11) to LTE eNB 3f-03 through a random access procedure. By using the aforementioned uplink access technology, the access request message is sent as an RRC layer message.

[0331] Subsequently, UE 3f-01 receives the access configuration message (3f-13) and sends an access configuration completion message (3f-15) as its confirmation message, thereby completing access to LTE eNB 3f-03. When UE 3f-01 receives the access configuration message, UE 3f-01 can transition to a connected state and can send and receive data to / from LTE eNB 3f-03. Then, in order to receive PHR reports for LTE eNB 3f-03 to perform scheduling on UE 3f-01, LTE eNB 3f-03 can configure PHR-related parameters (3f-19) using RRC layer messages. PHR-related parameters may include periodicPHR-Timer, prohibitPHR-Timer, downlink(dl)-PathlossChange, etc. The PeriodicPHR-Timer is a timer configured to periodically report PHR values ​​to the base station, the prohibitPHR-Timer is a timer configured to prevent frequent PHR reports, and the dl-PathlossChange value is a threshold at which a PHR is reported when the change in downlink channel reception is equal to or greater than the threshold value. Connection reconfiguration messages can include configuration information related to the radio bearer used in data transmission, or a separate connection reconfiguration message can be sent again for radio bearer configuration. Additionally, when UE 3f-01 is configured by LTE eNB 3f-03 to measure neighboring NR base stations and subsequently report the results, configuration (3f-17) is performed between LTE eNB 3f-03 and the NR base station, and this information can also be included in the RRC message. This information pertains to additional configurations not only for using LTE eNB 3f-03 but also for using NR gNB 3f-05. That is, information for dual connectivity (EN-DC) configuration can also be included in the RRC message. RRC configuration is based on the RRCConnectionReconfiguration message. UE 3f-01 receives the RRC layer message and sends an acknowledgment message (3f-21) to LTE eNB 3f-03. This acknowledgment message corresponds to the RRCConnectionReconfigurationComplete message.

[0332] When dual connectivity is established based on configuration messages, enabling the simultaneous use of LTE and NR base stations, UE 3f-01 can simultaneously perform data exchange with LTE eNB 3f-03 and NR gNB 3f-05 (3f-25 and 3f-27).

[0333] The conditions for when to send a PHR to the base station (i.e., when to trigger a report) can be defined, and the following conditions can be defined in both LTE and NR systems.

[0334] - When the prohibitPHR-Timer expires, the change in downlink received strength is equal to or greater than the value of dl-PathlossChange dB.

[0335] - When the periodicPHR-Timer expires.

[0336] - When initially configuring PHR reports.

[0337] - When adding a SCell that includes the uplink.

[0338] - When adding a secondary base station PSCell while using dual connectivity technology.

[0339] When the above PHR triggering condition occurs in each of the LTE eNB 3f-03 and NR gNB 3f-05 (3f-31 and 3f-41), UE 3f-01 generates a PHR and reports it to the LTE eNB 3f-03 and NR gNB 3f-05 (3f-33 and 3f-43), respectively.

[0340] When conditions are met in LTE eNB 3f-03 (3f-31), UE 3f-01 includes the type 1 power headroom value for all serving cells currently configured and activated in LTE eNB 3f-03 and NR gNB 3f-05, and reports the PHR to LTE eNB 3f-03 (3f-33). Furthermore, when an actual transmission occurs in LTE eNB 3f-03 or NR gNB 3f-05 at the time of reporting the PHR, it also includes and reports the PHR value for the cell for which it reported the type 1 power headroom. CMAX,c Value. Additionally, in Figure 3F In this context, assuming the LTE base station is a MeNB, when UE 3f-01 is configured to simultaneously transmit PUCCH and PUSCH in the PCell representing the MeNB's cell, UE 3f-01 will also include the Type 2 power margin value of that PCell in the PHR and report the PHR. Additionally, in... Figure 3F In this case, since the base station that reports the PHR is an LTE base station, regardless of whether the cell is the serving cell corresponding to the LTE base station or the serving cell corresponding to the NR base station, UE 3f-01 generates a value according to the aforementioned Table 2 (i.e., the table used when reporting the PHR of LTE) and reports the value to the base station.

[0341] When conditions are met in NR gNB 3f-05 (3f-41), UE 3f-01 includes the type 1 power headroom value for all serving cells currently configured and activated in LTE eNB 3f-03 and NR gNB 3f-05, and reports the PHR to NR gNB 3f-05 (3f-43). Furthermore, when an actual transmission occurs in LTE eNB 3f-03 or NR gNB 3f-05 at the time of PHR reporting, it also includes and reports the PHR value for the cell for which it reported the type 1 power headroom. CMAX,c Value. Additionally, in Figure 3F Since the conditions are met in NR gNB3f-05, it is assumed that the LTE base station is a MeNB, and UE 3f-01 reports the PHR to NR gNB3f-05. Therefore, when UE 3f-01 is configured to simultaneously transmit PUCCH and PUSCH in the PSCell of the representative cell of NR gNB 3f-05 (i.e., SgNB), UE 3f-01 will also include the type 2 power margin value of the PSCell in the PHR and report the PHR. Additionally, UE 3f-01 reports the type 2 power margin of the PCell of the LTE base station, and when UE 3f-01 is configured to report the actual transmission value, UE 3f-01 will include the type 2 power margin of the PCell of the LTE base station in the PHR. CMAX,c The values ​​are included in the report, and the report is sent. Figure 3F In this context, the base station receiving the PHR is an NR base station, assuming that the NR base station understands all tables in Tables 3, 5, and 6. Therefore, when the serving cell corresponds to an LTE base station, UE 3f-01 generates a value according to Table 2 (i.e., the table used when reporting the LTE PHR) and reports this value to the base station. In the case of an NR serving cell, UE 3f-01 reports its remaining transmission power to the base station by referring to Table 4 in the case of FR1 and Table 5 in the case of FR2, depending on the operating frequency range.

[0342] Therefore, when each corresponding condition occurs, the PHR is reported to the corresponding base station, and the base station can determine the current remaining power of the UE and perform appropriate scheduling for the UE.

[0343] Figure 3G This is a diagram illustrating the UE's operation flow when a UE reports a PHR while dual connectivity is established between different RATs according to an embodiment of the present disclosure.

[0344] When the UE is in an idle state, it scans its surrounding environment and selects an appropriate LTE base station (or cell), and attempts to access the LTE base station (3g-03). To do this, the UE sends an RRCConnectionRequest message from the RRC layer to the LTE base station, receives an RRCConnectionSetup message from the LTE base station, sends an RRCConnectionSetupComplete message to the LTE base station, and completes the access process.

[0345] Subsequently, the UE receives an RRC layer configuration message from the LTE base station for reporting the PHR and sends an acknowledgment message (3g-05) to it. The RRC layer configuration message can be an RRCConnectionReconfiguration message, and the acknowledgment message can be an RRCConnectionReconfigurationComplete message. This configuration message can include PHR-related parameters, including periodicPHR-Timer, prohibitPHR-Timer, and dl-PathlossChange. PeriodicPHR-Timer is a timer configured to periodically report the PHR value to the base station; prohibitPHR-Timer is a timer configured to prevent frequent PHR reports; and dl-PathlossChange is a threshold value at which a PHR is reported when the change in downlink channel reception is equal to or greater than this value. The connection reconfiguration message can include configuration information related to the radio bearer used in data transmission, or a separate connection reconfiguration message can be sent again for configuration. Additionally, when the UE is configured by the base station to measure neighboring NR base stations and then report the results, information can also be included in the message that pertains to additional configurations for using not only LTE base stations but also NR base stations. That is, information regarding the configuration for dual connectivity can also be included in the message.

[0346] Subsequently, based on the configured parameters, the UE determines whether to trigger a PHR report (3g-07) for each base station according to the following conditions.

[0347] - When the prohibitPHR-Timer expires, the change in downlink received strength is equal to or greater than the value of dl-PathlossChange dB configured by the base station.

[0348] - When the periodicPHR-Timer configured by the base station for periodic reporting expires.

[0349] - When initially configuring PHR reports.

[0350] - When adding a SCell that includes the uplink.

[0351] - When adding a secondary base station PSCell while using dual connectivity technology.

[0352] When a PHR trigger condition occurs in each of the base stations (3g-07), the UE will determine whether EN-DC is configured and whether the base station where the PHR trigger condition occurred is an LTE base station or an NR base station (3g-09).

[0353] When EN-DC is configured and conditions are met in the LTE eNB, or when LTE-LTE DC is configured, the UE generates a PHR message to report to the LTE eNB. This PHR message includes the type 1 power margin values ​​for all serving cells currently configured and activated in the LTE and NR base stations. Furthermore, when an actual transmission occurs in the LTE or NR base station at the time of PHR reporting, the generated PHR message also includes information about the type 1 power margin for the cell for which it reported it. CMAX,c Value. Additionally, in Figure 3G In this context, assuming the LTE base station is a MeNB, and when the UE is configured to simultaneously transmit PUCCH and PUSCH in the PCell of the representative cell of the MeNB, the UE includes the type 2 power margin value of that PCell in the generated PHR message. Additionally, in... Figure 3G In this case, since the base station that reports the PHR is an LTE base station, regardless of whether the cell is the serving cell corresponding to the LTE base station or the serving cell corresponding to the NR base station, the UE generates a value according to Table 2 above (i.e., the table used when reporting the PHR of LTE) and reports the value to the base station (3g-11).

[0354] When EN-DC is not configured in the UE, but DC is configured between NR base stations, or when conditions are met in the NR gNB (even if EN-DC is configured), the UE generates a PHR message to report to the NR gNB. The PHR message includes the type 1 power margin value for all serving cells currently configured and activated in the LTE and NR base stations. Additionally, when an actual transmission occurs in the LTE or NR base station at the time of PHR reporting, the PHR value for the cell that reported the type 1 power margin is also included. CMAX,c The value is also included in the generated PHR message. Additionally, in Figure 3GSince the conditions are met in the current NR gNB, it is assumed that the LTE base station is a MeNB, and the UE reports a PHR to the NR gNB. Therefore, when the UE is configured to simultaneously transmit PUCCH and PUSCH in the PSCell of the representative cell of the NR gNB (i.e., SgNB), the UE also includes the type 2 power margin value of the PSCell in the generated PHR message. Furthermore, the UE reports the type 2 power margin of the PCell of the LTE base station, and when the UE is configured to report the actual transmission value, the UE generates a PHR message including the type 2 power margin of the PCell of the LTE base station. CMAX,c The report of values. In Figure 3G In this context, the base station receiving the PHR is an NR base station, assuming the NR base station understands all tables in Tables 3, 5, and 6. Therefore, when the serving cell corresponds to an LTE base station, the UE generates a value according to Table 2 (i.e., the table used when reporting the LTE PHR) and reports this value to the base station. In the case of an NR serving cell, the UE reports its remaining transmission power (3g-13) to the base station by referring to Table 4 in the case of FR1 and Table 5 in the case of FR2, depending on the operating frequency range. In the case of DC between NR base stations, when the serving cell is not included in the base station to which the UE is currently reporting (i.e., when reporting the PHR to the MCG for the serving cell of the SCG, or when reporting the PHR to the SCG for the serving cell of the MCG), the UE reports the PHR value to the base station according to Table 4 (i.e., FR1). Alternatively, the UE can notify the base station separately whether the corresponding value is related to Table 4 of FR1 or Table 5 of FR2 by using one of the R bits 3e-39 reserved in the multi-entry PHR format, and thus, the UE can notify the base station of the accurate value.

[0355] The PHR is then reported to the base station (3g-15) to inform the base station of the UE's current remaining power. Therefore, the base station can determine the UE's current remaining power and perform appropriate scheduling for the UE.

[0356] Figure 3H This is a block diagram illustrating the configuration of a UE in a wireless communication system according to an embodiment of the present disclosure.

[0357] refer to Figure 3H The UE includes an RF processor 3h-10, a baseband processor 3h-20, a storage device 3h-30, and a controller 3h-40.

[0358] The RF processor 3h-10 performs functions including signal frequency band conversion and amplification to transmit and receive signals via a wireless channel. Specifically, the RF processor 3h-10 up-converts the baseband signal provided by the baseband processor 3h-20 into an RF band signal, receives the RF band signal via an antenna, and down-converts the received RF band signal back into a baseband signal. For example, the RF processor 3h-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Although... Figure 3H Only one antenna is shown, but the UE may include multiple antennas. Furthermore, the RF processor 3h-10 may include multiple RF chains. Additionally, the RF processor 3h-10 can perform beamforming. To perform beamforming, the RF processor 3h-10 can adjust the phase and amplitude of individual signals transmitted and received via multiple antennas or antenna elements.

[0359] The baseband processor 3h-20 performs the conversion function between baseband signals and bitstreams according to the system's physical layer specifications. For example, in data transmission, the baseband processor 3h-20 generates complex symbols by encoding and modulating the transmitted bitstream. Additionally, in data reception, the baseband processor 3h-20 reconstructs the received bitstream by demodulating and decoding the baseband signal provided from the RF processor 3h-10. For example, when transmitting data according to an OFDM scheme, the baseband processor 3h-20 generates complex symbols by encoding and modulating the transmitted bitstream, maps the complex symbols to subcarriers, and configures the OFDM symbols by performing an IFFT operation and inserting a cyclic prefix (CP). Furthermore, in data reception, the baseband processor 3h-20 can divide the baseband signal provided from the RF processor 3h-10 into OFDM symbol units, recover the signal mapped to the subcarriers by performing an FFT operation, and then demodulate the signal to reconstruct the received bitstream.

[0360] The baseband processor 3h-20 and RF processor 3h-10 transmit and receive signals as described above. Therefore, the baseband processor 3h-20 and RF processor 3h-10 can be referred to as transmitters, receivers, transceivers, or communicators. Furthermore, at least one of the baseband processor 3h-20 and RF processor 3h-10 may include different communication modules to support a variety of different wireless access technologies. Moreover, at least one of the baseband processor 3h-20 and RF processor 3h-10 may include different communication modules to process signals in different frequency bands. Examples of different wireless access technologies may include wireless local area networks (WLANs) (e.g., IEEE 802.11), cellular networks (e.g., LTE networks), etc. Furthermore, examples of different frequency bands may include SHF bands (e.g., 2.5 GHz, 5 GHz, etc.) and millimeter wave (e.g., 60 GHz) bands.

[0361] Storage device 3h-30 can store data such as default programs, applications, and configuration information for UE operation. Specifically, storage device 3h-30 can store information about WLAN nodes configured to perform wireless communication using WLAN access technology. Furthermore, in response to a request from controller 3h-40, storage device 3h-30 provides the stored data.

[0362] Controller 3h-40 controls the overall operation of the UE. For example, controller 3h-40 transmits and receives signals via baseband processor 3h-20 and RF processor 3h-10. Additionally, controller 3h-40 records and reads data stored in storage device 3h-30. For this purpose, controller 3h-40 may include at least one processor. For example, controller 3h-40 may include a communication processor (CP) configured to perform communication control and an upper-layer AP configured to control applications such as applications. According to embodiments of this disclosure, controller 3h-40 includes a multi-connection processor 3h-42 configured to perform processing for operation in a multi-connection mode. For example, controller 3h-40 may control... Figure 3E The process by which the UE performs its own operations.

[0363] According to an embodiment of this disclosure, the controller 3h-40 receives PHR configuration from control messages received from the base station, and when dual connectivity is configured, the controller 3h-40 determines which PHR information to send based on the type of the base station's RAT, or even the type of the RAT of another base station (not the base station reported to it by the UE), and sends a message to the base station to send the PHR information.

[0364] The methods described in the claims or specification of this disclosure according to embodiments of this disclosure can be implemented as hardware, software, or a combination of hardware and software.

[0365] When implemented as software, a non-transitory computer-readable storage medium may be provided to store at least one program (software module). The at least one program stored in the non-transitory computer-readable storage medium is configured to be executable by one or more processors in an electronic device. The one or more processors include instructions to cause the electronic device to perform a method according to an embodiment of the present disclosure as described in the claims or specification of this disclosure.

[0366] At least one program (software module, software) may be stored in non-volatile memory including random access memory (RAM) and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, optical disc-ROM (CD-ROM), digital versatile optical disc (DVD), other optical storage devices, cassette tape, etc., or may be stored in memory consisting of any or all combinations of the foregoing. Furthermore, each of the configuration memories may be provided in multiple quantities.

[0367] The at least one program may be stored in an attachable storage device accessible via a communication network including the Internet, an intranet, a local area network (LAN), a wide area network (WLAN), or a storage area network (SAN), or a combination of these networks. The storage device may access means for executing embodiments of this disclosure via an external port. Furthermore, a separate storage device on the communication network may access means for executing embodiments of this disclosure.

[0368] In the foregoing embodiments of this disclosure, each component of this disclosure is expressed in a singular or plural form. However, for ease of description, a singular or plural expression suitable for the provided circumstances is selected, and therefore this disclosure is not limited to singular or plural forms. Thus, even when an element is expressed in a plural form, the element may be configured in a singular form, and even when an element is expressed in a singular form, the element may be configured in a plural form.

[0369] Although this disclosure has been shown and described with reference to various embodiments thereof, those skilled in the art will understand that various changes in form and detail may be made to this disclosure without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents. For example, multiple portions of one embodiment of this disclosure may be combined with multiple portions of another embodiment in a manner that enables operation of a base station and a UE. While the embodiments of this disclosure are based on a Frequency Division Duplex (FDD) LTE system, modified embodiments based on the technical concept of the embodiments may be implemented in another system such as a Time Division Duplex (TDD) LTE system, a 5G system, and an NR system.

Claims

1. A method performed by a transmitting device in a wireless communication system, the method comprising: Based on the received first data, the Service Data Adaptation Protocol (SDAP) entity sends second data, generated by adding an SDAP header to the Packet Data Convergence Protocol (PDCP) entity; The uplink compressed data block is obtained by the PDCP entity by performing uplink data compression UDC on the second data excluding the SDAP header; The PDCP entity adds the UDC header to the SDAP header; The PDCP entity performs integrity protection on the UDC header, SDAP header, and UDC data blocks. The PDCP entity performs encryption on the integrity-protected UDC header and the integrity-protected UDC data block, wherein the encryption is not performed on the integrity-protected SDAP header; as well as The PDCP entity sends third data to the lower layer, including the PDCP header, the encrypted UDC header, the encrypted UDC data block, and the integrity-protected SDAP header.

2. The method as described in claim 1, wherein, Enforcing integrity protection includes: The Message Authentication Code (MAC-I) for integrity is generated by the PDCP entity; and The PDCP entity connects the MAC-I to the integrity-protected UDC data block, and Encryption includes: The PDCP entity performs encryption on MAC-I.

3. The method of claim 1, further comprising: Receive at least one of the following through higher-level signaling: SDAP header configuration information, UDC configuration information, and integrity protection configuration information.

4. A method performed by a receiving device in a wireless communication system, the method comprising: Based on receiving the first data from the lower layer, the Packet Data Convergence Protocol (PDCP) entity obtains the second data by removing the PDCP header from the first data; The PDCP entity performs decryption on a portion of the second data, which includes the uplink data compressed UDC header and the UDC data block, wherein the decryption does not perform on the Service Data Adaptation Protocol (SDAP) header included in the second data; The PDCP entity performs integrity verification on the decrypted UDC header, the decrypted UDC data block, and the SDAP header; The PDCP entity performs decompression on the integrity-verified UDC data block based on the integrity-verified UDC header; and The PDCP entity sends decompressed UDC data blocks and SDAP headers to the SDAP layer; The SDAP entity sends decompressed UDC data blocks to the upper layer.

5. The method of claim 4, wherein, Decryption includes: The PDCP entity decrypts the MAC-I message authentication code for integrity included in the second data, and The integrity verification process includes: The MAC-I calculated from the PDCP entity, i.e., the X-MAC calculation, and When X-MAC equals MAC-I, the integrity verification by PDCP entity recognition is successful.

6. The method of claim 4, further comprising: Receive at least one of the following through higher-level signaling: SDAP header configuration information, UDC configuration information, and integrity protection configuration information.

7. A transmitting device in a wireless communication system, the transmitting device comprising: transceiver; as well as The controller implements the Service Data Adaptation Protocol (SDAP) entity, the Packet Data Convergence Protocol (PDCP) entity, and the lower layers. The controller is configured as follows: Based on the received first data, the SDAP entity sends second data to the PDCP entity by adding the SDAP header to the first data; The uplink compressed data block is obtained by the PDCP entity by performing uplink data compression UDC on the second data excluding the SDAP header; The PDCP entity adds the UDC header to the SDAP header; The PDCP entity performs integrity protection on the UDC header, SDAP header, and UDC data blocks. The PDCP entity performs encryption on the integrity-protected UDC header and the integrity-protected UDC data block, wherein the encryption is not performed on the integrity-protected SDAP header; as well as The PDCP entity sends third data to the lower layer, including the PDCP header, the encrypted UDC header, the encrypted UDC data block, and the integrity-protected SDAP header.

8. The transmitting device as claimed in claim 7, wherein, The controller is also configured as follows: The Message Authentication Code (MAC-I) for integrity is generated by the PDCP entity; and The PDCP entity connects the MAC-I to the integrity-protected UDC data block, and The PDCP entity performs encryption on MAC-I.

9. The transmitting device as claimed in claim 7, wherein, The controller is also configured as follows: The transceiver receives at least one of the following via higher-layer signaling: SDAP header configuration information, UDC configuration information, and integrity protection configuration information.

10. A receiving device in a wireless communication system, the receiving device comprising: transceiver; as well as The controller implements the Service Data Adaptation Protocol (SDAP) entity, the Packet Data Convergence Protocol (PDCP) entity, and the lower layers. The controller is configured as follows: Based on receiving the first data from the lower layer, the PDCP entity obtains the second data by removing the PDCP header from the first data; The PDCP entity performs decryption on a portion of the second data, which includes the uplink data compressed UDC header and the UDC data block, wherein the decryption does not involve the SDAP header included in the second data; The PDCP entity performs integrity verification on the decrypted UDC header, the decrypted UDC data block, and the SDAP header; The PDCP entity performs decompression on the integrity-verified UDC data block based on the integrity-verified UDC header; and The PDCP entity sends decompressed UDC data blocks and SDAP headers to the SDAP layer; The SDAP entity sends decompressed UDC data blocks to the upper layer.

11. The receiving device as claimed in claim 10, wherein, The controller is also configured as follows: The PDCP entity decrypts the MAC-I message authentication code for integrity included in the second data. The MAC-I calculated from the PDCP entity, i.e., the X-MAC calculation, and When X-MAC equals MAC-I, the integrity verification by PDCP entity recognition is successful.

12. The receiving device as claimed in claim 10, wherein, The controller is also configured as follows: The transceiver receives at least one of the following via higher-layer signaling: SDAP header configuration information, UDC configuration information, and integrity protection configuration information.

Images