KR20220063695A - A method and an apparatus for accelerating data processing in a next generation wireless communication system - Google Patents

Abstract

The present invention relates to a 5G or 6G communication system for supporting a higher data transmitting rate after a 4G communication system such as LTE. According to the present invention, disclosed are a method for reducing procedures which have high complexity of data processing or require a lot of time in the data processing in a next-generation mobile communication system and a device thereof.

Description

A METHOD AND AN APPARATUS FOR ACCELERATING DATA PROCESSING IN A NEXT GENERATION WIRELESS COMMUNICATION SYSTEM

The present invention relates to a method and an apparatus for improving procedures that have high data processing complexity or require a lot of time for data processing in a next-generation mobile communication system.

Looking back on the progress of wireless communication generations, technologies for mainly human services such as voice, multimedia, and data have been developed. After the commercialization of the 5G (5th-generation) communication system, it is expected that connected devices, which are on an explosive increase, will be connected to the communication network. Examples of things connected to the network may include vehicles, robots, drones, home appliances, displays, smart sensors installed in various infrastructures, construction machines, and factory equipment. Mobile devices are expected to evolve into various form factors such as augmented reality glasses, virtual reality headsets, and hologram devices. In the 6th-generation (6G) era, efforts are being made to develop an improved 6G communication system to provide various services by connecting hundreds of billions of devices and things. For this reason, the 6G communication system is called a system after 5G communication (Beyond 5G).

In a 6G communication system that is predicted to be realized around 2030, the maximum transmission speed is tera (that is, 1,000 gigabytes) bps, and the wireless latency is 100 microseconds (μsec). That is, the transmission speed in the 6G communication system is 50 times faster than in the 5G communication system, and the wireless delay time is reduced by one-tenth.

In order to achieve such high data rates and ultra low latency, 6G communication systems use the terahertz band (for example, the 95 gigahertz (95 GHz) to 3 terahertz (3 THz) band). implementation is being considered. In the terahertz band, compared to the millimeter wave (mmWave) band introduced in 5G, the importance of technology that can guarantee the signal reach, that is, the coverage, is expected to increase due to more severe path loss and atmospheric absorption. As major technologies to ensure coverage, new waveforms, beamforming, and massive arrays that are superior in terms of coverage than radio frequency (RF) devices, antennas, orthogonal frequency division multiplexing (OFDM) input and multiple-output (MIMO)), full dimensional MIMO (FD-MIMO), an array antenna, and a multi-antenna transmission technology such as a large scale antenna should be developed. In addition, new technologies such as metamaterial-based lenses and antennas, high-dimensional spatial multiplexing technology using orbital angular momentum (OAM), and reconfigurable intelligent surface (RIS) are being discussed to improve the coverage of terahertz band signals.

In addition, in order to improve frequency efficiency and system network, in a 6G communication system, a full duplex technology in which uplink and downlink simultaneously use the same frequency resource at the same time, satellite and Network technology that integrates high-altitude platform stations (HAPS), etc., network structure innovation that supports mobile base stations, etc. and enables network operation optimization and automation, etc., and dynamic frequency sharing through collision avoidance based on spectrum usage prediction AI-based communication technology that realizes system optimization by utilizing (dynamic spectrum sharing) technology and artificial intelligence (AI) from the design stage and internalizing end-to-end AI support functions, The development of next-generation distributed computing technology that realizes complex services by utilizing ultra-high-performance communication and computing resources (mobile edge computing (MEC), cloud, etc.) is being developed. In addition, through the design of a new protocol to be used in the 6G communication system, the implementation of a hardware-based security environment, the development of a mechanism for the safe use of data, and the development of technology on the method of maintaining privacy, the connectivity between devices is further strengthened and the network Attempts to optimize, promote the softwareization of network entities, and increase the openness of wireless communication continue.

Due to the research and development of this 6G communication system, the next hyper-connected experience (the next hyper-connected) through the hyper-connectivity of the 6G communication system, which includes not only the connection between objects but also the connection between people and objects. experience) is expected to become possible. Specifically, the 6G communication system is expected to provide services such as true immersive extended reality (XR), high-fidelity mobile hologram, and digital replica. In addition, services such as remote surgery, industrial automation, and emergency response through security and reliability enhancement are provided through the 6G communication system, so it is applied in various fields such as industry, medical care, automobiles, and home appliances. will be

Since next-generation mobile communication systems must support extremely high data rates, procedures such as encryption or decryption procedures, integrity protection, verification procedures, or ARQ (Autonomous Repeat Request) operations that have a significant impact on data processing time are improved, and parallel processing is performed. We need a way to make this possible.

Accordingly, one object of the present invention is to propose various data processing methods for further improving data processing speed when a base station and a terminal perform data processing according to a high data rate in a next-generation mobile communication system.

In order to accomplish the above object, in a method of a transmitting apparatus in a wireless communication system according to an embodiment of the present invention, the method comprising: receiving service data units (SDUs) from an upper layer; generating concatenated data concatenating the SDUs; performing at least one of an integrity protection procedure and an encryption procedure on the concatenated data; and transmitting the data on which the at least one procedure has been performed to a receiving device through a lower layer, wherein security key information corresponding to each of the at least one procedure is included in one contiguous data. The same can be applied to SDUs.

In addition, in a method of a receiving device in a wireless communication system according to an embodiment of the present invention, the method comprising: receiving data from a transmitting device through a lower layer; performing at least one of an integrity verification procedure and a decryption procedure on the data; separating service data units (SDUs) included in the data on which the at least one procedure has been performed; and transferring the separated SDUs to a higher layer, wherein security key information corresponding to each of the at least one procedure may be equally applied to the SDUs included in the data.

In addition, in a transmitting apparatus in a wireless communication system according to an embodiment of the present invention, the transmitting and receiving unit; and receiving, from a higher layer, service data units (SDUs); generate concatenated data concatenating the SDUs; performing at least one of an integrity protection procedure and an encryption procedure on the concatenated data; and a control unit controlling the transceiver to transmit the data on which the at least one procedure has been performed to a receiving device through a lower layer, wherein security key information corresponding to each of the at least one procedure is one The same may be applied to SDUs included in concatenated data.

In addition, in a receiving apparatus in a wireless communication system according to an embodiment of the present invention, a transceiver; and controlling the transceiver to receive data from the transmitting device through a lower layer; performing at least one of an integrity verification procedure and a decryption procedure on the data; separating service data units (SDUs) included in the data on which the at least one procedure has been performed; and a control unit transmitting the separated SDUs to a higher layer, wherein security key information corresponding to each of the at least one procedure may be equally applied to the SDUs included in the data.

The present invention proposes a procedure such as an efficient encryption or decryption procedure, integrity protection, verification procedure, or ARQ (Autonomous Repeat Request) operation so that a very high data rate can be supported at a high data processing speed in the next-generation mobile communication system. It has the effect of maximizing the efficiency of the processing procedure and enabling more parallel processing.

1 is a diagram showing the structure of an LTE system to which the present invention can be applied.
2 is a diagram illustrating a radio protocol structure in an LTE system to which the present invention can be applied.
3 is a diagram illustrating the structure of a next-generation mobile communication system to which the present invention can be applied.
4 is a diagram illustrating a radio protocol structure of a next-generation mobile communication system to which the present invention can be applied.
5 shows a procedure for a terminal to switch from an RRC idle mode to an RRC connected mode in the next-generation mobile communication system of the present invention, and proposes a method for setting a protocol layer device or functions of the terminal is a drawing that
6 is a diagram showing the structure of a protocol layer device proposed in the present invention.
7A, 7B and 7C show a procedure for processing and transmitting data received from a higher layer device in each protocol layer device of a bearer in the next-generation mobile communication system of the present invention, and each protocol of a bearer for data received from a lower layer device It is a diagram for explaining a procedure of processing in a layer device and transferring it to a higher layer device.
8 is a view for explaining integrity protection, verification procedure, encryption or decryption procedure in the next-generation mobile communication system of the present invention.
9 is a diagram for explaining a long data processing time with high complexity when an integrity protection procedure or an encryption procedure is applied to data in a PDCP layer device in the present invention.
10 is a diagram illustrating an operation of driving an RLC reception window in the RLC layer device of the present invention.
11A and 11B are diagrams illustrating a first embodiment of a data concatenation procedure according to an embodiment of the present invention.
12A and 12B are diagrams illustrating a second embodiment of a data concatenation procedure according to an embodiment of the present invention.
13 is a diagram illustrating a third embodiment of a data concatenation procedure according to an embodiment of the present invention.
14A, 14B, 14C, and 14D are diagrams illustrating a structure of a header or a new field of an upper layer device suitable for the first or third embodiment of the data concatenation procedure proposed in the present invention.
15A, 15B, 15C, and 15D are diagrams illustrating a header structure or a new field structure of an upper layer device suitable for the second embodiment of the data concatenation procedure proposed in the present invention.
16 is a diagram comparing a data processing procedure in a next-generation mobile communication system according to the present invention and a data processing procedure proposed in the present invention.
17A and 17B are diagrams illustrating the gain of the data concatenation procedure proposed in the present invention from the viewpoint of an RLC layer device.
18 is a diagram for explaining that the data concatenation procedure of the upper layer device proposed in the present invention does not affect the basic data processing procedure of the next-generation mobile communication system.
19 is a diagram for explaining a method of implementing while inheriting the characteristics of a data concatenation function of a higher layer device proposed in the present invention, or an implementation method that can have advantages similar to those of a data concatenation function of a higher layer device.
20 is a diagram illustrating a data loss problem that may occur when a terminal configured with a data concatenation function proposed in the present invention performs a handover procedure.
21 is a diagram illustrating an SO-based segmentation operation that can be used in an RLC layer RLC AM mode or an RLC UM mode in the present invention.
22 is a diagram illustrating a data processing operation to which the SO-based partitioning method of the RLC AM mode or the RLC UM mode proposed in the present invention is applied.
23 is a diagram for explaining an SI field-based segmentation method proposed for an RLC UM mode or an RLC AM mode in the present invention.
24 is a diagram illustrating a data processing operation to which the SI-based partitioning method of the RLC UM mode or the RLC AM mode proposed in the present invention is applied.
25 is a diagram illustrating an RLC header structure applicable to an RLC UM mode or an RLC AM mode proposed by the present invention.
26 is a diagram showing the operation of the PDCP layer apparatus of the terminal proposed above of the present invention.
27 is a diagram illustrating the operation of the SDAP layer device (or new layer device) of the terminal proposed above of the present invention.
28 is a diagram illustrating a structure of a terminal to which an embodiment of the present invention can be applied.
29 is a diagram illustrating a block configuration of a TRP in a wireless communication system to which an embodiment of the present invention can be applied.

Hereinafter, the operating principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, if it is determined that a detailed description of a known function or configuration related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. And the terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification.

In the following description of the present invention, if it is determined that a detailed description of a related well-known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings.

A term for identifying an access node used in the following description, a term referring to network entities, a term referring to messages, a term referring to an interface between network objects, a term referring to various identification information and the like are exemplified for convenience of description. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

For convenience of description, the present invention uses terms and names defined in the 3GPP LTE (3rd Generation Partnership Project Long Term Evolution) standard. However, the present invention is not limited by the terms and names, and may be equally applied to systems conforming to other standards. In the present invention, eNB may be used interchangeably with gNB for convenience of description. That is, a base station described as an eNB may represent a gNB.

In the present invention, bearer may mean including SRB and DRB, SRB means Signaling Radio Bearer, and DRB means Data Radio Bearer. The SRB is mainly used to transmit and receive RRC messages of the RRC layer device, and the DRB is mainly used to transmit and receive user layer data. In addition, UM DRB means a DRB using an RLC layer device operating in UM (Unacknowledged Mode) mode, and AM DRB means a DRB using an RLC layer device operating in AM (Acknowledged Mode) mode.

The present invention proposes various data processing methods for improving data processing speed when a base station and a terminal perform data processing at a high data rate in a next-generation mobile communication system.

Among the data processing procedures performed when the terminal or the base station transmits or receives data, the procedure that consumes the most processing load or time is an encryption procedure (ciphering), a decryption procedure (deciphering), and integrity protection of the PDCP layer device. Procedure (integrity protection), integrity verification procedure (Integrity verification), or ARQ (Autonomous Repeat Request) procedure in the RLC layer device.

The above procedures are procedures performed in the RLC layer device or the PDCP layer device configured for each bearer, and when the UE establishes a connection with the network, the base station transmits an RRC message (eg, an RRCReconfiguration message or an RRCSetup message or an RRCResume message) to the UE. , whether or not to use the encryption procedure (or decryption procedure), integrity protection procedure (or integrity verification procedure), or ARQ procedure (eg RLC AM mode set) for each bearer (eg SRB or DRB), respectively You can set whether or not to do it as an indicator.

Therefore, if an encryption procedure (or decryption procedure) is established for a bearer and an integrity protection procedure (or integrity verification procedure) is not configured, the UE or the base station performs the integrity protection procedure (or integrity verification procedure) for the bearer. Without it, an encryption procedure (or a decryption procedure) may be performed.

In addition, if an encryption procedure (or decryption procedure) is not established for a bearer and an integrity protection procedure (or integrity verification procedure) is established, the terminal or base station performs the integrity protection procedure (or integrity verification procedure) for the bearer and , the encryption procedure (or decryption procedure) may not be performed.

In addition, when an encryption procedure (or decryption procedure) is set for a bearer and an integrity protection procedure (or integrity verification procedure) is also set, the terminal or base station performs an integrity protection procedure (or integrity verification procedure) for the bearer, Then, an encryption procedure (or a decryption procedure) may be performed.

In the above, since the PDCP layer device performs an encryption procedure (or decryption procedure) or an integrity protection procedure (or integrity verification procedure) once for each data received from a higher layer device, the more data it receives, the more the encryption procedure (or decryption procedure) procedure) or integrity protection procedure (or integrity verification procedure) must be performed a lot, which increases data processing complexity and increases data processing time. In addition, since the RLC layer device allocates an RLC serial number to each data received from a higher layer device (eg, a PDCP layer device), the more data it receives, the more RLC serial numbers are allocated and used. The ARQ procedure that operates based on it becomes very complicated and requires a lot of data processing time.

Therefore, in the present invention, the number or frequency of performing an encryption procedure (or decryption procedure) or integrity protection procedure (or integrity verification procedure) in the PDCP layer device is reduced, and the number of RLC serial numbers allocated and used by the RLC layer device itself is reduced. suggest a way

Since the encryption procedure (or decryption procedure) or the integrity protection procedure (or integrity verification procedure) in the above is a procedure with a large data processing load, it can be processed using a hardware accelerator or hardware engine, in which the encryption procedure ( Alternatively, if the number of times the hardware accelerator is called and used to perform the decryption procedure) or the integrity protection procedure (or integrity verification procedure) is reduced, the number of hardware accelerator calls to process other data (for example, data of other bearers) is increased. Since they can be used in parallel, data processing time can be reduced and data processing speed can be improved.

In addition, if the number of RLC serial numbers allocated for each data is reduced, the time for searching the list with the RLC serial number, data, ACK or NACK indicator in the ARQ procedure of the RLC layer device can be reduced, so the data processing time can be reduced. .

In the present invention, a data concatenation procedure (concatenation) is performed on data (eg, SDAP SDU or PDCP SDU) received from a higher layer device (eg, a PDCP layer device or an SDAP layer device) in a higher layer device (eg, a PDCP layer device or an SDAP layer device) suggest to do

The upper layer device data concatenation procedure proposed in the present invention may have one or a plurality of functions among the following functions. If the upper layer device data concatenation procedure is set at the transmitting end, the receiving end needs to perform a data separation procedure (de-concatenation or separation).

- The data concatenation procedure proposed in the present invention may be configured or performed in an SDAP layer device, a PDCP layer device, or a new layer device, and is an RRC message (eg, RRCReconfiguration message or RRCSetup message or RRCResume message) for each bearer Alternatively, whether to apply the data concatenation procedure may be set as an indicator for each downlink or uplink. When the data concatenation procedure is set in the RRC message, the number of data to be concatenated or the maximum size of concatenated data may be set. In another method, the number of data to be concatenated or the size to be concatenated may be freely determined by the terminal implementation or the base station implementation.

- The terminal supporting the data concatenation procedure proposed in the present invention is the maximum size that can be concatenated with the data concatenation procedure (eg, the maximum size of concatenated data or an encryption procedure (or decryption procedure) at one time) The maximum size to which the integrity protection procedure (or integrity verification procedure) can be applied) or whether the data concatenation procedure is supported may be reported in a UE capability reporting message. In the above, the maximum size that the terminal or base station can concatenate with the data concatenation procedure or the maximum size of concatenated data, or the encryption procedure (or decryption procedure) or the integrity protection procedure (or integrity verification procedure) can be applied at once. The maximum size may be predefined or defined and used in the PDCP layer device. For example, the maximum size (eg, 8192 bytes or 9000 bytes) may be defined in the PDCP layer device related standard.

- It is proposed to introduce new fields to perform the data concatenation procedure or data separation procedure proposed in the present invention. Some of the new fields proposed above may be introduced or defined in the SDAP header or PDCP header, or some of the new fields may be attached or introduced in front of each concatenated data, or some of the new fields may be attached or introduced at the beginning of all concatenated data. In the present invention, the terminal or the base station may apply or perform the data concatenation procedure or the data separation procedure proposed above based on the new fields. The new fields may include one or a plurality of fields among the following fields. The new fields proposed in the present invention may be generated or introduced in the PDCP layer device or SDAP layer device, may be attached and used in the data concatenation procedure, or may be used in the PDCP layer device or SDAP layer device in the data separation procedure It can be used to read and interpret the new fields to separate concatenated data.

■ C field: It can indicate whether data concatenation function is performed or not. Another way is to indicate whether there is data immediately after, new fields, or concatenated data. As another method, it may indicate whether it is the last data.

■ E field: It can indicate whether there is data immediately after, new fields, or concatenated data. As another method, it may indicate whether it is the last data.

■ LI field: The size of each concatenated data can be indicated in bytes, or the size of each data received from or transmitted to the upper layer device for the concatenated data can be indicated in bytes. there is. For example, the first LI field may indicate the size of the first (or first) data among concatenated data in bytes, or the second LI field may indicate the size of the second (or first) data among concatenated data. Then) the size of data can be indicated in bytes. For example, you can introduce an LI field for each data and use it in a data concatenation procedure or a data separation procedure.

For example, each of the LI fields is located in front of each data, {[LI field + data] [LI field + data] ... Data can be concatenated in the same structure as [LI field + data]}. The above structure facilitates data processing speed because data processing can be performed sequentially and quickly using new fields and the processed data can be directly transferred to the upper layer.

Another way is [E field LI field] [E fill LI field]… [E Fill LI Field] [Data + Data + … + data], data may be concatenated. The above structure has the advantage of being able to process new fields at once in the implementation.

As another method, the LI field indicating the size of the last data may be omitted. This is because, assuming that n pieces of data are concatenated, if the n-1 th data is separated by the LI field, the remaining data itself becomes the nth data even if the size of the remaining data is not known.

As another method, in the above, the LI field may indicate the size of concatenated data in bytes. can be specified in units.

As another method, in the above, the LI field may indicate the size of concatenated data in bytes, and if an integrity protection procedure is set, it may indicate the size of data before the integrity protection procedure is applied, and the concatenated data MAC-I field can be added at the end of Taking this into account, data separation procedures can be performed. For example, the LI field for the last data may indicate the length of the last data except for the MAC-I field.

As another method, in the above, the LI field may indicate the size of concatenated data in bytes. can indicate the size of , and a MAC-I field can be added at the end of the concatenated data, and if the header compression procedure or integrity protection procedure is set when the data separation procedure is applied at the receiving end, a predetermined length ( For example, the data separation procedure may be performed considering that there is a MAC-I field having 4 bytes). For example, the LI field for the last data may indicate the length of the compressed last data to which the header compression procedure is applied except for the MAC-I field. In the above, if the LI field indicates only the size of data, data processing can be accelerated by applying the same processing procedure to all data. On the other hand, an indicator indicating whether the MAC-I field exists or an indicator indicating the location of the MAC-I field needs to be newly introduced.

Alternatively, if the LI field in the above can indicate the size of data and the size of the MAC-I field or the total size of the fields (for example, for the last data or the front data or for each data) ), an indicator indicating whether the MAC-I field is present or an indicator indicating the location is not required, so overhead can be reduced.

■ F field: A field indicating the type of length of the LI field introduced or attached for data concatenation or data separation. Whether the LI field is a field with a small length (eg 6 bytes) or a long length (eg 6 bytes) For example, it can indicate whether the field has 14 bytes). The overhead for the LI field can be reduced by introducing the F field.

■ SN field: A field indicating the order of data in concatenated data (eg, a sequence number) can indicate the order of data.

- For the new fields proposed in the present invention, when integrity protection is set in the PDCP layer device for convenience of implementation (for example, the same processing as data can be performed), the integrity protection procedure is applied to the new fields, or When the encryption procedure is applied to the PDCP layer device, the encryption procedure may be applied. In another method, in order for the receiving end to read new fields before the decoding procedure, the new fields proposed in the present invention apply the integrity protection procedure to the new fields when integrity protection is set in the PDCP layer device, or When the encryption procedure is applied to the PDCP layer device, the encryption procedure may not be applied. That is, if the encryption procedure is not applied even when the integrity protection procedure is applied, the receiving end can read the new fields in advance before the decryption procedure.

- The data concatenation procedure proposed in the present invention is characterized in that the transmitting end (terminal or base station) applies or performs the data concatenation procedure to data to which the integrity protection procedure or the encryption procedure is not applied or performed. In another method, the data concatenation procedure proposed in the present invention is characterized in that the data concatenation procedure is applied or performed on data before or before the integrity protection procedure or encryption procedure is applied or performed at the transmitting end (terminal or base station). do. For example, if an integrity protection procedure or encryption procedure has been established, the data concatenation procedure may be performed or applied, and then the integrity protection procedure or encryption procedure may be performed on the concatenated data. This is because the number or frequency of performing the integrity protection procedure or encryption procedure can be minimized and the data processing time can be reduced only when the integrity protection procedure or the encryption procedure is applied to the concatenated data at once. In addition, when applying the integrity protection procedure or encryption procedure to one concatenated data concatenating multiple data in the above, the integrity protection procedure or encryption procedure is performed on a plurality of concatenated data at once using a single COUNT value. , it enables single processing with one set of security key values (such as a COUNT value or bearer identifier or security key) and shortens the data processing time. For example, if a plurality of data is not concatenated in the above, data processing time is reduced because integrity protection or encryption procedures must be performed multiple times based on different sets of security key values using a different COUNT value for each data. need a lot In addition, when the integrity protection procedure is applied in the above, one MAC-I field can be added after concatenated data, but when the concatenated procedure is not applied, each MAC-I field must be added after each data. Processing is also complex and can increase overhead. Also, when applying or performing the data concatenation procedure to the data, the data concatenation procedure may be applied in the order received from the upper layer device, or the data may be concatenated in order from the beginning of the concatenation procedure. This is because, when the data concatenation procedure is performed, the data can be sequentially transferred to the upper layer device when the data concatenated at the receiving end is separated only by concatenating the data from the front in order. For example, data concatenated to concatenated data to which one PDCP serial number is assigned are in the order of data first received from a higher layer device from the front.

- The data separation procedure proposed in the present invention is characterized in that a data separation procedure is applied or performed on concatenated data to which a decoding procedure or an integrity verification procedure has been applied or performed at the receiving end (terminal or base station). In another method, the data separation procedure proposed in the present invention applies or performs a data separation procedure on concatenated data after or after applying a decoding procedure or an integrity verification procedure at the receiving end (terminal or base station), characterized in that do. For example, if an encryption procedure or an integrity verification procedure is set, a decryption procedure may be performed on the received concatenated data, or a data separation procedure may be performed on the concatenated data after the integrity verification procedure is performed. This is because the number or frequency of performing the decryption procedure or the integrity verification procedure can be minimized and the data processing time can be reduced only when the decryption procedure or the integrity verification procedure is applied to the concatenated data at once. In addition, when the decryption procedure or integrity protection procedure is applied to one concatenated data concatenated with multiple data in the above, the decryption procedure or integrity protection procedure is performed once for a plurality of concatenated data using a single COUNT value. By doing so, it is possible to enable single processing with one set of security key values (such as a COUNT value or a bearer identifier or security key) and shorten the data processing time. For example, if the data is not concatenated above, the data processing time is very long because the decryption procedure or the integrity protection procedure must be performed multiple times based on different sets of security key values using a different COUNT value for each data. need. In addition, when applying or performing the data separation procedure to the concatenated data in the above, the data may be sequentially separated from the front part of the concatenated data, the data may be processed sequentially from the front part, and transmitted to the upper layer device. For example, data concatenated to concatenated data to which one PDCP serial number is assigned must first be delivered to a higher layer device from the front.

- If the data concatenation procedure proposed above is configured or performed in the SDAP layer device, the SDAP layer device may not apply the data concatenation procedure to SDAP control data (SDAP control PDU). Because the encryption procedure or decryption procedure is not applied to SDAP control data, when the SDAP control data is concatenated with other data (eg SDAP data SDU or SDAP data PDU), the concatenated data is encrypted or the decryption procedure is performed. This is because it can increase the implementation complexity when performing. In the above, when the SDAP layer device performs a data concatenation function, data only for data (eg, SDAP data SDU or SDAP data PDU) of a higher layer device corresponding to QoS flow IDs (QoS identifiers) mapped to each bearer A concatenation procedure may be performed, and concatenated data may be delivered to the PDCP layer device of the bearer. As another method, when performing the data concatenation function in the SDAP layer device and performing the data concatenation procedure on the data of the upper layer device corresponding to QoS flow IDs (QoS identifiers) mapped to each bearer, specifically The data concatenation procedure may be applied only to data corresponding to the same QoS flow ID (QoS identifier), and the concatenated data may be delivered to the PDCP layer device of the bearer. In the above, when an integrity protection procedure is set for SDAP control data, the integrity protection procedure may be applied, or when an encryption procedure is set, the encryption procedure may not be applied. As another method, as in FIG. 13, which will be described later, if the SDAP layer device has a data concatenation structure such as 1m-10 or 1m-15 when performing a data concatenation procedure, the SDAP control data can be quickly processed by the receiving end. Control data may be placed at the beginning of the header of new fields for data concatenation. As another method, when performing a data concatenation procedure in the SDAP layer device as shown in FIG. 13 to be described later as another method, if it has a data concatenation structure such as 1m-10 or 1m-15, dynamically generated SDAP control data is added. To make it easier, you may place them at the end of the header of the new fields for data concatenation.

