WO2010088804A1

WO2010088804A1 - Relay transmission method, relay node and base station

Info

Publication number: WO2010088804A1
Application number: PCT/CN2009/071345
Authority: WO
Inventors: 蔺波; 王燕; 刘宇红
Original assignee: 华为技术有限公司
Priority date: 2009-02-03
Filing date: 2009-04-17
Publication date: 2010-08-12

Abstract

A relay transmission method, a relay node and a base station are provided, relating to the communication art. The method can depress wireless return trip transmission overhead between a relay node and a base station. The relay transmission method includes steps as following: a SI interface bearing of a user equipment is established between a relay node and a core network; for the user face, pear to pear entities are established between the relay node and the core network, which is used for compressing the IP head of the user equipment; pear to pear entities are established between the relay node and a base station, which is used for compressing the SI interface bearing. Another relay transmission method includes steps as following: a wireless bearing is established between a relay node and a base station; pear to pear entities are established between the relay node and the base station, which is used for bearing X2 interface data or signaling.

Description

Method for relay transmission, relay node and base station The present application claims the application number PCT/CN2009/070352 submitted on February 3, 2009, and the invention name is "a relay transmission method and relay node" Priority of the PCT application, and the priority of the PCT application filed on March 16, 2009, with the application number PCT/CN2009/070817 and the invention titled "a relay transmission method, relay node and base station" The entire contents of which are incorporated herein by reference.

Technical field

The present invention relates to the field of communications technologies, and in particular, to a method, a relay node, and a base station for relay transmission. Background technique

As a new technology, Relay can increase cell edge throughput and extend cell coverage. The LTE (Long Term Evolution) system is used as an example. The user equipment (UE) to the relay node (RN) is the LTE air interface technology transmission, and the RN to the base station (eNodeB, eNB) is also the LTE air interface technology transmission. . The RN is used for forwarding data between the UE and the eNB.

The peer-to-peer protocol layers between the UE and the eNB are: a physical layer (LI), a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, and a PDCP (Packet Data Convergence Protocol). , packet data convergence protocol) layer. After the introduction of the Relay, the forwarded data may be forwarded by the above layers. For PDCP layer forwarding, it is called IP layer forwarding or Layer 3 Relay/L3 Relay, which is called after the PDCP layer processing of the RN is completed (becomes an IP packet). The IP-layer forwarding between the RN and the eNB may bring about a large overhead of the IP header. This is a serious challenge for transmitting information on the wireless channel between the RN and the eNB.

As shown in FIG. 1, the prior art discloses an S1 interface user plane protocol stack architecture, assuming There is no Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) bearer on the IP layer of the UE. The data packet overhead is analyzed. When the UE sends an air interface, it is in the PDCP layer. The packet header is PDCP+APP; after the RN air interface is received, the packet header of the data packet is IP+APP after being processed by the left protocol stack; the RN passes through the right protocol stack, and the packet header of the data packet before PDCP processing is IP+UDP+GTP-U+ IP+APP; The RN passes through the right protocol stack. The header of the data packet after PDCP processing is PDCP+GTP-U + IP+APP. It can be seen that, compared with the air interface overhead data packet of the original UE, at least the overhead is increased: 1 GTP-U header + 1 IP header. If the IP of the UE carries UDP, the overhead of 1 UDP header is further increased. . That is to increase the overhead of 16 ~ 24 bytes (Byte).

After analysis, it is found that the protocol stack structure disclosed in the prior art causes a large wireless backhaul transmission between the RN and the eNB. Summary of the invention

The first method for relay transmission provided by the embodiment of the present invention includes:

An S1 interface bearer of the user equipment is established between the relay node and the core network. For the user plane carried by the S1 interface, a peer entity is established between the relay node and the core network, and is used by the user equipment.

IP header compression; a peer entity is established between the relay node and the base station, and is used for compression carried by the S1 interface.

A second method for relay transmission provided by the embodiment of the present invention includes:

An S1 interface bearer of the user equipment is established between the relay node and the core network; a peer entity is established between the relay node and the base station, and is used for compression of the S1 interface bearer, and for the user plane carried by the S1 interface, IP header compression for the user equipment.

A third method for relay transmission provided by the embodiment of the present invention includes:

Establishing an S1 interface bearer of the user equipment between the base station and the core network; establishing a radio bearer of the user equipment between the base station and the relay node, and establishing, by the base station, the association between the radio bearer and the S1 interface bearer For the S1 interface to carry the user plane, a peer entity is established between the base station and the relay node, and is used for IP header compression of the user equipment. A fourth relay transmission method provided by the embodiment of the present invention includes:

A radio bearer is established between the relay node and the base station; a peer entity is established between the relay node and the base station, and is used to carry X2 interface data or signaling.

And the relay node provided by the embodiment of the present invention includes: an S1 interface bearer unit, configured to establish an S1 interface bearer of the user equipment with the core network; and a user plane compression unit, configured to be used for the user plane carried by the S1 interface And establishing, by the peer network, a peer entity to compress an IP header of the user equipment; and the S1 interface compression unit is configured to establish, by the peer entity, a peer entity to compress the S1 interface bearer established by the bearer establishing unit.

A relay node according to an embodiment of the present invention includes: an S1 interface bearer unit, configured to establish an S1 interface bearer of a user equipment with a core network; and a compression unit, configured to establish a peer entity compression with the base station The S1 interface bearer established by the S1 interface bearer unit and the user plane carried by the S1 interface are also used to compress the IP header of the user equipment.

A base station provided by the embodiment of the present invention includes: a radio bearer unit, configured to establish a radio bearer of a user equipment with a relay node; and an S1 interface bearer unit, configured to establish an S1 interface bearer of the user equipment with the core network. An association unit, configured to establish an association between the radio bearer and the S1 interface bearer established by the S1 interface bearer unit, and a user plane compression unit, configured to establish a peer relationship with the relay node for the user plane carried by the S1 interface The entity compresses the IP header of the user device.

