SRAN17A Site Setup Guide v2.0

Setup Guide Guipan Yang RSO Team 01-11-2017

Content

•

•

•

•

•

•

SRAN17A Overview SRAN17A Harmonized object model SBTS17A Commissioning and Integration SBTS17A SW upgrade path SBTS17A Web Element Manager Offline SCF conversion from dedicated RAT BTS to SBTS17A

SRAN17A Overview

SRAN Highlights New SBTS Software

Single OAM

One base station for GSM, WCDMA and LTE radio technologies

Common handling in Netact, Simplified site creation, commissioning commissioning and config.

Based on Flexi Multiradio 10 And AirScale System Module

Supporting single radio all radio- and Transport SW upgrades upgrades

Common backhaul IP transport

System module sharing

One IP host and interface

Extremely compact sites

One IP address and IP security

Lower energy consumption

No external IP transport boxes

Scalable capacity

SRAN17A Network Architecture NetAct

NE3S/ HTTP

OSS OMS

BTS Mediator NWI3/ CORBA

MSC/VLR

HLR

GSM NSS

A SOAM

MSS

BSC

3G Voice Core IMS

Ab is IuCS

GSM UE Um IuB

MGW

RNC IuPS

WCDMA UE

PSTN

SGSN

PCS

GPRS

Uu

SBTS (eNodeB, NodeB, LTE-Uu BTS)

S1-U

GGSN

LTE UE (FDD-LTE/NB-IoT/LTE-M)

Internet S1-MME

SGW+PGW MME

EPC

SRAN 17A Release highlights • •

• •

• •

Higher Capacity Single RAN sites 3-RAT capability (GSM, WCDMA, FDD-LTE) in one system module 4-RAT site solution to enable TD-LTE Outdoor sub-rack AMOB

• • • •

Single BTS O&M unified architecture New BTS Mediator with resiliency New Web Element Manager Dedicated RAT to SBTS Migration Remote ALDs SW Mngt Enhanced security access control

•

• • • • • •

• • •

6T/6R Radio in 900 band (FXDD) 2T/2R Radio in 900J band (FHDI) Low power Radios (LTE/WCDMA) (FHGA)

• •

NB-IoT In-band/Stan In-band/Stand-alone d-alone support LTE-M support

Transport and Security • • • •

•

New configurations with flexible SRAN cell set approach RF Sharing and Chaining Support for selected fALU fALU LTE Radios Inter-eNB CA SBTS(FDD) – LBTS(TD) MORAN/MOCN/MOBSS MORAN/MOCN/MO BSS support 36 GSM TRXs GSM extended cell range

LTE-FDD 17A, WCDMA 17, GSM 17

This release and its listed features are still und er study, no commitment can be made at this point on the availability and s chedules.

Dynamic X2 and S1 Firewall configs Fronthaul Passive/Active WDM Extended synchronization capabilities Efficient transport of Small IP packets

SRAN16.x vs. SRAN17A OAM architecture What is changing?

Before •

After

NE3S interface in SRAN16.2/SRAN1 SRAN16.2/SRAN16.10 6.10 for m-plane

•

•

•

Single Sin gleRAN RAN BTS

NetAct

BTS Mediator converts SCF file (RAML format) to IM (binary format) In SRAN17A NE3S interface connects NetAct and BTS Mediator In SRAN17A SOAM interface connects BTS Mediator AND SOAM BTS SOAM BTS

SOAM interface

NE3S

SRAN16.x

BTS Mediator

SRAN17A

NE3S

NetAct

BTS Mediator Introduction •

• •

•

•

•

•

New network element introduced outside physical BTS Implements mediation function for BTS m-plane BTS Mediator (IMP) elementary functionality is to provide Info Model conversion from the SCF file (RAML format) into corresponding IMI format (binary representative) Converts format between NE3S and SOAM interface. NE3S (xml format) interface towards NetAct and SOAM (binary format) interface towards BTS Binary protocol on SOAM interface (BTS Mediator <-> SBTS) allows lower bandwidth thus higher capacity and synchronization speed BTS Mediator as SW entity is managed from NetAct as network element BTS Mediator is deployed as virtual machine in NetAct Data Center

NetAct NE3S agent NE3S interface Logical m-plane

BTS Mediato Mediato r Physical m-plane

SOAM interface

SBTS

SBTS

SRAN17A  Fro From m Pro Profil files es to Cel Celll Set Setss (SR (SR001 001581 581 New SRA SRAN N SBTS SBTS cel celll sets sets on FSM FSMF) F) SRAN 16.x

•

Fixed configurations described by profiles

•

Profile defines configuration on BTS level

•

•

Profiles have (too) detailed information about the maximum system module HW, radio HW setup, OBSAI cabling, baseband allocations, RAT multiplexing rules in the fiber.

SRAN17 onwards

Adopt „Cell Set” approach from LTE: •

•

Therefore even small configuration changes require new profile •

➢

Means additional test effort, often even coding effort.

➢

Limited number of configurations released, while hundreds are needed.

•

➢

Higher effort on site migration from legacy RAT to SRAN

•

Cell sets defined on sub-baseband module module level are combined as independent building blocks to build an SBTS configuration System module – Radio Module connection topology is auto detected. Commissioning rules, Baseband allocation and data routing are calculated based on detected topology New SRAN cell sets for shared operation (LTEWCDMA, LTE-GSM, GSM-WCDMA) and dedicated RAT operation for GSM and WCDMA are defined LTE and SRAN cell sets can be flexibly combined to build target configuration Much easier migration from single RAT to SRAN

SRAN BB cell sets and RF sets LTE

LTE cell set X

Full BTS level

LBTS

SRAN

SRAN cell set X

LTE cell set Y

LTE cell set X

LTE cell set Z

SRAN cell set Y

SBTS

Cell set level LTE cell sets

SRAN cell sets : Compatibility level of SRAN and LTE cell sets

BB cell sets

+ RF sets 1 1L2, 1L3, 1L4, 1L6, 2L3

+…+

RF sets n LTE RF cell cell set e.g : #2965_1z2 #2965_1z2

SRAN17A Harmonized object model

Harmon Har monize ized d Obj Object ect Mod Model el for SRA SRAN N and LTE – 1/3 Why? Motivation for Single OAM for fo r LTE & SRAN •

•

•

Lack of one and common architecture applicable for all technologies (no unification between them) SRAN own architecture is not seen as flexible enough (each new RMOD configuration causes new efforts) LTE modeling not future-proof enough to support both LTE technologies (TDD and FDD) and SRAN

•

Lack of information about installed vs configured HW

•

Maintenance of all architecutres separately is problematic

Goal •

The purpose of the change in the object model is to prepare it for the Single RAN and Single OAM compatibility. It means that model has to be consistent between all technologies supported by Single OAM software including 2G, 3G, 4G Macro, 4G Cloud and 5G technologies and products. In order to be able to reach it all part of the model have to be commonly defined for all of those technologies.

Harmon Har monize ized d Obj Object ect Mod Model el for SRA SRAN N and LTE – 2/3 Overall concept of transition towards harmonization MRBTS

MRBTS

LNBTS

…

LNCEL

EQM

LNMME

EQM_R

SMOD

MNL

RMOD

TNLSVC*

BTSSCL

LTE Object Model GSM Object Model WCDMA Object Model SRAN Object Model

LCELL

Equipment Object (Operators input) Runtime equipment Object (Detected by BTS) Management Network Layer object Transport Network Layer object*

LNBTS

LTE BTS object

WNBTS

WCDMA BTS object

GNBTS

GSM BTS object

Harmon Har monize ized d Obje Object ct Mod Model el for SRA SRAN N and LTE – 3/3 SBTS (SRAN16.10) SRAN17A Object model is common for SRAN17A and LTE17* Root object is MRBTS (in SRAN16.2/SRAN16.10 it was SBTS) EQM – configuration HW information Object model is extended in HW configuration area where additional information is included to fully reflect running SBTS configuration e.g.: EQM_R – runtime HW information CABLINK / LOGLINK – physical / logical information •

• •

LNBTS object consists LTE eNB parameters similarly as for SRAN16.2 and SRAN16.10. WNBTS and GNBTS consists local cell WCDMA/GSM configuration parameters (previously in BTSSCW/LCELW and BTSSCC/LCELCC) TNLSVC object consists transport parameters (for standalone LTE will be used in future releases)

Root changed

MRBTS (SRAN17A)

ALD

EQM

ANTL

EQM_R

BTSSCC BTSSCL

Object model changes

MNL

BTSSCW

TNLSVC

MGMNT

LNBTS

MHA

WNBTS

PSSUNT

GNBTS

RET SYNC TNL HW

