WO2014206318A1

WO2014206318A1 - Emergency call implementation method, device, and system

Info

Publication number: WO2014206318A1
Application number: PCT/CN2014/080857
Authority: WO
Inventors: 王胡成
Original assignee: 电信科学技术研究院
Priority date: 2013-06-27
Filing date: 2014-06-26
Publication date: 2014-12-31
Also published as: CN104254055B; CN104254055A

Abstract

Disclosed are an emergency call implementation method, device, and system. In the present application, a core network device receives a PDN connection request that is sent by a user equipment for a cluster emergency call service; the core network device determines a PGW according to an APN carried in the PDN connection request or subscription information of the user equipment, initiates, for the user equipment according to the determined PGW, a PDN connection establishment process for the cluster emergency call service, and indicates that an established PDN connection is a PDN connection for the cluster emergency call service. The present application can implement a cluster emergency call service.

Description

Emergency call implementation method, device and system

This application claims priority to Chinese Patent Application No. 201310263521.1, filed on Jun. 27, 2013, the entire disclosure of which is incorporated herein by reference. In this application.

Technical field

The present application relates to the field of wireless communications technologies, and in particular, to an emergency call implementation method, device, and system. Background technique

The main application scenario of trunking communication is to meet the requirements of public safety communication and critical communication. The former 3GPP (3rd Generation Partnership Project) is studying the LTE (Long Term Evolution) network to support group communication. The problem is mainly to study how to enable LTE networks to efficiently support trunking communication services, such as voice group calls, video group calls, and so on.

The trunking communication system is a dedicated wireless communication system developed for industry-specific applications to meet the needs of industry users for command and dispatch. A large number of wireless users in a trunking communication system share a small number of wireless channels, and the channel resources in the system are dynamically allocated. It is a multi-purpose, high-performance wireless mobile communication system, representing the development direction of a dedicated mobile communication system.

A typical service in a trunking communication system is a group communication service, which includes three functions: group call, emergency group call, and broadcast call. Among them, the emergency group call is a special intercom mode in an emergency, with the highest call priority, to inform the pre-designated group in the shortest time and in the most convenient way.

The emergency call in the cluster system mainly refers to the emergency group call, and the emergency group call can be regarded as the highest priority group call, which can occupy the resources being requested and in the call, and assign the channel to the emergency call. The mobile user equipment with advanced scheduling function has an emergency call button, which triggers the call when pressed, and the network equipment installation scheduling group calls to handle the emergency call, and calls all members in the talk group where the user is located.

The emergency call service in the existing EPS (Evolution Packet System) mainly refers to making an emergency telephone number, such as an alarm call. The 3GPP classifies emergency services into emergency call services in the PS (Packet Switching) domain and emergency call services in the CS (Circuit Switching) domain. In the LTE network, only the PS domain emergency call service is supported. Therefore, the UE (User Equipment, ie, the terminal) needs to obtain an emergency call service through an IMS (IP Multimedia Subsystem) emergency session. An emergency PDN (Packet Data Network) connection needs to be established to support an IMS emergency session.

APN (Access Point Name) is the identifier of the external PDN. The APN is composed of an APN network identifier and an APN carrier identifier (the APN carrier identifier is optional), which can be obtained by performing domain name resolution on the AP. IP address of the PDN Gateway (PDN Gateway, PGW).

In the current public emergency call service in the EPS, the APN is configured in the MME Emergency Configuration Data (MME, Mobility Management Entity, Mobile Management Entity), and the APN can only be resolved to the PGW of the public emergency call service. When the UE establishes an emergency PD connection, the MME obtains the emergency PDN connection according to the emergency APN according to the emergency APN obtained by the MME Emergency Configuration Data, and establishes an emergency PDN connection according to the PGW.

Emergency calls in the cluster system are carried out within the current service scope, such as emergency calls within the public safety system, emergency calls within the fire protection system. The access PGWs of different cluster systems may be different when they access EPC (Evolved Packet Core). However, the APNs used according to emergency calls in the cluster system can only be resolved to the PGW of the public emergency call service, but cannot be resolved. The PGW that accesses the EPC to the cluster system.

