WO2017020746A1 - 一种建立紧急pdn连接的方法及设备 - Google Patents

一种建立紧急pdn连接的方法及设备 Download PDF

Info

Publication number
WO2017020746A1
WO2017020746A1 PCT/CN2016/091580 CN2016091580W WO2017020746A1 WO 2017020746 A1 WO2017020746 A1 WO 2017020746A1 CN 2016091580 W CN2016091580 W CN 2016091580W WO 2017020746 A1 WO2017020746 A1 WO 2017020746A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
emergency call
request message
user equipment
call service
Prior art date
Application number
PCT/CN2016/091580
Other languages
English (en)
French (fr)
Inventor
侯云静
Original Assignee
电信科学技术研究院
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 电信科学技术研究院 filed Critical 电信科学技术研究院
Publication of WO2017020746A1 publication Critical patent/WO2017020746A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for establishing an emergency packet data network (PDN) connection.
  • PDN packet data network
  • UE User equipment
  • 3GPP 3rd Generation Partnership Project
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • WLAN Wireless Local Area Networks
  • the WLAN network connected to the carrier's core network can be divided into a trusted WLAN network and an untrusted WLAN network. Whether the WLAN network is trusted or not is determined by the operator. For example, the WLAN network deployed by other carriers deployed by the operator or contracted with the operator is a trusted WLAN, and the others are non-trusted WLAN networks.
  • a schematic diagram of a logical architecture of a Trusted WLAN Access Network includes a WLAN access network, a trusted WLAN access gateway, and a trusted WLAN AAA proxy.
  • Step S201 The UE sends a WLAN control protocol (WLCP) PDN connection request message to the TWAN.
  • WLCP WLAN control protocol
  • Step S203 The TWAN sends a create session request message to the PDN GateWay (PGW).
  • PGW PDN GateWay
  • Step S205 PGW to Policy and Charging Rules (Policy and Charging Rules Function, PCRF) initiates an IP-Connectivity Access Network (IP-CAN) session establishment process.
  • Policy and Charging Rules Function Policy and Charging Rules Function
  • Step S207 The PGW updates the information of the PGW stored in the Home Subscriber Server (HSS).
  • HSS Home Subscriber Server
  • the PGW sends the Access Point Name (APN) and its own identifier (such as an IP address). Give HSS.
  • APN Access Point Name
  • IP address such as an IP address
  • Step S209 The PGW returns a create session reply message to the TWAN.
  • GTP GPRS Tunneling Protocol
  • Step S213 The TWAN returns a WLCP PDN connection reply message to the UE.
  • FIG. 3 a network architecture diagram of a UE connecting to a core network through a non-trusted WLAN network.
  • An untrusted WLAN network cannot connect directly to a PGW in the core network, but instead connects to the PGW through a security gateway.
  • the security gateway is the evolved Packet Data Gateway (ePDG) in FIG.
  • the UE can establish multiple PDN connections through the non-trusted WLAN network.
  • Each PDN connection consists of two parts: 1) an Internet Protocol Security (IPSec) tunnel between the UE and the ePDG; 2) a GTP between the ePDG and the PGW. /PMIP (Proxy Mobile IP) tunnel (depending on whether the operator deploys GTP or PMIP between ePDG and PGW).
  • IPSec Internet Protocol Security
  • PMIP Proxy Mobile IP
  • Step S401 Perform an access authentication process between the UE and the 3GPP Packet Core Evolution (EPC).
  • EPC 3GPP Packet Core Evolution
  • Step S403 The UE obtains an IP address of the ePDG through a domain name system (DNS), and then initiates an IKEv2 (an Internet Key Exchange Protocol) authentication and tunnel establishment process.
  • DNS domain name system
  • IKEv2 Internet Key Exchange Protocol
  • Step S405 The ePDG sends a Proxy Binding Update (PBU) message to the PGW, where the message carries parameters such as a UE identifier, an Access Point Name (APN), an access technology type, and a handover prompt.
  • PBU Proxy Binding Update
  • Step S407 PGW to PCRF (Policy and Charging Rules Function, strategy and The charging rule function unit) initiates an IP-CAN session establishment process.
  • PCRF Policy and Charging Rules Function
  • Step S409 The PGW notifies the 3GPP AAA Server (AAA server) of the identifier of the PGW.
  • Step S411 The PGW processes the proxy binding update, allocates an IP address to the UE, and returns a Proxy Binding Ack (PBA) message to the ePDG, where the message carries the UE identifier, the UE IP address, and the like.
  • PBA Proxy Binding Ack
  • Step S413 The ePDG indicates to the UE that the authentication with the AAA server is successful.
  • Step S415 The ePDG sends a final IKEv2 message to the UE, where the message carries the UE IP address.
  • Step S417 the IP connection of the UE to the PGW is successfully established.
  • the UE sends an emergency request indication to the 3GPP AAA Server in step S401.
  • the UE initiates an IKEv2 tunnel establishment process in step S403, in which the 3GPP AAA Server sends an emergency call prompt to the ePDG.
  • the ePDG uses the locally configured emergency configuration data to select a particular PGW for the UE.
  • the ePDG sends an emergency call prompt to the PGW in step S405.
  • the existing method Since the existing method only supports establishing an emergency call through the attach procedure, when the attached UE wishes to perform an emergency call, it needs to first attach and then reattach, and establish an emergency PDN connection during the attach process. That is, after the UE connects to the carrier network through the non-trusted WLAN network, the existing method for the UE to establish an emergency PDN connection is that the UE detaches from the network, then reattaches, and establishes an emergency PDN connection in the process of re-attachment. . Since the detach procedure will release all PDN connections that the UE has established, the existing method will cause the upper application to be disconnected, which will affect the user's service experience.
  • an embodiment of the present disclosure provides a method and a device for establishing an emergency PDN connection.
  • a UE performs an emergency call, if the network currently connected by the UE supports an emergency call, the UE may not need to be detached from the network.
  • the process of establishing an emergency call PDN connection is directly initiated, which avoids the problem that the upper layer application is interrupted due to detachment in the related art.
  • An aspect of the present disclosure provides a method for establishing an emergency PDN connection.
  • the method includes: receiving a first request message sent by a user equipment, where the first request message carries an emergency call prompt; and prompting according to the emergency call And determining whether the network device supports an emergency call service; if the network device does not support the emergency call service, returning a first reply message to the user equipment.
  • a method of establishing an emergency PDN connection comprising: receiving a second request message sent by a user equipment; returning a second request message to the user equipment And replying to the message, where the second reply message carries information about whether the network device supports the emergency call service.
  • a method for establishing an emergency PDN connection comprising: transmitting a first request message to a network device, where the first request message carries an emergency call prompt; When the network device does not support the emergency call service, the network device is received to return a first reply message.
  • a method for establishing an emergency PDN connection comprising: transmitting a second request message to a network device; receiving a second reply of the network device returning the second request message The message, the second reply message carries information about whether the network device supports an emergency call service.
  • a network device including: a first receiving module, configured to receive a first request message sent by a user equipment, where the first request message carries an emergency call prompt; And determining, according to the emergency call prompt, whether the network device supports the emergency call service, and the first sending module, configured to return a first reply message to the user equipment if the network device does not support the emergency call service.
  • a network device including: a second receiving module, configured to receive a second request message sent by the user equipment; and a second sending module, configured to return the And a second reply message of the second request message, where the second reply message carries information about whether the network device supports the emergency call service.
  • a user equipment including: a third sending module, configured to send a first request message to a network device, where the first request message carries an emergency call prompt; and the third receiving And a module, configured to: when the network device does not support an emergency call service, receive the network device to return a first reply message.
  • a user equipment including: a fourth sending module, configured to send a second request message to a network device; and a fourth receiving module, configured to receive, by the network device, the first And a second reply message of the request message, where the second reply message carries information about whether the network device supports the emergency call service.
  • the utility model has the beneficial effects that when the UE performs an emergency call, if the network currently connected by the UE supports the emergency call, the UE may not need to be detached from the network, and may directly initiate the establishment process of the emergency call PDN connection, which avoids related technologies.
  • the problem of the upper application being interrupted due to detachment.
  • the UE can confirm whether the network supports the emergency call service before requesting the establishment of the emergency PDN connection to the network, the problem of signaling waste is effectively avoided.
  • FIG. 1 is a schematic diagram of a logical architecture of a trusted WLAN network in the related art
  • FIG. 2 is a schematic diagram of a process of attaching a UE through a trusted WLAN network in the related art
  • FIG. 3 is a network architecture diagram of a UE connected to a core network through a non-trusted WLAN network in related art
  • FIG. 5 is a flowchart of a method for establishing an emergency PDN connection in a first embodiment of the present disclosure
  • FIG. 6 is a flowchart of a method for establishing an emergency PDN connection in a second embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of establishing an emergency call by a UE that has been attached to a network in a third embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram of a UE that has been attached to a network being rejected when establishing an emergency PDN connection according to a fourth embodiment of the present disclosure
  • FIG. 9 is a flowchart of a method for establishing an emergency PDN connection in a fifth embodiment of the present disclosure.
  • FIG. 10 is a flowchart of a method for establishing an emergency PDN connection in a sixth embodiment of the present disclosure
  • FIG. 11 is a schematic diagram of a UE that has attached to a network through a normal attach procedure in a seventh embodiment of the present disclosure, wishing to establish an emergency PDN connection;
  • FIG. 12 is a schematic diagram of a UE connected to an ePDG through a normal attach procedure in the eighth embodiment of the present disclosure wishing to establish an emergency PDN connection;
  • FIG. 12 is a schematic diagram of a UE connected to an ePDG through a normal attach procedure in the eighth embodiment of the present disclosure wishing to establish an emergency PDN connection;
  • FIG. 13 is a structural diagram of a network device in a ninth embodiment of the present disclosure.
  • FIG. 14 is a structural diagram of a network device in a tenth embodiment of the present disclosure.
  • Figure 15 is a structural diagram of a user equipment in an eleventh embodiment of the present disclosure.
  • 16 is a structural diagram of a user equipment in a twelfth embodiment of the present disclosure.
  • Figure 17 is a structural diagram of a network device in a thirteenth embodiment of the present disclosure.
  • Figure 18 is a structural diagram of a network device in a fourteenth embodiment of the present disclosure.
  • Figure 19 is a structural diagram of a user equipment in a fifteenth embodiment of the present disclosure.
  • Figure 20 is a structural diagram of a user equipment in a sixteenth embodiment of the present disclosure.
  • the execution subject of the method is a network device, and the method includes:
  • Step S501 Receive a first request message sent by the user equipment, where the first request message carries an emergency call prompt.
  • the first request message may be a WLCP PDN connection request message or an IKE_AUTH REQ message. It should be noted that the specific type of the first request message is not limited in this embodiment.
  • step S503 it is determined whether the network device supports the emergency call service according to the emergency call prompt. If the network device does not support the emergency call service, the process proceeds to step S505. If the network device supports the emergency call service, the process proceeds to step S507.
  • the network device may be an ePDG or a TWAN device.
  • the user equipment mentioned in step S501 refers to a user equipment that can be connected to the core network through a non-trusted WLAN network, or Connect to the user equipment of the core network through the TWAN network.
  • Step S505 returning a first reply message to the user equipment.
  • the first reply message may carry a reason for rejection, for example, the reason for the rejection is used to indicate that the network device does not support the emergency call service.
  • Step S507 performing an emergency PDN connection establishment process.
  • the related technology can be used to establish an emergency PDN connection, which is not described here.
  • the UE When the UE performs an emergency call, the UE may not need to be detached from the network, and may directly initiate an establishment process of the emergency call PDN connection, thereby avoiding the problem that the upper layer application is interrupted due to detachment in the related art. Moreover, since the UE can confirm whether the network supports the emergency call service before requesting the establishment of the emergency PDN connection to the network, the problem of signaling waste is effectively avoided.
  • the method may be a user equipment, and the method includes:
  • Step S601 Send a first request message to the network device, where the first request message carries an emergency call prompt, and then proceeds to step S603 or step S605.
  • the first request message may be a WLCP PDN connection request message or an IKE_AUTH REQ message. It should be noted that the specific type of the first request message is not limited in this embodiment.
  • the user equipment may be connected to the core network through a non-trusted WLAN network, or the user equipment may be connected to the core network through a TWAN network.
  • the network device may be an ePDG or a TWAN device.
  • Step S603 When the network device does not support the emergency call service, the receiving network device returns a first reply message, and then proceeds to step S607.
  • the first reply message may carry a reason for rejection, and the reason for the rejection may be used to indicate that the network device does not support the emergency call service.
  • Step S605 Receive a PDN connection accept message returned by the network device when the network device supports the emergency call service.
  • the PDN connection accept message may be a WLCP PDN connection reply message or an IKE_AUTH RESP message.
  • the specific type of PDN connection accept message is not limited in this embodiment.
  • Step S607 After receiving the first reply message, initiate a detach process to the network device.
  • the user equipment after the user equipment receives the first reply message, the user equipment performs detachment, then selects a network supporting the emergency call, and then reattaches to the network, and may be heavy An emergency call PDN connection is requested during the new attach procedure.
  • FIG. 7 a process of establishing an emergency call by a UE that has been attached to the network under the network architecture based on the S2a interface is shown.
  • Step S701 The UE sends a WLCP PDN connection request message to the TWAN.
  • the WLCP PDN connection request message carries an emergency call prompt. If the TWAN supports the emergency call service, the process goes to step S703. If the TWAN does not support the emergency call service, the process goes to step S709.
  • Step S703 The TWAN selects the PGW for the UE by using the emergency configuration data, and then sends a Create Session Request message to the PGW, where the Create Session Request message carries an emergency call prompt.
  • Step S705 The PGW returns a create session reply message to the TWAN.
  • Step S707 The TWAN returns a WLCP PDN connection reply message to the UE.
  • Step S709 The TWAN returns a WLCP PDN connection reject message to the UE, and the WLCP PDN connection reject message may carry the reject reason, indicating that the TWAN does not support the emergency call service.
  • the UE After the UE receives the WLCP PDN Connection Reject message, the UE detaches, reselects the TWAN supporting the emergency call service, reattaches to the network through the TWAN, and then requests to establish an emergency PDN connection.
  • the UE when the UE performs an emergency call, the UE may not need to be detached from the network, and may directly initiate an establishment process of the emergency call PDN connection, thereby avoiding the problem that the upper layer application is interrupted due to detachment in the related art.
  • the process of the UE that has been attached to the network is rejected when establishing an emergency PDN connection in the network architecture based on the S2b interface, and the specific steps are as follows:
  • Step S801 The UE sends an IKE_SA_INIT message to the ePDG to initiate an initial exchange of the IKEv2 process.
  • An untrusted WLAN network cannot connect directly to a PGW in the core network, but instead connects to the PGW through a security gateway.
  • the security gateway is the ePDG (Evolved Packet Data Gateway) in FIG.
  • Step S803 the ePDG returns an IKE_SA_INIT message to the UE.
  • Step S805 The UE sends an IKE_AUTH REQ message to the ePDG, where the message carries parameters such as an APN (Access Point Name, an access point name) and an emergency call prompt.
  • APN Access Point Name, an access point name
  • Step S805 The ePDG does not support the emergency call service, and returns an IKE_AUTH RSP message to the UE.
  • the message carries the reason for the rejection.
  • the reason indicates that the ePDG does not support the emergency call service.
  • the UE After receiving the reason for the rejection, the UE detaches from the currently connected ePDG. For details, refer to section 7.4 of 3GPP TS 23.402, which is not described here. The UE then selects the ePDG that supports the emergency call, then initiates the attach procedure and establishes an emergency PDN connection during the attach procedure.
  • the connection establishment process is different from the existing process: the UE sends an emergency call prompt to the ePDG in the IKE_AUTH REQ message (step S805), and the ePDG selects the PGW for the UE according to the locally configured emergency configuration data, and When a GTP/PMIP tunnel establishment request is sent to the PGW, an emergency call request is sent to the PGW.
  • the UE when the UE performs an emergency call, the UE may not need to be detached from the network, and may directly initiate an establishment process of the emergency call PDN connection, thereby avoiding the problem that the upper layer application is interrupted due to detachment in the related art.
  • FIG. 9 a flowchart of a method for establishing an emergency PDN connection is shown.
  • the execution body of the method is a network device, and the specific steps are as follows:
  • Step S901 Receive a second request message sent by the user equipment, where the second request message carries an emergency call prompt.
  • the network device may be an ePDG or a TWAN device.
  • the user equipment mentioned in step S901 refers to a user equipment that can be connected to the core network through a non-trusted WLAN network, or Connect to the user equipment of the core network through the TWAN network.
  • the WLCP emergency capability request message may be used to indicate the second request message, where the second request message may be used to request the TWAN device to determine whether it supports the emergency call service.
  • the IKE information request message may be used to indicate the second request message, and the second request message is used to request the ePDG to determine whether it supports the emergency call service.
  • Step S903 Return a second reply message of the second request message to the user equipment, where the second reply message carries information about whether the network device supports the emergency call service.
  • the network setting can be represented by the parameter value of the specific information in the second reply message. Whether to support emergency call service. It is of course understood that the specific parameter value is not limited in this embodiment.
  • step S905 the network device supports the emergency call service, and after receiving the third request message sent by the user equipment, performs an emergency PDN connection establishment process according to the third request message, where the third request message carries an emergency call prompt.
  • the third request message may be a WLCP PDN connection request message or an IKE_AUTH REQ message. It should be noted that the specific type of the third request message is not limited in this embodiment.
  • the execution body of the method may be a user equipment.
  • the specific steps are as follows:
  • Step S1001 Send a second request message to the network device, where the second request message carries an emergency call prompt.
  • the network device may be an ePDG or a TWAN device.
  • the user equipment refers to a user equipment that can be connected to the core network through a non-trusted WLAN network, or is connected to the TWAN network. User equipment of the core network.
  • the WLCP emergency capability request message may be used to indicate the second request message, where the second request message may be used to request the TWAN device to determine whether it supports the emergency call service.
  • the IKE information request message may be used to indicate the second request message, and the second request message is used to request the ePDG to determine whether it supports the emergency call service.
  • Step S1003 The receiving network device returns a second reply message of the second request message, where the reply message carries information about whether the network device supports the emergency call service.
  • parameter value of the specific information in the second reply message may indicate whether the network device supports the emergency call service. It is of course understood that the specific parameter value is not limited in this embodiment.
  • Step S1005 When the network device supports the emergency call service, send a third request message to the network device, where the third request message carries an emergency call prompt.
  • Step S1007 When the network device does not support the emergency call service, initiate a detach process to the network device.
  • step S1005 and step S1007 are optional steps in this embodiment.
  • the UE that has attached to the network through the normal attach procedure needs to establish an emergency PDN connection, and the UE first determines whether the TWAN (trusted WLAN network) supports the emergency call service, as follows:
  • Step S1101 The UE sends a WLCP emergency call request message to the TWAN, and the information carried in the WLCP emergency call request message indicates whether the TWAN supports the emergency call service.
  • Step S1103 The TWAN returns a WLCP emergency call reply message to the UE, and the information carried in the WLCP emergency call reply message indicates whether the TWAN supports the emergency call service.
  • the UE when the UE performs an emergency call, the UE may not need to be detached from the network, and may directly initiate an establishment process of the emergency call PDN connection, thereby avoiding the problem that the upper layer application is interrupted due to detachment in the related art.
  • the UE that connects to the ePDG through the normal attach procedure is required to establish an emergency PDN connection in the S2b scenario, and the UE determines whether the ePDG supports the emergency call service.
  • the specific process is as follows:
  • Step S1201 The UE sends an IKE information request message to the ePDG, where the message carries an emergency call prompt, and is used to request whether the ePDG has the capability of supporting an emergency call.
  • Step S1203 The ePDG returns an IKE information reply message to the UE, where the information carried in the message indicates whether the ePDG supports the emergency call service.
  • the UE initiates a PDN connection establishment process to the ePDG, and the UE carries an emergency call prompt in the message.
  • the ePDG selects the PGW according to the locally configured emergency configuration data. Then, a GTP/PMIP tunnel establishment process is initiated to the PGW, and an emergency call prompt is carried in the request message.
  • the UE detaches, reselects the ePDG that supports the emergency call, then re-attaches, and establishes an emergency PDN connection in the process of re-attaching, the process is related to the technology. It will not be described here.
  • the UE when the UE wishes to perform an emergency call, if the UE learns that the currently connected network side entity supports the emergency call, the UE needs to be detached from the network, and the establishment process of the emergency PDN connection can be directly initiated.
  • the network device includes: a first receiving module 1301, a determining module 1303, and a first sending module 1305, where
  • the first receiving module 1301 is configured to receive a first request message sent by the user equipment, where the first request message carries an emergency call prompt.
  • the first request message may be a WLCP PDN connection request message or an IKE_AUTH REQ message. It should be noted that the specific type of the first request message is not limited in this embodiment.
  • the determining module 1303 is configured to determine, according to the emergency call prompt, whether the network device supports the emergency call service.
  • the network device may be an ePDG or a TWAN device.
  • the user equipment refers to a user equipment that can be connected to the core network through a non-trusted WLAN network, or is connected to the TWAN network. User equipment of the core network.
  • the first sending module 1305 is configured to return a first reply message to the user equipment if the network device does not support the emergency call service.
  • the first reply message may carry a reason for rejection, for example, the reason for the rejection is used to indicate that the network device does not support the emergency call service.
  • the network device may further include: a first connection establishing module 1307, configured to perform an emergency PDN connection establishment process if the network device supports the emergency call service.
  • a first connection establishing module 1307 configured to perform an emergency PDN connection establishment process if the network device supports the emergency call service.
  • the related technology can be used to establish an emergency PDN connection, which is not described here.
  • the network device includes: a second receiving module 1401 and a second sending module 1403, where:
  • the second receiving module 1401 is configured to receive a second request message sent by the user equipment.
  • the second sending module 1403 is configured to return, to the user equipment, a second reply message of the second request message, where the second reply message carries information about whether the network device supports an emergency call service.
  • the network device further includes: a second connection establishing module, configured to be in the network device The emergency call service is supported, and after receiving the third request message sent by the user equipment, the emergency PDN connection establishment process is performed according to the third request message, where the third request message carries an emergency call prompt.
  • a second connection establishing module configured to be in the network device The emergency call service is supported, and after receiving the third request message sent by the user equipment, the emergency PDN connection establishment process is performed according to the third request message, where the third request message carries an emergency call prompt.
  • the user equipment includes: a third sending module 1501 and a third receiving module 1503, wherein
  • the third sending module 1501 is configured to send a first request message to the network device, where the first request message carries an emergency call prompt.
  • the first request message may be a WLCP PDN connection request message or an IKE_AUTH REQ message. It should be noted that the specific type of the first request message is not limited in this embodiment.
  • the user equipment may be connected to the core network through a non-trusted WLAN network, or the user equipment may be connected to the core network through a TWAN network.
  • the network device may be an ePDG or a TWAN device.
  • the third receiving module 1503 is configured to: when the network device does not support the emergency call service, the receiving network device returns a first reply message.
  • the first reply message may carry a reason for rejection, and the reason for the rejection may be used to indicate that the network device does not support the emergency call service.
  • the user equipment further includes: a fifth receiving module, configured to receive a PDN connection accept message returned by the network device when the network device supports the emergency call service.
  • a fifth receiving module configured to receive a PDN connection accept message returned by the network device when the network device supports the emergency call service.
  • the user equipment further includes: a fifth sending module, configured to initiate a detach process to the network device after receiving the first reply message.
  • a fifth sending module configured to initiate a detach process to the network device after receiving the first reply message.
  • the user equipment includes:
  • the fourth sending module 1601 is configured to send a second request message to the network device.
  • the network device may be an ePDG or a TWAN device, and correspondingly, the user device refers to a non-trusted WLAN network.
  • the WLCP emergency capability request message may be used to indicate the second request message, where the second request message may be used to request the TWAN device to determine whether it supports the emergency call service; if the network device is an ePDG
  • the second request message may be represented by an IKE information request message, and the second The request message is used to request the ePDG to determine whether it supports the emergency call service itself.
  • the fourth receiving module 1603 is configured to receive a second reply message that the network device returns the second request message, where the second reply message carries information about whether the network device supports the emergency call service. It should be noted that the parameter value of the specific information in the second reply message may indicate whether the network device supports the emergency call service. It is of course understood that the specific parameter value is not limited in this embodiment.
  • the user equipment further includes: a third connection establishing module, configured to support the emergency call service in the network device, and after receiving the third request message sent by the user equipment, perform the emergency PDN according to the third request message.
  • the connection establishment process wherein the third request message carries an emergency call prompt.
  • the third request message may be a WLCP PDN connection request message or an IKE_AUTH REQ message. It should be noted that the specific type of the third request message is not limited in this embodiment.
  • a network device including: a first processor 1701, a first memory 1702, and a first transceiver 1703, wherein
  • the first processor 1701 is configured to read the program in the first memory 1702, and execute the following process: receiving a first request message sent by the user equipment, where the first request message carries an emergency call prompt; according to the emergency call prompt And determining whether the network device supports an emergency call service; if the network device does not support the emergency call service, returning a first reply message to the user equipment.
  • the first transceiver 1703 is configured to receive and transmit data under the control of the first processor 1701.
  • the first processor 1701 is further configured to perform an emergency PDN connection establishment process if the network device supports the emergency call service.
  • the first processor 1701 may be a CPU (Central Embedded Device), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic). Device, complex programmable logic device).
  • CPU Central Embedded Device
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • CPLD Complex Programmable Logic
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by the first processor 1701 and various circuits of the memory represented by the first memory 1702. .
  • the bus architecture can also be used for peripherals, voltage regulators and power Various other circuits, such as rate management circuits and the like, are linked together, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • the first transceiver 1703 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the first processor 1701 is responsible for managing the bus architecture and general processing, and the first memory 1702 can store data used by the first processor 1701 when performing operations.
  • the UE may not need to be detached from the network, and may directly initiate the establishment process of the emergency call PDN connection, thereby avoiding the interruption of the upper layer application due to de-attachment in the related art. The problem.
  • a network device including: a second processor 1801, a second memory 1802, and a second transceiver 1803, wherein
  • the second processor 1801 is configured to read the program in the second memory 1802, and execute the following process: receiving a second request message sent by the user equipment, and returning a second reply message of the second request message to the user equipment, where The second reply message carries information about whether the network device supports an emergency call service
  • the second transceiver 1803 is configured to receive and transmit data under the control of the second processor 1801.
  • the second processor 1801 is further configured to: when the network device supports the emergency call service, and after receiving the third request message sent by the user equipment, perform an emergency PDN connection according to the third request message.
  • the second processor 1801 may be a CPU (Central Embedded Device), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic). Device, complex programmable logic device).
  • CPU Central Embedded Device
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • CPLD Complex Programmable Logic
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by the first processor 1801 and various circuits of the memory represented by the first memory 1802. .
  • 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.
  • the first transceiver 1803 can be a plurality of components, including a transmitter and a transceiver, provided for use on a transmission medium and various He is the unit that communicates with the device.
  • the first processor 1801 is responsible for managing the bus architecture and the usual processing, and the first memory 1802 can store data used by the first processor 1801 when performing operations.
  • the UE may not need to be detached from the network, and may directly initiate the establishment process of the emergency call PDN connection, thereby avoiding the interruption of the upper layer application due to de-attachment in the related art. The problem.
  • a user equipment including: a third processor 1901, a third memory 1902, and a third transceiver 1903, wherein
  • the third processor 1901 is configured to read the program in the third memory 1902, and execute the following process: sending a first request message to the network device, where the first request message carries an emergency call prompt; when the network device does not support the emergency call service The receiving network device returns a first reply message.
  • the third transceiver 1903 is configured to receive and transmit data under the control of the third processor 1901.
  • the third processor 1901 is further configured to receive a PDN connection accept message returned by the network device when the network device supports the emergency call service.
  • the third processor 1901 is further configured to initiate a detach process to the network device after receiving the first reply message.
  • the third processor 1901 may be a CPU (Central Embedded Device), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic). Device, complex programmable logic device).
  • CPU Central Embedded Device
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • CPLD Complex Programmable Logic
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by the third processor 1901 and various circuits of the memory represented by the third memory 1902. .
  • 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.
  • the third transceiver 1903 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the third processor 1901 is responsible for managing the bus architecture and the usual processing, and the third memory 1902 can store data used by the third processor 1901 when performing operations.
  • the first user interface 1905 may also be an interface capable of externally connecting the required devices.
  • Connected devices include, but are not limited to, a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the UE may not need to be detached from the network, and may directly initiate the establishment process of the emergency call PDN connection, thereby avoiding the interruption of the upper layer application due to de-attachment in the related art. The problem.
  • a user equipment including: a fourth processor 2001, a fourth memory 2002, and a fourth transceiver 2003, wherein
  • the fourth processor 2001 is configured to read the program in the fourth memory 2002, and execute the following process: sending a second request message to the network device, and receiving a second reply message, the second reply message, that the network device returns the second request message
  • sending a second request message to the network device and receiving a second reply message, the second reply message, that the network device returns the second request message
  • the information about whether the network device supports an emergency call service is carried.
  • the fourth transceiver 2003 is for receiving and transmitting data under the control of the fourth processor 2001.
  • the fourth processor 2001 is further configured to: when the network device supports the emergency call service, and after receiving the third request message sent by the user equipment, perform an emergency PDN connection establishment process according to the third request message, where the third The request message carries an emergency call prompt.
  • the fourth processor 2001 may be a CPU (Central Embedded Device), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic). Device, complex programmable logic device).
  • CPU Central Embedded Device
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • CPLD Complex Programmable Logic
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by the fourth processor 2001 and various circuits of the memory represented by the fourth memory 2002. .
  • 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.
  • the fourth transceiver 2003 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the fourth processor 2001 is responsible for managing the bus architecture and the usual processing, and the fourth memory 2002 can store data used by the fourth processor 2001 when performing operations.
  • the second user interface 2005 may also be an interface capable of externally connecting the required devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the UE may not need to De-attachment in the network can directly initiate the establishment process of the emergency call PDN connection, thereby avoiding the problem that the upper layer application is interrupted due to de-attachment in the related art.
  • the disclosed method and apparatus may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the above software functional units are stored in a storage medium, including partial steps if the dry instructions are used 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 disclosure.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, and the program code can be stored. Medium.

Landscapes

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

Abstract

本公开提供了一种建立紧急PDN连接的方法及设备，该方法包括：接收用户设备发送的第一请求消息，所述第一请求消息中携带有紧急呼叫提示；根据所述紧急呼叫提示，判断网络设备是否支持紧急呼叫业务；若所述网络设备不支持紧急呼叫业务，则向所述用户设备返回第一回复消息。

Description

一种建立紧急PDN连接的方法及设备
相关申请的交叉引用
本申请主张在2015年8月3日在中国提交的中国专利申请号No.201510481223.9的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种建立紧急分组数据网(Packet Data Network，PDN)连接的方法及设备。
背景技术
用户设备(UE)可以通过第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)接入网络(由国际标准化组织3GPP定义的接入网络，例如Evolved Universal Terrestrial Radio Access Network，E-UTRAN)建立紧急PDN连接。随着无线局域网(Wireless Local Area Networks，WLAN)网络的发展，越来越多的用户通过WLAN网络连接到运营商的核心网，因此出现了UE可通过WLAN网络建立紧急呼叫的需求。
连接到运营商的核心网的WLAN网络可分为可信WLAN网络和非可信WLAN网络。WLAN网络是否可信是由运营商决定的，例如由运营商部署或与运营商有签约关系的其他运营商部署的WLAN网络是可信WLAN，其他为非可信WLAN网络。
参见图1，为可信WLAN网络(Trusted WLAN Access Network，TWAN)的逻辑架构示意图，TWAN包括：WLAN接入网络、可信WLAN接入网关和可信WLANAAA代理。
下面简要介绍UE通过TWAN建立PDN连接的过程，具体过程如图2所示。
步骤S201、UE向TWAN发送无线局域网控制协议(WLAN control protocol，WLCP)PDN连接请求消息。
步骤S203、TWAN向PDN网关(PDN GateWay，PGW)发送创建会话请求消息。
步骤S205、PGW向策略与计费规则功能单元(Policy and Charging Rules  Function，PCRF)发起IP连接访问网络(IP-Connectivity Access Network，IP-CAN)会话建立过程。
步骤S207、PGW更新归属用户服务器(Home Subscriber Server，HSS)中存储的PGW的信息，在该步骤中，PGW将接入点名称(Access Point Name，APN)和自身的标识(如IP地址)发送给HSS。
步骤S209、PGW向TWAN返回创建会话回复消息。
步骤S211、TWAN和PGW之间的GPRS隧道协议(GPRS Tunneling Protocol，GTP)隧道建立成功。
步骤S213、TWAN向UE返回WLCP PDN连接回复消息。
参见图3，为UE通过非可信WLAN网络连接到核心网的网络架构图。非可信WLAN网络不能直接连接到核心网内的PGW，而是通过一个安全网关连接到PGW。该安全网关即为图3中的演进的分组数据网关(evolved Packet Data Gateway，ePDG)。
UE可通过非可信WLAN网络建立多条PDN连接，每条PDN连接由两部分组成：1)位于UE和ePDG之间的因特网协议安全(IPSec)隧道；2)位于ePDG和PGW之间的GTP/PMIP(Proxy Mobile IP)隧道(取决于运营商在ePDG和PGW之间部署的是GTP协议还是PMIP协议)。IPSec隧道和GTP/PMIP隧道之间一一映射。
下面简要介绍UE通过非可信WLAN网络的附着过程(以ePDG和PGW之间使用PMIP协议为例)，具体过程如图4所示。
步骤S401、UE和3GPP分组核心演进(Evolved Packet Core，EPC)之间执行接入认证过程。
步骤S403、UE通过域名系统(Domain Name System，DNS)解析获取ePDG的IP地址，然后发起IKEv2(一种互联网密钥交换协议)认证和隧道建立过程。
步骤S405、ePDG向PGW发送代理绑定更新(Proxy Binding Update，PBU)消息，消息中携带UE标识、APN(Access Point Name，接入点名称)、接入技术类型和切换提示等参数。
步骤S407、PGW向PCRF(Policy and Charging Rules Function，策略与 计费规则功能单元)发起IP-CAN会话建立过程。
步骤S409、PGW向3GPPAAA Server(AAA服务器)通知PGW的标识。
步骤S411、PGW处理代理绑定更新，为UE分配IP地址，向ePDG返回代理绑定确认(Proxy Binding Ack，PBA)消息，消息中携带UE标识，UE IP地址等参数。
步骤S413、ePDG向UE表明与AAA server之间的认证成功。
步骤S415、ePDG向UE发送最终的IKEv2消息，该消息中携带UE IP地址。
步骤S417、UE到PGW的IP连接成功建立。
目前已经有通过非可信WLAN网络建立紧急呼叫的方法，该方法对图4中的附着过程(UE为获取正常业务而发起的附着过程)进行了下述修改：
1、UE在步骤S401中将紧急呼叫提示(emergency request indication)发送给3GPP AAA Server。
2、UE在步骤S403发起IKEv2隧道建立过程，在该过程中3GPP AAA Server将紧急呼叫提示发送给ePDG。ePDG使用本地配置的紧急配置数据为UE选择特定的PGW。
3、ePDG在步骤S405将紧急呼叫提示发送给PGW。
由于现有方法只支持通过附着过程建立紧急呼叫，因此当已附着的UE希望执行紧急呼叫时，其需要先去附着，然后再重新附着，并在附着的过程中建立紧急PDN连接。也就是说，当UE通过非可信WLAN网络连接到运营商网络之后，UE建立紧急PDN连接的现有方法是UE从网络中去附着，然后重新附着，在重新附着的过程中建立紧急PDN连接。由于去附着过程将释放UE已建立的所有PDN连接，所以现有方法将导致上层应用断开，这将影响用户的服务体验。
发明内容
鉴于上述技术问题，本公开的实施例提供一种建立紧急PDN连接的方法及设备，当UE执行紧急呼叫时，如果UE当前连接的网络支持紧急呼叫，UE可以不需要从网络中去附着，可直接发起紧急呼叫PDN连接的建立过程，避免了相关技术中因去附着而导致上层应用中断的问题。
本公开的一个方面，提供了一种建立紧急PDN连接的方法所述方法包括：接收用户设备发送的第一请求消息，所述第一请求消息中携带有紧急呼叫提示；根据所述紧急呼叫提示，判断所述网络设备是否支持紧急呼叫业务；若所述网络设备不支持紧急呼叫业务，则向所述用户设备返回第一回复消息。
依据本公开的另一个方面，还提供了一种建立紧急PDN连接的方法，所述方法包括：接收用户设备发送的第二请求消息；向所述用户设备返回所述第二请求消息的第二回复消息，所述第二回复消息中携带网络设备是否支持紧急呼叫业务的信息。
依据本公开的又一个方面，还提供了一种建立紧急PDN连接的方法，所述方法包括：向网络设备发送第一请求消息，所述第一请求消息中携带有紧急呼叫提示；在所述网络设备不支持紧急呼叫业务时，接收所述网络设备返回第一回复消息。
依据本公开的又一个方面，还提供了一种建立紧急PDN连接的方法，所述方法包括：向网络设备发送第二请求消息；接收所述网络设备返回所述第二请求消息的第二回复消息，所述第二回复消息中携带所述网络设备是否支持紧急呼叫业务的信息。
依据本公开的又一个方面，还提供了一种网络设备，包括：第一接收模块，用于接收用户设备发送的第一请求消息，所述第一请求消息中携带有紧急呼叫提示；判断模块，用于根据所述紧急呼叫提示，判断网络设备是否支持紧急呼叫业务；第一发送模块，用于若所述网络设备不支持紧急呼叫业务，则向所述用户设备返回第一回复消息。
依据本公开的又一个方面，还提供了一种网络设备，包括：第二接收模块，用于接收用户设备发送的第二请求消息；第二发送模块，用于向所述用户设备返回所述第二请求消息的第二回复消息，所述第二回复消息中携带所述网络设备是否支持紧急呼叫业务的信息。
依据本公开的又一个方面，还提供了一种用户设备，包括：第三发送模块，用于向网络设备发送第一请求消息，所述第一请求消息中携带有紧急呼叫提示；第三接收模块，用于在所述网络设备不支持紧急呼叫业务时，接收所述网络设备返回第一回复消息。
依据本公开的又一个方面，还提供了一种用户设备，包括：第四发送模块，用于向网络设备发送第二请求消息；第四接收模块，用于接收所述网络设备返回所述第二请求消息的第二回复消息，所述第二回复消息中携带所述网络设备是否支持紧急呼叫业务的信息。
本公开的有益效果是：当UE执行紧急呼叫时，如果UE当前连接的网络支持紧急呼叫，UE可以不需要从网络中去附着，可直接发起紧急呼叫PDN连接的建立过程，避免了相关技术中因去附着而导致上层应用中断的问题。而且由于可以在UE向网络请求建立紧急PDN连接之前，先确认网络是否支持紧急呼叫业务，有效避免信令浪费的问题。
附图说明
图1为相关技术中可信WLAN网络的逻辑架构示意图；
图2为相关技术中UE通过可信WLAN网络的附着过程的示意图；
图3为相关技术中UE通过非可信WLAN网络连接到核心网的网络架构图；
图4为相关技术中UE通过非可信WLAN网络的附着过程；
图5为本公开的第一实施例中建立紧急PDN连接的方法流程图；
图6为本公开的第二实施例中建立紧急PDN连接的方法流程图；
图7为本公开的第三实施例中已附着到网络的UE建立紧急呼叫的示意图；
图8为本公开的第四实施例中已附着于网络的UE建立紧急PDN连接时被拒绝的示意图；
图9为本公开的第五实施例中建立紧急PDN连接的方法流程图；
图10为本公开的第六实施例中建立紧急PDN连接的方法流程图；
图11为本公开的第七实施例中已经通过正常附着过程附着到网络的UE希望建立紧急PDN连接的示意图；
图12为本公开的第八实施例中已经通过正常附着过程连接到ePDG的UE希望建立紧急PDN连接的示意图；
图13为本公开的第九实施例中的网络设备的结构图；
图14为本公开的第十实施例中的网络设备的结构图；
图15为本公开的第十一实施例中的用户设备的结构图；
图16为本公开的第十二实施例中的用户设备的结构图；
图17为本公开的第十三实施例中的网络设备的结构图；
图18为本公开的第十四实施例中的网络设备的结构图；
图19为本公开的第十五实施例中的用户设备的结构图；以及
图20为本公开的第十六实施例中的用户设备的结构图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
第一实施例
参见图5，示出了本公开的第一实施例中建立紧急PDN连接的方法的流程图，该方法的执行主体是网络设备，该方法包括：
步骤S501、接收用户设备发送的第一请求消息，第一请求消息中携带有紧急呼叫提示。
在本实施例中，该第一请求消息可以是WLCP PDN连接请求消息，也可以是IKE_AUTH REQ消息。需要说明的是，在本实施例中并不限定第一请求消息的具体类型。
步骤S503、根据紧急呼叫提示，判断网络设备是否支持紧急呼叫业务，若网络设备不支持紧急呼叫业务，则进入步骤S505；若网络设备支持紧急呼叫业务，则进入步骤S507。
需要说明的是，在本实施例中网络设备可以是ePDG或者TWAN设备，相应地，步骤S501提及的用户设备是指可以通过非可信WLAN网连接到核心网的用户设备，或者是指可以通过TWAN网连接到核心网的用户设备。
步骤S505、向用户设备返回第一回复消息。
在本实施例中，该第一回复消息中可以携带拒绝原因，例如该拒绝原因用于表明网络设备不支持紧急呼叫业务。
步骤S507、进行紧急PDN连接建立过程。
在本实施例中，可以采用相关技术进行紧急PDN连接建立，在此不再敷述。
当UE执行紧急呼叫时，UE可以不需要从网络中去附着，可直接发起紧急呼叫PDN连接的建立过程，避免了相关技术中因去附着而导致上层应用中断的问题。而且由于可以在UE向网络请求建立紧急PDN连接之前，先确认网络是否支持紧急呼叫业务，有效避免信令浪费的问题。
第二实施例
参见图6，图中示出了第二实施例中建立紧急PDN连接的方法，该方法的执行主体可以是用户设备，该方法包括：
步骤S601、向网络设备发送第一请求消息，第一请求消息中携带有紧急呼叫提示，然后进入步骤S603或步骤S605。
在本实施例中，该第一请求消息可以是WLCP PDN连接请求消息，也可以是IKE_AUTH REQ消息。需要说明的是，在本实施例中并不限定第一请求消息的具体类型。
在本实施例中，用户设备可以通过非可信WLAN网连接到核心网，或者用户设备通过TWAN网连接到核心网，相应地，该网络设备可以为ePDG或者TWAN设备。
步骤S603、在网络设备不支持紧急呼叫业务时，接收网络设备返回第一回复消息，然后进入步骤S607。
在本实施例中，第一回复消息中可以携带拒绝原因，该拒绝原因可以用于表明网络设备不支持紧急呼叫业务。
步骤S605、在网络设备支持紧急呼叫业务时，接收网络设备返回的PDN连接接受消息。
需要说明的是，PDN连接接受消息可以是WLCP PDN连接回复消息，也可以是IKE_AUTH RESP消息。在本实施例中并不限定PDN连接接受消息的具体类型。
步骤S607、在收到第一回复消息之后，向网络设备发起去附着过程。
在本实施例中，在用户设备接收到第一回复消息之后，用户设备进行去附着，然后选择支持紧急呼叫的网络，然后重新附着到该网络，并可以在重 新附着的过程中请求建立紧急呼叫PDN连接。
第三实施例
参见图7，图中示出了在基于S2a接口的网络架构下，已附着到网络的UE建立紧急呼叫的过程。
步骤S701、UE向TWAN发送WLCP PDN连接请求消息，该WLCP PDN连接请求消息中携带有紧急呼叫提示，如果TWAN支持紧急呼叫业务，进入步骤S703；如果TWAN不支持紧急呼叫业务，进入步骤S709。
步骤S703、TWAN使用紧急配置数据为UE选择PGW，然后向PGW发送创建会话请求消息，创建会话请求消息中携带有紧急呼叫提示。
步骤S705、PGW向TWAN返回创建会话回复消息。
步骤S707、TWAN向UE返回WLCP PDN连接回复消息。
步骤S709、TWAN向UE返回WLCP PDN连接拒绝消息，WLCP PDN连接拒绝消息中可以携带拒绝原因，表明TWAN不支持紧急呼叫业务。
当UE接收到WLCP PDN连接拒绝消息之后，UE去附着，重新选择支持紧急呼叫业务的TWAN，通过该TWAN重新附着到网络，然后请求建立紧急PDN连接。
在本实施例中，当UE执行紧急呼叫时，UE可以不需要从网络中去附着，可直接发起紧急呼叫PDN连接的建立过程，避免了相关技术中因去附着而导致上层应用中断的问题。
第四实施例
参见图8，图中示出了在基于S2b接口的网络架构下，已附着于网络的UE建立紧急PDN连接时被拒绝的过程，具体步骤如下：
步骤S801、UE向ePDG发送IKE_SA_INIT消息，发起IKEv2过程的初始交换。
非可信WLAN网络不能直接连接到核心网内的PGW，而是通过一个安全网关连接到PGW。该安全网关为图8中的ePDG(演进的分组数据网关)。
步骤S803、ePDG向UE返回IKE_SA_INIT消息。
步骤S805、UE向ePDG发送IKE_AUTH REQ消息，消息中携带APN(AccessPointName，接入点名称)、紧急呼叫提示等参数。
步骤S805、ePDG不支持紧急呼叫业务，其向UE返回IKE_AUTH RSP消息，消息中携带拒绝原因，该原因表明ePDG不支持紧急呼叫业务。
UE接收到拒绝原因之后，从当前连接的ePDG去附着，具体过程可参考3GPP TS 23.402第7.4小节，在此不再敷述。然后UE选择支持紧急呼叫的ePDG，然后发起附着过程并在附着过程中建立紧急PDN连接。
当ePDG支持紧急呼叫时，连接建立过程与现有过程的区别为：UE在IKE_AUTH REQ消息中将紧急呼叫提示发送给ePDG(步骤S805)，ePDG根据本地配置的紧急配置数据为UE选择PGW，并向PGW发送GTP/PMIP隧道建立请求时，将紧急呼叫请求发送PGW。
在本实施例中，当UE执行紧急呼叫时，UE可以不需要从网络中去附着，可直接发起紧急呼叫PDN连接的建立过程，避免了相关技术中因去附着而导致上层应用中断的问题。
第五实施例
参见图9，图中示出了建立紧急PDN连接的方法流程图，该方法的执行主体为网络设备，具体步骤如下：
步骤S901、接收用户设备发送的第二请求消息，第二请求消息中携带有紧急呼叫提示。
需要说明的是，在本实施例中网络设备可以是ePDG或者TWAN设备，相应地，步骤S901提及的用户设备是指可以通过非可信WLAN网连接到核心网的用户设备，或者是指可以通过TWAN网连接到核心网的用户设备。
若网络设备为TWAN设备时，可以用WLCP紧急能力请求消息来表示上述第二请求消息，此时该第二请求消息可以用于请求TWAN设备判断其自身是否支持紧急呼叫业务；
若网络设备为ePDG时，可以用IKE信息请求消息来表示上述第二请求消息，此时该第二请求消息用于请求ePDG判断其自身是否支持紧急呼叫业务。
步骤S903、向用户设备返回第二请求消息的第二回复消息，第二回复消息中携带网络设备是否支持紧急呼叫业务的信息。
需要说明的是，可以通过第二回复消息中具体信息的参数值表示网络设 备是否支持紧急呼叫业务。当然可以理解的是，在本实施例中并不限定该具体参数值。
步骤S905、在网络设备支持紧急呼叫业务，且在接收到用户设备发送的第三请求消息之后，根据第三请求消息，进行紧急PDN连接建立过程，其中第三请求消息中携带有紧急呼叫提示。
在本实施例中，该第三请求消息可以是WLCP PDN连接请求消息，也可以是IKE_AUTH REQ消息。需要说明的是，在本实施例中并不限定第三请求消息的具体类型。
第六实施例
参见图10，图中示出了建立紧急PDN连接的方法的流程，该方法的执行主体可以是用户设备，具体步骤如下：
步骤S1001、向网络设备发送第二请求消息，第二请求消息中携带有紧急呼叫提示。
需要说明的是，在本实施例中网络设备可以是ePDG或者TWAN设备，相应地，用户设备是指可以通过非可信WLAN网连接到核心网的用户设备，或者是指可以通过TWAN网连接到核心网的用户设备。
若网络设备为TWAN设备时，可以用WLCP紧急能力请求消息来表示上述第二请求消息，此时该第二请求消息可以用于请求TWAN设备判断其自身是否支持紧急呼叫业务；
若网络设备为ePDG时，可以用IKE信息请求消息来表示上述第二请求消息，此时该第二请求消息用于请求ePDG判断其自身是否支持紧急呼叫业务。
步骤S1003、接收网络设备返回第二请求消息的第二回复消息，回复消息中携带网络设备是否支持紧急呼叫业务的信息。
需要说明的是，可以通过第二回复消息中具体信息的参数值表示网络设备是否支持紧急呼叫业务。当然可以理解的是，在本实施例中并不限定该具体参数值。
步骤S1005、在网络设备支持紧急呼叫业务时，向网络设备发送第三请求消息，其中所述第三请求消息中携带有紧急呼叫提示。
步骤S1007、在网络设备不支持紧急呼叫业务时，向网络设备发起去附着过程。
需要说明的是，在本实施例中步骤S1005和步骤S1007为可选步骤。
第七实施例
参见图11，图中示出了已经通过正常附着过程附着到网络的UE希望建立紧急PDN连接，UE首先判断TWAN(可信WLAN网络)是否支持紧急呼叫业务，具体过程如下：
步骤S1101、UE向TWAN发送WLCP紧急呼叫请求消息，WLCP紧急呼叫请求消息中携带的信息表明TWAN是否支持紧急呼叫业务。
步骤S1103、TWAN向UE返回WLCP紧急呼叫回复消息，WLCP紧急呼叫回复消息中携带的信息表明TWAN是否支持紧急呼叫业务。
在本实施例中，当UE执行紧急呼叫时，UE可以不需要从网络中去附着，可直接发起紧急呼叫PDN连接的建立过程，避免了相关技术中因去附着而导致上层应用中断的问题。
第八实施例
参见图12，图中示出了在S2b场景下，已经通过正常附着过程连接到ePDG的UE希望建立紧急PDN连接，UE判断ePDG是否支持紧急呼叫业务，具体过程如下：
步骤S1201、UE向ePDG发送IKE信息请求消息，消息中携带紧急呼叫提示，用于请求ePDG是否具有支持紧急呼叫的能力。
步骤S1203、ePDG向UE返回IKE信息回复消息，消息中携带的信息表明ePDG是否支持紧急呼叫业务。
如果IKE信息回复消息中的参数表明ePDG支持紧急呼叫，则UE向ePDG发起PDN连接建立过程，UE在消息中携带紧急呼叫提示。ePDG接收到紧急呼叫提示之后，根据本地配置的紧急配置数据选择PGW。然后向PGW发起GTP/PMIP隧道的建立过程，在请求消息中携带紧急呼叫提示。
如果IKE信息回复消息中的参数表明ePDG不支持紧急呼叫，则UE去附着，重选支持紧急呼叫的ePDG，然后重新附着，并在重新附着的过程中建立紧急PDN连接，该过程为相关技术，在此不再敷述。
在本实施例中，当UE希望执行紧急呼叫时，如果UE获知当前连接的网络侧实体支持紧急呼叫，UE部需要从网络中去附着，可直接发起紧急PDN连接的建立过程。
第九实施例
参见图13，图中示出了第九实施例中网络设备的结构图，该网络设备包括：第一接收模块1301、判断模块1303和第一发送模块1305，其中
第一接收模块1301用于接收用户设备发送的第一请求消息，该第一请求消息中携带有紧急呼叫提示。在本实施例中，该第一请求消息可以是WLCP PDN连接请求消息，也可以是IKE_AUTH REQ消息。需要说明的是，在本实施例中并不限定第一请求消息的具体类型。
判断模块1303，用于根据紧急呼叫提示，判断网络设备是否支持紧急呼叫业务。需要说明的是，在本实施例中网络设备可以是ePDG或者TWAN设备，相应地，用户设备是指可以通过非可信WLAN网连接到核心网的用户设备，或者是指可以通过TWAN网连接到核心网的用户设备。
第一发送模块1305，用于若网络设备不支持紧急呼叫业务，则向用户设备返回第一回复消息。在本实施例中，该第一回复消息中可以携带拒绝原因，例如该拒绝原因用于表明网络设备不支持紧急呼叫业务。
需要说明的是，在本实施例中，网络设备还可以包括：第一连接建立模块1307，用于若网络设备支持紧急呼叫业务，则进行紧急PDN连接建立过程。在本实施例中，可以采用相关技术进行紧急PDN连接建立，在此不再敷述。
第十实施例
参见图14，图中示出了第十实施例中网络设备的结构图，该网络设备包括：第二接收模块1401和第二发送模块1403，其中：
第二接收模块1401用于接收用户设备发送的第二请求消息；
第二发送模块1403，用于向所述用户设备返回所述第二请求消息的第二回复消息，所述第二回复消息中携带所述网络设备是否支持紧急呼叫业务的信息。
可选地，该网络设备还包括：第二连接建立模块，用于在所述网络设备 支持紧急呼叫业务，且在接收到所述用户设备发送的第三请求消息之后，根据所述第三请求消息，进行紧急PDN连接建立过程，其中所述第三请求消息中携带有紧急呼叫提示。
第十一实施例
参见图15，图中示出了第十一实施例中用户设备的结构图，该用户设备包括：第三发送模块1501和第三收模块1503，其中
第三发送模块1501用于向网络设备发送第一请求消息，第一请求消息中携带有紧急呼叫提示。在本实施例中，该第一请求消息可以是WLCP PDN连接请求消息，也可以是IKE_AUTH REQ消息。需要说明的是，在本实施例中并不限定第一请求消息的具体类型。在本实施例中，用户设备可以通过非可信WLAN网连接到核心网，或者用户设备通过TWAN网连接到核心网，相应地，该网络设备可以为ePDG或者TWAN设备。
第三接收模块1503用于在网络设备不支持紧急呼叫业务时，接收网络设备返回第一回复消息。在本实施例中，第一回复消息中可以携带拒绝原因，该拒绝原因可以用于表明网络设备不支持紧急呼叫业务。
可选地，该用户设备还包括：第五接收模块，用于在所述网络设备支持紧急呼叫业务时，接收所述网络设备返回的PDN连接接受消息。
可选地，该用户设备还包括：第五发送模块，用于在收到所述第一回复消息之后，向所述网络设备发起去附着过程。
第十二实施例
参见图16，图中示出了第十二实施例中用户设备的结构图，该用户设备包括包括：
第四发送模块1601，用于向网络设备发送第二请求消息；需要说明的是，在本实施例中网络设备可以是ePDG或者TWAN设备，相应地，用户设备是指可以通过非可信WLAN网连接到核心网的用户设备，或者是指可以通过TWAN网连接到核心网的用户设备。若网络设备为TWAN设备时，可以用WLCP紧急能力请求消息来表示上述第二请求消息，此时该第二请求消息可以用于请求TWAN设备判断其自身是否支持紧急呼叫业务；若网络设备为ePDG时，可以用IKE信息请求消息来表示上述第二请求消息，此时该第二 请求消息用于请求ePDG判断其自身是否支持紧急呼叫业务。
第四接收模块1603，用于接收网络设备返回所述第二请求消息的第二回复消息，第二回复消息中携带所述网络设备是否支持紧急呼叫业务的信息。需要说明的是，可以通过第二回复消息中具体信息的参数值表示网络设备是否支持紧急呼叫业务。当然可以理解的是，在本实施例中并不限定该具体参数值。
在本实施例中，用户设备还包括：第三连接建立模块，用于在网络设备支持紧急呼叫业务，且在接收到用户设备发送的第三请求消息之后，根据第三请求消息，进行紧急PDN连接建立过程，其中第三请求消息中携带有紧急呼叫提示。在本实施例中，该第三请求消息可以是WLCP PDN连接请求消息，也可以是IKE_AUTH REQ消息。需要说明的是，在本实施例中并不限定第三请求消息的具体类型。
第十三实施例
参见图17，图中示出了一种网络设备，包括：第一处理器1701、第一存储器1702和第一收发机1703，其中
第一处理器1701用于读取第一存储器1702中的程序，执行下列过程：接收用户设备发送的第一请求消息，所述第一请求消息中携带有紧急呼叫提示；根据所述紧急呼叫提示，判断所述网络设备是否支持紧急呼叫业务；若所述网络设备不支持紧急呼叫业务，则向所述用户设备返回第一回复消息。
第一收发机1703用于在第一处理器1701的控制下接收和发送数据。
可选地，第一处理器1701还用于若网络设备支持紧急呼叫业务，则进行紧急PDN连接建立过程。
可选的，第一处理器1701可以是CPU(中央处埋器)、ASIC(Application SpecificIntegrated Circuit，专用集成电路)、FPGA(Field-Programmable Gate Array，现场可编程门阵列)或CPLD(Complex Programmable Logic Device，复杂可编程逻辑器件)。
其中，在图17中，总线架构可以包括任意数量的互联的总线和桥，具体由第一处理器1701代表的一个或多个处理器和第一存储器1702代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功 率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。第一收发机1703可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。第一处理器1701负责管理总线架构和通常的处理，第一存储器1702可以存储第一处理器1701在执行操作时所使用的数据。
在本实施例中，如果UE当前连接的网络支持紧急呼叫，UE可以不需要从网络中去附着，可直接发起紧急呼叫PDN连接的建立过程，避免了相关技术中因去附着而导致上层应用中断的问题。
第十四实施例
参见图18，图中示出了一种网络设备，包括：第二处理器1801、第二存储器1802和第二收发机1803，其中
第二处理器1801用于读取第二存储器1802中的程序，执行下列过程：接收用户设备发送的第二请求消息，向所述用户设备返回所述第二请求消息的第二回复消息，所述第二回复消息中携带所述网络设备是否支持紧急呼叫业务的信息
第二收发机1803用于在第二处理器1801的控制下接收和发送数据。
可选地，第二处理器1801还用于在所述网络设备支持紧急呼叫业务，且在接收到所述用户设备发送的第三请求消息之后，根据所述第三请求消息，进行紧急PDN连接建立过程，其中所述第三请求消息中携带有紧急呼叫提示。
可选的，第二处理器1801可以是CPU(中央处埋器)、ASIC(Application SpecificIntegrated Circuit，专用集成电路)、FPGA(Field-Programmable Gate Array，现场可编程门阵列)或CPLD(Complex Programmable Logic Device，复杂可编程逻辑器件)。
其中，在图18中，总线架构可以包括任意数量的互联的总线和桥，具体由第一处理器1801代表的一个或多个处理器和第一存储器1802代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。第一收发机1803可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其 他装置通信的单元。第一处理器1801负责管理总线架构和通常的处理，第一存储器1802可以存储第一处理器1801在执行操作时所使用的数据。
在本实施例中，如果UE当前连接的网络支持紧急呼叫，UE可以不需要从网络中去附着，可直接发起紧急呼叫PDN连接的建立过程，避免了相关技术中因去附着而导致上层应用中断的问题。
第十五实施例
参见图19，图中示出了一种用户设备，包括：第三处理器1901、第三存储器1902和第三收发机1903，其中
第三处理器1901用于读取第三存储器1902中的程序，执行下列过程：向网络设备发送第一请求消息，第一请求消息中携带有紧急呼叫提示；在网络设备不支持紧急呼叫业务时，接收网络设备返回第一回复消息。
第三收发机1903用于在第三处理器1901的控制下接收和发送数据。
可选地，第三处理器1901还用于在所述网络设备支持紧急呼叫业务时，接收所述网络设备返回的PDN连接接受消息。
可选地，第三处理器1901还用于在收到所述第一回复消息之后，向所述网络设备发起去附着过程。
可选的，第三处理器1901可以是CPU(中央处埋器)、ASIC(Application SpecificIntegrated Circuit，专用集成电路)、FPGA(Field-Programmable Gate Array，现场可编程门阵列)或CPLD(Complex Programmable Logic Device，复杂可编程逻辑器件)。
其中，在图19中，总线架构可以包括任意数量的互联的总线和桥，具体由第三处理器1901代表的一个或多个处理器和第三存储器1902代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。第三收发机1903可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。第三处理器1901负责管理总线架构和通常的处理，第三存储器1902可以存储第三处理器1901在执行操作时所使用的数据。针对不同的用户设备，第一用户接口1905还可以是能够外接内接需要设备的接口， 连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
在本实施例中，如果UE当前连接的网络支持紧急呼叫，UE可以不需要从网络中去附着，可直接发起紧急呼叫PDN连接的建立过程，避免了相关技术中因去附着而导致上层应用中断的问题。
第十六实施例
参见图20，图中示出了一种用户设备，包括：第四处理器2001、第四存储器2002和第四收发机2003，其中
第四处理器2001用于读取第四存储器2002中的程序，执行下列过程：向网络设备发送第二请求消息，接收网络设备返回所述第二请求消息的第二回复消息，第二回复消息中携带所述网络设备是否支持紧急呼叫业务的信息。
第四收发机2003用于在第四处理器2001的控制下接收和发送数据。
可选地，第四处理器2001还用于在网络设备支持紧急呼叫业务，且在接收到用户设备发送的第三请求消息之后，根据第三请求消息，进行紧急PDN连接建立过程，其中第三请求消息中携带有紧急呼叫提示。
可选的，第四处理器2001可以是CPU(中央处埋器)、ASIC(Application SpecificIntegrated Circuit，专用集成电路)、FPGA(Field-Programmable Gate Array，现场可编程门阵列)或CPLD(Complex Programmable Logic Device，复杂可编程逻辑器件)。
其中，在图20中，总线架构可以包括任意数量的互联的总线和桥，具体由第四处理器2001代表的一个或多个处理器和第四存储器2002代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。第四收发机2003可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。第四处理器2001负责管理总线架构和通常的处理，第四存储器2002可以存储第四处理器2001在执行操作时所使用的数据。针对不同的用户设备，第二用户接口2005还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
在本实施例中，如果UE当前连接的网络支持紧急呼叫，UE可以不需要从 网络中去附着，可直接发起紧急呼叫PDN连接的建立过程，避免了相关技术中因去附着而导致上层应用中断的问题。
在本申请所提供的几个实施例中，应该理解到，所揭露方法和装置，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理包括，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括如果干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述的是本公开的可选实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开所述的原理前提下还可以作出若干改进和润饰，这些改进和润饰也在本公开的保护范围内。

Claims (34)

  1. 一种建立紧急分组数据网PDN连接的方法，包括：
    接收用户设备发送的第一请求消息，所述第一请求消息中携带有紧急呼叫提示；
    根据所述紧急呼叫提示，判断网络设备是否支持紧急呼叫业务；
    若所述网络设备不支持紧急呼叫业务，则向所述用户设备返回第一回复消息。
  2. 根据权利要求1所述的方法，还包括：
    若所述网络设备支持紧急呼叫业务，则进行紧急PDN连接建立过程。
  3. 根据权利要求1所述的方法，其中，所述第一回复消息中携带有拒绝原因，所述拒绝原因用于表明所述网络设备不支持紧急呼叫业务。
  4. 根据权利要求1～3任一项所述的方法，其中，所述网络设备为演进的分组数据网关ePDG或者可信无线局域网WLAN设备。
  5. 一种建立紧急分组数据网PDN连接的方法，包括：
    接收用户设备发送的第二请求消息；
    向所述用户设备返回所述第二请求消息的第二回复消息，所述第二回复消息中携带网络设备是否支持紧急呼叫业务的信息。
  6. 根据权利要求5所述的方法，还包括：
    在所述网络设备支持紧急呼叫业务，且在接收到所述用户设备发送的第三请求消息之后，根据所述第三请求消息，进行紧急PDN连接建立过程，其中所述第三请求消息中携带有紧急呼叫提示。
  7. 根据权利要求5或6所述的方法，其中，所述网络设备为演进的分组数据网关ePDG或者可信无线局域网WLAN设备。
  8. 一种建立紧急分组数据网PDN连接的方法，包括：
    向网络设备发送第一请求消息，所述第一请求消息中携带有紧急呼叫提示；
    在所述网络设备不支持紧急呼叫业务时，接收所述网络设备返回第一回复消息。
  9. 根据权利要求8所述的方法，还包括：
    在所述网络设备支持紧急呼叫业务时，接收所述网络设备返回的PDN连接接受消息。
  10. 根据权利要求8所述的方法，其中，所述第一回复消息中携带有拒绝原因，所述拒绝原因用于表明所述网络设备不支持紧急呼叫业务。
  11. 根据权利要求8所述的方法，还包括：
    在收到所述第一回复消息之后，向所述网络设备发起去附着过程。
  12. 根据权利要求8～10任一项所述的方法，其中，所述网络设备为演进的分组数据网关ePDG或者可信无线局域网WLAN设备。
  13. 一种建立紧急分组数据网PDN连接的方法，包括：
    向网络设备发送第二请求消息；
    接收所述网络设备返回所述第二请求消息的第二回复消息，所述第二回复消息中携带所述网络设备是否支持紧急呼叫业务的信息。
  14. 根据权利要求13所述的方法，还包括：
    在所述网络设备支持紧急呼叫业务时，向所述网络设备发送第三请求消息，其中所述第三请求消息中携带有紧急呼叫提示。
  15. 根据权利要求14所述的方法，还包括：
    在所述网络设备不支持紧急呼叫业务时，向所述网络设备发起去附着过程。
  16. 根据权利要求13～15任一项所述的方法，其中，所述网络设备为演进的分组数据网关ePDG或者可信无线局域网WLAN设备。
  17. 一种网络设备，包括：
    第一接收模块，用于接收用户设备发送的第一请求消息，所述第一请求消息中携带有紧急呼叫提示；
    判断模块，用于根据所述紧急呼叫提示，判断网络设备是否支持紧急呼叫业务；
    第一发送模块，用于若所述网络设备不支持紧急呼叫业务，则向所述用户设备返回第一回复消息。
  18. 根据权利要求17所述的网络设备，还包括：第一连接建立模块，用 于若网络设备支持紧急呼叫业务，则进行紧急分组数据网PDN连接建立过程。
  19. 一种网络设备，包括：
    第二接收模块，用于接收用户设备发送的第二请求消息；
    第二发送模块，用于向所述用户设备返回所述第二请求消息的第二回复消息，所述第二回复消息中携带网络设备是否支持紧急呼叫业务的信息。
  20. 根据权利要求19所述的网络设备，还包括：第二连接建立模块，用于在所述网络设备支持紧急呼叫业务，且在接收到所述用户设备发送的第三请求消息之后，根据所述第三请求消息，进行紧急分组数据网PDN连接建立过程，其中所述第三请求消息中携带有紧急呼叫提示。
  21. 一种用户设备，包括：
    第三发送模块，用于向网络设备发送第一请求消息，所述第一请求消息中携带有紧急呼叫提示；
    第三接收模块，用于在所述网络设备不支持紧急呼叫业务时，接收所述网络设备返回第一回复消息。
  22. 根据权利要求21所述的用户设备，还包括：第五接收模块，用于在所述网络设备支持紧急呼叫业务时，接收所述网络设备返回的分组数据网PDN连接接受消息。
  23. 根据权利要求21所述的用户设备，还包括：第五发送模块，用于在收到所述第一回复消息之后，向所述网络设备发起去附着过程。
  24. 一种用户设备，包括：
    第四发送模块，用于向网络设备发送第二请求消息；
    第四接收模块，用于接收所述网络设备返回所述第二请求消息的第二回复消息，所述第二回复消息中携带所述网络设备是否支持紧急呼叫业务的信息。
  25. 根据权利要求24所述的用户设备，还包括：第三连接建立模块，用于在网络设备支持紧急呼叫业务，且在接收到用户设备发送的第三请求消息之后，根据所述第三请求消息，进行紧急分组数据网PDN连接建立过程，其中所述第三请求消息中携带有紧急呼叫提示。
  26. 一种网络设备，包括：第一处理器、第一存储器和第一收发机，其 中
    第一处理器用于读取第一存储器中的程序，执行下列过程：接收用户设备发送的第一请求消息，所述第一请求消息中携带有紧急呼叫提示；根据所述紧急呼叫提示，判断所述网络设备是否支持紧急呼叫业务；若所述网络设备不支持紧急呼叫业务，则向所述用户设备返回第一回复消息；
    第一收发机用于接收和发送数据。
  27. 根据权利要求26所述的网络设备，其中第一处理器还用于若网络设备支持紧急呼叫业务，则进行紧急分组数据网PDN连接建立过程。
  28. 一种网络设备，包括：第二处理器、第二存储器和第二收发机，其中
    第二处理器用于读取第二存储器中的程序，执行下列过程：接收用户设备发送的第二请求消息，向所述用户设备返回所述第二请求消息的第二回复消息，所述第二回复消息中携带所述网络设备是否支持紧急呼叫业务的信息；
    第二收发机用于接收和发送数据。
  29. 根据权利要求28所述的网络设备，其中，第二处理器还用于在所述网络设备支持紧急呼叫业务，且在接收到所述用户设备发送的第三请求消息之后，根据所述第三请求消息，进行紧急分组数据网PDN连接建立过程，其中所述第三请求消息中携带有紧急呼叫提示。
  30. 一种用户设备，包括：第三处理器、第三存储器和第三收发机，其中
    第三处理器用于读取第三存储器中的程序，执行下列过程：向网络设备发送第一请求消息，第一请求消息中携带有紧急呼叫提示；在网络设备不支持紧急呼叫业务时，接收网络设备返回第一回复消息；
    第三收发机用于接收和发送数据。
  31. 根据权利要求30所述的用户设备，其中，第三处理器还用于在所述网络设备支持紧急呼叫业务时，接收所述网络设备返回的分组数据网PDN连接接受消息。
  32. 根据权利要求30所述的用户设备，其中，第三处理器还用于在收到所述第一回复消息之后，向所述网络设备发起去附着过程。
  33. 一种用户设备，包括：第四处理器、第四存储器和第四收发机，其中
    第四处理器用于读取第四存储器中的程序，执行下列过程：向网络设备发送第二请求消息，接收网络设备返回所述第二请求消息的第二回复消息，第二回复消息中携带所述网络设备是否支持紧急呼叫业务的信息；
    第四收发机用于接收和发送数据。
  34. 根据权利要求33所述的用户设备，其中，第四处理器还用于在网络设备支持紧急呼叫业务，且在接收到用户设备发送的第三请求消息之后，根据第三请求消息，进行紧急分组数据网PDN连接建立过程，其中第三请求消息中携带有紧急呼叫提示。
PCT/CN2016/091580 2015-08-03 2016-07-25 一种建立紧急pdn连接的方法及设备 WO2017020746A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510481223.9 2015-08-03
CN201510481223.9A CN106413122B (zh) 2015-08-03 2015-08-03 一种建立紧急pdn连接的方法及设备

Publications (1)

Publication Number Publication Date
WO2017020746A1 true WO2017020746A1 (zh) 2017-02-09

Family

ID=57942445

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/091580 WO2017020746A1 (zh) 2015-08-03 2016-07-25 一种建立紧急pdn连接的方法及设备

Country Status (2)

Country Link
CN (1) CN106413122B (zh)
WO (1) WO2017020746A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106792612A (zh) * 2017-03-29 2017-05-31 努比亚技术有限公司 一种无卡紧急呼叫处理方法及终端
CN111226425A (zh) * 2017-10-16 2020-06-02 苹果公司 针对无紧急注册的VoLTE紧急呼叫释放紧急PDN承载

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101841790A (zh) * 2009-03-19 2010-09-22 大唐移动通信设备有限公司 用于紧急呼叫的地址分配方法和装置
CN101873561A (zh) * 2009-04-27 2010-10-27 华为技术有限公司 一种紧急业务的实现方法及设备
CN101998330A (zh) * 2009-08-18 2011-03-30 大唐移动通信设备有限公司 一种切换方法、装置和系统
CN101998329A (zh) * 2009-08-18 2011-03-30 大唐移动通信设备有限公司 一种保证紧急业务连续性的方法、设备和系统
US20110171924A1 (en) * 2010-01-12 2011-07-14 Research In Motion Limited Selective Support and Establishment of Emergency Services in Home Cells
CN102204217A (zh) * 2011-05-30 2011-09-28 华为技术有限公司 通知网络能力的方法、装置和系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101841790A (zh) * 2009-03-19 2010-09-22 大唐移动通信设备有限公司 用于紧急呼叫的地址分配方法和装置
CN101873561A (zh) * 2009-04-27 2010-10-27 华为技术有限公司 一种紧急业务的实现方法及设备
CN101998330A (zh) * 2009-08-18 2011-03-30 大唐移动通信设备有限公司 一种切换方法、装置和系统
CN101998329A (zh) * 2009-08-18 2011-03-30 大唐移动通信设备有限公司 一种保证紧急业务连续性的方法、设备和系统
US20110171924A1 (en) * 2010-01-12 2011-07-14 Research In Motion Limited Selective Support and Establishment of Emergency Services in Home Cells
CN102204217A (zh) * 2011-05-30 2011-09-28 华为技术有限公司 通知网络能力的方法、装置和系统

