External interfaces Sample Clauses
External interfaces. The physical layer external interfaces of the Internet FWA system are: o Analogue line interface at the RSS o Packet data interface at the RSS
External interfaces. | How will connections to third party applications be upheld?
External interfaces. 4.7.1 [****]
4.7.2 Interface with Engineering.
4.7.3 [****]
4.7.4 Interface with Management.
4.7.5 Interface with end users. [****] -------------------------------------------------------------------------------- Prepared by: [****] 6 **** Represents material which has been redacted and filed separately with the Commission pursuant to a request for confidential treatment pursuant to Rule 406 under the Securities Act of 1933, as amended. SOW Tracking Number: Predictive_SOW_1999_1000.doc Description: ▇▇▇▇▇▇▇▇.▇▇▇ NOC Revision Number: 003 Creation Date: 05/14/99 Revision Date: 08/13/99 Issue Date: 08/13/99 [****] -------------------------------------------------------------------------------- Prepared by: [****] 7 **** Represents material which has been redacted and filed separately with the Commission pursuant to a request for confidential treatment pursuant to Rule 406 under the Securities Act of 1933, as amended. SOW Tracking Number: Predictive_SOW_1999_1000.doc Description: ▇▇▇▇▇▇▇▇.▇▇▇ NOC Revision Number: 003 Creation Date: 05/14/99 Revision Date: 08/13/99 Issue Date: 08/13/99 [****] -------------------------------------------------------------------------------- Prepared by: [****] 8 **** Represents material which has been redacted and filed separately with the Commission pursuant to a request for confidential treatment pursuant to Rule 406 under the Securities Act of 1933, as amended. SOW Tracking Number: Predictive_SOW_1999_1000.doc Description: ▇▇▇▇▇▇▇▇.▇▇▇ NOC Revision Number: 003 Creation Date: 05/14/99 Revision Date: 08/13/99 Issue Date: 08/13/99 [****] -------------------------------------------------------------------------------- Prepared by: [****] 9 **** Represents material which has been redacted and filed separately with the Commission pursuant to a request for confidential treatment pursuant to Rule 406 under the Securities Act of 1933, as amended. SOW Tracking Number: Predictive_SOW_1999_1000.doc Description: ▇▇▇▇▇▇▇▇.▇▇▇ NOC Revision Number: 003 Creation Date: 05/14/99 Revision Date: 08/13/99 Issue Date: 08/13/99 [****] -------------------------------------------------------------------------------- Prepared By: [****] 10 **** Represents material which has been redacted and filed separately with the Commission pursuant to a request for confidential treatment pursuant to Rule 406 under the Securities Act of 1933, as amended. SOW Tracking Number: Predictive_SOW_1999_1000.doc Description: ▇▇▇▇▇▇▇▇.▇▇▇ NOC Revision Number: 003 Creation Date...
External interfaces. Details of the subsystem functions
External interfaces. Provider shall ensure the bus fare collection system has the ability to communicate with compatible external devices for purposes of data exchange and integrated operational functionality. Provider shall design the external communication architecture in conformance with open systems standards and the external communication architecture shall be free of non-standard, proprietary technology. The fare collection system shall support the following interfaces: • J1708/1587 • CAN Bus Expansion • CAN–External 1939 • Ethernet –connected to on-board mobile router for 3G/4G communication with the Garage Data System (GDS) • Wi-Fi 802.11 b/g Provider shall ensure that, utilizing one or more of the interfaces immediately above, the farebox is able to, at a minimum, communicate with J1708/1587-compliant third party devices. Provider shall furnish the farebox with functionality to support: • Single-point logon to enable the vehicle operator to log on to all on-board devices from a single control console. The farebox shall have the ability to accept and process logon information from a J1708-compliant third-party device, and shall be capable of transmitting logon data to such devices. • Geotagging of farebox transaction and event records using location data (either latitude/longitude or bus stop number) transmitted by a third-party J1708-compliant automatic vehicle location (“AVL”) system.
External interfaces. The PATHS system architecture is self-contained in that it does not have any external extension points beyond the capability of the application layer to communicate with the end- user applications in the client layer via web services. The interfaces between the different system architecture layers are: • Communication Between data layer and application layer o JDBC over TCP/IP o ODBC over TCP/IP o SMB over TCP/IP o SPARQL/HTTP over TCP/IP • Between the application layer and the client layer o RESTful XML and JSON Web Services While chapter 5 above is concerned with providing a logical overview of the system, this chapter provides detailed technical specifications of the modules of each of the sub-systems of the PATHS SOA application layer. The sub-systems of the data layer are described in chapter 7 below.
6.1 Data integration sub-system
1. Open DataBase Connectivity (ODBC) for connecting to PostgreSQL from .NET, C and PHP applications.
2. Java DataBase Connectivity (JDBC) for connecting to PostgreSQL from Java applications
3. Simple Protocol And RDF Query Language (SPARQL) over HTTP for issuing queries towards the Virtuoso RDF store from any application.
4. Server Message Block (SMB) protocol for read-write access to file server from any application.
Figure 6.1-1 UML class diagram showing communication interfaces in the PATHS data integration sub-system
6.2 User profile sub-system
6.2.1 User profile sub-system modules
6.2.1.1 User profile module
External interfaces