CN101742452B

CN101742452B - Load bearing management method, relevant equipment and network system

Info

Publication number: CN101742452B
Application number: CN200810175266A
Authority: CN
Inventors: 吴问付; 张艳平
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2008-11-10
Filing date: 2008-11-10
Publication date: 2012-08-29
Anticipated expiration: 2028-11-10
Also published as: CN101742452A

Abstract

The invention discloses a load bearing managing method, relevant equipment and a network system, wherein the load bearing management method comprises the following steps of: confirming that user equipment performing an emergent business is in a business-restricted mode; confirming the load bearing of the non-emergent business of the user equipment according to the load bearing properties of the user equipment; controlling that the load bearing of the non-emergent business is not available. Adopting the technical scheme of the invention, when the UE performing the emergent business is converted to the business-restricted mode from a business-unrestricted mode, or after the user equipment is confirmed to be in the business-restricted mode when the user equipment performing the emergent business is moved, the load bearing of the non-emergent business can be controlled to be available.

Description

Bearer management method, related equipment and network system

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a bearer management method, related equipment and a network system.

Background

In the prior art, sometimes an emergency service that a UE (User Equipment) needs to perform may be an alarm service or a fire alarm service, and an IP (IP multimedia Subsystem) needs to be used to communicate an access network and an IMS to provide the emergency service for a User. For the emergency service, in the wireless evolution network, it is required that the user can use the emergency service even if the user is allowed to use in the roaming forbidden area or the service forbidden area, i.e. in the above special scenario.

In a wireless evolved network, when a UE moves or a received network signal changes, a user may be caused to transition to a traffic limited state. And the mobility management entity accessed by the UE finds that the user service is limited, deletes the related bearer of the UE and sends a location updating rejection message to the UE.

The inventor discovers that in the process of implementing the invention:

and when the mobility management entity determines that the UE is subjected to service in the area, reserving the emergency service bearer of the UE and deleting the non-emergency service bearer of the UE. When the UE is converted to the non-service-limited state, if the UE wants to perform a service, the UE must initiate a re-request to establish the non-emergency service bearers, which increases the service delay of the user and makes the user experience poor.

Disclosure of Invention

Embodiments of the present invention provide a bearer management method, a related device, and a network system, which can control that a non-emergency service bearer is unavailable when a UE performing an emergency service is switched from a service unrestricted mode to a service restricted mode.

In view of this, the embodiment of the present invention provides:

a bearer management method, comprising:

determining that user equipment performing emergency services is in a service restricted mode;

determining non-emergency service bearing of the user equipment according to the bearing attribute of the user equipment;

controlling the non-emergency traffic bearer to be unavailable.

A bearer management method is used for a user equipment to move and comprises the following steps:

a packet data network gateway receives user service limitation indication information sent by a service gateway;

determining that the user service is limited according to the user service limitation indication information;

controlling not to initiate a non-emergency service bearer establishment flow;

and the user service limitation indication information is sent to the service gateway after the mobility management entity determines that the user service is limited.

A mobility management apparatus comprising:

a first determining unit, configured to determine that a user equipment performing an emergency service is in a service restricted mode;

a second determining unit, configured to determine, according to a bearer attribute of the user equipment, a non-emergency service bearer of the user equipment after the first determining unit determines that the user equipment performing an emergency service is in a service restricted mode;

and the control unit is used for controlling the non-emergency service bearer to be unavailable.

A data gateway, comprising:

the first receiving unit is used for receiving user service limitation indication information sent by a service gateway; the user service limitation indication information is sent to a service gateway after the mobility management entity determines that the user service is limited;

a determining unit, configured to determine that the user service is limited according to the user service limitation indication information;

and the control unit is used for controlling not to initiate a non-emergency service bearing establishing process after the determining unit determines that the user service is limited.

A network system, comprising:

the first mobility management entity is used for determining that user equipment which carries out emergency service is in a service limited mode and sending user service limited indication information to the first service gateway;

and the first service gateway is used for setting the non-emergency service bearing state of the user equipment as unavailable according to the user service limitation indication information.

A network system, comprising:

the first mobility management entity is used for determining that user equipment which carries out emergency service is in a service limited mode and sending user service limited indication information to the packet data network gateway through the first service gateway;

and the packet data network gateway is used for setting the non-emergency service bearing state of the user equipment as unavailable according to the user service limitation indication information and/or closing a gate of a data flow related to the non-emergency service.

A network system, comprising:

and the packet data network gateway is used for determining the user service limitation according to the user service limitation indication information and controlling not to initiate a non-emergency service bearing establishing process.

When the user equipment which is carrying out the emergency service is in the service limited mode, the first mobile management entity accessed by the UE reserves the non-emergency service bearing and controls the non-emergency service bearing to be unavailable.

Drawings

Fig. 1 is a diagram of a wireless evolution network architecture.

Fig. 2 is a signaling diagram of a bearer management method according to a second embodiment of the present invention;

fig. 3 is a signaling diagram of a bearer management method according to a third embodiment of the present invention;

fig. 4 is a signaling diagram of a bearer management method according to a fourth embodiment of the present invention;

FIG. 5 is a signaling diagram illustrating the handling of a service request to a UE according to an embodiment of the present invention;

fig. 6 is a signaling diagram of a bearer management method when the UE moves again according to an embodiment of the present invention;

fig. 7 is a signaling diagram of another bearer management method when the UE moves again according to the embodiment of the present invention;

fig. 8 is a signaling diagram of processing when the network side triggers an emergency service according to an embodiment of the present invention;

fig. 9 is a diagram illustrating a structure of a mobility management apparatus according to a fifth embodiment of the present invention;

fig. 10 is a diagram of a data gateway structure according to a sixth embodiment of the present invention.

Detailed Description

In order to make the embodiment of the present invention more clearly understood, a radio evolution network architecture to which the embodiment of the present invention is applied is briefly described as follows, and it should be noted that the embodiment of the present invention is not limited to be applied to the network architecture, and may be applied to other networks. As shown in fig. 1, a core network of a wireless evolved network mainly includes three logic functions, namely, an MME (Mobility Management Entity), a Serving Gateway (S-GW), and a PDN Gateway (P-GW), where the MME is a Mobility Management element and is responsible for functions such as NAS (non-access stratum) signaling, NAS signaling encryption, roaming, tracking, and the like, and allocates a user temporary identity, a security function, and the like. The ServingGateway is responsible for a local mobility anchor point, a mobility anchor point in the 3GPP system and related information of legal monitoring; the PDN Gateway is responsible for policy enforcement and charging and lawful interception related functions. The HSS (Home Subscriber Server) is configured to store Subscriber subscription information.

The first embodiment is as follows:

an embodiment of the present invention provides a bearer management method, including:

the first mobility management entity determines that user equipment which is carrying out emergency service is in a service limited mode;

controlling the non-emergency traffic bearer to be unavailable.

In this embodiment and subsequent embodiments, the bearer attribute of the ue may be an ARP (Allocation and Retention Priority) of the bearer, or a Qos of the bearer, or an APN (Access Point Name) in a PDN link.

When the user equipment which is carrying out the emergency service is in the service limited mode, the first mobility management entity accessed by the UE reserves the non-emergency service bearer and controls the non-emergency service bearer to be unavailable, so that the service can be quickly recovered when the subsequent user equipment is converted into the service unlimited mode, and the user experience is improved.

Description of the drawings: the key points of this and subsequent embodiments are that the user cannot access the mobile terminal at the current location/time/access network/access technology due to the change of the latter subscription data caused by the change of the mobile terminal or the access technology, and the user is converted into the service restricted mode, and the mobility management entity that whether the user will change the access is not necessarily connected. For convenience of description, the present invention is described only by taking the case that the user changes the mobility management entity. Similarly, when the user is switched from the service limited mode to the normal mode, there is no necessary connection with the mobility management entity to which the user will change access, and for convenience, the present invention is described by taking the example that the user changes the mobility management entity.

Example two:

referring to fig. 2, a second embodiment of the present invention provides a bearer management method, in which a UE performing an emergency service is switched from a source mobility management entity to a target mobility management entity, and a network side controls a non-emergency service bearer to be unavailable, in a third and a fourth embodiments of the present invention and subsequent embodiments, the target mobility management entity is also referred to as a first mobility management entity, and the bearer management method specifically includes:

and B1, the UE is switched from the source mobility management entity to the target mobility management entity.

B2, the UE sends a location update request to the target mobility management entity, which may be a routing area/tracking area update request.

B3, after receiving the location update request, if the context information such as the subscription data of the user is not stored, the target mobility management entity acquires the subscription data of the user from HLR/HSS (home location register/home subscriber server).

B4, the target mobility management entity determines whether the user service is limited according to the user subscription data, if so, the target mobility management entity checks whether the UE is currently carrying out the emergency service, and if the UE is carrying out the emergency service, the target mobility management entity permits the user to access. If the user has the non-emergency service related bearer, the mobility management entity sets the non-emergency service bearer of the UE to be unavailable.

The user subscription data in this and subsequent embodiments may include: the target mobility management entity determines whether the user service is limited according to the user subscription data, specifically, whether the user service is limited in the access area/network, or whether the access technology is limited or the access time is limited. The access area is limited, namely the UE accesses an area which is not allowed to be accessed; the access technology limitation may refer to that the UE accesses an access technology that is not allowed to access, such as 2G, 3G, or LTE, and the access network limitation may refer to that the user accesses a network that is not allowed to access, such as that a user moving in china is not allowed to access china unicom.

The target mobility management entity may determine whether the user performs an emergency service according to whether the ARP (Allocation and permission priority) of the bearer is an emergency ARP or according to whether an Access Point Name (Access Point Name) exists in a PDN link established by the user.

The following major sections (1), (2), (3), or (4) describe a processing flow of the network side, where the processing manner of the network side for the non-emergency service bearer of the UE may be: (1) (2), (1) + (3), (2) + (3) or (4).

(1) For the bearer related to the non-emergency service, the target mobility management entity may set the bearer state as unavailable, that is, set the bearer state as invalid or suspended, and at the same time:

the target mobility management entity sends an update bearer request to a Service gateway, wherein the update bearer request carries user Service Restriction Indication information, the user Service Restriction Indication information can be a Service Restriction Indication cell (Service Restriction Indication) which indicates that Service of a Service gateway UE is restricted in an access area, an access technology or access time, and informs the Service gateway to suspend the bearer; alternatively, the user traffic limitation indication information may be bearer information, such as a status list of bearers, where the status of the non-emergency traffic bearer is set to suspend/invalid, and the serving gateway sets the status of the non-emergency traffic bearer to suspend/invalid. Or, the target mobility management entity sends a bearer update message for each non-emergency service bearer, at this time, the user service limitation indication information carried in the bearer update message may be the status of the bearer (i.e., suspended/invalid), at this time, after the serving gateway receives a bearer update request corresponding to the bearer, the serving gateway learns that the bearer is unavailable according to the status of the bearer, and the serving gateway sets the status of the bearer to suspended/invalid. The user service restriction indication information in this embodiment and the following embodiments may also include the above three forms, which does not affect the implementation of the present invention. And when receiving a data packet related to non-emergency service bearer subsequently, the service gateway directly discards the data packet and does not send a downlink data notification message to the target mobility management entity.

Or:

the target mobility management entity sends a Suspend message to the serving gateway, where the message may carry user service restriction indication information, where the user service restriction indication information may be a bearer ID list or a service restriction indication cell or a combination of the two, which needs to be suspended, to indicate that the service of the serving gateway user is restricted and a non-emergency service related bearer needs to be suspended.

The user service limitation indication information can be bearer information or a service limitation indication cell; and the state of the non-emergency service bearer in the bearer information is unavailable. The load bearing state in the embodiment and the subsequent embodiments of the invention is unavailable: the status of the bearer is invalid/suspended. The relevant network elements (the service gateway and the packet data network gateway) receive the data of the relevant bearer, and directly discard the data packet, or save the data packet but do not send the data packet to other network elements or inform other network elements of downlink data packets. Namely: the serving gateway does not transmit a DownLink Data Notification message (DownLink Data Notification) to the mobility management entity to notify that there is DownLink Data. The packet data network gateway does not send data packets to the serving gateway.

If the suspend message does not carry the list of the bearer IDs to be suspended, the serving gateway determines whether the bearer is a bearer related to the emergency service according to the ARP in the pre-stored user context or the Qos of the bearer, and sets the status of the bearer related to the non-emergency service to be invalid or suspended, but does not delete the bearer. And when receiving a data packet related to non-emergency service bearer subsequently, the service gateway directly discards the data packet and does not send a downlink data notification message to the target mobility management entity.

(2) For the Bearer related to the non-emergency service, the MME may utilize the existing Bearer Update message (Update Bearer Request) or other messages that can notify the service gateway that the service of the user is limited, where the message carries the indication information of the limited service of the user to indicate that the service of the area where the user of the service gateway is located is limited, and only services with special requirements such as emergency service and the like can be performed;

after receiving the indication information of the user service limitation, the service gateway sends a bearing update message or other messages informing the packet data network gateway that the user service is limited to the packet data network gateway, wherein the message carries the indication information of the user service limitation, and the information indicates that the service of the area where the packet data network gateway user is located is limited and only services with special requirements such as emergency service and the like can be carried out.

If the user service limitation indication information carries a list of bearer IDs to be suspended, the packet data network gateway does not need to determine which bearers are related to the emergency service, otherwise, the packet data network gateway needs to determine which bearers are related to the emergency service by itself, and may determine whether the APN related to the bearers is an emergency APN according to whether the APR of the bearer is an emergency ARP, or determine which bearers are non-emergency service bearers and which bearers are emergency service bearers, and for the non-emergency service bearers, the packet data network gateway (PDN GW) may have the following two processing modes:

1. recording user service limitation, setting the state of non-emergency service related load bearing as unavailable or suspended, and directly discarding the packet without sending to a service gateway when receiving the data packets related to the load bearing.

2. If a static PCC rule is configured, the gate of the non-emergency service data flow is closed by the packet data network gateway, or if the processing mode of (1) + (3) is adopted, the gate of the non-GBR non-emergency service data flow can be only closed.

If the dynamic PCC rules are configured, the packet data network gateway sends a session modification message to a Policy and Charging Rule Function (PCRF). The message carries a Service Restriction Indication (Service Restriction Indication) message, which indicates that the PCRF is restricted in an access area, an access technology, an access time, or a roaming Service, and can only perform special services such as an emergency call. Or, in a more recent step, the message may also carry indication information indicating which Data Flow Service Data flows (SDF Service Data flows) of the PCRF are Data flows related to the emergency Service, and which are not Data flows related to the emergency Service.

After receiving the service restriction indication, the PCRF closes a gate (gate) of the non-emergency service related data flow, and may further formulate a new PCC rule, and send a session modification response message to the packet data network gateway, where the message carries the new PCC rule with the modified gate state.

Further, the PCRF can also: notifying an Application Function entity (AF) that the user service is limited, and the AF no longer initiates a service related to a non-emergency service; or, the PCRF rejects the service related to the non-emergency service initiated by the AF. The PCRF may also inform the AF of the reason for the rejection (user traffic restriction) so that the AF no longer initiates non-aggressive traffic related traffic.

After receiving the session modification response message, the packet data network gateway sets the gate states of the non-emergency service related data flows to be closed, namely closes the gates of the data flows, and sends the response message to the service gateway. The service gateway sends a response message to the mobility management network element.

(3) For non-emergency service-related GBR (guaranteed Bit Rate) bearers, the target mobility management entity may set the bearer status as invalid or suspended. Specifically, the following two methods can be adopted:

1. the target mobility management entity deletes GBR load related to non-emergency service of a user, the target mobility management entity sends a load deleting Request Delete Bearer Request message to a service gateway, the service gateway deletes the GBR load related to the non-emergency service after receiving the load deleting Request, and sends a load deleting Request Delete Bearer Request message to a packet data network gateway, the packet data network gateway is informed of deleting the GBR load related to the non-emergency service, and the packet data network gateway deletes the GBR load related to the non-emergency service and returns a response message to the service gateway.

2. The target mobility management entity modifies the GBR (guaranteed Bit Rate) bearer related to the non-emergency service of the user, and reduces the GBR and/or the MBR (Maximum Bit Rate) of the GBR bearer related to the non-emergency service to 0. The target mobility management entity sends a Bearer Update Request (Update Bearer Request) message to the serving gateway instructing the serving gateway to reduce GBR and/or MBR of non-emergency traffic related GBR bearers to 0. After receiving the Bearer Update Request, the service gateway sets the GBR and/or MBR of the GBR Bearer related to the non-emergency service to 0, and sends an Update Bearer Request (Update Bearer Request) message to the packet data network gateway, the packet data network gateway modifies the Bearer related to the non-emergency service, reduces the GBR and/or MBR of the GBR Bearer related to the non-emergency service to 0, and returns a response message to the service gateway.

This (3) can be combined with (1) or (2) to implement the processing of the non-emergency service bearer, and it is now illustrated how 2 in (3) is combined with (1) to implement the processing of the non-emergency service bearer: the target mobility management entity modifies the GBR bearer related to the non-emergency service of the user, reduces the GBR and/or MBR of the GBR bearer related to the non-emergency service to 0, and sends a bearer updating request to the service gateway, wherein the bearer updating request carries the information of the limited indication of the user service and the information indicating that the GBR bearer parameter is set to 0; after receiving the bearer update request, the service gateway sets the GBR and/or MBR of the GBR bearer related to the non-emergency service to 0, and sets the status of the bearer of the non-emergency service to be suspended or invalid according to the user service limitation indication information. And the service gateway sends an Update bearer request (Update bearer request) message to the packet data network gateway, the packet data network gateway modifies the bearer related to the non-emergency service, reduces the GBR and/or the MBR of the GBR bearer related to the non-emergency service to 0, and returns a response message to the service gateway.

(4) As long as the GBR bearer or the non-GBR bearer is not related to the emergency Service, the target mobility management entity sends a bearer update message or other messages for notifying that the Service of the Service gateway is limited to the Service gateway, such as Service Notification, where the message carries indication information indicating that the Service of the Service gateway is limited, and indicates that the Service of the Service gateway is limited, and only special services such as emergency Service can be performed.

The serving gateway sends a bearer update request or other messages for notifying that the packet data network gateway user Service is limited, such as Service notification, to the packet data network gateway after receiving the message, where the message carries indication information of user Service limitation, and indicates that the packet data network gateway user Service is limited and only can perform special services such as emergency services.

If static PCC rules are configured, the packet data network gateway sets the GBR and/or the MBR to 0 and closes the doors of the non-emergency traffic data flows. If GBR and/or MBR is reduced to 0, the related bearers need to be merged, and an update procedure of the bearers can be initiated. Or the packet data network gateway initiates a bearer deletion process to delete the non-emergency service related GBR bearer, wherein the process comprises the following steps: and the PDN GW informs the S-GW to delete the GBR load related to the non-emergency service, and the S-GW informs the mobility management entity to delete the GBR load related to the non-emergency service.

If the dynamic PCC rule is configured, the packet data network gateway sends a session update message to the PCRF, wherein the message carries a user Service Restriction (Service Restriction Indication) Indication cell, and indicates that the PCRF user access area, the access technology and/or the access time Service are restricted, and only special services such as emergency services and the like can be performed.

After the PCRF knows that the user traffic is limited, for the non-emergency traffic related data flows, if the non-emergency traffic related data flows are GBR data flows, the GBR and/or MBR may be set to 0 (not necessarily), a new PCC rule is established, or the non-emergency traffic GBR data flows are deleted, and the PDN GW is notified to delete the non-emergency traffic GBR data flows. Then the packet data network gateway initiates a bearer deletion process to delete the non-emergency service related GBR bearer, wherein the process comprises the following steps: and the PDN GW informs the S-GW to delete the GBR load related to the non-emergency service, and the S-GW informs the mobility management entity to delete the GBR load related to the non-emergency service. The PCRF may also close the non-GBR bearers related to the non-emergency traffic or all the data flow gates related to the non-emergency traffic, and send a session update response message to the packet data network gateway, where the message carries new PCC rule information, where the new PCC rule indicates that the data flow gate states related to the non-emergency traffic are closed, or the GBR and/or MBR of the GBR bearers related to the non-emergency traffic are set to 0, and the data flow gate states of the non-GBR bearers related to the non-emergency traffic are closed.

After receiving the message, the packet data network gateway modifies the gate state of the non-emergency service data flow to be closed (closed) or sets the state of the non-emergency service bearer to be suspended/invalid according to the new PCC rule. Or, if the GBR and/or MBR of the GBR bearer of the non-emergency service in the PCC rule is set to 0 and the gate state of the data flow of the non-GBR bearer of the non-emergency service is closed, the GBR and/or MBR of the GBR bearer of the non-emergency service is set to 0, and the gate of the data flow of the non-GBR bearer of the non-emergency service is closed, the packet data network gateway may initiate a bearer update procedure according to the new PCC rule. If the GBR and/or MBR of the GBR bearer of the non-emergency service is set to 0 by the packet data network gateway, the information indicating that the GBR bearer parameter of the non-emergency service is set to 0 needs to be sent to the service, the GBR and/or MBR of the GBR bearer of the non-emergency service is set to 0 by the service gateway, and the information indicating that the GBR bearer parameter of the non-emergency service is set to 0 is sent to the target mobility management entity; the target mobility management entity sets the GBR and/or MBR value of the GBR bearer of the non-emergency service to 0, the target mobility management entity may also send information indicating that the GBR bearer parameter of the non-emergency service is set to 0 to the UE, and the UE sets the GBR and/or MBR value of the GBR bearer of the non-emergency service to 0

B5, the target mobile management entity releases the bearing resource related to the non-emergency service of the access network.

The target mobility management entity (the first mobility management entity) needs to send a notification message to an access network element (the access network element is referred to as a first access network element), where the notification message is used to notify the access network element to delete a handover restriction of a user, or notify the access network element to modify a handover restriction of a user, so as to ensure that the user is not limited by an access area, an access technology and/or access time when the user has an emergency service, and then the access network element deletes the handover restriction of the user, or retains a roaming restriction and deletes the access area, the access technology and/or the access time restriction.

B6, the target mobility management entity sends a location update accept message to the UE, which may be a routing area/tracking area accept message, where the message carries user service restriction indication information indicating that the user service is restricted, and only special services such as emergency service can be performed, or carries a bearer list that needs to be suspended/invalidated, or a combination of the two.

After receiving the notification, the UE may distinguish emergency or non-emergency services according to the bearer APN or ARP, and set the status of the bearer for the non-emergency services to invalid/suspended, or set the bearer related to the non-emergency services to invalid/suspended status according to the bearer list in the received message, and control not to initiate the non-emergency services, that is, the user does not request network resources or send uplink data temporarily except for the emergency services.

B7, after the emergency service is completed, according to the user subscription data, if the service is judged to be not limited under the current condition of the UE, if the access network element deletes the switching restriction in B5, the target mobility management entity sends an initial context setup request message to the access network element to request to add the switching restriction again, the access network element adds the switching restriction, and sends an initial context setup response message to the target mobility management entity; if the access network element deletes part of the contents of the handover restriction in B5, the second mobility management element sends a user context modification request to the access network element to request modification of the handover restriction, i.e. re-adding the access area, access technology and/or access time restriction deleted in B5 to the handover restriction, the access network element modifies the handover restriction, and sends a user context modification response to the target mobility management entity, wherein the initial context setup request/user context modification request is a handover restriction request to restore the user.

And if the user service is still limited, initiating a separation flow to the UE to separate the UE so as to delete all the bearers of the UE.

In the first embodiment of the present invention, after the UE performing the emergency service is switched from the source mobility management entity to the target mobility management entity, the non-emergency service bearer is reserved and controlled to be unavailable under the condition that the user service is limited, so that it is ensured that the UE cannot perform other services except the emergency service under the condition that the user service is limited, thereby avoiding unnecessary loss of an operator, and further, when the subsequent user service is no longer limited, the service can be quickly recovered, thereby improving the user experience.

Example three:

referring to fig. 3, a third embodiment of the present invention provides a bearer management method, in which a UE performing an emergency service is switched from a source mobility management entity to a target mobility management entity, and a network side deletes a bearer controlling a non-emergency service, where the method specifically includes:

c1, the UE is switched from the source mobility management entity to the target mobility management entity.

C2, the UE sends a location update request to the target mobility management entity, which may be a routing area/tracking area update request.

C3, if the target mobility management entity does not store the context information of the user or the stored user context information is not valid, the target mobility management entity sends a location update request to HLR/HSS (home location register/home subscriber server). And the HLR/HSS sends a location updating confirmation to the target mobile management entity, wherein the location updating confirmation carries the user subscription data.

The target mobility management entity determines whether user service is limited or not according to user subscription data, and sends a routing area/tracking area receiving message to the UE, if the user service is limited, the message can carry a Cause value of Cause, the Cause value indicates that the user service is limited, only special services such as emergency services and the like can be carried out, or the routing area/tracking area receiving message carries a bearer list which needs to be suspended/invalid or a combination of the two. After receiving the notification, the UE distinguishes emergency or non-emergency services according to the bearer APN or ARP and sets the bearer related to the non-emergency services to be in a suspended state; or setting the state of the bearer indicated in the locally stored bearer list to be suspended/invalid, and the UE temporarily does not request network resources or send uplink data except for the emergency service.

C4, after sending the routing area/tracking area acceptance message, the target mobility management entity initiates a bearer deactivation/deletion process to delete the bearer related to the non-emergency service of the user.

The target mobility management entity (the first mobility management entity) needs to send a notification message to an access network element (the access network element is the first access network element), where the notification message is used to notify the access network element to delete a handover restriction of a user, or notify the access network element to modify a handover restriction of a user, so as to ensure that the user is not restricted by an access area, an access technology and/or access time when the user has an emergency service, and then the access network element deletes the handover restriction of the user, or retains a roaming restriction and deletes the access area, the access technology and/or the access time restriction.

C5, after the emergency service is finished, according to the user subscription data, if the service is judged to be not limited under the current condition of the UE, if the access network element deletes the switching limitation in C4, the target mobility management entity sends an initial context establishment request message to the access network element to request to add the switching limitation again, the access network element adds the switching limitation, and sends an initial context establishment response message to the target mobility management entity; if the access network element deletes part of the contents of the handover restriction in C4, the second mobility management element sends a user context modification request to the access network element to request modification of the handover restriction, such as: and the access area, the access technology and/or the access time limit are/is re-added into the switching limit, the access network element modifies the switching limit and sends a user context modification response to the target mobility management entity.

And if the user service is still limited under the current condition, namely the UE is determined not to be accessed, initiating a user separation process, deleting all the bearers of the user and separating the user.

In the third embodiment, after the UE is switched, if the user service of the UE is limited, the target mobility management entity allows the user to access and delete the bearer related to the non-emergency service of the user, so that the emergency service of the user can be ensured, the user cannot perform other services except the emergency service, and unnecessary loss of an operator is avoided. Further, after the emergency service is completed, the switching restriction of the user in the access network element is added or modified, so that the user can only perform the switching permitted by the switching restriction without the emergency service.

Example four:

referring to fig. 4, a fourth embodiment of the present invention provides a bearer management method, for a UE performing an emergency service to move from a non-3 GPP network to a 3GPP network, where the UE may directly register in the 3GPP network and handover a data stream to the 3GPP network when moving from the non-3 GPP network to the 3GPP network, which is referred to as non-optimized handover. Or, the UE pre-registers in the 3GPP network through the non-3 GPP network, accesses to the 3GPP network after success, and switches the data stream to the 3GPP network, which is called optimized handover. The embodiment does not limit whether the UE handover mode is an optimized or non-optimized handover. The method specifically comprises the following steps:

d1, the UE initiates an attach request to the target mobility management entity.

In this step, the UE may directly send an attach request to the target mobility management entity, or may send an attach request to the target mobility management entity through the non-3 GPP network.

D2, the target mobility management entity sends a location update message to the HLR/HSS.

D3, HSS/HLR sends the position renewal affirming information to the object mobile management entity, the information carries the subscription data of the user.

D4, the target mobility management entity determines whether the user service is limited according to the user subscription data, if the user service is limited (i.e. the user can not perform service in the current area/access technology/access time/roaming limit), the target mobility management entity judges whether the user has an emergency service, such as APN of the emergency service, according to the user subscription data sent by the HSS/HLR. It should be noted that: whether the user service is limited or not and whether the user has the emergency service or not are judged in no sequence.

And the target mobile management entity determines that the user service is limited, and when the user has an emergency service, the target mobile management entity sends a request message for establishing a default bearer to the service gateway, wherein the message carries user service limitation indication information and indicates that the service gateway user service is limited.

D5, after receiving the request message of establishing default load, the service gateway sends the request message of establishing default load to the packet data network gateway, the message carries the indication information of user service limitation, and indicates that the packet data network gateway user service is limited. After receiving the message, the packet data network gateway learns that the current user service is limited according to the service limitation indication information, and the packet data network gateway can establish the special bearers without initiating a special bearer establishment procedure aiming at the data flow related to the non-emergency service. The packet data network gateway may also close the door of the non-emergency service related data flows in the default bearer or may also initiate a bearer modification procedure to delete the non-emergency service related traffic flows from the bearer.

D6, the packet data network gateway may also interact with the PCRF to initiate a session update/modification message to the PCRF, where the message carries user traffic Restriction indication information, and the user traffic Restriction indication information may be a traffic Restriction indication (Service Restriction Indicator) cell, indicating that the PCRF user traffic is restricted. After receiving the message, the PCRF controls unavailability of the non-emergency traffic-related data flows according to the user traffic restriction, and may formulate a new PCC rule, where controlling unavailability of the non-emergency traffic-related data flows may be to close gates of the user non-emergency traffic-related data flows, or to delete the data flows.

The PCRF sends a session update/modification response message to the packet data network gateway, wherein the message may contain a new PCC rule, the new PCC rule may close (closed/closed) a data flow related to non-emergency services, or delete only a GBR data flow related to non-emergency services, and after receiving the message, the packet data network gateway closes the data flow related to non-emergency services, or initiates a bearer modification process to delete a data flow related to non-emergency services of a user, or delete only a GBR data flow related to non-emergency services, without initiating a dedicated bearer establishment request process.

Furthermore, the PCRF may also carry service restriction Indicator (ServiceRestriction Indicator) indication information in the event report, and after receiving the message, the AF knows that the user service is restricted, and does not initiate a non-emergency service to the UE any more. The AF sends an acknowledgement message or a new application/service message to the PCRF.

Or, when the PCRF receives a non-emergency service request initiated by the AF, rejecting the non-emergency service request.

This step is an optional step.

D7, the packet data network gateway sends a response message for establishing the default bearer to the service gateway.

D8, the service gateway sends a response message for establishing the default load to the target mobility management entity.

D9, the target mobility management entity sends an attach accept message to the user. The message carries user service limitation indication information to inform the user that the service is limited, and after receiving the message, the UE knows that the service is limited, and can not initiate a non-emergency service bearing resource request/modification and can not initiate a non-emergency service PDN link request. The UE sets the local non-emergency traffic data flow state to pending/unavailable.

In this step, the target mobility management entity may directly send the attach accept message to the UE, or send the attach accept message to the UE through the non-3 GPP network, without affecting the implementation of the present invention.

In the fourth embodiment of the present invention, when the UE moves from the non-3 GPP network to the 3GPP network, if the user service of the UE is limited, the packet data network gateway does not initiate the establishment procedure of the non-emergency service bearer, so as to ensure that the UE cannot perform other services except the emergency service, and avoid unnecessary loss of the operator.

Referring to fig. 5, the following describes a possible scenario that, after a non-emergency bearer of a user is suspended, in an abnormal situation, the user requests to resume the bearer to ensure that the UE cannot perform non-emergency services except for an emergency service when the user service is limited, where the scenario occurs:

1. after the user emergency service is completed, or the emergency service is subjected to clearance, and when the UE is converted from the connection state to the idle state, the network side releases the radio bearer of the emergency service of the user. If the user wants to recover the radio bearer of the emergency service, the user initiates a service request process.

2. After the user emergency service is completed, or the emergency service is subjected to clearance, and when the UE is converted from the connection state to the idle state, the network side releases the radio bearer of the emergency service of the user. If the user only establishes the signaling connection with the network side for other reasons, such as CSFB (CS fallback), but does not recover the bearer on the radio side, the user initiates a service request procedure to request recovery of the bearer on the radio side (including the radio bearer for emergency services and/or non-emergency services).

3. The user is carrying out the emergency service, and the radio bearer of the emergency service exists at the moment, but the user still initiates the service request process and wants to recover the bearer of the non-emergency service.

The service request flow is as follows:

e1, the UE sends a service request message to the first mobility management entity.

E2, the first mobility management entity determines whether there is a radio side bearer that the emergency service has not been recovered, if so, the first mobility management entity recovers the radio side bearer of the emergency service, otherwise, a service reject message is sent to the user equipment.

Or: the first mobility management entity verifies the validity of the user access in the current area/access technology/access time (namely, judges whether the service of the user is limited) according to the subscription data of the user, and if the service of the user is limited, the first mobility management entity only recovers the emergency service bearer of the user and does not recover other non-emergency service bearers. And if the user does not have the emergency service bearer which needs to be recovered, the first mobility management entity sends a service rejection message to the user equipment.

The service rejection message carries a user service restriction indication cell and/or carries a non-emergency service bearer list, after receiving the message, the UE can determine which bearers are related to the emergency service and which bearers are not related to the emergency service according to the supported ARP, APN, and the like, for example, determine whether the APN is an APN of the emergency service, and set a locally stored non-emergency service bearer state to a suspended/unavailable state, and no longer initiate a service request.

Referring to fig. 6 and fig. 7, a scenario is described in which a UE moves from a first mobility management entity to a second mobility management entity, in which case, the UE may switch from a traffic-limited mode to an unrestricted mode, or continue to be in a traffic-limited mode, so that there are two implementation manners, that is, when the UE is handed over to the second mobility management entity, if the UE has switched from the traffic-limited mode to the unrestricted mode, a bearer may be recovered during the handover process, so that the user can perform a service quickly; the other is as follows: if the UE is still in the service limited mode when being switched to the second mobility management entity, the non-emergency service bearer needs to be kept unavailable, and unnecessary loss of an operator is avoided.

The first mode is as follows:

f1, the first access network element sends a handover request message to the first mobility management entity.

And F2, the first mobility management entity sends a forward switching request message to the second mobility management entity. The message includes user service restriction indication information, which may be a user Bearer information list, and the user Bearer information list may include whether a Status (Bearer Status) of each Bearer is suspended/unavailable. Or: the user service restriction indication information is a service restriction indication (ServiceRequest Indicator) cell to notify the second mobility management entity that the UE is restricted in service at the source side and only can perform special services such as emergency services.

F3, if the serving gateway changes (i.e. the UE accesses the second serving gateway at this time), the second mobility management entity sends a create bearer request message to the second serving gateway.

The create bearer request message carries user service restriction indication information, which may be user bearer state information or a service restriction indication cell.

F4, after receiving the request message of establishing bearer, the second service gateway creates bearer, and for the bearer indicated as suspended/unavailable, the second service gateway sets the status of the bearer as suspended/unavailable, and when receiving the Data packet related to the bearer, discards the Data packet, and does not send DownLink Data Notification message to the second mobility management entity.

Alternatively, in step F3, if the second mobility management entity holds the subscription data of the user and verifies that the user is valid (i.e., the user can access within the current area/access technology/access time). The bearer establishment request message does not carry the service restriction indication information, and in step F4, the bearer is created according to the general bearer creation step.

Description of the drawings: the second mobility management entity may not in this step, but in step F9 inform the second serving gateway of the user traffic restriction indication information, or inform the second serving gateway to recover the associated bearer, without affecting the implementation of the present invention.

And F5, the second mobility management entity creates a radio bearer for the UE.

And F6, the second mobility management entity sends a forward switching response message to the first mobility management entity.

And F7, after the switching is completed, the second mobility management entity sends a forward switching completion message to the first mobility management entity.

And F8, the first mobility management entity sends a switching completion confirmation message to the second mobility management entity.

F9, the second mobility management entity sends an update bearer Request message UpdateBearer Request to the second serving gateway.

And F10, the second service gateway sends an update bearing request message to the packet data network gateway.

If the second mobility management entity does not notify the second serving gateway of the indication information of the limited user traffic in step F3, the indication information of the limited user traffic may be carried in the update bearer request message sent by the second mobility management entity to the second serving gateway in step F9.

In step F10, after receiving the bearer update request message, the second serving gateway sets the status of the bearer to be suspended/unavailable for the bearer indicated as suspended/unavailable, discards the Data packet when receiving the Data packet related to the bearer, and does not send a DownLink Data Notification message to the second mobility management entity.

Or, if the second mobility management entity stores the subscription data of the user and verifies that the user is valid (i.e., the user can access within the current area/access technology/access time), the bearer update request message does not carry the service restriction indication information in step F9.

In the first embodiment, for the implementation manner in which the packet data network gateway sets the non-emergency service bearer to be suspended, after receiving the message in step F10, the packet data network gateway sets the status of the suspended bearer to be available, and when receiving the downlink packet related to the bearer, the packet data network gateway does not discard the downlink packet but sends the downlink packet to the corresponding second serving gateway.

Or:

if the static PCC rule is configured, the packet data network gateway sets the state of the gate of the non-emergency service-related data flow to open (open), and may initiate a bearer update procedure for the non-emergency service bearer with GBR/MBR of 0.

If the dynamic PCC rule is configured, the packet data network gateway can send a session update request message to the PCRF, and the message can carry a recovery bearing indication cell to inform the PCRF that the user service is no longer limited. After receiving the message, the PCRF opens a gate of the user non-emergency service data flow, sets the state of the gate as open (open), and sends a session update response message to the packet data network gateway, wherein the message carries a new PCC rule which modifies the gate state of the data flow. After receiving the session update response message, the packet data network gateway updates the gate state of the non-emergency service data flow to open, and can also initiate a bearer addition/update/deletion flow according to the new PCC rule.

F11, the packet data network gateway sends an update bearer response message to the second serving gateway.

And F12, the second service gateway sends an update bearing response message to the second mobility management entity.

Description of the drawings: the second mobility management entity notifies the second serving gateway that the bearer recovery procedure can be completed in the subsequent location update procedure, please refer to F13-F18.

If the user finds that the routing area is changed or the tracking area is not in the stored tracking area list, the routing area/tracking area updating process is initiated.

F13, the UE sends a location update request to the second mobility management entity, i.e. initiates a routing area/tracking area update request.

And F14, if the second mobility management entity has no context information such as user subscription data or has not been registered in a home location register/home location server (HLR/HSS) before, sending a location updating request message to request to register and acquire the user subscription data.

F15, the second mobility management entity sends a bearer update request message to the second serving gateway.

And F16, the second service gateway sends a bearing update request message to the packet data network gateway.

In step F15, if the second mobility management entity determines that the user is still in the user service restricted mode according to the user subscription data, the update bearer request message includes the user service restricted indication information.

In step F16, after receiving the bearer update request message, the second serving gateway sets the status of the non-emergency service bearer to pending/unavailable, discards the Data packet when receiving the Data packet related to the bearer, and does not send a DownLink Data Notification message to the second mobility management entity.

Alternatively, if the second mobility management entity verifies that the user is valid according to the subscription data of the user (i.e. the user can access within the current area/access technology/access time) in step F15:

the second mobility management entity sends an update bearer request message to the second serving gateway, where the message carries user unlimited indication information, and the user unlimited indication information may be a bearer recovery indication to indicate the second serving gateway to recover the non-emergency service bearer.

Or, the second mobility management entity sends a Resume message to the second serving gateway, where the message may carry user unlimited indication information, and the user unlimited indication information may be a bearer list that needs to be recovered.

The second serving gateway sets the non-emergency service bearer state as available, and when receiving the downlink data packet of the user, the second serving gateway does not discard the data packet any more, and may notify the second mobility management entity (when the downlink data plane of the user is not available) or directly forward the user data to the second access network element (when the downlink data plane of the user is available).

If the state of the bearer of the non-emergency service is set to be suspended/invalid by the packet data network gateway in the first embodiment, or the gate of the data flow of the bearer of the non-emergency service is closed, after receiving the update bearer request message or the Resume message, the second serving gateway:

the second service gateway sends an update bearing request message to the packet data network gateway, wherein the update bearing request message carries user unlimited indication information, and the user unlimited indication information can be bearing recovery indication; to instruct the packet data network gateway to resume the non-emergency traffic bearer.

Or the second serving gateway sends a Resume message to the packet data network gateway, where the message carries user unlimited indication information, and the user unlimited indication information may be a bearer list that needs to be restored.

After receiving the message, the packet data network gateway sets the state of the suspended bearer to be available, and when receiving the downlink data packet related to the bearer, the packet data network gateway does not discard the downlink data packet but sends the downlink data packet to the corresponding second service gateway.

Or:

if a static PCC rule is configured, the packet data network gateway sets the state of the gate of the non-emergency service-related data flow to open (open), and for the non-emergency service bearer with GBR/MBR of 0, the packet data network gateway may initiate a bearer update procedure according to the PCC rule.

F17, the packet data network gateway sends an update bearer response message to the second serving gateway.

And F18, the second service gateway sends an update bearing response message to the second mobility management entity.

If the serving gateway is not changed during the handover procedure, that is, the second mobility management entity is connected to the first serving gateway, after step F2 is executed, steps F3 and F4 are not executed, and steps F5, F6, F7, F8, F9, and F10 are directly executed, wherein,

when the second mobility management entity receives a bearer whose existing state is suspended/unavailable in a user bearer information list sent by the first mobility management entity or receives a service limitation indication cell, the second mobility management entity carries bearer state information in an update bearer request message sent to the first service gateway, and the non-emergency service bearer in the bearer state information is suspended; or, the update bearer request message sent to the second service gateway carries the service limitation indication cell, and the second service gateway keeps the non-emergency service bearer state as the use limitation.

If the second mobility management entity stores the subscription data of the user and verifies that the user is valid (i.e. the user can access in the current area/access technology/access time), then:

the second mobility management entity sends an update bearer request message to the first service gateway, where the message carries user unlimited indication information, and the user unlimited indication information may be a bearer recovery indication to indicate that the first service gateway recovers the non-emergency service bearer.

Or, the second mobility management entity sends a Resume message to the first serving gateway, where the message carries user unlimited indication information, and the user unlimited indication information may be a bearer list that needs to be recovered.

The first serving gateway sets the non-emergency service bearer state as available, and when receiving the downlink data packet of the user, the serving gateway does not discard the data packet any more, and may notify the second mobility management entity (when the downlink data plane of the user is unavailable) or directly forward the user data to the second access network element (when the downlink data plane of the user is available).

If the state of the bearer of the non-emergency service is set to be suspended/invalid by the packet data network gateway in the first embodiment, or the gate of the data flow of the bearer of the non-emergency service is closed, after receiving the update bearer request message or the Resume message, the first service gateway:

the first service gateway sends an update bearing request message to the packet data network gateway, wherein the update bearing request message carries user unlimited indication information, and the user unlimited indication information can be bearing recovery indication; to instruct the packet data network gateway to resume the non-emergency traffic bearer.

Or the first serving gateway sends a Resume message to the packet data network gateway, where the message carries user unlimited indication information, and the user unlimited indication information may be a bearer list that needs to be restored.

After receiving the message, the packet data network gateway sets the state of the suspended bearer to be available, and when receiving the downlink data packet related to the bearer, the packet data network gateway does not discard the downlink data packet but sends the downlink data packet to the corresponding first service gateway.

Or:

The second mode is as follows:

g1, the UE sends a location update request, i.e. a routing area/tracking area update request, to the second mobility management entity.

G2, after receiving the routing area/tracking area update request, the second mobility management entity sends a context request message to the first mobility management entity, requesting user context information, where the context information includes bearer information of a user. The bearer information includes a status (bearer status) of each bearer, and the second mobility management entity can know whether the bearer is suspended/unavailable according to the bearer status. Or: the first mobility management entity carries a service limitation indication cell in the context response message, and informs the second mobility management entity that the UE is limited in the source side service and can only perform special services such as emergency service.

G3, if the user has the suspended/unavailable load, and the second mobile management entity holds the subscription data information of the user, the second mobile management entity verifies whether the user can access in the current area/access technology/access time, if so, the previous user service restriction does not exist, then:

and if the serving gateway is changed (namely the second mobility management entity after the UE is switched is connected with the second serving gateway), the second mobility management entity sends a bearer creation request message to the second serving gateway.

If the serving gateway is not changed (i.e. the second mobility management entity after the UE handover is connected to the first serving gateway), the second mobility management entity sends an update bearer request message to the first serving gateway, where the message carries a bearer recovery indication cell indicating that the first serving gateway recovers the suspended bearer, or: the second mobility management entity may also generate a Resume message to the first serving gateway, where the message may carry the recovered bearer list and notify the first serving gateway of the bearer information that needs to be recovered. And after receiving the bearer updating request message, the first service gateway sets the state of the relevant stored bearer to be available. When receiving the downlink data packet related to the user, the first service gateway may notify the second mobility management entity (that the downlink user plane is not available) or directly forward the data to the corresponding access network element (that the downlink user plane is available).

Or, if the second mobility management entity does not store the user subscription data, the validity of the user cannot be verified, which may be: if the service gateway changes, the second mobility management entity carries a service limited indication cell in a bearer establishment request message sent to the second service gateway for the suspended/unavailable bearer, and indicates that the bearer is temporarily in a suspended/unavailable state by the second service gateway. The second service gateway establishes a bearer first and then sets the state of the non-emergency service bearer as suspended; and if the service gateway is not changed, sending a bearer update request message to the second service gateway.

G4, the second serving gateway or the first serving gateway sends an update bearer request message or a Resume message to the packet data network gateway.

In this step, after receiving an update bearer request message or a Resume message, the packet data network gateway sets the original bearer suspended state as available, and when receiving a bearer-related downlink packet, the packet data network gateway does not discard the bearer and sends the bearer-related downlink packet to a corresponding serving gateway.

Or:

if the static PCC rule is configured, the packet data network gateway sets the state of the gate of the non-emergency service related data flow to open (open); for the non-emergency service bearer with GBR/MBR of 0, the packet data network gateway can initiate a bearer update process according to the PCC rule.

G5, the packet data network gateway sending an update bearer response message to the second serving gateway or the second serving gateway.

G6, the second service gateway sends a response message of establishing the load to the second mobile management entity, or the second service gateway sends a response message of updating the load to the second mobile management entity.

G7, the second mobility management entity sends a location update accept, that is, a routing area/tracking area accept message to the UE, where the message may carry a bearer recovery indication cell to indicate that the user service is no longer limited, or a bearer list that needs to be recovered, the UE determines that the user service is no longer limited according to the bearer recovery indication cell, and sets the state of the non-emergency service bearer to be available, or the UE recovers the bearer that needs to be recovered, which is indicated in the bearer list that needs to be recovered. When a user wants to perform a service, a signaling flow such as resource allocation/service request may be used to request resources.

When the user performs the emergency service, the user handover restriction on the access network element is modified or deleted, so that the user can perform the handover normally as follows:

h1, the serving gateway initiates a dedicated bearer setup Request (Create DedicatedBear Request) to the mobility management entity.

The mobility management entity may be a second mobility management entity.

H2, the mobility Management entity sends an SAE bearer Setup Request (SAE bearer Setup Request)/Session Management Request (Session Management Request) to an access network element (such as a second network element connected to a second mobility Management entity).

H3, the access network element and the UE interactively establish a radio bearer.

H4, the access network element sends SAE bearer setup response (SAE Bear setup response) to the mobility management entity.

H5, the mobility management entity knows that the bearer is an emergency service bearer, sends a user context modification request to the access network element, modifies and deletes the user switching limitation in the request, and ensures that the emergency service can be switched to a limited area or access technology.

H6, the access network element removes the handover restrictions of the user or modifies the handover restrictions of the user, such as preserving roaming restrictions, removing area restrictions, access technology restrictions and access time restrictions, and sends a user context modification response message to the mobility management entity.

H7, the UE sends direct transfer information to the access network element.

H8, the access network element transparently transmits a direct transfer message to the mobility management entity, wherein the direct transfer message is a session management response message.

H9, the mobility management entity sends a dedicated bearer setup response message to the serving gateway.

H10, after the emergency service is completed, the mobility management entity sends a message to update the handover restriction of the user on the access network element, where the message may be an Initial Context setup Request (Initial Context setup Request) message, or may be a UE Context setup Request (UE Context Modification Request) message carrying the handover restriction of the user.

H11, the access network element sends an initial Context Setup Response (initial Context Setup Response) or a UE Context modification Response (UE Context modification Response) to the mobility management entity.

The key points of this section are: after knowing that the established bearer is the emergency service bearer, the mobility management entity deletes or modifies the switching limitation on the access network element, so as to avoid the interruption of the emergency service caused by switching to the limited area. This section is not limited to the dedicated bearer establishment procedure, and may include the following scenarios, for example: in the PDN link request procedure initiated by the user, if the user carries the APN for the emergency service, the mobility management entity knows that the user needs to perform the emergency service, and at this time, the mobility management entity may also initiate a modification procedure of the user context. After the emergency service is completed, the mobility management entity adds or modifies the switching restriction on the access network element, so as to ensure that the user can only perform the service under the authorized condition.

