Coding and Behavior when Receiving an IMS Emergency Session Indicator from Authorized Source

• US 20090296688A1
• Filed: 06/02/2008
• Published: 12/03/2009
• Est. Priority Date: 06/02/2008
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: ALLEN, Andrew, BUCKLEY, Adrian, BAKKER, John-Luc
• Granted Patent: US 9,602,552 B2
• Time in Patent Office: Days
• US Class Current: 370/352
• 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-28. -28. (canceled)

29. A method for a user equipment (UE) to respond to an emergency-related message comprising:

receiving a response message containing an indicator indicating that a first message is an emergency-related request; and

sending a second message containing information associated with the UE.

30. The method of claim 29, wherein upon receiving the response message, the method further comprising:

providing a user indication that the first message is an emergency-related request.

31. The method of claim 29, wherein the information associated with the UE contained in the second message comprises a UE identity.

32. The method of claim 29, wherein the information associated with the UE contained in the second message comprises a UE location.

33. The method of claim 29, wherein the information associated with the UE contained in the second message comprises UE access network information.

34. The method of claim 29, wherein the UE is unaware that the first message is an emergency-related request.

35. The method of claim 29, wherein the first message is a SIP (Session Initiation Protocol) request.

36. The method of claim 29, wherein the response message is one of a SIP 1xx or 200 (OK) response.

37. The method of claim 29, wherein the second message is one of:

a SIP ACK;

a SIP PRACK;

a SIP target refresh;

a SIP UPDATE; and

a SIP RE-INVITE request.

38. The method of claim 29, wherein the first message is an initial request for a dialog.

39. The method of claim 31, wherein the UE identity is a globally routable user agent uniform resource identifier (GRUU).

40. The method of claim 32, wherein if the UE is aware of a URI (Uniform Resource Identifier) that points to the UE location, the method further comprising including the URI in a geolocation header field of the second message.

41. The method of claim 29, further comprising if geographical location information of the UE is available to the UE, including the geographical location information as a PIDF location object in a message body of the second message.

42. The method of claim 29, further comprising if a public GRUU value has been saved associated with a public user identity, including the public GRUU value in a contact header field of the second message.

43. The method of claim 33, wherein the UE access network information is included in a P-Access-Network-Info header field in the second message and comprises one of a location identifier, a cell identifier or an identity of an I-WLAN access node.

44. A user equipment (UE) comprising:

a component configured such that the UE receives a response message containing an indicator indicating that a first message is an emergency-related request, and such that the UE sends a second message containing information associated with the UE.

45. The UE of claim 44, wherein upon receiving the response message, the UE provides a user indication that the first message is an emergency-related request.

46. The UE of claim 44, wherein the information associated with the UE contained in the second message comprises a UE identity.

47. The UE of claim 44, wherein the information associated with the UE contained in the second message comprises a UE location.

48. The UE of claim 44, wherein the information associated with the UE contained in the second message comprises UE access network information.

49. The UE of claim 44, wherein the UE is unaware that the first message is an emergency-related request.

50. The UE of claim 44, wherein the first message is a SIP (Session Initiation Protocol) request.

51. The LIE of claim 44, wherein the response message is one of a SIP 1xx or 200 (OK) response.

52. The LIE of claim 44, wherein the second message is one of:

a SIP ACK;

a SIP PRACK;

a SIP target refresh;

a SIP UPDATE; and

a SIP RE-INVITE request.

53. The UE of claim 44, wherein the first message is an initial request for a dialog.

54. The UE of claim 46, wherein the UE identity is a globally routable user agent uniform resource identifier (GRUU).

55. The LIE of claim 47, wherein if the UE is aware of a urn (Uniform Resource Identifier) that points to the UE location, the UE includes the URI in a geolocation header field of the second message.

56. The UE of claim 44, wherein if geographical location information of the UE is available to the UE, the UE includes the geographical location information as a PIDF location object in a message body of the second message.

57. The UE of claim 44, wherein if a public GRUU value has been saved associated with a public user identity, the UE includes the public GRUU value in a contact header field of the second message.

58. The UE of claim 48, wherein the UE access network information is included in a P-Access-Network-Info header field in the second message and comprises one of a location identifier, a cell, identifier or an identity of an I-WLAN access node.