06 RA41126EN05GLA0 LTE Flexi Multiradio BTS Commissioning and Integration
Transcript of 06 RA41126EN05GLA0 LTE Flexi Multiradio BTS Commissioning and Integration
1 © Nokia Siemens Networks RA41126EN05GLA0
Flexi Multiradio LTE BTS Commissioning and Integration
RL40
2 © Nokia Siemens Networks RA41126EN05GLA0
NSN Siemens Networks Academy
Legal notice
Intellectual Property RightsAll copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session for development of groups without the prior written agreement of Nokia Siemens Networks.
3 © Nokia Siemens Networks 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
4 © Nokia Siemens Networks RA41126EN05GLA0
Contents
BTS Site Manager Installation
Manual BTS software update
Manual Commissioning
Integration
5 © Nokia Siemens Networks RA41126EN05GLA0
Flexi Multiradio LTE BTS Commissioning
Start
Power On
Autoconnection Enabled
Autoconfiguration Enabled
SW Update
Commissioning file download from iOMS
Site reset
Commisisoning tests (optional)
Integration
Local Connect
Remote Connect
SW Update
Commissioning File?
Planned Template Manual
Enter site-specific parameters
Enter all parameters
Site reset
Commissioning Report
Done
Yes
Yes
No
No
Autoconfiguration Report
Complete Template None
Commisisoning tests (optional)
6 © 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.
BTS Site Manager Installation
7 © Nokia Siemens Networks RA41126EN05GLA0
Launching BTS Site Manager
Element manager PC must be on proper IP subnet to connect to BTS
Local connections: Connected directly to eNB via LMP port
on Flexi BTS System Module, and Flexi BTS uses
192.168.255.0 / 24 subnet for internal OAM network.
PC IP address:
192.168.255.126
Subnet mask: 255.255.255.0
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
8 © Nokia Siemens Networks RA41126EN05GLA0
Launching BTS Site Manager
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.
9 © Nokia Siemens Networks 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.
Accept self-signed Certificate
10 © Nokia Siemens Networks RA41126EN05GLA0
Verify BTS Software Level
active SW running in the
FSMx
active SW running in the
FTM
Filter controller SW of Radio
Module, (AISG) MHA SW and Tilt Adjuster
SW.
11 © Nokia Siemens Networks RA41126EN05GLA0
Software Update via BTS Site Manager
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.
File selected was LN4.0_1202_108__00_release_BTSSM_downloadable.zip.
BTSSM decompresses and selects the TargetBD file which points to necessary binaries for this release.
12 © Nokia Siemens Networks RA41126EN05GLA0
Manual Commissioning
13 © Nokia Siemens Networks 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.
14 © Nokia Siemens Networks RA41126EN05GLA0
Site Commissioning File (SCF)
Site Commissioning File is XML format, it has the naming convention SCFC_<counter_id>.xml and is stored in /rom/config directory on FCM. BTS SM creates the ID and updates the path in /rom/FileDirectory.xml to point to the correct commissioning file. A new commissioning creates a new counter_id (1, 2, 3 etc.). There can be several SCFC_<Counter_id> be existing in the /rom/config. But only one of them may be flagged as active in the FileDirectory.xml.
Consists of managed objects related to site HW, transport, and radio network parameters.
BTS Site Manager runs a verification check prior to sending new commissioning file to ensure parameters are within range and related parameters are compatible.
Key site specific parameters are found in managed objects ADIPNO, LNBTS, LNCEL, IAFIM, IPNO, IEIF. At a minimum parameters within these MOs need to be changed during template commissioning.
15 © Nokia Siemens Networks RA41126EN05GLA0
Site Commissioning File Creation
File can be created via BTS Site Manager in offline mode (no connection to BTS required).
Select the BTS Site Manager release that corresponds to the SW load that will be running on the BTS and click Create.
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
16 © Nokia Siemens Networks RA41126EN05GLA0
E-UTRAN Cell Identifier
EUTRAN-Cell Id
20 bits correspond to BTS ID (parameter LNBTS-id) 8 bits lcrId
28 bits
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.
EUTRAN-cell ID Information Element in S1SetupRequest
lcrId - Local Cell Id defined in Commissioning (wizard page “Cell Resources”)
17 © Nokia Siemens Networks 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.
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).
Up to 3 NTP servers can be
configured
18 © Nokia Siemens Networks 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.
19 © Nokia Siemens Networks RA41126EN05GLA0
Physical Layer Configuration - Transport
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.
20 © Nokia Siemens Networks RA41126EN05GLA0
Ethernet Switching with FTIB 1/2
The QoS aware Ethernet switching function supports 4 queues in FTIB. The queue weight is configurable in the range 1...8.
The criteria for priority queue mapping can be eitherDSCP Differentiated Services Code Point or the or VLAN priority code point VLAN-PCP.
DSCP ModeVLAN PCP Mode
In VLAN-PCP Mode, the mapping to a queue is based on the VLAN priority (0…7).
21 © Nokia Siemens Networks RA41126EN05GLA0
Ethernet Switching in DSCP Mode with FTIB 2/2
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.
This is the priority and VLAN ID applied to all un-tagged frames of the internal interface between FTM and the System Module, carrying this eNodeB’s own traffic.
22 © Nokia Siemens Networks RA41126EN05GLA0
Ethernet Switching in DSCP Mode with FTLB 1/2
The QoS aware Ethernet switching function supports 6 queues in FTLB. The queue weight is configurable in the range 1...8.
23 © Nokia Siemens Networks RA41126EN05GLA0
Ethernet Switching in DSCP Mode with FTLB 2/2
If the Ethernet network allows the operator to temporarily oversubscript the leased bandwidth, then an increasing of the egress data rate to max. 106% (6% Egress burst size) may help to avoid congestion and buffer overflow.
Note: This option is not available with FTIB.
24 © Nokia Siemens Networks RA41126EN05GLA0
Ethernet Switching capabilities FTIB vs. FTLB
EIF 1
EIF 2
EIF 3
EIF 1
EIF 2
EIF 3
FTIBFTLB
To FSMxTo FSMx
25 © Nokia Siemens Networks RA41126EN05GLA0
Ethernet OAM
Ethernet CoreEthernet Core
Ethernet Link OAM
Ethernet Service OAM
eNodeBNode supporting Ethernet link OAM
Nodes supporting Ethernet Service OAM
eNodeB
26 © Nokia Siemens Networks RA41126EN05GLA0
Ethernet Link OAM
27 © Nokia Siemens Networks RA41126EN05GLA0
Ethernet Service OAM
28 © Nokia Siemens Networks RA41126EN05GLA0
IP Interfaces User Plane GBR admission control
29 © Nokia Siemens Networks RA41126EN05GLA0
IP Interfaces – Untagged interface
Is the individual TRS Eth / Vlan shaper (Path) or the overall shaper (WFQ) used?
Shaper rate and weight for the overall WFQ scheduler.
Enables QoS of the WFQ scheduler (pg. Quality of Service). One Eth IF or VLAN must have QoS enabled.
Shaper rate and weight for the overall Path scheduler.
IP address and subnet-mask of the un-tagged transport interface.
30 © Nokia Siemens Networks RA41126EN05GLA0
IP Interfaces – VLAN interface
31 © Nokia Siemens Networks RA41126EN05GLA0
all SIR/SBS
Transport Ethernet / VLAN QoS
SIR/SBS
OverallWFQ
egress
WFQ
SP
all
all
all
OverallShaperSIR/SBS
SIR/SBS
SIR/SBS
Sta
nd
ard
IP
ro
utin
g o
n I
P d
est
ina
tionUser
Ctrl
Mgmt
Sync
a
b
c
d
f
g
h
i
j
App
licat
ion
plan
es
Application IP Addresses
Interface IP Addresses
Expedited Forwarding
Assured Forwarding 4
Assured Forwarding 3
Assured Forwarding 2
Assured Forwarding 1
Best Effort
User-defined Queue weights
Weighted Fair Queuing Scheduler /
Strict Priority
QoS Enabled
QoS Disabled
QoS Disabled
QoS Disabled
QoS Disabled
individual ShapingTraffic
Shaping Type: Path
overall VLAN Shaping
Traffic Shaping Type: WFQ
Shaper Information Rate
Shaper Burst Size
Total Shaper Information
Rate
Total Shaper Burst Size
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.
Eth IF / VLAN
specifig WFQ
scheduler weight
32 © Nokia Siemens Networks RA41126EN05GLA0
IP Interfaces – VLAN interface
33 © Nokia Siemens Networks 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.
34 © Nokia Siemens Networks 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 Traffic type to
a DSCP.
This table defines the mapping of a DSCP to the PHB (defaults according to
http://tools.ietf.org/html/rfc2597 recommendations) and VLAN priority.
NOTE: Radio Network Parameters (LNBTS MO) contain mapping of LTE QCI indices to transport DSCP and radio bearer parameters (loss, delay, RLC mode).
Control Plane
Management Plane
Internet Control Message Protocol
Internet Key Exchange
Bi-directional Forwarding Detection
Site Support Equipment
35 © Nokia Siemens Networks RA41126EN05GLA0
Recommended Differentiated Services Code Points (DSCP)
Assured forwarding class
Per Hop Behavior Drop Precedence DSCP
PHB Drop Precedence binary binary decimal
Expedited Forwarding 1 0 1 1 1 0 46
4 3 1 0 0 1 1 0 38
4 2 1 0 0 1 0 0 36
4 1 1 0 0 0 1 0 34
3 3 0 1 1 1 1 0 30
3 2 0 1 1 1 0 0 28
3 1 0 1 1 0 1 0 26
2 3 0 1 0 1 1 0 22
2 2 0 1 0 1 0 0 20
2 1 0 1 0 0 1 0 18
1 3 0 0 1 1 1 0 14
1 2 0 0 1 1 0 0 12
1 1 0 0 1 0 1 0 10
Best Effort 0 0 0 0 0 0 0
36 © Nokia Siemens Networks RA41126EN05GLA0
Timing over Packet
Activating the Timing over Packet in use field makes it available as a synchronization source when
defining the Timing Sources on the Synchronization page of the wizard.
The Master Clock IP address must be reachable through the Def. GW / Static Route(s)
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
37 © Nokia Siemens Networks RA41126EN05GLA0
Application Addresses
38 © Nokia Siemens Networks RA41126EN05GLA0
RTT measurement 1/2
39 © Nokia Siemens Networks RA41126EN05GLA0
RTT measurement 2/2
40 © Nokia Siemens Networks RA41126EN05GLA0
Activate IPsec and choose a profile
Check the IPSec in use field to configure IP Security processing.
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.
41 © Nokia Siemens Networks RA41126EN05GLA0
IPSec tunnel
IPSec tunnel
IPSec
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.
Local IP address
Local IPSec tunnel IP address
Remote IPSec tunnel IP address
Remote IP address
eNodeB
42 © Nokia Siemens Networks RA41126EN05GLA0
Ipsec settings 1/4The 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.
43 © Nokia Siemens Networks RA41126EN05GLA0
Ipsec settings 2/4
The Local Ipsec tunnel endpoint IP address can be selected from the pull-down menu. It is either the previously configured Transport Ethernet IP address or a VLAN IP address.
The Protocol is to be selected according to the traffic type this policy applies for. For all protocol types, the field is to be left blank.
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.
44 © Nokia Siemens Networks RA41126EN05GLA0
Ipsec settings 3/4 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 encryption method used for the Key exchange.
This is the Encapsulated Security Payload encryption method used for IPSec.
45 © Nokia Siemens Networks RA41126EN05GLA0
PeerFTM
R-U-THERE
dpddelay
R-U-THERE
R-U-THERE
R-U-THERE
R-U-THERE
FTM raises DPD alarm, and deletes IKE and Ipsec SAs
dpddelay
dpddelay
dpdtimeout
dpddelay
dpddelay
dpddelay
dpddelayR-U-THERE
R-U-THERE-ACK
R-U-THERE
R-U-THERE-ACK
Peer is alive
Peer is not alive
PeerFTM
IKE INFORMATIONAL request
t1IKE INFORMATIONAL request
dpddelay
IKE INFORMATIONAL requestt2
IKE INFORMATIONAL request
IKE INFORMATIONAL request
t4
t3
t5
IKE INFORMATIONAL request
t6
FTM raises DPD alarm,And deletes IKE SA and CHILD SAs
IKE INFORMATIONAL request
IKE INFORMATIONAL response
dpddelay
dpddelay
IKE INFORMATION REQUEST
IKE INFORMATIONAL response
Peer is alive
Peer is not alive
FAP
parValueChangeInd( IKESA )
IKE version V1 IKE version V2 DPD (Dead peer detection) with Internet Key Exchange
Internet Key Exchange protocol versions
46 © Nokia Siemens Networks RA41126EN05GLA0
Ipsec settings 4/4
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.
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.
47 © Nokia Siemens Networks RA41126EN05GLA0
Synchronization
Maximum 2 Timing Sources can be configured. First Prority 1 must exist before selecting Priority 2.
Avalable Types
1. E1 interface, if previously set in use.
2. Synchronous Ethernet
3. Timing over Packet, if previously configured.
Priority 3 is fixed to Internal clock.
48 © Nokia Siemens Networks RA41126EN05GLA0
RoutingIf 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.
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.
49 © Nokia Siemens Networks RA41126EN05GLA0
IP Filtering
There a are 3 ways to configure IP Filtering.
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.
1.
2.
3.
50 © Nokia Siemens Networks RA41126EN05GLA0
Measurement Configuration for TRS
Note: The Measurement Configuration for BTS Statistics is configure on the Radio Network Configuration page in the object MRBTS – LNBTS – PMRNL-1.
This table allows to configure how often the eNode B sends a TRS PM report to NetAct and
which measurements are included.
51 © Nokia Siemens Networks RA41126EN05GLA0
BTS Settings
52 © Nokia Siemens Networks RA41126EN05GLA0
Module Settings
53 © Nokia Siemens Networks RA41126EN05GLA0
Cell Resources „A-Type“ and I-Type
54 © Nokia Siemens Networks RA41126EN05GLA0
Cell Resources „H-Type“Note: All 3 cells’ ANT ports are shown at once.
Cell 1: both ANT 1
Cell 2: both ANT 3
Cell 3: both ANT 5
55 © Nokia Siemens Networks RA41126EN05GLA0
Concurrent Mode Settings
56 © Nokia Siemens Networks RA41126EN05GLA0
3GPP Frequency Bands 1/2
Band F Uplink low
eUARFCN
ULlow
F Uplinkhigh
eUARFCN
ULhigh
F Downlinklow
eUARFCN
DLlow
F Downlinkhigh
eUARFCN
DLhigh
BW /MHz
Duplex
Freq.
1 1920 18000 1980 18599 2110 0 2170 599 60 190
2 1850 18600 1910 19199 1930 600 1990 1199 60 80
3 1710 19200 1785 19949 1805 1200 1880 1949 75 95
4 1710 19950 1755 20399 2110 1950 2155 2399 45 400
5 824 20400 849 20649 869 2400 894 2649 25 45
7 2500 20750 2570 21449 2620 2750 2690 3449 70 120
8 880 21450 915 21799 925 3450 960 3799 35 45
9 1749.9 21800 1784.9 22149 1844.9 3800 1879.9 4149 35 95
10 1710 22150 1770 22749 2110 4150 2170 4749 60 400
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
FDL[MHz] = FDL_low + 0.1 (eUARFCNDL – eUARFCNDLlow) FUL[MHz] = FUL_low + 0.1 (eUARFCNUL – eUARFCNULlow)
Example from band 7 (2600 MHz)
Calculation of UL & DL Frequencies:
57 © Nokia Siemens Networks RA41126EN05GLA0
3GPP Frequency Bands 2/2
Band F Uplinklow
eUARFCN
ULlow
F Uplinkhigh
eUARFCN
ULhigh
F Downlinklow
eUARFCN
DLlow
F Downlinkhigh
eUARFCN
DLhigh
Bandwidth Duplex
Freq.
11 1427.9 22750 1452.9 22999 1475.9 4750 1500.9 4999 25 48
12 698 23000 716 23179 728 5000 746 5179 18 30
13 777 23180 787 23279 746 5180 756 5279 10 -31
14 788 23280 798 23379 758 5280 768 5379 10 -30
17 704 23730 716 23849 734 5730 746 5849 12 30
18 815 23850 830 23999 860 5850 875 5999 15 45
19 830 24000 845 24149 875 6000 890 6149 15 45
20 832 24150 862 24449 791 6150 821 6449 30 -41
21 1447.9 25050 1462.9 25199 1495.9 7050 1510.9 7199 15 48
33 1900 36000 1920 36199 1900 36000 1920 36199 20 Tdd
34 2010 36200 2025 36349 2010 36200 2025 36349 15 Tdd
35 1850 36350 1910 36949 1850 36350 1910 36949 60 Tdd
36 1930 36950 1990 37549 1930 36950 1990 37549 60 Tdd
37 1910 37550 1930 37749 1910 37550 1930 37749 20 Tdd
38 2570 37750 2620 38249 2570 37750 2620 38249 50 Tdd
39 1880 38250 1920 38649 1880 38250 1920 38649 40 Tdd
40 2300 38650 2400 39649 2300 38650 2400 39649 100 Tdd
58 © Nokia Siemens Networks RA41126EN05GLA0
LTE Carriers
59 © Nokia Siemens Networks RA41126EN05GLA0
Antenna Line Management
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.
60 © Nokia Siemens Networks RA41126EN05GLA0
AISG MHA Settings
AISG capable MHAs are detected automatically.
Additional data can be added optionally.
61 © Nokia Siemens Networks RA41126EN05GLA0
Antenna Line Settings2 VSWR alarm threshold exist. All associated cells will be blocked on occurrence of the VSWR major fault. If no alarm thresholds are entered, then the default values apply
(minor: 1.9, major: 2.6).
62 © Nokia Siemens Networks RA41126EN05GLA0
Siemens Proprietry AISG 1.1 TMARET and RET settings
Since AISG 1.1 devices are not auto-detectable, they have to be defined during commissioning.
63 © Nokia Siemens Networks RA41126EN05GLA0
RET Settings 1/2
Additional information type of data may be added as an option.
64 © Nokia Siemens Networks RA41126EN05GLA0
RET Settings 2/2
65 © Nokia Siemens Networks RA41126EN05GLA0
System Module External Fault and Control Settings
66 © Nokia Siemens Networks RA41126EN05GLA0
Radio Module External Fault and Control Settings
67 © Nokia Siemens Networks RA41126EN05GLA0
Radio Network Configuration handling introduction
RNW parameters are formatted in a hierarchy, click arrows to see subordinate objects.
Parameters can be listed in two orders:
Alpahbetically lets you easily find a parameter known by name.
Related Functions uses the same order as in the SCF xml-file.
Hover mouse over parameter name to see description and short name (as appears in SCF file).
A validation check is performed by the BTS Manager. A missing or invalid parameter leads to an Error indication and description (table below).
68 © Nokia Siemens Networks RA41126EN05GLA0
LNBTS – LTE Node BTS Parameters
69 © Nokia Siemens Networks RA41126EN05GLA0
ADIPNO – Adjacent IP Node:Primary IP address of main MME
70 © Nokia Siemens Networks RA41126EN05GLA0
LNADJ – LTE Node Adjacencies 1/2
enbControlled The IP address will be maintained by ANR procedures if ANR features are activated. It is the default value for neighbor eNBs which have been learnt via ANR procedures.
71 © Nokia Siemens Networks RA41126EN05GLA0
LNADJ – LTE Node Adjacencies 2/2
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.
72 © Nokia Siemens Networks RA41126EN05GLA0
Global eNodeB Id X2-link blacklist
73 © Nokia Siemens Networks RA41126EN05GLA0
GTPU MO – Key ParametersUser plane Link supervision
74 © Nokia Siemens Networks RA41126EN05GLA0
SCTP MO – Key Parameters
Control plane supervision
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.
75 © Nokia Siemens Networks RA41126EN05GLA0
LNCEL MO – Key Parameters
76 © Nokia Siemens Networks RA41126EN05GLA0
BTS Performance Management Configuration
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.
77 © Nokia Siemens Networks RA41126EN05GLA0
Send Parameters – View Changes
78 © Nokia Siemens Networks RA41126EN05GLA0
Send Parameters – View Parameters
79 © Nokia Siemens Networks RA41126EN05GLA0
Send Parameters – Online Mode
Send Parameters will update the BTS with the new configuration and restart the BTS (if required) to enable the changes.
80 © Nokia Siemens Networks RA41126EN05GLA0
Initial BTS State
All relevant commissioning parameters are set -> “Send Parameters” to the BTS.
Expected final BTS State
Transfer status
BTS Commissioning: Send Parameters
81 © Nokia Siemens Networks RA41126EN05GLA0
Verify Commissioning
After sending parameters to eNB check status after site reset.
TRS status should say TRS Commissioned (as shown)
BTS Status should say “BTS Configured”. If S1 Setup is successful to MME state will show “IntegratedToRan” or “On Air”
82 © Nokia Siemens Networks RA41126EN05GLA0
Integration
83 © Nokia Siemens Networks RA41126EN05GLA0
BTS Startup Overview
BTS Initialising
BTS Uncommissioned
BTS Commissioned
BTS Configured
BTS Integrated
BTS Test Dedicated State
BTS On Air
CDM (SCF file does not exist/ SCF file invalid/ BTS re-hosted)
SCF and RNW configuration file download and reset
STUP (SCF exists in BTS, SCF parsed)
STUP (Ready check done, FD enabled)
STUP (S1 link connected)
STUP (at least one cell has operational state “Enabled”)
STUP (none of the cells is enabled)
STUP (TD state requested)
BTS can return to normal operation only after reset
Power ON / reset
84 © Nokia Siemens Networks 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).
85 © Nokia Siemens Networks RA41126EN05GLA0
SCTP Association Establishment
eNB (Power On / Reset) MMESCTP: INIT
SCTP: INIT_ACK
SCTP: COOKIE_ECHO
SCTP: COOKIE_ACK
SCTP: HEARTBEAT
SCTP: HEARTBEAT_ACK
SCTP: HEARTBEAT
SCTP: HEARTBEAT_ACK
...
SCTP establishment
SCTP link supervision
86 © Nokia Siemens Networks RA41126EN05GLA0
S1 Setup Procedure
eNB MME
S1AP: S1 SETUP REQUEST
SCTP: SACK
S1AP: S1 SETUP RESPONSE
SCTP: SACK
eNB global ID, eNB name, supported TAs and Paging DRX configuration
ServedGUMMEI, Relative MME capacity
GUMMEI: Globally Unique MME IdentityTA: Tracking AreaDRX: Discontinue Reception
87 © 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 S-GW.
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.
88 © Nokia Siemens Networks RA41126EN05GLA0
Appendix1: AbbreviationsAIS Alarm Indication SignalAPS Automatic Protection SwitchingBFD Bidirectional Forward DetectionBTS Base Transceiver StationBTSSM BTS Site ManagerCCM Continuity Check MessageCFM Connectivity Fault ManagementCoS Class of ServiceDA Destination AddressDTE Data Terminal EquipmentDSCP Differentiated Services Code PointE-OAM Ethernet OAMEM Element ManagereNB Evolved NodeBEPC Evolved Packet CoreETH EthernetETP External Transport Port (on FSMD/E)FCS Frame Check SequenceFM Fault ManagementFRM Flexi Radio ModuleFTM Flexi Transport ModuleGCI Global Cell IDID IdentifierIP Internet ProtocolL-OAM Link OAMLAN Local Area NetworkLB Loop BackLBM Loop Back MessageLBR Loop Back ReplyLMP Local Management Port (on FSMx)LOS Loss Of SignalLTE Long Term Evolution
LTM Link Trace Message LTR Link Trace ReplyMA Maintenance AssociationMAC Media Access ControlMAID Maintenance Association IdentifierMD Maintenance DomainMDL Maintenance Domain Level ME Maintenance EntityMEF Metro Ethernet ForumMEN Metro Ethernet NetworkMEG ME GroupMEP ME End PointMIB Management Information BaseMIP MEG Intermediate PointMME Mobility Management EntityMML Man-Machine LanguageMP Maintenance PointMRU Maximum Receive UnitMTU Maximum Transmission UnitOAM Operation, Administration and MaintenancePCI Physical Cell IDPCP Priority Code PointPDU Protocol Data UnitPHB Per Hop BehaviorPM Performance MonitoringRDI Remote Defect IndicationRRH Remote Radio HeadS-OAM Service OAMS-GW Serving GatewaySSE Site Support EquipmentTAC Tracking Area CodeTLV Type, Length, ValueTTL Time To LiveVLAN Virtual LANX2 IP interface between adjacent eNode BsXC Cross Connect