WO2010088804A1 - Procédé de transmission par relais, noeud de relais et station de base - Google Patents

Procédé de transmission par relais, noeud de relais et station de base Download PDF

Info

Publication number
WO2010088804A1
WO2010088804A1 PCT/CN2009/071345 CN2009071345W WO2010088804A1 WO 2010088804 A1 WO2010088804 A1 WO 2010088804A1 CN 2009071345 W CN2009071345 W CN 2009071345W WO 2010088804 A1 WO2010088804 A1 WO 2010088804A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
relay node
bearer
base station
peer entity
Prior art date
Application number
PCT/CN2009/071345
Other languages
English (en)
Chinese (zh)
Inventor
蔺波
王燕
刘宇红
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN200980151450.8A priority Critical patent/CN102369765B/zh
Publication of WO2010088804A1 publication Critical patent/WO2010088804A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point

Definitions

  • 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
  • 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
  • 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.
  • the forwarded data may be forwarded by the above layers.
  • IP 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.
  • 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.
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • the data packet overhead is analyzed.
  • 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.
  • 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 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.
  • 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 fourth relay transmission method 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.
  • 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 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.
  • the peer entity 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.
  • 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.
  • 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.
  • 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.
  • FIG. 1 is a schematic diagram of an S1 interface user plane protocol stack provided by the prior art
  • FIG. 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.
  • FIG. 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
  • 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.
  • 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.
  • 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.
  • 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
  • FIG. 4 is a schematic diagram of an S1 interface control plane protocol stack architecture of the UE to the MME.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • S1AP upper layer signaling
  • X2AP X2AP
  • 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.
  • 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 .
  • 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.
  • 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.
  • the S1 interface user plane protocol stack architecture 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.
  • 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.
  • TEID Tunnel Endpoint Identifier
  • 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.
  • the PDCP peer entity on the GW moves down to the eNB.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • FIG. 10 is a schematic diagram of an S1 interface control plane protocol stack architecture of the UE to the MME.
  • TCP/UDP is not considered on the IP layer of the UE
  • 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.
  • a fourth relay transmission method 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.
  • the peer entity is also used for compression carried by the X2 interface.
  • 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.
  • FIG. 12 and FIG. 13 are schematic diagrams of two X2 interface user plane protocol stacks according to an embodiment of the present invention
  • 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.
  • 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.
  • 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.
  • the PDCP peer entity 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • the X2 interface needs to perform data forwarding.
  • the RN can use the radio bearer existing by the RN and the eNB.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the PDCP PDU in Figure 16 can be replaced by the packet sequence + IP packet.
  • the principle is similar. Narration.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a relay node includes:
  • the S1 interface bearer unit 181 is configured to establish an S1 interface bearer of the user equipment with the core network
  • 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.
  • 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.
  • 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 ) contend
  • the relay node provided in this embodiment corresponds to the first type of relay transmission method provided by the present invention.
  • 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
  • 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.
  • 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.
  • 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.
  • 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
  • the association unit 203 is configured to establish the radio bearer established by the radio bearer unit 201 and the
  • 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.
  • 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.
  • 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.
  • 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.
  • 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,
  • the relay node provided in this embodiment corresponds to the fourth relay transmission method provided by the present invention.
  • a method for relay transmission 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention, qui concerne le domaine des communications, porte sur un procédé de transmission par relais, sur un nœud de relais et sur une station de base. Le procédé peut réduire un surdébit de transmission de retour sans fil entre un nœud de relais et une station de base. Le procédé de transmission par relais comprend les étapes suivantes : un support d'interface SI d'un équipement utilisateur est établi entre un nœud de relais et un cœur de réseau ; pour le côté utilisateur, des entités poste à poste sont établies entre le nœud de relais et le cœur de réseau, ce qui est utilisé pour compresser l'en-tête IP de l'équipement utilisateur ; des entités poste à poste sont établies entre le nœud de relais et une station de base, ce qui est utilisé pour compresser le support d'interface SI. Un autre procédé de transmission par relais comprend les étapes suivantes : un support sans fil est établi entre un nœud de relais et une station de base ; des entités poste à poste sont établies entre le nœud de relais et la station de base, ce qui est utilisé pour accueillir des données d'interface X2 ou une signalisation.
PCT/CN2009/071345 2009-02-03 2009-04-17 Procédé de transmission par relais, noeud de relais et station de base WO2010088804A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN200980151450.8A CN102369765B (zh) 2009-02-03 2009-04-17 一种中继传输的方法、中继节点和基站

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN2009070352 2009-02-03
CNPCT/CN2009/070352 2009-02-03
CNPCT/CN2009/070817 2009-03-16
CN2009070817 2009-03-16

Publications (1)

Publication Number Publication Date
WO2010088804A1 true WO2010088804A1 (fr) 2010-08-12

Family

ID=42541650

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/071345 WO2010088804A1 (fr) 2009-02-03 2009-04-17 Procédé de transmission par relais, noeud de relais et station de base

