WO2009082936A1 - Procédé et appareil pour un appel d'urgence - Google Patents

Procédé et appareil pour un appel d'urgence Download PDF

Info

Publication number
WO2009082936A1
WO2009082936A1 PCT/CN2008/073577 CN2008073577W WO2009082936A1 WO 2009082936 A1 WO2009082936 A1 WO 2009082936A1 CN 2008073577 W CN2008073577 W CN 2008073577W WO 2009082936 A1 WO2009082936 A1 WO 2009082936A1
Authority
WO
WIPO (PCT)
Prior art keywords
emergency call
emergency
bearer
service entity
call service
Prior art date
Application number
PCT/CN2008/073577
Other languages
English (en)
French (fr)
Inventor
Wei Guo
Xiaoqin Duan
Jian Zhang
Qingyu Li
Xiaobo Wu
Original Assignee
Huawei Technologies Co., Ltd.
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
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=40806387&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2009082936(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to BRPI0821355A priority Critical patent/BRPI0821355A8/pt
Priority to CN2008801192641A priority patent/CN101897205B/zh
Publication of WO2009082936A1 publication Critical patent/WO2009082936A1/zh
Priority to US12/818,966 priority patent/US20100255808A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/50—Connection management for emergency connections

Definitions

  • the embodiments of the present invention relate to the field of mobile communications technologies, and in particular, to an emergency call method and apparatus. Background technique
  • UMTS Universal Mobile Telecommunication System
  • WCDMA Wideband Code Division Multiple Access
  • the UMTS system is also commonly referred to as a WCDMA communication system.
  • the UMTS system includes a RAN (Radio Access Network) and a CN (Core Network).
  • the RAN is used to handle all wireless related functions, and the CN handles all voice calls and data connections in the UMTS system, and exchanges and routes with the external network.
  • FIG. 1 it is a schematic diagram of a logical architecture of a prior art UMTS system. The main parts of the UMTS system are described below:
  • the GGSN (Gateway General Packet Radio Service Support Node) serves as a basic network element function entity to provide routing and encapsulation of data packets with the external data network.
  • SGSN (Serving GPRS Support Node) serves as a basic component network element. Its main function is to forward the input/output IP (Internet Protocol, Internet) for the MS (Mobile Station) of the SGSN service area. Protocol) grouping.
  • the RAN Radio Access Network
  • RNC Radio Network Controller
  • NodeB Node Base Station
  • LTE Long Term Evolved, Long Term Evolution
  • SAE System Architecture Evolved
  • the function of the MME is to store the mobility management context of the UE (User Equipment), such as the user's identity, mobility management status, location information, etc., and to the NAS (Non Access Stratum). , non-access layer) signaling processing, responsible for NAS signaling security.
  • UE User Equipment
  • NAS Non Access Stratum
  • the SAE GW (SAE Gateway) consists of two parts called S-GW (Serving Gateway) and P-GW (PDN Gateway, Packet Data Network Gateway).
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • S-GW and P-GW are two logical entities that can exist on the same or different physical entities.
  • the S-GW saves the user plane context of the UE, such as the IP address and routing information of the UE, and performs lawful interception and packet data routing functions.
  • the MME is responsible for the connection between the control plane and the user plane through the S1-MME and the S-GW through the S1-U and the EUTRAN (Evolved UMTS Terrestrial Radio Access Network) network.
  • the MME is connected to the 2G/3G SGSN through the S3 interface through the S3 interface, and is responsible for the mobility control plane anchor point and the user plane anchor point function between the UE and the SAE network respectively.
  • the P-GW is responsible for the user plane anchor function of the UE accessing the packet data network, communicates with the external packet data network through the SGi reference point, has the function of packet routing and forwarding, and is responsible for the policy charging enhancement function, based on each user. Group filtering function, etc.
  • the problem to be solved by the embodiments of the present invention is to provide an emergency call method and apparatus, which solves the technical defect that the emergency call service cannot be implemented in the SAE/LTE network in the prior art.
  • an embodiment of the present invention provides an emergency call method, which specifically includes:
  • the user equipment UE initiates an emergency attach request to the evolved network SAE network, where the emergency attach request includes an emergency indication;
  • the SAE network After receiving the emergency indication, the SAE network selects an emergency call service entity for the UE;
  • the emergency call service entity establishes an emergency voice bearer, and the UE performs an emergency call according to the established emergency voice bearer.
  • An embodiment of the present invention further provides an emergency call release method, including:
  • the emergency call service entity receives the relevant release message sent by the UE or the emergency call center;
  • the emergency call service entity releases the relevant emergency voice bearer resource.
  • An embodiment of the present invention further provides an emergency attaching method, which specifically includes:
  • the UE When the UE detects that the user is initiating an emergency call, the UE initiates a NAS message to the SAE network, where the NAS message carries an emergency indication and a unique identifier of the user;
  • the local packet data network gateway PDN-GW is selected for the UE according to the NAS message, and the PDN-GW allocates a corresponding IP address to the UE, so that the UE is attached to the S AE network.
  • An embodiment of the present invention further provides an emergency call service entity, including emergency attach processing. a module, a bearer establishment information acquisition module, a bearer information delivery module, a bearer establishment notification module, and a bearer association control module,
  • the emergency attach processing module is configured to receive an emergency attach of the user equipment UE, and the bearer setup information acquiring module is configured to acquire, after the emergency call initiated by the UE, a bearer required for establishing an emergency voice bearer for the UE Establish information;
  • the bearer information sending module is configured to send the bearer setup information to the media gateway and the policy charging rule function PCRF;
  • the bearer establishment notification module is configured to notify the media gateway and the PCRF to establish an emergency call service entity side emergency voice bearer and a SAE side emergency voice bearer;
  • the bearer association control module is configured to associate, between the emergency call service entity side bearer and the PCRF side bearer, the media gateway to associate the emergency call bearer on the emergency call service entity side with the emergency voice bearer on the SAE side,
  • the UE performs an emergency call according to the associated emergency call service entity side emergency voice bearer and the SAE side emergency voice bearer.
  • the technical solution of the embodiment of the present invention has the following advantages.
  • the emergency call method and apparatus provided by the embodiments of the present invention can complete an emergency call of an analog circuit domain by using an emergency call service entity in a SAE/LTE evolved network.
  • FIG. 1 is a schematic diagram of a logical architecture of a prior art UMTS system
  • FIG. 2 is a schematic diagram of a prior art LTE/SAE network architecture
  • FIG. 3 is a flowchart of a method for implementing an emergency call according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a method for implementing an emergency call according to Embodiment 1 of the present invention
  • FIG. 5 is a structural diagram of an eMSC network architecture A according to an embodiment of the present invention.
  • FIG. 6 is a structural diagram of an eMSC network architecture B according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of a method for implementing an emergency call in an analog circuit domain on a packet domain according to Embodiment 2 of the present invention.
  • FIG. 8 is a flowchart of initial access of a UE under non-3GPP access according to an embodiment of the present invention
  • FIG. 9 is an implementation of an emergency call in an analog circuit domain on a packet domain according to Embodiment 3 of the present invention. Method flow chart;
  • FIG. 10 is a flowchart of a method for implementing an emergency call in an analog circuit domain on a packet domain according to Embodiment 3 of the present invention.
  • FIG. 11 is a flowchart of a method for implementing an emergency call in an analog circuit domain on a packet domain according to Embodiment 4 of the present invention.
  • FIG. 12 is a flowchart of a method for implementing an emergency call in an analog circuit domain on a packet domain according to Embodiment 5 of the present invention
  • FIG. 13 is a flowchart of a method for implementing an emergency call in an analog circuit domain on a packet domain according to Embodiment 6 of the present invention.
  • FIG. 14 is a flowchart of a method for implementing an emergency call in an analog circuit domain on a packet domain according to Embodiment 7 of the present invention.
  • FIG. 15 is a structural diagram of an eMSC of an evolved mobile service switching center according to an embodiment of the present invention. detailed description
  • the embodiment of the present invention completes an emergency call in the analog circuit domain through an emergency call service entity, which can protect the existing investment of the operator and continue to provide the services of the traditional circuit domain as much as possible.
  • the emergency call service entity is a p-CSCF (Proxy-Call Session Control Function) in an eMSC (Evolution Mobile-services Switching Center) or an IMS (IP Multimedia Subsysterm, IP Multimedia Subsystem) Call session control function).
  • the emergency call service of the eMGW (Evolved Media Gateway) side is associated with the emergency voice bearer on the SAE side to implement the emergency call of the UE; and the emergency service is not considered in the implementation process of the embodiment of the present invention. Restricted by user subscription, with higher priority, the principle of completing emergency services for roaming users on the network, and the possible planning status of the network integration product IMS network that the operator has not deployed, and implementing the invention according to the above factors The example was optimized.
  • an emergency call service entity as an eMSC as an example, but it should be noted that in the following embodiments, an emergency call service is provided.
  • the emergency entity is an eMSC, but in other network architectures, the emergency call service entity may also be other devices.
  • the emergency call service entity under the IMS network where the operator deploys the network integration product may also be the p-CSCF in the IMS.
  • An embodiment of the present invention provides an emergency call method, as shown in FIG. 3, which specifically includes:
  • S301 The user equipment UE initiates an emergency attach request to the evolved network SAE network, where the emergency attach request includes an emergency indication.
  • the SAE network After receiving the emergency indication, the SAE network selects an emergency call service entity for the UE.
  • the emergency call service entity establishes an emergency voice bearer, and the UE performs an emergency call according to the established emergency voice bearer.
  • the technical solution of the embodiment of the present invention has the following advantages.
  • the emergency call method and apparatus provided by the embodiments of the present invention can complete an emergency call of an analog circuit domain by using an emergency call service entity in a SAE/LTE evolved network.
  • FIG. 4 is a flowchart of a method for implementing an emergency call according to Embodiment 1 of the present invention.
  • the flowchart is a flowchart generally summarized in the embodiment of the present invention, where specific process details will be described in detail in subsequent embodiments.
  • the embodiment includes the following steps: Step S401: The UE detects an emergency call setup request.
  • Step S402 The UE does not have sufficient capabilities or resources to establish an emergency call situation. If the UE has sufficient capabilities or resources to establish an emergency call, there will be no such process.
  • Step S403 The UE evolves an emergency attach of the network to the SAE, and establishes a bearer of the CS signaling by using the attach procedure.
  • Step S404 the discovery process of the eMSC.
  • Step S405 the UE attaches to the eMSC process.
  • Step S406 completing an emergency call of the UE by using the eMSC.
  • the emergency attach process of the SAE/LTE evolved network in the foregoing embodiment, is the basis for the UE to attach to the eMSC, and only the UE attaches to the SAE/LTE evolved network to obtain the corresponding IP address to establish The connection to the eMSC prepares for subsequent emergency calls.
  • the emergency attach procedure of the foregoing UE to the SAE/LTE evolved network proposed by the embodiment of the present invention is applicable not only to the eMSC but also to the IMS emergency call, so that the location and role of the eMSC in the emergency call is equivalent to the P in the IMS emergency call.
  • the emergency call setup and the SAE emergency load setup procedure in the eMSC scheme of the embodiment of the present invention are all related to the architecture of the evolved network system. For example: Does the evolved network system introduce a Gs-like interface between the eMSC and the evolved network. Whether the interface can transmit high-level signaling of the calling plane, and how to ensure the security of call signaling and media plane without the interface.
  • the network architecture of the two eMSC schemes is proposed in the embodiment of the present invention, and the detailed process of implementing the PS domain simulation CS domain emergency call setup and the SAE emergency bearer establishment in different architectures and detailed descriptions of specific problems are given.
  • the two eMSC network architectures provided by the embodiments of the present invention include architecture A and architecture B.
  • the eMSC includes functions of a part of an MSC, an MGCF (Media Gateway Control Function), and has an AS in a packet domain. (Application Server, application server) features.
  • the eMSC controls the establishment of the bearer of the PS domain through the Rx+ interface between the Policy Control and Charging Rules Function (PCRF), and the logical tunnel is used between the eMSC and the UE to simulate the transmission of the circuit domain.
  • PCRF Policy Control and Charging Rules Function
  • the eMGW entity is introduced as a media gateway conversion gateway (ie, VoIP data of the packet domain and VoIP data of the circuit domain), and the entity includes an IM-MGW of the IMS domain and an MGW (Media Gateway) function of the circuit domain.
  • FIG. 6 it is a structural diagram of an eMSC network architecture B according to an embodiment of the present invention.
  • the architecture B similar to the foregoing architecture A, the MME and the eMSC are introduced differently.
  • a flowchart of an emergency call method for implementing an analog circuit domain on a packet domain according to Embodiment 2 of the present invention is based on the foregoing architecture A, that is, there is no similar Gs interface.
  • the voice media plane data of the UE runs on the SAE/LTE dedicated bearer or the default bearer.
  • the local PDN-GW needs to allocate an IP address for the emergency call to the UE. .
  • Step S701 The UE initiates an emergency attach to the SAE, and the SAE selects a corresponding local PDN-GW for the UE, and obtains an IP address allocated by the local PDN-GW for the emergency call, and simultaneously simulates the CS domain registration, the call, and the like.
  • the related signaling establishes a default bearer or a dedicated bearer.
  • the emergency indication indication is included in the bearer setup request.
  • the UE initiates the emergency attach.
  • the premise is that the UE must be able to identify that the user is initiating an emergency call.
  • a specific button may be defined in the UE terminal, or the terminal may recognize that the number dialed by the user is an emergency number. achieve. If the user dials 110, the terminal can automatically identify 110 as an emergency number and automatically initiate an emergency attach to the SAE.
  • the user has not attached to the SAE network, and the UE needs to be urgently attached to the SAE network before the emergency call is established.
  • the steps may include the following steps: A: UE transmits emergency attach request message to the SAE, wherein the emergency attach request The message carries an emergency indication and a unique identifier of the user.
  • the universal subscriber identity card) card has been attached (this attachment is different from emergency attachment, the UE is normally attached to the network) or is not attached.
  • emergency attach request message Carrying the identification information of the user, such as the IMSI of the user as the identifier of the UE, and the ordinary attachment is not
  • the attach request message carries an emergency indication to inform the network that this is an emergency attachment.
  • the message may also carry an emergency APN (Access Point Name).
  • the network determines whether to perform the process of authentication and security.
  • the local PDN-GW searching process may be triggered by the Tracking Area Update procedure or the service request procedure.
  • the emergency indication carries the emergency indication in the TAU Request message and the service request message, and may also carry the emergency APN. .
  • the UE uses the IMEI as the user's own identification information in the emergency attach request message, and the emergency indication indicates that the network is an emergency attachment, and can also carry the emergency APN.
  • the network does not need to perform authentication and security procedures.
  • the PDN-GW selection strategy is as follows:
  • the MME shall determine this. If the APN belongs to the home location, the MME will select a local PDN from the APN. GW, if it does not belong to the local home, the MME uses its own default emergency APN to select a PDN-GW.
  • the MME selects a local PDN-GW according to the default emergency APN configured by itself.
  • the MME queries the HSS for the subscription information of the user and determines whether the emergency APN subscribed by the user belongs to the local device, when the UE determines that the UE carries the emergency indication and uses the IMSI as the identifier. If yes, the emergency APN subscribed by the user is used, otherwise the MME is configured with a default emergency APN to select a PDN-GW. 4) If the UE does not carry the emergency ⁇ in the attach request message, and the MME cannot obtain the user's subscription data from the HSS or the user uses the IMEI as the identifier and carries the emergency indication, the MME uses its own default emergency APN to select a PDN. -GW.
  • Selecting the local PDN-GW for the UE is specifically as follows: After receiving the attach request message, the MME decides to use the static PDN-GW selection function configured locally or combines the locally configured emergency APN and the local static according to the emergency indication carried in the message. The PDN-GW selects a function to select a local PDN-GW for the UE.
  • the foregoing embodiment is an example of the present invention.
  • the embodiment of the present invention can also implement the access of the UE to the local PDN in the non-3GPP, that is, the UE obtains an IP address for the emergency call, as shown in FIG.
  • the UE may carry the emergency indication information in the following steps:
  • step 2 Trusted Non-3GPP IP Access brings the emergency indication information carried by the UE to the AAA proxy and the AAA server and the subsequent local PDN GW.
  • step 5 the PDG GW will also carry this emergency indication in the Indication of IP CAN Session Establishment message.
  • step 3 In the L3 Attach Trigger process of step 3, the UE will carry the emergency indication information, and the Trusted Non-3GPP IP Access continues to deliver this information to the PDN GW in step 4, so that the PDN GW is in the session establishment of the fifth step. Indicates that the session is an emergency session.
  • the MME is notified in the form that the attach request message carries the emergency indication information, so that it can select the local PDN GW for it.
  • the embodiment of the present invention is not limited to the attach request message, and other NAS messages may also carry emergency indication information and notify the MME. If the UE (the USIM card exists) has been generally attached (the PDN-GW may not be local at this time), the UE may initiate a local search by initiating a service request procedure or a Tracking Area Updating procedure. PDN-GW, and obtain an IP address assigned by the PDN-GW to the emergency call.
  • the request message of the above two processes must include the emergency indication.
  • Step S702 The UE establishes an association with the eMSC, and performs an emergency attach to the eMSC to establish an IP channel of the UE to the eMSC.
  • the UE uses the IMSI as the identifier; in the absence of the USIM card, the UE uses the IMEI as the identifier. In this case, the authentication process may not be required.
  • the attachment indication may carry a emergency indication.
  • the discovery mechanism of the eMSC is as follows:
  • the PCO option in the SAE emergency attach message or the originating bearer setup process carries the information requesting the eMSC address, and the PDN-GW or the MME queries the local eMSC address by parsing the parameters in the PCO (for example, configuring the eMSC address, or the PDN) -GW is obtained through the DHCP (Dynamic Host Configuration Protocol) query mechanism.
  • DHCP Dynamic Host Configuration Protocol
  • the eMSC address information is configured or saved for the user in the HSS, and the information is provided by the HSS to the MME.
  • this method is only suitable for the attribution situation.
  • the MME selects a local eMSC for the UE according to preset conditions, such as: location information, operator preference, network topology, or mapping the MME to the eMSC on the network side.
  • the network sends a broadcast to the UE located within its coverage, including whether the network supports CS over SAE/LTE and the corresponding eMSC address.
  • Step S703 When the UE initiates an emergency voice call, send a CM Service Request message to the eMSC, where the CM Service type indicates an emergency call.
  • Step S704 After receiving the CM Service Request message, the eMSC determines whether the authentication and security process is performed. If not, go to step S705 to return the CM Service Accept message to the UE. If initiated, then after the authentication and security are successful, go directly to step S706.
  • Step S706 After performing the authentication and security success or receiving the CM Service Accept message, the UE sends an Emergency Setup activation channel command to the eMSC.
  • UDP User Datagram Protocol
  • Step S707 After determining that the emergency call is acceptable, the eMSC sends a Call Proceeding message to the UE.
  • step S708 and step S709 the eMSC sends an IAM message to the emergency call center located in the PSTN or CS domain, and receives parameters related to the bearer. Then trigger an eMGW selection process.
  • the eMSC can also send the Bearer Information to the UE by using the IP tunnel, and the UE triggers a dedicated bearer setup or default bearer modification process, and the bearer setup request includes a emergency indication indication.
  • Step S710 The eMSC controls the eMGW to establish a voice bearer on the eMGW side. There are two possible scenarios:
  • step S723 If the default bearer established by the UE when it is attached to the SAE is used for signaling transmission and is also used for voice bearer, after step S709 is completed, step S723 is performed immediately.
  • step S709 will be A process of carrying the modification, and then performing step S723.
  • Step S711 The eMSC defines the information about the Rx interface, and sends the application service information to the PCRF, which mainly includes the UE's IP address, user identifier, media type and format, voice codec format, and emergency indication.
  • the PCRF grants the highest QoS authorization and flow-based no-charge rules for emergency calls based on emergency indications. In the case of severe resource scarcity, emergency calls can be prioritized or even preemptively obtained.
  • an emergency bearer of the voice service is established by establishing an emergency dedicated bearer in the evolved network.
  • the PCRF returns an ACK message to the eMSC.
  • Step S727 ⁇ Step S730 after receiving the ACM message, the eMSC returns an Alerting message to the UE. After receiving the ANM message, the eMSC sends a Connect message to the UE.
  • Step S731 The UE returns a Connect Ack message to the eMSC, and starts an emergency voice call.
  • the dedicated bearer setup described above is initiated by the eMSC via the Rx interface.
  • the UE may also initiate establishment of a dedicated bearer, and then the eMSC may modify these dedicated bearers through the Rx interface.
  • FIG. 9 it is a flowchart of an emergency call method for implementing an analog circuit domain on a packet domain according to Embodiment 3 of the present invention.
  • the embodiment is based on the foregoing architecture B, that is, has a similar Gs interface.
  • This embodiment is basically the same as the description in the second embodiment, except that the signaling of the simulated CS domain call initiated by the UE is encapsulated and transmitted through the NAS (Non Access Stratum) signaling in the SAE.
  • the indication of the received NAS message determines that the message needs to be sent to the eMSC, and the message is transparently transmitted to the eMSC for processing.
  • NAS Non Access Stratum
  • the MME and the eMSC have a Gs interface, so the UE can directly send the emergency bearer setup information to the eMSC through the MME, without establishing an IP channel between the UE and the eMSC as in the second embodiment.
  • the UE initiates the simulated CS attach, and the attached parameters are transmitted through a similar Gs interface between the eMSC and the MME.
  • the message of the call is encapsulated in a NAS message in the eUTRAN and sent to the MME.
  • An IE is added to the NAS message to instruct the MME to send the call message data in the message to the eMSC.
  • the remaining steps, such as 3-30a, are basically the same as those of the second embodiment.
  • the difference is that the signaling message of the analog CS call sent by the eMSC to the UE is forwarded to the UE by the MME using the NAS message.
  • the dedicated bearer setup described above is initiated by the eMSC through the Rx interface.
  • the UE may also initiate a dedicated bearer after receiving the call proceeding. Established, then the eMSC modifies these dedicated bearers through the Rx interface.
  • FIG. 10 it is a flowchart of a method for implementing an emergency call in an analog circuit domain on a packet domain according to Embodiment 3 of the present invention.
  • the embodiment is mainly based on architecture A, that is, there is no similar
  • the Gs interface exists.
  • the emergency call release procedure and the initial emergency call release procedure of the user are implemented through IP layer connectivity.
  • the relevant release information is to disconnect the Disconnect message or release the Release message.
  • This embodiment shows the process of releasing the emergency call release of the CS domain initiated by the user (that is, the scenario in which the UE actively hangs up), and the UE triggers the process of releasing the emergency exclusive payload by sending a Disconnect message to the eMSC.
  • the UE and the eMSC maintain the connection of the signaling plane through the connectivity of the IP. This embodiment includes the following steps:
  • Step S1001 The UE sends a Disconnect message to the eMSC to tell the eMSC user to hang up.
  • Step S1002 The eMSC sends a Release message to the emergency call center in the PSTN or CS domain.
  • Step S1003 The eMSC sends a REL message to the UE.
  • Step S1004 After receiving the REL, the UE stops all call control related timers, and then returns an RLC message to the eMSC.
  • Step S1005 The eMSC controls the eMGW to release the related voice media stream.
  • Step S1007 ⁇ Step S1016, the PDN-GW initial evolution network emergency private bearer deletion process.
  • Step S1017 after the emergency dedicated payload is deleted, the PCRF returns an ACK message to the eMSCo.
  • the related release information is to disconnect the Disconnect message or release the Release message.
  • the MME may also resume the recovery process of other proprietary bearers that are stopped by the emergency call (such as activating the values of GBR and MBR). That is, if the UE initiates an emergency call Can suspend or stop some ongoing services because of insufficient resources, release some resources to ensure the smooth progress of emergency calls, so after releasing the emergency bearer established by the emergency call, it is necessary to recover some stopped services, including how to stop and Restoring other proprietary bearers will be described in detail in subsequent embodiments of the present invention, and details are not described herein again.
  • FIG. 11 it is a flowchart of an emergency call method for implementing an analog circuit domain on a packet domain according to Embodiment 4 of the present invention.
  • the embodiment is mainly based on the architecture B, that is, an interface having a GS+ similarity exists.
  • the signaling between the UE and the eMSC is initiated by the UE initiating the CS emergency call release by using the signaling plane between the UE and the MME and the signaling plane between the MME and the eMSC.
  • the steps of the embodiment are basically the same as the foregoing embodiment 3.
  • the difference is that the signaling message of the analog circuit domain between the eMSC and the UE is forwarded by the MME to the UE through the NAS layer (transmitted through a Gs-like interface between the MME and the eMSC)
  • the related IE may be added to distinguish whether the processing of the NAS message in the normal eUTRAN or the signaling message of the emergency call.
  • the relevant release information is to disconnect the Disconnect message or release the Release message.
  • the MME may also resume the recovery process of other proprietary bearers that are stopped by the emergency call (such as activating the values of GBR and MBR).
  • FIG. 12 it is a flowchart of a method for implementing an emergency call in an analog circuit domain on a packet domain according to Embodiment 5 of the present invention.
  • the embodiment is also based on the architecture A, that is, when there is no Gs-like interface, the embodiment is mainly In order to initiate an emergency call release process by the network side, this embodiment needs to implement an emergency call release process through IP layer connectivity.
  • the initial emergency call release process of the network is as follows:
  • Step S1201 The eMSC receives a Release message from the emergency call center.
  • Step S1202 The eMSC sends a Disconnect message to the UE through the IP channel to notify the UE that the remote end has hanged up.
  • Step S1203 The eMSC controls the eMGW to release the voice bearer resources related to the emergency call.
  • Step S1205 After receiving the Disconnect message, the UE stops the call control timer related to the emergency call, and sends a REL message to the eMSC.
  • Step S1206 After receiving the REL message and stopping the call control timer, the eMSC returns an RLC message to the UE.
  • Step S1207 After receiving the RLC message, the UE initially performs a process of releasing the emergency private bearer of the network.
  • the relevant release information is to disconnect the Disconnect message or release the Release message.
  • the MME may also resume the recovery process of other proprietary bearers that are stopped by the emergency call (e.g., activate the values of GBR, MBR) after releasing the emergency proprietary bearer.
  • FIG. 13 it is a flowchart of a method for implementing an emergency call in an analog circuit domain on a packet domain according to Embodiment 6 of the present invention.
  • the embodiment is also based on the architecture B, that is, if an interface similar to Gs+ exists.
  • call release related signaling is delivered through a similar Gs+ interface between the MME and the eMSC.
  • the initial emergency call is released, and the UE initiates the emergency and exclusive after receiving the analog circuit domain release message.
  • step 7 The release process, in which the MME can revert to the recovery process of other proprietary bearers stopped by the emergency call (such as activating the values of GBR, MBR).
  • the description of each step is the same as that of the fifth embodiment. The difference is that the message of the NAS layer of the analog circuit domain module sent by the eMSC to the UE is forwarded to the UE by the MME, and the related IE is added to distinguish the processing of the NAS message in the normal eUTRAN.
  • the MME may also resume the initial emergency call release process of other private networks stopped by the emergency call, including the following steps: 7-load recovery process (such as activating GBR, MBR values) .
  • FIG. 14 is a flowchart of a method for implementing an emergency call in an analog circuit domain on a packet domain according to Embodiment 7 of the present invention.
  • This embodiment is a process of deleting or stopping other dedicated bearers while the UE makes an emergency call. If a UE performs an emergency call and also has service flow data interaction with other PDN-GWs (ie, PDN-GWs used for non-emergency calls), in order to ensure high quality completion of the emergency call, the MME performs a dedicated bearer.
  • PDN-GWs ie, PDN-GWs used for non-emergency calls
  • Activate or modify (such as rewriting GBR, MBR to 0) process to delete or stop all other services of the user or selectively stop the user according to the relevant QoS parameters (such as QCI, Label, ARP, etc.) stored in the MME. Those with lower priority levels.
  • the MME finds that it cannot support all the dedicated bearer setup requests, it initiates a process of deactivating or modifying a dedicated bearer to delete or stop the emergency call users with other lower priority services. To ensure the smooth completion of emergency calls.
  • Step S1401 The MME sends a Request Dedicated Bearer Deactivation message to the S-GW to activate a selected dedicated bearer.
  • the bearer release cause is an emergency call by a specific parameter or a specific indicator bit in the message.
  • Step S1402 The S-GW sends a Request Dedicated Bearer Deactivation message to the PDN GW.
  • Step S1403 if the PCC policy is used, the PDN GW notifies the PCRF about the resource to be released.
  • Step S1404 Step S1413, the evolved network PDN GW initially deactivates the process.
  • the terminal side bearer resources may be tight or scarce.
  • the UE may delete or stop when the emergency call is initiated (for example, the values of the GBR and the MBR are rewritten). 0) - cut other ongoing services or selectively delete or stop those services with lower priority according to QoS parameters (such as QCI, Label, ARP, etc.) stored in the UE to release resources to ensure emergency calls
  • QoS parameters such as QCI, Label, ARP, etc.
  • the eMSC is further configured to determine the actual location information of the UE according to the LCS (Location Services Location Service), for example, according to the network reported by the UE.
  • the location information of the network obtains its actual location information; or the location information of the UE is reported by the UE, and the actual location information reported by the LCS can be verified, so that the emergency call center can accurately locate the UE that makes the emergency call.
  • the embodiment of the present invention can accurately grasp the user location information (such as the cell ID) by using the terminal location in the emergency call, so that the eMSC routes the emergency call and quickly dispatches appropriate resources when the user needs assistance.
  • the eMSC can be used as a client of the LCS (Location Services) architecture to receive or actively obtain the location information of the user terminal.
  • the UE can provide the location of the UE in the emergency setup message.
  • Network location information such as cell ID
  • the eMSC queries the LCS for the location information of the user through the LCS message; if the UE provides the location of the UE in the emergency setup message Information, then eMSC can also seek LCS to verify location information.
  • the embodiment of the present invention proposes a method for completing an emergency call in an analog circuit domain by using an eMSC entity in an evolved network, so that an emergency call service in a SAE/LTE packet network is implemented without relying on IMS.
  • FIG. 15 it is a structural diagram of an emergency call service entity according to an embodiment of the present invention, where the emergency call service entity is a p-CSCF in an eMSC or an IMS.
  • the emergency call service entity includes an emergency attachment processing module 1, a bearer setup information acquisition module 2, a bearer information delivery module 3, a bearer setup notification module 4, and a bearer association control module 5.
  • the emergency attachment processing module 1 is configured to accept an emergency attachment of the user equipment UE, where the emergency call service entity is a local emergency call service entity selected by the mobility management entity MME that is accessed by the UE;
  • the module 2 is configured to obtain, after the emergency call initiated by the UE, the bearer setup information required for establishing an emergency voice bearer for the UE.
  • the bearer information sending module 3 is configured to separately send the bearer setup information to the evolved media.
  • the bearer establishment notification module 4 is configured to notify the eMGW and the PCRF to establish corresponding eMGW side emergency voice bearers and SAE side emergency voice bearers;
  • the bearer association control module 5 is used on the eMGW side 7
  • the UE performs an emergency call according to the associated emergency voice bearer on the eMGW side and the emergency voice bearer on the SAE side.
  • the bearer setup information acquisition module 2 includes a UE bearer setup information receiving sub-module 21 and a bearer parameter obtaining sub-module 22, and the UE bearer setup information receiving sub-module 21 is configured to receive an IP channel between the UE through the emergency call service entity and the UE or The UE bearer setup information sent by the interface between the MME and the emergency call service entity; the bearer parameter acquisition sub-module 22 is configured to request related bearer parameters from the emergency call center.
  • the emergency call service entity further includes a release module 6 configured to release the corresponding eMGW side emergency voice bearer and the SAE side emergency voice bearer after receiving the release message of the emergency call center or the UE.
  • the emergency call service entity further includes a location information determining module 7 configured to determine a specific location of the UE by using a positioning service LCS according to the location information reported by the UE.
  • the embodiment of the present invention provides an emergency call service entity, which can complete an emergency call in an analog circuit domain in an evolved network by using the emergency call service entity, so that an emergency call service in the S AE/LTE packet network can be implemented.
  • Non-volatile storage medium which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.
  • a computer device may It is a personal computer, a server, or a network device, etc. that performs the methods described in various embodiments of the present invention.

Description

一种紧急呼叫方法和装置 本申请要求于 2007年 12 月 18 日提交中国专利局， 申请号为 200710301851.X, 发明名称为 "一种紧急呼叫方法和装置" 的中国专 利申请的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明实施例涉及移动通信技术领域，特别是涉及一种紧急呼叫 方法和装置。 背景技术
UMTS ( Universal Mobile Telecommunication System,全球移动通 信系统）是采用 WCDMA ( Wideband Code Division Multiple Access, 宽带码分多址） 空中接口技术的第三代移动通信系统， 通常也把 UMTS系统称为 WCDMA通信系统。 UMTS系统包括 RAN ( Radio Access Network, 无线接入网络）和 CN ( Core Network, 核心网络）。 其中 RAN用于处理所有与无线有关的功能， 而 CN处理 UMTS系统 内所有的话音呼叫和数据连接， 并实现与外部网络的交换和路由功 h
匕。
如图 1所示，为现有技术 UMTS系统逻辑架构示意图。对 UMTS 系统中主要部分介绍如下：
GGSN ( Gateway General Packet Radio Service Support Node, 网 关通用分组无线业务支持节点）作为一个基本的网元功能实体， 提供 数据包在同外部数据网之间的路由和封装。 SGSN ( Serving GPRS Support Node, 服务 GPRS支持节点）作为一个基本的组成网元， 其 主要的作用就是为本 SGSN服务区域的 MS ( Mobile Station,移动台） 转发输入 /输出的 IP( Internet Protocol,互联网协议）分组。 RAN ( Radio Access Network, 无线接入网） 由 RNC ( Radio Network Controller, 无线网络控制器）和 NodeB ( Node Base station, 基站）组成。 目前，在 LTE ( Long Term Evolved,长期演进网络） /SAE ( System Architecture Evolved, 系统架构演进网络 )技术中， LTE的目的是提 供一种能够降低时延、提高用户数据速率、 改进的系统容量和覆盖的 低成本的网络，使用 PS域业务，承载网络都为 IP承载。如图 2所示， 为现有技术的 LTE/SAE网络架构图。
下述对 SAE演进网络架构及其功能说明， 在演进的分组核心网 中：
MME ( Mobility Management Entity, 移动性管理实体 )的功能是 保存 UE ( User Equipment, 用户设备 )的移动性管理上下文， 如用户 的标识，移动性管理状态、位置信息等，并对 NAS(Non Access Stratum, 非接入层)信令进行处理， 负责 NAS信令的安全等。
SAE GW(SAE网关）包括两部分筒称 S-GW ( Serving Gateway, 服务网关)和 P-GW ( PDN Gateway, 分组数据网络网关）。 S-GW与 P-GW是两个逻辑实体， 可以存在于同一个或不同的物理实体上。
S-GW上保存 UE的用户面上下文，如 UE的 IP地址和路由信息， 执行合法监听、 分组数据路由功能等。
MME通过 S1-MME, S-GW通过 S1-U分别与 EUTRAN( Evolution UMTS Terrestrial Radio Access Network,演进 UMTS陆地无线接入网 ) 网络负责控制面和用户面的连接。 同时 MME通过 S3接口， S-GW通 过 S4接口分别与 2G/3G SGSN连接， 分别负责 UE在 3G和 SAE网 络之间的移动性控制面锚点和用户面锚点功能。
P-GW负责 UE接入到分组数据网的用户面锚点功能， 通过 SGi 参考点与外部分组数据网进行通信， 具有分组路由和转发的功能， 并 负责策略计费增强功能、 基于每个用户的分组过滤功能等。
在实现本发明实施例过程中，发明人发现现有技术中至少存在如 下问题： 随着现有网络向 SAE/LTE网络的不断演进， 现有网络中的 业务也需要由基于电路域向基于分组域转变，如电路域语音呼叫到分 组域语音呼叫的 VOIP ( Voice Over IP, 基于 IP的语音） 业务， 然而 在目前的 SAE/LTE中， 却还没有紧急呼叫 （ Emergency Call )业务相 应的实现方法。
发明内容
本发明实施例要解决的问题是提供一种紧急呼叫方法和装置，解 决现有技术中无法在 SAE/LTE网络中实现紧急呼叫业务的技术缺陷。
为达到上述目的， 本发明实施例一方面提出一种紧急呼叫方法， 具体包括：
用户设备 UE向演进网络 SAE网络发起紧急附着请求， 所述紧 急附着请求包含紧急指示；
所述 SAE网络收到所述紧急指示后， 为所述 UE选择紧急呼叫 服务实体；
所述 UE紧急附着至所述 SAE网络后， 向所述紧急呼叫服务实 体发送所述紧急呼叫请求；
所述紧急呼叫服务实体建立紧急语音承载， 所述 UE根据所述建 立的紧急语音承载进行紧急呼叫。
本发明实施例还提出一种紧急呼叫释放方法， 包括：
紧急呼叫服务实体接收 UE 或紧急呼叫中心发送的相关释放 消息；
根据所述相关释放消息， 所述紧急呼叫服务实体释放相关的 紧急语音承载资源。
本发明实施例还提出一种紧急附着方法， 具体包括：
当所述 UE检测到用户正在发起紧急呼叫时，所述 UE向 SAE网 络发起 NAS消息，所述 NAS消息携带有紧急指示和所述用户的唯一 标识；
在收到所述 NAS消息之后， 根据所述 NAS消息为所述 UE选择 本地分组数据网络网关 PDN-GW , 所述 PDN-GW为所述 UE分配相 应的 IP地址， 使所述 UE附着至所述 S AE网络。
本发明实施例还提出一种紧急呼叫服务实体， 包括紧急附着处理 模块， 承载建立信息获取模块， 承载信息下发模块， 承载建立通知模 块和承载关联控制模块，
所述紧急附着处理模块， 用于接受用户设备 UE的紧急附着； 所述承载建立信息获取模块，用于在所述 UE发起的紧急呼叫后， 获取为所述 UE建立紧急语音承载所需的承载建立信息；
所述承载信息下发模块， 用于将所述承载建立信息分别下发 给媒体网关和策略计费规则功能 PCRF;
所述承载建立通知模块，用于通知媒体网关和 PCRF建立相应的 紧急呼叫服务实体侧紧急语音承载和 SAE侧紧急语音承载；
所述承载关联控制模块， 用于在所述紧急呼叫服务实体侧承 载和 PCRF侧承载建立后，所述媒体网关使所述紧急呼叫服务实体 侧紧急语音承载和 SAE侧紧急语音承载关联， 所述 UE根据关联 的所述紧急呼叫服务实体侧紧急语音承载和 SAE侧紧急语音承载 进行紧急呼叫。
本发明实施例的技术方案具有以下优点，通过本发明实施例所提 出的紧急呼叫方法和装置能够在 SAE/LTE演进网络中借助紧急呼叫 服务实体来完成模拟电路域的紧急呼叫。
附图说明
图 1为现有技术 UMTS系统逻辑架构示意图；
图 2为现有技术的 LTE/SAE网络架构图；
图 3为本发明实施例提供的一种实现紧急呼叫方法流程图； 图 4为本发明实施例一的实现紧急呼叫方法流程图；
图 5为本发明实施例 eMSC网络架构 A的结构图；
图 6为本发明实施例 eMSC网络架构 B的结构图；
图 7 为本发明实施例二的在分组域上模拟电路域实现紧急呼叫 方法流程图；
图 8为本发明实施例非 3GPP接入下 UE初始接入流程图； 图 9 为本发明实施例三的在分组域上模拟电路域实现紧急呼叫 方法流程图；
图 10为本发明实施例三的在分组域上模拟电路域实现紧急呼叫 方法流程图；
图 11为本发明实施例四的在分组域上模拟电路域实现紧急呼叫 方法流程图；
图 12为本发明实施例五的在分组域上模拟电路域实现紧急呼叫 方法流程图；
图 13为本发明实施例六的在分组域上模拟电路域实现紧急呼叫 方法流程图；
图 14为本发明实施例七的在分组域上模拟电路域实现紧急呼叫 方法流程图；
图 15为本发明实施例演进移动服务交换中心 eMSC结构图。 具体实施方式
本发明实施例通过一个紧急呼叫服务实体来完成模拟电路域的 紧急呼叫， 这样能够保护运营商的现有投资， 并尽可能的继续提供传 统电路域的业务。 其中， 该紧急呼叫服务实体为 eMSC ( Evolution Mobile-services Switching Center, 演进的移动服务交换中心）或 IMS ( IP Multimedia Subsysterm , IP 多媒体子系统） 中的 p - CSCF ( Proxy-Call Session Control Function, 代理呼叫会话控制功能）。 通 过紧急呼叫服务实体将 eMGW ( Evolved Media Gateway, 演进媒体 网关）侧紧急语音承载和 SAE侧紧急语音承载关联， 从而实现 UE 的紧急呼叫；并且在本发明实施例实现过程中还考虑到紧急业务不受 用户签约限制、 具有较高的优先级别、 为漫游用户在拜访网络就地完 成紧急业务的原则， 以及运营商尚未部署网络整合产品 IMS 网络的 可能规划现状等因素， 并根据上述因素对本发明实施例进行了优化。
为了便于理解本发明， 以下实施例将以紧急呼叫服务实体为 eMSC为例进行描述， 但是需要说明的是在下述实施例中紧急呼叫服 务实体为 eMSC, 但是在其他网络架构中该紧急呼叫服务实体也可以 是其他设备， 如在运营商部署了网络整合产品 IMS 网络下紧急呼叫 服务实体也可以是 IMS中的 p - CSCF。
本发明实施例提供一种紧急呼叫方法， 如图 3 所示， 具体包 括：
5301 ,用户设备 UE向演进网络 SAE网络发起紧急附着请求， 紧急附着请求包含紧急指示；
5302, SAE 网络收到紧急指示后， 为 UE选择紧急呼叫服务 实体；
5303 , UE 紧急附着至 SAE 网络后， 向紧急呼叫服务实体发 送紧急呼叫请求；
5304, 紧急呼叫服务实体建立紧急语音承载， UE根据建立的 紧急语音承载进行紧急呼叫。
本发明实施例的技术方案具有以下优点，通过本发明实施例所提 出的紧急呼叫方法和装置能够在 SAE/LTE演进网络中借助紧急呼叫 服务实体来完成模拟电路域的紧急呼叫。
如图 4所示， 为本发明实施例一的实现紧急呼叫方法流程图， 该 流程图为本发明实施例总体概括的流程图，其中具体流程细节将在后 续实施例中进行详细描述， 在此不再赘述， 该实施例包括以下步骤： 步骤 S401 , UE检测到紧急呼叫建立请求。
步骤 S402,在 UE没有足够的能力或者资源建立紧急呼叫情况的 处理。 如果 UE有足够的能力或者资源建立紧急呼叫， 将不存在该过 程。
步骤 S403, UE向 SAE演进网络的紧急附着， 并通过该附着过 程建立 CS信令的承载。
步骤 S404, eMSC的发现过程。
步骤 S405, UE附着到 eMSC过程。
步骤 S406, 借助 eMSC来完成 UE的紧急呼叫。
然而需要说明的是在上述步骤 S401 -步骤 S403 为 UE 向 SAE/LTE演进网络的紧急附着过程，在上述实施例中上述向 SAE/LTE 演进网络的紧急附着是 UE向 eMSC附着的基础， 只有 UE附着到 SAE/LTE演进网络才能获得相应的 IP地址从而建立与 eMSC的连接， 为后续的紧急呼叫做准备。 但是本发明实施例提出的上述 UE 向 SAE/LTE 演进网络的紧急附着过程不仅适用于 eMSC, 还适用于对 IMS 紧急呼叫， 这样 eMSC在紧急呼叫中的位置和作用相当于 IMS 紧急呼叫中的 P-CSCF网元。因此在 IMS紧急呼叫如果通过本发明下 述实施例的方式实现 UE向 SAE演进网络的紧急附着， 则也应当为 本发明实施例保护范围所涵盖。
本发明实施例的 eMSC方案中紧急呼叫建立以及 SAE紧急 载 建立流程都与演进网络系统的架构相关。 如： 演进网络系统是否引入 eMSC和演进网络间的类似 Gs的接口。 该接口是否可以传递呼叫方 面的高层信令，在没有该接口的情况下如何保证呼叫信令及媒体面的 安全建立等问题。并且本发明实施例提出了两种 eMSC方案的网络架 构， 并给出了不同架构下实现 PS域模拟 CS域紧急呼叫建立和 SAE 紧急承载建立的详细流程以及具体问题的细节描述。本发明实施例给 出的两种 eMSC网络架构包括架构 A和架构 B。
如图 5所示， 为本发明实施例 eMSC网络架构 A的结构图， 在 架构 A中， eMSC包含部分 MSC、 MGCF ( Media Gateway Control Function,媒体网关控制功能）的功能，并拥有分组域中 AS( Application Serve, 应用服务器）的功能。 eMSC通过与 PCRF ( Policy Control and Charging Rules Function, 策略控制与计费规则功能 )间的 Rx+接口来 控制建立 PS域的承载， eMSC和 UE间采用逻辑接口（ logical tunnel ) 来模拟传递电路域的信令。 并引入 eMGW实体作为媒体面的转换网 关（即分组域的 VoIP数据与电路域的 VoIP数据的转换 ), 该实体包 含 IMS域的 IM-MGW和电路域的 MGW( Media Gateway,媒体网关 ) 功能。
如图 6所示， 为本发明实施例 eMSC网络架构 B的结构图， 在架构 B中，与上述架构 A类似， 不同的是引入了 MME和 eMSC 间类似 GS+的接口， 该接口可用来传递呼叫消息的参数。
以下将以上述架构 Α和架构 B为基础， 对本发明紧急呼叫的 方法进行详细的描述：
如图 7 所示， 为本发明实施例二的在分组域上模拟电路域实 现紧急呼叫方法流程图， 该实施例基于上述架构 A, 即无类似 Gs 接口。本实施例说明， UE的语音媒体面数据在 SAE/LTE专有承载 或缺省承载上运行， 在 UE没有附着到 eMSC之前， 需要本地一个 PDN-GW为 UE分配一个用于紧急呼叫的 IP地址。
步骤 S701 , UE向 SAE发起紧急附着， SAE为 UE选择一个 相应的一个本地 PDN-GW, 并获得本地 PDN-GW为 UE分配的用 于紧急呼叫的 IP地址， 同时为模拟 CS域注册、 呼叫等相关信令 建立缺省承载或者专用承载。 其中， 在承载建立请求中含有 emergency indication指示。在该步骤中 UE发起紧急附着有一个前 提就是 UE必须能够识别用户正在发起一个紧急呼叫，本发明实施 例可以通过在 UE终端中定义一个特定按键，或者由终端识别用户 拨打的号码是紧急号码来实现。 如用户拨打 110, 则终端能够自动 识别 110为紧急号码， 自动向 SAE发起紧急附着。
该实施例中用户还没有附着到 SAE网络， 在紧急呼叫建立之 前， UE需要紧急附着至 SAE网络。
比如， 以 3GPP ( 3rd Generation Partnership Project, 第三代合 作伙伴计划）接入为例对该步骤进行描述， 可以包括以下几步： A: UE向 SAE发送 emergency attach request 消息, 其中该 emergency attach request 消息 中携带紧急标识 emergency indication和该用户的唯一标识。 通用用户识别卡） 卡， 已经附着 （该附着不同于紧急附着， 为 UE 的正常附着到网络） 或未附着的情况下， 为了紧急呼叫业务， UE 要发起一个紧急附着的过程， emergency attach request 消息中携带 用户的标识信息， 如用户的 IMSI作为 UE的标识， 与普通附着不 同的是该 attach request 消息中携带 emergency indication指示来告 知网络这是一个紧急附着， 作为后续 PDN-GW选择的参考， 消息 中还可以携带 emergency APN ( Access Point Name , 接入点名称 )。 在该过程中， 由网络决定是否执行认证和安全的过程。 另外 UE在 已经附着的情况下， 还可以通过 Tracking Area Update 过程或者 service request 过程来触发一个本地 PDN-GW 寻找过程， TAU Request消息和 service request消息中 emergency indication携带紧 急指示， 同时还可以携带 emergency APN。
2 )、 如果用户不存在 USIM 卡的情况下， emergency attach request 消息中 UE采用 IMEI作为用户自己的标识信息， emergency indication 指示来告知网络这是一个紧急附着， 同样可以携带 emergency APN。 网络不需要执行认证和安全的过程。
B、 由于紧急呼叫采用本地执行的策略， 所以在附着过程中网 络要找到一个本地的 PDN-GW为 UE分配用于紧急呼叫的 IP地址。 PDN-GW选择策略如下：
1 )、 如果 UE在 attach request 消息里携带了 emergency APN (包含网络标识和运营商标识）， MME要对此进行判别， 如果属 于本归属地的 APN , MME 将 居此 APN 选择一个本地的 PDN-GW , 如果不属于本地归属地， MME 使用自己配置默认的 emergency APN来选择一个 PDN-GW。
2 )、如果 UE在 attach request 消息里携带了 emergency APN (只 包含网络标识）， MME根据自己配置的默认的 emergency APN来 选择一个本地的 PDN-GW
3 )、 如果 UE 在 attach request 消息里没有携带 emergency APN, MME在判断 UE携带 emergency indication和采用 IMSI来 作为标识时， 它会向 HSS查询用户的签约信息并且判断用户签约 的 emergency APN是否属于本地， 如果是， 则采用该用户签约的 emergency APN , 否则采用 MME配置默认的 emergency APN来选 择一个 PDN-GW。 4 )、 如果 UE 在 attach request 消息里没有携带 emergency ΑΡΝ, ΜΜΕ无法从 HSS获得用户的签约数据或者该用户采用 IMEI 作为标识并且携带 emergency indication时， MME会使用自己配置 默认的 emergency APN来选择一个 PDN-GW。
为 UE选择本地 PDN-GW具体为： MME在接收到 attach request 消息后， 根据消息携带的紧急指示， 决定使用本地已经配置的静 态 PDN-GW选择功能或者是结合本地配置的紧急 APN以及本地的 静态 PDN-GW选择功能来为 UE选择一个本地的 PDN-GW。
上述实施例为本发明以 3GPP接入为例，本发明实施例还可在 非 3GPP实现 UE至本地一个 PDN的接入，即实现 UE获得一个用 于紧急呼叫的 IP地址， 如图 8所述， 为本发明实施例非 3GPP接 入下 UE初始接入流程图。 UE可以在以下步骤中携带 emergency indication信息：
A: 在第 2步的 EAP鉴权过程中， Trusted Non-3GPP IP Access 将 UE携带的 emergency indication信息带给 AAA代理以及 AAA 服务器和后续的本地 PDN GW。在第 5步中， PDG GW在 Indication of IP CAN Session Establishment 消息中也将携带此 emergency indication。
B:在第 3步的 L3 Attach Trigger过程中， UE将携带 emergency indication信息， Trusted Non-3GPP IP Access在第 4步中继续传递 此信息给 PDN GW, 以便 PDN GW在第 5步的会话建立中指示该 会话是一个紧急会话。
需要说明的是， 本发明上述实施例通过 attach request 消息携 带 emergency indication信息的形式通知 MME,使其能够为其选择 本地 PDN GW。 然而本发明实施例并不限于 attach request 消息， 其他 NAS消息也可携带 emergency indication信息并通知 MME。 如果 UE (存在 USIM卡） 已经一般式附着 （此时的 PDN-GW可 能并不是本地的）， UE可以通过再发起一个 service request过程或 者是 Tracking Area Updating 过程来发起一个寻找本地的 PDN-GW, 并获得一个该 PDN-GW为紧急呼叫分配的 IP地址。 上 述 2个过程的请求消息中都要必须包括 emergency indication
步骤 S702, UE建立和 eMSC的关联， 并向 eMSC进行紧急附 着， 建立 UE到 eMSC的 IP通道。 在有 USIM卡的情况下， UE采 用 IMSI作为标识； 在缺少 USIM卡情况下， UE采用 IMEI作为标 识， 此时， 可以不需要进行鉴权过程。 附着消息里可以携带 emergency indication指示。
该过程 eMSC的发现机制如下：
A: 在 SAE紧急附着消息或发起承载建立过程中的 PCO选项 中携带请求 eMSC地址的信息， PDN-GW或者 MME通过解析 PCO 中的参数来查询本地一个 eMSC地址 （如配置 eMSC的地址， 或 者 PDN-GW通过 DHCP ( Dynamic Host Configuration Protocol, 动 态主机分配协议） 查询机制获取）。
B:在 HSS中为用户配置或者保存 eMSC地址信息，并由 HSS 提供该信息给 MME。 但是该方法只适合归属地情况下。
C: MME根据预设的条件， 比如： 位置信息， 运营商偏好、 网络拓朴或在网络侧配置 MME与 eMSC的对应关系等为 UE选择 一个本地的 eMSC。
D: 网络向位于其覆盖范围内的 UE发送广播， 其中包括网络 是否支持 CS over SAE/LTE以及相应的 eMSC地址。
步骤 S703 , 当 UE 发起紧急语音呼叫时， 发送 CM Service Request消息给 eMSC,该消息里 CM Service type里指示 emergency call。
步骤 S704, eMSC接收到 CM Service Request消息后， 决定是 否发认证和安全的过程。 如果不发起， 转到步骤 S705 , 回 CM Service Accept消息给 UE。如果发起， 则在认证和安全成功后直接 转到步骤 S706。
步骤 S706, UE在进行认证和安全成功或者接收到 CM Service Accept消息后， 发送 Emergency Setup激活通道命令给 eMSC。 包 括以下 7 载建立信息： UE接受媒体面的 IP 地址和 UDP ( User Datagram Protocol, 用户数据报协议）端口、 承载能力、 流标识以 及用户支持的语音编解码列表， 在 emergency category单元段里指 示了该紧急呼叫的业务类别。同时 UE也可以在该消息中提供其位 置信息。
步骤 S707 , eMSC 判断该紧急呼叫可接受后， 发送 Call Proceeding消息给 UE。
步骤 S708和步骤 S709, eMSC发送 IAM消息给位于 PSTN 或者 CS域中的紧急呼叫中心， 并收到相关承载方面的参数。 接着 触发一个 eMGW的选择过程。 在步骤 S709后， eMSC也可以使用 IP隧道将 Bearer Information发给 UE, 由 UE触发一个专用承载建 立或者缺省承载修改的过程， 承载建立请求中含有 emergency indication指示。
步骤 S710, eMSC控制 eMGW建立 eMGW侧的语音承载。 接下来分两种可能情况：
A:如果 UE在附着到 SAE时所建立的缺省承载不但用于信令 传输同时也用于语音承载， 则步骤 S709 完成后， 紧接执行步骤 S723。
B:如果 UE在附着到 SAE时所建立的缺省承载不但用于信令 传输， 同时在对该承载的一些信息 （如 QoS ) 进行修改后既用于 语音承载， 那么步骤 S709步后将是一个承载修改的过程， 然后执 行步骤 S723。
步骤 S711 , eMSC定义相关 Rx接口的信息， 向 PCRF下发应 用业务信息， 主要包括 UE的 IP地址、 用户标识、 媒体类型及格 式、 语音编解码格式和紧急指示。 PCRF会根据紧急指示给予紧急 呼叫最高的 QoS授权和基于流的免计费规则。在资源严重匮乏时， 紧急呼叫能够优先甚至以抢占的方式获得资源。
步骤 S712 ~ 21 , 采用在演进网络中建立紧急专用承载的模式 建立语音业务的紧急承载。 步骤 S722, PCRF向 eMSC回 ACK消息。
步骤 S723 ~步骤 S726, eMSC控制 eMGW修改媒体流的关 联， 建立局间媒体承载。
步骤 S727 ~步骤 S730, eMSC收到 ACM消息后， 向 UE回 Alerting消息； 收到 ANM消息后， 发 Connect消息给 UE。
步骤 S731 , UE回 Connect Ack消息给 eMSC, 并开始紧急语 音通话。
上面描述的专用承载建立是 eMSC通过 Rx接口发起的。 除此 之外， UE在接收到 call proceeding之后也可以先发起专用承载的 建立， 然后 eMSC通过 Rx接口再对这些专用承载进行修改。
如图 9 所示， 为本发明实施例三的在分组域上模拟电路域实 现紧急呼叫方法流程图， 该实施例基于上述架构 B , 即有类似 Gs 接口。 该实施例与实施例二中的步骤说明基本相同， 只是 UE发起 的模拟 CS域呼叫方面的信令通过在 SAE中的 NAS ( Non Access Stratum, 非接入层）信令封装传递， MME根据收到的 NAS消息 的指示， 判断该消息需要发送到 eMSC, 则将该消息透传给 eMSC 处理。 因此也正是因为 MME和 eMSC之间有 Gs接口， 因此 UE 可以直接通过 MME将紧急承载建立信息发送给 eMSC, 而无需像 实施例二一样建立 UE和 eMSC之间的 IP通道。
1、 UE发起模拟的 CS附着， 通过 eMSC和 MME间的类似 Gs的接口传递附着参数。
2、 UE需要发起一个呼叫时， 将呼叫的消息封装在 eUTRAN 中的 NAS消息中发送给 MME。 在这个 NAS消息中增加一个 IE, 来指示 MME将该消息中的呼叫消息数据发送给 eMSC。
其余步骤如 3-30a同实施例二的技术方案基本相同， 区别在于 eMSC发送给 UE的模拟 CS呼叫的信令消息是通过 MME用 NAS 消息转发给 UE。
上面描述的专用承载建立是 eMSC通过 Rx接口发起的。 除此 之外， UE在接收到 call proceeding之后也可以先发起专用承载的 建立， 然后 eMSC通过 Rx接口再对这些专用承载进行修改。
如图 10所示， 为本发明实施例三的在分组域上模拟电路域实 现紧急呼叫方法流程图， 该实施例主要基于架构 A, 即没有类似
Gs的接口存在的情况，在该情况下需要通过 IP层连通性实现紧急 呼叫释放流程， 用户初始的紧急呼叫释放流程。
相关释放信息为断开连接 Disconnect 消息或释放 Release 消 息。
该实施例给出了用户发起的 CS 域紧急呼叫释放的流程 （即 UE主动挂机的情景 ), UE通过给 eMSC发 Disconnect消息触发释 放紧急专有^ ^载的过程。 在该实施例中， UE和 eMSC通过 IP的 连通性保持信令面的连接。 该实施例包括以下步骤：
步骤 S1001 , UE发 Disconnect消息给 eMSC来告诉 eMSC用 户挂机。
步骤 S1002, eMSC发 Release消息给处于 PSTN或者 CS域的 紧急呼叫中心。
步骤 S1003, eMSC发 REL消息给 UE。
步骤 S1004, UE收到 REL后， 停止所有的呼叫控制相关的定 时器， 然后回 RLC消息给 eMSC。
步骤 S1005, eMSC控制 eMGW释放相关的语音媒体流。 步骤 S1006, eMSC给 PCRF发应用业务信息来告知 PCRF有 关该紧急呼叫媒体流 QoS保证机制的关闭。
步骤 S1007 ~步骤 S1016, PDN-GW初始的演进网络紧急专有 承载的删除过程。
步骤 S1017, 在紧急专有^载被删除后， PCRF回 ACK消息 给 eMSCo
相关释放信息为断开连接 Disconnect 消息或释放 Release 消 息。 需要说明的是在上述实施例的步骤 S1009或步骤 S1013之后， MME 还可以恢复为紧急呼叫所停止的其它专有承载的恢复过程 (比如激活 GBR、 MBR的值）。 即如果在 UE发起紧急呼叫时可 能会因为自身资源不足而暂停或停止一些正在进行的业务， 释放 一些资源以保证紧急呼叫的顺利进行， 因此在释放紧急呼叫建立 的紧急承载后需要恢复一些已停止的业务， 其中关于如何停止及 恢复其他专有承载将在本发明后续实施例进行详细介绍， 在此不 再赘述。
如图 11所示， 为本发明实施例四的在分组域上模拟电路域实 现紧急呼叫方法流程图， 该实施例主要基于架构 B , 即有类似 GS+ 的接口存在的情况。该实施例给出了在 UE和 eMSC间的信令是通 过 UE和 MME间的 NAS层面和 MME与 eMSC间的信令面传递 情况下， UE主动发起 CS紧急呼叫释放的流程。
该实施例的步骤说明同上述实施例三基本相同， 区别在于 eMSC与 UE间的模拟电路域的信令消息是通过 NAS层由 MME 转发给 UE (通过 MME与 eMSC间的类似 Gs的接口传递），其中， 可在该 NAS 层消息的处理靠添加相关的 IE 来区分是正常的 eUTRAN中 NAS消息的处理， 还是紧急呼叫的信令消息。 相关释 放信息为断开连接 Disconnect消息或释放 Release消息。
同样在本实施例中的步骤 S1009或步骤 S1013之后， MME也 可以恢复为紧急呼叫所停止的其它专有承载的恢复过程 （比如激 活 GBR、 MBR的值）。
如图 12所示， 为本发明实施例五的在分组域上模拟电路域实 现紧急呼叫方法流程图， 该实施例也是基于架构 A, 即没有类似 Gs的接口存在的情况下， 该实施例主要为由网络侧发起紧急呼叫 释放流程，该实施例需要通过 IP层连通性实现紧急呼叫释放流程， 网络初始的紧急呼叫释放流程如下图所示：
步骤 S1201 , eMSC接收到来自紧急呼叫中心的 Release消息。 步骤 S1202, eMSC通过 IP通道给 UE发 Disconnect消息来告 知 UE远端已经挂机。
步骤 S1203 , eMSC控制 eMGW释放紧急呼叫相关的语音承 载资源。 步骤 S1204, 在得知 eMGW上语音 7 载资源被释放后回紧急 呼叫中心 Release Complete消息。
步骤 S1205 , UE在收到 Disconnect消息后， 停止与该紧急呼 叫相关的呼叫控制定时器， 并发 REL消息给 eMSC。
步骤 S1206, eMSC在收到 REL消息停止呼叫控制定时器后， 回 RLC消息给 UE。
步骤 S1207, UE在收到 RLC消息后， 初始演进网络紧急专有 承载释放的过程。
相关释放信息为断开连接 Disconnect 消息或释放 Release 消 息。 同样在该实施例步骤 S1207中， MME也可以在释放紧急专有 承载之后，恢复为紧急呼叫所停止的其它专有承载的恢复过程（比 如激活 GBR、 MBR的值）。
如图 13所示， 为本发明实施例六的在分组域上模拟电路域实 现紧急呼叫方法流程图， 该实施例也是基于架构 B , 即有类似 Gs+ 的接口存在的情况下。 在该实施例中呼叫释放相关的信令通过 MME和 eMSC 间类似 Gs+接口来传递。 该实施例给出了 UE和 eMSC间的呼叫信令是通过 UE和 MME间的 NAS层面转接的情况 下， 网络初始紧急呼叫释放， 同时 UE收到模拟电路域释放消息后 主动发起紧急专有 7 载的释放过程， 同时在该过程中， MME可以 恢复为紧急呼叫所停止的其它专有承载的恢复过程 （比如激活 GBR、 MBR 的值）。 各步骤的说明同实施例五， 区别在于 eMSC 发送给 UE的模拟电路域模块 NAS层的消息是通过 MME转发给 UE,靠添加相关的 IE来区分正常的 eUTRAN中 NAS消息的处理。 同样， 在本发明实施例步骤 7过程中， MME也可以恢复为紧急呼 叫所停止的其它专网络初始的紧急呼叫释放流程包括以下步骤： 有 7 载的恢复过程 （比如激活 GBR、 MBR的值）。
如图 14所示， 为本发明实施例七的在分组域上模拟电路域实 现紧急呼叫方法流程图。 该实施例为在 UE进行紧急呼叫的同时， 对其他专用承载的删除或停止流程。 如果在一个 UE进行紧急呼叫的同时还与其它的 PDN-GW(即 非紧急呼叫使用的 PDN-GW )有业务流数据交互的情况下， 为了 保证紧急呼叫高质量的完成， MME 执行专用承载去激活或修改 (如将 GBR、 MBR改写为 0 ) 过程来删除或停止该用户其它的一 切业务或者是根据保存在 MME中的有关 QoS参数（如 QCI, Label, ARP等 ) 来选择性的停止用户那些优先级别比较低的业务。
在网络拥塞的情况下， MME发现自己不能支持所有的专有承 载建立请求时， 会发起一个专有承载去激活或修改的过程来删除 或停止紧急呼叫用户其它优先级别比较低的业务， 以此来保证紧 急呼叫的顺利完成。
步骤 S 1401 , MME发送 Request Dedicated Bearer Deactivation 消息给 S-GW 来去激活一个选定的专有承载。 通过该消息中的特 定参数或者特定指示位来表明该承载释放原因是紧急呼叫。
步骤 S1402, S-GW发送 Request Dedicated Bearer Deactivation 消息给 PDN GW。
步骤 S1403 , 如果使用 PCC策略， PDN GW通知 PCRF关于 要被释放的资源。
步骤 S1404 ~步骤 S1413 , 演进网络 PDN GW初始专用 载 去激活的过程。
其中， 在 UE发起紧急呼叫时， 可能会发生终端侧承载资源紧 张或者匮乏的情况， 为了保证紧急呼叫高质量的执行， UE再发起 紧急呼叫时可删除或停止 （如将 GBR、 MBR的值改写为 0 ) —切 其它正在进行中的业务或者根据保存在 UE中有关 QoS参数（如 QCI, Label, ARP 等） 来选择性的删除或停止那些优先级别比较 低的业务来释放资源以保证紧急呼叫业务正常发起， 在触发一个 演进系统中 UE初始专用承载释放的过程中，通过释放消息里的特 定参数或者是特定指示位来表明释放原因是紧急呼叫。
其中，在该实施例中 eMSC还能够根据 LCS( Location Services 定位业务）确定 UE所在的实际位置信息， 例如根据 UE上报的网 络位置信息得到其实际位置信息；或 UE上报了其位置信息也可以 通过 LCS对其上报的实际位置信息进行校验， 使得紧急呼叫中心 能对进行紧急呼叫的 UE进行准确定位。本发明实施例借助紧急呼 叫中的终端定位可以准确地掌握用户位置信息 （如 cell ID ), 以便 eMSC 路由紧急呼叫并在用户需要协助时迅速调遣合适的资源。 eMSC在处理紧急呼叫时， 可以作为 LCS ( Location Services, 定 位业务） 架构的一个客户端， 通过以下方法来接收或主动获取用 户终端的位置信息： 如果 UE在 emergency setup消息中可提供 UE 所处的网络位置信息， 如 cell ID; 如果 UE未在该 emergency setup 消息中提供网络位置信息，如 cell ID, eMSC通过 LCS消息向 LCS 询问用户的位置信息； 如果 UE在 emergency setup消息中提供了 UE的位置信息， 那么 eMSC也可以寻求 LCS来证实位置信息。
本发明实施例提出了在演进网络中借助 eMSC 实体来完成模 拟电路域紧急呼叫的方法， 使得在不依赖于 IMS 情况下实现 SAE/LTE分组网络中的紧急呼叫业务。
如图 15所示， 为本发明实施例紧急呼叫服务实体结构图， 其 中， 该紧急呼叫服务实体为 eMSC或 IMS中的 p - CSCF。 该紧急 呼叫服务实体包括紧急附着处理模块 1 ,承载建立信息获取模块 2 , 承载信息下发模块 3 ,承载建立通知模块 4和承载关联控制模块 5。 紧急附着处理模块 1用于接受用户设备 UE的紧急附着， 其中， 该 紧急呼叫服务实体为所述 UE接入的移动性管理实体 MME为所述 UE选择的本地紧急呼叫服务实体； 承载建立信息获取模块 2用于 在所述 UE发起的紧急呼叫后， 获取为所述 UE建立紧急语音承载 所需的承载建立信息； 承载信息下发模块 3 用于将所述承载建立 信息分别下发给演进媒体网关 eMGW和策略计费规则功能 PCRF; 载建立通知模块 4用于通知 eMGW和 PCRF建立相应的 eMGW 侧紧急语音承载和 SAE侧紧急语音承载； 承载关联控制模块 5用 于在所述 eMGW侧 7|载和 PCRF侧 载建立后， 控制所述 eMGW 使所述 eMGW侧紧急语音承载和 SAE侧紧急语音承载关联，所述 UE根据关联的所述 eMGW侧紧急语音承载和 SAE侧紧急语音承 载进行紧急呼叫。
其中，承载建立信息获取模块 2包括 UE承载建立信息接收子 模块 21和承载参数获取子模块 22, UE承载建立信息接收子模块 21用于接收 UE通过紧急呼叫服务实体与 UE之间的 IP通道或通 过所述 MME与所述紧急呼叫服务实体间的接口发送的 UE承载建 立信息； 承载参数获取子模块 22用于向紧急呼叫中心请求相关承 载参数。
其中， 该紧急呼叫服务实体还包括释放模块 6, 用于在接收所 述紧急呼叫中心或所述 UE的释放消息后， 释放相应的 eMGW侧 紧急语音承载和 SAE侧紧急语音承载。
其中， 该紧急呼叫服务实体还包括位置信息确定模块 7, 用于 根据所述 UE上报的位置信息通过定位业务 LCS确定所述 UE的具 体位置。
本发明实施例提出了一种紧急呼叫服务实体， 通过上述紧急 呼叫服务实体能够在演进网络中完成模拟电路域的紧急呼叫， 使 得能够实现 S AE/LTE分组网络中的紧急呼叫业务。 通过以上的实施方式的描述，本领域的技术人员可以清楚地了解 到本发明可以通过硬件实现，也可以可借助软件加必要的通用硬件平 台的方式来实现基于这样的理解，本发明的技术方案可以以软件产品 的形式体现出来， 该软件产品可以存储在一个非易失性存储介质（可 以是 CD-ROM, U盘， 移动硬盘等） 中， 包括若干指令用以使得一 台计算机设备（可以是个人计算机， 服务器， 或者网络设备等）执行 本发明各个实施例所述的方法。
总之， 以上所述仅为本发明的较佳实施例而已， 并非用于限定本 发明的保护范围。 凡在本发明的精神和原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权利要求
1、 一种紧急呼叫方法， 其特征在于， 具体包括：
用户设备 UE向演进网络 SAE网络发起紧急附着请求， 所述 紧急附着请求包含紧急指示；
所述 SAE网络收到所述紧急指示后， 为所述 UE选择紧急呼 叫服务实体；
所述 UE紧急附着至所述 SAE网络后， 向所述紧急呼叫服务 实体发送所述紧急呼叫请求；
所述紧急呼叫服务实体建立紧急语音承载，所述 U E根据所述 建立的紧急语音承载进行紧急呼叫。
2、如权利要求 1所述紧急呼叫方法，其特征在于，在所述 SAE 网络为所述 UE选择紧急呼叫服务实体之后， 还包括：
所述 SAE网络在响应 UE的消息中携带所述紧急呼叫服务实 体信息。
3、 如权利要求 1所述紧急呼叫方法， 其特征在于， 所述用户 设备 UE向演进网络 SAE网络发起紧急附着请求， 所述紧急附着 请求包含紧急指示， 具体为：
当所述 UE检测到用户正在发起紧急呼叫时，所述 UE向 SAE 网络发送非接入层 NAS消息，所述 NAS消息携带有紧急指示和所 述用户的唯一标识。
4、 如权利要求 3所述的紧急呼叫方法， 其特征在于， 还包括： 在收到所述 NAS消息之后，根据所述 NAS消息为所述 UE选 择本地分组数据网络网关 PDN-GW, 所述 PDN-GW为所述 UE分 配相应的 IP地址， 使所述 UE附着至所述 SAE网络。
5、 如权利要求 3所述紧急呼叫方法， 其特征在于， 所述 NAS 消息包括 attach request消息、 service request消息或 Tracking Area Updating消息。
6、如权利要求 4所述紧急呼叫方法， 其特征在于， 所述为 UE 选择本地 PDN-GW具体为：
移动性管理实体 MME根据 NAS消息携带的紧急指示，使用如 下方法为 UE选择一个本地的 PDN-GW:
本地已经配置的静态 PDN-GW选择功能；
或，结合本地配置的紧急 APN以及本地的静态 PDN-GW选择 功能。
7、 如权利要求 1所述紧急呼叫方法， 其特征在于， 所述紧急 呼叫服务实体建立紧急语音承载具体为：
所述紧急呼叫服务实体获取为所述 UE 建立紧急语音承载所 需的承载建立信息；
所述紧急呼叫服务实体将所述承载建立信息分别下发给演进 媒体网关 eMGW和策略计费规则功能 PCRF来建立相应紧急语音 承载；
在相应的紧急语音承载建立后， 所述紧急呼叫服务实体控制 所述 eMGW使所述紧急呼叫服务实体侧紧急语音承载和 SAE侧紧 急语音承载关联。
8、 如权利要求 7所述紧急呼叫方法， 其特征在于， 所述紧急 呼叫服务实体获取为所述 UE 建立紧急语音承载所需的承载建立 信息， 具体为：
所述紧急呼叫服务实体接收所述 UE发送的 UE的承载建立信 息； 或者，
所述紧急呼叫服务实体向紧急呼叫中心请求相关承载参数。
9、 如权利要求 7所述紧急呼叫方法， 其特征在于， 所述紧急 呼叫服务实体接收所述 UE发送的 UE的承载建立信息具体为： 所述 UE通过所述紧急呼叫服务实体与所述 UE之间的 IP通 道或通过所述 MME 与所述紧急呼叫服务实体间的接口向所述紧 急呼叫服务实体发送 UE的承载建立信息。
10、 如权利要求 9 所述紧急呼叫方法， 其特征在于， 所述紧 急呼叫服务实体与所述 UE之间的 IP通道通过下述步骤建立， 在为所述 UE选择本地 PDN-GW之后，所述 PDN-GW为所述 UE分配相应的 IP地址；
在为所述 UE选择本地紧急呼叫服务实体之后，将选择的紧急 呼叫服务实体的 IP地址通知所述 UE,建立所述紧急呼叫服务实体 与所述 UE之间的 IP通道。
11、 如权利要求 9所述紧急呼叫方法， 其特征在于， 所述 UE 通过所述 MME 与所述紧急呼叫服务实体间的接口向所述紧急呼 叫服务实体发送 UE的承载建立信息具体为：
所述 UE在向所述 MME发送的 NAS消息中增加 IE, 所述 IE 用于指示所述 MME将所述 NAS消息中的 UE的承载建立信息发 送给所述紧急呼叫服务实体。
12、 如权利要求 7 所述紧急呼叫方法， 其特征在于， 所述紧 急呼叫服务实体将所述承载建立信息分别下发给 eMGW和 PCRF, 并通知所述 eMGW和所述 PCRF建立相应的紧急呼叫服务实体侧 紧急语音承载和 SAE侧紧急语音承载具体为：
所述紧急呼叫服务实体将获取的所述承载建立信息下发给所 述 UE;
由所述 UE根据接收到的所述承载建立信息请求所述 PCRF建 立相应的 SAE侧紧急语音 7 载；
所述紧急呼叫服务实体将所述承载建立信息发送给所述 eMGW, 通知所述 eMGW建立所述紧急呼叫服务实体侧紧急语音 承载。
13、 如权利要求 12所述紧急呼叫方法， 其特征在于， 所述紧 急呼叫服务实体通知所述 eMGW和所述 PCRF建立相应的紧急呼 叫服务实体侧紧急语音承载和 SAE侧紧急语音承载具体为：
所述紧急呼叫服务实体向所述 eMGW和所述 PCRF发送建立 承载信息， 在所述建立承载信息中包含有紧急标识。
14、如权利要求 12所述紧急呼叫方法， 其特征在于， 所述 UE 根据请求所述 PCRF建立相应的 SAE侧紧急语音承载具体为： 所述 UE向所述 PCRF发送建立承载信息，在所述建立承载信 息中包含有紧急标识。
15、 如权利要求 8所述紧急呼叫方法， 其特征在于， 还包括： 在所述紧急呼叫服务实体接收所述 UE发送的 UE的承载建立信息 中还包括所述 UE的位置信息；
所述紧急呼叫服务实体根据所述位置信息通过定位业务 LCS 确定所述 UE的具体位置。
16、 如权利要求 1 所述紧急呼叫方法， 其特征在于， 在所述 eMSC接受 UE的紧急附着之前， 对于非 3GPP网络， 还包括： 通过 EAP鉴权过程或 L3 Attach Trigger过程将紧急标识发送 给 AAA代理、 AAA服务器及本地 PDG GW, 所述本地 PDG GW 为所述 UE分配相应的 IP。
17、 如权利要求 1 所述紧急呼叫方法， 其特征在于， 所述紧 急呼叫服务实体为 eMSC或 IMS中的 p - CSCF或其它的紧急呼叫 网元实体。
18、 一种紧急呼叫释放方法， 其特征在于， 包括：
紧急呼叫服务实体接收 UE 或紧急呼叫中心发送的相关释放 消息；
根据所述相关释放消息， 所述紧急呼叫服务实体释放相关的 紧急语音承载资源。
19、 如权利要求 18所述的紧急呼叫释放方法， 其特征在于， 所述相关释放信息为断开连接 Disconnect 消息或释放 Release 消 息。
20、 如权利要求 19所述的紧急呼叫释放方法， 其特征在于， 所述紧急呼叫服务实体接收 UE 或紧急呼叫中心发送的相关释放 消息， 具体为：
所述紧急呼叫服务实体接收所述 UE发送的 Disconnect消息， 并根据所述 Disconnect消息向所述紧急呼叫中心发送释放 Release 消息； 或，
所述紧急呼叫服务实体接收所述紧急呼叫中心发送的 Release 消息， 并根据所述释放消息， 向 UE发送 Disconnect消息。
21、如权利要求 18-20任一项所述的紧急呼叫释放方法， 其特 征在于， 所述 UE通过 IP通道发送 /接收所述相关释放消息，
或， 所述 UE通过 NAS层由 MME转发所述相关释放消息。
22、 如权利要求 18所述紧急呼叫释放方法， 其特征在于， 所 述紧急呼叫服务实体释放相关的紧急语音承载资源之后， 还包括，
MME恢复其他暂停的专有承载。
23、 一种紧急附着方法， 其特征在于， 具体包括：
当所述 UE检测到用户正在发起紧急呼叫时，所述 UE向 SAE 网络发起 NAS消息，所述 NAS消息携带有紧急指示和所述用户的 唯一标识；
在收到所述 NAS消息之后，根据所述 NAS消息为所述 UE选 择本地分组数据网络网关 PDN-GW, 所述 PDN-GW为所述 UE分 配相应的 IP地址， 使所述 UE附着至所述 SAE网络。
24、如权利要求 23所述紧急附着方法，其特征在于，所述 NAS 消息包括 attach request消息、 service request消息或 Tracking Area Updating消息。
25、 如权利要求 23所述紧急附着方法， 其特征在于， 所述为 UE选择本地 PDN-GW具体为：
MME根据 NAS 消息携带的紧急指示， 使用如下方法为 UE 选择一个本地的 PDN-GW:
本地已经配置的静态 PDN-GW选择功能；
或，结合本地配置的紧急 APN以及本地的静态 PDN-GW选择 功能。
26、 一种紧急呼叫服务实体， 其特征在于， 包括紧急附着处 理模块， 承载建立信息获取模块， 承载信息下发模块， 承载建立 通知模块和承载关联控制模块， 所述紧急附着处理模块， 用于接受用户设备 UE的紧急附着； 所述承载建立信息获取模块，用于在所述 UE发起的紧急呼叫 后， 获取为所述 UE建立紧急语音承载所需的承载建立信息；
所述承载信息下发模块， 用于将所述承载建立信息分别下发 给媒体网关和策略计费规则功能 PCRF;
所述 7 载建立通知模块，用于通知媒体网关和 PCRF建立相应 的紧急呼叫服务实体侧紧急语音承载和 SAE侧紧急语音承载； 所述承载关联控制模块， 用于在所述紧急呼叫服务实体侧承 载和 PCRF侧承载建立后，所述媒体网关使所述紧急呼叫服务实体 侧紧急语音承载和 SAE侧紧急语音承载关联， 所述 UE根据关联 的所述紧急呼叫服务实体侧紧急语音承载和 SAE侧紧急语音承载 进行紧急呼叫。
27、 如权利要求 26所述紧急呼叫服务实体， 其特征在于， 所 述紧急呼叫服务实体为 eMSC或 IMS中的 p - CSCF。
28、 如权利要求 26所述紧急呼叫服务实体， 其特征在于， 所 述承载建立信息获取模块包括 UE承载建立信息接收子模块和承 载参数获取子模块，
所述 UE承载建立信息接收子模块， 用于接收所述 UE通过所 述 eMSC与所述 UE之间的 IP通道或通过所述 MME与所述 eMSC 间的接口发送的 UE承载建立信息；
所述承载参数获取子模块， 用于向紧急呼叫中心请求相关承 载参数。
29、 如权利要求 26所述紧急呼叫服务实体， 其特征在于， 还 包括释放模块，用于在接收所述紧急呼叫中心或所述 UE的释放消 息后，释放相应的 eMGW侧紧急语音承载和 SAE侧紧急语音承载。
30、 如权利要求 26 - 29任一项所述紧急呼叫服务实体， 其特 征在于， 还包括位置信息确定模块， 用于根据所述 UE上报的位置 信息通过定位业务 LCS确定所述 UE的具体位置。
PCT/CN2008/073577 2007-12-18 2008-12-18 Procédé et appareil pour un appel d'urgence WO2009082936A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
BRPI0821355A BRPI0821355A8 (pt) 2007-12-18 2008-12-18 método e aparelho para implementar chamadas de emergência
CN2008801192641A CN101897205B (zh) 2007-12-18 2008-12-18 一种紧急呼叫方法和装置
US12/818,966 US20100255808A1 (en) 2007-12-18 2010-06-18 Method and apparatus for implementing emergency calls

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710301851XA CN101466083B (zh) 2007-12-18 2007-12-18 一种紧急呼叫方法和装置
CN200710301851.X 2007-12-18

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/818,966 Continuation US20100255808A1 (en) 2007-12-18 2010-06-18 Method and apparatus for implementing emergency calls

Publications (1)

Publication Number Publication Date
WO2009082936A1 true WO2009082936A1 (fr) 2009-07-09

Family

ID=40806387

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/073577 WO2009082936A1 (fr) 2007-12-18 2008-12-18 Procédé et appareil pour un appel d'urgence

Country Status (4)

Country Link
US (1) US20100255808A1 (zh)
CN (2) CN101466083B (zh)
BR (1) BRPI0821355A8 (zh)
WO (1) WO2009082936A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011039636A2 (en) 2009-10-02 2011-04-07 Research In Motion Limited System and method for determining establishment causes for emergency sessions
CN102256219A (zh) * 2010-05-21 2011-11-23 电信科学技术研究院 一种机器类通信中的优先告警消息的传输方法及设备
US8625506B2 (en) 2009-01-15 2014-01-07 Blackberry Limited System and method for determining establishment causes
CN109981524A (zh) * 2017-12-27 2019-07-05 中国移动通信集团河北有限公司 用户号码分区接入方法、装置、设备及介质

Families Citing this family (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9019953B2 (en) * 2006-06-30 2015-04-28 Telefonaktiebolaget L M Ericsson (Publ) Network node, method, and mobile terminal for providing voice calls to a mobile terminal in a packet-switched-only network
CN102396249B (zh) 2009-04-17 2015-07-29 日本电气株式会社 移动通信系统、基站、网关装置、核心网络装置以及通信方法
CN101938727B (zh) * 2009-06-30 2015-06-03 中兴通讯股份有限公司 一种实现紧急呼叫的方法及系统
CN101945365B (zh) * 2009-07-07 2014-12-10 中兴通讯股份有限公司 一种紧急会话切换的方法和系统
CN101959163A (zh) * 2009-07-17 2011-01-26 中兴通讯股份有限公司 一种实现紧急呼叫的方法
CN101959123A (zh) * 2009-07-20 2011-01-26 中兴通讯股份有限公司 一种建立承载的方法和系统
CN101998333B (zh) * 2009-08-17 2013-06-05 中兴通讯股份有限公司 紧急附着的处理方法和系统
US8375245B2 (en) * 2010-07-15 2013-02-12 Verizon Patent And Licensing Inc. Mobility management entity failover
JP4767357B1 (ja) 2010-07-30 2011-09-07 株式会社エヌ・ティ・ティ・ドコモ 呼び出し方法、コアネットワーク装置、無線アクセスネットワーク装置及びゲートウェイ装置
CN102821377B (zh) * 2011-06-10 2016-03-30 中国科学院计算技术研究所 构建应急通信系统的方法及应急通信系统
US8630607B2 (en) * 2011-07-15 2014-01-14 Verizon Patent And Licensing Inc. Emergency call handoff between heterogeneous networks
CN103024737B (zh) * 2011-09-23 2017-08-11 中兴通讯股份有限公司 可信任非3gpp接入网元、接入移动网络及去附着方法
KR20130048561A (ko) * 2011-11-02 2013-05-10 삼성전자주식회사 이동통신 시스템에서 응급 호에 대한 미디어 선호 정보 전송 방법 및 시스템
CN102438330A (zh) * 2011-12-06 2012-05-02 大唐移动通信设备有限公司 一种附着到e-tran的方法及移动性管理实体
JP5773074B2 (ja) * 2012-01-27 2015-09-02 日本電気株式会社 Ｍ２ｍにおけるプライバシー問題
CN102625475B (zh) * 2012-04-06 2015-11-25 电信科学技术研究院 一种pdn连接的删除方法和设备
US9516176B2 (en) * 2012-05-31 2016-12-06 At&T Intellectual Property I, L.P. Long term evolution network billing management
CN107659908B (zh) 2012-07-18 2021-06-22 华为技术有限公司 一种数据连接管理的方法、装置及系统
WO2014106341A1 (zh) * 2013-01-06 2014-07-10 华为技术有限公司 一种资源分配方法和装置
WO2014109797A1 (en) * 2013-01-14 2014-07-17 Intel IP Corporation Energy-harvesting devices in wireless networks
KR102179048B1 (ko) 2013-11-08 2020-11-16 삼성전자 주식회사 패킷망을 통한 응급 콜 서비스를 지속적으로 제공하기 위한 방법
WO2015069076A1 (ko) * 2013-11-08 2015-05-14 삼성전자 주식회사 패킷망을 통한 응급 콜 서비스를 지속적으로 제공하기 위한 방법
CN104754551B (zh) * 2013-12-31 2019-03-29 中国移动通信集团公司 一种用户终端的语音流量路由优化方法及设备
US9807655B2 (en) * 2014-02-14 2017-10-31 Telefonaktiebolaget Lm Ericsson (Publ) PCRF assisted APN selection
US10154123B2 (en) 2014-04-28 2018-12-11 T-Mobile Usa, Inc. Insertion and use of application or radio information in network data packet headers
EP3678414B1 (en) * 2014-06-17 2021-08-25 Huawei Technologies Co., Ltd. Mme reselection method and mme
EP3148252B1 (en) * 2014-06-30 2018-12-12 Huawei Technologies Co. Ltd. Voice service switching method and device in single radio voice call continuity
EP3866500A1 (en) 2015-04-01 2021-08-18 Telefonaktiebolaget LM Ericsson (publ) Ims emergency calls for roaming ues
CN104918283B (zh) * 2015-05-21 2018-07-24 大唐移动通信设备有限公司 一种拥塞控制方法及设备
US9538351B1 (en) * 2015-08-12 2017-01-03 Verizon Patent And Licensing Inc. Supporting unprovisioned emergency phone calls using voice over wireless local area network
EP3166351A1 (en) * 2015-11-05 2017-05-10 Alcatel Lucent Support of emergency services over wlan access to 3gpp evolved packet core for unauthenticated users
CN108432336B (zh) 2015-12-28 2020-11-17 华为技术有限公司 一种pdn连接的释放方法、装置及用户设备
WO2017127673A1 (en) 2016-01-22 2017-07-27 Blackberry Limited Access point name determination for mission critical services
DE112017002504T5 (de) 2016-05-16 2019-03-07 Apple Inc. Notdienstunterstützung für drahtlosen Nichtmobilfunkzugang
CN109661853B (zh) * 2016-09-07 2020-12-08 华为技术有限公司 本地分组数据网络的动态创建方法、装置及系统
EP3574623B1 (en) * 2017-01-30 2022-05-04 Telefonaktiebolaget LM Ericsson (Publ) Methods and devices for parameter exchange during emergency access
CN109819440B (zh) * 2017-11-20 2022-08-26 华为技术有限公司 鉴权的方法和装置
EP3503635A1 (en) * 2017-12-22 2019-06-26 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Emergency notification (urllc) requesting spontaneous grant free transmission for v2x
US20190364412A1 (en) * 2018-05-25 2019-11-28 Mediatek Inc. Apparatus and method for pdu session establishment restriction in emergency registration
CN111328062A (zh) * 2018-12-14 2020-06-23 中国移动通信集团河南有限公司 一种VoLTE紧急电话的接通方法和装置
CN110602663B (zh) * 2019-07-31 2021-07-20 华为技术有限公司 语音呼叫方法、装置及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001080587A1 (en) * 2000-04-15 2001-10-25 Telefonaktiebolaget Lm Ericsson (Publ) System and method for emergency call handling in a mobile packet switched network
WO2006078212A1 (en) * 2005-01-19 2006-07-27 Telefonaktiebolaget Lm Ericsson (Publ) A method and apparatus for handling emergency calls in a packet switched radio access network
CN1933656A (zh) * 2005-09-16 2007-03-21 中兴通讯股份有限公司 宽带码分多址系统中的紧急呼叫处理方法
CN1984441A (zh) * 2006-06-12 2007-06-20 华为技术有限公司 一种实现紧急呼叫的系统及方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8072948B2 (en) * 2005-07-14 2011-12-06 Interdigital Technology Corporation Wireless communication system and method of implementing an evolved system attachment procedure
US8532606B2 (en) * 2005-10-07 2013-09-10 Lg Electronics Inc. Method and system for providing an emergency location service using interoperability between IMS core and access network
CN101047958B (zh) * 2006-03-31 2011-01-05 华为技术有限公司 3gpp演进网络中漫游场景下用户网络附着方法及系统
US8447302B2 (en) * 2006-04-26 2013-05-21 Telefonaktiebolaget Lm Ericsson (Publ) Network initiated mobility management for mobile terminals

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001080587A1 (en) * 2000-04-15 2001-10-25 Telefonaktiebolaget Lm Ericsson (Publ) System and method for emergency call handling in a mobile packet switched network
WO2006078212A1 (en) * 2005-01-19 2006-07-27 Telefonaktiebolaget Lm Ericsson (Publ) A method and apparatus for handling emergency calls in a packet switched radio access network
CN1933656A (zh) * 2005-09-16 2007-03-21 中兴通讯股份有限公司 宽带码分多址系统中的紧急呼叫处理方法
CN1984441A (zh) * 2006-06-12 2007-06-20 华为技术有限公司 一种实现紧急呼叫的系统及方法

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8625506B2 (en) 2009-01-15 2014-01-07 Blackberry Limited System and method for determining establishment causes
US9125182B2 (en) 2009-10-02 2015-09-01 Blackberry Limited System and method for determining establishment causes for emergency sessions
US9820125B2 (en) 2009-10-02 2017-11-14 Blackberry Limited System and method for determining establishment causes for emergency sessions
WO2011039636A3 (en) * 2009-10-02 2011-05-26 Research In Motion Limited Determining establishment causes for emergency sessions
AU2010302349B2 (en) * 2009-10-02 2014-07-17 Blackberry Limited Determining establishment causes for emergency sessions
KR101464417B1 (ko) * 2009-10-02 2014-11-21 블랙베리 리미티드 비상 세션을 위한 구축 원인을 결정하는 시스템 및 방법
WO2011039636A2 (en) 2009-10-02 2011-04-07 Research In Motion Limited System and method for determining establishment causes for emergency sessions
US9538353B2 (en) 2009-10-02 2017-01-03 Blackberry Limited System and method for determining establishment causes for emergency sessions
US11310288B2 (en) 2009-10-02 2022-04-19 Blackberry Limited System and method for determining establishment causes for emergency sessions
EP3952362A1 (en) * 2009-10-02 2022-02-09 BlackBerry Limited Method, user equipment and non-transitory computer-readable medium for determining establishment causes for emergency sessions
US10542051B2 (en) 2009-10-02 2020-01-21 Blackberry Limited System and method for determining establishment causes for emergency sessions
EP3606114A1 (en) * 2009-10-02 2020-02-05 BlackBerry Limited System and method for determining establishment causes for emergency sessions
CN102256219A (zh) * 2010-05-21 2011-11-23 电信科学技术研究院 一种机器类通信中的优先告警消息的传输方法及设备
CN109981524B (zh) * 2017-12-27 2021-06-04 中国移动通信集团河北有限公司 用户号码分区接入方法、装置、设备及介质
CN109981524A (zh) * 2017-12-27 2019-07-05 中国移动通信集团河北有限公司 用户号码分区接入方法、装置、设备及介质

Also Published As

Publication number Publication date
CN101466083A (zh) 2009-06-24
CN101897205A (zh) 2010-11-24
BRPI0821355A8 (pt) 2019-01-02
CN101466083B (zh) 2010-12-08
BRPI0821355A2 (pt) 2015-06-16
US20100255808A1 (en) 2010-10-07
CN101897205B (zh) 2012-11-21

Similar Documents

Publication Publication Date Title
WO2009082936A1 (fr) Procédé et appareil pour un appel d'urgence
AU2020244393B2 (en) Network handover method, apparatus and system
EP4064770A1 (en) Wireless device paging by a wireless network
AU2020256408C1 (en) Session context conversion
JP5536954B2 (ja) 回路交換ドメインからパケット交換ドメインへのハンドオーバー方法、装置、および通信システム
US8817751B2 (en) Method, device and system of handover
EP3104660B1 (en) Method, apparatus and system for routing user plane data in mobile network
WO2019011107A1 (zh) 网络切换方法及装置
WO2009132533A1 (zh) 资源处理的方法、通信系统和移动性管理网元
WO2009097818A1 (zh) 一种用户设备紧急接入的方法、设备和系统
WO2009024089A1 (fr) Système servant à mettre en place une compatibilité arrière avec un réseau, procédé de liaison et procédé de séparation
WO2009121255A1 (zh) 承载挂起的方法、承载恢复的方法及网关代理
WO2011023090A1 (zh) 家庭基站接入场景下寻呼的处理方法和装置
WO2013010415A1 (zh) 一种实现ip地址属性通知的方法、系统和sgw
WO2012097706A1 (zh) 一种承载修改的系统及方法
US20130010751A1 (en) Method and Device For Handling Handover of a Communications Service
WO2009031003A2 (en) Dynamic ggsn relocation in a gprs network
WO2009026835A1 (fr) Système, appareil et procédé pour un transfert de service d'utilisateur
WO2016107404A1 (zh) 业务流传输路径优化方法、装置及mme
WO2010069272A1 (zh) 一种网络切换的资源处理方法及装置
WO2012024989A1 (zh) 承载释放方法及系统
WO2009149656A1 (zh) 一种实现业务切换的方法、装置及系统
WO2009097779A1 (zh) 一种接入sae核心网的方法、系统及装置
WO2016019559A1 (zh) 共享网络的用户设备识别装置、系统及方法
WO2011150649A1 (zh) 分组数据网关重分配的方法和装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200880119264.1

Country of ref document: CN

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

Ref document number: 08867173

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: 08867173

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: PI0821355

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20100618