KR20190085454A - Method and apparatus for wireless communication in wireless communication system - Google Patents

Abstract

The present disclosure relates to a communication method and apparatus in a wireless communication system. According to an embodiment of the present invention, the communication method in the wireless communication system comprises the steps of: receiving management object information from a network through an application level data message or higher signaling; identifying an attempt to access a non access stratum (NAS); mapping one or more access identities and one access category based on the management object information; and delivering the mapped access identities and information of the access category to an access stratum (AS).

Description

TECHNICAL FIELD [0001] The present invention relates to a method and apparatus for communication in a wireless communication system,

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

Efforts are underway to develop an improved 5G or pre-5G communication system to meet the growing demand for wireless data traffic after commercialization of the 4G communication system. For this reason, a 5G communication system or a pre-5G communication system is called a system after a 4G network (Beyond 4G network) communication system or after a LTE system (Post LTE). To achieve a high data rate, a 5G communication system is being considered for implementation in a very high frequency (mmWave) band (e.g., a 60 Gigahertz (70GHz) band). In order to mitigate the path loss of the radio wave in the very high frequency band and to increase the propagation distance of the radio wave, in the 5G communication system, beamforming, massive MIMO, full-dimension MIMO (FD-MIMO ), Array antennas, analog beam-forming, and large scale antenna technologies are being discussed. In order to improve the network of the system, the 5G communication system has developed an advanced small cell, an advanced small cell, a cloud radio access network (cloud RAN), an ultra-dense network, (D2D), a wireless backhaul, a moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation Have been developed. In addition, in the 5G system, the Advanced Coding Modulation (ACM) scheme, Hybrid FSK and QAM Modulation (FQAM) and Sliding Window Superposition Coding (SWSC), the advanced connection technology, Filter Bank Multi Carrier (FBMC) (non-orthogonal multiple access), and SCMA (sparse code multiple access).

On the other hand, the Internet is evolving into an Internet of Things (IoT) network in which information is exchanged between distributed components such as objects in a human-centered connection network where humans generate and consume information. IoE (Internet of Everything) technology, which combines IoT technology with big data processing technology through connection with cloud servers, is also emerging. In order to implement IoT, technology elements such as sensing technology, wired / wireless communication, network infrastructure, service interface technology and security technology are required. In recent years, sensor network, machine to machine , M2M), and MTC (Machine Type Communication). In the IoT environment, an intelligent IT (Internet Technology) service can be provided that collects and analyzes data generated from connected objects to create new value in human life. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, and advanced medical service through fusion of existing information technology . ≪ / RTI >

Accordingly, various attempts have been made to apply the 5G communication system to the IoT network. For example, technologies such as a sensor network, a machine to machine (M2M), and a machine type communication (MTC) are implemented by techniques such as beam forming, MIMO, and array antennas, which are 5G communication technologies . The application of the cloud radio access network (cloud RAN) as the big data processing technology described above is an example of the convergence of 3eG technology and IoT technology.

The disclosed embodiments provide an apparatus and method that can effectively provide communication in a wireless communication system.

According to an embodiment, a method of communicating a terminal in a wireless communication system includes receiving management object information from a network through an application level data message or superior signaling; Identifying an access attempt to a NAS (Non Access Stratum); Mapping one or more access identities and one access category based on the managed object information; And transmitting the mapped access identity and access category information to an AS (Access Stratum).

FIG. 1A is a diagram illustrating a structure of a next generation mobile communication system to which an embodiment is applied.
FIG. 1B is a diagram for explaining a method for determining whether an access is granted in the LTE system.
1C is a diagram for explaining a process of performing an ACDC operation in an LTE system.
1D is a diagram for explaining the configuration of ACDC setup information in the LTE system.
FIG. 1E is a diagram for explaining a process of performing access control of a connection mode or an idle mode UE according to an exemplary embodiment. Referring to FIG.
1F is a flowchart illustrating a process of performing access control by a connection mode or an idle mode UE according to an exemplary embodiment of the present invention.
FIG. 1G is a flowchart of a terminal NAS operation according to an embodiment.
1H is a flowchart of the terminal AS operation according to one embodiment.
FIG. 1I is a block diagram illustrating an internal structure of a UE according to an exemplary embodiment of the present invention.
1J is a block diagram illustrating a configuration of a base station according to an embodiment.
2A is a diagram illustrating a structure of an LTE system to which an embodiment is applied.
FIG. 2B is a diagram illustrating a wireless protocol structure in an LTE system to which an embodiment is applied.
2C is a diagram illustrating a structure of a next generation mobile communication system to which an embodiment is applied.
FIG. 2D is a diagram illustrating a wireless protocol structure of a next generation mobile communication system to which an embodiment is applied.
FIG. 2E is a diagram illustrating a procedure for determining whether or not a base station performs uplink data compression when a UE establishes a connection with a network according to an exemplary embodiment. Referring to FIG.
FIG. 2F is a diagram illustrating a procedure and data structure for performing uplink data compression according to an exemplary embodiment.
FIG. 2G is a diagram illustrating uplink data compression according to an embodiment.
FIG. 2H is a diagram illustrating a procedure and data structure for performing ROHC (Robust Header Compression) header compression according to an embodiment.
FIG. 2I is a diagram illustrating a procedure for generating an SDAP header for data received from an upper layer according to an embodiment, applying integrity protection to an SDAP header in a PDCP layer device, and not performing encryption.
FIG. 2J is a diagram for explaining a procedure of generating an SDAP header for data received from an upper layer according to an exemplary embodiment, and not performing integrity protection on the SDAP header in the PDCP layer device, and not performing encryption.
FIG. 2K is a diagram illustrating a gain in a structure of a base station implementation when a non-encrypted or an integrity-protected SDAP header according to an exemplary embodiment is applied.
FIG. 21 is a diagram illustrating a processing gain obtainable in a base station and a terminal implementation when an SDAP header that is not encrypted and has not been subjected to integrity protection according to an exemplary embodiment is applied.
FIG. 2M is a flowchart illustrating a method of generating an SDAP header for data received from an upper layer according to an exemplary embodiment of the present invention, performing integrity protection on an SDAP header in a PDCP layer device, Fig.
FIG. 2n is a diagram illustrating a processing gain obtainable in a base station and a terminal when a non-encrypted SDAP header is not encrypted and an MAC-I is not encrypted according to an exemplary embodiment.
FIG. 20 illustrates a procedure for generating an SDAP header for data received from an upper layer according to an embodiment, performing header compression (ROHC) in the PDCP layer device, applying integrity protection to the SDAP header, and not performing encryption to be.
FIG. 2P illustrates a procedure for generating an SDAP header for data received from an upper layer according to an exemplary embodiment, performing header compression (ROHC) in the PDCP layer device, performing integrity protection on the SDAP header, and not performing encryption Fig.
FIG. 2Q is a diagram illustrating a processing gain that can be obtained in a base station and a terminal implementation when an SDAP header that is not encrypted and has not been subjected to integrity protection according to an exemplary embodiment is applied.
FIG. 2r is a diagram illustrating a method of generating an SDAP header for data received from an upper layer according to an exemplary embodiment, performing header compression (ROHC) on a PDCP layer device, performing integrity protection on an SDAP header, I < / RTI >
FIG. 2S illustrates a processing gain that can be obtained in the base station and the terminal implementation when applying an SDAP header that is not encrypted and has not been subjected to integrity protection according to an embodiment, performs header compression (ROHC), and does not encrypt MAC- FIG.
FIG. 2T illustrates a method of generating an SDAP header for data received from an upper layer according to an exemplary embodiment, performing uplink data compression (UDC) on a PDCP layer device, applying integrity protection to a UDC header, And applies integrity protection to the SDAP header and does not perform encryption.
FIG. 2U shows an example of generating an SDAP header for data received from an upper layer according to an exemplary embodiment, performing uplink data compression (UDC) on a PDCP layer device, applying integrity protection to a UDC header, FIG. 4 is a diagram illustrating a procedure for applying integrity protection to an SDAP header without performing encryption.
FIG. 2V is a diagram illustrating a method of generating an SDAP header for data received from an upper layer according to an embodiment of the present invention, performing uplink data compression (UDC) on the PDCP layer device, encrypting the UDC header without applying integrity protection And encrypting the MAC-I without performing integrity protection and applying the integrity protection to the SDAP header without performing encryption.
FIG. 2w is a diagram illustrating a processing gain that can be obtained in the base station and the terminal when the SDAP header and the UDC header, which are not encrypted and are not subjected to integrity protection, are applied according to an exemplary embodiment.
FIG. 2x illustrates a method of generating an SDAP header for data received from an upper layer according to an embodiment of the present invention, performing uplink data compression (UDC) on the PDCP layer device, encrypting the UDC header without applying integrity protection The integrity protection is not performed in the SDAP header, the encryption is not performed, and the encryption is not performed in the MAC-I.
FIG. 2 Y illustrates an example of a case where an SDAP header and an UDC header, which are not encrypted and unprotected according to an embodiment, are applied, user data compression (UDC) is performed, and MAC- Processing gain.
FIG. 2Z illustrates an operation of a SDAP / PDCP layer device in an SDAP / PDCP layer device or a bearer or a logical channel in which an integrity protection is set when an SDP header of an unencrypted SDP / Layer device according to the present invention.
FIG. 2B illustrates a structure of a UE according to an embodiment of the present invention.
2c shows a configuration of a base station according to an embodiment according to an embodiment.
3A is a diagram showing a structure of an LTE system.
3B is a diagram illustrating a wireless protocol structure of the LTE system.
3C is a diagram for explaining carrier integration in a terminal.
FIG. 3D is a diagram for explaining the concept of multiple connections in LTE and NR.
3E is a diagram illustrating an uplink transmission method according to an uplink type according to an exemplary embodiment of the present invention.
FIG. 3F is a diagram illustrating a message flow between a terminal and a base station when reporting a power headroom when applying a dual RAT-to-RAT connection according to an exemplary embodiment.
FIG. 3G is a diagram illustrating an operation sequence of a terminal when reporting a power headroom when applying a dual RAT-to-RAT connection according to an exemplary embodiment.
3H illustrates a block configuration of a UE in a wireless communication system according to an embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

In the following description of the embodiments of the present invention, descriptions of techniques which are well known in the technical field of the present invention and are not directly related to the present invention will be omitted. This is for the sake of clarity of the present invention without omitting the unnecessary explanation.

For the same reason, some of the elements in the accompanying drawings are exaggerated, omitted or schematically shown. Also, the size of each component does not entirely reflect the actual size. In the drawings, the same or corresponding components are denoted by the same reference numerals.

BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention and the manner of achieving them will become apparent with reference to the embodiments described in detail below with reference to the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. To fully disclose the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

It will be appreciated that the combinations of blocks and flowchart illustrations in the process flow diagrams may be performed by computer program instructions. These computer program instructions may be loaded into a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, so that those instructions, which are executed through a processor of a computer or other programmable data processing apparatus, Thereby creating means for performing functions. These computer program instructions may also be stored in a computer usable or computer readable memory capable of directing a computer or other programmable data processing apparatus to implement the functionality in a particular manner so that the computer usable or computer readable memory The instructions stored in the block diagram (s) are also capable of producing manufacturing items containing instruction means for performing the functions described in the flowchart block (s). Computer program instructions may also be stored on a computer or other programmable data processing equipment so that a series of operating steps may be performed on a computer or other programmable data processing equipment to create a computer- It is also possible for the instructions to perform the processing equipment to provide steps for executing the functions described in the flowchart block (s).

In addition, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing the specified logical function (s). It should also be noted that in some alternative implementations, the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may actually be executed substantially concurrently, or the blocks may sometimes be performed in reverse order according to the corresponding function.

Herein, the term " part " used in the present embodiment means a hardware component such as software or an FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit) do. However, 'part' is not meant to be limited to software or hardware. &Quot; to " may be configured to reside on an addressable storage medium and may be configured to play one or more processors. Thus, by way of example, 'parts' may refer to components such as software components, object-oriented software components, class components and task components, and processes, functions, , Subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided in the components and components may be further combined with a smaller number of components and components or further components and components. In addition, the components and components may be implemented to play back one or more CPUs in a device or a secure multimedia card. Also, in an embodiment, 'to' may include one or more processors.

A term used for identifying a connection node used in the following description, a term referring to network entities, a term referring to messages, a term indicating an interface between network objects, a term indicating various identification information Etc. are illustrated for convenience of explanation. Therefore, the present invention is not limited to the following terms, and other terms referring to objects having equivalent technical meanings can be used.

For convenience of explanation, the present invention uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard or terms and names based on them. However, the present invention is not limited by the above-mentioned terms and names, and can be equally applied to systems conforming to other standards.

1A is a diagram showing a structure of a next generation mobile communication system.

1A, a radio access network of a next-generation mobile communication system (New Radio, NR) includes a next-generation base station (gNB) 1a-10, an AMF 1a- Core Network). A user terminal (hereinafter referred to as NR UE or UE) 1a-15 accesses the external network through the gNB 1a-10 and the AMF 1a-05.

In FIG. 1A, the gNB 1a-10 corresponds to an eNB (Evolved Node B) 1a-30 of the existing LTE system. The gNB 1a-10 is connected to the NR UEs 1a-15 through a radio channel and can provide a better service than the existing Node B (1a-20). In the next generation mobile communication system, since all user traffic is served through a shared channel, a device for collecting and scheduling state information such as buffer status, available transmission power state, and channel state of UEs is required. 1a-10). One gNB 1a-10 normally controls a plurality of cells. In order to realize high-speed data transmission compared to existing LTE, it can have an existing maximum bandwidth or more, and additionally, beam-forming technology can be applied by using Orthogonal Frequency Division Multiplexing (OFDM) as a radio access technology . In addition, Adaptive Modulation and Coding (AMC) scheme is used to determine a modulation scheme and a channel coding rate in accordance with a channel state of a UE. The AMF (1a-05) performs functions such as mobility support, bearer setup, and QoS setup. The AMF 1a-05 is a device that performs various control functions as well as a mobility management function for a terminal, and is connected to a plurality of base stations. Also, the next generation mobile communication system can be interworked with the existing LTE system, and the AMF 1a-05 is connected to the MME 1a-25 through a network interface. The MMEs 1a-25 are connected to the eNBs 1a-30, which are existing base stations. A terminal supporting LTE-NR Dual Connectivity can transmit and receive data while maintaining connection to the gNBs 1a-10 as well as the eNBs 1a-30.

FIG. 1B is a diagram for explaining a method for determining whether an access is granted in the LTE system.

Referring to FIG. 1B, the LTE terminal is classified into an AS (1b-15, Access Stratum) and a NAS (1b-05, Non Access Stratum) according to functions. The AS 1b-15 performs all functions related to access, and the NAS 1b-05 performs functions related to access, such as PLMN selection and service request. The accessability is mainly performed in the terminal AS (1b-15). As mentioned above, when the network is congested, the network can restrict new access. To this end, the network broadcasts related configuration information (1b-35) so that each terminal can determine whether or not access is possible. With the addition of new requirements in LTE systems, a new barring mechanism has been proposed, resulting in several access barring checks. When the terminal NAS (1b-05) transmits a service request (1b-10) to the terminal AS (1b-15), the terminal AS (1b-15) responds to the request to check whether it can actually access the network Check whether access is possible. The terminal AS 1b-15 first performs EAB (1b-20, Extended Access Barring) when the establishment cause value of the service request (1b-10) is delay tolerant access. The EAB barring mechanism is an access check procedure that applies only to machine type communications (MTC). The terminal AS 1b-15 performs ACB (Application Specific Congestion Control for Data Communication) 1b-20 or ACB 1b-30 (Access Class Barring) when it passes the EAB 1b-20. The application requesting the service is given one ACDC category information, and the corresponding ACDC category value can be included in the service request and provided to the terminal AS (1b-15). The network provides barring configuration information by ACDC category. That is, the access check process can be performed for each application group classified into the ACDC category. If barring configuration information for the ACDC category is not provided from the network, the terminal AS (1b-15) omits the ACDC access check procedure. The terminal AS (1b-15) performs ACB 1b-30, Access Class Barring. The ACB carries out the access check procedure using the barring configuration information provided separately according to MO originating data or MO signaling. MMTEL voice / video / SMS can skip the ACB process using the ACB skip indicator (1b-25). If it is determined that access is possible in all of the above-mentioned plurality of access checking processes, then the terminal AS (1b-15) can attempt to access the network. That is, the terminal AS (1b-15) performs random access and transmits the RRC connection request message (1b-40) to the base station. There is also an access check process not performed in the terminal AS (1b-15). When the terminal AS 1b-15 receives barring configuration information (1b-45, SSAC) for the MMTEL voice / video from the network, it transfers it to the IMS layer 1b-50 in the terminal managing the corresponding service. Upon receiving the barring configuration information, the IMS layer performs an access check procedure when the corresponding service is triggered. When the SSAC is introduced, the terminal AS (1b-15) is designed to perform functions irrespective of the application or service type. Therefore, in order to control access authorization only for specific services such as MMTEL voice / video, the barring configuration information is directly transmitted to the layer that manages the service, and the access check process is performed at the layer.

In the next generation mobile communication system, there is no need to perform such a complicated process. You can design a single access check procedure from scratch that includes all the requirements introduced in LTE. This disclosure describes a single barring mechanism of the type developed in existing ACDCs.

1C is a diagram for explaining a process of performing an ACDC operation in an LTE system.

In the LTE system, the ACDC has been proposed for the purpose of judging whether or not access (application) is possible for each application (service). Each application is assigned at least one ACDC category value. The ACDC category has a value between 1 and 16. The network 1c-20 provides the ACDC category information corresponding to each application to the terminal NAS 1c-10 using the NAS message (1c-25). The network uses the SIB2 to provide the barring configuration information applicable to each ACDC category (1c-50). The barring configuration information includes ac-BarringFactor IE and ac-Barringtime IE. The range of ac-BarringFactor α is 0 ≤ α <1. The terminal AS (1c-15) derives a random value rand with 0? Rand <1, and if the random value is smaller than ac-BarringFactor, the access is not inhibited. Otherwise, access is prohibited. If it is determined that access is prohibited, the terminal AS (1c-15) delays the access attempt for a predetermined time derived using the following equation.

[Equation 1]

"Tbarring" = (0.7+ 0.6 * rand) * ac-BarringTime.

When a service request is triggered in the terminal NAS (1c-10), an ACDC category value corresponding to an application for which a service is requested is derived (1c-30). In addition, when the terminal NAS (1c-10) transmits a service request to the terminal AS (1c-15), the derived ACDC category value is included (1c-35). Upon receiving the service request, the terminal AS (1c-15) uses the ACDC barring setting information included in the SIB2 according to the ACDC category value to determine whether to grant access (1c-40). If the barring configuration information corresponding to the ACDC category does not exist in the SIB2, the application for the ACDC category considers that the access is approved in the ACDC process. If the access is approved through the access approval checking process, the terminal AS 1c-15 transmits the RRC Connection Request message while performing random access to the network (1c-45).

1D is a diagram for explaining the configuration of ACDC setup information in the LTE system.

The ACDC setup information may provide a set of barring setup information (1d-35, 1d-40) (ACDC-BarringPerPLMN 1, ACDC-BarringPerPLMN 2, ...) for each PLMN. If all PLMNs have the same set of barring configuration information, one set of barring configuration information (1d-05, ACDC-BarringForCommon-r13) can be broadcast. There are barring configuration information for each category (1d-20, 1d-25, 1d-30) in the set of barring setting information or common barring setting information per PLMN. The barring configuration information (1d-45) includes the ac-BarringFactor IE and the ac-Barringtime IE as mentioned above. If there is no barring configuration information for a particular ACDC category, then the application to the ACDC category is considered not to be accessible by the ACDC.

