WO2014071881A1

WO2014071881A1 - Method and device for managing backhaul network bearing

Info

Publication number: WO2014071881A1
Application number: PCT/CN2013/086856
Authority: WO
Inventors: 任亚珍
Original assignee: 华为技术有限公司
Priority date: 2012-11-09
Filing date: 2013-11-11
Publication date: 2014-05-15
Also published as: CN103813298B; CN103813298A

Abstract

The embodiments of the present invention provide a method and device for managing backhaul network bearing. The method for managing backhaul network bearing comprises that a first network device receives a attach request message with a device parameter, judges, according to the device parameter, whether the user equipment requesting for attachment is a backhaul node, and if so, transmits a request message for creating a session to a second network device, wherein, the request message for creating a session carries a international mobile subscriber identity (IMSI), a default bearing identification, and at least two special bearing identification, so that the second network device creates a default bearing and at least two special bearing for the backhaul node based on the default bearing identification and the at least two special bearing identification in the request message for creating a session. The method and device for managing backhaul network bearing provided by the embodiments of the present invention reduce the preparation time for providing service to the user equipment which access to the backhaul node, and reduce the system signaling overhead.

Description

Backhaul network bearer management method and device The application claims the priority of the Chinese patent application filed on November 09, 2012, the Chinese Patent Office, the application number is 201210447503.4, and the invention name is "backhaul network bearer management method and equipment", the entire contents thereof This is incorporated herein by reference. The present invention relates to the field of wireless communication technologies, and in particular, to a backhaul network bearer management method and device.

BACKGROUND OF THE INVENTION With the development of wireless communication systems, higher data rates and wider cell coverage are required, which are often contradictory. One solution of the prior art is to set up a backhaul node between the base station and the user for transmitting data and control information to achieve high data rate and wide coverage area, improve group mobility and cell edge coverage, and extend cell coverage and implementation. Blind area coverage.

The user equipment can directly access the network through the base station, or access the network through the backhaul node and the base station. The user equipment or the backhaul node first establishes a default bearer with the network side device, and the network side device requests or actively initiates the dynamic according to the service requirement. Establish and modify the process of dedicated bearers. Due to the large number of user equipments served by the backhaul node, the repeated bearer setup process necessarily increases the preparation time for providing services to the user equipment accessing the backhaul node, and brings a large system signaling overhead.

SUMMARY OF THE INVENTION The embodiments of the present invention provide a backhaul network bearer management method and device, which reduce the preparation time for providing service for a user equipment that accesses a backhaul node, and reduce system signaling overhead.

The first aspect, the embodiment of the present invention provides a backhaul network bearer management method, including: the first network device receives an attach request message carrying a device parameter, where the device The parameter is used to identify the user equipment, and the device parameter includes an international mobile subscriber identity; the first network device determines, according to the device parameter, whether the user equipment to be attached is a backhaul node, and if yes, sends the created to the second network device. a session request message, where the create session request message carries the identifier of the international mobile subscriber identity, the default bearer, and the identifier of at least two dedicated bearers, so that the second network device requests the session according to the session The identifier of the default bearer in the message and the identifier of the at least two dedicated bearers establish the default bearer and the at least two dedicated bearers for the backhaul node.

In a first possible implementation manner, the device parameter further includes identity indication information used to indicate that the user equipment is a backhaul node;

The first network device determines, according to the device parameter, whether the user equipment that is requested to be attached is a backhaul node, specifically:

If the first network device identifies that the device parameter includes the identity indication information, acquiring the subscription information of the user equipment according to the international mobile subscriber identity, and performing the identity indication information according to the subscription information. The verification is performed, and if the verification is successful, the user equipment is a backhaul node.

With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner, the second network device, according to the identifier and location of the default bearer in the create session request message After the identifier of the at least two dedicated bearers is that the backhaul node establishes the default bearer and the at least two dedicated bearers, the method further includes:

Sending, by the first network device, a session deletion request that carries the identifier of the default bearer to the second network device, so that the second network device deletes the identifier of the default bearer according to the session deletion request. The default bearer and all dedicated bearers corresponding to the default bearer.

In a second aspect, the embodiment of the present invention provides a backhaul network bearer management method, including: the second network device receives a create session request message sent by the first network device, where the create session request message carries an international backhaul node Mobile subscriber identity, identity of the default bearer and at least two dedicated 7-load identifiers;

And the second network device establishes the default bearer and the at least two dedicated bearers for the backhaul node according to the identifier of the default bearer in the create session request message and the identifier of the at least two dedicated bearers.

In a first possible implementation manner, the second network device, according to the creation session, invites After the identifier of the default bearer in the message and the identifier of the at least two dedicated bearers are used by the backhaul node to establish the default bearer and the at least two dedicated bearers, the method further includes: Receiving, by the network device, a data request message carrying the international mobile subscriber identity, determining whether the number of dedicated bearers established by the backhaul node corresponding to the international mobile subscriber identity reaches an upper limit, and if not, determining the to-be-established The identifier of the dedicated bearer is used to establish a dedicated bearer for the backhaul node according to the identifier of the dedicated bearer to be established, where the number of the dedicated bearer to be established is greater than 1 and less than or equal to the upper limit value.

With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner, the second network device, according to the identifier and location of the default bearer in the create session request message After the identifier of the at least two dedicated bearers is that the backhaul node establishes the default bearer and the at least two dedicated bearers, the method further includes:

The second network device receives a session deletion request that is sent by the first network device and carries the identifier of the default bearer, and deletes the default bearer and the identifier according to the identifier of the default bearer in the session deletion request. All the dedicated bearers corresponding to the default bearer.

With reference to the second aspect, or the first possible implementation manner of the second aspect, in a third possible implementation, the second network device, according to the identifier and location of the default bearer in the create session request message After the identifier of the at least two dedicated bearers is that the backhaul node establishes the default bearer and the at least two dedicated bearers, the method further includes:

The second network device monitors each dedicated bearer of the at least two dedicated bearers, and if there is no service data transmission on the dedicated bearer within a preset time range, deleting the dedicated bearer.

In a fourth possible implementation manner, the creating a session request message further carries a service quality parameter corresponding to the at least two dedicated bearers respectively;

The second network device establishes the default bearer and the at least two dedicated bearers for the backhaul node according to the identifier of the default bearer in the create session request message and the identifier of the at least two dedicated bearers. Specifically:

Adding, by the second network device, the identifier of the default bearer in the create session request message, the identifier of the at least two dedicated bearers, and the monthly good quality parameter corresponding to the at least two dedicated payloads respectively Transmitting the bearer mapping table to the backhaul node by using the first network device, so that the backhaul node respectively corresponds to the at least two dedicated bearers in the bearer mapping table. The quality of service parameters are mapped by bearers. In a third aspect, the embodiment of the present invention provides a first network device, including: a receiving unit, configured to receive an attach request message carrying a device parameter, where the device parameter is used to identify a user device, and the device parameter includes International mobile subscriber identity code;

a first requesting unit, configured to be connected to the receiving unit, configured to determine, according to the device parameter, whether the user equipment that is requested to be attached is a backhaul node, and if yes, send a create session request message to the second network device, where the creating session The request message carries the identifier of the international mobile subscriber identity, the default bearer, and the identifier of the at least two dedicated bearers, so that the second network device determines, according to the identifier of the default bearer in the create session request message, The identifiers of the at least two dedicated bearers establish the default bearer and the at least two dedicated bearers for the backhaul node.

The first requesting unit is specifically configured to: if the identifier information is included in the device parameter, obtain the subscription information of the user equipment according to the international mobile subscriber identity, and according to the subscription information, The identity indication information is verified, and if the verification is successful, the user equipment is a backhaul node.

With reference to the third aspect, or the first possible implementation manner of the third aspect, in the second possible implementation, the first network device further includes:

a second requesting unit, configured to send, to the second network device, a session deletion request that carries the identifier of the default bearer, so that the second network device determines, according to the identifier of the default bearer in the session deletion request The default bearer and all dedicated bearers corresponding to the default bearer are deleted.

In a fourth aspect, the embodiment of the present invention provides a second network device, including:

a receiving unit, configured to receive a create session request message sent by the first network device, where the create session request message carries an international mobile subscriber identity of the backhaul node, an identifier of the default bearer, and at least two dedicated 7-identity identifiers ;

The first processing unit is connected to the receiving unit, configured to establish, according to the identifier of the default bearer in the create session request message and the identifier of the at least two dedicated bearers, the default bearer and the backhaul node. The at least two dedicated bearers.

In a first possible implementation manner, the foregoing second network device further includes:

a second processing unit, configured to receive a data request that carries the international mobile subscriber identity code a message, determining whether the number of dedicated bearers established by the backhaul node corresponding to the international mobile subscriber identity reaches an upper limit, and if not, determining an identifier of the dedicated bearer to be established, according to the identifier of the dedicated bearer to be established. Establishing a dedicated bearer for the backhaul node, where the number of dedicated bearers to be established is greater than 1 and less than or equal to the upper limit value.

