FMR LTE Commissioning & Integration

LTE eNB Commissioning and Integration RL20

Flexi Multiradio LTE BTS Commissioning and Integration

RL40# Nokia Siemens NetworksRA41126EN05GLA0# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#NSN Siemens Networks AcademyLegal 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.# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#ObjectivesAfter this training module, the participant will be able to

list the generic steps when manually commissioning a LTE Flexi Multiradio BTSrecognize the different types of Flexi Transport sub-modules by name and functionsdescribe installation options for LTE Flexi Multiradio BTSlist the hardware and software requirements for the LTE Flexi Multiradio BTS Element Manager for Local/Remote usagedemonstrate configuration of the personal computer used for commissioningdescribe configuration of hardware settings, transmission interfaces and synchronization settingsdescribe the overview of Remote Management operation/administration of the LTE Flexi Multiradio BTSinspect and check BTS Interface terminationsinspect and check IP and DCN settings for Remote Access and Managementdescribe and Check all integration relevant parameters in the eNodeB commissioning filedemonstrate inspection, checking and testing of the LTE Flexi Multiradio BTS commissioned configuration and status using the LTE Flexi Multiradio BTS Element Manager

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#ContentsBTS Site Manager InstallationManual BTS software updateManual CommissioningIntegration# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Flexi Multiradio LTE BTS CommissioningStartPower OnAutoconnection EnabledAutoconfiguration EnabledSW UpdateCommissioning file download from iOMSSite resetCommisisoning tests (optional)IntegrationLocal ConnectRemote ConnectSW UpdateCommissioning File?PlannedTemplateManualEnter site-specific parametersEnter all parametersSite resetCommissioning ReportDoneYesYesNoNoAutoconfiguration ReportCompleteTemplateNoneCommisisoning tests (optional)# Nokia Siemens NetworksRA41126EN05GLA0Autoconnection enabledThis step is automatic if the autoconnection feature is enabled. If autoconnection is not enabled, the connection to the BTS must be done locally.

This feature enables automatic connection to servers in the network, and an automatic establishment of the O&M connection of the BTS to the O&M system.Only HW and cabling need to be installed at the site. No personnel with telecom experience needs to be at the site to commission the BTS, as the integration of a newly installed BTS is fully automated. When the BTS is powered up, it will automatically check the BTS commissioning status, establish IP connectivity and retrieve operator certificate and trust anchors (optional). As soon as the final certificates are available, the BTS starts the secure O&M plane connection to the NetAct framework.

Autoconfiguration enabledThis step is automatic if autoconnection is enabled. If autoconfiguration is not enabled, the connection to the BTS must be established remotely.

The BTS autoconfiguration feature provides automatic commissioning and configuration of new or re-homed base stations from a remote network operation centre with minimal manual intervention. The automated configuration is initiated by the eNB auto configuration agent and controlled by the NetAct auto configuration application, which belongs to the overall NetAct SON coordinator application.

NOTE: Prior to start of commissioning there should be a visual check and inspection

The following items are checked: the grounding power cabling and supply voltage other cables and fibers LED status during power up TX/RX antenna connector torque check

RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#

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# Nokia Siemens NetworksRA41126EN05GLA01 - Download the BTS Site Manager installation file.Save the file on your PC.

2 - If you have BTS Site Manager running on your PC, close it before starting theinstallation.

3 - Double-click the file to start the installation (here: BTSSiteEM-LTE20-2.0.33.exe).The above page opens.

4 - Click Next, and read and accept the terms of the license agreement.

5 - Click Next.Define the location where to install the BTS Site Manager. If you have earlier versions of the BTS Site Manager on your PC, you need to remove the installed versions before you can change the location. It is not required to remove earlier versions of the BTS Site Manager when a new version is installed. The correct BTS Site Manager version is selected automatically when the connection to the BTS is established. If the installation of the BTS Manager is unsuccessful, use the Clean installation option to remove all BTS Site Manager versions from your PC and start the installation again.

6 - Click Next, and inspect the summary information for the installation procedure.

7 - Click Next.The BTS Site Manager installer installs the software to the specified location.

8 - Click Finish.BTS Site Manager installer closes and you can use the BTS Site ManagerRA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Launching BTS Site Manager

PC Setting for Local Connection

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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.# Nokia Siemens NetworksRA41126EN05GLA0Launch BTS Site Manager by clicking on the shortcut created during installationEnter IP address. For local connections, select local. For remote connections, enter IP address of BTS OAM interface.Enter user name and password. The default user name is Nemuadmin and the default password nemuuser.Using web interface at 192.168.255.129, local user account information can be reset to factory defaults (Nemuadmin/nemuuser) via local connection. The FTM transportmodule provides a service to recover the transport module. Recovery will delete the configuration except: Super user account credentials NE account credentials (if existing) BTS keypair (BTS certificate and BTS private key, if existing) CA certificate (if existing)Recovery will reset the transport module.4) Click ConnectThe progress of the operation is displayed in the Task Selection view.If multiple versions of BTS Site Manager are installed on the PC, the appropriate BTS Site Manager version is selected automatically.When the connection is established, the Task Selection view closes and the BTS Site Manager main view opens. If you receive a message with the text "Cannot establish secure connection", click the Accept button to connect to the BTS.


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

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#