FIG. 1E is a diagram for explaining a process of performing access control of a connection mode or an idle mode UE according to an exemplary embodiment. Referring to FIG.

This disclosure describes an access control technique based on an access identity and an access category, similar to the existing ACDC. The access identity is defined in the 3GPP, i.e., the indication information specified in the standard document. The access identity is used to indicate a specific access as shown in the following table. It mainly refers to accesses classified as Access Classes 11 to 15, Multimedia Priority Service (MPS) with priority, and Mission Critical Service (MCS). Access Classes 11 through 15 direct access for business associates only or for public purposes.

[Table 1]

Access categories are divided into two categories. One type is standardized access category. The category is defined at the RAN level, that is, the category specified in the standard document. Therefore, different operators apply the same standardized access category. In the present disclosure, the category corresponding to Emergency belongs to the standardized access category. All accesses correspond to at least one of the standardized access categories. Another category is operator-specific (non-standardized) access categories. This category is defined outside 3GPP and is not specified in the standard document. Therefore, the meaning of one operator-specific access category for each operator is different. This is the same as the category in the existing ACDC. Any access triggered on the terminal NAS may not map to an operator-specific access category. The major difference from the existing ACDC is that the category does not correspond only to the application, but it can also correspond to other elements besides the application such as service type, call type, terminal type, user group, signaling type, . That is, it is possible to control whether or not the access granted to the other element is granted or denied. The corresponding access category is used to indicate specific access as shown in the following table. Access categories 0 through 7 are used to indicate the standardized access category, and access categories 32 through 63 are used to indicate the operator-specific access category.

[Table 2]

Specific information on the operator-specific access category information (Management Object (MO)) to the terminal NAS through the NAS signaling or the application level data transmission in the provider server 1e-25. The information indicates which element, such as an application, each operator-specific category corresponds to. For example, access category 32 may specify in the information that it corresponds to an access corresponding to a Facebook application. The base station 1e-20 provides the terminal with the category list providing the barring setting information and the barring setting information corresponding to each category, using the system information. The terminal 1e-05 includes logical blocks of the NAS 1e-10 and the AS 1e-15.

The terminal NAS (1e-10) maps the triggered access according to a predetermined rule to one or more access identities and one access category. This mapping operation is performed in all the RRC states, i.e., the connection mode (RRC_CONNECTED), the standby mode (RRC_IDLE), and the inactive mode (RRC_INACTIVE). The characteristics of each RRC state are listed as follows.

RRC_IDLE:

- A UE specific DRX may be configured by upper layers;

- UE controlled mobility based on network configuration;

- The UE:

- Monitors a Paging channel;

- Performs neigh- boring cell measurements and cell (re-) selection;

- Acquires system information.

RRC_INACTIVE:

- A UE specific DRX may be configured by upper layers or by RRC layer;

- UE controlled mobility based on network configuration;

- The UE stores the AS context;

- The UE:

- Monitors a Paging channel;

- Performs neigh- boring cell measurements and cell (re-) selection;

- Performs RAN-based notification area updates when moving outside the RAN-based notification area;

- Acquires system information.

RRC_CONNECTED:

- The UE stores the AS context.

- Transfer of unicast data to / from UE.

- At lower layers, the UE may be configured with a UE specific DRX .;

- For UEs supporting CA, use of one or more SCells, aggregated with the SpCell, for increased bandwidth;

- For UEs supporting DC, use of one SCG, aggregated with MCG, for increased bandwidth;

- Network controlled mobility, i.e. handover within NR and to / from E-UTRAN.

- The UE:

- Monitors a Paging channel;

- Monitors control channels associated with the shared data channel to determine if data is scheduled for it;

- Provides channel quality and feedback information;

- Performs neighbouring cell measurements and measurement reporting;

- Acquires system information.

Alternatively, in this access category mapping, one access may be further mapped to one operator-specific access category if it is mappable with one standardized access category. The terminal NAS (1e-10) transmits the access identity and the access category mapped together with the service request to the terminal AS (1e-15).

In the present disclosure, if the terminal AS (1e-15) receives the access identity or access category information together with the message received from the terminal NAS (1e-10) in all RRC states, it performs the wireless connection caused by the message Perform a barring check operation to determine whether this is allowed before. When the wireless connection is allowed through the barring check operation, the RRC connection establishment request is made to the network. For example, the NAS 1e-10 of the connected mode or the non-active mode terminal transmits the access identity and the access category to the terminal AS 1e-15 (1e-30) for the following reason. In the present disclosure, the following reasons are collectively referred to as a &quot; new session request &quot;.

- new MMTEL voice or video session

- sending of SMS (SMS over IP, or SMS over NAS)

- new PDU session establishment

- existing PDU session modification

- service request to re-establish the user plane for an existing PDU session

On the other hand, the NAS of the idle mode terminal transmits the access identity and the access category to the terminal AS (1e-15) at the time of a service request (Service Request).

The terminal AS (1e-15) uses the barring configuration information to determine whether access triggered by the terminal NAS (1e-10) is allowed (barring check).

A business operator may wish to allow only a certain type of service among the accesses corresponding to at least one of Access Classes 11 to 15. Accordingly, in the present disclosure, access is permitted or denied according to attributes distinguished by access categories, access belonging to Access Classes 11, 12, 13, 14, and 15 indicated by the access identity. To do this, we describe how to configure the barring configuration information in the access identity or access category. In the present disclosure, it is assumed that the barring setting information of the access category is composed of ac-barringFactor and ac-barringTime as in the barring setting information of the conventional ACB or ACDC.

1F is a flowchart illustrating a process of performing access control by a connection mode or an idle mode UE according to an exemplary embodiment of the present invention.

The terminal 1f-05 comprises the NAS 1f-10 and the AS 1f-15. The NAS 1f-10 is responsible for processes that are not directly related to the wireless connection: authentication, service request, session management, while the AS 1f-15 is responsible for the processes associated with the wireless connection. The network provides management object information to the NAS 1f-10 using an OAM (Application Level Data Message) or NAS message (1f-25). This information indicates which element, such as an application, each operator-specific access category corresponds to. The NAS 1f-10 uses this information to determine which operator-specific category the triggered access is mapped to. Triggered access includes new MMTEL services (voice call, video call), SMS transmission, new PDU session establishment, and existing PDU session change. When the service is triggered, the NAS 1f-10 maps the access identity and the access category corresponding to the attribute of the service (1f-30). The service may not be mapped to any access identity, and may be mapped to one or more access identities. The service can also be mapped to one access category. Assuming that it can be mapped to one access category, it first checks whether the service is mapped to the operator-specific access category provided by the management object. If it is not possible to map to any operator-specific access category, map it to a corresponding one of the standardized access categories. In the assumption that multiple access categories can be mapped, one service maps to one operator-specific access category and one standardized access category. However, if it is not possible to map to any operator-specific access category, map it to a corresponding one of the standardized access categories. In this mapping rule, the emergency service can be an exception. The NAS 1f-10 transmits a new session request or a service request to the AS (1f-15) together with the mapped access identity and access category (1f-40). The NAS 1f-10 transmits a new session request in a connection mode or an inactive mode, and a service request in a standby mode. The AS 1f-15 receives the barring setting information from the system information broadcasted by the network (1f-35). The barring setting information will be described later in detail. The AS 1f-15 determines whether the service request is permitted using the access identity and access category information mapped by the NAS 1f-10 and the corresponding barring setting information received from the network (1f-45) . If the service request is permitted according to a predetermined rule, the AS 1f-15 requests the RRC connection establishment or RRC connection resume to the network or transmits data related to the new session (1f-50) .

FIG. 1G is a flowchart of a terminal NAS operation according to an embodiment.

In step g-05, the terminal NAS receives management object information from the network through OAM or RRC signaling. This information indicates which element, such as an application, each operator-specific access category corresponds to.

In step g-10, the terminal NAS recognizes one of the following reasons.

- Access attempt

- new MMTEL voice or video session

- sending of SMS (SMS over IP, or SMS over NAS)

- new PDU session establishment

- existing PDU session modification

- service request to re-establish the user plane for an existing PDU session

In steps 1g-15, the terminal NAS maps one access category and one access category corresponding to the access attempt and the like. There may not be a corresponding access identity.

In steps 1g-20, the terminal NAS transmits the mapped access identity and access category information to the terminal AS together with a new session request / session modification (session management) or a service request.

1H is a flowchart of the terminal AS operation according to one embodiment.

In steps 1h-05, the terminal AS receives barring setting information from the network through the system information. The barring configuration information is provided for each access identity and access category.

In steps 1h-10, the terminal AS judges whether or not the access identity and the access category have been received from the terminal NAS together with a new session request / session modification (session management) or a service request. new session request / session modification (session management) and service request cause RRC connection establishment or RRC connection resume or data transmission for new session.

If the access identity and the access category are provided together with the new session request / session modification (session management) or the service request from the terminal NAS, in step 1h-15, the terminal AS transmits the barring configuration information corresponding to the access identity and the access category Performs a barring check using configuration information. At this time, a barring check is performed irrespective of the current RRC state of the UE.

If the access identity and the access category are not provided together with the new session request / session modification (session management) or the service request from the terminal NAS, then no barring check for any data transmission is performed in steps 1h-20. In other words, no barring check is performed for new data transmission and RRC connection resume that the NAS does not participate.

In this operation, the terminal NAS performs a barring check only for accesses providing access identities and access categories. On the other hand, accesses that the AS triggers (accesses not involving the NAS) may exist. For these accesses, omit the barring check. On the other hand, the frequency of accesses triggered by an AS may dominate and negatively affect network congestion. Therefore, a separate barring check may be required for accesses triggered by the AS. One way is for the terminal AS to perform a separate barring check on the access it triggers. The accesses triggered by the AS can be categorized according to their attributes. For example, accesses triggered by an AS can be classified as MO signaling or MO data according to their attributes. The network provides barring configuration information to be applied in connection mode or in inactive mode according to classified information, using system information or dedicated signaling. Or the barring configuration information of the access identity or access category corresponding to this kind can be reused. In one embodiment, if a terminal triggers a RAN area update in the INACTIVE state, the RAN area update is classified as MO signaling. The terminal AS performs a barring check using the barring setting information corresponding to the MO signalling. At this time, barring setting information corresponding to Access Category 3 may be reused as barring setting information.

The present disclosure describes a barring check process that considers Access Identities and Access Categories. This process can be applied not only to the connection mode but also to the standby mode.

The terminal NAS maps one or more Access Identities and one Access Category to one access and delivers it to the terminal AS. If the Access Identity is set to 0, it can be assumed that no other Access Identity is mapped.

The terminal AS judges whether the transmitted Access Identity is one and the value is 0 or not.

If at least one Access Identity is not zero, it performs a barring check based on non-zero Access Identities. To perform a barring check, use the barring configuration information that the network broadcasts. The setting information is information for determining whether or not access corresponding to the Access Identity is allowed. For example, the network may provide information for determining whether or not to allow access through the probability information between 0 and 1, such as indicating whether the access is allowed in the bitmap type information on and off or by using a barring factor can do. If at least one of the non-zero Access Identities is allowed, the terminal AS does not perform a barring check based on the Access Category, and regards that the access is finally allowed and performs the RRC connection setup for the access. If a barring check for the corresponding Access Identity is not allowed, access is prohibited, or a barring check is additionally performed using the access category and the corresponding barring setting information to finally determine whether or not access is allowed.

If the transmitted Access Identity is one and the value is 0, the terminal AS performs a barring check using the received Access Category and the corresponding barring configuration information. A barring check on the Access Identity is not performed. If it is determined that the barring check for the Access Category is allowed, the RRC connection establishment is performed considering that the access is finally allowed.

FIG. 1I is a block diagram illustrating an internal structure of a UE according to an exemplary embodiment of the present invention.

1I, a UE includes a Radio Frequency (RF) processing unit 1i-10, a baseband processing unit 1i-20, a storage unit 1i-30, and a control unit 1i-40.

The RF processor 1i-10 performs a function of transmitting and receiving a signal through a wireless channel such as band conversion and amplification of a signal. That is, the RF processor 1i-10 up-converts the baseband signal provided from the baseband processor 1i-20 to an RF band signal, transmits the RF band signal through the antenna, Signal. For example, the RF processing units 1i to 10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog converter (DAC), an analog to digital converter have. Although only one antenna is shown in FIG. 1I, the terminal may have a plurality of antennas. In addition, the RF processor 1i-10 may include a plurality of RF chains. Further, the RF processing unit 1i-10 can perform beamforming. For beamforming, the RF processing unit 1i-10 can adjust the phase and size of each of signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processor can perform MIMO and can receive multiple layers when performing a MIMO operation.

The baseband processor 1i-20 performs conversion between the baseband signal and the bitstream according to the physical layer specification of the system. For example, at the time of data transmission, the baseband processing unit 1i-20 generates complex symbols by encoding and modulating a transmission bit stream. In receiving the data, the baseband processor 1i-20 demodulates and decodes the baseband signal provided from the RF processor 1i-10 to recover the received bitstream. For example, according to an orthogonal frequency division multiplexing (OFDM) scheme, the baseband processing unit 1i-20 generates complex symbols by encoding and modulating transmission bit streams, and maps the complex symbols to subcarriers Then, OFDM symbols are constructed by performing inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. The baseband processing unit 1i-20 divides the baseband signal provided from the RF processing unit 1i-10 into OFDM symbol units and performs a fast Fourier transform (FFT) operation on the sub- And restores the received bit stream through demodulation and decoding.

The baseband processing unit 1i-20 and the RF processing unit 1i-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 1i-20 and the RF processing unit 1i-10 can be referred to as a transmitting unit, a receiving unit, a transmitting / receiving unit, or a communication unit. Furthermore, at least one of the baseband processing unit 1i-20 and the RF processing units 1i-10 may include a plurality of communication modules to support a plurality of different radio access technologies. Also, at least one of the baseband processing unit 1i-20 and the RF processing units 1i-10 may include different communication modules for processing signals of different frequency bands. For example, different wireless access technologies may include a wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), and the like. Also, different frequency bands may include a super high frequency (SHF) band (e.g., 2. NRHz, NRhz), and a millimeter wave (e.g., 60 GHz) band.

The storage unit 1i-30 stores data such as a basic program, an application program, and setting information for operation of the terminal. The storage unit 1i-30 provides the stored data at the request of the control unit 1i-40.

 The controller 1i-40 controls overall operations of the terminal. For example, the control unit 1i-40 transmits and receives signals through the baseband processing unit 1i-20 and the RF processing unit 1i-10. The control unit 1i-40 also writes and reads data in the storage unit 1i-40. To this end, the control unit 1i-40 may include at least one processor. For example, the controller 1i-40 may include a communication processor (CP) for performing communication control and an application processor (AP) for controlling an upper layer such as an application program.

1J is a block diagram illustrating a configuration of a base station according to an embodiment.

1J, the base station includes an RF processing unit 1j-10, a baseband processing unit 1j-20, a backhaul communication unit 1j-30, a storage unit 1j-40, .

The RF processor 1j-10 performs a function of transmitting and receiving signals through radio channels such as band conversion and amplification of signals. That is, the RF processor 1j-10 up-converts the baseband signal provided from the baseband processor 1j-20 to an RF band signal, transmits the RF band signal through the antenna, Signal. For example, the RF processor 1j-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. Although only one antenna is shown in FIG. 1J, the present invention is not limited to this, and a plurality of antennas may be provided. In addition, the RF processing unit 1j-10 may include a plurality of RF chains. Further, the RF processing unit 1j-10 can perform beam forming. For beamforming, the RF processor 1j-10 may adjust the phase and size of each of the signals transmitted and received via the plurality of antennas or antenna elements. The RF processor may perform downlink MIMO operation by transmitting one or more layers.

The baseband processing unit 1j-20 performs a function of converting a baseband signal and a bit string according to a physical layer standard. For example, at the time of data transmission, the baseband processing unit 1j-20 generates complex symbols by encoding and modulating transmission bit streams. In receiving the data, the baseband processor 1j-20 demodulates and decodes the baseband signal provided from the RF processor 1j-10 to recover the received bitstream. For example, in accordance with the OFDM scheme, when data is transmitted, the baseband processing unit 1j-20 generates complex symbols by encoding and modulating transmission bit streams, maps the complex symbols to subcarriers, And constructs OFDM symbols through CP insertion. Further, upon receiving the data, the baseband processing unit 1j-20 divides the baseband signal provided from the F processing unit 1j-10 into OFDM symbol units, restores the signals mapped to the subcarriers through the FFT operation , And demodulates and decodes the received bit stream. The baseband processing unit 1j-20 and the RF processing unit 1j-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 1j-20 and the RF processing unit 1j-10 may be referred to as a transmitting unit, a receiving unit, a transmitting / receiving unit, a communication unit, or a wireless communication unit.

The backhaul communication unit 1j-30 provides an interface for performing communication with other nodes in the network. That is, the backhaul communication unit 1j-30 converts a bit string transmitted from a main base station to another node, for example, a sub base station, a core network, etc., into a physical signal, converts a physical signal received from another node into a bit string do.

 The storage unit 1j-40 stores data such as a basic program, an application program, and setting information for operation of the main base station. In particular, the storage unit 1j-40 may store information on bearers allocated to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit 1j-40 may provide multiple connections to the terminal, or may store information serving as a criterion for determining whether to suspend the terminal. The storage unit 1j-40 provides the stored data at the request of the control unit 1j-50.

The control unit 1j-50 controls the overall operations of the main base station. For example, the control unit 1j-50 transmits and receives signals through the baseband processing unit 1j-20 and the RF processing unit 1j-10 or through the backhaul communication unit 1j-30. Further, the control section (1j-50) writes and reads data to the storage section (1j-40). To this end, the control unit 1j-50 may include at least one processor.

2A is a diagram illustrating a structure of an LTE system to which an embodiment is applied.

2A, the radio access network of the LTE system includes an Evolved Node B (hereinafter referred to as an ENB, a Node B or a base station) 2a-05, 2a-10, 2a-15, 25, a Mobility Management Entity) and an S-GW (2a-30, Serving-Gateway). A user equipment (hereinafter referred to as a UE or a terminal) 2a-35 accesses an external network through the ENBs 2a-05 to 2a-20 and the S-GW 2a-30.

In Fig. 2A, the ENBs 2a-05 to 2a-20 correspond to the Node B of the UMTS system. The ENB is connected to the UEs 2a-35 by radio channels and plays a more complex role than the Node Bs. In the LTE system, since all user traffic including a real-time service such as Voice over IP (VoIP) over the Internet protocol is serviced through a shared channel, status information such as buffer status, available transmission power status, And the ENB 2a-05 ~ 2a-20 takes charge of the scheduling. One ENB normally controls a plurality of cells. For example, in order to realize a transmission rate of 100 Mbps, an LTE system uses Orthogonal Frequency Division Multiplexing (OFDM) as a radio access technology, for example, at a bandwidth of 20 MHz. In addition, Adaptive Modulation & Coding (AMC) scheme is used to determine a modulation scheme and a channel coding rate in accordance with a channel state of a UE. The S-GW 2a-30 is a device for providing a data bearer and generates or removes a data bearer under the control of the MME 2a-25. The MME is a device that performs various control functions as well as a mobility management function for a terminal, and is connected to a plurality of base stations.

FIG. 2B is a diagram illustrating a wireless protocol structure in an LTE system to which an embodiment is applied.

Referring to FIG. 2B, the wireless protocol of the LTE system includes PDCP (Packet Data Convergence Protocol 2b-05 and 2b-40), RLC (Radio Link Control 2b-10 and 2b-35) Control 2b-15, 2b-30. Packet Data Convergence Protocol (PDCP) (2b-05, 2b-40) performs operations such as IP header compression / decompression. The main functions of the PDCP are summarized as follows.

- Header compression and decompression (ROHC only)

- Transfer of user data

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

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

- Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM -

- Retransmission function (PDCP SDUs at handover and for split bearers in DC, PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

- Ciphering and deciphering function

- Timer-based SDU discard in uplink.

Radio Link Control (RLC) (2b-10, 2b-35) reconfigures a PDCP PDU (Packet Data Unit) to an appropriate size and performs ARQ operations. The main functions of the RLC are summarized as follows.

- Transfer of upper layer PDUs

- ARQ function (Error Correction through ARQ (only for AM data transfer))

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

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

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

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

- Error detection (only for AM data transfer)

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

- RLC re-establishment function (RLC re-establishment)

MACs 2b-15 and 2b-30 are connected to a plurality of RLC layer devices arranged in one terminal, multiplex RLC PDUs into MAC PDUs, and demultiplex RLC PDUs from MAC PDUs. The main functions of the MAC are summarized as follows.

- Mapping between logical channels and transport channels.

- Multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels.

- Scheduling information reporting function

- HARQ (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification (MBMS service identification)

- Transport format selection function (Transport format selection)

- Padding function

The physical layers 2b-20 and 2b-25 channel-code and modulate the upper layer data, transmit them in a wireless channel by making them into OFDM symbols, or demodulate and decode OFDM symbols received through a wireless channel, .

2C is a diagram illustrating a structure of a next generation mobile communication system to which an embodiment is applied.

Referring to FIG. 2C, a radio access network of a next generation mobile communication system (NR or 5G) includes a next-generation base station (NR gNB or NR base station) 2c-10 and an NR CN (2c-05, New Radio Core Network). A user terminal (New Radio User Equipment) 2c-15 accesses the external network via the NR gNB 2c-10 and the NR CN 2c-05.

In FIG. 2C, the NR gNB (2c-10) corresponds to the eNB (Evolved Node B) of the existing LTE system. The NR gNB 2c-10 is connected to the NR UE 2c-15 through a radio channel, and can provide a better service than the Node B. In the next generation mobile communication system, since all user traffic is served through a shared channel, a device for collecting and scheduling state information such as buffer status, available transmission power state, and channel state of UEs is required. (2c-10). One NR gNB (2c-10) usually controls a plurality of cells. In order to realize high-speed data transmission in comparison with the current LTE, it can have an existing maximum bandwidth or more, and additionally, beam-forming technology can be applied by using Orthogonal Frequency Division Multiplexing (OFDM) as a radio access technology . In addition, Adaptive Modulation and Coding (AMC) scheme is used to determine a modulation scheme and a channel coding rate in accordance with a channel state of a UE. NR CN (2c-05) performs functions such as mobility support, bearer setup, and QoS setup. The NR CN (2c-05) is a device that performs various control functions as well as a mobility management function for the UE, and is connected to a plurality of base stations. Also, the next generation mobile communication system can be interworked with the LTE system, and the NR CN (2c-05) is connected to the MME 2c-25 through 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 wireless protocol structure of a next generation mobile communication system to which an embodiment is applied.

2d, the radio protocol of the next generation mobile communication system includes NR SDAP (2d-01, 2d-45), NR PDCP (2d-05, 2d-40), NR RLC , 2d-35, and NR MACs 2d-15 and 2d-30.

The main functions of the NR SDAP (2d-01, 2d-45) may include some of the following functions.

- Transfer of user plane data

- QoS flow and mapping of data bearer between uplink and downlink (mapping between a QoS flow and a DRB for both DL and UL)

- And a marking QoS flow ID in both DL and UL packets for the uplink and the downlink.

- And a function of mapping a relective QoS flow to the data bearer for the uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

For the SDAP layer device, the UE can set whether to use the header of the SDAP layer device or the SDAP layer device function for each PDCP layer device, bearer or logical channel in the RRC message. If the SDAP header If it is set, the mobile station moves the mapping information of the uplink and downlink QoS flows and the data bearer with the NAS reflective QoS setting 1 bit indicator (AS reflective QoS) of the SDAP header and the AS reflective QoS 1 bit indicator Update, or reset. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used as data processing priority, scheduling information, and the like for supporting a service as desired.

The main functions of the NR PDCP (2d-05, 2d-40) may include some of the following functions.

- Header compression and decompression (ROHC only)

- Transfer of user data

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- Order reordering function (PDCP PDU reordering for reception)

- Duplicate detection of lower layer SDUs

- Retransmission of PDCP SDUs

- Ciphering and deciphering function

- Timer-based SDU discard in uplink.

Here, the reordering function of the NR PDCP apparatus refers to the function of rearranging the PDCP PDUs received in the lower layer on the basis of the PDCP SN (sequence number) in order and transmitting the data to the upper layer in the order of rearrangement And may include a function of directly transmitting PDCP PDUs without considering the order, and may include a function of recording lost PDCP PDUs by rearranging the order, and may include a status report for lost PDCP PDUs To the transmitting side, and may include a function of requesting retransmission of lost PDCP PDUs.

The main functions of the NR RLCs (2d-10, 2d-35) may include some of the following functions.

- Transfer of upper layer PDUs

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- ARQ function (Error Correction through ARQ)

- Concatenation, segmentation and reassembly of RLC SDUs.

- Re-segmentation of RLC data PDUs

- Reordering of RLC data PDUs

- Duplicate detection function

- Protocol error detection

- RLC SDU discard function (RLC SDU discard)

- RLC re-establishment function (RLC re-establishment)

Herein, the in-sequence delivery function of the NR RLC apparatus refers to a function of delivering RLC SDUs received from a lower layer to an upper layer in order, and originally one RLC SDU is divided into a plurality of RLC SDUs And reassembling and delivering the received RLC PDUs when the RLC PDUs are received. The RLC PDUs may include a function of rearranging received RLC PDUs based on a RLC SN (sequence number) or a PDCP SN (sequence number) May include the capability to record lost RLC PDUs and may include the ability to send a status report for lost RLC PDUs to the sender and may include the ability to request retransmission of lost RLC PDUs And may include a function of transferring only the RLC SDUs up to the lost RLC SDU to the upper layer in order of the lost RLC SDU if there is a lost RLC SDU, If all the RLC SDUs received up to the present time have been expired, the RLC SDUs may be transmitted to the upper layer in order, To the upper layer in order. In addition, the RLC PDUs may be processed in the order of receiving (regardless of the order of the sequence number and the sequence number) in order of reception, and may be transmitted to the PDCP device in an out-of-sequence delivery manner. The RLC PDU can receive the segments stored in the RLC PDU or receive the segments to be received at a later time, reconfigure the RLC PDUs into a complete RLC PDU, The NR RLC layer may not include a concatenation function and may perform the function in the NR MAC layer or in place of the NR MAC layer multiplexing function.

The out-of-sequence delivery function of the NR RLC apparatus is a function of delivering the RLC SDUs received from the lower layer directly to the upper layer irrespective of the order. In the original RLC SDU, , And may include a function of reassembling and delivering the RLC PDUs when received, and storing the RLC SN or PDCP SN of the received RLC PDUs and ordering the lost RLC PDUs .

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

- Mapping between logical channels and transport channels.

- Multiplexing / demultiplexing of MAC SDUs

- Scheduling information reporting function

- HARQ (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification (MBMS service identification)

- Transport format selection function (Transport format selection)

- Padding function

The NR PHY layers 2d-20 and 2d-25 channel-code and modulate the upper layer data, transmit them to the wireless channel by making them into OFDM symbols, or demodulate and decode the OFDM symbols received through the wireless channel, Can be performed.

In the next generation mobile communication system, integrity protection and verification can be performed even in a data bearer for transmitting data. In the PDCP layer that processes data transmitted and received in the data bearer, the integrity protection and verification procedure is also a complex procedure in order to perform encryption and decryption procedures with high complexity. Therefore, efficient integrity protection and verification procedures are needed to reduce data processing complexity.

In this disclosure, a method of reducing data processing complexity for a Signaling Radio Bearer (DRB) or a Data Radio Bearer (DRB) in which integrity protection and integrity verification are set in a wireless communication system is described .

FIG. 2E is a diagram illustrating a procedure for determining whether or not a base station performs uplink data compression when a UE establishes a connection with a network according to an exemplary embodiment. Referring to FIG.

FIG. 2E is a flow chart illustrating a procedure for establishing a connection with a network by switching from an RRC idle mode or an RRC inactive mode (RRC inactive mode or lightly-connected mode) to an RRC connected mode And a procedure for setting whether to perform uplink data compression (UDC) will be described.

Referring to FIG. 2E, if the UE transmitting / receiving data in the RRC connection mode does not transmit / receive data for a predetermined reason or for a predetermined time, the base station gNB transmits an RRCConnectionRelease message to the UE to switch the UE into the RRC idle mode You can do it (2e-01). If a terminal that is not currently connected (hereinafter, idle mode UE) generates data to be transmitted, it performs RRC connection establishment procedure with the base station. The MS establishes an uplink transmission synchronization with the BS through a random access procedure and transmits an RRCConnectionRequest message to the BS (2e-05). The RRCConnectionRequest message contains an identifier of the UE and a reason for establishing a connection (establishmentCause). The base station transmits an RRCConnectionSetup message to establish the RRC connection (2e-10). The RRCConnectionSetup message may include information indicating whether to use the uplink data compression method (UDC) for each logical channel, a bearer, or for each PDCP device (PDCP-config). More specifically, each logical channel or bearer, or each PDCP device (or SDAP device), can indicate which IP flow or QoS flow to use for the uplink data compression method (UDC) Information about the IP flow or QoS flow to use or not to use the compression method may be set so that the SDAP apparatus can instruct the PDCP apparatus whether to use the uplink data compression method or not, May self-identify each QoS flow and decide whether or not to apply the uplink compression method). In addition, if it is instructed to use the uplink data compression method, an identifier for a predefined library or dictionary to be used in the uplink data compression method, or a buffer size size to be used in the uplink data compression method . In addition, the RRCConnectionSetup message may include instructions to setup or release to perform uplink decompression. In addition, when the uplink data compression method is used, the RLC AM bearer can always be set to an ARQ function, a lossless mode with a retransmission function, and may not be set together with the header compression protocol (ROHC). In addition, the RRCConnectionSetup message can indicate whether to use the SDAP layer device function or the SDAP header in each logical channel (logical channel configuration), per bearer or PDCP-config (PDCP-config) Message can indicate whether to apply ROHC (IP Packet Header Compression) to each logical channel or to each bearer or PDCP-to-PDCP device, and for each uplink and downlink, ROHC Can be set as an indicator, respectively. However, ROHC and UDC can not be set simultaneously for one PDCP layer device or logical channel or bearer, and UDC can be set for up to two bearers. In addition, the RRCConnectionSetup message can indicate whether to apply integrity protection and integrity verification to each logical channel (logicalchannelconfig) or bearer, or to each PDCP device (PDCP-config) The maximum data rate of the PDCP layer device, the bearer, or the logical channel. In addition, when the user data compression (UDC) or header compression (ROHC) or integrity protection is set for each logical channel, a bearer, or each PDCP device, it is possible to set whether or not to use uplink and downlink respectively have. That is, it can be set to be used in the uplink and not to be used in the downlink, conversely, it can be set not to be used in the uplink but to be used in the downlink. The RRC connection setup message includes RRC connection configuration information and the like. The RRC connection is also called a Signaling Radio Bearer (SRB) and is used for transmitting / receiving RRC messages, which are control messages between the UE and the BS. The UE having established the RRC connection transmits the RRCConnetionSetupComplete message to the BS (2e-15). If the base station does not know the terminal capabilities for the terminal that is currently establishing a connection, or if it wants to know the terminal capabilities, it can send a message asking for the capabilities of the terminal. The terminal may then send a message reporting its capabilities. In this message, it is possible to indicate whether the UE can use Uplink Data Compression (UDC), ROHC (Robust Header Compression) or Integrity Protection, . The RRCConnetionSetupComplete message includes a control message called a SERVICE REQUEST requesting the MME to set bearer for a predetermined service. The base station transmits the SERVICE REQUEST message stored in the RRCConnetionSetupComplete message to the MME (2e-20), and the MME determines whether to provide the service requested by the UE. As a result of the determination, if the UE determines to provide the requested service, the MME transmits an INITIAL CONTEXT SETUP REQUEST message to the BS (2e-25). The INITIAL CONTEXT SETUP REQUEST message includes information such as Quality of Service (QoS) information to be applied when DRB (Data Radio Bearer) is set and security related information (e.g., Security Key, Security Algorithm) to be applied to the DRB. The base station exchanges SecurityModeCommand message (2e-30) and SecurityModeComplete message (2e-35) to establish security with the terminal. When the security setting is completed, the base station transmits an RRCConnectionReconfiguration message to the UE (2e-40). The RRCConnectionReconfiguration message may include information indicating whether to use the uplink data compression method (UDC) for each logical channel, logical channel configuration, or bearer or for each PDCP device (PDCP-config). More specifically, each logical channel or bearer, or each PDCP device (or SDAP device), can indicate which IP flow or QoS flow to use for the uplink data compression method (UDC) Information about the IP flow or QoS flow to use or not to use the compression method may be set so that the SDAP device may instruct the PDCP device whether to use the uplink data compression method or not, Check each QoS flow on its own, and decide whether to apply the uplink compression method). In addition, if it is instructed to use the uplink data compression method, an identifier for a predefined library or dictionary to be used in the uplink data compression method, or a buffer size size to be used in the uplink data compression method . In addition, the RRCConnectionReconfiguration message may include instructions to setup or release to perform uplink decompression. In addition, when the uplink data compression method is used, the RLC AM bearer can always be set to an ARQ function, a lossless mode with a retransmission function, and may not be set together with the header compression protocol (ROHC). In addition, the RRCConnectionReconfiguration message can indicate whether to use the SDAP layer device function or the SDAP header in each logical channel configuration (logical channel configuration), on a bearer basis, or on each PDCP device (PDCP-config) , The RRCConnectionReconfiguration message may indicate whether to apply the ROHC (IP Packet Header Compression) to each logical channel, logical channel configuration, bearer or PDCP-config. For uplink and downlink, Whether or not ROHC is applied can be set as an indicator, respectively. However, ROHC and UDC can not be set simultaneously for one PDCP layer device or logical channel or bearer, and UDC can be set for up to two bearers. In addition, the RRCConnectionReconfiguration message can indicate whether to apply integrity protection and integrity verification to each logical channel, logical channel configuration, bearer or PDCP-config. And can be set in consideration of the maximum data rate of the corresponding PDCP layer device, bearer, or logical channel. In addition, when the user data compression (UDC), the header compression (ROHC), or the integrity protection are set for each logical channel, a bearer, or each PDCP device, whether to use the uplink or the downlink is set . That is, it can be set to be used in the uplink and not to be used in the downlink, conversely, it can be set not to be used in the uplink but to be used in the downlink. In addition, the RRCConnectionReconfiguration message includes configuration information of DRB to be processed by the user data, and the UE sets the DRB by applying the information, and transmits the RRCConnectionReconfigurationComplete message to the BS (2e-45). The base station that has completed the DRB setup sends the INITIAL CONTEXT SETUP COMPLETE message to the MME (2e-50). The MME receives the S1 BEARER SETUP message and the S1 BEARER SETUP RESPONSE message to set up the S- (2e-055, 2e-60). The S1 bearer is a data transmission connection established between the S-GW and the base station, and corresponds to the DRB on a one-to-one basis. When all of these processes are completed, the terminal transmits and receives data through the S-GW with the base stations (2e-65 and 2e-70). The general data transmission process consists of three stages: RRC connection setup, security setup, and DRB setup. Further, the base station may transmit the RRCConnectionReconfiguration message (2e-75) in order to renew, add, or change the setting to the UE for a predetermined reason. The RRCConnectionReconfiguration message may include information indicating whether to use the uplink data compression method (UDC) for each logical channel, logical channel configuration, or bearer or for each PDCP device (PDCP-config). More specifically, each logical channel or bearer, or each PDCP device (or SDAP device), can indicate which IP flow or QoS flow to use for the uplink data compression method (UDC) Information about the IP flow or QoS flow to use or not to use the compression method may be set so that the SDAP device may instruct the PDCP device whether to use the uplink data compression method or not, Check each QoS flow on its own, and decide whether to apply the uplink compression method). In addition, if it is instructed to use the uplink data compression method, an identifier for a predefined library or dictionary to be used in the uplink data compression method, or a buffer size size to be used in the uplink data compression method . The RRCConnectionReconfiguration message may also include instructions to setup or release to perform uplink decompression. In addition, when the uplink data compression method is used, the RLC AM bearer can always be set to an ARQ function, a lossless mode with a retransmission function, and may not be set together with the header compression protocol (ROHC). In addition, the RRCConnectionReconfiguration message can indicate whether to use the SDAP layer device function or the SDAP header in each logical channel configuration (logical channel configuration), on a bearer basis, or on each PDCP device (PDCP-config) , The RRCConnectionReconfiguration message may indicate whether to apply the ROHC (IP Packet Header Compression) to each logical channel, logical channel configuration, bearer or PDCP-config. For uplink and downlink, Whether or not ROHC is applied can be set as an indicator, respectively. However, ROHC and UDC can not be configured for a PDCP layer device or a logical channel or bearer at the same time, and UDC can be set for up to two bearers. In addition, the RRCConnectionReconfiguration message can indicate whether to apply integrity protection and integrity verification to each logical channel, logical channel configuration, bearer or PDCP-config. And can be set in consideration of the maximum data rate of the corresponding PDCP layer device, bearer, or logical channel. In addition, when the user data compression (UDC) or header compression (ROHC) or integrity protection is set for each logical channel, a bearer, or each PDCP device, it is possible to set whether or not to use uplink and downlink respectively have. That is, it can be set to be used in the uplink and not to be used in the downlink, conversely, it can be set not to be used in the uplink but to be used in the downlink.

FIG. 2F is a diagram illustrating a procedure and data structure for performing uplink data compression according to an exemplary embodiment.

In FIG. 2F, the uplink data 2f-05 may be generated as data corresponding to services such as video transmission, picture transmission, web search, and VoLTE. The data generated in the application layer apparatus is processed through TCP / IP or UDP corresponding to the network data transmission layer, and can be transmitted to the PDCP layer constituting each header 2f-10 and 2f-15 . When the PDCP layer receives data (PDCP SDU) from the upper layer, it can perform the following procedure.

If the uplink data compression method is set to be used in the PDCP layer by an RRC message such as 2e-10, 2e-40 or 2e-75 in FIG. 2e, uplink data compression (Header for compressed uplink data, 2f-25) corresponding to the UDC header, and if integrity protection is set, performs integrity protection (integrity protection) And ciphering, and configures the PDCP PDU by configuring the PDCP header 2f-30. The PDCP layer apparatus includes a UDC compression / decompression apparatus. The PDCP layer apparatus determines whether or not to perform the UDC procedure for each data as set in the RRC message, and uses a UDC compression / decompression apparatus. At the transmitting end, the transmitting PDCP layer apparatus performs data compression using the UDC compression apparatus, and at the receiving end, the receiving PDCP layer apparatus performs data decompression using the UDC decompression apparatus.

