US7302634B2
Expired / Lapsed
US
⏱️ 0.0 years remaining
Schema-based services for identity-based data access
Assignee: Microsoft Technology Licensing LLC
•
Filing: 2001-10-22
•
Granted: 2007-11-27
•
Expires: 2021-10-22
Abstract
Abstract A schema-based service for Internet access to per-user services data, wherein access to data is based on each user's identity. The 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 services 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 services 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.
Inventors
- 👤 Mark H. Lucovsky
- 👤 Shaun Douglas Pierce
- 👤 Steven D. White
- 👤 Ramu Movva
- 👤 Jagadeesh Kalki
- 👤 David Benjamin Auerbach
- 👤 Peter Sewall Ford
- 👤 Jay Christopher Jacobs
- 👤 Paul Andrew Steckler
- 👤 Walter C. Hsueh
- 👤 Kendall D. Keil
- 👤 Burra Gopal
- 👤 Suresh Kannan
- 👤 Yi-Wen Guu
- 👤 Samuel John George
- 👤 William Raymond Hoffman
- 👤 Philip Michael Smoot
- 👤 Lijiang Fang
- 👤 Michael B. Taylor
- 👤 Winnie C. Wu
- 👤 Paul J. Leach
- 👤 Richard B. Ward
- 👤 Yun-Qi Yuan
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-24 20:48
CPC Classifications
G; G06; G06Q; G06Q10/00; G06Q10/10; G06Q10/109; G06F; G06F21/00; G06F21/30; G06F21/31; G06F21/33; G06F21/335; G06F21/60; G06F21/62; G06F21/6218; G06F21/6227; G06F21/6236; G06F21/6245; G06F21/6272; G06F21/629; H; H04; H04L; H04L63/00; H04L63/10; H04L63/102; H04L67/00; H04L67/01; H04L67/02; H04L67/2866; H04L67/30; H04L67/303; H04L67/306; H04L67/50; H04L67/51; H04L67/56; H04L67/564; H04L67/60; H04L67/62; H04L9/00; H04L9/40; G06F2221/00; G06F2221/21; G06F2221/2115; G06F2221/2117; G06F2221/2119; G06F2221/2141; G06F2221/2149; H04L67/133; H04L69/00; H04L69/30; H04L69/32; H04L69/322; H04L69/329; Y; Y10; Y10S; Y10S707/00; Y10S707/99931; Y10S707/99939; Y10S707/99941; Y10S707/99942; Y10S707/99943
Claims Analysis
Total Claims: 26
Claim 1
Independent Claim
375 words
In a computer network, a method comprising, receiving a request from a requester at a my-services service for location information of a user identity-based service, wherein the my-services service describes available services for a given user identity of a user of the computer network, the my-services service having a my-services schema that maintains data about other services in one or more service-related fields; providing location information to the requester regarding the requested user identity-based service, wherein the requested user identity-based service to organize data associated with the user based on an identity of the user, the user identity-based service including a user identity-based service schema having service-related fields arranged into a content document with defined structures for the fields, wherein the user identity-based service to receive data used by the user identity-based service from another user identity-based service in accordance with a push model, wherein the push model includes receiving an update to the data from the another user identity-based service after the data changes at the another user identity-based service, wherein the push model uses a Service-to-Service Communication Protocol (SSCP) between user identity-based services, wherein a user identity-based service may be a publisher and/or a subscriber in the SSCP, wherein the SSCP includes: a publisher-to-subscriber communication to send changes to a publisher's data to one or more subscribers of the publisher's data; a subscriber-to-publisher communication to update one or more subscribers to the publisher's data; a service status communication used by a publisher to inform one or more subscribers to the publisher that the publisher is going offline or has come online, and used by a subscriber to inform one or more publishers to the subscriber that the subscriber is going offline or has come online; receiving a data access request directed to service information at the user identity-based service from the requester, the request including associated user identity information; in response to the data access request, manipulating at least one set of data in a logical service document that includes data therein according to the associated identity information, each set of data in the logical service document structured to correspond to a field in the content document; and returning the logical service document to the requester in response to the data access request.
Claim 2
Dependent Claim
375 words
In a computer network, a method comprising, receiving a request from a requester at a my-services service for location information of a user identity-based service, wherein the my-services service describes available services for a given user identity of a user of the computer network, the my-services service having a my-services schema that maintains data about other services in one or more service-related fields; providing location information to the requester regarding the requested user identity-based service, wherein the requested user identity-based service to organize data associated with the user based on an identity of the user, the user identity-based service including a user identity-based service schema having service-related fields arranged into a content document with defined structures for the fields, wherein the user identity-based service to receive data used by the user identity-based service from another user identity-based service in accordance with a push model, wherein the push model includes receiving an update to the data from the another user identity-based service after the data changes at the another user identity-based service, wherein the push model uses a Service-to-Service Communication Protocol (SSCP) between user identity-based services, wherein a user identity-based service may be a publisher and/or a subscriber in the SSCP, wherein the SSCP includes: a publisher-to-subscriber communication to send changes to a publisher's data to one or more subscribers of the publisher's data; a subscriber-to-publisher communication to update one or more subscribers to the publisher's data; a service status communication used by a publisher to inform one or more subscribers to the publisher that the publisher is going offline or has come online, and used by a subscriber to inform one or more publishers to the subscriber that the subscriber is going offline or has come online; receiving a data access request directed to service information at the user identity-based service from the requester, the request including associated user identity information; in response to the data access request, manipulating at least one set of data in a logical service document that includes data therein according to the associated identity information, each set of data in the logical service document structured to correspond to a field in the content document; and returning the logical service document to the requester in response to the data access request.
Claim 3
Dependent Claim
26 words
The method of claim 1 wherein manipulating at least one set of data comprises reading data from at least one field in the logical service document.
Claim 4
Dependent Claim
26 words
The method of claim 1 wherein manipulating at least one set of data comprises writing data to at least one field in the logical service document.
Claim 5
Dependent Claim
15 words
The method of claim 1 wherein the user identity-based service includes an application settings service.
Claim 6
Dependent Claim
14 words
The method of claim 1 wherein the user identity-based service includes a calendar service.
Claim 7
Dependent Claim
14 words
The method of claim 1 wherein the user identity-based service includes a categories service.
Claim 8
Dependent Claim
14 words
The method of claim 1 wherein the user identity-based service includes a contacts service.
Claim 9
Dependent Claim
14 words
The method of claim 1 wherein the user identity-based service includes a devices service.
Claim 10
Dependent Claim
14 words
The method of claim 1 wherein the user identity-based service includes a documents service.
Claim 11
Dependent Claim
14 words
The method of claim 1 wherein the user identity-based service includes a favorites service.
Claim 12
Dependent Claim
14 words
The method of claim 1 wherein the user identity-based service includes an inbox service.
Claim 13
Dependent Claim
14 words
The method of claim 1 wherein the user identity-based service includes a lists service.
Claim 14
Dependent Claim
14 words
The method of claim 1 wherein the user identity-based service includes a location service.
Claim 15
Dependent Claim
14 words
The method of claim 1 wherein the user identity-based service includes an alerts service.
Claim 16
Dependent Claim
14 words
The method of claim 1 wherein the user identity-based service includes a profile service.
Claim 17
Dependent Claim
14 words
The method of claim 1 wherein the user identity-based service includes a presence service.
Claim 18
Dependent Claim
14 words
The method of claim 1 wherein the user identity-based service includes a wallet service.
Claim 19
Dependent Claim
24 words
The method of claim 1 wherein the user identity-based service schema includes at least one defined field for extending the user identity-based service schema.
Claim 20
Dependent Claim
50 words
The method of claim 1 wherein the location information includes a uniform resource identifier for the user identity-based service, realm information of a Kerberos domain controller (KDC), and a service principal name for obtaining an identity license to authorize the requester to use the user identity-based service from the KDC.
Claim 21
Dependent Claim
33 words
The method of claim 1 wherein the location information includes a uniform resource identifier for the user identity-based service and an identity license to authorize the requester to use the user identity-based service.
Claim 22
Dependent Claim
35 words
The method of claim 1 wherein the location information includes referral information that points to another my-services service, wherein the another my-services service to provide location information to the requester for the user identity-based service.
Claim 23
Dependent Claim
23 words
The method of claim 21 wherein the referral information includes an identity license to authorize the requester to use the user identity-based service.
Claim 24
Dependent Claim
45 words
The method of claim 1 wherein the data is received by the user identity-based service in accordance with a pull model, wherein the pull model includes receiving the data from the another user identity-based service in response to a query from the user identity-based service.
Claim 25
Dependent Claim
27 words
The method of claim 1 wherein the push model uses a Service-to-Service Communication Protocol (SSCP), wherein the SSCP provides communication between user identity-based services in different realms.
Claim 26
Dependent Claim
22 words
A computer readable storage medium including computer readable instructions that when executed by a computer perform the method of claim 1 .
References Cited (Backward Citations)
US5446880A
Cited
US5666534A
Cited
US5487141A
Cited
US5819092A
Cited
US5634053A
Cited
US5754111A
Cited
US5790785A
Cited
US5862325A
Cited
US6018343A
Cited
WO1998038585A1
Cited
US5987454A
Cited
US6185551B1
Cited
US6044372A
Cited
US6442549B1
Cited
US5956730A
Cited
US5983273A
Cited
US6081840A
Cited
US6269369B1
Cited
US5974416A
Cited
US6457066B1
Cited
US6336119B1
Cited
US6122348A
Cited
US5999932A
Cited
US6415322B1
Cited
US6161125A
Cited
US6141778A
Cited
US6148301A
Cited
US6161139A
Cited
US6167408A
Cited
US6516341B2
Cited
US6480885B1
Cited
US6453317B1
Cited
US6275824B1
Cited
US6480850B1
Cited
US6324544B1
Cited
US6839733B1
Cited
US6317783B1
Cited
US6516315B1
Cited
US20020013788A1
Cited
US6334151B1
Cited
US6266690B1
Cited
US6401085B1
Cited
US6023223A
Cited
US6343287B1
Cited
US20020120685A1
Cited
US6526438B1
Cited
US6405191B1
Cited
US6651217B1
Cited
US6732080B1
Cited
US20030140112A1
Cited
US6556995B1
Cited
US6697865B1
Cited
US20050065950A1
Cited
US6643652B2
Cited
US20020049749A1
Cited
US20020040369A1
Cited
US20010044827A1
Cited
US6591260B1
Cited
US20010029470A1
Cited
US20050013417A1
Cited
US20030229529A1
Cited
US20040199663A1
Cited
US6584564B2
Cited
US6662340B2
Cited
US6792466B1
Cited
US6643650B1
Cited
US6789126B1
Cited
US6772216B1
Cited
US6990513B2
Cited
US20020059425A1
Cited
US20020095399A1
Cited
US20020026426A1
Cited
US6414635B1
Cited
US20020065881A1
Cited
US20020063732A1
Cited
US20020069298A1
Cited
US20020129000A1
Cited
US20020116232A1
Cited
US20030220891A1
Cited
US20020099593A1
Cited
US20020154161A1
Cited
US20020169876A1
Cited
US6986145B2
Cited
US6980993B2
Cited
US20030131073A1
Cited
US20050278366A1
Cited
US20060036642A1
Cited
US20030023623A1
Cited
US20040199869A1
Cited
US20040199861A1
Cited
US20050278344A1
Cited
US20050273692A1
Cited
US20030115228A1
Cited
US20030131069A1
Cited
US20030131142A1
Cited
US20030101190A1
Cited
US20040205526A1
Cited
US20040210839A1
Cited
US20040006564A1
Cited
US20040006590A1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2010-11-26 | 2011-05-28 | 2011-11-27 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2014-11-26 | 2015-05-28 | 2015-11-27 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2018-11-26 | 2019-05-28 | 2019-11-27 | $7700.00 | Window Closed / Lapsed |