all | frequencies |
|
|
|
exhibits | applications |
---|---|---|---|---|---|---|
manuals |
app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 2 3 |
|
User manual | Users Manual | 134.83 KiB | ||||
1 2 3 |
|
User manual 3101 | Users Manual | 192.39 KiB | April 03 2004 | |||
1 2 3 |
|
User manual 3104 | Users Manual | 134.80 KiB | September 03 2004 | |||
1 2 3 | Cover Letter(s) | September 03 2004 | ||||||
1 2 3 | Test Report | September 03 2004 | ||||||
1 2 3 | Cover Letter(s) | April 03 2004 | ||||||
1 2 3 | Test Report | / April 03 2004 | ||||||
1 2 3 | Operational Description | |||||||
1 2 3 | Parts List/Tune Up Info | |||||||
1 2 3 | Cover Letter(s) | |||||||
1 2 3 | ID Label/Location Info | |||||||
1 2 3 | Internal Photos | |||||||
1 2 3 |
|
Photos external | External Photos | 376.09 KiB | ||||
1 2 3 | Block Diagram | |||||||
1 2 3 | Cover Letter(s) | |||||||
1 2 3 | Test Report |
1 2 3 | User manual | Users Manual | 134.83 KiB |
E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 1 ( 25 ) Node Description Contents Page Introduction ....................................................................... Purpose ............................................................................ Scope .............................................................................. Radio Network Overview ....................................................... RBS Overview ................................................................... Main Functions .................................................................... Hardware ........................................................................... Software ............................................................................ RBS Characteristics and Configurations ....................................... 2 2 2 2 4 4 5 5 5 6 Hardware Structure .............................................................. 7 Connection Field .................................................................. 8 CU .................................................................................. 8 BB Subrack ........................................................................ RF Subrack ........................................................................ 9 MCPA Subrack .................................................................... 11 Transmission Interfaces .......................................................... 11 Internal Cables .................................................................... 11 Node Architecture ............................................................... 13 Structure ........................................................................... 14 Common Platform ................................................................. 16 Functions ......................................................................... 17 Application Functions ............................................................. 17 External Interfaces .............................................................. 20 lub Interface ....................................................................... 21 Uu Interface ........................................................................ 21 Mub Interface ...................................................................... 22
................................................................................. 23 GUI VMI
................................................................................. 23 O&M ................................................................................ 24 Standard Operation ............................................................... 24 Alarms .............................................................................. 25 1 1.1 1.2 2 3 3.1 3.2 3.3 3.4 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 5 5.1 5.2 6 6.1 7 7.1 7.2 7.3 7.4 7.5 8 8.1 8.2 A4 XSEIF R2 E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 2 ( 25 ) 1 Introduction This document describes the indoor Radio Base Station (RBS) 3202 in a Radio Access Network (RAN) that uses Wideband Code Division Multiple Access
(WCDMA) technology. 1.1 Purpose This document is intended as a first level introduction to the RBS for network Operations and Maintenance (O&M) personnel. 1.2 Scope This document is divided in the following sections:
Radio Network Overview RBS Overview Hardware Structure Software Structure Functions External Interfaces O&M 2 Radio Network Overview This section gives an overview of the Radio Network of which the RBS is a part. figure 1 shows the parts of the Radio Network. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 3 ( 25 ) Core Network Network Management System Core Network/
other management applications RANOS RAN RNC RBS RAN customer services User Equipment B 00 00268A Figure 1 Radio Network Overview The Radio Network consists of the following parts:
Core Network The Core Network (CN) provides call control as well as mobility for, and localization of, the User Equipment (UE). The CN also interacts with the RNC and provides support for network features and telecommunication services. The CN handles both packet-oriented services, such as data, and circuit-oriented services, such as speech. RAN RAN provides the connection between the CN and the User Equipment
(UE). RAN also comprises interfaces towards different management systems. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 4 ( 25 ) RAN consists of the following parts:
RNC The RNC interacts with the CN as well as the RBSs and manages radio links. The RNC also controls mobility and optimizes the radio network resources. A single RNC can handle one or more RBSs, and an RNC can work with other RNCs to increase capacity. For detailed information regarding the RNC, please refer to Node Description,RNC3810,6/1551AXD10503/1. RBS The RBSs main function is to maintain radio links to UE. A detailed overview of the RBS 3202 is given in the next section entitled RBSOverview. RANOS RANOS is one of the network management systems the operator can use. RANOS handles O&M tasks such as: alarm handling, configuration and performance monitoring. It is possible to integrate RAN with existing network management systems. 3 RBS Overview The RBS provides radio resources and handles radio transmission and reception in one or more cells to and from the UE. 3.1 Main Functions The RBS functionality is divided into traffic and O&M functions. Traffic related functions include:
Communicating with the RNC and UE Handling cells, transport channels, and ATM links O&M functions are:
Ensuring the system becomes, and remains, operational Handling equipment malfunction
E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 5 ( 25 ) Monitoring the RBS performance The RBS also contains all the software necessary for Element Management. 3.2 Hardware The RBS comprises of at least one cabinet with three subracks:
Baseband (BB) Radio Frequency (RF) Multiple Carrier Power Amplifier (MCPA) Apart from the subracks, the RBS consists of a capacitor unit (CU) and a connection field. 3.3 Software This section gives an overview of the software architecture and common platform. For a detailed description, please refer to page 13. Software Architecture The RBS software architecture consists of two layers:
The common platform layer provides basic support for the application program and includes the operating system and provides support for Asynchronous Transfer Mode (ATM) transport, as well as O&M. The application program layer runs on top of the common platform layer and defines the RBS functionality. A Main Processor (MP) and subordinate Board Processors execute the RBS software. Common Platform The RBS software is based on a common platform used both in RBS and RNC. From this platform it is possible to create an ATM cell-switching network node. The common platform consists of an ATM transport system, a distributed real-time telecommunication control system, and an element management system built with Java technology. ATM is used for communication between boards, subracks and nodes. 3.4 RBS Characteristics and Configurations This section gives an overview of RBS characteristics and configurations. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 6 ( 25 ) 3.4.1 Safety and Product Data The RBS has a CE marking and fulfills requirements for RF, electromagnetric compatibility, and so on. For detailed information on safety, product data and environmental characteristics, please refer to HEALTHANDSAFETYINFORMATIONand PRODUCTDATA. 3.4.2 Configurations The RBS has a modular architecture with scalable capacity. A single cabinet can be equipped and configured to handle a minimum of one sector with one carrier, and up to three sectors with two carriers when fully equipped. Currently, the RBS is available in the base configuration 32 (three sectors and two carriers) and the subconfigurations 12, 22, 11, 21, and 31. For detailed information on different RBS configurations, see CONFIGURATION DATA. 4 Hardware Structure An RBS consists of one or more cabinets, each equipped with three subracks and plug-in-units (PIUs). Which PIUs to use depends on configuration type as well as traffic and transmission capacities. figure 2 shows the hardware locations. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 7 ( 25 ) A B C D E F F F B 00 01511B Figure 2 Hardware Locations The letters in the figure above denote:
A) Connection Field B) CU C) BB subrack D) RF subrack E) MCPA subrack F) Subrack Fans Each subrack houses a number of boards designed for different functions. The boards and units are described later in this chapter 4.1 Connection Field The Connection Field is located on top of the cabinet and it comprises interfaces for:
grounding local O&M (Site Lan and Element Manager) Auxiliary Unit Hub (AU-Hub) E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 8 ( 25 ) 4.2 CU The CU keeps the RBS in operation if a short voltage drop should occur on the incoming -48 VDC distribution. 4.3 BB Subrack Baseband functionality handles dedicated and common channels to UE. The BB subrack comprises an interface for the connection with an RNC, an MP cluster, the external ATM interface termination as well as all functionality in the baseband domain except for average output power limiter, power clipping, delay- and gain adjustment which all are located in the RF subrack. The following sections gives a brief description of the boards in the subrack. 4.3.1 ETB The Exchange Terminal Board (ETB) serves as an interface between the transmission cables and the Asynchronous Transfer Mode (ATM) switch on an Switch Core Board (SCB). The ETB provides the connections for the Iub and remote Mub (management interface) interfaces. The type of ETBs depends on the transmission standard. For more information on the transmission standards, please refer to page 11. 4.3.2 SCB The SCB contains an ATM switch and is, via the backplane, connected to the ATM switch ports located on other boards. An SCB can also be connected with up to four other SCBs located in other subracks and to the RF subrack for ATM switching parts. The SCB also has a connector and filter for the system power. The system power is distributed within the subrack via the backplane. The SCB also supervises and controls the subrack fans. The SCB can be duplicated to provide redundancy. Of one SCB stops working, the other takes over the traffic. The first slot and the last slot the BB and RF subrack are reserved for SCBs. 4.3.3 RAXB The Random Access/Receiver Board (RAXB) comprises the BB receiver part, which takes care of:
of decoding, searching and RAKE receiving for dedicated and random access transport channels cell combination for softer hand over. A softer hand over takes place when a UE moves from one sector to another using the same frequency. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 9 ( 25 ) RAXBs within a BB subrack share the load to achieve high availability. If one RAXB fails, the load is divided over the remaining RAXBs. This ensures the RBS continues to handle traffic, although with reduced capacity. 4.3.4 GPB The General Processor Board (GPB) operates as an MP; it contains and executes the main part of the RBS software. The GPB controls devices on boards and in auxiliary units, it has flash disk storage, an Ethernet connection and an RS232 interface. The GPB can be duplicated to provide redundancy, in case of failure in the active MP, the other GPB can be started and take over as MP. 4.3.5 TXB The Transmitter Board (TXB) comprises the BB transmitter part for:
handling transport channels, encoding, cell splitting, modulation and spreading, and channel combining. 4.3.6 TUB The Timing Unit Board (TUB) generates and distributes reference signal for local timing generation. The frequency accuracy is given by an external reference signal either provided on a transmission interface or local external source. The reference signal must be traceable to clock having the equality of Stratum 2 (ITU-T G.812) or better. The TUB can be duplicated to provide redundancy. Due to close relationship with the SCB, the TUB and SCB must be duplicated simultaneously. 4.3.7 BBIFB The Baseband Interface Board (BBIFB) connects the BB subrack to the RF subrack. The connection carries the downlink and uplink traffic streams as well as timing signals. 4.4 RF Subrack The RF subrack contains most of the RF processing hardware (it does not contain the power amplifiers and optional ASC (Antenna System Control). The RF subrack takes care of:
E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 10 ( 25 ) D/A and A/D conversion RF modulation and demodulation RF carrier combining and splitting Llow noise amplification for reception The following sections give a brief description of the boards in the RF subrack. 4.4.1 SCB SCB is described at page 8 . 4.4.2 AIU The Antenna Interface Unit (AIU) board consists of a filter and control unit, as well as a combiner and splitter unit. Filter and Control Unit The filter and control unit provide the following:
Duplex filtering of the transmitter and receiver signal Low-noise amplification of the receiver signal Power measurement of transmitter signal Flexible frequency and signal splitting Combiner and Splitter Unit The combiner and splitter unit performs:
frequency combination in the downlink, signal splitting and high power combination when two MCPA modules are used Frequency combination can be either two- or four-way (when three frequencies have to be combined, the fourth input is unused). When using two MCPA modules for amplification, the combined signal is split, and after amplification, the signals are coherently combined again and sent to one antenna. 4.4.3 RFIFB The Radio Frequency Interface Board (RFIFB) connects the RF subrack to the BB subrack. The connection carries the downlink and uplink traffic, as well as timing signals. The RFIFB also implements power clipping for downlink traffic. 4.4.4 TRXB The Transceiver Board (TRXB) provides the following:
E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 11 ( 25 ) channel filtering delay and gain adjustment A/D and D/A conversion RF modulation and demodulation A TRXB comprises two independent transceivers for two transmitter and receiver signal pairs. 4.5 MCPA Subrack The MCPA subrack contains the linear power amplifiers for the RF carriers. The subrack contains positions for up to six MCPA modules and is connected to the RF subrack through front panel cabling. 4.5.1 MCPA TheMCPAisa20WRFpoweramplifier. 4.5.2 MCPA Hub The MCPA Hub is the connection interface between the MCPA and the RFIFB. 4.6 Transmission Interfaces The cabinet can be equipped and configured for various transmission network needs from one to 32 E1/J1 interfaces and/or one to four STM-1 interfaces. The Interfaces are as follows:
E1 2 Mbit/s, Transmission Link (European standard) J1 1.5 Mbit/s, Transmission Link (Japanese standard) STM-1 155 Mbit/s, Synchronous Transfer Mode on level 1 4.7 Internal Cables This section gives a brief description of the internal RBS cables. 4.7.1 Inter-Subrack Link This cable is a common platform ATM interface cable for inter-subrack communication. It carries control signaling from the MP to device boards in other subracks. This interface cable is a high-speed point-to-point communication link. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 12 ( 25 ) 4.7.2 Gamma Cable This cable connects the BBIFB and RFIFB. The cable carries serial traffic streams from the gamma interface. The BBIFB and RFIFB can connect two gamma cables, one for each antenna branch. 4.7.3 Intra-Cabinet Timing Cable This cable is also a connection between the BBIFB and RFIFB. This cable connection distributes timing signals from the RF to the BB subrack and is used to read RFIFB product information. 4.7.4 Inter-Subrack Timing Cable This cable distributes timing signals from the TUB to RF subracks. This cable is connected to the BBIFB in the main BB subrack and to all RFIFBs. In a multi-cabinet configuration these cables must have the same length. 4.7.5 Internal Jumper Cable This cable carries the transmit and receive RF signals. The cable connects an AIU to the Connection Field, and since an AIU can handle two antenna branches, two cables are connected per AIU. For Antenna Near Products, the AIU can feed power through both cable connections. One of the antenna connectors also has the capability to carry the AU interface, which supervises and controls units, for example the ASC. 4.7.6 MCPA and MCPA Fan Unit Control Cable This cable is the AU control connection for the MCPA and MCPA fan unit. This cable is connected between RFIFB and MCPA hub. MCPAs within the MCPA subrack and the fan unit are controlled through the same connection. 4.7.7 Low-Power Multi-Carrier TX Cable This cable carries the low power RF signal after carrier combination and signal splitting (if applicable) from the AIU to the MCPA. 4.7.8 High-Power TX Cable This cable carries the RF signal from the MCPA to the AIU after power amplification. 4.7.9 Site LAN Cable This cable is an Ethernet-based connection for the thin client. The site LAN cable connects the Ethernet interface of the GPB to the Connection Field. 4.7.10 Transmission Cable This cable connects the ETB to the Connection Field. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 13 ( 25 ) 4.7.11 CU Control Cable This cable is an AU interface connection for supervising and controlling the CU. This cable connects the SCB to the capacitor unit via the Connection Field. 4.7.12 XALM Interface Cable This cable connects the SCB to the Connection Field. The cable is an AU interface and it handles the customer specific alarms and output controls, as well as alarms for Ericsson external equipment. 4.7.13 High-Power Combining Cable This cable is for combining two MCPAs. The high power combiner in the AIU combines the signal from two MCPAs and sends it to one antenna. 4.7.14 Low-Power Single Carrier TX Cable This cable connects the TX output of the TRXB to the AIU for carrier combination and signal splitting, if applicable. 4.7.15 BB Subrack Fan Unit Cable This cable connects the BB subrack fan unit to the SCB and it supervises and controls the fan. 4.7.16 RF Subrack Fan Unit Cable This cable connects the RF subrack fan unit to the SCB and it supervises and controls the fan. 5 Node Architecture The general RBS architecture is described in figure 3 and the following subchapters. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 14 ( 25 ) Control Plane Traffic Control O&M Infrastructure and Platform Transport Baseband Radio Antenna Near Parts User Plane B 00 00 617 Figure 3 Architectural Overview Basically, the functionality is divided into two main parts:
Control plane functionality for traffic and O&M. User plane functionality for transport, baseband, radio and antenna near parts As a basis, there are infrastructure and platform functionality that make all parts fit together. 5.1 Structure There are three important views of an RBS node, each showing a specific aspect and containing several layers:
Platform View Common Platform Layer Application Program Layer Traffic control view Traffic Service Layer Logical Resource Layer Equipment Layer Hardware Layer
E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 15 ( 25 ) Management view Presentation Layer Management Adaptation Layer Resource Layer Platform View The platform view consists of two layers: the common platform layer and the application program layer. The application program layer is the software executing on top of the common platform. The common platform layer isolates the application program layer from the implementation details of the processor and ATM platforms. This makes it possible to change the processor and ATM parts without having to modify the application program. The common platform layer also supports the Element Manager (EM) by providing common platform support functions such as a graphical interface and Java applet communication. Traffic Control View This view hides the specific RBS hardware from the actual services supplied by the RBS to the RNC, and other RBS internal functions. This is done to encapsulate the parts of the system that have to be modified when the hardware is modified. Modification includes both modernization of a specific RBS and handling of different types of RBSs. There are four layers in the traffic control view:
Traffic service layer receives service requests from the RNC and then carries out the application program procedures using logical resources
(channels, cell-carrier, ATM links, and so on). Logical resource layer provides logical resources to the traffic service layer. It transforms operations on logical resources into operations on devices or ATM entities. Equipment layer hides information as to which specific board a certain functionality is allocated. The functionality is supplied to the Logical Resource Layer in term of devices. Hardware layer hides the detailed design of a hardware item. Management View The management view hides implementation details from being visible in the Graphical User Interface (GUI). There are three layers in the management view:
E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 16 ( 25 ) Presentation layer holds the GUI, which consists of, for example, HTML pages and Java applets. This includes work-flow oriented forms for configuration of the system, support for reading and presenting the event log, and so on. The presentation layer is implemented through web pages and applets which run in a web browser on a PC or Unix workstation. Management adaptation layer isolates the managed objects (MOs) interface from the resource objects. The MOs contain read/write attributes, and methods for operations on these objects. A MO may represent an alarm/event generating object (for example, a plug-in-unit), and also alarm/event handling objects such as logs and notification subscription objects. Resource layer hides the lower level implementation details of the MOs, which reduces the impact of changes. The Resource Layer embraces the Traffic Service Layer, Logical Resource Layer, Equipment Layer and the Hardware Layer. Fault detection functions in the resource layer, and also in the common platform, ensure fault and error detection. The hardware layer within the resource layer provides fault and error detection support on a low level. The management adaptation layer and the common platform generate the corresponding alarms. Events can have their origin in any part of the system, but the management adaptation layer and the common platform generate the event reports. 5.2 Common Platform The RNCs and RBSs are based on a Common Platform which consists of modules including both software (such as programs that set up connections and modify operating parameters) and hardware (such as processor boards, switch boards, backplane connectors). The C ommon Platform provides the following services to its application programs:
Core Software execution platform Node O&M Java execution platform System upgrade during operation IP-routing for management Space switching of cells over multiple subracks within the node Database Loading of MP/BP, fundamental configuration and start/restart functions E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 17 ( 25 ) Network and connection handling Transport Service Signaling Service Fractional ATM Network Synchronization 6 Functions The functions are divided into application and common platform functions. The application functions use common platform functions to realize their tasks. Measurement functionality is divided into a detector part (normally in radio transport functions), and a control part, that controls the measurement. Measurement functions have different roles in the measurement functionality. The O&M for traffic control functions is included within the function itself. Security aspects are handled within each function that interfaces with the Mub. Security support is provided by the platform functions. Functions that have an interface for management only cover functionality towards an Mub user. The Mub user can be either an element management node or RANOS. 6.1 Application Functions The application functions are divided into function groups each covering some specific RBS functionality. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 18 ( 25 ) Iub/NBAP Mub Iub/NBAP Iub/FP+AALO RBS t n e m e g a n a M n o i t a r u g i f n o C t n e m e g a n a M e c n a m r o f r e P Trafic Control r e r a e B r o p s n a r T i o d a R n o i t i a z n o r h c n y S Mub Iub/
FP Uu t n e m e g a n a M t l u a F Mub Infrastructure Application Specific Functions Platform Functions Figure 4 Main RBS Application Function Groups See table 1 for RBS function groups. The interfaces mentioned in the table text are described in page 20. B 00 00274A Table 1 RBS Function Groups Function Groups Fault Management Task These functions detect, isolate, and recover from faults in supervised functions. Faults are reported through alarms, and are logged and maintained in an active alarm list. Alarm handling is performed through the Mub interface. Supervision functions are always active and do not have to be configured. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 19 ( 25 ) Function Groups Task Configuration Management Performance Management Traffic Control Radio Transport Bearer These functions create and delete MOs. Attributes of these MOs can be set and read. These functions are performed over the Mub interface. Some functions use the Iub interface. These functions collect, store and report statistics regarding RBS measurements. These functions are performed through the Mub interface. These functions provide control of traffic-related resources such as common and dedicated radio connections, cells and ATM connections. The functions also provide measurement control requested from the RNC. Traffic control is performed through the Iub interface and is managed over the Mub interface. These functions manage user data processing in the BB and RF parts of the RBS node. The functions handle the air interface Uu. Measurement detector functionality is also included. These functions transfer user or control data between the RNC and RBS. The data is carried over the Iub interface. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 20 ( 25 ) Function Groups Synchronization Infrastructure GUI Task These functions provide correct data timing, and prevent data loss due to slip of sent and received information through the system. The functions also provide stable frequency references for RF stabilization. These functions are managed through the Mub interface. Synchronization frames are carried over the Iub interface to and from RNC. These functions handle power feeding, environmental control and basic infrastructure software functionality. These functions are managed through the Mub interface. This function group contains the GUI functionality. The user interface handles the GUI. 7 External Interfaces The RBS is connected to the outside world through the Iub, Uu and Mub interfaces. Besides these interfaces, the RBS provides a management GUI that uses the Mub, as well as a Visual and Mechanical Interface (VMI). The VMI comprises indicators, switches, buttons, cables, and so on. An overview of the external interfaces is given in figure 5. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 21 ( 25 ) RNC Iub Mub RBS Uu UE GUI VMI B 00 00559 Figure 5 External Interfaces 7.1 lub Interface The Iub interface is the standardized interface between the RBS and the RNC. The Iub is divided into several protocol layers:
Physical layer (L1) ATM and ATM adaptation layers (L2) Network layer (L3) for frame handling The L3 protocol for the RNC plane is called NBAP. The L2 and L3 part of air interface channels RACH, FACH, PCH and DCH terminate in the RNC. From an RBS perspective, the different air interface channels are all treated as transparent user plane channels. 7.2 Uu Interface The Uu interface is the radio interface between RBS and the UE. The radio interface is divided into three protocol layers:
Physical layer (L1) Data link layer (L2) Network layer (L3) E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 22 ( 25 ) The L2 comprises of Medium Access (MAC) and Radio Link Control (RLC). The MAC provides unacknowledged transfer of SDUs between peer MAC entities, and the RLC provides data transfer of SDU and can also support the retransmission protocol. L3 comprise the Radio Resource Control (RRC), which interfaces with L2. 7.3 Mub Interface The Mub is the management interface for the RBS and, in contrast to the Iub, is not standardized. The user interacts with the system using a web based thin client. The thin client gets software that is dependent on the managed RBS by loading Java applets from the RBS at execution time. The Mub is based on IP, so the RBS has an IP address. Remote management uses IP over ATM and on-site management uses Ethernet. The necessary low-level communication layers, including FTP server, HTTP server, ORB and Telnet server, are provided by the common platform. The management interfaces are shown in figure 6. RBS Element Manager/RANOS IM File system HTML docs. Java class file Terminal Browser Thin Client
"File Mgr"
"Cmd-
shell"
Telnet IIOP HTTP FTP Telnet IIOP HTTP FTP m r o f t l a P TCP IP TCP IP ATM/Ethernet ATM/Ethernet B 00 00557 Figure 6 Management Interfaces The interfaces are used as follows:
Telnet Telnet provides local and remote access to the operating system shell. The command line interface provides a set of commands handled by a Unix shell-like command interpreter. IIOP E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 23 ( 25 ) IIOP (IP based Inter-ORB Protocol) is the protocol used in Common Object Request Broker Architecture (CORBA). IIOP is the main protocol used for O&M; both the EM and the network manager (RANOS) uses IIOP. HTTP HTTP transfers HTML documents such as online documentation and Java applets from the file system to a managing system. FTP FTP transfers files to and from the file system in the RBS. FTP is primarily used for loading software, configuration data and other large volume data. 7.4 GUI GUI applications are web based (HTML and Java applets) and run in a standard web browser. Two general types exist:
Workflow oriented wizards, for example, for node expansion, initial configurations, and so on Panels used to set preferences, options, and so on 7.5 VMI The VMI consists of:
Visual indicators Switches and buttons Incoming external power External alarms and output Connectors, cables and screws Visual Indicators Each unit or board in the RBS is equipped with Light Emitting Diodes (LEDs):
red ones for fault indication and green ones for indication of operation. Additionally, boards with a processor are equipped with a yellow LED for traffic indication. All LEDs light simultaneously for one second when the power is switched on. Switches and buttons Each power output connector in the busbar is equipped with fused circuit breakers. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 24 ( 25 ) The AIU board has RF jumpers/cables to be able to allow for different RBS configurations with the same board. The jumpers connects combiners and splitters that are applicable for a certain configuration. The PCU contains a number of switches for the power system. The GPB and all device boards are equipped with a reset button. (The button is not reachable from the front of the board). Incoming External Power The RBS can be fed by either AC, DC +24V or DC -48V depending on the power equipment. External Alarms and Output The RBS supports external alarm input ports for both Ericsson or customer-specific use. The operator can configure whether an if an alarm generated by closed or open loop condition. Closed loop means that an alarm is triggered when an open switch is closed, and open loop condition means that an alarm is triggered when a closed switch is open. A number of external output ports for control of external equipment are also available in the RBS. The ports are controlled from a management interface. Connectors, cables and screws This is the actual mechanical interface for the RBS. The interface specifies the mounting of boards into subracks, and how to mount subracks in cabinets. 8 O&M O&M is handled through embedded management. It deals with issues such as:
configuration, fault, performance, and security management. 8.1 Standard Operation The EM monitors the RBS. The user accesses the EM by connecting a thin client to the Site LAN connection plate. Instructions on how to configure and connect a thin client to the RBS are found in PRODUCTHANDLING. For a detailed description of the EM, please refer to ELEMENTMANAGER. The EM performs the following tasks:
RBS EM topology view handling Configuration management Software management Alarm management E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 5/1551-HRB 105 102/1 Uen Date 2003-01-28 Rev C Reference 25 ( 25 ) Restart Timing Unit (TU) switch Object properties handling Locking and unlocking of objects Online help 8.2 Alarms The RBS alarms are collected in an alarm list. From this list it is possible to:
Display alarm details Acknowledge alarms Add comments to an alarm
1 2 3 | User manual 3101 | Users Manual | 192.39 KiB | April 03 2004 |
Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Node Description Contents 1 ( 28 ) Page 1 1.1 1.2 2 3 3.1 3.2 3.3 3.4 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 5 5.1 5.2 6 6.1 7 7.1 7.2 7.3 7.4 7.5 8 8.1 8.2 8.3 Introduction ....................................................................... Purpose ............................................................................ Scope .............................................................................. Radio Network Overview ....................................................... RBS Overview .................................................................... Main Functions .................................................................... Hardware ........................................................................... Software ............................................................................ RBS Characteristics and Configurations ....................................... 2 2 2 2 4 4 5 5 5 6 Hardware Structure .............................................................. BB Subrack ........................................................................ 8 RF Subrack ........................................................................ 10 MCPA Subrack .................................................................... 11 Power Units ........................................................................ 11 Transmission Interfaces .......................................................... 12 Space for Customer Transmission Module ..................................... 13 Connection Fields ................................................................. 13 Climate System ................................................................... 14 Internal Cables .................................................................... 15 Node Architecture ............................................................... 17 Structure ........................................................................... 18 Common Platform ................................................................. 19 Functions ......................................................................... 20 Application Functions ............................................................. 20 External Interfaces .............................................................. 23 lub Interface ....................................................................... 24 Uu Interface ........................................................................ 24 Mub Interface ...................................................................... 25 GUI
................................................................................. 26
................................................................................. 26 VMI Operation & Management ...................................................... 27 Standard Operation ............................................................... 27 Alarms .............................................................................. 28 External Alarms and Outputs .................................................... 28 A4 XSEIF R2 E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 2 ( 28 ) 1 Introduction This document describes the outdoor Radio Base Station (RBS) 3101 in a Radio Access Network (RAN) that uses Wideband Code Division Multiple Access (WCDMA) technology. 1.1 Purpose This document is intended as a first level introduction to the RBS for network Operations and Maintenance (O&M) personnel. 1.2 Scope This document is divided in the following sections:
Radio Network Overview RBS Overview Hardware Structure Software Structure Functions External Interfaces Operation & Maintenance Design for Environment 2 Radio Network Overview This section gives an overview of the Radio Network of which the RBS is a part. figure 1 shows the parts of the Radio Network. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 3 ( 28 ) Core Network Network Management System Core Network/
other management applications RANOS RAN RNC RBS RAN customer services User Equipment B 00 00268A Figure 1 Radio Network Overview The Radio Network consists of the following parts:
Core Network The Core Network (CN) provides call control as well as mobility for, and localization of, the User Equipment (UE). The CN also interacts with the RNC and provides support for network features and telecommunication services. The CN handles both packet-oriented services, such as data, and circuit-oriented services, such as speech. RAN RAN provides the connection between the CN and the User Equipment
(UE). RAN also comprises interfaces towards different management systems. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 4 ( 28 ) RAN consists of the following parts:
RNC The RNC interacts with the CN as well as the RBSs and manages radio links. The RNC also controls mobility and optimizes the radio network resources. A single RNC can handle one or more RBSs and an RNC can work with other RNCs to increase capacity. For detailed information regarding the RNC, please refer to Node Description,RNC3810,6/1551AXD10503/1. RBS The RBSs main function is to maintain radio links to UE. A detailed overview of the RBS 3101 is given in the next section entitled RBSOverview. RANOS RANOS is one of the network management systems the operator can use. RANOS handles O&M tasks such as: alarm handling, configuration and performance monitoring. It is possible to integrate RAN with existing network management systems. 3 RBS Overview The RBS provides radio resources and handles radio transmission and reception in one or more cells to and from the UE. 3.1 Main Functions The RBS functionality is divided into traffic and O&M functions. Traffic related functions include:
Communicating with the RNC and UE Handling cells, transport channels, and ATM links O&M functions are:
Ensuring the system becomes, and remains, operational Handling equipment malfunction
E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 5 ( 28 ) Monitoring the RBS performance The RBS also contains all the software necessary for Element Management. 3.2 Hardware The RBS comprises of at least one cabinet with four subracks:
Baseband (BB) Radio Frequency (RF) Multiple Carrier Power Amplifier (MCPA) Power Apart from the subracks, the RBS consists of a climate system, batteries and power distribution units 3.3 Software This section gives an overview of the software architecture and common platform. For a detailed description, please refer to page 17. Software Architecture The RBS software architecture consists of two layers:
The common platform layer provides basic support for the application program and includes the operating system and provides support for Asynchronous Transfer Mode (ATM) transport, as well as O&M. The application program layer runs on top of the common platform layer and defines the RBS functionality. A Main Processor (MP) and subordinate Board Processors execute the RBS software. Common Platform The RBS software is based on a common platform used both in RBS and RNC. From this platform it is possible to create an ATM cell-switching network node. The common platform consists of an ATM transport system, a distributed real-time telecommunication control system, and an element management system built with Java technology. ATM is used for communication between boards, subracks and nodes. 3.4 RBS Characteristics and Configurations This section gives an overview of RBS characteristics and configurations. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 6 ( 28 ) 3.4.1 Safety and Product Data The RBS has a CE marking and fulfills requirements for RF, electromagnetric compatibility, and so on. For detailed information on safety, product data and environmental characteristics, please refer to HEALTHANDSAFETYINFORMATIONand PRODUCTDATA. 3.4.2 Configurations The RBS has a modular architecture with scalable capacity. A single cabinet can be equipped and configured to handle a minimum of one sector with one carrier, and up to three sectors with two carriers when fully equipped. Currently, the RBS is available in the base configuration 32 (three sectors and two carriers) and the subconfigurations 12, 22, 11, 21, and 31. For detailed information on different RBS configurations, see CONFIGURATION DATA 4 Hardware Structure An RBS consists of one or more cabinets, each equipped with four subracks and plug-in-units (PIUs). Which PIUs to use depends on configuration type as well as traffic and transmission capacities. figure 2 shows the hardware locations. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 7 ( 28 ) A B C D E F G H I J PONMLK Q B 00 01656 Figure 2 Hardware Location The letters in the figure above denote:
A) B) C) D) E) F) G) H) I) J) Climate System Site LAN Inteface (including O&M interface) Auxiliary Unit Hub (AU-Hub) External Alarm Module (XALM) BB Subrack Power Subrack Smoke Detector Internal Distribution Module/Battery Fuse Unit (IDM/BFU) RF Subrack AC Connection Unit (ACCU) Distribution Unit (with Service Outlet) E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 8 ( 28 ) K) L) M) N) O) P) Q) Interface Connection Field (ICF 3) and space for Customer Transmission Module Distribution Frame (DF) ACCU Connection Unit Auxiliary Distribution Module (ADM) RF Connection Box Batteries MCPA Subrack Each subrack houses a number of boards designed for different functions. The boards and units are described later in this chapter. 4.1 BB Subrack Baseband functionality handles dedicated and common channels to UE. The BB subrack comprises an interface for the connection with an RNC, an MP cluster, the external ATM interface termination as well as all functionality in the baseband domain except for average output power limiter, power clipping, delay- and gain adjustment which all are located in the RF subrack. The following sections gives a brief description of the boards in the subrack. 4.1.1 ETB The Exchange Terminal Board (ETB) serves as an interface between the transmission cables and the ATM switch on an Switch Core Board (SCB). The ETB provides the connections for the Iub and remote Mub (management interface) interfaces. The type of ETBs depends on the transmission standard. For more information on the transmission standards, please refer to page 12. 4.1.2 SCB The SCB contains an ATM switch and is, via the backplane, connected to the ATM switch ports located on other boards. An SCB can also be connected with up to four other SCBs located in other subracks and to the RF subrack for ATM switching parts. The SCB also has a connector and filter for the system power. The system power is distributed within the subrack via the backplane. The SCB also supervises and controls the subrack fans. The SCB can be duplicated to provide redundancy. Of one SCB stops working, the other takes over the traffic. The first slot and the last slot the BB and RF subrack are reserved for SCBs. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked 4.1.3 RAXB Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 9 ( 28 ) The Random Access/Receiver Board (RAXB) comprises the BB receiver part, which manages:
Decoding, searching and RAKE receiving for dedicated and random access transport channels. Cell combination for softer hand over. A softer hand over takes place when a UE moves from one sector to another using the same frequency. RAXBs within a BB subrack share the load to achieve high availability. If one RAXB fails, the load is divided over the remaining RAXBs. This ensures the RBS continues to handle traffic, although with reduced capacity. 4.1.4 GPB The General Processor Board (GPB) operates as an MP; it contains and executes the main part of the RBS software. The GPB controls devices on boards and in auxiliary units. It has flash disk storage, an Ethernet connection and an RS232 interface. The GPB can be duplicated to provide redundancy. If there is a failure in the active MP, the redundant GPB can be started and take over as the MP. 4.1.5 TXB The Transmitter Board (TXB) comprises the BB transmitter part for:
handling transport channels encoding cell splitting modulation and spreading channel combining 4.1.6 TUB The Timing Unit Board (TUB) generates and distributes reference signal for local timing generation. The frequency accuracy is given by an external reference signal either provided on a transmission interface or local external source. The reference signal must be traceable to clock having the equality of Stratum 2 (ITU-T G.812) or better. The TUB can be duplicated to provide redundancy. Due to close relationship with the SCB, the TUB and SCB must be duplicated simultaneously. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 10 ( 28 ) 4.1.7 BBIFB The Baseband Interface Board (BBIFB) connects the BB subrack to the RF subrack. The connection carries the downlink and uplink traffic streams as well as timing signals. 4.2 RF Subrack The RF subrack contains most of the RF processing hardware (it does not contain the power amplifiers and optional ASC (Antenna System Control). The RF subrack takes care of:
D/A and A/D conversion RF modulation and demodulation RF carrier combining and splitting Low noise amplification for reception The following sections give a brief description of the boards in the RF subrack. 4.2.1 SCB SCB is described at page 8 . 4.2.2 AIU The Antenna Interface Unit (AIU) board consists of a filter and control unit, as well as a combiner and splitter unit. Filter and Control Unit The filter and control unit provide the following:
Duplex filtering of the transmitter and receiver signal Low-noise amplification of the receiver signal Power measurement of transmitter signal Flexible frequency and signal splitting Combiner and Splitter Unit The combiner and splitter unit performs:
Frequency combination in the downlink Signal splitting and high power combination when using two MCPA modules Frequency combination can be either two- or four-way (when three frequencies have to be combined, the fourth input is unused). When using two MCPA E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 11 ( 28 ) modules for amplification, the combined signal is split, and after amplification, the signals are coherently combined again and sent to one antenna. 4.2.3 RFIFB The Radio Frequency Interface Board (RFIFB) connects the RF subrack to the BB subrack and to the MCPA hub. The connection carries the downlink and uplink traffic, as well as timing signals. The RFIFB also implements power clipping for downlink traffic. 4.2.4 TRXB The Transceiver Board (TRXB) provides the following:
Channel filtering Delay and gain adjustment A/D and D/A conversion RF modulation and demodulation A TRXB comprises two independent transceivers for two transmitter and receiver signal pairs. 4.3 MCPA Subrack The MCPA subrack contains the linear power amplifiers for the RF carriers. The subrack contains positions for up to six MCPA modules and is connected to the RF subrack through front panel cabling. 4.3.1 MCPA The MCPA is a 20 W RF power amplifier. Each power amplifier can simultaneously amplify up to four RF carriers, by dividing the power over the carriers. 4.3.2 MCPA Hub The MCPA Hub is the connection interface between the MCPA and the RFIFB. 4.4 Power Units The Power Units are divided into subrack units and subrack external units. The Power Control Unit (PCU) and Power Supply Units (PSUs) are located in the power subrack. The subrack external units are ACCU, IDM/BFU, Batteries, and ADM. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 12 ( 28 ) 4.4.1 PCU The PCU supervises the PSUs, IDM/BFU, ACCU, power subrack fan and the climate system with regards to controlled functionality, abnormal conditions and failures. 4.4.2 PSU The PSU converts and rectifies the incoming power from the ACCU to 48 VDC system voltage. The PSU distributes the converted power to the IDM/BFU for distribution to other subracks. 4.4.3 ACCU The ACCU receives the incoming power and distributes it, via circuit breakers located in the ACCU, to the PSUs, climate system, lamp, smoke detector and service outlet . The ACCU consists of two parts: the connection unit at the bottom center of the cabinet and the distribution unit in the left part of the cabinet. The AC power cables connected to the connection unit must be adapted up to a 32 A fuse or a 63 A fuse. The ACCU also contains the cold start function, which is used when the RBS is started in temperatures below +5C. The ACCU then only supplies the Climate Control Unit (CCU) with power and the heater is turned on. When the temperature sensor senses that the internal temperature in the ACCU reaches
+5C, the rest of the RBS is supplied with power. 4.4.4 IDM/BFU The IDM/BFU handles the internal DC distribution and it is the connection point between the power distributors (PSUs and batteries) and the power consuming units. The IDM/BFU is equipped with a main distribution branch with fuses and a contactor. 4.4.5 ADM The ADM distributes the DC power taken from the IDM/BFU to the DC users in the Customer Transmission Module. The ADM is optional. 4.4.6 Batteries The RBS has an internal battery backup time of 30 minutes of operation. The four 12 V batteries provides 48 VDC. To prevent too high temperature, the batteries must be vented. The batteries are not included upon delivery due to safety regulations. Batteries are optional. 4.5 Transmission Interfaces The cabinet can be equipped and configured for various transmission network needs from one to 16 E1/J1 interfaces and/or one to four STM-1 interfaces. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 13 ( 28 ) The interfaces are as follows:
E1 2 Mbit/s, Transmission Link (European standard) J1 1.5 Mbit/s, Transmission Link (Japanese standard) STM-1 155 Mbit/s, Synchronous Transfer Mode on level 1 4.6 Space for Customer Transmission Module The RBS 3101 has a space for the operator transmission equipment. The space has a height of 267 mm and width of 446 mm. 4.7 Connection Fields This section gives a brief description of the connection fields in the RBS. 4.7.1 DF The DF contains over voltage protection and connection fields for transmission. The DF is also a connection field for external alarms that can be connected to and controlled by the XALM . 4.7.2 RF Connection Box The RF Connection Box is the connection interface for jumper cables and grounding. 4.7.3 Site LAN Connection Plate The Site LAN Connection Plate is an Ethernet based interface for connecting the thin client used for O&M. 4.7.4 XALM The XALM handles the customer specific alarms as well as alarms for Ericsson equipment, such as smoke detector alarm and door alarm. 4.7.5 ICF 3 The ICF3 is located under the space for Customer Transmission Module. The ICF3 is used:
for installing the DC filter for the external DC power supply as an interface for optional customer specific transmisstion equipment for STM-1/ETB-M4 cable passage E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked 4.8 Climate System Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 14 ( 28 ) The Climate System consists of a Climate Unit located in the cabinet door and fans located in the subracks. The cabinet either has a Combined Climate Unit or a Heat Exchanger Climate Unit. The difference between them is that the Heat Exchanger Climate Unit does not have an Active Cooler and thus cannot be used when the cabinet needs to operate at high ambient temperatures. 4.8.1 Combined Climate Unit The Combined Climate Unit mainly consists of:
Heat Exchanger Element consists of a cross flow Heat Exchanger as well as an external air circuit fan. Active Cooler consists of a compressor, reducing valve, condenser, evaporator and AC condensor fan. At low ambient temperatures, only the Heat Exchanger operates to cool the cabinet. At high ambient temperatures, the Active Cooler also operates to cool the cabinet. The Heat Exchanger and Active Cooler co-operate to ensure that long time average power consumption is minimized. Heater is used to ensure that the temperature inside the cabinet is kept above a certain level. The Heater is AC supplied and equipped with an over-temperature protection. The Heater and the Active Cooler are interlocked to prevent from being operated at the same time. CCU controls and supervises the climate system. Fans apart from the Condensor Fan in the Active Cooler and the external air circuit fan in the Heat Exchanger, a third fan distributes the internal air in the cabinet. 4.8.2 Heat Exchanger Climate Unit The Heat Exchanger Climate Unit mainly consists of:
Heat Exchanger Element operates with four cross flow heat exchangers that reduces the heat loads whenever the cabinet exceeds ambient temperatures, as well as two external air circuit fans. Heaters the two heaters are used at cold start-ups when the ambient temperature is lower than the minimum operating temperature. The internal fan blows the air across the heaters. CCU controls and supervises the climate system. Fans apart from the external air circuit fans in the Heat Exchanger element, a third fan distributes the internal air in the cabinet. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 15 ( 28 ) 4.9 Internal Cables This section gives a brief description of the internal RBS cables. 4.9.1 Inter-Subrack Link This cable is a common platform ATM interface cable for inter-subrack communication, it carries control signaling from the MP to device boards in other subracks. This interface cable is a high-speed point-to-point communication link. 4.9.2 Gamma Cable This cable connects the BBIFB and RFIFB, the cable carries serial traffic streams from the gamma interface. The BBIFB and RFIFB can connect two gamma cables, one for each antenna branch. 4.9.3 Intra-Cabinet Timing Cable This cable is also a connection between the BBIFB and RFIFB. This cable connection distributes timing signals from the RF to the BB subrack and is used to read RFIFB product information. 4.9.4 Inter-Subrack Timing Cable This cable distributes timing signals from the TUB to RF subracks. The cable is connected to the BBIFB in the main BB subrack and to all RFIFBs. In a multi-cabinet configuration these cables must have the same length. 4.9.5 Internal Jumper Cable This cable carries the transmit RF and receive RF signals. The cable connects an AIU to the Connection Field and since an AIU can handle two antenna branches, two cables are connected per AIU. For Antenna Near Products, the AIU can feed power through both cable connections. One of the antenna connectors also has the capability to carry the AU interface, which supervises and controls units, for example the ASC. 4.9.6 MCPA and MCPA Fan Unit Control Cable This cable is the AU control connection for the MCPA and MCPA fan unit. The cable is connected between RFIFB and MCPA hub. MCPAs within the MCPA subrack and the fan unit are controlled through the same connection. 4.9.7 Low-Power Multi-Carrier TX Cable This cable carries the low power RF signal after carrier combination and signal splitting (if applicable) from the AIU to the MCPA. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 16 ( 28 ) 4.9.8 High-Power TX Cable This cable carries the RF signal from the MCPA to the AIU after power amplification. 4.9.9 Transmission Cable This cable connects the ETB to the Connection Field. 4.9.10 Power Supply Control Cable This cable is an auxiliary unit interface connection for the supervision and control of the power subrack. 4.9.11 Site LAN Connection Cable This cable connects the GPB to the Site LAN connection plate at the right side of the inside of the cabinet. 4.9.12 XALM Interface Cable This cable connects the AU Hub to the XALM interface. The cable is an auxiliary unit interface and handles the customer specific alarms and control outputs as well as alarms for Ericsson external and internal equipment. 4.9.13 PCU to PSU Cable This cable between PCU and PSU is used for supervision and control of PSU in the Power Subrack. 4.9.14 High-Power Combining Cable This cable is used when combining two MCPAs. The high power combiner in the AIU combines the signal from two MCPAs and sends it to one antenna. 4.9.15 Low-Power Single Carrier TX Cable This cable connects the TX output of the Transceiver PBA to the AIU for carrier combination and signal splitting, if applicable. 4.9.16 BB Subrack Fan Unit Cable This cable connects the BB subrack fan unit to the SCB and is used for supervision and control of the fans. 4.9.17 Power Subrack Fan Unit Cable This cable connects the RF subrack fan unit to the SCB and is used for supervision and control of the fans. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 17 ( 28 ) 4.9.18 RF Subrack Fan Unit Cable This cable connects the RF subrack fan unit to the SCB and is used for supervision and control of the fans. 4.9.19 AU-Hub cable and AU-Hub The Auxiliary Unit Hub is an internal interface. It connects units such as the XALM and the PCU. 5 Node Architecture The general RBS architecture is described in figure 3 and the following subsections. Control Plane Traffic Control O&M Infrastructure and Platform Transport Baseband Radio Antenna Near Parts User Plane B 00 00 617 Figure 3 Architectural Overview Basically, the functionality is divided into two main parts:
Control plane functionality for traffic and O&M. User plane functionality for transport, baseband, radio and antenna near parts As a basis, there are infrastructure and platform functionality that make all parts fit together. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 18 ( 28 ) 5.1 Structure There are three important views of an RBS node, each showing a specific aspect and containing several layers:
Platform View Common Platform Layer Application Program Layer Traffic control view Traffic Service Layer Logical Resource Layer Equipment Layer Hardware Layer Management view Presentation Layer Management Adaptation Layer Resource Layer Platform View The platform view consists of two layers: the common platform layer and the application program layer. The application program layer is the software executing on top of the common platform. The common platform layer isolates the application program layer from the implementation details of the processor and ATM platforms. This makes it possible to change the processor and ATM parts without having to modify the application program. The common platform layer also supports the Element Manager (EM) by providing common platform support functions such as a graphical interface and Java applet communication. Traffic Control View This view hides the specific RBS hardware from the actual services supplied by the RBS to the RNC, and other RBS internal functions. This is done to encapsulate the parts of the system that have to be modified when the hardware is modified. Modification includes both modernization of a specific RBS and handling of different types of RBSs. There are four layers in the traffic control view:
E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 19 ( 28 ) Traffic service layer receives service requests from the RNC and then carries out the application program procedures using logical resources
(channels, cell-carrier, ATM links, and so on). Logical resource layer provides logical resources to the traffic service layer. It transforms operations on logical resources into operations on devices or ATM entities. Equipment layer hides information as to which specific board a certain functionality is allocated. The functionality is supplied to the Logical Resource Layer in term of devices Hardware layer hides the detailed design of a hardware. Management View The management view hides implementation details from being visible in the Graphical User Interface (GUI). There are three layers in the management view:
Presentation layer holds the GUI, which consists of, for example, HTML pages and Java applets. This includes work-flow oriented forms for configuration of the system, support for reading and presenting the event log, etc. The presentation layer is implemented through web pages and applets which run in a web browser on a PC or Unix workstation. Management adaptation layer isolates the managed objects (MOs) interface from the resource objects. The MOs contain attributes which can be read or written, and methods for operations on these objects. An MO may represent an alarm/event generating object (for example, a plug-in-unit), and also alarm/event handling objects such as logs and notification subscription objects. Resource layer hides the lower level implementation details of the MOs, which reduces the impact of changes. The Resource Layer embraces the Traffic Service Layer, Logical Resource Layer, Equipment Layer and the Hardware Layer. Fault detection functions in the resource layer, and also in the common platform, ensure fault and error detection. The hardware layer within the resource layer provides fault and error detection support on a low level. The management adaptation layer and the common platform generate the corresponding alarms. Events can have their origin in any part of the system, but the management adaptation layer and the common platform generate the event reports. 5.2 Common Platform The RNCs and RBSs are based on a Common Platform which consists of modules including both software (such as programs that set up connections and modify operating parameters) and hardware (such as processor boards, switch boards, backplane connectors). E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 20 ( 28 ) The C ommon Platform provides the following services to its application programs:
Core Software execution platform Node O&M Java execution platform System upgrade during operation IP-routing for management Space switching of cells over multiple subracks within the node Database Loading of MP/BP, fundamental configuration and start/restart functions Network and connection handling Transport Service Signaling Service Fractional ATM Network Synchronization 6 Functions The functions are divided into application and common platform functions. The application functions use common platform functions to realize their tasks. Measurement functionality is divided into a detector part (normally in radio transport functions), and a control part that controls the measurement. Measurement functions have different roles in the measurement functionality. 6.1 Application Functions The application functions are divided into function groups each covering some specific RBS functionality. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 21 ( 28 ) Iub/NBAP Mub Iub/NBAP Iub/FP+AALO RBS t n e m e g a n a M n o i t a r u g i f n o C t n e m e g a n a M e c n a m r o f r e P Trafic Control r e r a e B r o p s n a r T i o d a R n o i t i a z n o r h c n y S Mub Iub/
FP Uu t n e m e g a n a M t l u a F Mub Infrastructure Application Specific Functions Platform Functions Figure 4 Main RBS Application Function Groups See table 1 for RBS function groups. The interfaces mentioned in the table text are described in page 23. B 00 00274A Table 1 RBS Function Groups Function Group Fault Management Task These functions detect, isolate, and recover from faults in supervised functions. Faults are reported through alarms, they are logged and maintained in an active alarm list. Alarm handling is performed through the Mub interface. Supervision functions are always active and do not have to be configured. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 22 ( 28 ) Function Group Task Configuration Management Performance Management Traffic Control Radio Transport Bearer These functions create and delete MOs. Attributes of these MOs can be set and read. These functions are performed over the Mub interface. Some functions use the Iub interface. These functions collect, store and report statistics regarding RBS measurements. These functions are performed through the Mub interface. These functions provide control of traffic-related resources such as common and dedicated radio connections, cells and ATM connections. The functions also provide control of measurement requested from the RNC. Traffic control is performed through the Iub interface and is managed over the Mub interface. These functions manage user data processing in the BB and RF parts of the RBS node. The functions handle the air interface Uu. Measurement detector functionality is also included. These functions transfer user or control data between the RNC and RBS. The data is carried over the Iub interface. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 23 ( 28 ) Function Group Synchronization Infrastructure GUI Task These functions provide correct data timing, and prevent data loss due to slip of sent and received information through the system. The functions also provide stable frequency references for RF stabilization. Synchronization functions are managed through the Mub interface. Synchronization frames are carried over the Iub interface to and from RNC. These functions handle power feeding, environmental control and basic infrastructure software functionality. These functions are managed through the Mub interface. This function group contains the GUI functionality. The user interface handles the GUI. 7 External Interfaces The RBS is connected to the outside world through the Iub, Uu and Mub interfaces. Besides these interfaces, the RBS provides a management GUI that uses the Mub, and a Visual and Mechanical Interface (VMI). The VMI comprises indicators, switches, buttons, cables, and etc. An overview of the external interfaces is given in figure 5. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 24 ( 28 ) RNC Iub Mub RBS Uu UE GUI VMI B 00 00559 Figure 5 External Interfaces 7.1 lub Interface The Iub interface is the interface between the RBS and the RNC. The Iub is divided into several protocol layers:
Physical layer (L1) ATM and ATM adaptation layers (L2) Network layer (L3) for frame handling The L3 protocol for the RNC plane is called NBAP. The L2 and L3 part of air interface channels RACH, FACH, PCH and DCH terminate in the RNC. From an RBS perspective, the different air interface channels are all treated as transparent user plane channels. 7.2 Uu Interface The Uu interface is the radio interface between RBS and the UE. The radio interface is divided into three protocol layers:
Physical layer (L1) Data link layer (L2) Network layer (L3) E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 25 ( 28 ) The L2 comprises of Medium Access (MAC) and Radio Link Control (RLC). The MAC provides unacknowledged transfer of SDUs between peer MAC entities, and the RLC provides data transfer of SDU and can also support the retransmission protocol. L3 comprise the Radio Resource Control (RRC), which interfaces with L2. 7.3 Mub Interface The Mub is the management interface for the RBS and, in contrast to the Iub, is not standardized. The user interacts with the system using a web based thin client. The thin client gets software that is dependent on the managed RBS by loading Java applets from the RBS at execution time. The Mub is based on IP, so the RBS has an IP address. Remote management uses IP over ATM and on-site management uses Ethernet. The necessary low-level communication layers, including FTP server, HTTP server, ORB and Telnet server, are provided by the common platform. The management interfaces are shown in figure 6. RBS Element Manager/RANOS IM File system HTML docs. Java class file Terminal Browser Thin Client
"File Mgr"
"Cmd-
shell"
Telnet IIOP HTTP FTP Telnet IIOP HTTP FTP m r o f t l a P TCP IP TCP IP ATM/Ethernet ATM/Ethernet B 00 00557 Figure 6 Management Interfaces The interfaces are used as follows:
Telnet Telnet provides local and remote access to the operating system shell. The command line interface provides a set of commands handled by a Unix shell-like command interpreter. IIOP E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 26 ( 28 ) IIOP (IP based Inter-ORB Protocol) is the protocol used in Common Object Request Broker Architecture (CORBA). IIOP is the main protocol used for O&M; both the EM and the network manager (RANOS) uses IIOP. HTTP HTTP transfers HTML documents such as online documentation and Java applets from the file system to a managing system. FTP FTP transfers files to and from the file system in the RBS. FTP is primarily used for loading software, configuration data and other large volume data. 7.4 GUI GUI applications are web based (HTML and Java applets) and run in a standard web browser. Two general types exist:
Workflow oriented wizards, for example for node expansion, initial configurations and so on Panels used to set preferences, options and so on 7.5 VMI The VMI consists of:
Visual indicators Switches and buttons External alarms and output Connectors, cables and screws Visual Indicators Each unit or board in the RBS is equipped with Light Emitting Diodes (LEDs):
red ones for fault indication and green ones for indication of operation. Additionally, boards with a processor are equipped with a yellow LED for traffic indication. All LEDs light simultaneously for one second when the power is switched on. Switches and Buttons Each power output connector in the IDM/BFU is equipped with fused circuit breakers. The AIU board has RF jumpers/cables to be able to allow for different RBS configurations with the same board. The jumpers connects combiners and splitters that are applicable for a certain configuration. E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 27 ( 28 ) The GPB and all device boards are equipped with a reset button. (The button is not reachable from the front of the board). External Alarms and Output The RBS supports external alarm input ports for both Ericsson or customer-specific use. The operator can configure whether an if an alarm generated by closed or open loop condition. Closed loop means that an alarm is triggered when an open switch is closed, and open loop condition means that an alarm is triggered when a closed switch is open. A number of external output ports for control of external equipment are also available in the RBS. The ports are controlled from a management interface. Connectors, Cables and Screws This is the actual mechanical interface for the RBS. The interface specifies the mounting of boards into subracks and how to mount subracks in cabinets. 8 Operation & Management O&M is handled through embedded management and deal with issues such as: configuration, fault, performance, and security management. 8.1 Standard Operation The EM monitors the RBS. The user accesses the EM by connecting a thin client to the Site LAN connection plate. Instructions on how to configure and connect a thin client to the RBS are found in PRODUCTHANDLING. For a detailed description of the EM, please refer to ELEMENTMANAGER. The EM performs the following:
RBS EM topology view handling Configuration management Software management Alarm management Restart Timing Unit (TU) switch Object properties handling Locking and unlocking of objects Online help E Prepared (also subject responsible if other) ERA/RGN/PD Jennie Bergstrm Approved ERA/RKF/TU Carl Helander Checked Open Information DESCRIPTION No 10/1551-HRB 105 102/1 Uen Date 2003-01-30 Rev C Reference 28 ( 28 ) 8.2 Alarms The RBS alarms are collected in an alarm list. From this list it is possible to:
Display alarm details Acknowledge alarms Add comments to an alarm 8.3 External Alarms and Outputs The RBS provides external alarm input ports to be used for both Ericsson and customer specific use. The Ericsson external alarms have a predefined alarm definition while the alarm definition for the customer external alarms can be specified by a command. It is possible to configure whether an alarm is generated by closed or open loop condition. A number of external output ports for control of external equipment is also available in the RBS. The ports are controlled through the management interface.
1 2 3 | User manual 3104 | Users Manual | 134.80 KiB | September 03 2004 |
Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Node Description Contents 1 ( 20 ) Page 1 1.1 1.2 2 3 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 5 5.1 5.2 6 6.1 6.2 7 7.1 7.2 7.3 7.4 7.5 8 8.1 8.2 Introduction ....................................................................... Purpose ............................................................................ Scope .............................................................................. Radio Network Overview ....................................................... RBS Overview .................................................................... 2 2 2 2 4 5 Hardware Structure .............................................................. 6 Combined Baseband and Radio Frequency Subrack ......................... 9 MCPA .............................................................................. 9 XALM ............................................................................... 9 Capacitor Unit
..................................................................... Climate System ................................................................... 9 Internal Cables .................................................................... 10 Connections to the RBS .......................................................... 11 Node Architecture ............................................................... 11 Architectural Overview ............................................................ 11 Layered Views ..................................................................... 12 Functions ......................................................................... 14 Application Functions ............................................................. 14 Platform Functions ................................................................ 16 External Interfaces .............................................................. 16 lub Interface ....................................................................... 17 Uu Interface ........................................................................ 17 Mub Interface ...................................................................... 17 GUI
................................................................................. 18 Visual and Mechanical Interface ................................................. 19 Operation & Maintenance ...................................................... 19 Standard Operation ............................................................... 19 Alarms .............................................................................. 20 A4 XSEIF R2 E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 2 ( 20 ) 1 Introduction This document describes Radio Base Station (RBS) 3104 in a Radio Access Network (RAN) that uses Wideband Code Division Multiple Access (WCDMA) technology. The RBS 3104 is intended for outdoor use. 1.1 Purpose This document is intended as a first level introduction to the RBS for network operations and maintenance (O&M) personnel. 1.2 Scope The document gives a brief description of the different nodes in the RAN and a detailed description of the RBS. For further information, see :
page 2 page 4 page 5 page 11 page 14 page 16 page 19 2 Radio Network Overview This section gives an overview of the Radio Network in which the RBS is a part. figure 1 shows the parts of the Radio Network. E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 3 ( 20 ) Core Network Network Management System Core Network/
other management applications RANOS RAN RNC RBS RAN customer services User Equipment B 00 00268A Figure 1 Radio Network Overview The Radio Network consists of the following parts:
Core Network The Core Network (CN) provides call control as well as mobility for, and localization of, the User Equipment (UE). The CN also interacts with the RNC and provides support for network features and telecommunication services. The CN handles both packet-oriented services, such as data, and circuit-oriented services, such as speech. RAN The RAN provides the connection between the CN and the UE. The RAN also comprises interfaces towards different management systems. The RAN consists of the RNC and the RBS. The RNC interacts with the CN as well as the RBSs and manages radio links. The RNC also controls mobility and optimizes the radio network E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 4 ( 20 ) resources. A single RNC can handle one or more RBSs and an RNC can work with other RNCs to increase capacity. For detailed information about the RNC, seeNodeDescription,RNC3810, 6/1551-AXD10503/1. The RBS provides radio resources and handles radio transmission and reception to and from the UE. RANOS RANOS is one of the network management systems the operator can use. RANOS is used to handle O&M tasks such as alarm handling, configuration and performance monitoring. It is possible to integrate RAN with existing network management systems. 3 RBS Overview The following section is a brief introduction to the RBS. Common Platform The RBS hardware and software are based on a common platform used both in RBS and RNC. From this platform it is possible to create an Asynchronous Transfer Mode (ATM) cell-switching network node. The common platform consists of an ATM transport system, a distributed real-time telecommunication control system, and an element management system built with Java technology. Hardware The RBS comprises one cabinet with a subrack for plug-in units. Other units are a Climate Unit, a Fan Unit, a Capacitor Unit, a Connection Field and a Power Distribution Unit. Software The RBS software architecture consists of two layers: the Common Platform Layer and the Application Program Layer:
The Common Platform Layer provides basic support for the application program and includes the operating system and provides support for ATM transport, and O&M. The application program runs on top of the Common Platform Layer and defines the RBS functionality. A Main Processor (MP) and subordinate Board Processors execute the RBS software. E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 5 ( 20 ) RBS Main Services and Functions The RBS provides radio resources for the RAN. It provides radio transmission and reception in one cell. The RBS functionality is subdivided into traffic and O&M functions:
The traffic related functions handle the user data traffic and control communication with the RNC and the UE. This also includes the handling of cells, transport channels, and ATM links. The O&M functions ensure that the system becomes and remains operational, handles equipment malfunctions, and monitors the RBS performance. RBS Characteristics and Configurations For detailed information on product safety, product data and environmental characteristics, please refer to HealthandSafetyInformation,RBS3104, 7/12446HRB105102and ProductDataRBS3104,1/1553COH109392. The RBS has a modular architecture with scalable capacity. For detailed information on different RBS configurations, please refer to Configuration DataRBS3104. 4 Hardware Structure This section describes the units, the climate system, the internal cables and the connection field in the RBS 3104. An RBS 3104 consists of a single cabinet configured to handle one Radio Frequency carrier in one sector. The cabinet contains a subrack that can be equipped with several plug in units (PIU) depending on configuration and various traffic and transmission capacities. The location of the subrack, the climate system and other modules in the cabinet is shown in figure 2. E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 6 ( 20 ) A Climate Unit B Lifting Eyes C Fan Unit D BB/RF Subrack E MCPA F XALM G Capacitor Unit (CU) H Power Distribution Unit B 00 01831B K Heater J Connection Field Figure 2 RBS 3104, hardware The letters in the figure above denote:
Table 1 RBS 3104 main components Pos. Unit A B C D E F G H J K Climate Unit, seechapter4.5 Lifting Eyes Fan Unit, seechapter4.5 BB/RF Subrack Base Band/Radio Frequency Subrack, see chapter 4.1 MCPA XALM CU Multi Carrier Power Amplifier, seechapter4.2 External Alarm Unit, seechapter4.3. Capacitor Unit, seechapter4.4 Power Distribution Unit, seechapter4.7 Connection Field seechapter4.7 Heater, seechapter4.5 4.1 Combined Baseband and Radio Frequency Subrack The combined BB/RF subrack is based on a common platform. The Switch Core Board (SCB) uses the ATM protocol for communication via the backplane E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 7 ( 20 ) within the subrack. The subracks BB and RF parts are connected to each other through the BB Interface Board (BBIFB) and the RF Interface Board (RFIFB) carrying the downlink and uplink traffic streams. The BB/RF subrack comprises an Iub interface connection with an RNC, the MP cluster, and the baseband and radio frequency functionality. Baseband functionality consists of:
Encoding and decoding of transport channels Spreading of bits Combining of channels Reception through a rake receiver Searching and random access processing The RF part contains all the RF processing hardware, except for the power amplifiers. It takes care of:
D/A and A/D conversion RF modulation and demodulation RF carrier combining and splitting Low noise amplification for reception The following sections give a brief description of the boards in the subrack. 4.1.1 Baseband Boards ETB The Exchange Terminal Board (ETB) provides the connections for the Iub and remote Mub interfaces. It serves as an interface between the transmission cables and the Asynchronous Transfer Mode (ATM) switch on an SCB. The type of ETB(s) depends on the transmission standard. SCB The Switch Core Board (SCB) contains an ATM switch and interfaces to the ATM switch ports located on other boards via the backplane. The SCB also has a connector and filter for the system power. The system power is distributed within the subrack via the backplane. RAXB The Random Access/Receiver Board (RAXB) comprises the baseband receiver part, which takes care of decoding, searching and rake receiving for dedicated and random access transport channels, and cell combining for softer handover. E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 8 ( 20 ) With an optional RAXB it is possible to share the load to achieve high availability. If one RAXBs fails, the load is moved to the remaining RAXB. GPB The General Processor Board (GPB) operates as an MP and contains and executes the main part of the RBS software. It controls devices on boards and in auxiliary units. The GPB has flash disk storage, an Ethernet connection and an RS232 interface. TXB The Transmitter Board (TXB) comprises the baseband transmitter part for handling transport channels, encoding, cell splitting, modulating and spreading, and channel combining. TUB The Timing Unit Board (TUB) generates and distributes local timing signals. BBIFB The Baseband Interface Board (BBIFB) connects the baseband part of the BB/RF subrack to the RF part of the BB/RF subrack. The connection carries the downlink and uplink traffic streams, and timing signals. 4.1.2 Radio Frequency Boards AIU The Antenna Interface Unit (AIU) consists of a filter and control unit, and a combiner and splitter unit. The filter and control unit provides the following:
Duplex filtering of the transmitter and receiver signal Low-noise amplification of the receiver signal Power measurement of the transmitter signal Flexible frequency and signal splitting RFIFB The Radio Frequency Interface Board (RFIFB) connects the RF part of the BB/RF subrack to the baseband part of the BB/RF subrack. The connection carries the downlink and uplink traffic, and timing signals. The RFIFB also performs power clipping for downlink traffic. TRXB The Transceiver Board (TRXB) provides channel filtering, delay and gain adjustment, A/D and D/A conversion, and RF modulating and demodulating. A TRXB comprises two independent transceivers for two transmitter and receiver signal pairs. E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 9 ( 20 ) 4.2 MCPA The MCPA is a 20 W RF power amplifier with a bandwidth of 20 MHz. The MCPA can simultaneously amplify, in RBS 3104, up to two RF carriers, by dividing the power over the carriers. The MCPA subrack is connected to the RF subrack through front panel cabling. 4.3 XALM The XALM handles the customer specific alarms as well as alarms for Ericsson equipment, such as door alarm. 4.4 Capacitor Unit The Capacitor Unit (CU) receives the -48 V DC supply, which powers the RBS. The CU ensures that the RBS remains in operation during short transient drop of power. The CU smooths out irregularities in the supplied power, and the unit is subdivided into three electrically separated sections. 4.5 Climate System The climate system comprises the Climate Unit (CLU) in the cabinet door, a Fan Unit in the cabinet, and a Heater in the cabinet. The CLU comprises the two External Fans, a Heat Exchanger (H/E) and an Active Cooler (A/C). At low ambient temperatures, only the H/E operates to cool the cabinet. The Heater is used during start up at low ambient temperatures to ensure that the temperature inside the cabinet rises above a certain level. The Heater and A/C are interlocked to prevent them from operating at the same time. At high ambient temperatures, the A/C contributes to maintain sufficiently low cabinet temperatures. The H/E and A/C co-operate to ensure that long time average power consumption is minimized. Climate Unit The Climate Unit (CLU) is a cooling device that includes a Heat Exchanger, an Active Cooler, a compressor control unit, and the External Fans. The speed of the External Fans is temperature controlled. The H/E consists of a counter-flow H/E with external air circuit fans. The A/C consists of compressor, reducing valve, condenser and evaporator. Heater The Heater is DC supplied and is controlled by a thermostat to avoid overheating. E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 10 ( 20 ) Fan Unit The Fan Unit contains the Internal Fans and the Climate System Control Unit. The Fan Unit is accessible from the front of the cabinet. The speed of the Internal Fans is temperature-controlled. 4.6 Internal Cables This section gives a brief description of the internal RBS cables. Gamma Cable The gamma cables connect the BBIFB and RFIFB. The BBIFB and RFIFB can connect two gamma cables, one for each antenna branch. It carries serial traffic streams from the gamma interface. Timing Cable The timing cable is a connection between the BBIFB and RFIFB. This cable connection distributes timing signals from the BB part of the subrack to the RF part of the subrack, and reads RFIFB product information. Inter-Subrack Timing Cable The inter-subrack timing cable distributes timing signals from the TUB to the RF part. The cable is connected between the BBIFB and the RFIFB. Internal Jumper Cable The internal jumper cables connect the AIU to the RF connectors at the bottom of the RBS cabinet. As the AIU can handle two antenna branches, two cables are connected to the AIU. These cables carry the transmit RF and receive RF signals. For Antenna Near Products, the AIU can feed power through both cable connections. One of the antenna connectors also has the capability to carry the auxiliary unit interface, which supervises and controls units. MCPA Control Cable The MCPA control cable is the auxiliary unit control connection for the MCPA. The cable is connected between the RFIFB and MCPA. Low-Power Multi-Carrier TX Cable The low-power multi-carrier Transmitter (TX) cable carries the low power RF signal after carrier combination and signal splitting (if applicable) from the AIU to the MCPA. High-Power TX Cable The high-power Transmitter (TX) cable carries the RF signal from the MCPA to the AIU after power amplification. Transmission Cable The transmission cable connects the ETB to the Connection Field at the bottom of the RBS cabinet. E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 11 ( 20 ) Site LAN Connection Cable The Site LAN connection cable connects the GPB to the Site LAN panel in the connection field. XALM Interface Cable The XALM interface cable connects the SCB to the XALM. Low-Power Single Carrier TX Cable The low-power single carrier TX cable connects the TX output of the TRXB to the AIU. Fan Unit Cable The fan unit cable connects the Fan Unit to the Climate Unit and is used for power feeding, control of the fans and supervision. 4.7 Connections to the RBS This section gives a brief description of the connections to the RBS. Site LAN Connection The Site LAN connection is an Ethernet based interface for connecting the thin client used for O&M or for connection to site equipment.
- 48 V DC Connection
-48 V DC is connected to two terminal blocks on the Power Distribution Unit. External Alarms Four external alarms can be connected to the alarm panel. Transmission Lines The fibre optic transmission is connected directly to the ETB1 board. The twisted pair cable transmission is connected to an optional OVP module in the connection field. RF Connectors RF connectors are located at the bottom of the cabinet, on the left hand side. 5 5.1 Node Architecture Architectural Overview The functionality is subdivided into two parts that operate on the infrastructure and a common platform The two parts are:
Control plane functionality, featuring traffic control and O&M, and E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 12 ( 20 ) User plane functionality, featuring transport, baseband, radio and antenna near parts functionality. figure 3 shows the general RBS software architecture. Control Plane Traffic Control O&M Infrastructure and Platform Transport Baseband Radio Antenna Near Parts User Plane B 00 00 617 Figure 3 Architectural Overview 5.2 Layered Views There are three important views of an RBS node, each showing a specific aspect and containing several layers:
Platform View, seepage12 Traffic control view, seepage13 Management view, seepage13 Platform View The platform view consists of two layers:
The common platform layer isolates the application program layer from the implementation details of the processor and ATM platform. This makes it possible to change the processor and ATM parts without having to modify the application program. A standard web browser is used for RBS management through the element manager. The platform layer supports the Element Manager (EM) by providing common platform support functions such as a graphical interface, Java applet communication and online context sensitive help. E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 13 ( 20 ) The application program layer is the software executing on top of the common platform. So, from the platform point of view, there is no specific structure for the application program. Traffic Control View This view hides the specific RBS hardware from the actual services supplied by the RBS. This is done to encapsulate the parts of the system that change when hardware is modified. Modification normally takes place when an RBS is updated (for example, capacity increase) or when different types of RBSs are supported. There are four layers in the traffic control view:
Traffic service layer that carries out the application program procedures using logical resources, for example, channels. Logical resource layer that provides logical resources for the traffic service layer. It transforms operations on logical resources into operations on devices. Equipment layer that makes functionality hardware independent by providing devices to logical resource layer. Hardware layer that hides the hardware details. Management View The management view covers the application program and the common platform. It hides implementation details from the user interface. There are three layers in the management view:
The presentation layer holds the GUI, which consists of, for example, HTML pages and Java applets. They include, for example, workflow-oriented forms for system configuration and support for reading and presenting an event log. The presentation layer is implemented using web pages and applets, which can be viewed using a standard web browser. The management adaptation layer represents objects visible through the Mub management interface. These objects contain attributes, that can be read or written, and methods for operations on these objects through the standard web browser. The resource layer hides the lower level implementation details of the objects, which reduces the impact of changes. Fault detection functions in the resource layer, and also in the common platform, ensure fault and error detection. The hardware layer within the resource layer provides fault and error detection support on a low level. However, it has no direct interface to the management adaptation layer. The management adaptation layer and the common platform generate the corresponding alarms. Events can have their origin in any part of the system, but the management adaptation layer and the common platform generate the event reports. E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked 6 Functions Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 14 ( 20 ) The RBS functions can be subdivided into RBS application functions and common platform functions. RBS application functions use common platform functions to realize their tasks. An overview of the main RBS application function groups and their interfaces is given in figure 4. The interfaces are described in page 16. Iub/NBAP Mub Iub/NBAP Iub/FP+AAL0 t n e m e g a n a M n o i t a r u g i f n o C t n e m e g a n a M e c n a m r o f r e P n o i t i a z n o r h c n y S Traffic Control r e r a e B t r o p s n a r T i o d a R t n e m e g a n a M t l u a F Application Specific Functions Platform Functions Mub Iub/
FP Uu B 00 00274 Figure 4 Main RBS Application Function Groups Measurement functionality is subdivided into a detector part (normally in radio transport functions) and a control part, that controls the measurement. Measurement functions have different roles in the measurement functionality. The O&M for traffic control functions is included within the function itself. Security aspects are handled within each function that interfaces with the Mub. Security support is provided by the platform functions. Functions that have an interface for management only cover functionality towards an Mub user. The Mub user can be either an element management node or RANOS. 6.1 Application Functions The application functions of the RBS are subdivided into function groups each covering some specific RBS functionality. See table 2 for RBS function groups. E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 15 ( 20 ) Table 2 RBS Function Groups Function group Task Fault Management Configuration Management Performance Management Traffic Control Radio Transport Bearer Synchronization Infrastructure GUI Fault management functions detect, isolate, and recover from faults in supervised functions. Faults are reported through alarms, that also are logged and maintained in an active alarm list. Alarm handling is performed through the Mub interface. Supervision functions are always active and do not have to be configured. Configuration management functions create and delete RBS Managed Objects (MO). Attributes of these MOs can be set and read. These functions are performed over the Mub interface. Some functionality also exists that uses the Iub interface. Performance management functions collect, store and report statistics regarding RBS measurements. These functions are performed through the Mub interface. Traffic control functions provide control of traffic-related resources such as common and dedicated radio connections, cells and ATM connections. The functions also provide control of measurement requested from the RNC. Traffic control is performed through the Iub interface and is managed over the Mub interface. Radio transport functions manage user data processing in the baseband and RF parts of the RBS node. It handles the air interface Uu. Measurement detector functionality is also included. Bearer functions transfer user or control data between the RNC and the RBS. The data is carried over the Iub interface. Synchronization functions provide correct data timing, and prevent data loss due to slip of sent and received information through the system. The functions also provide stable frequency references for RF stabilization. Synchronization functions are managed through the Mub interface. Synchronization frames are carried over the Iub interface to and from RNC. Infrastructure functions handle power feeding, environmental control and basic infrastructure software functionality. These functions are managed through the Mub interface. This function group contains the GUI functionality. The user interface handles the GUI. E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 16 ( 20 ) 6.2 Platform Functions The Platform contains all the functionality necessary to switch ATM cells and variable length cells (that is, ATM Adaptation Layer type 2 (AAL2) Common Part Sublayer (CPS) packets) within an ATM-based telecommunications network. It also includes CCITT Signalling System number 7 (SS7) support (Signalling Connection Control Protocol (SCCP) Message Transfer Part layer 3 broadband
(MTP3b) as well as functionality for network signalling using Q.2630.1 for AAL2 connections. 7 External Interfaces Communication to and from the RBS is made through the Iub, Uu and Mub interfaces. Besides these interfaces the RBS also provides a management GUI that uses the Mub, and a Visual and Mechanical Interface (VMI), which comprises indicators, switches, buttons, cables, and so on. An overview of the external interfaces is given in figure 5. Descriptions of the interfaces are given below. RNC Iub Mub RBS Uu UE Figure 5 External Interfaces GUI VMI B 00 00559 E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 17 ( 20 ) 7.1 lub Interface The Iub interface is the interface between the RBS and the RNC. The Iub is subdivided into several protocol layers as follows:
Physical layer (L1) ATM and ATM adaptation layers (L2) Network layer (L3) for frame handling The L3 protocol for the RNC plane is called NBAP. The L2 and L3 part of air interface channels RACH, FACH, PCH and DCH terminate in the RNC. From an RBS perspective, the different air interface channels are all treated as transparent user plane channels. 7.2 Uu Interface The Uu interface is the radio interface between RBS and the UE. The radio interface is subdivided into three protocol layers as follows:
Physical layer (L1) Data link layer (L2) Network layer (L3) The L2 comprises of Medium Access (MAC) and Radio Link Control (RLC). The MAC provides unacknowledged transfer of SDUs between peer MAC entities, and the RLC provides data transfer of SDU and can also support the retransmission protocol. L3 comprises the Radio Resource Control (RRC), which interfaces with L2 7.3 Mub Interface The Mub is the management interface for the RBS and, in contrast to the Iub, is not standardized. The interaction between the system and a user is realized by means of a thin client. The thin client is a computer with basic software, such as a web browser, installed . The thin client gets software that is dependent on the managed node by loading Java applets from the node at execution time. The Mub is based on IP, so the RBS has an IP address. Remote management uses IP over ATM and on-site management uses Ethernet. The necessary low-level communication layers including FTP server, HTTP server, ORB and Telnet server are provided by the common platform. The management interfaces are shown in figure 6. E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 18 ( 20 ) RBS Element Manager/RANOS IM File system HTML docs. Java class file Terminal Browser Thin Client
"File Mgr"
"Cmd-
shell"
Telnet IIOP HTTP FTP Telnet IIOP HTTP FTP m r o f t l a P TCP IP TCP IP ATM/Ethernet ATM/Ethernet B 00 00557 Figure 6 Management Interfaces Telnet IIOP HTTP FTP Telnet provides local and remote access to the operating system shell in the RBS. The command line interface provides a set of commands handled by a Unix shell-like command interpreter. IIOP (IP based Inter-ORB Protocol) is the protocol used in Common Object Request Broker Architecture (CORBA). It is the main protocol used for RBS O&M. The element manager and the network manager (RANOS) use the protocol. HTTP transfers HTML documents such as online documentation and Java applets from the file system in the RBS node to a managing system. FTP transfers files to and from the file system in the RBS. This is primarily used for loading software, configuration data and other large volume data. 7.4 GUI The Graphical User Interface (GUI) is the man-machine interface provided to the user. GUI applications are web based (HTML and Java applets) and run in a standard web browser. Two general types exist:
Workflow oriented wizards, for example for node expansion and initial configurations. Panels used for example to set preferences. E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 19 ( 20 ) 7.5 Visual and Mechanical Interface The visual and mechanical interface consists of:
Optical indicators Switches and buttons Incoming external power External alarms/outputs Connectors, cables and screws 8 Operation & Maintenance This section describes different tasks included in O&M of the RBS. 8.1 Standard Operation The RBS is configured to suit the requirements of the operator. Configuration Operating Instructions give information regarding different configurations. The RBS is monitored by means of the RBS Element Manager (EM). The EM is accessed by connecting a thin client to the Site LAN connection plate. Instructions on how to configure and connect a thin client to the RBS is found in PRODUCTHANDLING. For a detailed description of the EM, please refer to ELEMENTMANAGER. The following are tasks performed via the EM:
RBS EM topology view handling Configuration management Software management Alarm management Restart Timing Unit (TU) switching Object properties handling Locking and unlocking of objects Online help E Prepared (also subject responsible if other) EAB/RWB/ZG Christina Wilson Approved EAB/RWB/Z (Dennis Radenholt) Checked Open Information DESCRIPTION No 18/1551HRB 105 102/1 Uen Date 2003-06-16 Rev B Reference 20 ( 20 ) 8.2 Alarms The RBS alarms are collected in an alarm list. From this list it is possible to:
Display alarm details Acknowledge alarms Add comments to alarms 8.2.1 External Alarms The RBS provides external alarm input ports to be used for both Ericsson and customer specific use. The Ericsson external alarms have a predefined alarm definition while the alarm definition for the customer external alarms can be specified by a command. It is possible to configure whether an alarm is generated by closed or open loop condition. There are four predefined external alarms in RBS 3104. Door Open Active Cooler Fault External Fan Fault Internal Fan Fault
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2004-03-09 | 1932.5 ~ 1967.5 | PCB - PCS Licensed Transmitter | Class II permissive change or modification of presently authorized equipment |
2 | 2004-03-04 | 1932.5 ~ 1967.5 | PCB - PCS Licensed Transmitter | |
3 | 2003-12-29 | 1932.5 ~ 1967.5 | PCB - PCS Licensed Transmitter | Original Equipment |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 2 3 | Effective |
2004-03-09
|
||||
1 2 3 |
2004-03-04
|
|||||
1 2 3 |
2003-12-29
|
|||||
1 2 3 | Applicant's complete, legal business name |
Ericsson Radio Systems AB
|
||||
1 2 3 | FCC Registration Number (FRN) |
0005940275
|
||||
1 2 3 | Physical Address |
Torshamnsgatan 21-23
|
||||
1 2 3 |
S-164 80 Stockholm, N/A
|
|||||
1 2 3 |
Sweden
|
|||||
app s | TCB Information | |||||
1 2 3 | TCB Application Email Address |
t******@sp.se
|
||||
1 2 3 | TCB Scope |
B1: Commercial mobile radio services equipment in the following 47 CFR Parts 20, 22 (cellular), 24,25 (below 3 GHz) & 27
|
||||
app s | FCC ID | |||||
1 2 3 | Grantee Code |
B5K
|
||||
1 2 3 | Equipment Product Code |
AROJ1192233-1
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 2 3 | Name |
B****** B****
|
||||
1 2 3 | Title |
Manager
|
||||
1 2 3 | Telephone Number |
+468 ********
|
||||
1 2 3 | Fax Number |
+468 ********
|
||||
app s | Technical Contact | |||||
1 2 3 | Firm Name |
Ericsson AB
|
||||
1 2 3 | Name |
L**** L******
|
||||
1 2 3 | Physical Address |
Torshamnsgatan 21-23
|
||||
1 2 3 |
Stockholm, 16480
|
|||||
1 2 3 |
Stockholm, 164 80
|
|||||
1 2 3 |
SE-164 80 Stockholm, 999999999
|
|||||
1 2 3 |
Sweden
|
|||||
1 2 3 | Telephone Number |
+46 8********
|
||||
1 2 3 | Fax Number |
+46 8********
|
||||
1 2 3 |
l******@era.ericsson.se
|
|||||
app s | Non Technical Contact | |||||
n/a | ||||||
app s | Confidentiality (long or short term) | |||||
1 2 3 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
1 2 3 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
1 2 3 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 2 3 | Equipment Class | PCB - PCS Licensed Transmitter | ||||
1 2 3 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | WCDMA Base station transceiver | ||||
1 2 3 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 2 3 | Modular Equipment Type | Does not apply | ||||
1 2 3 | Purpose / Application is for | Class II permissive change or modification of presently authorized equipment | ||||
1 2 3 | Original Equipment | |||||
1 2 3 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | No | ||||
1 2 3 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
1 2 3 | Grant Comments | The power listed is conducted. This transmitter must only be operated in the grantees RBS3202 base station, RBS 3101 base station and RBS3104 base station. The antenna(s) used for this transmitter must be fixed-mounted on outdoor permanent structures. RF exposure compliance is adressed at the time of licensing, as required by the responsible FCC Bureau(s), including antenna co-location requirements of 1.1307(b)(3). | ||||
1 2 3 | The power listed is conducted. This transmitter must only be operated in the grantees RBS3202 base station and RBS3101 base station. The antenna(s) used for this transmitter must be fixed-mounted on outdoor permanent structures. RF exposure compliance is adressed at the time of licensing, as required by the responsible FCC Bureau(s), including antenna co-location requirements of 1.1307(b)(3). | |||||
1 2 3 | The power listed is conducted.This transmitter must only be operated in the grantees RBS 3202 Base station. The antenna(s) used for this transmitter must be fixed-mounted on outdoor permanent structures. RF exposure compliance is adressed at the time of licensing, as required by the responsible FCC Bureau(s), including antenna co-location requirements of 1.1307(b)(3) | |||||
1 2 3 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 2 3 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
app s | Test Firm Name and Contact Information | |||||
1 2 3 | Firm Name |
SP Technical Research Institute of Sweden
|
||||
1 2 3 | Name |
M**** W****
|
||||
1 2 3 | Telephone Number |
46-10********
|
||||
1 2 3 | Fax Number |
46-33********
|
||||
1 2 3 |
m******@sp.se
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 24E | 1932.50000000 | 1967.50000000 | 0.0060000 | 0.0500000000 ppm | 4M20F9W | ||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
2 | 1 | 24E | 1932.50000000 | 1967.50000000 | 0.0060000 | 0.0500000000 ppm | 4M20F9W | ||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
3 | 1 | 24E | 1932.50000000 | 1967.50000000 | 0.0060000 | 0.0500000000 ppm | 4M20F9W |
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC