CN111567095B

CN111567095B - Method and apparatus for wireless communication in a wireless communication system

Info

Publication number: CN111567095B
Application number: CN201980007804.5A
Authority: CN
Inventors: 金相范; 金东建; 张宰赫; 金成勋
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2018-01-10
Filing date: 2019-01-10
Publication date: 2022-12-09
Anticipated expiration: 2039-01-10
Also published as: EP3682673A4; KR102427826B1; EP3682673A1; KR20190085454A; CN111567095A

Abstract

There is provided an operation method of a transmission apparatus, including: receiving a Service Data Adaptation Protocol (SDAP) header configuration and a header compression configuration through higher layer signaling; and 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 when the SDAP entity receives the first data from an upper layer, 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 ciphering on data of the second data except for the SDAP header by the PDCP entity, and generating a PDCP header, and transmitting third data obtained by adding the generated PDCP header to the ciphered data to a lower layer, the generating and the transmitting being performed by the PDCP entity.

Description

Method and apparatus for wireless communication in a wireless communication system

Technical Field

The present disclosure relates to methods and apparatus for wireless communication in a wireless communication system.

Background

In order to meet the increasing demand for wireless data traffic after commercialization of 4 th generation (4G) communication systems, considerable efforts have been made to develop pre-5 th generation (5G) communication systems or 5G communication systems. This is one reason why the "5G communication system" or the "pre-5G communication system" is called a "super 4G network communication system" or a "long-term evolution (LTE) system". In order to achieve a high data transmission rate, a 5G communication system implemented in an ultra high frequency band (mmWave), for example, a 60GHz band is being developed. In order to reduce the occurrence of stray electric waves in such an ultra-high frequency band and increase the transmission distance of electric waves in a 5G communication system, various techniques, such as beam forming, massive multiple-input multiple-output (MIMO), full-size MIMO (FD-MIMO), array antenna, analog beam forming, and massive antenna, are being studied. To improve the system network of the 5G communication system, various technologies have been developed, such as evolved small cells, advanced small cells, cloud radio access network (cloud RAN), ultra-dense networks, device to device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multi-point (CoMP), and interference cancellation. In addition, for the 5G communication system, other technologies have been developed, such as mixed modulation of frequency-shift keying (FSK) and Quadrature Amplitude Modulation (QAM) (FSK and QAM, FQAM) as Advanced Coding Modulation (ACM) schemes and Sliding Window Superposition Coding (SWSC), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and Sparse Code Multiple Access (SCMA) as advanced access schemes.

The Internet has evolved from a human-based connection network in which humans create and consume information into an Internet of Things (IoT) in which distributed configurations such as objects exchange information with each other to process information. Internet of Everything (IoE) technology is newly provided, for example, in which IoT-related technology is combined with technology for processing large data through connection with a cloud server. To implement IoT, various technical components are required, such as sensing technologies, wired/wireless communication and network infrastructure, service interface technologies, security technologies, and so forth. In recent years, technologies including a sensor network for connecting objects, machine to machine (M2M) communication, machine Type Communication (MTC), and the like have been studied. In an IoT environment, an intelligent Internet Technology (IT) service may be provided to collect and analyze data obtained from objects connected to each other, thereby creating new value in human life. As existing Information Technology (IT) and various industries are fused and combined with each other, ioT may be applied to various fields, such as smart homes, smart buildings, smart cities, smart cars or interconnected cars, smart grids, healthcare, smart home appliances, and high-quality medical services.

Various attempts are being made to apply the 5G communication system to the IoT network. For example, techniques related to sensor networks, M2M communication, MTC, etc. are implemented by using 5G communication techniques (including beamforming, MIMO, array antennas, etc.). The application of the cloud RAN as the big data processing technology described above may be an example of convergence of 5G communication technology and IoT technology.

The above information is provided merely as background information to aid in understanding the present disclosure. No determination is made as to whether any of the above can be applied as prior art with respect to the present disclosure, nor is an assertion made.

Disclosure of Invention

Technical scheme

According to an aspect of the present disclosure, there is provided an operation method of a transmission apparatus in a wireless communication system. The operation method comprises the following steps: receiving a Service Data Adaptation Protocol (SDAP) header configuration and a header compression configuration through higher layer signaling; and 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 when the SDAP entity receives the first data from an upper layer, 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 ciphering on data of the second data except for the SDAP header by the PDCP entity, and generating a PDCP header, and transmitting third data obtained by adding the generated PDCP header to the ciphered data to a lower layer, the generating and the transmitting being performed by the PDCP entity.

Advantageous effects

An apparatus and method capable of efficiently providing communication in a wireless communication system are provided.

Drawings

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:

fig. 1A is a diagram of a transmission structure of a time-frequency domain as a Downlink (DL) radio resource region of a Long Term Evolution (LTE) system, an LTE-advanced (LTE-a) system, or the like, according to an embodiment of the present disclosure;

fig. 1B is a diagram of a transmission structure of a time-frequency domain as an Uplink (UL) radio resource region of an LTE system, an LTE-a system, or the like, according to an embodiment of the present disclosure.

Fig. 2A is a diagram illustrating a configuration of a Long Term Evolution (LTE) system according to an embodiment of the present disclosure;

fig. 2B is a diagram illustrating a radio protocol architecture in an LTE system according to an embodiment of the present disclosure.

Fig. 2C is a diagram showing a configuration of a new mobile communication system according to an embodiment of the present disclosure;

fig. 2D is a diagram illustrating a radio protocol architecture of a new mobile communication system according to an embodiment of the present disclosure;

fig. 2E is a diagram illustrating a procedure performed by a base station to indicate whether to perform Uplink Data Compression (UDC) when a terminal establishes a connection to a network according to an embodiment of the present disclosure;

FIG. 2F is a diagram illustrating a process and data structures for performing UDC according to an embodiment of the present disclosure;

fig. 2G is a diagram for describing a UDC method according to an embodiment of the present disclosure;

fig. 2H illustrates a process and data structure for performing robust header compression (ROHC) according to an embodiment of the disclosure;

fig. 2I illustrates a process in which 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, and does not perform ciphering, according to an embodiment of the present disclosure;

fig. 2J illustrates a process in which the SDAP entity generates an SDAP header for data received from an upper layer, and the PDCP entity does not perform integrity protection and ciphering on the SDAP header, according to an embodiment of the present disclosure;

fig. 2K illustrates an advantage of the structure of the base station achieved by applying an SDAP header that is not subject to ciphering or integrity protection, according to an embodiment of the present disclosure;

fig. 2L illustrates the advantages of processing that may be obtained from a base station and User Equipment (UE) by applying an SDAP header that is not subject to ciphering and integrity protection, in accordance with an embodiment of the present disclosure;

fig. 2M illustrates a process 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 ciphering on the SDAP header and does not perform ciphering on a message authentication code (MAC-I) for integrity, according to an embodiment of the present disclosure;

fig. 2N illustrates the processing advantages that may be obtained from a base station and UE by applying an SDAP header that is not subject to ciphering and integrity protection and by not performing ciphering on the MAC-I, according to one embodiment;

fig. 2O illustrates a process 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), integrity protection is applied to the SDAP header, and ciphering is not performed on the SDAP header, according to an embodiment of the present disclosure;

fig. 2P illustrates a process in which the SDAP entity generates an SDAP header for data received from an upper layer, and the PDCP entity performs header compression (i.e., ROHC) and does not perform integrity protection and ciphering on the SDAP header, according to an embodiment of the present disclosure;

fig. 2Q illustrates the advantages of processing that may be obtained from a base station and a UE by applying an SDAP header that is not subject to ciphering and integrity protection, in accordance with an embodiment of the present disclosure;

fig. 2R illustrates a process 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), does not perform integrity protection and ciphering on the SDAP header, and does not perform ciphering on a MAC-I, according to an embodiment of the present disclosure;

fig. 2S illustrates advantages in processing that may be obtained from a base station and a UE by applying an SDAP header that is not subject to ciphering and integrity protection, by applying ROHC, and by not ciphering the MAC-I, according to an embodiment of the present disclosure;

fig. 2T illustrates a process 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 ciphering to the UDC header, applies integrity protection to the SDAP header, and does not perform ciphering to the SDAP header, according to an embodiment of the disclosure;

fig. 2U illustrates a process 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 perform ciphering on the UDC header, applies integrity protection to the SDAP header, and does not perform ciphering on the SDAP header, according to an embodiment of the disclosure;

fig. 2V illustrates a process in which an SDAP entity generates an SDAP header for data received from an upper layer and a PDCP entity performs UDC, applies no integrity protection to the UDC header, performs no ciphering to the UDC header, ciphers MAC-I, applies no integrity protection to the SDAP header, and performs no ciphering to the SDAP header, according to an embodiment of the present disclosure.

Fig. 2W illustrates the advantages of processing obtained from a base station and UE that may be achieved by applying an SDAP header and a UDC header that are not subject to ciphering and integrity protection, in accordance with embodiments of the present disclosure;

fig. 2X illustrates a process in which an SDAP entity generates an SDAP header for data received from an upper layer, and a PDCP entity performs UDC, applies no integrity protection to the UDC header, performs no ciphering to the UDC header, applies no integrity protection to the SDAP header, performs no ciphering to the SDAP header, and performs no ciphering to a MAC-I, according to an embodiment of the present disclosure.

Fig. 2Y illustrates the advantages of processing that may be obtained from a base station and UE by applying an SDAP header and a UDC header that are not subject to ciphering and integrity protection, by performing UDC, and by not ciphering MAC-I, in accordance with embodiments of the present disclosure;

fig. 2Z illustrates operations of a transmitting and receiving SDAP/PDCP entity of a logical channel, bearer or SDAP/PDCP entity configured with integrity protection when an SDAP header on which integrity protection and ciphering are not performed is applied to the SDAP/PDCP entity, according to an embodiment of the present disclosure;

fig. 2AA illustrates a configuration of a UE according to an embodiment of the present disclosure;

fig. 2AB illustrates a configuration of a base station according to an embodiment of the present disclosure;

fig. 3A is a diagram showing a configuration of an LTE system according to an embodiment of the present disclosure;

fig. 3B is a diagram illustrating a radio protocol architecture in an LTE system according to an embodiment of the present disclosure.

Fig. 3C is a diagram for describing Carrier Aggregation (CA) in a UE according to an embodiment of the present disclosure;

fig. 3D is a diagram for describing the concept of multi-connectivity in LTE and New Radio (NR) according to an embodiment of the present disclosure;

fig. 3E illustrates a method of transmitting an uplink according to a configuration and a type of the uplink according to an embodiment of the present disclosure;

fig. 3F illustrates a message flow between a UE and a base station to which the UE reports Power Headroom (PHR) while a dual connection is established between different Radio Access Technologies (RATs), according to an embodiment of the present disclosure.

Fig. 3G is a diagram illustrating an operation flow of a UE when the UE reports a PHR while dual connectivity is established between different RATs according to an embodiment of the present disclosure; and

fig. 3H is a block diagram illustrating a configuration of a UE in a wireless communication system according to an embodiment of the present disclosure.

Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures.

Detailed Description

Aspects of the present disclosure are to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present disclosure is to provide an apparatus and method capable of efficiently providing communication in a wireless communication system.

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

According to another aspect of the present disclosure, there is provided an operating method of a receiving apparatus in a wireless communication system. The operation method comprises the following steps: when the PDCP entity receives first data from a lower layer, receives an SDAP header configuration and a header compression configuration through higher layer signaling, reads and removes a PDCP header and an SDAP header from the first data by the PDCP entity, performs deciphering by the PDCP entity on data obtained by removing the PDCP header and the SDAP header from the first data, and transmits second data obtained by performing header decompression on the deciphered data to an upper layer by the PDCP entity.

According to another aspect of the present disclosure, a transmitting apparatus in a wireless communication system is provided. The device includes: a transceiver configured to receive SDAP header configuration and header compression configuration through higher layer signaling; and a controller configured to control the SDAP entity to generate an SDAP header and transmit second data obtained by adding the generated SDAP header to the first data to the PDCP entity when the SDAP entity receives the first data from an upper layer, and control the PDCP entity to perform header compression on an upper layer header of the second data except for the SDAP header, perform ciphering on data of the second data except for the SDAP header to generate a PDCP header, and transmit third data obtained by adding the generated PDCP header to the ciphered data to a lower layer.

According to another aspect of the present disclosure, there is provided a receiving apparatus in a wireless communication system. The device comprises: a transceiver configured to receive SDAP header configuration and header compression configuration through higher layer signaling; and a controller configured to control the PDCP entity to read and remove the PDCP header and the SDAP header from the first data, perform decryption on data obtained by removing the PDCP header and the SDAP header from the first data, and transmit second data obtained by performing header decompression on the decrypted data to the upper layer, when the PDCP entity receives the first data from the lower layer.

Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.

Detailed description of the preferred embodiments

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. The following description includes various specific details for the purpose of facilitating understanding, but these are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are not limited to bibliographic meanings, but are used only by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following descriptions of the various embodiments of the present disclosure are provided for illustration only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

In describing embodiments of the present disclosure, technical content that is well known in the related art and is not directly related to the present disclosure will not be provided. By omitting redundant description, the substance of the present disclosure will not be obscured and can be clearly explained.

For the same reason, components may be enlarged, omitted, or schematically shown in the drawings for clarity. Further, the size of each component does not fully reflect the actual size. In the drawings, like numbering represents like elements.

As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items. When an expression such as at least one of "\8230", follows the list of elements, the entire list of elements is decorated and individual elements in the list are not decorated.

Advantages and features of one or more embodiments of the present disclosure and methods of accomplishing the same may be understood more readily by reference to the following detailed description of embodiments of the disclosure and the accompanying drawings. In this regard, embodiments of the present disclosure may have different forms and should not be construed as limited to the description set forth herein. Rather, these embodiments of the disclosure are provided so that this disclosure will be thorough and complete and will fully convey the concept of the embodiments of the disclosure to those skilled in the art, and the present disclosure will only be defined by the appended claims.

Here, it will be understood that combinations of blocks in the flowchart or process flow diagrams can be implemented by computer program instructions. As these computer program instructions may be loaded onto a processor of a general purpose computer, special purpose computer, or another programmable data processing apparatus, the instructions that execute via the processor of the computer or another programmable data processing apparatus create means for implementing the functions specified in the flowchart block(s). The computer program instructions may be stored in a computer usable or computer-readable memory that can direct a computer or another programmable data processing apparatus to function in a particular manner, and thus the instructions stored in the computer usable or computer-readable memory may also produce an article of manufacture including instruction means that implement the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or another programmable data processing apparatus, and thus, the instructions for operating the computer or the other programmable apparatus by generating a computer-implemented process when a series of operations are performed in the computer or the other programmable apparatus may provide operations for executing the functions described in the flowchart block(s).

Further, each block may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of order. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

Here, the term "unit" in the embodiments of the present disclosure refers to a software component or a hardware component, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and performs a specific function. However, the term "unit" is not limited to software or hardware. A "unit" may be formed in an addressable storage 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, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, or variables. The functionality provided by the components and "units" may be associated with a fewer number of components and "units" or may be divided into additional components and "units". Further, the components and "units" may be embodied as one or more Central Processing Units (CPUs) embodied in a device or secure multimedia card. Further, in an embodiment, a "unit" may comprise at least one processor.

In the following description, terms for identifying an access node, terms for referring to network entities, terms for referring to messages, terms for referring to interfaces between network entities, terms for referring to various pieces of identification information, and the like are provided for convenience of description. Accordingly, the present disclosure is not limited to the following terms, and other terms referring to objects having equivalent technical meanings may be used.

For convenience of description, the present disclosure uses terms and names defined in the third generation partnership project long term evolution (3 GPP LTE) standard or modified based on the terms and names. However, the present disclosure is not limited to terms and names, and may be equally applied to systems conforming to other standards.

Fig. 1 is a diagram of a transmission structure of a time-frequency domain of a DL radio resource region of an LTE system or the like according to an embodiment of the present disclosure.

Referring to fig. 1, the horizontal axis represents a time domain in a radio resource region, and the vertical axis represents a frequency domain in the radio resource region. In the time domain, the smallest transmission unit is an OFDM symbol, and N is aggregated _symb One OFDM symbol 1a-02 to constitute one slot 1a-06 and two slots are aggregated to constitute one subframe 1a-05. The length of the slot may be 0.5ms, and the length of the subframe may be 0.1ms. Radio frames 1a-14 are time domain intervals consisting of 10 subframes. The minimum transmission unit in the frequency domain is a subcarrier, and the transmission bandwidth of the entire system is totally N _RB ^DL The sub-carriers 1 a-04. However, this particular value may vary depending on the system.

In the time-frequency domain, the basic unit of a resource is a Resource Element (RE) 1a-12, and may be indicated as an OFDM symbol index and a subcarrier index. Resource management systemA source block (RB) 1a-08 or PRB is defined as N in the time domain _symb A number of consecutive OFDM symbols 1a-02 and N in the frequency domain _RB A number of consecutive sub-carriers 1a-10. Thus, one RB 108 consists of N in one slot _symb X N _RB And RE 1 a-12.

Generally, the minimum transmission unit of data is an RB, and in an LTE system, generally, N _symb Is 7, and N _RB Is 2, and N _BW And N _RB May be proportional to the system transmission bandwidth. However, systems other than the LTE system may use different values. The data rate increases in proportion to the number of scheduled RBs.

In the LTE system, 6 transmission bandwidths may be defined and operated. In the case of an FDD system in which DL and UL are divided and operated by frequency, a transmission bandwidth of DL and a transmission bandwidth of UL may be different from each other. The channel bandwidth indicates a Radio Frequency (RF) bandwidth corresponding to a system transmission bandwidth. Table 1 presents a correspondence between a system transmission bandwidth and a channel bandwidth defined in the LTE system. For example, in the LTE system having a channel bandwidth of 10MHz, the transmission bandwidth is composed of 50 RBs.

[ Table 1]

Channel Bandwidth BW _Channel [MHz]	1.4	3	5	10	15	20
							Transmission bandwidth configuration N _RB	6	15	25	50	75	100

The DL control information may be transmitted within the first N OFDM symbols in the subframe. In general, N = {1,2,3}. Thus, the value N may be changed for each subframe according to 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 through, scheduling information on DL data or UL data, and a HARQ ACK/NACK signal.

In the LTE system, scheduling information on DL data or UL data is transmitted from a BS to a terminal through Downlink Control Information (DCI). The DCI is defined in various formats, and it may be indicated whether scheduling information is UL data scheduling information (UL grant) or DL data scheduling information (DL grant) according to each format, whether the DCI is a compact DCI having control information of a small size, whether spatial multiplexing using multiple antennas is applied, or whether the DCI is DCI for controlling power. For example, DCI format 1, which is scheduling control information (DL grant) of DL data, may include at least the following control information:

-resource allocation type 0/1 flag: indicating whether the resource allocation type is type 0 or type 1. Type 0 allocates resources in units of Resource Block Groups (RBGs) by application of bitmap type. In the LTE system, a scheduled basic unit is an RB expressed as a time domain and frequency domain resource, and an RBG is composed of a plurality of RBs considered as a scheduled basic unit in type 0. Type 1 allocates a specific RB in the RBG.

-RB assignment: indicating the RB allocated for data transmission. And determining the expressed resources according to the system bandwidth and the resource allocation method.

Modulation and Coding Scheme (MCS): a modulation method for data transmission and a size of a Transport Block (TB) that is data to be transmitted are indicated.

HARQ process number: indicating the process number of HARQ.

-new data indicator: indicating whether the HARQ transmission is an initial transmission or a retransmission.

-redundancy version: indicating the redundancy version of HARQ.

-Transmit Power Control (TPC) commands for Physical Uplink Control Channel (PUCCH): a transmission power control command of PUCCH which is a UL control channel is indicated.

After undergoing the channel coding and modulation processes, DCI may be transmitted through a Physical Downlink Control Channel (PDCCH) (or control information, hereinafter used mixedly) which is a DL physical control channel or an Enhanced PDCCH (EPDCCH) (or enhanced control information, hereinafter used mixedly).

In general, DCI is independently scrambled with respect to each terminal by a specific Radio Network Temporary Identifier (RNTI) or a terminal identifier, added with a Cyclic Redundancy Check (CRC), channel-coded, and then configured as an independent PDCCH to be transmitted. In the time domain, a PDCCH is mapped and transmitted for a control channel transmission interval. The mapping position of the PDCCH in the frequency domain is determined by an Identifier (ID) of each terminal, and the PDCCH may be transmitted through a transmission band of the entire system.

DL data may be transmitted through a Physical Downlink Shared Channel (PDSCH), which is a physical channel for transmitting DL data. The PDSCH may be transmitted after a control channel transmission interval, and scheduling information (such as a specific mapping position or modulation method in the frequency domain) may be included in DCI to be transmitted through the PDCCH.

The BS notifies the terminal of a modulation method applied to the PDSCH to be transmitted and a Transport Block Size (TBS) to be transmitted, by using the MCS in the control information constituting the DCI. The MCS may consist of 5 bits or may consist of another number of bits. The TBS corresponds to a size before channel coding for error correction is applied to a TB to be transmitted by the BS.

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. Also, the TB may indicate a unit of data or a MAC Protocol Data Unit (PDU) transmitted from the MAC layer to the physical layer.

The modulation methods supported in the LTE system are Quadrature Phase Shift Keying (QPSK), 16quadrature amplitude modulation (16qam), or 64QAM, and the corresponding modulation orders (Qm) correspond to 2, 4, and 6. In the case of QPSK modulation, 2 bits per symbol may be transmitted, in the case of 160QAM, 4 bits per symbol may be transmitted, and in the case of 64QAM, 6 bits per symbol may be transmitted. Further, a modulation method of 256QAM or more may be used according to system modification.

Fig. 1B is a diagram of a transmission structure of a time-frequency domain of a UL radio resource region of an LTE system or similar system according to an embodiment of the present disclosure.

Referring to fig. 1B, the horizontal axis represents a time domain in a radio resource region, and the vertical axis represents a frequency domain in the radio resource region. Radio frames 1b-14 are time domain intervals. In the time domain, the smallest transmission unit in the time domain is the SC-FDMA symbol 1b-02, and N is aggregated _symbUL One SC-FDMA symbol to constitute one slot 1b-06. Two slots are aggregated to form one subframe 1b-05. The minimum transmission unit in the frequency domain is a subcarrier, and the transmission bandwidth of the entire system is totally N _RB ^UL And a number of subcarriers 1 b-04. N is a radical of _RB ^UL May have a value proportional to the system transmission bandwidth.

In the time-frequency domain, the basic unit of resources is RE 1b-12, and can be defined as SC-FDMA symbol index and subcarrier index. RB pair 1b-08 is defined as N in the time domain _symb One consecutive SC-FDMA symbol and N in frequency domain _RB A number of consecutive subcarriers 1b-10. Thus, one RB is formed by N _symb X N _RB And RE. Generally, the minimum transmission unit of data or control information is an RB unit. A PUCCH may be mapped on a frequency domain corresponding to 1 RB and transmitted for one subframe.

In the LTE system, a timing relationship between a PDCCH or a PDCCH/EPDCCH including a semi-persistent scheduling (SPS) release as a physical channel for transmitting DL data and an UL physical channel (PUCCH or PUSCH) through which a corresponding HARQ ACK/NACK is transmitted may be defined. As an example, in the LTE system operating as FDD, HARQ ACK/NACK corresponding to a PDSCH transmitted in an (n-4) th subframe or a PDCCH/EPDCCH including an SPS release is transmitted by a PUCCH or a PUSCH in an nth subframe.

In the LTE system, DL HARQ employs an asynchronous HARQ method in which data retransmission time is not fixed. When HARQ NACK is fed back from the terminal with respect to initial transmission data transmitted by the BS, the BS freely determines a transmission time of retransmitted data through a scheduling operation. The terminal buffers the data determined to be erroneous for the HARQ operation as a result of decoding the received data and then performs a combination with the data of the next retransmission.

Upon receiving the PDSCH including DL data transmitted from the BS in subframe n, the terminal transmits UL control information including HARQ ACK or NACK of the DL data to the BS through the PUCCH or PUSCH in subframe n + k. K may be defined differently according to FDD or Time Division Duplex (TDD) and subframe configurations of the LTE system. As an example, in FDD LTE systems, k is fixed to 4. On the other hand, in the TDD LTE system, k may be changed according to the subframe configuration and the subframe number. During data transmission through a plurality of carriers, the value of k may be differently applied according to the TDD configuration of each carrier.

In the LTE system, in contrast to DL HARQ, UL HARQ employs a synchronous HARQ method in which a data transmission time is fixed. The UL/DL timing relationship between a Physical Uplink Shared Channel (PUSCH) which is a physical channel for transmitting UL data, a PDCCH which is a previous DL control channel, and a Physical Hybrid Indicator Channel (PHICH) which is a physical channel through which DL HARQ ACK/NACK corresponding to the PUSCH is transmitted can be fixed by the following rule.

Upon receiving a PDCCH including UL scheduling control information transmitted from the BS in subframe n or a PHICH through which DL HARQ ACK/NACK is transmitted, the terminal transmits UL data corresponding to the control information through a PUSCH in subframe n + k. K may be defined differently according to FDD or TDD of the LTE system and a configuration thereof. As an example, in FDD LTE systems, k is fixed to 4. On the other hand, in the TDD LTE system, k may be changed according to the subframe configuration and the subframe number.

In the FDD LTE system, when a BS transmits an UL scheduling grant or DL control signal and data to a terminal in a subframe n, the terminal receives the UL scheduling grant or DL control signal and data in the subframe n. First, when receiving UL scheduling grant in subframe n, the terminal transmits UL data in subframe n + 4. When receiving the DL control signal and data in the subframe n, the terminal transmits HARQ ACK or NACK with respect to the DL data in the subframe n + 4. Accordingly, the preparation time for the terminal to receive the UL scheduling grant and transmit UL data or receive DL data and transmit HARQ ACK or NACK is 3ms corresponding to three subframes. In addition, when the terminal receives a PHICH carrying DL HARQ ACK/NACK from the BS in subframe i, the PHICH corresponds to a PUSCH transmitted by the terminal in subframe i-k. K is defined differently according to FDD or TDD of the LTE system and its configuration. As an example, in FDD LTE systems, k is fixed to 4. On the other hand, in the TDD LTE system, k may be changed according to the subframe configuration and the subframe number. During data transmission through a plurality of carriers, the k value may be differently applied according to the TDD configuration of each carrier.

The wireless communication system has been described above with reference to the LTE system, but the embodiments are applicable not only to the LTE system but also to various wireless communication systems such as the NR system and the 5G system. When the embodiment is applied to another wireless communication system, the value of k may be changed even in a system using a modulation method corresponding to FDD.

In a 5G or NR access technology system, which is a new communication system, various services are designed to be freely multiplexed on time resources and frequency resources, and thus, waveforms, parameter sets, reference signals, etc. may be dynamically or freely allocated according to the needs of the corresponding service. In order to provide the terminal with the best service in wireless communication, data transmission optimized via channel quality and interference measurement is important, and therefore, it is essential to accurately measure the channel state. However, unlike 4G communication in which channel and interference characteristics do not change greatly according to frequency resources, in a 5G or NR system, channel and interference characteristics may change greatly according to services, so that a support subset is required in terms of Frequency Resource Groups (FRGs) in order to divide and measure channel and interference characteristics. Meanwhile, service types supported in a 5G or NR system may be classified into eMBB, mtc, and URLLC categories. Here, the eMBB may be a service for high-speed transmission of large-capacity data, the mtc may be a service for terminal power consumption minimization and access of a plurality of terminals, and the URLLC may be a service for high reliability and low delay. Different requirements may be applied based on the type of service applied to the terminal.

As such, a variety of services can be provided to users in a communication system, and a method and apparatus for providing a variety of services in the same time zone are required in order to provide a variety of services to users.

Fig. 2A is a diagram illustrating a configuration of an LTE system according to an embodiment of the present disclosure.

Referring to fig. 2a, a radio access network of an lte system is composed of a plurality of evolved Node bs (hereinafter referred to as enbs, node bs, or base stations) 2a-05, 2a-10, 2a-15, and 2a-20, mobility Management Entities (MMEs) 2a-25, and serving gateways (S-GWs) 2 a-30. User equipment (hereinafter referred to as UE or terminal) 2a-35 accesses an external network via enbs 2a-05, 2a-10, 2a-15 and 2a-20 and S-GW 2 a-30.

In FIG. 2A, eNBs 2A-05, 2A-10, 2A-15, and 2A-20 correspond to node Bs of a Universal Mobile Telecommunications System (UMTS) system, respectively. The eNBs 2a-05, 2a-10, 2a-15 and 2a-20 are each connected to the UE 2a-35 and perform complex functions compared to the node B. In the LTE system, all user traffic including a real-time service such as voice over internet protocol (VoIP) is provided through a shared channel, and thus, there is a need for an apparatus for acquiring and scheduling pieces of status information of a UE, including a buffer status, an available transmission power status, a channel status, etc., and enbs 2a-05, 2a-10, 2a-15, and 2a-20 correspond to the apparatuses, respectively. Generally, one eNB controls a plurality of cells. For example, to achieve a transmission speed of 100Mbps, the LTE system uses Orthogonal Frequency Division Multiplexing (OFDM) as a radio access technology at a bandwidth of 20 MHz. In addition, the LTE system uses an AMC technique that determines a modulation scheme and a channel coding rate according to a channel state of the UE. The S-GW 2a-30 is a device configured to provide a data bearer, and generates or removes the data bearer in response to control of the MME 2 a-25. The MMEs 2a-25 perform not only mobility management functions but also various control functions for the UE, and are connected to a plurality of enbs.

Referring to fig. 2B, in the UE and the LTE eNB, respectively, the radio protocols of the LTE system may be composed of Packet Data Convergence Protocols (PDCP) 2B-05 and 2B-40, radio Link Controls (RLC) 2B-10 and 2B-35, medium Access Controls (MAC) 2B-15 and 2B-30, and physical layers (PHY) 2B-20 and 2B-25. The PDCP 2b-05 and 2b-40 can perform operations such as IP header compression/decompression. The major functions of the PDCP 2b-05 and 2b-40 are summarized as follows.

Header compression and decompression (ROHC only).

-transmission of user data.

-in-order delivery of upper layer Packet Data Units (PDUs) during PDCP re-establishment of RLC AM.

For split (split) bearer in DC (RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception.

-duplicate detection of lower Service Data Units (SDUs) during PDCP re-establishment of RLC AM.

-retransmission function PDCP SDUs at handover and for separate bearer in DC, PDCP PDUs in PDLC data recovery procedure for RLC AM.

-encryption and decryption functions.

Timer based SDU discard in uplink.

The RLC 2b-10 and 2b-35 reconfigure the PDCP PDUs to an appropriate size to perform an automatic repeat request (ARQ) operation, etc. The main functions of the RLC 2b-10 and 2b-35 are summarized as follows.

-transmission of upper layer PDUs.

Error correction by ARQ (for Acknowledged Mode (AM) data transfer only).

Concatenation, segmentation and reassembly of RLC SDUs (only for Unacknowledged Mode (UM) and AM data transfer).

Re-segmentation of RLC data PDUs (for AM data transfer only).

Reordering of RLC data PDUs (only for UM and AM data transfer).

Duplicate detection (only for UM and AM data transfer).

Protocol error detection (for AM data transfer only).

RLC SDU discard (only for UM and AM data transfer).

RLC re-establishment.

The MACs 2b-15 and 2b-30 are connected to a plurality of RLC entities configured in one UE, and perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from the MAC PDUs. The main functions of the MACs 2b-15 and 2b-30 are summarized as follows.

-mapping between logical channels and transport channels.

-multiplexing/demultiplexing MAC SDUs belonging to/from a Transport Block (TB) delivered from a physical layer on a transport channel into/from MAC SDUs delivered to/from a physical layer on a transport channel.

-scheduling information reporting.

Error correction by HARQ.

-priority handling between logical channels of one UE.

-priority handling between UEs by dynamic scheduling.

-an MBMS service identity.

-transport format selection.

-filling.

The PHYs 2b-20 and 2b-25 perform an operation of channel-coding and modulating upper layer data and transmitting OFDM symbols through a radio channel by converting the upper layer data into the OFDM symbols, or an operation of demodulating and channel-decoding OFDM symbols received through the radio channel and transmitting the decoded data to the upper layer.

Fig. 2C is a diagram showing a configuration of a new mobile communication system according to an embodiment of the present disclosure.

Referring to fig. 2C, the radio access network of the new mobile communication system (hereinafter referred to as New Radio (NR) or fifth generation (5G)) is composed of a new radio node B (hereinafter referred to as NR gbb or NR base station) 2C-10 and a new radio core network (hereinafter referred to as NR CN) 2C-05. The new radio user equipment (hereinafter referred to as NR UE or terminal) 2c-15 accesses the external network through NR gbb 2c-10 and NR CN 2 c-05.

In fig. 2C, NR gNB 2C-10 corresponds to an evolved node B (eNB) of the LTE system. The NR gNB 2c-10 is connected to the NR UE 2c-15 through a radio channel and can provide excellent service, compared to an eNB according to the related art. In NR, all user traffics are provided through a shared channel, and thus, an apparatus for obtaining and scheduling pieces of status information (including a buffer status, an available transmission power status, a channel status, etc.) of a UE is required, and NR gNB 2c-10 corresponds to the apparatus. Typically, one NR gNB 2c-10 controls a plurality of cells. Compared to the existing LTE system, a bandwidth greater than the maximum bandwidth of the existing LTE can be given to achieve high-speed data transmission, and a beamforming technique can be added to a radio access technology such as OFDM.

In addition, NR uses an AMC technique that determines a modulation scheme and a channel coding rate according to a channel state of a UE. The NR CN 2c-05 performs functions of supporting mobility, configuring bearers, configuring quality of service (QoS), and the like. The NR CN 2c-05 is a device configured to perform not only a mobility management function for the UE but also various control functions for the UE, and is connected to a plurality of NBs. In addition, the NR may interoperate with the LTE system, and the NR CN 2c-05 is connected to the MME 2c-25 via a network interface. The MME 2c-25 is connected to the eNB 2c-30 which is an existing base station.

Fig. 2D is a diagram illustrating a radio protocol architecture of a new mobile communication system according to an embodiment of the present disclosure.

Referring to fig. 2D, the radio protocol of the new mobile communication system is composed of NR Service Data Access Protocols (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.

The primary functions of NR SDAP 2d-01 and 2d-45 may include some of the following functions.

-transmission of user plane data.

-mapping between quality of service (QoS) flows and data bearers for both downlink and uplink.

-marking the QoS flow Identification (ID) in both downlink and uplink data packets.

-mapping of reflected QoS flows to data bearers for uplink SDAP PDUs.

Regarding the SDAP entity, the UE may be configured to use a header of the SDAP entity or a function of the SDAP entity according to each PDCP entity, each bearer, or each logical channel through a Radio Resource Control (RRC) message. When the SDAP header is configured, the SDAP header may instruct the UE to update or reconfigure mapping information on QoS flows and data bearers for both uplink and downlink by using a 1-bit indicator of a non-access stratum (NAS) reflective QoS configuration and a 1-bit indicator of an Access Stratum (AS) reflective QoS configuration. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used as data processing priority order, scheduling information, etc. used in supporting the smooth service.

The primary functions of the NR PDCP 2d-05 and 2d-40 can include some of the following functions.

Header compression and decompression (ROHC only).

-transmission of user data.

-in-order delivery of upper layer PDUs.

-out of order delivery of upper layer PDUs.

-reordering for received PDCP PDUs.

Duplicate detection of lower layer SDUs.

-retransmission of PDCP SDUs.

-encryption and decryption functions.

Timer based SDU discard in uplink.

In the above, reordering for reception of NR PDCP 2d-05 and 2d-40 may refer to a function of sequential reordering of PDCP PDUs received from a lower layer based on a PDCP Sequence Number (SN), and may include the following functions: a function of transferring data to an upper layer in a reordered order or directly without regard to the order, a function of reordering the order and recording the lost PDCP PDUs, a function of transmitting a status report on the lost PDCP PDUs to a transmitter, and a function of requesting retransmission of the lost PDCP PDUs.

The primary functions of the NR RLC 2d-10 and 2d-35 may include at least some of the following functions.

-transmission of upper layer PDUs.

-in-order delivery of upper layer PDUs.

-out of order delivery of upper layer PDUs.

Error correction by ARQ.

Concatenation, segmentation and reassembly of RLC SDUs.

-re-segmentation of RLC data PDUs.

-reordering of RLC data PDUs.

-a duplicate detection function.

-protocol error detection.

RLC SDU discard.

RLC re-establishment.

In this regard, the sequential delivery of the nrrlc 2d-10 and 2d-35 may refer to a function of sequentially delivering RLC Service Data Units (SDUs) received from a lower layer to an upper layer, and may include the following functions: the function of reassembling and delivering a plurality of RLC SDUs when one RLC SDU, which has been segmented into a plurality of RLC SDUs, is received, has a function of reordering received RLC PDUs according to RLC Sequence Numbers (SNs) or PDCP SNs, a function of reordering the order and recording missing RLC PDUs, a function of transmitting a status report on the missing RLC PDUs to a transmitter, and a function of requesting retransmission of the missing RLC PDUs. The in-order delivery may include a function of sequentially delivering only RLC SDUs preceding the missing RLC SDU to an upper layer when there is the missing RLC SDU, and may include a function of sequentially delivering all RLC SDUs received before the preset timer is started to the upper layer when the preset timer expires or may include a function of sequentially delivering all RLC SDUs received so far to the upper layer when the timer expires even when there is the missing RLC SDU. In addition, the NR RLC 2d-10 and 2d-35 may process RLC PDUs in the order of reception (order of arrival, regardless of the order of sequence numbers) and may transfer the RLC PDUs to the NR PDCP 2d-05 and 2d-40, regardless of the order (out-of-order delivery), and in the case of segmentation, the NR RLC 2d-10 and 2d-35 may receive the segmentation stored in the buffer, or the segmentation to be received later, may reconstruct the segments into one RLC PDU, and may then process and transfer the RLC PDU to the NR PDCP 2d-05 and 2d-40. The NR RLC 2d-10 and 2d-35 may not include the concatenation function. The concatenation function may be performed by the NR MAC 2d-15 and 2d-30 or may be replaced by the multiplexing function of the NR MAC 2d-15 and 2 d-30.

The out-of-order delivery of the nrrlc 2d-10 and 2d-35 may refer to a function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of order. Out-of-order delivery may include the function of reassembling and delivering multiple RLC SDUs when one RLC SDU, which has been segmented into multiple RLC SDUs, is received. Further, the out-of-order delivery may include functions of storing and performing ordering of RLC SNs or PDCP SNs of received RLC PDUs, and recording missing RLC PDUs.

The NR MACs 2d-15 and 2d-30 may be connected to a plurality of NR RLC entities configured in one UE, and the main functions of the NR MACs 2d-15 and 2d-30 may include some of the following functions.

-mapping between logical channels and transport channels.

-multiplexing/demultiplexing of MAC SDUs.

-a scheduling information reporting function.

Error correction by HARQ.

-priority handling between logical channels of one UE.

-priority handling between UEs by dynamic scheduling.

-MBMS service identity.

-transport format selection.

-filling.

The PHYs 2d-20 and 2d-25 perform an operation of channel-coding and modulating upper layer data and transmitting OFDM symbols through a radio channel by converting the upper layer data into the OFDM symbols, or an operation of demodulating and channel-decoding OFDM symbols received through the radio channel and transmitting the decoded data to the upper layer.

In new mobile communication systems, integrity protection and verification may be performed by the data bearer that transmits the data. The PDCP layer, which processes data transmitted/received to/from the data bearer, performs ciphering and deciphering with high complexity, and the process of integrity protection and verification also requires high complexity. Therefore, in order to reduce the complexity of data processing, an effective integrity protection and verification process is required.

The present disclosure provides a method of reducing data processing complexity in a wireless communication system with respect to a signaling radio bearer or a Data Radio Bearer (DRB) in which integrity protection and integrity verification are configured.

Fig. 2E is a diagram illustrating a procedure performed by the gNB to indicate whether to perform Uplink Data Compression (UDC) when the UE establishes a connection to the network according to an embodiment of the present disclosure.

Fig. 2E illustrates a procedure in which a base station (gNB) requests UDC when a UE in an RRC idle mode or an RRC inactive (or lightly connected) mode switches to an RRC connected mode and establishes a connection to a network.

Referring to fig. 2E, when the UE transceiving data in the RRC connected mode does not transceive data for some reason or for a certain time, the gNB transmits an RRCConnectionRelease message to the UE to switch to the RRC idle mode (operation 2E-01). Thereafter, when a UE that has not established a connection with the base station (hereinafter referred to as an 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 transmits an RRCConnectionRequest message to the gNB (operation 2 e-05). The RRCConnectionRequest message may include an identifier of the idle mode UE, an establishment cause, and the like. The gNB transmits an RRCConnectionSetup message so that the idle mode UE establishes an RRC connection (operation 2 e-10). The RRCConnectionSetup message may include information indicating whether to use UDC for each logical channel (LogicalChannelConfig), each bearer, or each PDCP layer (PDCP-Config). In more detail, for each logical channel, each bearer, or each PDCP layer (or each Service Data Access Protocol (SDAP) layer), the RRCConnectionSetup message may indicate for which IP flow or QoS flow the UDC method is to be used (the RRCConnectionSetup message may configure information to the SDAP layer, the information being information about IP flows or QoS flows in which the UDC method is to be used or not, and then the SDAP layer may indicate whether the PDCP layer uses the UDC method for each QoS flow. In addition, the RRCConnectionSetup message may include an uplink data decompression setup or release command. In this regard, when configured to use UDC, a UE may always be configured with an RLC AM bearer (lossless mode due to ARQ functionality or retransmission functionality) and may not be configured with a header compression protocol (e.g., robust header compression (ROHC) protocol). In addition, the RRCConnectionSetup message may include information indicating whether the function of the SDAP entity is to be used or whether an SDAP header is to be used for each logical channel (LogicalChannelConfig), each bearer, or each PDCP device (PDCP-Config). The RRCConnectionSetup message may include information indicating whether ROHC (IP packet header compression) is applied to each logical channel (logical channel configuration), each bearer, or each PDCP device (PDCP-configuration), and configure whether ROHC is applied to the corresponding uplink and downlink by using the respective indicators. However, ROHC and UDC cannot be configured in one PDCP entity, one logical channel, or one bearer at the same time, and UDC can be configured in no more than two bearers. In addition, the RRCConnectionSetup message may include information indicating whether to apply integrity protection and integrity verification to each logical channel (logical channel configuration), each bearer, or each PDCP device (PDCP-configuration), and may configure integrity protection and integrity verification in consideration of a maximum data transmission rate of the corresponding PDCP entity, the corresponding bearer, or the corresponding logical channel. When UDC, header compression (ROHC), or integrity protection is configured in each logical channel, each bearer, or each PDCP device, its use may be configured for each of uplink and downlink. That is, it may be configured such that the uplink uses it and the downlink does not use it, or the uplink does not use it and the downlink uses it. In addition, the RRCConnectionSetup message may include RRC connection configuration information. The RRC connection may refer to a Signaling Radio Bearer (SRB) and may be used when transceiving an RRC message, which is a control message between the UE and the gNB. The UE establishes an RRC connection and then transmits an rrcconnectionsetupcomplete message to the gNB (operations 2 e-15). In the event that the gNB does not know or wish to check the capabilities of the currently connected UE, the gNB may send a UE capabilities query message. The UE may send a UE capability report message. The UE capability report message may include an indicator indicating whether the UE is capable of using the UDC method, ROHC, or integrity protection. The rrcconnectionsetupcomplete message may include a control message such as a SERVICE REQUEST message for requesting, by the UE, the MME to configure a bearer for a specific SERVICE.

The gNB transmits a SERVICE REQUEST message included in the rrcconnectionsetupcomplete message to the MME (operations 2 e-20), and the MME determines whether to provide the SERVICE requested by the UE. As a result of the determination, when the MME decides to provide the service requested by the UE, the MME sends an INITIAL CONTEXT SETUP REQUEST (INITIAL CONTEXT SETUP REQUEST message) to the gNB (operations 2 e-25). The INITIAL CONTEXT SETUP REQUEST message includes QoS information to be applied when configuring a Data Radio Bearer (DRB), security information (e.g., security key, security algorithm, etc.) to be applied to the DRB, and the like.

The gsb exchanges SecurityModeCommand messages 2e-30 and SecurityModeComplete messages 2e-35 with the UE to configure the security mode. After the security mode is fully configured, the gNB transmits an RRCConnectionReconfiguration message to the UE (operations 2 e-40). The RRCConnectionReconfiguration message may include information indicating whether the UDC method is used for each logical channel (logical channelconfiguration), each bearer, or each PDCP layer (PDCP-configuration). In more detail, for each logical channel, each bearer, or each PDCP layer (or each SDAP layer), the RRCConnectionReconfiguration message may indicate for which IP flow or QoS flow the UDC method will be used (the RRCConnectionReconfiguration message may configure information for the SDAP layer about the IP flow or QoS flow in which the UDC method will or will not be used, and then the SDAP layer may indicate whether the PDCP layer uses the UDC method for each QoS flow. In this regard, when instructed to use the UDC method, an identifier of a predefined library or dictionary to be used in the UDC method or a size of a buffer to be used in the UDC method may be instructed. In addition, the RRCConnectionReconfiguration message may include an uplink data decompression setup or release command. In this regard, when configured to use UDC, a UE may always be configured with RLC AM bearers (lossless mode due to ARQ functionality or retransmission functionality) and may not be configured with a header compression protocol (e.g., ROHC) protocol). Further, the RRCConnectionReconfiguration message may include information indicating whether the function of the SDAP entity is to be used or whether an SDAP header is to be used for each logical channel (logical channelconfiguration), each bearer, or each PDCP device (PDCP-configuration). The RRCConnectionReconfiguration message may include information indicating whether ROHC (IP packet header compression) is applied to each logical channel (logical channel configuration), each bearer, or each PDCP device (PDCP-configuration), and configure whether ROHC is applied to the corresponding uplink and downlink by using the corresponding indicator. However, the ROHC and the UDC cannot be configured in one PDCP entity, one logical channel, or one bearer at the same time, and the UDC can be configured in no more than two bearers. In addition, the RRCConnectionReconfiguration message may include information indicating whether integrity protection and integrity verification are applied to each logical channel (logical channelconfiguration), each bearer, or each PDCP device (PDCP-configuration), and may be configured in consideration of a maximum data transmission rate of the corresponding PDCP entity, the corresponding bearer, or the corresponding logical channel. When UDC, header compression (ROHC), or integrity protection is configured in each logical channel, each bearer, or each PDCP device, its use may be configured for each of uplink and downlink. That is, it may be configured such that the uplink uses it and the downlink does not use it, or the uplink does not use it and the downlink uses it. In addition, the RRCConnectionReconfiguration message may include setting information on the DRB for processing user data, and the UE sets the DRB by using the setting information and transmits an RRCConnectionReconfiguration complete message to the gNB (operations 2 e-45).

The gNB COMPLETEs DRB SETUP with the UE, then sends an INITIAL CONTEXT SETUP COMPLETE message to the MME (operation 2 e-50), and the MME receives the message and then exchanges S1 BEARER SETUP (S1 BEARER SETUP) messages 2e-55 and S1 BEARER SETUP RESPONSE (S1 BEARER SETUP RESPONSE) messages 2e-60 with the S-GW to set up the S1 BEARER. The S1 bearer indicates a data transmission connection established between the S-GW and the gNB, and corresponds to a DRB in a one-to-one manner. When the above procedure is completed, the UE and the gNB transmit and receive data via the S-GW (operations 2e-65 and 2 e-70). The above general data transfer procedure includes three steps, i.e., RRC connection setup, security setup, and DRB setup. The gNB may transmit an RRCConnectionReconfiguration message to the UE in order to newly perform, add, or change the configuration of the UE (operations 2 e-75). The RRCConnectionReconfiguration message may include information indicating whether the UDC method is used for each logical channel (logical channel configuration), each bearer, or each PDCP layer (PDCP-configuration). In more detail, for each logical channel, each bearer, or each PDCP layer (or each SDAP layer), the RRCConnectionReconfiguration message may indicate for which IP flow or QoS flow the UDC method will be used (the RRCConnectionReconfiguration message may configure information to the SDAP layer about the IP flow or QoS flow in which the UDC method will or will not be used, and then the SDAP layer may indicate whether the PDCP layer uses the UDC method for each QoS flow. In addition, the RRCConnectionReconfiguration message may include an uplink data decompression setup or release command. In this regard, when configured to use UDC, it may always be configured with RLC AM bearers (lossless mode due to ARQ functionality or retransmission functionality) and may not be configured with a header compression protocol (e.g., ROHC protocol). In addition, the RCConnectionReconfiguration message may include information indicating whether a function of the SDAP entity or an SDAP header is used for each logical channel (logical channelconfiguration), each bearer, or each PDCP device (PDCP-configuration). The RCConnectionReconfiguration message may include information indicating whether ROHC (IP packet header compression) is applied to each logical channel (logical channel configuration), each bearer, or each PDCP device (PDCP-configuration), and configure whether ROHC is applied to the corresponding uplink and downlink by using the corresponding indicator. However, ROHC and UDC cannot be configured in one PDCP entity, one logical channel, or one bearer at the same time, and UDC can be configured in no more than two bearers. In addition, the RCConnectionReconfiguration message may include information indicating whether integrity protection and integrity verification are applied to each logical channel (logical channelconfiguration), each bearer, or each PDCP device (PDCP-configuration), and may configure integrity protection and integrity verification in consideration of a maximum data transmission rate of the corresponding PDCP entity, the corresponding bearer, or the corresponding logical channel. When UDC, header compression (ROHC), or integrity protection is configured in each logical channel, each bearer, or each PDCP device, its use may be configured for each of uplink and downlink. That is, it may be configured such that the uplink uses it and the downlink does not use it, or the uplink does not use it and the downlink uses it.

Figure 2F is a diagram illustrating processes and data structures for performing UDC according to an embodiment of the disclosure.

In fig. 2F, the uplink data 2F-05 may be generated as data corresponding to a service including video transmission, photo transmission, web browsing, voice over long term evolution (VoLTE), and the like. A plurality of data items generated in the application layer may be processed by a network data transport layer such as a transmission control protocol and internet protocol (TCP/IP) or a User Datagram Protocol (UDP) to configure each of the headers 2f-10 and 2f-15, and the plurality of data items may be transferred to the PDCP layer. When the PDCP layer receives data (PDCP SDU) from an upper layer, the PDCP layer may perform a procedure as described below.

In fig. 2E, when the RRC message 2E-10, 2E-40, or 2E-75 indicates that UDC is used in the PDCP layer, the PDCP layer performs UDC 2f-22 on PDCP SDUs as shown in 2f-20 to compress uplink data, may configure UDC header (header for compressed uplink data) 2f-25, may perform integrity protection when configured to perform integrity protection, may perform ciphering, and may configure PDCP header 2f-30, thereby generating PDCP SDUs. A PDCP entity including means for processing a UDC (UDC compressor/UDC decompressor) determines whether to perform a UDC 2f-22 procedure on each data according to the configuration of the RRC message, and uses the UDC compressor/UDC decompressor. The transmitting end performs data compression 2f-22 by using a UDC compressor in the PDCP layer of the transmitting end, and the receiving end performs data decompression by using a UDC decompressor in the PDCP layer of the receiving end.

The process of fig. 2F may be applied not only to compression of uplink data, but also to compression of downlink data, which is performed by the UE. In addition, the description of uplink data may be equally applied to downlink data.

Fig. 2G is a diagram for describing a UDC according to an embodiment of the present disclosure.

Fig. 2G shows a DEFLATE-based UDC algorithm, which is a lossless compression algorithm. According to the DEFLATE-based UDC algorithm, basically, uplink data can be compressed using a combination of the LZ77 algorithm and the huffman coding algorithm.

According to the LZ77 algorithm, an operation of finding repeated occurrences of data within a sliding window is performed, and when repeated occurrences within the sliding window are found, data compression is performed by expressing repeated data within the sliding window as its position and length. The sliding window, which is called a buffer in the UDC method, can be set to 8 kilobytes or 32 kilobytes. That is, a sliding window or buffer may record 8192 characters or 32768 characters, find repeated occurrences of data, and perform data compression by representing repeated data as its location and length. Therefore, since the LZ77 algorithm is a sliding window scheme, that is, since the subsequent data is encoded immediately after the previously encoded data in the buffer is updated, there may be a correlation between the subsequent data. Therefore, only when previously encoded data is normally decoded, subsequent data can be normally decoded. In this regard, a code compressed by using the LZ77 algorithm and expressed as a position and a length is compressed again by using the huffman coding algorithm. According to the huffman coding algorithm, by assigning the shortest code to the most frequent character and the longest code to the least frequent character, a repeated character can be found and data compression can be performed again. The huffman coding algorithm is a prefix coding algorithm and is an optimal coding scheme by which all codes can be uniquely decoded.

As described above, the transmitting end can configure the UDC header by encoding the original data 2g-05 using the LZ77 algorithm (2 g-10), updating the buffer 2g-15, and generating a checksum (checksum) bit of the contents (or data) of the buffer. The receiving end can use the checksum bit to determine the validity of the buffer status. The transmitting end may compress a code encoded using the LZ77 algorithm by using the huffman coding algorithm (2 g-20), and may transmit the compressed data as uplink data (2 g-25). The receiving end may perform a decompression process on compressed data received from the transmitting end in a reverse manner to the transmitting end. That is, based on the checksum bits of the UDC header, the receiving end may perform huffman decoding (2 g-30), may update the buffer (2 g-35), and may check the validity of the updated buffer. After determining that the checksum bits have no errors, the receiving end may decompress the data by performing decoding using the LZ77 algorithm (2 g-40) to reconstruct the original data, and pass the decompressed data to the upper layer (2 g-45).

As described above, since the LZ77 algorithm is a sliding window scheme, that is, since the subsequent data is encoded immediately after the previously encoded data in the buffer is updated, there may be a correlation between the subsequent data. Therefore, only when previously encoded data is normally decoded, subsequent data can be normally decoded. Accordingly, the PDCP layer of the receiving end may check PDCP sequence numbers of PDCP headers, may check UDC headers (check an indicator indicating whether to perform data compression), and may perform a data decompression process on compressed UDC data in ascending order of PDCP sequence numbers.

Fig. 2H illustrates a process and data structure for performing ROHC according to an embodiment of the disclosure.

In fig. 2F, the uplink data 2h-05 may be generated as data corresponding to services including video transmission, photo transmission, web browsing, voLTE, and the like. The plurality of data items generated in the application entity may be processed by a network data transport layer (e.g., TCP/IP or UDP) to configure each of the headers 2h-10 and 2h-15, and the plurality of data items may be transferred to the PDCP layer. When the PDCP layer receives data (PDCP SDU) from an upper layer, the PDCP layer may perform a procedure as described below.

In fig. 2E, when the RRC message 2E-10, 2E-40, or 2E-75 indicates that ROHC is used in the PDCP layer, the PDCP layer performs ROHC on PDCP SDUs as shown in 2h-20 to compress headers 2h-15 of received data of an upper layer and generate compressed headers 2h-25, may perform integrity protection when it is configured to perform integrity verification, may perform ciphering, and may configure PDCP headers 2h-30 to generate PDCP PDUs. The PDCP entity including the header compressor/header decompressor determines whether to perform header compression on each data according to the configuration of the RRC message, and uses the header compressor/header decompressor. At the transmitting end, the PDCP entity of the transmitting end performs data compression by using a header compressor, and at the receiving end, the PDCP entity of the receiving end performs data decompression by using a header decompressor.

The procedure of fig. 2H may be applied not only to compression of the header of uplink data but also to compression of the header of downlink data, which is performed by the UE. In addition, the description of uplink data may be equally applied to downlink data.

Fig. 2I illustrates a process in which the SDAP entity generates an SDAP header for data received from an upper layer, and the PDCP entity applies integrity protection to the SDAP header, and does not perform ciphering, according to an embodiment of the present disclosure.

In fig. 2I, in the case of being configured to use the functions of the SDAP entity or to use the SDAP header in an RRC message and being configured to perform integrity protection and integrity verification in an RRC message, such as the RRC message shown in fig. 2E (see 2E-10, 2E-40, or 2E-75), the SDAP entity may generate and configure an SDAP header, such as 2I-05, and may transmit the SDAP header to the PDCP entity when the SDAP entity receives data from an upper layer. When integrity protection is configured, the PDCP entity may perform integrity protection 2I-10 on PDCP SDUs (the SDAP header and the IP packets 2I-05) received from the upper layer SDAP entity, and may calculate a message authentication code (MAC-I) for integrity. When the MAC-I2I-15 is calculated, a PDCP COUNT value, an uplink or downlink indicator, a bearer indicator, a security key, a data part (which is integrity-protected), etc. may be input values of an integrity protection algorithm. The calculated MAC-I may be concatenated to the end of the data as shown in 2I-25. The MAC-I may have a certain size, for example a size of 4 bytes. In addition to the SDAP header (2I-30), the PDCP entity may perform ciphering 2I-20 on 2I-25 to which the MAC-I is concatenated, may generate, configure and concatenate a PDCP header to ciphered data (2I-35) to which the SDAP header has been concatenated, and may transfer the data to a lower layer. Then, the RLC entity and the MAC entity can perform data processing (2 i-40 and 2 i-45).

The receiving end removes the MAC header and the RLC header and then transfers the data to the PDCP layer, and the PDCP entity of the receiving end reads and then removes the PDCP header and performs decryption on the data part except for the SDAP header. Thereafter, the PDCP entity of the receiving end performs integrity verification on the SDAP header, the upper layer header (TCP/IP header), and the data part, and calculates a calculated MAC-I (X-MAC). When the X-MAC is calculated, the PDCP COUNT value, the uplink or downlink indicator, the bearer indicator, the security key, the data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The PDCP entity of the receiving end checks whether the value of the X-MAC is equal to the value of the MAC-I concatenated to the end of the data. When the two values are equal, the integrity verification is successful, but when the values of X-MAC and MAC-I are not equal, the integrity verification fails, and thus, the PDCP entity of the receiving end discards the data and must report the failure of the integrity verification to an upper layer (e.g., RRC layer).

Fig. 2J illustrates a process in which the SDAP entity generates an SDAP header for data received from an upper layer, and the PDCP entity does not perform integrity protection and ciphering on the SDAP header, according to an embodiment of the present disclosure.

In fig. 2J, in the case of being configured to use the function of the SDAP entity or to use the SDAP header in the RRC message and to perform integrity protection and integrity verification in the RRC message, such as the RRC message shown in fig. 2E (see 2E-10, 2E-40, or 2E-75), the SDAP entity may generate and configure the SDAP header, such as 2i-05, when the SDAP entity receives data from an upper layer, and may transmit the SDAP header to the PDCP entity. When integrity protection is configured, the PDCP entity may perform integrity protection 2I-10 only on data (IP packets) other than the SDAP header of the PDCP SDU (the SDAP header and the IP packets 2I-05) received from the upper layer SDAP entity, and may calculate MAC-I2 j-15. When the MAC-I is calculated, the PDCP COUNT value, the uplink or downlink indicator, the bearer indicator, the security key, the data part (on which integrity protection is performed), etc. may be input values of an integrity protection algorithm. The calculated MAC-I may be concatenated to the end of the data as shown at 2 j-20. The MAC-I may have a certain size, for example a size of 4 bytes. In addition to the SDAP header (2I-30), the PDCP entity may perform ciphering 2j-25 on 2j-20 to which the MAC-I is concatenated, may generate, configure and concatenate a PDCP header to the data (2 j-35), and may transfer the data to a lower layer. Then, the RLC entity and the MAC entity can perform data processing (2 j-40 and 2 j-45). Embodiments of the present disclosure are characterized in that the MAC-I is also encrypted.

The receiving end removes the MAC header and the RLC header and transfers the data to the PDCP layer, and the PDCP entity of the receiving end reads and then removes the PDCP header and the SDAP header and performs decryption on the data part (except for the SDAP header). In this regard, the MAC-I is also decrypted. Thereafter, the PDCP entity of the receiving end performs integrity verification on the upper header (TCP/IP header) and the data part and calculates a calculated MAC-I (X-MAC). When the X-MAC is calculated, the PDCP COUNT value, the uplink or downlink indicator, the bearer indicator, the security key, the data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The PDCP entity of the receiving end checks whether the value of the X-MAC is equal to the value of the MAC-I concatenated to the end of the data. When the two values are equal, the integrity verification succeeds, but when the values of X-MAC and MAC-I are not equal, the integrity verification fails, and thus, the PDCP entity of the receiving end discards the data and must report the failure of the integrity verification to an upper layer (e.g., RRC layer).

In this way, when ciphering or integrity protection is not performed on the SDAP header, the configuration of embodiments of the base station can be simplified, especially in a Central Unit (CU) -Distributed Unit (DU) structure split structure. When the CU does not encrypt the SDAP header, the DU may check the QoS information by reading the SDAP header and may apply the QoS information to the schedule, so it may be advantageous to match and adjust the QoS. Also, the foregoing features may have advantages in terms of data processing in the configuration of the UE and the base station.

Fig. 2K illustrates an advantage of the structure of the base station achieved by applying the SDAP header without performing encryption or integrity protection according to an embodiment of the present disclosure.

When the base station is implemented as in fig. 2K, in order to reduce initial facility cost and maintenance cost, upper layer entities (e.g., PDCP entities and upper layer entities of PDCP entities) may be implemented in a CU, and lower layer entities (e.g., lower layer entities of RLC entities and RLC entities) may be implemented in a plurality of DUs connected to the CU. In such a CU-DU separation structure, when the SDAP header that does not perform ciphering or integrity protection by the PDCP entity 2k-05 as described with reference to fig. 2J of the present disclosure is applied, the plurality of DUs 2k-15 can read the SDAP header 2k-10, and because the SDAP header 2k-10 is not performed ciphering or integrity protection, the QoS information can be checked and applied to the scheduling of the DU 2 k-15. Thus, it may be advantageous to match and adjust the QoS for each service because each of DUs 2k-15 may use the QoS information of SDAP headers 2k-10 to allocate transmission resources and perform scheduling.

Fig. 2L illustrates the advantages of processing that may be obtained from a base station and a UE by applying an SDAP header that is not subject to ciphering and integrity protection, in accordance with embodiments of the present disclosure.

In fig. 2L, the SDAP entity and the PDCP entity may be unified into one entity (2L-01) when the UE and the base station are implemented. Since the SDAP entity is logically an upper layer entity of the PDCP entity, when receiving data 2l-05 from an upper application layer, the SDAP entity must generate and configure the SDAP header when the SDAP entity receives data from the upper layer, as in 2J-05 of FIG. 2J, in the case of being configured to use the function of the SDAP entity or using the SDAP header in an RRC message and having integrity protection configured in the RRC message as shown in FIG. 2E (see 2E-10, 2E-40, or 2E-75). However, the ciphering process or the integrity protection process is an operation requiring a high degree of complexity in the implementation of the UE and the base station, which may be performed by applying a Hardware (HW) accelerator thereto. The hardware accelerator gains high advantage in processing from a repetitive and continuous process. 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, when a process of performing an integrity protection procedure and a ciphering procedure on a data part other than the SDAP header, generating the PDCP header, and concatenating the PDCP header to the SDAP header is performed, an interruption to the HW accelerator may occur due to an operation of generating the SDAP header before performing the integrity protection procedure and the ciphering procedure in the process.

Accordingly, the present disclosure describes a method of implementing an SDAP header that is not integrity protected and ciphered and implementing one entity by unifying SDAP and PDCP entities. That is, when data is received from an upper application layer, an integrity protection process (2 l-10) may be continuously and repeatedly performed each time data is received, a MAC-I may be calculated and then may be concatenated to the end of the data (2 l-15), a ciphering process (2 l-20) may be performed on the MAC-I and the data to which integrity protection is applied, a PDCP header and an SDAP header (2 l-25) may be simultaneously generated, and then may be concatenated to the data to which integrity protection and ciphering are performed, and then the data may be transferred to a lower layer. The generation of the PDCP header and the SDAP header may be processed in parallel with an integrity protection procedure or a ciphering procedure. In this regard, when the headers are generated in a parallel manner, the SDAP header, the PDCP header, or the RLC header or the MAC header may be generated together and may be concatenated to the beginning of data that has completely undergone data processing and may be ready for transmission (may be ready for configuration of the MAC PDU) at a time. Also, the receiving end may separate the SDAP header, the PDCP header, or the RLC header or the MAC header from the data at a time and read them, may recognize information corresponding to each layer, and may process the data in the reverse order of the data processing performed by the transmitting end. Accordingly, the HW accelerator can be continuously and repeatedly applied, and since an interrupt such as generation of the SDAP header does not occur therebetween, the efficiency of data processing can be improved. In addition, when integrity protection is configured, the HW accelerator may be applied to integrity protection as described with respect to the cryptographic process before the cryptographic process is performed, and thus the integrity protection may be repeatedly performed. That is, integrity protection may be performed and then an encryption process may be performed.

The PDCP entity of the receiving end may use a method of implementing one entity by unifying the SDAP entity and the PDCP entity, as in 2 l-01. That is, when data is received from a lower layer (RLC layer), in case of being configured to use the function of the SDAP entity or use the SDAP header in an RRC message, such as the RRC message shown in fig. 2E (see 2E-10, 2E-40, or 2E-75), one of the SDAP and PDAP entities may read and remove the PDCP header and the SDAP header at a time, and may repeat the process of applying the deciphering code or deciphering code to the data. In addition, when integrity protection is configured, after the decryption process is performed, the HW accelerator may be applied to integrity verification as described with respect to the decryption process, and thus integrity verification may be repeatedly performed. That is, a decryption process may be performed, and then integrity verification may be performed.

Fig. 2M illustrates a process in which the SDAP entity generates an SDAP header for data received from an upper layer, and the PDCP entity does not perform integrity protection and ciphering on the SDAP header and does not perform ciphering on the MAC-I, according to an embodiment of the present disclosure.

In fig. 2M, in the case of being configured to use the function of the SDAP entity or to use the SDAP header in the RRC message and being configured to perform integrity protection and integrity verification in the RRC message, such as the RRC message shown in fig. 2E (see 2E-10, 2E-40, or 2E-75), the SDAP entity may generate and configure the SDAP header, such as 2M-05, when the SDAP entity receives data from an upper layer, and may transmit the SDAP header to the PDCP entity. When integrity protection is configured, the PDCP entity may perform integrity protection 2m-10 only on data (IP packets) other than the SDAP header of the PDCP SDU (the SDAP header and the IP packet 2 m-05) received from the upper layer SDAP entity, and may calculate MAC-I. When the MAC-I is calculated, a PDCP COUNT value, an uplink or downlink indicator, a bearer indicator, a security key, a data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The calculated MAC-I may be concatenated to the end of the data as shown by 2 m-20. The MAC-I may have a certain size, for example a size of 4 bytes. In addition to the SDAP header and the MAC-I (2 m-30 and 2 m-35), the PDCP entity may perform ciphering on 2m-25 to which the MAC-I is concatenated, may generate, configure and concatenate a PDCP header to data (2 m-40), and may transfer the data to a lower layer. Then, the RLC entity and the MAC entity can perform data processing (2 j-40 and 2 j-45). Embodiments of the present disclosure feature that the MAC-I is not encrypted. When the MAC-I is not encrypted, as will be described below, the advantages of data processing can be further obtained.

The receiving end removes the MAC header and the RLC header and then transfers the data to the PDCP layer, and the PDCP entity of the receiving end reads and then removes the PDCP header and the SDAP header and performs decryption on the data part (except for the last SDAP header and the MAC-I). In this regard, the MAC-I is not decrypted. Thereafter, the PDCP entity of the receiving end performs integrity verification on the upper header (TCP/IP header) and the data part (except for the SDAP header), and calculates a calculated MAC-I (X-MAC). When the X-MAC is calculated, the PDCP COUNT value, the uplink or downlink indicator, the bearer indicator, the security key, the data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The PDCP entity of the receiving end checks whether the value of the X-MAC is equal to the value of the MAC-I concatenated to the end of the data. When the two values are equal, the integrity verification succeeds, but when the values of X-MAC and MAC-I are not equal, the integrity verification fails, and thus, the PDCP entity of the receiving end discards the data and must report the failure of the integrity verification to an upper layer (e.g., RRC layer).

In this way, the configuration of embodiments of the base station can be simplified when no ciphering or integrity protection is performed on the SDAP header, especially in a CU-DU structure split structure, when the SDAP header is not ciphered by the CU, the DU can check the QoS information by reading the SDAP header and can apply the QoS information to the scheduling, so it may be advantageous to match and adjust the QoS. Also, the foregoing features may have advantages in terms of data processing in the configuration of the UE and the base station. In addition, when the MAC-I is not encrypted, as will be described below, the advantage of data processing can be further obtained.

Fig. 2N illustrates the processing advantages that may be obtained from a base station and UE by applying an SDAP header that is not subject to ciphering and integrity protection, and by not ciphering the MAC-I, according to one embodiment.

In fig. 2N, the SDAP entity and the PDCP entity may be unified into one entity (2N-01) when the UE and the base station are implemented. Since the SDAP entity is logically an upper layer entity of the PDCP entity, when receiving data 2n-05 from an upper application layer, the SDAP entity must generate and configure the SDAP header when the SDAP entity receives data from the upper layer, as in 2J-05 of FIG. 2J, in the case of being configured to use the function of the SDAP entity or using the SDAP header in an RRC message and having integrity protection configured in the RRC message as shown in FIG. 2E (see 2E-10, 2E-40, or 2E-75). However, the ciphering process or the integrity protection process is an operation requiring a high degree of complexity in the implementation of the UE and the base station, which can be performed by applying a Hardware (HW) accelerator thereto. HW accelerators gain high advantages in processing from repeated 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, when a process of performing an integrity protection procedure and a ciphering procedure on a data part other than the SDAP header, generating the PDCP header, and concatenating the PDCP header to the SDAP header is performed, an interruption of the HW accelerator may occur due to an operation of generating the SDAP header before performing the integrity protection procedure and the ciphering procedure.

Accordingly, the present disclosure describes a method of implementing an SDAP header and an MAC-I without ciphering that are not integrity protected and ciphered, and implementing one entity by unifying SDAP and PDCP entities. That is, when data is received from an upper application layer, an integrity protection process (2 n-10) may be continuously and repeatedly performed whenever data is received, MAC-I (2 n-20 and 2 n-25) may be calculated, a ciphering process may be performed on the data (2 n-30) to which integrity protection is applied, a PDCP header, an SDAP header, and MAC-I may be simultaneously generated and then may be concatenated to the data to which integrity protection and ciphering are performed, and then the data may be transferred to a lower layer (2 n-35). That is, the generated header may be concatenated to the beginning of the data, and the MAC-I may be concatenated to the end of the data. The generation of the PDCP header, the SDAP header, and the MAC-I may be processed in parallel with an integrity protection procedure or a ciphering procedure. In this regard, when the headers are generated in a parallel manner, an SDAP header, a PDCP header, or an RLC header or a MAC header may be generated together, and these headers may be concatenated to the beginning of data that has completely undergone data processing and may be ready for transmission (may be ready for configuration of MAC PDUs) at once. The MAC-I may be concatenated to the end of the data that has completely undergone data processing. Also, the receiving end may separate the SDAP header, the PDCP header, or the RLC header or the MAC header from the data at a time and read them, may recognize information corresponding to each layer, and may process the data in the reverse order of the data processing performed by the transmitting end. Accordingly, the HW accelerator can be continuously and repeatedly applied, and since an interrupt such as generation of the SDAP header does not occur therebetween, the efficiency of data processing can be improved. In addition, when integrity protection is configured, the HW accelerator may be applied to integrity protection as described with respect to the cryptographic process before the cryptographic process is performed, and thus the integrity protection may be repeatedly performed. That is, integrity protection may be performed and then an encryption process may be performed.

The PDCP entity of the receiving end may use a method of implementing one entity by unifying the SDAP entity and the PDCP entity, as in 2 l-01. That is, when data is received from a lower layer (RLC layer), in case of being configured to use the function of the SDAP entity or use the SDAP header in an RRC message, such as the RRC message shown in fig. 2E (see 2E-10, 2E-40, or 2E-75), one of the SDAP and PDAP entities may read and remove the PDCP header and the SDAP header at a time, and may repeat the process of applying no encryption or decryption to the data. In addition, when integrity protection is configured, after the decryption process is performed, the HW accelerator may be applied to integrity verification as described with respect to the decryption process, and thus integrity verification may be repeatedly performed. That is, a decryption process may be performed, and then integrity verification may be performed.

Fig. 2O illustrates a process in which the SDAP entity generates an SDAP header for data received from an upper layer, and the PDCP entity performs header compression (i.e., ROHC), applies integrity protection to the SDAP header, and does not perform ciphering on the SDAP header, according to an embodiment of the present disclosure.

In fig. 2O, when configured to use the function of the SDAP entity or use the SDAP header in the RRC message, configured to perform integrity protection and integrity verification in the RRC message, and configured to perform ROHC for uplink or downlink in the RRC message, as shown in fig. 2E (see 2E-10, 2E-40, or 2E-75) for the RRC message, when the SDAP entity receives data from an upper layer, the SDAP entity may generate and configure the SDAP header as in 2O-05, and may transmit the SDAP header to the PDCP entity. The PDCP entity performs ROHC on an upper header (e.g., IP data header) of the received PDCP SDU (2 o-10). When integrity protection is configured, the PDCP entity may perform integrity protection 2o-20 on PDCP SDUs (SDAP header and IP packet 2 o-05) received from an upper layer SDAP entity and applied with ROHC, and may calculate MAC-I (2 o-25). When the MAC-I is calculated, a PDCP COUNT value, an uplink or downlink indicator, a bearer indicator, a security key, a data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The calculated MAC-I may be concatenated to the end of the data as shown by 2 o-30. The MAC-I may have a certain size, for example a size of 4 bytes. In addition to the SDAP header (2 o-40), the PDCP entity may perform ciphering 2o-35 on the 2o-30 to which the MAC-I is concatenated, may generate, configure and concatenate the PDCP header to the data (2 o-45), and may transfer the data to a lower layer. Then, the RLC entity and the MAC entity may perform data processing.

The receiving end removes the MAC header and the RLC header and then transfers the data to the PDCP layer, and the PDCP entity of the receiving end reads and then removes the PDCP header and performs decryption on the data part except for the SDAP header. Thereafter, the PDCP entity of the receiving end performs integrity verification on the SDAP header, the upper layer header (TCP/IP header), and the data part, and calculates X-MAC. When the X-MAC is calculated, the PDCP COUNT value, the uplink or downlink indicator, the bearer indicator, the security key, the data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The PDCP entity of the receiving end checks whether the value of the X-MAC is equal to the value of the MAC-I concatenated to the end of the data. When the two values are equal, the integrity verification is successful, but when the values of X-MAC and MAC-I are not equal, the integrity verification fails, and thus, the PDCP entity of the receiving end discards the data and must report the failure of the integrity verification to an upper layer (e.g., RRC layer). When the integrity verification is completed, an ROHC decompression process may be performed on an upper layer header (e.g., an IP packet header) and the reconstructed upper layer data may be delivered to the upper layer.

Fig. 2P illustrates a process in which the SDAP entity generates an SDAP header for data received from an upper layer, and the PDCP entity performs header compression (i.e., ROHC) and does not perform integrity protection and ciphering on the SDAP header, according to an embodiment of the present disclosure.

In fig. 2P, when configured to use the function of the SDAP entity or to use the SDAP header in an RRC message, configured to perform integrity protection and integrity verification in an RRC message, configured to perform ROHC for uplink or downlink in an RRC message as shown in fig. 2E (see 2E-10, 2E-40, or 2E-75), the SDAP entity may generate and configure the SDAP header as in 2P-05 when the SDAP entity receives data from an upper layer, and may transmit the SDAP header to the PDCP entity. The PDCP entity performs ROHC 2p-10 for an upper header (e.g., IP data header) of the received PDCP SDU (2 p-15). When integrity protection is configured, the PDCP entity may perform integrity protection 2p-20 only on data (IP packets) other than the SDAP header of PDCP SDUs (the SDAP header and the IP packets 2 p-25), which are received from an upper layer SDAP entity and to which ROHC is applied, and may calculate MAC-I (2 p-30). When the MAC-I is calculated, a PDCP COUNT value, an uplink or downlink indicator, a bearer indicator, a security key, a data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The calculated MAC-I may be concatenated to the end of the data as shown by 2 p-35. The MAC-I may have a certain size, for example a size of 4 bytes. In addition to the SDAP header (2 p-45), the PDCP entity may perform ciphering 2p-40 on 2p-35 to which the MAC-I is concatenated, may generate, configure and concatenate the PDCP header to data (2 p-50), and may transfer the data to a lower layer. Then, the RLC entity and the MAC entity may perform data processing. Embodiments of the present disclosure are characterized in that the MAC-I is also encrypted.

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

The receiving end removes the MAC header and the RLC header and transfers the data to the PDCP layer, and the PDCP entity of the receiving end reads and then removes the PDCP header and the SDAP header and performs decryption on the data part (except for the SDAP header). In this regard, the MAC-I is also decrypted. Thereafter, the PDCP entity of the receiving end performs integrity verification on the upper header (TCP/IP header) and the data part (except for the SDAP header), and calculates a calculated MAC-I (X-MAC). When the X-MAC is calculated, the PDCP COUNT value, the uplink or downlink indicator, the bearer indicator, the security key, the data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The PDCP entity of the receiving end checks whether the value of the X-MAC is equal to the value of the MAC-I concatenated to the end of the data. When the two values are equal, the integrity verification is successful, but when the values of X-MAC and MAC-I are not equal, the integrity verification fails, and thus, the PDCP entity of the receiving end discards the data and must report the failure of the integrity verification to an upper layer (e.g., RRC layer). When integrity verification is complete, a ROHC decompression process may be performed on an upper layer header (e.g., an IP packet header) and reconstructed upper layer data may be delivered to the upper layer.

In this way, the configuration of embodiments of the base station may be simplified when no ciphering or integrity protection is performed on the SDAP header, especially in a CU-DU split structure, when the SDAP header is not ciphered by the CU, the DU may check the QoS information by reading the SDAP header and may apply the QoS information to the scheduling, so it may be advantageous to match and adjust the QoS. Also, the foregoing features may have advantages in terms of data processing in the configuration of the UE and the base station.

In addition, as described above, when ROHC is not performed on the SDAP header, the configuration of the embodiment of the base station can be simplified, especially in the CU-DU split structure, when the SDAP header is not encrypted by the CU, the DU can check the QoS information by reading the SDAP header and can apply the QoS information to the scheduling, and thus it may be advantageous to match and adjust the QoS. Also, the foregoing features may have advantages in terms of data processing in the configuration of the UE and the base station.

Fig. 2Q illustrates the advantages of processing that may be obtained from a base station and a UE by applying an SDAP header that is not subject to ciphering and integrity protection, according to an embodiment of the present disclosure.

In fig. 2Q, the SDAP entity and the PDCP entity may be unified into one entity (2Q-01) when the UE and the base station are implemented. Since the SDAP entity is logically an upper layer entity of the PDCP entity, when receiving data 2q-05 from an upper application layer, the SDAP entity must generate and configure the SDAP header when the SDAP entity receives data from the upper layer, as in 2J-05 of FIG. 2J, in the case of being configured to use the function of the SDAP entity or using the SDAP header in an RRC message and having integrity protection configured in the RRC message as shown in FIG. 2E (see 2E-10, 2E-40, or 2E-75). However, the ciphering process or the integrity protection process is an operation requiring a high degree of complexity in the implementation of the UE and the base station, which can be performed by applying a HW accelerator thereto. HW accelerators gain high advantages from a repetitive and continuous process. 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, when a process of performing an integrity protection procedure and a ciphering procedure on a data part other than the SDAP header, generating the PDCP header, and concatenating the PDCP header to the SDAP header is performed, an interruption of the HW accelerator may occur due to an operation of generating the SDAP header before performing the integrity protection procedure and the ciphering procedure.

Accordingly, the present disclosure describes a method of implementing an SDAP header that is not integrity protected and ciphered, and implementing one entity by unifying SDAP and PDCP entities. That is, when data is received from an upper application layer, ROHC 2q-10 can be continuously and repeatedly performed on an upper layer header part (e.g., IP packet header) of a received PDCP SDU whenever data is received. Then, as shown in 2q-20, an integrity protection process may be performed on the PDCP SDU to which the header compression is applied, MAC-I may be calculated (2 q-25), and then MAC-I may be concatenated to the end of the data (2 q-30), a ciphering process (2 q-35) may be performed on the MAC-I and the integrity-protected data, a PDCP header and an SDAP header may be simultaneously generated (2 q-40), and then may be concatenated to the integrity-protected and ciphered data, and then the data may be transferred to a lower layer. The generation of the PDCP header and the SDAP header may be processed in parallel with an integrity protection procedure or a ciphering procedure. In this regard, when the headers are generated in a parallel manner, an SDAP header, a PDCP header, or an RLC header or a MAC header may be generated together, and these headers may be concatenated to the beginning of data that has completely undergone data processing and may be ready for transmission (may be ready for configuration of MAC PDUs) at once. The MAC-I may be concatenated to the end of the data that has completely undergone data processing. Also, the receiving end may separate the SDAP header, the PDCP header, or the RLC header or the MAC header from the data at a time and read them, may recognize information corresponding to each layer, and may process the data in the reverse order of the data processing performed by the transmitting end. Accordingly, the HW accelerator can be continuously and repeatedly applied, and since an interrupt such as generation of the SDAP header does not occur therebetween, the efficiency of data processing can be improved. In addition, when integrity protection is configured, the HW accelerator may be applied to integrity protection as described with respect to the cryptographic process before the cryptographic process is performed, and thus the integrity protection may be repeatedly performed. That is, integrity protection may be performed and then an encryption process may be performed.

The PDCP entity of the receiving end may use a method of implementing one entity by unifying the SDAP entity and the PDCP entity as in 2 q-01. That is, when data is received from a lower layer (RLC layer), in case of being configured to use the function of the SDAP entity or use the SDAP header in an RRC message, such as the RRC message shown in fig. 2E (see 2E-10, 2E-40, or 2E-75), one of the SDAP and PDAP entities may read and remove the PDCP header and the SDAP header at a time, and may repeat the process of applying the decryption or decryption to the data. In addition, when integrity protection is configured, after the decryption process is performed, the HW accelerator may be applied to integrity verification as described with respect to the decryption process, and thus integrity verification may be repeatedly performed. That is, a decryption process may be performed, and then integrity verification may be performed. When integrity verification is complete, a ROHC decompression process may be performed on an upper layer header (e.g., an IP packet header) and reconstructed upper layer data may be delivered to the upper layer.

Fig. 2R illustrates a process in which the SDAP entity generates an SDAP header for data received from an upper layer, and the PDCP entity performs header compression (i.e., ROHC), does not perform integrity protection and ciphering on the SDAP header, and does not perform ciphering on the MAC-I, according to an embodiment of the present disclosure.

In fig. 2R, when configured to use the function of the SDAP entity or to use the SDAP header in an RRC message, configured to perform integrity protection and integrity verification in an RRC message, configured to perform ROHC for uplink or downlink in an RRC message as shown in fig. 2E (see 2E-10, 2E-40, or 2E-75), the SDAP entity may generate and configure the SDAP header as in 2R-05 when the SDAP entity receives data from an upper layer, and may transmit the SDAP header to the PDCP entity. The PDCP entity performs ROHC 2r-10 on an upper header (e.g., IP packet header) of the received PDCP SDU. When integrity protection is configured, the PDCP entity may perform integrity protection 2r-20 only on data (IP packets) other than the SDAP header of PDCP SDUs (the SDAP header and the IP packets 2 r-15), which are received from the upper layer SDAP entity and to which ROHC is applied, and may calculate MAC-I. When the MAC-I2 r-30 is calculated, the PDCP COUNT value, the uplink or downlink indicator, the bearer indicator, the security key, the data part (with integrity protection performed) 2r-25, etc. may be input values of the integrity protection algorithm. The calculated MAC-I may be concatenated to the end of the data as shown by 2 r-35. The MAC-I may have a certain size, for example, a size of 4 bytes (or 4 bits). The PDCP entity may perform ciphering (2 r-45) on 2r-40 (except for the SDAP header) and parts except for the MAC-I to which the MAC-I is concatenated, may generate, configure and concatenate a PDCP header to data (2 r-50), and may transfer the data to a lower layer. Then, the RLC entity and the MAC entity may perform data processing. Embodiments of the present disclosure are characterized in 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.

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

The receiving end removes the MAC header and the RLC header and transfers the data to the PDCP layer, and the PDCP entity of the receiving end reads and then removes the PDCP header and the SDAP header and performs decryption on the data part (except for the MAC-I at the end and the SDAP header). In this regard, the MAC-I is not decrypted. Thereafter, the PDCP entity of the receiving end performs integrity verification on the upper header (TCP/IP header) and the data part (except for the SDAP header), and calculates a calculated MAC-I (X-MAC). When the X-MAC is calculated, the PDCP COUNT value, the uplink or downlink indicator, the bearer indicator, the security key, the data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The PDCP entity of the receiving end checks whether the value of the X-MAC is equal to the value of the MAC-I concatenated to the end of the data. When the two values are equal, the integrity verification succeeds, but when the values of X-MAC and MAC-I are not equal, the integrity verification fails, and thus, the PDCP entity of the receiving end discards the data and must report the failure of the integrity verification to an upper layer (e.g., RRC layer). When the integrity verification is completed, an ROHC decompression process may be performed on an upper layer header (e.g., an IP packet header) and the reconstructed upper layer data may be delivered to the upper layer.

In this way, the configuration of embodiments of the base station can be simplified when no ciphering or integrity protection is performed on the SDAP header, especially in a CU-DU structure split structure, when the SDAP header is not ciphered by the CU, the DU can check the QoS information by reading the SDAP header and can apply the QoS information to the scheduling, so it may be advantageous to match and adjust the QoS. Also, the foregoing features may have advantages in terms of data processing in the configuration of the UE and the base station. When the MAC-I is not encrypted as described above, an advantage in data processing can be further obtained as described below.

In addition, as described above, when ROHC is not performed on the SDAP header, the configuration of the embodiment of the base station can be simplified, especially in the CU-DU structure separation structure, when the SDAP header is not encrypted by the CU, the DU can check the QoS information by reading the SDAP header and can apply the QoS information to the scheduling, and thus it may be advantageous to match and adjust the QoS. Also, the foregoing features may have advantages in terms of data processing in the configuration of the UE and the base station.

Fig. 2S illustrates advantages in processing that may be obtained from a base station and a UE by applying an SDAP header that is not subject to ciphering and integrity protection, by applying ROHC, and by not ciphering the MAC-I, according to embodiments of the present disclosure.

In fig. 2S, the SDAP entity and the PDCP entity may be unified into one entity (2S-01) when the UE and the base station are implemented. Since logically, the SDAP entity is an upper layer entity of the PDCP entity, when data 2s-01 is received from an upper application layer, the SDAP entity must generate and configure the SDAP header when being configured to use a function of the SDAP entity or use the SDAP header and configured integrity protection in an RRC message, and in case of being configured to perform ROHC for uplink or downlink in an RRC message as shown in FIG. 2E (see 2E-10, 2E-40, or 2E-75), when the SDAP entity receives data from the upper layer, as 2J-05 of FIG. 2J. However, the ciphering process or the integrity protection process is an operation requiring a high degree of complexity in the implementation of the UE and the base station, which can be performed by applying a HW accelerator thereto. HW accelerators gain high advantages in processing from repeated 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, when a process of performing an integrity protection procedure and a ciphering procedure on a data part other than the SDAP header, generating the PDCP header, and concatenating the PDCP header to the SDAP header is performed, an interruption to the HW accelerator may occur due to an operation of generating the SDAP header before performing the integrity protection procedure and the ciphering procedure.

Accordingly, the present disclosure describes a method of implementing an SDAP header that is not integrity protected and ciphered, implementing MAC-I that is not ciphered, and implementing one entity by unifying SDAP and PDCP entities. That is, 2s-05 when data is received from an upper application layer, ROHC (2 s-10) may be continuously and repeatedly performed on an upper layer header part (e.g., IP packet header) of a received PDCP SDU whenever the data is received, integrity protection procedure (2 s-15) may be performed, MAC-I (2 s-25 and 2 s-30) may be calculated on the data 2s-20, a ciphering procedure (2 s-40) may be performed (2 s-35) on the data to which integrity protection is applied, a PDCP header, an SDAP header, and MAC-I may be simultaneously generated and then may be concatenated to the data to which integrity protection and ciphering are performed, and then the data may be transferred to a lower layer (2 s-45). That is, the generated header may be concatenated to the beginning of the data, and the MAC-I may be concatenated to the end of the data. The generation of the PDCP header, the SDAP header, and the MAC-I may be processed in parallel with an integrity protection procedure or a ciphering procedure. In this regard, when the headers are generated in a parallel manner, the SDAP header, the PDCP header, or the RLC header or the MAC header may be generated together and may be concatenated to the beginning of data that has completely undergone data processing and may be ready for transmission (may be ready for configuration of the MAC PDU) at a time. The MAC-I may be concatenated to the end of the data that has completely undergone data processing. Also, the receiving end may separate the SDAP header, the PDCP header, or the RLC header or the MAC header from the data at a time and read them, may recognize information corresponding to each layer, and may process the data in the reverse order of the data processing performed by the transmitting end. Accordingly, the HW accelerator can be continuously and repeatedly applied, and since an interrupt such as generation of the SDAP header does not occur therebetween, the efficiency of data processing can be improved. In addition, when integrity protection is configured, the HW accelerator may be applied to integrity protection as described with respect to the cryptographic process before the cryptographic process is performed, and thus the integrity protection may be repeatedly performed. That is, integrity protection may be performed and then an encryption process may be performed.

The PDCP entity of the receiving end may use a method of implementing one entity by unifying the SDAP entity and the PDCP entity, as in 2 l-01. That is, when data is received from a lower layer (RLC layer), in case of being configured to use a function of the SDAP entity or use the SDAP header in an RRC message, such as the RRC message shown in fig. 2E (see 2E-10, 2E-40, or 2E-75), one of the SDAP and PDAP entities may read and remove the PDCP header and the SDAP header at a time, and may repeat a process of applying no encryption or decryption to the data. In addition, when integrity protection is configured, after the decryption process is performed, the HW accelerator may be applied to integrity verification as described with respect to the decryption process, and thus integrity verification may be repeatedly performed. That is, a decryption process may be performed, and then integrity verification may be performed. When integrity verification is complete, a ROHC decompression process may be performed on an upper layer header (e.g., an IP packet header) and reconstructed upper layer data may be delivered to the upper layer.

Fig. 2T illustrates a process in which the SDAP entity generates an SDAP header for data received from an upper layer, and the PDCP entity performs UDC, applies integrity protection to the UDC header, performs ciphering to the UDC header, applies integrity protection to the SDAP header, and does not perform ciphering to the SDAP header, according to an embodiment of the disclosure.

In fig. 2T, when configured to use the function of the SDAP entity or use the SDAP header in the RRC message, configured to perform integrity protection and integrity verification in the RRC message, and configured to perform UDC for uplink or downlink in the RRC message, as shown in fig. 2E (see 2E-10, 2E-40, or 2E-75) in the RRC message, when the SDAP entity receives data from an upper layer, the SDAP entity may generate and configure the SDAP header as in 2T-05, and may transmit the SDAP header to the PDCP entity. The PDCP entity performs UDC (2 t-10) on a part of the received PDCP SDU (e.g., IP data header) except for the SDAP header. Then, the PDCP entity may calculate a checksum field based on the current UDC buffer 2t-15, may configure the UDC header, and may concatenate the UDC header to the beginning of the SDAP header, as shown at 2 t-20. When integrity protection is configured, the PDCP entity may perform integrity protection 2t-25 on 2t-20 (including the UDC header, the SDAP header, and the UDC block) received from the upper-layer SDAP entity and to which the UDC is applied and to which the UDC header is concatenated, and may calculate MAC-I (2 t-35) from the data 2 t-30. When the MAC-I is calculated, a PDCP COUNT value, an uplink or downlink indicator, a bearer indicator, a security key, a data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The calculated MAC-I may be concatenated to the end of the data as shown at 2 t-40. The MAC-I may have a certain size, for example a size of 4 bytes. In addition to the SDAP header, the PDCP entity may perform ciphering (2 t-45) on 2t-40 to which the MAC-I is concatenated, may generate, configure and concatenate a PDCP header to data (2 t-50), and may transfer the data to a lower layer. Then, the RLC entity and the MAC entity may perform data processing.

The receiving end removes the MAC header and the RLC header and then transfers the data to the PDCP layer, and the PDCP entity of the receiving end reads and then removes the PDCP header and performs decryption on the data part (except for the SDAP header). Thereafter, the PDCP entity of the receiving end performs integrity verification on the SDAP header, the upper layer header (TCP/IP header), and the data part, and calculates X-MAC. When the X-MAC is calculated, the PDCP COUNT value, the uplink or downlink indicator, the bearer indicator, the security key, the data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The PDCP entity of the receiving end checks whether the value of the X-MAC is equal to the value of the MAC-I concatenated to the end of the data. When the two values are equal, the integrity verification is successful, but when the values of X-MAC and MAC-I are not equal, the integrity verification fails, and thus, the PDCP entity of the receiving end discards the data and must report the failure of the integrity verification to an upper layer (e.g., RRC layer). When the integrity verification is completed, it may be checked whether a checksum failure occurs by reading a UDC header from the upper layer data, a UDC decompression process may be performed, and the reconstructed upper layer data may be transferred to the upper layer.

Fig. 2U illustrates a process in which the SDAP entity generates an SDAP header for data received from an upper layer, and the PDCP entity performs UDC, applies integrity protection to the UDC header, does not perform ciphering on the UDC header, applies integrity protection to the SDAP header, and does not perform ciphering on the SDAP header, according to an embodiment of the disclosure.

In fig. 2U, when configured to use the function of the SDAP entity or to use the SDAP header in an RRC message, configured to perform integrity protection and integrity verification in an RRC message, and configured to perform UDC for uplink or downlink in an RRC message, as shown in fig. 2E (see 2E-10, 2E-40, or 2E-75) in an RRC message, when the SDAP entity receives data from an upper layer, the SDAP entity may generate and configure the SDAP header as in 2U-05, and may transmit the SDAP header to the PDCP entity. The PDCP entity performs UDC (2 u-10) on a part (e.g., IP data header) of the received PDCP SDU except for the SDAP header. Then, the PDCP entity may calculate a checksum field 2u-15 based on the current UDC buffer, may configure a UDC header, and may concatenate the UDC header to the beginning of the SDAP header, as shown in 2 u-20. When integrity protection is configured, the PDCP entity may perform integrity protection 2u-25 on 2u-20 (including the UDC header, the SDAP header, and the UDC block) received from the upper layer SDAP entity and applied with the UDC and concatenated with the UDC header, and may calculate MAC-I (2 u-35) on the data 2 u-30. When the MAC-I is calculated, the PDCP COUNT value, the uplink or downlink indicator, the bearer indicator, the security key, the data part (on which integrity protection is performed), etc. may be input values of an integrity protection algorithm. The calculated MAC-I may be concatenated to the end of the data as shown in 2 u-40. The MAC-I may have a certain size, for example a size of 4 bytes. In addition to the UDC header and the SDAP header, the PDCP entity may perform ciphering (2 u-45) on 2u-40 to which the MAC-I is concatenated, may generate, configure and concatenate the PDCP header to data (2 u-50), and may transfer the data to a lower layer. Then, the RLC entity and the MAC entity may perform data processing.

The receiving end removes the MAC header and the RLC header and then transfers the data to the PDCP layer, and the PDCP entity of the receiving end reads and then removes the PDCP header and performs decryption on the data part (except for the SDAP header). Thereafter, the PDCP entity of the receiving end performs integrity verification on the SDAP header, the upper layer header (TCP/IP header), and the data part, and calculates X-MAC. When the X-MAC is calculated, the PDCP COUNT value, the uplink or downlink indicator, the bearer indicator, the security key, the data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The PDCP entity of the receiving end checks whether the value of the X-MAC is equal to the value of the MAC-I concatenated to the end of the data. When the two values are equal, the integrity verification succeeds, but when the values of X-MAC and MAC-I are not equal, the integrity verification fails, and thus, the PDCP entity of the receiving end discards the data and must report the failure of the integrity verification to an upper layer (e.g., RRC layer). When the integrity verification is completed, it may be checked whether a checksum failure occurs by reading a UDC header from the upper layer data, a UDC decompression process may be performed, and the reconstructed upper layer data may be transferred to the upper layer.

In fig. 2V, when configured to use the function of the SDAP entity or use the SDAP header in the RRC message, configured to perform integrity protection and integrity verification in the RRC message, and configured to perform UDC for uplink or downlink in the RRC message, as shown in fig. 2E (see 2E-10, 2E-40, or 2E-75) in the RRC message, when the SDAP entity receives data from an upper layer, the SDAP entity may generate and configure the SDAP header as in 2V-05, and may transmit the SDAP header to the PDCP entity. The PDCP entity performs UDC (2 v-10) on a part of the received PDCP SDU other than the SDAP header, for example, an IP data header. The PDCP entity may then calculate a checksum field 2v-15 based on the current UDC buffer, may configure the UDC header, and may concatenate the UDC header to the beginning of the SDAP header, as shown at 2 v-20. When integrity protection is configured, the PDCP entity may perform integrity protection 2v-25 on 2v-20 (including the UDC header, the SDAP header, and the UDC block) received from the upper layer SDAP entity and applied with UDC and concatenated with the UDC header, and may calculate MAC-I (2 v-35) from the data 2 v-30. When the MAC-I is calculated, a PDCP COUNT value, an uplink or downlink indicator, a bearer indicator, a security key, a data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The calculated MAC-I may be concatenated to the end of the data as shown in 2 v-40. The MAC-I may have a certain size, for example a size of 4 bytes. In addition to the UDC header and the SDAP header, the PDCP entity may perform ciphering (2 v-45) on 2v-40 to which the MAC-I is concatenated, may generate, configure and concatenate a PDCP header to data (2 v-50), and may transfer the data to a lower layer. Then, the RLC entity and the MAC entity may perform data processing.

The receiving end removes the MAC header and the RLC header and then transfers the data to the PDCP layer, and the PDCP entity of the receiving end reads and then removes the PDCP header and performs decryption on the data part (except for the SDAP header). Thereafter, the PDCP entity of the receiving end performs integrity verification on the SDAP header, the upper layer header (TCP/IP header), and the data part, and calculates X-MAC. When the X-MAC is calculated, the PDCP COUNT value, the uplink or downlink indicator, the bearer indicator, the security key, the data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The PDCP entity of the receiving end checks whether the value of the X-MAC is equal to the value of the MAC-I concatenated to the end of the data. When the two values are equal, the integrity verification succeeds, but when the values of X-MAC and MAC-I are not equal, the integrity verification fails, and thus, the PDCP entity of the receiving end discards the data and must report the failure of the integrity verification to an upper layer (e.g., RRC layer). When the integrity verification is completed, it may be checked whether a checksum failure occurs by reading the UDC header, a UDC decompression process may be performed on the upper layer data, and the reconstructed upper layer data may be transferred to the upper layer.

Fig. 2W illustrates the advantages of processing obtained from a base station and a UE that can be achieved by applying an SDAP header and a UDC header that are not subject to ciphering and integrity protection, according to an embodiment of the present disclosure.

In fig. 2W, the SDAP entity and the PDCP entity may be unified into one entity (2W-01) when the UE and the base station are implemented. Since logically the SDAP entity is an upper layer entity of the PDCP entity, when data 2w-05 is received from an upper layer application layer, when configured to use a function of the SDAP entity or use the SDAP header and configured integrity protection in an RRC message, and in case of configuring use of UDC for uplink or downlink in the RRC message as shown in FIG. 2E (see 2E-10, 2E-40, or 2E-75), when the SDAP entity receives data from the upper layer, the SDAP entity must generate and configure the SDAP header as 2J-05 of FIG. 2J. However, the ciphering process or the integrity protection process is an operation requiring a high degree of complexity in the implementation of the UE and the base station, which can be performed by applying a HW accelerator thereto. HW accelerators gain high advantages in processing from repeated and continuous processes. However, when the SDAP entity configures the SDAP header and is configured to perform integrity protection and UDC each time the SDAP entity receives data from an upper layer entity, when a process of performing a UDC procedure, generating and concatenating a UDC header, performing an integrity protection procedure and a ciphering procedure on a data part other than the SDAP header and the UDC header, generating a PDCP header, and concatenating the PDCP header to the SDAP header is performed, an interruption of the HW accelerator may occur due to an operation of generating the UDC header and the SDAP header before performing the integrity protection procedure and the ciphering procedure in the process.

Accordingly, the present disclosure describes a method of implementing an SDAP header that is not integrity protected and ciphered, and implementing one entity by unifying SDAP and PDCP entities. That is, when data is received from an upper application layer, whenever data is received, UDC (2 w-10) may be continuously and repeatedly performed on an upper layer header part (e.g., IP packet header) of the received PDCP SDU, ti generating 2w-15. Then, as shown in 2w-20, an integrity protection procedure (2 w-25) may be performed on the PDCP SDU to which the header compression is applied, a MAC-I2 w-35 may be calculated and then the MAC-I may be concatenated to the end of the data (2 w-30), a ciphering procedure (2 w-40) may be performed on the MAC-I and the integrity-protected data (2 w-45), the PDCP header, the SDAP header, and the MAC-I may be simultaneously generated (2 w-50), and then may be concatenated to the integrity-protected and ciphered data, and then the data may be transferred to a lower layer. The generation of the PDCP header, UDC header and SDAP header may be processed in parallel with an integrity protection procedure or ciphering procedure. In this regard, when the headers are generated in a parallel manner, an SDAP header, a PDCP header, a UDC header, or an RLC header or a MAC header may be generated together, and these headers may be concatenated to the beginning of data that has completely undergone data processing and may be ready for transmission (may be ready for configuration of MAC PDUs) at a time. In addition, the receiving end may separate and read the SDAP header, PDCP header, UDC header, or RLC header or MAC header from the data at a time, may recognize information corresponding to each layer, and may process the data in the reverse order of the data processing performed by the transmitting end. Accordingly, the HW accelerator can be continuously and repeatedly applied, and since interrupts such as generation of the UDC header and the SDAP header do not occur therebetween, the efficiency of data processing can be improved. In addition, when integrity protection is configured, the HW accelerator may be applied to integrity protection as described with respect to the cryptographic process before the cryptographic process is performed, and thus the integrity protection may be repeatedly performed. That is, integrity protection may be performed and then an encryption process may be performed.

The PDCP entity of the receiving end may use a method of implementing one entity by unifying the SDAP entity and the PDCP entity, as in 2 w-01. That is, when data is received from a lower layer (RLC layer), in case of being configured to use the function of the SDAP entity or use the SDAP header in an RRC message, such as the RRC message shown in fig. 2E (see 2E-10, 2E-40, or 2E-75), one of the SDAP and PDAP entities may read and remove the PDCP header and the SDAP header at a time, and may repeat the process of applying the deciphering code or deciphering code to the data. In addition, when integrity protection is configured, after the decryption process is performed, the HW accelerator may be applied to integrity verification as described with respect to the decryption process, and thus integrity verification may be repeatedly performed. That is, a decryption process may be performed, and then integrity verification may be performed. When the integrity verification is completed, it may be checked whether a checksum failure occurs by reading a UDC header from the upper layer data, a UDC decompression process may be performed on the upper layer data, and the reconstructed upper layer data may be transferred to the upper layer.

In fig. 2X, when configured to use the function of the SDAP entity or use the SDAP header in an RRC message, configured to perform integrity protection and integrity verification in an RRC message, configured to perform UDC for uplink or downlink in an RRC message, as shown in fig. 2E (see 2E-10, 2E-40, or 2E-75) in an RRC message, when the SDAP entity receives data from an upper layer, the SDAP entity may generate and configure the SDAP header as in 2X-05, and may transmit the SDAP header to the PDCP entity. The PDCP entity performs UDC (2 x-10) on a part of the received PDCP SDU other than the SDAP header, for example, an IP data header. The PDCP entity may then calculate a checksum field 2x-15 based on the current UDC buffer, may configure the UDC header, and may concatenate the UDC header to the beginning of the SDAP header, as shown by 2 x-20. When integrity protection is configured, the PDCP entity may perform integrity protection on 2x-25 (including the UDC header, the SDAP header, and the UDC block) received from the upper layer SDAP entity and applied with UDC and concatenated with the UDC header, and may calculate MAC-I (2 x-30 and 2 x-35). When the MAC-I is calculated, a PDCP COUNT value, an uplink or downlink indicator, a bearer indicator, a security key, a data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The calculated MAC-I may be concatenated to the end of the data as shown by 2 x-40. The MAC-I may have a certain size, for example a size of 4 bytes. In addition to the UDC header and the SDAP header, the PDCP entity may perform ciphering (2 x-40 and 2 x-45) on 2x-40 to which the MAC-I is concatenated, may generate, configure and concatenate a PDCP header to data (2 x-50), and may transfer the data to a lower layer. Then, the RLC entity and the MAC entity may perform data processing. Embodiments of the present disclosure are characterized in that the MAC-I is not encrypted. When the MAC-I is not encrypted, advantages in data processing can be further obtained as described below.

The receiving end removes the MAC header and the RLC header and then transfers the data to the PDCP layer, and the PDCP entity of the receiving end reads and then removes the PDCP header and performs decryption on the data part (except for the UDC header, the SDAP header, and the MAC-I at the end). In this regard, decryption is not performed on the MAC-I. Thereafter, the PDCP entity of the receiving end performs integrity verification on the upper header (TCP/IP header) and the data part (except for the UDC header and the SDAP header), and calculates X-MAC. When the X-MAC is calculated, the PDCP COUNT value, the uplink or downlink indicator, the bearer indicator, the security key, the data part (which is integrity protected), etc. may be input values of an integrity protection algorithm. The PDCP entity of the receiving end checks whether the value of the X-MAC is equal to the value of the MAC-I concatenated to the end of the data. When the two values are equal, the integrity verification succeeds, but when the values of X-MAC and MAC-I are not equal, the integrity verification fails, and thus, the PDCP entity of the receiving end discards the data and must report the failure of the integrity verification to an upper layer (e.g., RRC layer). When the integrity verification is completed, it may be checked whether a checksum failure occurs by reading the UDC header, a UDC decompression process may be performed on the upper layer data, and the reconstructed upper layer data may be transferred to the upper layer.

In this way, the configuration of embodiments of the base station can be simplified when no ciphering or integrity protection is performed on the UDC header and the SDAP header, especially in a CU-DU structure split structure, when the CU does not cipher the SDAP header, the DU can check the QoS information by reading the SDAP header and can apply the QoS information to the scheduling, and therefore it may be advantageous to match and adjust the QoS. Also, the foregoing features may have advantages in terms of data processing in the configuration of the UE and the base station. Further, when the MAC-I is not encrypted, an advantage in data processing can be further obtained as described below.

Fig. 2Y illustrates the advantages of processing that may be obtained from a base station and a UE by applying an SDAP header and a UDC header that are not subject to ciphering and integrity protection, by performing UDC, and by not ciphering MAC-I, according to embodiments of the present disclosure.

In fig. 2Y, the SDAP entity and the PDCP entity may be unified into one entity (2Y-01) when the UE and the base station are implemented. Since logically, the SDAP entity is an upper layer entity of the PDCP entity, when data 2s-01 is received from an upper application layer, the SDAP entity must generate and configure the SDAP header when the SDAP entity is received from the upper layer, in the case where it is configured in an RRC message to use the function of the SDAP entity or to use the SDAP header and integrity protection is configured, and in the case where it is configured to perform UDC for uplink or downlink in an RRC message as shown in FIG. 2E (see 2E-10, 2E-40, or 2E-75), the SDAP entity must generate and configure the SDAP header when the SDAP entity receives data from the upper layer, as shown in 2J-05 of FIG. 2J. However, the ciphering process or the integrity protection process is an operation requiring a high degree of complexity in the implementation of the UE and the base station, which can be performed by applying a HW accelerator thereto. HW accelerators gain high advantages in processing from repeated and continuous processes. However, when the SDAP entity configures the SDAP header and is configured to perform integrity protection and UDC each time the SDAP entity receives data from an upper layer entity, when a process of performing a UDC procedure, generating and concatenating a UDC header, performing an integrity protection procedure and a ciphering procedure on a data part other than the SDAP header and the UDC header, generating a PDCP header, and concatenating the PDCP header to the SDAP header is performed, an interruption of the HW accelerator may occur due to an operation of generating the UDC header and the SDAP header before performing the integrity protection procedure and the ciphering procedure in the process.

Accordingly, the present disclosure describes a method of implementing a UDC header and an SDAP header that are not integrity protected and ciphered, implementing a MAC-I that is not ciphered, and implementing one entity by unifying an SDAP entity and a PDCP entity. That is, 2y-05 when receiving data from an upper application layer, whenever receiving data, UDC (2 y-10) may be continuously and repeatedly performed on an upper header part (e.g., IP packet header) of the received PDCP SDU, 2y-25 integrity protection procedures may be performed on the data 2y-15, MAC-I (2 y-35 and 2 y-45) may be calculated on the data 2y-20, a ciphering procedure may be performed on the integrity-protected data 2y-30, a PDCP header, an SDAP header, and MAC-I may be simultaneously generated and then may be concatenated to the integrity-protected and ciphered data, and then the data 2y-40 may be transferred to a lower layer (2 y-50). That is, the generated header may be concatenated to the beginning of the data, and the MAC-I may be concatenated to the end of the data. The generation of the PDCP header, the SDAP header, and the MAC-I may be processed in parallel with an integrity protection procedure or a ciphering procedure. In this regard, when the headers are generated in a parallel manner, an SDAP header, a PDCP header, a UDC header, or an RLC header or a MAC header may be generated together and may be concatenated to the beginning of data that has completely undergone data processing and may be ready for transmission (may be ready for configuration of MAC PDUs) at a time. The MAC-I may be concatenated to the end of the data that has completely undergone data processing. Further, the receiving end may separate the SDAP header, the PDCP header, the UDC header, or the RLC header or the MAC header from the data at a time and read them, may recognize information corresponding to each layer, and may process the data in the reverse order of the data processing performed by the transmitting end. Accordingly, the HW accelerator can be continuously and repeatedly applied, and since an interrupt such as generation of the UDC header and the SDAP header does not occur therebetween, the efficiency of data processing can be improved. In addition, when integrity protection is configured, the HW accelerator may be applied to integrity protection as described with respect to the cryptographic process before the cryptographic process is performed, and thus the integrity protection may be repeatedly performed. That is, integrity protection may be performed and then an encryption process may be performed.

The PDCP entity of the receiving end may use a method of implementing one entity by unifying the SDAP entity and the PDCP entity, as in 2 l-01. That is, when data is received from a lower layer (RLC layer), in case of being configured to use the function of the SDAP entity or use the SDAP header in an RRC message, such as the RRC message shown in fig. 2E (see 2E-10, 2E-40, or 2E-75), one of the SDAP and PDAP entities may read and remove the PDCP header, the UDC header, and the SDAP header at a time, and may repeat the process of applying the decryption code or decryption to the data. In addition, when the integrity verification is completed, it may be checked whether a checksum failure occurs by reading the UDC header, a UDC decompression process may be performed on the upper layer data, and the reconstructed upper layer data may be transferred to the upper layer. That is, the header of the received data may be read and removed, the MAC-1 at the end of the data may be read and removed, decryption may be performed on the data portion, and the integrity verification process may be performed. When the integrity verification is complete, a UDC decompression process may be performed on an upper layer header (e.g., an IP packet header) and the reconstructed upper layer data may be transferred to the upper layer.

Fig. 2Z illustrates operations of a transmitting and receiving SDAP/PDCP entity of a logical channel, bearer, or SDAP/PDCP entity configured with integrity protection when an SDAP header, on which integrity protection and ciphering are not performed, is applied to the SDAP/PDCP entity, according to an embodiment of the present disclosure.

In fig. 2Z, the SDAP entity and the PDCP entity may be unified into one entity (2Z-01) when implementing the UE and the base station. The present disclosure provides a method for implementing an SDAP header where ciphering is not performed and implementing one entity by unifying SDAP and PDCP entities for a case where integrity protection is configured. That is, when data is received from an upper application layer (2 z-05), integrity protection may be applied to the data each time the data is received (2 z-10), a ciphering process may be continuously and repeatedly performed (2 z-15), a PDCP header and an SDAP header may be simultaneously performed (2 z-20), the PDCP header and the SDAP header may be concatenated to the ciphered data, and the ciphered data may be transferred to a lower layer. The generation of the PDCP header and the SDAP header may be processed in parallel with an integrity protection procedure or a ciphering procedure. In this regard, when the headers are generated in a parallel manner, an SDAP header, a PDCP header, a UDC header, or an RLC header or a MAC header may be generated together, and these headers may be concatenated to the beginning of data that has completely undergone data processing and may be ready for transmission (may be ready for configuration of MAC PDUs) at a time. Further, the receiving end may separate the SDAP header, the PDCP header, the UDC header, or the RLC header or the MAC header from the data at a time and read them, may recognize information corresponding to each layer, and may process the data in the reverse order of the data processing performed by the transmitting end. Accordingly, the HW accelerator can be continuously and repeatedly applied, and since an interrupt such as generation of the SDAP header does not occur therebetween, the efficiency of data processing can be improved. The HW accelerator may be applied to UDC processes.

The PDCP entity 2z-02 of the receiving end can apply the method for implementing one entity by unifying the SDAP entity and the PDCP entity to the case where integrity protection is configured. That is, when data is received from a lower layer (RLC layer) (2 z-25), in case of being configured to use a function of the SDAP entity or use an SDAP header in an RRC message, such as an RRC message shown in fig. 2E (see 2E-10, 2E-40, or 2E-75), one of the SDAP and PDAP entities may read and remove the PDCP header and the SDAP header (2 z-30) at a time, and may repeat applying the decryption process to the data (2 z-35), may repeat applying the integrity verification process to the data, and may transfer the data to an upper layer (2 z-40).

Fig. 2AA illustrates a configuration of a UE according to an embodiment of the present disclosure.

Referring to fig. 2aa, the ue includes a Radio Frequency (RF) processor 2aa-10, a baseband processor 2aa-20, a storage device 2aa-30, and a controller 2aa-40.

The RF processors 2aa-10 perform functions including conversion, amplification, etc. of signal bands in order to transceive signals through wireless channels. That is, the RF processors 2aa-10 up-convert baseband signals provided from the baseband processors 2aa-20 into RF band signals and receive the RF band signals via the antennas and down-convert the RF band signals received via the antennas. To a baseband signal. For example, the RF processors 2aa-10 may include transmit filters, receive filters, amplifiers, mixers, oscillators, digital-to-analog converters (DACs), analog-to-digital converters (ADCs), and so forth. Although fig. 2AA shows only one antenna, the UE may include multiple antennas. Furthermore, the RF processors 2aa-10 may include a plurality of RF chains. In addition, the RF processors 2aa-10 may perform beamforming. For beamforming, the RF processors 2aa-10 may adjust the phase and amplitude of individual signals transceived via multiple antennas or antenna elements. Also, the RF processors 2aa-10 may perform massive Multiple Input Multiple Output (MIMO) and may receive multiple layers while performing MIMO operations. The RF processors 2aa-10 may perform receive beam scanning by appropriately setting a plurality of antennas or antenna elements under the control of the controllers 2aa-40, or may adjust the direction and width of the receive beam so that the receive beam is coordinated with the transmit beam.

The baseband processors 2aa-20 perform the conversion function between the baseband signal and the bit string according to the physical layer specification of the system. For example, in data transmission, the baseband processors 2aa to 20 generate complex symbols by encoding and modulating the transmitted bit string. In addition, in data reception, the baseband processors 2aa to 20 reconstruct the received bit string by performing demodulation and decoding on the baseband signal provided from the RF processors 2aa to 10. For example, when data is transmitted according to the OFDM scheme, the baseband processors 2aa to 20 generate complex symbols by performing coding and modulation on the transmitted bit string, map the complex symbols to subcarriers, and configure the OFDM symbols by performing an Inverse Fast Fourier Transform (IFFT) operation and inserting a Cyclic Prefix (CP). In addition, in data reception, the baseband processors 2aa to 20 may divide the baseband signal provided from the RF processors 2aa to 10 into OFDM symbol units and restore the signals mapped to the subcarriers by performing a Fast Fourier Transform (FFT) operation and then reconstruct the received bit string by demodulating and decoding the signals.

The baseband processors 2aa-20 and the RF processors 2aa-10 transmit and receive signals as described above. Thus, the baseband processor 2aa-20 and the RF processor 2aa-10 may be referred to as transmitters, receivers, transceivers or communicators. Further, at least one of the baseband processor 2aa-20 and the RF processor 2aa-10 may include a plurality of communication modules to support different radio access technologies. Also, at least one of the baseband processors 2aa-20 and the RF processors 2aa-10 may include different communication modules configured to support a plurality of different radio access technologies. Also, at least one of the baseband processors 2aa-20 and the RF processors 2aa-10 may include different communication modules configured to process signals of different frequency bands. For example, the different radio access technologies may include LTE networks, NR networks, and the like. Examples of different frequency bands may include the ultra high frequency (SHF) band (e.g., 2.5Ghz or 5 Ghz) and the millimeter wave band (e.g., 60 Ghz).

The storage means 2aa-30 may store data such as default procedures, application procedures and configuration information for the operation of the UE. The storage devices 2aa-30 provide stored data in response to requests by the controllers 2aa-40.

The controllers 2aa-40 control the overall operation of the UE. For example, the controllers 2aa-40 transmit and receive signals through the baseband processors 2aa-20 and the RF processors 2 aa-10. In addition, the controllers 2aa-40 record and read data stored in the storage devices 2 aa-30. To this end, the controllers 2aa-40 may include at least one processor. For example, the controllers 2aa to 40 may include a Communication Processor (CP) configured to perform communication control and an Application Processor (AP) configured to control an upper layer such as an application program. According to an embodiment of the present disclosure, the controller 2aa-40 includes a multi-connection processor 2aa-42, the multi-connection processor 2aa-42 being configured to perform processing for operating in a multi-connection mode.

Fig. 2AB shows a configuration of a base station according to an embodiment of the present disclosure.

Referring to FIG. 2AB, the base station includes RF processors 2AB-10, baseband processors 2AB-20, communicators 2AB-30, storage devices 2AB-40, and controllers 2AB-50.

The RF processors 2ab-10 perform functions including conversion, amplification, etc. of signal bands in order to transceive signals through wireless channels. That is, the RF processors 2ab-10 up-convert baseband signals supplied from the baseband processors 2ab-20 into RF band signals, and receive the RF band signals via the antennas, and down-convert the RF band signals received via the antennas into baseband signals. For example, the RF processors 2ab-10 may include transmit filters, receive filters, amplifiers, mixers, oscillators, DACs, ADCs, and so forth. Although fig. 2AB shows only one antenna, the base station may include multiple antennas. Also, the RF processors 2ab-10 may include a plurality of RF chains. Further, the RF processors 2ab-10 may perform beamforming. For beamforming, the RF processors 2ab-10 may adjust the phase and amplitude of the respective signals transceived via the plurality of antennas or antenna elements. In addition, the RF processors 2ab-10 may perform the lower MIMO operation by transmitting one or more layers.

The baseband processors 2ab-20 perform the conversion function between the baseband signals and the bit strings according to the physical layer specification of the first radio access technology. For example, in data transmission, the baseband processors 2ab-20 generate complex symbols by encoding and modulating the transmitted bit string. In addition, in data reception, the baseband processors 2ab-20 reconstruct the received bit string by performing demodulation and decoding on the baseband signals supplied from the RF processors 2 ab-10. For example, when transmitting data according to the OFDM scheme, the baseband processors 2ab-20 generate complex symbols by performing coding and modulation on the transmitted bit string, map the complex symbols to subcarriers, and configure OFDM symbols by performing an IFFT operation and inserting a Cyclic Prefix (CP). In addition, in data reception, the baseband processors 2ab-20 may divide the baseband signals provided from the RF processors 2ab-10 into OFDM symbol units, recover signals mapped to subcarriers by performing an FFT operation, and then reconstruct received bit strings by demodulating and decoding the signals. The baseband processors 2ab-20 and the RF processors 2ab-10 transmit and receive signals as described above. Thus, the baseband processors 2ab-20 and the RF processors 2ab-10 may be referred to as transmitters, receivers, transceivers, communicators, or wireless communicators.

The communicators 2ab-30 provide an interface for performing communications with other nodes in the network.

The storage means 2ab-40 store data such as default programs, application programs and configuration information for the operation of the base station. In particular, the storage means 2ab-40 may store information about bearers assigned to connected UEs, measurements reported by connected UEs, etc. Furthermore, the storage means 2ab-40 may store information which is a criterion for determining whether to provide or stop the multi-connection to the UE. Also, the storage devices 2ab-40 may provide stored data in response to requests by the controllers 2ab-50.

The controllers 2ab-50 control the overall operation of the base station. For example, the controllers 2ab-50 send and receive signals via the baseband processors 2ab-20 and the RF processors 2ab-10 or via the communicators 2 ab-30. In addition, the controllers 2ab-50 can record/read data to/from the storage devices 2ab-40 and 2 ab-40. To this end, the controllers 2ab-50 may include at least one processor. According to an embodiment of the present disclosure, the controller 2ab-50 comprises a multi-connection processor 2aa-52, which multi-connection processor 2aa-52 is configured to perform processing for operating in a multi-connection mode.

Fig. 3A is a diagram showing the configuration of the LTE system.

Referring to fig. 3A, the wireless communication system is composed of a plurality of base stations (also referred to as "enbs") 3A-05, 3A-10, 3A-15, and 3A-20, MMEs 3A-25, and S-GWs 3A-30. User equipment (hereinafter referred to as UE or terminal) 3a-35 accesses an external network via enbs 3a-05, 3a-10, 3a-15 and 3a-20 and S-GW 3 a-30.

eNBs 3a-05, 3a-10, 3a-15 and 3a-20, which are access nodes of the cellular network, provide radio access to UEs of the access network. That is, in order to serve the traffic of the user, the enbs 3a-05, 3a-10, 3a-15 and 3a-20 collect and schedule pieces of status information including a buffer status, an available transmission power status, a channel status, or the like of the UE, and then support the connection between the UE and the Core Network (CN). The MMEs 3a-25 are devices configured to perform not only mobility management functions but also various control functions for the UE, and are connected to a plurality of base stations. The S-GW 3a-30 is a device configured to provide a data bearer. In addition, the MME 3a-25 and S-GW 3a-30 can also be configured to perform authentication, bearer management, etc. for the UE accessing the network, and process packets received from the eNBs 3a-05, 3a-10, 3a-15 and 3a-20, or packets to be transmitted to the eNBs 3a-05, 3a-10, 3a-15 and 3 a-20.

Fig. 3B is a diagram showing a radio protocol architecture in the LTE system.

The NR system has a protocol architecture very similar to that of the LTE system.

Referring to fig. 3b, a radio protocol in the lte system is composed of PDCP3b-05 and 3b-40, RLC 3b-10 and 3b-35, and MAC3b-15 and 3b-30 in the respective UE and eNB. The PDCP3b-05 and 3b-40 perform operations including IP header compression/decompression, and the RLC 3b-10 and 3b-35 reconfigure a PDCP packet data Unit (PDCP PDU) to have an appropriate size. The MACs 3b-15 and 3b-30 are connected to a plurality of RLC layers configured in one UE, and can perform operations of multiplexing and demultiplexing RLC PDUs into and from the MAC PDU. The PHY layers 3b-20 and 3b-25 perform an operation of channel-coding and modulating the upper layer data and transmitting the OFDM symbols through a radio channel by converting the upper layer data into the OFDM symbols, or an operation of demodulating and channel-decoding the OFDM symbols received through the radio channel and transmitting the decoded data to the upper layer. To perform additional error correction, the PHY layers 3b-20 and 3b-25 use hybrid automatic repeat request (hybrid ARQ or HARQ), and the receiving end transmits 1 bit indicating Acknowledgement (ACK) or Negative Acknowledgement (NACK) with respect to a packet transmitted from the transmitting end. This is referred to as HARQ ACK/NACK information. Downlink HARQ ACK/NACK information for uplink transmission may be transmitted via a physical hybrid ARQ indicator channel (PHICH) physical channel, and uplink HARQ ACK/NACK information for downlink transmission may be transmitted via a Physical Uplink Control Channel (PUCCH) physical channel or a Physical Uplink Shared Channel (PUSCH) physical channel.

Although not shown in fig. 3B, respective Radio Resource Control (RRC) layers exist as upper layers of the PDCP layers 3B-05 and 3B-40 of the UE and the eNB, and the RRC layers may exchange setup control messages related to access and measurement to control radio resources.

The PHY layer 3b-20 or 3b-25 may include one or more frequencies/carriers, and a technique for simultaneously setting and using a plurality of frequencies in one base station is called Carrier Aggregation (CA). According to the CA technology, instead of using only one carrier for communication between a UE and a base station, i.e., an E-UTRAN node B (eNB), one primary carrier and a plurality of secondary carriers may be additionally used, so that transmission capacity may be greatly increased as much as the number of secondary carriers. In LTE and NR systems, a cell served by a base station using a primary carrier is referred to as a primary cell (PCell), and a cell served by a base station using a secondary carrier is referred to as a secondary cell (SCell). A technique of extending the CA technique is called Dual Connectivity (DC). According to the DC technique, a UE is simultaneously connected to a master base station, i.e., a master E-UTRAN node B (MeNB), and a secondary base station, i.e., a secondary E-UTRAN node B (SeNB), in order to use radio resources, and a cell served by the MeNB is referred to as a Master Cell Group (MCG) and a cell served by the SeNB is referred to as a Secondary Cell Group (SCG). Each group has one representative cell, and in this regard, the representative cell of the MCG is referred to as a primary cell (PCell) and the representative cell of the SCG is referred to as a primary secondary cell (PSCell). When NR is used, MCG uses LTE technology and SCG uses NR, so the UE can use both LTE technology and NR.

In LTE and NR systems, a UE transmits a Power Headroom Report (PHR) to an eNB according to certain conditions. The PHR indicates a difference between a maximum transmission power, which is set in the UE and estimated by the UE, and a transmission power. The transmission power estimated by the UE is calculated based on a value used when the UE transmits an actual uplink (the resultant value thereof is referred to as a real value), but when the UE does not transmit an actual uplink, the estimated transmission power is calculated according to a specific equation defined in a standard rule (the resultant value thereof is referred to as an imaginary value). When the eNB receives the PHR, the eNB may determine an available maximum transmission power of the UE. When CA is used, a PHR is transmitted to each of a plurality of secondary carriers.

Fig. 3C is a diagram for describing CA in a UE.

Referring to fig. 3C, in one base station, a plurality of carriers are generally transmitted and received over several frequency bands. For example, according to the related art, when the base station 3c-05 transmits the carrier 3c-15 of the main frequency f1 and the carrier 3c-10 of the main frequency f3, one UE transmits and receives data by using one of the two carriers. However, the CA-capable UE can simultaneously transceive data using a plurality of carriers. The base station 3c-05 can allocate more carriers to the CA capable UE 3c-30 depending on the conditions, thereby increasing the transmission rate of the UE3 c-30.

When it is assumed that one cell is generally composed of one forward carrier and one backward carrier transmitted/received by one base station, CA can be understood in a manner that a UE simultaneously transceives data through a plurality of cells. By doing so, the maximum transmission rate increases in proportion to the number of aggregated carriers.

Hereinafter, in the present disclosure, an expression that a UE receives data through a random forward carrier or transmits data through a random backward carrier has the same meaning as transceiving data by using a control channel and a data channel provided by a cell corresponding to a main frequency and a frequency bandwidth designating the corresponding carrier. In addition, hereinafter, for convenience of description, the present disclosure will now be described with reference to an LTE system, but the present disclosure may be applied to various wireless communication systems supporting CA.

Even when CA is performed or not performed, backward transmission (i.e., transmission from a UE to a base station) causes interference of backward transmission of another cell, and therefore, the backward transmission output must be maintained at an appropriate level. For this, when the UE performs the backward transmission, the UE calculates a backward transmission output by using a specific function and performs the backward transmission based on the calculated backward transmission output. For example, the UE may calculate a value of a requested backward transmission output by inputting scheduling information such as an amount of allocated transmission resources, a Modulation Coding Scheme (MCS) level to be applied, and the like, and input values such as a path loss value for estimating a channel state to a specific function, and may perform backward transmission by applying the calculated value of the requested backward transmission output. The value of the backward transmission output applicable to the UE is limited due to a maximum transmission value of the UE, and when the calculated request value for the backward transmission output is greater than the maximum transmission value of the UE, the UE performs the backward transmission according to the maximum transmission value. In this case, since the backward transmission output is insufficient, the quality of backward transmission may be deteriorated. The base station may perform scheduling to prevent the requested transmission output from exceeding the maximum transmission value. However, few parameters, including path loss, cannot be detected by the base station, and thus, the UE transmits a PHR as necessary to report a state of an available transmission output of the UE (power headroom (PH)) to the base station.

Factors that affect the available transmission output are: 1) An amount of allocated transmission resources; 2) MCS to be applied for backward transmission; 3) Path loss of the associated forward carrier; 4) Output an accumulated value of the adjustment command, and the like. Among these factors, the path loss (hereinafter, referred to as PL) or the accumulated value of the output adjustment command may vary according to the backward carriers, and therefore, when a plurality of backward carriers are aggregated in one UE, it is reasonable to configure whether to transmit a PHR for each of the backward carriers. However, for efficient transmission of the PHR, one backward carrier may report PHs of a plurality of backward carriers. According to one operation strategy, the PH may be requested by a carrier that does not actually transmit PUSCH. Therefore, for this case, it is more effective for one backward carrier to report all PHs of a plurality of backward carriers. For this purpose, the PHR to be exhibited must be expanded. A plurality of PHs to be included in one PHR may be configured according to a predetermined order.

When the PL of a normally connected forward carrier changes to exceed a preset reference value, the PHR is triggered when a PHR prohibition timer expires or when a preset time elapses after the PHR is generated. Even when the PHR is triggered, the UE does not immediately transmit the PHR and stands by until a backward transmission resource is allocated thereto. This is because the PHR is not information that should be processed quickly.

Fig. 3D is a diagram for describing the concept of multi-connectivity in LTE and NR.

By using DC technology, the UE can be connected to two base stations simultaneously and can use radio resources, and figure 3D shows the case where the UE 3D-05 is connected to the macro base station 3D-00 simultaneously using LTE technology and to the small cell base station 3D-10 using NR technology. This is called E-UTRAN-NR dual connectivity (EN-DC). The macro base station 3d-00 is referred to as the master E-UTRAN node B (MeNB) 3d-00 and the small cell base station 3d-10 is referred to as the secondary 5G node B (SgNB) 3d-10. There may be multiple small cells in the service coverage of the MeNB 3d-00, and the MeNB 3d-00 may be connected to multiple sgnbs 3d-10 via the wired backhaul network 3 d-15. The set of serving cells provided from the MeNB 3d-00 is referred to as a Master Cell Group (MCG) 3d-20, and one of the serving cells in the MCG 3d-20 is of course a master cell (PCell) 3d-25 with all functions, such as connection establishment, connection re-establishment, handover, etc., that were performed via existing cells. In PCell 3d-25, the uplink control channel has PUCCH. The serving cells other than the PCell 3d-25 are referred to as secondary cells (scells) 3d-30. Fig. 3D shows a scenario where MeNB 3D-00 provides one SCell 3D-30 and SgNB3D-10 provides three scells. The set of serving cells provided by SgNB3d-10 is called Secondary Cell Group (SCG) 3d-40. When the UE 3d-05 transceives data to/from the MeNB 3d-00 and the SgNB3d-10, the MeNB 3d-00 issues commands to the SgNB3d-10 for adding, changing, and removing the serving cell provided by the SgNB 3d-10. To issue this command, the MeNB 3d-00 may configure the UE 3d-05 to measure the serving cell and the neighbor cells. According to the configuration information, the UE 3d-05 has to report the measurement results to the MeNB 3d-00. In order for SgNB3d-10 to efficiently transceive data to/from UE 3d-05, sgNB3d-10 requires the serving cell to function similarly as PCell 3d-25 of MCG 3d-20, and in this disclosure, the serving cell is referred to as primary SCell (PSCell) 3d-35.PSCell 3d-35 is set as one of serving cells of SCG 3d-40 and is characterized by having PUCCH as an uplink control channel. The UE 3d-05 transmits HARQ ACK/NACK information, channel State Information (CSI) information, a Scheduling Request (SR), and the like to the base station using the PUCCH.

The present disclosure provides a method of reporting a remaining transmission power (power headroom) of a UE to a base station, the method being performed by the UE transceiving data using multiple Radio Access Technologies (RATs) simultaneously in a wireless communication system.

According to the present disclosure, the UE accurately reports available transmission power to each of the base stations, and thus the base stations can correctly perform uplink scheduling.

Fig. 3E illustrates a method of transmitting an uplink according to a configuration and a type of the uplink according to an embodiment of the present disclosure.

In fig. 3E, example 1 corresponds to the following scenario: two serving cells, i.e., PCell 3e-01 and SCell 3e-03, are configured to a UE, and thenThe UE performs uplink transmission according to the scheduling of the base station. In this scenario, the UE cannot simultaneously transmit PUCCH and PUSCH in one serving cell due to limitations of the transmission method and RF structure. Therefore, the UE transmits PUSCH (3 e-05) with PUCCH information embedded therein. In this regard, the UE transmits PUCCH information in PCell 3e-01, or when there is no PUSCH transmitted in PCell 3e-01, the UE transmits PUCCH information in an SCell having a low index among scells. The PHR message is sent as part of the PUSCH, so in this scenario, the UE is required to report only the maximum transmission power P by from each serving cell _CMAX,c A power margin value obtained by subtracting a transmission power, which is consumed by transmitting PUSCHs (3 e-05 and 3 e-07). This is referred to as a type 1 power headroom.

Also, example 2 corresponds to the following scenario: two serving cells, i.e., PCell 3e-11 and SCell3e-13, are configured to the UE, and then the UE performs uplink transmission according to the scheduling of the base station. In this scenario, the UE has the capability of simultaneously transmitting the PUCCH and the PUSCH in one serving cell, or separately transmitting the PUSCH and the PUCCH by using an uplink transmission technique in which simultaneous transmission can be performed. In this regard, in the PCell (or when PUCCH may be transmitted in the SCell, it is applied to the SCell), the UE is required to report the maximum transmission power P through the slave PCell in consideration of the transmission power consumed not only by the PUSCH transmission (3 e-17) but also by the PUCCH transmission (3 e-15) _CMAX,c A power headroom value obtained by subtracting both the PUSCH transmission value and the PUCCH transmission value. This is referred to as a type 2 power headroom.

The UE reports the power headroom by using the single entry PHR format 3e-21 or the multi entry PHR format 3e-31 when the UE reports the type 1 power headroom or the type 2 power headroom, and reports the power headroom by using the multi entry PHR format 3e-31 when the dual connection is configured. In this regard, the power headroom is reported as shown by 3e-41, 3e-51, 3e-61, etc., and when reporting is required, P corresponding thereto is also reported _CMAX,c Values (see 3e-43, 3e-53 and 3 e-63). When the UE reports the power headroom, the UE uses a field having a length of 6 bits, as shown in fig. 3E, and in LTE, the field has a value as shown in the following table.The table is called [ Table 2]]。

[ Table 2]

Reporting the value	Measured quality 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

In NR, frequency ranges are roughly specified as the following two frequency ranges according to the frequency coverage range in which the base station operates.

[ Table 3]

Frequency range designation	Corresponding frequency range
		FR1	450MHz–6000MHz
FR2	24250MHz–52600MHz

A base station operating in FR1 and a base station operating in FR2 may request significantly different transmission powers from the UE to operate in each of the base stations. Therefore, a table different from [ table 2] of LTE may be defined according to a frequency range (i.e., according to each of FR1 and FR 2).

For example, for PHR reporting for a base station operating in FR1 among NR base stations, the following [ table 4] may be used (since FR1 of table 4 is not much different from the frequency range of LTE, the same table as [ table 2] of LTE is shown for convenience, however [ table 4] may have different values).

[ Table 4]

As another example, for PHR reporting for a base station operating in FR1 among NR base stations, the following [ table 5] may be used.

[ Table 5]

Accordingly, when the UE reports the PHR with respect to each cell that the current base station is configured to the UE and is activated, the UE generates a value based on a table according to the type of the corresponding serving cell and reports the value to the base station even when the UE uses the same PH reporting field having a multi-entry PHR format according to the RAT and the operating frequency of the corresponding serving cell.

In EN-DC, an LTE base station as MeNB and an NR base station as SgNB may not be able to recognize each other's operating frequency. This is because MeNB and SgNB can be designed to operate separately to ensure independent operation between them. Therefore, when the UE reports the PHR to the LTE base station as the MeNB, the frequency range in which the LTE serving cell operates and the PHR report table corresponding thereto are related only to table 2, and the UE performs reporting according to table 2. In the EN-DC case, when the UE reports the PHR, the UE must report a serving cell for the SgNB (i.e., NR base station), and in this regard, the LTE base station receiving the PHR does not know frequency information for the serving cell for the NR base station, and thus 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 for reporting to the NR base station. However, when the UE reports to the LTE base station, the UE uses the value of POWER _ overhead _ 63. In case that the UE reports the PHR report to the SgNB (i.e., NR base station), when the PH value is 45dB, the UE reports an accurate value by using a value of POWER _ HEADROOM _ 58.