- If the data concatenation procedure proposed above is set or performed in the SDAP layer device, the data concatenation procedure proposed in the present invention is not applied to the header compression procedure, integrity protection procedure, or encryption procedure at the transmitting end (terminal or base station) or It is characterized in that the data concatenation procedure is applied or performed on the data that has not been performed. As another method, in the data concatenation procedure proposed in the present invention, the data concatenation procedure is applied or characterized by performing. Accordingly, the length field (eg, the LI field) among the new fields generated in the data concatenation procedure may set the length of header uncompressed data as a byte unit value. For example, if a header compression procedure, integrity protection procedure, or encryption procedure is established, the data concatenation procedure may be performed or applied, and then the header compression procedure, integrity protection procedure, or encryption procedure may be performed on the concatenated data. This is because the number or frequency of performing the integrity protection procedure or encryption procedure can be minimized and the data processing time can be reduced only when the integrity protection procedure or the encryption procedure is applied to the concatenated data at once. In addition, when the integrity protection procedure or encryption procedure is applied to one concatenated data concatenated with multiple data in the above, the integrity protection procedure or encryption procedure is performed using a single COUNT value to perform one set of security key values (COUNT). value or bearer identifier or security key) to enable single processing and shorten data processing time. For example, if data is not concatenated above, data processing time is required because integrity protection or encryption procedures must be performed multiple times based on a set of different security key values using a different COUNT value for each data. Do. Also, when applying or performing the data concatenation procedure to the data, the data concatenation procedure may be applied in the order received from the upper layer device, or the data may be concatenated in order from the beginning of the concatenation procedure. This is because, when the data concatenation procedure is performed, the data can be sequentially transferred to the upper layer device when the data concatenated at the receiving end is separated only by concatenating the data from the front in order. For example, data concatenated to concatenated data to which one PDCP serial number is assigned are in the order of data first received from a higher layer device from the front.

- If the data concatenation procedure proposed above is set or performed in the SDAP layer device, the data separation procedure proposed in the present invention is a decoding procedure, integrity verification procedure, or header decompression procedure applied or performed at the receiving end (terminal or base station) It is characterized in that the data separation procedure is applied or performed on the concatenated data. As another method, in the data separation procedure proposed in the present invention, the data separation procedure is applied to the data concatenated after or after the decoding procedure, the integrity verification procedure, or the header decompression procedure is applied at the receiving end (terminal or base station). Or characterized in that it is performed. For example, if the header compression procedure, encryption procedure, or integrity verification procedure is set, the received concatenated data is decrypted, or the integrity verification procedure or header decompression procedure is performed, and then the data separation procedure is performed on the concatenated data. can be performed. This is because the number or frequency of performing the decryption procedure or the integrity verification procedure can be minimized and the data processing time can be reduced only when the decryption procedure or the integrity verification procedure is applied to the concatenated data at once. In addition, when a decryption procedure or integrity protection procedure is applied to one concatenated data concatenated with several data in the above, a decryption procedure or integrity protection procedure is performed using a single COUNT value, so that one set of security key values ( COUNT value or bearer identifier or security key) enables single processing and shortens data processing time. For example, if the data is not concatenated above, the data processing time is very long because the decryption procedure or the integrity protection procedure must be performed multiple times based on different sets of security key values using a different COUNT value for each data. need. In addition, when applying or performing the data separation procedure to the concatenated data above, the data is separated in order from the front of the concatenated data, and data processing is sequentially performed from the front and delivered to the upper layer device. . For example, data concatenated to concatenated data to which one PDCP serial number is assigned must first be delivered to a higher layer device from the front.

- If the data concatenation procedure proposed above is configured or performed in the SDAP layer device, the data processing load and implementation complexity can be increased due to the header compression procedure. Therefore, in the above, if the data concatenation procedure or separation procedure is configured for a certain bearer, or for the bearer or higher layer device in which the data concatenation procedure is configured, the header compression procedure (eg, ROHC (Robust header compression), EHC (Ethernet header compression)) ) or data compression procedure (UDC, Uplink data compression) is set to use or add, it may adversely affect the data processing speed. This is because the transmitting end must perform a header compression procedure for each data or the receiving end must perform a header decompression procedure for each data. Therefore, for each bearer or higher layer device (PDCP layer device or SDAP layer device or new layer device), the data concatenation procedure and header compression procedure (eg, ROHC (Robust header compression), EHC (Ethernet header compression)) or data compression You can limit the procedure (UDC, Uplink data compression) not to be set together. For example, if a data concatenation procedure is configured, it may be restricted so that a header compression procedure (eg, robust header compression (ROHC), Ethernet header compression (EHC)) or a data compression procedure (UDC, uplink data compression) cannot be set. As another method, if a header compression procedure (for example, ROHC (Robust header compression), EHC (Ethernet header compression)) or a data compression procedure (UDC, Uplink data compression) is configured, it is possible to restrict the data concatenation procedure to be set. . Alternatively, the encryption procedure or the integrity protection procedure may not be set in order to further accelerate the data rate in the above.

- If the header compression procedure or data compression procedure is not set in order to accelerate data processing in the above, or if the data concatenation procedure proposed above is set or performed in the SDAP layer device, the data concatenation procedure proposed in the present invention is It is characterized in that the data concatenation procedure is applied or performed for data to which the integrity protection procedure or encryption procedure is not applied or performed in the terminal or base station). In another method, the data concatenation procedure proposed in the present invention is characterized in that the data concatenation procedure is applied or performed on data before or before the integrity protection procedure or encryption procedure is applied or performed at the transmitting end (terminal or base station). do. Accordingly, among the new fields generated in the data concatenation procedure, the length field (eg, the LI field) may set the data length as a byte unit value. For example, if an integrity protection procedure or encryption procedure is established, the data concatenation procedure may be performed or applied, and then the integrity protection procedure or encryption procedure may be performed on the concatenated data. This is because the number or frequency of performing the integrity protection procedure or encryption procedure can be minimized and the data processing time can be reduced only when the integrity protection procedure or the encryption procedure is applied to the concatenated data at once. In addition, when the integrity protection procedure or encryption procedure is applied to one concatenated data concatenated with multiple data in the above, the integrity protection procedure or encryption procedure is performed using a single COUNT value to perform one set of security key values (COUNT). value or bearer identifier or security key) to enable single processing and shorten data processing time. For example, if data is not concatenated above, data processing time is required because integrity protection or encryption procedures must be performed multiple times based on a set of different security key values using a different COUNT value for each data. Do. Also, when applying or performing the data concatenation procedure to the data, the data concatenation procedure may be applied in the order received from the upper layer device, or the data may be concatenated in order from the beginning of the concatenation procedure. This is because, when the data concatenation procedure is performed, the data can be sequentially transferred to the upper layer device when the data concatenated at the receiving end is separated only by concatenating the data from the front in order. For example, data concatenated to concatenated data to which one PDCP serial number is assigned are in the order of data first received from a higher layer device from the front.

- If a header compression procedure or data compression procedure is not set in order to accelerate data processing in the above, or if the data concatenation procedure proposed above is set or performed in the SDAP layer device, the data separation procedure proposed in the present invention is performed at the receiving end ( It is characterized in that the data separation procedure is applied or performed on the concatenated data to which the decoding procedure or the integrity verification procedure has been applied or performed in the terminal or the base station). In another method, the data separation procedure proposed in the present invention applies or performs a data separation procedure on concatenated data after or after applying a decoding procedure or an integrity verification procedure at the receiving end (terminal or base station), characterized in that do. For example, if an encryption procedure or an integrity verification procedure is set, a decryption procedure may be performed on the received concatenated data, or a data separation procedure may be performed on the concatenated data after the integrity verification procedure is performed. This is because the number or frequency of performing the decryption procedure or the integrity verification procedure can be minimized and the data processing time can be reduced only when the decryption procedure or the integrity verification procedure is applied to the concatenated data at once. In addition, when a decryption procedure or integrity protection procedure is applied to one concatenated data concatenating multiple data in the above, a decryption procedure or integrity protection procedure is performed using a single COUNT value, so that one set of security key values ( COUNT value or bearer identifier or security key) enables single processing and shortens data processing time. For example, if the data is not concatenated above, the data processing time is very long because the decryption procedure or the integrity protection procedure must be performed multiple times based on different sets of security key values using a different COUNT value for each data. need. In addition, when applying or performing the data separation procedure to the concatenated data in the above, the data may be sequentially separated from the front part of the concatenated data, the data may be processed sequentially from the front part, and transmitted to the upper layer device. For example, data concatenated to concatenated data to which one PDCP serial number is assigned must first be delivered to a higher layer device from the front.

- If the data concatenation procedure proposed above is configured or performed by the PDCP layer device, the PDCP layer device does not apply the data concatenation procedure to SDAP control data (SDAP control PDU) or PDCP control data (PDCP control PDU) can do. Because an encryption procedure or a decryption procedure is not applied to SDAP control data, concatenating the SDAP control data with other data can increase implementation complexity when encrypting or decrypting the concatenated data. . In addition, since an encryption procedure, a decryption procedure, an integrity protection procedure, or an integrity verification procedure are not applied to the PDCP control data, when the PDCP control data is concatenated with other data, the concatenated data is encrypted or decrypted, the integrity protection procedure , or because it may increase the implementation complexity when performing the integrity verification procedure. In the above, when an integrity protection procedure is set for SDAP control data, the integrity protection procedure may be applied, or when an encryption procedure is set, the encryption procedure may not be applied. However, when the integrity protection procedure is set to the PDCP control data in the above, the integrity protection procedure may not be applied, or the encryption procedure may not be applied when the encryption procedure is set. In another method, if the integrity protection procedure is set for SDAP control data above, without applying the integrity protection procedure, or if the encryption procedure is set, the encryption procedure is also may not apply, or may not apply integrity protection (or integrity verification) procedures to SDAP control data or PDCP control data, and may not apply encryption procedures (or decryption procedures) to SDAP control data or PDCP control data. Integrity protection (or integrity verification) procedures may be applied, and encryption procedures (or decryption procedures) may also be applied.

- If the data concatenation procedure proposed above is configured or performed in the PDCP layer device, data processing load and implementation complexity may be increased due to the header compression procedure. Therefore, in the above, if a data concatenation procedure or separation procedure is configured for a certain bearer, or a header compression procedure (eg, ROHC (Robust header compression), EHC (Ethernet header compression) )) or data compression procedure (UDC, Uplink data compression) is set to use or add, it may adversely affect the data processing speed. This is because the transmitting end must perform a header compression procedure for each data or the receiving end must perform a header decompression procedure for each data. Therefore, for each bearer or higher layer device (PDCP layer device or SDAP layer device or new layer device), the data concatenation procedure and header compression procedure (eg, ROHC (Robust header compression), EHC (Ethernet header compression)) or data compression You can limit the procedure (UDC, Uplink data compression) not to be set together. For example, if a data concatenation procedure is configured, it may be restricted so that a header compression procedure (eg, robust header compression (ROHC), Ethernet header compression (EHC)) or a data compression procedure (UDC, uplink data compression) cannot be set. As another method, if a header compression procedure (for example, ROHC (Robust header compression), EHC (Ethernet header compression)) or a data compression procedure (UDC, Uplink data compression) is configured, it is possible to restrict the data concatenation procedure to be set. . Alternatively, the encryption procedure or the integrity protection procedure may not be set in order to further accelerate the data rate in the above.

- If the data concatenation procedure proposed above is set or performed in the PDCP layer device, the data concatenation procedure proposed in the present invention applies or performs the header compression procedure at the transmitting end (terminal or base station), but the integrity protection procedure or encryption procedure is applied It is characterized in that the data concatenation procedure is applied or performed on the data that has not been or has not been performed. In another method, in the data concatenation procedure proposed in the present invention, the header compression procedure is applied or performed at the transmitting end (terminal or base station), but before or before the integrity protection procedure or encryption procedure is applied or performed, the data to which the header compression procedure is applied It is characterized in that the data concatenation procedure is applied or performed for them. Therefore, among the new fields generated in the data concatenation procedure, the length field (eg, LI field) may set the length of data to which the header compression procedure is applied as a byte unit value. For example, if a header compression procedure or integrity protection procedure or encryption procedure is set, the header compression procedure is applied or performed to each data, the data concatenation procedure is performed or applied to multiple data, and then the integrity protection procedure for the concatenated data Alternatively, an encryption procedure may be performed. This is because the number or frequency of performing the integrity protection procedure or encryption procedure can be minimized and the data processing time can be reduced only when the integrity protection procedure or the encryption procedure is applied to the concatenated data at once. On the other hand, since the complexity of applying or performing the header compression procedure to each data of concatenated data is high, it is convenient to concatenate after performing the header compression procedure in advance, and the length field indicating the length of each concatenated data can be reduced to reduce overhead. In addition, when the integrity protection procedure or encryption procedure is applied to one concatenated data concatenated with multiple data in the above, the integrity protection procedure or encryption procedure is performed using a single COUNT value to perform one set of security key values (COUNT). value or bearer identifier or security key) to enable single processing and shorten data processing time. For example, if data is not concatenated above, data processing time is required because integrity protection or encryption procedures must be performed multiple times based on a set of different security key values using a different COUNT value for each data. Do. Also, when applying or performing the data concatenation procedure to the data, the data concatenation procedure may be applied in the order received from the upper layer device, or the data may be concatenated in order from the beginning of the concatenation procedure. This is because, when the data concatenation procedure is performed, the data can be sequentially transferred to the upper layer device when the data concatenated at the receiving end is separated only by concatenating the data from the front in order. For example, data concatenated to concatenated data to which one PDCP serial number is assigned are in the order of data first received from a higher layer device from the front.

- If the data concatenation procedure proposed above is set or performed in the PDCP layer device, the data separation procedure proposed in the present invention is the data concatenated data to which the decoding procedure or integrity verification procedure is applied or performed at the receiving end (terminal or base station) It is characterized in that a data separation procedure is applied or performed, and a header decompression procedure may be applied to each of the separated data. In another method, the data separation procedure proposed in the present invention applies or performs a data separation procedure on concatenated data after or after applying a decoding procedure or an integrity verification procedure at the receiving end (terminal or base station), characterized in that and a header decompression procedure may be applied to each of the above separated data. For example, if a header compression procedure, encryption procedure, or integrity verification procedure is set, a decryption procedure is performed on the received concatenated data or an integrity verification procedure is performed and then a data separation procedure is performed on the concatenated data, and in the above A header decompression procedure can be applied to each separated data. This is because the number or frequency of performing the decryption procedure or the integrity verification procedure can be minimized and the data processing time can be reduced only when the decryption procedure or the integrity verification procedure is applied to the concatenated data at once. On the other hand, since it is complicated to apply or perform the header decompression procedure for each data of the concatenated data, it is easy to implement and perform the header decompression procedure after separating the data later, and the length of each concatenated data It is possible to reduce the length field indicating , thereby reducing overhead. In addition, when a decryption procedure or integrity protection procedure is applied to one concatenated data concatenated with several data in the above, a decryption procedure or integrity protection procedure is performed using a single COUNT value to perform a single set of security key values (COUNT). value or bearer identifier or security key) to enable single processing and shorten data processing time. For example, if the data is not concatenated above, the data processing time is very long because the decryption procedure or the integrity protection procedure must be performed multiple times based on different sets of security key values using a different COUNT value for each data. need. In addition, when applying or performing the data separation procedure to the concatenated data in the above, the data may be sequentially separated from the front part of the concatenated data, the data may be processed sequentially from the front part, and transmitted to the upper layer device. For example, data concatenated to concatenated data to which one PDCP serial number is assigned must first be delivered to a higher layer device from the front.

- If the header compression procedure or data compression procedure is not set in order to accelerate data processing in the above, or if the data concatenation procedure proposed above is configured or performed in the PDCP layer device, the data concatenation procedure proposed in the present invention is or base station) to which the data concatenation procedure is applied or performed to data to which the integrity protection procedure or the encryption procedure is not applied or is not performed. In another method, the data concatenation procedure proposed in the present invention is characterized in that the data concatenation procedure is applied or performed on data before or before the integrity protection procedure or encryption procedure is applied or performed at the transmitting end (terminal or base station). do. Therefore, among the new fields generated in the data concatenation procedure, the length field (eg, LI field) may set the length of data to which the header compression procedure is applied as a byte unit value. For example, if an integrity protection procedure or encryption procedure has been established, the data concatenation procedure may be performed or applied to multiple data, and then the integrity protection procedure or encryption procedure may be performed on the concatenated data. This is because the number or frequency of performing the integrity protection procedure or encryption procedure can be minimized and the data processing time can be reduced only when the integrity protection procedure or the encryption procedure is applied to the concatenated data at once. In addition, when the integrity protection procedure or encryption procedure is applied to one concatenated data concatenated with multiple data in the above, the integrity protection procedure or encryption procedure is performed using a single COUNT value to perform one set of security key values (COUNT). value or bearer identifier or security key) to enable single processing and shorten data processing time. For example, if data is not concatenated above, data processing time is required because integrity protection or encryption procedures must be performed multiple times based on a set of different security key values using a different COUNT value for each data. Do. Also, when applying or performing the data concatenation procedure to the data, the data concatenation procedure may be applied in the order received from the upper layer device, or the data may be concatenated in order from the beginning of the concatenation procedure. This is because, when the data concatenation procedure is performed, the data can be sequentially transferred to the upper layer device when the data concatenated at the receiving end is separated only by concatenating the data from the front in order. For example, data concatenated to concatenated data to which one PDCP serial number is assigned are in the order of data first received from a higher layer device from the front.

- If the header compression procedure or data compression procedure is not set in order to accelerate data processing in the above, or if the data concatenation procedure proposed above is configured or performed in the PDCP layer device, the data separation procedure proposed in the present invention is Alternatively, it may be characterized in that the data separation procedure is applied or performed on the concatenated data to which the decoding procedure or the integrity verification procedure has been applied or performed in the base station). In another method, the data separation procedure proposed in the present invention applies or performs a data separation procedure on concatenated data after or after applying a decoding procedure or an integrity verification procedure at the receiving end (terminal or base station), characterized in that can do. For example, if an encryption procedure or an integrity verification procedure is set, a decryption procedure may be performed on the received concatenated data, or a data separation procedure may be performed on the concatenated data after the integrity verification procedure is performed. This is because the number or frequency of performing the decryption procedure or the integrity verification procedure can be minimized and the data processing time can be reduced only when the decryption procedure or the integrity verification procedure is applied to the concatenated data at once. In addition, when a decryption procedure or integrity protection procedure is applied to one concatenated data concatenating multiple data in the above, a decryption procedure or integrity protection procedure is performed using a single COUNT value, so that one set of security key values ( COUNT value or bearer identifier or security key) enables single processing and shortens data processing time. For example, if the data is not concatenated above, the data processing time is very long because the decryption procedure or the integrity protection procedure must be performed multiple times based on different sets of security key values using a different COUNT value for each data. need. In addition, when applying or performing the data separation procedure to the concatenated data in the above, the data may be sequentially separated from the front part of the concatenated data, the data may be processed sequentially from the front part, and transmitted to the upper layer device. For example, data concatenated to concatenated data to which one PDCP serial number is assigned must first be delivered to a higher layer device from the front.

- In the above, the data concatenation procedure or separation procedure may be established for any bearer or higher layer device. If the data concatenation procedure is not configured, the transmitting PDCP layer device may allocate one PDCP serial number (or COUNT value) to one data (eg, PDCP SDU or PDCP PDU) received from a higher layer device, and , one PDCP serial number (for example, a value obtained by modulating the value of the variable storing the COUNT value by the total size of the PDCP serial number, or the transmission variable (COUNT value) modulo 2^ (length of the PDCP serial number for uplink)) , increment a variable for assigning a serial number by 1, and then assign a serial number incremented by 1 to the variable for the next data. However, if the data concatenation procedure is set in the above, when the transmitting PDCP layer device applies the data concatenation procedure to data received from the higher layer device, one PDCP serial number (or COUNT) for a plurality of concatenated data value), assigning one PDCP serial number and incrementing the variable for serial number assignment by 1 and incrementing the variable by 1 for the next data (concatenated or unconcatenated data). A number can be assigned, and when the data concatenation procedure is not applied to the data received from the upper layer device, one PDCP serial number can be assigned to one unconcatenated data, and one PDCP serial number can be assigned. It is possible to assign a number, increment a variable for serial number assignment by one, and assign a serial number incremented by one to the next data (concatenated data or non-concatenated data) as the variable. If the data concatenation procedure is performed in the SDAP layer device above, PDCP data processing (for example, header compression procedure or integrity protection procedure or encryption procedure) is performed for one PDCP SDU (or SDAP data PDU) concatenated with a plurality of SDAP SDUs. , generates a PDCP header, and generates and allocates one PDCP serial number for the PDCP data PDU. If the data concatenation procedure is performed in the PDCP layer device in the above, a plurality of PDCP SDUs (eg, a compressed PDCP SDU to which a header compression procedure is applied when a header compression procedure is set) is concatenated, and one concatenated PDCP SDUs PDCP data processing (for example, integrity protection procedure or encryption procedure) may be performed for the PDCP header, a PDCP header may be generated, and one PDCP serial number may be generated and assigned to the PDCP data PDU.

- In the above, if a data concatenation procedure or separation procedure is configured for a certain bearer, or an SDAP header or header compression procedure (eg, ROHC (Robust header compression), EHC (Ethernet) If it is set to use or add header compression) or data compression procedure (UDC, Uplink data compression), data processing speed may be adversely affected. This is because the transmitting end must add an SDAP header to each data or perform header compression, or the receiving end must remove the SDAP header for each data or decompress the header. Therefore, it may be restricted not to set the data concatenation procedure and the SDAP header or header compression procedure or data compression procedure together for each bearer or higher layer device (PDCP layer device or SDAP layer device or new layer device). For example, if the data concatenation procedure is set, it may be restricted so that the SDAP header or header compression procedure or data compression procedure cannot be set. As another method, if the SDAP header or header compression procedure or data compression procedure is set, it may be restricted so that the data concatenation procedure cannot be set.

- The data concatenation procedure proposed in the present invention may be activated or deactivated, or stopped or resumed according to an indication of an RRC message, MAC control information, or PDCCH.

- If the data concatenation procedure or data separation procedure is set for the PDCP layer device in the above, the UE may perform the data concatenation function in the higher layer device, and in the above, if the UE indicates a handover RRC message (RRCReconfiguration) If receiving from the base station or if ReconfigurationWithSync (handover indicator) is included in the RRC message, or if the RRC message includes an indicator (reestablishPDCP) for reestablishing PDCP layer device (PDCP re-establishment), or the RRC message If security configuration information (security config) for changing the security key is included, the terminal may derive a new security key from the RRC layer device based on the security configuration information and apply the security key to each PDCP layer device. In addition, the UE may perform a PDCP re-establishment procedure in the PDCP layer device. When the UE performs the PDCP re-establishment procedure in the above, based on the new security key, the data to be retransmitted for AM DRB or data to be transmitted may be newly applied and transmitted with the data processing procedure of the PDCP layer device. For example, specifically, in the PDCP re-establishment procedure, the UE may apply the data processing procedure of the PDCP layer device to retransmitted data and newly transmitted data as follows.

■ When re-applying the data processing procedure (header compression procedure, integrity protection procedure, or encryption procedure) of the PDCP layer device to the data to be retransmitted in the PDCP re-establishment procedure based on the new security key, the terminal sets the data concatenation procedure If the data concatenation procedure has been performed on previously transmitted data, when newly composing data to be retransmitted, if the header compression procedure has been set, the header compression procedure is newly performed again, or data concatenated during transmission If the data concatenation procedure is performed again in the same manner as in An encryption procedure may be performed on the concatenated data based on a new security key. For example, in the transmitting PDCP layer device, the first data and the second data are configured as PDCP serial number No. 1 and transmitted, and the third data is configured as No. 2 and transmitted. If successful delivery is not confirmed from the lower layer device for No. 2, a retransmission procedure (transfer to the lower layer device) is performed in the PDCP re-establishment procedure. In the above, it can be assumed that the receiving end has actually received data corresponding to PDCP serial number 1 and has not received data corresponding to PDCP serial number 2. However, if, in the retransmission procedure of the PDCP re-establishment procedure, the first data, the second data, and the third data are concatenated and transmitted as PDCP serial number 1, the receiving end receives the PDCP serial number 1 Since the data has already been received before, the data can be detected as duplicate received data and discarded. That is, data loss may occur because the third data is concatenated with the PDCP serial number 1 by concatenating the data retransmitted in the PDCP re-establishment procedure in the above, and differently from before, the concatenation function is newly concatenated. Therefore, when the procedure of the PDCP layer device is newly applied with the new security key to the data retransmitted by the PDCP re-establishment procedure in the above, the data concatenation function is concatenated in the same way as the previously transmitted data, and the PDCP layer based on the new security key The procedure of the device shall be applied anew.

■ When applying the data processing procedure (header compression procedure, integrity protection procedure, or encryption procedure) of the PDCP layer device to the data to be newly transmitted in the PDCP re-establishment procedure based on the new security key, if the data concatenation procedure is set When composing data to be transmitted, if a header compression procedure is set, a header compression procedure is performed, or a data concatenation procedure (data may or may not be concatenated) is performed, or concatenated data or If the integrity protection procedure is set for the unconcatenated data, the integrity protection procedure is newly performed based on the new security key for the concatenated or unconcatenated data, or if the encryption procedure is set, the concatenated data or the unconcatenated data An encryption procedure can be performed based on the new security key for data that has not been transmitted, and a transmission procedure (delivered to a lower layer device) is performed.

1 is a diagram showing the structure of an LTE system to which the present invention can be applied.

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

In FIG. 1 , ENBs 1a-05 to 1a-20 correspond to the existing Node Bs of the UMTS system. ENB is connected to the UE (1a-35) through a radio channel and performs a more complex role than the existing Node B. In the LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) through the Internet protocol, are serviced through a shared channel, so status information such as buffer status, available transmission power status, and channel status of UEs A device for scheduling is required, and the ENB (1a-05 ~ 1a-20) is responsible for this. One ENB typically controls multiple cells. For example, in order to implement a transmission rate of 100 Mbps, the LTE system uses, for example, orthogonal frequency division multiplexing (OFDM) in a 20 MHz bandwidth as a radio access technology. In addition, an Adaptive Modulation & Coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel state of the terminal is applied. The S-GW (1a-30) is a device that provides a data bearer, and creates or removes a data bearer under the control of the MME (1a-25). The MME is a device in charge of various control functions as well as the mobility management function for the UE, and is connected to a number of base stations.

2 is a diagram illustrating a radio protocol structure in an LTE system to which the present invention can be applied.

2, the radio protocol of the LTE system is PDCP (Packet Data Convergence Protocol 1b-05, 1b-40), RLC (Radio Link Control 1b-10, 1b-35), MAC (Medium Access) in the UE and ENB, respectively. Control 1b-15, 1b-30). The Packet Data Convergence Protocol (PDCP) (1b-05, 1b-40) is in charge of IP header compression/restore operations. The main functions of PDCP are summarized below.

- 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

- Order reordering function (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 (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

- Ciphering and deciphering

- Timer-based SDU discard in uplink.

The radio link control (hereinafter referred to as RLC) 1b-10, 1b-35 performs ARQ operation by reconfiguring a PDCP protocol data unit (PDU) or RLC service data unit (SDU) to an appropriate size. . The main functions of RLC are summarized below.

- Data transfer function (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)

- Protocol 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)

The MACs 1b-15 and 1b-30 are connected to several RLC layer devices configured in one terminal, and perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC are summarized below.

- Mapping function (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 (Scheduling information reporting)

- HARQ function (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification

- Transport format selection

- Padding function

The physical layer (1b-20, 1b-25) channel-codes and modulates upper layer data, makes OFDM symbols and transmits them over a radio channel, or demodulates and channel-decodes OFDM symbols received through the radio channel and transmits them to higher layers do the action

3 is a diagram illustrating the structure of a next-generation mobile communication system to which the present invention can be applied.

3, as shown, the radio access network of the next-generation mobile communication system (hereinafter NR or 5G) includes a next-generation base station (New Radio Node B, hereinafter, NR gNB or NR base station) 1c-10 and NR CN 1c -05, New Radio Core Network). A user terminal (New Radio User Equipment, hereinafter NR UE or terminal) 1c-15 accesses an external network through NR gNB 1c-10 and NR CN 1c-05.

In FIG. 3 , the NR gNB 1c-10 corresponds to an Evolved Node B (eNB) of the existing LTE system. The NR gNB is connected to the NR UE 1c-15 through a radio channel and can provide a service superior to that of the existing Node B. In the next-generation mobile communication system, since all user traffic is serviced through a shared channel, a device for scheduling by collecting status information such as buffer status, available transmission power status, and channel status of UEs is required. (1c-10) is in charge. One NR gNB typically controls multiple cells. In order to implement ultra-high-speed data transmission compared to current LTE, it can have more than the existing maximum bandwidth, and additional beamforming technology can be grafted using Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as a radio access technology. . In addition, an Adaptive Modulation & Coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel state of the terminal is applied. The NR CN (1c-05) performs functions such as mobility support, bearer setup, QoS setup, and the like. NR CN is a device in charge of various control functions as well as mobility management functions for the terminal and is connected to a number of base stations. In addition, the next-generation mobile communication system can be linked with the existing LTE system, and the NR CN is connected to the MME (1c-25) through a network interface. The MME is connected to the existing base station eNB (1c-30).

4 is a diagram illustrating a radio protocol structure of a next-generation mobile communication system to which the present invention can be applied.

4, the radio protocol of the next-generation mobile communication system is NR SDAP (1d-01, 1d-45), NR PDCP (1d-05, 1d-40), and NR RLC (1d-10) in the terminal and the NR base station, respectively. , 1d-35), and NR MAC (1d-15, 1d-30).

The main functions of the NR SDAPs 1d-01 and 1d-45 may include some of the following functions.

- Transfer of user plane data

- Mapping between a QoS flow and a DRB for both DL and UL for uplink and downlink

- Marking QoS flow ID in both DL and UL packets for uplink and downlink

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

With respect to the SDAP layer device, the UE can receive a configuration of whether to use the SDAP layer device header or the function of the SDAP layer device for each PDCP layer device, for each bearer, or for each logical channel in an RRC message, and the SDAP header If is set, the UE uses the uplink and downlink QoS flow and data bearer mapping information with the NAS QoS reflection setting 1-bit indicator (NAS reflective QoS) and the AS QoS reflection setting 1-bit indicator (AS reflective QoS) of the SDAP header. can be instructed to update or reset The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used as data processing priority and scheduling information to support a smooth service.

The main function of NR PDCP (1d-05, 1d-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

- Timer-based SDU discard in uplink.

In the above, the reordering function of the NR PDCP device refers to a function of reordering PDCP PDUs received from a lower layer in order based on a PDCP sequence number (SN), and a function of delivering data to the upper layer in the reordered order may include, or may include a function of directly delivering without considering the order, may include a function of reordering the order to record the lost PDCP PDUs, and report the status of the lost PDCP PDUs It may include a function for the transmitting side, and may include a function for requesting retransmission for lost PDCP PDUs.

The main function of the NR RLC (1d-10, 1d-35) may include some of the following functions.

- Data transfer function (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

- Protocol error detection

- RLC SDU discard function (RLC SDU discard)

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

In the above, in-sequence delivery of the NR RLC device refers to a function of sequentially delivering RLC SDUs received from a lower layer to an upper layer, and one RLC SDU is originally divided into several RLC SDUs and received , it may include a function of reassembling it and delivering it, and may include a function of rearranging the received RLC PDUs based on an RLC sequence number (SN) or PDCP SN (sequence number), and rearranging the order It may include a function of recording the lost RLC PDUs, a function of reporting a status on the lost RLC PDUs to the transmitting side, and a function of requesting retransmission of the lost RLC PDUs. and, if there is a lost RLC SDU, it may include a function of sequentially delivering only RLC SDUs before the lost RLC SDU to the upper layer, or even if there is a lost RLC SDU, if a predetermined timer has expired It may include a function of sequentially delivering all RLC SDUs received before the start of , or if a predetermined timer expires even if there are lost RLC SDUs, all RLC SDUs received so far are sequentially transferred to the upper layer. It may include a function to transmit. In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival, regardless of the sequence number and sequence number) and delivered to the PDCP device out of sequence (out-of sequence delivery). Segments stored in the buffer or to be received later are received, reconstructed into one complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and the function may be performed by the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

In the above, the out-of-sequence delivery function of the NR RLC device refers to a function of directly delivering RLC SDUs received from a lower layer to a higher layer regardless of order, and one RLC SDU originally has several RLCs. When received after being divided into SDUs, it may include a function of reassembling and transmitting it, and may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs, arranging the order, and recording the lost RLC PDUs. can

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

- Mapping function (Mapping between logical channels and transport channels)

- Multiplexing/demultiplexing of MAC SDUs

- Scheduling information reporting function (Scheduling information reporting)

- HARQ function (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification

- Transport format selection

- Padding function (Padding)

The NR PHY layer (1d-20, 1d-25) channel-codes and modulates the upper layer data, makes an OFDM symbol and transmits it to the radio channel, or demodulates and channel-decodes the OFDM symbol received through the radio channel to the upper layer. You can perform a forwarding action.

5 shows a procedure for a terminal to switch from an RRC idle mode to an RRC connected mode in the next-generation mobile communication system of the present invention, and proposes a method for setting a protocol layer device or functions of the terminal is a drawing that

One cell provided by the base station can service a very wide frequency band. First, the UE may search the entire frequency band provided by the operator (PLMN) in units of a certain resource block (eg, in units of 12 RBs). That is, the UE may start searching for a Primary Synchronization Sequence (PSS)/Secondary Synchronization Sequence (SSS) in the entire system bandwidth in units of the resource blocks. If the signals are detected while searching for PSS/SSS in units of the resource blocks, the boundaries between a subframe and a radio transmission resource frame can be identified by reading and analyzing (decoding) the signals. In the above, when the synchronization is completed, the terminal may read system information of the cell currently camped on. That is, you can check the MIB (Master system information block) or MSI (Minimum system information) to check the information of the CORESEST (Control Resource Set) and read the system information to check the Initial Bandwidth Part (BWP) information. (1e-01, 1e-05). In the above, the CORESET information refers to a location of a time/frequency transmission resource through which a control signal is transmitted from a base station, and, for example, indicates a resource location through which a PDCCH channel is transmitted.

As described above, when the terminal completes synchronization of the downlink signal with the base station and can receive a control signal, the terminal performs a random access procedure in the initial partial bandwidth, receives a random access response, requests RRC connection establishment, and , RRC connection establishment may be performed by receiving the RRC message (1e-10, 1e-15, 1e-20, 1e-25, 1e-30).

When the basic RRC connection establishment is completed in the above, the base station may send an RRC message inquiring about the capability of the terminal to the terminal in order to check the capability of the terminal (UECapabilityEnquiry, 1e-35). In another method, the base station may ask the MME or AMF for the capability of the terminal in order to check the capability of the terminal. This is because the MME or AMF may have stored the capability information of the terminal if it has previously accessed the terminal.

In the above, the UE performs a UE capability report procedure among the following information in an RRC message (eg, NAS (Non Access Stratum) message or AS (Access Stratum) message) for reporting the UE capability. It may include some or a plurality of pieces of information.

- Whether the terminal supports the data connection function or the data separation function of the upper layer device

- The maximum size that the terminal supports the data concatenation function or data separation function of the upper layer device (for example, the maximum size of concatenated data or the total maximum size of data concatenating a plurality of data)

- The maximum number of concatenable data when the terminal supports the data concatenation function or data separation function of the upper layer device

- Whether to support integrity protection procedures (or functions) per bearer

- Whether the integrity protection procedure is supported for DRB

- If the integrity protection procedure is supported for DRB, the integrity protection procedure is applied at any data transmission rate regardless of the maximum data transmission rate (eg 64kbps or full rate) or data rate supported when the integrity protection procedure is applied. Whether to support

- Information on the functions supported by the terminal

- Release information supported by the terminal, for example, Rel-15, Rel-16, or Rel-17. For example, if the base station or network supports only Rel-15, when supporting the integrity protection procedure for DRB, it can be considered to support only the data rate of 64 kbps, or the terminal's capability report message (for example, NAS (Non Access Stratum (NAS)) ) message or AS (Access Stratum) message), you can also check the integrity protection procedure function for the DRB. As another method, if the UE supports Rel-15 or Rel-16, when supporting the integrity protection procedure for DRB, the base station or network may always consider that it supports it regardless of the data rate, or the UE's capability report message (e.g., For example, you can check the integrity protection procedure function for DRB through NAS (Non Access Stratum) message or AS (Access Stratum) message).

- Whether the terminal supports the deactivation (disabled or deactivation) or activation (enabled or activation) of the data segmentation function (segmentation) (eg, the data segmentation function in the RLC layer device), or RLC UM mode or RLC AM mode Whether to support the deactivation (disabled or deactivation) or activation (enabled or activation) of the data segmentation function for

- Whether the terminal supports a new data segmentation method (eg, SI (segmentation information) based data segmentation method), or the new data segmentation method (eg, SI (segmentation information) for RLC UM mode or RLC AM mode) information) based data partitioning method)

- Whether the UE supports the bitmap-based RLC status report or whether the bitmap-based RLC status report is supported for the RLC AM mode

When receiving the terminal capability report message from the terminal in the above, the base station or the network configures the data concatenation function or the integrity protection function to the terminal in an RRC message (for example, an RRCReconfiguration message or an RRCSetup message or an RRCResume message) for each bearer or each layer device. there is.

If there is no terminal capability information desired by the base station, the base station may request terminal capability from the terminal.

The reason that the base station sends the RRC message to the terminal to check the terminal's performance is to check the terminal's performance, for example, how much frequency band the terminal can read or the area of the frequency band that the terminal can read or It is possible to determine whether a certain function is supported by the terminal and how. And after confirming the performance of the terminal, it is possible to set an appropriate partial bandwidth (BWP) or appropriate functions to the terminal. When the terminal receives the RRC message inquiring about the capability of the terminal, in response to this, the terminal may transmit to the base station including terminal capability information on the functions supported by the terminal (1e-40).

In the above, the UE transmits bearer configuration information or cell group configuration information or cell configuration information or each layer device information (eg For example, an SDAP layer device or a PDCP layer device or an RLC layer device or a MAC layer device or a PHY layer device) may be configured, and the RRC message may include configuration information for a PCell or Pscell or a plurality of cells. A plurality of partial bandwidths may be configured for each cell (PCell or Pscell or Scell). In the above, when the terminal receives the RRCReconfiguration message in which the configuration information of the terminal is received, the configuration information is applied to the bearer or layer device of the terminal, and the RRCReconfigurationComplete message (1e-50, 1e-75) indicating that the reconfiguration is completed is configured to the base station. can be transmitted

In addition, when the base station or network instructs the terminal to handover to another cell or frequency, a handover message (RRCReconfiguration message (1e-85)) including configuration information of the target base station for handover can be configured and transmitted to the terminal. , the terminal performs a handover procedure (eg, a random access procedure to a target base station or a synchronization procedure, etc.) according to the handover setting, and when the handover is successfully performed, configures an RRCReconfigurationComplete message (1e-90) to the target can be transmitted to the base station. The target base station configuration information includes bearer configuration information or cell group configuration information or cell configuration information or each layer device information (eg, SDAP layer device or PDCP layer device or RLC layer device or MAC layer device or PHY layer device). can

In the above, also in the RRC message (RRCSetup message or RRCResume message (1e-25) or RRCReconfiguration message (1e-70, 1e-80)), bearer configuration information or cell group configuration information or cell configuration information of the terminal or each layer device information (For example, an SDAP layer device or a PDCP layer device or an RLC layer device or a MAC layer device or a PHY layer device) may be configured, and the following information may be included.

- An indicator indicating whether to configure the data concatenation function or data separation function of a higher layer device (eg, a PDCP layer device or an SDAP layer device) for each bearer or each layer device for the uplink or the downlink

- The maximum size or threshold to be concatenated when the data concatenation function or data separation function of the upper layer device is set for downlink or uplink (for example, the maximum size of concatenated data or total maximum size of data)

- The maximum number that can be concatenated when the data connection function or data separation function of the upper layer device is set for the downlink or the uplink.

- An indicator indicating whether to set the integrity protection procedure (or function) for each bearer or layer device (eg, PDCP layer device) for downlink or uplink

- An indicator indicating whether to set the integrity protection procedure for the DRB for each bearer or for each layer device (eg, PDCP layer device) for the downlink or uplink

- For downlink or uplink, or for each bearer, or for each layer device (eg, RLC layer device), or for each RLC UM mode or RLC AM mode, whether the UE uses the data segmentation function (segmentation), or Prefect or configuration information indicating whether to disable, or disable (or deactivation) or enable (enabled or activation).

- For downlink or uplink, for each bearer or for each layer device (for example, RLC layer device), or for each RLC UM mode or RLC AM mode method) or not, or an indicator or setting information indicating whether to use an SI-based data partitioning method or an SO-based data partitioning method

- For downlink or uplink, or per bearer or per layer device (eg, RLC layer device), or per RLC AM mode, whether the UE uses or uses a bitmap-based RLC status report Indicators or setting information indicating whether or not to

6 is a diagram showing the structure of a protocol layer device proposed in the present invention.

In FIG. 6 , when the terminal receives the RRC message from the base station as in FIG. 5 , the terminal receives connection establishment information or bearer configuration information or protocol layer device information, and may establish and configure protocol layer devices as shown in 1f-05. For example, one PHY layer device and a MAC layer device may be established, and a plurality of bearers may be established and connected to the MAC layer device to be configured. The bearers may consist of an RLC layer device or a PDCP layer device.

7A, 7B, and 7C show data received from a higher layer device in the next-generation mobile communication system of the present invention is processed by each protocol layer device of a bearer and data is transmitted, or data is received from a lower layer device to receive data represents the procedure for processing by each protocol layer device of the bearer and forwarding it to a higher layer device.

As shown in Figure 7a, if the encryption procedure or security key setting information is set in the PDCP layer device, the terminal derives the security keys from the RRC layer device and applies the security key when establishing or re-establishing the PDCP layer device to perform the encryption procedure. can be done As in 1g-05, when the PDCP layer device receives data (eg, PDCP SDU) from a higher layer device, when a header compression procedure is set with an RRC message or an encryption procedure is set as shown in FIG. 5, the data is A header compression procedure is performed or an encryption procedure is performed on the data, a PDCP serial number is assigned, and a PDCP header is configured to transmit the data as a PDCP PDU to a lower layer device. The data (PDCP PDU) may be transmitted to the MAC layer device by setting the RLC serial number and header field values in the RLC layer device, attaching an RLC header, and transmitting the data to the MAC layer device, the MAC layer device setting the length of the data, the length field and the A MAC header field value such as a logical channel identifier corresponding to data may be set, and a MAC header may be attached and transmitted to a lower layer device. The RLC layer device may perform a data partitioning procedure if necessary or when uplink transmission resources are insufficient, and may update field values of the RLC header or set partition information.

In 1g-10, when the terminal receives data from the lower layer device, it reads the MAC header and checks the length field to separate the data or checks the logical channel identifier and demultiplexes the data to the corresponding RLC layer device and delivers it can do it In the above, when the RLC layer device receives the data, it reads the RLC header and can check whether it is split, and for unpartitioned data, it can remove the RLC header and deliver data to the PDCP layer device, and the divided data is a buffer When all the divided data for the RLC serial number corresponding to the stored data and the divided data are received, complete data is reassembled and the reassembled data can be transmitted to the PDCP layer device. In the above, when an encryption procedure is set, the PDCP layer device performs a decryption procedure, and if the decrypted data is arranged in the order of a PDCP serial number or COUNT value, or when a header compression procedure is set, header compression is decompressed for the data A procedure may be applied, and the data may be delivered to the upper layer device in an ascending order of the COUNT value. If the header compression procedure is not set in the above, the header compression procedure or the header decompression procedure may be omitted.

7B, when a header compression procedure, integrity protection procedure, or encryption procedure is set in the PDCP layer device as in 1g-20, the transmitting PDCP layer device applies a header compression procedure to higher layer device data, and header compression Integrity protection procedure is performed on the data or PDCP header, a 4-byte MAC-I field is attached to the back, and an encryption procedure can be applied to the data and MAC-I field to which the integrity protection procedure has been applied. Also, as in 1g-25, the receiving PDCP layer device at the receiving end applies a decoding procedure to the data received from the lower layer device, and an integrity verification procedure based on the 4-byte MAC-I field attached to the decoded data. is applied to check whether integrity has failed, the data that has failed the integrity verification procedure in the above is discarded, and the data that passed the integrity verification procedure is sorted in the order of the PDCP serial number or COUNT value, or when the header compression procedure is set , a header decompression procedure may be applied to the data, and the data may be delivered to a higher layer device in an ascending order of the COUNT value. If the header compression procedure is not set in the above, the header compression procedure or the header decompression procedure may be omitted.

Referring to Figure 7c, when the header compression procedure or integrity protection procedure is set in the PDCP layer device as in 1g-30, or the encryption procedure is not set, the transmitting PDCP layer device as shown in 1g-30 sends data to the upper layer device data. Header compression procedure is applied to the data, integrity protection procedure is performed on header compressed data or PDCP header, a 4-byte MAC-I field is appended to the back, and a PDCP header is applied to the data and MAC-I field to which the integrity protection procedure has been applied. can be passed to the lower layer device by attaching it to the front. Also, as in 1g-35, the receiving PDCP layer device at the receiving end checks whether the integrity fails by applying the integrity verification procedure based on the 4-byte MAC-I field attached to the back of the data received from the lower layer device, and in the above Data that has failed the integrity verification procedure is discarded, and the data that has passed the integrity verification procedure is sorted in the order of the PDCP serial number or COUNT value, or if the header compression procedure is set, the header decompression procedure is applied to the data, , the data may be delivered to the upper layer device in an ascending order of the COUNT value. If the header compression procedure is not set in the above, the header compression procedure or the header decompression procedure may be omitted.

The data transmitted above is generated and transmitted in a repeated structure of header and data as in 1g-15. For example, data having a repeated structure such as a header (MAC header, RLC header, PDCP header, or SDAP header) and data and a header (MAC header, RLC header, PDCP header or SDAP header) and data are included. Therefore, when generating data having a repeating structure with headers having a fixed size as described above, a hardware accelerator (hardward engine) may be applied to reduce data processing time in order to perform faster data processing. In the above, the hardware accelerator is applied or called when adding or removing the header (MAC header, RLC header, PDCP header or SDAP header), or performing an encryption procedure, a decryption procedure, an integrity protection procedure, or an integrity verification procedure. and can be used

8 is a view for explaining integrity protection, verification procedure, encryption, or decryption procedure in the next-generation mobile communication system of the present invention.

As shown in 1h-05 of FIG. 8, the integrity protection procedure, when the integrity protection procedure is set, the security keys derived or applied from the upper layer device (eg, the RRC layer device or the NAS layer device) and the data to which the integrity protection procedure is applied Integrity protection procedure can be performed based on the COUNT value corresponding to , or bearer identifiers corresponding to data. For example, the data to which the integrity protection procedure is applied is calculated according to the integrity protection algorithm in units of 8 bytes (64 bits), and finally a 4-byte (32-bit) MAC-I is calculated, and the MAC-I at the end of the data is calculated. (Message Authentication Code for Integrity) field can be attached. The integrity verification procedure at the receiving end compares the 4-byte X-MAC field value obtained by applying the integrity verification algorithm to the received data and the MAC-I value attached to the data, and if the two values are the same, the integrity verification of the data It can be judged that this has been carried out successfully. If the two values are different, it may be determined that the integrity verification has failed and the data may be discarded. As described above, the integrity protection procedure or integrity verification procedure is a very complex procedure, has high data processing complexity, and takes a long time to process data.

As shown in 1h-10, the encryption procedure can be performed when the encryption procedure is set. For example, an encryption algorithm based on security keys derived or applied from a higher layer device (for example, an RRC layer device or a NAS layer device) and a COUNT value corresponding to the data to be encrypted or bearer identifiers corresponding to the data. Through this, a key stream having the same length as the data can be generated. In addition, encrypted data may be generated by performing an XOR procedure on the generated key stream and the data to be encrypted. Conversely, the receiving end may perform the decryption procedure by performing an XOR procedure on the encrypted data that has received the key stream generated through the decryption algorithm. As such, the encryption procedure or the decryption procedure is a very complex procedure, and the data processing complexity is high, and the data processing time is long.

9 is a diagram for explaining a long data processing time due to high complexity when an integrity protection procedure or an encryption procedure is applied to data in a PDCP layer device in the present invention.

Assuming that the transmitting PDCP layer device receives 8 data from a higher layer device as in FIG. 9, if an integrity protection procedure or an encryption procedure is set, the transmitting PDCP layer device performs 8 integrity protection procedures and 8 MACs The -I field must be created and attached to the back of each data, or 8 encryption procedures must be performed on the data. Therefore, applying the integrity protection procedure or encryption procedure to each data above is to perform a very complicated procedure 8 times, which consumes a lot of data processing time. Also at the receiving end, if the receiving PDCP layer device receives 8 data from the lower layer device, it must perform 8 decoding procedures and 8 integrity verification procedures.

10 is a diagram illustrating an operation of driving an RLC reception window in the RLC layer device of the present invention.

In 1j-05, the RLC receive window may be driven by window variables. For example, the first variable (RX_NEXT) indicates the next RLC serial number of the data with the lowest RLC serial number successfully received in order, and the second variable (RX_NEXT_Highest) indicates that it will receive next It may indicate a contemplated RLC serial number or may indicate a next RLC serial number of data having the highest RLC serial number among received data. In the reception window, for each RLC serial number between the first variable or the second variable, a list mapping RLC serial number, data, or whether or not it has been successfully received, is configured, and the serial number or data search is performed. You can implement a linked list to do this.

The transmission RLC layer device can also drive the transmission window, configure a list that maps RLC serial number, data, or whether or not it has been successfully received as described above, and a linked list (linked list) to perform serial number or data search list) can be implemented. The linked lists configured above can be used when performing the ARQ procedure in the RLC layer device, more specifically when updating the window variables, configuring the RLC status report, or performing the retransmission procedure in the RLC ARQ procedure. It can be used to search the linked list based on the RLC serial number to find data or update information. Therefore, as the number of RLC serial numbers allocated by the transmitting RLC layer device increases, the length of the linked list becomes longer, and when the length of the linked list becomes longer, the search time performed with the length of the RLC serial number becomes very long. . 7A, 7B, and 7C, since there is no data concatenation procedure in the next-generation mobile communication system, the number of RLC serial numbers configured in the linked list becomes very large. The RLC serial number space or linked list becomes very large. Therefore, when the RLC layer device performs the ARQ procedure, as the data search time becomes longer, the data processing time increases.

11a, 11b, 12a, 12b, and 13 reduce the number of data processing of the integrity protection procedure, integrity verification procedure, encryption procedure, or decryption procedure in the present invention, and reduce the number of allocated RLC serial numbers, data It is a diagram showing a first embodiment, a second embodiment, or a third embodiment of the data concatenation procedure proposed by the present invention to reduce processing time.

Various data processing methods are proposed for improving data processing speed when a base station and a terminal perform data processing at a high data rate in a next-generation mobile communication system according to an example of the present invention.

As described above with reference to FIGS. 9 and 10, among the data processing procedures performed when the terminal or the base station transmits or receives data, the procedure that consumes the most processing load or time is the ciphering procedure of the PDCP layer device. , a decryption procedure (deciphering), integrity protection procedure (integrity protection), integrity verification procedure (Integrity verification), or ARQ (Autonomous Repeat Request) procedure in the RLC layer device.

As described in FIG. 5, the above procedures are procedures performed in the RLC layer device or the PDCP layer device configured for each bearer. or RRCResume message) to configure the encryption procedure (or decryption procedure), integrity protection procedure (or integrity verification procedure), or ARQ procedure (eg RLC AM mode) for each bearer (eg, SRB or DRB), or not to use, can be set as an indicator.

Therefore, if an encryption procedure (or decryption procedure) is established for a bearer and an integrity protection procedure (or integrity verification procedure) is not configured, the UE or base station performs the integrity protection procedure (or integrity verification procedure) for the bearer. Without it, an encryption procedure (or a decryption procedure) may be performed.

In addition, if an encryption procedure (or decryption procedure) is not established for a bearer and an integrity protection procedure (or integrity verification procedure) is set, the terminal or base station performs the integrity protection procedure (or integrity verification procedure) for the bearer and , the encryption procedure (or decryption procedure) may not be performed.

In addition, when an encryption procedure (or decryption procedure) is set for a bearer and an integrity protection procedure (or integrity verification procedure) is also set, the terminal or base station performs an integrity protection procedure (or integrity verification procedure) for the bearer, Then, an encryption procedure (or a decryption procedure) may be performed.

In the above, since the PDCP layer device performs the encryption procedure (or decryption procedure) or the integrity protection procedure (or integrity verification procedure) once for each data received from the upper layer device, the more data it receives, the more the encryption procedure (or decryption procedure) procedure) or integrity protection procedure (or integrity verification procedure) must be performed a lot, which increases data processing complexity and increases data processing time. In addition, in the RLC layer device, since an RLC serial number is assigned to each data received from a higher layer device (eg, a PDCP layer device), the more data it receives, the more RLC serial numbers must be allocated and used. The ARQ procedure that operates with this becomes very complicated and requires a lot of data processing time.

Therefore, in the present invention, the number or frequency of performing the encryption procedure (or decryption procedure) or integrity protection procedure (or integrity verification procedure) in the PDCP layer device is reduced, or the number of RLC serial numbers allocated and used by the RLC layer device itself is reduced. Suggest ways to reduce Since the encryption procedure (or decryption procedure) or the integrity protection procedure (or integrity verification procedure) in the above is a procedure with a large data processing load, it can be processed using a hardware accelerator or hardware engine, in which the encryption procedure ( Alternatively, if the number of calls to the hardware accelerator itself is reduced to perform the decryption procedure) or the integrity protection procedure (or integrity verification procedure), the hardware accelerator calls are made more parallel to process other data (for example, data from different bearers). Because it can be used as a data processing time, it is possible to reduce the data processing time and improve the data processing speed. In addition, if the number of RLC serial numbers allocated to each data is reduced, the time for searching the list with the RLC serial number, data, ACK, or NACK indicator in the ARQ procedure of the RLC layer device can be reduced, so the data processing time can be reduced. .

In the present invention, a data concatenation procedure (concatenation) is performed on data (eg, SDAP SDU or PDCP SDU) received from a higher layer device (eg, a PDCP layer device or an SDAP layer device) in a higher layer device (eg, a PDCP layer device or an SDAP layer device) suggest to do In the above, if the upper layer device data concatenation procedure is set at the transmitting end, data separation procedure (de-concatenation or separation) must be performed at the receiving end.

The present invention proposes a first embodiment of a data concatenation procedure as shown in FIGS. 11A and 11B, a second embodiment of a data concatenation procedure as shown in FIGS. 12A and 12B, or a third embodiment of a data concatenation procedure as shown in FIG. 13 do.

The first, second, or third embodiment of the upper layer device data concatenation procedure proposed by the present invention above may have one or a plurality of functions among the following functions.

- The data concatenation procedure proposed in the present invention may be configured or performed in an SDAP layer device, a PDCP layer device, or a new layer device, and is an RRC message (eg, RRCReconfiguration message or RRCSetup message or RRCResume message) for each bearer , or whether or not the data concatenation procedure is applied as an indicator for each downlink or uplink may be set. When the data concatenation procedure is set in the RRC message, the number of data to be concatenated or the maximum size of data that can be concatenated may be set. In another method, the number of data to be concatenated or the size to be concatenated may be freely determined by the terminal implementation or the base station implementation.

- The terminal supporting the data concatenation procedure proposed in the present invention is the maximum size that can be concatenated with the data concatenation procedure (for example, the maximum size of concatenated data or the encryption procedure (or decryption procedure) or integrity at one time The maximum size to which a protection procedure (or integrity verification procedure) can be applied) or whether a data concatenation procedure is supported may be reported in a UE capability reporting message. In the above, the maximum size that the terminal or base station can concatenate with the data concatenation procedure or the maximum size of concatenated data, or the encryption procedure (or decryption procedure) or integrity protection procedure (or integrity verification procedure) can be applied at once. The maximum size may be predefined or defined and used in the PDCP layer device. For example, the maximum size (eg, 8192 bytes or 9000 bytes) may be defined in the PDCP layer device related standard.

- It is proposed to introduce new fields (1k-01, 11-01, 1m-01) to perform the data concatenation procedure or data separation procedure proposed in the present invention. Some of the new fields proposed above may be introduced or defined in the SDAP header or PDCP header, or some of the new fields may be attached or introduced in front of each concatenated data, or some of the new fields may be attached or introduced at the beginning of all concatenated data. When performing the data concatenation procedure above, a new field may be introduced for each data and used in the data concatenation procedure or data separation procedure. For example, the new fields are placed in front of each data so that {[new field + data] [new field + data] ... Data may be concatenated in a structure such as [new field + data]} (11-05, 11-15, 11-20 in FIGS. 12A and 12B). The above structure facilitates data processing speed because data processing can be performed sequentially and quickly using new fields and the processed data can be directly transferred to the upper layer. Another way, [new field][new field]… [new field][data + data + … + data], data may be concatenated. The above structure has the advantage of being able to process new fields at once (1k-05, 1k-10, 1k-15, 1k-20 in FIGS. 11A and 11B or 1m-05, 1m-10, 1 m-15).

- In the present invention, the terminal or the base station may apply or perform the data concatenation procedure or the data separation procedure proposed above based on the new fields. The new fields 1k-01, 11-01, 1m-01 may include one or a plurality of fields among the following fields.

■ C field: It can indicate whether data linking function is performed or not. Another way is to indicate whether there is data immediately after or if there are new fields or concatenated data.

■ E field: It can indicate whether there is data immediately after, or whether there are new fields or concatenated data.

■ LI field: The size of each concatenated data can be indicated in bytes, or for concatenated data, the size of each data received from a higher layer device or transmitted to a higher layer device can be indicated in bytes. . For example, the first LI field may indicate the size of the first (or first) data among concatenated data in bytes, or the second LI field may indicate the size of the second (or first) data among concatenated data. Then) the size of data can be indicated in bytes. For example, you can introduce an LI field for each data and use it in a data concatenation procedure or a data separation procedure. For example, each of the LI fields is located in front of each data, so that {[LI field + data] [LI field + data] ... Data can be concatenated in the same structure as [LI field + data]}. The above structure facilitates data processing speed because data processing can be performed sequentially and quickly using new fields and the processed data can be directly transferred to the upper layer. Another way is [E field LI field] [E fill LI field]… [E Fill LI Field][Data + Data + … + data], data may be concatenated. The above structure has the advantage of being able to process new fields at once in the implementation. As another method, the LI field indicating the size of the last data may be omitted. This is because, when n pieces of data are concatenated, if the n-1 th data is separated by the LI field, the remaining data itself becomes the nth data without knowing the size of the remaining data. As another method, in the above, the LI field may indicate the size of concatenated data in bytes. can be directed to As another method, in the above, the LI field may indicate the size of concatenated data in bytes, and if the integrity protection procedure is set, it may indicate the size of data before the integrity protection procedure is applied, and the concatenated data MAC-I field can be added at the end of Taking this into account, data separation procedures can be performed. For example, the LI field for the last data may indicate the length of the last data except for the MAC-I field. As another method, in the above, the LI field may indicate the size of concatenated data in bytes. can indicate the size of , and a MAC-I field can be added at the end of the concatenated data, and if the header compression procedure or integrity protection procedure is set when the data separation procedure is applied at the receiving end, a predetermined length ( For example, the data separation procedure may be performed considering that there is a MAC-I field having 4 bytes). For example, the LI field for the last data may indicate the length of the compressed last data to which the header compression procedure is applied except for the MAC-I field.

■ F field: A field indicating the length of an LI field introduced or attached for data concatenation or data separation. Whether the LI field is a field with a small length (eg 6 bytes) or a long length (eg 14 bytes) bytes) can be indicated. The overhead for the LI field can be reduced by introducing the F field.

■ SN field: A field indicating the order of data in concatenated data (eg, a sequence number) can indicate the order of data.

- For the new fields proposed in the present invention, if integrity protection is set in the PDCP layer device for convenience of implementation (for example, the same processing as data can be performed), the integrity protection procedure is applied to the new fields, Alternatively, when the encryption procedure is applied to the PDCP layer device, the encryption procedure may be applied (1k-05 in FIG. 11A or 11-05 in FIG. 12A). In another method, in order to enable the receiving end to read new fields before the decoding procedure, the new fields proposed in the present invention apply the integrity protection procedure to the new fields when integrity protection is set in the PDCP layer device, or When the encryption procedure is applied to the PDCP layer device, the encryption procedure may not be applied (1k-10 in FIG. 11B ). That is, if the encryption procedure is not applied even when the integrity protection procedure is applied, the receiving end can read the new fields in advance before the decryption procedure.

- The data concatenation procedure proposed in the present invention is characterized in that the transmitting end (terminal or base station) applies or performs the data concatenation procedure to data to which the integrity protection procedure or the encryption procedure is not applied or performed. In another method, the data concatenation procedure proposed in the present invention is characterized in that the data concatenation procedure is applied or performed on data before or before the integrity protection procedure or encryption procedure is applied at the transmitting end (terminal or base station) do it with For example, if an integrity protection procedure or encryption procedure is established, the data concatenation procedure may be performed or applied, and then the integrity protection procedure or encryption procedure may be performed on the concatenated data. This is because the number or frequency of performing the integrity protection procedure or the encryption procedure can be minimized and the data processing time can be reduced only when the integrity protection procedure or the encryption procedure is applied to the contiguous data at once. In addition, when applying the integrity protection procedure or encryption procedure to one concatenated data concatenating multiple data in the above, the integrity protection procedure or encryption procedure is performed on a plurality of concatenated data at once using a single COUNT value. Thus, single processing is possible with one set of security key values (COUNT value or bearer identifier or security key, etc.) and data processing time can be shortened. For example, if a plurality of data is not concatenated in the above, data processing time is shortened because integrity protection or encryption procedure must be performed multiple times based on different sets of security key values using a different COUNT value for each data. need a lot In addition, when the integrity protection procedure is applied in the above, one MAC-I field can be added after concatenated data, but when the concatenated procedure is not applied, each MAC-I field must be added after each data. Processing is also complex and can increase overhead. Also, when applying or performing the data concatenation procedure to the data, the data concatenation procedure may be applied in the order received from the upper layer device, or the data may be concatenated in order from the beginning of the concatenation procedure. This is because, when the data concatenation procedure is performed, the data can be sequentially transferred to the upper layer device when the data concatenated at the receiving end is separated only by concatenating the data from the front in order. For example, data concatenated to concatenated data to which one PDCP serial number is assigned are in the order of data first received from the upper layer device from the front.

- The data separation procedure proposed in the present invention is characterized in that a data separation procedure is applied or performed on concatenated data to which a decoding procedure or an integrity verification procedure has been applied or performed at the receiving end (terminal or base station). In another method, the data separation procedure proposed in the present invention is characterized in that the data separation procedure is applied or performed on the concatenated data after or after the decoding procedure or the integrity verification procedure is applied at the receiving end (terminal or base station). do. For example, if an encryption procedure or an integrity verification procedure is set, a decryption procedure may be performed on the received concatenated data, or a data separation procedure may be performed on the concatenated data after the integrity verification procedure is performed. This is because the number or frequency of performing the decryption procedure or the integrity verification procedure can be minimized and the data processing time can be reduced only when the decryption procedure or the integrity verification procedure is applied to the concatenated data at once. In addition, when the decryption procedure or integrity protection procedure is applied to one concatenated data concatenating multiple data in the above, the decryption procedure or integrity protection procedure is performed once for a plurality of concatenated data using a single COUNT value. By doing so, it is possible to enable single processing with one set of security key values (such as a COUNT value or a bearer identifier or security key) and shorten the data processing time. For example, if data is not concatenated in the above, data processing time is very long because the decryption procedure or integrity protection procedure has to be performed multiple times based on different sets of security key values using a different COUNT value for each data. need. In addition, when applying or performing the data separation procedure to the concatenated data in the above, the data may be sequentially separated from the front of the concatenated data, and the data may be processed sequentially from the front and delivered to the upper layer device. For example, data concatenated to concatenated data to which one PDCP serial number is assigned must first be delivered to a higher layer device from the front.

- If the data concatenation procedure proposed above is configured or performed in the SDAP layer device (1k-20 of FIG. 11b or 11-20 of FIG. 12b or 13), the SDAP layer device performs the data concatenation procedure with SDAP control data (SDAP control) PDU) may not be applied. Because an encryption procedure or a decryption procedure is not applied to the SDAP control data, if the SDAP control data is concatenated with other data, the implementation complexity can be increased when the concatenated data is encrypted or decrypted. . In the above, when the SDAP layer device performs the data concatenation function, the data concatenation procedure is performed only on the data of the upper layer device corresponding to the QoS flow IDs (QoS identifiers) mapped to each bearer, and the concatenated data is transferred to the bearer. It can be delivered to the PDCP layer device. As another method, when performing the data concatenation function in the SDAP layer device and performing the data concatenation procedure on the data of the upper layer device corresponding to QoS flow IDs (QoS identifiers) mapped to each bearer, specifically The data concatenation procedure may be applied only to data corresponding to the same QoS flow ID (QoS identifier), and the concatenated data may be delivered to the PDCP layer device of the bearer. In the above, when the integrity protection procedure is set to the SDAP control data, the integrity protection procedure may be applied, or when the encryption procedure is set, the encryption procedure may not be applied.

- If the data concatenation procedure proposed above is configured or performed in the SDAP layer device (1k-20 in FIG. 11b or 11-20 or 13 in FIG. 12b), the data concatenation procedure proposed in the present invention is the transmitting terminal (terminal or base station) ), it is characterized in that the data concatenation procedure is applied or performed to data to which the header compression procedure, the integrity protection procedure, or the encryption procedure is not applied or performed. As another method, in the data concatenation procedure proposed in the present invention, the data concatenation procedure is applied or characterized by performing. Accordingly, the length field (eg, the LI field) among the new fields generated in the data concatenation procedure may set the length of header uncompressed data as a byte unit value. For example, if a header compression procedure, integrity protection procedure, or encryption procedure is established, the data concatenation procedure may be performed or applied, and then the header compression procedure, integrity protection procedure, or encryption procedure may be performed on the concatenated data. This is because the number or frequency of performing the integrity protection procedure or the encryption procedure can be minimized and the data processing time can be reduced only when the integrity protection procedure or the encryption procedure is applied to the contiguous data at once. In addition, when applying the integrity protection procedure or encryption procedure to one concatenated data concatenating multiple data in the above, the integrity protection procedure or encryption procedure is performed using a single COUNT value, so that one set of security key values ( COUNT value or bearer identifier or security key) enables single processing and shortens data processing time. For example, if data is not concatenated above, data processing time is required because integrity protection or encryption procedures must be performed multiple times based on different sets of security key values using a different COUNT value for each data. Do. Also, when applying or performing the data concatenation procedure to the data, the data concatenation procedure may be applied in the order received from the upper layer device, or the data may be concatenated in order from the beginning of the concatenation procedure. This is because, when the data concatenation procedure is performed, the data can be sequentially transferred to the upper layer device when the data concatenated at the receiving end is separated only by concatenating the data from the front in order. For example, data concatenated to concatenated data to which one PDCP serial number is assigned are in the order of data first received from the upper layer device from the front.

- If the data concatenation procedure proposed above is configured or performed in the SDAP layer device (1k-20 in FIG. 11b or 11-20 in FIG. 12b or 13), the data separation procedure proposed in the present invention is the receiving end (terminal or base station) ), it is characterized in that the data separation procedure is applied or performed to the concatenated data to which the decryption procedure, the integrity verification procedure, or the header decompression procedure is applied or performed. As another method, in the data separation procedure proposed in the present invention, the data separation procedure is applied to the data concatenated after or after the decoding procedure, the integrity verification procedure, or the header decompression procedure is applied at the receiving end (terminal or base station). Or characterized in that it is performed. For example, if a header compression procedure, encryption procedure, or integrity verification procedure is set, a decryption procedure is performed on the received concatenated data, and the integrity verification procedure or header decompression procedure is performed, and then data is separated on the concatenated data procedure can be performed. This is because the number or frequency of performing the decryption procedure or the integrity verification procedure can be minimized and the data processing time can be reduced only when the decryption procedure or the integrity verification procedure is applied to the concatenated data at once. In addition, when a decryption procedure or integrity protection procedure is applied to one concatenated data concatenated with several data in the above, a decryption procedure or integrity protection procedure is performed using a single COUNT value, so that one set of security key values ( COUNT value or bearer identifier or security key) enables single processing and shortens data processing time. For example, if the data is not concatenated above, the data processing time is reduced because the decryption procedure or the integrity protection procedure must be performed multiple times based on a set of different security key values using a different COUNT value for each data. need a lot In addition, when applying or performing the data separation procedure to the concatenated data in the above, the data may be sequentially separated from the front of the concatenated data, and the data may be processed sequentially from the front and delivered to the upper layer device. For example, data concatenated to data to which one PDCP serial number is assigned should be first delivered to a higher layer device from the front.

- If the data concatenation procedure proposed above is set or performed in the SDAP layer device (1k-20 in FIG. 11b or 11-20 or 13 in FIG. 12b), the data processing load is increased and implementation complexity is increased due to the header compression procedure. can be Therefore, in the above, if the data concatenation procedure or separation procedure is configured for a certain bearer, or for the bearer or higher layer device in which the data concatenation procedure is configured, the header compression procedure (eg, ROHC (Robust header compression), EHC (Ethernet header compression)) ) or data compression procedure (UDC, Uplink data compression) is set to use or add, it may adversely affect the data processing speed. This is because the transmitting end must perform a header compression procedure for each data or the receiving end must perform a header decompression procedure for each data. Therefore, for each bearer or higher layer device (PDCP layer device or SDAP layer device or new layer device), the data concatenation procedure and header compression procedure (eg, ROHC (Robust header compression), EHC (Ethernet header compression)) or data compression You can limit the procedure (UDC, Uplink data compression) not to be set together. For example, if a data concatenation procedure is configured, it may be restricted so that a header compression procedure (eg, robust header compression (ROHC), Ethernet header compression (EHC)) or a data compression procedure (UDC, uplink data compression) cannot be set. As another method, if a header compression procedure (eg, ROHC (Robust header compression), EHC (Ethernet header compression)) or data compression procedure (UDC, Uplink data compression) is set, it is possible to limit the setting of the data concatenation procedure. . Alternatively, the encryption procedure or the integrity protection procedure may not be set in order to further accelerate the data rate in the above.

- If the header compression procedure or data compression procedure is not set in order to accelerate data processing in the above, or if the data concatenation procedure proposed above is set or performed in the SDAP layer device, the data concatenation procedure proposed in the present invention is or base station) to which the data concatenation procedure is applied or performed to data to which the integrity protection procedure or the encryption procedure is not applied or is not performed. In another method, the data concatenation procedure proposed in the present invention is characterized in that the data concatenation procedure is applied or performed on data before or before the integrity protection procedure or encryption procedure is applied at the transmitting end (terminal or base station). do. Accordingly, among the new fields generated in the data concatenation procedure, the length field (eg, the LI field) may set the data length as a byte unit value. For example, if an integrity protection procedure or encryption procedure is established, the data concatenation procedure may be performed or applied, and then the integrity protection procedure or encryption procedure may be performed on the concatenated data. This is because the number or frequency of performing the integrity protection procedure or the encryption procedure can be minimized and the data processing time can be reduced only when the integrity protection procedure or the encryption procedure is applied to the contiguous data at once. In addition, when applying the integrity protection procedure or encryption procedure to one concatenated data concatenating multiple data in the above, the integrity protection procedure or encryption procedure is performed using a single COUNT value, so that one set of security key values ( COUNT value or bearer identifier or security key) enables single processing and shortens data processing time. For example, if data is not concatenated above, data processing time is required because integrity protection or encryption procedures must be performed multiple times based on different sets of security key values using a different COUNT value for each data. Do. Also, when applying or performing the data concatenation procedure to the data, the data concatenation procedure may be applied in the order received from the upper layer device, or the data may be concatenated in order from the beginning of the concatenation procedure. This is because, when the data concatenation procedure is performed, the data can be sequentially transferred to the upper layer device when the data concatenated at the receiving end is separated only by concatenating the data from the front in order. For example, data concatenated to concatenated data to which one PDCP serial number is assigned are in the order of data first received from the upper layer device from the front.

- If the header compression procedure or data compression procedure is not set in order to accelerate data processing in the above, or if the data concatenation procedure proposed above is set or performed in the SDAP layer device, the data separation procedure proposed in the present invention is or base station) to apply or perform a data separation procedure to concatenated data to which a decoding procedure or an integrity verification procedure has been applied or performed. In another method, the data separation procedure proposed in the present invention is characterized in that the data separation procedure is applied or performed on the concatenated data after or after the decoding procedure or the integrity verification procedure is applied at the receiving end (terminal or base station). do. For example, if an encryption procedure or an integrity verification procedure is set, a decryption procedure may be performed on the received concatenated data, or a data separation procedure may be performed on the concatenated data after the integrity verification procedure is performed. This is because the number or frequency of performing the decryption procedure or the integrity verification procedure can be minimized and the data processing time can be reduced only when the decryption procedure or the integrity verification procedure is applied to the concatenated data at once. In addition, when a decryption procedure or integrity protection procedure is applied to one concatenated data concatenating multiple data in the above, a decryption procedure or integrity protection procedure is performed using a single COUNT value, so that one set of security key values ( COUNT value or bearer identifier or security key) enables single processing and shortens data processing time. For example, if data is not concatenated in the above, data processing time is very long because the decryption procedure or integrity protection procedure has to be performed multiple times based on different sets of security key values using a different COUNT value for each data. need. In addition, when applying or performing the data separation procedure to the concatenated data in the above, the data may be sequentially separated from the front of the concatenated data, and the data may be processed sequentially from the front and delivered to the upper layer device. For example, data concatenated to concatenated data to which one PDCP serial number is assigned must first be delivered to a higher layer device from the front.

- If the data concatenation procedure proposed above is configured in the PDCP layer device (1k-15 of FIG. 11b or 11-15 of FIG. 12b or 13) or performed, the PDCP layer device performs the data concatenation procedure with SDAP control data (SDAP control) PDU) or PDCP control data (PDCP control PDU) may not be applied. This is because, since an encryption procedure or a decryption procedure is not applied to SDAP control data, when the SDAP control data is concatenated with other data, implementation complexity can be increased when the concatenated data is encrypted or decrypted. In addition, since an encryption procedure, a decryption procedure, an integrity protection procedure, or an integrity verification procedure is not applied to the PDCP control data, when the PDCP control data is concatenated with other data, the procedure for encrypting or decrypting the concatenated data, the integrity protection procedure, Alternatively, the implementation complexity may be increased when performing the integrity verification procedure. In the above, when the integrity protection procedure is set to the SDAP control data, the integrity protection procedure may be applied, or when the encryption procedure is set, the encryption procedure may not be applied. However, when the integrity protection procedure is set to the PDCP control data in the above, the integrity protection procedure may not be applied, or the encryption procedure may not be applied when the encryption procedure is set. As another method, when the integrity protection procedure is set to the SDAP control data, the integrity protection procedure may not be applied, or the encryption procedure may not be applied when the encryption procedure is set.

- If the data concatenation procedure proposed above is set or performed in the PDCP layer device (1k-15 of FIG. 11b or 11-15 of FIG. 12b or FIG. 13), the data processing load is increased due to the header compression procedure and implementation complexity is increased. can be Therefore, in the above, if a data concatenation procedure or separation procedure is configured for a certain bearer, or a header compression procedure (eg, ROHC (Robust header compression), EHC (Ethernet header compression) )) or data compression procedure (UDC, Uplink data compression) is set to use or add, it may adversely affect the data processing speed. This is because the transmitting end must perform a header compression procedure for each data or the receiving end must perform a header decompression procedure for each data. Therefore, for each bearer or higher layer device (PDCP layer device or SDAP layer device or new layer device), the data concatenation procedure and header compression procedure (eg, ROHC (Robust header compression), EHC (Ethernet header compression)) or data compression You can limit the procedure (UDC, Uplink data compression) not to be set together. For example, if a data concatenation procedure is configured, it may be restricted so that a header compression procedure (eg, robust header compression (ROHC), Ethernet header compression (EHC)) or a data compression procedure (UDC, uplink data compression) cannot be set. As another method, if a header compression procedure (eg, ROHC (Robust header compression), EHC (Ethernet header compression)) or data compression procedure (UDC, Uplink data compression) is set, it is possible to limit the setting of the data concatenation procedure. . Alternatively, the encryption procedure or the integrity protection procedure may not be set in order to further accelerate the data rate in the above.

- If the data concatenation procedure proposed above is configured or performed in the PDCP layer device (1k-15 in FIG. 11b or 11-15 in FIG. 12b or 13), the data concatenation procedure proposed in the present invention is the transmitting terminal (terminal or base station) ), it is characterized in that the data concatenation procedure is applied or performed to data to which the header compression procedure is applied or performed, but the integrity protection procedure or encryption procedure is not applied or performed. In another method, in the data concatenation procedure proposed in the present invention, the header compression procedure is applied or performed at the transmitting end (terminal or base station), but data to which the header compression procedure is applied before or before the integrity protection procedure or encryption procedure is applied or performed. It is characterized in that the data concatenation procedure is applied or performed. Therefore, among the new fields generated in the data concatenation procedure, the length field (eg, LI field) may set the length of data to which the header compression procedure is applied as a byte unit value. For example, if a header compression procedure or integrity protection procedure or encryption procedure is established, the header compression procedure is applied or performed to each data, the data concatenation procedure is performed on multiple data, or the integrity protection procedure is applied to the concatenated data Alternatively, an encryption procedure may be performed. This is because the number or frequency of performing the integrity protection procedure or the encryption procedure can be minimized and the data processing time can be reduced only when the integrity protection procedure or the encryption procedure is applied to the contiguous data at once. On the other hand, since the complexity of applying or performing the header compression procedure to each data of concatenated data is high, it is convenient to concatenate after performing the header compression procedure in advance, and the length field indicating the length of each concatenated data can be reduced to reduce overhead. In addition, when applying the integrity protection procedure or encryption procedure to one concatenated data concatenating multiple data in the above, the integrity protection procedure or encryption procedure is performed using a single COUNT value, so that one set of security key values ( COUNT value or bearer identifier or security key) enables single processing and shortens data processing time. For example, if data is not concatenated above, data processing time is required because integrity protection or encryption procedures must be performed multiple times based on different sets of security key values using a different COUNT value for each data. Do. Also, when applying or performing the data concatenation procedure to the data, the data concatenation procedure may be applied in the order received from the upper layer device, or the data may be concatenated in order from the beginning of the concatenation procedure. This is because, when the data concatenation procedure is performed, the data can be sequentially transferred to the upper layer device when the data concatenated at the receiving end is separated only by concatenating the data from the front in order. For example, data concatenated to concatenated data to which one PDCP serial number is assigned are in the order of data first received from the upper layer device from the front.

- If the data concatenation procedure proposed above is set or performed in the PDCP layer device (1k-15 in FIG. 11b or 11-15 in FIG. 12b or 13), the data separation procedure proposed in the present invention is the receiving terminal (terminal or base station) ), it is characterized in that the data separation procedure is applied or performed to the contiguous data to which the decryption procedure or the integrity verification procedure has been applied or performed, and the header decompression procedure can be applied to each of the above separated data. In another method, the data separation procedure proposed in the present invention is characterized in that the data separation procedure is applied or performed on the concatenated data after or after the decoding procedure or the integrity verification procedure is applied at the receiving end (terminal or base station). and a header decompression procedure may be applied to each of the above separated data. For example, if a header compression procedure, encryption procedure, or integrity verification procedure is set, a decryption procedure is performed on the received concatenated data or an integrity verification procedure is performed and then a data separation procedure is performed on the concatenated data, The header decompression procedure can be applied to each data separated in . This is because the number or frequency of performing the decryption procedure or the integrity verification procedure can be minimized and the data processing time can be reduced only when the decryption procedure or the integrity verification procedure is applied to the concatenated data at once. On the other hand, since it is complicated to apply or perform the header decompression procedure for each data of the concatenated data, it is easy to implement and perform the header decompression procedure after separating the data later, and the length of each concatenated data It is possible to reduce the length field indicating In addition, when a decryption procedure or integrity protection procedure is applied to one concatenated data concatenating multiple data in the above, a decryption procedure or integrity protection procedure is performed using a single COUNT value, so that one set of security key values ( COUNT value or bearer identifier or security key) enables single processing and shortens data processing time. For example, if data is not concatenated in the above, data processing time is very long because the decryption procedure or integrity protection procedure has to be performed multiple times based on different sets of security key values using a different COUNT value for each data. need. In addition, when applying or performing the data separation procedure to the concatenated data in the above, the data may be sequentially separated from the front of the concatenated data, and the data may be processed sequentially from the front and delivered to the upper layer device. For example, data concatenated to concatenated data to which one PDCP serial number is assigned must first be delivered to a higher layer device from the front.