An embodiment of the present invention provides another relay node or a base station, including: a radio bearer unit, configured to establish a radio bearer between the relay node and the base station; and an X2 interface bearer unit, where the relay node and the A peer entity is established between the base stations to carry X2 interface data or signaling.

According to the description of the foregoing technical solution, since the peer entity establishes a peer entity for compression of the S1 interface bearer, the wireless backhaul transmission overhead between the relay node and the base station is reduced, and for the user plane, Establishing a peer entity between the node and the core network for IP header compression of the user equipment may further reduce wireless backhaul transmission overhead between the relay node and the core network.

According to the description of the foregoing technical solution, the user equipment is established between the base station and the core network.

The S1 interface carries, and the radio bearer of the user equipment is established between the relay node and the base station, and the base station is configured by the base station Establishing association between the radio bearer and the S1 interface bearer, so that the core network can communicate with the relay node through the base station, thereby reducing the wireless backhaul transmission overhead between the relay node and the base station, and for the user plane, the relay node and the core Establishing IP header compression between the networks for the user equipment for the user equipment can further reduce the wireless backhaul transmission overhead between the relay node and the core network.

According to the description of the foregoing technical solution, since a radio bearer is established between the relay node and the base station, a peer entity is established between the relay node and the base station to carry X2 interface data or signaling, thereby reducing the relay node and the base station. Wireless backhaul overhead between.

The five relay transmission methods provided by the embodiments of the present invention include: a first peer entity is established between the relay node and the base station, and is used for compression of the S1 or X2 interface bearer; a second peer entity, the second peer entity being disposed above, below or below the first peer entity, for multiplexing indication of an upper layer protocol, or multiplexing indication of a user equipment, or service bearer Reuse indication, or an indication of priority or quality of service attributes.

According to the description of the foregoing technical solution, because the second peer entity can be used for the multiplexing indication of the upper layer protocol, or the multiplexing indication of the user equipment, or the multiplexing indication of the service bearer, or the indication of the priority or the quality of service attribute, The switchover delay of the upper-layer protocol is shortened, and the existing S1 or X2 interface bearer is omitted. This saves air interface overhead and ensures better service quality. DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description For some embodiments of the present invention, other drawings may be obtained from those skilled in the art without departing from the drawings.

FIG. 1 is a schematic diagram of an S1 interface user plane protocol stack provided by the prior art;

2 is a schematic flowchart of a first relay transmission method according to an embodiment of the present invention; FIG. 3 is a schematic structural diagram of a user plane protocol stack of an S1 interface according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of an S1 interface control plane protocol stack according to an embodiment of the present disclosure;

FIG. 5 is a schematic structural diagram of another S1 interface user plane protocol stack according to an embodiment of the present disclosure; FIG. 6 is a schematic flowchart of a second relay transmission method according to an embodiment of the present invention; FIG. 7 is a schematic structural diagram of another S1 interface user plane protocol stack according to an embodiment of the present invention; FIG. 9 is a schematic structural diagram of a user plane protocol stack of an S1 interface according to an embodiment of the present invention;

10 is a schematic structural diagram of an S1 interface control plane protocol stack according to an embodiment of the present invention; FIG. 11 is a schematic flowchart of a fourth relay transmission method according to an embodiment of the present invention; FIG. 13 is a schematic diagram of another X2 interface user plane protocol stack architecture according to an embodiment of the present invention; FIG. 14 is a schematic diagram of an X2 interface control plane protocol stack architecture according to an embodiment of the present invention; FIG. 15 is a schematic structural diagram of another X2 interface control plane protocol stack according to an embodiment of the present invention; FIG. 16 is a schematic diagram of multiple UEs and multiple service multiplexing scheduling structures according to an embodiment of the present invention; Another multiple UE, multiple service multiplexing scheduling structure diagrams provided by the embodiments of the present invention; FIG. 18 is a structural diagram of a relay node according to an embodiment of the present invention;

FIG. 19 is a structural diagram of another relay node according to an embodiment of the present invention;

FIG. 20 is a structural diagram of a base station according to an embodiment of the present invention;

FIG. 21 is a structural diagram of another relay node or a base station according to an embodiment of the present disclosure;

FIG. 22 is a schematic flowchart diagram of a fifth relay transmission method according to an embodiment of the present invention. detailed description

The technical solutions provided by the present invention are further described in detail below with reference to the accompanying drawings and embodiments. It is apparent that the described embodiments are only a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

FIG. 2 is a schematic flowchart diagram of a first relay transmission method according to an embodiment of the present invention. The method includes the following steps: Step 21: The S1 interface bearer of the user equipment is established between the relay node and the core network. Step 22: The user plane carried by the S1 interface is established between the relay node and the core network. a peering entity, for IP header compression of the UE;

Step 23: A peer entity is established between the relay node and the base station, and is used for compression carried by the S1 interface. In the relay transmission method provided by the embodiment of the present invention, since the relay node and the peer entity PDCP of the core network are used for IP header compression of the UE, the wireless backhaul transmission overhead between the RN and the eNB is reduced, and the PDCP is terminated. In the core network, the IP header of the UE is restored on the core network, so the user plane transmission overhead of the S1 interface of the eNB and the core network is also reduced. And because the peer entity of the RN and the eNB is used for compression of the S1 interface bearer, the UDP/IP or IP carried by the user plane can be compressed and decompressed, thereby further reducing the wireless backhaul transmission overhead between the RN and the eNB.

FIG. 3 is a schematic diagram of an S1 interface user plane protocol stack architecture of the UE to the GW, and FIG. 4 is a schematic diagram of an S1 interface control plane protocol stack architecture of the UE to the MME. In the protocol stack architecture diagram, the English abbreviations involved include: RRC (Radio Resource Control), UDP (User Datagram Protocol), IP (Internet Protocol), SCTP (Stream Control) Transmission Protocol, GTP (GPRS Tunneling Protocol), GPRS (General Packet Radio Service), S1AP (SI Interface Application Protocol), X2AP (X2 Interface Application Protocol), MME (Mobility Management Entity, Mobility Management Entity), GW (Gateway).

