Physical Interfaces Clause Samples

The 'Physical Interfaces' clause defines the requirements and specifications for the physical points of connection between different systems, devices, or components. It typically outlines the types of connectors, ports, cabling, and physical layout necessary to ensure compatibility and proper integration. For example, it may specify that a device must have a certain type of Ethernet port or that cabling must meet specific standards. This clause ensures that all parties understand and adhere to the necessary physical standards, thereby preventing incompatibility issues and facilitating seamless system integration.
Physical Interfaces. The over the air interface between the DAP and the subscriber device (CPE, MSS, PCMCIA, etc.) is per the 802.16e specification. The air interface covers both the physical and the MAC layers. The DAP provides an RJ-45 port for connectivity to the network allowing for the base stations to connect to a layer 2 backbone enabling faster handoff times.
View SourceView Similar (2)
Physical Interfaces. The DLI (notionally depicted in Figure B1 - 3) can actually consist of multiple physical interfaces. At least one full duplex bi-directional digital data interface shall provide a communication pathway for the following: ▪ Commands to the UAV, payload, data link and VSM ▪ Environmental data to the UAV system elements ▪ Status from the UAV, payload, data link and VSM ▪ Digital payload data from the UAV - depending on data rate requirements and available bandwidth, digital payload data may require a separate physical interface to be included in a specific DLI implementation Voice communication with ATC, if required, is outside the scope of this STANAG. Analogue Sensor Data Data Link Interface A/V & Payload Mode/Control Commands, Environmental Data Antenna and VSM Commands A/V Telemetry and Digital Sensor Data A/V, Data link, Payload, and VSM Status This STANAG envisions an all-digital medium for data; analogue data interfaces are not within the scope of the DLI. The VSM shall provide analogue to digital conversion (“frame grabbing”) services when imagery or other sensor data is transmitted from the air vehicle in analogue format. To avoid unnecessary translation from analogue to digital and back to analogue, the VSM shall provide a dedicated physical interface for displays or for external feeds (through the CCISM). The physical interface between the CUCS and the VSM can differ depending upon where the VSM is physically located. The VSM can either reside on the ground as part of the UCS and/or as a subsystem in the air vehicle. When the VSM interfaces with the CUCS, the physical interface shall support the TCP/IP and UDP/IP protocols (e.g., Ethernet (IEEE 802) – 10Base2, 10BaseT, 100BaseT, 1000BaseT, fibre, etc.). The VSM then interfaces to the data link and will incorporate the standards as documented in STANAG 7085. When the VSM resides in the air vehicle, the interface to the ADT portion of the data link is defined in STANAG 7085. The GDT/VSM shall support a DLI-compliant interface to the CUCS.
View Source
Physical Interfaces. ‌ CI-CGSN-P-001 The CGSN IO shall provide a satellite link between each mooring instance and the shore station. CI-CGSN-P-002 The CGSN IO shall provide high-bandwidth Wi-Fi and serial radio-modem wireless links for ship-to/from-mooring connections. CI-CGSN-P-003 The CGSN IO shall provide the CI with direct access to vendor-supplied sat- ellite and radio links for vehicles and profilers. CI-CGSN-P-004 The mooring satellite or other wireless links shall support standard internet protocols, including TCP/IP. CI-CGSN-P-005 The shore station CyberPoP shall have a TCP/IP connection to the mooring satellite links. CI-CGSN-P-006 The shore station CyberPop shall have a TCP/IP or direct access connection to vendor-supplied vehicles and other platforms. CI-CGSN-P-007 The CI shall be able to request engineering data from the CGSN infrastruc- ture and vendor-supplied platforms/components. CI-CGSN-P-008 The CI shall be able to request power and bandwidth allocations from the mooring controllers. CI-CGSN-P-009 The CI interface to the mooring controller must consist of documented, bi- directional, message-based IP services. CI-CGSN-P-010 The CGSN shall provide sensors with native Ethernet interfaces and the abil- ity to connect directly with the physical infrastructure. CI-CGSN-P-011 The CI shall communicate directly with all Ethernet sensors. CI-CGSN-P-012 The CI shall provide, as part of its CyberPop software distribution, virtual serial port server functionality on an embedded-Linux platform for sensors that have only a standard serial interface (RS232-RS485-RS422-TTL). This software shall convert IP commands to serial data streams to the sensor and convert serial data from the sensor to IP packets.
View Source
Physical Interfaces. The DLI (notionally depicted in Figure B1 - 3) can actually consist of multiple physical interfaces. At least one full duplex bi-directional digital data interface shall provide a communication pathway for the following:‌ CCISM Analogue Sensor Data VSM Figure B1 - 4: High-Level Depiction of DLI Interface Content
View Source
Physical Interfaces. CI-RSN-P-001 The RSN shall provide a scalable link between the shore stations and a National GigaPop located at the Pittock Building in Portland OR. The link will initially be provisioned at 10Gb/s. CI-RSN-P-002 The link shall support standard Internet protocols, including TCP/IP. CI-RSN-P-003 The Portland OR CyberPoP must have a TCP/IP connection to the backhaul transmission system. CI-RSN-P-004 The CI shall be able to request engineering data from any part of the RSN infrastructure through the EMS. CI-RSN-P-005 The RSN EMS must provide for and accept valid CI power allocation re- quests. CI-RSN-P-006 The CI interface to the EMS shall consist of documented, bi-directional, message-based IP services. CI-RSN-P-007 The RSN shall provide sensors with native Ethernet interfaces the ability to plug directly into a junction box port. CI-RSN-P-008 The CI shall communicate directly with all Ethernet sensors. CI-RSN-P-009 The RSN shall provide serial port servers for sensors that have only a ▇▇▇▇- dard serial interface (RS232-RS485-RS422-TTL) that convert IP commands to serial data streams to the sensor and convert serial data from the sensor to IP packets. CI-RSN-P-010 The CI shall communicate directly with all serial port servers. CI-RSN-P-011 The CI shall be able to directly change instrument characteristics (e.g., baud rate or toggling of control lines) at the serial port servers. CI-RSN-P-012 Serial streams shall be time-stamped as close to the sensor as possible.
View Source
Physical Interfaces. The DLI (notionally depicted in Figure B1-4) can actually consist of multiple physical interfaces. At least one full duplex bi-directional digital data interface shall provide a communication pathway for the following: ▪ Commands to the UAV, payload, data link and VSM ▪ Environmental data to the UAV system elements ▪ Status from the UAV, payload, data link and VSM ▪ Digital payload data from the UAV - depending on data rate requirements and available bandwidth, digital payload data may require a separate physical interface to be included in a specific DLI implementation Voice communication with ATC, if required, is outside the scope of this STANAG.
View Source

Related to Physical Interfaces

  • Technical Interfaces 3.2.6.1 The Interconnection facilities provided by each Party shall be formatted using either Alternate Mark Inversion (AMI) line code with Superframe format framing or Bipolar 8-Zero Substitution with Extended Superframe (B8ZS ESF) format framing or any mutually agreeable line coding and framing.

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

  • Firmware 7.1 The Supplier must deliver the equipment, Goods or hardware equipped with all the firmware required to use all the Goods or hardware’s functions. Any software embedded in the equipment, Goods or hardware, including the firmware, is provided to the Local Government with a license to use this software, with all license costs and royalties being included in the Fee Schedule (Schedule C). All firmware will be the most recent version available at the time of shipping.

  • Antivirus software All workstations, laptops and other systems that process and/or store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must have installed and actively use comprehensive anti-virus software solution with automatic updates scheduled at least daily.

  • Source Code 5.1 Nothing in this ▇▇▇▇ shall give to the User or any other person any right to access or use the Source Code or constitute any licence of the Source Code.