Abstract protocol independent data bus

• US 8,326,948 B2
• Filed: 03/02/2010
• Issued: 12/04/2012
• Est. Priority Date: 03/02/2010
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Bykov, Evgueni N., Netrebchenko, Alexander V., Bergevin, Jon D.
• Primary Examiner(s): JEAN, FRANTZ B
• Application Number:
  US12/715,400
• Publication Number:
  US 20110219154A1
• Time in Patent Office: 1,008 Days
• Field of Search: 709/217, 709/219, 709/218, 709/230, 717/100, 717/108, 717/106, 717/116, 717/118, 719/330, 719/331, 719/332, 710/105, 710/107
• US Class Current: 709/219
• CPC Class Codes: G06F 13/385 for adaptation of a particular data processing system to different peripheral devices
• CPC Class Codes: G06F 2213/0058 Bus-related hardware virtualisation
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence

Abstract

An abstraction layer (e.g., transport) between consumer logic (e.g., presentation) and provider logic (e.g., business) that makes composition of, for example, many presentation technologies to many business logic data providers possible without imposing strict interface boundaries to each. The abstraction layer can be an abstract transport data model bus that provides serialization, transformation, and transport services. A core concept of the data access library implementation is a transmittable data object based on a flexible property bag data structure and abstract type system. Pluggable data providers declare the associated data model, and pluggable consumer clients declare the data model consumed (a many-to-many implementation). In other words, declarative (codeless) combinations of front ends and back ends are employed. Moreover, the abstraction layer is hidden from the developer.

Claims

1. A computer-implemented data bus system having a physical storage media, comprising:

consumer logic that declares a data model consumed, that interacts with disparate data providers that declare an associated data model, for processing of provider data therefrom;

a transport layer interstitial to the consumer logic and the data providers that provides protocol independent services for many-to-many handling of the provider data by the consumer logic, thereby employing codeless, declarative combinations of consumer logic and data providers; and

a processor that executes computer-executable instructions associated with at least one of the consumer logic or the transport layer.

2. The system of claim 1, wherein the transport layer provides serialization services, transformation services, and transport services that accommodate the disparate data providers.

3. The system of claim 1, wherein the transport layer processes modifications and extensions that are bound at runtime.

4. The system of claim 1, wherein the transport layer accommodates data providers that are both pluggable and declarative of associated data models.

5. The system of claim 1, wherein the transport layer accommodates consumer logic that is both pluggable and declarative of an associated data model.

6. The system of claim 1, wherein the transport layer accommodates declarative consumer logic and data providers.

7. The system of claim 1, wherein the transport layer accommodates data providers that utilize methods having variable signatures.

8. The system of claim 1, wherein the transport layer processes synchronous and asynchronous methods.

9. A computer-implemented data bus system having a physical media, comprising:

pluggable data providers that declare associated data models;

pluggable data consumers that declare associated data models for consumption;

a transport data bus interactively positioned between the pluggable data providers and pluggable data consumers that provides protocol independent services for many-to-many handling of data between the data providers and data consumers, thereby employing codeless, declarative combinations of pluggable data consumers and pluggable data providers; and

a processor that executes computer-executable instructions associated with at least one of the pluggable data providers, pluggable data consumers, or transport data bus.

10. The system of claim 9, wherein the transport data bus provides serialization services, transformation services, and transport services that accommodate the data providers and data consumers.

11. The system of claim 9, wherein the transport data bus processes modifications and extensions that are bound at runtime.

12. The system of claim 9, wherein the transport data bus interacts with data providers that utilize methods having variable signatures, the methods are synchronous and asynchronous.

13. The system of claim 9, wherein the transport data bus processes a command and command parameters directed from a data consumer that specifies a data provider.

14. The system of claim 9, wherein the transport data bus includes a proxy data gateway and a core data gateway.

15. A computer-implemented data bus method executable via a processor and memory, comprising acts of:

receiving pluggable data providers that declare associated data provider data models;

receiving pluggable data consumers that declare data provider data models that are consumable;

processing commands and data between the data consumers and the consumable data provider data models via a protocol independent transport data bus, thereby employing codeless, declarative combinations of pluggable data providers and pluggable data consumers; and

utilizing a processor that executes instructions stored in memory to perform at least one of the acts of receiving or processing.

16. The method of claim 15, further comprising processing the commands and data synchronously and asynchronously via the protocol independent transport data bus.

17. The method of claim 15, further comprising specifying a data provider in a command from which to obtain data for presentation by a data consumer.

18. The method of claim 15, further comprising accessing data of a data provider in a same process as a concrete class.

19. The method of claim 15, further comprising accessing data of a data provider through a proxy to a transport service as a concrete class.

20. The method of claim 15, further comprising returning a result of a command to a data consumer from a data provider in a form compatible with a data consumer.