- If the header compression procedure or data compression procedure is not set in order to accelerate data processing in the above, or if the data concatenation procedure proposed above is configured or performed in the PDCP layer device, the data concatenation procedure proposed in the present invention is or base station) to which the data concatenation procedure is applied or performed to data to which the integrity protection procedure or the encryption procedure is not applied or is not performed. In another method, the data concatenation procedure proposed in the present invention is characterized in that the data concatenation procedure is applied or performed on data before or before the integrity protection procedure or encryption procedure is applied at the transmitting end (terminal or base station). do. Therefore, among the new fields generated in the data concatenation procedure, the length field (eg, LI field) may set the length of data to which the header compression procedure is applied as a byte unit value. For example, if an integrity protection procedure or encryption procedure has been established, the data concatenation procedure may be performed or applied to multiple data, and then the integrity protection procedure or encryption procedure may be performed on the concatenated data. This is because the number or frequency of performing the integrity protection procedure or the encryption procedure can be minimized and the data processing time can be reduced only when the integrity protection procedure or the encryption procedure is applied to the contiguous data at once. In addition, when applying the integrity protection procedure or encryption procedure to one concatenated data concatenating multiple data in the above, the integrity protection procedure or encryption procedure is performed using a single COUNT value, so that one set of security key values ( COUNT value or bearer identifier or security key) enables single processing and shortens data processing time. For example, if data is not concatenated above, data processing time is required because integrity protection or encryption procedures must be performed multiple times based on different sets of security key values using a different COUNT value for each data. Do. Also, when applying or performing the data concatenation procedure to the data, the data concatenation procedure may be applied in the order received from the upper layer device, or the data may be concatenated in order from the beginning of the concatenation procedure. This is because, when the data concatenation procedure is performed, the data can be sequentially transferred to the upper layer device when the data concatenated at the receiving end is separated only by concatenating the data from the front in order. For example, data concatenated to data to which one PDCP serial number is assigned is in the order of data first received from the upper layer device from the front.

- If the header compression procedure or data compression procedure is not set in order to accelerate data processing in the above, or if the data concatenation procedure proposed above is set or performed in the PDCP layer device, the data separation procedure proposed in the present invention is Alternatively, it may be characterized in that the data separation procedure is applied or performed on the concatenated data to which the decoding procedure or the integrity verification procedure has been applied or performed in the base station). In another method, the data separation procedure proposed in the present invention is characterized in that the data separation procedure is applied or performed on the concatenated data after or after the decoding procedure or the integrity verification procedure is applied at the receiving end (terminal or base station). can do. For example, if an encryption procedure or an integrity verification procedure is set, a decryption procedure may be performed on the received concatenated data, or a data separation procedure may be performed on the concatenated data after the integrity verification procedure is performed. This is because the number or frequency of performing the decryption procedure or the integrity verification procedure can be minimized and the data processing time can be reduced only when the decryption procedure or the integrity verification procedure is applied to the concatenated data at once. In addition, when a decryption procedure or integrity protection procedure is applied to one concatenated data concatenated with several data in the above, a decryption procedure or integrity protection procedure is performed using a single COUNT value to perform a single set of security key values (COUNT). value or bearer identifier or security key) to enable single processing and shorten data processing time. For example, if data is not concatenated in the above, data processing time is very long because the decryption procedure or integrity protection procedure has to be performed multiple times based on different sets of security key values using a different COUNT value for each data. need. In addition, when applying or performing the data separation procedure to the concatenated data in the above, the data may be sequentially separated from the front of the concatenated data, and the data may be processed sequentially from the front and delivered to the upper layer device. For example, data concatenated to data to which one PDCP serial number is assigned should be first delivered to the upper layer device from the front.

- In the above, the data concatenation procedure or the separation procedure may be established for any bearer or higher layer device. If the data concatenation procedure is not configured, the transmitting PDCP layer device may allocate one PDCP serial number to one data (eg, PDCP SDU or PDCP PDU) received from a higher layer device, and one PDCP sequence Assign a number (for example, the value of the variable storing the COUNT value modulo the total size of the PDCP serial number, or the sending variable (COUNT value) modulo 2^ (the length of the PDCP serial number for the uplink)) It is possible to increment a variable for assignment by 1 and assign a serial number incremented by 1 to the variable for the next data. However, if the data concatenation procedure is set above, the transmitting PDCP layer device can allocate one PDCP serial number to a plurality of concatenated data when the data concatenation procedure is applied to data received from the higher layer device. and assigning one PDCP serial number, incrementing a variable for serial number assignment by 1, and assigning a serial number incremented by 1 to the variable for the next data (concatenated data or non-concatenated data), , when the data concatenation procedure is not applied to the data received from the upper layer device in the above, one PDCP serial number may be allocated to one unconcatenated data, and one PDCP serial number is allocated and the serial number A variable for assignment may be incremented by one, and a serial number incremented by one may be assigned to the next data (concatenated data or non-concatenated data) as the variable. If the data concatenation procedure is performed in the SDAP layer device in the above, PDCP data processing (for example, header compression procedure or integrity protection procedure or encryption procedure) is performed for one PDCP SDU (or SDAP data PDU) concatenated with a plurality of SDAP SDUs. It can be performed, a PDCP header is generated, and a PDCP serial number can be generated and allocated for the PDCP data PDU. If the data concatenation procedure is performed in the PDCP layer device in the above, a plurality of PDCP SDUs (eg, a compressed PDCP SDU to which a header compression procedure is applied when a header compression procedure is set) is concatenated to one concatenated PDCP SDU. For example, PDCP data processing (eg, integrity protection procedure or encryption procedure) may be performed, a PDCP header may be generated, and one PDCP serial number may be generated and assigned to the PDCP data PDU.

- In the above, if the data concatenation procedure or separation procedure is configured for a certain bearer, or for a bearer or higher layer device in which the data concatenation procedure is configured, the SDAP header or header compression procedure (eg, ROHC (Robust header compression), EHC (Ethernet) If it is set to use or add header compression) or data compression procedure (UDC, Uplink data compression), data processing speed may be adversely affected. This is because the transmitting end must add an SDAP header to each data or perform header compression, or the receiving end must remove the SDAP header for each data or decompress the header. Therefore, for each bearer or higher layer device (PDCP layer device or SDAP layer device or new layer device), it is possible to restrict the configuration to use the data concatenation procedure and the SDAP header, or not to set the header compression procedure or data compression procedure together. . For example, if the data concatenation procedure is set, it may be restricted so that the SDAP header or header compression procedure or data compression procedure cannot be set. As another method, if the SDAP header or header compression procedure or data compression procedure is set, it may be restricted so that the data concatenation procedure cannot be set.

- The data concatenation procedure proposed in the present invention may be activated or deactivated, or stopped or resumed according to an indication of an RRC message, MAC control information, or PDCCH.

14A, 14B, 14C and 14D are a header structure of a higher layer device suitable for the first embodiment ( FIGS. 11A and 11B ) or the third embodiment ( FIG. 13 ) of the data concatenation procedure proposed by the present invention, or It is a diagram showing the structure of a new field.

In FIG. 14A, a new field (eg, C field or E field) is defined in the header (eg, PDCP header or SDAP header, 1n-01) of the upper layer device, and whether there is a new field (1n-02) after it Whether or not the concatenation procedure is applied, or whether there is a data field immediately after it, etc. can be indicated.

Therefore, if the data concatenation procedure is not applied to data transmitted from a higher layer device (eg, a PDCP layer device or an SDAP layer device), the data is converted to a new field (eg, E field) in the structure 1n-03. Data can be structured by indicating that is not concatenated, indicating that there are no more new fields, or indicating that the data is immediately following.

When the data concatenation procedure is applied to data in the transmitting PDCP layer device in the above, a new field (eg, C field or E) in the header (eg, PDCP header or SDAP header) of the higher layer device as in 1n-05 field) to indicate whether there is a new field after it, whether a concatenation procedure is applied, or whether there is a data field immediately after it. And by defining new fields (eg, E field or LI field) and configuring as many as the number of concatenated data, the new fields are attached in front of concatenated data, and data are concatenated and positioned after the new fields. . In the header structure of 1n-05, the new fields 1n-02 define the size of each field according to the size of the byte unit, so that byte alignment can be performed. As another method, byte alignment is not defined in the size of new fields as in the structure of 1n-10, and if the size of the new fields is not in bytes, padding is added at the end to fit new fields (1n-02) ) can be configured. As another method, referring to FIG. 14B , a new field (eg, F field) is introduced as in the structure of 1n-15, so that the length field can be dynamically indicated with the first size or the second size. overhead can be reduced. Even in the structure of 1n-15, byte alignment can be performed by well defining the sizes of new fields as in 1n-05. As another method, byte alignment may be performed by adding padding to the structure of 1n-15 as in 1n-10. As another method, the last E field or LI fields in the header structure (1n-05 or 1n-10 or 1n-15) may be omitted. For example, if n pieces of data are concatenated, only n-1 new fields can be added. This is because, if the n-th data and the n+1-th data are separated by the length field for the n-th data, it is not necessary to know the length of the last data.

As another method, when the data concatenation procedure is applied to data in the transmitting PDCP layer device in the above, a new field (eg, PDCP header or SDAP header) in the header of the higher layer device as in 1n-20 C field or E field), it is possible to indicate whether there is a new field after it, whether a concatenation procedure is applied, or whether there is a data field immediately after it. In addition, new fields (eg, LI fields) are defined and configured as many as the number of concatenated data, the new fields are attached to the front of the data, and the data can be concatenated and located behind. In the header structure of 1n-20, the new fields 1n-02 can perform byte alignment by defining the size of each field according to the size of the byte unit. A structure such as 1n-20 is a useful structure when a number of data to be concatenated is set or determined. As another method, as in the structure of 1n-25, when the set number of concatenations cannot be satisfied, data may be transmitted without concatenation. If the size of the new fields is not defined as in 1n-10, and the size of the new fields is not in bytes, padding is added at the end to configure the new fields 1n-02 to fit the bytes. . As another method, overhead can be reduced by introducing a new field (eg, F field) as in the structure of 1n-15 so that the length field can be dynamically indicated with the first size or the second size. As another method, the last E field or LI fields in the header structure (1n-05 or 1n-10 or 1n-15) may be omitted. For example, if n pieces of data are concatenated, only n-1 new fields can be added. This is because, if the n-th data and the n+1-th data are separated by the length field for the n-th data, it is not necessary to know the length of the last data.

In the above, if the data concatenation procedure is performed in the SDAP layer device, when the SDAP header is configured in the SDAP layer device, since there is no reservation field in the downlink SDAP header and there is no reservation field in the uplink SDAP header, 1n- A field indicating whether there is a new field following, whether a concatenation procedure is applied, or whether there is a data field immediately following, such as 35 and 1n-40, is defined after the downlink SDAP header (1n-36), or uplink It can be defined in the link SDAP header. And like the other structures proposed above, new fields can be defined and a data concatenation procedure can be performed. As another method, a data concatenation procedure may be applied by defining new fields as shown in 1n-40 shown in FIG. 14D and attaching them after an uplink SDAP header or a downlink SDAP header. Alternatively, if the SDAP header is not set, the data concatenation procedure may be applied by defining new fields such as 1n-45 and placing them in front of the data.

The header structures or new field structures of the upper layer device proposed in FIGS. 14A, 14B, 14C, and 14D may be combined and applied to form a new structure.

Also, to facilitate the implementation of hardware processing in FIGS. 14A, 14B, 14C, and 14D, new fields for data concatenation or data separation (eg, length indicator (LI) fields) are fixed. The header structure may be designed to have a larger size. For example, a header of a fixed size by always inserting a predetermined number of the new fields (the predetermined number k may be predetermined or may be set in an RRC message) regardless of data concatenation. can be made to have

Alternatively, as in 1n-20, if data concatenation is not applied with a new field (eg, C field or E field) indicating whether data concatenation is applied or not, All of the new fields (LI field) are not used, that is, the new fields (LI field) are not included in the header, and a new field (eg, C) indicating whether data concatenation is applied or not is applied. field or E field), all of the new fields (LI field) of the fixed size are used, that is, the new fields (LI field) of the fixed size are included in the header. can make it happen

15A, 15B, 15C and 15D are diagrams showing the structure of a header structure or a new field of a higher layer device suitable for the second embodiment ( FIGS. 12A and 12B ) of the data concatenation procedure proposed by the present invention.

In FIG. 15A, a new field (eg, C field or E field) is defined in the header (eg, PDCP header or SDAP header, 1o-01) of the upper layer device, and whether there is a new field (1o-02) after it Whether or not a concatenation procedure is applied, or whether there is a data field immediately after it, etc. can be indicated.

Therefore, if the data concatenation procedure is not applied to the data transmitted from the upper layer device (for example, the PDCP layer device or the SDAP layer device), the data is transferred to a new field (for example, E field) in the structure 1o-03 Data can be structured by indicating that it is not concatenated, indicating that there are no more new fields, or indicating that the data is immediately following.

In the above, when the data concatenation procedure is applied to data in the transmitting PDCP layer device, a new field (eg, C field or E) in the header (eg, PDCP header or SDAP header) of the higher layer device as shown in 1o-05 field) to indicate whether there is a new field after it, whether a concatenation procedure is applied, or whether there is a data field immediately after it. Then, new fields (eg, E field or LI field) are defined and configured as many as the number of concatenated data, and the new fields are attached to the front of each data, and a new field is attached to the front of concatenated data in the same way. can be repeated to perform the data concatenation procedure. In the header structure of 1o-05 or 1o-10, the new fields 1o-02 define the size of each field according to the size of the byte unit to perform byte alignment. In addition, since the L field is located in front of each data, if there is other data after the length indicated by the L field, it means that there is another L field. Therefore, it is possible to operate without a problem even if the E field is not defined. However, like 1o-10, the E field can be defined and used for convenience of implementation. As another method, as in the structure of 1n-05, byte alignment is not defined in the size of new fields, and if the size of the new fields is not in bytes, padding is added at the end to fit new fields (1o-02) can be configured.

As another method, as in the structure of 1o-20 shown in FIG. 15B, a new field (eg, F field) is introduced so that the length field can be dynamically indicated with the first size or the second size. head can be reduced. Even in the structure of 1o-20, byte alignment can be performed by well defining the sizes of new fields as in 1o-05. As another method, in the structure of 1o-20, byte alignment may be performed by adding padding as in 1n-10. As another method, the last E field or LI fields such as 1o-15 in the header structure (1o-05 or 1o-10 or 1o-15) may be omitted. For example, if n pieces of data are concatenated, only n-1 new fields can be added. This is because, if the n-th data and the n+1-th data are separated by the length field for the n-th data, the length of the last data need not be known.

In the above, if the data concatenation procedure is performed in the SDAP layer device, when the SDAP header is set in the SDAP layer device, since there is no reservation field in the downlink SDAP header and there is no reservation field in the uplink SDAP header, 1o shown in FIG. 15c Define a field after the downlink SDAP header, such as -35 and 1o-40, indicating whether there is a new field after it, whether a concatenation procedure is applied, or whether there is a data field immediately following it (1o-36), or It can be defined in the uplink SDAP header. And like the other structures proposed above, new fields can be defined and a data concatenation procedure can be performed.

As another method, as shown in 1o-45 shown in FIG. 15D , new fields may be defined and attached after an uplink SDAP header or a downlink SDAP header to apply a data concatenation procedure. Alternatively, if the SDAP header is not set, the data concatenation procedure can be applied by defining new fields like 1o-45 and placing it in front of each data. can have

The header structures or new field structures of the upper layer device proposed in FIGS. 15A, 15B, 15C, and 15D may be combined and applied to form a new structure.

16 is a diagram comparing the data processing procedure proposed in the present invention with the data processing procedure in the next-generation mobile communication system in the present invention.

For example, assuming that the transmitting PDCP layer device receives 4 pieces of first data, second data, third data, and fourth data from a higher layer device, if the integrity protection procedure is set, each data is Integrity protection procedures can be respectively performed based on security key values, bearer identifiers, or COUNT values for the data, and a total of four integrity protection procedures can be performed based on a total of four COUNT values. If the encryption procedure is set in the above, the transmitting PDCP layer device may perform each encryption procedure based on the security key values or bearer identifier or the COUNT value for the data for each data, and based on a total of four COUNT values. In this way, a total of 4 encryption procedures can be performed. In addition, if the receiving PDCP layer device receives four first data, second data, third data, and fourth data to which the integrity protection procedure or encryption procedure is applied in the above, security key values for each data; A decryption procedure or integrity verification procedure can be performed based on the bearer identifier or the COUNT value for the data, and eventually the decryption procedure is performed 4 times or the integrity verification procedure is performed 4 times (1p-05).

If the data concatenation procedure of the higher layer device proposed in the present invention is set or applied, the transmitting PDCP layer device is the first data, the second data, the third data, and the fourth data to one data concatenated. When the integrity protection procedure is set for the data, the integrity protection procedure can be performed once for the data based on the security key values or bearer identifier or the COUNT value for the data, and based on one COUNT value, the four data Integrity protection procedures can be performed on one data that is concatenated with them. If the encryption procedure is set in the above, the transmitting PDCP layer device may perform the encryption procedure once for the concatenated data based on security key values, bearer identifiers, or COUNT values for the data, and one COUNT value Based on this, a total of one encryption procedure can be performed. In addition, if the receiving PDCP layer device receives the concatenated data (first data, second data, third data, and fourth data) to which the integrity protection procedure or encryption procedure has been applied, the concatenated data is secured A decryption procedure or integrity verification procedure may be performed based on key values, bearer identifiers, or a COUNT value for the data, and eventually, the decryption procedure is performed once or the integrity verification procedure is performed once (1p-10).

In the above, how much data can be concatenated may be concatenated as much as the size of data that can be processed at once when the modem of the terminal performs an integrity protection procedure, integrity verification procedure, encryption procedure, or decryption procedure. Alternatively, how much data can be concatenated in the above may be concatenated by a predetermined, defined, or set size.

As in 1p-10, when the data concatenation procedure is performed in the upper layer device, the number of times of processing the integrity protection procedure, integrity verification procedure, encryption procedure, or decryption procedure can be reduced as more data is concatenated, so that it is parallel to other data. As a result, more data can be processed, and eventually, the data processing speed can be increased and the data processing time can be shortened.

As shown in 1p-15 of FIG. 16, if the data concatenation procedure of the upper layer device proposed in the present invention is applied (1p-10), the number of times of generating a security key or key stream is also reduced, and a bus for data transport is applied. ) is also reduced, and the efficiency of the bus increases because the bus is used in large data units at once. In addition, the number of processing of the integrity protection procedure, integrity verification procedure, encryption procedure, or decryption procedure can be reduced. If the number of integrity protection procedures is reduced, the MAC-I field is also less generated. In addition, when performing data concatenation in the above, when the modem of the terminal performs the integrity protection procedure, integrity verification procedure, encryption procedure, or decryption procedure, if the size of data that can be processed at once is concatenated, the hardware for performing the above procedures The efficiency of the accelerator can be increased. In addition, since a PDCP header, RLC header, or MAC header is generated for concatenated data rather than a PDCP header, RLC header, or MAC header for each data, overhead in transmission resources can be reduced.

17A and 17B are diagrams illustrating gains of the data concatenation procedure proposed in the present invention from the viewpoint of an RLC layer device.

In addition, as in FIG. 17A , when the data concatenation procedure is not applied (1q-05), one RLC serial number must be assigned to each data, but when the data concatenation procedure proposed in the present invention is applied (1q-10), the concatenated data Since one RLC serial number is allocated to RLC, when operating the ARQ procedure in the RLC layer device, it is possible to efficiently operate the ARQ procedure with a small RLC serial number.

Therefore, if the data concatenation procedure is not applied as in FIG. 17a (1q-05), as shown in FIG. 17b, the RLC serial number, data, and a linked list for successful delivery for the ARQ procedure, Alternatively, the space of the RLC serial number to be searched becomes longer (1q-15, 1q-20), but when the data concatenation procedure proposed in the present invention is applied (1q-10), one RLC serial number is assigned to the concatenated data. Therefore, when operating the ARQ procedure in the RLC layer device, the linked list or RLC serial number space to be searched is greatly reduced as shown in FIG. 17b (1q-25, 1q-20), the RLC serial number search time is reduced can be shortened, data processing speed can be improved, and data processing time can be reduced.

18 is a diagram for explaining that the data concatenation procedure of the upper layer device proposed in the present invention does not affect the basic data processing procedure of the next-generation mobile communication system.

In FIG. 18, as shown in 1r-05, the length of data received from a higher layer device or header compression procedure is set, so that the length of header-compressed data is variable. And when the integrity protection procedure or encryption procedure is set for data having a variable length, the integrity protection procedure or encryption procedure is applied to the data, and a PDCP header, RLC header, or MAC header is generated and attached to the data. and data can be transmitted.

18, 1r-15, the data concatenation procedure proposed in the present invention can be applied to data received from a higher layer device, and the length of the concatenated data has a variable length. And when the integrity protection procedure or encryption procedure is set for concatenated data having a variable length, the integrity protection procedure or encryption procedure is applied to the data, and a PDCP header, RLC header, or MAC header is generated to generate the data. It can be attached to and transmitted data. Therefore, if the data received from the upper layer device in the basic data processing procedure 1r-10 is regarded as concatenated data, the basic data processing procedure can be reused as it is, so that the impact on the existing implementation can be minimized. It can also significantly increase data processing speed with minimal impact to hardware accelerators or hardware engine or modem designs.

In FIG. 19, a method of implementing the data concatenation function of the upper layer device proposed above without introducing new fields by extending the data concatenation function of the upper layer device proposed in the present invention while inheriting the characteristics of the data concatenation function of the higher layer device proposed above, or new fields We propose an implementation method that can have advantages similar to the data concatenation function of the upper layer device without it. That is, reduce the number of encryption procedures (or decryption procedures) or integrity protection procedures (or integrity verification procedures) as in the first embodiment, the second embodiment, or the third embodiment proposed above of the present invention, Alternatively, an implementation method capable of increasing the data processing speed of a terminal or a base station and lowering processing complexity by allowing them to be processed at once is proposed below.

The fourth embodiment of the data concatenation procedure proposed in FIG. 19 is different from the first, second, or third embodiment of the data concatenation procedure proposed in the present invention. Therefore, if the transmitting PDCP layer device performs the data concatenation procedure and transmits the concatenated data, the receiving PDCP layer device cannot separate the concatenated data. Therefore, in the fourth embodiment of the data concatenation procedure proposed in the present invention, a PDCP serial number or a COUNT value is assigned to each data received from a higher layer device in the transmitting PDCP layer device (if the PDCP layer device has a header When a compression procedure (or data compression procedure) is set, a header compression procedure (or data compression procedure) may be applied to each data before performing the data concatenation procedure, and the data concatenation procedure is applied to the compressed data After performing the data concatenation procedure for the plurality of different data, security key values, bearer identifiers, or each other By applying a plurality of different COUNT values, an integrity protection procedure or encryption procedure is performed on each data of concatenated data at once, and a data separation procedure is performed again on the concatenated data to generate a PDCP header for each data and lower layer We propose a method for transmitting data to a device.

That is, as shown in 1p-05 in FIG. 16, different COUNT values, encryption key values, or bearer identifier values are applied to each data to perform integrity protection (or integrity verification) or encryption (or decryption) procedures, respectively. A multi-array implementation method (eg, matrix operation), which is an implementation method for performing data at once, may be applied. Also, the receiving PDCP layer device may apply a decryption procedure or an integrity verification procedure to each data it receives based on security key values, a bearer identifier, or a COUNT value for the data. In another method, the receiving PDCP layer device also applies the data concatenation procedure to collect the received data and perform the data concatenation procedure, so that a plurality of data A decoding procedure or an integrity verification procedure may be applied to each data of concatenated data at once by applying a bearer identifier or a plurality of different COUNT values. And again, each data is separated from the concatenated data, and the data can be delivered to the upper layer device in the ascending order of the COUNT value (if a header compression procedure (or data compression procedure) is set in the PDCP layer device, each data A header decompression procedure (or data decompression procedure) may be applied to the data, and the decompressed data may be delivered to a higher layer device).

When performing the data concatenation procedure in the fourth embodiment of the data concatenation procedure of the present invention, the PDCP layer device performs the data concatenation procedure in the SDAP header or when performing the integrity protection procedure, integrity verification procedure, encryption procedure, or decryption procedure. It may be characterized in that it is not applied to SDAP control data (SDAP control PDU) or PDCP control data (PDCP control PDU). Because an encryption procedure or a decryption procedure is not applied to the SDAP header or SDAP control data, if the SDAP header or SDAP control data is concatenated with other data, implementation complexity increases when the concatenated data is encrypted or decrypted because it can be done In addition, since an encryption procedure, a decryption procedure, an integrity protection procedure, or an integrity verification procedure is not applied to the PDCP control data, when the PDCP control data is concatenated with other data, the concatenated data is encrypted or decrypted or an integrity protection procedure or This is because implementation complexity can be increased when performing the integrity verification procedure.

As another method, when the SDAP header is set in the SDAP layer device, the SDAP header of each data may be excluded when performing the data concatenation procedure. This is because the encryption procedure or the decryption procedure is not applied to the SDAP header. For example, the transmitting PDCP layer device may apply the data concatenation procedure of the fourth embodiment proposed above to data except for the SDAP header for each data received from the higher layer device. For example, the receiving PDCP layer device may apply the data concatenation procedure of the fourth embodiment proposed above to data except for the SDAP header to each data received from the lower layer device. In the above, when an integrity protection procedure is set for SDAP control data, the integrity protection procedure may be applied, or when an encryption procedure is set, the encryption procedure may not be applied. However, when the integrity protection procedure is set to the PDCP control data in the above, the integrity protection procedure may not be applied, or the encryption procedure may not be applied when the encryption procedure is set. As another method, when the integrity protection procedure is set to the SDAP control data, the integrity protection procedure may not be applied, or the encryption procedure may not be applied when the encryption procedure is set.

In another method, when performing the data concatenation procedure in the fourth embodiment of the data concatenation procedure of the present invention, the PDCP layer device performs the data concatenation procedure on the PDCP control data (PDCP control) when performing the integrity protection procedure or the integrity verification procedure. PDU), and the data concatenation procedure may be applied to the SDAP header or SDAP control data (SDAP control PDU). This is because the integrity protection or verification procedure is applied to the SDAP header or SDAP control data, but the integrity protection or verification procedure is not applied to the PDCP control data (eg, ROHC feedback or EHC feedback or PDCP status report). For example, if the PDCP control data is concatenated with other data, implementation complexity can be increased when integrity protection or verification procedures are performed on the concatenated data. In addition, the PDCP layer device may not apply the data concatenation procedure to the SDAP header or SDAP control data or PDCP control data (PDCP control PDU) when performing the encryption or decryption procedure. This is because the encryption or decryption procedure is not applied to the SDAP header, SDAP control data, or PDCP control data (eg, ROHC feedback or EHC feedback or PDCP status report). For example, if the SDAP header, SDAP control data, or PDCP control data is concatenated with other data, implementation complexity may increase when integrity protection or verification procedures are performed on the concatenated data.

For example, when the transmitting PDCP layer device performs the integrity protection procedure, the data concatenation procedure of the fourth embodiment proposed above is applied to the data including the SDAP header or SDAP control data to each data received from the upper layer device. can For example, when the receiving PDCP layer device performs the integrity verification procedure, the data concatenation procedure of the fourth embodiment proposed above is applied to the data including the SDAP header or SDAP control data to each data received from the lower layer device. can

For example, when performing the encryption procedure, the transmitting PDCP layer device performs the data concatenation procedure of the fourth embodiment proposed above for data except SDAP control data or SDAP header for each data received from the upper layer device. can be applied For example, when the receiving PDCP layer device performs the decoding procedure, for each data received from the lower layer device, except for SDAP control data or for data other than the SDAP header, the data concatenation procedure of the fourth embodiment proposed above is performed. can be applied

