IP Library Granted Patent US 7,376,670
Granted Patent B2
US 7,376,670 · App. 10/783,856 · Granted May 20, 2008

System and method for provisioning presence application services

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,376,670
App. No.
10/783,856
Granted
May 20, 2008
Kind
B2
Abstract

A system and method for provisioning presence application services using a customizable presence data model. An ontology depository having at least one domain-specific ontology model for a particular presence application is provided on a communications network. Presence client software associated with a general-purpose presence entity is customized by referencing a domain-specific ontology model of the ontology depository, whereby the presence entity becomes operable to engage in a particular presence application relating to the domain-specific ontology model.

Claims (45)

1. A provisioning system for supporting presence applications, comprising:

an ontology depository having at least one domain-specific ontology model accessible via the Internet for a particular presence application, wherein the ontology model for the particular presence application includes a collection of:

abstracted entities that are appropriately classified;

relationships among the entities; and

information about how to collect presence data from persons, places and things; and

a presence entity having a structure operable to reference a domain-specific ontology model of said ontology depository via the Internet for customizing a presence client software module associated with said presence entity, whereby said presence entity becomes operable to engage in a particular presence application relating to said domain-specific ontology model.

2. The provisioning system for supporting presence applications as recited in claim 1 , wherein said at least one domain-specific ontology model for a particular presence application comprises a Unified Markup Language (UML)-based data model.

3. The provisioning system for supporting presence applications as recited in claim 1 , wherein said at least one domain-specific ontology model for a particular presence application comprises an Extended Markup Language (XML)-based data model.

4. The provisioning system for supporting presence applications as recited in claim 1 , wherein said at least one domain-specific ontology model for a particular presence application comprises a semantic net data model.

5. The provisioning system for supporting presence applications as recited in claim 1 , wherein said at least one domain-specific ontology model for a particular presence application comprises a General Markup Language (GML)-based data model.

6. The provisioning system for supporting presence applications as recited in claim 1 , wherein said at least one domain-specific ontology model for a particular presence application comprises a data model based on a semantic software application selected from the group consisting of a Resource Description Framework (RDF) application, an Ontology Inference Layer (OIL) application, an Ontology Web Language (OWL) application, a Semantic Web Initiative (SWI)-compliant application, and a Meta Object Framework (MOF) application.

7. The provisioning system for supporting presence applications as recited in claim 1 , wherein said structure operable to reference a domain-specific ontology model comprises a presence client software module operable to invoke a Universal Resource Locator (URL) path associated with said ontology depository including said domain-specific ontology model.

8. The provisioning system for supporting presence applications as recited in claim 1 , wherein said structure associated with said presence entity is operable to dynamically reference a domain-specific ontology model of said ontology depository.

9. The provisioning system for supporting presence applications as recited in claim 1 , wherein said structure associated with said presence entity is operable to effectuate a static reference to a domain-specific ontology model during said structure's compile time.

10. The provisioning system for supporting presence applications as recited in claim 1 , wherein said particular presence application is selected from the group consisting of transportation applications, shipping and delivery applications, premises security monitoring applications, private enterprise applications, government agency applications, and instant messaging applications.

11. A service provisioning methodology for supporting presence applications, comprising:

providing an ontology depository having at least one domain-specific ontology model accessible via the Internet for a particular presence application, wherein the ontology model for the particular presence application includes a collection of:

abstracted entities that are appropriately classified;

relationships among the entities; and

information about how to collect presence data from persons, places and things; and

customizing a presence client software module associated with a presence entity by referencing a domain-specific ontology model of said ontology depository via the Internet, whereby said presence entity becomes operable to engage in a particular presence application relating to said domain-specific ontology model.

12. The service provisioning methodology for supporting presence applications as recited in claim 11 , wherein said at least one domain-specific ontology model for a particular presence application comprises a Unified Markup Language (UML)-based data model.

13. The service provisioning methodology for supporting presence applications as recited in claim 11 , wherein said at least one domain-specific ontology model for a particular presence application comprises an Extended Markup Language (XML)-based data model.

14. The service provisioning methodology for supporting presence applications as recited in claim 11 , wherein said at least one domain-specific ontology model for a particular presence application comprises a semantic net data model.

15. The service provisioning methodology for supporting presence applications as recited in claim 11 , wherein said at least one domain-specific ontology model for a particular presence application comprises a General Markup Language (GML)-based data model.

