ip.access Ltd Building 2020 Cambourne Business Park Cambourne Cambridgeshire CB23 6DW United Kingdom The world's most deployed picocell nanoBTS Product Description NGSM_GST_300 1.0m0.
REVISION HISTORY Version Change Summary Date Author 0.1 First draft 13 Jun 2008 AM4 0.2 Added details of 165 Series C/D, added the Safety and Regulatory chapter, and removed the Profile chapters. 20 Oct 2008 MB3 0.3 Updated with comments from review 13 Oct 2008 MB3 1.0 Released 21 Nov 2008 ZN1 1.0m0.1 Added 165E/F/G/H information – CP DRAFT 30 Apr 2009 ZN1 DOCUMENT APPROVAL Approved by e-mail.
TABLE OF CONTENTS 1 INTRODUCTION ....................................................................................................... 1 1.1 Overview ............................................................................................................ 1 1.2 Related Information............................................................................................ 1 1.3 Terminology .......................................................................................................
5.4.2 Software Code Banks and Software Bank Activation................................ 18 5.4.3 Reset Reason........................................................................................... 19 5.5 Configuration.................................................................................................... 19 5.5.1 DHCP ....................................................................................................... 19 5.5.2 Fallback OML Link......................................
6 SOFTWARE IMPLEMENTATION (INFORMATIVE)................................................. 38 6.1 139/140 Platform.............................................................................................. 38 6.2 Functional Partitioning...................................................................................... 39 6.3 Interprocessor Communications....................................................................... 40 6.4 Process Scheduling ..............................................
1 INTRODUCTION 1.1 Overview This product description gives the technical specification of the 165 and 139/140 series nanoBTSs from ip.access. It describes the basic properties and functionality of the hardware and software. It includes information on the management model supported by the BTS. It does not go into detail on GSM service support beyond the most basic. This is described in the range of Feature Description documents also available from ip.access. 1.2 Related Information [GSM05.
CRC DAC Cyclic Redundancy Check Digital to Analog Converter DHCP Dynamic Host Configuration Protocol DLP Downlink Processor (baseband processor responsible for transmit processing) Dongle Hardware plug used to reset the BTS to factory default settings EEPROM Electrically Erasable Programmable Read Only Memory EFR Enhanced Full Rate (GSM Speech coding) ESD Electro-static Discharge FCC Federal Communications Commission FEC Fast Ethernet Controller, or Forward Error Correction FER FPGA Failu
RACH RSL Random Access Channel Radio Signalling Link SABM SACCH Set Asynchronous Block Mode (a message indicating the establishment of the radio data link) Slow Associated Control Channel SCH Synchronisation Channel SDP SI Software Download Package (proprietary format for software download to the BTS) System Information SMS-CB SMS-PP Short-message service – cell-broadcast Short-message service – point-to-point SNMP Simple Network Management Protocol SoLSA Support of Local Service Area TA Type
2 SERIES MEMBERS The 165 series consists of the following products for the GSM bands shown in brackets: • 165A (DCS 1800) • 165B (PCS 1900) • 165C (EGSM 900) • 165D (GSM 850) • 165E (DCS 1800) • 165F (PCS 1900) • 165G (DCS 1800) • 165H (PCS 1900) The 139/40 series consists of the following products for the GSM bands shown in brackets: • 139_ (DCS 1800) • 140_ (PCS 1900) • 177_ (GSM 850) • 178_ (EGSM 900) The band designator is as used in [GSM05.05]. nanoBTS Product Description © ip.
3 HARDWARE SPECIFICATION 3.1 External 3.1.1 Appearance (Informative) The 165 series nanoBTS are shown in Figure 1 and Figure 2. Figure 1 - 165A/B (EDGE) nanoBTS (left) and 165C/D/G/H (right) TIB out TIB in 48v DC Power Option Powered Ethernet Chassis Bond USB Port (Not used) Figure 2 - 165 nanoBTS connectors nanoBTS Product Description © ip.
The 139/140 series nanoBTS is shown in Figure 3 and Figure 4. Figure 3 - 139/140 nanoBTS Status Indicator TIB In TIB Out (26MHz) RJ45(48Vdc) Ethernet Figure 4 - 139/140 nanoBTS connectors 3.1.2 Size, Shape and Weight The 165A/B series nanoBTS fits in an envelope approximately 276mm long, 208mm wide and 63mm deep. The plan shape is roughly rectangular. The 165C/D/G/H series nanoBTS fits in an envelope approximately 291mm long, 222mm wide and 63mm deep. The plan shape is roughly rectangular.
Fins are also provided on the front of the unit, normally obscured by the plastic cosmetic cover. When ceiling mounted or in any other horizontal situation, the plastic cosmetic cover is intended to be removed to allow airflow across the front fins. 3.1.3 GSM Standards Standards Parts Date 3GPP 11.21 Essential Compliance v8.8.0 3GPP 05.05 EGSM, Power Class P1, as called up by 3GPP 11.21/Essential Compliance v8.14.0 ETS 301 489 Part 8 – specific requirements for GSM basestations v1.1.
3.1.6 DC Power Power is expected by the unit on the Ethernet connector, according to IEEE802.3af option B or A. Option A is implemented with Or-ing diodes from the unused wires, and results in reduced supply margin and efficiency. Option B is preferred, therefore. See section 3.2.1 for more information. The 139/140 series is designed to meet IEEE802.3af. Interoperability with 3rd party 802.3af supply equipment is not warranted.
TIB out 1 TIB SPARE 1 (to FPGA via link on PCB) 2 TIB SPARE 2 (to FPGA via link on PCB) 3 26MHz OUT - 4 26MHz OUT + 5 GSM SYNC OUT + 6 GSM SYNC OUT - 7 PPC Serial interface OUT (via link on PCB) 8 PPC Serial interface IN (via link on PCB) 9 FPGA SERIAL OUT (via link on PCB) 10 Ground TIB in 1 10MHz IN- 2 10MHz IN+ 3 26MHz IN- 4 26MHz IN+ 5 GSM SYNC IN+ 6 GSM SYNC IN- 7 TRX FRAME SYNC (via PCB link) 8 Not connected 9 Security 10 Ground nanoBTS Product Description © ip.
3.1.8 Antennas 165 nanoBTS units provide SMA connectors that are exposed when the antennas are unscrewed as illustrated in Figure 5. (The removable antennas for 165C, 165D, 165G and 165H are shown in Figure 5. The removable antennas for 165A and 165B are smaller. 165E and 165F have no removable antennas.) Figure 5 - Removable antennas – 165 hardware The 139/140 series is normally used with its own internal antennas, of which there is one for transmit and one for receive.
Antenna Cover Top Notch to aid removal of cover Compression Spring Clamp plate Antenna Cover Body Antenna Cover Bottom Figure 6 - External antenna kit 3.1.8.1 165 Antennas Internal receive aerial 0 dBi nominal screw-on SMA omni-directional Internal transmit aerial 0 dBi nominal screw-on SMA omni-directional Internal NWL aerial 0 dBi nominal screw-on SMA omni-directional Isolation (Tx to Rx) 30dB 3.1.8.
3.1.9 LED Indicator Two LEDS are provided on the PCB. These can provide three colours (red, green, orange) in various flash codes, as specified in section 5.8.2. 3.1.10 Labelling TA/CE certification Product 139 Product 165A Product 165E Product 165G CE mark with associated devices. (FCC not appropriate for 1800MHz devices) Product 140 Product 165B Product 165F Product 165H FCC mark with associated devices. UL mark with associated devices.
3.2 Internal 3.2.1 Power Supply Input Voltage 36-57VDC (to cover power-over-ethernet range) Input Current max. 500mA from an input voltage of 37V. Input capacitor <180uf when operating (less during signature detect – see below) Efficiency min. 80% Signature Power input signature to comply with 802.3af rel 3 V_I slope (at 2.7 to 10.1V) 23.75K to26.25K ohms V offset <1.9V I offset <10uA Input capacitance 50 to 110nf Input inductance >100uH IEEE802.
3.2.4 TRX Baseband Sub-System Processors Msp430 (3-off: ULM, ULS DLP) 139/140/178: ARM 139/140/178: DSP Memory 3.2.
3.2.6 Receiver - uplink Frequency range 139_ (DCS 1800) 1710-1785MHz 140_ (PCS 1900) 1850-1910MHz 177_ (GSM 850) 824-849MHz 178_ (EGSM 900) 880-915MHz 165A (DCS 1800) 1710-1785MHz 165B (PCS 1900) 1850-1910MHz 165C (EGSM 900) 880-915MHz 165D (GSM 850) 824-849MHz 165E (DCS 1800) 1710-1785MHz 165F (PCS 1900) 1850-1910MHz 165G (DCS 1800) 1710-1785MHz 165H (PCS 1900) 1850-1910MHz Channel spacing 200 kHz Performance Essential conformance to GSM 11.21 and GSM05.
4 MTBF The 139/14- series has an MTBF greater than 120,000 hours. The 165 series has an MTBF of approximately 100,000 hours. nanoBTS Product Description © ip.
5 SOFTWARE SPECIFICATION 5.1 Top Level Feature Overview The nanoBTS: • supports DHCP for IP configuration • supports 12.21 mechanism for software upgrades • supports a single boot code storage bank • supports two application code storage banks • only supports a single "base-band transceiver" GSM 12.21 managed object instance • supports configuration of the BTS via GSM 12.21 messages • supports the ip.
5.2 Explicitly Not Supported • Multi-Slot Circuit Switched Data • EDGE on 139 series BTS (supported by 165 with SR3 software) • Half-rate speech codec (HR) • Advanced Multi-Rate speech codec (AMR) on 139/140 series BTS (supported by 165 with SR3 software) • IP Security • IP Version 6 • HTTP server • VGCS and VBS • SOLSA 5.3 Standards The base software support level is 3GPP Release 99 unless otherwise stated. 5.4 5.4.
5.4.3 Reset Reason If the BTS undergoes a fatal software reset of any sort, a byte indicating the "reset reason" is stored in memory before the reset is initiated. During the reset procedure, this "reset reason" byte is read out, and sent to the management system as a Failure Event Report. 5.5 5.5.1 Configuration DHCP The BTS supports the ip.access specific implementation of DHCP. 5.5.
bss_001 0..200 btsSiteManager_004 0..1 1..1 btsNse_002 1..1 gprsCellEgprs_004 btsEdge1800_005 1..2 btsNsvc_001 1..4 basebandTransceiver_004 8..8 channelAmr_002 Figure 7 - 1800MHz, EDGE/AMR nanoBTS management model 5.5.4 Code Download The BTS supports code download by using the software download function of the BtsInstaller tool (see [INST_300]). The BTS examines the header of the downloaded file to determine if the BTS hardware is compatible with the SW.
5.6 Air Interface 5.6.
The BTS supports the "Directed Retry" procedure on a particular MS to produce a list of candidate NCELLs that it can be handed over to. 5.6.3 Cell Broadcast The BTS supports the "SMS-CB Default" message The BTS supports the "SMS-CB Normal" message The BTS does not support the "SMS-CB Scheduled" message The BTS does not support the CBCH Flow control. The BTS sends an 08.58 ErrorInd upon receipt and throws a warning level FER (see section 5.7). 5.6.
5.8 System Monitoring The BTS monitors the Radio Synthesiser OPLL to ensure that it is transmitting on frequency. This will be done once per GSM frame. If an error is detected then the BTS will autonomously attempt to relock the OPLL. If the synthesiser does re-lock then a warning level FER shall be sent and immediately ceased. If the synthesiser fails to lock then a critical level FER on the radio carrier object is sent. The BTS monitors the transmitter Power Amplifier OOL signal once per GSM Frame.
The BTS supports setting of the SNMP "SysContact" EEPROM parameter via 12.21 extensions only. The BTS supports setting of the SNMP "trap address" EEPROM parameter via 12.21 extensions only. The SNMP "SysLocation" shall be derived from 12.21 "location" string stored in EEPROM. Similarly the SNMP "SysName" shall be derived from the 12.21 "name" string stored in EEPROM. The BTS supports the "ipaccess.
LED_DOWNLOADING_CODE Orange Fast Flash Code download procedure is in progress. 4 LED_ESTABLISHING_OML Orange Slow Blink OML not yet established (via primary or secondary OML port) but is needed in order for the BTS to become operational. 5 LED_FACTORY_RESET Red Fast Blink Dongle detected at start up and the factory defaults have been applied.
LED_DOWNLOADING_CODE Off Code download procedure is in progress. 4 LED_ESTABLISHING_OML Off From power on until OML established. 5 LED_FACTORY_RESET Red Fast Blink Dongle detected at start up and the factory defaults have been applied. 6 LED_SELF_TEST Off From power on until end of backhaul power on self-test. 7 LED_NWL_TEST Off OML established, NWL test in progress. 8 LED_LOCKED Off OML established, but an MO is locked that will prevent C0 being transmitted.
5.9 5.9.1 Traffic Channel Types The BTS supports the transport of • Full Rate (FR) • Enhanced Full Rate (EFR) GSM speech. • AMR full- and half-rate speech (requires 165 BTS with SR3 software) • BS20 (14.4k) single slot circuit switched data. • BS21-26 (up to 9600) single slot circuit switched data • BS61 and BS81 speech-then-data and alternate-speech-and-data. The BTS does not perform any transcoding, but it does perform rate adaption for circuit switched calls to deliver all CSD bearers in V.
5.11 Peripherals 5.11.1 Backhaul 5.11.1.1 Miscellaneous The BTS contains a Fast Ethernet Controller IC (FEC) with 10/100 mbps auto-negotiation (auto-negotiation occurs without needing to reboot). 5.11.1.2 EEPROM Storage The EEPROM structure is protected against bit error using a CRC check mechanism. 5.12 5.12.1 NV Configuration Parameters The NV management state model for each parameter is as shown in Figure 8. All attributes are initially in the "illegal" state.
All other attributes are type 2. Those marked "Retained? == Y" are not reset to factory defaults by insertion of the dongle. If the EEPROM is deemed to be corrupt then the BTS attempts to send a FER as soon as it connects (or is connected to) an OMC (see section 5.7). It shall also set the base-band transceiver managed objects to "Disabled, Failed". The LED state should also be set to "LED_FACTORY_RESET". Note: Not all NV parameters are available for use by end-customers.
Secondary OML Link 0.0.0.
Input Supply Power Thresh Min Percent 0 N N BTS Location "" N N BTS Name "" N N Site Id 0xFFFF N N BTS Id 0xFF N N TRX Id 0xFF N N In Service Time 0 N Y Primary OML fallback address 0.0.0.0 N N Primary OML fallback port 0 N N SNMP community string "public" N N SNMP Trap Address 0.0.0.0 N N SNMP Trap Port 0 N N SNMP Manager Address 0.0.0.0 N N SNMP System Contact "Not Known" N N Note: "OEM Id" is defaulted with its null value 0xFF.
5.12.2 TRX Controlled Parameters Attribute Default Value Notes TRX database schema TX Power ramps 13 levels, 32 x UInt16 TX Scale factors 13 levels, UInt16 for each level TX Frequency compensation 12 ARFCN’s, UInt16 for each ARFCN TX DC Offsets 0x0, 0x0 2 x SInt16 RXGainControlNormal (i.e. uplink receiver) 26 AGC steps, UInt16 for each step RXGainControNWL (i.e. downlink receiver) 26 AGC steps, UInt16 for each step RxAccurateGainNormal (i.e.
• the "Beacon mode" test to enable other basestations to monitor it. This test is configurable to set the BSIC, ARFCN and transmit power to be used. The test continues until a "Stop Test" request is made. The transmitted BCCH information marks the cell as "barred" for all access types. NWL tests will take the BTS out of service for the duration of the test. The BTS will restart service after the test is complete. A state change event report is generated at the beginning and end of the test. 5.13.
Note that the value of the SW Configuration attribute in a SW Activate Request message sent by an object is therefore not the same as that of the SW Configuration attribute obtained by sending a Get Attributes message to the object. i.e. the SW Configuration Attribute reported as a response to the "GetAttributes" message includes the "Boot application"; the "Boot application" is not included in "SW Activate Request" messages.
The BTS’s Baseband Transceiver object sends a SW Activate Request containing a SW Description for the backhaul software image that was activated on the Site Manager object, plus a SW Description for each TRX software image that is present. The BTS expects the BSC to send a SW Activate message, which may contain no, one, or two, SW Descriptions. If there is no SW Description, the nanoBTS will activate the "default" TRX device software.
The BTS does not immediately use the new Primary OML or Secondary OML Configuration if a connection has already been established. It shall use the configuration for all new connections. The BTS does not immediately action receipt of configuration of new IP Configuration (either from the "IP Interface Config" or "IP Gateway Config"). A reboot is always required. The BTS immediately actions receipt of configuration of new BTS Location.
Keep trying to connect, send an alarm to the operations and maintenance, resume normal operations as soon as link is restored. 5.15 GPRS Feature Support The BTS supports • Gb over IP, with NS frames being transported over UDP/IP. • Mobiles up to multislot class 10. • All coding schemes, CS1 through CS4, with link adaptation. MCS1 through MCS9 is also supported on the 165 BTS with SR3.0 or later software • Air interface timeslots may be configured statically for GPRS or dynamically for GPRS.
6 SOFTWARE IMPLEMENTATION (INFORMATIVE) 6.1 139/140 Platform The hardware platform for the BTS is shown in Error! Reference source not found..
The MPC855T device runs the Nucleus operating system which includes TCP, UDP, IP, ICMP, SNMP, and all MPC855T device drivers (as part of the Board Support Package). Other application code is developed internally by ip.access, written in ANSI C. The FPGA is responsible for managing interprocessor communications buffers. An HDLC controller is implemented within it, which communicates directly to a similar sub-system in the MPC855T.
6.3 Interprocessor Communications Secure communications within the nanoBTS are implemented as follows BH to TRX HDLC framing including checksum generation and checking performed in MPC855T and FPGA Intra-TRX (GSM L2) Messages carried and routed through the FPGA ARM7 to DSP Dual-port memory interface ARM7 to Synthesiser programming registers DMA 6.
Block based tasks execute every four frames, again, at the conclusion of each timeslot and include • L2 block transfer from DLP • Channel coding and interleaving • Viterbi decoding of soft-decision results from equaliser • L2 block transfer to ULM/ULS Block based tasks run at lower priority than frame based tasks, and are usually interrupted by them. 6.
7 DHCP START If EEPROM is corrupt the BTS will assume a default MAC Address within the manufacturer range. N Set Default MAC Address MAC Address in valid range ? Y Validate stored Config None/not fixed Validate MAC Address in EEPROM against ip.access assigned Manufacturer's range.
SELECTING N Ts Expiry DHCPOFFER retransmissions finished ? Is !("Static VSI Config") & VSI was not received ? N DHCPDISCOVER Y Reset Ts Y Set Ts N Any saved offers ? SELECTING Y Save offer Select offer START SELECTING DHCPREQUEST Set Tr REQUESTING Figure 11 - SELECTING state nanoBTS Product Description © ip.
REQUESTING DHCP-NACK DHCP-ACK Tr Expiry Reset Tr Perform Check of IP Address (e.g. ARP) N IP Address Acceptable ? retransmissions finished ? N DHCPREQUEST Y Y DHCPDECLINE Set & save "i/f IP Config" START Set Tr Set & save "IP Gateway Config" START Save VSI if present AND static VSI config flag NOT set REQUESTING Use the VERY long lease time (126 years!) to change to static config Set T1 & T2 & Lease Timer 1 Figure 12 - REQUESTING state nanoBTS Product Description © ip.
1 Y Static VSI config? N Y DHCP VSI supplied ? N BOUND DHCPINFORM For VSI only Set Ti AWAITING DHCP VSI Figure 13 - Connector '1' nanoBTS Product Description © ip.
BOUND unicast to leasing server (includes request for VSI options) T1 Expiry Lease Expiry Set Tr ((Remaining time to T2)/2) Remove i/f IP Address DHCPREQUEST START RENEWING NOTES 1) T1, T2 & Lease Timer are not running if using a fixed IP Address Design assumes that T1 expiry time < T2 expiry timer < Lease expiry time 2) If the VSI is known, it should be used to attempt to contact the BSC (even if it is known from a previous config).
RENEWING DHCP-ACK Tr Expiry T2 Expiry DHCPREQUEST DHCPREQUEST Lease Expired DHCP-NACK 5 Unicast Set T1 & T2 & Lease Timer Any Config Changed? Broadcast Set Tr ((Remaining time toT2)/2) Set Tr ((Remaining time to Lease expiry)/2) RENEWING REBINDING START Y Update saved IP Address and IP Config + any VSI updates N Remove i/f IP Address DHCP spec says "inform the user" - attempt to send Warning FER if connected to an OML system.
REBINDING Tr Expiry N Set Tr ((Remaining time to Lease expiry)/2) DHCP-ACK Is !("Static VSI Config") & VSI was not received ? retransmissions finished ? N N Any saved offers ? Y Y Save offer DHCPREQUEST Lease Expired DHCP-NACK Reset Tr Any saved offers ? Y 5 Broadcast REBINDING Y Remove i/f IP Address Select offer START 5 N Wait for Lease expiry Select offer 5 REBINDING Figure 16 - REBINDING state nanoBTS Product Description © ip.
AWAITING GATEWAY CONFIG Ti Expiry DHCP-ACK Reset Ti retransmissions finished ? Y Set & save "IP Gateway Config" N Set & Save missing "IP Gateway Config" to defaults 1 DHCPINFORM Save VSI if present AND "Static VSI Config" flag NOT set Set Ti 1 AWAITING GATEWAY CONFIG Figure 17 - AWAITING GATEWAY CONFIG state nanoBTS Product Description © ip.
AWAITING DHCP VSI Y Ti Expiry DHCP-ACK retransmissions finished ? Reset Ti N N Includes VSI ? DHCPINFORM BOUND Set Ti Save VSI AWAITING DHCP VSI BOUND Set Ti AWAITING DHCP VSI Figure 18 - AWAITING DHCP VSI state nanoBTS Product Description © ip.
8 CUSTOMER SAFETY AND REGULATORY INFORMATION 8.1 Introduction 8.1.1 Purpose and Scope This section provides the customer with safety and regulatory warnings, cautions and information. Products covered are the model 108, 110, 139, 140, 165 and 178 range of nanoBTSs, model 109 and 126 power supplies. 8.1.2 Terminology UL Underwriters Laboratories FCC Federal Communications Commission IC Industry Canada CE European Union 8.2 8.2.
PSU109 – Environmental Specification • −10 °C to +45 °C ambient operating temperature. • This product has been listed by UL for use in a 25 °C ambient. • −20 to +80 °C ambient storage temperature. • 5 to 95% RH non-condensing humidity. 8.2.2 109 - Handbook - FCC Text WARNING This is a class B product. In a domestic environment this product may cause radio interference, in which case the user may be required to take adequate measures.
The PSU109 is supplied by Poly-Products Industries, model number ILA1711112. A copy of regulatory compliance documentation may be obtained in writing from: "IP access Ltd, Building 2020, Cambourne Business Park, Cambourne, Cambridge, CB23 6DW, UK". 8.3 8.3.1 Model 126 Ethernet Switch and Power Inserter 126 - Handbook - Warnings and Cautions This document is written in English. Please request a copy in your local language if required. This product is only intended to power products approved by IP Access.
126 - Input Power Source Specification • Unit may be powered via AC or DC (not both). • 90 to 132 and 180 to 264VAC (auto-ranging) via an IEC C13 connector. 135W, 2A rating. • 47 to 57V DC via screw terminals on the front panel. 115W 3A rating. The installer must ensure that this supply connection is fused externally at 5A and provision is made for an external disconnection device.
8.3.4 126 - Handbook - Regulatory Compliance Statement The nanoBTS conforms to the following regulatory standards. EMC Standards • EN 55022 and EN55024 (CE marked) • FCC Part 15 class A • ICES-003 Safety Standards • EN60950 (CE marked) • IEC 60950 • UL60950 Listed (File number E230296) (USA and Canada) • CB certificate (DK-7033) "Hereby, ip.
The nanoBTS is intended for dry indoor applications only. If evidence of condensation is present do not apply power to the nanoBTS. The nanoBTS must only be powered using an ip.access model 109 PSU (PPI part number ILA1711112) or ip.access model 126 Ethernet switch and power inserter (unless prior written approval is obtained from IP Access). Model 165 BTS’s may also be powered by a direct 48V connection using a PSU specified in writing by IP Access Ltd. PSUs supplied by ip.
nanoBTS nanoBTS PSU φ ~ RJ45(48v) RJ45 PSU θ ~ Ethernet Switch BSC θ PSU located at the switch φ PSU located at nanoBTS When using the ip.access model 126A Ethernet Switch and Power Inserter, external PSU’s are not required, the nanoBTS is connected locally or via site cabling to the powered ports of the 126. nanoBTS (max qty 7) RJ45(48v) ~ RJ45(48V) Ethernet 126A Ethernet Switch and 48V Power Inserter 8.4.3.
Cable to nanoBTS 110-230Vac ~ ! 48Vdc 48Vdc Connection to nanoBTS PSU RJ45 Connection to LAN Ethernet Switch 8.4.3.2 nanoBTS - Handbook - Installing the PSU at the nanoBTS Ensure that the 109 PSU is placed in a location that is ventilated and that the connection leads provide no safety hazard. 110-230Vac ! Connection to nanoBTS 48Vdc 48Vdc ~ PSU Connection to LAN 8.4.
Model 165B nanoBTS has FCC ID QGGKU02ZZP Model 165D nanoBTS has FCC ID QGGKU02ZZR Model 165F nanoBTS has FCC ID QGGKU02ZZP Model 165H nanoBTS has FCC ID QGGKU02ZZS Federal Communications Commission Note: This equipment has been tested and found to comply with the limits for a class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
Environmental Standards • ETS 300 019. Safety Standards • EN60950 (CE Marking) • IEC 60950 • UL60950 Listed (file number E230296, USA and Canada) • CB Certificate "Hereby, ip.access declares that this NanoBTS is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC." A copy of regulatory compliance documentation may be obtained in writing from: "IP access Ltd, Building 2020, Cambourne Business Park, Cambourne, Cambridge, CB23 6DW, UK".