It can be seen that the emergency AP in the existing EPS system cannot meet the emergency call service in the cluster system. Summary of the invention

The embodiment of the present application provides an emergency call implementation method, device, and system for implementing a trunk emergency call service.

The emergency call implementation method provided by the embodiment of the present application includes:

The core network device receives the PDN connection request sent by the user equipment for the cluster emergency call service; the core network device determines the PGW according to the APN carried in the PDN connection request or according to the APN in the subscription information of the user equipment;

The core network device initiates a PDN connection establishment process for the trunk emergency call service for the user equipment according to the determined PGW, and indicates that the established PDN connection is a PDN connection of the trunk emergency call service.

The core network device provided in this embodiment of the present application includes:

a receiving module, configured to receive a PDN connection request sent by the user equipment for the trunk emergency call service, and a determining module, configured to: according to the APN carried in the PDN connection request received by the receiving module, or according to the subscription of the user equipment The APN in the information determines the PGW;

The PDN connection establishing module is configured to initiate a PDN connection establishment process for the cluster emergency call service according to the PGW determined by the determining module, and indicate that the established PDN connection is a PDN connection of the cluster emergency call service.

The emergency service implementation system provided by the embodiment of the present application includes: a core network device, and a PGW;

The core network device is configured to receive a packet data network PDN for a trunk emergency call service sent by the user equipment. The connection request, the PGW is determined according to the APN carried in the PDN connection request or the APN according to the subscription information of the user equipment, and the PDN connection establishment procedure for the cluster emergency call service is initiated for the user equipment according to the determined PGW. And indicating that the established PDN connection is a PDN connection of the trunk emergency call service;

The PGW, in the PDN connection establishment process for the trunk emergency call service initiated by the core network device, after receiving the session establishment request sent by the core network device, determining, according to the received session establishment request, The established PDN connection is the PDN connection of the trunk emergency call service, and the congestion control is refused.

In the foregoing embodiment of the present application, the core network device determines the PGW according to the APN carried in the PDN connection request sent by the user equipment for the cluster emergency call service or the APN according to the subscription information of the user equipment, according to the determined PGW. The user equipment initiates a PDN connection establishment procedure for the trunk emergency call service. The APN of the subscription information of the APN or the user equipment carried in the PDN connection request for the trunk emergency call service sent by the user equipment can be parsed to obtain the PGW of the current cluster system accessing the core network of the user equipment, so that the core network equipment can be guaranteed. The determined PGW is the PGW of the cluster system accessing the core network, so as to ensure the realization of the cluster emergency call service. DRAWINGS

1 is a schematic flowchart of an emergency call service implementation process according to an embodiment of the present application;

2 is a schematic flowchart of an emergency call service implementation process according to Embodiment 1 of the present application;

3 is a schematic flowchart of an emergency call service implementation process according to Embodiment 2 of the present application;

4 is a schematic flowchart of an emergency call service implementation process according to Embodiment 3 of the present application;

FIG. 5 is a schematic structural diagram of a core network device according to Embodiment 4 and Embodiment 5 of the present application. FIG. 6 is a schematic structural diagram of a core network device according to Embodiment 6 of the present application. detailed description

The embodiment of the present application proposes a solution for implementing a cluster emergency call service by enhancing an EPS system. The embodiments of the present application are described in detail below with reference to the accompanying drawings.

As the content of the user equipment subscription information in the user equipment is related to the content of the emergency service permission of the user equipment, the cluster emergency service authority of the user equipment is first described below.

The 3GPP network is based on local regulations and operator policies and can support different levels of emergency call services (see A, B, C and D below):

A: valid UEs only (legal user equipment only), that is, only a normally attached UE with a valid subscription can obtain an emergency service. B: Only UEs that authenticated are allowed (only for authorized user equipment), that is, the UE can obtain an emergency service only by authorization, and the UE must have a valid IMSI (International Mobile Subscriber Identification). ).

C. IMSI required, authentication optional (must be IMSI, IMSI may be authorized or not), that is, the UE must have IMSI, and IMSI may not be authorized. The unlicensed IMSI is only used for recording purposes in the network. The network uses IMEI as the identity of the UE, and the IMEI (International Mobile Equipment Identity) only UE (UEEI) will be denied access to the emergency call service.

D. All UEs are allowed (i.e., all UEs are authorized), that is, all UEs, including UEs with only IMEI and UEs without IMSI, can obtain emergency call service, and IMEI is used as the identifier of the UE.

The degree of UE support for the emergency call service, that is, the usage rights information of the cluster emergency call service, is included in the subscription information of the UE.

Referring to FIG. 1 , it is a schematic diagram of an implementation process of an emergency call service provided by an embodiment of the present application. As shown in the figure, the process may include:

Step 101: The network device receives a PDN connection request sent by the user equipment for the trunk emergency call service. In a specific implementation, a specific request type (such as a cluster emergency call type) may be set for a PDN connection request for the trunk emergency call service, so that the network device can identify whether the received PDN connection request is a PDN connection for the trunk emergency call service. request. Of course, it is also possible to distinguish whether it is a PDN connection request of the trunk emergency call service by other means, for example, by setting an identifier in the request message.

Step 102: The network device determines a PGW according to the APN carried in the PDN connection request.

Step «103: The network device initiates a PDN connection establishment process for the trunk emergency call service for the user equipment according to the determined PGW, and indicates that the established PDN connection is a PDN connection of the trunk emergency call service.

In the foregoing process, the PDN connection request sent by the user equipment for the trunk emergency call service may carry the ANP or not.

If the APN is carried in the PDN connection request sent by the user equipment in step 101, the APN is an ordinary APN accessing the cluster service. For example, the current cluster system of the user equipment accesses the APN corresponding to the PGW of the EPC, and the APN is normal. Cluster service APN. The term "ordinary cluster service" as used herein refers to a cluster call service that is different from the cluster emergency call service. Correspondingly, in step 102, the network device parses the PGW according to the APN carried in the PDN connection request.

If the APN is not carried in the PDN connection request sent by the user equipment in step 101, the network device parses the PGW according to the cluster emergency service APN in the user equipment subscription information or the common cluster service APN in the user equipment subscription information. In the actual application scenario, a public service for the cluster service can be deployed for the emergency industry. The PGW of the PGW, the cluster emergency service APN in the user equipment subscription information is the APN corresponding to the public PGW for the emergency service, that is, the PGW for the emergency service can be obtained by parsing the APN, so that The user equipment is ensured to establish a PDN connection according to the PGW, thereby implementing an emergency call service.

In step 103 of the foregoing process, the network device may indicate that the established PDN connection is a PDN connection of the trunk emergency call service by carrying the indication information in the session establishment request sent to the PGW. In the case that the network device obtains the PGW according to the cluster emergency service APN in the user equipment subscription information, the network device may also carry the manner in which the cluster emergency service APN in the user equipment subscription information is carried in the session establishment request sent to the PGW. The established PDN connection is the PDN connection of the cluster emergency call service, and the PGW can identify the cluster emergency service APN and the common cluster service APN.

Further, after receiving the PDN connection request for the trunk emergency call service sent by the user equipment, the network device first authenticates the user equipment, and after the authentication is passed, according to the APN carried in the PDN connection request or the The APN in the subscription information of the user equipment determines the PGW, and then establishes an emergency PDN connection according to the determined PGW. The network device authenticates the user equipment, and determines whether the user equipment is allowed to initiate the cluster emergency call service according to the subscription information of the user equipment.

The network devices in the above process are usually core network devices, such as core network devices for mobility management. In an LTE system, the network device in the above process is usually an MME.

Through the above process, it can be seen that, for the LTE system, the embodiment of the present application implements an emergency call service by extending the function of the MME. The MME determines the PGW according to the APN requested by the user equipment (that is, the APN corresponding to the PGW of the current cluster system accessing the EPC of the user equipment), so that the PGW determined by the MME can be the PGW of the EPC of the cluster system, thereby ensuring The realization of cluster emergency call service. If the APN is not carried in the PDN connection request sent by the user equipment, the PGW can be determined according to the cluster emergency service APN in the user equipment subscription information or the common cluster service APN in the user equipment subscription information, thereby establishing a PDN connection for the emergency call service. Since the PGW parsed according to the cluster emergency service APN in the subscription information is a public PGW dedicated to the emergency call service, the cluster emergency call service can be implemented. In this way, an emergency PDN connection can be established for the user equipment regardless of whether the user equipment is in an emergency attach state.