The above-described FIG. 2F procedure can be applied not only to downlink data compression but also to downlink data compression. The description of the uplink data may be similarly applied to the downlink data.

FIG. 2G is a diagram illustrating uplink data compression according to an embodiment.

FIG. 2G is a diagram illustrating a DEFLATE-based uplink data compression algorithm, and a DEFLATE based uplink data compression algorithm is a lossless compression algorithm. The DEFLATE-based uplink data compression algorithm basically compresses the uplink data by combining the LZ77 algorithm and Huffman coding. The LZ77 algorithm performs an operation of finding a redundant array of data, and when a duplicate array is searched, a duplicate array is found in a sliding window through a sliding window. If there is a duplicate array, The data compression is performed by expressing the degree of overlap with the position in terms of length. The sliding window is also referred to as a buffer in the uplink data compression method (UDC), and may be set to 8 kilobytes or 32 kilobytes. That is, a sliding window or a buffer can be recorded by recording for 8192 or 32768 characters and searching for redundant arrays and expressing them in position and length. Therefore, since the LZ algorithm is a sliding window method, that is, the previously coded data is updated in the buffer, and the next data is immediately coded, so that the data is correlated with each other. Therefore, the first data can be normally decoded before the coded data is normally decoded. Here, compressed codes (position, length, etc.) expressed in position and length by the LZ77 algorithm are further compressed through Huffman coding. Hoffmann coding again finds redundant codes, uses short notation for redundant codes, and compresses again using long notations for less redundant codes. Hoffman coding is a prefix code, and all codes are optimal coding schemes having a distinctly decodable characteristic.

The transmitter performs encoding (2g-10), updates the buffer (2g-15) by applying the LZ77 algorithm to the original data (2g-05) as described above, checksum bits may be generated and configured in the UDC header. The checksum bits are used at the receiving end to determine the validity of the buffer status. The codes encoded by the LZ77 algorithm can be further compressed by Hoffman coding and transmitted as uplink data (2g-25). The receiver performs decompression of the received compressed data in the reverse order of the transmitter. That is, Hoffman decoding is performed (2g-30), the buffer is updated (2g-35), and the validity of the updated buffer is confirmed with the checksum bits of the UDC header. If it is determined that the checksum bits are not erroneous, the LZ77 algorithm can perform decoding (2g-40), decompress the data, and restore the original data to the upper layer (2g-45).

As described above, since the LZ algorithm is a sliding window method, that is, the previously coded data is updated in the buffer and the next data is immediately coded, so that the data is correlated with each other. Therefore, the first data can be normally decoded before the coded data is normally decoded. Accordingly, the receiving PDCP layer apparatus confirms the PDCP sequence number of the PDCP header, confirms the UDC header (confirms whether the data compression is performed or not), and transmits the PDCP serial number in ascending order of the PDCP serial number And then performs a data decompression procedure in that order.

FIG. 2H is a diagram illustrating a procedure and data structure for performing ROHC (Robust Header Compression) header compression according to an embodiment.

2H, the uplink data 2h-05 may be generated as data corresponding to services such as video transmission, picture transmission, web search, and VoLTE. The data generated in the application layer apparatus is processed through TCP / IP or UDP corresponding to the network data transmission layer, and can be transmitted to the PDCP layer constituting each header 2h-10 and 2h-15 . When the PDCP layer receives data (PDCP SDU) from the upper layer, it can perform the following procedure.

If ROHC is set to be used in the PDCP layer by an RRC message such as 2e-10 or 2e-40 or 2e-75 in FIG. 2e, a header compression (ROHC) method is applied to the PDCP SDU like 2h-20 And compresses the header 2h-15 of the received upper layer data to generate a compressed header 2h-25. If integrity verification is set, integrity protection is performed and ciphering is performed , And construct a PDCP PDU by constructing a PDCP header (2h-30). The PDCP layer device includes a header compression / decompression device. The PDCP layer device determines whether to perform header compression or not, and uses a header compression / decompression device for each data as set in the RRC message. At the transmitting end, the transmitting PDCP layer apparatus performs data compression using a header compression apparatus, and at the receiving end, the receiving PDCP layer apparatus performs header decompression using a header decompression apparatus.

The above-described FIG. 2H procedure can be applied not only to the downlink header compression but also to the header compression of the downlink data. The description of the uplink data may be similarly applied to the downlink data.

FIG. 2I is a diagram illustrating a procedure for generating an SDAP header for data received from an upper layer according to an embodiment, applying integrity protection to an SDAP header in a PDCP layer device, and not performing encryption.

In FIG. 2i, the SDAP layer device is configured to use the SDAP layer device function by an RRC message such as 2e-10 or 2e-40 or 2e-75 in FIG. 2e, or to use an SDP header, protection and Integrity verification. When data is received from an upper layer, the SDP header can be generated and configured as in 2i-05 and transmitted to the PDCP layer device. If the integrity protection is set, the PDCP layer device performs integrity protection (integrity authentication) on the PDCP SDU (SDAP header and IP packet, 2i-05) received from the upper SDAP layer device and transmits the message authentication code for integrity Can be calculated. When calculating the MAC-I, the input value may be a PDCP COUNT value, an uplink or downlink indicator, a bearer identifier, a security key, data itself (a part where integrity protection is performed), and the like. The calculated MAC-I can be joined to the rear part of the data like 2i-25. The MAC-I may have a predetermined size, for example, a size of 4 bytes. (2i-20) PDCP headers are generated, configured, and transmitted (2i-35) to the lower layer for the 2i-25 to which the MAC- (2i-40, 2i-45) in the MAC layer device.

At the receiving end, the MAC header and the RLC header are removed and data is transmitted to the PDCP layer. The receiving PDCP layer apparatus reads the PDCP header, removes it, and decodes the data part except for the SDAP header. Then, integrity verification is performed on the SDAP header and the upper layer header (for example, the TCP / IP header) and the data portion, and the computed MAC-I (X-MAC) is calculated. When calculating the X-MAC, the input value may be the PDCP COUNT value, the uplink or downlink indicator, the bearer identifier, the security key, and the data itself (the part where integrity verification is performed), to the integrity verification algorithm. If the MAC-I value matches the computed X-MAC and the MAC-I value attached to the back of the received data, then the integrity verification is successfully performed if it matches, and if the X-MAC and MAC- Otherwise, integrity verification has failed, so the data should be discarded and reported to the upper layer (eg the RRC layer) that the integrity verification failed.

FIG. 2J is a diagram for explaining a procedure of generating an SDAP header for data received from an upper layer according to an exemplary embodiment, and not performing integrity protection on the SDAP header in the PDCP layer device, and not performing encryption.

In FIG. 2J, the SDAP layer device is configured to use the SDAP layer device function by an RRC message such as 2e-10 or 2e-40 or 2e-75 in FIG. 2e, or to use an SDP header, protection and Integrity verification, when receiving data from an upper layer, it can generate and configure an SDAP header like 2j-05 and transmit it to the PDCP layer device. If the integrity protection is set, the PDCP layer device performs integrity protection only on the data (IP packet) excluding the SDAP header for the PDCP SDU (SDAP header and IP packet, 2j-05) received from the upper SDAP layer device The MAC-I (Message Authentication Code for Integrity) can be calculated. When calculating the MAC-I, the input value may be a PDCP COUNT value, an uplink or downlink indicator, a bearer identifier, a security key, data itself (a part where integrity protection is performed), and the like. The calculated MAC-I can be joined to the back of the data as 2j-20. The MAC-I may have a predetermined size, for example, a size of 4 bytes. (2j-25) PDCP headers are generated, constructed, and then transmitted to the lower layer (2j-35), and the data is transmitted to the RLC layer (2j-40, 2j-45) in the MAC layer device. Here, MAC-I may also be encrypted.

At the receiving end, the MAC header and the RLC header are removed and data is transmitted to the PDCP layer. In the receiving PDCP layer apparatus, the PDCP header and the SDAP header are read and removed, and deciphering is performed to the data part excluding the SDAP header. Here, MAC-I is also decoded. Integrity verification is performed on the upper layer header (eg, TCP / IP header) and the data portion excluding the SDAP header, and the computed MAC-I (X-MAC) is calculated. When calculating the X-MAC, the input value may be the PDCP COUNT value, the uplink or downlink indicator, the bearer identifier, the security key, and the data itself (the part where integrity verification is performed), to the integrity verification algorithm. If the MAC-I value matches the computed X-MAC and the MAC-I value attached to the back of the received data, then the integrity verification is successfully performed if it matches, and if the X-MAC and MAC- Otherwise, integrity verification has failed, so the data should be discarded and reported to the upper layer (eg the RRC layer) that the integrity verification failed.

If the SDAP header is not encrypted or the integrity protection is not performed, the structure of the base station implementation can be facilitated. In particular, if the SDU header is not encrypted in the CU in the CU (Distributed Unit) split structure Since the SD can read the SDAP header and check the QoS information and apply it to the scheduling, it may be advantageous to adjust and adjust the QoS. In addition, there is an advantage in terms of data processing in terminal and base station implementation.

FIG. 2K is a diagram illustrating a gain in a structure of a base station implementation when a non-encrypted or an integrity-protected SDAP header according to an exemplary embodiment is applied.

As shown in FIG. 2K, in order to reduce the initial facility cost and the maintenance cost in the base station implementation, the upper layer devices (for example, the PDCP layer device and its upper layer devices) are implemented in the CU The lower layer devices (for example, the RLC layer device and its lower layer devices) may be implemented in the DU (Distributed Unit). If a SDAP header that is not encrypted or has not been subjected to integrity protection is applied in the PDCP layer apparatus 2k-05 as described in FIG. 2J of the present disclosure in the CU-DU split structure, a plurality of DUs (2k-15) Since the header is not encrypted or the integrity protection is not performed, the SDAP header (2k-10) can be read and the QoS information can be checked and applied to the scheduling of the DU. Therefore, DU can utilize the QoS information of the SDAP header in allocating and scheduling transmission resources, which may be advantageous for adjusting and adjusting QoS for each service.

FIG. 21 is a diagram illustrating a processing gain obtainable in a base station and a terminal implementation when an SDAP header that is not encrypted and has not been subjected to integrity protection according to an exemplary embodiment is applied.

In FIG. 21, when the terminal and the base station are implemented, the SDAP layer device and the PDCP layer device can be integrated into one layer device (2l-01). Since the SDAP layer device is logically an upper layer device of the PDCP layer device, when the SDAP layer device receives data (2l-05) from the upper application layer, the SDAP layer device performs RRC If the SDAP layer device function is enabled by the message, or if the SDAP header is set to be used and the integrity protection is set, the SDAP header should be generated and configured as shown in 2j-05 of FIG. . However, the ciphering procedure or the integrity protection procedure in the terminal and the base station implementation can be implemented by applying the HW (hardware) accelerator because it is a high-complexity operation. These HW accelerators have high processing gains in repetitive and continuous procedures. However, when the SDAP layer device receives data from the upper layer device, the SDAP header is configured. If the integrity protection is set, the integrity protection process and the encryption process are performed on the data part excluding the SDAP header, Performing the processing attached to the header may interfere with the HW accelerator due to the procedure for generating the SDAP header before performing the integrity protection and encryption in the above procedure.

Therefore, in the present disclosure, a method of integrating an SDAP layer device and a PDCP layer device together with an unencrypted SDAP header without applying integrity protection and implementing it as a single layer device will be described. That is, when data is received from the upper application layer, the integrity protection procedure (2l-10) is continuously and repeatedly performed every time data is received, the MAC-I is calculated, The PDCP header and the SDAP header (2l-25) are generated at the same time by performing the encryption procedure (2l-20) for the data and the MAC-I with the integrity protection applied thereto and the integrity protection is applied. . The generation of the PDCP header and the SDAP header may be performed in parallel with an integrity protection procedure or an encryption procedure. Here, when generating a header in parallel, an SDAP header, a PDCP header, an RLC header, or a MAC header are generated together, and headers are connected at the head of the data processed data at a time to prepare for transmission You can prepare. In addition, the receiving end separates the SDAP header, the PDCP header, the RLC header or the MAC header from the data all at once, grasps the information corresponding to each layer, and processes the data in a reverse order of the data processing of the transmitting end have. Therefore, the HW accelerator can be applied continuously and repeatedly, and the data processing efficiency can be improved because there is no interruption such as generation of the SDAP header in the middle. In addition, if integrity protection is set, integrity protection can be repeatedly performed by applying a hardware accelerator as described in the encryption procedure before performing the encryption procedure. That is, integrity protection can be applied and encryption can be performed.

The receiving PDCP layer apparatus may also be implemented as a single layer apparatus by integrating the SDAP layer apparatus and the PDCP layer apparatus as in the case of 2l-01. That is, when data is received from a lower layer (RLC layer), the SDAP layer device function is set to be used by an RRC message such as 2e-10, 2e-40, or 2e-75 in FIG. , The PDCP header and the SDAP header can be read and removed at once, and the data can be decrypted or decrypted repeatedly. In addition, if integrity protection is set, integrity verification can be repeatedly performed by applying a hardware accelerator as described in the decryption procedure after performing the decryption procedure. That is, it can perform decryption and perform integrity verification.

FIG. 2M is a flowchart illustrating a method of generating an SDAP header for data received from an upper layer according to an exemplary embodiment of the present invention, performing integrity protection on an SDAP header in a PDCP layer device, Fig.

In FIG. 2M, the SDAP layer device is configured to use the SDAP layer device function by an RRC message such as 2e-10 or 2e-40 or 2e-75 in FIG. 2e, or to use the SDP header, protection and Integrity verification. When data is received from an upper layer, the SDP header can be generated and configured as 2m-05 and transmitted to the PDCP layer device. If the integrity protection is set, the PDCP layer device performs integrity protection only on the data (IP packet) excluding the SDAP header for the PDCP SDU (SDAP header and IP packet, 2m-05) received from the upper SDAP layer device The MAC-I (Message Authentication Code for Integrity) can be calculated. When calculating the MAC-I, the input value may be a PDCP COUNT value, an uplink or downlink indicator, a bearer identifier, a security key, data itself (a part where integrity protection is performed), and the like. The calculated MAC-I can be joined to the back of the data, such as 2m-20. The MAC-I may have a predetermined size, for example, a size of 4 bytes. (2m-30, 2m-35) PDCP headers are generated, constructed, and joined (2m-40) by performing encryption on the part excluding the SDAP header and the MAC-I for 2m- To the lower layer, and the data processing can be performed in the RLC layer device and the MAC layer device. Here, the MAC-I is not encrypted. If MAC-I is not encrypted, the processing gain of the data processing can be further improved as described below.

The receiving end removes the MAC header and the RLC header and transfers data to the PDCP layer. The receiving PDCP layer apparatus reads and removes the PDCP header and the SDAP header, decodes the data part except for the SDAP header and the rear part MAC-I, . Here, MAC-I is not decoded. Integrity verification is performed on the upper layer header (eg, TCP / IP header) and the data portion excluding the SDAP header, and the computed MAC-I (X-MAC) is calculated. When calculating the X-MAC, the input value may be the PDCP COUNT value, the uplink or downlink indicator, the bearer identifier, the security key, and the data itself (the part where integrity verification is performed), to the integrity verification algorithm. If the MAC-I value matches the computed X-MAC and the MAC-I value attached to the back of the received data, then the integrity verification is successfully performed if it matches, and if the X-MAC and MAC- Otherwise, integrity verification has failed, so the data should be discarded and reported to the upper layer (eg the RRC layer) that the integrity verification failed.

If the SDAP header is not encrypted or the integrity protection is not performed, the structure of the base station implementation can be facilitated. In particular, if the SDU header is not encrypted in the CU (Distributed Unit) split structure in the CU (Central Unit) The SDAP header can be read and the QoS information can be confirmed and applied to the scheduling, which is advantageous for adjusting and adjusting the QoS. Also, there is an advantage in terms of data processing in terminal and base station implementation. In addition, if the MAC-I is not encrypted, the processing gain of data processing can be further improved as described below.

FIG. 2n is a diagram illustrating a processing gain obtainable in a base station and a terminal when a non-encrypted SDAP header is not encrypted and an MAC-I is not encrypted according to an exemplary embodiment.

When implementing a terminal and a base station in FIG. 2n, the SDAP layer device and the PDCP layer device may be integrated into a single layer device (2n-01). Since the SDAP layer device is logically an upper layer device of the PDCP layer device, when the SDAP layer device receives data (2n-05) from the upper application layer, the SDAP layer device performs RRC If the SDAP layer device function is enabled by the message, or if the SDAP header is set to be used and the integrity protection is set, the SDAP header should be generated and configured as shown in 2j-05 of FIG. . However, the ciphering procedure or the integrity protection procedure in the terminal and the base station implementation can be implemented by applying the HW (hardware) accelerator because it is a high-complexity operation. These HW accelerators have high processing gains in repetitive and continuous procedures. However, in the SDAP layer device, the SDAP header is configured every time data is received from the upper layer device. If the integrity protection is set, the integrity protection procedure and the encryption procedure are performed on the data part excluding the SDAP header, the PDCP header is generated, Processing may cause interruption to the HW accelerator due to the procedure for generating the SDAP header before integrity protection and encryption are performed.

Therefore, in the present disclosure, a method of integrating an SDAP header and an unencrypted MAC-I together into an SDAP layer device and a PDCP layer device in a single layer device without applying integrity protection will be described. In other words, when data is received from the upper layer, the integrity protection procedure (2n-10) is continuously and repeatedly performed every time data is received, the MAC-I is calculated (2n-20, 2n-25) (2n-20), and generates PDCP header, SDAP header, and MAC-I at the same time, applies integrity protection, and transmits the encrypted data to the lower layer (2n-25 ). That is, the generated headers can be joined at the beginning of the data, and MAC-I can be joined at the rear. The generation of the PDCP header, the SDAP header and the MAC-I may be performed in parallel with the integrity protection procedure or the encryption procedure. When a header is generated in parallel, an SDAP header, a PDCP header, an RLC header or a MAC header are generated together, and the data is processed at the head of the completed data, . In the case of MAC-I, data can be concatenated at the end of the processed data. In addition, the receiving end separates the SDAP header, the PDCP header, the RLC header or the MAC header from the data all at once, grasps the information corresponding to each layer, and processes the data in a reverse order of the data processing of the transmitting end have. Therefore, the HW accelerator can be applied continuously and repeatedly, and the data processing efficiency can be improved because there is no interruption such as generation of the SDAP header in the middle. In addition, if integrity protection is set, integrity protection can be repeatedly performed by applying a hardware accelerator as described in the encryption procedure before performing the encryption procedure. That is, integrity protection can be applied and encryption can be performed.

The receiving PDCP layer apparatus may also be implemented as a single layer apparatus by integrating the SDAP layer apparatus and the PDCP layer apparatus as in the case of 2l-01. That is, when data is received from a lower layer (RLC layer), the SDAP layer device function is set to be used by the RRC message such as 2e-10, 2e-40, or 2e-75 in FIG. 2E or the SDAP header is set to be used , The PDCP header and the SDAP header can be read and removed at once, and the data can be decrypted or decrypted repeatedly. In addition, if integrity protection is set, integrity verification can be repeatedly performed by applying a hardware accelerator as described in the decoding procedure after performing the decryption procedure. That is, it can perform decryption and perform integrity verification. That is, the header of the received data can be read and removed, the MAC-I after the data can be read and removed, the data portion can be decrypted, and the integrity verification procedure can be performed.

FIG. 20 illustrates a procedure for generating an SDAP header for data received from an upper layer according to an embodiment, performing header compression (ROHC) in the PDCP layer device, applying integrity protection to the SDAP header, and not performing encryption to be.

In FIG. 20, the SDAP layer device is configured to use the SDAP layer device function by an RRC message such as 2e-10 or 2e-40 or 2e-75 in FIG. 2e, or to use an SDP header, (ROHC) is used for the uplink or the downlink, if data is received from the upper layer, the SDAP header (eg, 2o-05) And transmit it to the PDCP layer device. The PDCP layer apparatus performs header compression (ROHC) (2o-10) on the upper layer header part (for example, the IP packet header) of the received PDCP SDU. If the integrity protection is set, the PDCP layer device performs integrity protection on the PDCP SDU (SDAP header and IP packet, 2o-15) to which the header compression (ROHC) is applied and performs integrity protection (integrity protection) (Message Authentication Code for Integrity) (2o-25). When calculating the MAC-I, the input value may be a PDCP COUNT value, an uplink or downlink indicator, a bearer identifier, a security key, data itself (a part where integrity protection is performed), and the like. The calculated MAC-I can be joined to the back of the data, such as 2o-30. The MAC-I may have a predetermined size, for example, a size of 4 bytes. (2o-35) PDCP headers are generated, configured and joined (2o-45) to the lower layer, and the data is transmitted to the RLC layer Device and the MAC layer device.

At the receiving end, the MAC header and the RLC header are removed and data is transmitted to the PDCP layer. The receiving PDCP layer apparatus reads the PDCP header, removes it, and decodes the data part except for the SDAP header. Then, integrity verification is performed on the SDAP header and the upper layer header (for example, the TCP / IP header) and the data portion, and the computed MAC-I (X-MAC) is calculated. When calculating the X-MAC, the input value may be the PDCP COUNT value, the uplink or downlink indicator, the bearer identifier, the security key, and the data itself (the part where integrity verification is performed), to the integrity verification algorithm. If the MAC-I value matches the computed X-MAC and the MAC-I value attached to the back of the received data, integrity verification is successfully performed. If the MAC-I value matches Otherwise, the integrity verification has failed, so you should discard the data and report that the integrity verification failed at the higher layer (eg the RRC layer). When the integrity verification is completed, a header compression (ROHC) cancellation procedure is performed on an upper layer header (for example, an IP packet header), and the restored upper layer data can be transferred to an upper layer.

FIG. 2P illustrates a procedure for generating an SDAP header for data received from an upper layer according to an exemplary embodiment, performing header compression (ROHC) in the PDCP layer device, performing integrity protection on the SDAP header, and not performing encryption Fig.

In FIG. 2P, the SDAP layer device is configured to use the SDAP layer device function by an RRC message such as 2e-10 or 2e-40 or 2e-75 in FIG. 2e, or to use an SDP header, (ROHC) is set to use uplink or downlink, if data is received from an upper layer, SDP header (2p-05) And transmit it to the PDCP layer device. The PDCP layer device performs header compression (ROHC) on the upper layer header part (for example, IP packet header) of the received PDCP SDU (2p-10). If the integrity protection is set, the PDCP layer device performs integrity protection only on the data (IP packet) to which the header compression (ROHC) is applied except for the SDAP header for the PDCP SDU (SDAP header and IP packet, 2p-05) received from the upper SDAP layer device (Integrity protection) and computes Message Authentication Code for Integrity (MAC-I) (2p-30). When calculating the MAC-I, the input value may be a PDCP COUNT value, an uplink or downlink indicator, a bearer identifier, a security key, data itself (a part where integrity protection is performed), and the like. The calculated MAC-I can be joined to the rear part of the data as shown in 2p-35. The MAC-I may have a predetermined size, for example, a size of 4 bytes. (2p-40), generates PDCP header, constructs (2p-50) the PDCP header, and transmits the PDCP header to the lower layer (2p-50) Device and the MAC layer device. Here, MAC-I may also be encrypted.

The header compression (ROHC) can be applied only to the upper layer header (for example, the IP packet header) of the SDAP layer apparatus except for the SDAP header for the PDCP SDU received from the upper layer in the PDCP layer apparatus as described above. The PDCP SDU may include an SDAP header, an upper layer header (e.g., IP packet header) of the SDAP layer device, and upper layer data (IP packet data) of the SDAP layer device. By not applying header compression (ROHC) to the SDAP header, the degree of freedom of implementation of the base station can be increased and the processing complexity of the terminal can be reduced.

At the receiving end, the MAC header and the RLC header are removed and data is transmitted to the PDCP layer. In the receiving PDCP layer apparatus, the PDCP header and the SDAP header are read and removed, and deciphering is performed to the data part excluding the SDAP header. Here, MAC-I is also decoded. Integrity verification is performed on the upper layer header (eg, TCP / IP header) and the data portion excluding the SDAP header, and the computed MAC-I (X-MAC) is calculated. When calculating the X-MAC, the input value may be the PDCP COUNT value, the uplink or downlink indicator, the bearer identifier, the security key, and the data itself (the part where integrity verification is performed), to the integrity verification algorithm. If the MAC-I value matches the computed X-MAC and the MAC-I value attached to the back of the received data, integrity verification is successfully performed. If the MAC-I value matches Otherwise, the integrity verification has failed, so you should discard the data and report that the integrity verification failed at the higher layer (eg the RRC layer). When the integrity verification is completed, a header compression (ROHC) cancellation procedure is performed on an upper layer header (for example, an IP packet header), and the restored upper layer data can be transferred to an upper layer.

If the SDAP header is not encrypted or the integrity protection is not performed, the structure of the base station implementation can be facilitated. In particular, if the SDU header is not encrypted in the CU (Distributed Unit) split structure in the CU (Central Unit) The SDAP header can be read and the QoS information can be confirmed and applied to the scheduling, which is advantageous for adjusting and adjusting the QoS. In addition, there is an advantage in terms of data processing in terminal and base station implementation.

In addition, if the SDAP header is not subjected to header compression (ROHC) as described above, the structure of the base station implementation can be facilitated. In particular, if the SDU header is not header-compressed in the CU in the split structure of a Central Unit (DUU) Since the SD can read the SDAP header and check the QoS information and apply it to the scheduling, it may be advantageous to adjust and adjust the QoS. In addition, there is an advantage in terms of data processing in terminal and base station implementation.

FIG. 2Q is a diagram illustrating a processing gain that can be obtained in a base station and a terminal implementation when an SDAP header that is not encrypted and has not been subjected to integrity protection according to an exemplary embodiment is applied.

In FIG. 2q, when implementing a terminal and a base station, the SDAP layer device and the PDCP layer device may be integrated into one layer device (2q-01). Since the SDAP layer device is logically an upper layer device of the PDCP layer device, when the SDAP layer device receives data (2q-05) from the upper application layer, the SDAP layer device performs RRC such as 2e-10 or 2e-40 or 2e- When the SDAP layer device function is set to use the SDAP layer function or the SDAP header is set to use the message and the integrity protection is set and the header compression (ROHC) is set to be used for the uplink or the downlink, Upon receiving the data, the SDAP header should be generated and configured as shown in 2j-05 of FIG. 2J. However, the ciphering procedure or the integrity protection procedure in the terminal and the base station implementation can be implemented by applying the HW (hardware) accelerator because it is a high-complexity operation. These HW accelerators have high processing gains in repetitive and continuous procedures. However, in the SDAP layer device, the SDAP header is configured every time data is received from the upper layer device. If the integrity protection is set, the integrity protection procedure and the encryption procedure are performed on the data part excluding the SDAP header, the PDCP header is generated, Processing may cause interruption to the HW accelerator due to the procedure for generating the SDAP header before integrity protection and encryption are performed.

Therefore, in the present disclosure, a method of integrating an SDAP layer device and a PDCP layer device together with an unencrypted SDAP header without applying integrity protection and implementing it as a single layer device will be described. That is, when data is received from an upper application layer, it performs header compression (ROHC) on an upper layer header part (for example, an IP packet header) of the PDCP SDU continuously and repeatedly received each time data is received. Then, the integrity protection procedure (2q-15) is performed on the PDCP SDU to which the header compression is applied such as 2q-20, the MAC-I is calculated and the data is connected to the rear part of the data (2q-30) (2q-35) for the PDCP header and the PDCP header and the SDAP header (2q-40) at the same time, integrity protection is applied, and the PDCP header and the SDAP header (2q-40) The generation of the PDCP header and the SDAP header may be performed in parallel with an integrity protection procedure or an encryption procedure. When a header is generated in parallel, an SDAP header, a PDCP header, an RLC header or a MAC header are generated together, and the data is processed at the head of the completed data, . In addition, the receiving end separates the SDAP header, the PDCP header, the RLC header or the MAC header from the data all at once, grasps the information corresponding to each layer, and processes the data in a reverse order of the data processing of the transmitting end have. Therefore, the HW accelerator can be applied continuously and repeatedly, and the data processing efficiency can be improved because there is no interruption such as generation of the SDAP header in the middle. In addition, if integrity protection is set, integrity protection can be repeatedly performed by applying a hardware accelerator as described in the encryption procedure before performing the encryption procedure. That is, integrity protection can be applied and encryption can be performed.

In the receiving PDCP layer apparatus, a method of integrating the SDAP layer apparatus and the PDCP layer apparatus into one hierarchical unit, such as 2q-01, can be applied. That is, when data is received from a lower layer (RLC layer), the SDAP layer device function is set to be used by an RRC message such as 2e-10, 2e-40, or 2e-75 in FIG. , The PDCP header and the SDAP header can be read and removed at once, and the data can be decrypted or decrypted repeatedly. In addition, if integrity protection is set, integrity verification can be repeatedly performed by applying a hardware accelerator as described in the decryption procedure after performing the decryption procedure. That is, it can perform decryption and perform integrity verification. When the integrity verification is completed, a header compression (ROHC) cancellation procedure is performed on an upper layer header (for example, an IP packet header), and the restored upper layer data can be transferred to an upper layer.

FIG. 2r is a diagram illustrating a method of generating an SDAP header for data received from an upper layer according to an exemplary embodiment, performing header compression (ROHC) on a PDCP layer device, performing integrity protection on an SDAP header, I &lt; / RTI &gt;

In FIG. 2r, the SDAP layer device is configured to use the SDAP layer device function by an RRC message such as 2e-10 or 2e-40 or 2e-75 in FIG. 2e, or to use an SDP header, (ROHC) is used for the uplink or the downlink, when the data is received from the upper layer, the SDP header And transmit it to the PDCP layer device. The PDCP layer apparatus performs header compression (ROHC) on the upper layer header part (for example, IP packet header) of the received PDCP SDU (2r-10). If the integrity protection is set, the PDCP layer device performs integrity protection only on the data (IP packet) to which header compression (ROHC) is applied except for the SDAP header for the PDCP SDU (SDAP header and IP packet, 2r-05) received from the upper SDAP layer device (Integrity protection) and calculate Message Authentication Code for Integrity (MAC-I). When calculating the MAC-I, the input value may be a PDCP COUNT value, an uplink or downlink indicator, a bearer identifier, a security key, data itself (a part where integrity protection is performed), and the like. The calculated MAC-I can be joined to the rear part of the data like 2r-35. The MAC-I may have a predetermined size, for example, a size of 4 bytes. (2r-40, 2r-45) PDCP headers are generated, constructed, and combined (2r-50) by performing encryption on the part excluding the SDAP header and the MAC-I for the 2r- To the lower layer, and the data processing can be performed in the RLC layer device and the MAC layer device. Here, the MAC-I is not encrypted. If MAC-I is not encrypted, the processing gain of the data processing can be further improved as described below.

The header compression (ROHC) can be applied only to the upper layer header (for example, the IP packet header) of the SDAP layer apparatus except for the SDAP header for the PDCP SDU received from the upper layer in the PDCP layer apparatus as described above. The PDCP SDU may include an SDAP header, an upper layer header (e.g., IP packet header) of the SDAP layer device, and upper layer data (IP packet data) of the SDAP layer device. By not applying header compression (ROHC) to the SDAP header, the degree of freedom of implementation of the base station can be increased and the processing complexity of the terminal can be reduced.

The receiving end removes the MAC header and the RLC header and delivers data to the PDCP layer. The receiving PDCP layer apparatus reads and removes the PDCP header and the SDAP header, deciphers the data part excluding the SDAP header and the rear part MAC-I, ). Here, the MAC-I is not decoded. Integrity verification is performed on the upper layer header (eg, TCP / IP header) and the data portion excluding the SDAP header, and the computed MAC-I (X-MAC) is calculated. When calculating the X-MAC, the input value may be the PDCP COUNT value, the uplink or downlink indicator, the bearer identifier, the security key, and the data itself (the part where integrity verification is performed), to the integrity verification algorithm. If the MAC-I value matches the computed X-MAC and the MAC-I value attached to the back of the received data, integrity verification is successfully performed. If the MAC-I value matches Otherwise, the integrity verification has failed, so you should discard the data and report that the integrity verification failed at the higher layer (eg the RRC layer). When the integrity verification is completed, a header compression (ROHC) cancellation procedure is performed on an upper layer header (for example, an IP packet header), and the restored upper layer data can be transferred to an upper layer.

If the SDAP header is not encrypted or the integrity protection is not performed, the structure of the base station implementation can be facilitated. In particular, if the SDU header is not encrypted in the CU (Distributed Unit) split structure in the CU (Central Unit) The SDAP header can be read and the QoS information can be confirmed and applied to the scheduling, which is advantageous for adjusting and adjusting the QoS. In addition, there is an advantage in terms of data processing in terminal and base station implementation. In addition, if MAC-I is not encrypted in the above, the processing gain of the data processing can be further improved as described below.

In addition, if the SDAP header is not subjected to header compression (ROHC) as described above, the structure of the base station implementation can be facilitated. In particular, if the SDU header is not header-compressed in the CU in the split structure of a Central Unit (DUU) Since the SD can read the SDAP header and check the QoS information and apply it to the scheduling, it may be advantageous to adjust and adjust the QoS. In addition, there is an advantage in terms of data processing in terminal and base station implementation.

FIG. 2S illustrates a processing gain that can be obtained in the base station and the terminal implementation when applying an SDAP header that is not encrypted and has not been subjected to integrity protection according to an embodiment, performs header compression (ROHC), and does not encrypt MAC- FIG.

When implementing a terminal and a base station in FIG. 2S, the SDAP layer device and the PDCP layer device may be integrated into one layer device (2s-01). Since the SDAP layer device is logically an upper layer device of the PDCP layer device, when the SDAP layer device receives data (2s-05) from the upper application layer, the SDAP layer device performs RRC such as 2e-10 or 2e-40 or 2e- When the SDAP layer device function is set to use the SDAP layer function or the SDAP header is set to use the message and the integrity protection is set and the header compression (ROHC) is set to be used for the uplink or the downlink, Upon receiving the data, the SDAP header should be generated and configured as shown in 2j-05 of FIG. 2J. However, the ciphering procedure or the integrity protection procedure in the terminal and the base station implementation can be implemented by applying the HW (hardware) accelerator because it is a high-complexity operation. These HW accelerators have high processing gains in repetitive and continuous procedures. However, in the SDAP layer device, the SDAP header is configured every time data is received from the upper layer device. If the integrity protection is set, the integrity protection procedure and the encryption procedure are performed on the data part excluding the SDAP header, the PDCP header is generated, Attach processing may interfere with the HW accelerator due to the procedure for generating SDAP headers before performing integrity protection and encryption.

Therefore, in the present disclosure, a method of integrating an SDAP header and an unencrypted MAC-I together and integrating an SDAP layer device and a PDCP layer device in a single layer device without applying integrity protection will be described. That is, when data is received from an upper application layer, header compression (ROHC) is performed on the upper layer header part (for example, the IP packet header) of the PDCP SDU continuously and repeatedly received -10) perform the integrity protection procedure (2s-15), calculate the MAC-I (2s-25, 2s-30), perform the encryption procedure (2s-35) on the data with the integrity protection applied, SDAP header and MAC-I are generated at the same time, and integrity protection is applied, and it can be transmitted to the lower layer by joining to the encrypted data (2s-45). That is, the generated headers can be attached to the front part of the data, and the MAC-I can be connected to the rear part. The generation of the PDCP header, the SDAP header and the MAC-I may be performed in parallel with the integrity protection procedure or the encryption procedure. When a header is generated in parallel, an SDAP header, a PDCP header, an RLC header or a MAC header are generated together, and the data is processed at the head of the completed data, . In the case of MAC-I, data can be concatenated at the end of the processed data. In addition, the receiving end separates the SDAP header, the PDCP header, the UDC header or the RLC header or the MAC header from the data all at once, grasps the information corresponding to each layer, and processes the data in the reverse order of the data processing of the transmitting end . Therefore, the HW accelerator can be applied continuously and repeatedly, and the data processing efficiency can be improved because there is no interruption such as generation of the SDAP header in the middle. In addition, if integrity protection is set, integrity protection can be repeatedly performed by applying a hardware accelerator as described in the encryption procedure before performing the encryption procedure. That is, integrity protection can be applied and encryption can be performed.

The receiving PDCP layer apparatus may also be implemented as a single layer apparatus by integrating the SDAP layer apparatus and the PDCP layer apparatus as in the case of 2l-01. That is, when data is received from a lower layer (RLC layer), the SDAP layer device function is set to be used by an RRC message such as 2e-10, 2e-40, or 2e-75 in FIG. , The PDCP header and the SDAP header can be read and removed at once, and the data can be decrypted or decrypted repeatedly. In addition, if integrity protection is set, integrity verification can be repeatedly performed by applying a hardware accelerator as described in the decryption procedure after performing the decryption procedure. That is, it can perform decryption and perform integrity verification. That is, it is possible to read and remove the headers of the received data, read and remove the MAC-I after the data, decrypt the data portion, and perform the integrity verification procedure. When the integrity verification is completed, a header compression (ROHC) cancellation procedure is performed on an upper layer header (for example, an IP packet header), and the restored upper layer data can be transferred to an upper layer.

FIG. 2T illustrates a method of generating an SDAP header for data received from an upper layer according to an exemplary embodiment, performing uplink data compression (UDC) on a PDCP layer device, applying integrity protection to a UDC header, And applies integrity protection to the SDAP header and does not perform encryption.

In FIG. 2T, the SDAP layer device is configured to use the SDAP layer device function by an RRC message such as 2e-10 or 2e-40 or 2e-75 in FIG. 2e, or to use an SDP header, (UDC) is used for uplink or downlink, if data is received from an upper layer, then SDAP Header to the PDCP layer device. The PDCP layer apparatus performs user data compression (UDC) (2t-10) on a part (for example, IP packet header) excluding the SDAP header of the received PDCP SDU. It can calculate the checksum field based on the current UDC buffer and construct the UDC header and attach it before the SDAP header like 2t-20. If the integrity protection is set, the PDCP layer device receives integrity protection from the upper SDAP layer device and applies UDC header, UDC header, and UDC block (2t-20) to which UDC header is connected. ) And calculate the Message Authentication Code for Integrity (MAC-I) (2t-35). When calculating the MAC-I, the input value may be a PDCP COUNT value, an uplink or downlink indicator, a bearer identifier, a security key, data itself (a part where integrity protection is performed), and the like. The calculated MAC-I can be joined to the back of the data as in 2t-40. The MAC-I may have a predetermined size, for example, a size of 4 bytes. (2t-45) PDCP headers are generated, configured, and then transmitted to the lower layer (2t-50) for the 2t-40 to which the MAC- Device and the MAC layer device.

