WO2019059638A1 - Method for processing data by relay node and apparatus therefor - Google Patents

Abstract

The present disclosure relates to a technique for relaying and processing data of other nodes. More particularly, the present disclosure relates to a method and an apparatus for configuring a relay node for data transmission for remote nodes connected through a side link-based relay under the control of a mobile communication network. One embodiment provides a method and an apparatus for a relay node to process remote node data. The method comprises: a step of receiving, from a base station, configuration information for configuring an adaptation entity; a step of configuring the adaptation entity by linking a PDCP entity and an RLC entity, on the basis of the configuration information; and a step in which the adaptation entity separates and processes data to be transmitted to the RLC entity and data to be transmitted to the PDCP entity.

Description

Method and apparatus for processing data of relay node

This disclosure relates to techniques for relaying and processing data from other nodes. And more particularly, to a relay node configuration method and apparatus for data transmission of a remote node connected through a wireless relay under the control of a mobile communication network.

As wireless communication technology is widely used in general life, various service requirements are being generated. For example, wireless communication technologies such as public safety disaster communication and inter-vehicle communication disclose the need for a form of communication between terminals as utilization scenarios for providing communication services in various situations while using a mobile communication network.

In other words, there has been a service requirement for performing communication between the terminal and the terminal, which is deviated from the communication between the terminal and the base station. For this purpose, a side link technique using a mobile communication network has been developed.

Specifically, in the case of conventional side-link communication or relay communication, terminals related to communication are authenticated by an upper layer and IP traffic is delivered through Layer 3 (L3) forwarding. Therefore, in the conventional side link communication based on L3 forwarding, it is impossible to provide reachability to a remote node in the network, and it is difficult to control power consumption or control QoS for traffic.

In addition, in the NR (New RAT) technology employing the 5G technology, the demand for the multi-hop relay technology is increasing. For this, the necessity of developing the communication technology between the terminal and the base station utilizing the multi-hop relay node is also increasing.

The present disclosure in the background described above proposes a technique for providing traffic control according to power consumption or QoS control of a remote node.

In addition, the present disclosure proposes a specific method and apparatus for performing a data transmission / reception operation through a Layer 2 (L2) based relay node.

According to an embodiment of the present invention, there is provided a method of processing a remote node data by a relay node, the method comprising: receiving configuration information for configuring an adapter object from a base station; and associating the PDCP entity and the RLC entity And separating and processing data to be transferred to the RLC entity and the PDCP entity from the adapter entity in the adapter entity.

According to another embodiment of the present invention, there is provided a method of processing remote node data by a base station, the method comprising: constructing an adaptation object by linking a PDCP entity and an RLC entity; Information is added to the PDCP PDU, and data to be transmitted to the relay node and the remote node are divided into RLC entities associated with the adapter entity and transmitted.

According to an embodiment of the present invention, there is provided a relay node for processing remote node data, comprising: a receiver for receiving configuration information for configuration of an adaptation object from a base station; and a PDCP entity and an RLC entity based on the configuration information, And a control unit for discriminating between data to be transferred from the adapter entity to the RLC entity and data to be transmitted to the PDCP entity, and processing the relay node device.

According to an embodiment of the present invention, there is provided a base station for processing remote node data, the base station including a control unit configured to associate a PDCP entity and an RLC entity to form an adaptation object, wherein the control unit discriminates data of a relay node and a remote node from the adaptation object And adds the header information to the PDCP PDU and separates the data to be transmitted to the relay node and the remote node into the RLC entity associated with the adapter entity and delivers the header information to the relay node and the remote node.

As described above, the present disclosure provides an effect of distinguishing and processing traffic between a remote node and a relay node or between a relay node and a base station.

The present disclosure also provides an effect that the traffic to the remote node can be controlled according to the QoS, and the network can control the power consumption and the like in detail.

FIG. 1 is a view schematically showing a structure of an NR wireless communication system to which the present embodiment is applicable.

2 is a diagram for explaining a frame structure in an NR system to which the present embodiment can be applied.

FIG. 3 is a diagram for explaining a resource grid supported by a radio access technology to which the present embodiment is applicable.

4 is a diagram for explaining a bandwidth part supported by a radio access technology to which the present embodiment can be applied.

5 is a diagram exemplarily showing a synchronization signal block in a radio access technology to which the present embodiment can be applied.

6 is a diagram for explaining a random access procedure in a radio access technology to which the present embodiment can be applied.

Fig. 7 is a diagram for explaining CORESET. Fig.

8 is a diagram illustrating a control plane protocol stack for one-to-one side-link communications.

9 is a view for explaining a relay node operation according to an embodiment.

10 is a view for explaining a base station operation according to an embodiment.

11 is a view for explaining a base station operation according to another embodiment.

12 is a diagram illustrating an example of a user plane wireless protocol stack based on an L2 relay node.

13 is a diagram showing another example of a user plane wireless protocol stack based on an L2 relay node.

14 (A) to 14 (E) are views showing an example of the L2-based relay structure.

15 is a diagram showing another example of the L2-based relay structure.

16 is a diagram illustrating a layer 2 structure of a base station for downlink transmission in a conventional LTE radio access technology.

17 is a diagram exemplarily showing radio bearer configuration information according to an embodiment.

18 is a diagram illustrating a configuration of a relay node according to an embodiment.

19 is a diagram illustrating a configuration of a base station according to an embodiment.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. In the drawings, like reference numerals are used to denote like elements throughout the drawings, even if they are shown on different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention unclear.

In describing the components of the embodiments, terms such as first, second, A, B, (a), and (b) may be used. These terms are intended to distinguish the components from other components, and the terms do not limit the nature, order, order, or number of the components. When a component is described as being "connected", "coupled", or "connected" to another component, the component may be directly connected or connected to the other component, Quot; intervening " or that each component may be " connected, " " coupled, " or " connected " through other components.

In addition, terms and technical names used herein are for the purpose of describing specific embodiments, and the technical terms are not limited to the terms. Unless defined otherwise, the terms used below are to be construed in a manner generally understood by one of ordinary skill in the art to which this technical idea belongs. Where the term is an erroneous technical term that does not precisely express this technical thought, it should be understood that it is replaced by a technical term that can be understood by those skilled in the art. Also, the general terms used in the present specification should be interpreted in accordance with the predefined or prior context, and should not be construed as being excessively reduced in meaning.

The wireless communication system in this specification refers to a system for providing various communication services such as voice, data packet, etc. using wireless resources, and may include a terminal, a base station, and a core network.

The embodiments described below can be applied in a wireless communication system using various wireless connection technologies. For example, the present embodiments may be implemented in a wireless communication system such as code division multiple access (CDMA), frequency division multiple access (FDMA), timedivision multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC- And the like. CDMA may be implemented with wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented in wireless technologies such as global system for mobile communications (GSM) / general packet radio service (GPRS) / enhanced data rates for GSM evolution (EDGE). OFDMA may be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and evolved UTRA (E-UTRA). IEEE 802.16m is an evolution of IEEE 802.16e, providing backward compatibility with systems based on IEEE 802.16e. UTRA is part of the universal mobile telecommunications system (UMTS). 3GPP (3rd generation partnership project) LTE (Long Term Evolution) is a part of E-UMTS (evolved UMTS) using evolved-UMTS terrestrial radio access (E-UTRA). It adopts OFDMA in downlink and SC- FDMA. As described above, the present embodiments can be applied to wireless connection technologies that are currently being launched or commercialized, and may be applied to wireless connection technologies that are being developed or developed in the future.

The term " terminal " as used herein is a generic term meaning a device including a wireless communication module for communicating with a base station in a wireless communication system. The term " UE " in WCDMA, LTE, HSPA and IMT- (Mobile Station), a UT (User Terminal), a Subscriber Station (SS), and a wireless device in addition to the User Equipment (UE). In addition, the terminal may be a user portable device such as a smart phone according to the usage type, and may mean a vehicle, a device including a wireless communication module in the vehicle, or the like in the V2X communication system. In addition, in the case of a machine type communication system, it may mean a MTC terminal, an M2M terminal, or the like, on which a communication module is mounted so that a machine type communication is performed.

A base station or a cell in this specification refers to an end that communicates with a terminal on the network side and includes a Node-B, an evolved Node-B, a gNode-B, a Low Power Node, A sector, a site, various types of antennas, a base transceiver system (BTS), an access point, a point (for example, a transmission point, a reception point, a transmission / reception point), a relay node ), A megacell, a macrocell, a microcell, a picocell, a femtocell, a remote radio head (RRH), a radio unit (RU), and a small cell.

Since the various cells listed above exist in the base station controlling each cell, the base station can be interpreted into two meanings. Macro cell, micro cell, picocell, femtocell, small cell, or 2) the wireless region itself in connection with the wireless region. 1), all of the devices that interact to configure the wireless area to be cooperatively controlled by the same entity are all pointed to the base station. A point, a transmission / reception point, a transmission point, a reception point, and the like are examples of the base station according to the configuration method of the radio area. 2 may direct the base station to the wireless region itself to receive or transmit signals at the point of view of the user terminal or in the vicinity of the neighboring base station.

In this specification, a cell refers to a component carrier having a coverage of a signal transmitted from a transmission point or a transmission point or a transmission point or a transmission / reception point of a signal transmitted from a transmission / reception point, and a transmission / reception point itself .

The uplink (uplink, UL, or uplink) refers to a method for transmitting / receiving data to / from a base station by a terminal, and the downlink (DL, or downlink) refers to a method for transmitting / receiving data to / A downlink may refer to a communication or communication path from a multipoint transmission / reception point to a terminal, and an uplink may refer to a communication or communication path from a terminal to a multiple transmission / reception point. At this time, in the downlink, the transmitter may be a part of the multiple transmission / reception points, and the receiver may be a part of the terminal. Also, in the uplink, the transmitter may be a part of the terminal, and the receiver may be a part of multiple transmission / reception points.