The PDCP peer entity between the relay and the base station may further configure a new header compression profile, which is responsible for partial compression and recovery of GTP-U or SCTP to reduce the overhead of GTP-U or SCTP. For example, for the control plane, the PDCP peer entity at the transmitting end detects that the profile ID is equal to a specific value, and then compresses the source port and the target port of the upper layer SCTP; the PDCP peer entity at the receiving end detects that the profile ID is equal to the specific The value of the source port and the target port of the upper layer SCTP are restored. For example, for the user plane, if the PDCP peer entity of the sending end detects that the profile ID is equal to a specific value, the TEID port field of the upper layer GTP-U is compressed; the PDCP peer entity of the receiving end detects the p _ro fil _e If the ID is equal to the specific value, the TEID port field of the upper layer GTP-U is restored.

The PDCP peer entity between the relay and the base station can further increase the S 1 AP signaling integrity. The protection and/or encryption functions are responsible for the security and integrity protection of S1AP signaling. For example, for RN uplink signaling, the RN uses the encryption and/or integrity protection key, and the PDCP peer entity at the transmitting end performs integrity protection and/or encryption processing on the S1AP signaling; the PDCP peer entity at the receiving end uses the encryption and encryption. / or integrity protection key, decryption and / or integrity check processing of S1AP signaling.

The foregoing functions added to the PDCP peer entity are applicable to all embodiments of the present invention, including adding signaling integrity protection function and/or encryption function of the upper layer signaling (S1AP or X2AP) of the PDCP peer entity of the control plane. ; The header compression and/or encryption function of the upper layer data of the cross layer is added to the PDCP peer entity of the user plane.

Taking the user plane protocol stack architecture of the S1 interface of the UE to the GW in FIG. 3 as an example, it is assumed that the TCP/UDP bearer on the IP layer of the UE is not considered, and the data packet overhead is analyzed: when the UE transmits through the air interface, in the PDCP The packet header of the layer data packet is PDCP+APP; the RN receives the packet through the air interface, and the packet header of the data packet processed by the upper layer PDCP of the left protocol stack is IP+APP; the RN passes the right protocol stack, and the data packet before the lower layer PDCP processing The header of the packet is IP+UDP+GTP-U+IP+APP; the header of the packet processed by the lower layer PDCP is PDCP+GTP-U+PDCP+APP. It can be seen that compared with the original UE air interface overhead data packet, only the overhead is increased: 1 PDCP header + 1 GTP-U header. That is, the overhead of 8 Byte + (7~12) bits is obviously superior to the prior art scheme. Moreover, compared with the prior art on the S1 interface, since the PDCP is terminated on the GW, the IP header of the UE does not need to be transmitted on the S1 interface, which reduces the wireless backhaul transmission overhead of the S1 interface, and thus can bring more gain. The comparison is as follows: The header of the data packet on the prior art S 1 interface: IP + UDP + GTP-U + IP + APP; the header of the data packet on the S 1 interface of this embodiment: IP + UDP + GTP-U + APP . It can be seen that the embodiment reduces the overhead at least: 1 IP header, that is, the overhead of adding a PDCP peer entity between the RN and the GW (7 to 12 bits), which can reduce the overhead of 8 to 16 bytes on the S1 interface. The radio link between the RN and the eNB also reduces at least (7 to 12 bit) to (8 to 16 Bytes) overhead.

If the TCP/UDP bearer is used on the IP layer of the UE, the prior art may introduce an 8 Byte overhead, and the embodiment of the present invention may further compress the UDP header, thereby reducing the overhead of 8 bytes. If the PDCP peer entity between the RN and the eNB is considered to be partially compressed by the SCTP and the GTP-U, the overhead can be further reduced.

It should be noted that the S1 interface user plane protocol stack architecture provided by the embodiment of the present invention differs from the prior art mainly in that a PDCP peer entity is introduced on the RN and the GW, and a PDCP peer entity is between the RN and the eNB. A partial compression mechanism can be applied to SCTP and GTP-U.

In one embodiment, a mapping layer (MapLayer) peer entity is set up between the RN and the eNB, and the MapLayer peer entity is used for compression carried by the S1 interface.

The compression used by the MapLayer peer entity for the S1 interface bearer includes: compression of the user plane bearer protocol and compression of the control plane bearer protocol. Moreover, for user plane bearers, the MapLayer peer entity can be further used for partial compression of GTP-U. For control plane bearers, the MapLayer peer entity can be further used for partial compression of SCTP.

For example, for the SCTP header, you can only compress the Source Port Number, the Destination Port Number, and the Verification Tag. See Table 1:

Table 1

For the header of GTP-U, you can only compress the Tunnel Endpoint Identifier (TEID) field.

( 4Bits ), see table 2 below:

Table 2

FIG. 5 is a schematic diagram of an SI interface user plane protocol stack architecture of the UE to the GW, FIG. 5 The MapLayer peer entity between the RN and the eNB has a mapping function of the S1 bearer. The MapLayer peer entity can further compress the TEID in the GTP-U (ie, GTP partial compression), or can perform SCTP partial compression. Compared with the S1 interface user plane protocol stack architecture in FIG. 3, the PDCP peer entity on the GW moves down to the eNB.

It should be noted that, in the protocol stack architecture shown in FIG. 5, the GTP-U/UDP/IP protocol layer on the left side of the eNB does not exist in the protocol stack. The reason why the suffix is described in Figure 5 is that the eNB receives the data from the RN and then performs the mapping after the PDCP peer entity on the left side of the eNB (the uplink direction is similar to the downlink direction). The uppermost layer PDCP on the left side of the eNB and the upper layer PDCP of the RN are peer entities. This architecture can be considered as a variant of the protocol architecture of Figure 3. The MapLayer peer entity in this architecture can be considered as a functional extension of the PDCP peer entity between the RN and the eNB in Figure 3.

