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

• US 20040199869A1
• Filed: 07/31/2002
• Published: 10/07/2004
• Est. Priority Date: 03/14/2001
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Lucovsky, Mark H., Guu, Yi-Wen, Yuan, Yun-Qi, Steckler, Paul Andrew, Pierce, Shaun D.
• Application Number:
  US10/209,831
• Publication Number:
  US 20040199869A1
• Time in Patent Office: Days
• US Class Current: 715/225
• 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/2115 Third party
• CPC Class Codes: G06F 2221/2117 User registration
• CPC Class Codes: G06F 2221/2119 Authenticating web pages, e.g. with suspicious links
• 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
• CPC Class Codes: Y10S 707/99931 : Database or file accessing
• CPC Class Codes: Y10S 707/99939 : Privileged access
• CPC Class Codes: Y10S 707/99942 : Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 : Generating database or data structure, e.g. via user interface

Abstract

A schema-based Wallet service for centralized access to per-user financial data, wherein access to data is based on each user'"'"'s identity. The Wallet 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 Wallet 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 Wallet schemas are arranged to provide 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, document 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 Wallet 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.

Claims

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 wallet document.

5. In a computer network, a method comprising,

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

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

constructing a wallet document including at least part of the data, the document arranged according to a defined schema for financial 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 that identifies a type of financial data;

a second set of data corresponding to identifying information about the type of financial data identified in the first set of data; and

wherein the first and second sets of data are regularized according to a schema in a centralized service such that an identity-based recipient of the data structure interprets the data according to the schema to obtain financial information from the centralized service.

9. The data structure of claim 8 wherein the first set of data comprises data corresponding to an account at a financial institution, and wherein the second set of data comprises an account number.

10. The data structure of claim 8 wherein the second set of data comprises a routing number.

11. The data structure of claim 8 wherein the second set of data comprises currency data associated with the account.

12. The data structure of claim 8 wherein the second set of data comprises a name associated with the account.

14. The data structure of claim 8 wherein the first set of data comprises data corresponding to a type of financial card, and wherein the second set of data comprises a card number.

15. The data structure of claim 8 wherein the second set of data comprises a name associated with the card.

16. The data structure of claim 8 wherein the second set of data comprises currency data associated with the card.

20. The data structure of claim 8 wherein the second set of data comprises an expiration date of the card.

21. The data structure of claim 8 wherein the second set of data comprises an issue date of the card.

22. The data structure of claim 8 wherein the second set of data comprises a date from which the card is valid.

13-1. The data structure of claim 13 wherein the location corresponds to an address.

19. The data structure of claim 8 wherein the second set of data comprises a location corresponding to an entity that is associated with the card.

19-2. The data structure of claim 18 wherein the card is a credit card, and wherein the location comprises a billing address.