At the receiving end, the MAC header and the RLC header are removed and data is transmitted to the PDCP layer. The receiving PDCP layer apparatus reads the PDCP header, removes it, and decodes the data part except for the SDAP header. Then, integrity verification is performed on the SDAP header and the upper layer header (for example, the TCP / IP header) and the data portion, and the computed MAC-I (X-MAC) is calculated. When calculating the X-MAC, the input value may be the PDCP COUNT value, the uplink or downlink indicator, the bearer identifier, the security key, and the data itself (the part where integrity verification is performed), to the integrity verification algorithm. If the MAC-I value matches the computed X-MAC and the MAC-I value attached to the back of the received data, integrity verification is successfully performed. If the MAC-I value matches Otherwise, the integrity verification has failed, so you should discard the data and report that the integrity verification failed at the higher layer (eg the RRC layer). When the integrity verification is completed, the UDC header is read from the upper layer data to check whether the checksum fails or not, the user data decompression (UDC) procedure is performed, and the restored upper layer data can be transferred to the upper layer.

FIG. 2U shows an example of generating an SDAP header for data received from an upper layer according to an exemplary embodiment, performing uplink data compression (UDC) on a PDCP layer device, applying integrity protection to a UDC header, FIG. 4 is a diagram illustrating a procedure for applying integrity protection to an SDAP header without performing encryption.

In FIG. 2U, the SDAP layer device is configured to use the SDAP layer device function by an RRC message such as 2e-10 or 2e-40 or 2e-75 in FIG. 2e, or to use an SDP header, (UDC) is used for uplink or downlink, if data is received from an upper layer, then SDAP (User Datagram Protocol), such as 2u-05, Header to the PDCP layer device. The PDCP layer apparatus performs user data compression (UDC) (2u-10) on a part (for example, IP packet header) excluding the SDAP header of the received PDCP SDU. Then, based on the current UDC buffer, the checksum field can be calculated and the UDC header can be constructed to be attached before the SDAP header like 2u-20. If the integrity protection is set, the PDCP layer device receives integrity protection from the upper SDAP layer device and applies user data compression (UDC) to the UDC header, the SDAP header, and the UDC block 2u-20 to which the UDC header is connected. ) And calculate the Message Authentication Code for Integrity (MAC-I) (2u-35). When calculating the MAC-I, the input value may be a PDCP COUNT value, an uplink or downlink indicator, a bearer identifier, a security key, data itself (a part where integrity protection is performed), and the like. The calculated MAC-I can be joined to the back of the data like 2u-40. The MAC-I may have a predetermined size, for example, a size of 4 bytes. (2u-45) generates and constructs a PDCP header for the 2u-40 that has joined the MAC-I, encrypts it except for the UDC header and the SDAP header, May be performed by the RLC layer device and the MAC layer device.

At the receiving end, the MAC header and the RLC header are removed and data is transmitted to the PDCP layer. The receiving PDCP layer apparatus reads the PDCP header, removes it, and decodes the data part except for the SDAP header. Then, integrity verification is performed on the SDAP header and the upper layer header (for example, the TCP / IP header) and the data portion, and the computed MAC-I (X-MAC) is calculated. When calculating the X-MAC, the input value may be the PDCP COUNT value, the uplink or downlink indicator, the bearer identifier, the security key, and the data itself (the part where integrity verification is performed), to the integrity verification algorithm. If the MAC-I value matches the computed X-MAC and the MAC-I value attached to the back of the received data, integrity verification is successfully performed. If the MAC-I value matches Otherwise, the integrity verification has failed, so you should discard the data and report that the integrity verification failed at the higher layer (eg the RRC layer). When the integrity verification is completed, the UDC header is read from the upper layer data to check whether the checksum fails or not, the user data decompression (UDC) procedure is performed, and the restored upper layer data can be transferred to the upper layer.

FIG. 2V is a diagram illustrating a method of generating an SDAP header for data received from an upper layer according to an embodiment of the present invention, performing uplink data compression (UDC) on the PDCP layer device, encrypting the UDC header without applying integrity protection And encrypting the MAC-I without performing integrity protection and applying the integrity protection to the SDAP header without performing encryption.

In FIG. 2V, the SDAP layer device is configured to use the SDAP layer device function by an RRC message such as 2e-10 or 2e-40 or 2e-75 in FIG. 2e, or to use an SDP header, (UDC) is used for uplink or downlink, if data is received from an upper layer, then SDAP (2v-05) Header to the PDCP layer device. The PDCP layer apparatus performs user data compression (UDC) (2v-10) on a part excluding the SDAP header of the received PDCP SDU (for example, an IP packet header). The UDC buffer is used to calculate the checksum field based on the current UDC buffer, and the UDC header can be formed to be connected to the SDAP header such as 2v-20. If the integrity protection is set, the PDCP layer apparatus receives UDC header, SDAP header, UDC block (2v-20), UDC header and SDAP header (Integrity protection) and computes Message Authentication Code for Integrity (MAC-I) (2v-35). When calculating the MAC-I, the input value may be a PDCP COUNT value, an uplink or downlink indicator, a bearer identifier, a security key, data itself (a part where integrity protection is performed), and the like. The calculated MAC-I can be joined to the back of the data as in 2v-40. The MAC-I may have a predetermined size, for example, a size of 4 bytes. (2v-45) PDCP headers are generated, configured, and transmitted (2v-50) to the lower layer for data processing May be performed by the RLC layer device and the MAC layer device.

At the receiving end, the MAC header and the RLC header are removed and data is transmitted to the PDCP layer. The receiving PDCP layer apparatus reads the PDCP header, removes it, and decodes the data part except for the SDAP header. Then, integrity verification is performed on the SDAP header and the upper layer header (for example, the TCP / IP header) and the data portion, and the computed MAC-I (X-MAC) is calculated. When calculating the X-MAC, the input value may be the PDCP COUNT value, the uplink or downlink indicator, the bearer identifier, the security key, and the data itself (the part where integrity verification is performed), to the integrity verification algorithm. If the MAC-I value matches the computed X-MAC and the MAC-I value attached to the back of the received data, integrity verification is successfully performed. If the MAC-I value matches Otherwise, the integrity verification has failed, so you should discard the data and report that the integrity verification failed at the higher layer (eg the RRC layer). Upon completion of the integrity verification, the UDC header is read to check whether the checksum has failed, the UDC procedure for the upper layer data can be performed, and the restored upper layer data can be transferred to the upper layer.

FIG. 2w is a diagram illustrating a processing gain that can be obtained in the base station and the terminal when the SDAP header and the UDC header, which are not encrypted and are not subjected to integrity protection, are applied according to an exemplary embodiment.

In FIG. 2w, when implementing a terminal and a base station, the SDAP layer device and the PDCP layer device may be integrated into one layer device (2w-01). Since the SDAP layer device is logically an upper layer device of the PDCP layer device, when the SDAP layer device receives the data (2w-05) from the upper application layer, the SDAP layer device performs RRC such as 2e-10 or 2e-40 or 2e- If the SDAP layer device function is set to use the message or the SDAP header is set to be used and if the integrity protection is set and if user data compression (UDC) is set to be used for the uplink or downlink, It is necessary to generate and configure an SDAP header as shown in 2j-05 in Fig. 2J. However, the ciphering procedure or the integrity protection procedure in the terminal and the base station implementation can be implemented by applying the HW (hardware) accelerator because it is a high-complexity operation. These HW accelerators have high processing gains in repetitive and continuous procedures. However, if the SDAP layer device configures the SDAP header each time data is received from the upper layer device, and if the integrity protection and user data compression (UDC) are set, the user data compression procedure is performed, the UDC header is generated, If the procedure and the encryption procedure are performed on the data part excluding the UDC header and the SDAP header, and the PDCP header is generated and added to the SDAP header, the procedure of generating the UDC header and the SDAP header before performing the integrity protection and the encryption, (Interruption).

Therefore, in the present disclosure, a method of integrating an SDAP layer device and a PDCP layer device together with an unencrypted SDAP header and a UDC header without applying integrity protection is described as a single layer device. That is, when data is received from an upper application layer, user data compression (UDC) is performed on an upper layer header portion (for example, an IP packet header) of a PDCP SDU received continuously and repeatedly each time data is received. Then, integrity protection procedure (2w-25) is performed for the PDCP SDU to which the header compression is applied such as 2w-20, MAC-I is calculated and the data is connected to the rear part (2w-30) (2w-45) is performed on the PDCP header, the PDCP header, the UDC header and the SDAP header (2w-50) are simultaneously generated, integrity protection is applied, and the encrypted data is transmitted to the lower layer. The generation of the PDCP header, the UDC header and the SDAP header may be performed in parallel with the integrity protection procedure or the encryption procedure. When a header is generated in parallel, an SDAP header, a PDCP header, a UDC header or an RLC header or a MAC header are generated together and the transmission is prepared by connecting headers at the head of the data processed data at once Can be prepared. In addition, the receiving end separates the SDAP header, the PDCP header, the UDC header or the RLC header or the MAC header from the data all at once, grasps the information corresponding to each layer, and processes the data in the reverse order of the data processing of the transmitting end . Therefore, the HW accelerator can be applied continuously and repeatedly, and the data processing efficiency can be improved because there is no interruption such as generation of UDC header and SDAP header in the middle. In addition, if integrity protection is set, integrity protection can be repeatedly performed by applying a hardware accelerator as described in the encryption procedure before performing the encryption procedure. That is, integrity protection can be applied and encryption can be performed.

The receiving PDCP layer device may also be implemented by integrating the SDAP layer device and the PDCP layer device into a single layer device such as 2w-01. That is, when data is received from a lower layer (RLC layer), the SDAP layer device function is set to be used by an RRC message such as 2e-10, 2e-40, or 2e-75 in FIG. , The PDCP header and the SDAP header can be read and removed at once, and the data can be decrypted or decrypted repeatedly. In addition, if integrity protection is set, integrity verification can be repeatedly performed by applying a hardware accelerator as described in the decryption procedure after performing the decryption procedure. That is, it can perform decryption and perform integrity verification. Upon completion of the integrity verification, the UDC header is read to check whether the checksum has failed, the UDC procedure for the upper layer data can be performed, and the restored upper layer data can be transferred to the upper layer.

FIG. 2x illustrates a method of generating an SDAP header for data received from an upper layer according to an embodiment of the present invention, performing uplink data compression (UDC) on the PDCP layer device, encrypting the UDC header without applying integrity protection The integrity protection is not performed in the SDAP header, the encryption is not performed, and the encryption is not performed in the MAC-I.

In FIG. 2x, the SDAP layer device is configured to use the SDAP layer device function by an RRC message such as 2e-10 or 2e-40 or 2e-75 in FIG. 2e, or to use the SDAP header, (UDC) is used for uplink or downlink, if data is received from an upper layer, then SDAP (2x-05), such as 2x-05, Header to the PDCP layer device. The PDCP layer apparatus performs user data compression (UDC) (2x-10) on a part (for example, IP packet header) excluding the SDAP header of the received PDCP SDU. The UDC buffer is used to calculate the checksum field based on the current UDC buffer, and the UDC header can be formed to be connected to the SDAP header such as 2v-20. If the integrity protection is set, the PDCP layer device receives UDC header, SDAP header, UDC block (2x-20), UDC header and SDAP header (2x-25, 2x-35), and perform integrity protection (Integrity protection) and calculate Message Authentication Code for Integrity (MAC-I). When calculating the MAC-I, the input value may be a PDCP COUNT value, an uplink or downlink indicator, a bearer identifier, a security key, data itself (a part where integrity protection is performed), and the like. The calculated MAC-I can be joined to the back of the data, such as 2x-40. The MAC-I may have a predetermined size, for example, a size of 4 bytes. (2x-40, 2x-45) PDCP headers are generated for the 2x-40s that have joined the MAC-I, except for the UDC header, the SDAP header and the MAC-I, -50) to the lower layer so that data processing can be performed in the RLC layer device and the MAC layer device. Here, the MAC-I is not encrypted. If MAC-I is not encrypted, the processing gain of the data processing can be further improved as described below.

The receiving end removes the MAC header and the RLC header and forwards the data to the PDCP layer. The receiving PDCP layer reads and removes the PDCP header, the UDC header and the SDAP header, removes the UDC header, the SDAP header, And performs deciphering. Here, MAC-I is not decoded. Integrity verification is performed on the upper layer header (for example, TCP / IP header) and the data portion excluding the UDC header and the SDAP header, and the computed MAC-I (X-MAC) is calculated. When calculating the X-MAC, the input value may be the PDCP COUNT value, the uplink or downlink indicator, the bearer identifier, the security key, and the data itself (the part where integrity verification is performed), to the integrity verification algorithm. If the MAC-I value matches the computed X-MAC and the MAC-I value attached to the back of the received data, integrity verification is successfully performed. If the MAC-I value matches Otherwise, the integrity verification has failed, so you should discard the data and report that the integrity verification failed at the higher layer (eg the RRC layer). Upon completion of the integrity verification, the UDC header is read to check whether the checksum has failed, the UDC procedure for the upper layer data can be performed, and the restored upper layer data can be transferred to the upper layer.

If the UDC header and the SDAP header are not encrypted or the integrity protection is not performed, the structure of the base station implementation can be facilitated. In particular, in the CU (Distributed Unit) split structure, the CU encrypts the SDAP header Otherwise, DU can read the SDAP header, check the QoS information, and apply it to the scheduling, which is advantageous for adjusting and adjusting the QoS. In addition, there is an advantage in terms of data processing in terminal and base station implementation. Also, if MAC-I is not encrypted, the processing gain of the data processing can be further improved as described below.

FIG. 2 Y illustrates an example of a case where an SDAP header and an UDC header, which are not encrypted and unprotected according to an embodiment, are applied, user data compression (UDC) is performed, and MAC- Processing gain.

When implementing a terminal and a base station in FIG. 2Y, the SDAP layer device and the PDCP layer device may be integrally implemented as a single layer device (2y-01). Since the SDAP layer device is logically an upper layer device of the PDCP layer device, when the SDAP layer device receives data (2y-05) from an upper application layer, the SDAP layer device performs RRC If the SDAP layer device function is set to use the message or the SDAP header is set to be used and if the integrity protection is set and if user data compression (UDC) is set to be used for the uplink or downlink, It is necessary to generate and configure an SDAP header as shown in 2j-05 in Fig. 2J. However, the ciphering procedure, the integrity protection procedure or the user data compression procedure in the terminal and the base station implementation can be implemented by applying the HW (hardware) accelerator because the operation is a complex operation. These HW accelerators have high processing gains in repetitive and continuous procedures. However, if the SDAP layer device configures the SDAP header each time data is received from the upper layer device, and if the integrity protection and user data compression (UDC) are set, the user data compression procedure is performed, the UDC header is generated, If the procedure and the encryption procedure are performed on the data part excluding the UDC header and the SDAP header, and the PDCP header is generated and added to the SDAP header, the procedure of generating the UDC header and the SDAP header before performing the integrity protection and the encryption, (Interruption).

Therefore, the present disclosure describes a method of integrating an SDAP layer device and a PDCP layer device together with an unencrypted UDC header, an SDAP header, and an unencrypted MAC-I, without applying integrity protection, as a single layer device do. That is, when data is received from an upper application layer, user data compression (UDC) is performed on an upper layer header portion (for example, an IP packet header) of the PDCP SDU continuously and repeatedly received each time data is received 2y-10) performs the integrity protection procedure (2y-25), calculates the MAC-I (2y-35, 2y-45), performs the encryption procedure on the data subjected to the integrity protection, and transmits the PDCP header, the UDC header, and the SDAP Header and MAC-I at the same time, integrity protection is applied, and it can be connected to the encrypted data and transmitted to the lower layer (2y-50). That is, the generated headers can be attached to the front part of the data, and the MAC-I can be connected to the rear part. The generation of the PDCP header, the SDAP header and the MAC-I may be performed in parallel with the integrity protection procedure or the encryption procedure. When a header is generated in parallel, an SDAP header, a PDCP header, a UDC header or an RLC header or a MAC header are generated together and the transmission is prepared by connecting headers at the head of the data processed data at once Can be prepared. In the case of MAC-I, data can be concatenated at the end of the processed data. In addition, the receiving end separates the SDAP header, the PDCP header, the UDC header or the RLC header or the MAC header from the data all at once, grasps the information corresponding to each layer, and processes the data in the reverse order of the data processing of the transmitting end . Therefore, the HW accelerator can be applied continuously and repeatedly, and the data processing efficiency can be improved because there is no interruption such as generation of UDC header or SDAP header in the middle. In addition, if integrity protection is set, integrity protection can be repeatedly performed by applying a hardware accelerator as described in the encryption procedure before performing the encryption procedure. That is, integrity protection can be applied and encryption can be performed.

The receiving PDCP layer apparatus may also be implemented as a single layer apparatus by integrating the SDAP layer apparatus and the PDCP layer apparatus as in the case of 2l-01. That is, when data is received from a lower layer (RLC layer), the SDAP layer device function is set to be used by an RRC message such as 2e-10, 2e-40, or 2e-75 in FIG. , The PDCP header, the UDC header, and the SDAP header can be read and removed at once, and the decryption process can be repeatedly applied to the data. Upon completion of the integrity verification, the UDC header is read to check whether the checksum has failed, the UDC procedure for the upper layer data can be performed, and the restored upper layer data can be transferred to the upper layer. That is, it is possible to read and remove the headers of the received data, read and remove the MAC-I after the data, decrypt the data portion, and perform the integrity verification procedure. When the integrity verification is completed, a user data decompression procedure is performed on an upper layer header (for example, an IP packet header), and the restored upper layer data can be transferred to the upper layer.

FIG. 2Z illustrates an operation of a SDAP / PDCP layer device in an SDAP / PDCP layer device or a bearer or a logical channel in which an integrity protection is set when an SDP header of an unencrypted SDP / Layer device according to the present invention.

In FIG. 2Z, when implementing a terminal and a base station, an SDAP layer device and a PDCP layer device may be integrally implemented as a single layer device (2z-01). In the present invention, a method of integrating an SDAP layer device and a PDCP layer device together with an unencrypted SDAP header and implementing it as a single layer device is proposed when integrity protection is set. In other words, when data is received from the upper application layer, the integrity protection is applied (2z-10), the encryption process is continuously and repeatedly performed (2z-15), and the PDCP header The SDAP header 2z-20 can be generated at the same time, and can be transmitted to the lower layer by connecting to the encrypted data. The generation of the PDCP header and the SDAP header may be performed in parallel with an integrity protection procedure or an encryption procedure. When a header is generated in parallel, an SDAP header, a PDCP header, a UDC header or an RLC header or a MAC header are generated together and the transmission is prepared by connecting headers at the head of the data processed data at once Can be prepared. In addition, the receiving end separates the SDAP header, the PDCP header, the UDC header or the RLC header or the MAC header from the data all at once, grasps the information corresponding to each layer, and processes the data in the reverse order of the data processing of the transmitting end . Therefore, the HW accelerator can be applied continuously and repeatedly, and the data processing efficiency can be improved because there is no interruption such as generation of the SDAP header in the middle. HW accelerators can also be applied to user compressed data procedures.