*TNLSVC *TNLS VC for LTE LTE is scop scope e of LTE3 LTE3442 442 in future future release release

MO tree EQM and EQM_R EQuipment Management: •

EQM – configuration view Lists hardware configured by operator This part is not touched by SBTS

•

SBTS (SRAN16.10)

MRBTS (SRAN17A) EQM

EQM_R – runtime view Lists hardware detected by SBTS and can be updated dynamically during SBTS operations

Configuration View (CV)

HW

This part is filled by SBTS •

•

Configured hardware can appear in both (i.e. configured and runtime) objects e.g. RMOD and RMOD_R

Note: Corresponding CV and RV objects may have different ids, e.g. RMOD-1 may correspond to RMOD_R-15

EQM_R Runtime view (RV)

MRBTS (SRAN17A)

MO tree MNL MGMNT (SRAN16.10) AMGR

MNL MNLENT

Management Layer Entity

BBADM

Baseband Administration

CAPCFG

CAPADM Capacity Administration

CAPLIM

CELLMAPPING Cell Mapping

CERTH

CERTH

Certificate Handling Feature Common Administration

CLIC

FEATCADM

DNS

FMCADM

Fault Management Common Administration

EACA

PMCADM

Performance and Monitoring Common Admin

EACC

PMMNL

Performance Monitoring for MNL

MPLANE

SECADM

Security Common Administration

PM

SYNC

PMCADM

TEST

SECADM TRBLCADM

Synchronization

Tests Troubleshooting Common TRBLCADM Administration

MO tree MNL>MNLENT> MNL>MNLENT>SYNCH SYNCH MRBTS (SRAN17A) SBTS (SRAN16.10)

MNL

SYNC CLOCKOUTPUTS EXT2M

MNLENT SYNC CLOCK

GNSSE

GNSSE

PDH

GNSSI

SYNCE

PDH

SYNCHUBBTS

SYNCE

TOP

TOP

TIME

TIME

MO tr tree ee TN TNLL

MRBTS (SRAN17A)

SBTS (SRAN16.10)

TNLSVC TNL

Common transport configuration based on concept from SRAN16.2/SRAN16.10. One transport MOC for all Radio Access Technologies TNLSVC is also used for LTE if running on SRAN17A TNLSVC concept coming to „standalone“ LTE (non SBTS) with LTE3442 in future release

TNL ETHSVC

ETHSVC

FRLI

FRLI

IPAPP

IPAPP

IPNO

IPNO

P3LP

P3LP

P3ML

P3ML

P3SL

P3SL

PPTT

PMTNL

TRIGGER

PPTT TRIGGER TNL_R

MO tree MNL – local cell remodeling – 1/2 •

Object Model changes ( x17) – relevant LCELx subtree

MNL/MNLENT CELLMAPPING contains mapping between logical cells (LNCEL/WNCEL/GNCEL) and hardware (RMOD/ANTL) in the form of LCELx

CELLMAPPING LCELx

CHANNELGROUP CHANNEL

In case case of a normal normal cell: cell: 1 CHANNELGROUP instance per normal cell In case case of a superce supercellll (LTE relat related ed only): only): 1 CHANNELGROUP instance per subcell

A CHANNEL CHANNEL instance instance repre represents sents a data path. There The re is one CHA CHANNE NNEL L ins instan tance ce per antenn ant enna a lin line e and per direc directio tion n

MO tree MNL – local cell remodeling – 2/2 •

Object Model changes ( x17) – relevant LCELx subtree

…

… CHANNELGROUP

CHANNEL

•

used d ins instea tead d antlId antlDN use

LCELL/C/W

channelGroupId

Subcelll rel Subcel relate ated d par parame ameter terss at one one pla place: ce: As CHANNELGROUP CHANNELGROUP represents represents a subcel sub celll in cas case e the cel celll is a supe superce rcell, ll, used d in inste stead ad of channelGroupId is use subCellId

•

channelId antlDN direction

struct resour struct resourceLis ceListt { subCellId, antlId, txRxUsage } repeaterDelay

shif ifte ted d to repeaterDelay is sh RMOD/ANTL

txRxUsage removed used d ins instea tead d direction use can n be se sett to ei eith ther er TX or RX bu butt no nott to to direction ca TXRX, there therefore fore for each resour resourceLis ceListt with txRXUs txR XUsage age == TXRX, TXRX, two CHA CHANNE NNEL L instances instances hav have e to be cre create ated, d, one wit with h dir direc ectio tion n = TX, and one wit with h