The uplink and downlink transmit and receive control information through a control channel such as a physical downlink control channel (PDCCH) and a physical uplink control channel (PUCCH), and transmit and receive control information through PDSCH (Physical Downlink Shared CHannel), PUSCH (Physical Uplink Shared CHannel) Hereinafter, a state in which a signal is transmitted / received through a channel such as a PUCCH, a PUSCH, a PDCCH, and a PDSCH is expressed as 'transmission / reception of PUCCH, PUSCH, PDCCH and PDSCH' do.

In order to clarify the description, the technical idea is described below mainly in 3GPP LTE / LTE-A / NR (New RAT) communication system, but the technical features are not limited thereto.

After studying 4G (4th-generation) communication technology, 3GPP is studying 5G (5th-generation) communication technology to meet ITU-R's next generation wireless access technology requirements. Specifically, 3GPP is conducting research on a new NR communication technology that is independent of LTE-A pro and 4G communication technology that improved LTE-Advanced technology to meet ITU-R requirements with 5G communication technology. Although both LTE-A pro and NR are supposed to be submitted with 5G communication technology, the embodiments will be described mainly with reference to NR for convenience of explanation.

The operating scenarios in NR define various operating scenarios by adding consideration to satellite, automobile, and new vertical in the existing 4G LTE scenario. In the service aspect, we have the eMBB (Enhanced Mobile Broadband) scenario, (MMTC) scenarios that require low data rates and asynchronous connections, and Ultra Reliability and Low Latency (URLLC) scenarios that require high responsiveness and reliability and can support high-speed mobility. .

In order to satisfy such a scenario, NR discloses a wireless communication system employing new waveform and frame structure technology, low latency technology, high frequency band (mmWave) support technology, and forward compatible technology. In particular, NR systems offer various technological changes in terms of flexibility in order to provide forward compatibility. The main technical features are described below with reference to the drawings.

<NR System General>

FIG. 1 is a view schematically showing a structure of an NR system to which the present embodiment can be applied.

Referring to FIG. 1, the NR system is divided into 5GC (5G Core Network) and NR-RAN parts, and the NG-RAN is divided into a user plane (SDAP / PDCP / RLC / MAC / PHY) GNB and ng-eNBs that provide a plane (RRC) protocol termination. The gNB mutual or gNB and ng-eNB are interconnected via the Xn interface. gNB and ng-eNB are connected to 5GC through NG interface respectively. 5GC may be configured to include AMF (Access and Mobility Management Function) for controlling the control plane such as terminal connection and mobility control function and UPF (User Plane Function) for controlling the user data. NR includes support for frequency bands below 6GHz (FR1, Frequency Range 1) and over 6GHz (FR2, Frequency Range 2).

gNB denotes a base station providing NR user plane and control plane protocol termination to a UE, and ng-eNB denotes a base station providing an E-UTRA user plane and a control plane protocol termination to a UE. The base station described in the present specification should be understood to mean gNB and ng-eNB, and may be used to refer to gNB or ng-eNB as needed.

<NR Waveform, Numerical Rollers and Frame Structure>

NR uses a CP-OFDM waveform using a cyclic prefix for downlink transmission and CP-OFDM or DFT-s-OFDM for uplink transmission. OFDM technology is easy to combine with multiple input multiple output (MIMO) and has the advantage of using a low complexity receiver with high frequency efficiency.

On the other hand, in NR, the requirements for data rate, delay rate, coverage, etc. are different for each of the three scenarios described above. Therefore, it is necessary to efficiently satisfy requirements for each scenario through frequency bands constituting an NR system . To this end, a technique has been proposed for efficiently multiplexing a plurality of different numerology-based radio resources.

Specifically, the NR transmission medium is determined based on the sub-carrier spacing and the CP (Cyclic Prefix), and is based on 15 kHz as shown in Table 1 below

The value is used as an exponent value of 2 and exponentially changed.

[Table 1]

As shown in Table 1 above, the NR bearings can be classified into five types according to the subcarrier interval. This is different from LTE subcarrier spacing, which is one of the 4G communication technologies, fixed at 15kHz. Specifically, the subcarrier intervals used for data transmission in NR are 15, 30, 60, and 120 kHz, and the subcarrier intervals used for synchronous signal transmission are 15, 30, 12, and 240 kHz. Also, the extended CP applies only to the 60 kHz subcarrier interval.

On the other hand, a frame structure in NR is defined as a frame having a length of 10 ms constituted by 10 subframes having the same length of 1 ms. One frame can be divided into 5 ms half frames, and each half frame includes 5 sub frames. In the case of a 15 kHz subcarrier interval, one subframe is composed of one slot, and each slot is composed of 14 OFDM symbols.

2 is a diagram for explaining a frame structure in an NR system to which the present embodiment can be applied.

Referring to FIG. 2, the slot is composed of 14 OFDM symbols fixedly in the case of the normal CP, but the length of the slot may vary according to the subcarrier interval. For example, in the case of a spreader with 15khz subcarrier spacing, the slot is of the same length as the subframe with a length of 1ms. On the other hand, in the case of a spreader with a 30 kHz subcarrier interval, the slot is composed of 14 OFDM symbols, but two slots may be included in one subframe with a length of 0.5 ms. That is, the subframe and the frame are defined with a fixed time length, and the slot is defined by the number of symbols, and the time length may vary according to the subcarrier interval.

NR defines a basic unit of scheduling as a slot and also introduces a minislot (or a sub-slot or a non-slot based schedule) to reduce the transmission delay of the radio section. If a wide subcarrier interval is used, the transmission delay in the radio section can be reduced because the length of one slot is shortened in inverse proportion. A minislot (or subslot) is for efficient support of URLLC scenarios and can be scheduled in 2, 4, or 7 symbol units.

Also, unlike LTE, NR defines the uplink and downlink resource allocation as a symbol level within one slot. In order to reduce the HARQ delay, a slot structure capable of directly transmitting HARQ ACK / NACK in a transmission slot is defined, and the slot structure is referred to as a self-contained structure.

NR is designed to support a total of 256 slot formats, of which 62 slots are used in Rel-15. In addition, a common frame structure constituting an FDD or a TDD frame is supported through a combination of various slots. For example, a slot structure in which all symbols of a slot are set as a downlink, a slot structure in which symbols are both set in an uplink, and a slot structure in which a downlink symbol and an uplink symbol are combined is supported. Also, NR supports that data transmission is scheduled in one or more slots. Accordingly, the base station can inform the terminal whether the slot is a downlink slot, an uplink slot, or a flexible slot using a Slot Format Indicator (SFI). The BS can indicate the slot format by indicating the index of the table configured through the RRC signaling using the SFI by dynamically specifying the UE through the DCI (Downlink Control Information) or instructing the RRC through the RRC statically or quasi-statically It is possible.

<NR Physical Resources>

An antenna port, a resource grid, a resource element, a resource block, and a bandwidth part are considered in relation to a physical resource in the NR. .

An antenna port is defined such that the channel on which the symbol on the antenna port is carried can be deduced from the channel on which another symbol on the same antenna port is carried. If a large-scale property of a channel on which a symbol on one antenna port is carried can be deduced from a channel on which symbols on another antenna port are carried, the two antenna ports may be quasi co-located (QC / QCL) quasi co-location relationship. Here, the wide-range characteristic includes at least one of a delay spread, a Doppler spread, a frequency shift, an average received power, and a received timing.

FIG. 3 is a diagram for explaining a resource grid supported by a radio access technology to which the present embodiment is applicable.

Referring to FIG. 3, a resource grid may have a resource grid according to each network resource since NR supports a plurality of network resources in the same carrier. Also, the resource grid may exist depending on the antenna port, subcarrier spacing, and transmission direction.

A resource block consists of 12 subcarriers and is defined only in the frequency domain. In addition, a resource element is composed of one OFDM symbol and one subcarrier. Therefore, as shown in FIG. 3, the size of one resource block may vary according to the subcarrier interval. In addition, NR defines "Point A" that acts as a common reference point for the resource block grid, a common resource block, and a virtual resource block.

4 is a diagram for explaining a bandwidth part supported by a radio access technology to which the present embodiment can be applied.

In NR, the maximum carrier bandwidth is set from 50 MHz to 400 MHz according to the subcarrier interval, unlike LTE in which the carrier bandwidth is fixed at 20 MHz. Therefore, it is not assumed that all terminals use all of these carrier bandwidths. Accordingly, as shown in FIG. 4, the NR can specify a bandwidth part within the carrier bandwidth and use the part. In addition, the bandwidth part is composed of a subset of consecutive common resource blocks in association with one reader roller and can be activated dynamically over time. The terminal has up to four bandwidth parts of uplink and downlink, respectively, and data is transmitted and received using the active bandwidth part at a given time.

In the case of paired spectrum, the uplink and downlink bandwidth parts are set independently, and in the unpaired spectrum, unnecessary frequency re-tuning between downlink and uplink operations is prevented The bandwidth parts of the downlink and uplink are set in pairs so that the center frequency can be shared.

<NR Initial Connection>

In the NR, a terminal performs cell search and random access procedures to access a base station and perform communication.

The cell search is a procedure in which a terminal synchronizes with a cell of a corresponding base station, acquires a physical layer cell ID, and acquires system information using a synchronization signal block (SSB) transmitted from the base station.

5 is a diagram exemplarily showing a synchronization signal block in a radio access technology to which the present embodiment can be applied.

Referring to FIG. 5, the SSB includes a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) occupying one symbol and 127 subcarriers, and a PBCH spanning three OFDM symbols and 240 subcarriers.

The terminal monitors the SSB in the time and frequency domain and receives the SSB.

SSB can be transmitted up to 64 times for 5ms. A plurality of SSBs are transmitted in different transmission beams within a time period of 5 ms, and the terminal performs detection based on a specific one beam used for transmission, assuming that the SSB is transmitted every 20 ms period. The number of beams that can be used for SSB transmission within 5ms time can be increased as the frequency band is higher. For example, up to four SSB beams can be transmitted at a frequency of 3 GHz or less, and SSBs can be transmitted at a maximum of 8 at a frequency band of 3 to 6 GHz and at a maximum of 64 different beams at a frequency band of 6 GHz or more.

The SSB includes two slots in one slot, and the start symbol and the repetition number in the slot are determined according to the subcarrier interval as follows.

