WO2014071881A1 - Procédé et dispositif de gestion du support d'un réseau de raccordement - Google Patents

Procédé et dispositif de gestion du support d'un réseau de raccordement Download PDF

Info

Publication number
WO2014071881A1
WO2014071881A1 PCT/CN2013/086856 CN2013086856W WO2014071881A1 WO 2014071881 A1 WO2014071881 A1 WO 2014071881A1 CN 2013086856 W CN2013086856 W CN 2013086856W WO 2014071881 A1 WO2014071881 A1 WO 2014071881A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
network device
dedicated
backhaul node
dedicated bearers
Prior art date
Application number
PCT/CN2013/086856
Other languages
English (en)
Chinese (zh)
Inventor
任亚珍
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2014071881A1 publication Critical patent/WO2014071881A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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:
  • 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.
  • 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 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;
  • 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.
  • the second network device 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.
  • 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.
  • 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.
  • 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:
  • 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 device parameter further includes identity indication information used to indicate that the user equipment is a 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.
  • 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.
  • 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 are 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 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.
  • 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.
  • the second network device further includes:
  • 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 creating a session request message further carries a service quality parameter corresponding to the at least two dedicated bearers respectively;
  • 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
  • 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.
  • 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;
  • the backhaul node establishes 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.
  • 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.
  • 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:
  • 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.
  • 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.
  • the second network device further includes:
  • 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 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.
  • 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.
  • 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.
  • 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
  • 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 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
  • FIG. 1 is a flowchart of a first backhaul network bearer management method according to an embodiment of the present invention.
  • 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.
  • Packet Packet
  • Data Network Gateway called PDN GW
  • Serving Gateway Serving Gateway
  • MME Mobility Management Entity
  • base station evolved Node B
  • backhaul nodes evolved Node B
  • 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.
  • 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).
  • the backhaul network is the access network User data is transmitted.
  • Ordinary devices can also access the core network directly through the eNB.
  • 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.
  • IMSI International Mobile Subscriber Identification Number
  • the MME can implement the first network device, of course, in other communications.
  • the first network device can be implemented by using a network element with similar functions.
  • 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.
  • 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:
  • 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).
  • HSS Home Subscriber Server
  • 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.
  • the device parameter does not include the identity indication information
  • 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.
  • 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.
  • the bearer management process for the common device can be processed according to the prior art.
  • 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.
  • the number of dedicated bearers that can be established for the backhaul node has an upper limit, such as eight.
  • 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.
  • the PDN GW can implement the second network device.
  • the second network device can be implemented by using a network element with similar functions.
  • 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.
  • the backhaul node 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.
  • 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.
  • QoS quality of service
  • 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.
  • the first network device can preferentially perform the bearer establishment process of the backhaul node.
  • 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.
  • 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.
  • the backhaul node is connected to the network, the default bearer and at least two dedicated bearers are simultaneously established for the backhaul node.
  • 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.
  • 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:
  • 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.
  • FIG. 2 is a flowchart of a second backhaul network bearer management method according to an embodiment of the present invention.
  • 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.
  • 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.
  • the backhaul node 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.
  • the backhaul node 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.
  • 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.
  • 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).
  • PDN GW Packet Data Network Gateway
  • the Serving Gateway Serving Gateway
  • MME Mobility Management Entity
  • eNB evolved Node B
  • backhaul node a common user equipment
  • a common user equipment hereinafter referred to as a normal device
  • the backhaul network and the access network can use the same or different frequencies and formats.
  • the backhaul network uses LTE TDD (time-division duplex) as the backhaul transmission
  • 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
  • LTE FDD Frequency Division Duplexing
  • the backhaul network is transparent to the access network Transfer user data.
  • Ordinary devices can also access the core network directly through the eNB.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the mapping in the bearer mapping table may also be a mapping relationship between a QoS Class Identifier (QCI) and a dedicated bearer flag.
  • QCI QoS Class Identifier
  • the backhaul node 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 Different Service Code Point
  • the downlink data can also be implemented in a similar manner, and will not be described here.
  • bearer mapping rules may also be used to implement bearer mapping.
  • 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.
  • OMN Operaation Administration and Maintenance
  • 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.
  • 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;
  • Attach Request an attach request message
  • 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.
  • EPC Evolved Packet Core
  • 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.
  • RRC Radio Resource Control
  • 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.
  • the session creation request message may carry multiple parameters, for example,
  • 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.
  • 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.
  • 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”.
  • 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.
  • 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.
  • 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.
  • 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.
  • Session Management Response Session Management Response
  • Step 9 The MME sends a create bearer response message to the Serving GW (Create Bearer)
  • Step 10 The Serving GW sends a Create Bearer Response message to the PDN GW.
  • 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.
  • 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.
  • the backhaul node 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.
  • 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.
  • 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.
  • 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.
  • a timer corresponding to the dedicated bearer may be set.
  • the timer is started, and a clock is set.
  • the establishment of the dedicated bearer is maintained before the clock expires.
  • 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.
  • 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 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 deactivation bearer response message to the MME (Deactivate Bearer)
  • 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)
  • 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.
  • 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.
  • 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.
  • 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).
  • 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;
  • the user equipment 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.
  • 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.
  • the second network device can establish a part of the dedicated bearer or all the dedicated bearers for the backhaul node.
  • 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.
  • the second network device allocates an IP address to the common device.
  • the process of establishing the dedicated bearer is also triggered.
  • 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.
  • 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.
  • 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.
  • 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.
  • a default bearer is established for the backhaul node.
  • at least two dedicated bearers are established for the backhaul node at a time, when accessed through the backhaul node.
  • 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.
  • 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
  • the second network device deletes the default bearer and the default bearer corresponding to all the dedicated bearers.
  • the backhaul node 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.
  • the PDN GW deletes all bearers corresponding to the backhaul node.
  • 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.
  • a timer corresponding to the dedicated bearer may be set.
  • the timer is started, and a clock is set.
  • the establishment of the dedicated bearer is maintained before the clock expires.
  • the clock expires, there is still no service data transmission on the dedicated bearer, and the dedicated bearer is deleted.
  • 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.
  • the bearer establishment process of the backhaul node can also be implemented in the following manner:
  • 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.
  • 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 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.
  • 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.
  • the default bearer and at least two dedicated bearers are simultaneously established for the backhaul node.
  • 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.
  • the device parameter further includes identity indication information that is used to indicate that the user equipment is a backhaul node.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the create session request message further carries the QoS parameter corresponding to the at least two dedicated bearers respectively.
  • 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.
  • FIG. 15 is a schematic structural diagram of a third type of second network device according to an embodiment of the present invention.
  • 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.
  • a default bearer is established for the backhaul node.
  • at least two dedicated bearers are established for the backhaul node at a time, when accessed through the backhaul node.
  • FIG. 16 is a schematic structural diagram of a fourth type of second network device according to an embodiment of the present invention.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 are 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 are 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.
  • FIG. 19 is a schematic structural diagram of a sixth type of second network device according to an embodiment of the present invention.
  • 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.
  • 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.

Landscapes

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

Abstract

La présente invention concerne, dans certains de ses modes de réalisation, un procédé et un dispositif de gestion du support d'un réseau de raccordement. Le procédé de gestion du support d'un réseau de raccordement comporte les étapes suivantes : un premier dispositif de réseau reçoit un message de demande de rattachement comportant un paramètre de dispositif, juge, en fonction du paramètre de dispositif, si l'équipement d'utilisateur demandant le rattachement est un nœud de raccordement et, si c'est le cas, envoie un message de demande visant à créer une session à un deuxième dispositif de réseau, le message de demande de création de session transportant un identifiant d'abonné mobile international (IMSI), un identifiant de support par défaut, et au moins deux identifiants de supports spéciaux , de telle façon que le deuxième dispositif de réseau crée un support par défaut et au moins deux supports spéciaux pour le nœud de raccordement en se basant sur l'identifiant de support par défaut et sur lesdits au moins deux identifiants de supports spéciaux figurant dans le message de demande de création de session. Le procédé et le dispositif de gestion du support d'un réseau de raccordement décrits dans les modes de réalisation de la présente invention réduisent le temps de préparation pour assurer un service à l'équipement d'utilisateur qui accède au nœud de raccordement, et réduisent la surcharge de signalisation du système.
PCT/CN2013/086856 2012-11-09 2013-11-11 Procédé et dispositif de gestion du support d'un réseau de raccordement WO2014071881A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210447503.4 2012-11-09
CN201210447503.4A CN103813298B (zh) 2012-11-09 2012-11-09 回程网络承载管理方法及设备

Publications (1)

Publication Number Publication Date
WO2014071881A1 true WO2014071881A1 (fr) 2014-05-15

Family

ID=50684075

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/086856 WO2014071881A1 (fr) 2012-11-09 2013-11-11 Procédé et dispositif de gestion du support d'un réseau de raccordement

Country Status (2)

Country Link
CN (1) CN103813298B (fr)
WO (1) WO2014071881A1 (fr)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108307530B (zh) * 2016-09-30 2023-09-22 华为技术有限公司 一种会话连接建立方法、相关设备及系统
WO2019096393A1 (fr) * 2017-11-16 2019-05-23 Huawei Technologies Co., Ltd. Dispositif client, dispositif de réseau d'accès, procédé et programme informatique pour établir un support radio de données
FI20185326A1 (en) * 2018-04-06 2019-10-07 Nokia Technologies Oy Monitoring in wireless backhaul networks
CN110831076B (zh) * 2018-08-10 2023-07-14 大唐移动通信设备有限公司 一种pdu会话的处理方法及设备
CN113424499B (zh) * 2019-02-14 2023-05-30 瑞典爱立信有限公司 在iab网络中协助向ue路由数据的cu、网络节点及其中的方法和相应介质
CN111585725B (zh) * 2019-02-15 2022-07-29 华为技术有限公司 标识管理的方法和装置
CN111010745B (zh) * 2020-01-06 2021-11-05 杭州迪普信息技术有限公司 控制隧道处理方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101388901A (zh) * 2007-09-14 2009-03-18 大唐移动通信设备有限公司 长期演进系统中支持用户静态ip地址寻址的方法及系统
CN101860910A (zh) * 2009-04-09 2010-10-13 大唐移动通信设备有限公司 本地网络的承载建立方法、系统及装置
CN102244910A (zh) * 2010-05-10 2011-11-16 中兴通讯股份有限公司 一种增强单接入语音业务连续性的通信系统及方法
CN102378393A (zh) * 2010-08-11 2012-03-14 电信科学技术研究院 一种中继节点的非接入层过程处理方法及设备

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8179903B2 (en) * 2008-03-12 2012-05-15 Qualcomm Incorporated Providing multiple levels of service for wireless communication devices communicating with a small coverage access point
US8724509B2 (en) * 2009-04-03 2014-05-13 Panasonic Corporation Mobile communication method, mobile communication system, and corresponding apparatus
CN101998449B (zh) * 2009-08-17 2015-07-22 中兴通讯股份有限公司 一种应用于无线中继的传输系统及传输方法
CN102098676B (zh) * 2010-01-04 2015-08-12 电信科学技术研究院 一种实现完整性保护的方法、装置和系统
CN102244937A (zh) * 2010-05-11 2011-11-16 电信科学技术研究院 一种承载建立方法、中继节点及基站
CN102387542A (zh) * 2010-08-31 2012-03-21 中兴通讯股份有限公司 一种演进无线接入系统小区全球标识的配置方法和系统
CN102083178B (zh) * 2010-09-29 2014-04-02 电信科学技术研究院 启动阶段指示发送及网关节点选择方法、系统和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101388901A (zh) * 2007-09-14 2009-03-18 大唐移动通信设备有限公司 长期演进系统中支持用户静态ip地址寻址的方法及系统
CN101860910A (zh) * 2009-04-09 2010-10-13 大唐移动通信设备有限公司 本地网络的承载建立方法、系统及装置
CN102244910A (zh) * 2010-05-10 2011-11-16 中兴通讯股份有限公司 一种增强单接入语音业务连续性的通信系统及方法
CN102378393A (zh) * 2010-08-11 2012-03-14 电信科学技术研究院 一种中继节点的非接入层过程处理方法及设备

Also Published As

Publication number Publication date
CN103813298B (zh) 2017-06-06
CN103813298A (zh) 2014-05-21

Similar Documents

Publication Publication Date Title
US10966222B2 (en) Method, device, and system for processing reflective QoS characteristics
US10972956B2 (en) Enhanced handling on QoS flow description
US11924144B2 (en) Method and apparatus for configuring aggregate maximum bit rate
US11223988B2 (en) Quality of service rule management in 5G
WO2020177764A1 (fr) Procédé de garantie de transmission de données et dispositif de communication
US9532395B2 (en) System and method for device to device (D2D) communication
WO2018059268A1 (fr) Procédé et dispositif de création de tranche de réseau
WO2014071881A1 (fr) Procédé et dispositif de gestion du support d'un réseau de raccordement
EP3512245B1 (fr) Procédé de communication sans fil et équipement utilisateur
WO2013010420A1 (fr) Procédé, dispositif et système de communication à très large bande sans fil
WO2022033558A1 (fr) Procédé de gestion de relais et appareil de communication
WO2018082431A1 (fr) Procédé de communication sans fil, équipement d'utilisateur, dispositif de réseau d'accès, et dispositif de réseau central
WO2021037115A1 (fr) Procédé de gestion de ressources de réseau sans fil, système de réseau et produit associé
US20230388863A1 (en) Communication method and apparatus
WO2018170747A1 (fr) Procédé et appareil de communication
WO2022012361A1 (fr) Procédé et appareil de communication
WO2017008402A1 (fr) Procédé permettant un accès authentifié, station de base et terminal
WO2023174150A1 (fr) Procédé et appareil de commande d'accès
KR101954397B1 (ko) Ｌｔｅ 이동통신 시스템에서 패킷 차단 방법 및 패킷 차단 시스템
KR20200092070A (ko) 무선 통신 시스템에서 등록 관리 방법 및 장치
EP4040845B1 (fr) Procédé, appareil et système de communication
WO2023185772A1 (fr) Procédé et appareil de communication
WO2014056444A1 (fr) Procédé, dispositif et système d'autorisation de ressource

Legal Events

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

Ref document number: 13852822

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13852822

Country of ref document: EP

Kind code of ref document: A1