LTE and SRAN17A For LTE eNB can be: •

As standalone LTE17 (no (non n SBTS) SBTS) BTS -

HW info (SMOD,RMOD…) located in • •

•

-

MRBTS/MNL/MNLENT/CELLMAPPING/LCELL

•

•

MRBTS/MNL/MNLENT/CELLMAPPING/LCELL

Transport generic parameters located in SingleOAM BTS object model •

-

MRBTS/EQM/APEQM/RMOD MRBTS/EQM/APEQM/CABINET/SMOD MRBTS/EQM/APEQM/CABINET/BBMOD

Local cell info (LCELL…) located in •

-

eNB

WBTS17

BTS

HW info (SMOD,RMOD…) located in •

-

BSC

MRBTS/LNBTS/FTM

As part of SRAN17A BTS -

RN C

Transport info (TNL…) located in •

•

BTS MED MED

Local cell info (LCELL…) located in •

-


MRBTS/TNLSVC

Transport LTE specific parameters located in SingleOAM BTS object model •

MRBTS/LNBTS/TRSNW

SRAN17A

MO tree LNBTS and child MOCs changes – remodeling 1/3 •

•

In the LNBTS and LNCEL MOCs new param parameters eters are added in xL17 to define technology technology used for the particular particular cell These new parameters are a first step of introduction multiLTE229 2294 4 FDD technology support coming in release 17A with LTE TDD Coexistence within one (logical) eNB functionality

MRBTS EQM EQM_R MNL

MRBTS LNBTS LNCEL

LNBTS supportedCellTechnology

LNCEL CellTechnology


As a consequence of technology distinguish in LNBTS and LNCEL MOCs some parameters are moved to new dedicated MOCs (_FDD and _ TDD postfix respectively) -

Parameter that are exclusive in FDD or TDD are moved to LNBTS_FDD or LNCEL_FDD resp. LNBTS_TDD or LNCEL_TDD

-

Parameter which are from range and / or inter-parameter relation extreme divergent or belonging to a set of parameter for one functional configuration (e.g. MIMO) are moved to LNCEL_FDD resp. LNCEL_TDD

LNBTS supportedCellTechnology

‚FDD’ or ‚TDD’ only in xL17, starting from 17A ‚FDD’ or ‚TDD’ or ‚mixed_FDD_TDD mixed_FDD_TDD*’ *’

LNBTS_FDD LNBTS _FDD LNBTS_TDD LNBTS_ TDD LNCEL CellTechnology

LNCEL_FDD LNCEL _FDD LNCEL_TDD LNCEL _TDD

‚FDD’ or ‚TDD’


Similar rules as for LNCEL LNCEL apply per MO LNCEL childs -

Techno Tec hnolog logyy spe specif cific ic class classes es are are relate related d to the cor corres respon pondin ding g techno technolog logyy cell cell

-

For commo common n classes classes in wider wider parts parts differe different, nt, the the classes classes will will become become technolog technologyy specific specific (->APU (->APUCCH, CCH, MPUCCH MPUCCH))

… LNCEL

LNCEL_FDD LNCEL _FDD MPUCCH_FDD MPUCCH _FDD APUCCH_FDD APUCCH _FDD LNCEL_TDD LNCEL _TDD MPUCCH_TDD MPUCCH _TDD APUCCH_TDD APUCCH _TDD

WCDMA and SRAN17A For WCDMA WBTSs can be: •

As standalone WBTS17 -

WCDMA Radio parameters and HW info, local cell info, transport parameters located in WBTS under RNC HW info (SMOD,RMOD…) located in •

•

-

Local cell info (LCELW, LCELGW…) located in •

•

•

WBTS/MRBTS/SMOD WBTS/MRBTS/RMOD

WBTS/MRBTS/BTSSCW/LCELW WBTS/MRBTS/BTSSCW/LCELGW

BTS MED

RN C

As part of SRAN17A BTS -

Similar as for SRAN16.x WBTS17 WCDMA Radio parameters are still located in WBTS under RNC WCDMA HW info, local cell, transport parameters info is now defined in SingleOAM BTS object model HW info (SMOD,RMOD…) located in SingleOAM BTS object model •

•

•

-

Local cell info (LCELW, LCELGW…) located in SingleOAM BTS object model •

•

-


MRBTS/WNBTS/WNCEL MRBTS/WNBTS/WNCELG

Transport located in SingleOAM BTS object model •

MRBTS/TNLSVC

BSC eNB

BTS

SRAN17A

MO tre tree e WNB WNBTS TS •

Object Model changes (compared to WCDMA16) – moved parameters

MRBTS(SRAN17A)

MRBTS(WBTS16)

WNBTS BTSSCW

numberOfCCCHSet numberOfHSDPASet1 numberOfHSDPASet2 numberOfHSDPASet3 numberOfHSUPASet1 ….

LCELW

LCELGW

maxCarrierPower resourceList hspaSetting …

WNCEL WNCELG WNPMRNL MNLENT CELLMAPPING LCELW CHANNELGROUP CHANNEL

GSM and SRAN17A For GSM BCF can be: •

As standalone BCF -

GSM Radio parameters and HW info, local cell info, transport parameters located in BCF under BSC HW info (SMOD,RMOD…) located in •

•

-

BTS MED

Local cell info (LCELC…) located in •

•

BCF/MRBTS/SMOD BCF/MRBTS/RMOD

BCF/MRBTS/BTSSCC/LCELC

RN C

As part of SRAN17A Singl SingleOAM eOAM BTS -

Similar as for SRAN16.x GSM Radio parameters are still located in BCF under BSC WBTS17 BTS object model GSM HW info, local cell, transport parameters info is now defined in SingleOAM BTS HW info (SMOD,RMOD…) located in SingleOAM BTS • •

•

-

Local cell info (LCELC…) located in SingleOAM BTS •

•

-


MRBTS/GNBTS/GNBCF MRBTS/GNBTS/GNBCF/GNCEL

Transport located in SingleOAM BTS •

MRBTS/TNLSVC

BSC eNB

BTS SRAN17A

MO tre tree e GN GNBTS BTS •

Object Model changes (compared to GSM16) – moved parameters

MRBTS(SRAN17A)

MRBTS(GSM16)

GNBTS

BTSSCC

GNBCF LCELC BTSSCG

txPowerPooling perTrxPower ….

BTSNE bcfId bscId …

GNCEL CARRIERGROUPC_R

SBTS17A Commissioning and Integration

SBTS17A Commissioning and Integration •

The commissioning of SBTS17A is done by modifying and upload SCF xml file according to the need. Modify XML SCF to contain correct SBTS parameters (MRBTS ID, SMOD, BBMOD, RMOD, ANT, IP addresses, Cell ids, earfcn(s), etc …) and upload it to the SBTS.

SBTS17A Commissioning and Integration Important Parameters for SCF Creation ---Common parameters •

MRBTS-id

•

btsName

•

enbName

•

btsName is show up on Browser(WEB Element Element Manager). Manager).

•

enbName enbNa me is used for SCFC file file naming when when you want to save it.


•

FSMF config configuratio uration n --- BBMOD-i BBMOD-id, d, prodCod prodCodePla ePlanned, nned, SMOD-id SMOD-id,, prodCo prodCodePla dePlanned, nned, TRMOD, prodCodePlanned

AirScale configu AirScale configuration ration --- BBMOD-i BBMOD-id, d, prodCod prodCodePla ePlanned, nned, SMOD-id SMOD-id,, prodCo prodCodePla dePlanned, nned, positionInSubrack


RMOD-id, prodCodePlanned

•

ANTL-id, antPortId, vswrMajorThreshold, vswrMinorThreshold


RSL-id (every RMOD need to configuration one RSL)

•

CABLINK-id (physical link definition for RRU connection)

•

firstEndpointLabel, secondEndpointLabel

•

firstEndpointPortId, secondEndpointPortId


CABLINK-id (physical link definition for BB extension connection)

•

firstEndpointLabel, firstEndpointPortId, secondEndpointLabel

•

definition Note: Although AirScale BB communication used back panel, but it still need to definition the connection.

SBTS17A Commissioning and Integration Important Parameters for SCF Creation ---GSM Special parameters •

•

bcfId, bscId, mPlaneLocalIpAddressDN, mPlaneRemoteIpAddressOmuSig, sctpPortOmuSig GNCEL-id, lcelcId, perTrxPower

SBTS17A Commissioning and Integration Important Parameters for SCF Creation ---LTE&NB Special parameters •

LNBTS-id

•

mcc, mnc, mncLength

SBTS17A Commissioning and Integration Important Parameters for SCF Creation •

NB Special parameters

•

LNCEL-id,

•

cellTechnology,

•

grpAssigPUSCH,

•

lcrId,

•

nbIoTMode,

•

pMax,

•

phyCellId,

•

tac

•

ulRsCs



•

DRX-0

•

SDRX-0



•

NBIOT_FDD-0

•

dlChBw, dlMimoMode, maxCoverageMCL, nbIoTProfId, numCoverageLevels, standaloneEarfcnDL, standaloneEa rfcnDL, standaloneEar standaloneEarfcnUL, fcnUL, ulChBw



•

SIB-0



•

NBIOTPR-id, cpInactivity cpInactivityTimerNB, TimerNB, nprachCpLen,

•

cssProfNBNorCov, cssProfNBRobCov, cssProfNBExtCov

•

macProfNBNorCov, macProfNBRobCov, macProfNBExtCov

•

nprachProfNBNorCov, nprachProfNBRobCov, nprachProfNBExtCov

•

rachProfNBNorCov, rachProfNBRobCov, rachProfNBExtCov

•

rlcProfNBNorCov, rlcProfNBRobCov, rlcProfNBExtCov

•

schedProfNBNorCov, schedProfNBRobCov, schedProfNBExtCov


LTE Special parameters

•

LNCEL-id,

•

cellTechnology,

•

grpAssigPUSCH,

•

lcrId,

•

nbIoTMode,

•

pMax,

•

phyCellId,

•

tac

•

ulRsCs



•

DRX-0

•

SDRX-0



•

SIB-0

•

IFGDPR-0, LNCEL_FDD-0

•

dlChBw, earfcnDL, earfcnUL, prachCS, prachConfIndex, rootSeqIndex, ulChBw



•

MPUCCH_FDD-0, APUCCH_FDD-0


LNMME-id, administrativeState, ipAddrPrim, mmeRatSupport


PMRNL-1 (just check it, no need to change anything)


TRSNW-1

•

ipV4AddressDN1


LCELC-id, LCELL-id, LCELW-id, CHANNELGROUP-id

•

For example, the GSM has 3 local cells, every cell has 4 TRX.


GSM CELLMAPPING

•

CHANNEL-id, antlDN, direction


FDD-LTE or NB-IoT CELLMAPPING

•



WCDMA CELLMAPPING

•



cmpCrlSrcIpAddressDN, mPlaneIpAddressDN, oamPeerIpAddress, reportingIntervalPm,

•

actServiceAccountSsh, actServicePortState, ethernetPortSecurityEnabled

SBTS17A Commissioning and Integration Important Parameters for SCF Creation ---SYNC Special parameters •

btsSyncMode, sModDN, syncInputPrio, syncInputType

•

btsSyncMode: FreqSync, PhaseSync

•

syncInputTy syncInp utType: pe: - 1pp 1pps/To s/ToD D fro from m Sync Hub Hub Master Master - 1pp 1pps/To s/ToD D fro from m external external GNSS GNSS receiver recei ver - intern internal al GNSS GNSS receive receiverr - 2.048MH 2.048MHzz input input – TRS - 1pp 1pps/To s/ToD D from bac backpl kplane ane PDHPD H-1 1 - PD PDHH-2 2 - SY SYNCE NCE-1 -1 - SY SYNC NCE-2 E-2 – TOP TOPF F - TOP TOPP P


•

syncMaster, gnssCableLength, gnssControlMode, ntpServerIpAddrList

gnssControlMode: GPS only, GLONASS only, Beidou only, GLONASS-Beidou, GPSGLONASS, GPS-Beidou


sPlaneIpAddressDN, masterIpAddr, syncMessageRate, timeZone

SBTS17A Commissioning and Integration Important Parameters for SCF Creation ---TRS Special parameters •

VLANIF-id, ETHLK-id, connectorLabel, modDN


IPIF-id, interfaceDN, IPADDRESSV4-id, localIpAddr, localIpPrefixLength


IPRT-1, destIpAddr, destinationIpPrefixLength, gateway

SBTS17A Commissioning and Integration Important Parameters for SCF Creation ---WCDMA Special parameters •

identifier(“identifier” should match with IPBR ID in the RNC) , ipV4AddressDN, sctpPortMin, identifier(“identifier” sctpFarEndSubnetIpAddress, sctpFarEndSubnetPrefixLength


WNCEL-id, defaultCarrier, lCelwDN, maxCarrierPower, mimoType

•

WNCELG-id, cellGroupName, wncelIdList


WNPMRNL-1

•

If we have WCDMA technology, we need to add it.

SBTS17A Commissioning and Integration Open Web Element manager manager (ADMIN) by typing url: htt https://1 ps://192.1 92.168.2 68.255.1 55.129 29 in the brow browser ser Per default Username: Nemuadmin and password: nemuuser Click on Configuration Configuration Tab and select Parameter Editor Editor Choose load SCF and browse where prepared SCF is stored Wait NIDD validation Succeeded (if fails errors will be prompted describing the cause) Click on Deploy Click on Activate ( this will deploy SCF and activate it directly)

WEB Element Manager

WebEM Web EM for SBT SBTS S Introduction WebEM replaces BTS Site Manager Manager for SBTS Can be used both locally and remotely Works with a standard Web browser(Chrome prefer) No need to install additional SW on the client side New tool with modern user interface and high usability

• • • • •

http(s) SOAM

LTE

TRS SBTS

WCDMA

GSM

BTS Platform SW

SRAN Overview WebEM – SBTS View

SRAN17A SW Upgrade Path

SRAN17A Upgrade Path •

We have verified the upgrade path are as below:

•

FDSW1.3 can upgrade to SRAN17A directly verified

•

FL17A 3.1TD/4.0TDSRAN17A verified

•

SRAN16.2 3.0/SRAN16.10 3.0SRAN17A verified(still have pronto) –

MRBTS ID: SBTS::sbtsDescription SBTS:: sbtsDescription

–

BTSMED IP address: DNS::serverIpAddressSecondary DNS::serverIpAddressSecondary

•

WCDMA17 1.0SRAN17A not verify

•

GSM17 1.0SRAN17A not verify

Offline SCF conversion from dedicated RAT BTS to SBTS17A

Introduction Offline SCF conversion from dedicated RAT BTS to SBTS17A Feature scope Legacy RAT SCF (LTE, WCDMA, GSM)

Legacy SRAN SRAN16.2 SRAN16.10

RP001420 Offline SCF conversion

SBTS17 SCF

RP001062 SRAN 17 release upgrade from older SRAN releases

SBTS17 SCF

Introduction Offline SCF conversion from dedicated RAT BTS to SBTS17A FL16 (FSMF)

LTE

FL16A (FSMF)

FL17A (FSMF)

WCDMA GSM Under discussion

WBTS16 (FSMC/D/E/F) WBTS17 (FSMC/D/E/F)

GF16 (FSMF)

RP001420 Offline SCF conversion

GF17 (FSMF) LTE+GSM LTE+WCDMA GSM+WCDMA LTE+GSM+WCDMA

This includes also released Maintenance/Service SW Packages (MPx, SPx)

SBTS17A

Copyright and confidentiality

The contents of this document are proprietary and confidential property of Nokia. This document is provided subject to confidentiality obligations of the applicable agreement(s). This document is intended for use of Nokia’s customers and collaborators only for the purpose for which this document is submitted by Nokia . No part of this document may be reproduced or made available to the public or to any third party in any form or means without the prior written permission of Nokia. This document is to be used by properly trained professional personnel. Any use of the contents in this document is limited strictly to the use(s) specifically created in the applicable agreement(s) under which the document is submitted. The user of this document may voluntarily provide suggestions, comments or other feedback to Nokia in respect of the contents of this document ("Feedback").

Such Feedback may be used in Nokia products and related specifications or other documentation. Accordingly, if the user of this document gives Nokia Feedback on the contents of this document, Nokia may freely use, disclose, reproduce, license, distribute and otherwise commercialize the feedback in any Nokia product, technology, service, specification or other documentation.

are made in relation to the accuracy, reliability or contents of this document. NOKIA SHALL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT or for any loss of data or income or any special, incidental, consequential, indirect or direct damages howsoever caused, that might arise from the use of this document or any contents of this document.

Nokia operates a policy of ongoing development. Nokia reserves the right to make changes and improvements to any of the products and/or services described in this document or withdraw this document at any time without prior notice.

This document and the product(s) it describes are protected by copyright according to the applicable laws.

The contents of this document are provided "as is". Except as required by applicable law, no warranties of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose,

Nokia is a registered trademark of Nokia Corporation. Other product and company names mentioned herein may be trademarks or trade names of their respective owners.

SRAN17A Site Setup Guide v2.0

Recommend Documents