RL40
RA41126EN05GLA0
RA41126EN05GLA0
Objectives
After this training module, the participant will be able to
-list the generic steps when manually commissioning a LTE Flexi Multiradio BTS -recognize the different types of Flexi Transport sub-modules by name and functions -describe installation options for LTE Flexi Multiradio BTS -list the hardware and software requirements for the LTE Flexi Multiradio BTS Element Manager for
Local/Remote usage -demonstrate configuration of the personal computer used for commissioning -describe configuration of hardware settings, transmission interfaces and synchronization settings -describe the overview of Remote Management operation/administration of the LTE Flexi Multiradio BTS -inspect and check BTS Interface terminations -inspect and check IP and DCN settings for Remote Access and Management -describe and Check all integration relevant parameters in the eNodeB commissioning file -demonstrate inspection, checking and testing of the LTE Flexi Multiradio BTS commissioned configuration and status using the LTE Flexi Multiradio BTS Element Manager
RA41126EN05GLA0
Contents
BTS Site Manager Installation Manual BTS software update
Manual Commissioning
Integration
RA41126EN05GLA0
Start
Power On
SW Update Commissioning File? Complete Template Template Enter site-specific parameters Site reset None Manual
Autoconfiguration Enabled
Yes SW Update
Remote Connect No
Planned
Commissioning file download from iOMS Site reset Commisisoning tests (optional)
Commissioning Report
Done
5 Nokia Siemens Networks RA41126EN05GLA0
Normally we recommend to keep the older versions when installing a new BTS Site Manager. The more BTS Site Manager versions are installed the less likely is an incompatibility issue with BTSs running on various SW levels.
RA41126EN05GLA0
Remote connections: Connect to eNB transport interface via DCN. PC will need an IP address on the DCN network.
PC IP settings will be based on DCN, which will be routable to Flexi BTS OAM transport interface PC Setting for Local Connection
RA41126EN05GLA0
If connecting remotely, enter Management Plane IP address of the BTS. Remote connection to an un-commissioned BTS will not be available, because no MP IP address has been configured yet.
RA41126EN05GLA0
If there is no any signed certificate installed on the BTS it is required during the Authentication phase to accept self-signed BTS certificate.
RA41126EN05GLA0
Filter controller SW of Radio Module, (AISG) MHA SW and Tilt Adjuster SW.
10
RA41126EN05GLA0
SW update takes approximately 15...35 minutes, depending on number of files updated. If the box Activate SW after update remains unchecked, then the new SW will be downloaded to the second bank for later activation.
11
RA41126EN05GLA0
Manual Commissioning
12
RA41126EN05GLA0
Commissioning Options
Template Follow wizard to update existing commissioning file, only site specific parameters need to be changed. Planned Requires a complete commissioning file for this site. Skips wizard and sends file direct to BTS without editing. Manual Use wizard to create a commissioning file from scratch. Must enter all required parameters that differ from default values.
13
RA41126EN05GLA0
Commissioning Wizard launches and you can create a file manually, or choose a template.
OSS network and configuration management tools can be used to create plan files to be loaded via OSS, or BTS SM
15
RA41126EN05GLA0
LNCEL eutraCelId (E-UTRAN cell identifier) is set by the system. In order to make it unique, the creation is based on the unique BTS ID (eNodeB ID). eutraCelId = 256 x BTS_ID + Local Cell ID LNCEL lncelId is the instance identifier of object LNCEL, used by NetAct and BTS Site Manager. This parameter appears only in the distinguished name (DN) in the plan file and is used for O&M purposes.
16
RA41126EN05GLA0
Site Properties
The BTS can act as a DHCP server, providing an IP address to external SSE (Site Support Equipment). 1. Provide a single (example above) or range of IP addresses to the connected devices without further specification on which device will get which IP address. Up to 3 NTP servers can be configured 2. Client ID provides a certain IP address to the specified client ID. 3. HW ID provides a certain IP address to the specified MAC address (ID).
17
RA41126EN05GLA0
Security
The Authentication Lightweight Directory Access Protocol server is required for the optional Remote User Account Management. In case a remote user attempts a BTS Site Manager connection, the eNode B grants the access based on account information read from the LDAP Server. If Allow only secure connection is selected, then TLS is required. The Certificate Management Protocol / Certificate Authority server optionally handles the automatic installation and renewal of certificates in the BTS. Certificates are needed to support the features Transport Layer Security and IP Security.
The optional Transport Layer Security for OAM interface can be Forced on, forced OFF or Probing (ON, if supported by certificates and iOMS configuration, otherwise OFF).
For security reasons the operator may want to block the BTS FTM from replying to Ping and Traceroute messages by removing the tick. The FTP server function may be required to transfer files to/from the eNodeB FTM without the use of the BTSSite Manager.
18 Nokia Siemens Networks RA41126EN05GLA0
In LTE, a PDH interface (max. 2) can only be used for one purpose: Synchronization.
Up to 3 Ethernet interfaces can be used (with FTIB only 2, EIF1&3 or 2&3). The Ethernet switching function is configured on the next page.
19
RA41126EN05GLA0
DSCP Mode
The criteria for priority queue mapping can be eitherDSCP Differentiated Services Code Point or the or VLAN priority code point VLAN-PCP.
In VLAN-PCP Mode, the mapping to a queue is based on the VLAN priority (07).
20 Nokia Siemens Networks RA41126EN05GLA0
The switch mode can be based on All (considering both MAC address and VLAN ID). In Tagged mode, only Ethernet frames with VLAN tagging will be switched). The user defined VLAN ID list can contain up to 16 entries (single or range).
The Shaper allows to limit the switched bandwidth per interface in Egress and Ingress direction individually.
21
RA41126EN05GLA0
22
RA41126EN05GLA0
23
RA41126EN05GLA0
24
RA41126EN05GLA0
Ethernet OAM
eNodeB Ethernet Link OAM
Ethernet Core
25
RA41126EN05GLA0
26
RA41126EN05GLA0
27
RA41126EN05GLA0
28
RA41126EN05GLA0
Enables QoS of the WFQ scheduler (pg. Quality of Service). One Eth IF or VLAN must have QoS enabled.
29
RA41126EN05GLA0
30
RA41126EN05GLA0
Expedited Forwarding
Assured Forwarding 4
Assured Forwarding 3
SIR/SBS
User
Assured Forwarding 2
Assured Forwarding 1 Best Effort
Application planes
g h i j
b c d
SIR/SBS
QoS Disabled
SIR/SBS
all
QoS Disabled
SIR/SBS
Note: In RL30 there can be - 1 un-tagged Eth IF and up to 4 VLANs or - 1...5 VLANs and no un-tagged Eth IF.
31 Nokia Siemens Networks RA41126EN05GLA0
32
RA41126EN05GLA0
BFD Sessions
BFD (Bi-directional Forwarding Detection) is an option to monitor IP connectivity to a far end Router. Up to 16 different destinations (sessions) can be monitored. If IP connectivity gets lost, an BFD alarm is generated.
33
RA41126EN05GLA0
Quality of Service
The Quality Of Service definitions on this page are applied to only that Transport Ethernet interface or VLAN for which QoS is enabled. The Weight definitions specify how the WFQ scheduler proiritizes between the 5 queues. This table defines the mapping of a DSCP to the PHB (defaults according to http://tools.ietf.org/html/rfc2597 recommendations) and VLAN priority.
Control Plane Management Plane Internet Control Message Protocol Internet Key Exchange Bi-directional Forwarding Detection Site Support Equipment
NOTE: Radio Network Parameters (LNBTS MO) contain mapping of LTE QCI indices to transport DSCP and radio bearer parameters (loss, delay, RLC mode).
34 Nokia Siemens Networks RA41126EN05GLA0
Expedited Forwarding
1
1 1 1 0 0 0 0 0 0 0 0 0 0
0
0 0 0 1 1 1 1 1 1 0 0 0 0
1
0 0 0 1 1 1 0 0 0 1 1 1 0
1
1 1 0 1 1 0 1 1 0 1 1 0 0
1
1 0 1 1 0 1 1 0 1 1 0 1 0
0
0 0 0 0 0 0 0 0 0 0 0 0 0
46
38 36 34 30 28 26 22 20 18 14 12 10 0
Best Effort
35
RA41126EN05GLA0
The Message rate should be set as high as necessary for a stable synchronization. The higher the message rate, the better is the stability and the higher is the required bandwidth. 8 times/second: ~7 kbps 16 times/second: ~ 13 kbps 32 times/second: ~ 25 kbps
36
RA41126EN05GLA0
Application Addresses
37
RA41126EN05GLA0
38
RA41126EN05GLA0
39
RA41126EN05GLA0
IPSec can be individually configured per traffic type. The pull-down menu under New Policy lets you select from a list of Policy templates with pre-filled traffic type specific port numbers and protcol IDs. Site specific settings still need to be filled in.
40
RA41126EN05GLA0
IPSec tunnel
Local IP address Local IPSec tunnel IP address Remote IPSec tunnel IP address Remote IP address
eNodeB
Gateway
Local IP address For own IP networks, this can either be the (physical) Transport Ethernet IP address or VLAN IP address or, in leased or public (VPN) connections this address can be virtual*. Local IPSec tunnel IP address This can either be the Transport Ethernet or VLAN IP address.
Note: In RL10 there can be a maximum of only 1 virtual address and only the Ethernet
Transport IP or 1 VLAN IP address are allowed to exist then.
* a virtual address is different from Ethernet interface or VLAN IP address.
41 Nokia Siemens Networks RA41126EN05GLA0
The smaller the Policy order number is the more highly valued is the policy. The applicable Policy/ies with the lowest order number(s) will be applied.
Bypass-setting does not process any packets, Discarded-setting does not forward any packets. Protected-setting follows the IPsec process.
In case a physical address is used, it can be selected from the pull-down menu. A virtual address has to be entered manually. The field is to be left blank, if the same policy is to be applied to all (VLAN) IP addresses.
The port number has to be specified according to the traffic type this policy is applied for. If a policy is to be used for all types of traffic, then the Local port field is to be left blank.
42
RA41126EN05GLA0
The Remote IP address, Remote port and Remote Ipsec tunnel endpoint IP address are set according the configuration on the Security gateway side of the Ipsec tunnel.
43
RA41126EN05GLA0
The IKE Internet Key Exchange is a protocol to exchange the keys used for IPSec encryption in a secure way and to detect if the far end peer is still alive (DPD-Dead Peer Detection). There are 2 versions V1 and V2. The version has to be selected according to the far end configuration at the Security Gateway
This is the Encapsulated Security Payload encryption method used for IPSec.
44
RA41126EN05GLA0
Peer is alive
dpddelay
Peer is alive
dpddelay
R-U-THERE R-U-THERE-ACK
IKE version V1
IKE version V2
t2
dpddelay R-U-THERE
t3
dpdtimeout
t4
FTM raises DPD alarm, and deletes IKE and Ipsec SAs
t6
FTM raises DPD alarm, And deletes IKE SA and CHILD SAs
45
RA41126EN05GLA0
parValueChangeInd( IKESA )
Anti replay is a method to protect the transport interface from replay attacks where formerly recorded data packages are send to the receiver in order to authenticate the (non-authorized) sender, even the encryption key is not known by him. Anti replay is based on a consecutive numbering of data packages with a sequence number. A replayed package would have the same sequence number like the original package and the receiver (here FTLB) would then discard the (faked) package. Also packages with a delay of more than one Anti replay window size would be rejected.
The Dead peer detection delay is the time between sending R-U-there messages in IKEv1 or Information Request Messgages in IKEv2.
The Dead peer detection timeout is the time after which a R-U-there Acknowledge message must be received. Otherwise a DPD alarm is raised. In IKEv2 the Dead peer detection timeout is not adjustable, but fixed to 165 seconds (T1...T6 = 4+7+13+24+42+75 sec.).
The Security associated lifetime is the time after which the key used for ESP encryption is automatically renewed.
46 Nokia Siemens Networks RA41126EN05GLA0
Synchronization
Maximum 2 Timing Sources can be configured. First Prority 1 must exist before selecting Priority 2. Avalable Types 1. 2. 3. E1 interface, if previously set in use. Synchronous Ethernet Timing over Packet, if previously configured.
47
RA41126EN05GLA0
Routing
If not already done on the IP settings page (9/32), BFD sessions can be configured here. If fast IP rerouting feature is used, then a BFD session has to be assigned at least to the preferred of the 2 alternative routes. Previously configured BFD sessions can be assigned to a gateway.
If alternative routes to a certain destination exist, then the Preference setting specifies which route will be preferred by the FTM.
48
RA41126EN05GLA0
IP Filtering
1.
2.
3.
1. Exception Rules allow the access to the Site Support equipment from certain remote IP addresses. Rules can be configured for single or ranges of far end IP addresses. 2. Restricted mode ON -> Remote Access to Site Support IP addresses totally blocked. 3. Restricted mode OFF -> Remote Access to Site Support IP addresses allowed for any far end IP address.
49
RA41126EN05GLA0
This table allows to configure how often the eNode B sends a TRS PM report to NetAct and which measurements are included.
Note: The Measurement Configuration for BTS Statistics is configure on the Radio Network Configuration page in the object MRBTS LNBTS PMRNL-1.
50
RA41126EN05GLA0
BTS Settings
51
RA41126EN05GLA0
Module Settings
52
RA41126EN05GLA0
53
RA41126EN05GLA0
54
RA41126EN05GLA0
55
RA41126EN05GLA0
F Uplink low
1920 1850 1710 1710 824
eUARFCN ULlow
18000 18600 19200 19950 20400
F Uplink high
1980 1910 1785 1755 849
eUARFCN ULhigh
18599 19199 19949 20399 20649
F Downlink low
2110 1930 1805 2110 869
eUARFCN DLlow
0 600 1200 1950 2400
F Downlink high
2170 1990 1880 2155 894
eUARFCN DLhigh
599 1199 1949 2399 2649
BW / MHz
60 60 75 45 25
Duplex Freq.
190 80 95 400 45
7
8 9 10
2500
880 1749.9 1710
20750
21450 21800 22150
2570
915 1784.9 1770
21449
21799 22149 22749
2620
925 1844.9 2110
2750
3450 3800 4150
2690
960 1879.9 2170
3449
3799 4149 4749
70
35 35 60
120
45 95 400
FDL[MHz] = FDL_low + 0.1 (eUARFCNDL eUARFCNDLlow) FUL[MHz] = FUL_low + 0.1 (eUARFCNUL eUARFCNULlow)
NDL and NUL are earfcnDL and earfcnUL which are attributes of LNCEL. earfcnDL = 3050, earfcnUL = 21050 FDL = FDL_low + 0.1 (eUARFCNDL eUARFCNDLlow) = 2620 + 0.1 (3050 2750) =2620 + 30 = 2650 MHz FUL = FUL_low + 0.1 (eUARFCNUL eUARFCNULlow) = 2500 + 0.1 (21050 -20750) = 2500 + 30 = 2530 MHz
56 Nokia Siemens Networks RA41126EN05GLA0
57
RA41126EN05GLA0
LTE Carriers
58
RA41126EN05GLA0
DC power and AISG communication is required to operate currently detected or to detect antenna line devices added in the future. For un-commissioned eNodeBs, both the AISG communication and DC power (24V) is active on all supporting ports. If no MHA is present, then DC power shall be turned off in order to reduce the power consumption of the eNodeB.
59
RA41126EN05GLA0
AISG capable MHAs are detected automatically. Additional data can be added optionally.
60
RA41126EN05GLA0
61
RA41126EN05GLA0
Since AISG 1.1 devices are not auto-detectable, they have to be defined during commissioning.
62
RA41126EN05GLA0
63
RA41126EN05GLA0
64
RA41126EN05GLA0
65
RA41126EN05GLA0
66
RA41126EN05GLA0
A validation check is performed by the BTS Manager. A missing or invalid parameter leads to an Error indication and description (table below).
67
RA41126EN05GLA0
68
RA41126EN05GLA0
69
RA41126EN05GLA0
70
RA41126EN05GLA0
oamControlled It is the responsibility of the operator to configure the correct cPlaneIpAddr. In terms of the limitation to maximum 32 X2 links oam controlled links have priority.
71
RA41126EN05GLA0
72
RA41126EN05GLA0
73
RA41126EN05GLA0
Note The S1 and X2 SCTP ports are not configurable anymore from RL20 onwards. It is now hard-coded to the 3GPP recommended values S1 SCTP port = 36412 and X2 SCTP port = 36422.
74 Nokia Siemens Networks RA41126EN05GLA0
75
RA41126EN05GLA0
This object allows to configure how often the eNode B sends a BTS PM report to NetAct and which measurements are included . If set to disabled, a measurement will not be collected and sent at all.
76
RA41126EN05GLA0
77
RA41126EN05GLA0
78
RA41126EN05GLA0
Send Parameters will update the BTS with the new configuration and restart the BTS (if required) to enable the changes.
79
RA41126EN05GLA0
All relevant commissioning parameters are set -> Send Parameters to the BTS.
Transfer status
80
RA41126EN05GLA0
Verify Commissioning
BTS Status should say BTS Configured. If S1 Setup is successful to MME state will show IntegratedToRan or On Air
81
RA41126EN05GLA0
Integration
82
RA41126EN05GLA0
BTS Initialising
BTS Commissioned
CDM (SCF file does not exist/ SCF file invalid/ BTS re-hosted)
BTS Uncommissioned
BTS Configured
STUP (S1 link connected) BTS can return to normal operation only after reset
BTS Integrated
STUP (none of the cells is enabled)
BTS On Air
83
RA41126EN05GLA0
Test IP Connectivity
Choose All configured hosts and make sure OAM, NTP Server, and Default gateway are connected. Choose User-defined address and enter the IP address for MME and S-GW and make sure they are connected (assuming no firewall restrictions block ICMP).
84
RA41126EN05GLA0
MME
SCTP: HEARTBEAT
SCTP: HEARTBEAT_ACK
...
85
RA41126EN05GLA0
S1 Setup Procedure
eNB
S1AP: S1 SETUP REQUEST
eNB global ID, eNB name, supported TAs and Paging DRX configuration
MME
SCTP: SACK
GUMMEI: Globally Unique MME Identity TA: Tracking Area DRX: Discontinue Reception
86 Nokia Siemens Networks RA41126EN05GLA0
Verify Integration
Once integrated to MME, BTS status should show IntegratedToRan or On Air if cell setup was successful for at least one cell.
Once communication is established with iOMS, OAM state should show OAM Connected. If GTPU supervision is enabled, check to make sure there are no GTP-U Path Failure alarms related to connection SGW. Confirm no SCTP endpoint failure alarms. This alarm is triggered due to S1 or X2 SCTP failure. This indicates X2 or S1 failure. Confirm no S1 or X2 alarms are active. If SCTP connection is established, but S1 or X2 protocol fails these alarms will be generated.
87
RA41126EN05GLA0
Appendix1: Abbreviations
AIS APS BFD BTS BTSSM CCM CFM CoS DA DTE DSCP E-OAM EM eNB EPC ETH ETP FCS FM FRM FTM GCI ID IP L-OAM LAN LB LBM LBR LMP LOS LTE Alarm Indication Signal Automatic Protection Switching Bidirectional Forward Detection Base Transceiver Station BTS Site Manager Continuity Check Message Connectivity Fault Management Class of Service Destination Address Data Terminal Equipment Differentiated Services Code Point Ethernet OAM Element Manager Evolved NodeB Evolved Packet Core Ethernet External Transport Port (on FSMD/E) Frame Check Sequence Fault Management Flexi Radio Module Flexi Transport Module Global Cell ID Identifier Internet Protocol Link OAM Local Area Network Loop Back Loop Back Message Loop Back Reply Local Management Port (on FSMx) Loss Of Signal Long Term Evolution LTM LTR MA MAC MAID MD MDL MEF MEN MEG MEP MIB MIP MME MML MP MRU MTU OAM PCI PCP PDU PHB PM RDI RRH S-OAM S-GW SSE TAC TLV TTL VLAN X2 XC Link Trace Message Link Trace Reply Maintenance Association Media Access Control Maintenance Association Identifier Maintenance Domain Maintenance Domain Level ME Maintenance Entity Metro Ethernet Forum Metro Ethernet Network ME Group ME End Point Management Information Base MEG Intermediate Point Mobility Management Entity Man-Machine Language Maintenance Point Maximum Receive Unit Maximum Transmission Unit Operation, Administration and Maintenance Physical Cell ID Priority Code Point Protocol Data Unit Per Hop Behavior Performance Monitoring Remote Defect Indication Remote Radio Head Service OAM Serving Gateway Site Support Equipment Tracking Area Code Type, Length, Value Time To Live Virtual LAN IP interface between adjacent eNode Bs Cross Connect
88
RA41126EN05GLA0