With reference to the fourth aspect, or the first possible implementation manner of the fourth aspect, in the second possible implementation, the second network device further includes:

a first bearer deleting unit, configured to receive a session deletion request that is sent by the first network device and that carries the identifier of the default bearer, and delete the default bearer according to the identifier of the default bearer in the session deletion request, and All dedicated bearers corresponding to the default bearers.

With reference to the fourth aspect, or the first possible implementation manner of the fourth aspect, in a third possible implementation, the second network device further includes:

And a second bearer deleting unit, configured to monitor each dedicated bearer of the at least two dedicated bearers, and if there is no service data transmission on the dedicated bearer within a preset time range, deleting the dedicated bearer.

The first processing unit is specifically configured to add, to the identifier of the default bearer in the create session request message, the identifier of the at least two dedicated bearers, and the service quality parameter corresponding to the at least two dedicated bearers respectively In the bearer mapping table, the bearer mapping table is sent to the backhaul node by the first network device, so that the backhaul node respectively corresponds to the at least two dedicated bearers in the bearer mapping table. The quality parameters are mapped by bearers.

In a fifth aspect, the present invention provides a backhaul network bearer management method, including:

The second network device receives the create session request message sent by the first network device, where the create session request message carries an identifier for identifying the international mobile subscriber identity, the identity indication information, and the default bearer of the user equipment, where the identity The indication information is used to indicate that the user equipment is a backhaul node;

The second network device establishes the default load for the backhaul node according to the identifier of the default bearer in the create session request message;

Determining, by the second network device, an identifier of at least two dedicated bearers corresponding to the backhaul node when the downlink data of the ordinary device accessed by the backhaul node arrives or receives the data request message initiated by the common device According to the identifier of the at least two dedicated bearers, The backhaul node establishes the at least two dedicated bearers.

In a first possible implementation, after the second network device establishes the at least two dedicated bearers for the backhaul node according to the identifiers of the at least two dedicated bearers, the method further includes:

In a second possible implementation, after the second network device establishes the at least two dedicated bearers for the backhaul node according to the identifiers of the at least two dedicated bearers, the method further includes:

With reference to the fifth aspect or the first or the second possible implementation manner of the fifth aspect, in a third possible implementation manner, the second network device is configured according to the identifier of the at least two dedicated bearers The backhaul node establishes the at least two dedicated bearers, specifically:

And obtaining, by the second network device, a QoS parameter corresponding to the at least two dedicated bearers, and adding, to the bearer mapping table, the QoS parameter corresponding to the identifier of the at least two dedicated bearers and the at least two dedicated bearers respectively Transmitting the bearer mapping table to the backhaul node by using the first network device, so that the backhaul node performs the service quality parameter corresponding to the at least two dedicated bearers in the bearer mapping table respectively. Bearer mapping.

In a sixth aspect, the present invention provides a second network device, including:

a receiving unit, configured to receive a create session request message sent by the first network device, where the create session request message carries an identifier for identifying an international mobile subscriber identity, an identity indication, and a default bearer of the user equipment, where The identity indication information is used to indicate that the user equipment is a backhaul node;

a first processing unit, configured to be connected to the receiving unit, configured to establish the default bearer for the backhaul node according to the identifier of the default bearer in the create session request message;

a second processing unit, configured to determine, when the downlink data of the common device accessed by the backhaul node arrives or receives the data request message initiated by the common device, determine at least two dedicated bearers corresponding to the backhaul node Identifying, according to the identifier of the at least two dedicated bearers The backhaul node establishes the at least two dedicated 7-loads.

In a first possible implementation manner, the second network device further includes:

In a second possible implementation, the second network device further includes:

With reference to the sixth aspect or the first or the second possible implementation manner of the sixth aspect, in a third possible implementation, the second processing unit is configured to obtain that the at least two dedicated bearers respectively correspond to The QoS parameter, the QoS parameter corresponding to the identifier of the at least two dedicated bearers and the at least two dedicated bearers is added to the bearer mapping table, and the bearer mapping table is sent by using the first network device Giving the backhaul node, so that the backhaul node performs bearer mapping according to the quality of service parameters corresponding to the at least two dedicated bearers in the bearer mapping table.

According to the foregoing technical solution, the backhaul network bearer management method and device provided by the embodiment of the present invention, the first network device receives an attach request message carrying a device parameter, where the device parameter is used to identify the user equipment, and the device parameter includes an international mobile user. The identification code is used to determine whether the user equipment to be attached is a backhaul node according to the device parameter, and if yes, send a create session request message to the second network device, where the create session request message carries the identifier of the international mobile subscriber identity and the default bearer. And an identifier of the at least two dedicated bearers, so that the second network device establishes a default bearer and at least two dedicated bearers for the backhaul node according to the identifier of the default bearer in the create session request message and the identifier of the at least two dedicated bearers. Through the distinction between the identity of the backhaul node and the common device, when the backhaul node accesses the network, the default load and at least two dedicated bearers are simultaneously established for the backhaul node, and when the number of common devices accessed through the backhaul node is large, the repeated establishment is avoided. The increase in the preparation time for the service provided by the bearer to the ordinary device accessing the backhaul node also reduces the system signaling overhead. BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art description will be briefly described below, and obviously, the following description will be described below. The drawings in the drawings are some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any inventive labor.

FIG. 1 is a flowchart of a first backhaul network bearer management method according to an embodiment of the present invention; FIG. 2 is a flowchart of a second backhaul network bearer management method according to an embodiment of the present invention; A flow chart of three backhaul network bearer management methods; FIG. 4 is a signaling diagram of a backhaul node attach process according to an embodiment of the present invention;

FIG. 5 is a flowchart of a fourth backhaul network bearer management method according to an embodiment of the present invention; FIG. 6 is a schematic diagram of a dedicated bearer setup signaling according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of bearer deletion signaling according to an embodiment of the present invention;

FIG. 8 is another bearer deletion signaling diagram according to an embodiment of the present invention;

FIG. 9 is a flowchart of a fifth backhaul network bearer management method according to an embodiment of the present invention; FIG. 10 is a flowchart of a sixth backhaul network bearer management method according to an embodiment of the present invention; FIG. 12 is a schematic structural diagram of a second network device according to an embodiment of the present invention; FIG. 13 is a schematic structural diagram of a first network device according to an embodiment of the present invention; FIG. 15 is a schematic structural diagram of a third network device according to an embodiment of the present invention; FIG. 16 is a fourth network structure according to an embodiment of the present invention; FIG. 17 is a schematic structural diagram of a third network device according to an embodiment of the present invention; FIG. 18 is a schematic structural diagram of a fifth network device according to an embodiment of the present invention; A sixth schematic diagram of the second network device structure.

DETAILED DESCRIPTION OF THE EMBODIMENTS In order to make the objects, technical solutions and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. It is to be understood that the described embodiments are a part of the embodiments of the invention, rather than all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

FIG. 1 is a flowchart of a first backhaul network bearer management method according to an embodiment of the present invention. As shown in FIG. 1, the backhaul network bearer management method provided in this embodiment may be specifically applied to a bearer management process of a communication system provided with a backhaul network. The communication system may specifically be an LTE (Long Term Evolution) communication system or a UMTS (Universal Mobile Telecommunications System). The LTE communication system may be specifically configured to include a packet data network gateway (Packet). Data Network Gateway, called PDN GW), Serving Gateway (Serving Gateway), Mobility Management Entity (MME), base station (evolved Node B), and backhaul nodes. . In the communication system, a common user equipment (hereinafter referred to as a normal device) can access the core network through the access network and the backhaul network, that is, the ordinary device accesses the core network via the backhaul node and the eNB. The backhaul network and the access network can use the same or different frequencies and formats. For example, the backhaul network uses LTE TDD (time-division duplex), time division duplex M乍 is the backhaul transmission, and the access network can use GSM (Global System of Mobile communication). , one of the global mobile communication systems, UMTS, Wi-Fi (Wireless Fidelity) and LTE FDD (Frequency Division Duplexing) / TDD, the backhaul network is the access network User data is transmitted. Ordinary devices can also access the core network directly through the eNB.

The backhaul network bearer management method provided in this embodiment specifically includes:

Step A10: The first network device receives an attach request message carrying a device parameter, where the device parameter is used to identify the user equipment, where the device parameter includes an international mobile subscriber identity code; specifically, when the user equipment accesses the network In the attaching process, the user equipment may be a common device or a backhaul node, and the user equipment sends an attach request message to the network device on the network side, where the attach request message carries the device parameter, and the device parameter may be specifically used to identify the user equipment. The device parameters include the International Mobile Subscriber Identification Number (IMSI). If the user equipment that initiates the attach procedure is a backhaul node, the device parameter may further include identity indication information, where the identity indication information may indicate that the user equipment is a backhaul node.

In an LTE communication system, the MME can implement the first network device, of course, in other communications. In the system, the first network device can be implemented by using a network element with similar functions. Taking the LTE communication system as an example, the process of the first network device receiving the attach request message may be: the user equipment sends an attach request message to the eNB, and the eNB sends the attach request message to the MME, that is, the first network device.