The effective effects of this part are: when the UE carries out the emergency service, the user switching restriction on the access network element is modified or deleted, so that the user can normally carry out switching: such as when a user makes an emergency call in an E-UTRAN network and the user's access restrictions are such that the user cannot access the UTRAN. At this time, the radio signal of the E-UTRAN is not good, but the UTRAN signal is good, but due to the handover limitation, the user cannot handover to the UTRAN network, which may cause emergency call drop/quality degradation. If the mobility management entity cancels the switching restriction at this time, the user can switch to the UTRAN network, and the service quality is improved.

With reference to fig. nine, a fifth embodiment of the present invention provides a mobility management apparatus, including:

a first determining unit 901, configured to determine that a user equipment performing an emergency service is in a service limited mode;

a second determining unit 902, configured to determine, after the first determining unit determines that the user equipment performing the emergency service is in the service limited mode, according to a bearer state of the user equipment, a non-emergency service bearer of the user equipment;

a control unit 903, configured to control that the non-emergency service bearer is unavailable.

The first determining unit 901 is configured to determine that a user equipment performing an emergency service is switched from a service-unrestricted mode to a service-restricted mode; or when the user equipment which is in the emergency service moves, determining that the user equipment is in a service limited mode.

Preferably, the apparatus further comprises:

the bearer release unit is used for releasing the wireless side bearer of the emergency service when the emergency service is subjected to the gap and the user equipment is converted from the connection state to the idle state;

a service request receiving unit, configured to receive a service request sent by the user equipment;

and the first execution unit is used for recovering the wireless side bearing of the emergency service after the service request receiving unit receives the service request and controlling not to recover the non-emergency service bearing.

Or,

and the second execution unit is used for rejecting the service request of the user equipment after the service request receiving unit receives the service request.

The control unit 903 is configured to set a non-emergency service bearer state of the user equipment as unavailable after the first determining unit 901 determines that the user equipment performing the emergency service is in the service limited mode, or send user service limited indication information to the serving gateway after the first determining unit 901 determines that the user equipment performing the emergency service is in the service limited mode.

Preferably, the apparatus further comprises:

a first user-side message sending unit 904, configured to send user service restriction indication information to the user equipment after the first determining unit determines that the user equipment performing the emergency service is switched from the service non-restriction mode to the service restricted mode.

A third determining unit 905, configured to determine that the user equipment is converted from the service-limited mode to a service-unrestricted mode;

a second user-side message sending unit 906, configured to send user service non-limitation indication information to the user equipment after the third determining unit determines that the user equipment is converted from the service limited mode to the service unlimited mode.

In the fifth embodiment of the present invention, after the first determining unit 901 determines that the UE performing the emergency service is in the service limited mode, the non-emergency service bearer is reserved, and the control unit 903 controls the non-emergency service bearer to be unavailable, so as to ensure that the UE cannot perform other services except the emergency service under the condition that the user service is limited, thereby avoiding unnecessary loss of an operator, and further, so that the service can be quickly recovered when the subsequent user service is no longer limited, thereby improving the user experience.

Referring to fig. ten, a sixth embodiment of the present invention provides a data gateway, including:

a first receiving unit 1001, configured to receive user service restriction indication information sent by a serving gateway; the user service limitation indication information is sent to a service gateway after the mobility management entity determines that the user service is limited;

a determining unit 1002, configured to determine that the user service is limited according to the user service limitation indication information;

a control unit 1003, configured to control not to initiate a non-emergency service bearer establishment procedure after the determining unit 1002 determines that the user service is limited.

Preferably, the control unit 1003 includes:

a sending unit, configured to send user service restriction indication information to the PCRF;

a second receiving unit, configured to receive a message sent by the PCRF and used for notifying that a non-emergency service-related data flow is unavailable;

and the bearer control unit is used for controlling not to initiate a non-emergency service bearer establishment flow according to the message for informing that the non-emergency service related data stream is unavailable.

The data gateway of the sixth embodiment of the invention does not initiate a non-emergency service bearer establishment flow after knowing that the UE performing the emergency service is in the service limited mode, ensures that the UE cannot perform other services except the emergency service under the condition that the user service is limited, and avoids unnecessary loss of an operator.

The seventh embodiment of the present invention provides a network system, including:

In the seventh embodiment of the present invention, after the first mobility management entity determines that the UE performing the emergency service is in the service limited mode, the first mobility management entity sends the user service limited indication information to the first service gateway, and controls the first service gateway to set the non-emergency service bearer state of the user equipment as unavailable, so as to ensure that the UE cannot perform other services except the emergency service under the condition that the user service is limited, thereby avoiding unnecessary loss of an operator, and further, so that the subsequent user service is not limited any more, the service can be quickly recovered, and the user experience is improved.

An eighth embodiment of the present invention provides a network system, including:

Eighth of the embodiments of the present invention, after the first mobility management entity determines that the UE performing the emergency service is in the service limited mode, the first service gateway sends the user service limited indication information to the packet data network gateway, and controls the packet data network gateway to set the non-emergency service bearer state of the user equipment as unavailable, and/or close a gate of a data stream related to the non-emergency service, so as to ensure that the UE cannot perform other services except the emergency service under the condition that the user service is limited, avoid unnecessary loss of an operator, and so that the subsequent user service is no longer limited, the service can be quickly recovered, and user experience is improved.

An embodiment of the present invention provides a network system, including:

In the ninth embodiment of the present invention, after the first mobility management entity determines that the UE performing the emergency service is in the service restricted mode, the first service gateway sends the user service restricted indication information to the packet data network gateway, and the packet data network gateway does not initiate a non-emergency service bearer establishment procedure after knowing that the UE performing the emergency service is in the service restricted mode, so as to ensure that the UE cannot perform other services except the emergency service under the condition that the user service is restricted, thereby avoiding unnecessary loss of an operator.

It will be understood by those skilled in the art that all or part of the steps in the method for implementing the above embodiments may be implemented by hardware that is instructed to implement by a program, and the program may be stored in a computer-readable storage medium, such as a read-only memory, a magnetic or optical disk, and the like.

The bearer management method, the related device and the network system provided by the embodiment of the present invention are described in detail above, and a specific example is applied in the description to explain the principle and the implementation manner of the present invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. A bearer management method, comprising:

controlling the non-emergency traffic bearer to be unavailable.

2. The method of claim 1,

the determining that the user equipment performing the emergency service is in the service limited mode comprises:

the first mobility management entity determines that user equipment which is carrying out emergency service is converted from a service non-limited mode to a service limited mode;

or, when the user equipment which is performing the emergency service moves, the first mobility management entity determines that the user equipment is in a service limited mode.

3. The method of claim 1, wherein after determining that the user equipment conducting the emergency service is in the service restricted mode, the method further comprises:

when the user equipment is converted from a connection state to an idle state, the first mobile management entity releases the wireless side bearing of the emergency service;

and after receiving the service request sent by the user equipment, the first mobility management entity recovers the wireless side bearer of the emergency service and controls not to recover the non-emergency service bearer.

4. The method of claim 1, wherein after determining that the user equipment conducting the emergency service is in the service restricted mode, the method further comprises:

and after receiving the service request sent by the user equipment, rejecting the service request of the user equipment.

5. The method of claim 1,

the controlling that the non-emergency traffic bearer is unavailable comprises:

and the first mobility management entity sets the state of the non-emergency service bearer of the user equipment as unavailable.

6. The method of claim 1,

the controlling that the non-emergency traffic bearer is unavailable comprises:

a first mobility management entity sends user service limitation indication information to a first service gateway;

and the first service gateway sets the non-emergency service bearing state of the user equipment as unavailable according to the user service limitation indication information.

7. The method of claim 1,

the controlling that the non-emergency traffic bearer is unavailable comprises:

the first mobility management entity sends user service limitation indication information to a packet data network gateway through a first service gateway;

and the packet data network gateway sets the non-emergency service bearing state of the user equipment as unavailable and/or closes a gate of a data flow related to the non-emergency service according to the user service limitation indication information.

8. The method of claim 7,

the packet data network gateway sets the non-emergency service bearing state of the user equipment as unavailable according to the user service limitation indication information, and/or the gate for closing the non-emergency service related data flow comprises:

the packet data network gateway sends user service restriction indication information to a policy and charging function (PCRF) entity;

the PCRF sends a message for notifying that a non-emergency service related data flow gate is closed to the packet data network gateway according to the user service limitation indication information;

and the packet data network gateway sets the state of the non-emergency service bearer of the user equipment as unavailable or closes the door of the non-emergency service related data flow according to the message for informing the closing of the door of the non-emergency service related data flow.

9. The method of claim 8,

after the packet data network gateway sends the user service restriction indication information to the PCRF, the method further includes:

the PCRF sends user service restriction indication information to an application function entity (AF);

after receiving the user service limitation indication information, the AF controls not to initiate non-emergency service;

or,

and when the PCRF receives a non-emergency service request initiated by the AF, rejecting the non-emergency service request.

10. The method of claim 7,

the controlling non-emergency traffic bearers not available further comprises:

the first mobility management entity sets the parameter of the guaranteed bit rate GBR bearer of the non-emergency service to 0, and sends information indicating that the GBR bearer parameter of the non-emergency service is set to 0 to the first service gateway;

the first service gateway sets the GBR bearer parameter of the non-emergency service to 0, and sends information indicating that the GBR bearer parameter of the non-emergency service is set to 0 to the packet data network gateway;

and the packet data network gateway sets the parameter of the GBR load of the non-emergency service to be 0.

11. The method of claim 7,

after the first mobility management entity sends the user traffic restriction indication information to the packet data network gateway via the first serving gateway, the method further comprises:

the packet data network gateway sets the GBR bearer parameter of the non-emergency service to 0, and sends information indicating that the GBR bearer parameter of the non-emergency service is set to 0 to the first service gateway; the first service gateway sets the GBR bearer parameter of the non-emergency service to 0, and sends information indicating that the GBR bearer parameter of the non-emergency service is set to 0 to a first mobility management entity; and the first mobility management entity sets the parameter of the GBR load of the non-emergency service to be 0.

12. The method of claim 8, wherein:

the PCRF sends information indicating that the parameter of the GBR load of the non-emergency service is set to 0 to the packet data network gateway;

and after receiving the information indicating that the GBR bearer parameter of the non-emergency service is set to 0, the packet data network gateway sets the GBR bearer parameter of the non-emergency service to 0.

13. The method according to any one of claims 10-12, wherein:

the parameters of the GBR bearer of the non-emergency traffic comprise: GBR and/or maximum bit number MBR of GBR load of the non-emergency service.

14. The method according to any one of claims 5 to 7,

the controlling non-emergency traffic bearers not available further comprises:

the first mobility management entity deletes the GBR bearer of the non-emergency service and sends information indicating that the GBR bearer of the non-emergency service is deleted to the first service gateway;

the first service gateway deletes the GBR load of the non-emergency service and sends information indicating that the GBR load of the non-emergency service is deleted to the packet data network gateway;

and the packet data network gateway deletes the GBR load of the non-emergency service.

15. The method of claim 7,

the packet data network gateway deletes the GBR load of the non-emergency service, and sends information indicating that the GBR load of the non-emergency service is deleted to the first service gateway; the first service gateway deletes the GBR load of the non-emergency service and sends information indicating the deletion of the GBR load of the non-emergency service to a first mobility management entity; and the first mobility management entity deletes the GBR load of the non-emergency service.

16. The method of claim 8, wherein:

the PCRF sends information indicating deletion of GBR data flow of non-emergency service to the packet data network gateway;

and after receiving the information indicating that the GBR data flow of the non-emergency service is deleted, the packet data network gateway deletes the GBR data flow of the non-emergency service.

17. The method according to claim 6, wherein, during the emergency service,

when the user equipment is switched from the first mobility management entity to the second mobility management entity, the method further comprises:

the second mobile management entity acquires the user service limitation indication information from the first mobile management entity and sends the user service limitation indication information to the second service gateway;

and after the second service gateway establishes the load of the user equipment, setting the non-emergency service load state of the user equipment as unavailable.

18. The method according to claim 6, wherein, during the emergency service,

the second mobility management entity determines that the service of the user equipment is not limited under the current condition, and sends user service non-limited indication information to the first service gateway;

and the first service gateway sets the state of the non-emergency service bearer as available.

19. The method according to claim 6, wherein, during the emergency service,

and the second mobility management entity determines that the service of the user equipment is not limited under the current condition, and sends a bearer establishment request to a second service gateway, wherein the second service gateway establishes a bearer.

20. Method according to any of claims 7-9, characterized in that during the emergency service is in progress,

the second mobility management entity determines that the service of the user equipment is not limited under the current condition;

sending user service unlimited indication information to a packet data network gateway;

and the packet data network gateway sets the state of the non-emergency service bearer to be available or opens a door of a non-emergency service data flow.

21. The method of claim 20,

the packet data network gateway setting the status of the non-emergency service bearer to be available, or opening a gate for a non-emergency service data flow comprises:

the packet data network gateway sends user service unlimited indication information to the PCRF;

the PCRF opens a gate of a non-emergency service data flow and sends a message carrying the gate state of the non-emergency service data flow to the packet data network gateway;

and the packet data network gateway sets the state of the non-emergency service bearer to be available or opens the door of the non-emergency service data flow according to the door state of the non-emergency service data flow.

22. The method of claim 2, wherein when the user equipment performing the emergency service is switched from the service non-limited mode to the service limited mode, the method further comprises:

the first mobility management entity sends user service limitation indication information to user equipment;

and after receiving the user service limitation indication information, the user equipment controls not to initiate non-emergency services.

23. The method of claim 2,

after the user equipment performing the emergency service is switched from the service unrestricted mode to the service restricted mode, if the user equipment is switched to the service unrestricted mode, the method further includes:

and the first mobility management entity sends user service non-limitation indication information to the user equipment.

24. The method of claim 2,

when the user equipment which is in the emergency service is switched from the service non-limited mode to the service limited mode, the method further comprises the following steps:

the first mobility management entity sends a notification message to a first access network element, wherein the notification message is used for notifying the first access network element to delete the switching restriction or modify the switching restriction;

after controlling the non-emergency traffic bearer to be unavailable, the method further comprises:

when the emergency service is completed, the first mobility management entity determines that the service of the user equipment is no longer limited under the current condition, and sends a request for recovering the switching limitation to the first access network element.

25. The method of claim 19,

after the second serving gateway establishes the bearer, the method further includes:

when user equipment needs to perform emergency service, the second mobility management entity sends a notification message to a second access network element, wherein the notification message is used for notifying the second access network element to delete a switching limit or modify the switching limit;

and when the emergency service is completed, the second mobility management entity sends a request for recovering the switching limitation to a second access network element.

26. A bearer management method is used when user equipment moves, and is characterized by comprising the following steps:

controlling not to initiate a non-emergency service bearer establishment flow;

27. The method of claim 26,

the process of controlling not to initiate the non-emergency service bearer establishment comprises the following steps:

the packet data network gateway sends user service limitation indication information to the PCRF;

the PCRF sends a message for notifying that a non-emergency service related data flow is unavailable to the packet data network gateway;

and the packet data network gateway controls not to initiate a non-emergency service bearer establishment flow according to the message for informing that the non-emergency service related data stream is unavailable.

28. The method of claim 27,

or,

29. A mobility management apparatus, comprising:

30. The apparatus of claim 29, further comprising:

the first determining unit is used for determining that the user equipment which is carrying out the emergency service is switched from a service non-limited mode to a service limited mode; or when the user equipment which is in the emergency service moves, determining that the user equipment is in a service limited mode.

31. The apparatus of claim 29, further comprising:

a bearer release unit, configured to release a radio side bearer of the emergency service when the ue changes from the connected state to the idle state;

32. The apparatus of claim 29, further comprising:

33. The apparatus of claim 29,

the control unit is configured to set a non-emergency service bearer state of the user equipment to be unavailable after the first determining unit determines that the user equipment performing the emergency service is in the service restricted mode.

34. The apparatus of claim 29,

the control unit is configured to send user service restriction indication information to the serving gateway after the first determining unit determines that the user equipment performing the emergency service is in the service restriction mode.

35. The apparatus of claim 30, further comprising:

and the first user side message sending unit is used for sending user service limitation indication information to the user equipment after the first determining unit determines that the user equipment which is carrying out the emergency service is converted from the service unlimited mode to the service limited mode.

36. The apparatus of claim 30, further comprising:

a third determining unit, configured to determine that the user equipment is converted from the service-limited mode to a service-unlimited mode;

and the second user side message sending unit is used for sending user service non-limitation indication information to the user equipment after the third determining unit determines that the user equipment is converted from the service limited mode to the service unlimited mode.

37. A data gateway, comprising:

38. The data gateway of claim 37,

the control unit includes:

39. A network system, comprising:

40. A network system, comprising:

41. A network system, comprising: