TRANSPORT INDEPENDENT ARCHITECTURE
2 Assignments
0 Petitions
Accused Products
Abstract
A system for automating connection management in a manner that may be transparent to any actively communicating applications operating in a Network on Terminal Architecture (NoTA). An application level entity, such as an application node, may access another node by making a request to a high level communication structure via a high level interface. The high level structure may then interact with a lower level structure in order to facilitate a connection to a programmatic element on another device, for example, via a wireless communication transport.
40 Citations
52 Claims
-
1-30. -30. (canceled)
-
31. A method, comprising:
-
receiving an access request including at least one indicator identifying one or more services or applications, wherein the access request is transport-independent; mapping the at least one indicator to at least one interconnect address indicating one or more subsystems corresponding to the one or more services or applications, the at least one interconnect address being inserted into the transport-independent access request; mapping the at least one interconnect address in the access request to one or more transports capable of providing access to the one or more services or applications; and establishing a connection to access the one or more requested services or applications using at least one of the one or more mapped transports. - View Dependent Claims (32, 33, 34, 35, 36, 37)
-
-
38. A computer program product comprising a computer usable medium having computer readable program codes recorded in said medium, comprising:
-
a computer readable program code configured to receive an access request including identification of a service or application in a high level transport-independent communication structure via a high level interface; a computer readable program code configured to map the identification to at least one interconnect address indicating one or more subsystems corresponding to the requested service or application, the at least one interconnect address being inserted into the access request; a computer readable program code configured to pass the access request from the high level transport-independent communication structure to a low level communication structure via a low level interface, the low level communication structure including at least a transport-independent up structure and one or more transport-specific down structures; a computer readable program code configured to select, by the transport-independent up structure, one or more transport-specific down structures based on the at least one interconnect address, the selected transport-specific down structure corresponding to a particular transport; and a computer readable program code configured to establish access to the requested service or application using the transport. - View Dependent Claims (39, 40, 41, 42)
-
-
43. A device, comprising:
-
at least one communication module configured to support one or more wireless transports; and a processor coupled to the at least one communication module, the processor being configured to instruct one or more operational elements of the device to; receive an access request including identification of a service or application in a high level transport-independent communication structure via a high level interface; map the identification to at least one interconnect address indicating one or more subsystems corresponding to the requested service or application, the at least one interconnect address being inserted into the access request; pass the access request from the high level transport-independent communication structure to a low level communication structure via a low level interface, the low level communication structure including at least a transport-independent up structure and one or more transport-specific clown structures; select, by the transport-independent up structure, one or more transport-specific clown structures based on the at least one interconnect address, the transport-specific clown structure corresponding to a particular transport; and establish access to the requested service or application using the transport. - View Dependent Claims (44, 45, 46, 47, 48, 49)
-
-
50. A middleware layer in an operational structure, comprising:
-
an upper layer configured to receive identification for an application or service and to map the identification to an interconnect address; and a lower layer configured to receive the interconnect address and to map the interconnect address to one or more transports. - View Dependent Claims (51, 52)
-
Specification