CN103458398B

CN103458398B - Method and equipment for transmitting data

Info

Publication number: CN103458398B
Application number: CN201210168451.7A
Authority: CN
Inventors: 鲍炜; 焦斌; 杨义
Original assignee: China Academy of Telecommunications Technology CATT
Current assignee: China Academy of Telecommunications Technology CATT; Datang Mobile Communications Equipment Co Ltd
Priority date: 2012-05-28
Filing date: 2012-05-28
Publication date: 2017-02-08
Anticipated expiration: 2032-05-28
Also published as: CN103458398A

Abstract

The invention discloses a method and equipment for transmitting data. The method includes that relay nodes RN acquire transmission layer care-of addresses distributed by a target donor evolved node B DeNB for the relay nodes RN; the relay nodes RN inform serving gateways S-GW corresponding to user equipment UE of the transmission layer care-of addresses, and the serving gateways S-GW transmit the data which are required to be transmitted to the relay nodes RN to the target donor evolved node B DeNB by the aid of the transmission layer care-of addresses. The method and the equipment in an embodiment of the invention have the advantages that the relay nodes RN inform the serving gateways S-GW corresponding to the user equipment UE of the transmission layer care-of addresses which are distributed to the relay nodes RN by the target donor evolved node B DeNB, so that the serving gateways S-GW corresponding to the user equipment UE can directly transmit the data to the target donor evolved node B DeNB, the data can be prevented from being transmitted through P-GW (data packet networks gateway) (RN)/S-GW (RN) in data transmission procedures, the UE data packet transmission delay can be shortened, transmission load on a network can be reduced, return link resources between the P-GW (RN)/S-GW (RN) and the target donor evolved node B DeNB can be saved, and the user experience can be improved.

Description

Data transmission method and equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a data transmission method and device.

Background

As shown in fig. 1, the EPS (Evolved Packet System) is a schematic diagram of an EPS bearer, where the EPS bearer is established between a UE (User Equipment) and a P-GW (Packet Data Networks Gateway), and is used for transmitting User plane Data between the UE and the P-GW; a data packet sent by the UE is mapped to a corresponding EPS bearer, transmitted to the P-GW through the EPS bearer, enters an external network in an IP packet form, and is routed to a communication opposite terminal; and the data packet sent by the communication opposite end reaches the P-GW through the external network, and the P-GW maps the data packet to the corresponding EPS bearing and sends the data packet to the UE through the EPS bearing.

It should be noted that the complete EPS bearer includes an S5/S8 bearer, an S1 bearer and a radio bearer, and the S5/S8 bearer and the S1 bearer are in a one-to-one correspondence, and the S1 bearer and the radio bearer are in a one-to-one correspondence; wherein, the S5/S8 bearer and the S1 bearer are implemented by GTP (GPRS Tunneling Protocol ) tunnels, and one GTP Tunnel is identified by the transport layer addresses of the nodes at both ends of the Tunnel and the TEID (Tunnel Endpoint Identifier) assigned by the end node; taking S1 as an example for bearing a corresponding GTP tunnel, an uplink endpoint thereof is identified by a user plane transport layer address (IP address) of an S-GW (Serving Gateway) and a TEID allocated by the S-GW; the downlink endpoint of the S1 bearer GTP tunnel is identified by the user plane transport layer address (IP address) of the eNB (base station) and the eNB' S assigned TEID.

In order to solve the problems of poor signal coverage, frequent handover, etc. in a high-speed mobile environment, a Relay (Relay Node) supporting mobility may be deployed on a vehicle moving at a high speed to enhance the signal quality in the vehicle, and may also reduce the number of handovers of UEs by group handover.

As shown in fig. 2, in order to illustrate a network architecture after mobile RNs are deployed, RNs access a network through a Donor Cell (a Cell managed by a DeNB (Donor evolved Node B)), a core network (S-GW (UE)) connected to a UE and an MME (UE), where the S-GW (UE) represents a serving S-GW of the UE, and the MME (UE) represents a serving MME of the UE, and each RN may control one or more cells; and the UE can obtain wireless access service through accessing the cell controlled by the RN. Under the framework, an interface between the UE and the RN is called a Uu port, an interface between the RN and the DeNB is called a Un port, a logical interface between the RN and the MME (UE) is an S1-MME (Mobility Management Entity) interface, and a logical interface between the RN and the S-GW (UE) is an S1-U interface.

It should be noted that the mobile RN has dual identities of UE and eNB, and as a special UE, establishes an rnsps bearer (the nodes through which the bearer passes include RN, DeNB, S-GW (RN), P-GW (RN), etc.) between the serving S-GW of the user plane gateway node RN (i.e., S-GW (RN))/serving P-GW of RN (i.e., P-GW (RN)) and the network, and the bearer is managed by the serving MME of the control plane node RN (i.e., MME (RN)); as an eNB, the mobile RN provides an air interface (Uu port) and a wireless backhaul link (Un port) for the UE, and assists in establishing an EPS bearer for the UE (nodes through which the bearer passes include the UE, RN, S-GW (UE), serving P-GW of the UE, and the like).

As shown in fig. 3, it is a schematic view of a bearer relationship between an RN and a UE, where bearers of the UE and the RN are nested; for downlink data packets, after the data packets of the UE are mapped to the EPS bearer corresponding to the UE, the PGW corresponding to the RN is mapped to the EPS bearer corresponding to the RN for transmission, the EPS bearer data corresponding to the UE is recovered to the RN, and the data is transmitted at an empty port (Uu port); for the uplink data packet, after the data of the UE is mapped to the EPS bearer corresponding to the UE, the data is mapped to the EPS bearer corresponding to the RN for transmission, and the PGW corresponding to the RN is restored to the EPS bearer data corresponding to the UE for subsequent transmission.

It should be noted that, in terms of logical functions, the S-GW and the P-GW corresponding to the RN and the UE may be implemented in different physical entities or in the same physical entity, and an example where the two logical functions are located in the same physical entity is shown in fig. 3; in addition, logically, an opposite end of the S1 interface connected to the MME/S-GW corresponding to the UE in fig. 2 is an RN, the PGW corresponding to the RN is an IP gateway of the RN, and all IP packets sent to the RN by the MME/S-GW corresponding to the UE are routed to the PGW corresponding to the RN first and then transmitted to the RN.

In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:

when the RN is started, a closer P-GW (RN)/S-GW (RN) can be selected for the RN according to the geographical position of the DeNB selected by the RN; as the RN moves, its serving DeNB may move farther and farther away from the initially selected P-gw (RN)/S-gw (RN) due to the RN' S handover; at this time, the transmission delay of the data packet between the P-gw (RN)/S-gw (RN) and the serving DeNB of the RN will be larger and larger, resulting in a reduction in user experience; and the transmission of large data volume in long distance also consumes the backhaul link resource between the P-gw (rn)/S-gw (rn) and the DeNB.

Disclosure of Invention

Embodiments of the present invention provide a data transmission method and device, so as to reduce transmission delay and save backhaul link resources.

In order to achieve the above object, an embodiment of the present invention provides a data transmission method, including:

a relay node RN acquires a transport layer care-of address distributed by a target donor base station DeNB for the RN;

and the RN informs a service gateway S-GW corresponding to user equipment UE of the transport layer care-of address, and the S-GW sends data needing to be sent to the RN to the target DeNB by utilizing the transport layer care-of address.

The embodiment of the invention provides a data transmission method, which comprises the following steps:

a serving gateway S-GW corresponding to user equipment UE obtains a transmission layer care-of address distributed by a target donor base station DeNB for a relay node RN;

and the S-GW sends the data which needs to be sent to the RN to the target DeNB by utilizing the transport layer care-of address.

a target donor base station DeNB allocates a transfer layer care-of address for a relay node RN;

the target DeNB sends the transport layer care-of address to the RN, and the RN informs the transport layer care-of address to a service gateway S-GW corresponding to User Equipment (UE);

the target DeNB receives data which is sent by the S-GW by utilizing the transmission layer care-of address and needs to be sent to the RN;

and the target DeNB sends the data to the RN.

an operation maintenance OAM entity sends first configuration information for configuring a filling mode of a Differential Service Code Point (DSCP) to a service gateway (S-GW) corresponding to User Equipment (UE), the S-GW modifies data needing to be sent to a Relay Node (RN) by using the filling mode of the DSCP, and sends the modified data to a target donor base station (DeNB); and the number of the first and second groups,

and the OAM entity sends second configuration information for configuring the mapping relationship between the DSCP and the RN bearer to the target DeNB, the target DeNB determines the RN bearer corresponding to the DSCP value in the modified data according to the mapping relationship between the DSCP and the RN bearer, and sends the data to the RN on the determined RN bearer.

An embodiment of the present invention provides a relay node RN, including:

an obtaining module, configured to obtain a transport layer care-of address allocated by a target donor base station DeNB to an RN;

and the sending module is used for informing a service gateway S-GW corresponding to the user equipment UE of the transmission layer care-of address, and the S-GW sends data needing to be sent to the RN to the target DeNB by utilizing the transmission layer care-of address.

The embodiment of the invention provides a serving gateway S-GW, wherein the S-GW is an S-GW corresponding to user equipment UE, and the S-GW comprises:

an obtaining module, configured to obtain a transport layer care-of address allocated by a target donor base station DeNB for a relay node RN;

and the sending module is used for sending the data which needs to be sent to the RN to the target DeNB by utilizing the transport layer care-of address.

The embodiment of the invention provides a target donor base station DeNB, which comprises:

the distribution module is used for distributing a transmission layer care-of address for the relay node RN;

a first sending module, configured to send the transport layer care-of address to the RN, where the RN notifies the transport layer care-of address to a serving gateway S-GW corresponding to a user equipment UE;

a receiving module, configured to receive data that needs to be sent to the RN and is sent by the S-GW using the transport layer care-of address;

and the second sending module is used for sending the data to the RN.

An embodiment of the present invention provides an operation and maintenance OAM entity, including:

a first sending module, configured to send first configuration information for configuring a filling mode of a differentiated services code point DSCP to a serving gateway S-GW corresponding to a user equipment UE, where the S-GW modifies data to be sent to a relay node RN by using the filling mode of the DSCP, and sends the modified data to a target donor base station DeNB;

a second sending module, configured to send second configuration information used for configuring a mapping relationship between the DSCP and the RN bearer to the target DeNB, where the target DeNB determines, according to the mapping relationship between the DSCP and the RN bearer, the RN bearer corresponding to the DSCP value in the modified data, and sends the data to the RN on the determined RN bearer.

Compared with the prior art, the embodiment of the invention at least has the following advantages: in the embodiment of the invention, the RN informs the S-GW corresponding to the UE of the transmission layer care-of address distributed by the target DeNB, so that the S-GW corresponding to the UE can directly transmit data with the target DeNB, thereby avoiding the data from passing through P-GW (RN)/S-GW (RN) in the data transmission process, reducing the transmission delay of UE data packets, reducing the transmission load of a network, saving the return link resources between the P-GW (RN)/S-GW (RN) and the DeNB, and improving the user experience.

Drawings

In order to more clearly illustrate the technical solution of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.

Fig. 1 is a schematic diagram of an EPS bearer in the prior art;

fig. 2 is a schematic diagram of a network architecture after a mobile RN is deployed in the prior art;

fig. 3 is a schematic diagram of a bearer relationship between an RN and a UE in the prior art;

FIG. 4 is a schematic diagram illustrating a handover procedure of a mobile RN in the prior art;

fig. 5 is a diagram illustrating a UE data transmission path after handover in the prior art;

fig. 6 is a flowchart illustrating a data transmission method according to an embodiment of the present invention;

FIG. 7 is a flowchart illustrating a process of a RN obtaining a transport layer care-of address from a handover command according to an embodiment of the invention;

FIG. 8 is a flowchart illustrating a process of a RN obtaining a transport layer care-of address from a transport layer care-of address assignment response according to an embodiment of the invention;

FIG. 9 is a flowchart illustrating a process of a RN notifying an S-GW of a transport layer care-of address according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of a relay node RN according to a second embodiment of the present invention;

fig. 11 is a schematic structural diagram of a serving gateway S-GW according to a third embodiment of the present invention;

fig. 12 is a schematic structural diagram of a target donor base station DeNB according to a fourth embodiment of the present invention;

fig. 13 is a schematic structural diagram of an operation and maintenance OAM entity according to the fifth embodiment of the present invention.

Detailed Description

In implementing the present invention, the inventors noted that: in an LTE-a (Long Term evolution advanced) system, an RN is introduced for improving network coverage, and the RN may be deployed in a vehicle such as a train, so as to achieve the purposes of reducing the handover times of UEs in the vehicle and improving the quality of wireless signals in a car, and it should be noted that the RN deployed on the vehicle is called a mobile RN; furthermore, when the mobile RN moves with the vehicle, it needs to perform handover between different Donor cells/denbs, as shown in fig. 4, the handover procedure of the mobile RN includes the following steps:

step 1, the source DeNB performs measurement configuration on the RN, and the RN performs measurement subsequently according to the received measurement configuration information.

And step 2, on the uplink resources distributed to the RN by the source DeNB, the RN reports the measurement result, and the measurement result is used for assisting the source DeNB to carry out switching judgment.

Step 3, the source DeNB makes measurement judgment; wherein if the source DeNB decides to switch, the subsequent steps are continued.

And step 4, the source DeNB sends a switching request message to the target DeNB, wherein the switching request message contains relevant information of switching preparation.

Step 5, the target DeNB refers to the switching request message and carries out admission judgment according to the QoS (Quality of service) information of the bearer to be admitted; wherein if the target DeNB allows the RN to be admitted, performing underlying configuration to prepare handover.

Step 6, the target DeNB returns a handover request response message to the source DeNB, and the handover request response message includes a Radio Resource Control (RRC) container (RRC container), and the specific content is a handover command for triggering the RN to perform handover.

Step 7, the source DeNB transparently transmits (without any modification) the received switching command to the RN on the scheduled downlink resource; and after receiving the switching command, the RN stops transmitting and receiving data in the source DeNB.

And step 8, the source DeNB sends the serial number state information (such as the serial number of the unsuccessfully sent downlink data packet, the first serial number assignable by the target DeNB and the like) sent by the current data to the target DeNB.

It should be noted that the transmission sending state is to ensure that the sequence numbers of the data received and sent by the source and target DeNB are continuous, so as to avoid packet loss or repetition; after step 8, the source DeNB may send a downlink packet, which is received from the core network by itself but not successfully sent to the RN, to the target DeNB, so that the target DeNB continues to transmit the downlink packet to the RN; similarly, the source DeNB may send an RN uplink data packet with a discontinuous sequence number received by the source DeNB from the air interface (an air interface transmission error may cause a packet sent after the RN to be successfully received earlier than a packet sent before the DeNB, so that the packet receiving sequence number of the DeNB is discontinuous) to the target DeNB, so that the target DeNB sends a data packet with a continuous sequence number to the core network after receiving an absent data packet retransmitted by the RN.

And step 9, the RN sends a lead code to the target DeNB to establish uplink synchronization with the target DeNB.

And step 10, the target DeNB returns response information which carries uplink resources (used for subsequent transmission) allocated for the RN and RN timing advance (used for adjusting the uplink sending time of the RN and establishing uplink synchronization).

Step 11, the RN returns a switching completion message to the target DeNB; thereafter, data can be transmitted and received between the RN and the target DeNB.

And step 12, the target DeNB initiates a path switching request to the MME, and the path switching request carries user plane transport layer addresses (IP addresses) and downlink GTP tunnel identifiers (TEIDs) which are respectively appointed by the target DeNB for each RN EPS bearer.

Step 13, the MME requests an S-GW bearer modification request, and carries user plane transport layer addresses (IP addresses) and downlink GTP tunnel identifiers (TEIDs) respectively appointed by the target DeNB for each RN EPS bearer.

And step 14, the S-GW performs path switching.

And step 15, the S-GW returns a bearer modification response to the MME, and carries user plane transport layer addresses (IP addresses) and uplink GTP tunnel identifiers (TEID) which are respectively appointed by the S-GW for EPS bearers corresponding to the RNs.

And step 16, the MME returns a path switching response to the target DeNB, and carries user plane transport layer addresses (IP addresses) and uplink GTP tunnel identifiers (TEID) which are respectively appointed by the S-GW for EPS bearing corresponding to each RN.

Thus, the path switching is completed; and then sending the downlink data packet to the RN, the S-GW sending the downlink data packet to a user plane transport layer address (IP address) appointed by a corresponding target DeNB according to the bearer to which the S-GW belongs, and setting a downlink GTP tunnel identifier (TEID); for the uplink data packet sent by the RN, the target DeNB sends the uplink data packet to a user plane transport layer address (IP address) specified by the corresponding S-GW according to the bearer to which the target DeNB belongs, and sets an uplink GTP tunnel identifier (TEID).

And step 17, the target DeNB sends a terminal context release request to the source DeNB.

And step 18, the source DeNB releases the related resources allocated for the switching RN.

Based on the above handover procedure of the mobile RN, as shown in fig. 5, it is a schematic diagram of UE data transmission path after handover, and as can be seen by comparing fig. 2 and fig. 5, what changes occur before and after RN handover is: the RN data is changed from being transmitted via the source DeNB to being transmitted via the target DeNB, and it should be noted that, before and after the RN handover, the communication opposite end of the relevant network node of the UE is not changed, the core network node of the UE is still connected to the PGW corresponding to the RN through the wired port, and the UE is still connected to the RN through the air port, so that the handover of the RN between the donocell and the DeNB is invisible/imperceptible to the EPS network of the whole UE, and the UE-related handover process does not need to be executed.

When the RN is started, a P-GW (RN)/S-GW (RN) which is closer to the service DeNB can be selected for the RN according to the geographical position of the service DeNB; as the RN moves, its serving DeNB gets farther and farther away from the initially selected P-gw (RN)/S-gw (RN) due to the handover of the RN; the data routing of the UE user plane is lengthened, the end-to-end time delay of the service is increased, and the user experience is reduced; in view of the foregoing problems, embodiments of the present invention provide a data transmission method and device, where an RN notifies an S-GW corresponding to a UE of a transport layer care-of address allocated by a target DeNB for the RN, so that the S-GW corresponding to the UE can directly perform data transmission with the target DeNB, and thus, routing data to a P-GW (RN)/S-GW (RN) can be avoided in a data transmission process, transmission delay of a UE data packet is reduced, a transmission load of a network is reduced, backhaul link resources between the P-GW (RN)/S-GW (RN) and the DeNB are saved, and user experience can be improved.

The technical solutions in the present invention will be described clearly and completely with reference to the accompanying drawings, and it is obvious that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Example one

The embodiment of the invention provides a data transmission method, which is used for carrying out route optimization on user plane data in a scene of using a mobile RN; as shown in fig. 6, the method comprises the steps of:

in step 601, the RN (mobile RN) obtains a transport layer care-of address allocated by the target DeNB for itself.

In the first mode, before the RN accesses the target DeNB, the RN obtains a transport layer care-of address from a switching command; as shown in fig. 7, the process for the RN to obtain the transport layer care-of address from the handover command includes the following steps:

step 701, a source DeNB sends a switching request to a target DeNB, wherein the switching request carries an RN indication, and the RN indication is used for indicating that a switching node is an RN; in addition, the RN Context (Context) may also be carried in the handover request: such as capability information, configuration information, bearer information, etc. of the RN.

In step 702, after determining that the handover node is an RN (determined by an RN indicator carried in the handover request), the target DeNB allocates a transport layer care-of address to the RN.

Step 703, the target DeNB sends a handover request response to the source DeNB, where the handover request response carries a handover command to be transmitted to the RN, and the handover command carries a transport layer care-of address; in addition, the handover command may also carry parameter configuration information and the like that the RN needs to adopt in the target DeNB.

In a preferred implementation manner of the embodiment of the present invention, after the target DeNB receives the handover request from the source DeNB, the target DeNB may further allocate an available TEID value range to the RN, and the handover command may further carry the available TEID value range allocated by the target DeNB to the RN, and the available TEID value range allocated by each RN is different.

Step 704, the source DeNB sends a handover command to the RN, and the handover command carries a transport layer care-of address allocated by the target DeNB to the RN; preferably, the handover command may further carry an available TEID value range allocated by the target DeNB for the RN.

For the above processing flow, in order for the RN to obtain the transport layer care-of address, for the processing at the RN side: before the RN accesses the target DeNB, the RN obtains a transmission layer care-of address by receiving a switching command from the source DeNB; it should be noted that the handover command carries a transport layer care-of address, and the transport layer care-of address is notified to the source DeNB by the target DeNB through the handover request response.

Preferably, the handover command may also carry an available TEID value range allocated by the target DeNB for the RNs, and the available TEID value range allocated by each RN is different.

For the above processing flow, in order for the RN to obtain the transport layer care-of address, for the processing on the target DeNB side, then: the target DeNB needs to allocate a transport layer care-of address to the RN and send the transport layer care-of address to the RN, and the process further includes: before the RN accesses the target DeNB, the target DeNB receives a switching request from a source DeNB, and the switching request indicates that a switching node is the RN; further, after the target DeNB determines that the handover node is the RN, the target DeNB needs to allocate a transport layer care-of address for the RN and send a handover request response to the source DeNB, and the handover request response carries a handover command that needs to be transparently transmitted to the RN, and the handover command carries the transport layer care-of address.

Preferably, after receiving the handover request from the source DeNB, the target DeNB may further allocate an available TEID value range for the RN, and the handover command further carries the available TEID value range allocated by the target DeNB for the RN, and the available TEID value range allocated by each RN is different.

In a second mode, after the RN accesses the target DeNB (the target DeNB becomes the current service DeNB of the RN at this time), the RN obtains a transport layer care-of address from a transport layer care-of address allocation response; as shown in fig. 8, a diagram for the RN to obtain the transport layer care-of address from the transport layer care-of address assignment response includes the following steps:

in step 801, the RN sends a transport layer care-of address allocation request to the target DeNB to request the target DeNB to allocate a transport layer care-of address. Preferably, the transport layer care-of address allocation request may also be used to request the target DeNB to allocate an available TEID value range.

In step 802, the target DeNB allocates a transport layer care-of address for the RN after receiving the transport layer care-of address allocation request. Preferably, after receiving the transport layer care-of address allocation request, the target DeNB may further allocate an available TEID value range for the RN.

Step 803, the target DeNB sends a transport layer care-of address allocation response to the RN, and the transport layer care-of address allocation response carries the transport layer care-of address allocated by the target DeNB for the RN. Preferably, the transport layer care-of address allocation response may also carry a value range of the available TEID allocated for the RN.

It should be noted that, since the RN has dual identities of UE and eNB, the above-mentioned interaction procedure of the transport layer care-of address allocation request and the transport layer care-of address allocation response can be completed by RRC procedure (eNB-UE interaction procedure) or X2-AP procedure (inter-eNB interaction procedure).

For the above processing flow, in order for the RN to obtain the transport layer care-of address, for the processing at the RN side: after the RN accesses the target DeNB, the RN sends a transmission layer care-of address allocation request for requesting allocation of a transmission layer care-of address to the target DeNB, and obtains the transmission layer care-of address by receiving a transmission layer care-of address allocation response returned by the target DeNB.

Preferably, the transport layer care-of address allocation request is further configured to request allocation of an available TEID value range, and the transport layer care-of address allocation response further carries the available TEID value range allocated by the target DeNB to the RNs, and the available TEID value range allocated by each RN is different.

For the above processing flow, in order for the RN to obtain the transport layer care-of address, for the processing on the target DeNB side, then: the target DeNB needs to allocate a transport layer care-of address to the RN and send the transport layer care-of address to the RN, and the process further includes: after the RN accesses the target DeNB, the target DeNB receives a transport layer care-of address allocation request for requesting allocation of a transport layer care-of address from the RN, allocates the transport layer care-of address to the RN, and sends a transport layer care-of address allocation response to the RN.

Preferably, the transport layer care-of address allocation request is further configured to request allocation of an available TEID value range, after receiving the transport layer care-of address allocation request from the RN, the target DeNB allocates the available TEID value range for the RN, and the transport layer care-of address allocation response further carries the available TEID value range allocated by the target DeNB for the RN, and the available TEID value ranges allocated by each RN are different.

It should be noted that, for the first and second manners, the process of allocating the transport layer care-of address to the RN by the target DeNB further includes: when a plurality of RNs are accessed to the same target DeNB, the target DeNB allocates different transport layer care-of addresses for different RNs in the plurality of RNs; or when a plurality of RNs access to the same target DeNB, the target DeNB allocates the same transport layer care-of address for different RNs in the plurality of RNs, and allocates different available TEID value ranges for different RNs.

For the case of assigning different transport layer care-of addresses: a DeNB may have multiple transport layer care-of addresses, and when multiple RNs access to the DeNB simultaneously, the DeNB may allocate different transport layer care-of addresses to the multiple RNs so as to distinguish RNs to which different data packets belong; further, all data packets with target IP addresses being transport layer care-of addresses (any transport layer care-of address of DeNB) are routed to the DeNB to which the transport layer care-of address belongs according to an IP routing mechanism; and the DeNB may send the data packet to the corresponding RN according to the allocation record of the transport layer care-of address (i.e. the mapping relationship between the transport layer care-of address and the RN).