The receiving PDCP layer device may be embodied as a single layer device by integrating the SDAP layer device and the PDCP layer device in a case where the integrity protection is set. In other words, when data is received from the lower layer (RLC layer), (2z-25) is set to use the SDAP layer device function by an RRC message such as 2e-10 or 2e-40 or 2e-75 in FIG. The PDCP header and the SDAP header are read and removed at once, (2z-30), the deciphering procedure is repeatedly applied to the data (2z-35), and the integrity verification is performed verification process can be repeatedly applied to the upper layer (2z-40).

FIG. 2B illustrates a structure of a UE according to an embodiment of the present invention.

2B, the UE includes a radio frequency (RF) processing unit 2ab-10, a baseband processing unit 2ab-20, a storage unit 2ab-30 and a control unit 2ab-40 .

The RF processor 2ab-10 performs a function of transmitting and receiving a signal through a radio channel such as band conversion and amplification of a signal. That is, the RF processor 2ab-10 up-converts the baseband signal provided from the low-band processor 2ab-20 to an RF band signal and transmits the RF band signal through the antenna, Signal. For example, the RF processor 2ab-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital to analog converter (DAC), an analog to digital converter have. In Fig. 2B, only one antenna is shown, but the terminal may have a plurality of antennas. In addition, the RF processing unit 2ab-10 may include a plurality of RF chains. Further, the RF processing unit 2ab-10 may perform beamforming. For beamforming, the RF processor 2ab-10 may adjust the phase and size of each of the signals transmitted and received through a plurality of antennas or antenna elements. The RF processor 2ab-10 may perform MIMO and may receive multiple layers when performing a MIMO operation. The RF processing unit 2ab-10 may perform reception beam sweeping by appropriately setting a plurality of antennas or antenna elements under the control of the control unit, or adjust the direction and beam width of the reception beam such that the reception beam is coordinated with the transmission beam .

The baseband processor 2ab-20 performs conversion between the baseband signal and the bitstream according to the physical layer specification of the system. For example, at the time of data transmission, the baseband processing unit 2ab-20 generates complex symbols by encoding and modulating transmission bit streams. In receiving the data, the baseband processor 2ab-20 demodulates and decodes the baseband signal provided from the RF processor 2ab-10 to recover the received bitstream. For example, in accordance with an orthogonal frequency division multiplexing (OFDM) scheme, the baseband processing unit 2ab-20 generates complex symbols by encoding and modulating transmission bit streams, and maps the complex symbols to subcarriers Then, OFDM symbols are constructed by performing inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. In receiving the data, the baseband processing unit 2ab-20 divides the baseband signal provided from the RF processing unit 2ab-10 into OFDM symbol units and performs a fast Fourier transform (FFT) operation on the sub- And restores the received bit stream through demodulation and decoding.

The baseband processing unit 2ab-20 and the RF processing unit 2ab-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 2ab-20 and the RF processing unit 2ab-10 may be referred to as a transmitting unit, a receiving unit, a transmitting / receiving unit, or a communication unit. Furthermore, at least one of the baseband processing unit 2ab-20 and the RF processing unit 2ab-10 may include a plurality of communication modules to support a plurality of different radio access technologies. Also, at least one of the baseband processing unit 2ab-20 and the RF processing unit 2ab-10 may include different communication modules for processing signals of different frequency bands. For example, different wireless access technologies may include LTE networks, NR networks, and the like. Also, different frequency bands may include a super high frequency (SHF) band (e.g., 2.5 GHz, 5 GHz), and a millimeter wave (e.g., 60 GHz) band.

The storage unit 2ab-30 stores data such as a basic program, an application program, and setting information for operation of the terminal. The storage unit 2ab-30 provides the stored data at the request of the control unit 2ab-40.

The control unit 2ab-40 controls overall operations of the terminal. For example, the control unit 2ab-40 transmits and receives signals through the baseband processing unit 2ab-20 and the RF processing unit 2ab-10. Further, the control unit 2ab-40 writes data to the storage unit 2ab-40 and reads it. To this end, the control unit 2ab-40 may include at least one processor. For example, the controller 2ab-40 may include a communication processor (CP) for performing communication control and an application processor (AP) for controlling an upper layer such as an application program.

2c shows a configuration of a base station according to an embodiment according to an embodiment.

2C, the base station includes an RF processing unit 2ac-10, a baseband processing unit 2ac-20, a backhaul communication unit 2ac-30, a storage unit 2ac-40, .

The RF processing unit 2ac-10 performs a function of transmitting and receiving a signal through a wireless channel such as band conversion and amplification of a signal. That is, the RF processor 2ac-10 up-converts the baseband signal provided from the baseband processor 2ac-20 to an RF band signal, transmits the RF band signal through the antenna, Signal. For example, the RF processing unit 2ac-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. In Fig. 2 (a), only one antenna is shown, but the present invention is not limited thereto. Further, the RF processing unit 2ac-10 may include a plurality of RF chains. Further, the RF processing unit 2ac-10 can perform beam forming. For beamforming, the RF processor 2ac-10 may adjust the phase and size of each of the signals transmitted and received through the plurality of antennas or antenna elements. The RF processor 2ac-10 can perform downlink MIMO operation by transmitting one or more layers.

 The baseband processing unit 2ac-20 performs a function of converting a baseband signal and a bit string according to a physical layer standard. For example, at the time of data transmission, the low-band processing unit 2ac-20 generates complex symbols by encoding and modulating transmission bit streams. Also, upon receiving the data, the baseband processing unit 2ac-20 demodulates and decodes the baseband signal provided from the RF processing unit 2ac-10 to recover the received bit stream. For example, in accordance with the OFDM scheme, when data is transmitted, the baseband processing unit 2ac-20 generates complex symbols by encoding and modulating transmission bit streams, maps the complex symbols to subcarriers, And constructs OFDM symbols through CP insertion. Also, upon receiving the data, the baseband processing unit 2ac-20 divides the baseband signal provided from the RF processing unit 2ac-10 into OFDM symbol units, restores the signals mapped to the subcarriers through the FFT operation , And demodulates and decodes the received bit stream. The baseband processing unit 2ac-20 and the RF processing unit 2ac-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 2ac-20 and the RF processing unit 2ac-10 may be referred to as a transmitting unit, a receiving unit, a transmitting / receiving unit, a communication unit, or a wireless communication unit.

 The communication unit 2ac-30 provides an interface for performing communication with other nodes in the network.

 The storage unit 2ac-40 stores data such as a basic program, an application program, and setting information for operation of the main base station. In particular, the storage unit 2ac-40 may store information on the bearer allocated to the connected terminal, the measurement result reported from the connected terminal, and the like. In addition, the storage unit 2ac-40 may provide multiple connections to the terminal or may store information serving as a criterion for determining whether to suspend the terminal. The storage unit 2ac-40 provides the stored data at the request of the control unit 2ac-50.

 The control unit 2ac-50 controls the overall operations of the main base station. For example, the control unit 2ac-50 transmits and receives signals through the baseband processing unit 2ac-20 and the RF processing unit 2ac-10 or through the backhaul communication unit 2ac-30. Further, the control unit 2ac-50 writes and reads data in the storage unit 2ac-40. To this end, the control unit 2ac-50 may include at least one processor.

3A is a diagram showing a structure of an LTE system.

3A, a wireless communication system includes a plurality of base stations 3a-05, 3a-10, 3a-15 and 3a-20, a Mobility Management Entity (MME) (Serving-Gateway) 3a-30. A user equipment (hereinafter referred to as a UE or a terminal) 3a-35 is connected to the outside through the base stations 3a-05, 3a-10, 3a-15, 3a-20 and S- Connect to the network.

The base stations 3a-05, 3a-10, 3a-15, and 3a-20 provide wireless access to terminals connected to the network as access nodes of the cellular network. That is, the base stations 3a-05, 3a-10, 3a-15, and 3a-20 collect status information such as buffer status, available transmission power status, channel status, And supports connection between terminals and a core network (CN) by scheduling. The MME 3a-25 is a device for performing various control functions as well as a mobility management function for a terminal, and is connected to a plurality of base stations. The S-GW 3a-30 is a device for providing a data bearer. The MME 3a-25 and the S-GW 3a-30 can further perform authentication and bearer management for the terminals connected to the network, -10) 3a-15 (3a-20) or packets to be transmitted to the base stations 3a-05, 3a-10, 3a-15 and 3a-20.

3B is a diagram illustrating a wireless protocol structure of the LTE system.

The NR system has almost the same protocol structure as the LTE system.

3B, the wireless protocol of the LTE system includes Packet Data Convergence Protocol (PDCP) (3b-05) 3b-40 and RLC (Radio Link Control) 3b-10 ), And a MAC (Medium Access Control) 3b-15 (3b-30). The Packet Data Convergence Protocol (PDCP) 3b-05 3b-40 is responsible for operations such as IP header compression / decompression and performs Radio Link Control (RLC) 3b-10 -35) reconfigures the PDCP PDU (Packet Data Unit) to an appropriate size. The MAC (3b-15) 3b-30 is connected to a plurality of RLC layer devices arranged in one terminal, multiplexes RLC PDUs into MAC PDUs, and demultiplexes RLC PDUs from MAC PDUs. The physical layer 3b-20 (3b-25) channel-codes and modulates the upper layer data, converts the OFDM symbol into an OFDM symbol and transmits the OFDM symbol on a wireless channel, or demodulates and decodes an OFDM symbol received on a wireless channel, . Also, in the physical layer, HARQ (Hybrid ARQ) is used for additional error correction. In the receiving end, transmission of the packet transmitted from the transmitting end is carried out with 1 bit. This is called HARQ ACK / NACK information. The downlink HARQ ACK / NACK information for uplink transmission is transmitted through a PHICH (Physical Hybrid-ARQ Indicator Channel) physical channel, and the uplink HARQ ACK / NACK information for downlink transmission includes a Physical Uplink Control Channel (PUCCH) (Physical Uplink Shared Channel) physical channel.

Although not shown in FIG. 3B, RRC (Radio Resource Control (RRC) layer) exists in the upper part of the PDCP layer of the UE and the base station. The RRC layer provides connection and measurement related control messages for radio resource control Can receive.

Meanwhile, the PHY layer may be composed of one or a plurality of frequency / carriers, and a technique of simultaneously setting and using a plurality of frequencies in one base station is referred to as a carrier aggre- gation (CA). The CA technology is a technique in which only one carrier is used for communication between a UE (User Equipment, UE) and a base station (E-UTRAN NodeB, eNB), and the subcarrier is further used by using one or more sub- It is possible to dramatically increase the amount of transmission. Meanwhile, in the LTE and NR systems, a cell in a base station using a main carrier is referred to as PCell (Primary Cell), and a subcarrier is referred to as SCell (Secondary Cell). A technology in which the CA function is extended to two base stations is referred to as dual connectivity (hereinafter referred to as DC). DC technology, a UE concurrently connects a Master E-UTRAN NodeB (MeNB) and a Secondary E-UTRAN NodeB (SeNB) (Hereinafter referred to as MCG), and cells belonging to the auxiliary base station are referred to as a secondary cell group (hereinafter referred to as SCG). The representative cell of each cell group is referred to as a primary cell (hereinafter, referred to as PCell), and the representative cell of the auxiliary cell group is referred to as a primary secondary cell (hereinafter referred to as PSCell) . When using the above-mentioned NR, the terminal can use LTE and NR simultaneously by using MCG as LTE technology and SCG as NR.

Meanwhile, in the LTE and NR systems, the UE reports the power headroom information (PHR) according to predetermined conditions to the BS. The power headroom information means a difference between a maximum transmission power set for the terminal and a transmission power estimated by the terminal. The transmission power estimated by the terminal is calculated based on a value used for transmission when the terminal actually transmits the uplink (the calculated value is referred to as a Real value). However, if the terminal does not actually transmit the transmission power, (The calculated value is referred to as a virtual value) based on a predetermined predetermined formula. By reporting the power headroom information, the base station can determine to what degree the maximum transmittable power value of the terminal is. On the other hand, in the CA situation, the power headroom information is transmitted for each subcarrier.

3C is a diagram for explaining carrier integration in a terminal.

Referring to FIG. 3C, one base station generally transmits and receives multiple carriers over several frequency bands. For example, when a carrier 3c-15 with a center frequency f1 and a carrier with a center frequency f3 (3c-10) are transmitted from the base station 3c-05, Lt; RTI ID = 0.0 &gt; carriers. &Lt; / RTI &gt; However, a terminal having a carrier aggregation capability can transmit and receive data from several carriers at the same time. The base station 3c-05 can increase the transmission rate of the terminal 3c-30 by allocating more carriers to the terminal 3c-30 having the carrier integration capability depending on the situation.

In the conventional sense, when one forward carrier and one reverse carrier that are transmitted and received from one base station constitute one cell, carrier integration may be understood as a case in which a terminal simultaneously transmits and receives data through a plurality of cells will be. This increases the maximum transfer rate in proportion to the number of carriers being integrated.

Hereinafter, in the present disclosure, it is assumed that a terminal receives data through any forward carrier or transmits data through an arbitrary reverse carrier means that a control channel and a data channel provided in a cell corresponding to a center frequency and a frequency band, And has the same meaning as that of transmitting and receiving data. In the following, the present disclosure will be described on the assumption of an LTE system for convenience of explanation, but the present disclosure can be applied to various wireless communication systems supporting carrier integration.

Even if carriers are aggregated or not, the reverse transmission output should be maintained at an appropriate level since the reverse (i.e., terminal to base station) transmission will cause interference in the reverse direction of the other cell. To do so, the terminal calculates an uplink transmission output using a predetermined function in performing uplink transmission, and performs uplink transmission using the calculated uplink transmission output. For example, the UE inputs input values capable of estimating channel conditions such as scheduling information and path loss value, such as the amount of allocated transmission resources, a modulation coding scheme (MCS) level to be applied, to a predetermined function, And performs reverse transmission by applying the calculated requested reverse transmission output value. The reverse transmission output value applicable to the UE is limited by the maximum transmission value of the UE. When the calculated required transmission output value exceeds the maximum transmission value of the UE, the UE applies reverse transmission by applying the maximum transmission value. In this case, since a sufficient reverse transmission output can not be applied, degradation of the reverse transmission quality may occur. The base station preferably performs scheduling so that the requested transmission power does not exceed the maximum transmission power. However, since some parameters such as path loss can not be grasped by the base station, the terminal transmits a Power Headroom Report (PHR) message, if necessary, to transmit its own PH (Power Headroom) .

2) the MCS to be applied to the reverse transmission; 3) the path loss of the associated forward carrier; and 4) the cumulative value of the output adjustment command. Since the path loss (PL) or the accumulated output adjustment command value may differ from one reverse carrier to another, it is appropriate to set whether or not the PHR transmission is performed for each reverse carrier when a plurality of reverse carriers are integrated in one terminal. However, for efficient PHR transmission, it may also report all of the PHs for multiple reverse carriers in one reverse carrier. Depending on the operational strategy, a PH may be needed for carriers that do not have actual PUSCH transmissions. Thus, in such a case, the method of reporting all of the PHs for multiple reverse carriers in one reverse carrier may be more efficient. To this end, the existing PHR should be expanded. A plurality of PHs to be included in one PHR will be configured in a predetermined order.

The PHR is triggered when the path loss of the associated forward carrier is changed beyond a predetermined reference value, the prohibit PHR timer expires, or a predetermined period of time after the PHR is generated. Even if the PHR is triggered, the UE does not transmit the PHR immediately but waits until the time when the reverse transmission is possible, for example, the time when the reverse transmission resource is allocated. This is because the PHR is not information that needs to be processed very quickly.

FIG. 3D is a diagram for explaining the concept of multiple connections in LTE and NR.

In Figure 3D, the terminal (3d-05) uses a macro base (3d-00) using LTE technology and NR technology And the small cell base stations 3d-10 are connected at the same time to transmit and receive data. This is called EN-DC (E-UTRAN-NR Dual Connectivity). The macro base station is referred to as MeNB (Master E-UTRAN NodeB), and the small cell base station is referred to as SgNB (Secondary 5G NodeB). There may be several small cells in the service area of MeNB, and MeNB is connected to SgNBs via wired backhaul network (3d-15). The set of serving cells received from MeNB is referred to as a master cell group (3d-20). In a MCG, one serving cell must have all the functions that the existing cell has performed, such as connection establishment, connection re- PCell (primary cell) (3d-25). In PCell, the uplink control channel has a PUCCH. The serving cell other than PCell is called SCell (Secondary Cell) (3d-30). FIG. 3D shows a scenario in which MeNB provides one SCell and SgNB provides three SCells. The set of serving cells provided by the SgNB is referred to as an SCG (Secondary Cell Group) (3d-40). MeNB sends a command to the SgNB to add, change and remove the serving cells provided by the SgNB when the UE transmits and receives data from two base stations. In order to issue such a command, the MeNB can configure the UE to measure the serving cell and neighboring cells. The terminal shall report the measurement result to MeNB according to the setting information. In order for the SgNB to efficiently transmit and receive data to and from the UE, a serving cell that plays a role similar to that of the MCG is required. In the present disclosure, this is referred to as PSCell (Primary SCell). The PSCell is defined as one of the serving cells of the SCG and has an uplink control channel PUCCH. The PUCCH is used by the UE to transmit HARQ ACK / NACK information, CSI (Channel Status Information) information, and SR (Scheduling Request) to the BS.

The present disclosure describes a method for a terminal that transmits and receives data using a plurality of radio access technologies (RATs) simultaneously in a wireless communication system to report a transmission power margin (power headroom) of a terminal do.

According to the present disclosure, a terminal correctly reports transmit power that can be transmitted for each base station, thereby enabling the base station to correctly perform uplink scheduling.

3E is a diagram illustrating an uplink transmission method according to an uplink type according to an exemplary embodiment of the present invention.

In FIG. 3E, an example 1 schematically illustrates a scenario in which a UE sets up two serving cells, that is, PCell (3e-01) and SCell (3e-03), and performs uplink transmission according to scheduling of the BS FIG. In this scenario, the UE can not simultaneously transmit the PUCCH and the PUSCH in one serving cell due to the constraints of the transmission method and the RF structure. Accordingly, the UE encapsulates the PUCCH information when transmitting the PUSCH (3e-05). At this time, the PUCCH information is transmitted in the PCell, or in the case where there is no PUSCH to be transmitted to the PCell, the SCell transmits the lower SCell to the lower SCell. The PHR message is transmitted as a part of the PUSCH. Accordingly, in this scenario, the UE transmits the PUSCH transmission (3e-05) (3e-07) at the maximum transmission power (PCMAX, c) To report only the power headroom value. This is called a Type 1 power headroom.

FIG. 2 is a diagram illustrating a scenario in which a UE performs uplink transmission according to scheduling of a BS after receiving two serving cells, that is, a PCell (3e-11) and a SCell (3e-13). In this scenario, the UE has the capability to transmit PUCCH and PUSCH simultaneously in one serving cell, or transmits the PUCCH and PUSCH separately using the uplink transmission technique capable of simultaneous transmission. At this time, in the case of PCell (or the corresponding SCell when the PUCCH can be transmitted to the SCell), the UE not only transmits the PUSCH transmission (3e-17) but also the PUCCH transmission (3e- It is necessary to report the power headroom value obtained by subtracting the PUSCH transmission and the PUCCH transmission value from each other. This is called a Type 2 power headroom.

When reporting the Type 1 or Type 2 power headroom, the terminal reports using the Single Entry PHR format (3e-21) or the Multiple Entry PHR format (3e-31). When the dual connection is established, Report using format. In this case, the power headroom is reported as (3e-41) (3e-51) (3e-61), and when reporting is required, the corresponding PCMAX, 53) (3e-63). On the other hand, when reporting the power headroom, the terminal reports a field having a length of 6 bits as shown in the figure. In LTE, the value is as shown in the following table. This is referred to as Table 3.

