US2018075093A1PendingUtilityA1

Sharing document links from multiple data providers

Assignee: MICROSOFT TECHNOLOGY LICENSING LLCPriority: Nov 22, 2013Filed: Sep 19, 2017Published: Mar 15, 2018
Est. expiryNov 22, 2033(~7.3 yrs left)· nominal 20-yr term from priority
H04L 67/2823H04L 67/2842H04L 67/1091H04L 51/08G06F 17/30424H04L 67/16H04L 67/565H04L 67/51H04L 67/568G06F 16/245
49
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A document sharing system includes a plurality of different data provider implementations. The document sharing system exposes a common application programming interface to a plurality of different clients and receives data requests identifying a given data provider, from the clients. The document sharing system then uses the data provider implementation for the data provider identified in the request, in order to obtain the requested data, and place it in a common data structure that is returned to the client.

Claims

exact text as granted — not AI-modified
1 - 20 . (canceled) 
     
     
         21 . A computer-implemented method, comprising:
 receiving a request for message data, the request being associated with a client device;   based on the request:
 obtaining first message data from a first data provider, the first message data corresponding to a first data structure, and 
 obtaining second message data from a second data provider, the second message data corresponding to a second data structure that is different than the first data structure; 
   placing the first message data and the second message data in a common data structure that is associated with the client device and defines a single presentation view for Tendering the first and second message data on the client device; and   providing the first and second message data in the common data structure to the client device.   
     
     
         22 . The computer-implemented method of  claim 21 , wherein the first data structure is generated by the first data provider, the second data structure is generated by the second data provider, and wherein the first data provider is different than the second data provider. 
     
     
         23 . The computer-implemented method of  claim 22 , wherein the common data structure defines a same data structure that is the same regardless of the first and second data structures being generated by the first and second data providers from which message data is obtained, respectively. 
     
     
         24 . The computer-implemented method of  claim 21 , wherein placing the first message data and the second message data in the common data structure comprises:
 parsing the first message data and the second message data into correspondingly parsed portions; and   placing the parsed portions into the common data structure.   
     
     
         25 . The computer-implemented method of  claim 21 , wherein the first message data obtained from the first data provider corresponds to a first message, and the second message data obtained from the second data provider corresponds to a second message that is separate from the first message. 
     
     
         26 . The computer-implemented method of  claim 21 , wherein the first message data corresponds to a first portion of a particular message associated with a user, and the second message data corresponds to a second portion of the particular message. 
     
     
         27 . The computer-implemented method of  claim 26 , wherein the first portion of the message corresponds to a first type of content, and the second portion of the message corresponds to a second type of content. 
     
     
         28 . The computer-implemented method of  claim 27 , wherein the first type of content comprises content included in the message and wherein the second type of content comprises content attached to the message. 
     
     
         29 . The computer-implemented method of  claim 21 , wherein the client device comprises a first client device, and further comprising:
 based on the request, identifying a particular user account;   identifying one or more other client devices, other than the first client device, associated with the particular user account; and   providing the first and second message data in the common data structure to the first client device and the one more other client devices such that the first and second message data is rendered in the same single presentation view across the client devices.   
     
     
         30 . A computing system comprising:
 a processor; and   memory storing instructions executable by the processor, wherein the instructions, when executed, configure the computing system to:
 receive a first request for message data associated with a first message; 
 based on the first request, obtain first message data from a first data provider that corresponds to a first data structure; 
 receive a second request for message data associated with a second message; 
 based on the second request, obtain second message data from a second data provider that corresponds to a second data structure that is different than the first data structure; 
 place the first message data and the second message data in a common data structure that defines a single presentation view for rendering the first and second message data on a client device associated with the first and second message; and 
 provide the first and second message data in the common data structure to the client device. 
   
     
     
         31 . The computing system of  claim 30 , wherein the instructions configure the computing system to;
 define the common data structure as a same structure of data, that is the same regardless of the first and second data structures associated with the first and second data providers from which the first and second message data is obtained, respectively.   
     
     
         32 . The computing system of  claim 30 , wherein the instructions configure the computing system to:
 parse the first and second message data into correspondingly parsed portions; and   placing the parsed portions in the common data structure.   
     
     
         33 . The computing system of  claim 30 , wherein the client device comprises a first client device, and wherein the instructions configure the computing system to:
 identify the first message as being associated with the first client device; and   identify the second message as being associated with a second client device.   
     
     
         34 . The computing system of  claim 33 , wherein the instructions configure the computing system to:
 place the first message data and the second Message data in the common data structure for rendering the first and second message data in a same presentation style across the first client device and the second client device.   
     
     
         35 . The computing system of  claim 34 , wherein the same presentation style provides a similar visual representation of the first message data and the second message data across the first client device and the second client device. 
     
     
         36 . The computing system of  claim 30 , wherein the instructions configure the computing system to:
 expose by a first data provider implementation, a first application programming interface configured to interact with the first data provider to obtain the first message data; and   expose, by a second data provider implementation, a second application programming interface configured to interact with the second data provider to obtain the second message data.   
     
     
         37 . The computing system of  claim 32 , wherein the instructions configure the computing system to:
 parse the first message data using first provider-specific parsing to identify a portion of the first message data to be included in the common data structure; and   parse the second message data using second provider-specific parsing to identify a portion of the second message data to be included in the common data structure.   
     
     
         38 . A computing system comprising:
 a communication component configured to receive a request for message data associated with a client device;   a data provider identifier component configured to, based on the request for message data:
 identify a first data provider to obtain first message data having a first data structure, and 
 identify a second data provider to obtain second message data having a second data structure, the second data structure being different than the first data structure; 
   a common data model component configured to place the first message data and the second message data in a common data structure that defines a single presentation view for rendering the first and second message data on the client device; and   wherein the client communication component is configured to provide, to the client device, the first and second message data in the common data structure.   
     
     
         39 . The computing system of  claim 38 , wherein the first message data corresponds to a first type of message content, and the second message data corresponds to a second type of message content, the second type being different than the first type. 
     
     
         40 . The computing system of  claim 39 , wherein the data provider identifier is configured to:
 identify the first data provider as a provider of the first type of message content, and   identify the second data provider as a provider of the second type of message content, wherein the second type of message content comprises a message attachment.

Join the waitlist — get patent alerts

Track US2018075093A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.