On the other hand, SSB is not transmitted at the center frequency of the carrier bandwidth unlike the SS of the conventional LTE. That is, the SSB can be transmitted not only in the center of the system band, but can also transmit a plurality of SSBs in the frequency domain when supporting broadband operation. Accordingly, the terminal monitors the SSB using a synchronization raster, which is a candidate frequency position for monitoring the SSB. The carrier raster and the synchronous raster, which are the center frequency position information of the channel for the initial connection, are newly defined in the NR. The synchronous raster has a wider frequency interval than the carrier raster, .

The terminal can acquire the MIB through the PBCH of the SSB. The MIB (Master Information Block) includes minimum information for the UE to receive Remaining Minimum System Information (RMSI) broadcasted by the network. In addition, the PBCH includes information on the position of the first DM-RS symbol in the time domain, information for monitoring the SIB1 by the UE (for example, SIB1 transmitter information, information related to the SIB1 CORESET, Related parameter information, etc.), offset information between the common resource block and the SSB (the location of the absolute SSB in the carrier is transmitted via SIB1), and the like. Herein, the SIB1 Node RL information is also applied to the message 2 and the message 4 of the random access procedure for accessing the base station after the UE completes the cell search procedure.

The above-mentioned RMSI means SIB1 (System Information Block 1), and SIB1 is broadcast periodically (ex, 160 ms) in the cell. The SIB1 includes information necessary for the UE to perform the initial random access procedure, and is periodically transmitted through the PDSCH. In order for the UE to receive the SIB1, the UE must receive the NIC relay information used for the SIB1 transmission and the CORESET (Control Resource Set) used for the SIB1 scheduling through the PBCH. The UE confirms the scheduling information for SIB1 using SI-RNTI in the CORESET, and acquires SIB1 on the PDSCH according to the scheduling information. SIBs other than SIB1 may be periodically transmitted or may be transmitted according to the request of the terminal.

6 is a diagram for explaining a random access procedure in a radio access technology to which the present embodiment can be applied.

Referring to FIG. 6, when the cell search is completed, the UE transmits a random access preamble for random access to the base station. The random access preamble is transmitted through the PRACH. Specifically, the random access preamble is transmitted to the base station through the PRACH, which is composed of consecutive radio resources in a specific slot repeated periodically. In general, a contention-based random access procedure is performed when a UE initially accesses a cell, and a contention-based random access procedure is performed when random access is performed for beam failure recovery (BFR).

The UE receives a random access response to the transmitted random access preamble. The random access response may include a random access preamble identifier (ID), a UL grant (uplink radio resource), a temporary C-RNTI (Temporary Cell-Radio Network Temporary Identifier), and a TAC (Time Alignment Command). Since one random access response may include random access response information for one or more UEs, the random access preamble identifier may be included to inform which UE the UL Grant included, the temporary C-RNTI and the TAC are valid for. The random access preamble identifier may be an identifier for the random access preamble received by the base station. The TAC may be included as information for the UE to adjust the uplink synchronization. The random access response may be indicated by a random access identifier on the PDCCH, i.e., Random Access-Radio Network Temporary Identifier (RA-RNTI).

The MS receiving the valid random access response processes the information included in the random access response and performs the scheduled transmission to the BS. For example, the terminal applies the TAC and stores the temporary C-RNTI. In addition, using the UL Grant, data stored in the buffer of the terminal or newly generated data is transmitted to the base station. In this case, information that can identify the terminal should be included.

Finally, the UE receives a downlink message to resolve the contention.

<NR CORESET>

The downlink control channel in NR is transmitted in a CORESET (Control Resource Set) having a length of 1 to 3 symbols, and transmits up / down scheduling information, SFI (Slot format Index), TPC (Transmit Power Control) .

In this way, the concept of CORESET is introduced to ensure the flexibility of the system. A CORESET (Control Resource Set) refers to a time-frequency resource for a downlink control signal. The terminal may decode the control channel candidate using one or more search spaces in the CORESET time-frequency resource. CORESET-based QCL (Quasi CoLocation) assumption is established, which is used for the purpose of informing the characteristic of analogue beam direction besides delayed spread, Doppler spread, Doppler shift, average delay which are assumed by QCL.

Fig. 7 is a diagram for explaining CORESET. Fig.

Referring to FIG. 7, a CORESET may exist in various forms within a carrier bandwidth in one slot, and a CORESET may be composed of a maximum of 3 OFDM symbols in a time domain. In addition, CORESET is defined as a multiple of six resource blocks up to the carrier bandwidth in the frequency domain.

The first CORESET is directed through the MIB as part of the initial bandwidth part configuration to receive additional configuration information and system information from the network. After establishing a connection with a base station, the terminal can receive and configure one or more CORESET information through RRC signaling.

In the prior art, relay-based side-link communication

8 is a diagram illustrating a control plane protocol stack for one-to-one side-link communications.

Referring to FIG. 8, in the conventional LTE technology, the UE does not establish or maintain a logical connection with the receiving terminals for one-to-many sidelobe communication. For one-to-one side-link communications, the upper layer (e.g., the PC5 signaling protocol) establishes and maintains a logical connection. The control plane protocol stack for establishing, maintaining, and releasing logical connections for one-to-one side link communications is shown in FIG. That is, the MSs maintain a logical connection to the upper layer of the PDCP using the PC5 signaling protocol.

In the conventional LTE technology, a relay using a side link (ProSe UE-to-Network Relay) provides an L3 forwarding function capable of relaying arbitrary type of IP traffic between a remote node and a network. For convenience of description, in the conventional LTE, a relay using a side link (ProSe UE-to-Network Relay) is indicated as an L3 relay or an L3 relay node. Only one single carrier (i.e., public secure ProSe carrier) operation is supported for the remote node and the L3 relay node. That is, the Uu interface between the terminal and the base station and the PC5 interface between the terminals were the same carrier for the L3 relay and the remote node.

The remote node must be authorized by the higher layer and may be in the coverage of public safety ProSe carriers. Or the remote node may be out of coverage on a supported carrier that includes L3 relay discovery, public safety ProSe carriers for selection and communication. The L3 relay node is always in coverage.

In conventional LTE technology, the base station may broadcast a minimum and / or maximum Uu link quality (RSRP) threshold for initiating the L3 relay discovery procedure.

When the terminal is in RRC IDLE, the terminal can autonomously start or stop the L3 relay discovery procedure using the threshold when the base station broadcasts the resource pool.

The remote node can determine when to start monitoring for L3 relay discovery. The remote node can send an L3 relay discovery solicitation message on RRC IDLE or RRC CONNECTED. The base station can broadcast a threshold, which is used to determine whether the remote node can send an L3 relay discovery solicitation message to connect or communicate with the L3 relay node. For example, at the cell coverage edge, the communication quality is lower than the threshold, and the L3 relay can be solved. A remote node in the RRC CONNECTED state may use the broadcast threshold to indicate to the base station that it is a remote node and wants to participate in L3 relay discovery and / or communication. For example, a side link terminal information message may be used to indicate support for communication participation.

L2 relay-based side-link communication

The L3 relay provided in the conventional LTE technology has an advantage that it can relay any type of IP traffic between the remote node and the network, but it can not provide reachability to the remote node connected through the relay in the network. In addition, there is a problem that it is difficult to control the power consumption of the remote node or control the QoS for the corresponding traffic. Therefore, it is difficult to apply the side-link-based relay to terminals that require efficient power control and QoS control like wearable terminals. To solve this problem, we can consider Layer 2 (L2) based relay technology. However, since there is no specific method for supporting data transmission through the layer 2-based relay node, there is a problem that the traffic of the remote node can not be effectively classified and processed.

NR (New Radio) based multi-hop relay

As described above, in the NR that can use the high frequency band, the utilization of the relay technology needs to be increased by using a wider bandwidth than the LTE and the use of the multi-beam system. This allows operators to more easily build a dense network of self-backhauled NR cells that provide backhaul functionality by themselves. However, due to the small coverage of the millimeter wave band, it costs a lot of money to apply all cells to the wired / optical line basis. It may therefore be necessary to connect the NR cell / base station to a base station connected to a wired / optical fiber via a plurality of relay hops. However, since it supports only a single hop based relay according to the conventional LTE technology, it can not provide a multi-hop relay. In addition, conventional LTE technology relays are provided based on L3. Especially, multi-hop relay needs to process data in multi-hop, so it may be difficult to transmit delay sensitive 5G service. In order to support 5G low-latency data transmission and QoS support, L2-based relay transmission described above may be preferable to L3-based relay transmission such as LTE.

The structure shown in FIG. 14 or FIG. 15 to be described below can be considered as an L2 structure for supporting this. However, no concrete operation method has been provided for the structure. As described above, there is no specific method for supporting data transmission through the layer 2-based relay, so that the traffic of the terminal can not be effectively classified and processed.

Disclosure of the Invention The present disclosure, which is devised to solve the above-described problems, provides a method and apparatus for efficiently distinguishing and processing traffic of a remote node in a structure in which a remote node transmits data to a mobile communication network through a wireless connection based on a layer 2 relay I want to. In particular, the present invention provides a method and apparatus for efficiently classifying and processing traffic through an adaptation layer between a remote node and a relay node or between a relay node and a base station.

Embodiments provided below may be implemented individually or in combination of each other. The present invention can be applied not only to LTE based wireless connection but also to wireless connection based on next generation mobile communication (5G mobile communication). Hereinafter, a data radio bearer will be described as a reference, but the present invention can also be applied to a signaling radio bearer.

For convenience of description, an L2 relay node may be described as a relay node, a relay terminal, a relay device, or the like, and the relay node may be a terminal or a base station. Hereinafter, the L2 remote node means a terminal wirelessly connected through a relay node, and can be described as a terminal, a remote terminal, a remote device, a remote node, and the like.

The following terms can be used to describe the following terms, and the terms used herein are for convenience of description and are not limited to the corresponding terms that can be interpreted in the same sense. In other words, the terms in this disclosure may be replaced with other terms having the same or equivalent roles.