For the case of assigning the same transport layer care-of address: a DeNB may have multiple transport layer care-of addresses, when multiple RNs access to the DeNB at the same time, the DeNB may also allocate the same transport layer care-of addresses for the multiple RNs, and the DeNB also needs to allocate reserved TEID ranges to the RNs, and the reserved TEID ranges allocated to each RN are different, so as to distinguish RNs to which different data packets belong; further, all data packets with target IP addresses as transport layer care-of addresses are routed to the DeNB to which the transport layer care-of addresses belong according to an IP routing mechanism; and the DeNB can determine the RN to which the data packet belongs according to the target TEID carried in the data packet and the distribution record of the TEID range, and send the data packet to the corresponding RN.

In step 602, the RN notifies the S-GW corresponding to the UE (i.e. the serving S-GW of the UE, which will be directly described as S-GW in the following) of the transport layer care-of address allocated by the target DeNB for itself.

In the embodiment of the invention, after the RN obtains the care-of address of the transmission layer, the RN can inform the S-GW of the care-of address of the transmission layer through a path switching process, so that a direct data transmission tunnel is established between the S-GW and a target DeNB through the path switching process in the process of switching the DeNB by the RN; as shown in fig. 9, the process for the RN to notify the S-GW of the transport layer care-of address includes the following steps:

in step 901, the RN sends a path switching request to an MME (serving MME of the UE) to indicate EPS bearer information corresponding to the UE that needs to perform path switching.

In the path switching request, carrying a transport layer care-of address allocated by the target DeNB for the RN and a TEID of an S1-U downlink GTP tunnel allocated for an EPS bearer corresponding to each UE; it should be noted that, if the target DeNB allocates an available TEID range to the RN, the downlink TEID allocated by the RN for the EPS bearer corresponding to the UE should fall within the available TEID range allocated by the target DeNB to the RN.

Step 902, the MME sends a bearer modification request to the S-GW to request the S-GW to modify the corresponding UE bearer. Wherein, the bearing modification request carries the transmission layer care-of address.

In step 903, the S-GW performs bearer modification and converts the downlink path.

Step 904, the S-GW returns a bearer modification response to the MME to indicate which EPS bearers corresponding to the UEs have been modified; and in the bearer modification response, the TEID and the transport layer care-of address of the S1 uplink GTP tunnel of the EPS bearer corresponding to each UE are carried.

Step 905, the MME returns a path switching request response to the RN, and in the path switching request response, carries the TEID and the transport layer care-of address of the S1 uplink GTP tunnel of the EPS bearer corresponding to each UE.

It should be noted that after the above steps are completed, a direct data transmission tunnel is established between the S-GW and the target DeNB, so that UE user plane data interacted between the S-GW and the target DeNB may no longer need to be routed to the serving P-GW node of the RN.

For the above process flow, in order to transmit the transport layer care-of address to the S-GW, for the process on the RN side: RN sends path switching request carrying transport layer care-of address to MME corresponding to UE, MME informs S-GW of the transport layer care-of address through bearing modification request; for the processing on the S-GW side, then: the S-GW obtains the transport layer care-of address by receiving a bearer modification request from the MME.

Step 603, the S-GW transmits data to be transmitted to the RN to the target DeNB (i.e., the DeNB after the RN handover) using the transport layer care-of address.

In the embodiment of the invention, an OAM (Operation And Maintenance) entity can send configuration information for configuring a filling mode of a DSCP (DiffServ Code Point) to an S-GW (S-GW), the S-GW receives the configuration information from the OAM entity, modifies data needing to be sent to the RN by using the filling mode of the DSCP, And sends the modified data to a target DeNB.

In the embodiment of the invention, the step that the S-GW sends the data to the target DeNB by utilizing the transport layer care-of address comprises the following steps: and the S-GW modifies the data by using a DSCP filling mode and sends the modified data to the target DeNB by using a transport layer care-of address. Further, the S-GW modifies the data by using a DSCP filling mode, including: the S-GW fills a corresponding DSCP value for the data by using the QoS requirement of the bearer to which the data needing to be sent to the RN belongs; note that the DSCP is located in a ToS (Type of Service) field in the IP header of the data.

In step 604, the target DeNB receives data from the S-GW, which needs to be sent to the RN, and sends the data to the corresponding RN.

In the embodiment of the present invention, the process of sending data to the RN specifically includes: when different RNs are allocated with different transmission layer care-of addresses, the target DeNB determines the RN corresponding to the transmission layer care-of address carried in the data according to the mapping relation between the transmission layer care-of address and the RN, and sends the data to the determined RN; or, when different RNs are allocated with the same transport layer care-of address and different available TEID value ranges, the target DeNB determines the RN corresponding to the target TEID carried in the data according to the mapping relationship between the available TEID value ranges and the RNs, and sends the data to the determined RN.

In this embodiment of the present invention, an OAM entity may send configuration information for configuring a mapping relationship between a DSCP and an RN bearer to a target DeNB, and the target DeNB receives the configuration information from the OAM entity, determines, according to the mapping relationship between the DSCP and the RN bearer, an RN bearer corresponding to a DSCP value in modified data, and sends data to the RN on the determined RN bearer.

In the embodiment of the invention, the process that the target DeNB sends the data to the RN comprises the following steps: after receiving data (i.e. data to be sent to the RN) from the S-GW, the target DeNB maps the data to the corresponding RN bearer for encapsulation (carrying an identifier of the corresponding RN bearer) according to a DSCP domain value in the data and a mapping relationship between the DSCP and the RN bearer, and sends the data to the corresponding RN according to a sending policy (corresponding to QoS of the RN bearer) corresponding to the RN bearer.

It should be noted that after sending data to the corresponding RN, the RN determines, according to a bearer ID (identified by a TEID) corresponding to the data, an EPS bearer of the UE to which the received data belongs, and sends the data to the UE on a radio bearer corresponding to the EPS bearer. In addition, the RN can ensure that the TEID corresponding to each S1-U GTP bearer is unique on one S1-U interface; if the RN has a plurality of S1-U interfaces (the RN is connected with S-GWs corresponding to a plurality of UEs) at the same time, TEIDs corresponding to a plurality of S1-U GTP bearers on different interfaces may be repeated, in this case, the RN needs to uniquely determine the EPS bearer to which the received data belongs according to a source address (IP address of the S-GW) + the TEID in the received data.

In this embodiment of the present invention, the process is a process in which the S-GW sends data to the RN, and for the process in which the RN sends data to the S-GW, the data transmission method may further include:

the target DeNB receives uplink data which is from the RN and needs to be sent to the S-GW, and after receiving the uplink data, decapsulates the uplink data to obtain an IP data packet; if the source address of the IP data packet is a transport layer care-of address allocated by the target DeNB for the RN (namely the source address of the IP data packet is filled in as the transport layer care-of address allocated by the DeNB for the RN before the RN sends data on the air interface), the target DeNB directly sends the IP data packet to the S-GW; and if the source address of the IP data packet is not the transport layer care-of address allocated by the target DeNB for the RN, the target DeNB modifies the source address of the IP data packet into the transport layer care-of address allocated by the target DeNB for the RN, and sends the modified IP data packet to the S-GW.

It should be noted that before the RN switches into the target DeNB and triggers the S-GW to switch the target node for sending downlink data from the source DeNB to the target DeNB, the S-GW will still send the downlink data to the source DeNB; the data sent to the source DeNB needs to be mapped to the bearer of the RN and forwarded to the target DeNB by the source DeNB as the data of the RN, and the process of forwarding the data is completed in the handover process of the RN.

Example two

Based on the same inventive concept as the above method, an embodiment of the present invention further provides a relay node RN, as shown in fig. 10, where the relay node RN includes:

an obtaining module 11, configured to obtain a transport layer care-of address allocated by a target donor base station DeNB for an RN; a sending module 12, configured to notify the transport layer care-of address to a serving gateway S-GW corresponding to a user equipment UE, and send, by the S-GW, data that needs to be sent to the RN to the target DeNB by using the transport layer care-of address.

The obtaining module 11 is specifically configured to obtain the transport layer care-of address by receiving a handover command from a source DeNB before accessing to a target DeNB; wherein the handover command carries the transport layer care-of address, and the transport layer care-of address is notified to the source DeNB by the target DeNB through a handover request response; or after accessing to a target DeNB, sending a transmission layer care-of address allocation request for requesting allocation of a transmission layer care-of address to the target DeNB, and obtaining the transmission layer care-of address by receiving a transmission layer care-of address allocation response returned by the target DeNB; wherein the transport layer care-of address assignment response carries the transport layer care-of address.

In the embodiment of the invention, the switching command also carries a value range of available tunnel endpoint identification TEID allocated by the target DeNB for the RNs, and the value range of the available TEID allocated by each RN is different; or, the transport layer care-of address allocation request is further configured to request allocation of an available TEID value range, the transport layer care-of address allocation response further carries the available TEID value range allocated by the target DeNB to the RNs, and the available TEID value range allocated by each RN is different.

The sending module 12 is specifically configured to send a path switching request to a mobility management entity MME corresponding to the UE, where the path switching request carries the transport layer care-of address; notifying, by the MME, the S-GW of the transport layer care-of address via a bearer modification request.

The modules of the device can be integrated into a whole or can be separately deployed. The modules can be combined into one module, and can also be further split into a plurality of sub-modules.

EXAMPLE III

Based on the same inventive concept as the above method, an embodiment of the present invention further provides a serving gateway S-GW, where the S-GW is an S-GW corresponding to a user equipment UE, and as shown in fig. 11, the serving gateway S-GW includes:

an obtaining module 21, configured to obtain a transport layer care-of address allocated by a target donor base station DeNB for a relay node RN; a sending module 22, configured to send, by using the transport layer care-of address, data that needs to be sent to the RN to the target DeNB.

The obtaining module 21 is specifically configured to obtain the transport layer care-of address by receiving a bearer modification request from a mobility management entity MME corresponding to the UE; wherein the bearer modification request carries the transport layer care-of address, and the transport layer care-of address is sent to the MME by the RN through a path switch request.

The sending module 22 is specifically configured to receive configuration information from an operation and maintenance OAM entity, where the configuration information is used to configure a filling manner of a differentiated services code point DSCP; and modifying the data by using the filling mode of the DSCP, and sending the modified data to the target DeNB by using the transmission layer care-of address.

The sending module 22 is further configured to fill a DSCP value for the data according to a QoS requirement of a bearer to which the data to be sent to the RN belongs.

Example four

Based on the same inventive concept as the above method, an embodiment of the present invention further provides a target donor base station DeNB, and as shown in fig. 12, the target donor base station DeNB includes:

an allocating module 31, configured to allocate a transport layer care-of address for the relay node RN; a first sending module 32, configured to send the transport layer care-of address to the RN, where the RN notifies the transport layer care-of address to a serving gateway S-GW corresponding to a user equipment UE; a receiving module 33, configured to receive data that needs to be sent to the RN and is sent by the S-GW by using the transport layer care-of address; a second sending module 34, configured to send the data to the RN.

The allocating module 31 is specifically configured to receive a handover request from a source DeNB before the RN accesses a target DeNB, where the handover request indicates that a handover node is the RN; after the switching node is determined to be the RN, a transmission layer care-of address is distributed to the RN; or after the RN accesses the target DeNB, receiving a transmission layer care-of address allocation request for requesting allocation of a transmission layer care-of address from the RN, and allocating the transmission layer care-of address for the RN;

the first sending module 32 is specifically configured to send a handover request response to the source DeNB, where the handover request response carries a handover command that needs to be transparently transmitted to the RN, and the handover command carries the transport layer care-of address; or sending a transmission layer care-of address allocation response to the RN, wherein the transmission layer care-of address allocation response carries the transmission layer care-of address.

The allocating module 31 is further configured to allocate, after receiving a handover request from a source DeNB, an available tunnel endpoint identifier TEID value range to the RN, and the handover command also carries an available TEID value range allocated by the target DeNB to the RN, where the available TEID value range allocated by each RN is different; or the transport layer care-of address allocation request is further configured to request allocation of an available TEID value range, and after receiving the transport layer care-of address allocation request from the RN, the transport layer care-of address allocation request allocates the available TEID value range for the RN, and the transport layer care-of address allocation response also carries the available TEID value range allocated by the target DeNB for the RN, and the available TEID value range allocated by each RN is different.

The allocating module 31 is specifically configured to allocate different transport layer care-of addresses to different RNs in the multiple RNs when multiple RNs access the target DeNB; or when a plurality of RNs access the target DeNB, distributing the same transport layer care-of address for different RNs in the plurality of RNs, and distributing different available TEID value ranges for the different RNs.

