Messaging infrastructure for identity-centric data access

• US 6,985,958 B2
• Filed: 10/22/2001
• Issued: 01/10/2006
• Est. Priority Date: 03/14/2001
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Leach, Paul J., Simon, Daniel R., Ward, Richard B., Weinert, Alexander T., Moore, George M., Pierce, Shaun D., Hyman, Robert M., Zwiegincew, Arthur, Burner, Michael G., Pincus, Jonathan D., Lucovsky, Mark, Gundotra, Vivek
• Primary Examiner(s): VU, VIET D
• Application Number:
  US10/003,754
• Publication Number:
  US 20020174125A1
• Time in Patent Office: 1,541 Days
• Field of Search: 709/230, 709/236, 709/237, 709/245, 709/246, 719/313, 719/315, 719/316, 707/103, 707/104
• US Class Current: 709/230
• 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/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting
• CPC Class Codes: H04L 12/1859 adapted to provide push services, e.g. data channels
• CPC Class Codes: H04L 12/1863 comprising mechanisms for improved reliability, e.g. status reports arrangements for detecting or preventing errors by carrying supervisory signal the return channel H04L1/16
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/1425 Traffic logging, e.g. anomaly detection
• 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/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 messaging data structure for accessing data in an identity-centric manner. An identity may be a user, a group of users, or an organization. Instead of data being maintained on an application-by-application basis, the data associated with a particular identity is stored by one or more data services accessible by many applications. The data is stored in accordance with a schema that is recognized by a number of different applications and the data service. The messaging data structure includes fields that identify the target data object to be operated upon using an identity field, a schema field, and an instance identifier field. In addition, the desired operation is specified. Thus, the target data object is operated on in an identity-centric manner.

Claims

1. In a computer network that includes a plurality of applications that operate on data objects associated with identities, the computer network also including a plurality of services that maintain data objects associated with the identity, each service managing at least data objects that follow a corresponding data type schema, a computer-readable medium storing or carrying thereon a data structure that represents a request to perform an operation on a data object associated with an identity, the data structure following a message schema, the data structure including the following data fields that are structured in accordance with the message schema:

one or more data fields that identify one of a plurality of identities who owns a data object to be accessed by one of a plurality of mobile applications in accordance with an identity-centric, as opposed to an application-centric, data access model;

one or more data fields that identify one or more services that manage a plurality of data objects for the plurality of identities including the identity who owns the data object to be accessed, at least some of the data objects being organized in accordance with a data type schema;

one or more data fields that identify one of a plurality of data type schemas corresponding to one of the plurality of mobile applications that access the plurality of data objects managed by the one or more services, wherein a particular data object to be accessed is identifiable from at least the identification of the identity who owns the data object to be accessed and the identification of the data type schema; and

one or more data fields that identify an operation to be performed on the particular data object.

2. A computer-readable medium in accordance with claim 1, wherein the message schema follows a formal message schema.

3. A computer-readable medium in accordance with claim 1, further comprising the following:

one or more data fields that identify correlation information for use in correlating the request with a response to the request.

4. A computer-readable medium in accordance with claim 3, wherein the one or more data fields that identify correlation information are included in header information defined by an underlying transport protocol used to transmit the request.

5. A computer-readable medium in accordance with claim 4, wherein the data structure further includes the following:

one or more data fields that identify a transport protocol used to transmit the request.

6. A computer-readable medium in accordance with claim 5, where the one or more data fields that identify a transport protocol identify a version of HyperText Transport Protocol (HTTP) as the transport protocol used to transmit the request.

7. A computer-readable medium in accordance with claim 3, wherein the one or more data fields that identify the correlation information comprises the following:

one or more data fields that identifies a message identifier.

8. A computer-readable medium in accordance with claim 7, wherein the transport protocol used to transport the request is not request/response oriented.

9. A computer-readable medium in accordance with claim 7, wherein the data structure further includes the following:

one or more data fields that identifies a transport protocol used to transmit the request.

10. A computer-readable medium in accordance with claim 9, where the one or more data fields that identifies a transport protocol identifies a version of Simple Mail Transport Protocol (SMTP) as the transport protocol used to transmit the request.

11. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify the data type schema are human-readable.

12. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify the data type schema are not human-readable.

13. A computer-readable medium in accordance with claim 1, wherein the data structure further includes the following:

one or more data fields that identify an instance of a data object that follows the data type schema and that is associated with the identity, wherein the particular data object to be accessed is identifiable from at least the identification of the identity, the identification of the data type schema, and the identification of the instance.

14. A computer-readable medium in accordance with claim 13, wherein the data structure further includes the following:

