1 / 7

“sos” URI parameter for marking emergency requests

“sos” URI parameter for marking emergency requests. Milan Patel 5 th SDO Emergency Services Workshop. Agenda. 3GPP emergency registration Issues in 3GPP emergency services solution “sos” URI parameter Alternative solutions. Emergency registration. 3GPP release 7 requirement

alma
Download Presentation

“sos” URI parameter for marking emergency requests

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. “sos” URI parameter for marking emergency requests Milan Patel 5th SDO Emergency Services Workshop 5th SDO Emergency Services Workshop 21-23 October 2008

  2. Agenda • 3GPP emergency registration • Issues in 3GPP emergency services solution • “sos” URI parameter • Alternative solutions 5th SDO Emergency Services Workshop 21-23 October 2008

  3. Emergency registration • 3GPP release 7 requirement • UE registers to attach to IMS via visited P-CSCF • UE performs emergency registration if: • UE is not registered or is registered in IMS but is roaming • Has credentials to register in IMS and is emergency aware • Removal of Emergency public user identity from release 7 removes indication of emergency registration – need to mark emergency registration and registered contact address for special handling of services and call back. 5th SDO Emergency Services Workshop 21-23 October 2008

  4. Issues in 3GPP release 7 • Identification of emergency registration • Identification of emergency call from the UE (in INVITE request) • Identification of emergency call towards the UE (in response to INVITE request, in the case where the UE was not aware that it sets up an emergency call) • Identification of a call back 5th SDO Emergency Services Workshop 21-23 October 2008

  5. “sos” URI parameter • The proposed solution intends to solve all 4 problems • NOT a replacement for urn:service:sos • Current proposal appends “sos” URI parameter to the contact address in the Contact header of SIP requests and responses • This URI parameter is mandated only for the registration case • In the event that standardization of the “sos” URI parameter is unsuccessful, 3GPP are considering the use of IMS Communication Service Identifier to mark emergency registration. • This does not solve all four issues with the 3GPP solution. 5th SDO Emergency Services Workshop 21-23 October 2008

  6. Back up 5th SDO Emergency Services Workshop 21-23 October 2008

  7. “sos” parameter in the emergency INVITE P-CSCF adds “sos” URI parameter in Contact if UE does NOT detect emergency session attempt. Service URN is included in the Request-URI and To header PSAP URI added to Route. “sos” URI parameter preserved in Contact UE adds “sos” URI parameter in Contact if UE detects emergency session attempt. Service URN is included in the Request-URI and To header PSAP URI as tel URI added to Request URI (replaces service URN). BGCF URI added to Route. “sos” URI parameter preserved in Contact 5th SDO Emergency Services Workshop 21-23 October 2008

More Related