Page 2 Upon completion of this course, you will be able to: Master data configuration procedure with CME Master procedure of NodeB data configuration Page 3 Chapter 1 Data Configuration Overview Chapter 2 Configuring Physical Equipment Chapter 3 Configuring Transport Chapter 4 Configuring Local Cell Chapter 5 Configuring Operation and Maintenance Channel Page 4 Data Configuration Overview Configuration Tool CME Page 5 CME for Initial Configuration in Network Commissioning RAN Initial Data Configuration Configuring data based on the RAN network planning Exporting configuration data files Loading the files to the RNC and NodeB through LMTs CME Wizards of the task focused Planned Radio data Cell Radio Parameter templates NodeB Templates Script is downloaded and activated RAN RNS RNC NodeB RNS RNC NodeB Page 6 CME for Data Modification in Network Expansion CME Wizards of the task focused Planned Radio data Cell Radio Parameter templates NodeB Templates Script is downloaded and activated Upload RAN RNS RNC NodeB RNS RNC NodeB RAN Data Modification Adding/deleting/modifying a RNC WRBS Adding/deleting/modifying a NodeB Adding/deleting/modifying a cell Modifying algorithm setting for RNO Page 7 Data Configuration Overview Procedure of NodeB Data Configuration Configuring NodeB Data Configuring Physical Equipment Configuring Transport Configuring Local cell Physical equipment must be configured first Page 8 Chapter 1 Data Configuration Overview Chapter 2 Configuring Physical Equipment Chapter 3 Configuring Transport Chapter 4 Configuring Local Cell Chapter 5 Configuring Operation and Maintenance Channel Page 9 Physical Equipment Configuration Add NMPT Add NAOI/NDTI Add UL BB Resource Group Add HBBI Add NMON NEMU/GPS Add NPMU Add NCMU Add NPSU Add Battery Create NodeB Add MRRU Chain/Ring Add HBBU Add NPMU for MBBU Add NPMU For MRRU Add MRRU USED FOR 3812E&A USED FOR DBS3800 Add HBOI Add HULP/HDLP A Add MTRU/MAFU A End Procedure of Physical Equipment Configuration Configuring Physical Equipment Page 10 Configuring Physical Equipment Creating NodeB Adding NodeB basic data The basic data includes NodeB name and some basic NodeB data such as clock reference source, transmission line type, IP address, time zone, and demodulation mode Note A NodeB name must be unique in one RNS Page 11 Configuring Physical EquipmentBTS3812E/A Adding Boards to Baseband Subrack Adding boards to the baseband subrack The board can be NMPT,NMON,HBBI,HBOI,HULP,HDLP,NDTI or NAOI board Note You must configure NMPT first, and configure HBBI before configuring MTRU and MAFU. NMPT, HBBI/HBOI and NDTI/NAOI (alternative) are mandatory N C C U 1 2 3 4 5 0 6 7 8 9 10 11 12 13 14 15 16 17
N M O N N A O I N D T I H B B I H B B I H U L P H U L P H U L P H U L P H U L P H U L P H D L P H D L P N M P T N M P T N U T I Page 12 Configuring Physical Equipment BTS3812E/A Adding Boards to RF Subrack Adding boards to the RF subrack. The board can be MTRU or MAFU board Note MTRU and MAFU have a one-to-one relationship You must add HBBI first before you are adding MTRU and MAFU MAFU0 MAFU1 MAFU2 MAFU3 MAFU4 MAFU5
MTRU0 MTRU1 MTRU2 MTRU3 MTRU4 MTRU5 Page 13 Configuring Physical Equipment BTS3812E/A Adding UL Baseband Resource Group Adding a UL baseband resource group and UL process units Note Each UL baseband resource group administrates up to six cells Cells in the same frequency band shall be assigned in the same UL baseband resource group N C C U 1 2 3 4 5 0 6 7 8 9 10 11 12 13 14 15 16 17
N M O N N A O I N D T I H B B I H B B I H U L P H U L P H U L P H U L P H U L P H U L P H D L P H D L P N M P T N M P T N U T I Page 14 Configuring Physical Equipment BTS3812E/A Adding NPMU (only for BTS3812A) Adding an NPMU and its PSU and batteries Adding NCMU (only for BTS3812A) The NCMU is the temperature control unit of the BTS3812A. Configuring NEMU (only for BTS3812E) The NEMU is a peripheral of the NodeB Page 15 Configuring Physical Equipment ----DBS3800 Adding HBBU Adding an HBBU Note You can add only one HBBU to a NodeB Page 16 Configuring Physical Equipment DBS3800 Adding MRRU Chain/Ring Adding an MRRU chain or ring Note The MRRU chain or ring is configured to the HBBU/HBOI CPRI ports Each HBBU/HBOI has three CPRI ports The MRRU chain occupies one CPRI port, and the MRRU ring occupies two CPRI ports Adding MRRU Note For the data configuration of a distributed NodeB, each MRRU is considered as a subrack. The subrack number of an MRRU must be unique within the distributed NodeB system Chain Ring Star Page 17 Chapter 1 Data Configuration Overview Chapter 2 Configuring Physical Equipment Chapter 3 Configuring Transport Chapter 4 Configuring Local Cell Chapter 5 Configuring Operation and Maintenance Channel Page 18 Chapter 3 Configuring Transport Sector 1 Configuring Transport over ATM Sector 2 Configuring Transport over IP
Page 19 Configuring Transport over ATM I ub I nterface protocol over ATM Control Plane Transport Network Control Plane User plane Radio Network Layer Transport Network User Plane Transport Network Layer Transport Network User Plane NCP CCP A B C CCP NBAP SAAL UNI AAL2 PATH Physical Layer ALCAP SAAL UNI R A C H
F P
F A C H
F P
ATM Page 20 Physical Layer VPI-10 VPI-20 VCI-100 VCI-101 VCI-100 VCI-101 ATM Cell segmentation packing Iub data CBR E1/T1/SDH(STM-1) ATM Layer AAL Layer VBR-NRT AAL5 AAL1 AAL2 VBR-RT VPI-10 CES AAL2 PATH NCP or CCP or ALCAP or IPoA IMA/UNI/STM-1 AAL2Path RNC NodeB NCP CCP 1~n RNC Control Plane ALCAP NodeB User Plane Adjnode I ub I nterface protocol Configuring Transport over ATM Page 21 Transport Configuration Create NodeB Add NAOI Add Fractional ATM Add UNI LINK Add IMA Group Add NDTI/HBBU Add IMA Link Add Treelink PVC Add NCP/CCP/ IPoA Device Add ALCAP Add CES (only3812E&A) Add AAL2 Path Add Time Slot Across Add STM-1 Link End Configuring Transport over ATM Procedure of Transport Configuration Page 22 Configuring Transport over ATM Configuring Physical Links at Transport Layer Adding the physical links to the NodeB for data transmission over Iub interface Note An E1/T1 port can be configured to any of the following links for data transmission: UNI link Fractional ATM link IMA link CES link An optical port can be configured to any of the following links for data transmission: STM-1 link Page 23 Board type Port number Work mode NDTI E1/T1 port No.0 IMA,UNI, CES, Fractional ATM, Timeslot cross (connect with RNC) E1/T1 port No.1 IMA,UNI, CES, Fractional ATM E1/T1 port No.2~3 IMA, UNI, Timeslot cross (connect with lower level NodeB) E1/T1 port No.4~7 IMA,UNI NAOI E1/T1 port No.0~3 CES Optical port No.0~1 STM-1 Configuring Transport over ATM Physical Links Configuration Physical ports(BTS3812E&A) Page 24 Configuring Transport over ATM Physical Links Configuration Physical ports(DBS3800) Board type Port number Work mode HBBU E1/T1 port No.0 IMA,UNI, Fractional ATM, Timeslot cross (connect with RNC) E1/T1 port No.1 IMA,UNI, Fractional ATM E1/T1 port No.2~3 IMA, UNI, Timeslot cross (connect with lower level NodeB) E1/T1 port No.4~7 IMA,UNI Page 25 Configuring Transport over ATM Physical Links Configuration Add an UNI link Header 256 bits/125 ls ATM cell mapping field: 30 octets (TS1 - TS15 and TS17 - TS31) TS0 provides F3 OAM functions: Performance monitoring (CRC-4) Transmission of FERF and LOC Performance reporting Detection of loss of frame alignment Header Header Header TS16: Reserved for signaling ATM cell 53 octets Header Page 26 Configuring Transport over ATM Physical Links Configuration Add an IMA Group PHY PHY PHY PHY PHY PHY ATM Original ATM cell stream from ATM layer IMA group
Physical I ink #0 IMA group Recovered ATM cell stream to ATM layer Physical I ink #1 Physical I ink #2 IMA virtual link Page 27 Configuring Transport over ATM Physical Links Configuration Adding a Fractional ATM Link Bearing port No. : defines the E1/T1 No. on the NDTI BTS38XX NDTI RNC Iub interface board NDTI E1 0/1 Fractional ATM link ATM cell carrying 3G data Fractional E1 slots available for ATM cell, others may be used by 2G BTS Transport other information rather than ATM cell Page 28 Configuring Transport over ATM Adding NCP Adding the NCP to the Iub interface Note Only one NCP is configured to the NodeB Negotiated with the peer end RNC VPI and VCI of NCP Traffic over the NCP includes: Service type, Peak cell rate , Sustain cell rate Page 29 Configuring Transport over ATM Adding CCP Adding a CCP to the Iub interface Note One NodeB supports multiple CCPs Negotiated with the peer end RNC CCP No. VPI and VCI of CCP Traffic over the CCP includes: Service type, Peak cell rate , Sustain cell rate Page 30 Configuring Transport over ATM Adding ALCAP Node and link Adding the ALCAP node to the NodeB and an ALCAP link to the Iub interface Note One NodeB is configured with only one ALCAP link Negotiated with the peer end RNC ATM address of NodeB VPI and VCI of the ALCAP link Traffic over the ALCAP link includes :Service type, Peak cell rate , Sustain cell rate Page 31 Configuring Transport over ATM Adding AAL2 Path Adding an AAL2 path to the Iub interface Note One NodeB may have multiple AAL2 paths The number of paths can be calculated based on the traffic model over the Iub interface Negotiated with the peer end RNC AAL2 path ID VPI and VCI of the AAL2 path Traffic over the AAL2 path includes :Service type, Peak cell rate , Sustain cell rate Page 32 Configuring Transport over ATM Adding Treelink PVC Adding a Treelink PVC to the lower level NodeB The Treelink PVC enables the NodeB to connect with its upper level node and lower level NodeB through different E1/T1 ports Note Optional for NodeB initial configuration Add Treelink PVCs to all the upper level NodeBs when the NodeB is cascaded with the other NodeBs Negotiated with the lower level NodeB PVC to lower level NodeB Negotiated with the upper level NodeB PVC to upper level NodeB Page 33 Chapter 3 Configuring Transport Sector 1 Configuring Transport over ATM Sector 2 Configuring Transport over IP
Page 34 Configuring Transport over IP I ub interface protocol over I P Control Plane User Plane Radio Network Layer Transport Network Layer
Transport Network User Plane NCP CCP A C CCP NBAP Data Link Layer Physical Layer Data Link Layer R A C H
F P
F A C H
F P
IP UDP IP SCTP U S C H
F P
C P C H
F P
Transport Network User Plane Page 35 Configuring Transport over IP Configure the IP Route Configure the MP Configure the PPP Configure the PPPoE Configure the Ethernet IP NodeB Configure the QoS (optional) IP Route Configure the NBAP IP Route Configure the OM Configure the IP path Start End Page 36 Configuring Transport over IP Configure the PPP, MP, PPPoE, and Ethernet IP In a single transport mode, configure one type of transport links. In hybrid transport mode, configure E1 and FE transport links. For E1 links, configure PPP or MP. For FE links, configure PPPoE or Ethernet IP. IP network NodeB RNC PDH/SDH IP hybrid transmission Page 37 Configuring Transport over IP Configure the IP route If the gateway type of the route is Ethernet, the next hop address and the gateway IP address must be in the same network segment If the NodeB and RNC are in layer 2 networking The IP addresses of the FE ports on the NodeB and RNC should be in the same subnet If the NodeB and RNC are in layer 3 networking The next hop address is the IP address of the router that connects to the NodeB or the IP address of the port on a layer 3 switch. The destination address of packets has the corresponding route in the routing table. The corresponding link layer address can be found only when the router specifies the next hop IP address (gateway). Configure just one route to the same destination address. Page 38 Configuring Transport over IP Configure the QoS To configure signaling and OM priorities IP Quality of Service (QoS) is an IP network capability to provide specific services over the IP network that uses mutiple bottom-layer network technologies such as MP, FR, ATM, Ethernet, SDH, and MPLS IP QoS supports the switching between the IP precedence and DSCP The IP QoS configuration is flexible Page 39 Configuring Transport over IP Configure the NBAP Configure destination IP address & local IP interface, port type and port number The IP routes for destination addresses are available Only one NCP can be configured Several CCPs can be configured The destination IP address, local port number, and destination port number of the NCP/CCP on the same link should be different When you choose one NCP/CCP on the NBAP tab page, the corresponding links are displayed in the middle part, and the corresponding routes are displayed in the lower part
Page 40 Configuring Transport Based on IP Configure the OM Ensure that the route from the LMT (or M2000) to the subnet is configured Only one OM channel can be configured If you choose an OM channel in the upper part of the OM tab page, the corresponding route is displayed in the lower part The destination IP address of the OM channel is the IP address of the NodeB LMT or M2000 Page 41 Configuring Transport over IP Configure the IP path The IP routes for destination addresses are available The IP path does not have bandwidth limit. Therefore, to configure the IP path is to differentiate service priorities. When the HSDPA service is transmitted, configure two IP paths with different path IDs. The two paths correspond to R99 service and HSDPA service. There is no service priority at the NodeB side. Therefore, configure one IP path at the NodeB side If you choose one path on the upper part of the IP path tab page, the corresponding links are displayed in the middle part and the corresponding route is displayed in the lower part
Page 42 Chapter 1 Data Configuration Overview Chapter 2 Configuring Physical Equiment Chapter 3 Configuring Transport Chapter 4 Configuring Local Cell Chapter 5 Configuring Operation and Maintenance Channel Page 43 Configuring Local Cell Procedure of Local Cell Configuration Add Site Add Sector Add Local Cell Locall cell Page 44 Configurando una celda Local Adding Site Adding a site to the NodeB Note A site number within one NodeB must be unique.
Adding Sector Adding a sector to the NodeB Note A sector number must be unique within one NodeB Configuring a sector is mainly configuring the corresponding antenna and feeder system Page 45 Configuring Local Cell Adding Local Cell Adding a local cell to the NodeB Note Local Cell ID must be unique within the same NodeB Negotiated with the peer end RNC Local Cell ID Uplink Frequency Downlink Frequency Page 46 Chapter 1 Data Configuration Overview Chapter 2 Configuring Physical Equiment Chapter 3 Configuring Transport Chapter 4 Configuring Local Cell Chapter 5 Configuring Operation and Maintenance Channel Page 47 Configuring Operation and Maintenance Channel NodeB provides two modes of operation and maintenance: Near end operation and maintenance: Far end operation and maintenance: RNC SNTP Server M2000 Subnet 2 Subnet 3 IPoA local IP IPoA Peer IP RNC BAM IP Subnet 5 Subnet 4 LMT 2 LMT1 Subnet 1 BTS3812E NMPT Ethernet Port IP address Page 48 Configuring Operation and Maintenance Channel Adding IPoA Device Configuring an IPoA maintenance channel to the NodeB Through the IPoA maintenance channel, you may log in to the NodeB remotely with the LMT or the M2000 Note You can add only one IPoA maintenance channel to a NodeB Negotiated with the peer end RNC Local IP and Local IP Mask Peer IP and Peer IP Mask VPI/VCI Service Type