Step A20: The first network device determines, according to the device parameter, whether the user equipment to be attached is a backhaul node, and if yes, sends a create session request message to the second network device, where the create session request message carries The identifier of the international mobile subscriber identity, the default bearer, and the identifier of the at least two dedicated bearers, so that the second network device according to the identifier of the default bearer in the create session request message and the at least two The identifier of the dedicated bearer establishes the default bearer and the at least two dedicated bearers for the backhaul node.

Specifically, the manner in which the first network device determines, according to the device parameter, whether the requested user equipment is a backhaul node may be multiple:

In an implementation manner, if the user equipment to be attached is a backhaul node, the device parameter includes the identity indication information and the IMSI. If the user equipment to be attached is a common device, the device information does not include the identity indication information. If the first network device identifies that the device parameter includes the identity indication information, the subscription information of the user equipment is obtained, and if the subscription information also indicates that the identity of the user equipment is a backhaul node, the verification is successful, and the user equipment is a backhaul node. If the verification fails, the user equipment access is denied. The subscription information may be stored in a Home Subscriber Server (HSS). The first network device may query the HSS through the IMSI to obtain the subscription information of the user equipment, or directly send the IMSI to the HSS. The IMSI authenticates the user equipment and returns the identity indication information of the user equipment. The first network device compares the identity indication information in the device parameter with the identity indication information returned by the HSS. If the identity is consistent, the user equipment is a backhaul node. If not, the user equipment is denied access.

In the second implementation manner, regardless of whether the user equipment is a backhaul node or a common device, the device parameter does not include the identity indication information, and the subscription information stored in the HSS includes the identity indication information. The first network device may obtain the subscription information corresponding to the IMSI from the HSS, and identify the identity of the user equipment according to the subscription information.

In a third implementation manner, a field may be set in the IMSI to indicate the identity of the user equipment, and the first network device may identify the identity of the user equipment according to the field in the IMSI. The identification is not limited to this embodiment.

If the user equipment to be attached is a common device, the bearer management process for the common device can be processed according to the prior art.

If the user equipment to be attached is the backhaul node, the first network device sends a create session request message to the second network device, where the create session request message carries the identifier of the IMSI, the default bearer, and the identifier of the at least two dedicated bearers. The second network device establishes a default 7-load and at least two dedicated bearers for the backhaul node corresponding to the IMSI according to the identifier of the default bearer and the identifier of the at least two dedicated 7-load. In practical applications, the number of dedicated bearers that can be established for the backhaul node has an upper limit, such as eight. Then, in the attaching process of the backhaul node, the default bearer and all the dedicated bearers may be established for the backhaul node, or the default bearer and the partial dedicated bearer may be established for the backhaul node, and the number of the dedicated bearers is at least two.

In the LTE communication system, the PDN GW can implement the second network device. Of course, in other communication systems, the second network device can be implemented by using a network element with similar functions. For example, the LTE communication system sends a session creation request message to the second network device. The MME may send a create session request message to the Serving GW, and the Serving GW sends the session request message to the PDN GW.

The second network device establishes a corresponding default bearer and a dedicated bearer for the backhaul node according to the identifier of the default bearer and the identifier of the at least two dedicated bearers. After the bearer between the backhaul node and the second network device is successfully established, when the normal device accesses the backhaul node, the backhaul node establishes a bearer with the common device. When the normal device sends the uplink data, the backhaul node can be based on the uplink data. The type or quality of service (QoS) maps the bearer between the backhaul node and the common device to the bearer between the backhaul node and the second network device to implement uplink data transmission. When the downlink data corresponding to the common device reaches the second network device, the second network device may also send the data to the backhaul node through the bearer between the backhaul node according to the type or QoS of the downlink data, and the backhaul node passes the downlink data again. A bearer with a normal device is sent to a normal device.

In an actual application, if the normal device and the backhaul node access the network at the same time, the first network device can preferentially perform the bearer establishment process of the backhaul node.

The backhaul network bearer management method provided in this embodiment, the first network device receives an attach request message carrying a device parameter, where the device parameter is used to identify the user equipment, the device parameter includes an international mobile subscriber identity, and the request is determined according to the device parameter. Whether the user device is back a process node, if yes, sending a create session request message to the second network device, where the create session request message carries an international mobile subscriber identity, an identifier of the default bearer, and an identifier of at least two dedicated bearers, so that the second network The device establishes a default bearer and at least two dedicated bearers for the backhaul node according to the identifier of the default bearer in the Create Session Request message and the identifier of the at least two dedicated bearers. When the backhaul node is connected to the network, the default bearer and at least two dedicated bearers are simultaneously established for the backhaul node. When the number of common devices accessed through the backhaul node is large, the repeated establishment is avoided. The increase in the preparation time for the service provided by the bearer to the ordinary device accessing the backhaul node also reduces the system signaling overhead.

In this embodiment, the device parameter further includes identity indication information used to indicate that the user equipment is a backhaul node;

Step A20: The first network device determines, according to the device parameter, whether the user equipment to be attached is a backhaul node, which may be:

2 is a flowchart of a second backhaul network bearer management method according to an embodiment of the present invention. As shown in FIG. 2, in the embodiment, the second network device establishes, as the backhaul node, an identifier of the default bearer and an identifier of the at least two dedicated bearers in the create session request message. After the default bearer and the at least two dedicated bearers, the method further includes:

Step A30: The first network device sends, to the second network device, a session deletion request that carries the identifier of the default bearer, so that the second network device is configured according to the default bearer in the session deletion request. The identifier deletes the default bearer and all dedicated bearers corresponding to the default bearer.

Specifically, when the backhaul node leaves the network or closes the backhaul function, the backhaul node can actively initiate a leave request, or the first network device or the HSS initiates the leave process of the backhaul node. The first network device sends a session deletion request to the second network device, where the session deletion request carries an identifier corresponding to the default bearer of the backhaul node, and the second network device deletes the default bearer and all the dedicated bearers corresponding to the default bearer.

Taking the LTE communication system as an example, when the backhaul node actively initiates the leave request, the backhaul node sends a leave request message to the eNB, and the eNB sends a leave request message to the MME, and the MME sends the Leave message to the MME. The GW sends a session deletion request, and the Serving GW sends the session deletion request to the PDN GW, and the PDN GW deletes all bearers corresponding to the backhaul node.

All the bearers of the backhaul node are maintained during the whole life of the backhaul node accessing the network. When the backhaul node leaves or closes the backhaul function, all the bearers are deleted, and the prior art can be avoided as long as there is no data transmission in the dedicated bearer. That is, when the user equipment that is accessed by the backhaul node is re-occurred, the dedicated bearer needs to be re-established to increase the service preparation time, and the system signaling overhead is further reduced.

FIG. 3 is a flowchart of a third backhaul network bearer management method according to an embodiment of the present invention. As shown in FIG. 3, the backhaul network bearer management method provided in this embodiment may be specifically applied to a bearer management process of a communication system configured with a backhaul network, and the method provided in this embodiment may be applied to a backhaul network bearer applied to the first network device. The management method is implemented in coordination, and the specific implementation process will not be described here. The communication system may be an LTE (Long Term Evolution) communication system. The LTE communication system may specifically include a Packet Data Network Gateway (PDN GW). The Serving Gateway (Serving Gateway), the Mobility Management Entity (MME), the evolved Node B (eNB), and the backhaul node. In the communication system, a common user equipment (hereinafter referred to as a normal device) can access the core network through the access network and the backhaul network, that is, the ordinary device accesses the core network via the backhaul node and the eNB. The backhaul network and the access network can use the same or different frequencies and formats. For example, the backhaul network uses LTE TDD (time-division duplex) as the backhaul transmission, and the access network can use GSM (Global System of Mobile communication, Global mobile communication system;), UMTS, Wi-Fi (Wireless Fidelity), and one or more of LTE FDD (Frequency Division Duplexing) / TDD, the backhaul network is transparent to the access network Transfer user data. Ordinary devices can also access the core network directly through the eNB.

The method for providing backhaul network bearer management in this embodiment specifically includes:

Step B10: The second network device receives a create session request message sent by the first network device, where the create session request message carries an international mobile subscriber identity of the backhaul node, an identifier of the default bearer, and at least two dedicated bearers. Identification

Step B20: The second network device establishes the default for the backhaul node according to the identifier of the default bearer in the create session request message and the identifier of the at least two dedicated bearers. The bearer and the at least two dedicated bearers are recognized.

In the backhaul network bearer management method provided by the embodiment, the second network device receives the create session request message sent by the first network device, where the create session request message carries the international mobile subscriber identity, the default bearer identifier, and at least two The identifier of the dedicated bearer establishes a default bearer and at least two dedicated bearers for the backhaul node according to the identifier of the default bearer in the Create Session Request message and the identifier of the at least two dedicated bearers. Through the distinction between the identity of the backhaul node and the common device, when the backhaul node accesses the network, the default load and at least two dedicated 7-loads are simultaneously established for the backhaul node, and when the number of common devices accessed through the backhaul node is large, the repetition is avoided. The increase in the preparation time for providing services for the ordinary devices accessing the backhaul node caused by the bearer also reduces the system signaling overhead.

