Source: https://patents.google.com/patent/US9814082B2/en
Timestamp: 2018-07-20 17:16:19
Document Index: 418042981

Matched Legal Cases: ['Application No. 61', 'Application No. 61', 'art 1', 'art 2', 'art 3', 'art 4', 'Application No. 09759257', 'Application No. 15156206', 'Application No. 12172479', 'Application No. 12177729', 'Application No. 13162547', 'Application No. 13162615', 'Application No. 15156206', 'Application No. 200980130796', 'Application No. 7721']

US9814082B2 - System and method for managing emergency requests - Google Patents
System and method for managing emergency requests Download PDF
US9814082B2
US9814082B2 US15253036 US201615253036A US9814082B2 US 9814082 B2 US9814082 B2 US 9814082B2 US 15253036 US15253036 US 15253036 US 201615253036 A US201615253036 A US 201615253036A US 9814082 B2 US9814082 B2 US 9814082B2
US15253036
US20160374117A1 (en )
A network component is provided. The network component including a component configured such that the network transmits a response message containing an indicator indicating that a first message is an emergency-related request, and such that the network receives a second message containing information associated with a user equipment (UE).
This application is a continuation of U.S. patent application Ser. No. 14/968,686 filed on Dec. 14, 2015, which is a continuation of U.S. patent application Ser. No. 12/937,199 filed on Jan. 13, 2011, which is a filing under 35 U.S.C. 371 of International Application No. PCT/US2009/045990 filed Jun. 2, 2009, entitled “System and Method for Managing Emergency Requests” claiming priority to U.S. patent application Ser. No. 12/131,785 filed on Jun. 2, 2008, and claiming priority to U.S. Provisional Application No. 61/061,507 filed on Jun. 13, 2008, and claiming priority to U.S. Provisional Application No. 61/081,576 filed on Jul. 17, 2008 which these applications are incorporated by reference herein in their entirety.
In an embodiment, a user equipment is provided. The user equipment including a component, such that responsive to making an emergency request that is rejected, the component configured to receive a message containing information associating the emergency request with a combined emergency centre.
In another embodiment, a network component is provided that includes a component, such that upon receiving an emergency request from a user equipment, the component configured to determine whether the emergency request is related to a combined emergency centre and to send the user equipment a message containing information identifying that the emergency request is related to a combined emergency centre.
In the event the PSAP callback or emergency call signaling response is received over a Circuit Switched network, the solution can allow for mapping between appropriate Calling-Party-Category fields which is sometimes used to carry the indication of an emergency call in ISUP/TUP (ISDN User Part/Telephone User Part) based systems. Typically, the ISUP/TUP signaling information does not allow for a granularity as fine as the emergency urn:service:sos identifiers defined in RFC 5031.
Policy / Preference set
Consult preference / policy
Not allowed determine if
Token received ascertain authenticity of
token and if valid provide
Token received, fake, provide indication to
network fake token received, provide
0—UE provides emergency information.
Before the emergency request reaches the PSAP 130, it might be handled by one or more components in the IMS network 120. Examples of such components are the P-CSCF, E-CSCF, AS, and IBCF (Interconnect Border Control Function). An IMS network component, such as P-CSCF, AS, and E-CSCF, can inspect all requests in order to determine if they are related to emergencies. If a request is determined to relate to an emergency, based on configurations and regulator policies, the network component can determine to reject the request or update the request or include the emergency call indicator 160 in a SIP response that is sent to the UE 110. Updating the request might be done if the UE provides a T-GRUU and the network operator policy settings (e.g., in the P-CSCF) indicate that the public user identities must be provided. In such a case, the T-GRUU can be replaced with the GRUU. In addition, updating of messages to be routed to PSAPs might be done if the message contains P-Preferred-Service header fields, P-Asserted-Service header fields, Accept-Contact header fields containing one or more IMS Communication Service Identifier (ICSI) values (coded as specified in subclause 7.2A.8.2 in 3GPP TS 24.229) or one or more IMS Application Reference Identifier (IARI) values (coded as specified in subclause 7.2A.9.2 in 3GPP TS 24.229) that are related to the request in a g.3gpp.app_ref feature tag. Note that the network element can be in Back to Back User Agent (B2BUA) or proxy role when updating these SIP requests or responses. Note that if the network element is an AS, there is a need for a new reference point between the AS and at least one of IBCF, E-CSCF or P-CSCF as at the moment there is only a service control reference point between AS and S-SCSF or I-CSF. The P-Preferred-Service header fields, P-Asserted-Service header fields should not be forwarded to the PSAP or emergency centre. The Accept-Contact header fields should be groomed for ICSI values and IARI values as they may cause interactions when selecting a SIP user agent terminating the session at the PSAP. If the Accept-Contact header field contains g.3gpp.app_ref media feature tags, they and their values shall be removed. If the Accept-Contact header field contains g.3gpp.app_ref media feature IARII tags, they and their values can be removed.
In other words, what is termed “updating” can include changing the GRUU from a temporary GRUU into a public GRUU. This is done because a temporary GRUU is invalid if the UE is disconnected and has to reregister. A PSAP cannot make a callback to a temporary GRUU after the UE de-registers and re-registers. Public GRUUs, on the other hand, have the property that they are routable even after the UE de-registers and re-registers (making a PSAP callback to that public GRUU more likely to complete). “Updating” can also include not propagating of ICSI or IARI feature tags, P-Preferred-Service header fields, and/or P-Asserted-Service header fields. The presence of such tags or fields might skew the handling of the request at the PSAP and cause the request to be routed based on services supported on the UE rather than, for example, on geographical proximity and type of service requested. Since there is typically not an S-SCSF and not a (MultiMedia Telephony) Application Server in the session path between the UE, the P-CSCF, the E-CSCF, and the PSAP, these services the UE supports are typically not available during the emergency call. So signaling it as part of an emergency request (even when the UE did not realize it is an emergency request and includes ICSI or IARI feature tags, P-Preferred-Service header fields, and/or P-Asserted-Service header fields because it believes the request it makes is a normal request) does not serve any purpose and may only detract/result in routing the requests to other PSAPs or PSAP User Agents than those determined based on location, requested type of service, and RFC 3261 procedures. In a worst case scenario, if a PSAP User Agent registers its support for said services, it may receive a higher load of emergency service requests than other PSAP User Agents, possibly leading to delay in the emergency response.
Two examples can illustrate cases where the network rejects the request because the type of emergency session request is not supported. In the first example, RFC 5031 defines urn:service:sos.aninmal-control as follows: Animal control typically enforces laws and ordinances pertaining to animal control and management, investigates cases of animal abuse, educates the community in responsible pet ownership and wildlife care, and provides for the housing and care of homeless animals, among other animal-related services. In some jurisdictions, a request to urn:service:sos.aninmal-control may not be classified as an emergency in the sense that it is subjected to network and operator emergency procedures (e.g. allow or disallow a request to urn:service:sos.aninmal-control when the UE didn't register or has insufficient credentials). If so configured, the network could either reject with an indication that the call is not actually an emergency or it could reject with an indication that the call is not an emergency and offer alternative steps to be executed such as offering a different URI to contact and/or a different Circuit Switched (CS) network address such as a digit string. Note that, since emergency service URNs are not routable and are not E.164 numbers, the UE may not be able to proceed lacking knowledge of routable addresses or numbers. In those jurisdictions, it would be inappropriate if the UE executed emergency procedures (as specified in 3GPP TS 24.008) and a UE should not automatically contact, for example, “911” or “112”” upon receiving a rejection when contacting, e.g., urn:service:sos.aninmal-control.
TABLE 10.5.135d
3GPP TS 24.008: Service Category information element
Bits 6, 7, 8 are spare and set to ″0″
Mobile station may set one or more bits to ″1″
If more than one bit is set to ″1″, routing to a combined Emergency
centre (e.g. ambulance and fire brigade in Japan) is required. If the
MSC can not match the received service category to any of the
emergency centres, it shall route the call to an operator defined
default emergency centre.
If no bit is set to ″1″, the MSC shall route the Emergency call to an
However, at present no mapping for urn:service:sos.animal-control exists. A mapping for some other emergency services as defined in RFC 5031 (e.g. urn:service:sos.police) can be made by setting the corresponding bit in Emergency Category Value (e.g. urn:service:sos.police maps to Bit 1 of the Emergency Service Category Value, urn:service:sos.ambulance maps to Bit 2 of the Emergency Service Category Value, urn:service:sos.fire maps to Bit 3 of the Emergency Service Category Value, urn:service:sos.marine maps to Bit 4 of the Emergency Service Category Value, urn:service:sos.mountian maps to Bit 5 of the Emergency Service Category Value). urn:service:sos.animal-control, urn:service:sos.physician, urn:service:sos.poison, urn:service:sos.gas, and others could map to an Emergency Service Category Value with no bits set “1”, causing the call to be routed to an operator-defined default emergency centre. Alternatively, for requests for which no PSAP is supported in the network, the UE could be instructed to make a normal SIP request (using procedures in 3GPP TS 24.228) or setup a normal CS call (using procedures in 3GPP TS 24.008). The network could accomplish such by not indicating an alternative address that cannot be mapped to an Emergency Service Category Value (i.e. not one of the urn:service:sos URNs for which a mapping is standardized). When an emergency request is received by the PSAP but the PSAP cannot handle the request and returns a SIP 380 or a similar message, if a mapping exists on the UE from the given URN to an Emergency Service Category Value, a call shall be setup to that CS PSAP E.164 number automatically.
In some cases, the network might reject a request made to a regular emergency center or perhaps a combined PSAP or a combined emergency centre, where a combined PSAP or a combined emergency centre is a PSAP that accepts calls for multiple types of emergencies. For example, a combined PSAP or a combined emergency centre might accept calls for police emergencies, fire emergencies, ambulance emergencies, and other types of emergencies. A request made to a combined emergency centre might include bits, flags or other indicators (such as a PSAP address (e.g., “119” in some countries) or part of an PSAP address) that specify the emergency response entities to which the request should be routed. For example, if a request is made for fire service and ambulance service, the request might include a “fire” flag and an “ambulance” flag. Upon reading these tags, the combined emergency centre can route the request to the appropriate emergency response entities.
In an embodiment, a UE might send a request to an emergency center or perhaps combined emergency centre and the UE is not aware that the request is related to an emergency center and for various reasons the network rejects or otherwise does not process the request. In this case, the network might identify the request as related to a combined emergency centre. The network then sends a message to the UE containing information identifying that the request relates to a combined emergency centre. The UE might then use this information to send the request to a combined emergency centre or combined PSAP or other alternate emergency centre or PSAP. In some embodiments, the alternate PSAP is in the circuit switched domain. The information in the message that the network sends to the UE can include information identifying the combined emergency centre, bits, flags or other indicators that specify the emergency response entities to which the original request was routed. Upon receiving this message, the UE can send an alternate request to the alternate or combined PSAP and can include the bits, flags or other indicators so that the alternate PSAP can route the alternate request to the appropriate emergency response entities. The bits, flags or other indicators may be the bits specified in Table 10.5.135d in 3GPP TS 24.008.
More specifically, a network element such as a P-CSCF verifies if the requests that it receives contain emergency service identifiers. The P-CSCF may determine that a proper emergency call request was made but that the local network does not support the requested emergency PSAP (e.g., a request to urn:service:sos.gas was made). The P-CSCF may also determine that the UE failed to recognize the request as an emergency call request. The P-CSCF can then be configured to reject the request and provide sufficient information for the UE to route the request to an alternate answering point since the UE user is of the impression it is reporting a situation that requires attention. However, a PSAP/emergency centre for that type of emergency is not supported in the network.
Today, in the CS network, Service Categories have been allocated for Police, Ambulance, Fire Brigade, Marine Guard and Mountain Rescue. However, in the event a 380 (Alternative Service) is returned by the P-CSCF, one of the options the UE has is to initiate an emergency call in the CS domain using appropriate access technology specific procedures. However, the UE, upon receiving the 380, still does not know if the original request with the emergency service identifier that was not recognized by the UE was destined for a default PSAP, Police PSAP, Ambulance PSAP, Fire Brigade PSAP, combined PSAP, etc.
In an embodiment, in the event the P-CSCF has been configured to recognize the request as for a particular type of emergency, then the P-CSCF informs the UE that the request was for that type of emergency. In addition, if the P-CSCF rejects the request because the requested emergency type is not supported, the P-CSCF can provide additional information. The UE can be enhanced to handle 380 (Alternative Service) messages for unrecognized emergency requests to particular PSAPs. When attempting to connect to a particular PSAP using the CS Domain, a mapping to the correct Emergency Category Value (see 3GPP TS 24.008, subclause 10.5.4.33) can be made. The P-CSCF can be enhanced to reject emergency service requests to unsupported PSAPs, e.g., urn:service:sos.gas, based on local policy.
The following is an example of an XML body indicating to the UE that an emergency service request was detected and instructing the UE to connect to the determined PSAP.
<ims-3gpp version=“...”>
<type alternate=“
tel:119;phone-context=+81
urn:service:sos.fire-urn:service:sos.ambulance”>
<emergency/>
Previous proposals mentioned signaling recognition by the IMS network of a request to a combined emergency centre and mapping from the signaled value representing a combined emergency centre to one or more bits presented in Table 10.5.135d in 3GPP TS 24.008. 3GPP TS 24.008 is GSM/UMTS specification, and GSM/UMTS supports different regular Setup vs. Emergency Set-up (i.e., without dialed digits). In CDMA, from “IS-2000 release A” onwards, there is also a field called GLOBAL_EMERGENCY_CALL that can be included in an Origination message to make such a call independent of a dialed string. The protocol revision level that supports this is 7 and up. Earlier UEs, with a “protocol revision level currently in use is less than 7”, do not distinguish between emergency and normal calls. Thus, such UEs might have to map, say, “tel:119;phone-context=+81” to 119 and dial 119 as a normal call.
Also, CDMA does not support routing to Combined Emergency Centres or Specialized Emergency Centres (e.g., for “police” only). 3GPP2 only documents how to route to default PSAPs. Thus, in an alternative embodiment, a CDMA UE detects that the IMS network has determined that the original request to the IMS network was for a non-default PSAP. The CDMA UE might then, rather than sending an emergency call with GLOBAL_EMERGENCY_CALL set to “1” (rather than routing to the default PSAP), support one or more of the following: an emergency call with Global_Emergency set to “1” and in the address field a phone number: say 119, if “the protocol revision level currently in use is NOT less than 7”; an emergency call with Global_Emergency set to “0” and in the address field a phone number: say 119, if “the protocol revision level currently in use is NOT less than 7”; and/or an emergency call with in the address field a phone number: say 119, if “the protocol revision level currently in use is less than 7”.
Current proposals add an “alternate attribute” to the existing XML Schema. In an embodiment, the alternate attribute includes a number of alternative addresses, one of which (the last element) could be an indicator encoding the need to route the call to a combined emergency centre by ‘dashing’ together emergency service URNs: e.g. “Urn:service:sos.ambulance-Urn:service:sos.fire”. Alternative embodiments could encode the alternative addresses differently in the SIP response, e.g., in the Contact header fields or in a separate, new XML body. Another alternative could be a different encoding such that the indicator would still be a URN or tel URI or SIP URI. For example, urn:service:sos.fire.ambulance (e.g., ‘dotting’ together the emergency sub types).
An emergency number might be interpreted in different ways in different countries. For example, the address “119” might translate to policy+marine in one country and fire+ambulance in another. If both countries have operators that are roaming partners with the home network of a roaming user, the UE or the network needs to recognize the address as an emergency request, but the network might not know which 119 translation is intended. In an embodiment, in such a situation, the network selects one of the translations after further interaction with the UE.
Such further interaction includes, for example, the network sending information to the UE indicating that the address is associated with different emergency types in different jurisdictions. Such information includes a mapping between the address, a phone context and one or more optional emergency identifier types and is known as alternate address information. An emergency identifier type is optional where the phone context does not map to an emergency type but non “emergency” or “urgent” alternatives are known.
Alternate address information comprises a mapping between an address, a phone context and one or more optional emergency identifier types. The address indicates the emergency number dialed which could be a telephone number such as ‘119’ for example. The phone context indicates a relevant condition of the UE, such as the location or country the UE is in, and could be a number or a string such as ‘+81’, the textual string ‘Japan’, a combination of a number and a string or other information that can be resolved to a location, for example. The textual string (e.g. ‘Japan’) can be received in multiple languages and multiple character encodings, including Japanese and other non ASCII character sets. The emergency identifier type (e.g. ‘police’, ‘fire’ or ‘ambulance’ for example) is extendible and indicates the type of emergency service associated with the address for a given phone context. The country or region where the emergency services apply can be identified using applicable ITU, IANA, ISO codes, however, in some cases certain emergency services are provided in an area not coinciding with a “country” or region, in which case a standard ITU, IANA, ISO code might not have been allocated. Some ITI, IANA, ISO or other codes applicable for encoding locations, countries or regions are extendible, such as ISO 3166-1, and the ISO 3166/MA.
Alternate address information may additionally contain a reason element, such as a <reason> XML element (as described in e.g. 3GPP IMS XML body as defined in 3GPP TS 24.229) for example. A reason element is populated with information that can be presented to a user of a UE to identify, for example, the location, the emergency service types supported and/or the emergency service numbers. Such a reason element could be transmitted in an enhanced application/3gpp-ims+xml body (as defined in 3GPP TS 24.229). The contents of a reason element can be specified in multiple languages, using the xml:lang attribute. For example, a reason element can be represented by the following body (which corresponds to an enhanced XML Schema in 3GPP TS 24.229).
<ims-3gpp version=“2”>
<type><emergency/></type>
<reason lang=“en”>emergency</reason>
<reason lang=“nl”>noodgeval</reason>
The network sends such alternate address information to the UE, for example, as part of the body of a SIP 300 (Multiple Choices) response, in one or more Contact field headers of the SIP 300 (Multiple Choices) response or in another SIP 3xx response (e.g. a SIP 380 (Alternative Service) response).
The following is an example of an XML body included in a response to a request for an emergency service indicating to the UE that an address (‘119’ for example) is associated with a different, or a combination of, emergency types (‘fire’, ‘ambulance’ or ‘police’ for example) in different phone contexts (‘+81’ for example). Note that the emergency types are derived from RFC 5031's emergency service URN (i.e. urn:service:sos and its subtypes, police, ambulance, gas, fire, etc., where <police/> can map to urn:service:sos.police, etc.) Note that the emergency type <sos/> can map to the generic service URN urn:service:sos. Note that <sos/> can map to the dial string “112” or to a GSM/UMTS CS domain emergency call setup with all Emergency Service Category Value bits set to ‘0’ (see Table 10.5.135d/3GPP TS 24.008: Service Category information element) such that the call is routed to an operator defined default emergency centre or equivalent signaling in other CS domain technologies such as CDMA. Note that <police/> could also map to setting bit 1 of the Emergency Service Category Value when making a GSM/UMTS emergency call over the CS domain.
<alternativeURI>tel:112;phone-context=+57</alternativeURI>
<sos/>
<alternativeURI>tel:123;phone-context=+57</alternativeURI>
<ambulance/>
<fire/>
<police/>
<alternativeURI>tel:119;phone-context=+81</alternativeURI>
<alternativeURI>tel:119;phone-context=+82</alternativeURI>
<alternativeURI>tel:119;phone-
context=+886</alternativeURI>
<alternativeURI>tel:119;phone-context=+94</alternativeURI>
context=+1876</alternativeURI>
<alternativeURI>tel:119;phone-context=+57</alternativeURI>
<alternativeURI>tel:119;phone-context=+86</alternativeURI>
<alternativeURI>tel:119;phone-context=+62</alternativeURI>
<alternativeURI>tel:118;phone-context=+62</alternativeURI>
The above exemplary XML body indicates that the address ‘119’ can be translated to a different emergency type in a different jurisdiction. For example, the address ‘119’ is associated with ‘fire’ and ‘ambulance’ emergency services when the UE is in a jurisdiction having a phone context of ‘+81’ (Japan) or ‘+82’ (Korea). The address ‘119’ is alternatively associated with ‘police’ emergency services when the UE is in a jurisdiction having a phone context of ‘+94’ (Sri Lanka).
If a country code or location code is included in an emergency service request which can be mapped to multiple emergency service types, it is assumed that the handset specifically intends for the request to be routed to the emergency service type associated to the emergency service address in the indicated country or region.
In another embodiment, the UE or network are configured to select or reduce the alternatives in the response and to remove some of the less probable possibilities. Such selection or reduction can be achieved based on the current network of a UE, the home network of the UE, the nationality of the user of the UE, or past travel plans of the user of the UE for example. A UE which performs selection or reduction, could include a policy which hard codes a mapping between an address, an emergency type and phone context, thereby enabling the UE to explicitly select the intended emergency type when making an emergency call over the CS domain or PS domain. On the PS domain, an emergency type can be either indicated per a RFC 5031 URN or per a TEL URL including a country or region indicator such as ‘phone context’. An emergency type selection function on the UE could be further enhanced if the UE is aware of the country or region it is in and if a locally stored or received mapping of emergency types, location indicators and emergency call addresses is present. The emergency type selection function could then determine that that in certain countries or regions a certain mapping does or does NOT apply, or the mapping applies universally (e.g. for UMTS/GSM handsets the number “112” can map to a GSM/UMTS CS domain emergency call setup with all Emergency Service Category Value bits set to ‘0’ (see Table 10.5.135d/3GPP TS 24.008: Service Category information element)).
Such further interaction between the network and the UE to select a translation also includes, for example, placing choices for the translation in a textual field to be displayed on the UE (such as the <reason> element in the 3GPP IMS XML body). The UE user could then select one of the choices, the selection could be transmitted to the network, and the network could translate the emergency number based on the selection. Alternatively, the network could make the selection in the following order: map the address (e.g., 119) as defined in the home network; if the address is not defined in the home network, map the address as defined in the current visited network, if the address is not defined in the current visited network, map the address as defined for roaming partners or route the call to the default or most capable PSAP. Alternatively, the request can always be routed to the default or most capable PSAP.
A similar problem can occur for the UE when it attempts to recognize the dialed address as an emergency identifier. In an embodiment, the UE is configured with one translation to prevent this problem from occurring. Alternatively, the UE can interact with the user to select a desired translation. Alternatively, the UE can be configured to route the call to the default or most capable PSAP. Alternatively, the UE could route the call based on the network it is attached to and could map the digits according to that network's rules. The UE could also interact with the network and use any advice it gets.
shall assume that the UE supports version 1 of the XML Schema for the IM CN subsystem XML, body if support for the 3GPP IMS XML body in the Accept header is not indicated; and
NOTE 1a: “sip:911@example.com;user=phone” could be an alternate emergency service URI. “urn:service:sos animal-control” could be an unsupported type of emergency call.
In an embodiment, a method for a network component to handle requests sent to the network component is provided. The network component inspects requests sent to the network component to determine if the requests are related to emergencies, and if one of the requests is determined to relate to an emergency, the network component updates the request.
When the request is determined to relate to an emergency, the network component is alternatively configured, based on configurations and regulator policies, to perform one of: accepting the request; accepting the request and including an emergency call indicator in a Session Initiation Protocol (SIP) response sent to a user equipment (UE) that initiated the request; not accepting the request by rejecting the request; not accepting the request and indicating alternative contact information for an emergency response center to which the request was directed.
In an embodiment, a SIP (Session Initiated Protocol) response is sent to the UE in response to the UE making a call that the UE is unaware is an emergency call.
If a globally routable user agent uniform resource identifier (GRUU) is associated with the UE, and if the GRUU is a temporary GRUU, the temporary GRUU is replaced with a non-temporary GRUU. The temporary GRUU might be replaced with the non-temporary GRUU only when a request is not made to keep the GRUU private.
If an IMS Communication Service Identifier (ICSI) or an IMS Application Reference Identifier (IARI) is present, before the Request is routed to a PSAP or emergency centre, the network component performs at least one of: removing P-Preferred-Service header fields; removing P-Asserted-Service header fields; removing ICSI feature tags and tag values from the Accept-Contact header fields; and removing IARI feature tags and tag values from the Accept-Contact header fields.
When the network component does not accept the request, the network component responds with one of a 300 (Multiple Choices) message, a 301 (Moved Permanently) message, a 302 (Moved Temporarily) message, a SIP 4xx response, a SIP 6xx response, a SIP 380 (Alternative Service) response.
In an embodiment, the network component does not accept the request due to at least one of: the network not being able to handle emergency sessions; an internet multimedia core network subsystem to which the network component belongs not being able to handle emergency sessions; the network not handling emergency sessions due to local policy; the network only handling certain types of emergency session requests; the UE roaming; the network component being in a different network than the UE's home operator's network; and the network not supporting emergency sessions for one of the geographical location where the UE is located and the Internet Protocol Connectivity Access Network to which the UE is attached.
In an embodiment, the network component includes a configurable list with local and roaming partners' emergency service identifiers that indicate on a per emergency service identifier basis the handling of requests. When the network component does not accept the request, a configurable list of alternate emergency service identifiers is sent to the UE. The at least one alternative emergency service URI might be presented to the user of the UE.
In an embodiment, the network component, rather than not accepting the request for an unsupported emergency service type, prepares the request for forwarding to the UE's home network. The UE's home network might be configured to handle the URI value associated with the request.
In an embodiment, the network component is a proxy call session control function (P-CSCF).
In an embodiment, the requests comprise initial SIP requests for a dialog, standalone SIP transactions, unknown SIP methods.
In an alternative embodiment, a user equipment is provided. The user equipment comprises a component, such that responsive to making an emergency request that is rejected, the component is configured to receive a message containing information associating the emergency request with a combined emergency centre. The component may be further configured to use the information to make a subsequent emergency request to the combined emergency centre.
In an alternative embodiment, a network component is provided. The network component comprises a component, such that upon receiving an emergency request from a user equipment, the component is configured to determine whether the emergency request is related to a combined emergency centre and to send the user equipment a message containing information identifying that the emergency request is related to a combined emergency centre.
In an alternative embodiment, a user equipment is provided. The user equipment comprises a component configured to receive a reject message containing alternate address information associating an emergency request with a plurality of emergency centres, non-emergency centres, or combined emergency centres. The alternate address information can be used to determine to which one of the plurality of centres an emergency call should be routed.
In an alternative embodiment, a network component is provided. The network component comprises a component configured to determine whether a received request is an emergency request and whether the received request is related to one or more specific emergency centres, combined emergency centres, or non-emergency centres and to send a rejection response containing alternate address information. The alternate address information can comprise a mapping between the received request, a phone context and one or more optional emergency identifier types.
The following 3rd Generation Partnership Project (3GPP) Technical Specifications (TS) are incorporated herein by reference: TS 24.229 V7.8.0 (2007-12) and TS 24.008.
a network component that is part of a trust domain configured to:
receive from a user equipment (“UE”) a Session Initiation Protocol (“SIP”) request message for a dialog that is an emergency-related request;
update header information of the SIP request message for a dialog;
forward the SIP request message for a dialog toward a Public Safety Answering Point (“PSAP”);
send to the UE a SIP response message containing a P-Asserted-Identity header field in response to the SIP request message, the P-Asserted-Identity header field comprising an emergency number, the SIP response message indicating that the SIP request message for a dialog, sent by the UE, is an emergency-related request and that the UE should include location information in a response to the SIP response message; and
receive from the UE, in response to the SIP response message, a SIP request message within the dialog, the SIP request message within the dialog containing emergency-related information comprises a UE location.
2. The apparatus of claim 1, wherein the emergency-related information associated with the UE contained in the SIP request message within the dialog comprises a UE identity.
3. The apparatus of claim 1, wherein the emergency-related information associated with the UE contained in the SIP request message within the dialog comprises UE access network information.
4. The apparatus of claim 1, wherein the network component is an E-CSCF (emergency call session control function).
5. The apparatus of claim 1, wherein the SIP response message is one of a SIP 1xx or 200 (OK) response.
6. The apparatus of claim 1, wherein a message body of the SIP request message within the dialog includes geographical location information of the UE as a PIDF location object.
7. The apparatus of claim 1, wherein a contact header field of the SIP request message within the dialog includes a public GRUU value associated with a public user identity.
8. The apparatus of claim 1, wherein the emergency-related information associated with the UE is not contained in the SIP request message for a dialog.
9. The apparatus of claim 1, wherein the SIP request message within the dialog is one of:
10. The apparatus of claim 1, wherein the SIP request message for a dialog is a SIP INVITE request.
11. The apparatus of claim 2, wherein the UE identity is a globally routable user agent uniform resource identifier (GRUU).
12. The apparatus of claim 1, wherein a geolocation header field of the SIP request message within the dialog includes a URI (Uniform Resource Identifier) that points to the UE location.
13. The apparatus of claim 3, wherein the UE access network information is included in a P-Access-Network-Info header field in the SIP request message within the dialog and comprises one of a location identifier, a cell identifier or an identity of an WLAN access node.
14. A method for a network component that is part of a trust domain to manage emergency-related information, comprising:
receiving from a user equipment (“UE”) a Session Initiation Protocol (“SIP”) request message for a dialog that is an emergency-related request;
updating header information of the SIP request message for a dialog;
forwarding the SIP request message for a dialog toward a Public Safety Answering Point (“PSAP”);
sending from the network component to the UE a SIP response message containing a P-Asserted-Identity header field in response to the SIP request message, the P-Asserted-Identity header field comprising an emergency number, the SIP response message indicating that the SIP request message for a dialog, sent by the UE, is an emergency-related request and that the UE should include location information in a response to the SIP response message; and
receiving from the UE, in response to the SIP response message, a SIP request message within the dialog, the SIP request message within the dialog containing emergency-related information comprises a UE location.
15. The method of claim 14, wherein the emergency-related information associated with the UE contained in the SIP request message within the dialog comprises a UE identity.
16. The method of claim 14, wherein the emergency-related information associated with the UE contained in the SIP request message within the dialog comprises UE access network information.
17. The method of claim 14, wherein the network component is an E-CSCF (emergency call session control function).
18. The method of claim 14, wherein the SIP response message is one of a SIP 1xx or 200 (OK) response.
19. The method of claim 14, wherein a message body of the SIP request message within the dialog includes geographical location information of the UE as a PIDF location object.
20. The method of claim 14, wherein a contact header field of the SIP request message within the dialog includes a public GRUU value associated with a public user identity.
21. The method of claim 14, wherein the emergency-related information associated with the UE is not contained in the SIP request message for a dialog.
22. The method of claim 14, wherein the SIP request message within the dialog is one of:
23. The method of claim 14, wherein the SIP request message for a dialog is a SIP INVITE request.
24. The method of claim 15, wherein the UE identity is a globally routable user agent uniform resource identifier (GRUU).
25. The method of claim 14, wherein a geolocation header field of the SIP request message within the dialog includes a URI (Uniform Resource Identifier) that points to the UE location.
26. The method of claim 16, wherein the UE access network information is included in a P-Access-Network-Info header field in the SIP request message within the dialog and comprises one of a location identifier, a cell identifier or an identity of an WLAN access node.
27. A tangible, non-transitory, computer readable medium storing computer readable instructions executable by a processor of a network component that is part of a trust domain to cause said network component to implement the method of:
US15253036 2008-06-02 2016-08-31 System and method for managing emergency requests Active US9814082B2 (en)
US12131785 US8478226B2 (en) 2008-06-02 2008-06-02 Updating a request related to an IMS emergency session
US6150708 true 2008-06-13 2008-06-13
US8157608 true 2008-07-17 2008-07-17
PCT/US2009/045990 WO2009149096A1 (en) 2008-06-02 2009-06-02 System and method for managing emergency requests
US93719911 true 2011-01-13 2011-01-13
US14968686 US9462616B2 (en) 2008-06-02 2015-12-14 System and method for managing emergency requests
US15253036 US9814082B2 (en) 2008-06-02 2016-08-31 System and method for managing emergency requests
US15789586 US20180042055A1 (en) 2008-06-02 2017-10-20 System and Method for Managing Emergency Requests
US14968686 Continuation US9462616B2 (en) 2008-06-02 2015-12-14 System and method for managing emergency requests
US15789586 Continuation US20180042055A1 (en) 2008-06-02 2017-10-20 System and Method for Managing Emergency Requests
US20160374117A1 true US20160374117A1 (en) 2016-12-22
US9814082B2 true US9814082B2 (en) 2017-11-07
ID=40972853
US14968686 Active US9462616B2 (en) 2008-06-02 2015-12-14 System and method for managing emergency requests
US15253036 Active US9814082B2 (en) 2008-06-02 2016-08-31 System and method for managing emergency requests
US15789586 Pending US20180042055A1 (en) 2008-06-02 2017-10-20 System and Method for Managing Emergency Requests
US (3) US9462616B2 (en)
EP (1) EP2260633B1 (en)
JP (1) JP5244969B2 (en)
KR (1) KR101281844B1 (en)
CN (1) CN102113293B (en)
CA (1) CA2726627C (en)
ES (2) ES2393301T3 (en)
WO (1) WO2009149096A1 (en)
US20150078208A1 (en) * 2013-09-16 2015-03-19 Blackberry Limited System and Method for Maintaining Privacy Applied to Communications Caused by an Emergency
US9894504B2 (en) * 2015-11-30 2018-02-13 Verizon Patent And Licensing Inc. Emergency call support for VoLTE roaming within S8 home routing architecture
WO2003094563A1 (en) 2002-05-06 2003-11-13 Nokia Corporation System and method for handling sessions of specific type in communication networks
US20070260739A1 (en) 2006-05-02 2007-11-08 Adrian Buckley Apparatus, and associated method, for generating and transmitting an anonymous routing identifier to identify user agent
CN101132623A (en) 2006-08-25 2008-02-27 华为技术有限公司 Emergency business processing method and communication network
US20080267171A1 (en) 2007-04-25 2008-10-30 Research In Motion Limited Methods and apparatus for obtaining variable call parameters suitable for use in originating a sip call via a circuit-switched network from a user equipment device
JP2004535645A (en) 2001-04-27 2004-11-25 ノキア コーポレイション Method and system for handling emergency sessions network identification
JP2005525030A (en) 2002-05-06 2005-08-18 ノキア コーポレイション System and method handling a session of a specific type in a communication network
JP2007172625A (en) 2005-12-21 2007-07-05 Internatl Business Mach Corp <Ibm> Method and system for allowing session initiating user to select one or more privacy settings to be applied to instant messaging session from among multiple possible privacy controls
JP2009535944A (en) 2006-04-28 2009-10-01 クゥアルコム・インコーポレイテッドＱｕａｌｃｏｍｍ Ｉｎｃｏｒｐｏｒａｔｅｄ Voip system and method for supporting voice call continuity on emergency call
WO2007127991A2 (en) 2006-04-28 2007-11-08 Qualcomm Incorporated System and method for supporting voice call continuity for voip emergency calls
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Prot", 3GPP STANDARD; 3GPP TS 24.403, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V1.8.1, 3GPP TS 24.403, 1 December 2007 (2007-12-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 96, XP050365362
"AII-IP Network Emergency Call Support," 3GPP2, 3GPP2 X. P0049-0, Version 1.0, Nov. 7, 2007, pp. 1-68, XP06210045, retrieved from the Internet: URL:http://ftp.3gpp2.org/TSGX/Working/2007/TSG-X-2007-11-Osaka/TR45.2-2007-11-Osaka/452-20071108-19TIA-1111ballot/ [retrieved on Nov. 7, 2007], paragraphs [7.2.1], [8.1.2], [08.3], [08.6].
"Presence Information Data Format (PIDF)," Internet Engineering Task Force (IETF) Network Working Group, Request for Comments: 3863, pp. 1-28, Aug. 2004, [retrieved on Dec. 19, 2012 from: http://tools.ietf.org/html/rfc3863].
"Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)," Internet Engineering Task Force (IETF) Network Working Group, Request for Comments: 3455, pp. 1-34, Jan. 2003.
"SIP: Session Initiation Protocol," Internet Engineering Task Force (IETF) Network Working Group, Request for Comments: 3261, pp. 1-269, Jun. 2002, [retrieved on Dec. 19, 2012 from: http://tools.ietf.org/html/rfc3261].
3GPP ETSI TS 124 008, Apr. 2008, version 7.11.0, pp. 1-551.
3GPP TS 24.229 V7.11.0, Technical Specification Group Core Network and Terminals, IP Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), Stage 3, Release 7, Mar. 2008, 434 pages.
3GPP TS 24.229 V7.11.0, Technical Specification Group Core Network and Terminals, IP Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), Stage 3, Release 7, Section 5.1.2A, Mar. 2008, pp. 1-15 and 49-53.
3GPP TS 24.229 V8.3.0 Release 8, ETSI TS 124 229 v8.3.0, Digital Cellular Telecommunications System (Phase 2+): Universal Mobile Telecommunications System (UMTS), Internet Protocol (IP) Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), Stage 3, Apr. 2008, 498 pages.
3GPP TS 24.229 v8.3.0, Release 8, ETSI TS 124 229 v8.3.0, Digital Cellular Telecommunications System (Phase 2+): Universal Mobile Telecommunications System (UMTS), Internet Protocol (IP) Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), Stage 3, Apr. 2008, 1-125, Part 1.
3GPP TS 24.229 v8.3.0, Release 8, ETSI TS 124 229 v8.3.0, Digital Cellular Telecommunications System (Phase 2+): Universal Mobile Telecommunications System (UMTS), Internet Protocol (IP) Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), Stage 3, Apr. 2008, 126-250, Part 2.
3GPP TS 24.229 v8.3.0, Release 8, ETSI TS 124 229 v8.3.0, Digital Cellular Telecommunications System (Phase 2+): Universal Mobile Telecommunications System (UMTS), Internet Protocol (IP) Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), Stage 3, Apr. 2008, 251-375, Part 3.
3GPP TS 24.229 v8.3.0, Release 8, ETSI TS 124 229 v8.3.0, Digital Cellular Telecommunications System (Phase 2+): Universal Mobile Telecommunications System (UMTS), Internet Protocol (IP) Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), Stage 3, Apr. 2008, 376-497, Part 4.
3GPP TS 24.229 v8.3.0, Technical Specification Group Core Network and Terminals, IP Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), Stage 3, Release 8, Mar. 2008, 495 pages.
3GPP TS 24.403 v1.8.1, Technical Specification Group Core Network and Terminals, Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN), IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), Stage 3, Release 7, Dec. 2007, 96 pages.
3GPP TS 24.403, v1.8.1, Technical Specification Group Core Network and Terminals, Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN), IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SOP), Dec. 1, 2007, XP050365362, pp. 1-96, paragraphs [5.2.6.3], [5.2.7.2], [5.2.10.2].
3GPP TSG CT WG1 24.229 v8.4.1 Meeting #54, 24.229, Change Request, CR 2321, C1-082335, Zagreb, Croatia, Jun. 23-27, 2008, 20 pages.
3GPP TSG CT WG1 Meeting #49, "Corrections for Emergency Procedures," C1-072991, Nokia Siemens Networks, Nokia, Ericsson, Kobe, Japan, Oct. 8-12, 2007, 8 pages.
3GPP TSG SA WG2 Architecture-S2 #50, Basic Call Flow of North America IMS Emergency Session Establishment, S2-060406, Jan. 16-20, 2005.
3GPP TSG SA WG2 Architecture—S2 #50, Basic Call Flow of North America IMS Emergency Session Establishment, S2-060406, Jan. 16-20, 2005.
Communication Pursuant to Article 94(3) EPC issued in European Application No. 09759257.0 dated Jul. 6, 2016.
Communication under Rule 71(3) EPC issued in European Application No. 15156206.3 dated Feb. 19, 2016.
European Search Report in European Application No. 12172479.3, dated Sep. 11, 2012, 6 pages.
European Search Report in European Application No. 12177729.6, dated Sep. 3, 2012, 9 pages.
European Search Report in European Application No. 13162547.7, dated Jul. 11, 2013, 10 pages.
European Search Report in European Application No. 13162615.2, dated Jul. 15, 2013, 8 pages.
European Search Report in European Application No. 15156206.3, dated Jun. 16, 2015, 5 pages.
International Preliminary Report on Patentability in International Application No. PCT/US2009/045987, dated Dec. 6, 2010, 7 pages.
International Preliminary Report on Patentability in International Application No. PCT/US2009/045990, dated Dec. 6, 2010, 6 pages.
International Preliminary Report on Patentability in International Application No. PCT/US2009/045992, dated Dec. 6, 2010, 8 pages.
International Search Report in International Application No. PCT/US2009/045987, dated Sep. 7, 2009, 3 pages.
International Search Report in International Application No. PCT/US2009/045990, dated Sep. 7, 2009, 3 pages.
International Search Report in International Application No. PCT/US2009/045992, dated Sep. 15, 2009, 3 pages.
International Written Opinion in International Application No. PCT/US2009/045987, dated Sep. 7, 2009, 6 pages.
International Written Opinion in International Application No. PCT/US2009/045990, dated Sep. 7, 2009, 6 pages.
International Written Opinion in International Application No. PCT/US2009/045992, dated Sep. 15, 2009, 7 pages.
Jennings et al., "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks," RFC 3325, Nov. 1, 2002, XP015009093, ISSN: 0000-0003, 19 pages.
Nokia Siemens Networks et al., "Corrections for emergency procedures," 3GPP Draft; C1-072991-24229CR1997R2-EMC1-REL-8 Procedure, 3rd Generation Partnership Project (3GPP), vol. CTWG1, Nov. 12, 2007, XP050027161, 7 pages.
Nokia Siemens Networks et al., "Corrections for emergency procedures," 3GPP Draft; C1-072991—24229CR1997R2—EMC1—REL-8 Procedure, 3rd Generation Partnership Project (3GPP), vol. CTWG1, Nov. 12, 2007, XP050027161, 7 pages.
Office Action issued in Chinese Application No. 200980130796.X dated Apr. 11, 2016.
Office Action issued in Indian Application No. 7721/CHENP/2010 dated Mar. 14, 2017.
RFC 4474 Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP); Aug. 2006; 38 pages.
RFC 5012 Requirements for Emergency Context Resolution with Internet Technologies; Jan. 2008; 22 pages.
Rosen et al., "Best Current Practices for Communications Services in Support of Emergency Calling," Feb. 27, 2006, draft-rosen-sos-phonebcp-00.txt.
SIP: More Than You Ever Wanted to Know About; Mar. 2007; 242 pages.
Taylor et al., "Security Threats and Requirements for Emergency Call Marking and Mapping," Jan. 2008, RFC 5069, 13 pages.
ES2440344T3 (en) 2014-01-28 grant
KR20110015654A (en) 2011-02-16 application
US20160100435A1 (en) 2016-04-07 application
US20180042055A1 (en) 2018-02-08 application
EP2260633A1 (en) 2010-12-15 application
CN102113293B (en) 2016-08-03 grant
KR101281844B1 (en) 2013-08-23 grant
CN102113293A (en) 2011-06-29 application
CA2726627A1 (en) 2009-12-10 application
CA2726627C (en) 2014-01-21 grant
WO2009149096A1 (en) 2009-12-10 application
US9462616B2 (en) 2016-10-04 grant
US20160374117A1 (en) 2016-12-22 application
JP5244969B2 (en) 2013-07-24 grant
ES2393301T3 (en) 2012-12-20 grant
JP2011524674A (en) 2011-09-01 application
EP2260633B1 (en) 2012-08-15 grant
US20100223326A1 (en) 2010-09-02 Method of Providing a Service through a User Equipment Unit in a an IP Multimedia Sub-System Telecommunications Network, Including a User Database Server, Service Policy Server and Application Server for use with Said Method
US20110141979A1 (en) 2011-06-16 Technique for emergency session handling in a communication network
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BAKKER, JAN HENDRIK LUCAS;BUCKLEY, ADRIAN;ALLEN, ANDREW;SIGNING DATES FROM 20080618 TO 20080811;REEL/FRAME:042146/0676
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RESEARCH IN MOTION CORPORATION;REEL/FRAME:042146/0929
Free format text: CHANGE OF NAME;ASSIGNOR:RESEARCH IN MOTION LIMITED;REEL/FRAME:042344/0284
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BAKKER, JAN HENDRIK LUCAS;BUCKLEY, ADRIAN;ALLEN, ANDREW MICHAEL;SIGNING DATES FROM 20101119 TO 20101122;REEL/FRAME:044853/0419