WO2010096963A1 - Configuration method and apparatus for wireless backhaul ip address - Google Patents

Abstract

A configuration method and apparatus for wireless backhaul IP address are used to configure the IP address of the inner network of an operator for a slave base station, wherein, the backhaul terminal communicating with the slave base station is non-bridge mode, the method includes the following steps: the primary base station instead of the slave base station initiates the address application to the inner network element of the operator (S601); the primary base station receives the allocated IP address for the slave base station returned by the inner network element of the operator, and establishes the mapping relationship between the applied IP address and the pre-obtained IP address of the backhaul terminal (S602). Therefore, the intercommunication between the slave base station and the inner network element of the operator is ensured.

Description

 Wireless backhaul IP address configuration method and device

Technical field

 The present invention relates to the field of wireless communication technologies, and in particular, to a wireless backhaul IP address configuration method and apparatus.

Background technique

 With the large-scale deployment of third-generation mobile communication technology (3rd Generation, 3G) broadband wireless access, such as High-Speed Packet Access (HSPA), microwave access, global interoperability access (Worldwide Interoperability) The large-scale deployment of Microwave Access (WiMAX) has led to significant growth in mobile data services. At the same time, the future of 4th Generation (4G) network technology (Long Term Evolved, LTE) / 802.16m standardization is progressing rapidly, and the data rate is expected to reach 100Mbps or more. However, regardless of 3G or the future 4G, the mobile network will face some problems, including the poor access quality of the mobile equipment (User Equipment, UE) at the edge of the cell coverage, the existence of coverage holes and coverage holes, and poor indoor coverage. For operators, it takes a lot of cost to achieve wireless coverage deployment. In addition, with the substantial increase in the wireless access rate, low cost is also required for the existing wireless access transmission network, especially in countries and regions where the cost of the wireless transmission network accounts for about 1/3.

 Finding a relatively low-cost, scalable backhaul solution is one of the key issues for mobile operators to consider. The backhaul (backhaul) refers to the connection between the base station (Node B, NB) and the gateway (Gateway), which is located between the access network and the backbone network. The backhaul refers to the connection of the access network or the cell site to the switching center. The switching center is connected to the backbone network, and the backbone network is connected to the core network. Thus, the backhaul link network is the middle layer of any telecommunications network structure that sits between the access network and the backbone network, providing an important connection between the two networks. For example, when a user accesses a wireless fidelity device (Wi-Fi) in an Internet cafe, the Wi-Fi device must be connected back to the Internet Service Provider (ISP), and the link task is Can be served by WiMAX. This feature helps service providers reduce the cost of backhaul transmissions. Wireless Backhaul transmission is relatively wired backhaul, construction complexity is small, and no trench wiring is required.

The transmission mode of the wireless backhaul is that the UE is used as the transmission bearer of the base station, and the transmission problem of some small base stations can be solved by cascading the two-level wireless access links. See Figure 1, for the wireless backhaul network junction. The base station 1 generally corresponds to a picocell base station or a femtocell base station, or may be a macro base station, and is generally deployed to indoor or rural areas such as homes and enterprise networks. The normal terminal 1, 2, and the backhaul terminal are the same type of terminal, but the backhaul terminal can provide the backhaul transmission capability for the base station 1. It can also be considered that the uplink and downlink data of the base station 1 is the upper layer service data of the backhaul terminal. The base station 2 generally corresponds to the macro base station, and can provide the backhaul transmission capability for the base station 1 in addition to providing access capability for the directly accessed terminal (for example, the ordinary terminal 2). The base station 1 and the base station 2 are base stations of the same standard or different standards, but the volume, the access capability, the coverage area, and the like may be different, and the frequency points used may be the same or different.

 It should be noted that the backhaul link is limited by the bandwidth limitation of the backhaul terminal and the base station 2. Therefore, the wireless backhaul is more suitable for supplementary coverage, especially the coverage rate of the base station such as the coverage of the hole scenario, the indoor coverage scenario, the home coverage scenario, and the rural coverage scenario. Application scenarios that are not too high and that are difficult to deploy or costly. It can be seen that the advantage of the wireless backhaul scheme is achieved by a simple combination of existing devices, whether for wideband code division multiple access packet data transmission (Wideband Code Division).

Multiple Access (WCDMA) or LTE (including Frequency Division Duplex Mode (FDD) and Time Division Duplex (TDD)) or WiMAX systems eliminate the need to define additional standard protocols to reduce product development cycles and costs.

 The focus of this paper is as follows: The base station 1 in Figure 1 is used as an example. Although it is deployed on the user side (for example, in the home or enterprise), it belongs to the carrier equipment and must be managed by the network management server of the operator, and the base station. 1 It also needs to be connected with the internal signaling gateway and service gateway of the operator. Therefore, for the IP address allocation of the base station 1, the network management server or the dynamic host must allocate the protocol (Dynamic Host Configuration Protocol Server, DHCP). Server) can be used to interconnect with the intranet of the carrier.

 In the following, for the signaling gateway, the service gateway, and the network management server, the following is simply referred to as the internal network element of the operator; for the network element connecting the internal network of the operator and the external public network, hereinafter referred to as the public network connection network element; The base station of the 1 function is simply referred to as the slave base station, and the base station for performing the function of the base station 2 is simply referred to as the master base station.

 The wireless backhaul networks covered in this paper include LTE, WiMAX, WCDMA, and Time Division-Synchronous Code Division Multiple Access (Time Division-Synchronous Code Division Multiple Access,

For networks such as TD-SCDMA, the following uses LTE as an example. As an example of the LTE wireless backhaul application, the following briefly introduces the technical background of LTE.

 Referring to FIG. 2, it is a schematic diagram of a network structure of a UMTS Terrestrial Radio Access Network (E-UTRAN). In the overall architecture and interface of the LTE, the logical network elements involved are an evolved Node B (eNB), a Mobility Management Entity (MME), a Serving Gateway (S-GW), and a packet data network. Gateway (PEN-Gateway, P-GW), the interface has S1 interface and X2 interface. The LTE user plane protocol stack and interface definitions: The involved logical network elements are UE, eNB, S-GW, and P-GW. It can be seen that the IP data packet of the UE is carried by the PDCP on the LTE-Uu interface. The Sl-U and S5/S8 interfaces are carried by the GPRS Tunneling Protocol (GTP) tunnel. The LTE control plane protocol stack and interface definition: The involved logical network elements are UE, eNB, and MME. It can be seen that the NAS signaling of the UE is based on the Radio Resource Control (RRC) on the LTE-Uu interface. / Packet Data Convergence Protocol (PDCP) bearer, SI access point (Sl-AP) / Stream Control Transmission Protocol (SCTP) tunnel on the Sl-MME interface Hosted. The signaling layer of the eNB and the MME is carried by the SCTP tunnel on the S1-MME interface. If in the Pico/Femtocell application scenario, the above eNB is replaced by Pico/Femtocell NB; accordingly, the interface and protocol stack are basically unchanged. In 3GPP, the Pico/Femtocell NB is uniformly defined as an LTE home base station (eHomeNodeB, eHB).

 The following uses LTE as an example to introduce two schemes for assigning IP addresses to base stations that are most relevant to the present invention. The first solution is that the base station is in the base station address allocation of the operator's internal network.

 Referring to FIG. 3, it is a schematic diagram of an existing macro base station network architecture in an LTE system. The network element in Figure 3 includes a macro base station (corresponding to LTE eNB), a signaling gateway (corresponding to LTE MME), a service gateway (corresponding to LTE S-GW/P-GW), and a network management server (corresponding to OM Server).

 The internal network of the carrier is used for interworking between the network side devices of the carrier. Each device is configured with one or more internal network IP addresses for communication. This internal network IP is a private network IP for the Internet network. Internal network, this intranet IP is unique and can be routed.

The external public network is generally an Internet network and is used for interconnection and intercommunication of various Internet services. Generally, the IP address of the UE is allocated by the service gateway, and may be an external public network IP or a private network IP. The private network IP only needs to be unique within the service gateway, so the UE and the service gateway can be considered. It also constitutes a private network. This new private network is isolated from the internal network of the operator. If it is a public network IP, the service packets of the UE can directly enter the external public network after reaching the service gateway. At this time, the service gateway assumes the role of the router.

 For the configuration of the IP address of the macro base station:

 · One of the IP address allocation methods: After the macro base station is powered on, the network management server sends an IP address to the macro base station through the connection with the network management server.

 • IP address allocation method 2: After the macro base station is powered on, the DHCP server is responsible for assigning an IP address to the macro base station by initiating a DHCP process.

 The address of the macro base station may be multiple, for example, it is divided into network management IP, service IP, and signaling IP, and communicates with the network management server, the service network management, and the signaling network management respectively, and is convenient for management; the address may also be one, that is, the network management IP, The service IP and signaling IP are the same, and the macro base station uses an IP address to simultaneously communicate with the network management server, the service gateway, and the signaling gateway.

 The inventor of the present invention found in the research process that if a network management server similar to the above is used,

The DHCP server allocates an IP address to the macro base station, which corresponds to FIG. 1, that is, the network management server or the DHCP server in the wireless backhaul network allocates an IP address to the base station 1, and the corresponding interactive message passes through the backhaul terminal and the base station 2, but In the existing process, the data packet of the backhaul terminal is directly sent to the service gateway through the base station 2, and the message exchange between the base station 1 and the network management server/DHCP server cannot be guaranteed.

 The second solution is that the base station is in the base station address allocation of the operator's external network.

 Based on the situation in which the base station is in the external network of the operator, refer to the deployment of the existing micro base station. See Figure 4 for a schematic diagram of the network architecture of the micro base station in the LTE system.

 The micro base station is generally in a private network, such as an enterprise network or a home network. The micro base station belongs to the operator and must be managed by the operator and can be interconnected with various network side network elements of the internal network of the operator. The micro base station needs to be assigned an internal IP address of the operator.

 You need to assign two IP addresses to the micro-base station for the private network and the internal network of the carrier. The specific process is as follows:

 • After the micro base station is powered on, obtain the IP address of a private network through the DHCP server on the private network through the DHCP process.

• After the micro base station initiates the connection with the security gateway of the carrier network, it will be in the private network. A network address translation (NAT) server maps the private IP address of the micro base station to a public network IP, and establishes a connection with the security gateway on the public network to negotiate the establishment of a secure tunnel.

 • Through this secure tunnel, the micro base station initiates a network management process or a DHCP process again, because the network management server or DHCP server of the internal network of the operator allocates an IP address of the internal network of the operator.

 Similar to the first solution, the intranet address of the micro base station can be multiple, for example, it is divided into network management IP, service IP, and signaling IP, and communicates with the network management server, the service network management, and the signaling network management respectively, which is convenient for management; It is one, that is, the network management IP, service IP, and signaling IP are the same. ^ The base station uses an IP address to communicate with the network management server, the service gateway, and the signaling gateway at the same time.

 The inventor of the present invention found in the research process that if a method similar to the above-mentioned security gateway control, the network management server or the DHCP server is used to allocate an IP address to the micro base station, the method corresponding to FIG. 1 cannot be implemented, because the wireless device of FIG. 1 There is no security gateway device in the backhaul network, and IP address allocation cannot be achieved.

Summary of the invention

 The embodiment of the present invention provides a method and a device for configuring a wireless backhaul IP address, so as to solve the problem that the network element in the base station and the carrier network cannot be interconnected and interconnected, and the existing second solution cannot be solved. The problem of implementing wireless backhaul IP address allocation.

 The solution provided by the present invention includes:

 A wireless backhaul IP address configuration method, configured to configure an IP address of an internal network of an operator for a secondary base station, where the backhaul terminal that communicates with the secondary base station is in a non-bridge mode, and includes:

 The primary base station initiates an address request instead of the slave base station to the internal network element of the operator;

 The primary base station receives the IP address applied for from the base station from the internal network element of the operator, and establishes a mapping relationship between the applied IP address and the pre-acquired backhaul terminal IP address.

 A wireless backhaul IP address configuration method, configured to configure an IP address of an internal network of an operator for a secondary base station, where the backhaul terminal that communicates with the secondary base station is in a non-bridge mode, and includes:

The backhaul terminal initiates an address application process to the public network connection network element by the primary base station to apply for an IP address; the backhaul terminal receives the applied IP address from the public network connection network element by the primary base station; The primary base station establishes an IP address to be applied for and the backhaul terminal is empty. The mapping relationship carried by the port.

 A method for configuring a wireless backhaul IP address, configured to configure an IP address of an internal network of an operator for a secondary base station, where the backhaul terminal that communicates with the secondary base station is in a bridging mode, including:

 Initiating an address application process from the base station to the internal network element of the operator through the backhaul terminal and the primary base station, and applying for an IP address;

 The internal network element of the carrier sends the IP address to the secondary base station through the primary base station and the backhaul terminal. In the address application process, the primary base station establishes a mapping relationship between the applied IP address and the backhaul terminal air interface.

 A primary base station configured with a wireless backhaul IP address, configured to configure an IP address of an internal network of the operator for the secondary base station, where the backhaul terminal that communicates with the secondary base station is in a non-bridge mode, including:

 In place of the address requesting unit, the address requesting unit is configured to receive an address request from the base station to the internal network element of the operator; and the address receiving unit is configured to receive an IP address that is returned by the internal network element of the operator to be allocated from the base station;

 The mapping relationship establishing unit is configured to establish a mapping relationship between the applied IP address and the pre-acquired backhaul terminal IP address.

 A primary base station configured with a wireless backhaul IP address, configured to configure an IP address of an internal network of the operator for the secondary base station, where the backhaul terminal that communicates with the secondary base station is in a non-bridge mode, including:

 The address application forwarding unit is configured to forward the address application process initiated by the backhaul terminal to the public network connection network element to apply for an IP address;

 The mapping relationship establishing unit is configured to: in the address requesting process, the primary base station establishes a mapping relationship between the applied IP address and the air interface bearer of the backhaul terminal.

 A primary base station configured with a wireless backhaul IP address, configured to configure an IP address of an internal network of the operator for the secondary base station, where the backhaul terminal that communicates with the secondary base station is in a bridging mode, including:

 An address request forwarding unit, configured to forward an address application process sent by the backhaul terminal initiated by the base station to the internal network element of the operator, and apply for an IP address;

The mapping relationship establishing unit is configured to establish, in the address application process, a mapping relationship between the applied IP address and the air interface bearer of the backhaul terminal. It can be seen that the embodiment of the present invention provides a method for configuring an IP address from a base station in a wireless backhaul application scenario, by storing the slave base station IP address and the backhaul terminal IP address/air interface on the primary base station. The mapping relationship correspondence table ensures that the base station 1 as shown in FIG. 1 can normally communicate with the internal network elements of the operator, such as the network management server, the service gateway, and the signaling gateway.

DRAWINGS

 1 is a schematic structural diagram of a wireless backhaul network in the prior art;

 2 is a schematic structural diagram of an E-UTRAN network in the prior art;

 3 is a schematic diagram of a network structure of a macro base station of an LTE system in the prior art;

 4 is a schematic diagram of a micro base station network architecture in an LTE system in the prior art;

 5 is a schematic structural diagram of a wireless backhaul network of an LTE system according to the present invention;

 6 is a flowchart of Embodiment 1 of a method for configuring a wireless backhaul IP address according to the present invention;

 FIG. 7 is a flowchart of Embodiment 1 of an LTE system according to an embodiment of the present invention;

 Figure 8 is a flow chart of the attachment application IP address;

 Figure 9 is a flow chart of the DHCP application IP address;

 10 is a flowchart of Embodiment 2 of a method for configuring a wireless backhaul IP address according to the present invention;

 FIG. 11 is a flowchart of Embodiment 2 of an LTE system according to an embodiment of the present invention;

 FIG. 12 is a flowchart of Embodiment 3 of a method for configuring a wireless backhaul IP address according to the present invention;

 FIG. 13 is a flowchart of Embodiment 3 of an LTE system according to an embodiment of the present invention;

 FIG. 14 is a schematic structural diagram of a primary base station according to Embodiment 1 of a wireless backhaul IP address configuration apparatus according to the present invention; FIG. 15 is a schematic structural diagram of a primary base station according to Embodiment 2 of a wireless backhaul IP address configuration apparatus according to the present invention; A schematic diagram of the structure of the primary base station of the third embodiment of the apparatus. detailed description

 The present invention will be described in detail below with reference to the drawings and specific embodiments.

Referring to FIG. 5, a schematic diagram of a wireless backhaul network structure of an LTE system, where the eNB 501 corresponds to the primary base station of the backhaul network, the eHB 502 corresponds to the secondary base station of the backhaul network, and the network management data of the eHB 502 is transmitted by the backhaul terminal (B-UE) 503 and the eNB 501. The signaling data and the service data are backhauled to the network management server (OM Server or DHCP Server) 504, MME 505, and S-GW 506 corresponding to the eHB 502. As shown in FIG. 5, the embodiment of the present invention aims to allocate and use the IP address of the eHB 502 to ensure interconnection between the eHB 502 and the corresponding network management server 504, MME 505, and S-GW 506. In the specific implementation of the present invention, it may be different depending on the mode of operation of the B-UE.

 The B-UE working modes include the following two types:

 Non-bridge mode: B-UE typical working mode, working at the IP layer, with IP address; all packets from eHB are treated as B-UE IP layer application packets for unified processing; B-UE built-in DHCP Server function and NAT Address translation function;

 Bridging mode: The B-UE works at the L2 layer. All the packets from the eHB are directly sent to the eNB, or the packets received from the air interface are forwarded to the eHB.

 The embodiments of the present invention are described below in different working modes of the B-UE. First, the first embodiment is to introduce a scheme for configuring an IP address from a base station when the B-UE working mode is a non-bridge mode.

 Referring to FIG. 6, a flowchart of Embodiment 1 includes:

 S601: The primary base station sends an address request to the internal network element of the operator instead of the secondary base station;

 S602: The primary base station receives the IP address applied by the base station from the internal network element of the operator, and establishes a mapping relationship between the applied IP address and the pre-acquired backhaul terminal IP address.

 The specific primary base station refers to the eNB, and the secondary base station refers to the eHB. The internal network element of the operator includes the MME, the S-GW, and the network management server (OM Server or DHCP Server).

 The first embodiment will be described in detail by taking the LTE system as an example.

 Referring to FIG. 7, a flow chart of Embodiment 1 in which an LTE system is taken as an example includes:

 S701: The B-UE initiates a network access process, and obtains a public network or private network IP address for the Internet service.

 The network access process initiated by the B-UE is prior art and will not be discussed in detail herein. During the process of the B-UE initiating the network access process by the eNB, the eNB saves the B-UE IP address.

 S702: The eNB initiates an address request process to the OM Server/DHCP server by using the eHB corresponding to the B-UE that initiates the network access process in step S701, and obtains the IP address of one or more internal networks of the operator allocated for the eHB, and saves, and establishes this / mapping relationship between some IP addresses and B-UE IP addresses;

The eNB needs to configure the correspondence between the B-UE and the eHB, for example, the mapping between the B-UE identifier and the eHB identifier, so that after the B-UE of the S701 enters the network, the eNB can learn that the B-UE is known. The corresponding eHB generation is the application IP address.

 The IP address of the eNB instead of the eHB application includes one or more of a network management IP address, a signaling IP address, and a service IP address.

 In addition, preferably, in the address application procedure, the eNB carries the identifier of the eHB that is known in advance. The purpose of the eNB to replace the eHB initiating the address request process with the eHB is to enable the OM Server/DHCP Server to learn the address assignment and record for eHB. The eNB needs to know the identifier of the eHB in advance, for example, directly configuring the identifier of the eHB on the eNB. The identifier may be the eHB device number, the Media Access Control (MAC) address, or the unique identifier of the eHB such as the International Mobile Subscriber Identification Number (IMSI).

 Preferably, the eNB sends its own IP address to the OM Server/DHCP Server to initiate the address request process, so that the OM Server/DHCP Server can know that the IP address of the eNB and the IP address of the eNB belong to the same network segment. The eHB IP address can be used to communicate with the internal network element of the carrier. When the IP address assigned by the OM Server/DHCP Server for the eHB and the IP address of the eNB do not belong to the IP address of the same network segment, the IP address can be converted by the existing networking technology to implement the eHB and the internal NE of the carrier. Communication.

 S703: After the eHB device is started, initiate a DHCP process requesting IP address allocation, and the B-UE allocates a private network IP address to the DCCP Server, for example, 192.168.X.X;

 S704: When the eHB communicates with the internal network element of the operator (for example, when communicating with the MME/S-GE/OM Server), the processing procedure of the uplink IP data packet is:

 After obtaining the uplink IP packet from the eHB, the B-UE performs a NAT address translation, that is, the private network IP address of the source address eHB is converted into the IP address of the B-UE. After the NAT address translation, the B-UE sends the IP packet to the B-UE. eNB;

 After receiving the uplink IP packet, the eNB performs an address mapping, that is, the IP address of the source address B-UE is modified to the intranet IP address of the corresponding eHB according to the mapping relationship table established in S702 (the network management IP address and the information obtained by S702) After one of the IP address and the service IP address, the address mapping is performed, and then the eNB sends the IP packet to the internal network element of the operator;

 Thus, in step S704, the internal network element of the operator can know that it is communicating with the eHB.

S705: When the eHB communicates with the internal network element of the operator (for example, the MME/S-GE/OM Server The processing time of the downlink IP data packet is:

 After receiving the downlink IP packet from the internal network element of the operator, the eNB performs address mapping, that is, according to the mapping relationship table established in S702, the destination address is the intranet IP address of the eHB (the network management IP address and signaling IP address obtained by S702). And one of the service IP addresses is modified to the IP address of the corresponding B-UE, after performing address mapping, the eNB sends the IP data packet to the B-UE;

 After obtaining the downlink IP packet from the eHB, the B-UE performs a NAT address translation, that is, the IP address of the destination address B-UE is converted into the private network IP address of the eHB. After the NAT address translation, the B-UE sends the IP packet to the IP address. eHB.

 Therefore, in step S705, the eNB can learn that the IP data packet is sent to the B-UE through the air interface bearer of the B-UE, and then sent to the eHB.

 In summary, in the first embodiment, the IP address of the B-UE is mapped to the internal IP address of the eHB on the eNB. The main reason is that the IP address obtained by the B-UE is in accordance with the process in the prior art. Public network or private network IP address used for Internet services. This IP address cannot be used for communication on the internal network of the carrier. In the second embodiment described below, another scheme for configuring an IP address for the eHB when the B-UE working mode is the non-bridge mode. In this solution, the B-UE and the eHB are bound: After the B-UE enters the network, the B-UE is directly assigned the IP address of the internal network of the operator, and the IP address is also when the eHB communicates with the internal network element of the operator. The IP address used.

 In summary, in the second embodiment, the B-UE obtains an IP address through the existing LTE IP address application process. The key is that the internal network element of the operator needs to identify that the B-UE is a backhaul terminal, not an ordinary terminal. The B-UE may obtain or configure the identifier of the eHB in advance, and carry the eHB identifier in the address request related message, so that the network side network element learns that the eHB is assigned an internal addressable IP address of the operator, and The IP address must belong to the same network segment as the IP address of the corresponding eNB device.

 In the existing LTE system, there are two solutions for the UE to apply for an IP address, one is an attach process and the other is a DHCP process. In order to understand the second embodiment more smoothly, the two existing solutions are briefly introduced. .

 See Figure 8. The process for the UE to apply for an IP address through the Attach request:

The SeNB sends an attach request (Attach Request) message to the MME via the eNB, Requesting an IP address;

 In S802, the MME sends a Create Default Bearer Request message to the P-GW via the S-GW.

 Optionally, remote authentication dial-in user service (RADIUS/diameter protocol (RADIUS protocol upgrade protocol, Diameter) is performed between the P-GW and the external PDN (External PDN) through S803. DHCP); The Radius or Diameter protocol is a bearer protocol that carries DHCP.

 In S804, the P-GW returns a Create Default Bearer Response message to the MME through the S-GW, and carries an IP address or an address prefix allocated to the UE.

 The SMME returns an Attach Accept message to the UE through the eNB, and carries an IP address or an address prefix assigned to the UE.

 Through the attach process, the P-GW allocates an IP address to the UE, and notifies the UE of the allocation result through the Attach Accept message. At this time, the IPv6 only brings back the address prefix, and the address configuration needs to be completed in S806 and S807:

 S806 ~ S807: The UE initiates a routing request (Router Solicitation) to the P-GW, and the P-GW

The UE returns a Router Advertisement to complete the IP address allocation to the UE.

 See Figure 9, for the UE to apply for IP address allocation through DHCP:

 The SeNB initiates an attach process with the eNB, the S-GW, and the P-GW to complete the default bearer setup.

 If the Attach process does not assign a successful IP address, the UE triggers the DHCP process to apply for the assigned address:

 In S902 ~ S903, the DHCP discovery process is completed: the UE sends a DHCP Discover message to the intranet (intranet) or the ISP (Internet Service Provider) via the eNB, the S-GW, and the P-GW; the intranet or the ISP The UE returns a DHCP Allow message.

 Among them, S903 may be repeated many times.

In S904 ~ S905, the DHCP response process is completed: the UE sends a DHCP Request message to the Intranet or the ISP via the eNB, the S-GW, the P-GW, and requests the address allocation; the Intranet or the ISP returns a DHCP response (DHCP ACK) to the UE. ) message, completed as the IP address of the UE Match.

 It should be noted that, the P-GW allocates an address to the UE, and may directly allocate an address by the P-GW address pool, or may apply for allocation by the P-GW to the external P-GW, or may also use P- The GW applies for allocation to the DHCP Sever. The specific allocation manner is transparent to the UE, and the unified can be considered as being allocated by the P-GW. This article does not limit this.

 After introducing the scheme in which the existing Attach and DHCP processes allocate addresses to the UE, the scheme of the second embodiment will be described in detail.

 Referring to FIG. 10, a flowchart of Embodiment 2 includes:

 S1001: The backhaul terminal initiates an address application process to the public network connection network element by the primary base station, and applies for an IP address;

 S1002: The backhaul terminal receives the applied IP address from the public network connection network element by the primary base station; wherein, in the address application process, the primary base station establishes an applied IP address and a backhaul terminal air interface. The mapping relationship of the bearer.

 Preferably, the backhaul terminal applies for an IP address belonging to the same network segment as the IP address of the primary base station, and thus, the IP address can directly realize communication between the base station and the internal network element of the operator; when the applied IP address and the IP address of the primary base station When the network segment does not belong to the same network segment, the address can be translated through the existing networking technology, and the internal network element of the slave base station and the carrier can also be communicated.

 If it is specific to the backhaul network of the LTE system, the above-mentioned primary base station refers to the eNB, the secondary base station refers to the eHB, the backhaul terminal refers to the B-UE, and the public network connected network element refers to the P-GW. In addition, in the LTE system, the internal network element of the operator includes the MME, the S-GW, and the network management server (OM Server or DHCP Server).

 The preferred embodiment 2 will be described in detail below by taking the LTE system as an example.

 Referring to FIG. 11, the flow of the second embodiment of the LTE system is as follows:

 S1101: The P-GW allocates an IP address in the same network segment as the eNB address to the B-UE through the Attach or DHCP process. In the Attach or DHCP process, the eNB records the P-GW allocated to the B-UE. IP address, and establish a mapping relationship between the IP address and the B-UE air interface bearer; meanwhile, the B-UE saves the applied IP address;

 There are two issues to solve here:

First, the internal network element of the operator needs to identify that the B-UE is a backhaul terminal, not an ordinary terminal. The The problem is solved by carrying the eHB identity to the P-GW in the Attach or DHCP process. Specifically, the e-BB identifier may be carried in the B-UE address request message, for example, an Attach Request message from the eNB to the MME, and a Create Default Bearer from the MME to the S-GW/P-GW.

The eHB identifier is carried in the Request message, and the eHB identifier is carried in the "client identifier" or "chadder (client hardware address)" attribute of the DHCP message. The eHB identifier may be obtained or configured in advance in the B-UE, and the specific form of the identifier is not limited, and may be an eHB device number, a MAC address, or an eHB unique identifier such as IMSI.

 Second, the internal network element of the operator needs to know the eNB address, so that the B-UE can be assigned an address that belongs to the same network segment as the eNB. This problem is solved by carrying the eNB address to the P-GW in the Attach or DHCP procedure.

 Specifically, a or b can be optionally implemented:

 a. When the B-UE enters the network and initiates the attach procedure to establish a default bearer (e.g., the default bearer), the eNB fills in its own IP address into the interactive message to notify the P-GW, specifically to the LTE message, which can be created in Create Default. The Bearer Request message carries the IP address of the eNB, so that the P-GW can allocate an IP address to the B-UE that belongs to the same network segment as the eNB address.

 b. If the Attach process does not assign an address to the B-UE, the DHCP process may be triggered to allocate an address. At this time, the eNB fills in its own IP address into the DHCP message, for example, fills in the "giaddr" field of the DHCP message. In this way, the P-GW can allocate an IP address to the B-UE that belongs to the same network segment as the eNB address.

 The P-GW allocates an address to the UE, and may directly allocate an address from the address pool of the P-GW, or may apply for allocation to the external P-GW by the P-GW, or apply to the DHCP Sever through the P-GW. Allocation, specifically, these allocation methods are transparent to the UE, and the unification can be considered as being allocated by the P-GW. This article does not limit this.

It should be noted that any one of the eHB identifier and the eNB IP address may be carried in the address application process, or may not be carried. When only the eHB identifier is carried, the P-GW learns that the IP address is assigned to the eHB, and the IP address can be assigned to the IP address. After the IP address is converted by the networking technology, the communication with the internal network element of the carrier can be implemented. When only the eNB IP address is carried, the P-GW allocates an IP address that belongs to the same network segment as the eNB IP address, so that the eHB can communicate with the internal network element of the operator by directly using the IP address; P-GW protection when eNB IP address The identifier is stored and assigned an IP address that belongs to the same network segment as the eNB IP address.

 S1102: After the eHB device is started, initiate a DHCP process request IP address allocation, and the B-UE acts as

The DCCP Server assigns it a private IP address, such as 192.168.X.X;

 S1103: When the eHB communicates with the internal network element of the operator (for example, when communicating with the MME/S-GE/OM Server), the processing of the uplink IP data packet:

 After obtaining the uplink IP packet from the eHB, the B-UE performs a NAT address translation, that is, the private network IP address of the source address eHB is converted into the IP address of the B-UE obtained in the step S1101. After the NAT address translation, B- The UE sends the IP packet to the eNB, and the eNB does not perform special processing to forward the data packet to the network element.

 S1104: When the eHB communicates with the internal network element of the operator (for example, when communicating with the MME/S-GE/OM Server), the processing of the downlink IP data packet:

 After receiving the downlink IP packet from the internal network element of the operator, the eNB performs address mapping, that is, according to the mapping relationship table established by the eNB in S1101, the data packet is put into the radio bearer of the B-UE for transmission;

 After the data packet arrives at the B-UE, the B-UE performs an address translation. The IP address of the B-UE is translated into the private network address of the eHB. After the address translation is completed, the data packet is forwarded to the eHB. Finally, the third embodiment is introduced. When the B-UE working mode is the bridge mode, the scheme for configuring the IP address from the base station is adopted.

 Referring to FIG. 12, a flowchart of Embodiment 3 includes:

 S1201: Initiating an address application process from the base station to the internal network element of the operator through the backhaul terminal and the primary base station, and applying for an IP address;

 S1202: The internal network element of the operator sends the IP address to the secondary base station through the primary base station and the backhaul terminal. In the address application process, the primary base station establishes a mapping relationship between the applied IP address and the bearer terminal air interface bearer.

 Preferably, the base station applies for an IP address that belongs to the same network segment as the IP address of the primary base station, thereby using the IP address to directly implement communication between the base station and the internal network element of the operator; when applying for the IP address and the IP address of the primary base station When the network segment does not belong to the same network segment, the address can be translated through the existing networking technology, and the internal network element of the slave base station and the carrier can also be communicated.

If it is specific to the backhaul network of the LTE system, the above primary base station refers to the eNB, and the secondary base station refers to eHB, the internal network element of the operator includes the MME, the S-GW, and the network management server (OM Server or DHCP Server).

 The following describes the third embodiment with the LTE system as an example.

 When the B-UE is in the bridging mode, due to the characteristics of the bridging mode (the B-UE works in the L2 layer, all the packets from the eHB are directly put into the air interface bearer and sent to the eNB, or the packets received from the air interface are directly forwarded to the packet. eHB), the eHB DHCP request message can be transparently transmitted to the eNB through the B-UE. For the specific process, see Figure 13, including:

 S1301: After the eHB device is started, an address request process, such as a DHCP process, is initiated. When the request packet is transparently transmitted to the eNB through the B-UE, the eNB fills in its own IP address into the message, for example, "giaddr" filled in the DHCP message. In the field, then forwarded to the OM Server/DHCP Sever; thus, the OM Server/DHCP Sever can determine the IP address of the same subnet as the eNB to be assigned to the eHB according to the giaddr field in the received message;

 In addition, the OM server/DHCP Sever can also be configured to assign an arbitrary IP address to the eHB. The eHB and the intranet can also be implemented after the IP address is converted by the existing networking technology. Meta communication.

 S1302: The OM Server/DHCP Sever returns a DHCP response by the eNB, and the response is transmitted to the B-UE, and the B-UE is transparently transmitted to the eHB.

 When the DHCP responds to the eNB, the eNB saves the applied eHB IP address (including the network management IP address, the signaling IP address, and the service IP address), and establishes a mapping relationship between the IP address and the B-UE radio bearer. ;

 S1303: When the eHB communicates with the internal network element of the operator (for example, the MME/S-GE/OM Server), the uplink does not perform special processing. When the destination address is the IP address of the eHB, the address mapping is performed at the eNB: The mapping relationship table established by S1302 is put into the radio bearer of the B-UE for transmission, and then transmitted to the eHB.

In addition, in the third embodiment, in addition to the DHCP process as illustrated in FIG. 13, the eHB may obtain an IP address belonging to the same network segment as the eNB through another address request procedure. In addition, DHCP here includes DHCPv4, DHCPv6 and other address application procedures. At the same time, it needs to be stated that the DHCP process can be carried on other protocols, such as the Radius/Diameter/DHCP process mentioned above. In addition, an embodiment of the present invention further provides an apparatus for configuring a wireless backhaul IP address, specifically, It refers to the primary base station, which corresponds to the LTE wireless backhaul network, and refers to the eNB device.

 Referring to FIG. 14, it is a schematic diagram of the internal structure of the primary base station in the first embodiment of the apparatus.

 The primary base station is configured to configure an IP address of the internal network of the operator for the secondary base station, where the backhaul terminal that communicates with the secondary base station is in a non-bridge mode, and the primary base station includes:

 The address requesting unit 1401 is used instead of initiating an address request from the base station to the internal network element of the operator;

 An address receiving unit 1402, configured to receive an IP address that is returned by the internal network element of the operator, and is an IP address allocated from the base station;

 The mapping relationship establishing unit 1403 is configured to establish a mapping relationship between the applied IP address and the pre-acquired backhaul terminal IP address.

 Preferably, the primary base station further includes:

 The uplink data packet processing unit 1404 is configured to modify, according to the mapping relationship established by the mapping relationship establishing unit 1403, the source address of the uplink data packet received from the backhaul terminal into an IP address applied by the base station, where the source address is a backhaul terminal IP address. And then sending the uplink data packet to the internal network element of the operator;

 The downlink data packet processing unit 1405 is configured to: according to the mapping relationship established by the mapping relationship establishing unit 1403, the destination address is a secondary base station IP address, and then send the downlink data packet to the backhaul terminal.

 Preferably, the primary base station further includes:

 The address request control unit 1406 is configured to control the substitute address requesting unit 1401 to carry the slave base station identifier or/and the primary base station IP address to the internal network element of the operator in the address request process.

 Referring to FIG. 15, it is a schematic diagram of the internal structure of the primary base station in the second embodiment of the apparatus.

 The primary base station is configured to configure an IP address of the internal network of the operator for the secondary base station, where the backhaul terminal that communicates with the secondary base station is in a non-bridge mode, and the primary base station includes:

 The address request forwarding unit 1501 is configured to forward the address request process initiated by the backhaul terminal to the public network connection network element, and apply for an IP address;

 The mapping relationship establishing unit 1502 is configured to: in the address requesting process, the primary base station establishes a mapping relationship between the applied IP address and the air interface bearer of the backhaul terminal.

Preferably, the primary base station of the second embodiment further includes: The address request forwarding control unit 1503 is configured to control, from the base station identifier or/and the primary base station IP address, to the public network connection network element by using an address request procedure.

 Therefore, when the public network connection network element receives the IP address of the primary base station, it can allocate an IP address that belongs to the same network segment as the IP address of the primary base station, thereby directly implementing the secondary base station and the carrier internal network by using the IP address. When the IP address of the application does not belong to the same network segment as the IP address of the primary base station, the address can be converted by the existing networking technology, and the internal network element of the slave base station and the carrier can also be communicated. When the public network connection network element receives the IP address of the primary base station, it can be known that the address is assigned to the secondary base station. At this time, the public network connection network element can save the identifier.

 Preferably, the primary base station of the second embodiment further includes:

 The uplink data packet forwarding unit 1504 is configured to forward the uplink data packet sent by the backhaul terminal to the internal network element of the operator;

 The downlink data packet processing unit 1505 is configured to: put, according to the mapping relationship, a downlink data packet sent by an internal network element of the operator into a radio bearer of the backhaul terminal, and transmit the data packet to the backhaul terminal.

 Referring to FIG. 16, it is a schematic diagram of the internal structure of the primary base station in the third embodiment of the apparatus.

 The primary base station is configured to configure an IP address of the internal network of the operator for the secondary base station, where the backhaul terminal that communicates with the secondary base station is in a bridge mode, and the primary base station includes:

 The address request forwarding unit 1601 is configured to forward an address application process sent by the backhaul terminal initiated by the base station to the internal network element of the operator, and apply for an IP address;

 The mapping relationship establishing unit 1602 is configured to establish, in the address application process, a mapping relationship between the applied IP address and the bearer terminal air interface bearer.

 Preferably, the primary base station of the third embodiment further includes:

 The address request forwarding control unit 1603 is configured to control, by using the address requesting process, the IP address of the primary base station to be transmitted to the internal network element of the operator.

 Therefore, the address request forwarding unit 1601 can apply for an IP address that belongs to the same network segment as the IP address of the primary base station. At this time, the IP address can be directly used to communicate with the internal network element of the operator from the base station; When the IP address of the primary base station does not belong to the same network segment, the existing network technology can be used to translate the address, and the base station can communicate with the internal network element of the carrier.

 Preferably, the primary base station of the third embodiment further includes:

The uplink data packet forwarding unit 1604 is configured to forward the uplink data packet sent by the backhaul terminal to the transport Business internal network element;

 The downlink data packet processing unit 1605 is configured to: put the downlink data packet sent by the internal network element of the operator into the radio bearer of the backhaul terminal to transmit to the backhaul terminal according to the mapping relationship. In summary, the embodiment of the present invention provides a mapping relationship between a base station IP address and a backhaul terminal IP address/air port bearer mapping on the primary base station in the wireless backhaul application scenario. The base station 1 as shown in FIG. 1 can be properly interconnected with various network elements (such as a network management server, a service gateway, and a signaling gateway) in the same carrier network.

 In addition, it should be noted that the embodiment of the present invention is described by taking an LTE system as an example, but the embodiments of the present invention are equally applicable to other similar wireless backhaul networks, such as WiMAX, WCDMA, and TD-SCDMA networks.

 The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalents, improvements, etc., which are made within the spirit and principles of the present invention, should be included in the present invention. Within the scope of protection.

Claims

Rights request  A wireless backhaul IP address configuration method, configured to configure an IP address of an internal network of an operator for a slave base station, where the backhaul terminal that communicates with the slave base station is in a non-bridge mode, and the method includes:  The primary base station initiates an address request instead of the slave base station to the internal network element of the operator;  The primary base station receives the IP address applied for from the base station from the internal network element of the operator, and establishes a mapping relationship between the applied IP address and the pre-acquired backhaul terminal IP address.  2. The method of claim 1 wherein:  Before the primary base station sends an address request to the internal network element of the operator instead of the base station, the method further includes: the backhaul terminal initiates a network access procedure to the primary base station, and obtains a backhaul terminal IP address;  The primary base station sends an address request to the internal network element of the operator instead of the secondary base station, which means that the primary base station searches for the corresponding slave base station and the backhaul terminal, instead of the slave base station corresponding to the backhaul terminal that initiates the network access process. The internal network element initiates an address request.  3. The method according to claim 1, further comprising:  The primary base station carries the secondary base station identifier or/and the primary base station IP address in the process of the primary base station initiating an address request from the base station to the internal network element of the operator;  The intranet of the operator receives and records the identity of the slave base station from the primary base station, or/and the internal network element of the operator allocates an IP address that belongs to the same network segment as the IP address of the primary base station from the base station. .  The method according to claim 3, wherein the identifier of the slave base station comprises a device number from the base station, a medium access control address of the slave base station, or an international mobile subscriber identity of the slave base station.  The method according to any one of claims 1 to 4, characterized in that the IP address assigned to the base station comprises one or more of a network management IP address, a signaling IP address and a service IP address.  The method according to claim 1, wherein after the primary base station establishes a mapping relationship between the applied IP address and the pre-obtained backhaul terminal IP address, the method further includes:  After obtaining the uplink data packet from the base station, the backhaul terminal converts the source address from the private network IP address of the base station to the IP address of the backhaul terminal, and then sends the data packet to the primary base station; The primary base station modifies the source address as the backhaul terminal IP address into a slave base according to the mapping relationship table. The IP address applied by the station, and then the data packet is sent to the internal network element of the operator.  The method according to claim 1 or 6, wherein after the primary base station establishes a mapping relationship between the applied IP address and the pre-obtained backhaul terminal IP address, the method further includes:  After receiving the downlink data packet from the internal network element of the operator, the primary base station modifies the IP address requested by the base station from the IP address applied by the base station to the IP address of the backhaul terminal according to the mapping relationship table, and then sends the data packet to the backhaul terminal;  The backhaul terminal translates the destination address into its own IP address into the private network IP address of the secondary base station, and then sends the data packet to the secondary base station.  A wireless backhaul IP address configuration method, configured to configure an IP address of an internal network of an operator for a slave base station, where the backhaul terminal that communicates with the slave base station is in a non-bridge mode, and the method includes:  The backhaul terminal initiates an address application process to the public network connection network element by the primary base station to apply for an IP address; the backhaul terminal receives the applied IP address from the public network connection network element by the primary base station; The primary base station establishes a mapping relationship between the applied IP address and the air interface bearer of the backhaul terminal.  9. The method according to claim 8, wherein the address application process refers to an attach procedure;  The backhaul terminal initiates an address application process to the public network connection network element, and the application for the IP address includes: carrying the slave base station identifier or/and the primary base station IP address in the default bearer setup request message sent to the public network connection network element in the attach procedure ;  If the default bearer setup request message includes only the slave base station identifier, the public network connection network element saves the slave base station identifier, and allocates an arbitrary IP address to the backhaul terminal;  If the default bearer setup request message includes only the primary base station IP address, the public network connection network element allocates, to the backhaul terminal, an IP address that belongs to the same network segment as the primary base station IP address;  If the default bearer setup request message includes the slave base station identifier and the primary base station IP address, the public network connection network element stores the slave base station identifier, and the backhaul terminal is assigned the same IP address as the master base station. IP address of the network segment. The method according to claim 8, wherein the address application process refers to a dynamic host allocation protocol DHCP process; The backhaul terminal initiates an address application process to the public network connection network element, and the application for the IP address includes: carrying the slave base station identifier or/and the primary base station IP address in the DHCP message;  If the DHCP message includes only the slave base station identity, the public network connection network element saves the slave base station identifier, and allocates an arbitrary IP address to the backhaul terminal;  If the DHCP message includes only the IP address of the primary base station, the public network connection network element allocates, to the backhaul terminal, an IP address that belongs to the same network segment as the IP address of the primary base station;  If the DHCP message includes the slave base station identifier and the primary base station IP address, the public network connection network element stores the slave base station identifier, and allocates, to the backhaul terminal, an IP address that belongs to the same network segment as the primary base station IP address. .  The method according to claim 8, wherein after the primary base station establishes the mapping relationship between the applied IP address and the air interface bearer of the backhaul terminal, the method further includes:  After receiving the uplink data packet from the base station, the backhaul terminal converts the source address from the private network IP address of the base station to the IP address to which the application is applied, and then the data is forwarded to the internal network element of the operator by the primary base station.  The method according to claim 8 or 11, wherein after the primary base station establishes the mapping relationship between the applied IP address and the air interface bearer of the backhaul terminal, the method further includes:  After receiving the downlink data packet from the internal network element of the operator, the primary base station adds the data packet to the wireless bearer of the backhaul terminal according to the mapping relationship table for transmission;  The backhaul terminal converts the destination address of the downlink data packet to the IP address of the backhaul terminal to the private network IP address of the secondary base station, and then forwards the data packet to the secondary base station.  A method for configuring a wireless backhaul IP address, configured to configure an IP address of an internal network of the operator for the slave base station, where the backhaul terminal that communicates with the slave base station is a bridge mode, and the method includes:  Initiating an address application process from the base station to the internal network element of the operator through the backhaul terminal and the primary base station, and applying for an IP address;  The internal network element of the carrier sends the IP address to the secondary base station through the primary base station and the backhaul terminal. In the address application process, the primary base station establishes a mapping relationship between the applied IP address and the backhaul terminal air interface. 14. The method of claim 13, wherein the address application process is a DHCP process; The slave base station initiates an address application process to the internal network element of the operator through the backhaul terminal and the primary base station, and the application for the IP address includes:  The backhaul terminal transparently transmits the DHCP request to the primary base station;  After receiving the DHCP request, the intranet of the operator allocates an IP address to the base station and responds to the slave base station via DHCP.  The method according to claim 14, wherein the DHCP request carries an IP address of the primary base station; the internal network element of the carrier belongs to the same network as the IP address allocated by the base station and the IP address of the primary base station. segment.  The method according to claim 13, 14 or 15, wherein after the internal network element of the carrier sends the IP address to the secondary base station and the backhaul terminal to the secondary base station, the method further includes:  The primary base station receives the downlink data packet from the internal network element of the operator. When the destination address of the downlink data packet is an IP address applied by the base station, the downlink data packet is placed into the wireless terminal of the backhaul terminal according to the mapping relationship table. The bearer transmits and then passes to the slave base station.  A primary base station configured for a wireless backhaul IP address, configured to configure an IP address of an internal network of the operator for the secondary base station, wherein the backhaul terminal that communicates with the secondary base station is in a non-bridge mode, and the method includes:  In place of the address requesting unit, the address requesting unit is configured to receive an address request from the base station to the internal network element of the operator; and the address receiving unit is configured to receive an IP address that is returned by the internal network element of the operator to be allocated from the base station;  The mapping relationship establishing unit is configured to establish a mapping relationship between the applied IP address and the pre-acquired backhaul terminal IP address.  The primary base station according to claim 17, further comprising:  An uplink data packet processing unit, configured to modify, according to the mapping relationship, a source address of an uplink data packet received from a backhaul terminal to an IP address applied by the base station, where the source address is a backhaul terminal IP address, and then the uplink The data packet is sent to the internal network element of the operator;  a downlink data packet processing unit, configured to modify, according to the mapping relationship, a destination address of a downlink data packet received from an internal network element of the operator as an IP address of the backhaul terminal, where the destination address is an IP address applied for from the base station, The downlink data packet is then sent to the backhaul terminal. The primary base station according to claim 17 or 18, further comprising: The address request control unit is configured to control the substitute address request unit to carry the slave base station identifier or/and the primary base station IP address to the internal network element of the operator in the address application procedure.  A primary base station configured with a wireless backhaul IP address, configured to configure an IP address of an internal network of the operator for the secondary base station, wherein the backhaul terminal that communicates with the secondary base station is in a non-bridge mode, and the method includes:  The address application forwarding unit is configured to forward the address application process initiated by the backhaul terminal to the public network connection network element to apply for an IP address;  The mapping relationship establishing unit is configured to: in the address requesting process, the primary base station establishes a mapping relationship between the applied IP address and the air interface bearer of the backhaul terminal.  The primary base station according to claim 20, further comprising:  The address request forwarding control unit is configured to control, from the base station identifier or/and the primary base station IP address, to the public network connection network element by using an address request procedure.  The primary base station according to claim 20 or 21, further comprising: an uplink data packet forwarding unit, configured to forward the uplink data packet sent by the backhaul terminal to the internal network element of the operator;  The downlink data packet processing unit is configured to: put, according to the mapping relationship, a downlink data packet sent by the internal network element of the operator into the radio bearer of the backhaul terminal for transmission to the backhaul terminal.  A primary base station configured for the wireless backhaul IP address, configured to configure an IP address of the internal network of the operator for the secondary base station, where the backhaul terminal that communicates with the secondary base station is in a bridge mode, and the method includes:  An address request forwarding unit, configured to forward an address application process sent by the backhaul terminal initiated by the base station to the internal network element of the operator, and apply for an IP address;  The mapping relationship establishing unit is configured to establish, in the address application process, a mapping relationship between the applied IP address and the bearer terminal air interface bearer.  The primary base station according to claim 23, further comprising:  The address request forwarding control unit is configured to control the IP address of the primary base station to be transmitted to the internal network element of the operator through the address application process. The primary base station according to claim 23 or 24, further comprising: an uplink data packet forwarding unit, configured to forward the uplink data packet sent by the backhaul terminal to the operator Ministry network element;  The downlink data packet processing unit is configured to: forward the downlink data packet sent by the internal network element of the operator to the wireless bearer of the backhaul terminal according to the mapping relationship, and transmit the downlink data packet to the backhaul terminal.