Country Status (1)

Country Link
WO (1) WO2010088804A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016184347A1 (fr) * 2015-05-19 2016-11-24 华为技术有限公司 Procédé et dispositif permettant de fournir un service relais
CN108605378A (zh) * 2016-02-04 2018-09-28 华为技术有限公司 一种数据传输方法、装置及相关设备
CN110048758A (zh) * 2018-01-13 2019-07-23 华为技术有限公司 节点和通信方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1949769A (zh) * 2005-10-12 2007-04-18 华为技术有限公司 一种用户面协议栈和头压缩方法
CN1992671A (zh) * 2005-12-28 2007-07-04 上海原动力通信科技有限公司 第三代演进系统中传输ip头压缩数据包的方法
CN101335715A (zh) * 2008-07-21 2008-12-31 华为技术有限公司 无线自回传的方法、装置和系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1949769A (zh) * 2005-10-12 2007-04-18 华为技术有限公司 一种用户面协议栈和头压缩方法
CN1992671A (zh) * 2005-12-28 2007-07-04 上海原动力通信科技有限公司 第三代演进系统中传输ip头压缩数据包的方法
CN101335715A (zh) * 2008-07-21 2008-12-31 华为技术有限公司 无线自回传的方法、装置和系统

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016184347A1 (fr) * 2015-05-19 2016-11-24 华为技术有限公司 Procédé et dispositif permettant de fournir un service relais
US10326520B2 (en) 2015-05-19 2019-06-18 Huawei Technologies Co., Ltd. Method and apparatus for providing relay service using a relay user equipment
CN108605378A (zh) * 2016-02-04 2018-09-28 华为技术有限公司 一种数据传输方法、装置及相关设备
US10750357B2 (en) 2016-02-04 2020-08-18 Huawei Technologies Co., Ltd. Data transmission method and apparatus, and related device
CN108605378B (zh) * 2016-02-04 2020-12-15 华为技术有限公司 一种数据传输方法、装置及相关设备
CN112492578A (zh) * 2016-02-04 2021-03-12 华为技术有限公司 一种数据传输方法、装置及相关设备
CN110048758A (zh) * 2018-01-13 2019-07-23 华为技术有限公司 节点和通信方法
CN110048758B (zh) * 2018-01-13 2020-12-15 华为技术有限公司 节点和通信方法
US11647561B2 (en) 2018-01-13 2023-05-09 Huawei Technologies Co., Ltd. Node and communication method

Similar Documents

Publication Publication Date Title
US9999028B2 (en) Data transmission method, base station, and user equipment
US10412650B2 (en) Data transmission method, apparatus and system
US7961875B2 (en) Means and method for ciphering and transmitting data in integrated networks
EP1875763B1 (fr) Interfonctionnement de reseaux de radio cellulaires et reseaux de donnees sans fil
JP5680633B2 (ja) バックホールヘッダ圧縮
JP5088091B2 (ja) 基地局装置、通信方法及び移動通信システム
JP6084754B2 (ja) セルラ基地局、ユーザ端末、及びプロセッサ
WO2011072529A1 (fr) Système et procédé de transmission de données entre une passerelle de desserte et un terminal relais
JP2007527179A (ja) 無線通信システムの分離型媒体アクセス制御プロトコル構造と、これを用いたデータ送受信方法並びにハンドオーバー方法及びそのシステム
WO2014114101A1 (fr) Procédé et appareil de transmission de données multiflux
WO2015165051A1 (fr) Procédé et dispositif de transmission de données
WO2010121416A1 (fr) Procédé, noeud de relais et système pour traiter des données dans une liaison de relais
WO2010124641A1 (fr) Système d'évolution à long terme et son procédé de transmission de données
WO2010108353A1 (fr) Procédé et dispositif d'émission/réception pour une pdu
WO2006032213A1 (fr) Structure de reseau sans fil et procede de mise en oeuvre de transmission de donnees par application de la structure de reseau sans fil
US9332532B2 (en) Radio transmission apparatus, radio receiving apparatus, radio communication apparatus, radio transmission method, and radio receiving method
WO2011120358A1 (fr) Procédé et système de transmission d'informations dans un réseau de communication à relais
TW201531051A (zh) 媒綈存取控制依序傳遞方法及裝置
WO2013155981A1 (fr) Procédé et dispositif de dérivation de données
WO2015062287A1 (fr) Procédé et système d'échange local de terminal
WO2010133022A1 (fr) Procédé, appareil et système d'envoi et de réception de paquets vocaux
WO2010088804A1 (fr) Procédé de transmission par relais, noeud de relais et station de base
CN102369765A (zh) 一种中继传输的方法、中继节点和基站
WO2006032203A1 (fr) Reseau d'acces radio et procede de communication correspondant
WO2014205838A1 (fr) Procédé de transfert de données, équipement de nœud relais et système de réseau

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200980151450.8

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09839521

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09839521

Country of ref document: EP

Kind code of ref document: A1