The second sending module 34 is specifically configured to, when different RNs are allocated with different transport layer care-of addresses, determine, according to a mapping relationship between the transport layer care-of addresses and the RNs, an RN corresponding to the transport layer care-of address carried in the data, and send the data to the determined RN; or, when different RNs are allocated with the same transport layer care-of address and different available TEID value ranges, determining the RN corresponding to the target TEID carried in the data according to the mapping relationship between the available TEID value ranges and the RNs, and sending the data to the determined RN.

The second sending module 34 is specifically configured to receive configuration information from an operation and maintenance OAM entity, where the configuration information is used to configure a mapping relationship between a DSCP and an RN bearer; determining the RN bearer corresponding to the DSCP value in the data according to the mapping relation between the DSCP and the RN bearer; and sending the data to the RN on the determined RN bearer.

The target donor base station DeNB further includes: a third sending module 35, configured to decapsulate, after receiving uplink data that needs to be sent to the S-GW from the RN, the uplink data to obtain an IP data packet; if the source address of the IP data packet is the transport layer care-of address, the IP data packet is sent to the S-GW; if the source address of the IP data packet is not the transport layer care-of address, modifying the source address of the IP data packet into the transport layer care-of address, and sending the modified IP data packet to the S-GW.

EXAMPLE five

Based on the same inventive concept as the above method, an embodiment of the present invention further provides an operation and maintenance OAM entity, as shown in fig. 13, where the operation and maintenance OAM entity includes:

a first sending module 41, configured to send first configuration information used for configuring a filling mode of a DSCP to a serving gateway S-GW corresponding to a user equipment UE, where the S-GW modifies data to be sent to a relay node RN by using the filling mode of the DSCP, and sends the modified data to a target donor base station DeNB; a second sending module 42, configured to send second configuration information used for configuring a mapping relationship between the DSCP and the RN bearer to the target DeNB, where the target DeNB determines, according to the mapping relationship between the DSCP and the RN bearer, the RN bearer corresponding to the DSCP value in the modified data, and sends the data to the RN on the determined RN bearer.

Through the above description of the embodiments, those skilled in the art will clearly understand that the present invention may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.

Those skilled in the art will appreciate that the drawings are merely schematic representations of one preferred embodiment and that the blocks or flow diagrams in the drawings are not necessarily required to practice the present invention.

Those skilled in the art will appreciate that the modules in the devices in the embodiments may be distributed in the devices in the embodiments according to the description of the embodiments, and may be correspondingly changed in one or more devices different from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

The above disclosure is only for a few specific embodiments of the present invention, but the present invention is not limited thereto, and any variations that can be made by those skilled in the art are intended to fall within the scope of the present invention.

Claims

1. A method for transmitting data, comprising:

the RN informs a service gateway S-GW corresponding to user equipment UE of the transport layer care-of address, and the S-GW sends data needing to be sent to the RN to the target DeNB by utilizing the transport layer care-of address;

the RN acquiring a transport layer care-of address allocated by a target DeNB for the RN comprises the following steps:

before the RN accesses a target DeNB, the RN obtains the transmission layer care-of address by receiving a switching command from a source DeNB; wherein the handover command carries the transport layer care-of address, and the transport layer care-of address is notified to the source DeNB by the target DeNB through a handover request response.

2. The method of claim 1,

the switching command also carries a value range of available tunnel endpoint identification TEID allocated by the target DeNB for the RNs, and the value range of the available TEID allocated by each RN is different; or,

the transport layer care-of address allocation request is also used for requesting allocation of an available TEID value range, the transport layer care-of address allocation response also carries the available TEID value range allocated by the target DeNB for the RNs, and the available TEID value range allocated by each RN is different.

3. The method of claim 1, wherein the RN notifying the UE corresponding S-GW of the transport layer care-of address comprises:

the RN sends a path switching request to a Mobile Management Entity (MME) corresponding to the UE, and the path switching request carries the transport layer care-of address; notifying, by the MME, the S-GW of the transport layer care-of address via a bearer modification request.

4. A method for transmitting data, comprising:

the S-GW sends data needing to be sent to the RN to the target DeNB by using the transport layer care-of address;

the S-GW sending, to the target DeNB, data that needs to be sent to the RN by using the transport layer care-of address, including:

the S-GW receives configuration information from an operation maintenance OAM entity, and the configuration information is used for configuring a filling mode of a Differential Service Code Point (DSCP);

and the S-GW modifies the data by using the filling mode of the DSCP and sends the modified data to the target DeNB by using the transmission layer care-of address.

5. The method of claim 4, wherein the obtaining, by the S-GW corresponding to the UE, the transport layer care-of address allocated by the target DeNB for the RN comprises:

the S-GW obtains the transport layer care-of address by receiving a bearer modification request from a Mobility Management Entity (MME) corresponding to the UE; wherein the bearer modification request carries the transport layer care-of address, and the transport layer care-of address is sent to the MME by the RN through a path switch request.

6. The method of claim 4, wherein the S-GW modifying the data with the DSCP filling pattern comprises:

and the S-GW fills a DSCP value for the data by using the QoS requirement of the bearer to which the data needing to be sent to the RN belongs.

7. A method for transmitting data, comprising:

the target DeNB sends the data to the RN;

the process that the target DeNB allocates a transport layer care-of address for the RN and sends the transport layer care-of address to the RN further comprises the following steps:

before the RN accesses a target DeNB, the target DeNB receives a switching request from a source DeNB, and a switching node is indicated to be the RN in the switching request; after determining that the switching node is the RN, the target DeNB allocates a transport layer care-of address for the RN, sends a switching request response to the source DeNB, and the switching request response carries a switching command which needs to be transmitted to the RN through, and the switching command carries the transport layer care-of address.

8. The method of claim 7, wherein the method further comprises:

after receiving a handover request from a source DeNB, the target DeNB allocates an available Tunnel Endpoint Identifier (TEID) value range for the RNs, and the handover command also carries the available TEID value range allocated by the target DeNB for the RNs, and the available TEID value range allocated by each RN is different; or,

the transport layer care-of address allocation request is further used for requesting allocation of an available TEID value range, after receiving the transport layer care-of address allocation request from the RN, the target DeNB allocates an available TEID value range for the RN, and the transport layer care-of address allocation response also carries the available TEID value range allocated by the target DeNB for the RN, and the available TEID value range allocated by each RN is different.

9. The method of claim 7, wherein the target DeNB allocates a transport layer care-of address for the RN, comprising:

when a plurality of RNs are accessed to the target DeNB, the target DeNB allocates different transport layer care-of addresses for different RNs in the plurality of RNs; or,