one or more data fields that identify a requestor of the operation.

15. A computer-readable medium in accordance with claim 14, wherein the data structure further includes the following:

one or more data fields that identify a response address where a response to the request is to be directed.

16. A computer-readable medium in accordance with claim 15, wherein the data structure further includes the following:

one or more data fields that identify a protocol used to transport the request.

17. A computer-readable medium in accordance with claim 14, wherein the data structure further includes the following:

one or more data fields that identify a protocol used to transport the request.

18. A computer-readable medium in accordance with claim 13, wherein the data structure further includes the following:

one or more data field that identify a response address where a response to the request is to be directed.

19. A computer-readable medium in accordance with claim 18, wherein the data structure further includes the following:

one or more data fields that identify a protocol used to transport the request.

20. A computer-readable medium in accordance with claim 13, wherein the data structure further includes the following:

one or more data fields that identify a protocol used to transport the request.

21. A computer-readable medium in accordance with claim 1, wherein the data structure further includes the following:

one or more data fields that identify a requestor of the operation.

22. A computer-readable medium in accordance with claim 21, wherein the data structure further includes the following:

one or more data fields that identify a response address where a response to the request is requested to be directed.

23. A computer-readable medium in accordance with claim 22, wherein the data structure further includes the following:

one or more data fields that identify a protocol used to transport the request.

24. A computer-readable medium in accordance with claim 21, wherein the data structure further includes the following:

one or more data fields that identify a protocol used to transport the request.

25. A computer-readable medium in accordance with claim 1, wherein the data structure further includes the following:

one or more data fields that identify a response address where a response to the request is to be directed.

26. A computer-readable medium in accordance with claim 25, wherein the data structure further includes the following:

one or more data fields that identify a protocol used to transport the request.

27. A computer-readable medium in accordance with claim 1, wherein the data structure further includes the following:

one or more data fields that identify a protocol used to transport the request.

28. A computer-readable medium in accordance with claim 1, wherein the computer-readable medium is one or more physical storage media.

29. A computer-readable medium in accordance with claim 1, wherein the computer-readable medium has stored thereon an encoded form of the data structure.

30. A computer-readable medium in accordance with claim 1, wherein the computer-readable medium has stored thereon a plain text form of the data structure.

31. A computer-readable medium in accordance with claim 1, wherein at least some of the one or more data fields that identify the data type schema are the same as at least some of the one or more data fields that identify an address such that the data type schema is at least partially implied by the address of the service.

32. A computer-readable medium in accordance with claim 1, wherein none of the one or more data fields that identify the data type schema are the same as any of the second set of one or more data fields that identify an address.

33. A computer-readable medium in accordance with claim 1, wherein the data object comprises content that includes actual data of interest.

34. A computer-readable medium in accordance with claim 33, wherein the data structure further includes the following:

one or more data fields that identify that the data object comprises content.

35. A computer-readable medium in accordance with claim 1, wherein the data object comprises access control information associated with other data objects.

36. A computer-readable medium in accordance with claim 35, wherein the data structure further includes the following:

one or more data fields that identify that the data object comprises access control information.

37. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify the operation to be performed includes the following:

one or more data fields that identify a fragment of the particular data object to be accessed.

38. A computer-readable medium in accordance with claim 37, wherein the one or more data fields that identify a fragment of the particular data object identify that all of the data object is to be accessed.

39. A computer-readable medium in accordance with claim 37, wherein the one or more data fields that identify a fragment of the particular data object identify one or more data fields of the particular data object as being the elements that the operation is to be applied to.

40. A computer-readable medium in accordance with claim 37, wherein the one or more data fields that identify a fragment of the particular data object identify a data field of the particular data object as being the data field that the operation is to be applied to.

41. A computer-readable medium in accordance with claim 37, wherein the one or more data fields that identify the operation to be performed further includes the following:

one or more data fields that identify a specific operation that is to be performed on the fragment of the particular data object.

42. A computer-readable medium in accordance with claim 41, wherein the one or more data fields that identify a specific operation indicate that the fragment is to be added to the particular data object.

43. A computer-readable medium in accordance with claim 41, wherein the one or more data fields that identify a specific operation indicate that the fragment is to be deleted from the identity-specific data.

44. A computer-readable medium in accordance with claim 41, wherein the one or more data fields that identify a specific operation indicate that the fragment is to be modified.

45. A computer-readable medium in accordance with claim 41, wherein the one or more data fields that identify a specific operation indicate a query related to the fragment.

46. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify the data type schema identify a data type schema corresponding to personal address information.

47. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify the data type schema identify a data type schema corresponding to contacts information.

48. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify the data type schema idenitify a data type schema corresponding to grocery list information.

49. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify the data type schema identify a data type schema corresponding to in-box information corresponding to the identity.

50. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify the data type schema identify a data type schema corresponding to music service information.

51. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify the data type schema identify a data type schema corresponding to calendar information.

52. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify the data type schema identify a data type schema corresponding to document collections.

53. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify the data type schema identify a data type schema corresponding to application setting information.

54. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify the data type schema identify a data type schema corresponding to physical device information.

55. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify the data type schema identify a data type schema corresponding to favorite Web site information.

56. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify an identity identify a person.

57. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify an identity identify a group of people.

58. A computer-readable medium in accordance with claim 1, wherein the one or more data fields that identify an identity identify an organization.

59. A computer-readable medium in accordance with claim 1, wherein the data structure further comprises the following:

one or more data fields that identifies a path the request is to take on its way to the service.

60. A computer-readable medium in accordance with claim 59, wherein the one or more data fields that identify a path specify a plurality of routing segments to take on its way to the service.

61. A computer-readable medium in accordance with claim 60, wherein the one or more data fields that identify a path specify a transport protocol to use for the plurality of routing segments, wherein the transport protocol specified is different for at least some of the plurality of routing segments.

62. A computer-readable medium in accordance with claim 59, wherein the data structure further comprises the following:

one or more data fields that identify a path that the corresponding response is to take when responding.

63. A computer-readable medium in accordance with claim 62, wherein the one or more data fields that identify a path that the corresponding response is to take when responding specifies a transport protocol when responding to the request, wherein the transport protocol specified for the response is different than the transport protocol specified for the request.

64. A computer-readable medium in accordance with claim 1, wherein the data type formats are in accordance with a version of the eXtensible Markup Language (XML) specification.

65. A computer-readable medium in accordance with claim 1, wherein the message type format is in accordance with a version of the eXtensible Markup Language (XML) specification.

66. A computer-readable medium in accordance with claim 65, wherein the data structure is structured within a Simple Object Access Protocol (SOAP) envelope.

67. In a computer network that includes a plurality of applications that operate on data objects associated with identities, the computer network also including a plurality of services that maintain data objects associated with the identity, each service managing at least data objects that follow a corresponding data type schema, a method for generating a data structure that represents a request to perform an operation on a data object associated with an identity, the data structure following a message schema, the method including the following:

generating and inserting a first set of one or more data fields into the data structure in accordance with the message schema, the first set of one or more data fields identifying one of a plurality of identities who owns a data object to be accessed by one of a plurality of mobile applications in accordance with an identity-centric, as opposed to an application-centric, data access model;

generating and inserting a second set of one or more data fields into the data structure in accordance with the message schema, the second set of one or more data fields identifying one or more services that manage a plurality of data objects for the plurality of identities including the identity who owns the data object to be accessed, at least some of the data objects being organized in accordance with a data type schema;

generating and inserting a third set of one or more data fields into the data structure in accordance with the message schema, the third set of one or more data fields identifying one of a plurality of data type schemas corresponding to one of the plurality of mobile applications that access the plurality of data objects managed by the one or more services, wherein a particular data object to be accessed is identifiable from at least the identification of the identity who owns the data object to be accessed and the identification of the data type schema;

generating and inserting a fourth set of one or more data fields into the data structure in accordance with the message schema, the fourth set of one or more data fields identifying correlation information for use in correlating the request with a response to the request; and

generating and inserting a fifth set of one or more data fields into the data structure in accordance with the message schema, the fifth set of one or more data fields identifying an operation to be performed on the particular data object.

68. A method in accordance with claim 67, further comprising the following:

generating and inserting a sixth set of one or more data fields into the data structure in accordance with the message schema, the sixth set of one or more data fields identifying an instance of a data object that follows the data type schema and that is associated with the identity, wherein the particular data object to be accessed is identifiable from at least the identification of the identity, the identification of the data type schema, and the identification of the instance.

69. A method in accordance with claim 67, further comprising the following:

generating and inserting a sixth set of one or more data fields into the data structure in accordance with the message schema, the sixth set of one or more data fields identifying a request of the operation.

70. A method in accordance with claim 67, further comprising the following:

generating and inserting a sixth set of one or more data fields into the data structure in accordance with the message schema, the sixth set of one or more data fields identifying a response address where a response to the request is to be directed.

71. A method in accordance with claim 67, further comprising the following:

generating and inserting a sixth set of one or more data fields into the data structure in accordance with the message schema, the sixth set of one or more data fields identifying a protocol used to transport the request.

72. A computer program product for use in a computer network that includes a plurality of applications that operate on data objects associated with identities, the computer network also including a plurality of services that maintain data objects associated with the identity, each service managing at least data objects that follow a corresponding data type schema, the computer-program product for implementing a method for generating a data structure that represents a request to perform an operation on a data object associated with an identity, the data structure following a message schema, the computer program product comprising a computer-readable medium having stored thereon the following:

computer-executable instructions for generating and inserting a first set of one or more data fields into the data structure in accordance with the message schema, the first set of one or more data fields identifying one of a plurality of identities who owns a data object to be accessed by one of a plurality of mobile applications in accordance with an identity-centric, as opposed to an application-centric, data access model;

computer-executable instructions for generating and inserting a second set of one or more data fields into the data structure in accordance with the message schema, the second set of one or more data fields identifying one or more services that manage a plurality of data objects for the plurality of identities including the identity who owns the data object to be accessed, at least some of the data objects being organized in accordance with a data type schema;

computer-executable instructions for generating and inserting a third set of one or more data fields into the data structure in accordance with the message schema, the third set of one or more data fields identifying one of a plurality of data type schemas corresponding to one of the plurality of mobile applications that access the plurality of data objects managed by the one or more services, wherein a particular data object to be accessed is identifiable from at least the identification of the identity who owns the data object to be accessed and the identification of the data type schema;

computer-executable instructions for generating and inserting a fourth set of one or more data fields into the data structure in accordance with the message schema, the fourth set of one or more data fields identifying correlation information for use in correlating the request with a response to the request; and

computer-executable instructions for generating and inserting a fifth set of one or more data fields into the data structure in accordance with the message schema, the fifth set of one or more data fields identifying an operation to be performed on the particular data object.

73. A computer program product in accordance with claim 72, wherein the computer-readable medium further has stored thereon the following:

computer-executable instructions for generating and inserting a sixth set of one or more data fields into the data structure in accordance with the message schema, the sixth set of one or more data fields identifying an instance of a data object that follows the data type schema and that is associated with the identity, wherein the particular data object to be accessed is identifiable from at least the identification of the identity, the identification of the data type schema, and the identification of the instance.

74. A computer program product in accordance with claim 72, wherein the computer-readable medium further has stored thereon the following:

computer-executable instructions for generating and inserting a sixth set of one or more data fields into the data structure in accordance with the message schema, the sixth set of one or more data fields identifying a requestor of the operation.

75. A computer program product in accordance with claim 72, wherein the computer-readable medium further has stored thereon the following:

computer-executable instructions for generating and inserting a sixth set of one or more data fields into the data structure in accordance with the message schema, the sixth set of one or more data fields identifying a response address where a response to the request is to be directed.

76. A computer program product in accordance with claim 72, wherein the computer-readable medium further has stored thereon the following:

computer-executable instructions for generating and inserting a sixth set of one or more data fields into the data structure in accordance with the message schema, the sixth set of one or more data fields identifying a protocol used to transport the request.

77. A computer program product in accordance with claim 72, wherein the computer-readable medium is one or more physical storage media.

78. In a computer network that includes a plurality of applications that operate on data objects associated with identities, the computer network also including a plurality of services that maintain data objects associated with the identity, each service managing at least data objects that follow a corresponding data type schema, a method for interpreting a data structure that represents a request to perform an operation on a data object associated with an identity, the data structure following a message schema, the method including the following:

extracting and interpreting a first set of one or more data fields from the data structure in accordance with the message schema, the first set of one or more data fields identifying one of a plurality of identities who owns a data object to be accessed by one of a plurality of mobile applications in accordance with an identity-centric, as opposed to an application-centric, data access model;

extracting and interpreting a second set of one or more data fields from the data structure in accordance with the message schema, the second set of one or more data fields identifying one or more services that manage a plurality of data objects for the plurality of identities including the identity who owns the data object to be accessed, at least some of the data objects being organized in accordance with a data type schema;

extracting and interpreting a third set of one or more data fields from the data structure in accordance with the message schema, the third set of one or more data fields identifying one of a plurality of data type schemas corresponding to one of the plurality of mobile applications that access the plurality of data objects managed by the one or more services;

identifying a particular data object to be accessed based at least on the identification of the identity who owns the data object to be accessed and the identification of the data type schema;

extracting and interpreting a fourth set of one or more data fields from the data structure in accordance with the message schema, the fourth set of one or more data fields identifying correlation information for use in correlating the request with a response to the request;

extracting and interpreting a fifth set of one or more data fields from the data structure in accordance with the message schema, the fifth set of one or more data fields identifying an operation to be performed on the particular data object;

performing the operation on the particular data object; and

returning a response to the request, the response including at least some of the correlation information.

79. A method in accordance with claim 78, further comprising the following:

extracting and interpreting a sixth set of one or more data fields from the data structure in accordance with the message schema, the sixth set of one or more data fields identifying an instance of a data object that follows the data type schema and that is associated with the identity, wherein the particular data object to be accessed is identifiable from at least the identification of the identity, the identification of the data type schema, and the identification of the instance.

80. A method in accordance with claim 78, further comprising the following:

extracting and interpreting a sixth set of one or more data fields from the data structure in accordance with the message schema, the sixth set of one or more data fields identifying a requestor of the operation.

81. A method in accordance with claim 78, further comprising the following:

extracting and interpreting a sixth set of one or more data fields from the data structure in accordance with the message schema, the sixth set of one or more data fields identifying a response address where a response to the request is to be directed.

82. A method in accordance with claim 78, further comprising the following:

extracting and interpreting a sixth set of one or more data fields from the data structure in accordance with the message schema, the sixth set of one or more data fields identifying a protocol used to transport the request.

83. A computer program product for use in a computer network that includes a plurality of applications that operate on data objects associated with identities, the computer network also including a plurality of services that maintain data objects associated with the identity, each service managing at least data objects that follow a corresponding data type schema, the computer program product for implementing a method for interpreting a data structure that represents a request to perform an operation on a data object associated with an identity, the data structure following a message schema, the computer program product comprising a computer-readable medium having stored thereon the following:

computer-executable instructions for extracting and interpreting a first set of one or more data fields from the data structure in accordance with the message schema, the first set of one or more data fields identifying one of a plurality of identities who owns a data object to be accessed by one of a plurality of mobile applications in accordance with an identity-centric, as opposed to an application-centric, data access model;

computer-executable instructions for extracting and interpreting a second set of one or more data fields from the data structure in accordance with the message schema, the second set of one or more data fields identifying one or more services that manage a plurality of data objects for the plurality of identities including the identity who owns the data object to be accessed, at least some of the data objects being organized in accordance with a data type schema;

computer-executable instructions for extracting and interpreting a third set of one or more data fields from the data structure in accordance with the message schema, the third set of one or more data fields identifying one of a plurality of data type schemas corresponding to one of the plurality of mobile applications that access the plurality of data objects managed by the one or more services;

computer-executable instructions for identifying a particular data object to be accessed based at least on the identification of the identity who owns the data object to be accessed and the identification of the data type schema;

computer-executable instructions for extracting and interpreting a fourth set of one or more data fields from the data structure in accordance with the message schema, the fourth set of one or more data fields identifying correlation information for use in correlating the request with a response to the request;

computer-executable instructions for extracting and interpreting a fifth set of one or more data fields from the data structure in accordance with the message schema, the fifth set of one or more data fields identifying an operation to be performed on the particular data object;

computer-executable instructions for causing the operation to be performed on the particular data object; and

computer-executable instructions for causing a response to the request to be returned, the response including at least some of the correlation information.

84. A computer program product in accordance with claim 83, wherein the computer-readable medium further has stored thereon the following:

computer-executable instructions for extracting and interpreting a sixth set of one or more data fields from the data structure in accordance with the message schema, the sixth set of one or more data fields identifying an instance of a data object that follows the data type schema and that is associated with the identity, wherein the particular data object to be accessed is identifiable from at least the identification of the identity, the identification of the data type schema, and the identification of the instance.

85. A computer program product in accordance with claim 83, wherein the computer-readable medium further has stored thereon the following:

computer-executable instructions for extracting and interpreting a sixth set of one or more data fields from the data structure in accordance with the message schema, the sixth set of one or more data fields identifying a requestor of the operation.

86. A computer program product in accordance with claim 83, wherein the computer-readable medium further has stored thereon the following:

computer-executable instructions for extracting and interpreting a sixth set of one or more data fields from the data structure in accordance with the message schema, the sixth set of one or more data fields identifying a response address where a response to the request is to be directed.

87. A computer program product in accordance with claim 83, wherein the computer-readable medium further has stored thereon the following:

computer-executable instructions for extracting and interpreting a sixth set of one or more data fields from the data structure in accordance with the message schema, the sixth set of one or more data fields identifying a protocol used to transport the request.

88. A computer program product in accordance with claim 83, wherein the computer-readable medium is one or more physical storage media.