Location Aware Content Using Presence Information Data Formation with Location Object (PIDF-LO)

• US 20120290921A1
• Filed: 05/21/2012
• Published: 11/15/2012
• Est. Priority Date: 01/02/2006
• Status: Active Grant

• Current Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Original Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Inventors: MITCHELL, Don
• Granted Patent: US 9,087,132 B2
• Time in Patent Office: Days
• US Class Current: 715/234
• CPC Class Codes: G06F 16/29 Geographical information databases
• CPC Class Codes: G06F 16/9537 Spatial or temporal dependent retrieval, e.g. spatiotemporal queries
• CPC Class Codes: H04W 4/021 Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 4/029 Location-based management or tracking services

Abstract

The format of the Presence Information Data Format-Location Object (PIDF-LO) as defined by the Internet Engineering Task Force (IETF) is extended or modified to accommodate, within the standard PIDF-LO format, an association of geospacial location to XML content on the Internet. A geospacial location is associated with Extensible Markup Language (XML) content on the Internet. The XML content is identified by a universal resource locator (URL), and associated with geospatial location information (either a specific location, zone, or direction). The URL is inserted into a <presence . . . > section of a Presence Information Data Format-Location Object (PIDF-LO) compliant document as defined by the Internet Engineering Task Force (IETF). In this way, geospacial location information is associated with Internet based XML content using a standard PIDF-LO format.

Claims

1-30. -30. (canceled)

31. A method of tying a geospacial location to Extensible Markup Language (XML) content on a network, comprising:

receiving, at a physical network server, an XML based document as defined by the Internet Engineering Task Force (IETF), said XML based document lacking geospacial location information identifying a specific physical zone;

in response to a determination that said XML based document lacks said geospacial location information, identifying a universal resource locator (URL) of XML content to be tagged with said geospacial location information;

requesting said geospacial location information, through said physical network server, for said XML content;

associating, at said physical network server, said geospacial location information with said XML content; and

inserting, at said physical network server, said XML content and said associated said geospacial location information into a <

presence . . . >

section of said XML based document.

32. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said XML content and its associated said geospacial location information is inserted in an “

entity=”

list in said <

presence . . . >

section of said XML based document.

33. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 32, wherein:

said XML content and its associated said geospacial location information is also inserted in a “

src=”

list in said <

presence . . . >

section of said XML based document.

34. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said XML content and its associated said geospacial location information is inserted in a “

src=”

list in said <

presence . . . >

section of said XML based document.

35. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said XML content and its associated said geospacial location information is inserted in a “

name=”

list in said <

presence . . . >

section of said XML based document.

36. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said specific physical zone is defined using a coordinate based polygon system.

37. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 36, wherein:

said coordinate based polygon system is defined using an assigned numbering system.

38. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said geospacial location information identifies a specific latitude/longitude.

39. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said geospacial location information is defined directionally.

40. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said network is an Internet.

41. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said network is a corporate Intranet.

42. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said network is a corporate Extranet.

43. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said XML content comprises text.

44. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said XML content comprises images.

45. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said XML content comprises audio.

46. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said XML content comprises video.

47. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein:

said XML content is Multimedia Internet Message Extensions (MIME) type content.

48. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, further comprising:

tagging descriptive information relating to said location aware XML content in said <

presence . . . >

section of said XML based document.

49. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 48, wherein:

said tagged descriptive information is included in said <

presence . . . >

section of said XML based document.

50. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 48, wherein:

said tagged descriptive information includes at least one of;

“

weather”

, “

century”

, “

season”

, and “

year”

tags.

51. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 48, wherein:

said tagged descriptive information includes at least one of;

“

Time Reference”

, “

Weather Reference”

, and “

Descriptive Reference”

tags.

52. A method of tying a geospacial location to Extensible Markup Language (XML) content on a network, comprising:

receiving, at a physical network server, an XML based document as defined by the Internet Engineering Task Force (IETF), said XML based document lacking geospacial location information identifying a specific physical zone;

in response to a determination, at said physical network server, that said XML based document lacks said geospacial location information, identifying a universal resource locator (URL) of XML content to be tagged with said geospacial location information;

requesting, at a physical network server, said geospacial location information for said XML content;

associating, via a Session Initiation Protocol (SIP) protocol, said geospacial location information with said XML content; and

inserting, at said physical network server, said XML content and said associated said geospacial location information into a <

presence . . . >

section of said XML based document.

53. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said XML content and its associated said geospacial location information is inserted in an “

entity=”

list in said <

presence . . . >

section of said XML based document.

54. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 53, wherein:

said XML content and its associated said geospacial location information is also inserted in a “

src=”

list in said <

presence . . . >

section of said XML based document.

55. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said XML content and its associated said geospacial location information is inserted in a “

src=”

list in said <

presence . . . >

section of said XML based document.

56. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said XML content and its associated said geospacial location information is inserted in a “

name=”

list in said <

presence . . . >

section of said XML based document.

57. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said specific physical zone is defined using a coordinate based polygon system.

58. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 57, wherein:

said coordinate based polygon system is defined using an assigned numbering system.

59. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said geospacial location information identifies a specific latitude/longitude.

60. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said geospacial location information is defined directionally.

61. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said network is an Internet.

62. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said network is a corporate Intranet.

63. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said network is a corporate Extranet.

64. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said XML content comprises text.

65. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said XML content comprises images.

66. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said XML content comprises audio.

67. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said XML content comprises video.

68. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein:

said XML content is Multimedia Internet Message Extensions (MIME) type content.

69. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, further comprising:

tagging descriptive information relating to said location aware XML content in said <

presence . . . >

section of said XML based document.

70. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 69, wherein:

said tagged descriptive information is included in said <

presence . . . >

section of said XML based document.

71. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 69, wherein:

said tagged descriptive information includes at least one of;

“

weather”

, “

century”

, “

season”

, and “

year”

tags.

72. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 69, wherein:

said tagged descriptive information includes at least one of;

“

Time Reference”

, “

Weather Reference”

, and “

Descriptive Reference”

tags.