when a plurality of RNs are accessed to the target DeNB, the target DeNB allocates the same transport layer care-of address for different RNs in the plurality of RNs, and allocates different available TEID value ranges for the different RNs.

10. The method of claim 8, wherein the target DeNB sends the data to the RN, comprising:

when different RNs are allocated with different transmission layer care-of addresses, the target DeNB determines the RN corresponding to the transmission layer care-of address carried in the data according to the mapping relation between the transmission layer care-of address and the RN, and sends the data to the determined RN; or,

and when different RNs are allocated with the same transport layer care-of address and different available TEID value ranges, the target DeNB determines the RN corresponding to the target TEID carried in the data according to the mapping relation between the available TEID value ranges and the RNs, and sends the data to the determined RN.

11. The method of claim 7, wherein the target DeNB transmitting the data to the RN, comprising:

the target DeNB receives configuration information from an operation maintenance OAM entity, and the configuration information is used for configuring a mapping relation between a DSCP (differential service code point) and an RN (relay node) bearer;

the target DeNB determines an RN bearer corresponding to the DSCP value in the data according to the mapping relation between the DSCP and the RN bearer;

and the target DeNB sends the data to the RN on the determined RN bearer.

12. The method of claim 7, wherein the method further comprises:

after receiving uplink data which is from the RN and needs to be sent to the S-GW, the target DeNB decapsulates the uplink data to obtain an IP data packet;

if the source address of the IP data packet is the transport layer care-of address, the target DeNB directly sends the IP data packet to the S-GW;

and if the source address of the IP data packet is not the transport layer care-of address, the target DeNB modifies the source address of the IP data packet into the transport layer care-of address and sends the modified IP data packet to the S-GW.

13. A Relay Node (RN), comprising:

a sending module, configured to notify the transport layer care-of address to a serving gateway S-GW corresponding to a user equipment UE, and send, by the S-GW, data that needs to be sent to the RN to the target DeNB by using the transport layer care-of address;

the obtaining module is specifically configured to obtain the transport layer care-of address by receiving a handover command from a source DeNB before accessing to a target DeNB; wherein the handover command carries the transport layer care-of address, and the transport layer care-of address is notified to the source DeNB by the target DeNB through a handover request response.

14. The relay node RN of claim 13,

15. The relay node RN of claim 13,

the sending module is specifically configured to send a path switching request to a mobility management entity MME corresponding to the UE, where the path switching request carries the transport layer care-of address; notifying, by the MME, the S-GW of the transport layer care-of address via a bearer modification request.

16. A serving gateway (S-GW), wherein the S-GW is an S-GW corresponding to a User Equipment (UE), the S-GW comprising:

a sending module, configured to send, to the target DeNB, data that needs to be sent to the RN by using the transport layer care-of address;

the sending module is specifically configured to receive configuration information from an operation and maintenance OAM entity, where the configuration information is used to configure a filling mode of a DSCP; and modifying the data by using the filling mode of the DSCP, and sending the modified data to the target DeNB by using the transmission layer care-of address.

17. The serving gateway S-GW of claim 16,

the obtaining module is specifically configured to obtain the transport layer care-of address by receiving a bearer modification request from a mobility management entity MME corresponding to the UE; wherein the bearer modification request carries the transport layer care-of address, and the transport layer care-of address is sent to the MME by the RN through a path switch request.

18. The serving gateway, S-GW, of claim 17,

the sending module is further configured to fill a DSCP value for the data according to a QoS requirement of a bearer to which the data to be sent to the RN belongs.

19. A target donor base station, DeNB, comprising:

a second sending module, configured to send the data to the RN;

the allocation module is specifically configured to receive a handover request from a source DeNB before the RN accesses a target DeNB, where the handover request indicates that a handover node is the RN; and after the switching node is determined to be the RN, a transmission layer care-of address is distributed to the RN.

20. The target donor base station, DeNB, of claim 19,

the first sending module is specifically configured to send a handover request response to the source DeNB, where the handover request response carries a handover command that needs to be transparently transmitted to the RN, and the handover command carries the transport layer care-of address; or sending a transmission layer care-of address allocation response to the RN, wherein the transmission layer care-of address allocation response carries the transmission layer care-of address.

21. The target donor base station, DeNB, of claim 20,

the allocation module is further configured to allocate an available Tunnel Endpoint Identifier (TEID) value range to the RNs after receiving a handover request from a source DeNB, and the handover command also carries the available TEID value range allocated by the target DeNB to the RNs, where the available TEID value range allocated to each RN is different; or the transport layer care-of address allocation request is further configured to request allocation of an available TEID value range, and after receiving the transport layer care-of address allocation request from the RN, the transport layer care-of address allocation request allocates the available TEID value range for the RN, and the transport layer care-of address allocation response also carries the available TEID value range allocated by the target DeNB for the RN, and the available TEID value range allocated by each RN is different.

22. The target donor base station, DeNB, of claim 19,

the allocating module is specifically configured to allocate different transport layer care-of addresses to different RNs in the multiple RNs when the multiple RNs access the target DeNB; or when a plurality of RNs access the target DeNB, distributing the same transport layer care-of address for different RNs in the plurality of RNs, and distributing different available TEID value ranges for the different RNs.

23. The target donor base station, DeNB, of claim 22,

the second sending module is specifically configured to, when different RNs are allocated with different transport layer care-of addresses, determine, according to a mapping relationship between the transport layer care-of addresses and the RNs, an RN corresponding to the transport layer care-of address carried in the data, and send the data to the determined RN; or, when different RNs are allocated with the same transport layer care-of address and different available TEID value ranges, determining the RN corresponding to the target TEID carried in the data according to the mapping relationship between the available TEID value ranges and the RNs, and sending the data to the determined RN.

24. The target donor base station, DeNB, of claim 19,

the second sending module is specifically configured to receive configuration information from an operation and maintenance OAM entity, where the configuration information is used to configure a mapping relationship between a DSCP and an RN bearer; determining the RN bearer corresponding to the DSCP value in the data according to the mapping relation between the DSCP and the RN bearer; and sending the data to the RN on the determined RN bearer.

25. The target donor base station DeNB of claim 19, further comprising:

a third sending module, configured to decapsulate, after receiving uplink data that needs to be sent to the S-GW from the RN, the uplink data to obtain an IP data packet; if the source address of the IP data packet is the transport layer care-of address, the IP data packet is sent to the S-GW; if the source address of the IP data packet is not the transport layer care-of address, modifying the source address of the IP data packet into the transport layer care-of address, and sending the modified IP data packet to the S-GW.