Schema-based service for identity-based access to presence data

• US 20030023623A1
• Filed: 06/28/2002
• Published: 01/30/2003
• Est. Priority Date: 03/14/2001
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Horvitz, Eric J., Fang, Lijiang, Lucovsky, Mark H., Pierce, Shaun D., Steckler, Paul A.
• Application Number:
  US10/187,063
• Publication Number:
  US 20030023623A1
• Time in Patent Office: Days
• US Class Current: 715/500
• CPC Class Codes: G06F 21/335 for accessing specific resources, e.g. using Kerberos tickets
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 21/6236 between heterogeneous systems
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 21/6272 by registering files or documents with a third party
• CPC Class Codes: G06F 21/629 to features or functions of an application
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 2221/2149 Restricted operating environment
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/62 : Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols

Abstract

A schema-based presence service for Internet access to per-user presence data, wherein access to data is based on each user'"'"'s identity. The presence service includes a schema that defines rules and a structure for each user'"'"'s data, and also includes methods that provide access to the data in a defined way. The presence schema thus corresponds to a logical document containing the data for each user. The user manipulates (e.g., reads or writes) data in the logical document by data access requests through defined methods. In one implementation, the presence schemas are arranged as XML documents, and the services provide methods that control access to the data based on the requesting user'"'"'s identification, defined role and scope for that role. In this way, data can be accessed by its owner, and shared to an extent determined by the owner. The structure of the data is defined from the perspective of the data, not from that of an application program or a device, whereby appropriate programs can communicate with the presence service to access the data, with existing knowledge of the schema-defined format, regardless of the device or application program in use. Extensibility is defined into the schema, and argots may be used to contain the presence information.

Claims

1. In a computer network, a method comprising,

providing a presence schema, the presence schema having presence-related fields arranged into a content document with defined structures for the fields;

receiving a data access request directed to presence information, the request including associated identity information; and

in response to the data access request, manipulating at least one set of data in a logical presence document that includes data therein according to the associated identity information, each set of data in the logical presence document structured to correspond to a field in the content document.

2. The method of claim 1 wherein manipulating at least one set of data comprises reading data from at least one field in the logical presence document.

3. The method of claim 1 wherein manipulating at least one set of data comprises writing data to at least one field in the logical presence document.

4. A computer-readable medium having computer-executable instructions for performing the method of claim 1.

5. In a computer network, a method comprising,

receiving a request to retrieve presence data, the request including associated identity information;

reading from a data store to obtain presence data based on the associated identity information;

constructing a presence document including at least part of the data, the document arranged according to a defined schema for presence data; and

returning the document in response to the request.

6. The method of claim 5 wherein the schema includes at least one defined field for extending the schema.

7. A computer-readable medium having computer-executable instructions for performing the method of claim 5.

8. A computer-readable medium having stored thereon a data structure, comprising:

a first set of data corresponding to activity at an endpoint device;

a second set of data corresponding to anticipated presence at the endpoint device; and

wherein the first and second sets of data are regularized according to a schema by a service for an identity such that access to the service receives information related to a user'"'"'s presence with respect to the endpoint device.

9. The data structure of claim 8 wherein the first set of data includes data corresponding to explicit indication of presence at the endpoint device.

10. The data structure of claim 8 wherein the first set of data includes data corresponding to device availability.

11. The data structure of claim 8 wherein the first set of data includes data corresponding to user interaction the device endpoint.

12. The data structure of claim 8 wherein the first set of data includes data corresponding to proximity to the device endpoint

13. The data structure of claim 12 wherein the proximity to the device endpoint is detected via sound.

14. The data structure of claim 12 wherein the proximity to the device endpoint is detected via motion.

15. The data structure of claim 8 wherein the first set of data includes data corresponding to a time of sensed last activity at the device endpoint.

16. The data structure of claim 8 wherein the second set of data includes data corresponding to an availability forecast.

17. The data structure of claim 8 wherein the second set of data includes data corresponding to a time until a user associated with the device endpoint is available.

18. The data structure of claim 17 wherein the time data corresponds to an ending time of a scheduled event.

19. The data structure of claim 17 wherein the time data corresponds to a time when no event is scheduled.

20. The data structure of claim 8 wherein the second set of data includes data corresponding to a time when at least one resource of the device endpoint is available.

21. A computer-readable medium having stored thereon a data structure, comprising:

a first set of data indicating that the data structure contains presence information corresponding to an identity;

a second set of data corresponding to an argot, the argot including presence data with respect to an endpoint device; and

wherein the first and second sets of data are regularized according to a schema by a service for the identity, such that access to the service receives the argot and a software program interprets the argot to determine presence information for a user corresponding to the identity with respect to the endpoint device.

22. The data structure of claim 21 wherein the argot provides presence information for a plurality of endpoints.