Verify BTS Software Level

active SW running in the FSMxactive SW running in the FTMFilter controller SW of Radio Module, (AISG) MHA SW and Tilt Adjuster SW.# Nokia Siemens NetworksRA41126EN05GLA0To verify the software for all modules (RF, transport, system) you can select Software SW Versions to see a list of all of the binaries and versions which can be compared against release notes. RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#

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.# Nokia Siemens NetworksRA41126EN05GLA0The software for the transmission sub-module, radio modules and radio heads is included in the software package for the BTS site. BTS Site Manager will update the transport, RF module and system module SW as required.If you do not check Activate SW after update the SW update will be downloaeded but not applied and you will have to perform the Update SW to BTS Site again, this time files already stored on BTS do not have to be downloaded again.NOTE: If the BTS site has a connection to Nokia Siemens Networks NetAct, the NetAct will manage the BTS site SW (that is, checks the SW version and, if it is different than the SW in the NetAct database, downloads new SW in the BTS site).

RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Manual Commissioning# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Commissioning Options

# Nokia Siemens NetworksRA41126EN05GLA0Commissioning is divided into BTS and TRS. One commissioning file is created that contains values for both BTS and transport.

Reconfiguration is only an option after initial commissioning has been completed. It allows you to update parameters from the existing configuration.

For Template or Planned commissioning you need to select a commissioning file (XML format). This is not required for Manual or Reconfiguration.

NOTE: Site commissioning can only begin after all modules are initialized. If there are SW problems and modules cannot initialize the commissioning options will be grayed-out and not be selectable.

RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Site Commissioning File (SCF)

# Nokia Siemens NetworksRA41126EN05GLA0Site specific parameters include:

Adjacent eNB IP addresses in ADIPNO (Adjacent IP Nodes), and possibly MME, S-GW IP addressesBTS ID in LNBTS object, LNCEL ID in LNCEL object Physical cell ID in LNCEL objectAdjacent physical cell ids in IAFIM (Intra frequency idle mode configuration)IP addresses of BTS functions (U, C, M, S plane interface addresses), iOMS, and BTS ID in IPNO (IP Nodes, TRS parameters)Transport physical IP address in IEIF MO (TRS parameters)

RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Site Commissioning File Creation

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#E-UTRAN Cell IdentifierEUTRAN-Cell Id20 bits correspond to BTS ID (parameter LNBTS-id)8 bits lcrId28 bits

lcrId - Local Cell Id defined in Commissioning (wizard page Cell Resources)# Nokia Siemens NetworksRA41126EN05GLA0The E-UTRAN cell identifier is unique within one PLMN and has a length of 28 bits. The leftmost 20 bits of the value correspond to the value of the eNB ID (parameter lnBtsId) and the 8 rightmost bits correspond to the value of the local cell resource ID (lcrId). This parameter cannot be set by operator, it is calculated system internally and is only readable.


Site PropertiesThe 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# Nokia Siemens NetworksRA41126EN05GLA0Name Enter the name for the BTS site in the Name field (maximum of 15 characters). Location Enter the location of the element in the Location field (maximum of 50 characters). Description Enter the description of the element in the Description field (maximum of 128 characters).

BTS ID Enter the BTS identifier in the BTS ID field. The BTS ID has to be defined according to agreed value, which is usually determined at the network planning stage. Do not assign arbitrary value for this parameter. Note, that BTS ID in MRBTS (mrbtsId), LNBTS (lnBtsId), BTSSC (btsId) and FTM: IPNO: (btsId) parameters must all have the same BTS ID value in commissioning file. If the value is changed it must be done in site commissioning. IPNO: btsId (BTS ID) is set on Site Properties page. MRBTS: mrbtsId (Multiradio BTS site identifier) and LNBTS: lnBtsId (Instance identifier of object LNBTS) are set on Radio Network Configuration page. BTSSC: btsId is set automatically by BTS Site Manager to commissioning file according to BTS Id value set to other related parameters. BTS subnet interface Enter the BTS subnet interface IP address in the BTS subnet interface field. The Subnet Mask IP address can be 1.0.0.0 - 255.255.255.255 / 1...30. The other IP addresses can be 0.0.0.0 - 255.255.255.254 but the following IP addresses should not be configured: default address (0.0.0.0) addresses in the subnet 127.x.x.x (reserved for loopbacks) addresses in the subnet 192.168.254.xxx (internal address) addresses in the subnet 192.168.255.xxx (internal address) multicast address (224.0.0.0 - 239.255.255.255) class E address (240.0.0.0 - 255.255.255.255) broadcast address (255.255.255.255) directed broadcast/network address (x.x.x.255/24 or x.x.x.0/24)

Primary OAM system Enter the primary OAM system IP address in the Primary OAM system field.

Secondary OAM system Enter the secondary OAM system IP address in the Secondary OAM system field.

OAM system preference Select the OAM system preference from the OAM system preference drop-down list: Automatic, Primary forced or Secondary forced.

Primary DNS server Enter the IP address for the primary DNS server.

Secondary DNS server Enter the IP address for the secondary DNS server.


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.# Nokia Siemens NetworksRA41126EN05GLA0CA Subject nameThis parameter identifies the CMP server by its subject name. It may either be detected by DHCP upon autoconnection or configured by the management system.CA certificate and trust anchorThis parameter specifies how many days before a CA certificate or Trust Anchor certificate expires the BTS autonomously triggers a CMP update sequence.BTS certificateThis parameter specifies how many days before a BTS certificate expires the BTS autonomously triggers a CMP update sequence.CRL update intervalThis parameter specifies the period for executing a periodical update of the Certificate Revocation List. The value is given in hours. Value 0 means "no periodical update".

RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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. # Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#

Ethernet Switching with FTIB 1/2The 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 ModeIn VLAN-PCP Mode, the mapping to a queue is based on the VLAN priority (07).# Nokia Siemens NetworksRA41126EN05GLA0Ethernet switching in use:Queue weights: 1...8Qos classificationModeDSCPPriority queue for non-IP framesDSCP to priority queue mapping: queue 1..3VLAN aware configurationSwitch modeMAC Address:VLAN IDKeep untagged framesVLAN ID listEthernet interface shaperEgress shaper rate:

Ingress rate limiting:

Speed and duplex:RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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 eNodeBs own traffic. # Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#

Ethernet Switching in DSCP Mode with FTLB 1/2The QoS aware Ethernet switching function supports 6 queues in FTLB. The queue weight is configurable in the range 1...8.# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#

Ethernet Switching in DSCP Mode with FTLB 2/2If 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.# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Ethernet Switching capabilities FTIB vs. FTLBEIF 1EIF 2EIF 3EIF 1EIF 2EIF 3

FTIBFTLBTo FSMxTo FSMx# Nokia Siemens NetworksRA41126EN05GLA0FTIB can perform Ethernet switching either between EIF 1 and EIF 3 or between EIF 2 and EIF 3.FTLB can switch Ethernet packets from any EIF to any other EIF.RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Ethernet OAM

Ethernet CoreEthernet Link OAMEthernet Service OAMeNodeBNode supporting Ethernet link OAMNodes supporting Ethernet Service OAMeNodeB# Nokia Siemens NetworksRA41126EN05GLA0Link OAM: Introduction to 802.3AH OAMas specified in IEEE 802.3ah-2004 Clause 57. 802.3ah OAM is implemented on any full-duplex point-to-point or emulated point-to-point Ethernet link. The frames (OAM Protocol Data Units or OAMPDUs) cannot propagate beyond a single hop within an Ethernet network and have modest bandwidth requirements (frame transmission rate is limited to a maximum of 10 frames per second).The major features covered by this protocol are:DiscoveryLink MonitoringRemote Fault DetectionRemote Loopback

Service OAM: Introduction to Connectivity Fault Management (IEEE 802.1AG)Connectivity Fault Management ProtocolsEthernet CFM comprises three protocols that work together to help administrators debug Ethernet networks. These are: continuity check, link trace and loopback protocols. Continuity Check These are heartbeat messages issued periodically by maintenance endpoints. They allow maintenance endpoints to detect loss of service connectivity amongst themselves. They also allow maintenance endpoints to discover other maintenance endpoints within a domain, and allow maintenance intermediate points to discover maintenance endpoints. Link Trace These are transmitted by a maintenance endpoint on the request of the administrator to track the path (hop-by-hop) to a destination maintenance endpoint. They allow the transmitting node to discover vital connectivity data about the path. Link trace is similar in concept to UDP Traceroute. Loopback These are transmitted by a maintenance endpoint on the request of the administrator to verify connectivity to a particular maintenance point. Loopback indicates whether the destination is reachable or not; it does not allow hop-by-hop discovery of the path. It is similar in concept to ICMP Echo (Ping).RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Ethernet Link OAM

# Nokia Siemens NetworksRA41126EN05GLA0A detailed example setup Ethernet Link OAM is described in eNodeB OAMRA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Ethernet Service OAM

# Nokia Siemens NetworksRA41126EN05GLA0A detailed example setup of Ethernet Service OAM is described in eNodeB OAM

RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#IP Interfaces User Plane GBR admission control

# Nokia Siemens NetworksRA41126EN05GLA0TAC settings Define the settings for Userplane Guaranteed Bit Rate (GBR) admission control. TAC (Transmission Admission Control) gives the possibility to restrict the admission of guaranteed bit rate (GBR) connections served by an eNB. RAC and TAC together form the eNB CAC. Decision to accept or reject a connection is done only at the moment it is requested. The expected transport bit rate of the new connection is added to the aggregated values of currently active GBR connections before making the admission decision.

Exclude layer 2 overhead in calculations Select the Exclude layer 2 overhead in calculations check box if you wish to exclude layer 2 overhead. When set, the transport bandwidth is calculated only for layer 3 (excluding Ethernet and VLAN overhead) in order to support transport networks which provide guaranteed bit rate on layer 3 only.

Overbooking activity factor Enter the overbooking activity factor in the Overbooking activity factor field. The activity factor allows overbooking - it compensates periods of silence. It applies for all connection types (normal, HO, emergency) and for both directions (UL, DL).A value of zero means no TAC and all calls can be accepted from transport point of view.

Limit for normal GBR connections Enter the limit for normal GBR connections in the Limit for normal GBR connections field.

Limit for GBR handovers Enter the limit for GBR handovers in the Limit for GBR handovers field.

Limit for GBR emergency connections Enter the limit for GBR emergency connections in the Limit for GBR emergency connections field.

Average packet size for QCI value 2 Enter the average packet size for QCI value 2 in the Average packet size for QCI value 2 field.

Average packet size for QCI value 3 Enter the average packet size for QCI value 3 in the Average packet size for QCI value 3 field.

Average packet size for QCI value 4 Enter the average packet size for QCI value 4 in the Average packet size for QCI value 4 field. RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#

IP Interfaces Untagged interfaceIs 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.# Nokia Siemens NetworksRA41126EN05GLA0Transport Ethernet interface The parameter area displays the parameters for Transport Ethernet interface. Select an object/item in the tree to view its parameters. Address IP address of the Transport Ethernet interfaceSelect the traffic shaping type value from the Traffic shaping type drop-down list. Total shaper information rate This parameter holds the total Shaper Information Rate (SIR) at the output of the WFQ aggregator. Total shaper burst size Total Shaper Burst Size (SBS) defines the maximum burst size that is allowed to pass at the output of the WFQ aggregator.

Shaper information rate

Shaper burst size

WFQ scheduler queue weight

Enable QoS Select the Enable QoS check box to enable Quality of Service monitoring.Note: QoS has to be enabled for one IP interfaceInclude Ethernet overhead Select the Include Ethernet overhead to take Ethernet overhead into account. MTU

RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#IP Interfaces VLAN interface# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#allSIR/SBSTransport Ethernet / VLAN QoSSIR/SBSOverallWFQegressWFQSPallallallOverallShaperSIR/SBSSIR/SBSSIR/SBSStandard IP routing on IP destinationUserCtrlMgmtSyncabcdfghijApplication planesApplication IP AddressesInterface IP AddressesExpedited ForwardingAssured Forwarding 4Assured Forwarding 3Assured Forwarding 2Assured Forwarding 1Best EffortUser-defined Queue weightsWeighted Fair Queuing Scheduler / Strict PriorityQoS EnabledQoS DisabledQoS DisabledQoS DisabledQoS Disabledindividual ShapingTraffic Shaping Type: Pathoverall VLAN ShapingTraffic Shaping Type: WFQShaper Information RateShaper Burst SizeTotal Shaper Information RateTotal Shaper Burst SizeNote: 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# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#IP Interfaces VLAN interface

# Nokia Siemens NetworksRA41126EN05GLA0VLAN ID The parameter area displays the parameters for VLAN ID. Select an object/item in the tree to view its parameters.

VLAN ID Enter the VLAN ID in the VLAN ID field.

Address Enter the VLAN IP address in the Address field. Enter also the netmask bits.

Shaper information rate Enter the shaper information rate in Mbit/s in the Shaper information rate field.

Shaper burst size Enter the shaper burst size in octets in the Shaper burst size field.

WFQ scheduler queue weight Enter the WFQ scheduler queue weight in the WFQ scheduler queue weight field.

Enable QoS Select the Enable QoS check box to enable Quality of Service monitoring.

RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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.# Nokia Siemens NetworksRA41126EN05GLA0Functional descriptionBidirectional Forwarding Detection (BFD) is a link supervision protocol which allows to detect faults between two forwarding engines connected by a link. BFD can be used as a component in a link redundancy protection scheme, because it permits detection of a link failure to the respective BFD peer. The Bidirectional Forwarding Detection (BFD) protocol defines a method for liveness detection of network paths. The BFD single-hop is used across single network hops. BFD can also be useful on paths, which may span multiple network hops and follow unpredictable paths. Furthermore, a pair of forwarding engines may have multiple paths between them that may overlap. In these cases the multi-hop BFD is used.Note: BFD sessions are to be confiured to routers (gateways) when fast IP re-routing is usedRA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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 PlaneManagement PlaneInternet Control Message ProtocolInternet Key ExchangeBi-directional Forwarding DetectionSite Support Equipment# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Recommended Differentiated Services Code Points (DSCP)Assured forwarding classPer Hop BehaviorDrop PrecedenceDSCPPHBDrop PrecedencebinarybinarydecimalExpedited Forwarding10111046431001103842100100364110001034330111103032011100283101101026230101102222010100202101001018130011101412001100121100101010Best Effort0000000# Nokia Siemens NetworksRA41126EN05GLA0source: http://tools.ietf.org/html/rfc2597

RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Application Addresses

# Nokia Siemens NetworksRA41126EN05GLA0Commissioning - Application Addresses In the Commissioning - Application Addresses and Create Commissioning File - Application Addresses pages you can configure application addresses for different planes. Application addresses are virtual addresses and plane addresses can be configured to the same value as network interface IP addresses. All plane addresses must be configured. Select same IP interface for all planes Select the same IP interface for all planes from the Select same IP interface for all planes drop-down list if required. User plane This is the eNodeB IP address seen from the S-GWControl plane This is the eNodeB IP address seen from the MMEManagement plane This is the eNodeB IP address seen from the iOMS, NetAct or remote BTS Site ManagerSynchronization plane This is the eNodeB IP address seen from the ToP (Timing over Packet) clock master.

RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#RTT measurement 1/2

# Nokia Siemens NetworksRA41126EN05GLA0Functional DescriptionWith this feature, an active measurement is done between two points in the mobile backhaul. One point performs test traffic generation and analysis. The other point must be able to send back the test traffic. The purpose of the measurement is to have an estimation of the quality and performance of the IP-based mobile backhaul for each QoS class independently, indicated by Diff Serv Code points.In detail- The eNB provides Two Way Active Measurement Protocol (TWAMP) Sender functionality according to RFC5357. The received packets need to be analyzed and used for statistics whether the responding partner is capable to generate a TWAMP Response message or whether it returns the sent message un-modified (UDP echo server).- The eNB provides TWAMP Responder functionality so that a supporting router in the network could use TWAMP test traffic to measure the connection from there towards the eNB. Up to 10 simultaneous measurement sessions can be started on the eNB. The sessions can be used to get measurements on different QoS classes. Once started, the measurements are gathered forever or till the measurements are explicitly stopped. The measurements are aggregated into PM counters that are uploaded every 15 minutes. If the network condition falls under a configurable threshold, alarms will be raised.Measured values are- Round-trip time (RTT, presented as Maximum, Minimum and Average Packet Delay)- Packet Loss Ratio- In case of TWAMP responses additionally- One way delay variation- One way packet lossRA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#RTT measurement 2/2

# Nokia Siemens NetworksRA41126EN05GLA0Two-way Active Measurement Protocol (TWAMP), http://tools.ietf.org/html/draft-ietf-ippm-twamp-09

twampMessageRate (TWAMP initiator rate for sending messages)This parameter specifies the overall rate at which the BTS sends TWAMP initiator messages. The messages are evenly spread over the enabled TWAMP sessions at any given time.twampFlag (TWAMP reflector and udp echo flag indicator)This struct handles the enables/disables the TWAMP reflector and UDP echo functionality for the each application and IP interface object. This can have a maximum of 10 instances as per configured addresses.twampReflectorPort (TWAMP reflector port number)This parameter specifies the source port that is assigned to the TWAMP reflector. The sender on any measurement request packet shall use that port to reach the TWAMP reflector.


Activate IPsec and choose a profileCheck 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.# Nokia Siemens NetworksRA41126EN05GLA0Commissioning - IP Security Policies In the Commissioning - IP Security Policies and Create Commissioning File - IP Security Policies pages you can define IP security options. Note that FTIB does not support IP security in RL10. IPSec in use Select the check box to enable IP security processing in node. Policy Select Policy to see all Ipsec policies in one table. Select one policy item in the tree to see and manage parameters of that policy. Parameters are shown in the parameter area next to the tree. RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#IPSec tunnelIPSec tunnelIPSecGatewayLocal IP addressFor 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 addressThis 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 addressLocal IPSec tunnel IP addressRemote IPSec tunnel IP addressRemote IP address

eNodeB# Nokia Siemens NetworksRA41126EN05GLA0Supported IPsec capabilitiesServices Data integrity protection, origin authentication and anti-replay protectionProtocol ESP (RFC 4303)Transport Tunnel modeConfidentiality mandatoryEncryption/Ciphering 3DES-192-CBC, AES-128-CBC and NULLModes: CBC, random chosen IVIntegrity HMAC-MD5, HMAC-SHA-1-96Identification: IP addresses and Fully Qualified Do-main Names (FQDN) are supported for identificationAuthentication Digital certificates in X.509v3 format Key exchange: dual stack IKEv1 (RFC 2409) / IKEv2 (RFC 4306) Key Management: ISAKMP (utilizes IKEv2 for key exchange)Diffie-Hellman key exchange Group 2 (1024-bit MODP)RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Ipsec settings 1/4

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.# Nokia Siemens NetworksRA41126EN05GLA0Policy order number Enter the policy order number in the Policy order number field. The smaller the order number is the more highly valued is the policy. IPsec action Select the IPSec action from the drop-down list. Bypass-setting does not process any packets, Discarded-setting does not forward any packets. Protected-setting follows the IPsec process. Local IP address Enter the local IP address in the Local IP address field. Enter also the address netmask bits. You can either define this address yourself by selecting the Define address radio button (empty value means any address - whole range of addresses) or choose the address from the drop-down list if you select the Select application address option. Local port Enter the local port number in the Local port field. Empty value means any port - whole range of ports.


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.# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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 GatewayThis is the encryption method used for the Key exchange.This is the Encapsulated Security Payload encryption method used for IPSec.# Nokia Siemens NetworksRA41126EN05GLA0Nokia Siemens Networks suggestion on IPsec configuration IPSec implementation is optimized to provide best throughput and strongest security level when using ESP encapsulation with AES-CBS (128 or 256 bit key size) ciphers together with SHA-1 HMAC algorithm. There is no significant performance / throughput difference between AES-CBC-128 and AES-CBC-256, but 3DES is ignorantly slower than any AES algorithms, and because of this should be avoided when possible.


IKE version V1IKE version V2 DPD (Dead peer detection) with Internet Key ExchangeInternet Key Exchange protocol versions# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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.# Nokia Siemens NetworksRA41126EN05GLA0ISAKMP SA and the IPsec SA(s) are regularly updated, the ISAKMP SA life time is set to 24 hours/86400 sec and the IPsec child SA(s) lifetime is adjustable from 5 Minutes/300 sec up 24 hours/86400 sec, common for all IPsec child SA(s).


SynchronizationMaximum 2 Timing Sources can be configured. First Prority 1 must exist before selecting Priority 2.Avalable TypesE1 interface, if previously set in use.Synchronous EthernetTiming over Packet, if previously configured.Priority 3 is fixed to Internal clock.


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.# Nokia Siemens NetworksRA41126EN05GLA0Functional DescriptionLTE866 Fast IP Rerouting is an extension of LTE592 Link Supervision with BFD.The eNB sees two routers connected to it. A BFD session is running between the eNB and one router.Redirecting the downlink traffic:The primary route in the routing table of the router R1 is connected to the BFD session. If the BFDsession fails, the route is removed in the routing table of the router and the secondary route is selected(via R2).Redirecting the uplink traffic:The primary route in the routing table of the eNB is connected to the BFD session. If the BFD sessionfails, the route is removed in the routing table of the eNB and the next best route is selected (via R2).In conjunction with the feature LTE649 QoS aware switching the solution provides two physical linksto connect the eNB.


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.# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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.# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#

BTS Settings

# Nokia Siemens NetworksRA41126EN05GLA0Network synchronization modeWith this parameter the synchronization mode of the eNB can be selected.LTE systems supporting MBSFN or co-operate with CDMA 2000 system require a tight timing on air interface transmission synchronization. In all those cases Phase synchronization should be selected. For LTE systems which do not require such accurate phase synchronization, the 50ppb frequency accuracy has met via normal Frequency synchronization. For those that value should be set. Air frame timing as for 1PPS referenceDifferent systems could have a difference in the frame synchronisation to GPS PPS timing pulse. This parameter offers the possiblity to adjust freely an air interface timing as for 1PPS synchronisation pulse.Cable length between GPS and eNBThis parameter defines the length of cable used between GPS receiver and eNB (fixed length as meters). The NSN offcial cable with length 30 meter (471606A) or 100 meter (471653A) is used. If this parameter is set, the gpsTotalAntennaLineDelay shall not be set.Total GPS antenna line delayThis parameter shall be specified when NSN official cable (30m or 100m) is replaced with an own proprietary cable between GPS receiver and eNB. The maximum lenght of cable shall be less than 200 meters. In this case an operator has obliged to measure the delay of cable. If this parameter is set he value for gpsCableLength shall not be set.

RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Module Settings

# Nokia Siemens NetworksRA41126EN05GLA0Module The Module column displays the names of the modules, which are under the commissioning procedure. Profiling The Profiling column informs if the module supports climate control profiling or not. Possible options are Supported / Not supported. In use Select the In use check box to enable the climate control profiling. This option is available only if selected module supports climate control profiling. Profile Select the Profile from the drop-down list. This option is available only if selected module supports climate control profiling Possible choices are Optimized Cooling, Linear and Low Noise.


Cell Resources A-Type and I-Type

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Cell Resources H-Type

Note: All 3 cells ANT ports are shown at once.Cell 1: both ANT 1Cell 2: both ANT 3Cell 3: both ANT 5# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Concurrent Mode Settings

# Nokia Siemens NetworksRA41126EN05GLA0This parameter enables the RF sharing with GSM in LTE BTS. Parameter is used only for automatic licence activation and in addition this parameter is used for shared RF modules IP address configuration. This means that the Multi Carrier Power Amplifiers (MCPA) transmitting both GSM/EDGE RF and LTE RF carrier signals at the same 3GPP frequency band. When operating in RF sharing mode, a single RF Module is connected to 2 System Modules simultaneously. Flexi EDGE System Module is operating in GSM/EDGE SW mode and Flexi Multimode System Module in LTE SW mode. Both are connected to the one and same Flexi Multiradio RF Module.RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#3GPP Frequency Bands 1/2BandF Uplink loweUARFCNULlowF UplinkhigheUARFCNULhighF DownlinkloweUARFCNDLlowF DownlinkhigheUARFCNDLhighBW /MHzDuplexFreq.11920 180001980 185992110 02170 59960 190 21850 186001910 191991930 6001990 119960 80 31710 192001785 199491805 12001880 194975 95 41710 199501755 203992110 19502155 239945 400 5824 20400849 20649869 2400894 264925 45 72500 207502570 214492620 27502690 344970 120 8880 21450915 21799925 3450960 379935 45 91749.9 218001784.9 221491844.9 38001879.9 414935 95 101710 221501770 227492110 41502170 474960 400 NDL and NUL are earfcnDL and earfcnUL which are attributes of LNCEL.earfcnDL = 3050, earfcnUL = 21050FDL = 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:# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#3GPP Frequency Bands 2/2BandF UplinkloweUARFCNULlowF UplinkhigheUARFCNULhighF DownlinkloweUARFCNDLlowF DownlinkhigheUARFCNDLhighBandwidthDuplexFreq.111427.9 227501452.9 229991475.9 47501500.9 499925 48 12698 23000716 23179728 5000746 517918 30 13777 23180787 23279746 5180756 527910 -31 1478823280798233797585280768537910-3017704 23730716 23849734 5730746 584912 30 18815 23850830 23999860 5850875 599915 45 19830 24000845 24149875 6000890 614915 45 20832 24150862 24449791 6150821 644930 -41 211447.9 250501462.9 251991495.9 70501510.9 719915 48 331900 360001920 361991900 360001920 3619920 Tdd342010 362002025 363492010 362002025 3634915 Tdd351850 363501910 369491850 363501910 3694960 Tdd361930 369501990 375491930 369501990 3754960 Tdd371910 375501930 377491910 375501930 3774920 Tdd382570 377502620 382492570 377502620 3824950 Tdd391880 382501920 386491880 382501920 3864940 Tdd402300 386502400 396492300 386502400 39649100 Tdd# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#LTE Carriers

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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.# Nokia Siemens NetworksRA41126EN05GLA0Antenna Line DC voltageDefines if antenna line DC power is enabled/disabled for an antenna line. The DC power is enabled by default (when the file or parameter is not available for an AL). This parameter is the most relevant for AL DC power Note: The parameter can be changed on-line. To take the change into use, the radio module must be locked and unlocked or a BTS restart need to be initiated.RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#

AISG MHA Settings

AISG capable MHAs are detected automatically.Additional data can be added optionally.# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Antenna Line Settings

2 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). # Nokia Siemens NetworksRA41126EN05GLA0Additional Rx gainin decibels, is used in gain calculation to compensate a Rx gain produced by an external device e.g. the base station when two radio modules are cross-connected together via RX diversity outputs sharing the antenna line. User shall know the gain produced by the external device to apply proper value here. Note: an MHA/TMA gain shall not be included in this parameter. TheMHA/TMA gain is commissioned together with the MHA/TMA device commissioning and taken into account as default by the system.Uplink Delay in nanoseconds, is used to compensate the antenna line UL delay difference between main and diversity Rx branches of the cell. This is needed to avoid gain (i.e. performance) loss due to the time difference between Rx branches data. For example, offset of 1/2 chip period (130ns) introduces diversity gain degradation of about 1dB. Different delays are met e.g. when two radio modules are cross-connected together via RX diversity outputs. User may provide absolute UL delay values for all Rx branches of the cell, or optionally only the positive difference referred to the smallest delay branch and leave smallest delay branch value to zero. It's not required to apply the UL delay when the delay for Rx branches of the cell are about equal. Note: Multiradio Combiner (MRC) delay shall not be included in this parameter. The MRC delays are taken into account as default by the system when the Multiradio Combiner is commissioned into use.RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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.# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#RET Settings 1/2

Additional information type of data may be added as an option.# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#RET Settings 2/2

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#System Module External Fault and Control Settings

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Radio Module External Fault and Control Settings


Radio Network Configuration handling introductionRNW 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).


LNBTS LTE Node BTS Parameters

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#ADIPNO Adjacent IP Node:Primary IP address of main MME

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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.# Nokia Siemens NetworksRA41126EN05GLA0Control Plane IP address controlThe parameter determines whether the C-Plane IP address of the neighbor eNB (X2 link) is statically configured or whether eNB is allowed to update the address based on information provided by ANR procedures.

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.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.

RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#LNADJ LTE Node Adjacencies 2/2oamControlled 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.

# Nokia Siemens NetworksRA41126EN05GLA0Control Plane IP address controlThe parameter determines whether the C-Plane IP address of the neighbor eNB (X2 link) is statically configured or whether eNB is allowed to update the address based on information provided by ANR procedures.

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.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.RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Global eNodeB Id X2-link blacklist

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#GTPU MO Key Parameters

User plane Link supervision# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#SCTP MO Key ParametersControl plane supervisionNote 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.

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#LNCEL MO Key Parameters

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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.# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#

Send Parameters View Changes


Send Parameters View Parameters

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Send Parameters Online Mode

Send Parameters will update the BTS with the new configuration and restart the BTS (if required) to enable the changes.# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#

Initial BTS StateAll relevant commissioning parameters are set -> Send Parameters to the BTS.

Expected final BTS StateTransfer statusBTS Commissioning: Send Parameters


Verify Commissioning

# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#Integration# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#BTS Startup OverviewBTS InitialisingBTS UncommissionedBTS CommissionedBTS ConfiguredBTS Integrated BTS Test Dedicated StateBTS On AirCDM (SCF file does not exist/ SCF file invalid/ BTS re-hosted)SCF and RNW configuration file download and resetSTUP (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 resetPower ON / reset# Nokia Siemens NetworksRA41126EN05GLA0BTS status will not change to On Air until S1 Setup is successful with MME and at least one cell is enabled (unlocked and unblocked).RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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). # Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#SCTP Association EstablishmenteNB (Power On / Reset)MMESCTP: INITSCTP: INIT_ACKSCTP: COOKIE_ECHOSCTP: COOKIE_ACKSCTP: HEARTBEATSCTP: HEARTBEAT_ACKSCTP: HEARTBEATSCTP: HEARTBEAT_ACK...SCTP establishmentSCTP link supervision# Nokia Siemens NetworksRA41126EN05GLA0The initialization of an association is completed on both sides after the exchange of four messages. The passive side (called server, MME in S1 case) does not allocate resources until the third of these messages has arrived and been validated.MME receives an association setup request (an INIT chunk).From the request, MME generates all the values needed at its side to enter an established association and put into the so-called COOKIE. This COOKIE is returned to the sender of the INIT chunk in an INIT-ACK chunk.Upon reception of a COOKIE-ECHO chunk, MME unpacks the data contained in this COOKIE to verify whether it was the originator of this COOKIE.If it is a valid COOKIE, the MME will send a COOKIE-ACK to the eNBAfter all four messages have been exchanged, the SCTP association between MME and eNB is established and both are ready to exchange SCTP data (S1AP messages).eNB sends a HEARTBEAT messages to monitor the tranmission path. This message has to be acknowledged with HEARTBEAT_ACK.RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#S1 Setup ProcedureeNBMMES1AP: S1 SETUP REQUESTSCTP: SACKS1AP: S1 SETUP RESPONSESCTP: SACKeNB global ID, eNB name, supported TAs and Paging DRX configurationServedGUMMEI, Relative MME capacityGUMMEI: Globally Unique MME IdentityTA: Tracking AreaDRX: Discontinue Reception# Nokia Siemens NetworksRA41126EN05GLA0The S1 setup procedure shall be the first S1AP procedure triggered after the TNL association has become operational (after SCTP association establishment).The eNB initiates the procedure by sending a S1 SETUP REQUEST message including the appropriate data to the MME. The MME responds with S1 SETUP RESPONSE including the appropriate data.All S1 messages are treated as SCTP data, thus everytime either eNB or MME receives S1 message, it shall sends back selective acknowledge (SACK) chunk to its peer.RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#

Verify Integration# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#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 EquipmentDSCPDifferentiated Services Code PointE-OAM Ethernet OAMEM Element ManagereNB Evolved NodeBEPC Evolved Packet CoreETH EthernetETPExternal Transport Port (on FSMD/E)FCS Frame Check SequenceFM Fault ManagementFRMFlexi Radio ModuleFTM Flexi Transport ModuleGCIGlobal Cell IDID IdentifierIP Internet ProtocolL-OAM Link OAMLAN Local Area NetworkLB Loop BackLBM Loop Back MessageLBR Loop Back ReplyLMPLocal Management Port (on FSMx)LOS Loss Of SignalLTE Long Term EvolutionLTM 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 PointMMEMobility Management EntityMML Man-Machine LanguageMP Maintenance PointMRU Maximum Receive UnitMTU Maximum Transmission UnitOAM Operation, Administration and MaintenancePCIPhysical Cell IDPCP Priority Code PointPDU Protocol Data UnitPHBPer Hop BehaviorPM Performance MonitoringRDI Remote Defect IndicationRRHRemote Radio HeadS-OAM Service OAMS-GWServing GatewaySSESite Support EquipmentTACTracking Area CodeTLV Type, Length, ValueTTL Time To LiveVLAN Virtual LANX2IP interface between adjacent eNode BsXC Cross Connect# Nokia Siemens NetworksRA41126EN05GLA0RA41126EN05GLA0Flexi Multiradio LTE BTS Commissioning and Integration#[guard]

[guard]

[guard]

[guard]

[guard]

[guard]

[guard]

[guard]

ref

Balloon callout. Select shape and start typing. Resize box to desired dimensions. Move control handle to aim pointer at speaker.

Text

dpdtimeout

Peer

R-U-THERE

R-U-THERE

dpddelay

R-U-THERE

dpddelay

R-U-THERE

dpddelay

dpddelay

FTM raises DPD alarm, and deletes IKE and Ipsec SAs

dpddelay

FTM

R-U-THERE

dpddelay

R-U-THERE

R-U-THERE-ACK

dpddelay

R-U-THERE

R-U-THERE-ACK

Peer is alive

Peer is not alive

[guard]

[guard]

[guard]

[guard]

[guard]

[guard]

[guard]

[guard]

ref

Balloon callout. Select shape and start typing. Resize box to desired dimensions. Move control handle to aim pointer at speaker.

Text

t5

Peer

IKE INFORMATIONAL request

t2

dpddelay


t3


t6



t4

FTM raises DPD alarm,And deletes IKE SA and CHILD SAs

t1

FTM



dpddelay

IKE INFORMATIONAL response

dpddelay

IKE INFORMATION REQUEST

IKE INFORMATIONAL response

Peer is alive

Peer is not alive

parValueChangeInd( IKESA )

FAP

Documents

FMR LTE Commissioning & Integration