[Table 3]

On the other hand, according to the frequency range in which the base station operates in NR, it can be broadly divided into two frequency ranges as follows.

[Table 4]

The transmission power required for the base station operating in FR1 and the base station operating in FR2 may be very different. Accordingly, it is possible to define a table different from the table of LTE according to each frequency range (i.e., FR1 and FR2, respectively).

For example, Table 5 below can be used for the PHR report for the base station operating in FR1 among NR base stations (Table 5 below shows the same table as the LTE table for the sake of convenience because it is not much different from the frequency range in which LTE operates) , It may have a different value).

[Table 5]

For example, Table 6 below can be used for PHR reporting for base stations operating in FR1 among NR base stations.

[Table 6]

Accordingly, when the UE reports the PHR for each cell set up and activated by the current BS, even if the same PH report field is used in the Multiple Entry PHR format according to the RAT and the operating frequency of the corresponding serving cell, The table is used to generate a value and report it to the base station.

On the other hand, in the case of EN-DC, the frequencies operating between the LTE base station MeNB and the NR base station SgNB may not be known. This is because they can be designed to operate independently to assure independent operation. Accordingly, when reporting the PHR to the LTE base station, which is the MeNB, the frequency range in which the corresponding cells operate and the corresponding PHR report table for the LTE serving cells are reported using Table 3 since only Table 3 is shown. Also, when reporting the PHR in the EN-DC situation, the serving cell of the SgNB (i.e., the NR base station) should also be reported. Since the LTE base station does not know the frequency information of the serving cell of the NR base stations , And reported using Table 3. For example, if the frequency of the calculated NR serving cell belongs to FR2 and the PH value is 45 dB, it should be reported using the POWER_HEADROOM_58 value when reporting to the NR base station, but using the POWER_HEADROOM_63 value when reporting to the LTE base station. Report. If the PHR report is reported as an SgNB (i.e., an NR base station), if the PH value is 45 dB, report the correct value using the POWER_HEADROOM_58 value.

On the other hand, the scenario of dual connectivity between an NR base station and an NR base station is referred to as NR-DC. In this case as well, the frequencies operating between the NR base station of MgNB and the NR base station of SgNB may not be known. This is because they can be designed to operate independently to assure independent operation. If the serving cell is not included in the currently reporting base station (that is, if the serving cell is not included in the MCG report), the MCG reports the serving cell in accordance with the frequency operation range (FR1 or FR2) The PHR value is reported to the base station based on Table 5 (i.e. FR1) for the serving cell of the SCG, or for the serving cell of the MCG for reporting the PHR to the SCG. Or one of the R bits reserved (3e-39) reserved in the Multiple Entry PHR format is used to inform the base station whether the corresponding value is a table for FR1 (Table 5) or a table for FR2 (Table 6) It may separately inform the base station of the correct value.

FIG. 3F is a diagram illustrating a message flow between a terminal and a base station when reporting a power headroom when applying a dual RAT-to-RAT connection according to an exemplary embodiment.

When the terminal 3f-01 in the idle state IDLE selects the appropriate LTE base station (or cell) 3f-03 by searching the periphery of the terminal and decides to connect to the cell, the terminal transmits random access And transmits an access request message through the procedure (3f-11). The connection request message is transmitted as a message of the RRC layer and is transmitted using the corresponding technique according to the above-described UL linking technique.

Thereafter, the base station receives a connection setup message from the base station (3f-13), receives a connection setup completion message (3f-15) as a confirmation message for the connection setup message, and completes the connection to the base station. Upon receiving the connection setup message, the terminal transitions to a connected state (CONNECTED) and can transmit and receive data to / from the corresponding base station. Then, the base station can set the PHR-related parameters using the RRC layer message (3f-19) in order to receive the PHR report for scheduling to the UE. PHR-related parameters include periodicPHR-Timer, prohibitPHR-Timer, and dl-PathlossChange. The periodicPHR-Timer is a timer that is periodically set to report the PHR value to the base station. The prohibitPHR-Timer is a timer that is set to prevent frequent PHR reporting, and the dl-PathlossChange value is a value indicating that the reception change of the downlink channel is not less than the corresponding value If so, to report the PHR accordingly. In addition, the connection reestablishment message may include radio bearer related setup information used for data transmission, or a separate connection reestablishment message may be transmitted and set again. In addition, if the UE has set up the measurements for the neighboring NR base stations as set by the base station and reports the result, the terminal is set up between the LTE base station and the NR base station (3f-17) -03 to the NR base station 3f-05 in addition to the NR base station 3f-05. That is, information for setting dual connectivity (EN-DC) may also be included. The RRC configuration uses the RRCConnectionReconfiguration message. The MS receiving the RRC layer message transmits an acknowledgment message to the BS (3f-21). It uses the RRCConnectionReconfigurationComplete message.

When the dual connectivity capable of using the LTE base station and the NR base station simultaneously is established according to the setup message, the UE can simultaneously transmit and receive data with the LTE base station and the NR base station (3f-25) (3f-27).

On the other hand, conditions for when the PHR is to be transmitted to the base station (i.e., whether to trigger the report) can be defined, and the following conditions can be defined for both the LTE system and the NR system.

- When the prohibitPHR-Timer expires and the downlink reception intensity change is dl-PathlossChange dB or more

- periodicPHR-Timer has expired

- When the PHR report is initially set up

- If you add SCell with uplink

- In the case of using dual connectivity technology, if the secondary cell's primary cell (PSCell) is added

(3f-31) (3f-41), the UE generates and reports a PHR to the corresponding base station (3f-33) (3f-43).

If the UE satisfies the condition (3f-31) in the LTE eNB (3f-03), the UE sets the Type 1 power headroom value for all serving and currently active serving cells of the LTE base station and the NR base station And reports it to the LTE eNB 3f-03 (3f-33). Also, when actual transmission occurs in LTE base station or NR base station at the time of reporting PHR, report including PCMAX, c value for cell reporting Type 1 power headroom. In FIG. 3F, since the LTE is MeNB, if the terminal is configured to simultaneously transmit PUCCH and PUSCH to the PCELL, which is a representative cell of the MeNB, the terminal includes the Type 2 power headroom value of the PCell report. In addition, since the base station reporting the PHR in FIG. 3F is an LTE base station, regardless of whether it is a serving cell corresponding to an LTE base station or a serving cell corresponding to an NR base station, Table 3 (i.e., a table used for reporting PHR of LTE) And reports the result to the base station.

If the UE satisfies the condition in the NR gNB (3f-05) (3f-41), the UE includes a Type 1 power headroom value for all serving and currently active serving cells of the LTE base station and NR base station And reported as NR gNB (3f-05) (3f-43). Also, when actual transmission occurs in LTE base station or NR base station at the time of reporting PHR, report including PCMAX, c value for cell reporting Type 1 power headroom. Referring to FIG. 3F, a situation is assumed in which LTE is MeNB. Since the UE reports the power headroom to the NR gNB after the condition is satisfied in the NR gNB, it is assumed that the representative cell of the NR gNB (i.e., SgNB) If the PUCCH and PUSCH transmission are simultaneously enabled, the terminal reports the Type 2 power headroom value of the PSCell. In addition, if the terminal reports the Type 2 power headroom for the PCEl of the LTE base station and reports the actual transmission value, the PCMAX and c values for the LTE PCEl are also reported and transmitted. In addition, since the base station reporting the PHR in FIG. 3F is an NR base station, it is assumed that the NR base station understands Tables 3, 5, and 6. Accordingly, if the serving cell is a serving cell corresponding to the LTE base station, the UE generates a value using Table 3 (i.e., a table used for reporting PHR of LTE) and reports the result to the base station. Reports to the base station using Table 5 for FR1 and Table 6 for FR2 to report the extra power of the terminal.

Accordingly, the PHR is reported to the corresponding BS when each condition is generated, and the BS can determine the margin power currently possessed by the MS and schedule it according to the determined margin.

FIG. 3G is a diagram illustrating an operation sequence of a terminal when reporting a power headroom when applying a dual RAT-to-RAT connection according to an exemplary embodiment.

The terminal in the idle state (IDLE) searches the periphery of the terminal to select an appropriate LTE base station (or cell), and performs connection to the base station (3g-03). To this end, the RRConnectionRequest message of the RRC layer is transmitted to the base station, and the RRCConnectionSetupComplete message is transmitted to the base station by completing the connection procedure.

Then, the UE receives the setup message of the RRC layer for reporting the PHR from the LTE base station and transmits an acknowledgment message (3g-05). The RRConnectionReconfiguration message may be used for the setup message of the RRC layer, and the RRCConnectionReconfigurationComplete message may be used for the confirmation message. The setup message may include parameters such as periodicPHR-Timer, prohibitPHR-Timer, and dl-PathlossChange for PHR reporting. The periodicPHR-Timer is a timer that is periodically set to report the PHR value to the base station. The prohibitPHR-Timer is a timer that is set to prevent frequent PHR reporting, and the dl-PathlossChange value is a value indicating that the reception change of the downlink channel is not less than the corresponding value If so, to report the PHR accordingly. In addition, the connection reestablishment message may include radio bearer related setup information used for data transmission, or a separate connection reestablishment message may be transmitted and set again. In addition, if the UE is configured to measure the neighboring NR base stations as set by the base station, and reports the result, information that additionally sets the current LTE base station to use the NR base station may also be included. That is, information for setting up the dual connectivity may also be included.

Then, according to the set parameters, the UE determines whether to trigger the PHR report according to the following conditions (3g-07).

- When the prohibitPHR-Timer expires and the downlink reception intensity change is equal to or greater than the dl-PathlossChange dB value set by the base station

- If the periodicPHR-Timer set by the base station expires for periodic reporting

- When the PHR report is initially set up

- If you add SCell with uplink

- In the case of using dual connectivity technology, if the secondary cell's primary cell (PSCell) is added

If a PHR triggering condition occurs in each base station (3g-07), the UE determines whether EN-DC is set and whether the base station where the PHR triggering condition occurs is LTE or NR (3g-09).

If EN-DC is set and the condition is satisfied in the LTE eNB, or if LTE-LTE DC is set, the terminal shall set the Type 1 power headroom for all currently active and active serving cells of the LTE base station and NR base station And generates a PHR message to report to the LTE eNB. Also, when an actual transmission occurs in an LTE base station or an NR base station at the time of reporting a PHR, a PCMAX, c value for a cell reporting a Type 1 power headroom is also generated. Assuming that the LTE is MeNB in FIG. 3G, if the UE is configured to simultaneously transmit PUCCH and PUSCH to the PCELL, which is a representative cell of the MeNB, the UE also includes the Type 2 power headroom value of the PCell . In addition, since the base station reporting the PHR in FIG. 3G is the LTE base station, regardless of whether it is a serving cell corresponding to an LTE base station or a serving cell corresponding to an NR base station, Table 3 (i.e., a table used for reporting PHR of LTE) And generates a value and reports it to the base station (3g-11).

If the condition is satisfied in the NR gNB even if EN-DC is not set in the UE, DC is set in NR, or EN-DC is set, the UE is currently set up and activated in the LTE base station and the NR base station Generate a PHR message to report to the NR gNB including Type 1 power headroom values for all serving cells. Also, when an actual transmission occurs in an LTE base station or an NR base station at the time of reporting a PHR, a PCMAX, c value for a cell reporting a Type 1 power headroom is also generated. In FIG. 3G, it is assumed that the LTE is MeNB. Since the UE reports the power headroom to the NR gNB after the condition is satisfied in the NR gNB, it is assumed that the representative cell of the NR gNB (i.e., SgNB) If the terminal is set to transmit PUCCH and PUSCH simultaneously, the terminal generates a Type 2 power headroom value of the PSCell. In addition, if the terminal reports Type 2 power headroom to the PCEl of the LTE base station and reports the actual transmission value, the PCMAX and c values for the LTE PCell are also included in the report. In addition, since the base station reporting the PHR in FIG. 3G is an NR base station, it is assumed that the NR base station understands Tables 3, 5, and 6. Accordingly, if the serving cell is a serving cell corresponding to the LTE base station, the UE generates a value using Table 3 (i.e., a table used for reporting PHR of LTE) and reports the result to the base station. (3g-13) reports to the base station using Table 5 for FR1 and Table 6 for FR2, and reports the extra power of the terminal. In the case of DC between NRs, if the serving cell is not included in the currently reporting base station (i.e., reporting the PHR to the MCG, reporting the PHR to the serving cell of the SCG, or serving the SCG, The cell reports the PHR value to the base station based on Table 5 (i.e., FR1). Or one of the R bits reserved (3e-39) reserved in the Multiple Entry PHR format is used to inform the base station whether the corresponding value is a table for FR1 (Table 5) or a table for FR2 (Table 6) It may separately inform the base station of the correct value.

The generated PHR is reported to the base station (3g-15), and the base station informs the mobile station of the available power. Accordingly, the base station can determine the available power of the terminal and schedule it according to the determined available power.

3H illustrates a block configuration of a UE in a wireless communication system according to an embodiment.

Referring to FIG. 3H, the terminal includes a radio frequency (RF) processor 3h-10, a baseband processor 3h-20, a storage 3h-30, and a controller 3h-40.

The RF processing unit 3h-10 performs a function for transmitting and receiving a signal through a radio channel such as band conversion and amplification of a signal. That is, the RF processor 3h-10 up-converts the baseband signal provided from the baseband processor 3h-20 to an RF band signal and transmits the RF band signal through the antenna, Signal. For example, the RF processing unit 3h-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog converter (DAC), an analog to digital converter have. In Fig. 3H, only one antenna is shown, but the terminal may have a plurality of antennas. In addition, the RF processor 3h-10 may include a plurality of RF chains. Further, the RF processor 3h-10 may perform beamforming. For beamforming, the RF processor 3h-10 may adjust the phase and size of each of the signals transmitted and received through a plurality of antennas or antenna elements.

The baseband processor 3h-20 performs conversion between the baseband signal and the bitstream according to the physical layer specification of the system. For example, at the time of data transmission, baseband processing section 3h-20 generates complex symbols by encoding and modulating transmission bit streams. In receiving the data, the baseband processor 3h-20 demodulates and decodes the baseband signal provided from the RF processor 3h-10 to recover the received bitstream. For example, according to an orthogonal frequency division multiplexing (OFDM) scheme, the baseband processing unit 3h-20 generates complex symbols by encoding and modulating transmission bit streams, and maps the complex symbols to subcarriers Then, OFDM symbols are constructed by performing inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. When receiving the data, the baseband processing unit 3h-20 divides the baseband signal provided from the RF processing unit 3h-10 into OFDM symbol units and performs a fast Fourier transform (FFT) operation on the sub- And restores the received bit stream through demodulation and decoding.

The baseband processing section 3h-20 and the RF processing section 3h-10 transmit and receive signals as described above. Accordingly, the baseband processing section 3h-20 and the RF processing section 3h-10 may be referred to as a transmitting section, a receiving section, a transmitting / receiving section, or a communication section. Further, at least one of the baseband processing unit 3h-20 and the RF processing unit 3h-10 may include a plurality of communication modules to support a plurality of different radio access technologies. Also, at least one of the baseband processing unit 3h-20 and the RF processing unit 3h-10 may include different communication modules for processing signals of different frequency bands. For example, different wireless access technologies may include a wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), and the like. Also, different frequency bands may include a super high frequency (SHF) band (e.g., 2.5 GHz, 5 GHz), and a millimeter wave (e.g., 60 GHz) band.

The storage unit 3h-30 stores data such as a basic program, an application program, and setting information for operation of the terminal. In particular, the storage unit 3h-30 may store information related to a wireless LAN node performing wireless communication using a wireless LAN access technology. The storage unit 3h-30 provides the stored data at the request of the control unit 3h-40.

 The controller 3h-40 controls overall operations of the terminal. For example, the control unit 3h-40 transmits and receives signals through the baseband processing unit 3h-20 and the RF processing unit 3h-10. The control unit 3h-40 also writes and reads data in the storage unit 3h-40. To this end, the controller 3h-40 may include at least one processor. For example, the controller 3h-40 may include a communication processor (CP) for performing communication control and an application processor (AP) for controlling an upper layer such as an application program. In one embodiment, the control unit 3h-40 includes a multiple connection processing unit 3h-42 for performing processing for operating in a multiple connection mode. For example, the control unit 3h-40 may control the terminal to perform the procedure shown in the operation of the terminal shown in Fig. 3E.

In one embodiment, the controller 3h-40 receives the power headroom setting from the control message received from the base station, and when the dual connection is established, Determines the type of RAT of the base station, determines which power headroom information is to be sent, and transmits a message to the base station to transmit it.

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

When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored on a computer-readable storage medium are configured for execution by one or more processors in an electronic device. The one or more programs include instructions that cause the electronic device to perform the methods in accordance with the embodiments of the present disclosure or the claims of the present disclosure.

Such programs (software modules, software) may be stored in a computer readable medium such as a random access memory, a non-volatile memory including a flash memory, a ROM (Read Only Memory), an electrically erasable programmable ROM (EEPROM), a magnetic disc storage device, a compact disc-ROM (CD-ROM), a digital versatile disc (DVDs) An optical storage device, or a magnetic cassette. Or a combination of some or all of these. In addition, a plurality of constituent memories may be included.

The program may also be accessed through a communication network comprised of a communication network such as the Internet, an Intranet, a LAN (Local Area Network), a WLAN (Wide Area Network), or a SAN (Storage Area Network) and can be stored in an attachable storage device that can access the storage device. Such a storage device may be connected to an apparatus performing an embodiment of the present disclosure via an external port. Further, a separate storage device on the communication network may be connected to an apparatus performing the embodiments of the present disclosure.

In the specific embodiments of the present disclosure described above, the elements included in the invention have been represented singular or plural in accordance with the specific embodiments shown. It should be understood, however, that the singular or plural representations are selected appropriately according to the situations presented for the convenience of description, and the present disclosure is not limited to the singular or plural constituent elements, And may be composed of a plurality of elements even if they are expressed.

In the meantime, the embodiments of the present disclosure disclosed in this specification and the drawings are merely illustrative of specific examples in order to facilitate the understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it will be apparent to those skilled in the art that other modifications based on the technical idea of the present disclosure are feasible. Further, each of the above embodiments can be combined with each other as needed. For example, portions of an embodiment different from one embodiment of the present disclosure may be combined with one another to enable a base station and a terminal to operate. Although the above embodiments are presented on the basis of the FDD LTE system, other systems based on the technical idea of the above embodiment may be implemented in other systems such as a TDD LTE system, a 5G or NR system.

Claims (1)

A communication method of a terminal in a wireless communication system,
Receiving management object information from a network through an application level data message or higher signaling;
Identifying an access attempt to a NAS (Non Access Stratum);
Mapping one or more access identities and one access category based on the managed object information; And
And transmitting the mapped access identity and access category information to an AS (Access Stratum).

Images