|Publication number||US7319979 B2|
|Application number||US 09/823,084|
|Publication date||Jan 15, 2008|
|Filing date||Mar 29, 2001|
|Priority date||Mar 29, 2001|
|Also published as||US20020143641|
|Publication number||09823084, 823084, US 7319979 B2, US 7319979B2, US-B2-7319979, US7319979 B2, US7319979B2|
|Inventors||Christian R. Thomas, Narasimha R. Edala, Joel I. Marcey|
|Original Assignee||Intel Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (12), Non-Patent Citations (2), Referenced by (7), Classifications (37), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This invention relates to matching and interaction of clients and Internet services, more particularly, dynamically interacting, at runtime, with an Internet service using a client specified communication proxy type and protocol, the client and the Internet service matched by a broker.
Several technologies are available for discovering devices and web services, including Salutation, E-Speak, Jini, and Universal Description Discovery and Integration (UDDI). These technologies are often employed by Internet services, clients that request Internet services, and brokers to help coordinate interaction between an Internet service and a client. Salutation and E-Speak rely on a proprietary transport that funnels through a broker, requiring clients and services to be built with respective products such that both use an agreed protocol. Jini provides a Java object to clients to interact with a service, requiring the Java object to interact with another Java object alone, whether it is a Java client or a Java wrapper. The protocol used between the Java object and the service is determined by the service. UDDI provides a client with Web Service Description Language (WSDL) and the client develops a communications code based on methods and parameters disclosed by the WSDL.
Currently employed technologies utilize a service, a broker and a communications proxy for clients to interact with an Internet service, but they fail to provide a method, a required Application Program Interface (API) and implementations for clients to specify a desired application-level transport protocol and a language/component technology. With current technologies, a client has no ability to specify a protocol that makes the most sense for the client. As an example of a conventional method, Jini, a server centric model, provides a Java object to clients to interact with a service. There is no negotiation between the service and the client for type of proxy. The protocol used between the Java object and the service is determined by the service.
Additional advantages of the invention will become apparent upon reading the following detailed description and upon reference to the drawings, in which:
Exemplary embodiments are described with reference to specific configurations. Those of ordinary skill in the art will appreciate that various changes and modifications can be made while remaining within the scope of the appended claims. Additionally, well-known elements, devices, components, circuits, process steps and the like are not set forth in detail in order to avoid obscuring the present invention.
As existing businesses and new businesses expand to the Internet, brokers and repositories play an increasing role as focal points in the Internet infrastructure. In an embodiment of the invention, a method is provided for clients to locate Internet services fulfilling the clients needs. In contrast to currently employed technologies, an embodiment of the invention provides a client centric model. Clients and Internet services are matched by a broker. In an embodiment of the invention, clients specify a type of communications proxy that can be different than a proxy used by an Internet service, promoting interaction between heterogeneous systems. In an embodiment, the invention provides a method and apparatus for clients to dynamically interact, at runtime, with an Internet service using at least one of a client specified language/component technology and a client specified application-level communications protocol. In an embodiment, a client requests, to a broker, a specific language/component technology (communication proxy), and, optionally, an application-level transport protocol. The broker matches the client request and an Internet service, and transmits metadata to the client enabling the client to locate the matched Internet service communication proxy. The language/component technologies include Java, common language runtime (CLR), component object model (COM), Win32 binaries, etc. The application-level communications protocols include hypertext transfer protocol (HTTP), simple mail transfer protocol (SMTP), simple object access protocol (SOAP), secure sockets layer (SSL/HTTPS), secure HTTP (S-HTTP), etc. In an embodiment, the client downloads the requested communication proxy and dynamically interacts, at runtime, with an Internet service using the requested communication proxy, the communication proxy being local to the client. In an embodiment of the invention, a client application is executing, and during runtime the client is interacting with the communications proxy. By “dynamically interact” it is meant, in an embodiment of the invention, that the client has no prior knowledge of what is needed to interact with an Internet service. In an embodiment of the invention, the client is relieved from having to develop a remote communications code.
As shown in
As shown in
As shown in functional block 202, Client 100 registers with Broker 102 to request and locate a desired service that provides a client-requested type of communication proxy and protocol. As shown in functional block 204, Broker 102 locates a match between Client 100 request and Service 104 registered services. As shown in functional block 206, Broker 102 provides the stored metadata to Client 100. In an embodiment, Broker 102 provides a digital certificate to Client 100 ensuring the security of downloading the metadata. As shown in functional block 208, Client 100 parses the metadata and determines the location and name of the communication proxy
As shown in functional block 210, Client 100 downloads, to its node, communications proxy 106 based on the location provided with the metadata returned from the Broker 102. In an embodiment, Client 100 uses a protocol to download communications proxy 106. The chosen type of communications proxy must be compatible with the environment of Client 100 so that Client 100 can interact with proxy 106. In an embodiment, after Client 100 downloads a communications proxy, Client 100 uses dynamic method discovery and invocation mechanisms. For example, in an embodiment, reflection is used with C sharp (an object-oriented programming language), and Client 100 discovers at runtime (as opposed to build-time) the methods and parameters within communication proxy 106. In an embodiment, Service 104 provides proxies supporting more than one protocol. In an embodiment, Client 100 downloads one communication proxy from Service 104 and can use multiple protocols supported by a single communication proxy.
As shown in functional block 212, Client 100 interacts directly with local communication proxy 106 to communicate with Service 104. By “local” it is meant that Client 100 and proxy 106 share the same node. The interaction between Client 100 and Service 104 is simplified since Client 100 interacts only with a local component, the communications proxy.
Client 100 downloads a communication proxy and interacts with Service 104 (by interacting with proxy 106) at runtime. If the type of protocol is not significant to Client 100, or if Client 100 fails to choose a protocol, then a default protocol of the specified communications proxy is used. In an embodiment, Client 100 is required to specify a proxy type. In an embodiment, Client 100 is required to specify a proxy type and a protocol.
As shown in functional block 214, communications proxy 106 directly interacts with Service 104 on behalf of Client 100. The remote communications burden is left to communications proxy 106. Since Service 104 provides communications proxy 106, communication proxy 106 includes the necessary logic to connect and communicate with Service 104. Client 100 is relieved of concerns including firewalls of Service 104, since proxy 106 includes the necessary information and handles such concerns. In an embodiment, proxy 106 has accessibility to the intranet and extranet of Service 104 for any needs of Client 100.
In an embodiment, Service 104 provides as many communication proxies as it desires. In an embodiment Service 104 provides no communications proxies. If no communications proxies are provided by Service 104, or if none of the provided communication proxies fulfill the needs of Client 100, then, in an embodiment, Client 100 uses a service description language provided as part of the metadata and optionally uses SOAP to interact with Service 104. In an embodiment, Client 100 receives service description language information from Broker 102 and develops an application, its own communications code, to communicate with Service 104.
The methods of a client, the methods of a broker and the methods of a service individually represent an embodiment of the invention as described below.
In an embodiment of the invention, a machine readable medium is provided having instructions which when executed by a machine cause the machine to perform operations. The operations performed include requesting a desired Internet service to a broker, requesting a desired communication proxy to a broker, receiving metadata from the broker, receiving the desired communication proxy, and interacting with an Internet service using the desired communication proxy. In an embodiment of the invention, the machine downloads the desired communication proxy to a node local to a client. In an embodiment of the invention, the interacting is accomplished at runtime. In an embodiment of the invention, the interacting is dynamic interacting. The machine-readable storage medium includes any mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine (e.g., a computer). For example, a machine-readable medium includes read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.); etc.
Having disclosed exemplary embodiments, modifications and variations may be made to the disclosed embodiments while remaining within the spirit and scope of the invention as defined by the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US6026414 *||Mar 5, 1998||Feb 15, 2000||International Business Machines Corporation||System including a proxy client to backup files in a distributed computing environment|
|US6167438 *||May 22, 1997||Dec 26, 2000||Trustees Of Boston University||Method and system for distributed caching, prefetching and replication|
|US6542908 *||Mar 22, 2000||Apr 1, 2003||International Business Machines Corporation||Technique for automatically and transparently transforming software components into software components capable of execution in a client/server computing environment|
|US6594700 *||Jun 14, 1999||Jul 15, 2003||International Business Machines Corporation||System and method for implementing a universal service broker interchange mechanism|
|US6708223 *||Dec 9, 1999||Mar 16, 2004||Microsoft Corporation||Accelerating a distributed component architecture over a network using a modified RPC communication|
|US6735771 *||Mar 12, 1999||May 11, 2004||Perot Systems Corporation||System and method for delivering web services using common object request broker architecture|
|US6922685 *||May 22, 2001||Jul 26, 2005||Mci, Inc.||Method and system for managing partitioned data resources|
|US6950875 *||Oct 19, 2000||Sep 27, 2005||Sun Microsystems, Inc.||Message conductors in a distributed computing environment|
|US20020087714 *||Dec 28, 2000||Jul 4, 2002||Sun Microsystems, Inc.||Method, system, and program for managing the rate at which client requests for a service are transmitted|
|US20020133581 *||Mar 16, 2001||Sep 19, 2002||Embrace Networks, Inc.||System and method to manage network-enabled embedded devices operating under various protocols|
|US20050021759 *||Jun 24, 2004||Jan 27, 2005||Gupta Abhay K.||Method for locating and retaining new software on a local server|
|WO2000077634A1 *||May 30, 2000||Dec 21, 2000||Sun Microsystems, Inc.||Integration of small footprint device applications and services with network-based services|
|1||*||Gopalan, Suresh Rai, "Jini Technology"; published on the Web Cornucopia (C) site and last updated on Dec. 19, 1998, extracted from the Internet Google site on Apr. 19, 2004.|
|2||*||Waldo, Jim, "The Jini Architecture for network-centric computing"; Communications of the ACM v42n7 pp. 76-82 Jul. 1999 ISSN: 0001-0782; extracted from Dialog on Jul. 5, 2007; Dialog File 15:ABI/Inform( R); 01850272 05-01264.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7739301 *||Mar 17, 2004||Jun 15, 2010||Netapp, Inc.||Method and apparatus for improving file system proxy performance and security by distributing information to clients via file handles|
|US7752080||Jul 6, 2010||Greener Jeremy D||System and method for interactively providing services through a central hub|
|US8396973 *||Mar 12, 2013||Microsoft Corporation||Distributed speech service|
|US8949390 *||Aug 8, 2003||Feb 3, 2015||International Business Machines Corporation||Management of service quality information in web services|
|US20050210072 *||Mar 17, 2004||Sep 22, 2005||Bojinov Hristo I||Method and apparatus for improving file system proxy performance and security by distributing information to clients via file handles|
|US20050235053 *||Aug 8, 2003||Oct 20, 2005||Akira Sano||Network system, provider, management site, requester, and program|
|US20060101146 *||Feb 16, 2005||May 11, 2006||Microsoft Corporation||Distributed speech service|
|U.S. Classification||705/26.44, 719/315, 709/203, 709/223, 709/235, 709/226, 719/316, 709/216, 709/230, 707/999.001, 707/999.202, 705/26.62, 705/27.1|
|International Classification||G06Q30/02, G06Q30/06, H04L29/08, G06F15/177, G06F15/167, G06F15/16, G06F9/46, G06F15/173|
|Cooperative Classification||Y10S707/99931, Y10S707/99953, G06Q30/02, G06Q30/0619, G06Q30/0641, H04L67/02, H04L67/2819, H04L67/2814, G06Q30/0625, G06F9/548|
|European Classification||G06F9/54P1, G06Q30/02, G06Q30/0619, G06Q30/0641, G06Q30/0625, H04L29/08N1|
|Mar 29, 2001||AS||Assignment|
Owner name: INTEL CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:THOMAS, CHRISTIAN R.;EDALA, NARASIMHA R.;MARCEY, JOEL I.;REEL/FRAME:011676/0324
Effective date: 20010328
|Jul 6, 2011||FPAY||Fee payment|
Year of fee payment: 4
|Jul 1, 2015||FPAY||Fee payment|
Year of fee payment: 8