In this embodiment, the create session request message further carries the service quality parameter corresponding to the at least two dedicated bearers respectively;

Step B20, the second network device establishes the default load and the at least two for the backhaul node according to the identifier of the default bearer and the identifier of the at least two dedicated bearers in the create session request message. Dedicated 7-load, specifically:

Adding, by the second network device, the identifier of the default bearer in the create session request message, the identifier of the at least two dedicated bearers, and the monthly good quality parameter corresponding to the at least two dedicated payloads respectively Transmitting the bearer mapping table to the backhaul node by using the first network device, so that the backhaul node respectively corresponds to the at least two dedicated bearers in the bearer mapping table. The quality of service parameters are mapped by bearers.

Specifically, the QoS parameters corresponding to the at least two dedicated bearers may be carried in the session creation request message in the form of an EPS (Evolved Packet System) Bearer QoS list. The QoS parameter of the at least two dedicated bearers that needs to be established in this manner is recorded in the EPS Bearer QoS list, and the second network device adds the QoS parameters of the at least two dedicated bearers to the bearer mapping table, and passes the bearer mapping table through the first The network device sends to the backhaul node. In the actual application process, the mapping in the bearer mapping table may also be a mapping relationship between a QoS Class Identifier (QCI) and a dedicated bearer flag. When a normal device accesses the backhaul node, the backhaul node establishes a bearer with the common device. When the normal device sends the uplink data, the backhaul node can map the bearer between the backhaul node and the common device to the backhaul node according to the QoS of the uplink data. The bearer between the second network devices is used to implement uplink data transmission. For example, if the uplink data is an IP packet, it can be based on the IP packet. The DSCP (Differential Service Code Point) in the header implements the mapping of the bearer. The downlink data can also be implemented in a similar manner, and will not be described here.

In practical applications, other bearer mapping rules may also be used to implement bearer mapping. Taking the LTE communication system as an example, if the upper limit of the number of dedicated bearers that can be established for the backhaul node is eight, the default bearer and eight dedicated bearers are established once for the backhaul node when the backhaul node is attached. When the backhaul node communicates with the OMN (Operation Administration and Maintenance) device via the PDN GW co-located with the eNB, the control plane data stream and the OAM high priority data stream occupy a dedicated bearer, OAM low priority data stream A dedicated bearer is occupied, and the remaining 6 dedicated bearers are used by the user service data stream. When the backhaul node communicates with the OAM device located outside the eNB, the data stream with high OAM priority and the data stream with low priority occupy one dedicated bearer respectively; the user control plane data stream occupies one dedicated bearer; the remaining 5 dedicated The bearer is used by the user service data stream.

FIG. 4 is a signaling diagram of a backhaul node attach process according to an embodiment of the present invention. Referring to FIG. 4, an LTE communication system is taken as an example to describe a detailed process of triggering bearer establishment in a backhaul node attach procedure.

Step 1: The backhaul node sends an attach request message (Attach Request) to the eNB, where the attach request message carries the device parameter of the backhaul node, and the device parameter includes the IMSI and the identity indication information;

Step 2. The eNB sends an attach request message to the MME.

Step 3: The MME queries the HSS according to the device parameter in the attach request message, and obtains the identity indication information of the backhaul node to perform authentication on the backhaul node.

Step 4: The MME feeds back the authentication result to the backhaul node.

Step 5: The MME sends a Create Session Request message to the Serving GW. The session establishment request carries a default bearer identifier and at least two dedicated bearer identifiers. The Serving GW will default to 7 logos and at least two dedicated 7-carriers. The identifier is added to the local EPS bearer mapping table;

Step 6: The Serving GW sends a create session request message to the PDN GW, and the PDN GW adds the default bearer identifier and at least two dedicated bearer identifiers to the local EPS bearer mapping table.

Step 7: The PDN GW sends a Create Session Response message to the Serving GW, where the Create Session Response message carries the bearer mapping table. Step 8, the Serving GW sends a create session response message to the MME;

Step 9: The MME sends an initial response setup request/attachment message to the eNB, and establishes an EPC (Evolved Packet Core) bearer for the backhaul node by the port eNB, and the initial context is established. The request message/accept attachment message carries a bearer mapping table;

Step 10: The eNB sends an RRC (Radio Resource Control) connection reconfiguration message (RRC Connection Reconfiguration) to the backhaul node, where the RRC connection reconfiguration message carries a bearer mapping table.

Step 11. The backhaul node sends an RRC connection reconfiguration complete message to the eNB.

Step 12: The eNB sends an initial context setup response message (Initial Context Setup Response) to the MME.

Step 13. The backhaul node sends a direct transfer message to the eNB (Direct Transfer);

Step 14. The eNB sends an Attach Complete message to the MME.

In the foregoing implementation process, the session creation request message may carry multiple parameters, for example,

IMSI, MME TEID (Tunnel Endpoint Identifier), control plane, PDN GW address, APN, EPS Bearer QoS list, APN-AMBR (Aggregate Maximum Bit Rate, Total maximum bit rate), EPS Bearer Identity, Protocol Configuration Options, Charging Characteristics, and Protocol Type over S5/S8 (S5/S8 interface protocol type) The QoS parameters included in the EPS Bearer QoS list may include QCI, ARP (Allocation and Retention Priority), GBR ( Guaranteed Bit Rate), and MBR (Maximum Bit Rate). The ARP parameter includes the following information: the priority level (scalar), the pre-emption capability (flag), and the pre-emption vulnerability (flag). The ARP is mainly used for determining Whether a bearer's setup/modification request is accepted, and whether the bearer is rejected when the resource is restricted. The first-level guarantees that the high-priority bearer requests are preferentially satisfied. When the dominant capability defines the resource-constrained, whether a high-priority bearer has the ability to delete a low-priority bearer to meet the required resources, is occupied. The attribute defines the attribute of whether a bearer can be deleted by a high-priority bearer. In order to perform bearer management on the backhaul node and the common user, the backhaul node bearer can be set to be more common than the normal user. The ARP priority is set to a high priority, and the dominant capability in the ARP is set to "Yes". The dominant attribute in the ARP is set to "Yes". "no". When the PDN GW adds a corresponding new bearer entry in the local EPS bearer mapping table, it also generates Charging IDs, which can be used to implement the service level differentiated charging mode, and feedback to Serving by creating a session response message. GW.

A dedicated bearer established before the service is initiated can be configured with a larger GBR ( Guaranteed Bit Rate) / MBR (Maximum Bit Rate). GBR indicates that a bearer can guarantee the bandwidth provided. The maximum bandwidth that the bearer can provide. If the amount of data exceeds the set value after the service is initiated, the data is randomly discarded or the bearer modification is initiated.

FIG. 5 is a flowchart of a fourth backhaul network bearer management method according to an embodiment of the present invention. As shown in FIG. 5, in this embodiment, in step B20, the second network device is configured to use the identifier of the default bearer and the identifier of the at least two dedicated bearers in the create session request message as the backhaul. After the node establishes the default bearer and the at least two dedicated bearers, the method may further include:

Step B30: The second network device receives a data request message carrying the international mobile subscriber identity, and determines whether the number of dedicated bearers established by the backhaul node corresponding to the international mobile subscriber identity reaches an upper limit. If yes, the identifier of the dedicated bearer to be established is determined, and the dedicated bearer is established for the backhaul node according to the identifier of the dedicated bearer to be established, where the number of the dedicated bearers to be established is greater than 1 and less than or equal to the Upper limit.

Specifically, in the attaching process of the backhaul node, the second network device may establish a part of the dedicated bearer for the backhaul node, and then trigger the establishment of the remaining dedicated bearer by sending a data request message when the user equipment of the ordinary device accessing the backhaul node generates the user service. The remaining dedicated bearers can all be established at one time, and can be established separately under the trigger of multiple data request messages.

FIG. 6 is a schematic diagram of a dedicated bearer setup signaling according to an embodiment of the present invention. Referring to FIG. 6, taking the LTE communication system as an example, the specific process of the PDN GW establishing a dedicated bearer for the backhaul node after the backhaul node is attached is described in detail.

Step 1: The PDN GW sends a Create Bearer Request message to the Serving GW, where the Create Bearer Request message carries the identifier of the dedicated bearer to be established.

Step 2, the Serving GW sends a create bearer request message to the MME;

Step 3: The MME sends a bearer setup request message/session management request message to the eNB (Bearer) Setup Request/ Session Management Request );

Step 4: The eNB sends an RRC connection reconfiguration message to the backhaul node.

Step 5: The backhaul node sends an RRC connection reconfiguration complete message to the eNB.

Step 6, the eNB sends a Bearer Setup Response message to the MME; Step 7. The backhaul node sends a Direct Transfer message to the eNB.

Step 8. The eNB sends a session management response message (Session Management Response) to the MME.

Step 9. The MME sends a create bearer response message to the Serving GW (Create Bearer)

Response );

Step 10: The Serving GW sends a Create Bearer Response message to the PDN GW.

In the foregoing implementation process, the PDN GW sends a Create Bearer Request message to the Serving GW, which may carry multiple parameters, such as an IMSI, a PTI (Process Transaction Id, and a process transaction identifier, which is only used by the UE to bear the resource modification request activation process). EPS Bearer QoS list, TFT (Traffic Flow Template), S5/S8 TEID, Charging Id, LBI (Linked EPS Bearer Identity), and Protocol Configuration Options.

In this embodiment, in step B20, the second network device establishes the default bearer for the backhaul node according to the identifier of the default bearer and the identifier of the at least two dedicated bearers in the create session request message. And after the at least two dedicated bearers, the method may further include:

Step B40: The second network device receives a session deletion request that is sent by the first network device and carries the identifier of the default bearer, and deletes the default bearer according to the identifier of the default bearer in the session deletion request. And all dedicated bearers corresponding to the default bearers.

Taking the LTE communication system as an example, when the backhaul node actively initiates the leaving request, the backhaul node The eNB sends a leave request message, the eNB sends a leave request message to the MME, and the MME sends a session delete request to the Serving GW. The Serving GW sends the session delete request to the PDN GW, and the PDN GW deletes all bearers corresponding to the backhaul node. FIG. 7 is a schematic diagram of bearer deletion signaling according to an embodiment of the present invention. Referring to FIG. 7, the deletion process carried by the backhaul node when leaving or closing the backhaul function will be described in detail.

Step 1. The backhaul node sends a Leave Request message (Dttach Request) to the eNB;

Step 2: The eNB sends a Leave Request message to the MME.

Step 3: The MME sends a Delete Session Request message to the Serving GW.

Step 4: The Serving GW sends a Delete Bearer Request message to the PDN GW, where the Delete Bearer Request message carries the identifier of the default bearer corresponding to the backhaul node.

Step 5: The PDN GW sends a Delete Bearer Response message to the Serving GW.

Step 6, the Serving GW sends a Delete Session Response message to the MME (Delete Session Response);

Step 7. The MME sends a leave response message (Dttach Response) to the eNB.

Step 8. The eNB sends a Leave Response message (Dttach Response) to the backhaul node.

In this embodiment, B20, the second network device establishes the default bearer and the backhaul node according to the identifier of the default bearer in the create session request message and the identifier of the at least two dedicated bearers. After the at least two dedicated bearers, the method may further include: Step B50: The second network device monitors each dedicated bearer of the at least two dedicated bearers, if the preset time range is If there is no service data transmission on the dedicated bearer, the dedicated bearer is deleted.

Specifically, after the second network device establishes a dedicated bearer for the backhaul node, a timer corresponding to the dedicated bearer may be set. When the data service on the dedicated bearer stops transmitting, the timer is started, and a clock is set. The establishment of the dedicated bearer is maintained before the clock expires. When the clock expires, there is still no service data transmission on the dedicated bearer, and the dedicated bearer is deleted.

FIG. 8 is a schematic diagram of another bearer deletion signaling according to an embodiment of the present invention. With reference to FIG. 8, the LTE communication system is taken as an example to describe a detailed process of deleting the dedicated payload when there is no service data transmission on the dedicated bearer in the preset time range. Step 1: The PDN GW sends a Delete Bearer Request message to the Serving GW, where the Delete Bearer Request message carries the identifier of the dedicated bearer.

Step 2: The Serving GW sends a delete bearer request message to the MME.

Step 3: The MME sends a Deactivate Bearer Request message to the eNB.

Step 6. The eNB sends a deactivation bearer response message to the MME (Deactivate Bearer)

Response );

Step 7. The backhaul node sends a direct transfer message to the eNB (Direct Transfer);

Step 8. The eNB sends a Deactivate Bearer Response Accept message to the MME.

Step 9. The MME sends a delete bearer response message to the Serving GW (Delete Bearer)

Response );

Step 10: The Serving GW sends a delete bearer response message to the PDN GW.

FIG. 9 is a flowchart of a fifth backhaul network bearer management method according to an embodiment of the present invention. As shown in FIG. 9 , the backhaul network bearer management method provided in this embodiment may be specifically applied to a bearer management process of a communication system configured with a backhaul network, where the communication system may be an LTE (Long Term Evolution) communication system or The UMTS communication system is exemplified by an LTE communication system. The LTE communication system may specifically include a Packet Data Network Gateway (PDN GW), a Serving Gateway (Serving Gateway), and a mobility management entity. Mobility Management Entity, called MME, base station (evolved Node B, eNB) and backhaul nodes. In a communication system, a common user equipment (hereinafter referred to as a normal device) can access a core network through an access network and a backhaul network, that is, a common device accesses a core network via a backhaul node and an eNB. The backhaul network and the access network can use the same or different frequencies and formats. For example, the backhaul network uses LTE TDD (time-division duplex), time division duplex M乍 is the backhaul transmission, and the access network can use GSM (Global System of Mobile communication). , Global System for Mobile Communications, UMTS, Wi-Fi (Wireless Fidelity) and LTE FDD (Frequency Division Duplexing, Full Duplex) / TDD One or several standards, the backhaul network transparently transmits user data to the access network. Ordinary devices can also access the core network directly through the eNB.

Step C10: The second network device receives the create session request message sent by the first network device, where the create session request message carries an identifier of the international mobile subscriber identity, the identity indication information, and the default bearer used to identify the user equipment. The identity indication information is used to indicate that the user equipment is a backhaul node;

Specifically, when the user equipment initiates the attaching process, the user equipment may be a common device or a backhaul node, and the user equipment sends an attach request message to the network device on the network side, where the attach request message carries the device parameter, and the device parameter is specific. It can be used to identify user equipment, and equipment parameters include IMSI. If the user equipment that initiates the attach procedure is a backhaul node, the device parameter may further include identity indication information, where the identity indication information may indicate that the user equipment is a backhaul node.

The first network device can determine whether the user equipment to be attached is a backhaul node according to the device parameter. For the specific implementation manner, reference may be made to the implementation manner in the foregoing embodiment, and details are not described herein again. When the user equipment to be attached is the backhaul node, the first network device sends a create session request message to the second network device, where the session request message carries the identifier of the IMSI, the identity indication information, and the default bearer. The second network device can learn that the user equipment is a backhaul node according to the identity indication information in the create session request message, and execute a corresponding processing procedure.

Step C20: The second network device establishes the default bearer for the backhaul node according to the identifier of the default bearer in the create session request message.

Step C30: The second network device determines, when the downlink data of the common device accessed by the backhaul node arrives or receives the data request message initiated by the common device, determining at least two dedicated channels corresponding to the backhaul node. The identifier of the bearer, the at least two dedicated bearers are established for the backhaul node according to the identifiers of the at least two dedicated bearers.

Specifically, when the backhaul node accesses the network, only the default bearer is established for the backhaul node. After the backhaul node is attached to the network, when the user equipment of the normal device accessing the backhaul node generates the user service, the second network device can establish a part of the dedicated bearer or all the dedicated bearers for the backhaul node. When a part of the dedicated bearer is established for the backhaul node at a time, the number of dedicated bearers established is at least two, and the remaining dedicated bearers may be respectively established under the trigger of one or more data request messages in the future. Data request message can be carried There is a backhaul node IMSI such that the second network device can determine a backhaul node based on the IMSI and establish at least two dedicated bearers for the backhaul node. After the normal device accesses the network through the backhaul node, the second network device allocates an IP address to the common device. When the downlink data corresponding to the normal device arrives, the process of establishing the dedicated bearer is also triggered. Then, the second network device determines, according to the IP address of the common device carried in the downlink data, the backhaul node accessed by the common device, and establishes at least two dedicated bearers for the backhaul node.

When the communication system is an LTE communication system, a specific process for the PDN GW to establish a dedicated bearer for the backhaul node after the backhaul node is attached may be referred to the description of the embodiment shown in FIG. 6, and details are not described herein.

In the backhaul network bearer management method provided by the embodiment, the second network device receives the create session request message sent by the first network device, where the create session request message carries the international mobile subscriber identity, the identity indication information, and the default of the user equipment. The bearer identifier is used to indicate that the user equipment is a backhaul node, and the default bearer is established for the backhaul node according to the identifier of the default bearer in the create session request message, and the downlink data of the ordinary device accessed through the backhaul node is received or received. When the data request message is initiated by the normal device, the identifiers of the at least two dedicated bearers corresponding to the backhaul node are determined, and at least two dedicated bearers are established for the backhaul node according to the identifiers of the at least two dedicated bearers. By the identity of the backhaul node and the common device, when the backhaul node accesses the network, a default bearer is established for the backhaul node. When the user service occurs, at least two dedicated bearers are established for the backhaul node at a time, when accessed through the backhaul node. When the number of common devices is large, the preparation time for providing services for the ordinary devices accessing the backhaul nodes caused by the repeated establishment of the bearers is avoided, and the system signaling overhead is also reduced.