Referring to FIG. 6, a second relay transmission method provided by an embodiment of the present invention is shown. Includes:

Step 61: The S1 interface bearer of the user equipment is established between the relay node and the core network.

Step 62: Establish a compression between the relay node and the base station for the bearer of the S1 interface, and IP header compression of the user equipment for the user plane.

In the relay transmission method provided by the embodiment of the present invention, the peer entity establishes a peer entity for the compression of the S1 interface bearer, and for the user plane, the peer entity is also used for the IP header of the user equipment. Compression, thus reducing the wireless backhaul transmission overhead between the RN and the eNB, and compressing and decompressing the UDP/IP or IP carried by the user plane, thereby further reducing the wireless backhaul transmission overhead between the RN and the eNB.

In one embodiment, the MapLayer functional entity and the PDCP functional entity in Figure 5 can be grouped together to form a new e-PDCP (Enhanced PDCP) peer entity. The new e-PDCP peer entity can be located in the original PDCP or the original MapLayer location, as shown in Figure 7 for the S1 interface user plane protocol stack architecture diagram.

In an embodiment, the e-PDCP peer entity established between the RN and the eNB may be further used for carrying part of the compression of the GTP-U by the user plane, or for controlling the partial compression of the SCTP by the control plane.

E-PDCP pair by configuring a new Profile ID for the e-PDCP peer entity The entity implements IP header compression of the UE, UDP/IP compression of the SI interface, and partial GTP-U compression. The existing profile is shown in Table 3 below.

table 3

There are two types of configuration methods of the present invention. One is to add a new Profile ID to indicate the new protocol stack usage, as shown in Table 4.

Table 4

The other is to configure multiple sequential Profile IDs to represent a protocol stack combination. For example, based on the two new profiles added above, configure the composite profile as follows:

Profile ID 1 = 0x0105, Profile ID 2 = 0x0106, Profile ID 3 = 0x0102, which means the compression protocol stack IP/GTP-U/UDP/IP.

Referring to FIG. 8, a third relay transmission method provided by an embodiment of the present invention is shown. Includes:

Step 81: The S1 interface bearer of the user equipment is established between the base station and the core network.

Step 82: The radio bearer of the user equipment is established between the base station and the relay node, and the association between the radio bearer and the S1 interface bearer is established by the base station.

Step 83: A peer entity is established between the base station and the relay node for the user plane carried by the S1 interface, and is used for IP header compression of the user equipment. In the relay transmission method provided by the embodiment of the present invention, the radio bearer of the UE is established between the RN and the eNB, so that the air interface between the RN and the eNB does not need to transmit the IP header of the UE, thereby reducing the wireless backhaul transmission overhead. The eNB establishes an S1 interface user plane connection with the core network, and the eNB establishes a mapping between the eNB and the RN to the S1 user plane bearer, so that the core network can communicate with the RN through the eNB. The S1 user plane bearer between the UE under the RN and the core network is maintained by the eNB; and, for the user plane, the peer header established between the eNB and the RN is used for IP header compression of the UE. The wireless backhaul transmission overhead between the RN and the eNB is also further reduced.

FIG. 9 is a schematic diagram of an S1 interface user plane protocol stack architecture of the UE to the GW, and FIG. 10 is a schematic diagram of an S1 interface control plane protocol stack architecture of the UE to the MME. Taking the user plane protocol stack architecture of the UE to GW S1 interface in FIG. 9 as an example, it is assumed that TCP/UDP is not considered on the IP layer of the UE, and the packet header overhead is analyzed: when the UE air interface is sent, the PDCP layer is The packet header is PDCP+APP; after the RN air interface is received, the packet header is IP+APP after being processed by the left protocol stack; the RN passes the right protocol stack, and the PDCP processes the packet header IP+APP; the RN passes the right protocol. Stack, PDCP processed packet header is PDCP+APP. It can be seen that compared with the original UE air interface overhead data packet, the wireless backhaul transmission overhead is not increased, which is superior to the prior art solution.

Referring to FIG. 11, a fourth relay transmission method provided by an embodiment of the present invention includes: Step 111: Establish a radio bearer between a relay node RN and a base station eNB;

Step 112: A peer entity is established between the RN and the eNB, and is used to carry data or signaling of the X2 interface.

In one embodiment, for a user plane, the peer entity is also used for compression carried by the X2 interface. In an embodiment, the peer entity established between the RN and the eNB is further used for partial compression of the user plane carrying the GTP-U, or for controlling the partial compression of the SCTP by the control plane.

Referring to FIG. 12 to FIG. 15 , FIG. 12 and FIG. 13 are schematic diagrams of two X2 interface user plane protocol stacks according to an embodiment of the present invention, and FIG. 14 and FIG. 15 are two embodiments of the present invention. X2 interface control plane protocol stack architecture diagram. The X2 interface user plane protocol stack architecture provided in FIG. 12 and FIG. 13 is described. In FIG. 12, the air interface between the RN and the eNB directly carries the upper layer. The user plane data of X2 does not increase the wireless backhaul transmission overhead, which is superior to the prior art scheme. In FIG. 13, the air interface between the RN and the eNB serves as a bearer protocol layer of the X2 interface, and is used by the PDCP peer entity. Header compression of the upper layer UDP/IP reduces the overhead of wireless backhaul transmission over the wireless link and is also superior to prior art solutions.

The multiplex layer (MuxLayer) peer entity is described below.

In each of the above protocol stacks, there is a PDCP peer entity between the RN and the eNB. That is, according to the interface division, the PDCP peer entity carries the S1 interface or the X2 interface protocol, and is divided according to the control plane CP and the user plane UP. The PDCP peer entity carries the CP or UP protocol.

According to the prior art, the eNB schedules each UE according to the measurement and data volume of each UE, and allocates uplink and downlink resources for each UE. The scheduling of the UE under the RN is performed by the RN itself, and the eNB may not participate. Since the radio link resources between the RN and the eNB are limited, and the scheduling of the radio link resources does not depend on a single specific UE, that is, the radio link resources allocated by the eNB are given to the RN. The radio link resource has the same channel environment for the UE under the RN, so it is necessary to multiplex the radio link resources and reduce the scheduling signaling to the UE. Specifically, data of multiple interfaces may be transmitted by using one radio bearer; data of multiple UEs may be transmitted by using one radio bearer; multiple service flows of one UE may also be transmitted on one bearer. For example, if a UE has an S1AP bearer on the radio link, if X2 handover is initiated on the RN, the X2 signaling can also be transmitted on the radio link resource carrying the S1 signaling, instead of re-establishing the X2. The radio link of the interface is carried, thereby shortening the handover delay.

The specific multiplexing mode may be: setting a multiplex layer peer entity between the RN and the eNB, where the multiplex layer peer entity is used for the indication of the upper layer interface or protocol or the UE identifier or the service flow/service bearer indication of the UE or An indication of priority or QoS attributes.

The indication of the upper layer interface or the protocol may include: a user plane protocol indication of the S1 interface, a user plane protocol indication of the X2 interface, a control plane protocol indication of the S1 interface, or a control plane protocol indication of the X2 interface. Or use the interface + plane mode, such as the upper interface: S1 interface or X2 interface, the upper plane is: control plane or user plane. The UE identifier may be specifically a C-RNTI (Cell Radio Network Temporary Identity), IMSI, P-TMSI, M-TMSI (M-Temporary Mobile Subscriber Identity).

The service flow/traffic bearer indication of the UE is used to identify an upper layer service or a data stream of the UE (which may also include signaling), and may be an LCH ID (logical channel identifier) and an RB ID (radio bearer id). E-RAB ID (E-UTRAN Radio Access Bearer), TFT (Traffic Flow Template), SI bearer ID (SI interface bearer ID). When the service identifier is not the E-RAB ID, if the eNB needs to accurately distinguish the service of the UE to be aggregated and transmitted, the RN needs to associate the identifier with the E-RAB ID after the radio bearer is established for the UE. The message is sent to the eNB so that the eNB knows in a subsequent process.

Therefore, the multiplex layer should contain one of the following information or any combination thereof: interface (values S1, X2), control plane or user plane CU (values CP, UP), upper layer protocol (ie interface and CU fields) Combination: S1AP, X2AP, Sl-U, X2-U), UE identity, or priority or Qos attribute, and service flow/service bearer identity.

The multiplex layer is a peer entity established between the RN and the eNB. Specifically, it may be set below the PDCP peer entity between the RN and the eNB, or above, or in the PDCP peer entity (that is, combined with the PDCP peer entity). For the S1 or X2 interface signaling of the control plane signaling, the multiplex layer may also be placed in the RRC, that is, the upper layer protocol indication is added in the RRC message, and the S1AP and X2AP messages are encapsulated in the RRC message, and the transmission may be omitted. Some S1APs and X2APs carry SCTP/IP, which saves air interface overhead.

For the user plane, the UEID in the multiplex layer, the field of the service flow/service bearer indication, can be represented by the TEID (tunnel port identifier) of the GTP-U layer. For the control plane, the UEID in the multiplex layer, the field of the service flow/traffic bearer indication, can be represented by the Port Number of the SCTP layer.

The multiplexing layer may further add a field for identifying the GW or MME. The eNB can judge the destination of the uplink packet according to this field. Since the multiplexed data may be data of multiple services of multiple UEs, the multiplex layer may further add an identifier of a priority or QoS attribute, The data packets of the same priority or the QoS attribute are multiplexed together, so that the eNB can treat the forwarded data packets differently, so that services with higher requirements for QoS are better satisfied. Alternatively, for multiplexed data with different priorities or QoS attributes, the underlying wireless link can be configured with different MCS configurations, and adaptively adjusted based on priority or QoS attributes to better ensure service quality.

For example, when the UE switches between the RN and the eNB, the X2 interface needs to perform data forwarding. Through the multiplexing layer, the RN can use the radio bearer existing by the RN and the eNB. For example, the S1 interface is previously carried to carry the forwarding on the X2 interface. The switching data is distinguished by adding an interface identifier in the multiplexing layer to distinguish the data of the S1 interface or the data of the X2 interface. The advantage of multiplexing is that there is no need to establish a radio bearer for the same UE again, which can shorten the handover delay and reduce the allocation management of radio resources.

For example, a radio bearer is established for multiple services on the RN and the eNB, and multiple service flows or service bearers are transmitted on one radio bearer, and are identified by a service flow/service bearer field. According to this identifier, it can be used to distinguish multiple service flows or service bearers of the same UE, or to distinguish service flows or service bearers of different UEs when the service flows or services have similar QoS characteristics. The multiplex layer peer entity can reduce the allocation management of wireless resources by including the service flow/service bearer field identifier.

Different from the wireless environment between the traditional eNB and the UE, the wireless environment between the RN and the eNB is UE-independent. The services or data flows of all UEs have the same channel environment, so the same MCS can be used for transmission. Channel configuration, etc., to reduce the overhead of scheduling individual UEs.