If only the encryption procedure is set in the PDCP layer device as shown in 1s-05 of FIG. 19, the fourth embodiment of the present invention is applied to apply the data concatenation procedure to the data received from the upper layer device and to the concatenated data By implementing multiple arrays, each data can be encrypted at once with different security key values (eg, COUNT values). In addition, by separating the concatenated data, a PDCP header may be individually configured for each data, and each data may be transmitted to a lower layer device by concatenating it in front.

If only the integrity protection procedure is set in the PDCP layer device as shown in 1s-10 of FIG. 19, the data concatenation procedure is applied to the data received from the higher layer device by applying the fourth embodiment of the present invention, and the concatenated data is By implementing multiple arrays, integrity protection procedures can be performed on each data at once with different security key values (eg, COUNT values). Then, by separating the concatenated data, each 4-byte long MAC-I field generated by the integrity protection procedure for each data is spliced at the end of each data, and the PDCP header is individually configured and spliced in front to connect each data. It can be passed to lower layer devices.

If the integrity protection procedure and encryption procedure are set in the PDCP layer device as shown in 1s-15 of FIG. 19, the data concatenation procedure is applied to the data received from the upper layer device by applying the fourth embodiment of the present invention, and the concatenated With multiple array implementations for data, integrity protection procedures can be performed on each data at once with different security key values (eg, COUNT values). In addition, for each data of the concatenated data, each 4-byte MAC-I field generated by the integrity protection procedure may be spliced at the end of each data, and concatenated data may be reconstructed. With respect to the concatenated data reconfigured above, an encryption procedure can be applied to each data at once with different security key values (eg, COUNT values) in a multiple array implementation. In addition, by separating the concatenated data, a PDCP header may be individually configured for each data, and each data may be transmitted to a lower layer device by concatenating it in front.

In the fourth embodiment proposed by the present invention, after performing a data concatenation procedure in the transmitting or receiving PDCP layer device, an integrity protection procedure, an integrity verification procedure, an encryption procedure, or a decryption procedure are performed. The processing time can be shortened. However, since the concatenated data is separated again and each data is transmitted to the lower layer device, the space of the RLC serial number or the size of the linked list cannot be reduced when searching the linked list implemented in the RLC layer device.

20 is a diagram illustrating a data loss problem that may occur when a terminal configured with a data concatenation function proposed in the present invention performs a handover procedure.

As in 1t-05 of FIG. 20 , it may be assumed that data corresponding to PDCP serial numbers (or COUNT values) 0, 1, and 2 are transmitted from the transmitting PDCP layer device of the AM DRB. And the RLC layer device (RLC layer device operating in AM mode) connected to the PDCP layer device has received the ACK (confirmation indicator that it has been successfully delivered) for the data corresponding to No. 0, and still said Nos. 1 and 2 It can be assumed that the ACK corresponding to . However, in reality, it can be assumed that the receiving PDCP layer device has received data corresponding to the PDCP serial numbers (or COUNT values) 0, 1, and 2. In this situation, upon receiving a handover command message (eg, RRCReconfiguration message), the transmitting PDCP layer device performs a PDCP re-establishment procedure, and from the first data for which successful delivery is not received from the lower layer device (RLC layer device) Start retransmission. When performing the data concatenation procedure proposed in the present invention in the PDCP re-establishment procedure, if the existing (or initially) PDCP serial number (or COUNT value) is different from the concatenated data based on the concatenation data, the concatenation procedure is newly performed 1t- 10, data loss may occur. Because the data corresponding to PDCP serial numbers (or COUNT values) 1 and 2 are already received from the receiving PDCP layer device when the data concatenation procedure is newly performed as in 1t-10 and transmitted, the PDCP serial number (or This is because the data corresponding to the COUNT value) may be assumed as duplicate reception in the duplicate detection procedure and the data may be discarded. In that case, even though data 6 and data 7 (data6, data7, 1t-15) are the first received data, since the duplicate detection procedure is performed based on the PDCP serial number (or COUNT value), the data will be discarded, and data loss will occur. can happen

Therefore, in the present invention, when the data concatenation procedure proposed in the present invention is performed in the PDCP layer device or when the data concatenation procedure is performed in the PDCP layer device, if the PDCP re-establishment procedure is triggered or if retransmission is to be performed, retransmission is required. For the data corresponding to the PDCP serial number (or COUNT value) to be transmitted, we propose a procedure for re-transmitting the concatenated data as it is when it is first transmitted. A more specific procedure is suggested below.

As shown in 1e-85 in FIG. 5 of the present invention, when the terminal receives a handover command message (eg, RRCReconfiguration message) from the base station, or when a data concatenation procedure is set in the PDCP layer device, or data connection procedure in the PDCP layer device The following proposes a PDCP re-establishment procedure that prevents data loss while performing , or when a PDCP re-establishment procedure is indicated in the RRC message.

- If the data concatenation procedure or data separation procedure is set for the PDCP layer device in the above, the UE may perform the data concatenation function in the higher layer device, and in the above, if the UE indicates a handover RRC message (RRCReconfiguration) is received from the base station, or if ReconfigurationWithSync (handover indicator) is included in the RRC message, or if an indicator to reestablish PDCP layer device (PDCP re-establishment) is included in the RRC message (reestablishPDCP), or the If the RRC message includes security configuration information (security config) for changing the security key, the terminal derives a new security key from the RRC layer device based on the security configuration information and applies the security key to each PDCP layer device. there is. In addition, the UE may perform a PDCP re-establishment procedure in the PDCP layer device. When performing the PDCP re-establishment procedure in the above, the UE may newly apply and transmit the data processing procedure of the PDCP layer device based on the new security key for data to be retransmitted or data to be transmitted for AM DRB. For example, specifically, in the PDCP re-establishment procedure, the UE may apply the data processing procedure of the PDCP layer device to retransmitted data and newly transmitted data as follows.

■ When re-applying the data processing procedure (header compression procedure, integrity protection procedure, or encryption procedure) of the PDCP layer device to the data to be retransmitted in the PDCP re-establishment procedure based on the new security key, the data concatenation procedure is set If yes, or if the data concatenation procedure was performed on previously transmitted data, if a header compression procedure was set when new data to be retransmitted If the data concatenation procedure is performed again in the same way as in the above, and if the integrity protection procedure is set for the identically concatenated data, the integrity protection procedure is newly performed on the concatenated data based on the new security key, or the encryption procedure is set If so, an encryption procedure can be performed on the concatenated data based on the new security key. For example, in the transmitting PDCP layer device, the first data and the second data are configured as PDCP serial numbers No. 1 and transmitted, and the third data is configured as No. 2 and transmitted. The PDCP serial numbers 1 and 2 If successful delivery is not confirmed from the lower layer device for the first time, a retransmission procedure (transfer to the lower layer device) is performed in the PDCP re-establishment procedure. In the above, it can be assumed that the receiving end has actually received data corresponding to PDCP serial number 1 and has not received data corresponding to PDCP serial number 2. However, if, in the retransmission procedure of the PDCP re-establishment procedure, the first data, the second data, and the third data are concatenated and transmitted as PDCP serial number 1, the receiving end receives the PDCP serial number 1 Since the data has already been received before, the data can be detected as duplicate received data and discarded. That is, data loss may occur because the third data is concatenated to PDCP serial number 1 by newly concatenating the concatenation function for the data retransmitted in the PDCP re-establishment procedure above. Therefore, when the procedure of the PDCP layer device is newly applied with the new security key to the data retransmitted by the PDCP re-establishment procedure above, the data concatenation function is concatenated the same as the previously transmitted data, and based on the new security key, the PDCP layer device procedure must be re-applied.

■ When applying the data processing procedure (header compression procedure, integrity protection procedure, or encryption procedure) of the PDCP layer device to the data to be newly transmitted in the PDCP re-establishment procedure based on the new security key, if the data concatenation procedure is set If a header compression procedure is set when constructing data to be transmitted, a header compression procedure is performed, or a data concatenation procedure (data may or may not be concatenated) is performed, or concatenated data or concatenated data If the integrity protection procedure is set for the unconcatenated data, the integrity protection procedure is newly performed based on the new security key for the concatenated or unconcatenated data, or if the encryption procedure is set, the concatenated data or the unconcatenated data An encryption procedure can be performed on data based on a new security key, and a transmission procedure (transfer to a lower layer device) is performed.

■ Following the above procedure, for example, window state variables are initialized for UM DRB, and for data that has not yet been transmitted to a lower layer device or data for which the PDCP discard timer has not expired, Transmission or retransmission can be performed by compressing, encrypting, or performing integrity protection based on the header (or data) compression context or security key, and if the reorder timer is running, it stops and initializes and PDCP SDU or PDCP PDU) can be sequentially processed and delivered to the upper layer device. For AM DRB, window state variables are not initialized, and the first data (PDCP SDU or PDCP PDU) for which successful delivery is not confirmed from the lower layer device. ) to the PDCP serial number or COUNT value in ascending order based on the header (or data) compression context or security key of the target base station, or by performing encryption or integrity protection, transmission or retransmission can be performed. .

The problem described in paragraph 20 of the present invention and the corresponding PDCP re-establishment procedure can be applied when the target base station to which the terminal needs to perform handover supports the data concatenation function proposed in the present invention. For example, when the source base station supports the data concatenation function or the target base station supports the data concatenation function, the PDCP re-establishment procedure may be performed.

In the following of the present invention, when the handover procedure is performed from the source base station supporting the data concatenation function to the target base station supporting the data concatenation function by extending the handover procedure proposed above, in the source base station that does not support the data concatenation function When performing a handover procedure to a target base station supporting the data concatenation function, when performing a handover procedure from a source base station supporting the data concatenation function to a target base station not supporting the data concatenation function, or supporting the data concatenation function An efficient PDCP re-establishment procedure is proposed when a handover procedure is performed from a source BS that does not support the data concatenation function to a target BS that does not support the data concatenation function.

When the terminal receives a handover command message (eg, RRCReconfiguration message) from the base station as shown in 1e-85 in FIG. 5 of the present invention, or when a data concatenation procedure is set or not set in the PDCP layer device, or A PDCP re-establishment procedure for preventing data loss when the PDCP layer device is performing or not performing a data connection procedure or when a PDCP re-establishment procedure is indicated in the RRC message is proposed as follows.

- If the data concatenation procedure or data separation procedure is set for the PDCP layer device in the above, the UE may perform the data concatenation function in the higher layer device, and in the above, if the UE indicates a handover RRC message (RRCReconfiguration) is received from the base station, or if ReconfigurationWithSync (handover indicator) is included in the RRC message, or if the RRC message includes an indicator (reestablishPDCP) for reestablishing a PDCP layer device (PDCP re-establishment), or the If the RRC message includes security configuration information (security config) for changing the security key, the terminal derives a new security key from the RRC layer device based on the security configuration information and applies the security key to each PDCP layer device. there is. In addition, the UE may perform a PDCP re-establishment procedure in the PDCP layer device. When the UE performs the PDCP re-establishment procedure in the above, for data to be retransmitted for AM DRB or data to be transmitted (or for data to be retransmitted or data to be transmitted for UM DRB), based on the new security key, a new PDCP layer device can apply and transmit data processing procedures of For example, specifically, in the PDCP re-establishment procedure, the UE may apply the data processing procedure of the PDCP layer device to retransmitted data and newly transmitted data as follows. (For example, when performing a handover procedure from a source base station supporting the data concatenation function to a target base station supporting the data concatenation function, or from a source base station not supporting the data concatenation function to a target base station supporting the data concatenation function when performing the over procedure)

■ When re-applying the data processing procedure (header compression procedure, integrity protection procedure, or encryption procedure) of the PDCP layer device to the data to be retransmitted in the PDCP re-establishment procedure based on the new security key, the data concatenation procedure is set If yes, or if the data concatenation procedure was performed on previously transmitted data, if a header compression procedure was set when new data to be retransmitted If the data concatenation procedure is performed again in the same way as in the above, and if the integrity protection procedure is set for the identically concatenated data, the integrity protection procedure is newly performed on the concatenated data based on the new security key, or the encryption procedure is set If so, an encryption procedure can be performed on the concatenated data based on the new security key. For example, in the transmitting PDCP layer device, the first data and the second data are configured as PDCP serial number No. 1 and transmitted, and the third data is configured as No. 2, and the PDCP serial number No. 1 is transmitted. If successful delivery from the lower layer device is not confirmed for and No. 2, the retransmission procedure (transfer to the lower layer device) is performed in the PDCP re-establishment procedure. In the above, it can be assumed that the receiving end has actually received data corresponding to PDCP serial number 1 and has not received data corresponding to PDCP serial number 2. However, if, in the retransmission procedure of the PDCP re-establishment procedure, the first data, the second data, and the third data are concatenated and transmitted as PDCP serial number 1, the receiving end receives the PDCP serial number 1 Since the data has already been received before, the data can be detected as duplicate received data and discarded. That is, since the concatenation function is newly concatenated with respect to the data retransmitted in the PDCP re-establishment procedure in the above, and the third data is concatenated with the PDCP serial number No. 1, data loss may occur. Therefore, when the procedure of the PDCP layer device is newly applied with the new security key to the data retransmitted by the PDCP re-establishment procedure above, the data concatenation function is concatenated the same as the previously transmitted data, and based on the new security key, the PDCP layer device procedure must be re-applied.

■ When applying the data processing procedure (header compression procedure, integrity protection procedure, or encryption procedure) of the PDCP layer device to the data to be newly transmitted in the PDCP re-establishment procedure based on the new security key, if the data concatenation procedure is set Alternatively, if a header compression procedure is set when constructing data to be transmitted, a header compression procedure is performed, or a data concatenation procedure (data may or may not be concatenated) is performed, or concatenated data or If the integrity protection procedure is set for the unconcatenated data, the integrity protection procedure is newly performed based on the new security key for the concatenated or unconcatenated data, or if the encryption procedure is set, the concatenated data or the unconcatenated data An encryption procedure can be performed based on the new security key for data that has not been transmitted, and a transmission procedure (delivered to a lower layer device) is performed.

■ Following the above procedure, for example, window state variables are initialized for UM DRB, and for data that has not yet been transmitted to a lower layer device or data for which the PDCP discard timer has not expired, Transmission or retransmission can be performed by compressing, encrypting, or performing integrity protection based on the header (or data) compression context or security key, and if the reorder timer is running, it stops and initializes and PDCP SDU or PDCP PDU) can be sequentially processed and delivered to the upper layer device. For AM DRB, window state variables are not initialized, and the first data (PDCP SDU or PDCP PDU) for which successful delivery is not confirmed from the lower layer device. ) to the PDCP serial number or COUNT value in ascending order based on the header (or data) compression context or security key of the target base station, compressed or encrypted, or integrity protection is performed to perform transmission or retransmission.

- If the data concatenation procedure or data separation procedure is not set for the PDCP layer device in the above (or the data concatenation procedure or data separation procedure has been previously set, but the data concatenation procedure or data separation procedure in the RRC message (RRCReconfiguration message)) is not configured), the terminal may not perform a data concatenation function in the higher layer device, and in the above, if the terminal receives an RRC message (RRCReconfiguration) indicating handover from the base station, or in the RRC message If ReconfigurationWithSync (handover indicator) is included, or if an indicator (reestablishPDCP) for reestablishing a PDCP layer device is included in the RRC message, or security configuration information for changing a security key in the RRC message (security config) is included, the UE may derive a new security key based on the security configuration information in the RRC layer device and apply the security key to each PDCP layer device. In addition, the UE may perform a PDCP re-establishment procedure in the PDCP layer device. When the UE performs the PDCP re-establishment procedure in the above, for data to be retransmitted for AM DRB or data to be transmitted (or for data to be retransmitted or data to be transmitted for UM DRB), based on the new security key, a new PDCP layer device can apply and transmit data processing procedures of For example, specifically, in the PDCP re-establishment procedure, the UE may apply the data processing procedure of the PDCP layer device to retransmitted data and newly transmitted data as follows. (For example, when a handover procedure is performed from a source base station supporting the data concatenation function to a target base station not supporting the data concatenation function, or when a source base station that does not support the data concatenation function does not support the data concatenation function. handover procedure to base station)

■ When re-applying the data processing procedure (header compression procedure, integrity protection procedure, or encryption procedure) of the PDCP layer device to the data to be retransmitted in the PDCP re-establishment procedure based on the new security key, the terminal transmits the previously transmitted data. If a data concatenation procedure is performed on data, if a header compression procedure is set when composing data to be retransmitted, perform a new header compression procedure again, or deconcatenate data concatenated during transmission (or data separation) and (or without applying the data concatenation function) for unconcatenated data (by assigning different PDCP serial numbers or COUNT values), if integrity protection procedures are established, for each unconcatenated data, The integrity protection procedure is newly performed, or, if the encryption procedure is set, the encryption procedure may be performed based on the new security key for each non-connected data. For example, in the transmitting PDCP layer device, the first data and the second data are configured as PDCP serial numbers No. 1 and transmitted, and the third data is configured as No. 2 and transmitted. The PDCP serial numbers 1 and 2 If successful delivery is not confirmed from the lower layer device for the first time, a retransmission procedure (transfer to the lower layer device) is performed in the PDCP re-establishment procedure. In the above, when the procedure of the PDCP layer device is newly applied with the new security key to the data retransmitted by the PDCP re-establishment procedure, the concatenation is released (or data is separated) for the previously transmitted concatenated data, or the data concatenation function is applied. Instead, the first data is configured as PDCP serial number (or COUNT value) No. 1, the second data is configured as PDCP serial number (or COUNT value) No. 2, and the third data is configured as PDCP By configuring the serial number (or COUNT value) as number 3, the data processing procedure of the PDCP layer device can be applied based on the new security key and transmitted to the lower layer device. In the above, since the transmitting PDCP layer device or the receiving PDCP layer device is reset so that the data concatenation function is not used, the concatenated data can be regarded as data that has not been successfully transmitted or received, or the PDCP serial number corresponding to the concatenated data Alternatively, the COUNT value may be considered unused, or may not be reflected in the window variable update. For example, the terminal does not apply the data concatenation function as described above from the first data (or the first concatenated data) that does not receive an indication that it has been successfully delivered from the lower layer device when performing the PDCP re-establishment procedure, Retransmission or retransmission can be performed by re-assigning a PDCP serial number (or COUNT value) to each data in ascending order and processing the data. In the handover procedure, the source base station (or target base station) considers the concatenated data as unsuccessfully received data (or from the first concatenated data among the received data in the ascending order of the PDCP serial number or COUNT value) Data that have not been received (including the first concatenated data), or the PDCP serial number or COUNT value corresponding to the data may be considered unused (or not received). Alternatively, the data may not be reflected in the window variable update, or the data may not be transmitted to the target base station. In addition, in the above, the source base station (or target base station) may send a PDCP status report for the data successfully received or not successfully received as described above to the terminal. In this way, even when a handover procedure is performed to a target base station that does not support the data concatenation function proposed in the present invention, a handover procedure without data loss can be performed.

■ When applying the data processing procedure (header compression procedure, integrity protection procedure, or encryption procedure) of the PDCP layer device to the data to be newly transmitted in the PDCP re-establishment procedure based on the new security key, if the data concatenation procedure is set Alternatively, if a header compression procedure is set when constructing data to be transmitted, a header compression procedure is performed, or a data concatenation procedure (data may or may not be concatenated) is performed, or concatenated data or If the integrity protection procedure is set for the unconcatenated data, the integrity protection procedure is newly performed based on the new security key for the concatenated or unconcatenated data, or if the encryption procedure is set, the concatenated data or the unconcatenated data An encryption procedure can be performed based on the new security key for data that has not been transmitted, and a transmission procedure (delivered to a lower layer device) is performed.

■ Following the above procedure, for example, window state variables are initialized for UM DRB, and for data that has not yet been transmitted to a lower layer device or data for which the PDCP discard timer has not expired, Transmission or retransmission can be performed by compressing or encrypting header (or data) based on the compression context or security key, or performing integrity protection. Alternatively, PDCP PDU) can be sequentially processed and delivered to the upper layer device. For AM DRB, window state variables are not initialized, and from the first data (PDCP SDU or PDCP PDU) for which successful delivery is not confirmed from the lower layer device. In the ascending order of the PDCP serial number or COUNT value, transmission or retransmission can be performed by compressing or encrypting the header (or data) based on the compression context or security key of the target base station or performing integrity protection.

In the following of the present invention, another embodiment of allocating a PDCP serial number (or COUNT value) to concatenated data when a data concatenation function is applied in a PDCP layer device is proposed.

In the above embodiment, when assigning the PDCP serial number (or COUNT value), the transmitting PDCP layer device may allocate the PDCP serial number (or COUNT value) in consideration of the number of concatenated data. Even if the data concatenation function is performed for a plurality of PDCP SDUs as proposed in the present invention, one PDCP serial number (or COUNT value) is assigned to each PDCP SDU, and the number of concatenated data to be mapped or used is considered. Thus, the PDCP serial number of the actually transmitted PDCP PDU can be allocated in a new way. For example, when the first data (eg, PDCP SDU) is transmitted as one PDCP PDU, PDCP serial number (or COUNT value) 0 is allocated and transmitted, and then the second data (PDCP SDU) and When the third data (PDCP SDU) is concatenated, when the concatenated data is transmitted as one PDCP PDU, the PDCP serial number (or COUNT value) may be assigned as No. 1 . Then, when the fourth data (PDCP SDU) is transmitted as one PDCP PDU, the PDCP serial number (or COUNT value) No. 3 can be assigned because two data are concatenated in the previous data (PDCP PDU). there is. Also, when the fifth data (PDCP SDU) and the sixth data (PDCP SDU) are concatenated later, when the concatenated data is transmitted as one PDCP PDU, the PDCP serial number (or COUNT value) is assigned No. 4 can do. Then, when the seventh data (PDCP SDU) and the eighth data (PDCP SDU) are concatenated and transmitted as one PDCP PDU, since two data are concatenated and transmitted in the previous data (PDCP PDU), the PDCP serial number (or COUNT value) 6 can be assigned.

Accordingly, the receiving end receiving the PDCP PDUs receives the first data and considers the PDCP serial number (or COUNT value) as No. 0, and considers the second data as the PDCP serial number (or COUNT value) as No. 1 and consider the third data as PDCP serial number (or COUNT value) No. 2, consider the fourth data as PDCP serial number (or COUNT value) No. 3, and consider the fifth data as PDCP serial number (or COUNT value) No. 3 Consider number (or COUNT value) as number 4, the sixth data as PDCP serial number (or COUNT value) as number 5, and the seventh data as PDCP serial number (or COUNT value) as number 6 and the eighth data may be considered as the PDCP serial number (or COUNT value) number 7

That is, in the above embodiment, when the transmitting end updates the transmission window variable for allocating the PDCP serial number (or COUNT value), it increases by the number of PDCP SDUs received from the upper layer device (or increases each time the PDCP SDU is received). ), or increase by the number of PDCP SDUs transmitted to the lower layer (or increase each time each PDCP SDU is transmitted), or when concatenated PDCP SDUs are transmitted as one PDCP PDU, the concatenated PDCP included in the The PDCP serial number (or COUNT value) of the PDCP SDU having the smallest PDCP serial number (or COUNT value) among the SDUs may be included in the header of the PDCP PDU as the PDCP serial number and transmitted.

Therefore, when the receiving end receives the PDCP PDU, it first checks whether the data concatenation function is applied, and when the data concatenation function is applied, it separates the PDCP SDUs from the PDCP PDU, and starts from the PDCP serial number included in the PDCP header. For each of the separated PDCP SDUs, the PDCP serial number is incremented by 1 in ascending order, each PDCP serial number (or COUNT value) is mapped or set, reception window variables are managed, and reception data processing can be performed.

In the following of the present invention, methods for reducing the data processing complexity of the ARQ operation performed by the RLC layer device of the AM DRB configured in the terminal are proposed.

The following fifth embodiment is proposed as an embodiment for reducing the data processing complexity of the ARQ operation performed by the RLC layer device of the AM DRB proposed by the present invention. In the fifth embodiment, the base station may release the data segmentation function in the RLC layer device configuration information when configuring the bearer configuration information with the RRC message to the terminal as shown in FIG. 5, or use the data partitioning function. We suggest setting it not to. For example, by introducing an indicator in the RRC message or in the RLC layer device configuration information, the data partitioning function may be configured to be used or not. Therefore, if the data segmentation method is set not to be used, the terminal cannot transmit data due to insufficient uplink transmission resources. Therefore, when data must be segmented, the data segmentation method is not performed and the data is not transmitted instead of performing the data segmentation method. It can be transmitted including padding.

If the data partitioning function is set not to be used, only one type of RLC header is used in the RLC layer device having various RLC header types according to the data partitioning procedure. Accordingly, since the header of each layer device has a fixed size in the PDCP layer device, the RLC layer device, or the MAC layer device, the UE can increase the data processing speed. For example, if a fixed-size header is used in SDAP, PDCP, RLC, or MAC layer devices as described above when applying a hardware accelerator with high efficiency to data processing when repeating the same size or operation as repeated procedures It is possible to increase the processing efficiency and reduce the data processing speed. In addition, as described above, if the data segmentation function is not used in the RLC layer device, the RLC status report configuration method can be simplified based on the bitmap, thereby reducing the complexity of the ARQ operation. For example, there is no need to consider the segmented data when configuring the RLC status report (that is, there is no need to consider the segment offset (SO) field or the segmentation information (SI) field), and only the RLC serial number field based on the bitmap Because it can be considered, ARQ operation can be simplified. The bitmap-based RLC status report proposed above may be configured as follows.

- In the present invention, the RX_Next variable is a variable indicating the value of increasing 1 to the RLC serial number corresponding to the last RLC SDU completely received in order or the value of the next RLC serial number of the RLC serial number, and RX_Highest_Status is the RLC status report. The highest RLC serial number value that can be indicated by the ACK_SN value may be indicated.

- The first configuration method is as follows.

◆ The value of ACK_SN in the RLC status report may be set to the RLC serial number of the next RLC SDU that is not indicated to be lost in the RLC status report or has not yet been received. As another method, the value of ACK_SN may be set to the value of the RLC serial number of RX_Highest_Status. In another method, the value of ACK_SN is the serial number of the first lost RLC SDU, or the RLC serial number of the first data that is not delivered to the upper layer device, or the RLC serial number of the last data delivered to the upper layer device by adding 1 Alternatively, it may be set to an RLC serial number value of RX_Highest_Status.

◆ For RLC SDUs having a size of RLC serial number greater than or greater than RX_NEXT or less than RX_Highest_Status

● Set the length of the bitmap field to a length from the RLC serial number not including the first lost RLC SDU to a multiple of 8 including the RLC serial number of the last data out of order, or the length of the bitmap field From the RLC serial number that does not include the first lost RLC SDU to the RLC serial number of the RLC SDU in which the size of RLC control data (RLC status report) matches the size of the transmission resource (transmission resource indicated by the lower layer device) may be set to the length of , and the length may be set according to the first of the above two cases.

● If RLC SDUs corresponding to the bitmap field are not successfully received, the bitmap field corresponding to the RLC SDU may be set to 0.

● If RLC SDUs corresponding to the bitmap field are successfully received, the bitmap field corresponding to the RLC SDU may be set to 1.

■ When transmitting the RLC status report configured as described above to the lower layer device, it may be transmitted to the lower layer device as the first RLC PDU of the transmitting RLC layer device. That is, if the highest priority is given to the RLC status report and the RLC status report is generated, it is transmitted to a lower layer device first so that transmission can be fast.

- The second configuration method is as follows.

■ For RLC SDUs having a size of RLC serial number greater than or equal to RX_NEXT or less than RX_Highest_Status, in ascending order of RLC serial number, starting from the RLC serial number value such as RX_Next, according to the transmission resource indicated by the lower layer device. RLC status reporting can be configured as follows.

◆ Starting from the RLC serial number value such as RX_Next, each RLC serial number is one-to-one from LSB (least significant bit or right) or MSB (most significant bit or left) in ascending order of bit values and RLC serial numbers of the bitmap. It can be a mapping.

◆ If RLC SDUs corresponding to the bitmap field are not successfully received, the bitmap field corresponding to the RLC SDU may be set to 0 (or 1).

◆ If RLC SDUs corresponding to the bitmap field are successfully received, the bitmap field corresponding to the RLC SDU may be set to 1 (or 0).

◆ The value of ACK_SN in the RLC status report may be set to the RLC serial number of the next RLC SDU that is not indicated to be lost in the RLC status report or has not yet been received. As another method, the value of ACK_SN may be set to the value of the RLC serial number of RX_Highest_Status. In another method, the value of ACK_SN is the serial number of the first lost RLC SDU, or the RLC serial number of the first data that is not delivered to the upper layer device, or the RLC serial number of the last data delivered to the upper layer device by adding 1 Alternatively, it may be set to an RLC serial number value of RX_Highest_Status.

◆ Set the length of the bitmap field to a length from the RLC serial number not including the first lost RLC SDU to a multiple of 8 including the RLC serial number of the last out-of-order data, or the length of the bitmap field can be set to the length from the RLC serial number not including the first lost RLC SDU to the RLC serial number of the RLC SDU in which the size of RLC control data (RLC status report) matches the size of the transmission resource, The length can be set according to the first satisfying case among the cases of .

◆ When transmitting the RLC status report configured as above to the lower layer device, it can be sent to the lower layer device as the first RLC PDU of the transmitting RLC layer device. That is, if the highest priority is given to the RLC status report and the RLC status report is generated, it is transmitted to a lower layer device first so that transmission can be fast.

As described above, the bitmap-based RLC status report proposed by the present invention may be defined as new RLC control data (RLC control PDU). For example, by defining a PDU type field value in the RLC header, RLC status report using ACK_SN, NACK_SN, NACK_RANGE, or SO fields and the bitmap-based RLC status report proposed in the present invention Each can be indicated so that they can be distinguished. In another method, a new indicator is introduced in the RLC header to indicate that the RLC status report using the ACK_SN, NACK_SN, NACK_RANGE, or SO fields can be distinguished from the bitmap-based RLC status report proposed in the present invention. there is.

The following sixth embodiment is proposed as an embodiment for reducing the data processing complexity performed by the RLC layer device of the UM DRB or AM DRB proposed by the present invention. In the sixth embodiment, the base station configures to use one RLC header format in the RLC layer device configuration information or to use a new RLC header format when configuring the bearer configuration information with the RRC message to the terminal as shown in FIG. It is proposed to give or to indicate a data partitioning method (or a type of data partitioning method, an SO field-based method (to be described later in FIG. 22) or an SI field-based method (to be described later in FIG. 24)) or a new function (set as another method Even without information, the terminal may use the method proposed in the sixth embodiment). For example, by introducing an indicator in the RRC message or in the RLC layer device configuration information, the sixth embodiment may be configured to be used or not to be used.

The sixth embodiment proposes a method in which only one type of RLC header can be used even if the data division procedure is used in an RLC layer device having various RLC header types according to the data division procedure. Accordingly, since the header of each layer device has a fixed size in the PDCP layer device, the RLC layer device, or the MAC layer device, the UE can increase the data processing speed. For example, if a fixed-size header is used in SDAP, PDCP, RLC, or MAC layer devices as described above when applying a hardware accelerator with high efficiency to data processing when repeating the same size or operation as repeated procedures It is possible to increase the processing efficiency and reduce the data processing speed.

A detailed method of the sixth embodiment of the present invention will be described with reference to FIGS. 23 and 24 .

21 is a diagram illustrating an SO-based segmentation operation that can be used in an RLC layer RLC AM mode or an RLC UM mode in the present invention.

In the present invention, a procedure and method for performing a segmentation operation based on a segment offset (SO) on a packet received from a higher layer in the RLC layer may be applied. The proposed method may be characterized in that an integrated division operation is performed without distinguishing each of the division operations in the case of first transmission and the case of retransmission. In addition, it may be characterized in that concatenation is not performed in the RLC layer. In addition, by introducing the SI field in the RLC header, whether the RLC SDU, the data part after the RLC header, is a complete RLC SDU without segmentation, the first segmented RLC SDU segment, or a segmented middle RLC SDU segment. Alternatively, it may be characterized in that it is possible to distinguish whether it is the last segmented RLC SDU segment. In addition, it may be characterized in that there is no Length field indicating the length in the RLC header.

In FIG. 21 , the RLC layer receives a PDCP PDU (RLC SDU, 1u-05) from the PDCP layer, which is a higher layer. The RLC SDU may be processed to a size indicated by the MAC layer, and if it is divided, it may be configured including header division information to compose an RLC PDU. The RLC PDU consists of an RLC header and an RLC payload (RLC SDU). The RLC header may include characteristics (data or control information) and division information of the RLC PDU, and may include a D/C field, a P field, an SI field, an SN field, and an SO field. In the above RLC UM mode that does not support ARQ, there is no P field and may be replaced with a reserved field.

The D/C (Data/Control) field is 1 bit and is used to indicate whether the configured RLC PDU is a control PDU or a data PDU.

The SN (Sequence Number) field indicates the serial number of the RLC PDU and may have a predetermined length. For example, it may have a length of 12 bits or 18 bits.

The Segment Offset (SO) field may have a size of 2 bytes, indicates at which position in the original RLC SDU segment the RLC SDU segment is segmented, and is used to indicate the first byte of the segmented segment.

In the P field, when a condition triggering polling at the transmitting end occurs, the P field may be set to 1 to enable the receiving end to perform an RLC status report. That is, ACK/NACK information for the RLC PDUs received so far can be transmitted to the transmitter.

When the RLC layer receives the RLC SDU of 1u-05, the RLC layer may directly insert an RLC SN into the RLC SDU, generate an RLC header, and create an RLC PDU. If a segmentation operation is required for a predetermined reason, the RLC PDU may be generated by updating the SI field such as 1u-10 or 1u-15 and adding the SO field to the RLC header. That is, after the segmentation operation, the SO field may or may not be added to the segmented segment according to a predetermined condition. The predetermined condition is determined according to the SI field, which will be described below. The predetermined reason for the need for the partitioning operation is that the size of the currently generated MAC subheader and MAC SDU is larger than the size of the transmission resource allocated by the MAC layer. may be the case In the above, the SN (Sequence Number) field is the serial number of the RLC PDU, or if necessary or configured, the PDCP SN may be reused. The Segment Offset (SO) field is a field having a predetermined length and may indicate what number of bytes the first byte of the RLC PDU data field (RLC SDU) segmented at the time of initial transmission is of the original RLC PDU data field (RLC SDU), , may indicate which byte the first byte of the re-segmented RLC PDU data field is of the original RLC PDU data field (RLC SDU) even during retransmission. In the above, the SO field may have a fixed length (eg, 2 bytes) or set by an RRC message (eg, RRCConnectionSetup or RRCConnectionReconfiguration message, 3e-10, 3e-40, 3e-75). can be In the above, the Segmentation Information (SI) field may be defined as follows or may be named with a different name.

When the SI field is 00, it indicates a complete unsegmented RLC SDU. In this case, the SO field is not required in the RLC header. When the SI field is 01, it indicates the first segmented RLC SDU segment. In this case, the SO field is not required in the RLC header. This is because, in the case of the first segment, the SO field always indicates 0. When the SI field is 10, it indicates the last segmented RLC SDU segment. In this case, the SO field is required in the RLC header. When the SI field is 11, it indicates a segmented middle RLC SDU segment. In this case, the SO field is required in the RLC header. The mapping relationship between the 2 bits and the 4 pieces of information (complete RLC SDU, the first segment, the last segment, and the middle segment) may have a total of 4x3x2x1 = 24, and the above shows one example. The present invention includes all of the above 24 mapping cases. If the RLC PDUs of 1u-10 and 1u-15 have failed in transmission, retransmission can be performed. In this case, if transmission resources are insufficient, re-segmentation is performed as in 1u-20, 1u-25, 1u-30. can During the re-segmentation, the SI field and the SO field of the newly generated RLC PDUs 1u-20, 1u-25, 1u-30 may be updated. In the case of 1u-20, since it is the first segment, the SI is updated to 01, and the SO field is not needed.

In the case of 1u-25, since it is the middle segment, the SI is updated to 11, and the SO field can indicate which byte the first byte of the RLC PDU data field (RLC SDU) is of the original RLC PDU data field (RLC SDU). Update to 300 so that In the case of 1u-30, since it is the last segment, the SI is updated to 10, and the SO field is set to indicate which byte the first byte of the RLC PDU data field (RLC SDU) is of the original RLC PDU data field (RLC SDU). Update to 600.

22 is a diagram illustrating a data processing operation to which the SO-based partitioning method of the RLC AM mode or the RLC UM mode proposed in the present invention is applied.

In FIG. 22 , when an IP packet arrives at the PDCP layer, a PDCP header may be attached, and a PDCP PDU (or RLC SDU, 1v-05) may be transmitted to the RLC layer. The RLC layer may first generate an RLC header, allocate an RLC serial number, configure the RLC header to complete the RLC PDU 1v-10, and then transmit it to the MAC layer. The MAC layer calculates the size of the MAC SDU (or RLC PDU) to configure the L field, sets a corresponding logical channel identifier, etc., configures the MAC subheader 1v-15, and configures the buffer 1v-20. can be stored in Therefore, data packets received in the PDCP layer in this way can be stored in a buffer by performing data pre-processing before receiving the transmission resource (UL grant) from the base station, or immediately after receiving the transmission resource. On-the-fly processing may also be performed.

If uplink transmission resources (UL grant 1, 1v-25) are received from the base station, but the division operation needs to be performed due to insufficient uplink transmission resources, after performing the division operation as in 1v-30, the RLC header of each segment is After setting the SI field according to the segment, the RLC header of the segments can be newly configured (1v-30, 1v35). And, as described with reference to FIG. 1u, an SO field must be added to the middle segment or the last segment other than the first segment and the offset thereof must be indicated, so the SO field can be added to the RLC header as in 1v-35. In addition, the MAC PDU configured to fit the uplink transmission resource may be transmitted. If the second uplink transmission resource (UL grant 2, 1v-45) is received, and the size of the transmission resource is insufficient and a split operation is required once again, it is applied to newly divided segments such as 1v-40 and 1v-50. The SI field is updated accordingly, the SO field is updated or added, and the RLC header is configured respectively. Then, the MAC PDU is configured and transmitted according to the uplink transmission resource (UL grant 2).

In the SO-based segmentation method, even after segmentation is performed, the segmented segments have the same RLC serial number of the original RLC PDU. Accordingly, the segments divided in one RLC PDU are identical to the RLC serial numbers of the original RLC PDU (1v-30, 1v-35, 1v-40, 1v-40, 1v-50).

The RLC layer may operate in RLC AM (Acknowledged Mode) mode, RLC UM (Unacknowledged Mode) mode, and RLC TM (Transparent Mode) mode. In the RLC AM mode, the RLC layer supports the ARQ function, the transmitting end can receive an RLC status report from the receiving end, and retransmission of lost (NACK) RLC PDUs through the status report. can be done In the case of performing the retransmission, if the uplink transmission resource is insufficient, a re-segmentation operation may be performed. Therefore, it guarantees reliable data transmission without errors and is suitable for services requiring high reliability. In order to efficiently support the ARQ function, accurate information on the lost RLC PDUs is required. Therefore, the SO field can be very usefully used. That is, which RLC PDU is lost and which part of the RLC PDU is lost can be more specifically indicated in the RLC Status Report with the SO field. When the transmitting end receives the specific information of the lost RLC PDU in the SO field, it can perform an SO-based division operation accordingly to perform retransmission.

On the other hand, the ARQ function is not supported in the RLC UM mode. Therefore, RLC status report is not performed, and there is no retransmission function. In the RLC UM mode, the RLC layer of the transmitter configures RLC headers for PDCP PDUs (RLC SDUs) received from an upper layer before or after receiving an uplink transmission resource and transmits it to a lower layer. Therefore, continuous data transmission is possible without transmission delay, and it may be useful for a service sensitive to transmission delay. Therefore, in the RLC UM mode, the ARQ function is not performed as described above and the RLC status report is not performed, so detailed information such as the SO field is not required in the SO-based partitioning method applied in the RLC AM mode.

23 is a diagram for explaining an SI field-based segmentation method proposed for an RLC UM mode or an RLC AM mode in the present invention.

The SI field-based segmentation method proposed in FIG. 23 does not require an SO field, unlike the SO field and SI field-based segmentation method proposed in FIG. 21 . That is, there is an advantage that the overhead is much less. That is, since the SO field corresponding to the 2 bytes is not needed, overhead is reduced and transmission resource waste can be reduced.

There are two major differences between the partitioning method proposed in FIG. 21 and the SI field-based partitioning method proposed in FIG. 1w .

1. RLC serial number assignment: In FIG. 21, even if multiple segments are generated by a segmentation operation for one RLC SDU, they have the same RLC serial number. That is, even if a segmentation operation is performed on one RLC SDU and the four segments are segment 1, segment 2, segment 3, and segment 4, the four segments have the same RLC serial number, and the four segments are divided. This makes it possible to distinguish by indicating the offset with the SO field of each segment. On the other hand, in the SI field-based segmentation method proposed in FIG. 23, when four segments are generated (1w-10, 1w-15, 1w-20, 1w-25) for one RLC SDU (1w-05) as described above, each segment They are assigned different RLC serial numbers. That is, RLC serial numbers 0, 1, 2, 3 are assigned to each segment, and the SI field is set according to whether it is the first segment, the middle segment, or the last segment. Therefore, the order of each segment can be distinguished using the SI field, and when three or more segments occur, several segments in the middle (segments having the same SI field) can be distinguished in the order of the RLC serial number. . Therefore, at the receiving end, reassembly is possible only with the combination of the RLC serial number and the SI field (without the SO field).

2. SO field not used: In FIG. 21, since the same RLC serial number is assigned to each segment, the SO field has to be distinguished. In FIG. 23, different RLC serial numbers are assigned to each segment and the SI field is also set. No fields are needed.

In the above, the Segmentation Information (SI) field may be defined as follows or may be named with a different name.

If the SI field is 00, it indicates a complete unsegmented RLC SDU, if the SI field is 01, it indicates the first segmented RLC SDU segment, and if the SI field is 10, it indicates the last segmented RLC SDU segment. , when the SI field is 11, it indicates a segmented middle RLC SDU segment. The mapping relationship between the 2 bits and the 4 pieces of information (complete RLC PDU, the first segment, the last segment, and the middle segment) may have a total of 4x3x2x1 = 24, and the above shows one example. The present invention includes all of the above 24 mapping cases.

24 is a diagram illustrating a data processing operation to which the SI-based partitioning method of the RLC UM mode or the RLC AM mode proposed in the present invention is applied.

In FIG. 24 , when an IP packet arrives at the PDCP layer, a PDCP header may be attached, and a PDCP PDU (or RLC SDU, 1x-05) may be transmitted to the RLC layer. A characteristic of the RLC UM mode proposed by the present invention is that an RLC serial number is not assigned to an RLC PDU in which a split operation is not performed. Therefore, in the RLC layer, the RLC PDU (1x-10) can be completed by configuring the RLC header without first allocating an RLC serial number, and then delivered to the MAC layer. The MAC layer calculates the size of the MAC SDU (or RLC PDU) to configure the L field, sets a corresponding logical channel identifier, etc., configures the MAC subheader (1x-15), and configures the buffer (1x-20) can be stored in Therefore, data packets received in the PDCP layer in this way can be stored in a buffer by performing data pre-processing before receiving the transmission resource (UL grant) from the base station, or after receiving the transmission resource, Likewise, on-the-fly processing may be performed.

If an uplink transmission resource (UL grant 1, 1x-25) is received from the base station, but the division operation needs to be performed due to insufficient uplink transmission resources, different RLC serial numbers are assigned to the RLC headers of each segment, such as 1x-30. And, after setting the SI field according to whether the original RLC PDU is the first segment, the middle segment, or the last segment, the RLC headers of the segments can be newly configured (1x-30, 1x-35). In addition, MAC PDUs may be configured and transmitted according to uplink transmission resources. If the second uplink transmission resource (UL grant 2, 1x-45) is received, but the size of the transmission resource is insufficient and a segmentation operation is required once again, re-segmentation from the segment as in 1x-40 (re-segmentation) ), the same RLC serial number as the original segment is applied, and the SI field is updated according to whether the original RLC PDU is the first segment, the middle segment, or the last segment. In addition, a new RLC serial number is assigned to a newly segmented segment such as 1x-50, and the SI field of the segment generated by performing the segmentation operation is set according to whether the original RLC PDU is the first segment, the middle segment, or the last segment. Then, the RLC header may be newly configured.

Therefore, it can be seen that the transmission/reception operation in the RLC UM mode proposed in FIG. 23 proposed by the present invention works well even in the data pre-processing procedure as described above.

In the RLC layer device of the AM mode in the present invention, when the data partitioning method is not set or not used, the terminal uses the bitmap-based RLC status report proposed in the present invention, or the bitmap-based RLC By configuring and sending status reports, the data processing speed of the receiving end can be improved. In another method, when the data partitioning method is not set or not used in the RLC layer device of the AM mode in the present invention, the UE reports the RLC status using the ACK_SN, NACK_SN, NACK_RANGE, or SO fields. Alternatively, the RLC status report may be configured and transmitted.

When the SI field-based data partitioning method proposed in the present invention is configured or used in the RLC layer device of the AM mode, the UE uses the bitmap-based RLC state report proposed in the present invention, or reports the bitmap-based RLC state can be configured and transmitted to improve the data processing speed of the receiving end. As another method, when the SI field-based data partitioning method proposed in the present invention is configured or used in the RLC layer device of the AM mode, the UE uses an RLC status report using ACK_SN, NACK_SN, NACK_RANGE, or SO fields. Alternatively, the RLC status report may be configured and transmitted.

When the SI field-based data segmentation method proposed in the present invention is configured or used in the RLC layer device of the AM mode, the UE may apply the following methods when data re-segmentation is required. In the above, data re-segmentation is performed when retransmission is performed on data that has already been transmitted (eg, fragmented data or complete (non-partitioned) data) (eg, some data has already been transmitted but successfully reported in the RLC status report). This means that the data segmentation method needs to be applied again to the data (eg, segmented data) due to insufficient uplink transmission resources (when it is indicated that it is not received and retransmission is required).

First method: In the first method, when the SI field-based data segmentation method proposed in the present invention is configured or used in the RLC layer device of the AM mode, the data segmentation may not be allowed. For example, when retransmission is performed on data that has already been transmitted (eg, fragmented data or complete (unpartitioned) data) in the above (eg, some data has already been transmitted but it is successfully reported in the RLC status report). In case retransmission is required because it has not been received), if there is a case where it is necessary to apply the data segmentation method again to the data (eg, segmented data or complete (non-segmented) data) due to insufficient uplink transmission resources. , the data may not be transmitted because the transmission resource is insufficient to transmit the data without re-applying the data partitioning method or performing data re-segmentation, or to transmit the data without re-segmenting the data, or You can send padding instead of data. Then, when an uplink transmission resource large enough to transmit the data is received, the data may be transmitted.

Second method: In the second method, when the SI field-based data segmentation method proposed in the present invention is configured or used in the RLC layer device of the AM mode, if the data to be transmitted for the first time is insufficient, data segmentation If the method needs to be performed, the SI field-based data segmentation method proposed in the present invention may be applied. However, if retransmission is performed on data that has already been transmitted (eg, fragmented data or complete (unpartitioned) data) (eg, some data has already been transmitted but not successfully received in the RLC status report) In case retransmission is required because it is indicated that the ), a data re-segmentation procedure may be performed by applying the SO field-based data segmentation method proposed in the present invention to the data (eg, RLC SDU). In the above, a new indicator may be introduced in the RLC header to indicate whether the SO field-based data partitioning method is applied, the SI field-based data partitioning method is applied, or data re-segmentation is performed. In addition, when the receiving RLC layer device receives the data on which the data re-segmentation procedure has been performed as described above, an RLC status report using ACK_SN, NACK_SN, NACK_RANGE, or SO fields or a bitmap-based RLC status report is configured to configure the transmission RLC layer can be sent to the device.

25 shows an RLC header structure applicable to RLC UM mode or RLC AM mode proposed by the present invention.

The RLC header structure may include some or another new field among the fields described with reference to FIG. 23, and may have a different structure according to the length of each field, such as a different RLC serial number length, and according to the location of each field. there is. R refers to a reserved bit, and the RLC header structure may be characterized in that there is no RF field and E field. As described above, the SI field serves to indicate a complete RLC SDU (complete RLC SDU) in which the segmentation operation is not performed, and the first segment, the middle segment, and the last segment in which the segmentation operation is performed.

In the case of the RLC UM mode proposed by the present invention, the RLC serial number is not used and is not required for the Complete RLC SDU (RLC SDU in which the division operation is not performed). In fact, there are many reasons why you need an RLC serial number. That is, the RLC serial number is required for order reordering, duplicate check, lost packet detection and ARQ function support, and segmented segment reassembly. However, in the next-generation mobile communication system, there is no need to perform reordering at the RLC layer, and the redundancy check can be performed instead of the PDCP layer, and the lost packet detection and ARQ functions are not supported in the RLC UM mode. Therefore, the RLC serial number is only needed for the divided RLC PDU segment. Therefore, the RLC serial number is not required in the Complete RLC PDU.

In the present invention, in the case of the RLC UM mode, the RLC serial number is not used in the Complete RLC PDU, and a header format such as 1y-05 is proposed (if RLC SN exists or RLC in the MAC subheader of the MAC layer) If the presence or absence of a header is indicated by a 1-bit indicator, the RLC header itself can be omitted without using a header format such as 1y-05 for the Complete RLC PDU In this case, the receiving end checks the indicator of the MAC subheader, There is no RLC header, and it can be known whether it is a Complete RLC PDU). That is, for an RLC PDU that has not been divided at the transmitting end, the SI field of the header of 1y-05 is indicated as 00 to indicate that it is a complete RLC PDU to indicate that there is no RLC serial number, and at the receiving end, the SI field of the header is indicated. If it is 00, you can see that there is no RLC serial number. Accordingly, the header structure is independent of the length of the RLC serial number. A 1-byte header such as 1y-05 may be used for a complete RLC PDU.

And for the first RLC PDU segment on which the segmentation operation has been performed, an RLC serial number is assigned as described above, and the RLC header is set to 1y-10 (when using a 6-bit RLC serial number) or 1y-15 (12-bit RLC). When using serial number) format can be used. However, a new continuous RLC serial number is assigned to the middle segment and the last segment created by performing the segmentation operation, not the same RLC serial number, and the SI field is set for each segment, RLC header format such as 1y-15 (when using a 12-bit RLC serial number) can be used. As described above, RLC serial numbers are required for segments on which the segmentation operation has been performed. This is because it is only possible to distinguish which segments have the order of which RLC serial number only if there is an RLC serial number. there is. Therefore, the receiving end can reassemble the segmented segments into a complete RLC PDU using the RLC serial number and SI field.

In addition, in the RLC AM mode, the RLC serial number is always included for each data (or regardless of whether data is divided), and a format of 1y-10 or 1y-15 can be used.

In the present invention, in the RLC UM mode, the operation of the transmitter applying the SI-based partitioning method without using a serial number is as follows.

If the RLC serial number is set not to be used in the RLC layer device at the transmitting end, a 1-byte RLC header such as 1y-05 without the RLC serial number is appended to the RLC SDU for which the division operation is not performed at the transmitting end (the RLC header cannot be configured). When the SI field is set to 00 and the operation of configuring the RLC header is performed), the transmission may be performed by passing it to the lower layer. However, in order not to use the RLC serial number in order to reduce the overhead, if the RLC SDU division operation is performed even when the RLC serial number is not used, the RLC serial number must be added and the SI field must be set as described in FIG. The reason for configuring the RLC header by allocating a new continuous RLC serial number to each segment and setting the SI field to the divided RLC SDU is to receive the divided RLC SDU segments at the receiving end and reassemble them to complete the RLC SDU in order to be able to restore Therefore, even when the RLC serial number is set not to be used in the RLC UM mode, if a split operation is performed, RLC headers such as 1y-10 and 1y-15 must be applied.

In summary, the transmitter attaches a 1-byte RLC header such as 1y-05 without an RLC serial number to the RLC SDU for which the segmentation operation is not performed, depending on whether the segmentation operation of the RLC SDU is performed, and transmits it to the lower layer. , for the RLC SDU on which the segmentation operation has been performed, as described above, the corresponding SI field is updated according to the segmented segment type (first, middle, last), and different consecutive RLC serial numbers are assigned to each segment. By adding them in order, the RLC header is constructed and delivered to the lower layer.

In the present invention, the operation of the receiving end with respect to the operation of the transmitting end applying the SI-based partitioning method without using a serial number in the RLC UM mode is as follows.

The RLC layer device at the receiving end receives the RLC PDU, checks the SI field in the RLC header, and distinguishes whether the received RLC PDU is an RLC PDU without segmentation operation (Complete RLC PDU) or a segmentation operation received RLC PDU (segment) do. If the RLC SDU has not been divided, the RLC header may be deleted and the RLC header may be uploaded to a higher layer. If it is an RLC SDU that has been segmented, check the SI field, check whether it is the first, middle, or last segment, consider the RLC serial number, store and organize it according to the RLC serial number, and reassemble by a window or timer When the re-assembly function is triggered, it is reassembled to form a complete RLC SDU and delivered to the upper layer.

The procedure of FIG. 24 can be easily extended to the procedure of the RLC AM mode, the only difference is that the RLC serial number is included for the complete data (complete RLC SDU) as well as the divided data regardless of whether the data is divided or not. Therefore, in consideration of this difference, the content of the invention can be easily extended to the RLC AM mode.

In the present invention, an embodiment of the operation of the transmitting end and the receiving end RLC layer device in the RLC UM mode is as follows.

In the transmitter RLC UM mode device, a variable called VT(S) can be managed (it can be reused as another variable or named with a different name). The variable VT(S) is an RLC serial number value assigned to segments on which the segmentation operation has been performed by the transmitter. The segments divided for one RLC SDU have different RLC serial numbers, that is, different VT(S). has The receiving end may set a timer and timer value set by the base station. The VT(S) value may be initially set to zero.

If data is generated in the RLC UM mode at the transmitting end (or received from a higher layer device), the RLC UM PDU may be configured, and the MAC SDU and MAC subheader may also be configured.

Thereafter, when the transmitting end confirms the transmission resource or receives the transmission resource, it determines whether to divide and transmit the RLC UM PDUs according to the size of the transmission resource. In the case of a complete RLC PDU that does not perform split transmission, a 1-byte RLC header not including the RLC serial number is configured (1g-05), and the VT(S) value is maintained. That is, the RLC serial number is not assigned. If it is decided to perform split transmission on a certain RLC PDU, a header including the RLC serial number is configured (a header such as 1y-05 is configured).

When performing segmented transmission in the above, a new RLC serial number (a new VT(S) value) is allocated to each segment and the VT(S) value is increased by one. That is, each time a new RLC serial number (new VT(S) value) is assigned to each segment, the VT(S) value is increased by 1. And, when the division operation is also performed on the next RLC PDU, the RLC serial number is continuously incremented and allocated. And when the value of VT(S) reaches the maximum value (2^(length of RLC serial number) - 1 ), it is reset to 0 again and the above process is repeated again. If the above procedure is applied to the RLC AM mode, in the AM mode, a new RLC serial number (new VT(S) value) may be allocated for each segment or complete data (RLC SDU), and the VT(S) value may be increased by one.

When the receiving end RLC layer device operates on a window basis, the receiving end operates the RLC receive window, and the window may be operated with the size of half of the RLC serial number, and in the case of the lower edge of the window, the size of the RLC window at the upper edge It may be set as a serial number obtained by subtracting , and the upper edge may be set as the highest RLC serial number received from the receiving end RLC. Therefore, if the received RLC serial number has a higher value than the RLC serial numbers in the window, the window moves accordingly. If the serial number of the received RLC PDU has a value greater than the upper edge of the received window, the window moves forward.

On the other hand, if the serial number of the received RLC PDU has a value smaller than the lower edge of the received window, the RLC layer at the receiving end may discard it, and check whether a duplicate RLC PDU is received for the RLC serial number within the window and discard it. there is also And when the RLC PDU segment having the RLC serial number in the window arrives, it is stored and when the lower edge of the window passes the RLC serial number corresponding to the RLC PDU segment, a reassembly procedure is performed to obtain a complete RLC PDU. It is generated and sent to a higher layer, and if a complete RLC PDU is not generated, an operation of discarding RLC PDU segments can be performed. In addition, the RLC layer at the receiving end checks the SI field and, in the case of an RLC PDU in which the segmentation operation is not performed, directly uploads it to the upper layer, and stores it when the SI field indicates the RLC PDU in which the segmentation operation is performed, and stores the same as described above. Similarly, when the reassembly procedure is triggered by the window (the lower edge moves to a value larger than the RLC serial number of the segments), it is carried out and sent to the upper layer or discarded.

In the following of the present invention, for RLC UM data transfer, when the SI field-based data division method proposed in the present invention is set (or used) or when the SO field-based data division method is set (or used) When), the operation of the transmitting RLC layer device and the operation of the receiving RLC layer device are proposed.

- The transmitting UM RLC layer device performs the following operation when transmitting data (UMD PDU) to a lower layer device.

■ 1> If it is not set to use the SI field-based data segmentation method, or if it is set to use the SO field-based data segmentation method

◆ 2> If data (UMD PDU) includes a segment of RLC SDU

● 3> Set the RLC serial number of the data (UMD PDU) to the value of the UM_TX_Next variable.

◆ 2> If the data contains a segment that maps (or matches) the last byte of the RLC SDU

● 3> Increase the UM_TX_Next value by 1.

■ 1> Otherwise (or if it is set to use the SI field-based data segmentation method, or if the SO field-based data segmentation method is disabled)

◆ 2> If the data (UMD PDU) includes a segment of the RLC SDU, set the RLC serial number of the data (UMD PDU) to the value of the UM_TX_Next variable. Then, the UM_TX_Next value is increased by 1.

- The receiving UM RLC layer device performs the following operation when storing data (UMD PDU) corresponding to the RLC serial number x in the buffer.

■ 1> If all byte segments corresponding to RLC serial number x have been received, and/or SI field-based data segmentation method is not configured,

◆ 2> The RLC SDU is reassembled into all byte segments corresponding to the RLC serial number x, the RLC header is removed, and the reassembled RLC SDU is delivered to the upper layer device.

■ 1> Otherwise, if all byte segments corresponding to the data (RLC SDU or UMD PDU) have been received, and/or if the SI field-based data segmentation method is configured,

◆ 2> The RLC SDU is reassembled into all byte segments corresponding to the data (RLC SDU or UMD PDU), the RLC header is removed, and the reassembled RLC SDU is delivered to the upper layer device.

In the above, the UM_TX_Next variable is a variable that stores an RLC serial number value to be allocated for data to be newly generated next (data including a segment). The initial value of the variable is 0.

In the following of the present invention, when the SI field-based data segmentation method proposed in the present invention is set (or used) for the RLC AM mode (AM data transfer), or when the SO field-based data segmentation method is set (or used) When), the operation of the transmitting RLC layer device and the operation of the receiving RLC layer device are proposed.

- The transmitting AM RLC layer device performs the following operation for each RLC SDU received from a higher layer device.

■ 1> If it is not set to use the SI field-based data segmentation method, or if it is set to use the SO field-based data segmentation method

◆ 2> Create an AMD PDU by setting the RLC serial number of the RLC SDU to the same value as AM_TX_Next and setting the RLC serial number of the AMD PDU to the same value as AM_TX_Next.

◆ 2> Increase the AM_TX_Next value by 1.

- The transmitting AM RLC layer device performs the following operation when transmitting data (AMD PDU) including the segment of the RLC SDU to the lower layer device.

■ 1> If it is not set to use the SI field-based data segmentation method, or if it is set to use the SO field-based data segmentation method

◆ 2> Set the RLC serial number of the data (AMD PDU) to the RLC serial number corresponding to the RLC SDU.

- The transmitting AM RLC layer device performs the following operation when transmitting data (AMD PDU) to a lower layer device.

■ 1> If the SI field-based data segmentation method is set to use

◆ 2> Set the RLC serial number of the data (AMD PDU) to the AM_TX_Next value, and increase the AM_TX_Next value by 1.

- The receiving AM RLC layer device performs the following operation when storing data (AMD PDU) corresponding to the RLC serial number x in the buffer.

■ 1> If all byte segments of the RLC SDU corresponding to the RLC serial number x have been received, and/or the SI field-based data segmentation method is not configured

◆ 2> The RLC SDU is reassembled into AMD PDUs or all byte segments corresponding to the RLC serial number x, the RLC header is removed, and the reassembled RLC SDU is delivered to the upper layer device.

■ 1> Otherwise, if all byte segments corresponding to the data (RLC SDU or AMD PDU) have been received, and/or if the SI field-based data segmentation method is configured

◆ 2> The RLC SDU is reassembled into all byte segments corresponding to the data (RLC SDU or AMD PDU), the RLC header is removed, and the reassembled RLC SDU is delivered to the upper layer device.

In the above, the AM_TX_Next variable is a variable that stores an RLC serial number value to be allocated for data to be newly generated next. The initial value of the variable is 0.

26 is a diagram showing the operation of the PDCP layer apparatus of the terminal proposed above of the present invention.

If the data concatenation procedure proposed in FIG. 26 is configured or performed in the PDCP layer device, the data concatenation procedure proposed in the present invention is transmitted when data is received from the upper layer device (1z-05), the transmission PDCP layer device (1z-01) For data to which the header compression procedure was applied or performed (if the header compression procedure was set) (1z-10), but to which the integrity protection procedure (1z-25) or encryption procedure (1z-30) was not applied or performed It is characterized by applying or performing the data concatenation procedure (1z-15). In another method, the data concatenation procedure proposed in the present invention applies or performs the header compression procedure in the transmitting PDCP layer device, but before applying or performing the integrity protection procedure or the encryption procedure, the header compression procedure is applied to data. It is characterized by applying or performing a data concatenation procedure. Accordingly, among the new fields generated in the data concatenation procedure 1z-15, the length field (eg, LI field) may set the length of data to which the header compression procedure is applied as a byte unit value. For example, if a header compression procedure or integrity protection procedure or encryption procedure is established, the header compression procedure is applied or performed to each data, the data concatenation procedure is performed on multiple data, or the integrity protection procedure is applied to the concatenated data (1z-25) or encryption procedure (1z-30). This is because the number or frequency of performing the integrity protection procedure or encryption procedure can be minimized and the data processing time can be reduced only when the integrity protection procedure or the encryption procedure is applied to the concatenated data at once.

On the other hand, since the complexity of applying or performing the header compression procedure to each data of concatenated data is high, it is convenient to concatenate after performing the header compression procedure in advance, and the length field indicating the length of each concatenated data can be reduced to reduce overhead. In addition, when the integrity protection procedure or encryption procedure is applied to one concatenated data concatenating several data in the above, the integrity protection procedure or encryption procedure is performed using one COUNT value (1z-20), so that With one set (such as a COUNT value or a bearer identifier or security key), single processing is possible and data processing time can be shortened. For example, if data is not concatenated above, data processing time is required because integrity protection or encryption procedures must be performed multiple times based on different sets of security key values using a different COUNT value for each data. Do. Also, when applying or performing the data concatenation procedure to the data, the data concatenation procedure may be applied in the order received from the upper layer device, or the data may be concatenated in order from the beginning of the concatenation procedure. This is because, when the data concatenation procedure is performed, the data can be sequentially transferred to the upper layer device when the data concatenated at the receiving end is separated only by concatenating the data from the front in order. For example, data concatenated to concatenated data to which one PDCP serial number is assigned are in the order of data first received from the upper layer device from the front (1z-15, 1z-40).

If the data concatenation procedure proposed in FIG. 26 is configured or performed in the PDCP layer device, the data separation procedure proposed in the present invention is the decoding procedure (1z-55) or the integrity verification procedure (1z-55) in the receiving PDCP layer device 1z-02 ( It is characterized in that the data separation procedure (1z-65) is applied or performed on the concatenated data to which 1z-60) is applied or performed, and the header decompression procedure (1z-70) for each of the separated data can be applied.

In another method, the data separation procedure proposed in the present invention is characterized in that the data separation procedure is applied or performed on the concatenated data after or after the decoding procedure or the integrity verification procedure is applied at the receiving end (terminal or base station). and a header decompression procedure may be applied to each of the above separated data. For example, if a header compression procedure, encryption procedure, or integrity verification procedure is set, a decryption procedure is performed on the received concatenated data, or an integrity verification procedure is performed and then a data separation procedure is performed on the concatenated data, A header decompression procedure can be applied to each separated data. This is because the number or frequency of performing the decryption procedure or the integrity verification procedure can be minimized and the data processing time can be reduced only when the decryption procedure or the integrity verification procedure is applied to the concatenated data at once.

On the other hand, since it is complicated to apply or perform the header decompression procedure for each data of the concatenated data, it is easy to implement and perform the header decompression procedure after separating the data later, and the length of each concatenated data It is possible to reduce the length field indicating , thereby reducing overhead. In addition, when a decryption procedure or integrity protection procedure is applied to one concatenated data concatenating multiple data in the above, a decryption procedure or integrity protection procedure is performed using a single COUNT value, so that one set of security key values ( COUNT value or bearer identifier or security key) enables single processing and shortens data processing time. For example, if the data is not concatenated above, the data processing time is very long because the decryption procedure or the integrity protection procedure must be performed multiple times based on different sets of security key values using a different COUNT value for each data. need. In addition, when applying or performing the data separation procedure to the concatenated data in the above, the data may be sequentially separated from the front part of the concatenated data, the data may be processed sequentially from the front part, and transmitted to the upper layer device. For example, data concatenated to concatenated data to which one PDCP serial number is assigned must first be delivered to a higher layer device from the front (1z-75).

27 is a diagram illustrating the operation of the SDAP layer device (or new layer device) of the terminal proposed above according to the present invention.

If the data concatenation procedure proposed in FIG. 27 is configured or performed in the SDAP layer device (or a new layer device), the data concatenation procedure proposed in the present invention is a header compression procedure and integrity protection procedure in the transmitting SDAP layer device 1ab-01 , or it is characterized in that the data concatenation procedure is applied or performed to data to which the encryption procedure is not applied or is not performed. As another method, the data concatenation procedure proposed in the present invention is a data concatenation procedure (1ab-) for data before or before applying a header compression procedure, an integrity protection procedure, or an encryption procedure at the transmitting end (terminal or base station). 05) is applied or performed. Accordingly, the length field (eg, the LI field) among the new fields generated in the data concatenation procedure may set the length of header uncompressed data as a byte unit value. In the above, when the SDAP layer device performs the data concatenation function, the data concatenation procedure is performed only on the data of the upper layer device corresponding to the QoS flow IDs (QoS identifiers) mapped to each bearer, and the concatenated data is transferred to the bearer. It can be delivered to the PDCP layer device.

As another method, when performing the data concatenation function in the SDAP layer device and performing the data concatenation procedure on the data of the upper layer device corresponding to QoS flow IDs (QoS identifiers) mapped to each bearer, specifically The data concatenation procedure may be applied only to data corresponding to the same QoS flow ID (QoS identifier), and the concatenated data may be delivered to the PDCP layer device of the bearer. For example, if a header compression procedure, integrity protection procedure, or encryption procedure is set, the data concatenation procedure (1ab-01) is performed or applied, and then the concatenated data is transferred to the PDPC layer device (1ab-20) to perform the header compression procedure , integrity protection procedures, or encryption procedures. If the SDAP header is set in the above, the SDAP header can be configured and attached in front of the concatenated data before transferring the concatenated data to the lower layer device (1ab-15). This is because the number or frequency of performing the integrity protection procedure or encryption procedure can be minimized and the data processing time can be reduced only when the integrity protection procedure or the encryption procedure is applied to the concatenated data at once.

In addition, when applying the integrity protection procedure or encryption procedure to one concatenated data concatenating multiple data in the above, the integrity protection procedure or encryption procedure is performed using one COUNT value, so that one set of security key values ( COUNT value or bearer identifier or security key) enables single processing and shortens data processing time. For example, if data is not concatenated above, data processing time is required because integrity protection or encryption procedures must be performed multiple times based on a set of different security key values using a different COUNT value for each data. Do.

Also, when applying or performing the data concatenation procedure to the data, the data concatenation procedure may be applied in the order received from the upper layer device, or the data may be concatenated in order from the beginning of the concatenation procedure. This is because, when the data concatenation procedure is performed, the data can be sequentially transferred to the upper layer device when the data concatenated at the receiving end is separated only by concatenating the data from the front in order. For example, data concatenated to concatenated data to which one PDCP serial number is assigned are in the order of data first received from a higher layer device from the front (1ab-20).

If the data concatenation procedure proposed in FIG. 27 is configured or performed in the SDAP layer device (or a new layer device), the data separation procedure proposed in the present invention is a decryption procedure and an integrity verification procedure in the receiving SDAP layer device 1ab-02 , or it is characterized in that the data separation procedure is applied or performed on the concatenated data to which the header decompression procedure has been applied or performed.

In another method, the data separation procedure proposed in the present invention receives concatenated data from a lower layer device after or after the decoding procedure, integrity verification procedure, or header decompression procedure is applied or performed in the receiving SDAP layer device (1ab- 025) is characterized by applying or performing the data separation procedure (1ab-35). If the SDAP header is set in the above, when data is received from the lower layer device, the SDAP header can be removed and processed (1ab-30). For example, if a header compression procedure, encryption procedure, or integrity verification procedure is set, a decryption procedure is performed on the concatenated data received, or an integrity verification procedure or header decompression procedure is performed, and then the data separation procedure ( 1ab-35) can be performed. This is because the number or frequency of performing the decryption procedure or the integrity verification procedure can be minimized and the data processing time can be reduced only when the decryption procedure or the integrity verification procedure is applied to the concatenated data at once.

In addition, when a decryption procedure or integrity protection procedure is applied to one concatenated data concatenating multiple data in the above, a decryption procedure or integrity protection procedure is performed using a single COUNT value, so that one set of security key values ( COUNT value or bearer identifier or security key) enables single processing and shortens data processing time. For example, if the data is not concatenated above, the data processing time is very long because the decryption procedure or the integrity protection procedure must be performed multiple times based on different sets of security key values using a different COUNT value for each data. need. In addition, when applying or performing the data separation procedure to the concatenated data in the above, the data may be sequentially separated from the front part of the concatenated data, the data may be processed sequentially from the front part, and transmitted to the upper layer device. For example, data concatenated to concatenated data to which one PDCP serial number is assigned must first be transferred to a higher layer device from the front (1ab-40).

28 shows the structure of a terminal to which an embodiment of the present invention can be applied.

Referring to the drawings, the terminal includes a radio frequency (RF) processing unit 1cd-10, a baseband processing unit 1cd-20, a storage unit 1cd-30, and a control unit 1cd-40. .

The RF processing unit 1cd-10 performs a function for transmitting and receiving a signal through a wireless channel, such as band conversion and amplification of the signal. That is, the RF processing unit 1cd-10 up-converts the baseband signal provided from the baseband processing unit 1cd-20 into an RF band signal, transmits it through an antenna, and receives an RF band signal received through the antenna. down-converts to a baseband signal. For example, the RF processing unit 1cd-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 (ADC), etc. can In the figure, only one antenna is shown, but the terminal may include a plurality of antennas. Also, the RF processing unit 1cd-10 may include a plurality of RF chains. Furthermore, the RF processing unit 1cd-10 may perform beamforming. For the beamforming, the RF processing unit 1cd-10 may adjust the phase and magnitude of each of signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processing unit may perform MIMO, and may receive multiple layers when performing MIMO operation. The RF processing unit 1cd-10 may perform receive beam sweeping by appropriately setting a plurality of antennas or antenna elements under the control of the controller, or adjust the direction and beam width of the receive beam so that the receive beam is coordinated with the transmit beam. there is.

The baseband processing unit 1cd-20 performs a function of converting between a baseband signal and a bit stream according to a physical layer standard of a system. For example, when transmitting data, the baseband processing unit 1cd-20 generates complex symbols by encoding and modulating a transmitted bit stream. Also, when receiving data, the baseband processing unit 1cd-20 restores a received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit 1cd-10. For example, in the case of orthogonal frequency division multiplexing (OFDM), when transmitting data, the baseband processing unit 1cd-20 encodes and modulates a transmission bit stream to generate complex symbols, and convert the complex symbols to subcarriers. After mapping to , OFDM symbols are constructed through inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processing unit 1cd-20 divides the baseband signal provided from the RF processing unit 1cd-10 into OFDM symbol units, and sends them to subcarriers through a fast Fourier transform (FFT) operation. After reconstructing the mapped signals, the received bit stream is reconstructed through demodulation and decoding.

The baseband processing unit 1cd-20 and the RF processing unit 1cd-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 1cd-20 and the RF processing unit 1cd-10 may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit 1cd-20 and the RF processing unit 1cd-10 may include a plurality of communication modules to support a plurality of different radio access technologies. In addition, at least one of the baseband processing unit 1cd-20 and the RF processing unit 1cd-10 may include different communication modules to process signals of different frequency bands. For example, the different radio access technologies may include an LTE network, an NR network, and the like. In addition, the different frequency bands may include a super high frequency (SHF) (eg, 2.5 GHz, 5 GHz) band and a millimeter wave (eg, 60 GHz) band.

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

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

29 shows a block configuration of a TRP (eg, a base station) in a wireless communication system to which an embodiment of the present invention can be applied.

As shown in the figure, the base station includes an RF processing unit 1ef-10, a baseband processing unit 1ef-20, a backhaul communication unit 1ef-30, a storage unit 1ef-40, and a control unit 1ef-50. is comprised of

The RF processing unit 1ef-10 performs a function for transmitting and receiving a signal through a wireless channel, such as band conversion and amplification of the signal. That is, the RF processing unit 1ef-10 up-converts the baseband signal provided from the baseband processing unit 1ef-20 into an RF band signal, transmits it through an antenna, and receives the RF band signal through the antenna. downconverted to a baseband signal. For example, the RF processing unit 1ef-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 the drawing, the first access node may include a plurality of antennas. Also, the RF processing unit 1ef-10 may include a plurality of RF chains. Furthermore, the RF processing unit 1ef-10 may perform beamforming. For the beamforming, the RF processing unit 1ef-10 may adjust the phase and magnitude of each of signals transmitted and received through a plurality of antennas or antenna elements. The RF processing unit may perform a downlink MIMO operation by transmitting one or more layers.

The baseband processing unit 1ef-20 performs a function of converting a baseband signal and a bit stream according to the physical layer standard of the first radio access technology. For example, when transmitting data, the baseband processing unit 1ef-20 generates complex symbols by encoding and modulating a transmitted bit stream. Also, upon data reception, the baseband processing unit 1ef-20 restores a received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit 1ef-10. For example, in the OFDM scheme, when transmitting data, the baseband processing unit 1ef-20 generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then IFFT OFDM symbols are constructed through operation and CP insertion. Also, upon data reception, the baseband processing unit 1ef-20 divides the baseband signal provided from the RF processing unit 1ef-10 into OFDM symbol units, and restores signals mapped to subcarriers through FFT operation. After that, the received bit stream is restored through demodulation and decoding. The baseband processing unit 1ef-20 and the RF processing unit 1ef-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 1ef-20 and the RF processing unit 1ef-10 may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

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

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

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

In the specific embodiments of the present disclosure described above, elements included in the disclosure are expressed in the singular or plural according to the specific embodiments presented. However, the singular or plural expression is appropriately selected for the context presented for convenience of description, and the present disclosure is not limited to the singular or plural component, and even if the component is expressed in plural, it is composed of the singular or singular. Even an expressed component may be composed of a plurality of components.

Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments and should be defined by the claims described below as well as the claims and equivalents.

Claims (28)

A method of a transmitting apparatus in a wireless communication system, the method comprising:
receiving service data units (SDUs) from a higher layer;
generating concatenated data concatenating the SDUs;
performing at least one of an integrity protection procedure and an encryption procedure on the concatenated data; and
Transmitting the data on which the at least one procedure has been performed to a receiving device through a lower layer,
The security key information corresponding to each of the at least one procedure is equally applied to SDUs included in one piece of concatenated data. The method of claim 1, wherein the generating of the concatenated data comprises:
generating a field including information on concatenation of the SDUs; and
and generating the concatenated data including the concatenated SDUs and the field. The method of claim 1, wherein the layer generating the concatenated data comprises:
A method of a transmitting apparatus, characterized in that it is a packet data convergence protocol (PDCP) layer or a service data adaptation protocol (SDAP) layer. 4. The method of claim 3,
If the layer generating the concatenated data is the SDAP layer,
A method of a transmitter, characterized in that the concatenation is performed based on a quality of service (QoS) flow identifier (ID) corresponding to each SDU. According to claim 1,
distinguishing control data and user data from the received SDUs; and
and concatenating SDUs corresponding to the user data. According to claim 1,
The method of the transmitting apparatus, characterized in that the SDUs are concatenated so as to be located from the front in the order received from the upper layer. According to claim 1,
adding a header to the data on which the at least one procedure has been performed; and
The method of the transmitting apparatus, characterized in that it further comprises the step of transferring the header-added data to the lower layer. A method of a receiving device in a wireless communication system, comprising:
receiving data from the transmitting device through a lower layer;
performing at least one of an integrity verification procedure and a decryption procedure on the data;
separating service data units (SDUs) included in the data on which the at least one procedure has been performed; and
transmitting the separated SDUs to a higher layer;
The security key information corresponding to each of the at least one procedure is applied equally to the SDUs included in the data. The method of claim 8, wherein separating the SDUs comprises:
checking a field including information on concatenation of the SDUs included in the data; and
and separating the concatenated SDUs using the field. The method of claim 8, wherein the layer separating the SDUs comprises:
A method of a receiving device, characterized in that it is a packet data convergence protocol (PDCP) layer or a service data adaptation protocol (SDAP) layer. 11. The method of claim 10,
If the layer separating the SDUs is the SDAP layer,
A method of a receiving device, characterized in that the separation is performed based on a quality of service (QoS) flow identifier (ID) corresponding to each SDU. 9. The method of claim 8,
The separated SDUs are user data. 9. The method of claim 8,
The method of the receiving device, characterized in that the separated SDUs are delivered to the upper layer in the order in which they are located from the front. 9. The method of claim 8,
further comprising removing a header from the data;
and performing the at least one procedure on the data from which the header has been removed. A transmitting device in a wireless communication system, comprising:
transceiver; and
receive service data units (SDUs) from a higher layer; generate concatenated data concatenating the SDUs; performing at least one of an integrity protection procedure and an encryption procedure on the concatenated data; and a control unit for controlling the transceiver to transmit the data on which the at least one procedure has been performed to a receiving device through a lower layer,
The security key information corresponding to each of the at least one procedure is equally applied to SDUs included in one piece of concatenated data. The method of claim 15, wherein the control unit,
and generating a field including information on concatenation of the SDUs, and generating the concatenated data including the concatenated SDUs and the field. The method of claim 15, wherein the layer generating the concatenated data comprises:
A transmission device, characterized in that it is a packet data convergence protocol (PDCP) layer or a service data adaptation protocol (SDAP) layer. The method of claim 17, wherein the control unit,
If the layer that generates the concatenated data is the SDAP layer, the transmission apparatus characterized in that the concatenation is performed based on a quality of service (QoS) flow identifier (ID) corresponding to each SDU. The method of claim 15, wherein the control unit,
The transmission apparatus according to claim 1, wherein control data and user data are distinguished from the received SDUs, and SDUs corresponding to the user data are concatenated. The method of claim 15, wherein the control unit,
The transmission apparatus, characterized in that the concatenation is performed so that the SDUs are located from the front in the order they are received from the upper layer. The method of claim 15, wherein the control unit,
and adding a header to the data on which the at least one procedure has been performed, and transferring the header-added data to the lower layer. A receiving device in a wireless communication system, comprising:
transceiver; and
controlling the transceiver to receive data from a transmitting device through a lower layer; performing at least one of an integrity verification procedure and a decryption procedure on the data; separating service data units (SDUs) included in the data on which the at least one procedure has been performed; and a control unit for transferring the separated SDUs to a higher layer,
Security key information corresponding to each of the at least one procedure is equally applied to SDUs included in the data. 23. The method of claim 22, wherein the control unit,
The receiving apparatus of claim 1, wherein a field including information on concatenation of the SDUs included in the data is checked, and the SDUs are separated using the field. The method of claim 22, wherein the layer separating the SDUs comprises:
A receiving device, characterized in that it is a packet data convergence protocol (PDCP) layer or a service data adaptation protocol (SDAP) layer. The method of claim 24, wherein the control unit,
If the layer separating the SDUs is the SDAP layer, the reception apparatus, characterized in that the separation is performed based on a quality of service (QoS) flow identifier (ID) corresponding to each SDU. 23. The method of claim 22,
The separated SDUs are user data. 23. The method of claim 22, wherein the control unit,
The receiving device, characterized in that the separated SDUs are controlled to be delivered to the upper layer in an order from the front. 23. The method of claim 22, wherein the control unit,
and removing a header from the data, and performing the at least one procedure on the data from which the header is removed.

Images