FIG. 10 is a flowchart of a sixth backhaul network bearer management method according to an embodiment of the present invention. As shown in FIG. 10, in this embodiment, after the second network device establishes the at least two dedicated bearers for the backhaul node according to the identifiers of the at least two dedicated bearers, the method further Can include:

Step C40: The second network device receives a session deletion request that is sent by the first network device and carries the identifier of the default bearer, and deletes the default bearer according to the identifier of the default bearer in the session deletion request. And all dedicated bearers corresponding to the default bearers.

Specifically, when the backhaul node leaves the network or closes the backhaul function, the backhaul node may initiate a leave request actively, or the departure process of the backhaul node is initiated by the first network device or the HSS. The first network device sends a session deletion request to the second network device, where the session deletion request is carried Corresponding to the identifier of the default bearer of the backhaul node, the second network device deletes the default bearer and the default bearer corresponding to all the dedicated bearers.

Taking the LTE communication system as an example, when the backhaul node actively initiates the leave request, the backhaul node sends a leave request message to the eNB, and the eNB sends a leave request message to the MME, and the MME sends a session delete request to the Serving GW, and the Serving GW deletes the session request. Sent to the PDN GW, the PDN GW deletes all bearers corresponding to the backhaul node. For a specific implementation process, reference may be made to the description of the embodiment shown in FIG. 7, and details are not described herein again.

In this embodiment, after the second network device establishes the at least two dedicated bearers for the backhaul node according to the identifiers of the at least two dedicated bearers, the method may further include:

Step C50: The second network device monitors each dedicated bearer of the at least two dedicated bearers, and if there is no service data transmission on the dedicated bearer within a preset time range, deleting the dedicated bearer.

Specifically, after the second network device establishes a dedicated bearer for the backhaul node, a timer corresponding to the dedicated bearer may be set. When the data service on the dedicated bearer stops transmitting, the timer is started, and a clock is set. The establishment of the dedicated bearer is maintained before the clock expires. When the clock expires, there is still no service data transmission on the dedicated bearer, and the dedicated bearer is deleted. For a specific implementation process, reference may be made to the description of the embodiment shown in FIG. 8, and details are not described herein again.

In this embodiment, in step C30, the second network device establishes the at least two dedicated bearers for the backhaul node according to the identifiers of the at least two dedicated bearers, where the second network device obtains: And the QoS parameters corresponding to the at least two dedicated bearers and the at least two dedicated bearers respectively are added to the bearer mapping table, and the bearer mapping is performed. The table is sent to the backhaul node by the first network device, so that the backhaul node performs bearer mapping according to the service quality parameter corresponding to the at least two dedicated bearers in the bearer mapping table.

In the actual application process, the bearer establishment process of the backhaul node can also be implemented in the following manner: When the backhaul node accesses the network, the create session request message sent by the first network device to the second network device carries the identifier of the default bearer and The identity indication information, when the second network device identifies that the user equipment that is requested to be attached is a backhaul node, first establishes a default bearer for the backhaul node, determines identifiers and parameters of at least two dedicated bearers, and establishes at least two dedicated for the backhaul node. Hosted. That is, the second network device sets the default bearer and the dedicated bearer at different times for the backhaul node, However, the establishment of a dedicated bearer is not triggered by the user's service.

FIG. 11 is a schematic structural diagram of a first type of first network device according to an embodiment of the present invention. As shown in FIG. 11, the first network device 81 provided in this embodiment may implement various steps of the backhaul network bearer management method applied to the first network device 81 according to any embodiment of the present invention, and the specific implementation process is not implemented here. Let me repeat.

The first network device 81 provided by this embodiment includes a receiving unit 11 and a first requesting unit 12, where the receiving unit 11 is configured to receive an attach request message carrying a device parameter, where the device parameter is used to identify the user equipment. The device parameter includes an international mobile subscriber identity. The first requesting unit 12 is connected to the receiving unit 11 and configured to determine, according to the device parameter, whether the user equipment that is requested to be attached is a backhaul node, and if yes, send a create session request message to the second network device, where The create session request message carries the international mobile subscriber identity, the default identifier, and the at least two dedicated identifiers, so that the second network device performs the default bearer according to the create session request message. The identifier and the identifier of the at least two dedicated bearers establish the default bearer and the at least two dedicated bearers for the backhaul node.

In the first network device 81, the receiving unit 11 receives the attach request message carrying the device parameter, where the device parameter is used to identify the user device, the device parameter includes an international mobile subscriber identity, and the first request unit 12 is configured according to the device. The parameter determines whether the user equipment to be attached is a backhaul node, and if yes, sends a create session request message to the second network device, where the create session request message carries an international mobile subscriber identity, an identifier of the default bearer, and at least two dedicated The identifier of the bearer, so that the second network device establishes a default bearer and at least two dedicated bearers for the backhaul node according to the identifier of the default bearer in the create session request message and the identifier of the at least two dedicated bearers. When the backhaul node is connected to the network, the default bearer and at least two dedicated bearers are simultaneously established for the backhaul node. When the number of common devices accessed through the backhaul node is large, the repeated establishment is avoided. The increase in the preparation time for the service provided by the bearer to the ordinary device accessing the backhaul node also reduces the system signaling overhead.

FIG. 12 is a schematic structural diagram of a second network device according to an embodiment of the present invention. As shown in FIG. 12, in the embodiment, the device parameter further includes identity indication information that is used to indicate that the user equipment is a backhaul node. Correspondingly, the first requesting unit 12 may be specifically configured to: The device parameter includes the identity indication information, and the subscription information of the user equipment is obtained according to the international mobile subscriber identity, and the identity indication information is used according to the subscription information. The verification is performed, and if the verification is successful, the user equipment is a backhaul node.

In this embodiment, the first network device 81 may further include a second requesting unit 13 , where the second requesting unit 13 is configured to send, to the second network device, a session deletion that carries the identifier of the default bearer. And the requesting, by the second network device, deleting the default bearer and all dedicated bearers corresponding to the default bearer according to the identifier of the default bearer in the session deletion request.

FIG. 13 is a schematic structural diagram of a first type of second network device according to an embodiment of the present invention. As shown in FIG. 13, the second network device 82 provided in this embodiment may implement various steps of the backhaul network bearer management method provided in the embodiment shown in FIG. 3, and the specific implementation process is not described herein.

The second network device 82 provided in this embodiment specifically includes a receiving unit 21 and a first processing unit 22. The receiving unit 21 is configured to receive a create session request message sent by the first network device, where the create session request message carries an international mobile subscriber identity of the backhaul node, an identifier of the default bearer, and at least two dedicated bearers. Logo. The first processing unit 22 is connected to the receiving unit 21, and configured to establish, according to the identifier of the default bearer in the create session request message and the identifier of the at least two dedicated bearers, the backhaul node. The default bearer and the at least two dedicated bearers.

The second network device 82 is provided by the embodiment, and the receiving unit 21 receives the create session request message sent by the first network device, where the create session request message carries the international mobile subscriber identity, the identifier of the default bearer, and at least two dedicated The identifier of the bearer, the first processing unit 22 establishes a default bearer and at least two dedicated bearers for the backhaul node according to the identifier of the default bearer in the create session request message and the identifier of the at least two dedicated bearers. Through the distinction between the identity of the backhaul node and the common device, when the backhaul node accesses the network, the default load and at least two dedicated bearers are simultaneously established for the backhaul node, and when the number of common devices accessed through the backhaul node is large, the repeated establishment is avoided. The increase in the preparation time for the service provided by the bearer to the ordinary device accessing the backhaul node also reduces the system signaling overhead.

FIG. 14 is a schematic structural diagram of a second second network device according to an embodiment of the present invention. As shown in FIG. 14, in the embodiment, the second network device 82 may further include a second processing unit 23, where the second processing unit 23 is configured to receive a data request that carries the international mobile subscriber identity. a message, determining whether the number of dedicated bearers established by the backhaul node corresponding to the international mobile subscriber identity reaches an upper limit, and if not, determining an identifier of the dedicated bearer to be established, according to the identifier of the dedicated bearer to be established. Establishing a dedicated bearer for the backhaul node, where the to-be-built The number of dedicated dedicated bearers is greater than one and less than or equal to the upper limit.

In this embodiment, the second network device 82 may further include a first bearer deleting unit 24, where the first bearer deleting unit 24 is configured to receive the identifier that is sent by the first network device and that carries the default bearer. The session deletion request deletes the default bearer and all dedicated bearers corresponding to the default bearer according to the identifier of the default bearer in the session deletion request.

In this embodiment, the second network device 82 may further include a second bearer deleting unit 25, where the second bearer deleting unit 25 is configured to monitor each dedicated bearer in the at least two dedicated bearers. If there is no service data transmission on the dedicated bearer within a preset time range, the dedicated bearer is deleted.

