WO2019027538A1 - Élément de réseau permettant un appel d'urgence amélioré par sms - Google Patents

Élément de réseau permettant un appel d'urgence amélioré par sms Download PDF

Info

Publication number
WO2019027538A1
WO2019027538A1 PCT/US2018/033906 US2018033906W WO2019027538A1 WO 2019027538 A1 WO2019027538 A1 WO 2019027538A1 US 2018033906 W US2018033906 W US 2018033906W WO 2019027538 A1 WO2019027538 A1 WO 2019027538A1
Authority
WO
WIPO (PCT)
Prior art keywords
emergency
message
sms message
emergency call
network element
Prior art date
Application number
PCT/US2018/033906
Other languages
English (en)
Inventor
Vashishth Jhunjhunwala
Hargovind Prasad BANSAL
Stephen William Edge
Original Assignee
Qualcomm Incorporated
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 Qualcomm Incorporated filed Critical Qualcomm Incorporated
Publication of WO2019027538A1 publication Critical patent/WO2019027538A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/402—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel non-real time sessions, e.g. downloading a file in a parallel FTP session, initiating an email or combinational services
    • H04L65/4025—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel non-real time sessions, e.g. downloading a file in a parallel FTP session, initiating an email or combinational services where none of the additional parallel sessions is real time or time sensitive, e.g. downloading a file in a parallel FTP session, initiating an email or combinational services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • 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

  • a voice channel may be established between a user equipment (UE) (such as a mobile phone) and a public safety answering point (PSAP), enabling a user of the UE to speak with an emergency services operator. Due to network or other issues, however, the call may not be established.
  • GSM Global System for Mobile communication
  • UMTS Universal Mobile Telecommunications Service
  • LTE Long Term Evolution
  • RATs radio access technologies
  • a UE capable of establishing an emergency call using multiple RATs may then try one RAT and/or one network after another until an emergency call is successfully established. But this may take a long time - e.g. when the UE resorts to using WiFi (which may take 20-40 seconds to establish an emergency call). Delays in establishing the emergency call may be extremely undesirable in some emergency situations and may even lead to a user abandoning the emergency call attempt before the call succeeds.
  • Techniques described herein enable a network element of a serving network different than a home network of a user equipment (UE) to route an emergency-related short message service (SMS) message from the UE to a public safety answering point (PSAP) during an emergency situation.
  • SMS short message service
  • PSAP public safety answering point
  • Techniques can involve receiving an emergency call request and SMS message from the UE, determining a destination address for the SMS message based on an emergency indication, and routing the SMS message to the PSAP based on the destination address, wherethe routing bypasses the home network.
  • An example method of initiating an emergency call at a user equipment (UE) on a behalf of a user comprises detecting, with the UE, an emergency condition, initiating, based on the emergency condition, the emergency call to a public safety answering point (PSAP) using a certain radio access type, detecting a trigger condition, and sending, based on the trigger condition, an emergency-related short message service (SMS) message to the PSAP via a serving network different than a home network of the UE, wherein the sending bypasses the home network.
  • PSAP public safety answering point
  • SMS emergency-related short message service
  • the example method may include one or more of the following features.
  • the emergency condition may comprise an automatically-detected emergency condition.
  • the automatically-detected emergency condition may comprise a medical condition of the user, an indication of an accident involving the user, or an indication of an imminent danger to the user, or any combination thereof.
  • the trigger condition further may comprise the emergency condition, a failure to establish the emergency call using the certain radio access type, a delay in establishing the emergency call exceeding a certain threshold of time, or a quality of the certain radio access type being below a certain threshold of quality, or any combination thereof.
  • the emergency-related SMS message may comprise an emergency indication, a location of the UE, information regarding the user, or information regarding the emergency condition, or any combination thereof.
  • the emergency-related SMS message may comprise a uniform resource locator (URL) that enables the PSAP to access data regarding the user.
  • URL uniform resource locator
  • Sending the emergency-related SMS message to the PSAP further may comprise sending the emergency-related SMS message to an IP Multimedia Subsystem (IMS) in the serving network using a session initiation protocol (SIP).
  • the method further may comprise sending an updated emergency-related SMS message to the PSAP based on a subsequently detected change in a location of the UE, change in information regarding the user, or change in information regarding the emergency condition, or any combination thereof.
  • An example method of routing emergency-related short message service (SMS) messages at a network element of a serving network different than a home network of a user equipment (UE), may comprise receiving a request for an emergency call from the UE, receiving an SMS message from the UE, the SMS message comprising an emergency indication, determining, based on the emergency indication, a destination address for the SMS message, and routing the SMS message towards a public safety answering point (PSAP) based on the destination address, wherein the routing bypasses the home network.
  • PSAP public safety answering point
  • the example method may include one or more of the following features.
  • the emergency indication may comprise an association of the SMS message with the emergency call.
  • the association with the emergency call may comprise use of the same IP address by the UE for both the emergency call and the SMS message, use of the same emergency packet data network connection by the UE for both the emergency call and the SMS message, or use of the same identification of the UE for both the emergency call and the SMS message, or any combination thereof.
  • the method may further comprise sending the SMS message towards the PSAP based on the routing.
  • the network element may be part of an IP Multimedia Subsystem (IMS) in the serving network.
  • the network element may comprise a Proxy Call Session Control Function (P- CSCF) or an Emergency Call Session Control Function (E-CSCF).
  • the request for the emergency call may comprise a Session Initiation Protocol (SIP) REGISTER message or a SIP INVITE message.
  • the SMS message may be received in a SIP MESSAGE.
  • the association of the SMS message with the emergency call may comprise a first IP address for the UE in a SIP Contact header for the SIP REGISTER message or SIP INVITE message and a second IP address for the UE in a SIP Contact header for the SIP MESSAGE, where the first IP address is the same as the second IP address.
  • An example user equipment comprises a wireless communication interface, a memory, and a processing unit communicatively coupled with the wireless communication interface and memory, and configured to cause the UE to detect an emergency condition, initiate, based on the emergency condition, an emergency call to a public safety answering point (PSAP) using a certain radio access type, detect a trigger condition, and send, based on the trigger condition, an emergency-related short message service (SMS) message to the PSAP.
  • PSAP public safety answering point
  • SMS emergency-related short message service
  • the emergency- related SMS message is sent, using the wireless communication interface, via a serving network different than a home network of the UE, bypassing the home network of the UE.
  • the user equipment may comprise one or more of the following features.
  • the user equipment may comprise one or more sensors, wherein the processing unit is configured to cause the UE to detect an emergency condition using data from the one or more sensors.
  • the one or more sensors may be configured to detect a medical condition of a user, an indication of an accident involving the user, or an indication of an imminent danger to the user, or any combination thereof.
  • the processing unit may be configured to cause the UE to detect the trigger condition by detecting the emergency condition, a failure to establish the emergency call using the certain radio access type, a delay in establishing the emergency call exceeding a certain threshold of time, or a quality of the certain radio access type being below a certain threshold of quality, or any combination thereof.
  • the processing unit may be configured to cause the UE to include, in the emergency-related SMS message, an emergency indication, a location of the UE, information regarding a user, or information regarding the emergency condition, or any combination thereof.
  • the processing unit may be configured to cause the UE to include, in the emergency -related SMS message, a uniform resource locator (URL) that enables the PSAP to access data regarding a user.
  • the processing unit may be configured to cause the UE to send the emergency -related SMS message to an IP Multimedia Subsystem (IMS) in the serving network using a session initiation protocol (SIP).
  • IMS IP Multimedia Subsystem
  • SIP session initiation protocol
  • the processing unit may be further configured to cause the UE to send an updated emergency-related SMS message to the PSAP based on a subsequently detected change in a location of the UE, change in information regarding a user, or change in information regarding the emergency condition, or any combination thereof.
  • An example network element comprises a communications interface configured to enable the network element to compose part of a serving network, a memory, and a processing unit communicatively coupled with the communications interface and the memory, and configured to cause the network element to receive a request for an emergency call from a user equipment (UE) having a home network different than the serving network, receive an short message service (SMS) message from the UE, the SMS message comprising an emergency indication, determine, based on the emergency indication, a destination address for the SMS message, and route the SMS message towards a public safety answering point (PSAP) based on the destination address, where the routing bypasses the home network of the UE.
  • SMS short message service
  • the network element may comprise one or more of the following features.
  • the processing unit may be further configured to cause the network element to determine, from the SMS message, an association of the SMS message with the emergency call.
  • the processing unit may be configured to cause the network element to determine the association of the SMS message with the emergency call by determining use of the same IP address by the UE for both the emergency call and the SMS message, use of the same emergency packet data network connection by the UE for both the emergency call and the SMS message, or use of the same identification of the UE for both the emergency call and the SMS message, or any combination thereof.
  • the processing unit may be configured to cause the network element to send the SMS message towards the PSAP based on the routing.
  • the network element may be configured to compose part of an IP Multimedia Subsystem (IMS) in the serving network.
  • IMS IP Multimedia Subsystem
  • P-CSCF P-CSCF
  • E-CSCF Emergency Call Session Control Function
  • the processing unit may be configured to cause the network element to receive the request for the emergency call by receiving a Session Initiation Protocol (SIP)
  • SIP Session Initiation Protocol
  • the processing unit may be configured to cause the network element to receive the SMS message in a SIP MESSAGE.
  • the processing unit may be configured to cause the network element to determine the association of the SMS message with the emergency call by determining a first IP address for the UE in a SIP Contact header for the SIP REGISTER message or SIP INVITE message is the same as a second IP address for the UE in a SIP Contact header for the SIP MESSAGE.
  • An example mobile device comprises means for detecting, with the mobile device, an emergency condition, means for initiating, based on the emergency condition, an emergency call to a public safety answering point (PSAP) using a certain radio access type, means for detecting a trigger condition, and means for sending, based on the trigger condition, an emergency -related short message service (SMS) message to the PSAP via a serving network different than a home network of the mobile device, wherein the sending bypasses the home network.
  • PSAP public safety answering point
  • SMS short message service
  • the example mobile device may include one or more of the following features.
  • the means for detecting an emergency condition may comprise means for automatically detecting the emergency condition.
  • the means for automatically detecting the emergency condition may comprise means for detecting a medical condition of a user, an indication of an accident involving the user, or an indication of an imminent danger to the user, or any combination thereof.
  • the means for detecting the trigger condition further may comprise means for detecting the emergency condition, a failure to establish the emergency call using the certain radio access type, a delay in establishing the emergency call exceeding a certain threshold of time, or a quality of the certain radio access type being below a certain threshold of quality, or any combination thereof.
  • the means for sending the emergency-related SMS message may comprise means for including, in the emergency -related SMS message, an emergency indication, a location of the mobile device, information regarding a user, or information regarding the emergency condition, or any combination thereof.
  • the means for sending the emergency-related SMS message may comprise means for including, in the emergency- related SMS message, a uniform resource locator (URL) that enables the PSAP to access data regarding a user.
  • the means for sending the emergency-related SMS message to the PSAP may further comprise means for sending the emergency-related SMS message to an IP Multimedia Subsystem (IMS) in the serving network using a session initiation protocol (SIP).
  • IMS IP Multimedia Subsystem
  • SIP session initiation protocol
  • the mobile device may further comprise means for sending an updated emergency-related SMS message to the PSAP based on a subsequently detected change in a location of the mobile device, change in information regarding a user, or change in information regarding the emergency condition, or any combination thereof.
  • An example network element comprises means for receiving a request for an emergency call from a user equipment (UE) at the network element, wherein the network element composes part of a serving network different than a home network of the UE, means for receiving a short message service (SMS) message from the UE, the SMS message comprising an emergency indication, means for determining, based on the emergency indication, a destination address for the SMS message, and means for routing the SMS message towards a public safety answering point (PSAP) based on the destination address, wherein the routing bypasses the home network.
  • SMS short message service
  • the example network element may include one or more of the following features.
  • the network element may include means for determining, from the emergency indication, an association of the SMS message with the emergency call.
  • the means for determining the association with the emergency call may comprise means for determining use of the same IP address by the UE for both the emergency call and the SMS message, use of the same emergency packet data network connection by the UE for both the emergency call and the SMS message, or use of the same identification of the UE for both the emergency call and the SMS message, or any combination thereof.
  • the network element may include means for sending the SMS message towards the PSAP based on the routing.
  • the network element may be configured to compose part of an IP Multimedia Subsystem (IMS) in the serving network.
  • IMS IP Multimedia Subsystem
  • the network element may comprise a Proxy Call Session Control Function (P-CSCF) or an Emergency Call Session Control Function (E-CSCF).
  • the means for receiving the request for the emergency call may comprise means for receiving a Session Initiation Protocol (SIP) REGISTER message or a SIP INVITE message.
  • the means for receiving the SMS messages may comprise means for receiving the SMS message in a SIP MESSAGE.
  • the network element may further comprise means for determining the association of the SMS message with the emergency call by determining a first IP address for the UE in a SIP Contact header for the SIP REGISTER message or SIP INVITE message is the same as a second IP address for the UE in a SIP Contact header for the SIP MESSAGE.
  • An example non-transitory computer-readable medium has instructions embedded thereon for initiating an emergency call at a user equipment (UE) on behalf of a user.
  • the instructions include computer code for detecting an emergency condition, initiating, based on the emergency condition, the emergency call to a public safety answering point (PSAP) using a certain radio access type, detecting a trigger condition, and sending, based on the trigger condition, an emergency-related short message service (SMS) message to the PSAP via a serving network different than a home network of the UE, wherein the sending bypasses the home network.
  • PSAP public safety answering point
  • SMS emergency-related short message service
  • the example non-transitory computer-readable medium may include one or more of the following features.
  • the computer code for detecting an emergency condition may comprise computer code for automatically detecting the emergency condition.
  • the computer code for automatically detecting the emergency condition may comprise computer code for detecting a medical condition of the user, an indication of an accident involving the user, or an indication of an imminent danger to the user, or any combination thereof.
  • the computer code for detecting the trigger condition further comprise computer code for detecting the emergency condition, a failure to establish the emergency call using the certain radio access type, a delay in establishing the emergency call exceeding a certain threshold of time, or a quality of the certain radio access type being below a certain threshold of quality, or any combination thereof.
  • the computer code for sending the emergency-related SMS message may comprise computer code for including, in the emergency-related SMS message, an emergency indication, a location of the UE, information regarding the user, or information regarding the emergency condition, or any combination thereof.
  • the computer code for sending the emergency-related SMS message may comprise computer code for including, in the emergency-related SMS message, a uniform resource locator (URL) that enables the PSAP to access data regarding the user.
  • the computer code for sending the emergency-related SMS message to the PSAP further may comprise computer code for sending the emergency-related SMS message to an IP Multimedia Subsystem (IMS) in the serving network using a session initiation protocol (SIP).
  • IMS IP Multimedia Subsystem
  • SIP session initiation protocol
  • the instructions further may comprise computer code for sending an updated emergency-related SMS message to the PSAP based on a subsequently detected change in a location of the UE, change in information regarding the user, or change in information regarding the emergency condition, or any combination thereof.
  • An example non-transitory computer-readable medium has instructions embedded thereon for routing emergency -related short message service (SMS) messages at a network element of a serving network different than a home network of a user equipment (UE).
  • the instructions comprise computer code for receiving a request for an emergency call from the UE at the network element, receiving a short message service (SMS) message from the UE, the SMS message comprising an emergency indication, determining, based on the emergency indication, a destination address for the SMS message, and routing the SMS message towards a public safety answering point (PSAP) based on the destination address, wherein the routing bypasses the home network.
  • SMS short message service
  • PSAP public safety answering point
  • the example non-transitory computer-readable medium may include one or more the following features.
  • the instructions further comprise computer code for determining, from the emergency indication, an association of the SMS message with the emergency call.
  • the computer code for determining the association with the emergency call may comprises computer code for determining use of the same IP address by the UE for both the emergency call and the SMS message, use of the same emergency packet data network connection by the UE for both the emergency call and the SMS message, or use of the same identification of the UE for both the emergency call and the SMS message, or any combination thereof.
  • the instructions further may comprise computer code for sending the SMS message towards the PSAP based on the routing.
  • the instructions further comprise computer code for causing a computer to perform functions as part of an IP Multimedia Subsystem (IMS) in the serving network.
  • IMS IP Multimedia Subsystem
  • the instructions further may comprise computer code for performing one or more functions of a Proxy Call Session Control Function (P-CSCF) or an Emergency Call Session Control Function (E-CSCF).
  • the computer code for receiving the request for the emergency call may comprise computer code for receiving a Session Initiation Protocol (SIP) REGISTER message or a SIP INVITE message.
  • the computer code for receiving the SMS messages may comprise computer code for receiving the SMS message in a SIP MESSAGE.
  • the instructions further may comprise computer code for determining the association of the SMS message with the emergency call by
  • REGISTER message or SIP INVITE message is the same as a second IP address for the UE in a SIP Contact header for the SIP MESSAGE.
  • FIG. 1 is a simplified illustration of an embodiment of a communication system capable of transmitting an emergency short message service (SMS) message according to the techniques described herein.
  • SMS emergency short message service
  • FIG. 2 is a signaling flow diagram illustrating how an emergency SMS (ESMS) message can be communicated from a user equipment (UE) to a public safety answering point (PSAP) in conjunction with an emergency call, in an embodiment, for the communication system of FIG. 1.
  • FIG. 3 is a simplified illustration of a Long Term Evolution (LTE) communication system capable of transmitting an ESMS message according to the techniques described herein.
  • LTE Long Term Evolution
  • FIG. 4 is a signaling flow diagram illustrating how an ESMS message can be communicated from a user equipment (UE) to a public safety answering point (PSAP) in conjunction with an emergency call, in an embodiment, for the communication system of FIG. 3.
  • UE user equipment
  • PSAP public safety answering point
  • FIG. 5 is a flow diagram illustrating a method of initiating an emergency call at a UE, according to an embodiment.
  • FIG. 6 is a flow diagram illustrating a method 600 of routing an ESMS message, according to an embodiment.
  • FIG. 7 is a block diagram illustrating an embodiment of a UE, according to an embodiment.
  • FIG. 8 is a block diagram illustrating an embodiment of a computer system.
  • a voice channel may be established between a user equipment (UE) (such as a mobile phone) and a public safety answering point (PSAP), enabling a user of the UE to speak with an emergency services operator. Due to network or other issues, however, the call may not be established.
  • GSM Global System for Mobile communication
  • UMTS Universal Mobile Telecommunications Service
  • LTE Long Term Evolution
  • RATs radio access technologies
  • a UE capable of establishing an emergency call using multiple RATs may then try one RAT and/or one network after another until an emergency call is successfully established. But this may take a long time - e.g. when the UE resorts to using WiFi (which may take 20-40 seconds to establish an emergency call). Delays in establishing the emergency call may be extremely undesirable in urgent emergency situations and may even lead to a user abandoning the emergency call attempt before the call succeeds.
  • SMS short message service
  • the SMS message (also referred to herein as an "emergency-related SMS message,” “emergency SMS message,” “emergency SMS,” “ESMS,” or “ESMS message”) can include information that may be valuable to the PSAP, such as the location of the UE, the identity of the UE or user, a call back number for the UE, available medical and/or emergency data, other identification information, and the like. Further, the SMS message may be sent via a serving network, different than the UE's home network, in order to improve reliability and/or reduce delay in transferring the SMS message.
  • Sending an emergency SMS message in this manner may be advantageous for a variety of reasons, primarily due the fact that an emergency message provides another means on contacting a PSAP in situations where an emergency call may not be reliable (e.g. not successful or sucessful only after a long delay).
  • an emergency call requires a large number of procedures between various network components to establish a dedicated signaling and voice bearer and a session with a PSAP.
  • This requires the availability and assignment of resources (e.g. wireless bandwidth, bandwidth on wireline links and trunks) in the wireless network, in any intermediate networks and at the PSAP. In some situations, the resources may not be available at one or more entities.
  • an emergency call may be established with acceptable voice quality, but a user may be unable to speak (e.g. due to a severe medical condition or as the result of an accident).
  • An emergency SMS message is not session based, may not require a dedicated bearer or a continuously good wireless QoS and may not require voice interaction between a user and PSAP.
  • an emergency SMS message can be sent in a short burst of wireless signaling and does not require the availability of signaling and voice transfer over a long period. Additional details regarding these advantages are provided below.
  • the communication system 100 can include a UE 105, one or more space vehicles (SVs) 1 10, one or more base stations 120, one or more access points 130, a serving network 140, a location server 150, a home network 160, the Internet 170, and a PSAP 180.
  • SVs space vehicles
  • FIG. 1 provides only a generalized illustration of various components, any or all of which may be utilized as appropriate, and each of which may be duplicated (or absent) as necessary.
  • UE 105 is illustrated, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the communication system 100.
  • UEs e.g., hundreds, thousands, millions, etc.
  • the communication system 100 may include a larger or smaller number of base stations 120 and/or APs 130 than illustrated in FIG. 1.
  • the illustrated connections that connect the various components in the communication system 100 comprise data and signaling connections which may include additional (intermediary) components, direct or indirect physical and/or wireless connections, and/or additional networks.
  • components may be rearranged, combined, separated, substituted, and/or omitted, depending on desired functionality.
  • the location server 150 may be incorporated into the serving network 140.
  • RATs other than those shown in and described for FIG. 1 may be available to the UE 105 for communicating with the PSAP 180.
  • a person of ordinary skill in the art will recognize many modifications to the components illustrated.
  • the UE 105 may comprise and/or be referred to herein as a device, a mobile device, a wireless device, a mobile terminal, a terminal, a mobile station (MS), a Secure User Plane Location (SUPL) Enabled Terminal (SET), or by some other name.
  • a device a mobile device, a wireless device, a mobile terminal, a terminal, a mobile station (MS), a Secure User Plane Location (SUPL) Enabled Terminal (SET), or by some other name.
  • MS mobile station
  • SUPL Secure User Plane Location
  • SET Secured Terminal
  • UE 105 may correspond to a cellphone, smartphone, laptop, tablet, PDA, tracking device or some other portable or moveable device.
  • the UE 105 may support wireless communication such as using GSM, Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), LTE, High Rate Packet Data (HRPD), WiFi (also referred to as Wi-Fi), Bluetooth® (BT), Worldwide Interoperability for Microwave Access (WiMAX), etc.
  • the UE 105 may also support wireless communication using a Wireless Local Area Network (WLAN) which may connect to other networks (e.g. the Internet 170) using a Digital Subscriber Line (DSL) or packet cable for example.
  • WLAN Wireless Local Area Network
  • DSL Digital Subscriber Line
  • one or more of these RATs may enable the UE 105 to communicate with the PSAP 180.
  • the UE 105 may comprise a single entity or may comprise multiple entities such as in a personal area network where a user may employ audio, video and/or data I/O devices and/or body sensors and a separate wireline or wireless modem.
  • An estimate of a location of the UE 105 may be referred to as a location, location estimate, location fix, fix, position, position estimate or position fix, and may be geographic, thus providing location coordinates for the UE 105 (e.g., latitude and longitude) which may or may not include an altitude component (e.g., height above sea level, height above or depth below ground level, floor level or basement level).
  • a location of the UE 105 may be expressed as a civic location (e.g., as a postal address or the designation of some point or small area in a building such as a particular room or floor).
  • a location of the UE 105 may also be expressed as an area or volume (defined either
  • a location of the UE 105 may further be a relative location comprising, for example, a distance and direction or relative X, Y (and Z) coordinates defined relative to some origin at a known location which may be defined geographically, in civic terms, or by reference to a point, area, or volume indicated on a map, floor plan or building plan.
  • a relative location comprising, for example, a distance and direction or relative X, Y (and Z) coordinates defined relative to some origin at a known location which may be defined geographically, in civic terms, or by reference to a point, area, or volume indicated on a map, floor plan or building plan.
  • Serving network 140 may provide wireless access to UE 105 (e.g. using any of the RATs described previously).
  • Home network 160 may be a network with which the user of UE 105 maintains a subscription for wireless services.
  • networks 140 and 160 may be the same network.
  • the serving network 140 and home network 160 may comprise any of a variety of wireless and/or wireline networks. These networks 140 and 160 can, for example, comprise any combination of public and/or private networks, local and/or wide-area networks, and the like. Furthermore, networks 140 and 160 may utilize one or more wired and/or wireless communication
  • the networks 140 and 160 may comprise a cellular network, some other wireless wide area network (WW AN) network and/or a wireless local area network (WLAN), for example.
  • WW AN wireless wide area network
  • WLAN wireless local area network
  • Particular examples of networks 140 and 160 include an LTE wireless network, a Fifth Generation (5G) wireless network (also referred to as New Radio (NR) wireless network), a WiFi WLAN and the Internet.
  • LTE, GSM, WCDMA, 5G and NR are wireless technologies defined, or being defined, by the 3 rd Generation Partnership Project (3GPP).
  • Networks 140 and 160 may also include more than one network and/or more than one type of network. [0040] Under non-emergency situations, the UE 105 can communicate with the home network 160 for authentication and authorization purposes.
  • This communication from the UE 105 to the home network 160 may be made via the serving network 140 and Internet 170.
  • the home network 160 may also provide IP multimedia subsystem (IMS) and/or other services.
  • IMS IP multimedia subsystem
  • the home network 160 may be bypassed during emergency calls, for both voice channel establishment and for the transmission of an emergency SMS to the PSAP 180, in accordance with the techniques disclosed herein.
  • the base stations 120 and access points (APs) 130 are communicatively coupled to the serving network 140 and may be considered to be part of the serving network 140 (though are shown separately for greater clarity).
  • a base station 120 may comprise a Node B, an Evolved Node B (also referred to as an eNodeB or eNB), a base transceiver station (BTS), a radio base station (RBS), or the like.
  • a base station 120 may support a WW AN technology or RAT such as GSM, WCDMA, LTE or 5G.
  • An AP 130 may comprise a WiFi AP or a Bluetooth AP.
  • the UE 105 can send and receive information to and from network-connected devices, such as the location server 150, by accessing the serving network 140 via a base station 120 using a first communication link 133. Additionally or alternatively, because APs 130 also may be communicatively coupled with the serving network 140, the UE 105 may communicate with network- connected devices, including the location server 150, using a second communication link 135.
  • the location server 150 may comprise a server and/or other computing device configured to determine a location estimate for the UE 105 and/or provide data (e.g., "assistance data") to the UE 105 to facilitate the location determination.
  • the location server 150 may comprise a Secure User Plane Location (SUPL) Location Platform (SLP) server, which may support the SUPL user plane (UP) location solution defined by the Open Mobile Alliance (OMA) and may support location services for UE 105 based on subscription information for UE 105 stored in the location server 150.
  • the location server 150 may comprise a Discovered SLP (D-SLP) or an Emergency SLP (E-SLP).
  • the location server 150 may also comprise an Enhanced Serving Mobile Location Center (E-SMLC) that supports location of UE 105 using a control plane (CP) location solution for LTE access by UE 105.
  • the location server 150 may further comprise a Location
  • LMF Location Management Function
  • CP control plane
  • signaling to control and manage the location of UE 105 may be exchanged between elements of serving network 140, and with UE 105, using existing network interfaces and protocols and as signaling from the perspective of serving network 140.
  • signaling to control and manage the location of UE 105 may be exchanged between location server 150 and UE 105 as data (e.g. data transported using the Internet Protocol (IP) or Transmission Control Protocol (TCP) and IP
  • IP Internet Protocol
  • TCP Transmission Control Protocol
  • TCP/IP Transmission Control Protocol/IP
  • the UE 105 may include its location in an emergency SMS message sent to the PSAP 180. This location may be obtained using any of a variety of techniques.
  • UE 105 may have circuitry and processing resources capable of obtaining location related measurements (e.g. for signals received from SVs 110, APs 130, and/or base stations 120) and possibly computing a position fix or estimated location of the UE 105 based on these location related measurements.
  • location related measurements obtained by the UE 105 may be transferred to the location server 150 after which the location server 150 may estimate or determine a location for the UE 105 based on the measurements.
  • Location related measurements obtained by the UE 105 may include measurements of signals received from SVs 110 belonging to a Satellite Positioning System (SPS) or Global Navigation Satellite System (GNSS) such as the Global Positioning System (GPS), GLONASS, Galileo or Beidou, and/or may include measurements of signals received from terrestrial transmitters fixed at known locations (e.g., such as base stations 120 and/or APs 130).
  • SPS Satellite Positioning System
  • GNSS Global Navigation Satellite System
  • GPS Global Positioning System
  • GLONASS Global Positioning System
  • Galileo Galileo or Beidou
  • the UE 105 and/or location server 150 may then obtain a location estimate for the UE 105 based on these location related measurements using any one of several known position methods such as, for example, GNSS, Assisted GNSS (A-GNSS), Advanced Forward Link Trilateration (AFLT), Observed Time Difference Of Arrival (OTDOA), or Enhanced Cell ID (E-CID), or combinations thereof.
  • GNSS Assisted GNSS
  • AFLT Advanced Forward Link Trilateration
  • OTDOA Observed Time Difference Of Arrival
  • E-CID Enhanced Cell ID
  • pseudoranges or timing differences may be measured at the UE 105 relative to three or more terrestrial transmitters fixed at known locations or relative to four or more satellites with accurately known orbital data, or combinations thereof, based at least in part, on pilots, navigation signals, positioning reference signals (PRS) or other positioning related signals transmitted by the transmitters or satellites and received at the UE 105.
  • PRS positioning reference signals
  • the location server 150 may be capable of providing positioning assistance data to the UE 105 including, for example, information regarding signals to be measured (e.g., signal timing, frequency, coding and/or bandwidth), locations and identities of terrestrial transmitters and/or signal, timing and/or orbital information for GNSS satellites to facilitate positioning techniques such as A-GNSS, AFLT, OTDOA and E-CID.
  • the location server 150 may comprise an almanac which indicates locations and identities of base stations 120 and/or APs 130 in a particular region or regions such as a particular venue, and may provide information descriptive of signals transmitted by one or more of the terrestrial transceivers (e.g., base stations 120 and/or APs 130) such as transmission power and signal timing.
  • the UE 105 may obtain measurements of signal strengths for signals received from terrestrial transceivers and/or may obtain a round trip signal propagation time (RTT) between the UE 105 and a terrestrial transceiver.
  • RTT round trip signal propagation time
  • the UE 105 may use the measurements obtained for signals received from satellites and/or terrestrial transceivers (or transmitters) together with assistance data (e.g. terrestrial almanac data or GNSS satellite data such as GNSS Almanac and/or GNSS Ephemeris information) received from the location server 150 to determine a location for the UE 105 or may transfer the measurements to the location server 150 to perform the same determination.
  • assistance data e.g. terrestrial almanac data or GNSS satellite data such as GNSS Almanac and/or GNSS Ephemeris information
  • An emergency and/or SMS message sent from the UE 105 may be routed to or towards the PSAP 180 based on the location of the UE.
  • the PSAP 180 may be a PSAP whose public safety service area includes the location that was determined for the UE 105.
  • the PSAP 180 may comprise one or more devices to which emergency calls and/or SMS messages may be routed.
  • FIG. 1 illustrates the PSAP 180 as having separate connections with both the serving network 140 and the Internet 170, other configurations are possible. In some embodiments, the PSAP 180 may be directly connected with only one or the other.
  • FIG. 2 is a signaling flow diagram illustrating how an emergency SMS message can be communicated from the UE 105 to the PSAP 180 in conjunction with an emergency call, according to an embodiment.
  • the home network 160 it may be largely bypassed to establish both the emergency call and send the emergency SMS message.
  • bypassing the home network 160 may improve reliability by avoiding dependence on the home network 160. For example, if the home network 160 does not provide wireless coverage at or nearby to the present location of UE 105, the home network 160 may not be able to send an ESMS message to PSAP 180 due to
  • bypassing home network 160 may avoid failure of ESMS message transfer to PSAP 180 due to such limitations of home network 160.
  • FIG. 2 Communication between components in FIG. 2 may be made via messages provided in accordance with governing standards and/or protocols.
  • a person of ordinary skill in the art will appreciate that alternative embodiments may perform functions in a different order, add functions, omit functions, and/or employ other variations from the functionality illustrated in FIG. 2, depending on desired
  • the UE 105 detects an emergency condition. This can be done in any of a variety of ways, depending on the scenario. The detection may be made using sensor, location, and/or other information obtained by the UE 105.
  • an emergency condition can comprise any of a variety of events detected by the UE 105, including the user dialing of an emergency number, entering a predetermined location, performing a certain gesture, speaking a certain word or phrase, and the like.
  • Health information of the user may additionally or alternatively be considered, and may be obtained through health-monitoring sensors worn by, implanted in, or otherwise connected with the user.
  • an emergency condition may comprise the receipt of certain health information, such as an indication of an irregular heartbeat, high or low blood pressure, hyperventilation, high or low body temperature, high or low blood sugar, etc.
  • the emergency condition may be user defined.
  • UE 105 In response to detecting the emergency condition, UE 105 then performs actions to initiate an emergency call.
  • the UE attaches to the serving network 140 (e.g., by sending an Attach Request message to serving network 140) if the UE 105 is not already attached.
  • the UE 105 and serving network 140 then establish an emergency packet data network (PDN) connection at action 220, which may include assigning an IP address to the UE 105.
  • PDN packet data network
  • the UE 105 then performs an IMS emergency registration at action 225 with both the serving network 140 and the home network 160 and may provide the IP address obtained at action 220 as a contact address to the serving network 140 and the home network 160.
  • PDN packet data network
  • the UE 105 can attempt to establish an IMS emergency call with the PSAP 180 via the serving network 140. Timing, format, and/or other aspects of communication may be governed by applicable standards and/or protocols. Actions 215 to 235 may be as defined for IMS emergency call initiation with LTE wireless access - e.g. as in 3GPP Technical
  • the UE 105 may detect a trigger condition, which can trigger the sending of the emergency SMS message from the UE 105 to the PSAP 180 at actions 245 and 250. Similar to the emergency condition of block 210, the trigger condition can be any of a variety of events detected by the UE 105 that may be cause for sending an emergency SMS message. For example, the UE 105 may detect that the IMS emergency call establishment attempt (actions 230 and 235) has failed, or simply that the attempt was made but the emergency call was not established. As previously mentioned (and not shown in FIG.
  • emergency attempts may be made with a variety of different RATs, in which case embodiments may send an emergency SMS message (e.g., perform actions 245 and 250) after an emergency call establishment fails with each RAT and/or after each attempt with a particular RAT fails (e.g. in embodiments that make multiple attempts to establish an emergency call using a single RAT).
  • the trigger condition detected at block 240 may be time-based, such that, the trigger condition is detected after a certain amount of time passes since a previous event, such as the IMS emergency call establishment attempt (action 230), the emergency condition being detected (block 210), and/or another such event.
  • the UE may instigate ESMS message sending at action 245 following the elapse of a short period (e.g. 10 to 20 seconds) following detection of the emergency condition at block 210 if an emergency is not yet established or was (briefly) established and has failed.
  • the trigger condition detected at block 240 may comprise a deterioration or seriousness in the emergency condition detected at block 210 - e.g. such as health monitoring indicating that the user may not be able to speak to a PSAP operator even if the emergency call initiated by actions 215 to 235 is successfully established.
  • the content of the emergency SMS message can vary, depending on desired functionality, capabilities of the UE 105, type of emergency condition, and/or other factors. For example, if the UE 105 has access to information specific to the user of the UE 105, such as identification, address, health, age, and/or other information, the UE may include this information in the emergency SMS message. (This information may be previously entered by the user specifically for this purpose and stored in the UE 105 and/or may be obtained through other usage of the UE 105.) Applicable data from health monitors and/or sensors such as pulse, blood pressure, heart rate, blood sugar, body temperature, etc., may be included, if available.
  • information specific to the user of the UE 105 such as identification, address, health, age, and/or other information
  • Applicable data from health monitors and/or sensors such as pulse, blood pressure, heart rate, blood sugar, body temperature, etc., may be included, if available.
  • location information can be provided, where available, to allow emergency services to locate the user (e.g. in cases where emergency services are dispatched to assist the user).
  • Location information may include a current location of the UE 105, a recent previous location of the UE 105, a current velocity of the UE 105, a recent previous velocity of the UE 105, and/or indication of whether the UE 105 is currently stationary.
  • content included in the SMS message may be user definable and may be established in a setup procedure that may be performed, for example, when the UE 105 is being configured to enable emergency SMS messaging (e.g., when the UE 105 is used at an earlier time prior to the emergency condition).
  • the emergency SMS message may include information regarding emergency call attempt history, which may help emergency responders further understand the urgency of an emergency situation.
  • the emergency SMS message may include an indication of the number of emergency call attempts made for the current emergency condition and/or recent previous emergency conditions and a time or period when the attempts took place.
  • the emergency SMS message may include timestamps or time deltas to show when previous emergency call attempts occurred. This may be limited to a certain number of attempts (e.g., the last 2 attempts) and/or a certain window of time (e.g., the last 24 hours).
  • An indication of whether those previous attempts were successful may also be included, according to some embodiments.
  • the ESMS message may include an emergency indication indicating that the ESMS message relates to an emergency situation.
  • the emergency indication may distinguish the ESMS message from a normal (nonemergency) SMS message and may enable or assist routing of the ESMS message to a PSAP 180 rather than to some other destination.
  • the emergency indication may comprise a destination address for the ESMS message that corresponds to a dialed emergency number such as "911" in North America, "112" in Europe or "999" in the United Kingdom.
  • the destination address in the ESMS message containing the emergency number may replace a normal destination address in the ESMS message such as a Mobile Station International Subscriber Directory Number (MSISDN) for a destination UE.
  • MSISDN Mobile Station International Subscriber Directory Number
  • the emergency indication may comprise an association of the SMS message with (or a reference to) the IMS emergency call attempt at actions 230 and 235.
  • the association may comprise: (i) the use of the same IP address by the UE 105 to send the ESMS message at action 245 as was obtained by the UE 105 for the emergency PDN connection established at action 220; (ii) the use of the emergency PDN connection obtained by the UE 105 at action 220 to send the ESMS message to the serving network 140 at action 245; or (iii) inclusion of an identification (e.g. an MSISDN or SIP public user ID) for UE 105 in a message (e.g.
  • an identification e.g. an MSISDN or SIP public user ID
  • a SIP MESSAGE used to transport the ESMS message to serving network 140 at action 245, wherein serving network 140 (e.g. a P-CSCF in serving network 140) has previously stored the identification and is aware that UE 105 instigated the IMS emergency call attempt at actions 230 and 235.
  • serving network 140 e.g. a P-CSCF in serving network 140
  • the emergency indication may indicate to serving network 140 that the ESMS message should not be routed to the home network 160 for UE 105 but should instead be routed to PSAP 180 by serving network 140 at action 250 by bypassing home network 160.
  • the data to be included in the emergency SMS message may exceed size limits for a single SMS message.
  • data may be sent in multiple ESMS messages.
  • data may be prioritized such that higher-priority data is sent in earlier messages. This priority can be based on a variety of factors, such as the detected emergency condition, user preferences, and the like. For example, in a situation where the emergency condition detected at block 210 is a heart attack (based on health data), heart-related information (e.g., blood pressure, pulse, etc.) may be given a high priority.
  • heart-related information e.g., blood pressure, pulse, etc.
  • the emergency SMS message may include a Uniform Resource Locator (URL) (or possibly a Uniform Resource Identifier (URI)) that enables the PSAP to access data regarding the user.
  • the URL may, for example, indicate the location of a website, document, or other electronic file hosted on a server maintained by the home network 160, a third party, or another entity (even the PSAP 180 itself or another PSAP), accessible to the PSAP 180.
  • the website, document, or other electronic file may include not only information that may be included in an emergency SMS message as described above, but additionally or alternatively, the website, document, or other electronic file may include information such as a picture, video, or other content that may not otherwise be included in an emergency SMS message.
  • a key, login and/or password may be included in the ESMS message along with the URL to enable a PSAP operator to access secure information for the user of the UE 105 that is only intended to be seen by authorized users such as PSAP 180.
  • the ESMS message may be sent by UE 105 to serving network 140 at action 245 and serving network 140 may then forward the ESMS message to PSAP 180 at action 250 - e.g. based on an emergency indication in the ESMS message as described previously.
  • serving network 140 may forward the ESMS message to the same PSAP at action 250 as the PSAP to which the emergency call establishment attempt is sent at action 235.
  • serving network 140 may obtain a location estimate for UE 105 (e.g.
  • a serving cell for UE 105 or positioning of UE 105 using a location solution such as the OMA SUPL solution or the 3 GPP control plane solution for LTE access may route the ESMS message at action 250 to a PSAP associated with this location estimate (e.g. a PSAP whose service area includes the location estimate for UE 105).
  • a PSAP associated with this location estimate e.g. a PSAP whose service area includes the location estimate for UE 105.
  • forwarding of the ESMS message to PSAP 180 by serving network 140 at action 250 may bypass the home network 160 for UE 105 which may result in ESMS message forwarding with lower delay and higher reliability.
  • the UE 105, the serving network 140 and PSAP 180 may engage in additional signaling (e.g. using the Session Initiation Protocol (SIP)) to establish a voice-dedicated bearer and complete the emergency call establishment at actions 255 and 260.
  • the user of the UE 105 may then conduct a voice call with a responder at the PSAP 180 at action 265.
  • the emergency call may fail (e.g. may be released by the UE 105, serving network 140 or PSAP 180).
  • the UE 105 may optionally detect a new trigger condition and send another emergency SMS message via the serving network 140 (e.g. repeating actions at block 240 and actions 245 and 250).
  • detecting the new trigger condition may comprise detecting that the emergency call was dropped, that there was a change in the information sent in the first emergency SMS message (e.g., a change in UE 105 location, change in the emergency situation such as user health for a medical emergency, etc.), and the like.
  • some embodiments may be configured to send emergency SMS messages periodically (e.g., every 10 seconds, 30 seconds, 60 seconds, etc.) during the emergency call and/or while the emergency condition is met.
  • the detection of a trigger condition and subsequent sending of the emergency SMS message may be located at additional or alternative times or periods.
  • the emergency SMS message may be sent at actions 245 and 250 as soon as possible after detecting the emergency condition (block 210).
  • sending the emergency SMS message at actions 245 and 250 may be optional (e.g., only sent if the emergency call fails), whereas in other embodiments or scenarios the emergency SMS message may always be sent.
  • Such variations can be made to accommodate different call flows, technologies, and/or desired functionality.
  • FIG. 3 is a simplified block diagram showing a communication system 300 that may be an example of the communication system 100 for the case that the serving network 140 supports LTE access for a UE 105.
  • the serving network 140 may be referred to as an Evolved Packet System (EPS)).
  • Communication system 300 includes a Legacy Emergency Services (ES) Network 345 attached to a Legacy PSAP 180-1, and a National Emergency Number Association (NENA) i3 Emergency Services IP network (ESInet) 355 attached to a NENA i3 capable PSAP 180-2.
  • ES Legacy Emergency Services
  • NENA National Emergency Number Association
  • ESInet Emergency Services IP network
  • the serving network 140 may include an Evolved Node B (eNodeB, or eNB) 305 which may correspond to a base station 120, a Serving Gateway 315, a Packet Data Network (PDN) Gateway 320, a Mobility Management Entity (MME) 310, a Proxy Call Session Control Function (P-CSCF) 325, an Emergency Call Session Control Function (E-CSCF) 330, a Media Gateway Control Function (MGCF) 335, an Interconnection Border Control Function (IBCF) 340, a Serving Call Session Control Function (S-CSCF) 350, a Location Retrieval Function (LRF) 390, an IP Short Message Gateway (IP-SM-GW) 360, an SMS Gateway Mobile Switching Center (SMS-GMSC) 365 and an SMS Service Center (SMS SC) 370.
  • eNodeB Evolved Node B
  • eNodeB Evolved Node B
  • eNodeB Evolved Node B
  • the MGCF 335 may be incorporated into or otherwise joined with a Media Gateway (MGW) (not shown in FIG. 3).
  • MGW Media Gateway
  • the communication system 300 may comprise other components (some of which are shown in FIG. 3 but which are not discussed in this disclosure), and other embodiments may add, omit, join, separate, rearrange, or otherwise alter components depending on desired functionality. Such variations will be recognized by a person of ordinary skill in the art.
  • the eNB 305 may be a serving eNB for the UE 105 and may provide wireless communications access to the serving network 140 on behalf of UE 105.
  • the MME 310 may be a serving MME for the UE 105 and may support mobility of UE 105 and provision of signaling access and voice bearer paths to UE 105.
  • the serving gateway 315 and PDN gateway 320 may provide IP based signaling and IP transport support for UE 105 - e.g. with PDN gateway 320 assigning an IP address for UE 105 and providing IP access to other entities in serving network 140 such as P-CSCF 325.
  • Serving network 140 may include an IP Multimedia Subsystem (IMS) 380 that may include the P-CSCF 325, E-CSCF 330, MGCF 335, IBCF 340, S-CSCF 350 and LRF 390.
  • IMS 380 may support an FMS emergency services call from UE 105 to a PSAP 180 such as i3 PSAP 180-2 or legacy PSAP 180-1.
  • PSAP 180 such as i3 PSAP 180-2 or legacy PSAP 180-1.
  • a signaling path not shown in FIG.
  • a signaling path (not shown in FIG. 3) from UE 105 may pass through the eNB 305, serving gateway 315, PDN gateway 320, P-CSCF 325, E-CSCF 330, IBCF 340, the i3 ESInet 355 and i3 PSAP 180-2.
  • a signaling path (not shown in FIG. 3) from UE 105 may pass through the eNB 305, serving gateway 315, PDN gateway 320, P-CSCF 325, E-CSCF 330, a Breakout Gateway Control Function (BGCF), MGCF 335, the legacy ES Network 345 and legacy PSAP 180-1.
  • BGCF Breakout Gateway Control Function
  • Elements in IMS 380 may provide call handling and call routing support to enable an FMS emergency services call from UE 105 to either i3 PSAP 180-2 or legacy PSAP 180-1.
  • P-CSCF 325 may detect an IMS emergency services call when instigated by UE 105 (e.g. by receiving, decoding and interpreting a SIP INVITE message sent by UE 105).
  • E-CSCF 330 may support routing of an IMS emergency services call from UE 105 (e.g. by sending a SIP INVITE received from UE 105 via P- CSCF 325 towards either legacy PSAP 180-1 via MGCF 335 or i3 PSAP 180-2 via IBCF 340).
  • LRF 390 may assist routing of an IMS emergency services call from UE 105 when queried by E-CSCF 330.
  • LRF 390 may determine a location for UE 105 (e.g. from information provided by UE 105 in a SIP INVITE) and may determine a PSAP (e.g. legacy PSAP 180-1 or i3 PSAP 180-2) that supports an emergency services call for that location and may return an identity or address for this PSAP to E-CSCF 330.
  • PSAP e.g. legacy PSAP 180-1 or i3 PSAP 180-2
  • MGCF 335 may perform conversion of SIP based signaling, received from or sent to UE 105, to or from signaling used by ES network 345 such as Integrated Services Digital Network (ISDN) User Part (ISUP) signaling in the case of an emergency services call to legacy PSAP 180-1.
  • ISDN Integrated Services Digital Network
  • ISUP ISUP User Part
  • MGCF 335 may convert an IMS emergency services call received from UE 105 into a Circuit Switched (CS) emergency services call in the case of an IMS emergency services call routed to legacy PSAP 180-1.
  • CS Circuit Switched
  • 13 ESInet 355 may support IP based emergency calls from UE 105 on behalf of i3 PSAP 180-2 - e.g. may route an IP based emergency services call from UE 105 to i3 PSAP 180-2.
  • Legacy ES network 345 may similarly support Circuit Switched (CS) based emergency calls on behalf of legacy PSAP 180-1 received via MGCF 335 from UE 105 - e.g. may route a CS emergency services call from UE 105 received via MGCF 335 to legacy PSAP 180-1.
  • An MGW connected to MGCF 335 (not shown in FIG.
  • VoIP Voice over IP
  • IP-SM-GW 360 may serve as gateway to route IP based SMS messages received from UE 105 to or towards SMS SC 370 and IP based SMS messages received from SMS SC 370 to or towards UE 105.
  • Functions of the IP-SM-GW 360 can include (i) providing protocol interworking for transfer of an SMS message or ESMS message between UE 105 and SMS SC 370, (ii) determining the domain (e.g. CS, packet switched (PS) or FMS) for delivery of an SMS or ESMS message (e.g. to UE 105 or PSAP 180), (iii) connecting to the SMS-GMSC 365 using established Mobile
  • MAP Application Part
  • Diameter based protocols (iv) appearing to (e.g. connecting to) the SMS-GMSC 365 as a Mobile Switching Center (MSC), Serving General Packet Radio Service (GPRS) Support Node (SGSN) or MME, (v) connecting to a Home Subscriber Server (HSS - not shown in FIG. 3) using established MAP or Diameter based protocols to obtain MSC/SGSN/MME address(es) for SMS termination, and/or (vi) acting as an Application Server towards the IMS 380.
  • MSC Mobile Switching Center
  • GPRS General Packet Radio Service
  • HSS Home Subscriber Server
  • SMS-GMSC 365 which may also function as (or be referred to as) an SMS Interworking MSC (SMS-IWMSC) may transfer SMS messages to and from SMS SC 370 and may serve as the access node in serving network 140 that provides access to SMS SC 370 using standardized protocols.
  • SMS-IWMSC SMS Interworking MSC
  • SMS SC 370 may provide a store and forward capability for SMS message transfer for serving network 140 by receiving SMS messages sent by UEs subscribed to serving network 140 and forwarding the SMS messages to their destinations such as other UEs or clients and servers access via a wireline network.
  • serving network 140 e.g. serving network 140 is the same as home network 160
  • an SMS message sent by UE 105 may be routed to SMS SC 370 via P-CSCF 325, S-CSCF 350, IP-SM-GW 360 and SMS-GMSC 365.
  • UE 105 may send the SMS message within a SIP MESSAGE to S-CSCF 350 via P-CSCF 325.
  • S-CSCF 350 may forward the SIP MESSAGE to IP-SM-GW 360 which may extract the SMS message and forward the SMS message to SMS-GMSC 365.
  • SMS-GMSC 365 may then forward the SMS message to SMS SC 370.
  • SMS SC 370 may then forward the SMS message to a destination indicated by a destination address (e.g. an MSISDN) in the SMS message which may in some scenarios involve forwarding through similar or identical entities to those used to forward the SMS message to SMS SC 370 but in a reverse order (e.g. may involve forwarding through an SMS-GMSC, IP-SM GW, S-CSCF, P-CSCF to a UE which may be associated with serving network 140 or with some other network).
  • a destination address e.g. an MSISDN
  • an SMS message sent by UE 105 may be routed to an SMS SC in home network 160 and not to SMS SC 370 which may make routing an ESMS message to a PSAP 180 difficult or impossible.
  • FIG. 4 is a signaling flow diagram illustrating how an emergency SMS message can be communicated from the UE 105 to a PSAP 180 in conjunction with an emergency call for the communication system 300 described for FIG. 3.
  • the signaling flow in FIG. 4 may be a particular example of the signaling flow in FIG. 2.
  • the home network 160 is not illustrated, as it may be largely bypassed to establish both the emergency call and to send the emergency SMS message.
  • Blocks and actions in FIG. 4 that may correspond to blocks and actions, respectively, in FIG. 2 are identified. For such blocks and actions, the description provided in FIG. 2 applies to FIG. 4, except as stated otherwise, and is thus not always repeated.
  • the UE 105 detects an emergency condition.
  • Block 410 may correspond to block 210 in FIG 2.
  • the detection may be made using sensor, location, and/or other information obtained by the UE 105.
  • UE 105 performs actions to initiate an emergency call.
  • action 415 which may correspond to action 215, the UE attaches to the serving network 140 (e.g., by sending an LTE Non Access Stratum (NAS) Attach Request message or a NAS Emergency Attach Request message to the serving MME 310) if the UE 105 is not already attached to serving network 140.
  • the UE 105 and serving network 140 e.g.
  • serving eNB 305, MME 310, Serving Gateway 315 and PDN Gateway 320 then exchange signaling messages to establish an emergency packet data network (PDN) connection at action 420, which may correspond to action 220.
  • PDN packet data network
  • the serving network 140 e.g. the PDN Gateway 320
  • UE 105 then initiates and performs an IMS emergency registration at action 425, which may correspond to action 225, by performing a emergency registration with IMS 380 in the serving network 140 and with an IMS (not shown in FIG. 4) in the home network 160.
  • UE 105 may send a SIP REGISTER message to P-CSCF 325 (e.g. via eNB 305, Serving Gateway 315 and PDN Gateway 320) and P-CSCF 325 may forward the SIP REGISTER message to an S-CSCF (not shown in FIG. 3 or FIG. 4) in the home network 160, after which UE 105, P-CSCF 325 and the S-CSCF in home network 160 may exchange further SIP messages to complete the IMS emergency registration.
  • P-CSCF 325 e.g. via eNB 305, Serving Gateway 315 and PDN Gateway 320
  • S-CSCF 325 may forward the SIP REGISTER message to an S-CSCF (not shown in FIG. 3 or FIG. 4) in the home
  • the SIP REGISTER message sent by the UE 105 as part of action 425 may include (e.g. in a Contact header for the SIP REGISTER message) an IP address received by UE 105 from serving network 140 (e.g. from PDN Gateway 320) as part of emergency PDN connection establishment at action 420.
  • the IP address may be stored by P-CSCF 325 as part of action 425.
  • the UE 105 can attempt to establish an IMS emergency call with the PSAP 180 via the serving network 140.
  • UE 105 may send a SIP INVITE message to P-CSCF 325 at action 430 (e.g. via eNB 305, Serving Gateway 315 and PDN Gateway 320).
  • the SIP INVITE message may indicate an emergency call and may include (i) the serving cell identity (ID) for UE 105, (ii) an identification for UE 105 such as an MSISDN, a SIP public user ID or an International Mobile Equipment Identity (IMEI), and/or (iii) the IP address received by the UE 105 from serving network 140 as part of emergency PDN connection establishment at action 420 and stored by P-CSCF 325 as part of IMS emergency registration at action 425.
  • P-CSCF 425 may forward the SIP INVITE message to E-CSCF 330 (not shown in FIG.
  • E-CSCF 330 may request routing and/or location information for UE 105 from LRF 390 by forwarding the SIP INVITE to LRF 390 (not shown in FIG. 4).
  • LRF 390 may use the serving cell ID (if present) in the SIP INVITE to determine a location estimate and/or routing information for UE 105 and may return these to E-CSCF 330 (not shown in FIG. 4).
  • E-CSCF 330 may then forward the SIP INVITE towards either legacy PSAP 180-1 or i3 PSAP 180-2 based on the location information or routing information received from LRF 390.
  • E-CSCF 330 may forward the SIP INVITE to MGCF 335 via a BGCF (not shown in FIG. 4) and MGCF 335 (not shown in FIG. 4) may interwork SIP signaling with ISUP signaling and forward the emergency call request indicated in the SIP INVITE as an ISUP Initial Address Message (IAM) to legacy ES network 345 at action 435.
  • Legacy ES network 345 (not shown in FIG. 4) may then forward the emergency call request (e.g. the ISUP IAM) to legacy PSAP 180- 1.
  • E-CSCF 330 may forward the SIP INVITE to IBCF 340 (not shown in
  • IBCF 340 may forward the SIP INVITE to i3 ESInet 355 at action 435, with i3 ESInet 355 then forwarding the SIP INVITE to i3 PSAP 180-2.
  • i3 ESInet 355 then forwarding the SIP INVITE to i3 PSAP 180-2.
  • one of these forwarding actions may fail or may be delayed - e.g. due to lack of resources - in which case legacy PSAP 180-1 or i3 PSAP
  • legacy PSAP 180-1 or i3 PSAP 180-2 may not receive the emergency call request (e.g. the ISUP IAM in the case of legacy PSAP 180-1 or the SIP INVITE in the case of i3 PSAP 180-2).
  • legacy PSAP 180-1 or i3 PSAP 180-2 may receive the emergency call request but may delay answering the request (e.g. may queue the request) or may reject the request due to lack of resources (e.g., lack of telecommunication related resources or lack of a PSAP operator to answer the call).
  • UE 105 may detect a trigger condition, which can trigger the sending of an emergency SMS message from UE 105 to PSAP 180 at actions 445, 450 and 455.
  • the trigger condition may be as described for block 240 in FIG. 2.
  • the content of the emergency SMS message (sent at actions 445, 450 and 455) may be as described for actions 245 and 250 in FIG. 2.
  • the data may be sent in multiple ESMS messages.
  • the emergency SMS message may include a URL (or URI) that enables the PSAP to access data regarding the user.
  • the ESMS message may include an emergency indication.
  • the emergency indication may comprise a destination address for the ESMS message that corresponds to a dialed emergency number such as "911" in North America, "112" in Europe or "999" in the United Kingdom.
  • the emergency indication may also or instead comprise an association with (or reference to) the FMS emergency call instigated by UE 105 at action 430.
  • the ESMS message may be sent by UE 105 to serving network 140 at action 445, which may correspond to action 245 in FIG. 2.
  • UE 105 may send the ESMS message to IMS 380 in serving network 140 by including the ESMS message in a SIP MESSAGE and sending the SIP MESSAGE to P- CSCF 325 (not shown in FIG. 4) at action 445 (e.g. via e B 305, Serving Gateway 315 and PDN Gateway 320).
  • the UE 105 may associate the SIP MESSAGE with (or include a reference in the SIP MESSAGE to) the IMS emergency registration at action 425 and/or the SIP INVITE sent at action 430.
  • the association may comprise or serve as an emergency indication, as previously described for block 440, and may assist or enable the IMS 380 (e.g. the P-CSCF 325 and/or E-CSCF 330) to recognize the ESMS message as an emergency message.
  • the association with (or reference to) the IMS emergency registration at action 425 and/or the SIP INVITE sent at action 430 may be indicated by UE 105 by including a SIP Contact header in the SIP MESSAGE sent at action 445.
  • the SIP Contact header may comprise an IP address assigned to the UE 105 as part of emergency PDN connection establishment at action 420, included by UE 105 (e.g.
  • the emergency indication may comprise an association with (or reference to) the IMS emergency call attempt at actions 430 and 435.
  • the association of the SIP MESSAGE sent at action 445 with (or the reference to) the IMS emergency registration at action 425 and/or the SIP INVITE sent at action 430 may also or instead comprise: (i) the use of the emergency PDN connection obtained by the UE 105 at action 420 to send the SIP MESSAGE to IMS 380 (e.g.
  • P-CSCF 325) at action 445; or (ii) inclusion of an identification (e.g. an MSISDN or SIP public user ID) for UE 105 in the SIP MESSAGE (e.g. in a From header in the SIP MESSAGE) sent at action 445 to IMS 380 (e.g. to P-CSCF 325 in IMS 380).
  • an identification e.g. an MSISDN or SIP public user ID
  • IMS 380 e.g. to P-CSCF 325 in IMS 380.
  • An emergency indication in the SIP MESSAGE (or in the ESMS message) sent at action 445 or an association of the SIP MESSAGE with (or a reference in the SIP MESSAGE to) the IMS emergency registration at action 425 and/or the SIP INVITE sent at action 430 may enable P-CSCF 325 and/or E-CSCF 330 to recognize the ESMS message as being an emergency SMS message rather than a normal (nonemergency) SMS message.
  • the recognition of the ESMS message as being an emergency SMS message may be used by P-CSCF 325 and/or E-CSCF 330 to transfer the ESMS message to a PSAP 180 via the serving network 140 rather than transferring the ESMS message to the home network 160 as for a normal (non-emergency) SMS message.
  • P-CSCF 325 may forward the SIP MESSAGE received at action 445 to E- CSCF 330 (not shown in FIG. 4). In one embodiment, P-CSCF 325 may forward the SIP MESSAGE based on recognizing the ESMS message contained in the SIP
  • E-CSCF 330 may then forward the SIP MESSAGE to IP-SM-GW 360 (not shown in FIG. 4). In one embodiment, E- CSCF 330 may forward the SIP MESSAGE based on recognizing the ESMS message contained in the SIP MESSAGE as an emergency message (e.g. based on an emergency indication in the ESMS message or an association of the SIP MESSAGE to the SIP INVITE at action 430).
  • IP-SM-GW 360 may extract the ESMS message from the SIP MESSAGE received from E-CSCF 330 and may forward the ESMS message to SMS- GMSC 365 (not shown in FIG. 4) which may forward the ESMS message to SMSC SC 370. Forwarding of the ESMS message from P-CSCF 325 to SMS SC 370 via E-CSCF 330, IP-SM-GW 360 and SMS-GMSC 365 as just described may correspond to action 450 in FIG. 4. SMS SC 370 may then forward the ESMS message to legacy PSAP 180- 1 or i3 PSAP 180-2 at action 455 (e.g. via legacy ES Network 345 or i3 ESInet 355, respectively), which may correspond to action 250 in FIG. 2.
  • legacy PSAP 180- 1 or i3 PSAP 180-2 at action 455 (e.g. via legacy ES Network 345 or i3 ESInet 355, respectively), which may correspond to action 250 in FIG. 2.
  • E-CSCF 330 may determine routing information for the ESMS message. For example, after receiving the SIP MESSAGE containing the ESMS message from P-CSCF 325 as previously described for action 450, E-CSCF 330 may query LRF 390 for location information for UE 105 or routing information for the ESMS message (not shown in FIG. 4) and LRF 390 may return a location estimate for UE 105 and/or routing information for the ESMS message.
  • the routing information may comprise the address of a PSAP 180 (e.g. a URL or URI).
  • E-CSCF 330 may have stored routing information (e.g.
  • E-CSCF 330 may include the routing information (e.g., the address of a PSAP 180 or an address in the i3 ESInet 355 or legacy ES network 345) in the ESMS message as the destination address for the ESMS message.
  • the E-CSCF 330 may replace a destination address in the ESMS message that comprises a dialed emergency number with the routing information.
  • SMS SC 370 may then forward the ESMS message to PSAP 180 at action 455 based on the destination address in the ESMS message, where the destination address may comprise an address for the PSAP 180 or an address in the i3 ESInet 355 or legacy ES network 345.
  • E-CSCF 330 may route the ESMS message to or towards the same PSAP 180 (e.g. the same legacy PSAP 180-1 or i3 PSAP 180-2) to which the emergency call establishment attempt at action 435 was sent.
  • the UE 105, the IMS 380 e.g.
  • the P-CSCF 325 and E-CSCF 330) and PSAP 180 may engage in additional signaling (e.g. using SIP) to complete the establishment of the IMS emergency call including a voice-dedicated bearer at action 460, which may correspond to actions 255 and 260.
  • the user of the UE 105 may then conduct a voice call with a responder at the PSAP 180 at action 465, which may correspond to action 265.
  • the emergency call may fail (e.g. may be released by the UE 105, IMS 380 or PSAP 180).
  • the UE 105 may optionally detect a new trigger condition and send another emergency SMS message to the PSAP 180 via the IMS 380 at actions 475, 480 and 485 which may be similar to or the same as actions 445, 450 and 455, respectively.
  • block 470 may correspond to block 270 in FIG. 2
  • actions 475 and 480 may correspond to action 275
  • action 485 may correspond to action 280.
  • the detection of a trigger condition at block 470 and subsequent sending of the emergency SMS message at actions 475-485 may be located at additional or alternative times or periods.
  • the emergency SMS message may be sent at actions 445, 450 and 455 as soon as possible after detecting the emergency condition (block 410).
  • sending the emergency SMS message at actions 445, 450 and 455 may be optional (e.g., if the emergency call fails), whereas in other embodiments or scenarios the emergency SMS message may always be sent.
  • FIG. 1 can be made to accommodate different call flows, technologies, and/or desired functionality.
  • FIG. 5 is a flow diagram illustrating a method 500 of initiating an emergency call at a UE, according to an embodiment.
  • the method 500 may be employed and/or implemented by a UE (e.g., UE 105 of FIGS. 1 to 4).
  • FIG. 5 is provided as a non-limiting example.
  • Alternative embodiments may include additional functionality to that shown in the figure, and/or the functionality shown in one or more of the blocks in the figure may be omitted, combined, separated, and/or performed simultaneously.
  • Means for performing the functionality of the blocks may include one or more hardware and/or software components, such as those described with regard to the UE 105 of FIG. 7, described herein below.
  • a person of ordinary skill in the art will recognize many variations.
  • an emergency condition is detected with the UE. As previously indicated, this may be done in a variety of ways.
  • the emergency condition may be detected by user input (e.g., the user dialing an emergency number).
  • the emergency condition may comprise an automatically-detected emergency condition, and may be automatically detected by the UE at block 510, such as by sensor(s), and/or device(s) coupled to and/or in
  • the UE, sensor(s), and/or device(s) may automatically detect an emergency health condition for the user, an accident involving the user, and/or an imminent danger for the user. This detection may be based on data from one or more sensors capable of detecting movement, position, orientation, temperature, sound, proximity, a visual image, health conditions (e.g. blood pressure, heart rate, breathing rate), and/or the like. These sensors may be incorporated into the UE itself (see, for example, sensor(s) 740 of the UE 105 illustrated in FIG.
  • a device or system related to the UE such as a vehicle or building security system (e.g., securing a vehicle or building owned, rented, and/or otherwise used by the user, or securing a vehicle or building in which the user is located), a wearable device worn by the user, a health monitoring system or device, etc.
  • vehicle or building security system e.g., securing a vehicle or building owned, rented, and/or otherwise used by the user, or securing a vehicle or building in which the user is located
  • a wearable device worn by the user e.g., a wearable wearable device worn by the user, a health monitoring system or device, etc.
  • Means for performing the functionality at block 510 may include hardware and/or software components of a UE, such as a bus 705, processing unit(s) 710, DSP 720, wireless communication interface 730, wireless communication antenna(s) 732, sensor(s) 740, memory 760, input device(s) 770, SPS receiver 780, SPS antenna 782, and/or other components of the UE 105 illustrated in FIG. 7 and described in detail below.
  • a bus 705 processing unit(s) 710, DSP 720, wireless communication interface 730, wireless communication antenna(s) 732, sensor(s) 740, memory 760, input device(s) 770, SPS receiver 780, SPS antenna 782, and/or other components of the UE 105 illustrated in FIG. 7 and described in detail below.
  • the functionality at block 520 includes initiating, based on the emergency condition, the emergency call to a PSAP using a certain radio access type (RAT) such as LTE, WCDMA, 5G etc.
  • a certain radio access type such as LTE, WCDMA, 5G etc.
  • Such initiation can include one or more of actions (e.g., actions 215, 220, 225, or 230 illustrated in FIG. 2 or actions 415, 420, 425, or 430 illustrated in FIG. 4) taken by the UE in communicating with a serving network (e.g. serving network 140) to initiate the emergency call.
  • a serving network e.g. serving network 140
  • the UE may be configured to communication using a plurality of RATs, and the certain RAT may be a preferred RAT or an available RAT for making an emergency call.
  • Means for performing the functionality at block 520 may include hardware and/or software components of a UE, such as a bus 705, processing unit(s) 710, wireless communication interface 730, wireless communication antenna(s) 732, memory 760, and/or other components of the UE 105 illustrated in FIG. 7 and described in detail below.
  • a trigger condition is detected.
  • the trigger condition can comprise any of a variety of conditions, based on desired functionality.
  • the trigger condition can comprise the emergency condition itself.
  • an emergency SMS message based on the detected trigger condition may be sent to the PSAP at block 540 prior to the initiation of the emergency call at block 520.
  • the trigger condition can additionally or alternatively comprise a failure to establish the emergency call using the certain radio access type, a delay in establishing the emergency call exceeding a certain threshold of time, an escalation or worsening of the emergency condition detected at block 510, and/or a quality of the certain RAT being below a certain threshold of quality.
  • Means for performing the functionality at block 530 may include hardware and/or software components of a UE, such as a bus 705, processing unit(s) 710, wireless communication interface 730, wireless communication antenna(s) 732, sensor(s) 740, memory 760, and/or other components of the UE 105 illustrated in FIG. 7 and described in detail below.
  • a bus 705 processing unit(s) 710, wireless communication interface 730, wireless communication antenna(s) 732, sensor(s) 740, memory 760, and/or other components of the UE 105 illustrated in FIG. 7 and described in detail below.
  • the functionality at block 540 comprises sending, based on the trigger condition, an emergency-related SMS message to the PSAP via a serving network different than a home network for the UE, wherein the sending bypasses the home network.
  • sending the emergency related SMS message to the PSAP may comprise sending the emergency related SMS message to an IP Multimedia Subsystem (IMS) in the serving network using the Session Initiation Protocol (SIP).
  • sending the emergency related SMS message to an IMS in the serving network may comprise sending the emergency related SMS message to a Proxy Call Session Control Function (P-CSCF) (e.g. P-CSCF 325) in the FMS and/or sending a SIP MESSAGE containing the emergency related SMS message to the FMS.
  • P-CSCF Proxy Call Session Control Function
  • the UE may include an emergency indication in the emergency related SMS message which may enable the serving network (e.g. the IMS in the serving network such as a P-CSCF or E-CSCF in the IMS) to determine that the emergency related SMS message is for an emergency condition.
  • the emergency indication may comprise a destination address for the emergency related SMS message that corresponds to a dialed emergency number.
  • the emergency indication may comprise an association with, or a reference to, the emergency call initiated at block 520.
  • the association or reference may comprise: (i) use of the same IP address for the UE to send the emergency related SMS message at block 540 as was used to initiate the emergency call at block 520; (ii) use of the same emergency packet data network (PDN) connection to send the emergency related SMS message at block 540 as was used to initiate the emergency call at block 540; and/or (iii) inclusion of the same identification for the UE in a message (e.g. a SIP MESSAGE) used to transport the emergency related SMS message sent at block 540 as was used to identify the UE for the emergency call initiated at block 520.
  • block 540 may correspond to action 245 in FIG. 2 and/or to action 445 in FIG. 4.
  • the emergency-related SMS can include any of a variety of types of information that may be useful to the PSAP in providing emergency services to the user.
  • the emergency-related SMS message may comprise a location of the UE, personal information of the user, and/or information regarding the emergency condition.
  • the location of the UE may be an estimated location obtained by the UE using any of the location estimation techniques described herein (e.g., involving GPS and/or other SPS or GNSS SVs, terrestrial transceivers, motion sensor(s), location server(s), and the like).
  • the location may be entered manually by the user.
  • the personal information of the user may be identification, age, health-related, and/or other information regarding the user, which may be entered by the user and/or stored by the UE.
  • the information regarding the emergency condition may be based on the detected emergency condition. If, for example, the UE received data from one or more sensor(s) of a vehicle in which the user was traveling that indicated the vehicle was in an accident, the information regarding the emergency condition could indicate that the emergency condition is a traffic accident and/or include information regarding the severity of the traffic accident, if available. Similarly, if the UE received data from one or more sensor(s) associated with (e.g.
  • the information regarding the emergency condition could indicate a medical condition for the user (e.g. irregular heart rate, high or low blood pressure, high or low blood sugar level, etc.).
  • the emergency-related SMS message can comprise a URL (or URI) that enables the PSAP to access data regarding the user.
  • some embodiments may provide for sending one or more additional emergency-related SMS messages.
  • the method 500 may additionally or alternatively include sending an updated emergency-related SMS message to the PSAP based on a subsequently- detected change in a location of the UE, change in information regarding the user, and/or change in information regarding the emergency condition.
  • the updated emergency-related SMS message may correspondingly include the updated information regarding the location, user, and/or emergency condition.
  • such updated emergency-related SMS messages can be sent based on triggering events, such as, a change in location beyond a threshold distance, a detected change in urgency and/or type of emergency condition, a change in health-related data of the user, and the like.
  • Means for performing the functionality at block 540 may include hardware and/or software components of a UE, such as a bus 705, processing unit(s) 710, DSP 720, wireless communication interface 730, wireless communication antenna(s) 732, sensor(s) 740, memory 760, input device(s) 770, SPS receiver 780, SPS antenna 782, and/or other components of the UE 105 illustrated in FIG. 7 and described in detail below.
  • a bus 705 processing unit(s) 710, DSP 720, wireless communication interface 730, wireless communication antenna(s) 732, sensor(s) 740, memory 760, input device(s) 770, SPS receiver 780, SPS antenna 782, and/or other components of the UE 105 illustrated in FIG. 7 and described in detail below.
  • FIG. 6 is a flow diagram illustrating a method 600 of routing an emergency- related SMS message received from a UE (e.g. UE 105), according to an embodiment.
  • the method 600 may be employed and/or implemented by a network element of a serving network for the UE (e.g., a network element may compose part of the serving network 140 of FIG. 1).
  • the serving network may be different than a home network for the UE.
  • the network element may be a network element in an FMS for the serving network (e.g. FMS 380) and may be a P-CSCF (e.g. P-CSCF 325) or an E-CSCF (e.g. E- CSCF 330).
  • the method 600 may be implemented by a network element of a serving network in conjunction with the UE performing the method 500 of FIG. 5.
  • Alternative embodiments may also employ other techniques for routing emergency- related SMS messages.
  • FIG. 6 is provided as a non-limiting example. Alternative embodiments may include additional functionality to that shown in the figure, and/or the functionality shown in one or more of the blocks in the figure may be omitted, combined, separated, and/or performed simultaneously.
  • a network element configured to performing the functionality of one or more of the blocks of the method 600 may comprise a computer system, such as a computer server. Accordingly, means for performing the functionality of one or more of the blocks of the method 600 may include one or more hardware and/or software components of a computer system as illustrated in FIG. 8 and described in more detail below. A person of ordinary skill in the art will recognize many variations.
  • a request for an emergency call is received from the UE.
  • the request may include receiving a request for a network attachment for an emergency call from the UE (e.g. as at action 215 and/or 415), receiving a request for an emergency PDN connection from the UE (e.g. as at action 220 and/or 420), receiving a request for an FMS emergency registration (e.g. a SIP REGISTER message) from the UE (e.g. as at action 225 and/or 425) and/or receiving a request for an IMS emergency call (e.g. a SIP INVITE message) from the UE (e.g. as at action 230 and/or 430).
  • a request for a network attachment for an emergency call from the UE (e.g. as at action 215 and/or 415)
  • receiving a request for an emergency PDN connection e.g. as at action 220 and/or 420
  • receiving a request for an FMS emergency registration e.g. a S
  • the network element may route the request for the emergency call to or towards a PSAP (e.g. PSAP 180) (e.g. as at action 235 and/or action 435).
  • PSAP e.g. PSAP 180
  • Means for performing the functionality at block 610 may include hardware and/or software components of a computer system, such as a bus 805, processing unit(s) 810, communications subsystem 830, working memory 835, operating system 840, application(s) 845, and/or other components of the computer system 800 illustrated in FIG. 8 and described in detail below.
  • an SMS message from the UE is received at the network element, where the SMS message comprises an emergency indication.
  • the receipt of the SMS message may be in conjunction with an attempt to establish the emergency call at block 610.
  • Block 620 may correspond to action 245, action 445 and/or action 450.
  • Means for performing the functionality at block 620 may include hardware and/or software components of a computer system, such as a bus 805, processing unit(s) 810, communications subsystem 830, working memory 835, operating system 840, application(s) 845, and/or other components of the computer system 800 illustrated in FIG. 8 and described in detail below.
  • the emergency indication at block 620 comprises a destination address for the SMS message that comprises an emergency number (e.g. "911" in North America or " 112" in Europe).
  • the emergency indication at block 620 comprises an association with, or a reference to, the emergency call of block 610. This association may be determined by the network element from the SMS message.
  • the association with, or reference to, the emergency call comprises use of the same IP address for the UE as for the emergency call, use of the same emergency PDN connection for the UE as for the emergency call, use of the same identification for the UE as for the emergency call, or some combination thereof.
  • the network entity e.g.
  • a P-CSCF may determine use of the same emergency PDN connection for the UE by determining if the SMS message is received through an emergency PDN connection for the UE that was previously established to support the emergency call received at block 610.
  • the SMS message is received at block 620 in a SIP MESSAGE.
  • the association with, or the reference to, the emergency call comprises a first IP address for the UE in a SIP Contact header for a SIP REGISTER message or SIP INVITE message received at block 610 and a second IP address for the UE in a SIP Contact header for a SIP MESSAGE received at block 620, where the first IP address is the same as the second IP address.
  • the functionality at block 630 includes determining by the network element a destination address for the SMS message based on the emergency indication.
  • the destination address may be the address of another network element in the serving network that is closer to or better able to route the SMS message to a PSAP.
  • the network element is a P-CSCF (e.g. P-CSCF 325)
  • the other network element may be an E-CSCF (e.g. E-CSCF 330), as described for action 450 in FIG. 4.
  • the destination address may be an address of a PSAP (e.g. PSAP 180, legacy PSAP 180-1 or i3 PSAP 180-2) or an address in a legacy ES network (e.g.
  • the network entity may obtain a location for the UE (e.g. from another network entity in the serving network such as LRF 390) and may determine the destination address based on the location.
  • the network entity e.g. an E-CSCF such as E-CSCF 330
  • Means for performing the functionality at block 630 may include hardware and/or software components of a computer system, such as a bus 805, processing unit(s) 810, input device(s) 815, communications subsystem 830, working memory 835, operating system 840, application(s) 845, and/or other components of the computer system 800 illustrated in FIG. 8 and described in detail below.
  • a computer system such as a bus 805, processing unit(s) 810, input device(s) 815, communications subsystem 830, working memory 835, operating system 840, application(s) 845, and/or other components of the computer system 800 illustrated in FIG. 8 and described in detail below.
  • the functionality at block 640 comprises routing the SMS message to or towards a PSAP (e.g. a PSAP 180), based on the destination address, wherein the routing bypasses the home network. As previously indicated, this can avoid additional steps that may delay the routing of the SMS message or fail to transfer the SMS messafge to a PSAP or to the correct PSAP.
  • Block 640 may correspond to action 250 in FIG. 2 and/or to action 450 and/or action 455 in FIG. 4.
  • the method 600 may further include sending an updated SMS message to the PSAP.
  • the updated SMS message may be received from the UE based on a subsequently detected change in a location of the UE, a change in information regarding the user of the UE, or change in information regarding the emergency condition, or any combination thereof.
  • the updated SMS may be generated by the network element - e.g. based on a failure to successfully establish the emergency call requested at block 610.
  • the SMS generation may be based on information provided to the network element by the UE and/or other devices (e.g., a location server) regarding the location of the UE, information regarding the user, and/or information regarding the emergency condition.
  • Means for performing the functionality at block 640 may include hardware and/or software components of a computer system, such as a bus 805, processing unit(s) 810, input device(s) 815, communications subsystem 830, working memory 835, operating system 840, application(s) 845, and/or other components of the computer system 800 illustrated in FIG. 8 and described in detail below.
  • a computer system such as a bus 805, processing unit(s) 810, input device(s) 815, communications subsystem 830, working memory 835, operating system 840, application(s) 845, and/or other components of the computer system 800 illustrated in FIG. 8 and described in detail below.
  • FIG. 7 illustrates an embodiment of a UE 105, which can be utilized as described herein above.
  • the UE 105 can be used in the communication system 100 and/or communication system 300 for initiating an emergency call, which may comprise performing one or more of the UE functions described for FIGS. 2, 4 and 5.
  • FIG. 7 is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. It can be noted that, in some instances, components illustrated by FIG.
  • PAN Personal Area Network
  • the UE 105 is shown comprising hardware elements that can be electrically coupled via a bus 705 (or may otherwise be in communication, as appropriate).
  • the hardware elements may include a processing unit(s) 710 which can include without limitation one or more general-purpose processors, one or more special-purpose processors (such as digital signal processing (DSP) chips, graphics acceleration processors, application specific integrated circuits (ASICs), and/or the like), and/or other processing structure or means. As shown in FIG. 7, some embodiments may have a separate DSP 720, depending on desired functionality. Location determination and/or other determinations based on wireless communication may be provided in the processing unit(s) 710 and/or wireless communication interface 730 (discussed below).
  • DSP digital signal processing
  • ASICs application specific integrated circuits
  • the UE 105 also can include one or more input devices 770, which can include without limitation a touch screen, a touch pad, microphone, button(s), dial(s), switch(es), and/or the like; and one or more output devices 715, which can include without limitation a display, light emitting diode (LED), speakers, and/or the like.
  • input devices 770 can include without limitation a touch screen, a touch pad, microphone, button(s), dial(s), switch(es), and/or the like
  • output devices 715 which can include without limitation a display, light emitting diode (LED), speakers, and/or the like.
  • the UE 105 may also include a wireless communication interface 730, which can include without limitation a modem, a network card, an infrared
  • the wireless communication interface 730 may permit data to be exchanged with a network, wireless access points, base stations, other computer systems, and/or any other electronic devices described herein.
  • the communication can be carried out via one or more wireless communication antenna(s) 732 that send and/or receive wireless signals 734.
  • the wireless communication interface 730 can include separate transceivers to communicate with one or more wireless networks using various RATs.
  • the one or more wireless networks can include various network types (e.g. associated with different RATs) such as a CDMA network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal Frequency Division Multiple Access (OFDMA) network, a Single-Carrier Frequency Division Multiple Access (SC-FDMA) network, a WiMax network (IEEE 802.16), a Wireless Local Area Network (WLAN), and so on.
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-Carrier Frequency Division Multiple Access
  • WiMax IEEE 802.16
  • WLAN Wireless Local Area Network
  • a CDMA network may implement one or more radio access technologies (RATs) such as cdma2000, Wideband CDMA (WCDMA), and so on.
  • Cdma2000 includes IS-95, IS- 2000, and/or IS-856 standards.
  • a TDMA network may implement Global System for Mobile Communications (GSM), Digital Advanced Mobile Phone System (D-AMPS), or some other RAT.
  • GSM Global System for Mobile Communications
  • D-AMPS Digital Advanced Mobile Phone System
  • An OFDM A network may employ LTE, LTE Advanced, and so on.
  • LTE, LTE Advanced, GSM, and WCDMA are described in documents from 3GPP.
  • Cdma2000 is described in documents from a consortium named "3rd Generation Partnership Project 2" (3GPP2). 3 GPP and 3GPP2 documents are publicly available.
  • a WLAN may be an IEEE 802.1 lx network (also referred to as WiFi network), a
  • Bluetooth network an IEEE 802.15x network, or some other type of network.
  • the techniques described herein may also be used for any combination of two or more wireless networks or for wireless networks combined with wireline networks.
  • the UE 105 can further include sensor(s) 740.
  • sensors can include, without limitation, one or more accelerometer(s), gyroscope(s), camera(s),
  • sensor(s) 740 can be utilized, among other things, to determine a location and/or sense an emergency condition that may be used to initiate an emergency call and/or emergency SMS message in accordance with the techniques described herein. Some or all of sensor(s) 740 may be attached to, connected to or embedded in a user of UE 105 and may communicate with other components of UE 105 (e.g. wireless communication interface 730) by wireless or wireline means (e.g. using BT or Zigbee).
  • wireless communication interface 730 e.g. using BT or Zigbee
  • Embodiments of the UE 105 may also include an SPS receiver 780 capable of receiving and measuring signals 784 from one or more SPS satellites (e.g., SVs 110 of FIG. 1) using an SPS antenna 782 (e.g. which may or may not be the same as wireless communication antenna(s) 732).
  • SPS receiver 780 may provide SPS location measurements to a location server (e.g. an E-SLP or E-SMLC in serving network 140) to enable a position of the UE 105 to be obtained by the location server or may enable UE 105 (e.g. processing units 710) to obtain the UE 105 location.
  • a location server e.g. an E-SLP or E-SMLC in serving network 140
  • UE 105 e.g. processing units 710
  • Location of UE 105 may assist the techniques described herein and may use conventional location techniques associated with signal measurements for an SPS system or GNSS such as the GPS, Galileo, Glonass, Quasi-Zenith Satellite System (QZSS) over Japan, Indian Regional Navigational Satellite System (IRNSS) over India, Beidou over China, and/or the like.
  • SPS receiver 780 may receive signals from various sources.
  • the SPS receiver 780 may be configured to determine or help determine a location (e.g. latitude and longitude coordinates, and optionally an altitude) for the UE 105, based on measuring SPS signals 784, either by itself or in combination with other elements of the UE 105 such as processing unit(s) 710.
  • the location may be determined periodically (e.g. at 1 or 2 second intervals) and may be included within the emergency SMS sent to a PSAP.
  • the UE 105 may further include and/or be in communication with a memory
  • the memory 760 can include, without limitation, local and/or network accessible storage, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory (“RAM”), and/or a read-only memory
  • ROM read-only memory
  • the memory 760 of the UE 105 also can comprise software elements (not shown in FIG. 7), including an operating system, device drivers, executable libraries, and/or other code, such as one or more application programs, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein.
  • one or more procedures described with respect to the method(s) discussed above may be implemented as code and/or instructions executable by the UE 105 (and/or a processing unit(s) 710 or DSP 720 within UE 105).
  • code and/or instructions can be used to configure and/or adapt a general purpose computer (or other device) to perform one or more operations in accordance with the described methods.
  • FIG. 8 illustrates an embodiment of a computer system 800, which may be utilized and/or incorporated into one or more components of a communication system
  • FIG. 8 provides a schematic illustration of one embodiment of a computer system 800 that can perform the methods provided by various other embodiments, such as the method described in relation to FIGS. 2, 4 and/or 6. It should be noted that FIG. 8 is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. FIG. 8, therefore, broadly illustrates how individual system elements may be implemented in a relatively separated or relatively more integrated manner. In addition, it can be noted that components illustrated by FIG. 8 can be localized to a single device and/or distributed among various networked devices, which may be disposed at different physical or geographical locations.
  • the computer system 800 may correspond to any of P-CSCF 325, E-CSCF 330, IP-SM-GW 360, SMS-GMSC 365, SMS SC 370 or LRF 390 in communication system 300.
  • the computer system 800 is shown comprising hardware elements that can be electrically coupled via a bus 805 (or may otherwise be in communication, as appropriate).
  • the hardware elements may include processing unit(s) 810, which can include without limitation one or more general-purpose processors, one or more special- purpose processors (such as digital signal processing chips, graphics acceleration processors, and/or the like), and/or other processing structure, which can be configured to perform one or more of the methods described herein, including the method described in relation to FIG. 6.
  • the computer system 800 also can include one or more input devices 815, which can include without limitation a mouse, a keyboard, a camera, a microphone, other biometric sensors, and/or the like; and one or more output devices 820, which can include without limitation a display device, a printer, and/or the like.
  • input devices 815 can include without limitation a mouse, a keyboard, a camera, a microphone, other biometric sensors, and/or the like
  • output devices 820 which can include without limitation a display device, a printer, and/or the like.
  • the computer system 800 may further include (and/or be in communication with) one or more non-transitory storage devices 825, which can comprise, without limitation, local and/or network accessible storage, and/or can include, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory (“RAM”), and/or a read-only memory
  • non-transitory storage devices 825 can comprise, without limitation, local and/or network accessible storage, and/or can include, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory (“RAM”), and/or a read-only memory
  • the computer system 800 may also include a communications subsystem 830, which can include support of wireline communication technologies and/or wireless communication technologies managed and controlled by a wireless communication interface 833.
  • the communications subsystem 830 may include a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device, and/or a chipset, and/or the like.
  • the communications subsystem 830 may include one or more input and/or output communication interfaces, such as the wireless communication interface 833, to permit data to be exchanged with a network, mobile devices, other computer systems, and/or any other electronic devices described herein.
  • the terms “mobile device” and “UE” are used interchangeably herein to refer to any mobile communications device such as, but not limited to, mobile phones, smartphones, wearable devices, mobile computing devices (e.g., laptops, PDAs, tablets), embedded modems, and automotive and other vehicular computing devices.
  • the computer system 800 will further comprise a working memory 835, which can include a RAM and/or or ROM device.
  • Software elements shown as being located within the working memory 835, can include an operating system 840, device drivers, executable libraries, and/or other code, such as application(s) 845, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein.
  • application(s) 845 may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein.
  • code and/or instructions may be implemented as code and/or instructions executable by a computer (and/or a processing unit within a computer); in an aspect, then, such code and/or instructions can be used to configure and/or adapt a general purpose computer (or other device) to perform one or more operations in accordance with the described methods.
  • a set of these instructions and/or code might be stored on a non-transitory computer-readable storage medium, such as the storage device(s) 825 described above.
  • the storage medium might be incorporated within a computer system, such as computer system 800.
  • the storage medium might be separate from a computer system (e.g., a removable medium, such as an optical disc), and/or provided in an installation package, such that the storage medium can be used to program, configure, and/or adapt a general purpose computer with the instructions/code stored thereon.
  • These instructions might take the form of executable code, which is executable by the computer system 800 and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computer system 800 (e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc.), then takes the form of executable code.
  • components that can include memory can include non-transitory machine-readable media.
  • machine- readable medium and “computer-readable medium” as used herein, refer to any storage medium that participates in providing data that causes a machine to operate in a specific fashion.
  • various machine-readable media might be involved in providing instructions/code to processing units and/or other device(s) for execution. Additionally or alternatively, the machine-readable media might be used to store and/or carry such instructions/code.
  • a computer- readable medium is a physical and/or tangible storage medium. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media.
  • Computer-readable media include, for example, magnetic and/or optical media, punchcards, papertape, any other physical medium with patterns of holes, a RAM, a PROM, EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read instructions and/or code.
  • a special purpose computer or a similar special purpose electronic computing device is capable of manipulating or transforming signals, typically represented as physical electronic, electrical, or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the special purpose computer or similar special purpose electronic computing device.
  • the term "at least one of if used to associate a list, such as A, B, or C, can be interpreted to mean any combination of A, B, and/or C, such as A, AB, AA, AAB, AABBCCC, etc.
  • A, B, or C can be interpreted to mean any combination of A, B, and/or C, such as A, AB, AA, AAB, AABBCCC, etc.
  • the above elements may merely be a component of a larger system, wherein other rules may take precedence over or otherwise modify the application of the various embodiments.
  • a number of steps may be undertaken before, during, or after the above elements are considered. Accordingly, the above description does not limit the scope of the disclosure.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente invention concerne des techniques permettant à un élément de réseau appartenant à un réseau de desserte différent du réseau domestique d'un équipement utilisateur (UE) d'acheminer un message de service de messages courts (SMS) lié à une urgence, depuis l'UE vers un point de réponse de sécurité publique (PSAP), pendant une situation d'urgence. Les techniques peuvent consister à recevoir une demande d'appel d'urgence ainsi qu'un message SMS provenant de l'UE, à déterminer une adresse de destination pour le message SMS sur la base d'une indication d'urgence et à acheminer le message SMS au PSAP sur la base de l'adresse de destination, ledit acheminement contournant le réseau domestique.
PCT/US2018/033906 2017-08-01 2018-05-22 Élément de réseau permettant un appel d'urgence amélioré par sms WO2019027538A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201715666302A 2017-08-01 2017-08-01
US15/666,302 2017-08-01

Publications (1)

Publication Number Publication Date
WO2019027538A1 true WO2019027538A1 (fr) 2019-02-07

Family

ID=62598045

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/033906 WO2019027538A1 (fr) 2017-08-01 2018-05-22 Élément de réseau permettant un appel d'urgence amélioré par sms

Country Status (1)

Country Link
WO (1) WO2019027538A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR3127860A1 (fr) * 2021-10-04 2023-04-07 Orange Procédé de gestion d’une situation d’urgence et terminal mettant en œuvre ce procédé
WO2023094261A1 (fr) * 2021-11-24 2023-06-01 Telefonaktiebolaget Lm Ericsson (Publ) Prise en charge des sms d'urgence par le plan de contrôle
US12021905B2 (en) 2022-10-19 2024-06-25 T-Mobile Usa, Inc. Reducing IMS network congestion when a node in the IMS network becomes unavailable

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130203373A1 (en) * 2011-08-12 2013-08-08 Qualcomm Incorporated Emergency messaging between citizens and authorities

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130203373A1 (en) * 2011-08-12 2013-08-08 Qualcomm Incorporated Emergency messaging between citizens and authorities

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR3127860A1 (fr) * 2021-10-04 2023-04-07 Orange Procédé de gestion d’une situation d’urgence et terminal mettant en œuvre ce procédé
WO2023057396A1 (fr) * 2021-10-04 2023-04-13 Orange Procédé de gestion d'une situation d'urgence et terminal mettant en œuvre ce procédé
WO2023094261A1 (fr) * 2021-11-24 2023-06-01 Telefonaktiebolaget Lm Ericsson (Publ) Prise en charge des sms d'urgence par le plan de contrôle
US12021905B2 (en) 2022-10-19 2024-06-25 T-Mobile Usa, Inc. Reducing IMS network congestion when a node in the IMS network becomes unavailable

Similar Documents

Publication Publication Date Title
US10567943B2 (en) Methods and systems for handover of an emergency call between different wireless networks
US10085142B2 (en) Location by reference for an over-the-top emergency call
US10165395B2 (en) Methods of supporting location and emergency calls for an over-the-top service provider
US10959078B2 (en) Systems and methods to support distress signaling from a wireless device
EP3105983B1 (fr) Procédés et systèmes permettant de renvoyer un relevé de positionnement précoce
US20130203373A1 (en) Emergency messaging between citizens and authorities
EP3993295B1 (fr) Repli amélioré en mode intrabande pour appel d'urgence
US11812301B2 (en) Methods and systems for segmentation of positioning protocol messages
US10645563B2 (en) Generating location information for an e911 call
WO2019027538A1 (fr) Élément de réseau permettant un appel d'urgence amélioré par sms
US20120289181A1 (en) In-vehicle emergency call service registration and call setup using follow-on request
US20180249283A1 (en) Control plane lcs solution for improving multiple reporting lpp messaging
WO2019027537A1 (fr) Équipement utilisateur permettant un appel d'urgence amélioré par sms

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

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

Country of ref document: EP

Kind code of ref document: A1