- Integrated access and backhaul (IAB) node: A RAN node that provides a wireless backhaul of wireless access and access traffic to the terminal. For example, a node that can configure a backhaul to another NR node using NR radio technology and a node that is physically unable to connect to another NR node through a wired / optical line. Relay nodes, NR-RNs, NR relays, unified nodes, etc.

- IAB-donor: A radio network node / base station / gNB / part of gNB that provides and terminates a terminal interface (NG interface, for example N2, N3 interface) to the core network. For example, it is a RAN node that provides a terminal interface to a core network and provides a wireless backhaul to an IAB node, and is physically connected to the core network or another base station through a wired / optical line. NR radio technology can be used to configure backhaul with other NR nodes such as base station, CU, DU, and core network nodes (AMF, UPF, etc.). Base station, IAB-DN, DgNB, DN, donor base station, and so on.

The embodiments provided below can be used in the case of relaying the NR technology-based access of the NR terminal to the NR base station (donor base station) through the NR backhaul (of the IAB node). In addition, the embodiment provided below can be used when relaying LTE technology based access of an LTE terminal to an LTE base station (donor base station) through an NR backhaul (of an IAB node). In addition, embodiments provided below may also be used when relaying NR technology-based access of an NR terminal to an LTE base station (or donor base station) that provides EN-DC through an NR backhaul (of an IAB node).

As shown in FIG. 4 or 5, each IAB node includes one DU (Distribute Unit) and one MT (mobile termination). Through the MT, the IAB node is connected to the upper IAB node or the donor base station. Through DU, the IAB node establishes an RLC channel to the terminal. Then, through DU, the IAB node establishes an RLC channel to the lower IAB node.

The user plane data of the relay node is relayed between the remote node and the network through the relay node at the RLC top. The PDCP entity for one radio bearer is terminated between the remote node and the base station and the RLC, MAC, PHY or non-3GPP transport layer is terminated on each link.

9 is a view for explaining a relay node operation according to an embodiment.

Referring to FIG. 9, in a method of processing remote node data, a relay node may perform a step of receiving configuration information for configuring an adapter entity from a base station (S910). For example, the relay node may receive configuration information for configuring the adapter entity from higher-layer signaling from the base station.

The adaptation entity may mean an entity for controlling the operation of the adaptation layer, which is additionally configured between the PDCP layer and the RLC layer. Alternatively, the adapter entity may be configured in the PDCP layer, but may be an entity distinct from the PDCP entity. The terms of the adapter entity may be used in various ways and are not limited to the terms in this specification.

Meanwhile, the adapter entity may generate header information including at least one of a relay node identifier, a remote node identifier, a DRB identifier, an SRB identifier, and a logical channel identifier. In addition, the adapter entity may add the generated header information to the PDCP PDU transmitted from the PDCP layer to the adapter entity and forward the PDCP PDU to the RLC entity.

In addition, the relay node may perform the step of configuring the adapter entity by linking the PDCP entity and the RLC entity based on the configuration information (S920). For example, the relay node can configure the adapter entity based on the instruction information indicating the association of the PDCP entity and the adapter entity received from the base station.

The adaptation entity can be composed of only one relay node as a single entity. Alternatively, the adapter entity may be composed of a plurality of PDCP entity or RLC entity.

In addition, the relay node may perform a step of discriminating and transmitting data to be transferred from the adapter entity to the RLC entity and data to be transmitted to the PDCP entity (S930). For example, the adaptation entity can associate a remote node-specific or a radio bearer-specific signal with an RLC bearer of an RLC entity.

Alternatively, the adaptation entity can process the data through the mapping information between the remote node identifier, the radio bearer identifier, and the logical channel identifier of the relay node.

On the other hand, the adapter entity checks the header information of the adapter entity or the above-described identifier information with respect to the data received and transmitted from the lower layer, and determines whether to forward the data to an upper layer (ex. PDCP layer) To the RLC entity that is mapped to the information, and determines whether to transfer the RLC entity to the remote node.

This discrimination process determination operation may be applicable to both downlink data and uplink data. When the adapter entity transfers data to a remote node, a relay node, or a base station, header information is added to one DRB or a plurality of DRBs Can be used.

As described above, according to this operation, the traffic between the remote node and the relay node or between the relay node and the base station can be distinguished and processed. According to the present embodiment, there is an effect that the traffic to the remote node can be controlled according to the QoS, and the network can control the power consumption and the like in detail.

10 is a view for explaining a base station operation according to an embodiment.

Referring to FIG. 10, in a method of processing remote node data, a base station may perform a step of configuring an adapter entity by linking a PDCP entity and an RLC entity (S1010). For example, an adaptation entity may be configured between the PDCP layer and the RLC layer. Alternatively, the adaptation entity may be configured in the PDCP layer, but may be configured separately from the PDCP entity. On the other hand, the adapter entity may be constructed by peering with the adapter entity of the relay node.

In addition, the base station may generate header information for identifying data of the relay node and the remote node in the adapter entity and add the header information to the PDCP PDU (S1020). For example, the header information may include at least one of a relay node identifier, a remote node identifier, a DRB identifier, an SRB identifier, and a logical channel identifier.

In addition, if the uplink data is received, the adapter entity can confirm and remove the header information and transmit the corresponding data to the PDCP entity. If the data to be processed by the adapter entity is downlink data, the adapter entity may add header information to the PDCP PDU.

In addition, the base station may perform a step of transmitting data to be transmitted to the relay node and the remote node by dividing the data into RLC entities associated with the adapter entity (S 1030). For example, the adaptation entity can associate the data delivered from the upper layer with the RLC bearer of the RLC entity for each remote node or the radio bearer.

The adaptation entity may be composed of only one entity in the base station as a single entity. Alternatively, the adapter entity may be composed of a plurality of PDCP entity or RLC entity.

11 is a view for explaining a base station operation according to another embodiment.

Referring to FIG. 11, a base station can perform an operation for configuring an adapter entity to a relay node. S1100 in Fig. 11 is the same as S1010, and S1130 and S1140 are the same as S1020 and S1030. That is, the BS may additionally perform steps S1110 and S1120 to configure the adapter entity in the relay node in FIG.

However, steps S1110 and S1120 may be performed before S1100, and the procedure may be divided into S1110, S1100, and S1120. That is, there is no limitation on the order in which the steps S1110 and S1120 are performed. Also, steps S1110 and S1120 may be performed through one higher layer signaling message in one step.

For example, the base station may perform the step of transmitting configuration information for configuring the adapter entity to the relay node to the relay node (S1110). For example, the relay node may receive configuration information for configuring the adapter entity from higher-layer signaling from the base station.

The base station may further perform step S1120 to transmit to the relay node indication information indicating a connection between the PDCP entity of the relay node and the adapter entity of the relay node. For example, the relay node can configure the adapter entity based on the instruction information indicating the association of the PDCP entity and the adapter entity received from the base station. If steps S1110 and S1120 are performed in one step, the configuration information for configuring the adapter entity and the indication information for instructing the association of the PDCP entity and the adapter entity may be transmitted in one higher layer message.

When the adapter object is configured, the relay node can distinguish the data to be transferred from the adapter object of the relay node to the RLC entity of the relay node and the data to be transmitted to the PDCP entity.

As described above, according to this operation, the traffic between the remote node and the relay node or between the relay node and the base station can be distinguished and processed. According to the present embodiment, there is an effect that the traffic to the remote node can be controlled according to the QoS, and the network can control the power consumption and the like in detail.

Hereinafter, the wireless relay operation including the operations of the relay node, the remote node, and the base station will be described in more detail. Each of the steps described below and the embodiments of the respective constitutions can be applied in combination with each other.

In the following, a single-hop wireless relay-based transmission is described, but this is for convenience of description and can be applied to multi-hop relay based transmission as well. For example, a method of distinguishing and processing data of one or more remote nodes through a radio bearer (or RLC bearer) between a relay node and a base station will be described. However, when a remote node and a base station are connected through a plurality of relay nodes, A method of distinguishing and processing data of one or more remote nodes through a radio bearer (or RLC bearer) between a node and a relay node can be similarly applied.

12 is a diagram illustrating an example of a user plane wireless protocol stack based on an L2 relay node.

Referring to FIG. 12, a remote node (a remote terminal) is connected to a relay node (relay terminal) through a PC 5 interface, and a relay node is connected to a base station through a Uu interface. The relay node can be connected to the base station by configuring the adapter entity.

13 is a diagram showing another example of a user plane wireless protocol stack based on an L2 relay node.

Referring to FIG. 13, a remote node can configure an adapter object. In addition, the remote node and the relay node may be configured using a technology other than the 3GPP technology such as WiFi. As in FIG. 12, the relay node and the base station can configure each adapter entity to perform the connection.

14 is a diagram showing an example of the L2-based relay structure. 15 is a diagram showing another example of the L2-based relay structure.

14 and 15 disclose various forms of the relay structure when the relay node is an IAB node. Herein, UE denotes a remote node, and IAB-donor denotes a base station.

14A shows a case where the adapter entity is located under the RLC segmentation entity in the case of two IAB-nodes. As shown in FIG. 14B, the RLC segmentation entity may be configured as an RLC entity. Alternatively, an adaptation entity may be configured on the RLC entity, as shown in FIG. 14 (C).

Alternatively, as shown in FIG. 14 (d), a GTP-U entity may be constructed on the adapter entity and logically connected to the IAB-donor. FIG. 14 (e) shows a structure in the case where an IP layer, a UDP layer, and the like are present on the adapter entity, and the IAB nodes 1 and 2 may be configured differently.

In the case of FIG. 15, the adaptation entity is configured between the PDCP and the RLC entity, and illustratively shows a structure in which the IAB-donor is connected to the UPF.

As discussed above, the relay structure can be configured in a variety of ways, and the description below can be applied to all of the structures described above. The relay structure is not limited.

In the following description, the remote node is referred to as " terminal " in order to more clearly distinguish the remote node and the relay node.

As shown in FIGS. 12 to 15, traffic of one or a plurality of terminals may be mapped to a single radio bearer (or RLC bearer) on a radio interface between a relay node and a base station. Here, the RLC bearer indicates the channel between the RLC entity of the relay node and the RLC entity of the base station to be peered. For convenience of description, the RLC bearer is referred to as a radio bearer, but this can be replaced by an RLC bearer or an RLC channel. A plurality of radio bearers may be used to carry traffic of different QoS classes for one or more terminals.

In addition, the traffic of the relay node itself can be multiplexed through the radio bearer between the relay node relaying the traffic from the terminal to the terminal and the base station. An admission layer is supported over the air interface between the relay node and the base station to identify the bearer corresponding to the terminal / relay node.

Different bearers in the radio interface bearer between one relay node and the base station and different bearers of the bearer are indicated as additional information in the adaptation layer header added to the PDCP PDU. A terminal is identified by a terminal identifier in an adaptation layer on a radio interface between a relay node and a base station. For example, the terminal identifier may be identified by a local identifier (i.e., an index). In another example, the terminal identifier may be identified by an identifier (C-RNTI, I-RNTI) assigned by the base station. The terminal identifier is known to at least the base station and the relay node. In order to identify the bearer of the terminal, a bearer identifier is indicated by the additional information contained in the adaptation layer header.

An adaptation layer may be supported through non-3GPP access to a short range link between the terminal and the relay node. The adaptation layer header is added to the PDCP PDU. On the Non-3GPP, the adaptation layer header includes a radio bearer identifier.

Hereinafter, a description will be given of a method of distinguishing and processing traffic in the relay and the base station in the case of downlink and uplink, respectively.

For example, a radio bearer on a radio interface between one relay node and a base station can distinguish one DRB for one or a plurality of terminals and a DRB between a relay node and a base station.

In another example, a DRB on a radio interface between one relay node and a base station can transmit and receive DRBs for one or a plurality of terminals and a DRB between a relay node and a base station.

For convenience of explanation, traffic of two DRBs (one DRB of the first terminal and one DRB of the second terminal) provided by two terminals (a first terminal and a second terminal) and a traffic between a relay node and a base station It is assumed that one DRB (one DRB of the relay node) through the interface is transmitted through a single DRB through the air interface between the relay node and the base station. This is for convenience of description, and it is also included in the scope of the present embodiment that one or more DRBs by one or more terminals and one or more DRBs between the relay node and the base station are separately transmitted between the relay node and the base station.

Also, for convenience of description, one DRB relayed to the first terminal is denoted by a first DRB, and one DRB relayed to a second terminal is denoted by a second DRB. And one DRB through the Uu interface between the relay node and the base station is denoted by the third DRB.

In the mobile communication network, the radio bearer is used for data transmission between the layer 2 of the UE and the layer 2 of the BS. Therefore, the first DRB indicates the DRB configured between the PDCP of the first UE and the PDCP of the BS. Which are connected via a relay node on the above-described relay structure. For convenience of description, the PDCP entity of the base station peered to the PDCP entity of the first terminal is represented by the first PDCP entity. Similarly, the second DRB indicates the DRB configured between the PDCP of the second terminal and the base station PDCP. The DRB is connected through the relay node. For convenience of description, the PDCP entity of the base station peered to the PDCP entity of the second terminal is denoted by the second PDCP entity. In the base station, the first PDCP entity and the second PDCP entity are composed of different PDCP entities.

The third DRB represents a DRB configured between the PDCP of the relay node and the PDCP of the base station through the air interface between the relay node and the base station. For convenience of description, the PDCP entity of the base station peered to the PDCP entity of the relay node is denoted by the third PDCP entity. In the base station, the first PDCP entity, the second PDCP entity, and the third PDCP entity are composed of different PDCP entities.

Hereinafter, various configuration examples of the adapter entity for relay communication will be described.

How to configure the adapter object

The adaptation layer may be configured as a separate layer between the PDCP layer and the RLC layer. Or an adaptation layer may be configured as part of the PDCP layer. The base station can instruct the relay node through the RRC connection reconfiguration message to configure the adaptation entity to perform the function of the adaptation layer. Alternatively, the base station can indicate the configuration of the adapter entity as a sub-entity of the PDCP entity.

The base station can associate a radio bearer for each UE connected to the corresponding relay node from the adapter entity of the first relay node directly connected by the UE. The base station transmits, to the PDCP PDUs of the respective radio bearers of the respective terminals, a terminal identifier or a radio bearer identifier capable of distinguishing the radio bearers of the corresponding terminal from the adaptation entity of the first relay node directly connected to the terminal To be added.

The base station can link the radio bearers for the lower nodes of the lower nodes wirelessly connected to the relay node in the adapter object of the relay node.

The base station can associate the PDCP entity terminated at the corresponding relay node with the adapter entity of the relay node.

Accordingly, the base station can allow the relay node to separately transmit data for each terminal or the radio bearer.

Embodiment 1: Configure the adapter object to specify the relay node

The adaptation layer may be configured to be relay node specific.

For example, the base station can configure one adapter entity in the relay node. One or more radio bearers of one or more terminals and one or more radio bearers between a relay node and a base station can be distinguished and processed through one adaptation entity.

In another example, the base station may configure one relay node and one adaptation object for processing data transmission / reception between the base station and the relay node and one adaptation object for processing data transmission / reception between the relay node and the one or more terminals have.

In another example, the base station may configure one relay node to process data between the base station and the relay node and to process the relay node and the data transmission / reception between the relay node and the plurality of terminals.

Second Embodiment: Constructing an adapter object to specify a terminal

The adaptation layer may be configured to be terminal specific.

For example, the base station can configure one adapter entity for each terminal accommodated by the relay node. One or more radio bearers for one terminal and one or a plurality of radio bearers between the relay node and the base station can be discriminated and processed through one adaptation entity.

For example, the base station may configure one relay node and one relay node to process data between the base station and the relay node, and one or more relay nodes to process data between the relay node and the plurality of terminals. can do.

For example, the base station may include one or a plurality of adaptation objects for processing data transmitted / received between the base station and the relay node according to the terminals, one or more adaptation objects for processing data between the relay node and the plurality of terminals, The relay node can configure the relay node.

In another example, the base station may configure one or a plurality of adaptation objects in the relay node for processing data transmission / reception between the base station and the relay node and for processing data transmission / reception between the relay node and one or more terminals.

Third Embodiment: Configuration of an adapter object for each radio bearer of a relay node

The adaptation layer can be configured for each radio bearer of the relay node.

For example, the base station can configure one relay entity for each radio bearer of the terminal in the relay node. One or more radio bearers of one or more terminals and one radio bearer between the relay node and the base station can be discriminated and processed through one adaptation entity.

In another example, the base station may include a bearer-specific adapter entity for processing data transmission and reception between the base station and the relay node, one or more adapter objects for processing data transmission between the relay node and one or more terminals, can do.

In another example, the base station may configure one or more bearer-specific adapter objects for processing bearer-specific data transmission and reception between the base station and the relay node and data transmission / reception between the relay node and one or more terminals in the relay node .

Embodiment 4: Configuration of an adapter object for each radio bearer of the UE

The adaptation layer may be configured for each radio bearer of the UE.

For example, the base station can configure one admission entity for each radio bearer of each terminal accommodated by the relay node. One radio bearer of one terminal and one radio bearer between a relay node and a base station can be distinguished and processed through one adaptation entity.

For example, the base station may include an adapter entity for each radio bearer of the terminal for processing radio bearer data transmission and reception between the base station and the relay node, one or more acknowledgments for processing data transmission between the relay node and one or more terminals, The relay node can configure the relay node.

In another example, the base station may be configured to transmit and receive radio bearer data of a terminal between a base station and a relay node, and to receive bearer-specific admission objects of one or more terminals for processing data transmission / reception between the relay node and one or more terminals It can be configured in the relay node.

As described above, the adaptation entity can be configured in various ways such as relay node, terminal, radio bearer, and the like.

Various embodiments of a method of processing downlink data transmitted to a mobile station by a base station will be described below.

Downlink processing method

16 is a diagram illustrating a layer 2 structure of a base station for downlink transmission in a conventional LTE radio access technology.

Referring to FIG. 16, in a conventional LTE technology, one radio bearer connects / links one PDCP entity and one RLC entity.

The base station adds an adaptation layer header to the PDCP PDU. The message header layer header includes a terminal identifier for identifying the UE, a bearer identifier (e.g., a radio bearer identifier (drb-Identity) or a signaling bearer identifier (srb-Identity, SRB0, SRB1, SRB2 ), Logical channel identification information associated with the QoS information (logicalChannelIdentity), and eps-BearerIdentity).

For example, the terminal identifier may be identified by a local identifier (i.e., an index). In another example, the terminal identifier may be identified by an identifier (C-RNTI, I-RNTI) assigned by the base station. Other examples include both a terminal identifier and a bearer identifier. Other examples may include one or more of a terminal identifier, a radio bearer identifier, and logical channel identification information.

The adaptation entity of the base station may receive the PDCP PDU through the first PDCP entity, the second PDCP entity, and the third PDCP entity, add an adaptation layer header, and forward the PDCP PDU to a lower layer (for example, an RLC entity).

Specifically, the following embodiments may be applied for data transmission through a relay node.

Embodiment 1: An embodiment in which one PDCP entity is connected to one RLC entity / linkage

The first PDCP entity, the second PDCP entity, and the third PDCP entity of the base station may have a first RLC entity, a second RLC entity, and a third RLC entity, respectively, connected / linked to the first, second and third RCP entities.

In the base station, the first RLC entity, the second RLC entity, and the third RLC entity are composed of different RLC entities.

The adaptation entity forwards the adaptation PDU including the PDCP PDU or the adaptation layer header to each corresponding RLC entity using at least one of the terminal identifier and the bearer identifier.

The RLC entity of the base station transmits the corresponding data to the corresponding RLC entity of the relay node through the air interface between the base station and the relay node.

The RLC entity of the relay node transmits the adaptation PDU including the RLC SDU or the adaptation layer header to the relay entity of the relay node.

The adaptation entity of the relay node can transmit the PDCP entity of the RCP entity or the relay node to the adaptation entity for data transmission by bearer or per-terminal using the at least one of the terminal identifier and the bearer identifier.

