Physical Interfaces Sample Clauses

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.
Sample 1Sample 2
AutoNDA by SimpleDocs
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 VSM UCS Core Processing Suite 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 CCISM Figure B1 - 4: High-Level Depiction of DLI Interface Content 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.
Sample 1
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.
Sample 1
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 xxxx- 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.
Sample 1

Related to Physical Interfaces

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Source Code 5.1 Nothing in this XXXX 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.

  • Proprietary Software Depending upon the products and services You elect to access through Electronic Access, You may be provided software owned by BNY Mellon or licensed to BNY Mellon by a BNY Mellon Supplier (“Proprietary Software”). You are granted a limited, non-exclusive, non-transferable license to install the Proprietary Software on Your authorized computer system (including mobile devices registered with BNY Mellon) and to use the Proprietary Software solely for Your own internal purposes in connection with Electronic Access and solely for the purposes for which it is provided to You. You and Your Users may make copies of the Proprietary Software for backup purposes only, provided all copyright and other proprietary information included in the original copy of the Proprietary Software are reproduced in or on such backup copies. You shall not reverse engineer, disassemble, decompile or attempt to determine the source code for, any Proprietary Software. Any attempt to circumvent or penetrate security of Electronic Access is strictly prohibited.

  • Software Title and ownership to Existing Software Product(s) delivered by Contractor under the Contract that is normally commercially distributed on a license basis by the Contractor or other independent software vendor proprietary owner (“Existing Licensed Product”), embedded in the Custom Products, shall remain with Contractor or the proprietary owner of other independent software vendor(s) (ISV). Effective upon acceptance, such Product shall be licensed to Authorized User in accordance with the Contractor or ISV owner’s standard license agreement, provided, however, that such standard license, must, at a minimum: (a) grant Authorized User a non-exclusive, perpetual license to use, execute, reproduce, display, perform, adapt (unless Contractor advises Authorized User as part of Contractor’s proposal that adaptation will violate existing agreements or statutes and Contractor demonstrates such to the Authorized User’s satisfaction) and distribute Existing Licensed Product to the Authorized User up to the license capacity stated in the Purchase Order or work order with all license rights necessary to fully effect the general business purpose(s) stated in the Bid or Authorized User’s Purchase Order or work order, including the financing assignment rights set forth in paragraph (c) below; and (b) recognize the State of New York as the licensee where the Authorized User is a state agency, department, board, commission, office or institution. Where these rights are not otherwise covered by the ISV’s owner’s standard license agreement, the Contractor shall be responsible for obtaining these rights at its sole cost and expense. The Authorized User shall reproduce all copyright notices and any other legend of ownership on any copies authorized under this clause. Open source software is developed independently of Contractor and may be governed by a separate license (“open source software”). If the open source software is governed by a separate License and provided under this Contract, Contractor shall provide a copy of that license in the applicable Documentation and the Authorized User's license rights and obligations with respect to that open source software shall be defined by those separate license terms and subject to the conditions, if any, therein. Nothing in this Contract shall restrict, limit, or otherwise affect any rights or obligations the Authorized User may have, or conditions to which the Authorized User may be subject, under such separate open source license terms.

  • Company Software “Company Software” shall mean any software (including software development tools and software embedded in hardware devices, and all updates, upgrades, releases, enhancements and bug fixes) owned, developed (or currently being developed), used, marketed, distributed, licensed or sold by an Acquired Corporation at any time (other than non-customized third-party software that is not incorporated into any Company Product and is licensed to an Acquired Corporation solely in object code form and solely for internal use on a non-exclusive basis).

  • Computer Software The Grantee certifies that it has appropriate systems and controls in place to ensure that state funds will not be used in the performance of this Grant Agreement for the acquisition, operation, or maintenance of computer software in violation of copyright laws.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Derivative Works Constellation Beers shall acquire no ownership rights in the Licensed Intellectual Property or derivative works based thereon or any intellectual property deemed to be owned by Marcas Modelo or Modelo Group as a result of this Agreement. Constellation Beers shall, at any time requested by Marcas Modelo or Modelo Group, whether during or subsequent to the term hereof, disclaim in writing any such property interest or ownership in the Licensed Intellectual Property.

  • Third Party Software 1. The Software may contain third party software that requires and/or additional terms and conditions. Such required third party software notices and/or additional terms and conditions are located at xxxx://xxx.xxxxxxxxx.xxx/thirdparty/index.html and are made a part of and incorporated by reference into this XXXX. By accepting this XXXX, You are also accepting the additional terms and conditions, if any, set forth therein.

Time is Money Join Law Insider Premium to draft better contracts faster.