Updating a Request Related to an IMS Emergency Session

• US 20090298458A1
• 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: Research In Motion Limited (Blackberry Limited)
• Inventors: ALLEN, Andrew, BUCKLEY, Adrian, BAKKER, John-Luc
• Granted Patent: US 8,478,226 B2
• Time in Patent Office: Days
• US Class Current: 455/404.1
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/40 Support for services or applications
• CPC Class Codes: H04M 2242/04 for emergency applications
• CPC Class Codes: H04M 3/42068 where the identifier is used to access a profile
• CPC Class Codes: H04M 3/42348 Location-based services which utilize the location information of a target
• 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 network component is provided that includes a processor configured to inspect requests sent to the network component to determine if the requests are related to emergencies. If one of the requests is determined to relate to an emergency, the processor is further configured, based on configurations and regulator policies, to update the request.

Claims

1-30. -30. (canceled)

31. A network component comprising:

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).

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

33. The network component of claim 31, wherein the information associated with the UE contained in the second message comprises a UE identity.

34. The network component of claim 31, wherein the information associated with the UE contained in the second message comprises a UE location.

35. The network component of claim 31, wherein the information associated with the UE contained in the second message comprises UE access network information.

36. The network component of claim 31, wherein the UE is unaware that the first message is an emergency-related request.

37. The network component of claim 31, wherein the first message is a SIP (Session Initiation Protocol) request.

38. The network component of claim 31, wherein the response message is one of a SIP 1xx or 200 (OK) response.

39. The network component of claim 31, 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.

40. The network component of claim 31, wherein the first message is an initial request for a dialog.

41. The network component of claim 33, wherein the UE identity is a globally routable user agent uniform resource identifier (GRUU).

42. The network component of claim 34, wherein if the UE is aware of a URI (Uniform Resource Identifier) that points to the UE location, the UE includes the URI in a geolocation header field of the second message.

43. The network component of claim 31, 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.

44. The network component of claim 31, 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.

45. The network component of claim 35, 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.

46. A method for a network component to manage emergency-related information, comprising:

the network component transmitting a response message containing an indicator indicating that a first message is an emergency-related request; and

the network component receiving a second message containing information associated with a user equipment (UE).

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

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

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

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

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

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

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

54. The method of claim 46, 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.

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

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

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

58. The method of claim 46, 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.

59. The method of claim 46, 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.

60. The method of claim 50, 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.