For this purpose, the BS can configure information for configuring the RLC entity connected / associated with each PDCP entity in the relay node through the RRC connection reconfiguration message.

17 is a diagram exemplarily showing radio bearer configuration information according to an embodiment.

Referring to FIG. 17, for example, a radio bearer including the third PDCP entity may include radio bearer configuration information as shown in FIG.

In another example, the radio bearer configuration information including the third PDCP entity may include information for instructing transmission / reception / transmission / reception / transmission / processing of data through the adaptation layer. The PDCP configuration information may include information for instructing the PDCP entity of the relay node to associate with the adapter entity. The PDCP entity that has received the RB configuration information that does not include the RB entity can transmit / receive / transmit / receive / transfer / process data from the PDCP entity to the RLC entity without passing through the adapter layer.

For example, the radio bearer of the relay node associated with the first PDCP entity or the second PDCP entity may include the adaptation configuration information without including the PDCP configuration information (pdcp-Config). The adaptation configuration information may include information for distinguishing the RLC entity associated with the corresponding radio bearer. For example, it may include RLC entity information mapped to each radio bearer for each UE. The RLC entity information may be distinguished using logical channel identifiers. Thus, the adaptation entity can transmit the PDCP PDUs of the respective radio bearers to the RLC entity of the UE or the lower node (for example, another relay node) through the associated RLC entity.

Embodiment 2: Embodiment in which a plurality of PDCP entities are connected / linked to one RLC entity

For example, the first PDCP entity, the second PDCP entity, and the third PDCP entity of the base station may have a common RLC entity connected thereto / connected thereto. In another example, the first PDCP entity and the third PDCP entity of the base station may have a common RLC entity connected thereto / connected thereto. In another example, the second PDCP entity and the third PDCP entity of the base station may have a common RLC entity connected thereto / connected thereto. As another example, the first PDCP entity of the base station and the second PDCP entity may be connected / linked to the RLC entity connected / associated with the third PDCP entity. In another example, the first PDCP entity of the base station may be connected / associated with the RLC entity connected / associated with the third PDCP entity. In another example, the second PDCP entity of the base station may be coupled / associated with the RLC entity associated / associated with the third PDCP entity.

One RLC entity is configured in association with the first PDCP entity, the second PDCP entity, and the third PDCP entity in the base station. Or one RLC entity in the base station is configured in association with the first PDCP entity and the third PDCP entity. Or one RLC entity in the base station is configured in association with the second PDCP entity and the third PDCP entity. For convenience of description, this is referred to as a common RLC entity. This is for convenience of explanation only and may be replaced by any other name.

The adaptation entity transmits the adaptation PDU including the PDCP PDU or the adaptation layer header to the corresponding common RLC entity using at least one of the UE ID and the bearer ID.

The common RLC entity of the base station transmits the corresponding data to the corresponding common RLC entity of the relay node through the air interface between the base station and the relay node.

The common RLC entity of the relay node delivers the adaptation PDU including the RLC SDU or the adaptation layer header to the relay node's adapter entity.

The adaptation entity of the relay node can transmit the PDCP entity of the RCP entity or the relay node to the adaptation entity for data transmission by bearer or per-terminal using the at least one of the terminal identifier and the bearer identifier.

To this end, the base station can configure information for configuring the common RLC entity in the relay node through the RRC connection reconfiguration message.

As an example, the RLC configuration information may include information for indicating association with the adapter entity. If the RLC configuration information includes information indicating association with the adapter entity, the adapter entity may transmit to the RLC entity an adaptation PDU belonging to the UE, the radio bearer of the UE, or the radio bearer of the relay node.

In another example, information for instructing association between the RLC entity and the adapter entity may be included in the DRB configuration information.

As another example, the information for indicating association between the RLC entity and the adapter entity may include information for identifying the corresponding RLC entity of the relay node (for example, a radio bearer identifier (drb-Identity) or a signaling The bearer identifier / type (eg srb-Identity, SRB0, SRB1, SRB2), the logical channel identification information associated with the QoS information (logicalChannelIdentity), and the identifier of one of eps-BearerIdentity) .

As another example, the information for indicating association between the RLC entity and the adapter entity may include information for identifying the corresponding RLC entity of the relay node (for example, a radio bearer identifier (drb-Identity) or a signaling (Eg, SRB-Identity, SRB0, SRB1, SRB2), logical channel identification information (logicalChannelIdentity) associated with QoS information, and eps-BearerIdentity) and a terminal of a terminal to be transmitted through the corresponding RLC entity (E.g., a radio bearer identifier (drb-Identity) or a signaling bearer identifier / type (eg srb-Identity, SRB0, SRB1, SRB2) for identifying a bearer of the UE, Associated logical channel identification information (logicalChannelIdentity), and eps-BearerIdentity). If the information indicates that the connection object is associated with the adapter entity, the adapter entity can transmit to the RLC entity an adaptation PDU belonging to the radio bearer of the corresponding mobile station or the UE or the radio bearer of the corresponding relay node.

As another example, information for identifying a relay node may be required to distinguish data to be received / transmitted from a PDCP entity configured in a relay node associated with a corresponding RLC entity of the relay node. For this purpose, a specific value of the terminal identifier for identifying the terminal may be specified as a value for the relay node, so that the adapter entity can distinguish and process the specific value.

As another example, the radio bearer configuration information including the third PDCP entity or the radio bearer configuration information for the specific radio bearer may be transmitted to the third PDCP entity or the common RLC entity (or the PDCP entity or the RLC entity) Receive / transmit / receive / forward / process. The third PDCP entity or the common RLC entity (or the PDCP entity or the RLC entity) does not go through the authentication layer and the second PDCP entity or the RLC entity does not go through the authentication layer It is possible to transmit / receive / transmit / receive / transfer / process data from the PDCP entity to the RLC entity.

As another example, the information for configuring the common RLC entity may be included in the PDCP configuration information. PDCP PDUs for each UE can be identified on the admission layer and transmitted to the associated common RLC entity. Common RLC entity information can be distinguished using logical channel identifiers. For example, a common RLC entity may be indicated by a specific information element or by specifying a specific value of a logical channel identifier.

As another example, the information for configuring the common RLC entity may be included in the adapter entity configuration information. This may be provided through the association identifier / mobility bearer identifier and association / mapping information for the common RLC entity, as described above. PDCP PDUs for each UE can be identified on the admission layer and transmitted to the associated common RLC entity. Common RLC entity information can be distinguished using logical channel identifiers.

As another example, the information for configuring the common RLC entity may be included in the RLC configuration information. This may be provided through the association identifier / mobility bearer identifier and association / mapping information for the common RLC entity, as described above. PDCP PDUs for each UE can be identified on the admission layer and transmitted to the associated common RLC entity. Common RLC entity information can be distinguished using logical channel identifiers.

As described above, the downlink data transmitted to the mobile station by the base station can be transmitted through the adapter entity of the relay node.

Various embodiments will be described below with respect to a processing method of uplink data.

Uplink data processing method

The terminal or the lower relay node transmits the PDCP PDU to the adaptation entity in the terminal or the relay node or the corresponding RLC entity.

If data of the terminal is transmitted through the adapter entity, the terminal adds an adaptation layer header to the PDCP PDU. The adaptation layer header means a header outside the PDCP PDU or a PDCP PDU as a payload. (Eg, a radio bearer identifier (drb-Identity) or a signaling bearer identifier (eg srb-Identity, SRB0, SRB1, or SRB2) for identifying a bearer of the UE, SRB2, logical channel identification information associated with QoS information (logicalChannelIdentity), and eps-BearerIdentity). For example, the header information may include both the terminal identifier and the bearer identifier. As another example, the header information may include either a terminal identifier or a bearer identifier.

The UE or the lower relay node transmits the adaptation PDU or the RLC SDU to the adapter entity of the terminal or the lower relay node or to the adapter entity or the RLC entity of the relay node that is peered to the RLC entity.

The adaptation object of the relay node receives the adaptation PDU (RLC SDU). If the data of the terminal is transmitted without passing through the adapter entity (for example, if it is transferred from the PDCP entity directly to the RLC entity and transmitted through the interface between the terminal and the relay node), the relay node (or the relay node ) Adds an adaptation layer header to the RLC SDU. The adaptation layer header added to the RLC SDU means a header outside the RLC SDU or a header with the RLC SDU as a payload. (Eg, a radio bearer identifier (drb-Identity) or a signaling bearer identifier (eg, srb-Identity, SRB0, SRB1) for identifying a bearer of a mobile station , SRB2), logical channel identification information (logicalChannelIdentity), eps-BearerIdentity, and QoS information (e.g., 5QI, QoS flow ID). For example, both a terminal identifier and a radio bearer identifier. Other examples may include one or more of a terminal identifier, a radio bearer identifier, and a logical channel identifier. The logical channel identifier can be used as information for identifying QoS. Or a logical channel identifier may be used as information for identifying an RLC entity to be transmitted.