For a more detailed description of the present application, the specific implementation process of the present application will be described in detail below with reference to specific embodiments.

Embodiment 1

In this embodiment, when the UE requests the establishment of the emergency PD connection (emergency PDN connection) of the cluster service, the UE carries the common cluster service APN in the PDN connection request message, and sets the request type (Request type) to "group communication emergency service (group). Communication emergency ),, , is used to indicate that the request is for the cluster emergency call service PDN connection request.

After receiving the PDN connection request, the MME determines, according to the request type, that the request is to establish an emergency PDN connection for the cluster service, and determines, according to the UE subscription information, whether the UE is allowed to initiate the cluster emergency service, and if allowed, according to the PDN connection request message. The APN establishes an emergency PDN connection for the UE and indicates to the PGW that the established PDN connection is an emergency PDN connection.

Correspondingly, in this embodiment, the UE subscription information includes the cluster emergency call service usage authority information for the specific APN, that is, whether the UE is allowed to initiate the cluster emergency call service for the specific APN.

It should be noted that, the foregoing step of determining, according to the UE subscription information, whether the UE is allowed to initiate the cluster emergency service is an optional step.

Referring to FIG. 2, the signaling interaction process of the foregoing process in Embodiment 1 may include:

Step 1: The UE sends a PDN Connectivity Request (PDN Connectivity Request) message to the MME to request to establish an emergency PDN connection for the cluster service. The PDN connection request message carries the common cluster service APN (through which the APN can be parsed to obtain the PGW of the cluster system accessing the EPC), and the request type Request type of the request message is set to "group communication emergency". The common cluster service APN can be pre-configured on the user equipment.

Step 2: After receiving the PDN Connectivity Request message, the MME determines, according to the Request type of the message, that the request is to establish an emergency PDN connection for the cluster service, and therefore authenticates the UE.