In this embodiment, the create session request message further carries the QoS parameter corresponding to the at least two dedicated bearers respectively. Correspondingly, the first processing unit 22 may be specifically configured to use the create session request message. The identifier of the default bearer, the identifier of the at least two dedicated bearers, and the QoS parameter corresponding to the at least two dedicated bearers are added to the bearer mapping table, and the bearer mapping table is passed through the first The network device sends the backhaul node to the backhaul node, so that the backhaul node performs bearer mapping according to the quality of service parameters corresponding to the at least two dedicated bearers in the bearer mapping table.

Figure 15 is a schematic structural diagram of a third type of second network device according to an embodiment of the present invention. As shown in FIG. 15, the second network device 82 provided in this embodiment may implement various steps of the backhaul network bearer management method provided in the embodiment shown in FIG. 9, and the specific implementation process is not described herein.

The second network device 82 provided in this embodiment specifically includes a receiving unit 31, a first processing unit 32, and a second processing unit 33. The receiving unit 31 is configured to receive a create session request message sent by the first network device, where the create session request message carries an identifier for identifying an international mobile subscriber identity, identity indication information, and default bearer of the user equipment, The identity indication information is used to indicate that the user equipment is a backhaul node. The first processing unit 32 is connected to the receiving unit 31, and is configured to establish the default bearer for the backhaul node according to the identifier of the default bearer in the create session request message. The second processing unit 33 is configured to determine, when the downlink data of the common device accessed by the backhaul node arrives or receives the data request message initiated by the common device, determining at least two dedicated channels corresponding to the backhaul node. The identifier of the bearer, the at least two dedicated bearers are established for the backhaul node according to the identifiers of the at least two dedicated bearers.

The second network device 82 is provided by the embodiment, and the receiving unit 31 receives the create session request message sent by the first network device, where the session request message carries the international device of the user equipment. The mobile subscriber identity, the identity indication information, and the identifier of the default bearer, the identity indication information is used to indicate that the user equipment is a backhaul node, and the first processing unit 32 establishes a default bearer for the backhaul node according to the identifier of the default bearer in the create session request message. The second processing unit 33 determines, when the downlink data of the ordinary device accessed by the backhaul node arrives or receives the data request message initiated by the normal device, the identifier of the at least two dedicated bearers corresponding to the backhaul node, according to the at least two dedicated bearers. The identifier establishes at least two dedicated bearers for the backhaul node. By the identity of the backhaul node and the common device, when the backhaul node accesses the network, a default bearer is established for the backhaul node. When the user service occurs, at least two dedicated bearers are established for the backhaul node at a time, when accessed through the backhaul node. When the number of common devices is large, the preparation time for providing services for the ordinary devices accessing the backhaul nodes caused by the repeated establishment of the bearers is avoided, and the system signaling overhead is also reduced.

FIG. 16 is a schematic structural diagram of a fourth type of second network device according to an embodiment of the present invention. As shown in FIG. 16, in the embodiment, the second network device 82 may further include a first bearer deleting unit 34, where the first bearer deleting unit 34 is configured to receive the carried by the first network device. The session deletion request of the identifier of the default bearer deletes the default bearer and all dedicated bearers corresponding to the default bearer according to the identifier of the default bearer in the session deletion request.

In this embodiment, the second network device 82 may further include a second bearer deleting unit 35, where the second bearer deleting unit 35 is configured to monitor each dedicated bearer in the at least two dedicated bearers. If there is no service data transmission on the dedicated bearer within a preset time range, the dedicated bearer is deleted.

In this embodiment, the second processing unit 33 may be configured to obtain the QoS parameters corresponding to the at least two dedicated bearers, and the identifiers of the at least two dedicated bearers and the at least two dedicated bearers. The corresponding QoS parameters are added to the bearer mapping table, and the bearer mapping table is sent to the backhaul node by using the first network device, so that the backhaul node is configured according to the at least one of the bearer mapping tables. The bearer mapping is performed on the quality of service parameters corresponding to the two dedicated bearers.

FIG. 17 is a schematic structural diagram of a third first network device according to an embodiment of the present invention. As shown in FIG. 17 , the first network device 91 provided in this embodiment may implement various steps of the backhaul network bearer management method as shown in FIG. 1 , and the specific implementation process is not described herein. The first network device 91 provided in this embodiment specifically includes a receiver 41, a processor 42, and a transmitter 43. The receiver 41 is configured to receive an attach request message carrying a device parameter, where the device parameter is used to identify a user equipment, and the device parameter includes an international mobile subscriber identity. The processor 42 And the receiver 41 is configured to determine, according to the device parameter, whether the user equipment that is requested to be attached is a backhaul node, and if yes, send, by the sender 43, a create session request message to the second network device, where The creating a session request message carries the identifier of the international mobile subscriber identity, the default bearer, and the identifier of the at least two dedicated bearers, so that the second network device is configured according to the default bearer in the create session request message. The identifier and the identifier of the at least two dedicated bearers establish the default bearer and the at least two dedicated bearers for the backhaul node.

FIG. 18 is a schematic structural diagram of a fifth type of second network device according to an embodiment of the present invention. As shown in FIG. 18, the second network device 92 provided in this embodiment may implement various steps of the backhaul network bearer management method as shown in FIG. 3, and the specific implementation process is not repeated herein. The second network device 92 provided in this embodiment specifically includes a receiver 51 and a processor 52. The receiver 51 is configured to receive a create session request message sent by the first network device, where the create session request message carries an international mobile subscriber identity of the backhaul node, an identifier of the default bearer, and at least two dedicated bearers. Logo. The processor 52 is connected to the receiver 51, and configured to establish, according to the identifier of the default bearer in the create session request message and the identifier of the at least two dedicated bearers, the backhaul node. The default bearer and the at least two dedicated bearers.

FIG. 19 is a schematic structural diagram of a sixth type of second network device according to an embodiment of the present invention. As shown in FIG. 19, the second network device provided in this embodiment may implement various steps of the backhaul network bearer management method as shown in FIG. 9, and the specific implementation process is not repeated herein. The second network device 93 provided in this embodiment specifically includes a receiver 61 and a processor 62. The receiver 61 is configured to receive a create session request message sent by the first network device, where the create session request message carries an identifier for identifying an international mobile subscriber identity, identity indication information, and default bearer of the user equipment. The identity indication information is used to indicate that the user equipment is a backhaul node. The processor 62 is connected to the receiver 61, and configured to establish the default bearer for the backhaul node according to the identifier of the default bearer in the create session request message. The receiver is further configured to receive downlink data of a common device accessed by the backhaul node, and a data request message initiated by the common device. The processor is further configured to determine, when the downlink data of the common device accessed by the backhaul node arrives or receives the data request message initiated by the common device, determine at least two dedicated bearers corresponding to the backhaul node. And identifying, establishing, according to the identifiers of the at least two dedicated bearers, the at least two dedicated bearers for the backhaul node.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to the program instructions, and the foregoing program may be stored in a computer. The readable storage medium, when executed, executes the steps including the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

It should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that: The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced; and the modifications or substitutions do not deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

Rights request

1. A backhaul network bearer management method, characterized by including:

The first network device receives an attach request message carrying device parameters, where the device parameters are used to identify the user equipment, and the device parameters include the International Mobile Subscriber Identity;

The first network device determines whether the user equipment requesting attachment is a backhaul node based on the device parameters, and if so, sends a create session request message to the second network device, wherein the create session request message carries the international The mobile user identification code, the identity of the default bearer and the identities of at least two dedicated bearers, so that the second network device can use the identity of the default bearer and the identities of the at least two dedicated bearers in the create session request message to Identifies establishing the default bearer and the at least two dedicated bearers for the backhaul node.

2. The backhaul network bearer management method according to claim 1, characterized in that: the device parameters further include identity indication information used to indicate that the user equipment is a backhaul node;

The first network device determines whether the user equipment requesting attachment is a backhaul node based on the device parameters, specifically:

If the first network device recognizes that the device parameters include the identity indication information, it obtains the subscription information of the user equipment according to the International Mobile Subscriber Identity code, and compares the identity indication information according to the subscription information. Verification is performed, and if the verification is successful, the user equipment is the backhaul node.

3. The backhaul network bearer management method according to claim 1 or 2, characterized in that, the second network device performs the following steps according to the identification of the default bearer and the at least two dedicated bearers in the create session request message. After establishing the default bearer and the at least two dedicated bearers for the backhaul node, the method further includes:

The first network device sends a session deletion request carrying the identifier of the default bearer to the second network device, so that the second network device deletes the session according to the identifier of the default bearer in the session deletion request. The default bearer and all dedicated bearers corresponding to the default bearer.

4. A backhaul network bearer management method, characterized by including:

The second network device receives a create session request message sent by the first network device, wherein the create session request message carries the International Mobile Subscriber Identity and default bearer of the backhaul node. logo and at least two dedicated logos;

The second network device establishes the default bearer and the at least two dedicated bearers for the backhaul node based on the identifier of the default bearer and the identifiers of the at least two dedicated bearers in the create session request message.

5. The backhaul network bearer management method according to claim 4, characterized in that, the second network device performs the following steps according to the identification of the default bearer and the identification of the at least two dedicated bearers in the create session request message. After establishing the default bearer and the at least two dedicated bearers for the backhaul node, the method further includes:

The second network device receives the data request message carrying the International Mobile Subscriber Identity code, and determines whether the number of dedicated bearers established for the backhaul node corresponding to the International Mobile Subscriber Identity code reaches the upper limit, and if not, then Determine the identity of the dedicated bearer to be established, and establish a dedicated bearer for the backhaul node according to the identity of the dedicated bearer to be established, wherein the number of the dedicated bearers to be established is greater than 1 and less than or equal to the upper limit value .

6. The backhaul network bearer management method according to claim 4 or 5, characterized in that, the second network device performs the following steps according to the identification of the default bearer and the at least two dedicated bearers in the create session request message. After establishing the default bearer and the at least two dedicated bearers for the backhaul node, the method further includes:

The second network device receives the session deletion request carrying the identifier of the default bearer sent by the first network device, and deletes the default bearer and the connection with the default bearer according to the identifier of the default bearer in the session deletion request. All dedicated bearers corresponding to the default bearers listed above.

7. The backhaul network bearer management method according to claim 4 or 5, characterized in that, the second network device performs the following steps according to the identification of the default bearer and the at least two dedicated bearers in the create session request message. After establishing the default bearer and the at least two dedicated bearers for the backhaul node, the method further includes:

The second network device monitors each of the at least two dedicated bearers, and deletes the dedicated bearer if there is no service data transmission on the dedicated bearer within a preset time range.

8. The backhaul network bearer management method according to claim 4, characterized in that: the session creation request message also carries quality of service parameters corresponding to the at least two dedicated bearers;

The second network device determines the default bearer according to the identifier of the default bearer in the create session request message. identifying the identities of the at least two dedicated bearers and establishing the default bearer and the at least two dedicated bearers for the backhaul node, specifically:

The second network device adds the identification of the default bearer, the identification of the at least two dedicated bearers and the monthly service quality parameters corresponding to the at least two dedicated bearers in the create session request message. into the bearer mapping table, and send the bearer mapping table to the backhaul node through the first network device, so that the backhaul node corresponds to the at least two dedicated bearers in the bearer mapping table. Quality of Service parameters for bearer mapping.

9. A first network device, characterized by including:

A receiving unit configured to receive an attach request message carrying device parameters, where the device parameters are used to identify the user equipment, and the device parameters include the International Mobile Subscriber Identity;

A first request unit, connected to the receiving unit, is used to determine whether the user equipment requesting attachment is a backhaul node according to the device parameters, and if so, send a create session request message to the second network device, wherein, the create session The request message carries the International Mobile Subscriber Identity, the identifier of the default bearer and the identifiers of at least two dedicated bearers, so that the second network device can perform the operation according to the identifier of the default bearer and the identifier of the default bearer in the create session request message. The identities of the at least two dedicated bearers establish the default bearer and the at least two dedicated bearers for the backhaul node.

10. The first network device according to claim 9, characterized in that: the device parameters further include identity indication information used to indicate that the user equipment is a backhaul node;

The first requesting unit is specifically configured to obtain the subscription information of the user equipment according to the International Mobile Subscriber Identity code if it is recognized that the device parameters include the identity indication information, and perform the verification of the user equipment according to the subscription information. The identity indication information is verified. If the verification is successful, the user equipment is a backhaul node.

11. The first network device according to claim 9 or 10, further comprising: a second request unit, configured to send a session deletion request carrying the identifier of the default bearer to the second network device. , so that the second network device deletes the default bearer and all dedicated bearers corresponding to the default bearer according to the identification of the default bearer in the session deletion request.

12. A second network device, characterized by: including:

The receiving unit is configured to receive a create session request message sent by the first network device, wherein the create session request message carries the International Mobile Subscriber Identity code of the backhaul node and the default bearer. logo and at least two dedicated 7-carat logos;

A first processing unit, connected to the receiving unit, configured to establish the default bearer and the ID of the at least two dedicated bearers for the backhaul node according to the identifier of the default bearer and the identifier of the at least two dedicated bearers in the create session request message. The at least two dedicated bearers.

13. The second network device according to claim 12, further comprising: a second processing unit, configured to receive a data request message carrying the international mobile subscriber identity code, and determine that the international mobile subscriber is the Whether the number of dedicated bearers established by the backhaul node corresponding to the identification code reaches the upper limit, if not, determine the identity of the dedicated bearer to be established, and establish a dedicated bearer for the backhaul node according to the identity of the dedicated bearer to be established, Wherein, the number of dedicated bearers to be established is greater than 1 and less than or equal to the upper limit.

14. The second network device according to claim 12 or 13, further comprising:

A first bearer deletion unit configured to receive a session deletion request carrying the identifier of the default bearer sent by the first network device, delete the default bearer according to the identifier of the default bearer in the session deletion request; All dedicated bearers corresponding to the default bearer.

15. The second network device according to claim 12 or 13, further comprising:

The second bearer deletion unit is configured to monitor each dedicated bearer among the at least two dedicated bearers, and delete the dedicated bearer if there is no service data transmission on the dedicated bearer within a preset time range.

16. The second network device according to claim 12, characterized in that: the session creation request message also carries quality of service parameters corresponding to the at least two dedicated bearers; the first processing unit is specifically configured to: Add the identification of the default bearer, the identification of the at least two dedicated bearers and the service quality parameters corresponding to the at least two dedicated bearers in the create session request message to the bearer mapping table, and add the bearers to the bearer mapping table. The mapping table is sent to the backhaul node through the first network device, so that the backhaul node performs bearer mapping according to the service quality parameters respectively corresponding to the at least two dedicated bearers in the bearer mapping table.

17. A backhaul network bearer management method, characterized by including:

The second network device receives the create session request message sent by the first network device, wherein the create session request message carries the International Mobile Subscriber Identity code used to identify the user equipment, identity indication information and the identity of the default bearer, and the identity Instruction information is used to instruct the user device to Prepare as a backhaul node;

The second network device establishes the default bearer for the backhaul node according to the identification of the default bearer in the create session request message;

The second network device determines the identifiers of at least two dedicated bearers corresponding to the backhaul node when the downlink data of the common device accessed through the backhaul node arrives or receives a data request message initiated by the common device. , establishing the at least two dedicated bearers for the backhaul node according to the identifiers of the at least two dedicated bearers.

18. The backhaul network bearer management method according to claim 17, wherein after the second network device establishes the at least two dedicated bearers for the backhaul node according to the identifiers of the at least two dedicated bearers, The method also includes:

19. The backhaul network bearer management method according to claim 17, characterized in that, after the second network device establishes the at least two dedicated bearers for the backhaul node according to the identifiers of the at least two dedicated bearers, The method also includes:

20. The backhaul network bearer management method according to any one of claims 17 to 19, characterized in that, the second network device establishes the at least two dedicated bearers for the backhaul node according to the identifiers of the at least two dedicated bearers. Dedicated bearer, specifically:

The second network device obtains the service quality parameters corresponding to the at least two dedicated bearers, and adds the identifiers of the at least two dedicated bearers and the service quality parameters corresponding to the at least two dedicated bearers to the bearer mapping table. , the bearer mapping table is sent to the backhaul node through the first network device, so that the backhaul node performs operation according to the service quality parameters respectively corresponding to the at least two dedicated bearers in the bearer mapping table. Bearer mapping.

21. A second network device, characterized by: including:

The receiving unit is configured to receive a create session request message sent by the first network device, wherein the create session request message carries the International Mobile Subscriber Identity code used to identify the user equipment, identity indication information and a default bearer identifier, Identity indication information is used to indicate user settings Prepare as a backhaul node;

A first processing unit, connected to the receiving unit, configured to establish the default bearer for the backhaul node according to the identification of the default bearer in the create session request message;

A second processing unit, configured to determine whether the downlink data of a common device accessed through the backhaul node arrives or when a data request message initiated by the common device is received, corresponding to at least two dedicated bearers of the backhaul node. Identification, establishing the at least two dedicated bearers for the backhaul node according to the identifiers of the at least two dedicated bearers.

22. The second network device according to claim 21, further comprising: a first bearer deletion unit, configured to receive a session deletion request sent by the first network device and carrying the identifier of the default bearer. , Delete the default bearer and all dedicated bearers corresponding to the default bearer according to the identification of the default bearer in the session deletion request.

23. The second network device according to claim 21, further comprising: a second bearer deletion unit, configured to monitor each of the at least two dedicated bearers. If there is no service data transmission on the dedicated bearer within the time range, the dedicated bearer is deleted.

24. The second network device according to any one of claims 21 to 23, characterized in that: the second processing unit is specifically configured to obtain the service quality parameters corresponding to the at least two dedicated bearers, and convert the at least two dedicated bearers to The identifiers of the two dedicated bearers and the service quality parameters corresponding to the at least two dedicated bearers are added to the bearer mapping table, and the bearer mapping table is sent to the backhaul node through the first network device, so that the The backhaul node performs bearer mapping according to the service quality parameters respectively corresponding to the at least two dedicated bearers in the bearer mapping table.