A scenario of dual connection between NR base stations is called NR-DC, and even in this case, the NR base station as MgNB and the NR base station as SgNB may not be able to recognize each other's operating frequency. This is because MeNB and SgNB can be designed to operate separately to ensure independent operation between them. In this case, when the UE reports the PHR about the serving cell included in the base station to which the UE is currently reporting, the UE reports the PHR according to the frequency operating range (FR 1 or FR 2). However, when the serving cell is not included in the base station to which the UE is currently reporting (i.e., the serving cell for the SCG when reporting PHR to the MCG, or the serving cell for the MCG when reporting PHR to the SCG), the UE reports the PHR value to the base station according to table 4 (i.e., FR 1). Alternatively, the UE may inform the base station whether the corresponding value is related to table 4 of FR1 or table 5 of FR2 by using one bit of R bits 3e-39 reserved in the multi-entry PHR format, respectively, and thus the UE may inform the base station of the exact value.

Fig. 3F illustrates a message flow between a UE3F-01 and an LTE eNB3F-03 to which the UE reports PHR while establishing dual connectivity between different RATs according to an embodiment of the disclosure.

The UE3f-01 in the idle state scans the surrounding environment of the UE3f-01 and selects an appropriate LTE base station (or cell), i.e. LTE eNB3f-03, and when the UE3f-01 determines to access the cell, the UE3f-01 sends an access request message (3 f-11) to the LTE eNB3f-03 by means of a random access procedure. By using the above uplink access technique, the access request message is transmitted as an RRC layer message.