Specifically, the MME obtains the subscription information of the UE, for example, the subscription information of the UE may be obtained from the Home Subscriber Server (HSS), and determines, according to the subscription information of the UE, whether the UE is allowed to initiate the subscription for the APN (ie, The cluster emergency call service of the APN carried in the PDN Connectivity Request message. If so, continue with step 3 below, otherwise the process ends.

Step 3: If the UE subscription information indicates that the UE is allowed to initiate a trunk emergency call service for the APN, the MME establishes an emergency PDN connection for the cluster service for the UE.

Specifically, the MME requests the DNS (Domain Name Resolution Server) to perform domain name resolution according to the APN requesting the received PDN Connectivity Request message, and obtains the IP address of the PGW, and sends a session to the PGW through the SGW (Serving Gateway). A Create Session Request message is generated. The Create Session Request message carries an indication message for indicating to the PGW that the established PDN connection is an emergency PDN connection.

Step 4: The PGW learns that the established PDN is connected to the emergency PD connection according to the indication information carried in the Create Session Request message. Therefore, the PGW does not perform the restriction operation such as congestion control. The PGW returns a Session Set Response (Message) message, which is sent to the MME via the SGW.

Step 5: The MME returns a PDN Connection Response (PDN Connection Response) message to the UE, to The PDN connection requested by the notification has been successfully established.

As can be seen from the description of the first embodiment, the PDN Connectivity Request sent by the user equipment carries the common cluster service APN, and the MME can parse the PGW of the cluster system to access the EPC according to the APN, thereby ensuring the cluster emergency call service. Implementation.

Embodiment 2

This embodiment describes that the UE sets the Request type to "group communication emergency" when requesting the establishment of an emergency PDN connection for the cluster service.

After receiving the PDN connection request, the MME determines, according to the Request type, that the request is to establish an emergency PDN connection for the cluster service, and determines whether the UE is allowed to initiate the cluster emergency service according to the UE subscription information, and if possible, obtains the cluster emergency from the UE subscription information. The service APN (referred to as emergency APN in this embodiment) establishes an emergency PDN connection.

After receiving the Create Session Request sent by the MME, the PGW learns that the established PDN connection is an emergency PDN connection according to the emergency APN in the message.

In this embodiment, the UE subscription information includes a cluster emergency service APN (ie, emergency APN), and whether the cluster call service is allowed to be initiated. The emergency APN can be formed by adding a special suffix or prefix to the common cluster service APN.

Referring to FIG. 3, the signaling interaction process of the foregoing process in Embodiment 2 may include:

Step 1: The UE sends a PDN Connectivity Request (PDN Connectivity Request) message to the MME to request to establish an emergency PDN connection for the cluster service. The Request type in the PDN Connectivity Request message is set to "group communication emergency".

Step 2: After receiving the PDN Connectivity Request message, the MME determines that the request is to establish an emergency PDN connection for the cluster service according to the request type of the message, so the UE is authenticated, and the UE subscription information is obtained after the authentication is passed. Cluster emergency call service APN.

Specifically, the MME obtains the subscription information of the UE, and determines whether the UE is allowed to initiate the cluster emergency service according to the subscription information of the UE. If yes, the cluster emergency service APN is obtained from the subscription information of the UE, and the following step 3 is performed. Otherwise, the process ends.

Step 3: If the UE subscription information indicates that the UE is allowed to initiate the trunk emergency call service, the MME uses the emergency APN in the UE subscription information to establish an emergency PDN connection for the UE for the UE.

Specifically, the MME requests the DNS (Domain Name Resolution Server) to perform domain name resolution according to the emergency AP in the UE subscription information, and resolves the IP address of the PGW, and sends a Session Set Request (Create Session Request) message to the PGW through the SGW, Create Session Request The message carries the emergency APN for the PGW Indicates that the established PDN connection is an emergency PDN connection.

Step 4: The PGW establishes a PDN connection as an emergency PDN connection according to the emergency APN attack carried in the Create Session Request, and the PGW does not perform restriction operations such as congestion control. The PGW returns a Create Session Response message, which is sent to the MME via the SGW.

Step 5: The MME returns a PDN Connection Response (PDN Connection Response) message to the UE to notify that the requested PDN connection has been successfully established.

As shown in the foregoing description of the second embodiment, the user equipment subscription information includes the APN of the cluster emergency service, and the PG that the MME resolves based on the APN of the cluster emergency service in the subscription information of the user equipment is the emergency call service of the cluster. The PGW of the EPC can ensure the realization of the cluster emergency call service.

Embodiment 3

This embodiment describes the emergency PDN connection that the UE allows to initiate the establishment of the cluster service, and sets the Request type to "group communication emergency" in the PDN connection request.

When the MME receives the PDN connection establishment request, the MME determines that the request is to establish an emergency PDN connection for the cluster service according to the request type, and determines whether the UE is allowed to initiate the cluster emergency service according to the subscription. If allowed, the MME obtains the common cluster from the subscription information of the UE. The service APN establishes an emergency PDN connection. The MME carries an indication in the Create Session Request, and indicates to the PGW that the established PDN connection is an emergency PD connection. Correspondingly, the UE subscription information includes the common cluster service APN, and whether the cluster call service is allowed to be initiated.

Referring to FIG. 4, the signaling interaction process of the foregoing process in Embodiment 3 may include:

Step 2: After receiving the PDN Connectivity Request message, the MME determines that the request is to establish an emergency PDN connection for the cluster service according to the request type of the message, so the UE is authenticated, and the UE subscription information is obtained after the authentication is passed. Ordinary cluster service APN.

Specifically, the MME obtains the subscription information of the UE, and determines, according to the subscription information of the UE, whether the UE is allowed to initiate the cluster emergency service, and if so, obtains the common cluster service APN of the UE from the subscription information of the UE, otherwise Process.

Step 3: If the UE subscription information indicates that the UE is allowed to initiate the trunk emergency call service, the MME establishes an emergency PDN connection for the UE by using the common cluster service APN in the UE subscription information. Specifically, the MME requests the DNS (Domain Name Resolution Server) to perform domain name resolution according to the APN obtained from the UE subscription information, and resolves the IP address of the PGW, and sends a Session Set Request (Create Session Request) message to the PGW through the SGW, Create Session The request message carries the indication information, and is used to indicate to the PGW that the established PDN connection is an emergency PDN connection.

Step 4: The PGW learns that the established PDN connection is an emergency PDN connection according to the indication information carried in the Create Session Request, and the PGW does not perform the restriction operation such as congestion control. The PGW returns a Create Session Response message, which is sent to the MME via the SGW.

Step 3: The MME returns a PDN Connection Response (PDN Connection Response) message to the UE to notify that the requested PDN connection has been successfully established.

As can be seen from the description of the third embodiment, the PGW that is parsed by the MME according to the APN of the common cluster service in the subscription information of the user equipment is the PGW of the cluster system accessing the EPC, because the user equipment subscription information includes the common cluster service APN. Therefore, the realization of the cluster emergency call service can be guaranteed.

Based on the same technical concept, the embodiment of the present application further provides a core network device. In an LTE system, the core network device may be an MME.

FIG. 5A is a schematic structural diagram of a core network device according to Embodiment 4 of the present application. The core network device may include: a receiving module 51, a determining module 52, and a PDN connection establishing module 53, where:

The receiving module 51 is configured to receive a PDN connection request for the trunk emergency call service sent by the user equipment, where the determining module 52 is configured to be used by the core network device according to the APN or the information carried in the PDN connection request received by the receiving module. The APN in the subscription information of the user equipment determines the PDN gateway PGW; wherein the APN in the subscription information of the user equipment may be a trunk emergency call service APN or a common trunk service APN;

The PDN connection establishing module 53 is configured to initiate a PDN connection establishment process for the trunk emergency call service for the user equipment according to the PGW determined by the determining module, and indicate that the established PDN connection is a PDN connection of the trunk emergency call service. .

Specifically, the request type of the PDN connection request for the cluster emergency call service received by the receiving module 51 is a cluster emergency call. Correspondingly, the receiving module 51 may determine, according to the request type of the PDN connection request, that the PDN connection request is a PDN connection request for the trunk emergency call service.

Further, as shown in FIG. 5B, an authentication module 54 may be further included, and the authentication module 54 may be carried according to the PDN connection request before the determining module 52 determines the PGW according to the APN carried in the PDN connection request. The subscription information of the APN and the user equipment determines whether the user equipment is allowed to initiate a trunk emergency call service for the APN carried in the PDN connection request. Correspondingly, the determining module 52 determines the PGW according to the APN carried in the PDN connection request, if it is determined to be allowed. Specifically, in the core network device shown in FIG. 5A or FIG. 5B, the PDN connection establishing module 53 may carry the indication information in the session establishment request sent to the determined PGW, indicating that the established PDN connection is a cluster. PDN connection for emergency call service.

Specifically, in the core network device shown in FIG. 5A or FIG. 5B, the APN carried in the PDN connection request is an ordinary cluster service APN, and the determining module is configured according to the common cluster service carried in the PDN connection request. The PGW determined by the APN is the PGW of the cluster system accessing the EPC.

Based on the same concept, the embodiment of the present application further provides an emergency service implementation system. The system can include: a PGW, and a core network device, where:

The core network device is configured to receive a PDN connection request for the trunk emergency call service sent by the user equipment, determine the PDN gateway PGW according to the APN carried in the PDN connection request, or according to the APN in the subscription information of the user equipment, Determining, according to the determined PGW, a PDN connection establishment procedure for the cluster emergency call service, and indicating that the established PDN connection is a PDN connection of the trunk emergency call service;

The functions that can be implemented by the core network device in the above system can be referred to the foregoing embodiment. The structure of the core network device can be as shown in FIG. 5A or FIG. 5B.

FIG. 6 is a schematic structural diagram of a core network device according to Embodiment 6 of the present application. The core network device may include: a processor 60 and a transceiver 61, where:

The processor 60 is configured to receive, by the transceiver 61, a PDN connection request for the trunk emergency call service sent by the user equipment, according to the APN carried in the received PDN connection request or the APN according to the subscription information of the user equipment. Determining a PDN gateway PGW; wherein the APN in the subscription information of the user equipment may be a trunk emergency call service APN or a common trunk service APN; and initiating a PDN connection for the trunk emergency call service for the user equipment according to the determined PGW Establishing a process, and indicating that the established PDN connection is a PDN connection of the trunk emergency call service;

The transceiver 61 is configured to receive and transmit data under the control of the processor 60.

Specifically, the request type of the PDN connection request for the trunk emergency call service is a cluster emergency call; the processor 60 determines, according to the request type of the PDN connection request, the PDN connection request is a PDN connection for the trunk emergency call service. request.

Further, before determining the PGW according to the APN carried in the PDN connection request, the processor 60 determines whether the user equipment is allowed according to the APN carried in the PDN connection request and the subscription information of the user equipment. The cluster emergency call service for the APN carried in the PDN connection request is initiated; if it is determined to be allowed, the PGW is determined according to the APN carried in the PDN connection request.

The processor 60 may carry the indication information in the session establishment request sent to the determined PGW, indicating that the established PDN connection is a PDN connection of the trunk emergency call service.

Specifically, the APN carried in the PDN connection request is an ordinary cluster service APN;

The processor 60 is specifically configured to: determine, according to the common cluster service APN carried in the PDN connection request, the PGW as a PGW of the cluster system accessing the EPC.

In Figure 6, the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 60 and various circuits of memory represented by memory 62. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein. The bus interface provides an interface. Transceiver 61 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium. The processor 60 is responsible for managing the bus architecture and general processing, and the memory 62 can store data used by the processor 60 in performing operations.

The processor 60 is responsible for managing the bus architecture and general processing, and the memory 62 can store data used by the processor 60 in performing the operations.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present application. It will be understood that each process and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram. While the preferred embodiment of the present application has been described, those skilled in the art can make further changes and modifications to these embodiments once they are aware of the basic inventive concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and the modifications and

It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the present invention.

Claims

Rights request

1. An emergency call implementation method, characterized by including:

The core network equipment receives the packet data network PDN connection request for the cluster emergency call service sent by the user equipment;

The core network device determines the PDN gateway PGW based on the access point name APN carried in the PDN connection request or based on the APN in the subscription information of the user equipment;

The core network device initiates a PDN connection establishment process for the cluster emergency call service for the user equipment based on the determined PGW, and instructs the established PDN connection to be a PDN connection for the cluster emergency call service.

2. The method of claim 1, wherein the request type of the PDN connection request for the cluster emergency call service is a cluster emergency call;

The core network device determines that the PDN connection request is a PDN connection request for the cluster emergency call service according to the request type of the PDN connection request.

3. The method according to claim 1, characterized in that, before the core network device determines the PGW according to the APN carried in the PDN connection request, it further includes: the core network device determines the PGW according to the APN carried in the PDN connection request. The APN and the subscription information of the user equipment, determine whether the user equipment is allowed to initiate a cluster emergency call service for the APN carried in the PDN connection request;

When the core network device determines that it is allowed, the PGW is determined based on the APN carried in the PDN connection request.

4. The method according to claim 1, characterized in that, the PDN connection established by the instruction is a PDN connection for the cluster emergency call service, specifically including:

The core network device indicates that the established PDN connection is a PDN connection for the cluster emergency call service by carrying indication information in the session establishment request sent to the determined PGW.

5. The method of claim 4, characterized in that the method further includes:

After the determined PGW receives the session establishment request, if the indication information is obtained from the received session establishment request, it refuses to perform congestion control.

6. The method according to any one of claims 1 to 5, characterized in that, the APN carried in the PDN connection request is a common cluster service APN, and the core network device determines The PGW determined by the common cluster service APN is the PGW through which the cluster system accesses the evolved packet core network EPC.

7. The method of claim 1, wherein the APN in the subscription information of the user equipment is a cluster emergency call service APN or a common cluster service APN.

8. A core network equipment, characterized by including: A receiving module, configured to receive a PDN connection request for the cluster emergency call service sent by the user equipment; a determining module, configured to determine the access point name carried in the PDN connection request received by the receiving module.

APN or determine the PDN gateway PGW based on the APN in the subscription information of the user equipment;

The PDN connection establishment module is configured to initiate a PDN connection establishment process for the cluster emergency call service for the user equipment based on the PGW determined by the determination module, and indicate that the established PDN connection is a PDN connection for the cluster emergency call service.

9. The core network device according to claim 8, wherein the request type of the PDN connection request for the cluster emergency call service received by the receiving module is a cluster emergency call;

The receiving module is specifically configured to determine, according to the request type of the PDN connection request, that the PDN connection request is a PDN connection request for the cluster emergency call service.

10. The core network equipment according to claim 8, further comprising:

An authentication module, configured to determine whether the user equipment is based on the APN carried in the PDN connection request and the subscription information of the user equipment before the determination module determines the PGW based on the APN carried in the PDN connection request. Allow the initiation of cluster emergency call services for the APN carried in the PDN connection request;

The determination module is specifically configured to determine the PGW according to the APN carried in the PDN connection request when it is determined that it is allowed.

11. The core network device according to claim 8, wherein the PDN connection establishment module is specifically configured to indicate the established session establishment request by carrying indication information in the session establishment request sent to the determined PGW. The PDN connection is the PDN connection of the cluster emergency call service.

12. The core network device according to any one of claims 8-11, characterized in that the APN carried in the PDN connection request is a common cluster service APN;

The determination module is specifically used for:

The PGW determined according to the common trunking service APN carried in the PDN connection request is the PGW for the trunking system to access the evolved packet core network EPC.

13. The core network device according to claim 8, wherein the APN in the subscription information of the user equipment is a cluster emergency call service APN or a common cluster service APN.

14. An emergency service implementation system, characterized by including: core network equipment, and packet data network PDN gateway PGW;

The core network device is configured to receive a packet data network PDN connection request for the cluster emergency call service sent by the user equipment, according to the access point name APN carried in the PDN connection request or according to the subscription information of the user equipment. Determine the PGW based on the APN, and initiate an emergency call for the cluster for the user equipment based on the determined PGW. The PDN connection establishment process of the service, and indicates that the established PDN connection is a PDN connection for the cluster emergency call service; the PGW is used to receive during the PDN connection establishment process for the cluster emergency call service initiated by the core network device. After receiving the session establishment request sent by the core network device, if it is determined that the established PDN connection is a PDN connection for the cluster emergency call service according to the received session establishment request, congestion control is refused to be performed.

15. A core network equipment, characterized by including:

A processor configured to receive, through a transceiver, a PDN connection request for the cluster emergency call service sent by the user equipment; according to the access point name APN carried in the received PDN connection request or according to the subscription information of the user equipment. The APN determines the PDN gateway PGW; according to the determined PGW, initiates a PDN connection establishment process for the cluster emergency call service for the user equipment, and indicates that the established PDN connection is a PDN connection for the cluster emergency call service;

A transceiver for receiving and transmitting data under the control of said processor.

16. The core network device according to claim 15, wherein the request type of the received PDN connection request for the cluster emergency call service is a cluster emergency call;

The processor is specifically configured to determine, according to the request type of the PDN connection request, that the PDN connection request is a PDN connection request for the cluster emergency call service.

17. The core network device according to claim 15, wherein the processor is further configured to: before determining the PGW according to the APN carried in the PDN connection request, based on the APN carried in the PDN connection request and the subscription information of the user equipment, determine whether the user equipment is allowed to initiate the cluster emergency call service for the APN carried in the PDN connection request; if it is determined to be allowed, based on the APN carried in the PDN connection request APN determines PGW.

18. The core network device according to claim 15, wherein the processor is specifically configured to: indicate the established session by carrying indication information in the session establishment request sent to the determined PGW.

The PDN connection is the PDN connection of the cluster emergency call service.

19. The core network device according to any one of claims 15-18, characterized in that the APN carried in the PDN connection request is a common cluster service APN;

The processor is specifically used for:

20. The core network device according to claim 15, wherein the APN in the subscription information of the user equipment is a cluster emergency call service APN or a common cluster service APN.