16. The service provisioning methodology for supporting presence applications as recited in claim 11 , wherein said at least one domain-specific ontology model for a particular presence application comprises a data model based on a semantic software application selected from the group consisting of a Resource Description Framework (RDF) application, an Ontology Inference Layer (OIL) application, an Ontology Web Language (OWL) application, a Semantic Web Initiative (SWI)-compliant application, and a Meta Object Framework (MOP) application.

17. The service provisioning methodology for supporting presence applications as recited in claim 11 , wherein said customizing a presence client software module associated with a presence entity is effectuated by invoking a Universal Resource Locator (URL) path associated with said ontology depository including said domain-specific ontology model.

18. The service provisioning methodology for supporting presence applications as recited in claim 11 , wherein said customizing a presence client software module associated with a presence entity is effectuated by dynamically referencing a domain-specific ontology model of said ontology depository.

19. The service provisioning methodology for supporting presence applications as recited in claim 11 , wherein said customizing a presence client software module associated with a presence entity is effectuated by a static reference to a domain-specific ontology model during said presence client software module's compile time.

20. The service provisioning methodology for supporting presence applications as recited in claim 11 , wherein said particular presence application is selected from the group consisting of transportation applications, shipping and delivery applications, premises security monitoring applications, private enterprise applications, government agency applications, and instant messaging applications.

21. A system for provisioning presence applications over a presence service network, comprising:

means operable to host an ontology depository accessible via the Internet that includes a domain-specific ontology model corresponding to each of a plurality of presence applications, wherein the ontology model for each of the plurality of presence applications includes a collection of:

abstracted entities that are appropriately classified;

relationships among the entities; and

information about how to collect presence data from persons, places and things; and

means for customizing a presence client software module associated with a presence entity with a particular presence application accessed from the ontology model via the Internet.

22. The system for provisioning presence applications over a presence service network as recited in claim 21 , wherein said domain-specific ontology model comprises a Unified Markup Language (UML)-based data model.

23. The system for provisioning presence applications over a presence service network as recited in claim 21 , wherein said domain-specific ontology model comprises an Extended Markup Language (XML)-based data model.

24. The system for provisioning presence applications over a presence service network as recited in claim 21 , wherein said domain-specific ontology model comprises a semantic net data model.

25. The system for provisioning presence applications over a presence service network as recited in claim 21 , wherein said domain-specific ontology model for a particular presence application comprises a General Markup Language (GML)-based data model.

26. The system for provisioning presence applications over a presence service network as recited in claim 21 , wherein said domain-specific ontology model comprises a data model based on a semantic software application selected from the group consisting of a Resource Description Framework (RDF) application, an Ontology Inference Layer (OIL) application, an Ontology Web Language (OWL) application, a Semantic Web Initiative (SWI)-compliant application, and a Meta Object Framework (MOF) application.

27. The system for provisioning presence applications over a presence service network as recited in claim 21 , wherein said means for customizing a presence client software module associated with a presence entity comprises means for referencing a domain-specific ontology model for a particular presence application using a Universal Resource Locator (URL) path associated with said ontology depository.

28. The system for provisioning presence applications over a presence service network as recited in claim 21 , wherein said means for customizing a presence client software module associated with a presence entity is operable to dynamically reference a domain-specific ontology model of said ontology depository.

29. The system for provisioning presence applications over a presence service network as recited in claim 21 , wherein said means for customizing a presence client software module associated with a presence entity is operable to effectuate a static reference to a domain-specific ontology model during said presence client software module's compile time.

30. The system for provisioning presence applications over a presence service network as recited in claim 21 , wherein said particular presence application is selected from the group consisting of transportation applications, shipping and delivery applications, premises security monitoring applications, private enterprise applications, government agency applications, and instant messaging applications.

Assignments (6)
RELEASE OF SECURITY INTEREST Recorded Sep 30, 2014
From: CREDIT SUISSE AG
To: ALCATEL LUCENT
Reel/Frame 033868/0001 →
RELEASE OF SECURITY INTEREST Recorded Mar 26, 2014
From: CREDIT SUISSE AG
To: ALCATEL LUCENT
Reel/Frame 032536/0006 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 17, 2014
From: ALCATEL LUCENT
To: SOUND VIEW INNOVATIONS, LLC
Reel/Frame 032086/0016 →
SECURITY AGREEMENT Recorded Jan 30, 2013
From: ALCATEL LUCENT
To: CREDIT SUISSE AG
Reel/Frame 029821/0001 →
CHANGE OF NAME Recorded Apr 1, 2008
From: ALCATEL
To: ALCATEL LUCENT
Reel/Frame 020736/0848 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 20, 2004
From: BADT JR., SIG; SUHAIL, ATIYA
To: ALCATEL
Reel/Frame 015021/0331 →