Thereafter, the UE3f-01 receives the access configuration message (3 f-13) and sends an access configuration complete message (3 f-15) as its acknowledgement message, thereby completing access to the LTE eNB3 f-03. When the UE3f-01 receives the access configuration message, the UE3f-01 may transition to the connected state and may transceive data to/from the LTE eNB3 f-03. Thereafter, in order to receive a PHR report for the LTE eNB3f-03 to perform scheduling for the UE3f-01, the LTE eNB3f-03 may configure parameters related to PHR by using an RRC layer message (3 f-19). The PHR-related parameters may include periodicPHR-Timer, prohibitPHR-Timer, downlink (dl) -pathsschange (downlink (dl) path loss change), and the like. The PeriodicPHR-Timer is a Timer configured to periodically report a PHR value to a base station, the prohibitPHR-Timer is a Timer configured to prevent frequent PHR reporting, and the value of dl-pathchange is a threshold value at which the PHR is reported when the variation in reception of a downlink channel is equal to or greater than the value. The connection reconfiguration message may include configuration information related to a radio bearer used in the data transmission, or a separate connection reconfiguration message may be sent again for radio bearer configuration. In addition, when the UE3f-01 is configured by the LTE eNB3f-03 to measure the neighboring NR base station and then report the result thereof, configuration (3 f-17) is performed between the LTE eNB3f-03 and the NR base station, and then information relating to additional configuration to use not only the LTE eNB3f-03 but also the NR gbb 3f-05 may also be included in the RRC message. That is, information for configuration of dual connectivity (EN-DC) may also be included in the RRC message. The RRC configuration is based on an RRCConnectionReconfiguration message. The UE3f-01 receives the RRC layer message and sends an acknowledgement message (3 f-21) to the LTE eNB3 f-03. The acknowledgement message corresponds to an rrcconnectionreconfiguration complete message.