An adaptation entity of a relay node may receive data originating / originated / generated (signaling data or user data) at the relay node. The relay node (or the relay node's adapter entity) adds an adaptation layer header to the PDCP PDU. (Eg, a radio bearer identifier (drb-Identity) or a signaling bearer type (eg, srb-Identity, SRB0, SRB1, or SRB2) for identifying a bearer of the UE, SRB2, logical channel identification information associated with QoS information (logicalChannelIdentity), and eps-BearerIdentity). For example, both a terminal identifier and a radio bearer identifier. Other examples may include one or more of a terminal identifier, a radio bearer identifier, and a logical channel identifier. Or a logical channel identifier may be used as information for identifying an RLC entity to be transmitted.

Hereinafter, an uplink data transmission procedure will be described by dividing a connection embodiment of a PDCP entity and an RLC entity.

Embodiment 1: Embodiment in which one PDCP entity and one RLC entity are connected / linked together

The first PDCP entity, the second PDCP entity, and the third PDCP entity of the base station may have a first RLC entity, a second RLC entity, and a third RLC entity, respectively, connected / linked to the first, second and third RCP entities.

In the base station, the first RLC entity, the second RLC entity, and the third RLC entity are composed of different RLC entities. The base station may configure a first RLC entity, a second RLC entity, a first RLC entity, a second RLC entity, and a third RLC entity of a relay node to be peered to a third RLC entity.

The adaptation entity of the relay node transmits the PDCP PDU or the adaptation PDU including the adaptation layer header to each corresponding RLC entity using one or more of the UE ID and the RBID.

The RLC entity of the relay node transmits the corresponding data to the corresponding RLC entity of the base station through the air interface between the relay node and the base station.

The RLC entity of the base station transmits the adaptation PDU including the RLC SDU or the adaptation layer header to the adaptation entity of the base station.

The adaptation entity of the base station can transmit the PDCP entity of the corresponding base station using at least one of the UE ID and the RBID.

To this end, the BS may configure information for configuring the RLC entity connected / associated with each PDCP entity for each UE in the relay node through the RRC connection reconfiguration message.

For example, the radio bearer including the third PDCP entity may include radio bearer configuration information as shown in FIG.

In another example, the radio bearer configuration information including the third PDCP entity may include information for directing processing of data through an adaptation layer. The PDCP configuration information may include indication information for instructing the PDCP entity of the relay node to associate with the adapter entity. The PDCP entity that has received the RB configuration information that does not include the instruction information can process data from the PDCP entity to the RLC entity without using the adapter layer.

For example, the radio bearer of the relay node associated with the first PDCP entity or the second PDCP entity may include the adaptation configuration information without including the PDCP configuration information (pdcp-Config). The adaptation configuration information may include information for distinguishing the RLC entity associated with the corresponding radio bearer. For example, it may include RLC entity information mapped to each radio bearer for each UE. The RLC entity information may be distinguished using logical channel identifiers. Accordingly, the adaptation entity can transmit the PDCP PDUs of the respective radio bearers to the RLC entity of the UE or the lower node through the associated RLC entity.

Embodiment 2: Embodiment in which a plurality of PDCP entities are connected / linked to one RLC entity

For example, the first PDCP entity, the second PDCP entity, and the third PDCP entity of the base station may have a common RLC entity connected thereto / connected thereto. In another example, the first PDCP entity and the third PDCP entity of the base station may have a common RLC entity connected thereto / connected thereto. In another example, the second PDCP entity and the third PDCP entity of the base station may have a common RLC entity connected thereto / connected thereto. As another example, the first PDCP entity of the base station and the second PDCP entity may be connected / linked to the RLC entity connected / associated with the third PDCP entity. In another example, the first PDCP entity of the base station may be connected / associated with the RLC entity connected / associated with the third PDCP entity. In another example, the second PDCP entity of the base station may be coupled / associated with the RLC entity associated / associated with the third PDCP entity.

One RLC entity is configured in association with the first PDCP entity, the second PDCP entity, and the third PDCP entity in the base station. Or one RLC entity in the base station is configured in association with the first PDCP entity and the third PDCP entity. Or one RLC entity in the base station is configured in association with the second PDCP entity and the third PDCP entity. It is represented as a common RLC entity as in the downlink data description. This is for convenience of explanation only and may be replaced by any other name.

The base station can configure the common RLC entity of the relay node that is peered to the common RLC entity of the base station to the relay node.

The adaptation entity of the relay node transmits the adaptation PDU including the PDCP PDU or the adaptation layer header to the common RLC entity of the corresponding relay node using at least one of the UE ID and the RBID.

The common RLC entity of the relay node transmits the corresponding data to the corresponding common RLC entity of the base station through the air interface between the relay node and the base station.

The common RLC entity of the base station transmits the adaptation PDU including the RLC SDU or the adaptation layer header to the adapter entity of the base station.

The adaptation entity of the base station can transmit the PDCP entity of the corresponding base station using at least one of the UE ID and the RBID.

To this end, the base station can configure information for configuring the common RLC entity in the relay node through the RRC connection reconfiguration message.

As an example, the RLC configuration information may include information for indicating association with the adapter entity. The adaptation entity can transmit an adaptation PDU belonging to the radio bearer of the corresponding terminal or the corresponding terminal or the radio bearer of the corresponding relay node to the corresponding RLC entity.

In another example, information for instructing association between the RLC entity and the adapter entity may be included in the DRB configuration information.

As another example, the information for indicating association between the RLC entity and the adapter entity may include information for identifying the corresponding RLC entity of the relay node (for example, a radio bearer identifier (drb-Identity) or a signaling The bearer identifier / type (eg srb-Identity, SRB0, SRB1, SRB2), the logical channel identification information associated with the QoS information (logicalChannelIdentity), and the identifier of one of eps-BearerIdentity) .

As another example, the information for indicating association between the RLC entity and the adapter entity may include information for identifying the corresponding RLC entity of the relay node (for example, a radio bearer identifier (drb-Identity) or a signaling A logical channel identification information (logicalChannelIdentity), and an eps-BearerIdentity) and a terminal identifier for identifying a terminal of a terminal to be transmitted through the corresponding RLC entity (for example, SRB-Identity, SRB0, SRB1 and SRB2) A bearer identifier (e.g., a radio bearer identifier (drb-Identity) or a signaling bearer identifier / type (eg srb-Identity, SRB0, SRB1, SRB2), logicalChannelIdentity, eps-BearerIdentity &quot;). If the information indicates that the connection object is associated with the adapter entity, the adapter entity can transmit to the RLC entity an adaptation PDU belonging to the radio bearer of the corresponding mobile station or the UE or the radio bearer of the corresponding relay node.

As another example, information for identifying a relay node may be required to distinguish data to be received / transmitted from a PDCP entity configured in a relay node associated with a corresponding RLC entity of the relay node. For this purpose, a specific value of the terminal identifier for identifying the terminal may be specified as a value for the relay node, so that the adapter entity can distinguish and process the specific value.

As another example, the radio bearer configuration information including the third PDCP entity or the radio bearer configuration information for the specific radio bearer may be configured such that the third PDCP entity or the common RLC entity (or PDCP entity or RLC entity) processes data through the admission layer And may include instruction information for instructing. When the radio bearer configuration information that does not include the instruction information is received, or when the instruction information in which the instruction information is set to OFF is received, the third PDCP entity or the common RLC entity (or the PDCP entity or the RLC entity) The PDCP entity can process data from the PDCP entity to the RLC entity as in the conventional case.

As another example, the information for configuring the common RLC entity may be included in the PDCP configuration information. PDCP PDUs for each UE can be identified on the admission layer and transmitted to the associated common RLC entity. Common RLC entity information can be distinguished using logical channel identifiers.

As another example, the information for configuring the common RLC entity may be included in the adapter entity configuration information. This may be provided through the association identifier / mobility bearer identifier and association / mapping information for the common RLC entity, as described above. PDCP PDUs for each UE can be identified on the admission layer and transmitted to the associated common RLC entity. Common RLC entity information can be distinguished using logical channel identifiers. For example, the common RLC entity information may be indicated through a specific information element, or may be distinguished by specifying a specific value of a logical channel identifier.

As another example, the information for configuring the common RLC entity may be included in the RLC configuration information. This may be provided through the association identifier / mobility bearer identifier and association / mapping information for the common RLC entity, as described above. PDCP PDUs for each UE can be identified on the admission layer and transmitted to the associated common RLC entity. Common RLC entity information can be distinguished using logical channel identifiers.

On the other hand, as described above, the adaptation entity can be configured in association with the PDCP entity. However, when there are a plurality of PDCP entities, some PDCP entities may not be associated with the adapter entity. Therefore, it is necessary to distinguish between the PDCP entity associated with the adapter entity and the PDCP entity not associated with the adapter entity.

Hereinafter, a method for distinguishing PDCP entities based on the association with the adapter entity will be described.

How to distinguish between PDCP objects that are not associated with adapter objects and PDCP objects that are associated with adapter objects

A plurality of radio bearers can be configured between the relay node and the base station.

For example, a particular radio bearer may be a generic radio bearer configured between a relay node and a base station regardless of the terminal (or regardless of relay operation). The relay node can transmit data (signaling data or user data) originated / generated / generated in the terminal to the base station through a specific radio bearer while operating as a general terminal regardless of the relay operation. For convenience of explanation, this is referred to as a general radio bearer. That is, the relay node may operate as a node in a relay structure and also operate as a general mobile communication terminal.

In another example, another specific radio bearer may be a radio bearer configured to relay and transmit data of the terminal.

In another example, another specific radio bearer may be a radio bearer configured to multiplex and transmit data of a terminal and data originating / originated / generated at a relay node. I.e., a radio bearer configured to multiplex and transmit the origination data of the relay node itself and the origination data of the relaying terminal.

The PDCP entity and / or the RLC entity of a general radio bearer configured at the relay node can operate like the conventional LTE technology without interaction with the adapter entity. For example, the PDCP entity processes the PDCP SDU received from the upper layer and then transmits the corresponding PDCP PDU to the RLC entity, and the RLC entity receives the PDCP PDU. Alternatively, the RLC entity processes the RLC PDU received from the lower layer, and transmits the RLC SDU to the PDCP entity, and the PDCP entity receives the RLC PDU.

The general radio bearer does not need to perform the interaction with the adapter entity described in the above embodiments.

Therefore, information may be required to indicate to the relay node whether the PDCP entity or RLC entity corresponding to the radio bearer transmits or receives data to the adapter entity. To this end, the radio bearer configuration information included in the RRC reconfiguration message or the RRC reconfiguration message may include information for instructing the PDCP entity or the RLC entity to process the data through the adapter entity.

For example, the base station may instruct the general radio bearer not to include information for indicating whether the PDCP entity or the RLC entity should transmit or receive data to the adapter entity. Alternatively, the base station can instruct the general radio bearer by setting off the information for instructing the PDCP entity or the RLC entity to transmit or receive data to the adapter entity. In this case, the PDCP entity or the RLC entity can process data from the PDCP entity to the RLC entity (without going through the adapter layer).

In another example, the base station may indicate to the specific radio bearer, including information for instructing the PDCP entity or the RLC entity to forward or receive data to the adapter entity. Alternatively, the base station can instruct the PDCP entity or the RLC entity to turn on or instruct the specific radio bearer to transmit or receive data to the adapter entity. In this case, the PDCP entity or the RLC entity can process the data to the adaptation layer. For example, the PDCP entity processes the PDCP SDU received from the upper layer, and then transmits the corresponding PDCP PDU to the adapter entity. The adapter entity processes the function of the adapter layer in the received PDCP PDU (for example, And transmits the data (for example, the data to which the header is added to the adaptation PDU or the PDCP PDU) to the corresponding RLC entity, and the RLC entity receives the data.

The RLC entity processes the RLC PDU received from the lower layer and forwards the RLC SDU to the adapter entity. The adaptation object handles the function of the adaptation layer to the received RLC SDU (for example, the header removal function), and then transmits the corresponding data (for example, the data or PDCP PDU whose header is removed from the adaptation SDU or RLC SDU) To the PDCP entity and the PDCP entity receives it.

In the above description, a configuration example of an adaptation entity that can be configured as a relay node, a base station, and the like for the relay operation, a transmission example of downlink data, a transmission example of uplink data, a connection relationship between a PDCP entity and an adaptation object And an embodiment in which data is divided and processed. A plurality of embodiments included in each description may be applied to each other in combination, or may be applied individually.

Through this operation, it is possible to efficiently distinguish and process the traffic between the remote node (terminal) and the relay node or the relay node and the base station through the admission layer in the relay environment.

Hereinafter, a configuration of a relay node and a base station to which each of the above embodiments can be applied will be described again with reference to the drawings.

18 is a diagram illustrating a configuration of a relay node according to an embodiment.

Referring to FIG. 18, a relay node 1800 for processing remote node data includes a receiver 1830 that receives configuration information for configuring an adapter entity from a base station, and a receiver 1830 that links the PDCP entity and the RLC entity based on the configuration information, And a control unit 1810 for separating and processing the data to be transferred from the adapter entity to the RLC entity and the data to be transmitted to the PDCP entity.

For example, the receiver 1830 can receive configuration information for configuring the adapter entity from the base station through higher layer signaling.

Meanwhile, the control unit 1810 may control the adapter entity to generate header information including at least one of a relay node identifier, a remote node identifier, a DRB identifier, an SRB identifier, and a logical channel identifier. In addition, the controller 1810 may control the PDCP layer to add the generated header information to the PDCP PDU transferred to the adapter entity in the PDCP layer, and to forward the PDCP PDU to the RLC entity.

In addition, the control unit 1810 may configure the adapter entity based on the instruction information indicating the linkage of the PDCP entity received from the base station and the adapter entity. The adaptation entity can be composed of only one relay node as a single entity. Alternatively, the adapter entity may be composed of a plurality of PDCP entity or RLC entity.

In addition, the control unit 1810 may control the adapter entity to perform a linking process by separating the RLC entity bearer or RB bearer signal into the RLC bearer. For example, the control unit 1810 may control the adapter entity to process and process the data through the mapping information between the remote node identifier and the radio bearer identifier and the logical channel identifier of the relay node. For example, the adapter entity checks header information of the adapter entity or the above-described identifier information with respect to data received from a lower layer and transmits the corresponding data to an upper layer (ex. PDCP layer) Or to the RLC entity mapped to the identifier information and determine whether to transmit the RLC entity to the base station.

In addition, the control unit 1810 controls the overall operation of the relay node 1800 necessary for controlling the data relay operation of the remote node and the base station by utilizing the adapter entity in the relay operation necessary for performing the above- do.

The transmitting unit 1820 and the receiving unit 1830 are used to transmit and receive signals, messages, and data necessary for performing the above-described embodiments to and from a remote node (ex, terminal), another relay node, and a base station.

19 is a diagram illustrating a configuration of a base station according to an embodiment.

19, a base station 1900 for processing remote node data includes a control unit 1910 that configures an adapter object by linking a PDCP entity and an RLC entity, and the controller 1910 controls the relay node And header information for identifying the data of the remote node and adds the header information to the PDCP PDU, and the data to be transmitted to the relay node and the remote node can be divided into the RLC entity associated with the adapter entity and transmitted.

For example, the header information may include at least one of a relay node identifier, a remote node identifier, a DRB identifier, an SRB identifier, and a logical channel identifier.

In addition, the base station 1800 transmits configuration information for configuring the adapter entity to the relay node to the relay node, and instructs the relay node to instruct the association of the PDCP entity of the relay node and the adapter entity of the relay node And a transmitting unit 1920 for transmitting the data.

Also, the adaptation entity may be configured in association with the PDCP entity and the RLC entity as described above, and may be configured between the PDCP layer and the RLC layer. The adaptation entity may be composed of a single entity or a plurality of entities by PDCP or RLC.

In addition, the control unit 1910 controls the overall operation of the base station 1900 for transmitting and receiving data through the relay node and the relay node, which are necessary for performing the above-described embodiments.

The transmission unit 1920 and the reception unit 1930 are used to transmit and receive signals, messages, and data necessary for performing the above-described embodiments to the relay node and the remote terminal.

The embodiments described above can be supported by the standard documents disclosed in at least one of the wireless access systems IEEE 802, 3GPP and 3GPP2. That is, the steps, configurations, and parts not described in the present embodiments for clarifying the technical idea can be supported by the above-mentioned standard documents. In addition, all terms disclosed herein may be described by the standard documents set forth above.

Also, the terms "system", "processor", "controller", "component", "module", "interface", "model", "unit", and the like described above generally refer to computer-related entity hardware, Combination, software, or software in execution. For example, the above-described components may be, but are not limited to, a process driven by a processor, a processor, a controller, a control processor, an entity, an execution thread, a program and / or a computer. For example, a component can be a controller or an application running on a processor and a controller or processor. One or more components can reside within a process and / or thread of execution, and a component can reside on one system or be deployed on more than one system.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not to be construed as limiting the scope of the present invention. Various modifications and variations will be possible. Accordingly, the embodiments disclosed herein are intended to be illustrative rather than limiting, and the scope of the present invention is not limited by these embodiments. The scope of protection of the present invention is to be construed according to the claims, and all technical ideas within the scope of the claims should be construed as being included in the scope of the present invention.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is based on Korean Patent Application No. 10-2017-0122529 filed on Sep. 22, 2017, and Korean Patent Application No. 10-2018-0111250 filed on September 18, 2018, (a) (35 USC § 119 (a)), the entire contents of which are incorporated herein by reference. In addition, the present patent application is also incorporated in the present patent application as a reference, if the priority is given to the countries other than the US for the same reason as above.

Claims (17)

1. A method for a relay node to process remote node data,

   Receiving configuration information for configuring an adaptation entity from a base station;

   Configuring an adapter entity by linking the PDCP entity and the RLC entity based on the configuration information; And

   And separating and processing data to be transferred from the adapter entity to the RLC entity and data to be transmitted to the PDCP entity.
2. The method according to claim 1,

   Wherein the adapter entity comprises:

   Wherein the header information includes at least one of a relay node identifier, a remote node identifier, a DRB identifier, an SRB identifier, and a logical channel identifier.
3. The method according to claim 1,

   Wherein the adapter entity comprises:

   And separating the RLC bearer according to a remote node or a radio bearer signal into an RLC bearer of the RLC entity.
4. The method according to claim 1,

   Wherein the adapter entity comprises:

   And separating and processing the data through the mapping information between the remote node identifier and the radio bearer identifier and the logical channel identifier of the relay node.
5. The method according to claim 1,

   Wherein configuring the adapter entity comprises:

   Wherein the adapter entity is configured based on PDCP configuration information including indication information indicating association of the PDCP entity and the adaptation entity received from the base station.
6. The method according to claim 1,

   Wherein the adapter entity comprises:

   RTI ID = 0.0 &gt; 1, &lt; / RTI &gt;
7. A method for a base station to process remote node data,

   Constructing an adapter entity by linking the PDCP entity and the RLC entity;

   Generating header information for identifying data of a relay node and a remote node in the adapter entity and adding the header information to the PDCP PDU; And

   And separating data to be transmitted to the relay node and the remote node into RLC entities associated with the adapter entity and delivering the separated RLC entities.
8. 8. The method of claim 7,

   The header information includes:

   A relay node identifier, a remote node identifier, a DRB identifier, an SRB identifier, and a logical channel identifier.
9. 8. The method of claim 7,

   Transmitting configuration information for configuring an adapter entity to the relay node to the relay node; And

   Further comprising the step of transmitting, to the relay node, instruction information indicating a connection between a PDCP entity of the relay node and an adapter entity of the relay node.
10. 10. The method of claim 9,

    The relay node comprises:

    Wherein data to be transferred from the adapter entity of the relay node to the RLC entity of the relay node and data to be transmitted to the PDCP entity are distinguished and processed.
11. 8. The method of claim 7,

    Wherein the adapter entity comprises:

    RTI ID = 0.0 &gt; 1, &lt; / RTI &gt;
12. A relay node for processing remote node data,

    A receiving unit for receiving configuration information for configuring an adaptation entity from a base station; And

    Constructing an adapter entity by linking the PDCP entity and the RLC entity based on the configuration information,

    And a controller for separating and processing data to be transferred from the adapter entity to the RLC entity and data to be transmitted to the PDCP entity.
13. 13. The method of claim 12,

    Wherein the adapter entity comprises:

    Wherein the relay node generates header information including at least one of a relay node identifier, a remote node identifier, a DRB identifier, an SRB identifier, and a logical channel identifier.
14. 13. The method of claim 12,

    Wherein the adapter entity comprises:

    And separates the RLC entity bearer signal or the RNC bearer signal into a RLC bearer for the RLC entity.
15. 13. The method of claim 12,

    Wherein the adapter entity comprises:

    And separates and processes the data through the mapping information between the remote node identifier, the radio bearer identifier, and the logical channel identifier of the relay node.
16. 13. The method of claim 12,

    Wherein,

    Wherein the adaptation module configures the adaptation entity based on PDCP configuration information including indication information indicating association between the PDCP entity and the adaptation entity received from the base station.
17. 13. The method of claim 12,

    Wherein the adapter entity comprises:

    Wherein the relay node comprises a single entity.

Images