WO2010124644A1

WO2010124644A1 - Emergency service implementation method, emergency service implementation system and network device

Info

Publication number: WO2010124644A1
Application number: PCT/CN2010/072311
Authority: WO
Inventors: 周汉; 吴问付; 孙晓姬; 王珊珊
Original assignee: 华为技术有限公司
Priority date: 2009-04-28
Filing date: 2010-04-28
Publication date: 2010-11-04
Also published as: CN101877841A; CN101877841B

Abstract

An emergency service implementation method, an emergency service implementation system and a network device are disclosed. The method includes: receiving a handover request of a User Equipment without an Universal Integrated Circuit Card (UICC-less UE), which is a terminal device has no subscriber data, determining that handover occurs between a Third Generation Partnership Project (3GPP) network and a Non-3GPP network during the emergency service by the UICC-less UE, according to obtained information of Packet Data Network (PDN) connection of the UICC-less UE, recovering the PDN connection of the emergency service of the UICC-less UE. The technical solution said above may avoid interruption phenomenon of the emergency service during the handover between the 3GPP network and the Non-3GPP network by the UICC-less UE.

Description

Emergency service implementation method, system and network device

Technical field

The present invention relates to the field of network communication technologies, and particularly relates to an emergency service implementation method, an emergency service implementation system, and a network device.

Background technique

When the UE (User Equipment) is attached to the 3GPP network or the Non-3GPP (non-3GPP) network, it is usually required to obtain the subscription data of the UE from the HSS (Home Subscriber Service), for example, the MME in the 3GPP network (Mobility). Management Entity, the mobility management entity) acquires the subscription data of the UE from the HSS. However, the terminal device UICC less UE (the user equipment of the default subscription data) without the subscription data does not acquire the subscription data of the UE from the HSS when the 3GPP network attachment or the Non-3GPP network is attached. At this time, the UICC less UE only Ability to conduct emergency services, such as emergency call services.

In the process of implementing the present invention, the inventor has found that when the UICC less UE performs emergency services (such as emergency call service), if the UICC less UE moves between the 3GPP network or the Non-3GPP network, an emergency service interruption is caused. The following describes the phenomenon in which the UICC less UE moves from the 3GPP network to the Non-3GPP network, and the emergency call service interruption occurs when the UICC less UE moves from the Non_3GPP network to the 3GPP network.

In the case that the UICC less UE is attached to the 3GPP network, the MME selects a PDN GW (Packet Data Network Gateway) for the UICC less UE according to the emergency APN (Access Point Name) information carried by the UICC less UE in the attach request. Packet data network gateway), and establish a PDN connection. Since the UICC less UE does not have the SI (International Mobile Subscriber Identity) information, it is impossible to select an HSS for the UICC less UE, and the selected PDN GW information cannot be registered in the HSS. After that, the UICC less UE moves to the Non-3GPP network, because the Non_3GPP network cannot obtain the UICC in the 3GPP network. The PDN of the emergency call established by the UE is connected to the selected PDN GW information. Therefore, the Non_3GPP network cannot restore the PDN connection established in the 3GPP network for the emergency call of the UICC less UE, thereby causing the emergency call service to be interrupted.

Similarly, in the case where the UICC less UE is attached to the Non-3GPP network, since the Non_3GPP network cannot select an HSS for the UICC less UE, the PDN GW information selected for the emergency call cannot be registered in the HSS. After that, the UICC less UE moves to the 3GPP network, and since the MME cannot obtain the PDN GW information selected by the PDN connection established for the emergency call of the UICC less UE in the Non_3GPP network, the MME cannot be restored in the Non-3GPP network. A PDN connection established for an emergency call of the UICC less UE, thereby causing an emergency call service interruption.

Summary of the invention

The embodiments of the present invention provide an emergency service implementation method, system, and network device, which can avoid the interruption of emergency services of the UICC less UE.

The emergency service implementation method provided by the embodiment of the present invention includes:

Receiving a handover request of a terminal device UICC less UE without subscription data;

Determining that the UICC less UE performs a handover between the 3GPP network and the non-3GPP network in the process of performing an emergency service;

And recovering the PDN connection of the emergency service of the UICC less UE according to the acquired information of the packet data network PDN connection of the UICC less UE.

An emergency service implementation system provided by an embodiment of the present invention includes:

a first mobility management entity, configured to send, by the PDN connection, a packet data network for the emergency service of the UICC less UE, to send information required to establish a PDN connection to the storage network element;

a second mobility management entity, configured to receive the UICC less UE handover request, determine that the UICC less UE performs a handover between a 3GPP network and a non-3GPP network in performing an emergency service; according to the acquired UICC less UE The information of the PDN connection recovers the PDN connection of the UE. A network device provided by an embodiment of the present invention includes:

Establishing a module, configured to establish a packet data network PDN connection for emergency services of the UICC less UE;

And a sending module, configured to send, to the storage network element, the information required to establish a PDN connection for the established PDN connection.

A network device provided by an embodiment of the present invention includes:

a receiving module, configured to receive a handover request of a UICC less UE;

a determining module, configured to determine that the UICC less UE has a handover between the 3GPP network and the non-3GPP network during the process of performing an emergency service;

And a recovery module, configured to recover the PDN connection of the emergency service of the UICC less UE according to the obtained information of the PDN connection of the packet data network of the UICC less UE. According to the description of the foregoing technical solution, the information required to establish a PDN connection corresponding to the packet data network PDN connection successfully established by storing the emergency service for the UICC less UE at the predetermined network element is performed, thereby performing an emergency service process in the UICC less UE. When moving between the 3GPP network and the non-3GPP network, the information required for establishing the PDN connection may be obtained from the predetermined network element. Further, the obtained information may be used to perform PDN connection recovery; finally, the emergency service of the UICC less UE is avoided. The interruption phenomenon has improved the reliability of emergency services. DRAWINGS

1 is a flowchart of an emergency service implementation method according to Embodiment 1 of the present invention;

2a is a flowchart of a UICC less UE accessing and initiating an emergency call service on a 3GPP network according to Embodiment 2 of the present invention; 2b is a flowchart of a UICC less UE accessing and initiating an emergency call service on a 3GPP network according to Embodiment 4 of the present invention;

FIG. 3a is a flow chart of attaching an attachment type to Handover after the UICC less UE moves from the 3GPP network to the non-3GPP network in the emergency call process according to the second embodiment of the present invention;

FIG. 3b is a flowchart of attaching an attachment type to Handover after the UICC less UE moves from the 3GPP network to the non-3GPP network in the emergency call process according to Embodiment 4 of the present invention;

4a is a flow chart of a UICC less UE accessing and initiating an emergency call service on a non-3GPP network according to Embodiment 3 of the present invention;

4b is a flow chart of a UICC less UE accessing and initiating an emergency call service on a non-3GPP network according to Embodiment 5 of the present invention;

FIG. 5a is a flowchart of attaching an attachment type to Handover after a UICC less UE moves from a non-3GPP network to a 3GPP network in an emergency call process according to Embodiment 3 of the present invention;

FIG. 5b is a flowchart of attaching an attachment type to Handover after the UICC less UE moves from a non-3GPP network to a 3GPP network in an emergency call process according to Embodiment 5 of the present invention;

6 is a schematic diagram of an emergency call service implementation system according to Embodiment 10 of the present invention;

7 is a schematic structural diagram of a network device according to Embodiment 11 of the present invention;

8A, B, and C are schematic structural diagrams of a transmitting module according to Embodiment 11 of the present invention;

9 is a schematic diagram of a network device according to Embodiment 12 of the present invention;

10A and FIG. 10B are schematic diagrams showing the structure of a recovery module according to Embodiment 12 of the present invention.

detailed description

Embodiments of the present invention will be described below with reference to the accompanying drawings.

Embodiment 1 The method for implementing an emergency service. This embodiment and the following embodiments all use emergency services as emergency calls. The service is described as an example. Other types of emergency services are similar to the implementation process of the emergency call service, and the description is not repeated. The flow of the method for implementing the emergency call service is as shown in FIG. 1.

Step 100: The PDN connection successfully established for the emergency call of the UICC less UE, the mobility management entity sends the information required for establishing the PDN connection to the storage network element. The mobility management entity is responsible for obtaining the network devices that need to establish the information required for the PDN connection. For example, the mobility management entity is an MME in a 3GPP network; for example, the mobility management entity is a mobile access gateway in a non-3GPP network or the like.

The successfully established PDN connection may be a PDN connection successfully established for an emergency call of the UICC less UE in the initial attach process of the emergency call by the UICC less UE, or a 3GPP network and a non-3GPP that make an emergency call in the UICC less UE. In the process of handover attachment between networks, the PDN connection is successfully restored for the emergency call of the UICC less UE.

The above information required to establish a PDN connection includes: access point name APN and PDN GW information. The PDN GW information is such as the PDN GW identifier or the PDN GW address.

The storage network element may be a UICC less UE or a home subscription server. When the storage network element is a home subscriber network server, the home subscriber network server may be a home subscriber network server configured by default in the mobility management entity, or may be selected by the mobility management entity according to the top SI of the UICC less UE. The home server is subscribed to the home. In addition, when the storage network element is the home subscriber network server, the home subscriber network server may store the correspondence between the top SI and the APN and PDN GW information, and may also store the International Mobile Equipment Identifier (B1EI). Correspondence with APN and PDN GW information. The top SI and top EI are used to find the information needed to establish a PDN connection corresponding to the successfully established PDN connection.

In the case where the home subscriber server is the home subscriber server selected by the mobility management entity according to the top SI, the mobility management entity needs to allocate the top SI for the UICC less UE making the emergency call. The mobility management entity may allocate B1SI to the UICC less UE during the initial attach procedure of the UICC less UE for making an emergency call.

If the mobility management entity assigns an MSI to the UICC less UE, the mobility management entity shall notify the assigned B1SI To the UICC less UE, after the UICC less UE sends an attach request to the mobility management entity due to the movement between the 3GPP network and the non-3GPP network, the top SI that the mobility management entity allocates should be carried in the attach request. In this way, during the subsequent PDN connection recovery process, the mobility management entity may select the home subscriber server according to the top SI carried in the attach request, and request information about the PDN connection to the selected home subscriber server. At this time, the corresponding attribute of the top SI and the APN and PDN GW information may be stored in the selected home subscriber server.

In the case that the home subscriber network server is the home subscriber network server selected by the mobility management entity according to the top SI, since there is no subscription information of the UICC less UE in the home subscriber server, the home registration is performed according to the usual processing manner. After receiving the top SI, APN, and PDN GW information, the user server does not perform storage processing, and also returns an error message to the mobility management entity. In order for the home subscriber server to correctly store the top SI, APN and PDN GW information, the mobility management entity may carry an indication in the message when transmitting the message carrying the top SI, APN and PDN GW information to the home subscriber server. The information is used to indicate that the home subscriber server does not store the subscription information of the UICC less UE, and the top SI, APN, and PDN GW information should also be stored.

In the case where the home subscriber network server is the default home subscriber network, the mobility management entity may not allocate the BiSI for the UICC less UE that makes the emergency call. Whether the UICC less UE performs the initial attach process of the emergency call or the UICC less UE performs the handover attach procedure of the emergency call, the mobility management entity shall send an emergency call to the default home subscription server server as the UICC less UE. The information required for establishing a PDN connection corresponding to the successfully established PDN connection is used to store the information required for establishing a PDN connection corresponding to the successfully established PDN connection in the default home subscriber network. At this time, the mapping between the top EI and the APN and PDN GW information may be stored in the default home subscriber server.

In the case that the home subscriber network server is the default home subscriber network, the same is true, because the subscriber subscriber server does not have the subscription information of the UICC less UE, the subscriber is subscribed according to the usual processing manner. After receiving the top EI, APN, and PDN GW information, the server will not perform storage processing, and will Return an error message to the mobility management entity. In order for the home subscriber server to correctly store the top EI, APN and PDN GW information, the mobility management entity may carry the indication in the message when transmitting the message carrying the top EI, APN and PDN GW information to the home subscriber server. The information is used to indicate that the home subscriber server does not store the subscription information of the UICC less UE, and the top EI, APN, and PDN GW information should also be stored. It should be noted that the message sent by the mobility management entity may not carry the indication information. In this case, when the home subscriber server determines that the message carries the top EI, the top EI, APN, and PDN GW information in the message Perform storage processing.

In the case that the storage network element is a UICC less UE, the mobility management entity shall send the APN and PDN GW information corresponding to the successfully established PDN connection to the storage network element for the emergency call of the UICC less UE. At this time, the mobility management entity may not allocate BiSI for the UICC less UE. Thereafter, the UICC less UE shall carry the top EI, APN and PDN GW information in the attach request when transmitting the attach request to the mobility management entity due to the movement between the 3GPP network and the non-3GPP network. The top EI can be used by the PDN GW for PDN connection recovery operations. It should be noted that the APN and PDN GW information may also be sent to the mobility management entity through other messages than the attach request.

Step 110: After receiving the attach request, the mobility management entity determines, by using the information carried in the attach request, whether the attach request is: UICC less an attach request sent by the UE to move between the 3GPP network and the non-3GPP network during the emergency call, For example, the mobility management entity determines the type of the UE that sends the attach request and the type of the attach request to determine whether the UE that sends the attach request is a UICC less UE, and whether the attach request is a handover type attach request. The handover type attachment request herein refers to an attachment request sent to the mobility management entity due to the UE moving between the 3GPP network and the non-3GPP network during the emergency call by the UE.

If the result of the above determination is that the UE that sends the attach request is the UICC less UE, and the attach request is an attach request sent by the UE to move between the 3GPP network and the non-3GPP network during the emergency call, go to step 120, otherwise Go to step 130.

The mobility management entity may use existing methods to determine the UE type and the type of the attachment request, and determine the specific The breaking process will not be described in detail here.

Step 120: The mobility management entity acquires, from the storage network element, information required for establishing a PDN connection corresponding to the UE that sends the attach request, and performs a recovery processing operation on the PDN connection of the emergency call of the UE that sends the attach request according to the information.

When the storage network element is a UICC less UE, the mobility management entity may obtain the top EI, APN, and PDN GW information from the message sent by the UICC less UE (such as in the attach request), after which the mobility management entity may utilize the APN and PDN GW information. Determining the PDN GW that establishes the PDN connection, and then the mobility management entity instructs the determined PDN GW to perform a recovery process on the PDN connection corresponding to the top EI (ie, the PDN connection corresponding to the top EI is switched).

When the storage network element is a home subscriber network server, the mobility management entity may obtain the B1EI or BiSI from the message sent by the UICC less UE (such as in the attach request). If the message sent by the UICC less UE is nisi, the mobility management entity may select the home subscriber server according to the top SI, and then the mobility management entity requests the APN and the PDN GW corresponding to the B1SI from the selected home subscriber server. The information, in this way, the mobility management entity can determine the PDN GW that establishes the PDN connection by using the APN and PDN GW information obtained by the request, and then the mobility management entity instructs the determined PDN GW to perform recovery processing on the PDN connection corresponding to the top SI. If the message sent by the UICC less UE carries the IMEI, the mobility management entity may request the APN and PDN GW information corresponding to the top EI from the home subscriber network that is set by default, so that the mobility management entity can obtain the request by using the request. The APN and PDN GW information determines the PDN GW that establishes the PDN connection, and then the mobility management entity instructs the determined PDN GW to perform recovery processing on the PDN connection corresponding to the top EI.

The emergency service of the UICC less UE may also be restored according to the pre-made default packet data network gateway PDN GW.

PDN connection.

Step 130: The method for implementing the emergency call service in this embodiment ends. The mobility management entity can perform subsequent processing operations in accordance with the existing processing flow for emergency calls.

It should be noted that, after the PDN connection is successfully restored, the information required to establish a PDN connection corresponding to the PDN connection after the recovery process should be sent to the storage network element, that is, return to step 100, and continue to wait for receiving the attach request. . In addition, in step 130, the mobility management entity may allocate an MSI to the UICC less UE in the case that the received attach request is an initial attach request sent by the UICC less UE for making an emergency call, and perform subsequent according to the B1SI. The PDN connection establishment process. After the PDN connection is successfully established, the mobility management entity sends the information required for establishing the PDN connection corresponding to the successfully established PDN connection to the storage network element, that is, returns to step 100, and continues to wait for the attachment request sent by the user equipment.

It should be noted that, in the first embodiment, the attach request with the type of the switch is a switch request, and the attach request with the attach type of the switch in the first embodiment may also be another form of the switch request, such as a PDN. The connection type is a PDN connection request for switching, and the like. The attachment request whose attachment type is switched as described in the following embodiments may be another type of handover request, and the attachment requests in the following embodiments will not be repeatedly described one by one. Also, the operations of steps 100, 110, and 120 in the first embodiment may be performed by the same mobility management entity, or may be performed by two different mobility management entities; in the case of being performed by the same mobility management entity, step 100 The UICC less UE in the steps 110 and 120 does not refer to the same UICC less UE; in the case of being executed by two mobility management entities, the UICC less UE in step 100 and the steps 110 and 120 UICC less UE refers to the same UICC less UE.

The description of the first embodiment shows that the information required to establish a PDN connection corresponding to the packet data network PDN connection successfully established by storing the emergency call for the UICC less UE at the predetermined network element, thereby performing an emergency call process in the UICC less UE. When moving between the 3GPP network and the non-3GPP network, the information required for establishing the PDN connection may be obtained from the predetermined network element. Further, the obtained information may be used for PDN connection recovery; finally, the emergency call of the UICC less UE is avoided. The disruption of the service improves the reliability of the emergency call service.

Embodiment 2: The UICC less UE accesses and initiates an emergency call service in the 3GPP, and the mobility management network element is UICC less

The UE dynamically allocates a nisi, and the mobility management network element selects a home subscriber server according to the allocated nisi, and registers the PDN GW information corresponding to the PDN connection established for the emergency call of the UICC less UE to the selected home registration. In the user server, thereafter, the UICC less UE moves from the 3GPP network to the non-3GPP network; in the above case, the emergency call service implementation flow is as shown in FIG. 2a and FIG. 3a.

Figure 2a shows the flow of the UICC less UE accessing and initiating the emergency call service in the 3GPP network, and the initial attach procedure of the gpUICC less UE in the 3GPP network.

Step 1: The UE sends an attach request message to the mobility management network element, where the attach request message carries the information of the emergency call.

Step 2: After the mobility management network element determines that the UE is the UICC less UE, and the attach request message carries the emergency call information, the mobility management network element dynamically allocates an MSI to the UE, and the mobility management network element can A top si is selected from the reserved nisi to be allocated to the UE to prevent the dynamically allocated nisi from colliding with the top si of other normal UEs. The mobility management network element sends a create default bearer request message to the serving gateway.

Step 3: The serving gateway sends a create default bearer request message to the packet data network gateway.

Step 4: After receiving the Create Default Bearer Request message, the packet data network gateway returns a Create Default Bearer Response message to the serving gateway.

Step 5: The service gateway returns a default bearer response message to the mobility management network element.

Step 6: The mobility management network element returns an attach accept message to the UE, where the attach accept message carries a nisi dynamically allocated by the mobility management network element to the UE.

Step 7. After receiving the attach accept message, the UE returns an attach complete message to the mobility management network element.

Step 8. The mobility management network element sends an update bearer request message to the serving gateway.

Step 9. After receiving the update bearer request message, the serving gateway returns an update bearer response message to the mobility management network element.

Step 10: The mobility management network element sends a notification request message to the home subscriber network server, where the notification request message carries the APN and PDN GW addresses corresponding to the PDN connection successfully established by the UE, and carries the indication information, so as to facilitate The APN and PDN GW addresses are registered to the home subscriber server. The indication information is, for example, UICC less EM (:. When the indication information is valid, it indicates that: the registration is performed by the UICC less UE performing an emergency call, and the home subscriber server should perform the registration operation, and does not need to return. Error message.

Step 11: After receiving the notification request message, the home subscriber server registers the APN and the PDN GW address to the home subscriber server according to the indication information carried in the message, for example, the home subscriber server obtains the notification request message. The top SI, APN, and PDN GW addresses, and the correspondence between the top SI information, the APN, and the PDN GW information is saved. The home subscriber server returns a notification response message to the mobility management network element.

FIG. 3a shows an attachment process in which the UICC less UE initiates an attach type of Handover after moving from the 3GPP network to the non-3GPP network during the emergency call.

Step 1: The UE triggers the attach procedure of the mobile access gateway, that is, the UE sends an attach request to the mobile access gateway, and the attach type carried in the attach request is a Handover, and the attach request carries the mobility management network element as the UE dynamic The top SI assigned.

Step 2: After receiving the attach request, the mobile access gateway determines that the attach request carries the information of the emergency call, the UE is the UICC less UE, and the attach type is Handover, and the mobile access gateway carries the information according to the attach request. The nisi selects the home subscriber network server and uses the nisi to obtain the APN and the PDN GW identity (or PDN GW address) from the selected home subscriber server.

Step 3: The mobile access gateway sends a proxy binding request message to the packet data network gateway according to the APN and the PDN GW identifier obtained from the home subscriber server.

Step 4: After receiving the proxy binding request message, the packet data network gateway returns a proxy binding confirmation message to the mobile access gateway.

Step 5: The mobile access gateway interacts with the UE to notify the UE that the attach procedure is successfully completed, that is, the PDN connection of the UE is successfully restored. The description of the second embodiment shows that the mobility management network element dynamically allocates the top SI for the UICC less UE that accesses and initiates the emergency call service in the 3GPP, so that the mobility management network element can select the home for the UICC less UE according to the top SI. The subscription host server, the mobility management network element sends the indication information, the APN and the PDN GW information to the selected home subscriber server, so that the home subscriber server can successfully register the APN and PDN GW information according to the indication information; When the mobility management network element sends the top SI to the UICC less UE, and the UICC less UE moves from the 3GPP network to the non-3GPP network during the emergency call, the UICC less UE sends the received B1SI to the mobile access gateway. The mobile access gateway may select the corresponding home subscription server according to the B1SI, and obtain the APN and PDN GW information from the selected home subscription server. Further, the mobile access gateway may use the acquired information to perform the PDN connection. Recovery; finally avoiding the interruption of the emergency call service of the UICC less UE, improving the tightness The reliability of call traffic.

Embodiment 3: The UICC less UE accesses and initiates an emergency call service in the non-3GPP, and the mobile access gateway is UICC less

The UE dynamically allocates a nisi, and the mobile access gateway selects a home subscriber server according to the allocated top si, and registers the PDN GW information corresponding to the PDN connection established for the emergency call of the UICC less UE to the selected home subscriber server. Thereafter, the UICC less UE moves from the non-3GPP network to the 3GPP network; in the above case, the emergency call service implementation flow is as shown in FIG. 4a and FIG. 5a.

Figure 4a shows the flow of the UICC less UE accessing and initiating an emergency call service on a non-3GPP network, and the initial attach procedure of the gpUICC less UE on the non-3GPP network.

Step 1. The UE finds and selects a mobile access gateway in the non-3GPP network.

Step 2: The UE triggers the attach procedure of the mobile access gateway, that is, the UE sends an attach request to the mobile access gateway, where the attach request carries the information of the emergency call.

Step 3: After the mobile access gateway determines that the UE is a UICC less UE, and the attach request message carries the information of the emergency call, the mobile access gateway dynamically allocates an IMSI to the UE, and the mobile access gateway may be retained from the reserved B1SI A nisi is selected to be allocated to the UE to avoid the dynamically allocated IMSI colliding with the nisi of other normal UEs. The mobile access gateway sends a proxy binding request message to the selected packet data network gateway, where the proxy binding request message carries the top SI dynamically allocated by the mobile access gateway to the UICC less UE.

Step 4: After receiving the proxy binding request message, the packet data network gateway selects the home subscriber server according to the top SI carried in the proxy binding request message. The packet data network gateway requests the selected home subscriber network server to update the packet data network gateway information (such as updating the address of the packet data network gateway), that is, the packet data network gateway sends an update PDN GW address message to the home subscriber server, the update packet. The data network gateway address message carries the indication information, such as the UICC less EM (:. When the indication information is valid, the indication is: the update registration is an update registration performed by the UICC less UE to perform an emergency call, belonging The home subscriber server should perform the update registration operation and does not need to return an error message. After receiving the update PDN GW address message, the home subscriber server registers the APN and PDN GW addresses to the home registration according to the indication information carried in the message. In the user server, the home subscriber network server obtains the BiSI, APN, and PDN GW addresses from the update PDN GW address message, and updates the correspondence between the saved top SI information, the APN, and the PDN GW information.

Step 5: The packet data network gateway sends a proxy binding acknowledgement message to the mobile access gateway.

Step 6: After receiving the proxy binding acknowledgement message, the mobile access gateway performs information exchange with the UE to notify the UE that the initial attach procedure is successfully completed, that is, the PDN connection is successfully established for the emergency call of the UE. During the information exchange, the mobile access gateway may send an attach complete message to the UE, where the attach complete message carries the nisi dynamically allocated by the mobile access gateway for the UE.

FIG. 5a shows an attachment process in which the UICC less UE initiates an attach type of Handover after moving from a non-3GPP network to a 3GPP network during an emergency call.

Step 1: The UE sends an attach request message to the mobility management network element, and the attach type carried in the attach request is a Handover, and the attach request carries a top SI dynamically allocated by the mobile access gateway to the UE. Step 2: After the mobility management network element determines that the attach request carries the emergency call information, the UE is the UICC less UE, and the attachment type is Handover, the mobility management network element selects the home location according to the top SI carried in the attach request. The subscriber server is subscribed, and the APN and the PDN GW identity (or PDN GW address) are obtained from the selected home subscriber server by using the B1SI.

Step 3: The mobility management network element sends a create default bearer request message to the serving gateway.

Step 4: The serving gateway sends a create default bearer request message to the packet data network gateway.

Step 5: After receiving the Create Default Bearer Request message, the packet data network gateway returns a Create Default Bearer Response message to the serving gateway.

Step 6. The service gateway returns a default bearer response message to the mobility management network element.

Step 7. After receiving the Create Default Bearer Response message, the mobility management network element returns an attach accept message to the UE. Step 8: After receiving the attach accept message, the UE returns an attach complete message to the mobility management network element.

Step 9. The mobility management network element sends an update bearer request message to the serving gateway.

Step 10: After receiving the update bearer request message, the serving gateway returns an update bearer response message to the mobility management network element.

The description of the foregoing embodiment 3 shows that the mobile access gateway dynamically allocates the top SI for the UICC less UE that accesses and initiates the emergency call service in the non-3GPP, so that the mobile access gateway can select the home location for the UICC less UE according to the top SI. The subscriber server, the mobile access gateway sends the indication information, the APN and the PDN GW information to the selected home subscriber server, so that the home subscriber server can successfully register the APN and PDN GW information according to the indication information; When the ingress gateway sends the top SI to the UICC less UE, and the UICC less UE moves from the non-3GPP network to the 3GPP network during the emergency call, the UICC less UE sends the received top SI to the mobility management network element to make the mobile The mobility management network element may select the corresponding home subscription server according to the top SI, and obtain the APN and PDN GW information from the selected home subscription server. Further, the mobility management network element may use the acquired information. The PDN connection recovery is performed; the interruption of the emergency call service of the UICC less UE is finally avoided, and the reliability of the emergency call service is improved.

Embodiment 4: The UICC less UE accesses and initiates an emergency call service in the 3GPP, and the mobility management network element does not allocate a top SI to the UICC less UE. After the mobility management network element selects the packet data network gateway for the UE, the APN and the APN are The packet data network gateway information is sent to the UE. Thereafter, the UICC less UE moves from the 3GPP network to the non-3GPP network, and the UE provides the received APN and packet data network gateway information to the mobility management network element. Embodiment 4 will be described below with reference to Fig. 2b and Fig. 3b.

Figure 2b shows the flow of the UICC less UE accessing and initiating the emergency call service in the 3GPP network, and the initial attach procedure of the gpUICC less UE in the 3GPP network.

Step 2: After the mobility management network element determines that the UE is a UICC less UE, and the attach request message carries the information of the emergency call, the mobility management network element sends a create default bearer request message to the serving gateway.

Step 6: The mobility management network element returns an attach accept message to the UE, where the attach accept message carries the packet data network gateway information selected by the APN and the mobility management network element for the UE.

Step 9. After receiving the update bearer request message, the serving gateway returns an update bearer response to the mobility management network element. Message.

FIG. 3b shows an attachment process in which the UICC less UE initiates an attach type of Handover after moving from the 3GPP network to the non-3GPP network during the emergency call.

Step 1: The UE triggers the attach procedure of the mobile access gateway, that is, the UE sends an attach request to the mobile access gateway, where the attach request carries the attach type, and the attach request carries the mobility management network element to send to the UE. APN and packet data network gateway information.

Step 2: After receiving the attach request, the mobile access gateway determines that the attach request carries the APN information and the PDN GW information, and the mobile access gateway sends a proxy binding request to the packet data network gateway according to the APN information and the PDN GW information. Message.

Step 3. After receiving the proxy binding request message, the packet data network gateway returns a proxy binding confirmation message to the mobile access gateway.

Step 4: The mobile access gateway interacts with the UE to notify the UE that the attach procedure is successfully completed, that is, the PDN connection of the UE is successfully restored.

The description of the foregoing embodiment 4 shows that the mobility management network element selects the APN and the PDN GW for the UICC less UE that accesses and initiates the emergency call service in the 3GPP, and sends the selected APN and PDN GW information to the UICC less UE. When the UE moves from the 3GPP network to the non-3GPP network during the emergency call, the UE can send the received APN and PDN GW information to the mobile access gateway, so that the mobile access gateway can obtain the APN from the received message. And the PDN GW information, so that the mobile access gateway can use the acquired information to perform PDN connection recovery; finally, the interruption of the emergency call service of the UICC less UE is avoided, and the reliability of the emergency call service is improved.

Embodiment 5: The UICC less UE accesses and initiates an emergency call service in the non-3GPP, and the mobile access gateway does not allocate BiSI to the UICC less UE. After the mobile access gateway selects the packet data network gateway for the UE, the APN and the packet data are used. The network gateway information is sent to the UE. Thereafter, the UICC less UE moves from the non-3GPP network to the 3GPP network, and the UE will receive the The APN and packet data network gateway information is provided to the mobile access gateway. Embodiment 5 will be described below with reference to FIG. 4b and FIG. 5b.

Figure 4b shows the flow of the UICC less UE accessing and initiating the emergency call service on the non-3GPP network, and the initial attach procedure of the gpUICC less UE in the non-3GPP network.

Step 2: The UE triggers the attach procedure of the mobile access gateway, that is, the UE sends an attach request to the mobile access gateway, where the attach request carries the information of the emergency call and the B1EI.

Step 3: After the mobile access gateway determines that the UE is a UICC less UE, and the attach request message carries the emergency call information, the mobile access gateway selects a packet data network gateway for the UE, and the mobile access gateway selects the packet. The data network gateway sends a proxy binding request message. The proxy binding request message carries a top EI.

Step 4: The packet data network gateway sends a proxy binding acknowledgement message to the mobile access gateway.

Step 5: After receiving the proxy binding acknowledgement message, the mobile access gateway performs information exchange with the UE to notify the UE that the initial attach procedure is successfully completed, that is, the PDN connection is successfully established for the emergency call of the UE. In the information exchange process, the mobile access gateway may send an attach complete message to the UE, where the attach complete message carries the packet data network gateway information selected by the APN and the mobile access gateway for the UE. The UE shall update its saved APN and PDN GW information according to the information carried in the Attachment Complete message.

FIG. 5b shows an attachment process in which the UICC less UE initiates an attach type of Handover after moving from a non-3GPP network to a 3GPP network during an emergency call.

Step 1: The UE sends an attach request message to the mobility management network element, and the attach type carried in the attach request is Handover, and the attach request carries the packet data network gateway information selected by the UE and the mobile access gateway for the UE.

Step 2: The mobility management network element carries the APN information and the packet data network gateway information in determining the attach request, After the UE is the UICC less UE and the attachment type is Handover, the mobility management network element sends a Create Default Bearer Request message to the serving gateway.

Step 6: After receiving the Create Default Bearer Response message, the mobility management network element returns an attach accept message to the UE. Step 7. After receiving the attach accept message, the UE returns an attach complete message to the mobility management network element.

The description of the foregoing embodiment 5 shows that the mobile access gateway selects the APN and the PDN GW for the UICC less UE that accesses and initiates the emergency call service in the non-3GPP, and sends the selected APN and PDN GW information to the UICC less UE. When the UE moves from the non-3GPP network to the 3GPP network during the emergency call, the UE can send the received APN and PDN GW information to the mobility management network element, so that the mobility management network element can receive the received message. The APN and PDN GW information is obtained, so that the mobility management network element can use the acquired information to perform PDN connection recovery; finally, the interruption of the emergency call service of the UICC less UE is avoided, and the reliability of the emergency call service is improved.

Embodiment 6: The UICC less UE accesses and initiates an emergency call service in the 3GPP network, and the mobility management network element does not allocate the top SI to the UICC less UE. After the mobility management network element selects the packet data network gateway for the UE, it will be the UICC less The PDN GW information corresponding to the PDN connection established by the emergency call of the UE is registered in the default home subscriber network. Thereafter, the UICC less UE moves from the 3GPP network to the non-3GPP network. The mobility access gateway obtains the APN and PGW GW information from the default home subscription server to recover the PDN connection of the emergency call. Still attached below Embodiment 6 is illustrated in Fig. 2a and Fig. 3a.

Step 1: The UE sends an attach request message to the mobility management network element, where the attach request message carries the information of the emergency call. The attach request message also carries a top EI.

Step 6. The mobility management network element returns an attach accept message to the UE.

Step 10: The mobility management network element sends a notification request message to the default home subscriber network server, where the notification request message carries the APN and PDN GW addresses corresponding to the PDN connection successfully established by the UE, and carries the indication information. In order to register the APN and PDN GW addresses to the home subscriber server. The indication information is UICC less EMC. When the indication information is valid, it indicates that: This registration is a registration performed by the UICC less UE to perform an emergency call, and the home subscriber server should perform a registration operation, and does not need to return an error message.

Step 11: After receiving the notification request message, the default home subscription server server is carried according to the message. The indication information registers the APN and the PDN GW address into the home subscriber server, for example, the home subscriber server obtains the top EI, APN, and PDN GW addresses from the notification request message, and saves the top EI information, the APN, and the PDN GW information. Correspondence relationship. The home subscriber server returns a notification response message to the mobility management network element.

Step 1: The UE triggers the attach procedure of the mobile access gateway, that is, the UE sends an attach request to the mobile access gateway, and the attach type carried in the attach request is Handover, and the attach request carries the top EI.

Step 2: After receiving the attach request, the mobile access gateway determines that the attach request carries the emergency call information, the UE is the UICC less UE, and the attach type is Handover, and the mobile access gateway uses the top EI from the default. The APN and the PDN GW identity (or PDN GW address) are obtained at the home subscriber network of the home subscriber.

Step 3. The mobile access gateway sends a proxy binding request message to the packet data network gateway according to the APN and the PDN GW identifier obtained from the default home subscription server.

Step 5: The mobile access gateway interacts with the UE to notify the UE that the attach procedure is successfully completed, that is, the PDN connection of the UE is successfully restored.

As described in the foregoing Embodiment 6, the mobility management network element selects the APN and the PDN GW for the UICC less UE that accesses and initiates the emergency call service in the 3GPP, and sends the indication information, the APN, and the default home subscriber server. The PDN GW information enables the home subscriber network server to successfully register the APN and PDN GW information according to the indication information; thus, when the UICC less UE performs an emergency call, when moving from the 3GPP network to the non-3GPP network, the mobile access gateway may The APN and the PDN GW information are obtained from the default home subscriber network server. Further, the mobile access gateway can use the obtained information to perform PDN connection recovery. Finally, the emergency call service of the UICC less UE is avoided. The phenomenon of disconnection improves the reliability of the emergency call service.

Embodiment 7: The UICC less UE accesses and initiates an emergency call service in a non-3GPP network, and the mobile access gateway does not allocate a top SI to the UICC less UE, and the mobile access gateway selects a packet data network gateway for the UE, and is a UICC less UE. The PDN GW information corresponding to the PDN connection established by the emergency call is registered in the default home subscriber server. Thereafter, the UICC less UE moves from the non-3GPP network to the 3GPP network. The mobility management network element obtains APN and PGW GW information from the default home subscription subscriber server to recover the PDN connection of the emergency call. Embodiment 7 will be described below with reference to Fig. 4a and Fig. 5a.

Step 3: After the mobile access gateway determines that the UE is a UICC less UE, and the attach request message carries the information of the emergency call, the mobile access gateway selects the packet data network gateway for the UE. The mobile access gateway sends a proxy binding request message to the selected packet data network gateway, where the proxy binding request message carries a top EI.

Step 4: After the packet data network gateway receives the proxy binding request message, the packet data network gateway requests the default home subscription server to save the APN and the packet data network gateway information (such as updating the address of the packet data network gateway), that is, the packet. The data network gateway sends an update PDN GW address message to the default home subscriber network server, where the update packet data network gateway address message carries the ΒίΕΙ, APN, and PDN GW addresses. After receiving the update PDN GW address message, the default home subscriber server uses the top EI to register the APN and PDN GW address updates carried in the message to the home subscriber server, such as the home subscriber server to update the PDN. The top EI, APN, and PDN GW addresses are obtained in the GW address message, and the correspondence between the top EI information, the APN, and the PDN GW information is updated. Step 5: The packet data network gateway sends a proxy binding acknowledgement message to the mobile access gateway.

Step 6: After receiving the proxy binding acknowledgement message, the mobile access gateway performs information exchange with the UE to notify the UE that the initial attach procedure is successfully completed, that is, the PDN connection is successfully established for the emergency call of the UE. During the information exchange, the mobile access gateway may send an attach complete message to the UE.

Step 1: The UE sends an attach request message to the mobility management network element, where the attach type carried in the attach request is

Handover, the attach request carries the top EI of the UE.

Step 2: The mobility management network element determines that the attach request carries the information of the emergency call, and the UE is the UICC less

After the UE and the attachment type is Handover, the mobility management network element obtains the APN and the PDN GW identifier (or PDN GW address) from the default home subscriber server according to the top EI carried in the attach request.

The description of Embodiment 7 above shows that the mobile access gateway passes the non-3GPP access and initiates an emergency call service. The UICC less UE selects the APN and the PDN GW, and sends the indication information, the APN, and the PDN GW information to the default home subscriber network server, so that the home subscriber server can successfully register the APN and PDN GW information according to the indication information. Therefore, when the UICC less UE moves from the non-3GPP network to the 3GPP network during the emergency call, the mobility management network element can obtain the APN and PDN GW information from the default home subscriber network server. Further, the mobility management network The element can use the obtained information to perform PDN connection recovery; finally, the interruption of the emergency call service of the UICC less UE is avoided, and the reliability of the emergency call service is improved.

Embodiment 8: The UICC less UE accesses and initiates an emergency call service in the 3GPP network, and the mobility management network element does not allocate a top SI to the UICC less UE, and the mobility management network element selects a default packet data network gateway for the UE. Thereafter, the UICC less UE moves from the 3GPP network to the non-3GPP network. The mobile access gateway uses the default packet data network gateway to recover the PDN connection for the emergency call. Embodiment 8 will be described below with reference to Figs. 2b and 3b.

Step 3: The serving gateway sends a default bearer request message to the default packet data network gateway.

Step 4: After receiving the Create Default Bearer Request message, the default packet data network gateway returns a default bearer response message to the serving gateway.

Step 7. After receiving the attach accept message, the UE returns an attach complete message to the mobility management network element. Step 8. The mobility management network element sends an update bearer request message to the serving gateway.

Step 2: After receiving the attach request, the mobile access gateway determines that the attach request carries the emergency call information, the UE is the UICC less UE, and the attach type is Handover, and the mobile access gateway sends the default packet data. The network gateway sends a proxy binding request message.

Step 3. After receiving the proxy binding request message, the default packet data network gateway returns a proxy binding acknowledgement message to the mobile access gateway.

As described in the foregoing embodiment 8, the mobility management network element establishes a PDN connection by selecting a default PDN GW for the UICC less UE that accesses and initiates the emergency call service in the 3GPP, so that the UICC less UE performs the emergency call process from the 3GPP. When the network moves to the non-3GPP network, the mobile access gateway can use the default PDN GW to restore the PDN connection. Finally, the interruption of the emergency call service of the UICC less UE is avoided, and the reliability of the emergency call service is improved.

Embodiment 9: The UICC less UE accesses and initiates an emergency call service in a non-3GPP network, the mobile access gateway does not allocate BiSI for the UICC less UE, and the mobile access gateway selects a default packet data network gateway for the UE. Thereafter, the UICC less UE moves from the non-3GPP network to the 3GPP network. The mobility management network element recovers the PDN connection of the emergency call using the default packet data network gateway. Embodiment 9 will be described below with reference to FIG. 4b and FIG. 5b. FIG. 4b shows a flow of a UICC less UE accessing and initiating an emergency call service on a non-3GPP network, and an initial attach procedure of the gpUICC less UE in a non-3GPP network.

Step 3: After the mobile access gateway determines that the UE is a UICC less UE, and the attach request message carries the emergency APN information, the mobile access gateway sends a proxy binding request message to the default packet data network gateway, where the proxy is tied. The request message carries a top EI.

Step 4. After receiving the proxy binding request message, the default packet data network gateway sends a proxy binding acknowledgement message to the mobile access gateway.

Step 5: After receiving the proxy binding acknowledgement message, the mobile access gateway performs information exchange with the UE to notify the UE that the initial attach procedure is successfully completed, that is, the PDN connection is successfully established for the emergency call of the UE. During the information exchange, the mobile access gateway may send an attach complete message to the UE.

Step 1: The UE sends an attach request message to the mobility management network element, and the attach type carried in the attach request is Handover, and the attach request carries the top EI of the UE.

Step 2: After the mobility management network element determines that the attach request carries the emergency call information, the UE is the UICC less UE, and the attachment type is Handover, the mobility management network element sends a create default bearer request message to the serving gateway. The default bearer request message carries the default packet data network gateway information and the top EI.

Step 4: The default packet data network gateway returns to the service gateway after receiving the create default bearer request message. Create a default bearer response message.

The description of the foregoing embodiment 9 shows that the mobile access gateway establishes a PDN connection by selecting a default PDN GW for the UICC less UE that is not in the 3GPP access and initiates the emergency call service, so that the UICC less UE performs the emergency call process. When the 3GPP network moves to the 3GPP network, the mobility management network element can use the default PDN GW to restore the PDN connection. Finally, the interruption of the emergency call service of the UICC less UE is avoided, and the reliability of the emergency call service is improved.

Embodiment 10: An emergency call service implementation system. The structure of the system is shown in Figure 6.

The emergency call service implementation system shown in FIG. 6 includes: a first mobility management entity 610 and a second mobility management entity 620. The system can also include a storage network element 630.

The packet data network PDN connection successfully established for the emergency call of the UICC less UE, the first mobility management entity 610 sends the information required to establish a PDN connection to the storage network element 630. The successfully established PDN connection may be a PDN connection successfully established for an emergency call of the UICC less UE in the initial attach process of the emergency call by the UICC less UE, or may be a 3GPP network and a non-3GPP that make an emergency call in the UICC less UE. In the process of handover attachment between networks, the PDN connection is successfully restored for the emergency call of the UICC less UE. The above information required to establish a PDN connection includes: APN and PDN GW information. The PDN GW information is such as the PDN GW identifier or the PDN GW address.

If the UICC less UE moves between the 3GPP network and the non-3GPP network during the emergency call, the second mobility management entity 620 receives the handover request of the user equipment, and the second mobility management entity 620 determines the handover request to carry The information of the band, after the determination result is that the handover request is sent between the 3GPP network and the non-3GPP network during the emergency call of the UICC less UE, the second mobility management entity 620 is according to the slave storage network element 630. The information required to establish a PDN connection corresponding to the obtained user equipment is restored by the PDN connection of the emergency call of the user equipment.

If the UICC less UE moves between the 3GPP network and the non-3GPP network during the emergency call, and thus needs to perform PDN connection handover, the first mobility management entity 610 is located in the source network of the handover, and the second mobility management entity 620 is located. Switching in the target network.

When the UICC less UE moves from the 3GPP network to the non-3GPP network during the emergency call, the first mobility management entity 610 is a mobility management network element in the 3GPP network, and the second mobility management entity 620 is in the non-3GPP network. Mobile access gateway.

When the UICC less UE moves from the non-3GPP network to the 3GPP network during the emergency call, the first mobility management entity 610 is a mobile access gateway in the non-3GPP network, and the second mobility management entity 620 is in the 3GPP network. Mobility management network element.

The storage network element 630 receives the information required to establish a PDN connection sent by the first mobility management entity 610, and stores the information. The storage network element 630 here may be a UICC less UE or a home subscriber network server. In the case that the storage network element 630 is a home subscriber network server, the home subscriber network server may be a home subscriber network server configured by default in the first mobility management entity 610 and the second mobility management entity 620, or may be The first mobile management entity 610 and the second mobility management entity 620 select a home subscriber network server according to the top SI of the UICC less UE. In addition, when the storage network element 630 is a home subscriber network server, the home subscriber network server may store the correspondence between the B1SI and the APN and the PDN GW information, and may also store the correspondence between the top EI and the APN and the PDN GW information. The top SI and top EI are used to find the information needed to establish a PDN connection corresponding to the successfully established PDN connection.

At the home subscriber network, the first mobile management entity 610 selects the home subscriber service selected according to the top SI. In the case of the server, it is predicted that the first mobility management entity 610 needs to allocate a top SI for the UICC less UE making an emergency call. The first mobility management entity 610 may allocate a top SI to the UICC less UE during an initial attach procedure of the UICC less UE for making an emergency call.

If the first mobility management entity 610 allocates B1SI to the UICC less UE, the first mobility management entity 610 shall notify the UICC less UE of the allocated B1SI, after which the UICC less UE moves due to moving between the 3GPP network and the non-3GPP network. When the attach request is sent to the second mobility management entity 620, the top SI to which the mobility management entity is assigned should be carried in the attach request. In this way, in the subsequent PDN connection recovery process, the second mobility management entity 620 can select the home subscriber server (ie, the storage network element 630) according to the B1SI carried in the attach request, and sign the subscriber server to the selected home location. Request information to establish a PDN connection. At this time, the corresponding attribute of the top SI and the APN and PDN GW information may be stored in the selected home subscriber server.

In the case that the home subscriber network server (ie, the storage network element 630) is the home registration service server selected by the mobility management entity according to the top SI, since the subscription information of the UICC less UE is not included in the home subscriber network, In normal processing mode, after receiving the top SI, APN, and PDN GW information, the home subscriber server does not perform storage processing, and also returns error information to the mobility management entity. In order for the home subscriber server to correctly store the IMSI, APN and PDN GW information, the first mobility management entity 610 may carry the message carrying the BiSI, APN and PDN GW information to the home subscriber server when carrying the message. The indication information is used to indicate that the home subscriber server does not store the B1SI, APN, and PDN GW information without the subscription information of the UICC less UE.

In the case that the home subscriber network server is the default home subscriber network, the first mobility management entity 610 may not allocate the top SI for the UICC less UE that makes the emergency call. Whether the UICC less UE performs the initial attach process of the emergency call or the UICC less UE performs the handover attach process of the emergency call, the first mobility management entity 610 should send the message to the default home subscriber network server as the UICC less UE. Emergency call is successfully established The information required to establish a PDN connection corresponding to the PDN connection is configured to store the information required to establish a PDN connection corresponding to the successfully established PDN connection in the default home subscriber network. At this time, the correspondence between the top EI and the APN and PDN GW information may be stored in the default home subscription server.

In the case that the home subscriber network server is the default home subscriber network, the same is true, because the subscriber subscriber server does not have the subscription information of the UICC less UE, the subscriber is subscribed according to the usual processing manner. After receiving the ΒίΕΙ, APN, and PDN GW information sent by the first mobility management entity 610, the server does not perform storage processing, and also returns error information to the first mobility management entity 610. In order for the home subscriber server to correctly store the top EI, APN and PDN GW information, the first mobility management entity 610 may send a message carrying the ΒίΕΙ, APN and PDN GW information to the home subscriber server, in the message. The indication information is carried to indicate that the home subscriber server does not store the subscription information of the UICC less UE, and the ΒίΕΙ, APN, and PDN GW information should also be stored. It should be noted that the message sent by the first mobility management entity 610 may not carry the indication information. In this case, when the home subscriber server determines that the message carries the top EI, the top EI, the APN, and the message PDN GW information is stored for processing.

In the case that the storage network element 630 is a UICC less UE, the first mobility management entity 610 should send the APN and PDN GW information corresponding to the PDN connection successfully established for the emergency call of the UICC less UE to the storage network element 630. At this time, the first mobility management entity 610 may not allocate the top SI for the UICC less UE. Thereafter, when the UICC less UE sends an attach request to the second mobility management entity 620 as it moves between the 3GPP network and the non-3GPP network, the IMEI, APN and PDN GW information should be carried in the attach request. The B1EI can be used by the second mobility management entity 620 for PDN connection recovery operations. It should be noted that the APN and PDN GW information may also be sent to the second mobility management entity 620 by other messages than the attach request.

After receiving the attach request, the second mobility management entity 620 determines, by using the information carried in the attach request, whether the attach request is: UICC less the UE sends the mobile station to move between the 3GPP network and the non-3GPP network during the emergency call. For example, the second mobility management entity 620 determines the type of the UE that sends the attach request and the type of the attach request to determine whether the UE that sends the attach request is a UICC less UE, and whether the attach request is a handover type attach request. The handover type attachment request herein refers to an attachment request sent to the second mobility management entity 620 due to the UE moving between the 3GPP network and the non-3GPP network during the emergency call by the UE.

When the storage network element 630 is a UICC less UE, and the foregoing determination result is that the UE that sends the attach request is the UICC less UE, and the attach request is the UE that moves between the 3GPP network and the non-3GPP network during the emergency call, the attached message is sent. In the case of the request, the second mobility management entity 620 may obtain the top EI, APN, and PDN GW information from the message sent by the UICC less UE (such as in the attach request), after which the second mobility management entity 620 may utilize the APN and the PDN. The GW information determines the PDN GW that establishes the PDN connection, and then the second mobility management entity 620 instructs the determined PDN GW to perform recovery processing on the PDN connection corresponding to the top EI.

The storage network element 630 is a home subscriber network server, and the foregoing judgment result is that the UE that sends the attach request is a UICC less UE, and the attach request is sent between the 3GPP network and the non-3GPP network during the emergency call process. In the case of the attach request, the second mobility management entity 620 may obtain the B1EI or BiSI from the message sent by the UICC less UE (such as in the attach request). If the message sent by the UICC less UE carries the IMSI, the second mobility management entity 620 may select the home subscription server according to the top SI, and then the second mobility management entity 620 requests the B1SI from the selected home subscription server. Corresponding APN and PDN GW information, such that the second mobility management entity 620 can determine the PDN GW establishing the PDN connection by using the APN and PDN GW information requested to be obtained, and then the second mobility management entity 620 indicates the determined PDN GW pair. The PDN connection corresponding to the top SI is restored. If the message sent by the UICC less UE is the top EI, the second mobility management entity 620 may request the APN and PDN GW information corresponding to the IMEI from the default home subscriber network, such that the second mobility management entity The 620 may determine the PDN GW that establishes the PDN connection by using the APN and PDN GW information obtained by the request, and then the second mobility management entity 620 instructs the determined PDN GW to perform a recovery process on the PDN connection corresponding to the top EI. It should be noted that, after the PDN connection is successfully restored, the information required for establishing the PDN connection corresponding to the PDN connection after the recovery process should be sent to the storage network element 630. At this time, the second mobility management entity 620. As the first mobility management entity 610, when the UICC less UE performs the mobility between the 3GPP network and the non-3GPP network again during the emergency call, the mobility management entity in the target network becomes the second mobility management entity 620.

The PDN connection of the emergency service of the UICC less UE may also be restored according to the pre-made default packet data network gateway PDN GW.

The specific structures of the first mobility management entity 610 and the second mobility management entity 620 described above may be as described in the following embodiments.

Embodiment 11 Network device. The network device is a mobility management entity in the network, such as a mobility management network element or a mobile access gateway. The structure of the network device is as shown in FIG.

The network device in FIG. ₇ includes: an establishing module 710 and a transmitting module 720.

For the emergency call of the UICC less UE, the setup module 710 establishes a packet data network PDN connection. The PDN connection established by the establishing module 710 may be a PDN connection established for an emergency call of the UICC less UE in the initial attach process of the emergency call by the UICC less UE, or a 3GPP network and non-3GPP that make an emergency call in the UICC less UE. In the process of handover attachment between networks, the PDN connection is successfully restored for the emergency call of the UICC less UE.

The transmitting module 720 sends the information required to establish a PDN connection to the storage network element for the PDN connection successfully established for the emergency call of the UICC less UE. The successfully established PDN connection may be a PDN connection successfully established for an emergency call of the UICC less UE in the initial attach process of the emergency call by the UICC less UE, or a 3GPP network and a non-3GPP that make an emergency call in the UICC less UE. In the process of handover attachment between networks, the PDN connection is successfully restored for the emergency call of the UICC less UE. The above information required to establish a PDN connection includes: APN and PDN GW information. The PDN GW information is such as the PDN GW identifier or the PDN GW address.

In the case where the storage network element is a UICC less UE, the specific structure of the foregoing sending module 720 is as shown in FIG. 8A. The sending module 720 in FIG. 8A includes: a first obtaining module 800 and a first sending module 810.

The first obtaining module 800 acquires APN and PDN GW information corresponding to the PDN connection successfully established for the emergency call of the UICC less UE. The first obtaining module 800 can obtain the APN and PDN GW information according to the packet data network gateway selected by the network device for the UE.

The first sending module 810 sends the information acquired by the first obtaining module 800 to the UICC less UE. For example, the first sending module 810 carries the APN and PDN GW information acquired by the first obtaining module 800 in the attach accept message, and sends the attach accept message to the UICC less UE.

In the case where the storage network element is a home subscriber network server, a specific structure of the foregoing transmission module 720 is as shown in FIG. 8B.

The transmitting module 720 in FIG. 8B includes: a second obtaining module 820 and a second transmitting module 830.

The second obtaining module 820 acquires the APN and PDN GW information corresponding to the B1SI of the UICC less UE and the PDN connection successfully established for the emergency call of the UICC less UE; the top SI is: the establishing module 710 is a UICC less for making an emergency call. The UE dynamically establishes the top SI dynamically allocated during the PDN connection process. The second obtaining module 820 may acquire the top SI from an attach request sent by the network device and sent by the UICC less UE. The B1SI in the attach request is obtained by the UICC less UE from the message sent by the network device. For example, after the establishing module 710 dynamically allocates the top SI to the UICC less UE, the establishing module 710 sends a message carrying the dynamically allocated top SI to the UICC less UE (eg, the establishing module 7100 carries the top SI in the attach accept message, and Send the attach accept message to the UICC less UE).

The second sending module 830 sends the indication information and the information acquired by the second obtaining module 820 to the home subscriber network server. The indication information is used to indicate that the home subscriber server does not store and receive the subscription data information of the UICC less UE. BiSI, APN and PDN GW information. The second sending module 830 may select the home subscription server according to the B1SI acquired by the second obtaining module 820, and send the indication information, the top SI, the APN, and the PDN GW information to the selected home subscription server. In the case where the storage network element is a home subscriber network server, another specific structure of the foregoing transmission module 720 is as shown in FIG. 8C.

The transmitting module 720 in FIG. 8C includes: a third obtaining module 840 and a third transmitting module 850.

The third obtaining module 840 obtains the top EI of the UICC less UE and the APN and PDN GW information corresponding to the PDN connection successfully established for the emergency call of the UICC less UE. The top EI acquired by the third obtaining module 840 is derived from a message sent by the UICC less UE, such as an attach request message. The APN and PDN GW information acquired by the third obtaining module 840 may be the APN and PDN GW information selected by the establishing module 710 for establishing a PDN connection.

The third sending module 850 sends the information acquired by the third obtaining module 840 to the default home subscriber service server. For example, the third transmitting module 850 carries the top EI, APN, and PDN GW information in the notification message and sends the message to the default home subscriber server. The notification message may further carry indication information, where the indication information is valid, indicating that: the registration is performed by the UICC less UE performing an emergency call, and the home subscriber server should perform a registration operation, and does not need to return. Error message. The default home subscription server is determined by the default configuration of the network device.

Embodiment 12: Network equipment. The network device is a mobility management entity in the network, such as a mobility management network element or a mobile access gateway. The structure of the network device is as shown in FIG.

The network device in FIG. 9 includes a receiving module 910, a determining module 920, and a recovery module 930.

The receiving module 910 receives the handover request sent by the user equipment. The handover request may be a handover request sent by the UICC less UE to move between the 3GPP network and the non-3GPP network during the emergency call. The switching request is such as an attach request.

In the case that the storage network element is the home subscriber network, the handover request received by the receiving module 910 may carry nisi or niEi. Here, nisi is the si of the network device in the source network dynamically allocated for uicc less UE.

In the case that the storage network element is a UICC less UE, the handover request received by the receiving module 910 may be carried in the handover request. IMEI o

The determining module 920 determines the information carried in the handover request received by the receiving module 910, for example, determining whether the UE that sends the attach request is a UICC less UE, whether the attach request message carries the information of the emergency call, and whether the type of the attach request is For switching etc.

In a case where the determination result of the determination module 920 is that the handover request is a handover request sent between the 3GPP network and the non-3GPP network during the emergency call of the UICC less UE, the recovery module 930 obtains according to the slave storage network element. Recovering the PDN connection of the emergency call of the user equipment corresponding to the information required to establish the PDN connection by the user equipment; the recovery module 930 may also restore the PDN connection of the emergency service of the UICC less UE according to the pre-made default PDN GW, that is, It is said that in the process of establishing a PDN connection for the emergency call of the UICC less UE, the default PDN GW is used to implement the establishment of the PDN connection. .

In the case that the storage network element is the home subscriber network server, the obtaining operation of the recovery module 930 may be performed after the determining operation of the module 920. Moreover, the recovery module 930 can select the home subscriber server according to the top SI carried in the received attach request, and then the recovery module 930 uses the B1SI to query the selected home subscriber service server to obtain the APN and PDN GW information. In addition, the recovery module 930 can obtain the information carried in the received attachment request, and then the recovery module 930 uses the IMEI to query the default home subscription server to obtain the APN and PDN GW information.

In the case that the storage network element is a UICC less UE, the obtaining operation of the recovery module 930 and the determining operation of the determining module 920 may be limited by the order. Moreover, the recovery module 930 can obtain APN and PDN GW information from information carried by a message (such as an attach request message) sent by the UICC less UE.

In the case where the storage network element is a home subscriber network server, a specific structure of the recovery module 930 is as shown in FIG. 10A.

The recovery module 930 in FIG. 10A includes: a first query sub-module 1000 and a recovery sub-module 1010. In a case where the determination result of the determination module 920 is that the handover request is a handover request sent between the 3GPP network and the non-3GPP network during the emergency call of the UICC less UE, the first query submodule 1000 receives from the receiving module.

Receiving si in the information carried in the received handover request, the first query sub-module 1000 selects the home subscriber server according to the acquired nisi, and sends a message carrying the top si to the selected home subscriber server ( For example, the first query sub-module 1000 obtains information required for establishing a PDN connection from the message returned by the home subscriber server, and transmits the information to the recovery sub-module 1010.

The recovery sub-module 1010 performs PDN connection recovery of the emergency call of the user equipment according to the information required to establish the PDN connection transmitted by the first query sub-module 1000.

In the case where the storage network element is a home subscriber network server, another specific structure of the recovery module 930 is as shown in FIG. 10B.

The recovery module 930 in FIG. 10B includes: a second query sub-module 1020 and a recovery sub-module 1010.

In a case where the determination result of the determination module 920 is that the handover request is a handover request sent between the 3GPP network and the non-3GPP network during the emergency call of the UICC less UE, the second query submodule 1020 receives from the receiving module 910. The information carried in the received handover request is obtained, and then the second query sub-module 1020 sends a message carrying the flaw (such as a query message) to the default home subscriber server according to the acquired B1EI, the second query. The module 1020 obtains the information required to establish a PDN connection from the message returned by the home subscriber server, and transmits the information to the recovery sub-module 1010.

The recovery sub-module 1010 performs PDN connection recovery of the emergency call of the user equipment according to the information required to establish the PDN connection transmitted by the second query sub-module 1020.

It should be noted that, in a network device, the modules described in Embodiment 11 and Embodiment 12 can be simultaneously provided; in one network device, the establishment module 710, the sending module 720, the receiving module 910, the determining module 920, and the recovery are simultaneously provided. In the case of module 930, the setup module 710 and the transmit module 720 perform the UICC less UE and the receive module in operation. 910. The UICC less UE in which the determining module 920 and the recovery module 930 perform operations does not refer to the same UICC less UE. Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary hardware platform, and of course, all can be implemented by hardware, but in many cases, the former is better. Implementation. Based on such understanding, all or part of the technical solution of the present invention contributing to the background art may be embodied in the form of a software product, which may be stored in a storage medium such as a ROM/RAM, a magnetic disk, an optical disk, or the like. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention or portions of the embodiments.

While the invention has been described by the embodiments of the invention, it will be understood that

Claims

An emergency service implementation method, the method comprising:

The method of claim 1, wherein the recovering the PDN connection of the emergency service of the UICC less UE according to the obtained information of the packet data network PDN of the UICC less UE, including:

Recovering the PDN connection of the emergency service of the UICC less UE according to the information of the packet data network PDN connection of the UICC less UE obtained from the storage network element; or

The PDN connection of the emergency service of the UICC less UE is restored according to the pre-made default packet data network gateway PDN GW.

The method of claim 2, wherein the storage network element is the UICC less UE, or the storage network element is a home subscription user server.

4. The method of claim 3 wherein:

The home subscriber network server is: a default home subscriber network; or

The home subscriber network server is: a home subscriber server selected according to the international mobile subscriber identity code BiSI of the UICC less UE, where the IMSI is: allocated by the UICC less UE for emergency service.

IMSI o

The method of claim 2, wherein the method further comprises:

Before the handover of the UICC less UE, the first mobility management entity establishes a PDN connection for the emergency service of the UICC less UE, and sends the established PDN connection information to the storage network element.

The method of claim 5, wherein the storage network element is a UICC less UE, the first The mobile management entity sends the information about the established PDN connection to the storage network element, including:

The first mobility management entity sends the access point name APN and the packet data network gateway PDN GW information corresponding to the PDN connection of the UICC less UE to the UICC less UE;

The switching request sent by the UICC less UE in the emergency service process to switch between the 3GPP network and the non-3GPP network carries the international mobile device identifier EI, APN, and PDN GW information, and is used to restore the PDN connection. .

The method of claim 5, wherein the storage network element is a home subscriber network server, and the first mobility management entity sends the information about the established PDN connection to the storage network element, including :

The first mobility management entity sends the indication information, the top SI of the UICC less UE, and the APN and PDN GW information corresponding to the establishment of the PDN connection to the home subscriber network server;

The indication information is used to indicate that the home subscription subscriber server stores the received BiSI, APN, and PDN GW information without the subscription data information of the UICC less UE;

Or the first mobility management entity sends the information about the established PDN connection to the storage network element, where: the first mobility management entity corresponds to the top EI of the UICC less UE and the PDN connection. The APN and PDN GW information is sent to the home subscriber network server, so that the home subscriber network server stores the received top EI, APN and PDN GW information.

The method of claim 7, wherein when the home subscriber network server stores the top SI of the UICC less UE, the method further includes:

The first mobility management entity sends the top SI to the UICC less UE, and the handover request sent by the UICC less UE in the emergency service process to switch between the 3GPP network and the non-3GPP network carries The top SI;

The nisi carried in the handover request is used to select a home subscriber network and a home subscriber network The information required to establish a PDN connection is stored, or is used to select information required to establish a PDN connection stored in the home subscriber server if the home subscriber server is the default home subscriber server.

The method of claim 7, wherein: when the home subscriber network server stores the top EI of the UICC less UE, the method further includes:

The switching request sent by the UICC less UE to perform handover in the emergency service process between the 3GPP network and the non-3GPP network carries the B1EI;

The top EI carried in the handover request is used to select information required to establish a PDN connection stored in the home subscriber server.

10. An emergency service implementation system, the system comprising:

a second mobility management entity, configured to receive the UICC less UE handover request, determine that the UICC less UE performs a handover between a 3GPP network and a non-3GPP network in performing an emergency service; according to the acquired UICC less UE The information of the PDN connection recovers the PDN connection of the UE.

The system according to claim 10, wherein the system further comprises a first mobility management entity, configured to send a packet data network PDN connection for emergency services of the UICC less UE, to the storage network element. Determining the information required for establishing the PDN connection; the second mobility management entity recovering the PDN connection of the emergency service of the UICC less UE according to the information of the packet data network PDN connection of the UICC less UE acquired from the storage network element .

The system of claim 11, wherein the storage network element is configured to receive and store information required to establish the PDN connection, and the storage network element is a UICC less UE, or the The storage network element is a home subscriber server.

The system according to claim 10, wherein the second mobility management entity restores the PDN connection of the emergency service of the UICC less UE according to the pre-made default PDN GW.

14. The system of claim 10, 11, 12 or 13 wherein: said first mobility management entity a mobility management network element in a 3GPP network, the second mobility management entity is a mobile access gateway in a non-3GPP network; or the second mobility management entity is a mobility management network element in a 3GPP network, The first mobility management entity is a mobile access gateway in a non-3GPP network.

15. A network device, comprising:

The network device according to claim 15, wherein the sending module comprises:

a first acquiring module, configured to acquire APN and PDN GW information corresponding to the PDN connection;

a first sending module, configured to send the APN and PDN GW information acquired by the first acquiring module to the UICC less UE;

Or the sending module includes:

a second acquiring module, configured to acquire BiSI of the UICC less UE, and the APN and PDN GW information; the top SI is: the establishing module is allocated in the process of establishing a PDN connection by the UICC less UE performing emergency service IMSI;

a second sending module, configured to select a home subscriber network server according to the nisi acquired by the second acquiring module, and send the indication information and the APN and PDN GW information acquired by the second acquiring module to the selected home location And the indication information is used to indicate that the home subscriber server stores the received BiSI, APN, and PDN GW information without the subscription data information of the UICC less UE;

Or the sending module includes:

a third obtaining module, configured to acquire a top EI of the UICC less UE, and the APN and PDN GW information, where the third sending module is configured to send the APN and PDN GW information acquired by the third acquiring module to a default Attribution Sign up for a user server.

17. A network device, comprising:

a receiving module, configured to receive a handover request of a UICC less UE;

And a recovery module, configured to recover the PDN connection of the emergency service of the UICC less UE according to the acquired information of the packet data network PDN connection of the UICC less UE.

The network device according to claim 17, wherein the recovery module recovers the emergency service of the UICC less UE according to the information of the packet data network PDN connection of the UICC less UE acquired from the storage network element. PDN connection; or recovering the PDN connection of the emergency service of the UICC less UE according to the pre-made default PDN GW.

The network device according to claim 18, wherein the storage network element is a UICC less UE, and the handover request received by the receiving module carries top EI, APN, and PDN GW information for restoration. The PDN is connected.

20. The network device of claim 18, wherein:

The storage network element is a home subscriber network server, and the handover request received by the receiving module carries an IMSI; and the recovery module includes:

a first query sub-module, configured to select a home-subscriber user server according to the B1SI carried in the handover request, and query, from the selected home-subscriber user server, information required to establish a PDN connection, and output the information;

a recovery submodule, configured to restore a PDN connection of the emergency service of the user equipment according to the received information required to establish a PDN connection;

Or the storage network element is a home subscriber network server, and the handover request received by the receiving module carries a top EI, and the recovery module includes:

a second query module, configured to sign a subscriber server from a default home location according to the B1EI carried in the handover request The query obtains the information required to establish a PDN connection, and outputs the recovery submodule, which is used to restore the PDN connection of the emergency service of the user equipment according to the received information required to establish a PDN connection.