The RLC, MAC, and PHY entities between the RN and the eNB are RN-specific and independent of the UE. The PDCP peer entity between the RN and the eNB is used to encapsulate the data of the UE, and indicates the identity of the UE and the identifier of the service in the PDCP. The PDCP packet of the aggregate transmission may encapsulate data of one or more UEs, and for each UE, data of one or more services may also be encapsulated. For example, the multiplexing of PDCPs of multiple UEs and multiple services is used as an example. Two configurations as shown in FIG. 16 or FIG. 17 can be used. From the perspective of implementation, in terms of user plane, multiple UEs and IP packets of multiple services can be multiplexed. For example, the PDCP PDU in Figure 16 can be replaced by the packet sequence + IP packet. The principle is similar. Narration. As shown in Figure 16, the first level: The SDU of the PDCP is changed from the original single SDU to the Aggregated PDCP SDU (aggregated transmitted PDCP SDU). The MAC Header, the RLC Header, and the PDCP Header are the information added by the Relay's MAC, RLC, and PDCP layers. The PDCP part may have an encryption and/or integrity protection function, and the key used is a relay-specific key configured by the network to the Relay when the relay accesses. That is, the aggregate PDCP SDU of the Relay is encrypted/decrypted with the relay's encryption context.

Second level: An Aggregated PDCP SDU contains several RB PDUs (Traffic Flow or Service Bearer) PDUs. The header portion may include upper layer interface/protocol indication and/or configuration information of several resource block RB PDUs (such as number configuration information) and/or priority or Qos attributes.

Level 3: Each RB PDU includes a UE ID, a Service Identity, and a PDCP PDU. The PDCP PDU is formed after processing for each UE, which may have header compression and/or encryption and/or integrity protection functions, ie, the second level of encryption and/or integrity protection of the entire packet, the key used. It is the key of the UE. The key can be configured by the network side to the RN and the eNB during the UE initiated connection.釆 Two-stage encryption can enhance the security of the relay wireless access link.

As shown in Figure 17, the first level: The SDU of the PDCP is changed from the original single SDU to the Aggregated PDCP SDU (the PDCP SDU of the aggregate transmission). The MAC Header, the RLC Header, and the PDCP Header are the information added by the Relay's MAC, RLC, and PDCP layers. The PDCP part may have encryption and/or integrity protection functions, and the key used is an RN-specific key configured by the network to the RN when the RN accesses. That is, the aggregated PDCP SDU of the RN is added/densified by the RN's encryption context.

Second level: An Aggregated PDCP SDU contains several PDUs (service flows or bearers) for several UEs. The header portion may include an upper layer interface/protocol indication and/or configuration information of several UEs (such as the number of UEs) and/or a priority or Qos attribute.

The third level: Each UE PDU includes a header (UE ID/UE identifier, the number of PDUs of the UE), and a number of aggregated packets, each of which is composed of a service flow/service bearer identifier and a PDCP PDU. The PDCP PDU is formed after processing for each UE, which can be header compressed and/or added. The secret and/or integrity protection function is the second-level encryption and/or integrity protection function of the entire packet. The key used is the key of the UE. The key can be configured by the network side during the UE initiated connection. RN and eNB.两 Two-level encryption can enhance the security of the RN wireless access link.

The respective fields of the above two data formats can be adjusted accordingly.

On the basis of the above relay transmission method, the present invention also provides the following relay nodes or base stations. Referring to FIG. 18, a relay node according to an embodiment of the present invention includes:

The S1 interface bearer unit 181 is configured to establish an S1 interface bearer of the user equipment with the core network, and the user plane compression unit 182 is configured to be used by the user plane of the S1 interface established by the S1 interface bearer unit to be used with the core network. Establishing a peer entity to compress the IP header of the user equipment;

The S1 interface compression unit 183 is configured to establish a peer entity with the base station to compress the S1 interface bearer established by the S1 interface bearer establishing unit.

In an embodiment, the S1 interface compression unit 183 is further configured to perform part of the compression of the GTP-U on the user plane, or to control the partial compression of the SCTP by the control plane.

In still another embodiment, the relay node further includes:

The multiplexing unit 184 is disposed on, in or under the S1 interface compression unit 183, for multiplexing an upper layer protocol, or multiplexing a user equipment, or multiplexing a service bearer, or indicating a priority or a quality of service attribute. . The upper layer protocol to be multiplexed includes: interface (takes the value of SI, X2), control plane or user plane CU (value is CP, UP), upper layer protocol (ie, combination of interface and CU field: S1AP, X2AP, Sl- U, X2-U )„

The relay node provided in this embodiment corresponds to the first type of relay transmission method provided by the present invention. For the analysis of the wireless backhaul transmission overhead between the relay node and the base station, refer to the corresponding method embodiment. Let me repeat.

Referring to FIG. 19, another relay node provided by an embodiment of the present invention includes:

The S1 interface bearer unit 191 is configured to establish an S1 interface bearer of the user equipment with the core network, and the compression unit 192 is configured to establish a peer entity with the base station to compress the S1 interface bearer established by the S1 interface bearer unit, and User plane carried by the S1 interface, also used to compress user equipment IP header.

In one embodiment, the compression unit 192 is further configured to partially compress the user plane to carry the GTP-U, or to partially compress the control plane to carry the SCTP.

In an embodiment, the relay node further includes:

The multiplexing unit 193 is disposed above, below or below the compression unit 192 for multiplexing the upper layer protocol, or multiplexing the user equipment, or multiplexing the service bearer, or indicating the priority or quality of service attribute. The upper layer protocol to be multiplexed includes: interface (takes the value of SI, X2), control plane or user plane CU (value is CP, UP), upper layer protocol (ie, combination of interface and CU field: S1AP, X2AP, S1- U, X2-U ).

The relay node provided in this embodiment corresponds to the second relay transmission method provided by the present invention. For the analysis of the wireless backhaul transmission overhead between the relay node and the base station, refer to the corresponding method embodiment. Let me repeat.

Referring to FIG. 20, a base station provided by an embodiment of the present invention includes:

a radio bearer unit 201, configured to establish a radio bearer of the user equipment with the relay node;

The S1 interface bearer unit 202 is configured to establish an S1 interface bearer of the user equipment with the core network, and the association unit 203 is configured to establish the radio bearer established by the radio bearer unit 201 and the

The association carried by the S1 interface established by the S1 interface bearer unit 202;

The user plane compression unit 204, for the user plane carried by the S1 interface established by the S1 interface bearer unit, is used to establish a peer entity with the relay node to compress the IP header of the user equipment.

In an embodiment, the base station further includes:

The multiplexing unit 205 is disposed on, in or under the user plane compression unit 204, for multiplexing the upper layer protocol, or multiplexing the user equipment, or multiplexing the service bearer, or indicating the priority or the quality of service attribute. The upper layer protocol of the multiplexing includes: an interface (takes values of SI, X2), a control plane or a user plane CU (valued as CP, UP), and an upper layer protocol (ie, a combination of an interface and a CU field: S1AP, X2AP, Sl-U, X2-U )„

The base station provided in this embodiment corresponds to the third relay transmission method provided by the present invention, which is For the analysis of the wireless backhaul transmission cost between the relay node and the base station, refer to the corresponding method embodiment, and details are not described herein again.

Referring to FIG. 21, an embodiment of the present invention further provides a relay node or a base station, including: a radio bearer unit 211, configured to establish a radio bearer between the relay node and the base station;

The X2 interface bearer unit 212 is configured to establish a peer entity to carry X2 interface data or signaling between the relay node and the base station.

In an embodiment, the relay node and the base station further include:

The X2 interface compression unit 213 is configured to establish a peer entity between the relay node and the base station to compress the X2 interface bearer. The X2 interface compression unit 213 can be used to partially compress the user plane to carry the GTP-U, or the partial compression control plane carries the SCTP.

In still another embodiment, the relay node and the base station further include:

The multiplexing unit 214 is disposed on, in or under the X2 interface compression unit 213, for multiplexing an upper layer protocol, or multiplexing a user equipment, or multiplexing a service bearer, or indicating a priority or a quality of service attribute. . The multiplexed upper layer protocol includes: an interface (takes a value of SI, X2), a control plane or a user plane CU (valued as CP, UP), and an upper layer protocol (ie, a combination of an interface and a CU field: S1AP,

X2AP, Sl-U, X2-U )„

The relay node provided in this embodiment corresponds to the fourth relay transmission method provided by the present invention. For the analysis of the wireless backhaul transmission overhead between the relay node and the base station, refer to the corresponding method embodiment. Let me repeat.

Referring to FIG. 22, a method for relay transmission according to a fifth embodiment of the present invention includes: Step 221: A first peer entity is established between a relay node and a base station, and is used for compression on an S1 or X2 interface.

Step 222: A second peer entity is further established between the relay node and the base station, where the second peer entity is disposed on, in or under the first peer entity, and is used for multiplexing of upper layer protocols. An indication, or a multiplexing indication of the user equipment, or a multiplexing indication of the service bearer, or an indication of a priority or quality of service attribute. The multiplexing indication of the upper layer protocol includes: a user plane protocol indication of the S1 interface, a user plane protocol indication of the X2 interface, a control plane protocol indication of the S1 interface, or a control plane protocol indication of the X2 interface. For the specific multiplexing method, refer to the above description, and details are not described herein again.

It can be understood that the compression carried by the S1 or X2 interface in the embodiment may include: partial compression of the GTP-U carried by the user plane, or partial compression of the SCTP by the control plane.

It is also understood that the relay transmission method provided by the embodiment of the present invention can be applied to the relay architecture provided by the embodiment of the present invention, and can also be applied to the existing relay architecture. limits.

By establishing a second peer entity with the base station at the relay node, the multiplexing indication for the upper layer protocol, or the multiplexing indication of the user equipment, or the multiplexing indication of the service bearer, or the indication of the priority or the quality of service attribute, The switchover delay of the upper-layer protocol is shortened, and the existing S1 or X2 interface bearer is omitted. This saves the air interface overhead and ensures better service quality.

Finally, it should be understood that those skilled in the art can understand that all or part of the process of implementing the above embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable. In the storage medium, the program, when executed, may include the flow of an embodiment of the methods as described above. The storage medium may be a magnetic disk, an optical disk, a read only memory (ROM), or a random access memory (RAM).

The functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. The integrated modules, if implemented in the form of software functional modules and sold or used as stand-alone products, may also be stored in a computer readable storage medium. The above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

The above specific embodiments are not intended to limit the present invention, and any modifications, equivalents, improvements, etc., which are included in the present invention, should be included in the present invention without departing from the principles of the present invention. Within the scope of protection.

Claims

Claim

A method for relay transmission, characterized in that it comprises:

Establishing an S 1 interface bearer of the user equipment between the relay node and the core network;

Establishing a peer entity between the relay node and the core network for the user plane carried by the S1 interface, for IP header compression of the user equipment;

A peer entity is established between the relay node and the base station, and is used for compression carried by the S1 interface.

The method according to claim 1, wherein the compression carried by the S1 interface comprises: partial compression of a user plane carrying GTP-U, or partial compression of a control plane carrying SCTP.

The method according to claim 1 or 2, wherein after the establishing a peer entity between the relay node and the base station, the method further includes:

And a multiplexing layer peer entity is further established between the relay node and the base station, where the multiplexing layer peer entity is disposed on a peer entity established between the relay node and the base station, or The multiplexing indication for the upper layer protocol, or the multiplexing indication of the user equipment, or the multiplexing indication of the service bearer, or the indication of the priority or quality of service attribute.

A method for relay transmission, characterized in that it comprises:

The relay node and the base station establish a peer entity for the compression of the S1 interface bearer, and the user plane carried by the S1 interface is also used for IP header compression of the user equipment.

The method according to claim 4, wherein the compression carried by the S1 interface comprises: partial compression of the user plane carrying the GTP-U, or partial compression of the control plane carrying the SCTP.

The method according to claim 4 or 5, wherein after the establishing a peer entity between the relay node and the base station, the method further includes:

A multiplexing layer peer entity is further established between the relay node and the base station, and the multiplexing layer peer entity is disposed on, in or under the peer entity, and is used for complexing of an upper layer protocol. An indication, or a multiplexing indication of the user equipment, or a multiplexing indication of the service bearer, or an indication of a priority or quality of service attribute.

A method for relay transmission, comprising:

Establishing a radio bearer of the user equipment between the base station and the relay node;

Establishing an S1 interface bearer of the user equipment between the base station and the core network;

Establishing, by the base station, an association between the radio bearer and the S1 interface bearer;

For the user plane carried by the S1 interface, a peer entity is established between the base station and the relay node, and is used for IP header compression of the user equipment.

The method according to claim 7, wherein after the base station and the relay node establish a peer entity, the method further includes:

A multiplexing layer peer entity is further established between the base station and the relay node, and the multiplexing layer peer entity is disposed on, in or under the peer entity, and is used for complexing of an upper layer protocol. An indication, or a multiplexing indication of the user equipment, or a multiplexing indication of the service bearer, or an indication of a priority or quality of service attribute.

A method for relay transmission, comprising:

Establishing a radio bearer between the relay node and the base station;

A peer entity is established between the relay node and the base station, and is used to carry X2 interface data or signaling.

The method according to claim 9, wherein the peer entity established between the relay node and the base station is further used for compression carried by the X2 interface.

The method according to claim 10, wherein the compression carried by the X2 interface comprises: partial compression of a user plane carrying GTP-U, or partial compression of a control plane carrying SCTP.

The method according to any one of claims 9 to 11, wherein after the establishing a peer entity between the relay node and the base station, the method further comprises:

And a multiplexing layer peer entity is further established between the relay node and the base station, where the multiplexing layer peer entity is disposed above, in or below the peer entity, and is used for an upper layer protocol. A multiplexing indication, or a multiplexing indication of the user equipment, or a multiplexing indication of the service bearer, or an indication of a priority or quality of service attribute.

13. A relay node, comprising:

An S1 interface bearer unit, configured to establish an S1 interface bearer of the user equipment with the core network; a user plane compression unit, for the user plane carried by the S1 interface established by the S1 interface bearer unit, An IP header for establishing a peer entity with the core network to compress the user equipment;

The S1 interface compression unit is configured to establish, by the peer entity, the S1 interface bearer established by the S1 interface bearer establishment unit.

The relay node according to claim 13, wherein the S1 interface compression unit is further configured to partially compress the user plane bearer GTP-U, or the partial compression control plane bears the SCTP.

The relay node according to claim 13 or 14, further comprising: a multiplexing unit, disposed above, in or below the S1 interface compression unit, for multiplexing an upper layer protocol, Or multiplex user equipment, or multiplex traffic bearers, or indicate priority or quality of service attributes.

16. A relay node, comprising:

The S1 interface bearer unit is configured to establish an S1 interface bearer of the user equipment with the core network, and the compression unit is configured to establish, by the peer entity, the S1 interface bearer established by the S1 interface bearer establishing unit, and the S1 interface bearer. The user plane carried by the interface is also used to compress the IP header of the user equipment.

The relay node according to claim 16, wherein the compression unit is further configured to partially compress the user plane to carry the GTP-U, or the partial compression control plane carries the SCTP.

The relay node according to claim 16 or 17, further comprising: a multiplexing unit, disposed above, in or below the compression unit, for multiplexing an upper layer protocol, or Use user equipment, or multiplex traffic bearers, or indicate priority or quality of service attributes.

19. A base station, comprising:

a radio bearer unit, configured to establish a radio bearer of the user equipment with the relay node;

An S1 interface bearer unit, configured to establish an S1 interface bearer of the user equipment with the core network; an association unit, configured to establish an association between the radio bearer established by the radio bearer unit and the S1 interface bearer established by the S1 interface bearer unit;

The user plane compression unit, for the user plane carried by the S1 interface established by the S1 interface bearer unit, is used to establish a peer entity with the relay node to compress the IP header of the user equipment.

The base station according to claim 19, further comprising: And a multiplexing unit, disposed above, in or below the user plane compression unit, for multiplexing an upper layer protocol, or multiplexing a user equipment, or multiplexing a service bearer, or indicating a priority or a quality of service attribute.

A relay node or a base station, comprising:

a radio bearer unit, configured to establish a radio bearer between the relay node and the base station;

The X2 interface bearer unit is configured to establish a peer entity to carry X2 interface data or signaling between the relay node and the base station.

The relay node or the base station according to claim 21, further comprising:

The X2 interface compression unit is configured to establish a peer entity between the relay node and the base station to compress the X2 interface bearer.

The relay node or the base station according to claim 22, wherein the X2 interface compression unit is further configured to partially compress the user plane bearer GTP-U, or the partial compression control plane bears the SCTP.

The relay node or the base station according to claim 22 or 23, further comprising: a multiplexing unit, disposed above, in or below the X2 interface compression unit, for multiplexing the upper layer Protocol, or reuse of user equipment, or multiplexing of service bearers, or indicating priority or quality of service attributes.

25. A method of relay transmission, comprising:

Establishing a first peer entity between the relay node and the base station for compression of the S1 or X2 interface bearer; a second peer entity is also established between the relay node and the base station, and the second peer entity Provided on, under or under the first peer entity, a multiplexing indication for an upper layer protocol, or a multiplexing indication of a user equipment, or a multiplexing indication of a service bearer, or a priority or quality of service attribute Instructions.

The method for relay transmission according to claim 25, wherein the compression carried by the S1 or X2 interface comprises: partial compression of the user plane carrying the GTP-U, or partial compression of the control plane carrying the SCTP.

The method for relay transmission according to claim 25, wherein the multiplexing indication of the upper layer protocol comprises one of the following:

The user plane protocol indication of the S1 interface, the user plane protocol indication of the X2 interface, the control plane protocol indication of the S1 interface, or the control plane protocol indication of the X2 interface.