RF-FE Clause Samples

RF-FE. For the design of the RF-FE [14] the following requirements are taken into account:  Operational bandwidth. Based on the availability of commercial components as well as licence for 5G mmW system testing in EU and Korea, the operational bandwidth of the RF-FE is set in the 26.5 -29.3 GHz band.  Time-division-duplex (TDD) communication: This is a system requirement determined by the fact that mmW communication protocol and frame structure.  Power consumption: Low power consumption is an important criterion in the design of the RF-FE. Key issue it to minimize power consumption with respect to long range and with poor availability of power amplifiers.  Beamforming: this is necessary requirement beamsteering/adaptation. It impacts on performance, capability/limitations, costs and consumption.  RF beamformer logic: this is necessary requirement to allow beamforming. It also considers timing interface with the DFE.  Automatic Gain Control: this is necessary at the receiver side to allow extended dynamic range, thus solving near-far effects in case of mobility. Based on the above requirements, the following specifications are determined. One RF-FE is needed for each antenna unit. For instance, in Figure 13, it is illustrated the architecture of the RF-FE unit including two RF beamformers based on digitally controlled phase-shifters. It can be noticed that frequency up/down conversion is used to achieve and tune the desired carrier frequency in the 26.5 -29.3 GHz band. Also, switched are used to separate TX and RX paths, thus, enabling TDD. Finally, to minimize energy consumptions, implementation cost and form-factor, several components are shared between the TX and RX paths.
View Source

Related to RF-FE

  • DNSSEC Registry Operator shall sign its TLD zone files implementing Domain Name System Security Extensions (“DNSSEC”). During the Term, Registry Operator shall comply with RFCs 4033, 4034, 4035, 4509 and their successors, and follow the best practices described in RFC 4641 and its successors. If Registry Operator implements Hashed Authenticated Denial of Existence for DNS Security Extensions, it shall comply with RFC 5155 and its successors. Registry Operator shall accept public-­‐key material from child domain names in a secure manner according to industry best practices. Registry shall also publish in its website the DNSSEC Practice Statements (DPS) describing critical security controls and procedures for key material storage, access and usage for its own keys and secure acceptance of registrants’ public-­‐key material. Registry Operator shall publish its DPS following the format described in ▇▇▇ ▇▇▇▇.

  • Use of FIIOC’s and FSC's Name The Trust shall not use the name of FIIOC and FSC in any Prospectus, sales literature or other material relating to the Trust or any Fund of the Trust in a manner not consented to by FIIOC and FSC prior to use; provided, however, that FIIOC and FSC shall approve all uses of its name which merely refer in accurate terms to its appointments, duties or fees hereunder or which are required by the Securities and Exchange Commission ("SEC" or “Commission”) or a state securities commission; and further, provided that in no event shall such approval be unreasonably withheld.

  • Name of Felon(s) The named person's role in the firm, and

  • Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:

  • Unbundled Sub-Loop Feeder 2.8.4.1 Unbundled Sub-Loop Feeder (USLF) provides connectivity between BellSouth's central office and cross-box (or other access point) that serves an end user location. 2.8.4.2 USLF utilized for voice traffic can be configured as 2-wire voice (USLF-2W/V) or 4-wire voice (USLF-4W/V). 2.8.4.3 USLF utilized for digital traffic can be configured as 2-wire ISDN (USLF-2W/I); 2-wire Copper (USLF-2W/C); 4-wire Copper (USLF-4W/C); 4-wire DS0 level loop (USLF-4W/D0); or 4-wire DS1 and ISDN (USLF-4W/DI). 2.8.4.4 USLF will provide access to both the equipment and the features in the BellSouth central office and BellSouth cross box necessary to provide a 2W or 4W communications pathway from the BellSouth central office to the BellSouth cross- box. This element will allow for the connection of Global Connection’s loop distribution elements onto BellSouth's feeder system.