Coding and behavior when receiving an IMS emergency session indicator from authorized source

• US 9,602,552 B2
• Filed: 06/02/2008
• Issued: 03/21/2017
• Est. Priority Date: 06/02/2008
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Bakker, Jan Hendrik Lucas, Buckley, Adrian, Allen, Andrew
• Primary Examiner(s): Kassim, Khaled
• Assistant Examiner(s): Yang, Zhaohui
• Application Number:
  US12/131,779
• Publication Number:
  US 20090296688A1
• Time in Patent Office: 3,214 Days
• Field of Search: 455/404.1, 370/352
• US Class Current: 1/1
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1059 End-user terminal functionalities specially adapted for real-time communication
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04M 1/72418 for supporting emergency services
• CPC Class Codes: H04M 2207/18 wireless networks
• CPC Class Codes: H04M 2242/04 for emergency applications
• CPC Class Codes: H04M 3/42382 Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks
• CPC Class Codes: H04M 3/436 Arrangements for screening incoming calls , i.e. evaluating the characteristics of a call before deciding whether to answer it based on the calling party profile H04M3/42059; based on location H04M3/42348; based on presence H04M3/42365; diversion H04M3/54
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04W 4/90 Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• CPC Class Codes: H04W 76/50 for emergency connections

Abstract

A method is provided for a user equipment (UE) to respond to an emergency-related message sent to the UE. The method comprises the UE receiving a first message containing an indicator indicating that an emergency-related request has been made, the UE recognizing the indicator as an indication that the emergency-related request is related to an emergency, and the UE sending a second message containing emergency-related information about itself.

Claims

1. A method in a user equipment (UE), the method comprising:

maintaining in memory, at the UE, one or more Emergency Service Category (ESC) Values, each ESC Value associated with an Emergency Service Uniform Resource Name (URN), wherein the Emergency Service URN is indicative of a type of emergency service from a plurality of types of emergency services;

receiving at the UE a Session Initiation Protocol (SIP) 380 response message from an Internet Protocol Multimedia (IM) Core Network (CN) Subsystem (IMS) using a first registration, the message including a URN of an emergency service within a Contact header field, the message indicating rejection of an emergency service request from the UE, and the message originated by a Proxy Call Session Control Function (P-CSCF) of the IMS; and

performing one of using a second registration with IMS and originating a call over a Circuit Switched (CS) network, comprising;

when using a second registration, creating the second registration with IMS and sending a SIP request message using the second registration towards a Public Safety Answering Point (PSAP), the SIP request message including the URN of the emergency service and emergency-related information associated with the UE;

when originating a call over a CS network, when the URN of the emergency service is an Emergency Service URN indicative of a type of emergency service associated with an ESC Value as maintained in memory, accessing the CS network and initiating an emergency request message on the CS network indicating the type of emergency service; and

when originating a call over the CS network and the URN of the emergency service is an Emergency Service URN indicative of a type of emergency service not associated with an ESC Value as maintained in memory, accessing the CS network and initiating a CS call request.

2. The method of claim 1, wherein the SIP 380 response message further comprises an indicator indicating that a first SIP request message, sent by the UE, is an emergency-related request.

3. The method of claim 1, wherein the URN of the emergency service comprises a code identifying a country or a code identifying a region.

4. The method of claim 1, wherein the Emergency Service URN is a service URN with a top-level service type of “

sos”

.

5. The method of claim 1, wherein the SIP 380 response message further comprises a P-Asserted-Identity header field from a node with a trust domain.

6. The method of claim 1, wherein mapping between the Emergency Service URN and the at least one of the one or more Emergency Service Category Values comprises at least one of:

mapping between the urn;

service;

sos.police URN value and Bit 1 of the Emergency Service Category Value;

mapping between the urn;

service;

sos.ambulance URN and Bit 2 of the Emergency Service Category Value;

mapping between the urn;

service;

sos.fire URN and Bit 3 of the Emergency Service Category Value;

mapping between the urn;

service;

sos.marine URN and Bit 4 of the Emergency Service Category Value; and

mapping between the urn;

service;

sos.mountain URN and Bit 5 of the Emergency Service Category Value.

7. The method of claim 1, wherein mapping between the Emergency Service URN and the at least one of the one or more Emergency Service Category Values comprises mapping the urn:

service;

sos URN value to an Emergency Service Category Value with no bits set to “

1”

.

8. The method of claim 1, wherein the SIP 380 response message is a response to a first SIP request message.

9. A user equipment (UE) comprising:

a component configured such that the UE

maintains in memory one or more Emergency Service Category (ESC) Values, each ESC Value associated with an Emergency Service Uniform Resource Name (URN), wherein the Emergency Service URN is indicative of a type of emergency service from a plurality of types of emergency services;

receives at the UE a Session Initiation Protocol (SIP) 380 response message from an Internet Protocol Multimedia (IM) Core Network (CN) Subsystem (IMS) using a first registration, the message including a URN of an emergency service within a Contact header field, the message indicating rejection of an emergency service request from the UE, and the message originated by a Proxy Call Session Control Function (P-CSCF) of the IMS; and

performs one of using a second registration with IMS and originating a call over a Circuit Switched (CS) network, comprising;

when using a second registration, creates the second registration with IMS and sends a SIP request message using the second registration towards a Public Safety Answering Point (PSAP), the SIP request message including the URN of the emergency service and emergency-related information associated with the UE;

when originating a call over a CS network, accesses the CS network and, when the URN of the emergency service is an Emergency Service URN indicative of a type of emergency service associated with an ESC Value as maintained in memory, initiates an emergency request message on the CS network indicating the type of emergency service; and

when originating a call over the CS network and the URN of the emergency service is an Emergency Service URN indicative of a type of emergency service not associated with an ESC Value as maintained in memory, accesses the CS network and initiates a CS call request.

10. The UE of claim 9, wherein the SIP 380 response message further comprises an indicator indicating that a first SIP request message, sent by the UE, is an emergency-related request.

11. The UE of claim 9, wherein the URN of the emergency service comprises a code identifying a country or a code identifying a region.

12. The UE of claim 9, wherein the Emergency Service URN is a service URN with a top-level service type of “

sos”

.

13. The UE of claim 9, wherein the SIP 380 response message further comprises a P-Asserted-Identity header field from a node with a trust domain.

14. The UE of claim 9, wherein mapping between the Emergency Service URN and the at least one of the one or more Emergency Service Category Values comprises at least one of:

mapping between the urn;

service;

sos.police URN value and Bit 1 of the Emergency Service Category Value;

mapping between the urn;

service;

sos.ambulance URN and Bit 2 of the Emergency Service Category Value;

mapping between the urn;

service;

sos.fire URN and Bit 3 of the Emergency Service Category Value;

mapping between the urn;

service;

sos.marine URN and Bit 4 of the Emergency Service Category Value; and

mapping between the urn;

service;

sos.mountain URN and Bit 5 of the Emergency Service Category Value.

15. The UE of claim 9, wherein mapping between the Emergency Service URN and the at least one of the one or more Emergency Service Category Values comprises mapping the urn:

service;

sos URN value to an Emergency Service Category Value with no bits set to “

1”

.

16. The UE of claim 9, wherein the SIP 380 response message is a response to a first SIP request message.