System and method for managing emergency requests
View Patent ↗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).
1. A method for responding to an emergency-related message by a user equipment (UE), the method comprising:
receiving a Session Initiation Protocol (SIP) rejection response message containing a P-Asserted-Identity header field from a node within a trust domain, the rejection response message further containing an indicator indicating that a first SIP request message, sent by the UE, is an emergency-related request, and the rejection response message further containing a Contact header field comprising a Uniform Resource Name (URN) of an emergency service; and
sending a second SIP request message towards a Public Safety Answering Point (PSAP), the second SIP request message including the URN of the emergency service and the second SIP request message containing emergency-related information associated with the UE.
2. The method according to claim 1 , wherein the URN of the emergency service comprises a code identifying a country or a code identifying a region.
3. The method according to claim 1 , wherein the code is a ISO 3166-1 compliant code.
4. The method according to claim 1 , wherein the indicator comprises the 3GPP IMS XML body with MIME type “application/3gpp-ims+xml” with the <type> element set to “emergency”.
5. The method according to claim 1 , wherein, prior to receiving the SIP rejection response message, the UE is unaware that the first SIP request message for a dialog is an emergency-related request.
6. The method according to claim 1 , wherein the URN of the emergency service identifies a PSAP.
7. The method of claim 1 , wherein the emergency-related information associated with the UE contained in the second SIP request message comprises a UE identity and, the UE identity is a globally routable user agent uniform resource identifier (GRUU).
8. The method of claim 1 , wherein the emergency-related information associated with the UE contained in the second SIP request message comprises a UE location or UE access network information.
9. The method of claim 1 , wherein the node is a network component that is a proxy call session control function (P-CSCF).
10. The method of claim 1 , wherein the SIP rejection response message is one of SIP 3xx, SIP 4xx, and SIP 6xx.
11. The method of claim 10 , wherein the SIP rejection response message is SIP 380.
12. The method of claim 1 , wherein the message body of the first or second SIP request message includes geographical location information of the UE as a PIDF location object.
13. The method of claim 1 , wherein a contact header field of the first or second SIP request message includes a public globally routable user agent uniform resource identifier (GRUU) value associated with a public user identity.
14. A user equipment (UE), configured to perform a method comprising:
receiving a Session Initiation Protocol (SIP) rejection response message containing a P-Asserted-Identity header field from a node within a trust domain, the rejection response message further containing an indicator indicating that a first SIP request message, sent by the UE, is an emergency-related request, and the rejection response message further containing a Contact header field comprising a Uniform Resource Name (URN) of an emergency service; and
sending a second SIP request message towards a Public Safety Answering Point (PSAP), the second SIP request message including the URN of the emergency service and the second SIP request message containing emergency-related information associated with the UE.
15. The user equipment according to claim 14 , wherein the URN of the emergency service comprises a code identifying a country or a code identifying a region.
16. The user equipment according to claim 15 , wherein the code is a ISO 3166-1 compliant code.
17. The user equipment according to claim 14 , wherein the indicator comprises the 3GPP IMS XML body with MIME type “application/3gpp-ims+xml” with the <type> element set to “emergency”.
18. The user equipment according to claim 14 , wherein, prior to receiving the SIP rejection response message, the UE is unaware that the first SIP request message for a dialog is an emergency-related request.
19. The user equipment according to claim 14 , wherein the URN of the emergency service identifies a PSAP.
20. The user equipment of claim 14 , wherein the emergency-related information associated with the UE contained in the second SIP request message comprises a UE identity and, the UE identity is a globally routable user agent uniform resource identifier (GRUU).
21. The user equipment of claim 14 , wherein the emergency-related information associated with the UE contained in the second SIP request message comprises a UE location or UE access network information.
22. The user equipment of claim 14 , wherein the node is a network component that is a proxy call session control function (P-CSCF).
23. The user equipment of claim 14 , wherein the SIP rejection response message is one of SIP 3xx, SIP 4xx, and SIP 6xx.
24. The user equipment of claim 23 , wherein the SIP rejection response message is SIP 380.
25. The user equipment of claim 14 , wherein the message body of the first or second SIP request message includes geographical location information of the UE as a PIDF location object.
26. The user equipment of claim 14 , wherein a contact header field of the first or second SIP request message includes a public globally routable user agent uniform resource identifier (GRUU) value associated with a public user identity.
27. A method for responding to an emergency-related message by a node within a trust domain, the method comprising:
receiving from a user equipment (UE) a first Session Initiation Protocol (SIP) request message;
transmitting, to the UE, a SIP rejection response message containing a P-Asserted-Identity header field, the rejection response message further containing an indicator indicating that the first SIP request message is an emergency-related request, and the rejection response message further containing a Contact header field comprising a Uniform Resource Name (URN) of an emergency service, such that, in response to receiving the SIP rejection response, the UE is able to send a second SIP request message towards a Public Safety Answering Point (PSAP), the second SIP request message including the URN of the emergency service and the second SIP request message containing emergency-related information associated with the UE.
28. The method according to claim 27 , wherein the indicator comprises the 3GPP IMS XML body with MIME type “application/3gpp-ims+xml” with the <type> element set to “emergency”.
29. The method of claim 27 , wherein the node is a network component that is a proxy call session control function (P-CSCF).
30. The method of claim 27 , wherein the SIP rejection response message is one of SIP 3xx, SIP 4xx, and SIP 6xx.
31. The method of claim 30 , wherein the SIP rejection response message is SIP 380.
32. A node of a telecommunications network within a trust domain configured to perform a method comprising:
receiving from a user equipment (UE) a first Session Initiation Protocol (SIP) request message;
transmitting, to the UE, a SIP rejection response message containing a P-Asserted-Identity header field, the rejection response message further containing an indicator indicating that the first SIP request message is an emergency-related request, and the rejection response message further containing a Contact header field comprising a Uniform Resource Name (URN) of an emergency service, such that, in response to receiving the SIP rejection response, the UE is able to send a second SIP request message towards a Public Safety Answering Point (PSAP), the second SIP request message including the URN of the emergency service and the second SIP request message containing emergency-related information associated with the UE.
33. The node according to claim 32 , wherein the indicator comprises the 3GPP IMS XML body with MIME type “application/3gpp-ims+xml” with the <type> element set to “emergency”.
34. The node of claim 32 , wherein the node is a network component that is a proxy call session control function (P-CSCF).
35. The node of claim 32 , wherein the SIP rejection response message is one of SIP 3xx, SIP 4xx, and SIP 6xx.
36. The node of claim 35 , wherein the SIP rejection response message is SIP 380.