Federated identity management for data repositories
US-2024348610-A1 · Oct 17, 2024 · US
US2016234337A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016234337-A1 |
| Application number | US-201315022770-A |
| Country | US |
| Kind code | A1 |
| Filing date | Sep 18, 2013 |
| Priority date | Sep 18, 2013 |
| Publication date | Aug 11, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method of establishing a network connection between an application hosted on a first network device and a second network device, comprising receiving data from the application indicating communication requirements for the network connection, identifying a plurality of alternative available transport level components; and based on the received data, selecting one of the transport level components for use in the network connection.
Opening claim text (preview).
1 . A method of establishing a network connection between an application hosted on a first network device and a second network device, comprising: receiving data from the application indicating communication requirements for the network connection; identifying a plurality of alternative available transport level components; and based on the received data, selecting one of the transport level components for use in the network connection. 2 . A method according to claim 1 , wherein the plurality of transport level components includes one or more transport protocols. 3 . A method according to claim 1 or 2 , wherein the plurality of transport level components includes one or more messaging patterns. 4 . A method according to claim 1 , wherein the transport level component is chosen so as to optimise the quality of service (QoS) of the network connection. 5 . A method according to claim 1 , wherein the communication requirements relate to one or more of the latency and bandwidth required for the network connection. 6 . A method according to claim 1 , wherein the choice of the transport level component is varied during the course of a single session between the application and the second network device. 7 . A method according to claim 6 , wherein a first one of the available transport level components is selected during initiation of the session and an alternative one of the available transport level components is subsequently selected during that same session. 8 . A method according to claim 1 , wherein the method includes receiving information about the network environment and the choice of transport level component is determined at least in part based on the information. 9 . A method according to claim 8 , wherein the selection of transport level components is varied overtime in response to changes in the network environment. 10 . A method according to claim 1 , wherein the first network device hosts a plurality of applications and the method comprises establishing a respective network connection for each application, the selection of transport components being carried out independently for each application. 11 . A method according to claim 10 , comprising generating a respective network socket for each application, the socket being generated based on the transport components selected for that application's network connection. 12 . A method according to claim 1 , comprising transmitting data from the application to the second network device across the network connection. 13 . A device for establishing a network socket for connecting an application to a communications network, the device comprising: a middleware component configured to interface with the application and to receive data from the application indicating communication requirements of the application; the middleware being operable to identify a plurality of alternative available transport level components for use in communicating data from the application over the network and to select one of the transport level components for generating the network socket. 14 . A device according to claim 13 , wherein the plurality of transport level components includes one or more transport protocols. 15 . A device according to claim 12 or 13 , wherein the plurality of transport level components includes one or more messaging patterns. 16 . A device according to claim 15 , wherein the transport level component is chosen so as to optimise the quality of service QoS of the network connection. 17 . A device according to claim 13 , wherein the communication requirements relate to one or more of the latency and bandwidth required for the network connection. 18 . A device according to claim 13 , wherein the middleware component is configured to vary the choice of the transport level component during the course of a single session between the application and the second network device. 19 . A device according to claim 18 , wherein the middleware component is configured to select a first one of the available transport level components during initiation of the session and to subsequently select an alternative one of the available transport level components during that same session. 20 . A device according to claim 13 , wherein the middleware is configured to receive as input information about the network environment and to select the transport level component at least in part based on the information. 21 . A device according to claim 13 , wherein the middleware is configured to interface with a plurality of applications and to receive data from each application indicating communication requirements of the respective application; the middleware being operable to select a transport level component for generating a respective network socket for each application, wherein the transport level components are selected independently for each application. 22 . A device according to claim 13 or 21 , wherein each application is hosted on the device. 23 . A system comprising a plurality of devices according to claim 22 . 24 . A system comprising a network device that hosts one or more applications; and one or more devices according to claim 13 or 21 . 25 . A computer readable storage medium comprising computer executable instructions that when executed by the computer will cause the compute to carry out a method according to claim 1 .
Initiating a communication · CPC title
in the transport layer [OSI layer 4] (H04L69/16 takes precedence) · CPC title
Initiating, continuing or ending a single-mode communication; Handshaking therefor {(H04N1/32614 takes precedence)} · CPC title
Electricity · mapped topic
taking into account QoS or priority requirements · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.