When establishing a dual connection enabling simultaneous use of an LTE base station and an NR base station based on a configuration message, the UE3f-01 can perform data exchange with the LTE eNB3f-03 and the NR gNB3f-05 (3 f-25 and 3 f-27) simultaneously.

A condition when the PHR is transmitted to the base station (i.e., when the report is triggered) may be defined, and the following condition may be defined in the LTE system and the NR system.

-when the prohibitprr-Timer expires, when the variation of the downlink reception strength is equal to or greater than the value of dl-PathlossChange dB.

-when periodicPHR-Timer expires.

When PHR reporting is initially configured.

When adding an SCell comprising uplink.

When adding PSCell of secondary base station while using dual connectivity technique.

When the above PHR trigger condition occurs in each of the LTE enbs 3f-03 and NR gNB3f-05 (3 f-31 and 3 f-41), the UE3f-01 generates and reports a PHR to the LTE enbs 3f-03 and NR gNB3f-05 (3 f-33 and 3 f-43), respectively.

When the condition is met in the LTE eNB3f-03 (3 f-31), the UE3f-01 includes values of type 1 power headroom for all serving cells currently configured and activated in the LTE eNB3f-03 and NR gNB3f-05, and reports PHR (3 f-33) to the LTE eNB3 f-03. Further, when actual transmission occurs in the LTE eNB3f-03 or NR gNB3f-05 at the time of reporting PHR, P for the cell for which the type 1 power headroom is reported is also included and reported _CMAX,c The value is obtained. In addition, in fig. 3F, it is assumed that the LTE base station is the MeNB, and thus, when the UE3F-01 is configured to be capable of doing soWhen PUCCH and PUSCH are simultaneously transmitted in a PCell, which is a representative cell of the MeNB, the UE3f-01 also includes a value of type 2 power headroom of the PCell in the PHR, and reports the PHR. In addition, in fig. 3F, since the base station to which PHR is reported is an LTE base station, UE3F-01 generates a value according to the aforementioned table 2 (i.e., the table used when reporting PHR of LTE) and reports the value to the base station regardless of whether the cell is a serving cell corresponding to the LTE base station or a serving cell corresponding to the NR base station.

When the condition is met in the NR gNB3f-05 (3 f-41), the UE3f-01 includes values for type 1 power headroom for all serving cells currently configured and activated in the LTE eNB3f-03 and the NR gNB3f-05, and reports PHR to the NR gNB3f-05 (3 f-43). Further, when actual transmission occurs in LTE eNB3f-03 or NR gNB3f-05 at the time of reporting PHR, P for the cell for which type 1 power headroom is reported is also included and reported _CMAX,c The value is obtained. In addition, in fig. 3F, since the condition is satisfied in NR gNB3F-05, it is assumed that the LTE base station is the MeNB, and the UE3F-01 reports PHR to NR gNB3F-05, and therefore, when the UE3F-01 is configured to be able to simultaneously transmit PUCCH and PUSCH in a PSCell that is a representative cell of NR gNB3F-05 (i.e., sgNB), the UE3F-01 also includes a value of type 2 power headroom of the PSCell in the PHR, and reports PHR. In addition, the UE3f-01 reports a type 2 power headroom for the PCell of the LTE base station, and when the UE3f-01 is configured to report an actual transmission value, the UE3f-01 will report P for the PCell of the LTE base station _CMAX,c The value is included in a report and the report is sent. In fig. 3F, the base station receiving the PHR is an NR base station, and it is assumed that the NR base station understands all tables in table 3, table 5, and table 6. Thus, when the serving cell corresponds to an LTE base station, UE3f-01 generates a value according to table 2 (i.e., a table used when reporting PHR of LTE) and reports the value to the base station, and in the case of an NR serving cell, UE3f-01 reports the remaining transmission power of UE3f-01 by reporting to the base station according to table 4 in the case of FR1 and according to table 5 in the case of FR2 depending on the operating frequency range.

Accordingly, when each respective condition occurs, the PHR is reported to the respective base station, and the base station may determine the current remaining power of the UE and may perform scheduling on the UE appropriately.

Fig. 3G is a diagram illustrating an operational flow of a UE when the UE reports a PHR while dual connectivity is established between different RATs according to an embodiment of the present disclosure.

The UE in idle state scans the UE's surroundings and selects an appropriate LTE base station (or cell) and attempts to access the LTE base station (3 g-03). For this, the UE transmits an RRCConnectionRequest message of an RRC layer to the LTE base station, receives an RRCConnectionSetup message from the LTE base station, transmits an RRCConnectionSetup complete message to the LTE base station, and completes an access procedure.

Thereafter, the UE receives an RRC layer configuration message for reporting the PHR from the LTE base station and transmits an acknowledgement message (3 g-05) thereto. The RRC layer configuration message may be an RRCConnectionReconfiguration message and the acknowledgement message may be an RRCConnectionReconfiguration complete message. The configuration message may include parameters related to the PHR, including periodicPHR-Timer, prohibitpyr-Timer, dl-pathlength change, and the like. The PeriodicPHR-Timer is a Timer configured to periodically report a PHR value to a base station, the prohibitPHR-Timer is a Timer configured to prevent frequent PHR reporting, and the value of dl-pathchange is a threshold value at which the PHR is reported when the variation in reception of a downlink channel is equal to or greater than the value. The connection reconfiguration message may include configuration information related to a radio bearer used in the data transmission, or a separate connection reconfiguration message may be sent again for configuration. In addition, when the UE is configured by the base station to measure the adjacent NR base station and then report the result thereof, information may also be included in the message, which relates to additional configurations to use not only the LTE base station but also the NR base station. That is, information for configuration of dual connectivity may also be included in the message.

Thereafter, the UE determines whether to trigger PHR reporting for each base station according to the following conditions based on the configured parameters (3 g-07).

-when the prohibitpyr-Timer expires, when the variation of the downlink reception strength is equal to or greater than the value of dl-PathlossChange dB configured by the base station.

-when the periodicPHR-Timer configured by the base station for periodic reporting expires.

When PHR reporting is initially configured.

When adding an SCell comprising uplink.

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

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, the PHR message including values of type 1 power headroom for all serving cells currently configured and activated in the LTE and NR base stations. In addition, when actual transmission occurs in an LTE base station or an NR base station when reporting PHR, P regarding a cell for which a type 1 power headroom is reported is also included in the generated PHR message _CMAX,c The value is obtained. In addition, in fig. 3G, it is assumed that the LTE base station is an MeNB, and when the UE is configured to be able to simultaneously transmit a PUCCH and a PUSCH in a PCell, which is a representative cell of the MeNB, the UE includes a value of a type 2 power headroom of the PCell in the generated PHR message. In addition, in fig. 3G, since the base station to which the PHR is reported is an LTE base station, regardless of whether the cell is a serving cell corresponding to the LTE base station or a serving cell corresponding to the NR base station, the UE generates a value according to the above table 2 (i.e., a table used when reporting the PHR of LTE), and reports the value to the base station (3G-11).

When EN-DC is not configured in the UE, DC is configured between NR base stations, or when a condition is satisfied in the NR gbb (even if EN-DC is configured), the UE generates a PHR message to report to the NR gbb, the PHR message including values of type 1 power headroom for all serving cells currently configured and activated in the LTE and NR base stations. In addition, when actual transmission occurs in an LTE base station or an NR base station at the time of reporting PHR, P with respect to a cell for which type 1 power headroom is reported _CMAX,c Values are also included in the generated PHR messageAnd (4) performing secondary fermentation. In addition, in fig. 3G, since the condition is satisfied in the current NR gNB, it is assumed that the LTE base station is the MeNB and the UE reports the PHR to the NR gNB, and thus, when the UE is configured to be able to simultaneously transmit the PUCCH and the PUSCH in the PSCell, which is a representative cell of the NR gNB (i.e., sgNB), the UE also includes a value of the type 2 power headroom of the PSCell in the generated PHR message. Also, the UE reports a type 2 power headroom for a PCell of the LTE base station, and when the UE is configured to report an actual transmission value, the UE generates a P including the PCell of the LTE base station _CMAX,c Reporting of the value. In fig. 3G, the base station receiving the PHR is an NR base station, and it is assumed that the NR base station understands all tables in table 3, table 5, and table 6. Thus, when the serving cell corresponds to an LTE base station, the UE generates a value according to table 2 (i.e., a table used when reporting PHR of LTE) and reports the value to the base station, and in the case of an NR serving cell, the UE reports the remaining transmission power of the UE by reporting to the base station according to table 4 in the case of FR1 and according to table 5 in the case of FR2 depending on the operating frequency range (3 g-13). In case of DC between NR base stations, when a serving cell is not included in a base station to which the UE is currently reporting (i.e., a serving cell for an SCG when reporting PHR to an MCG, or a serving cell for an MCG when reporting PHR to an SCG), the UE reports a PHR value to the base station according to table 4 (i.e., FR 1). Alternatively, the UE may inform the base station of whether the corresponding value is related to table 4 of FR1 or table 5 of FR2, respectively, by using one bit of R bits 3e-39 reserved in the multi-entry PHR format, and thus, the UE may inform the base station of the accurate value.

Thereafter, the PHR is reported to the base station (3 g-15) to inform the base station of the current remaining power of the UE. Accordingly, the base station may determine the current remaining power of the UE and may perform scheduling appropriately for the UE.

Referring to FIG. 3H, the UE includes an RF processor 3h-10, a baseband processor 3h-20, a storage device 3h-30, and a controller 3h-40.

The RF processors 3h-10 perform functions including conversion, amplification, etc. of frequency bands of signals in order to transmit and receive signals through a wireless channel. That is, the RF processors 3h-10 up-convert baseband signals provided from the baseband processors 3h-20 into RF band signals, and receive the RF band signals via the antennas, and down-convert the RF band signals received via the antennas into baseband signals. For example, the RF processors 3h-10 may include transmit filters, receive filters, amplifiers, mixers, oscillators, DACs, ADCs, and the like. Although fig. 3H shows only one antenna, the UE may include multiple antennas. Also, the RF processors 3h-10 may include a plurality of RF chains. Further, the RF processors 3h-10 may perform beamforming. To perform beamforming, the RF processors 3h-10 may adjust the phase and amplitude of individual signals transceived via multiple antennas or antenna elements.

The baseband processors 3h-20 perform a conversion function between the baseband signal and the bit stream according to the physical layer specification of the system. For example, in data transmission, the baseband processors 3h to 20 generate complex symbols by encoding and modulating a transmitted bit stream. In addition, in data reception, the baseband processor 3h-20 reconstructs a received bit stream by demodulating and decoding a baseband signal provided from the RF processor 3 h-10. For example, when transmitting data according to the OFDM scheme, the baseband processors 3h-20 generate complex symbols by encoding and modulating a transmitted bit stream, map the complex symbols to subcarriers, and configure OFDM symbols by performing an IFFT operation and inserting a Cyclic Prefix (CP). In addition, in data reception, the baseband processor 3h-20 may 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 reconstruct a received bit stream by decoding the signal through demodulation.

The baseband processor 3h-20 and the RF processor 3h-10 transmit and receive signals as described above. The baseband processor 3h-20 and the RF processor 3h-10 may thus be referred to as a transmitter, a receiver, a transceiver or a communicator. Further, at least one of the baseband processor 3h-20 and the RF processor 3h-10 may include different communication modules to support a plurality of different radio access technologies. Also, at least one of the baseband processor 3h-20 and the RF processor 3h-10 may include different communication modules to process signals of different frequency bands. Examples of different wireless access technologies may include Wireless Local Area Networks (WLANs) (e.g., institute of Electrical and Electronics Engineers (IEEE) 802.11), cellular networks (e.g., LTE networks), and so on. Also, examples of the different frequency bands may include an SHF frequency band (e.g., 2.5GHz, 5GHz, etc.) and a millimeter wave (e.g., 60 GHz) frequency band.

The storage means 3h-30 may store data such as default programs, application programs, and configuration information for the operation of the UE. In particular, the storage means 3h-30 may store information about WLAN nodes configured to perform wireless communication by using a WLAN access technology. In addition, the storage device 3h-30 supplies the stored data in response to a request of the controller 3h-40.

The controllers 3h-40 control the overall operation of the UE. For example, the controller 3h-40 transmits and receives signals through the baseband processor 3h-20 and the RF processor 3 h-10. In addition, the controller 3h-40 records and reads data stored in the storage device 3 h-30. To this end, the controllers 3h-40 may include at least one processor. For example, the controllers 3h-40 may include a Communication Processor (CP) configured to perform communication control and an AP configured to control an upper layer such as an application program. According to an embodiment of the present disclosure, the controller 3h-40 includes a multi-connection processor 3h-42, the multi-connection processor 3h-42 being configured to perform processing to operate in a multi-connection mode. For example, the controller 3h-40 may control the UE of FIG. 3E to perform procedures for the operation of the UE.

According to an embodiment of the present disclosure, the controller 3h-40 receives the PHR configuration from a control message received from the base station, and when the dual connection is configured, the controller 3h-40 determines which PHR information to transmit according to the type of RAT of the base station, even the type of RAT of another base station (not the base station to which the UE reports), and transmits a message to the base station to transmit the PHR information.

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

When implemented as software, a non-transitory computer-readable storage medium storing at least one program (software module) may be provided. At least one program stored in a 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 that cause the electronic device to perform a method according to an embodiment of the disclosure described in the claims or specification of the disclosure.

At least one program (software module, software) may be stored in a non-volatile memory including Random Access Memory (RAM) and flash memory, read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disk storage devices, compact disk-ROM (CD-ROM), digital Versatile Disks (DVD), other optical storage devices, magnetic cassettes, and the like, or may be stored in a memory comprised of any or all combinations of the foregoing. Further, each of the configuration memories may be provided in a plurality of numbers.

The at least one program may be stored in an attachable storage device, which may be accessed 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 the apparatus for performing embodiments of the present disclosure via an external port. Further, a separate storage device on the communication network may access the means for performing embodiments of the present disclosure.

In the foregoing embodiments of the present disclosure, each component in the present disclosure is expressed in a singular form or a plural form according to an embodiment of the present disclosure. However, for convenience of description, expressions in singular or plural form suitable for the provided case are selected, and thus the present disclosure is not limited to the singular or plural form. Therefore, even when an element is expressed in the plural, the element may be configured in the singular, and even when an element is expressed in the singular, the element may be configured in the plural.

While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents. For example, portions of one embodiment of the present disclosure may be combined with portions of another embodiment in such a manner as to be able to operate the base station and the UE. Although the embodiments of the present disclosure are proposed based on a Frequency Division Duplex (FDD) LTE system, modified embodiments based on the technical concept of the embodiments may be performed 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 apparatus in a wireless communication system, the method comprising:

generating, by the Service Data Adaptation Protocol (SDAP) entity, second data by adding an SDAP header to the first data based on receiving the first data;

transmitting, by the SDAP entity, second data to a Packet Data Convergence Protocol (PDCP) entity;

generating, by the PDCP entity, an Uplink Data Compression (UDC) data block by uplink data compression on the second data, wherein the uplink data compression is not performed on the SDAP header in the second data;

generating, by the PDCP entity, a UDC header;

adding, by the PDCP entity, a UDC header to the SDAP header;

performing integrity protection on the UDC header, the SDAP header, and the UDC data block by the PDCP entity;

performing, by the PDCP entity, ciphering on the integrity-protected UDC header and the integrity-protected UDC data block, wherein ciphering is not performed on the integrity-protected SDAP header;

generating, by the PDCP entity, third data comprising a PDCP header, a ciphered UDC data block, and an integrity-protected SDAP header; and

transmitting, by the PDCP entity, the third data to the lower layer.

2. The method of claim 1, wherein performing integrity protection comprises:

a message authentication code MAC-I for integrity is generated by the PDCP entity,

concatenation of MAC-I by PDCP entity to integrity protected UDC data block, and

wherein performing encryption comprises:

ciphering is performed on the MAC-I by the PDCP entity.

3. The method of claim 1, further comprising:

receiving at least one of SDAP header configuration information, UDC configuration information, or integrity protection configuration information through higher layer signaling.

4. A method performed by a receiving device in a wireless communication system, the method comprising:

removing, by a Packet Data Convergence Protocol (PDCP) entity, a PDCP header from the first data based on receiving the first data from a lower layer by the PDCP entity;

performing, by the PDCP entity, deciphering of a portion of the first data including an Uplink Data Compression (UDC) header and a UDC data block, wherein deciphering is not performed on a Service Data Adaptation Protocol (SDAP) header in the first data;

performing, by the PDCP entity, integrity verification on the decrypted UDC header, the decrypted UDC data block, and the SDAP header;

performing, by the PDCP entity, decompression of the integrity-verified UDC data block based on the integrity-verified UDC header;

the decompressed UDC data block and the SDAP header are sent to an upper layer by the PDCP entity.

5. The method of claim 4, wherein performing decryption comprises:

decrypting, by the PDCP entity, a message authentication code MAC-I for integrity included in the first data, and

wherein performing integrity verification comprises:

the calculated MAC-I is calculated by the PDCP entity, i.e., X-MAC is calculated, an

When X-MAC equals MAC-I, the integrity verification is successfully identified by the PDCP entity.

6. The method of claim 4, further comprising:

7. A transmission apparatus in a wireless communication system, the transmission apparatus comprising:

a transceiver; and

a controller implementing a Service Data Adaptation Protocol (SDAP) entity, a Packet Data Convergence Protocol (PDCP) entity, and a lower layer, the controller configured to:

based on receiving the first data, generating, by the SDAP entity, second data by adding an SDAP header to the first data;

transmitting, by the SDAP entity, the second data to the PDCP entity;

generating, by the PDCP entity, a UDC header;

adding, by the PDCP entity, a UDC header to the SDAP header;

transmitting, by the PDCP entity, the third data to the lower layer.

8. The transmission apparatus of claim 7, wherein the controller is further configured to:

ciphering is performed on the MAC-I by the PDCP entity.

9. The transmission apparatus of claim 7, wherein the controller is further configured to:

receiving, via the transceiver, at least one of SDAP header configuration information, UDC configuration information, or integrity protection configuration information through higher layer signaling.

10. A receiving apparatus in a wireless communication system, the receiving apparatus comprising:

a transceiver; and

a controller implementing a Packet Data Convergence Protocol (PDCP) entity and a lower layer, the controller configured to:

removing, by the PDCP entity, the PDCP header from the first data based on receiving the first data from the lower layer by the PDCP entity;

the decompressed UDC data block and the SDAP header are transmitted to an upper layer by the PDCP entity.

11. The receiving apparatus of claim 10, wherein the controller is further configured to:

calculating the calculated MAC-I by the PDCP entity, i.e., calculating the X-MAC, an

12. The receiving apparatus of claim 10, wherein the controller is further configured to:

receiving, via the transceiver, at least one of SDAP header configuration information, UDC configuration information, or integrity protection configuration information by high layer signaling.