Also Published As

Publication number Publication date
CN106413122A (zh) 2017-02-15
CN106413122B (zh) 2020-03-06

Similar Documents

Publication Publication Date Title
RU2745387C2 (ru) Способ, устройство и система межсистемного хэндовера
EP2458913B1 (en) Reselection system for bearer binding and event reporting function and method thereof
US9967781B2 (en) Apparatus and method for supporting handover
JP7387848B2 (ja) ユーザプレーンの完全性保護の方法および装置、ならびにデバイス
CN108632928B (zh) 一种切换核心网的方法及装置
US9408246B2 (en) System and method for seamless Wi-Fi to UMTS handover
EP2458914A1 (en) Method for reselecting bearer binding and event report function
BR112020020269A2 (pt) Método e aparelho de reestabelecimento de conexão
US10419935B2 (en) Access method in wireless communications network, related apparatus, and system
CN106465227A (zh) 经由无线设备的多个无线接入来支持基于网络的ip流移动性的方法和设备
WO2014056445A1 (zh) 一种路由转发的方法、系统及控制器
CN101860910B (zh) 本地网络的承载建立方法、系统及装置
EP2557729A1 (en) Method and system for information transmission
EP2317694B1 (en) Method and system and user equipment for protocol configuration option transmission
KR102246978B1 (ko) 라우팅 방법 및 장치
WO2017054190A1 (zh) 一种语音通信方法及装置
WO2019076308A1 (zh) 终端设备的状态的确定方法、装置及设备
CN107404736B (zh) 一种切换方法、设备及网络架构
WO2017020746A1 (zh) 一种建立紧急pdn连接的方法及设备
WO2022052798A1 (zh) QoS控制方法、装置及处理器可读存储介质
WO2018014667A1 (zh) 一种数据传输的方法及装置
WO2018058699A1 (zh) 一种切换方法及设备
WO2012146129A1 (zh) 一种支持多接入的承载管理方法、系统和锚定点
RU2796658C2 (ru) Способ, устройство и система межсистемного перемещения
EP4277316A1 (en) Security policy processing method and communication device

Legal Events

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

Ref document number: 16832234

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16832234

Country of ref document: EP

Kind code of ref document: A1