04_RA23104EN03GLA2_SRAN16_2_BTS_Commissioning_and_Integration.pdf

NokiaEDU Flexi Multiradio BTS SRAN Hands-on Delta Workshop for SRAN 16.2 NPI (Nokia Internal only)

Flexi SRAN BTS Commissioning and Integration RA23104EN03GLA2

© 2016 Nokia

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

2

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,

RA23104EN03GLA2

© 2016 Nokia

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.

Content

- SW upgrade from LTE/WCDMA to SBTS - Commissioning and Integration  SCF Migration – RAT Converter and RAT Merge Scripts  SCF creation - Manual

- Web User Interface for SBTS

4

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning Connecting to BTS locally Connect PC to BTS and use BTS Site Manager • IP settings for PC • PC IP address 192.168.255.126 • Subnet mask 255.255.255.0 (with /24 mask) • Gateway is not defined • Use BTS Site Manager to download SBTS SW • LTE/WCDMA BTS Site Manager • FDSW Site manager • Upgrade SW with BTS Site Manager (activate after SW update) • After SBTS restart in uncommissioned state • After SBTS restart LTE/WCDMA/FDSW cannot be used to connect locally to SBTS, only WebUI is usable • After restart connect to SBTS using web browser (WebUI tool) • Chrome preferred • Firefox • Internet Explorer 11 • https://192.168.255.1

5

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning Updating SBTS16.2 SW • SBTS runs on FSMF only • FSMF A102/3/4 and FBBC/FBBA are needed • SBTS 16.2 SW can be installed in FSMF System Module, which is currently running on:  LN7.0 and FL15A eNB SW  WN9.1 and WBTS16 SW  FDSW 1.1 (Factory Delivery SW)  From FDSW1.0 SW, follow path below FDSW1.0 -> RL70/WN9.1 (any version) -> SBTS16.2 SW Direct SW update from FDSW1.0 to SBTS16.2 is not possible due to restriction in Feature SR000913 SBTS Signed SW

6

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning How to identify FDSW SW?? • FDSW1.0 is identified from FSMF serial number  L1152205810  K9152820013  F7152526061  F4153700675  EA153052014  NK153000003 • FDSW1.1 is identified in the FSMF serial number  TY1542xxxxxxx  F41548xxxxxxx  F71542xxxxxxx

7

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning SBTS Software update from LTE Upgrade from LTE LN7.0 to SBTS is done as simple SW update in Site Manager

SBTS16 release package id is SBTS16_ENB_xxxx_yyyyyy_zzzzzz After Update and activation, the following message will appear: Press Exit

8

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning SBTS Software update After installation, BTS will be not accessible via site manger. But using a web browser and the address: https://192.168.255.1:8091/

The WebUI appears login interface appears Use Default Credentials to login: Username/Password : Nemuadmin/nemuuser nemuadmin/Nemuuser Supported web browsers for SRAN 16.2 are: Windows Google chrome, Internet Explorer and Firefox are supported

9

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning SBTS Software update The non commissioned and empty SBTS will look as figure – •For SRAN16 we used the package with A50 prefix •For SRAN16.2 we use the package with A53 prefix

To update SBTS SW, download the desired package

10

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning SBTS Software update On WEB UI interface, on Software file: Browse the local PC (1) where the Zip file of package is saved.

Check activate after download (2) and start update (3)

11

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning Using SCF Conversion script Supported Migration paths: • RL70, FL15A -> SBTS16.2 1.0 PCD2.2 • RU50 EP1, WBTS16 -> SBTS16.2 1.0 PCD2.2 • No GSM support for migration by the tool

The SCF Migration tool is delivered via NOLS

12

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning Using SCF Conversion script Preconditions – For Linux Terminal User has the SCF conversion script zip-file and it has been extracted to the hard drive of the PC Installation of Node.js Go to page https://nodejs.org/en/download/package-manager/ and follow instructions

1. Open terminal and download Linux binaries to your home directory. cd $HOME wget https://nodejs.org/dist/v4.4.0/node-v4.4.0-linuxx86. tar.xz tar -xJf node-v4.4.0-linux-x86.tar.xz

2. Now add node.js to your PATH cd node-v4.4.0-linux-x86/bin echo "export PATH=\$PATH:$PWD" >> ~/.bash_profile echo "export PATH=\$PATH:$PWD" >> ~/.zshrc

export PATH=$PATH:$PWD

13

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning Using SCF Conversion script

14

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning Using SCF Conversion script Preconditions – For Windows Terminal User has the SCF conversion script zip-file and it has been extracted to the hard drive of the PC

Installation of Node.js 1. Go to https://nodejs.org/download node.js (install button), and then install

15

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning Using SCF Conversion script 2. Install Visual C++ Redistributable for Visual Studio 2015.

Go to page https://www.microsoft.com/en-us/download/details.aspx?id=48145 and click download button. 3. Choose correct version for your system and click next. a. On 32-bit machine, choose 32-bit version (vc_redist.x86.exe). b. Important! On 64-bit machine, choose 32-bit version (vc_redist.x86.exe), 64-bit version does not work.

4. When download is finished, launch it and follow standard installation procedure.

16

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning Using SCF Conversion script To use conversion script you shall have following files stored in the same folder with script:

1. SBTS Profile (JSON file) · Profile shall be valid for the configuration you are planning to build · Supported SBTS Profiles can be found from SBTS SW packet from “profiles” folder. They are also separately delivered via NOLS. 2. Input SCF · FL15A, WBTS16, RL70 or RU50 EP1 level SCF file including (BTS and TRS parameters) which is used as input file for the script.

· SCF configuration file (e.g. used HW and cell configuration) shall match the selected SBTS Profile. · If you don’t have existing SCF you can create one (or modify existing) using FL15A, WBTS16, RL70 or RU50 EP1 level BTS Site Mgr.

17

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning Perform SCF Conversion 1. Open console and make sure that current working directory in your terminal is folder with the

script, e.g.

Test that script is working by printing the help menu with a command: node convert_scf.js --help

18

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning Perform SCF Conversion Example:

In this example, the WN9.1 level input SCF is “SCF_WN9.1_W_1.xml”. It’s matching with a SBTS Profile “W1_2.json”. Result SBTS16 level SCF shall have name “SCF_SBTS16_W_1.xml”. Following command shall be typed:

SBTS16 SCF will appear into the same folder with a conversion script.

In case you want to change SBTS ID to be different than eNB/WBTS ID was in source SCF you can give the new SBTS ID as an additional input for the script.

19

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning Perform SCF Migration and Merge 1. Open console and make sure that current working directory in your terminal is folder with the

script, e.g.

Test that script is working by printing the help menu with a command: node merge_scf.js --help

20

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning Perform SCF Migration and Merge Run the script using the proper command:

•

--input-lte-config is mandatory for each merge run

•

--input-wcdma-config or –input-gsm-config is mandatory with previous option for each run

•

--profile is mandatory for each merge run

•

--output is mandatory for each merge run

Example: Following command shall be typed:

21

RA23104EN03GLA2

© 2016 Nokia

SBTS commissioning SBTS configuration plan provisioning/SCF Creation Configuration provisioning with SBTS Element Manager (WebUI) • • • •

Select SBTS SCF using “Browse” Select BTS profile if not found Click “Start update” SBTS configuration plan is validated and activated The commissioning of SBTS is done by modifying and upload SCF xml file according to the need. Modify XML SCF to contain correct SBTS parameters (sbtsid, btsProfile, IP addresses, cell ids, arfcn(s), etc …) and upload it to the SBTS.

22

RA23104EN03GLA2

© 2016 Nokia

SBTS Configuration Parameters Example 10.88.20.222

10.88.4.226

NTP

ToP

BSC-6 OMU:10.31.232.4

SBTS40 Com MP/SP 2G 3G 4G

VLAN IP Addr. 421 10.31.224.1 422 10.31.224.65 423 10.31.224.129 424 10.31.224.193

FSMF FBBC FXDB FRGT

Opt2 Opt1

RNC-10

IP Cloud

OMU:10.31.197.1 OMS:10.88.1.185 mask 26 26 26 26

GW .62 .126 .190 .254

MME iOMS

G/W L G/L W

NetAct

23

RA23104EN03GLA2

© 2016 Nokia

IP Addr. 10.31.232.52 10.31.232.60 10.31.232.65 40 401/402/403 401/402/403 70/74/78

OMUSIG TRXSIG ETPE-1-0 BCF BTS CI ARFCN

ICSU subnet NPGE(P) IPNB min sctp wbts id Cid SAC PSC UARFCN MME SGW MCC MNC TAC eNB id PCI Lcr id eutraCelid CH BW Dlearfcn Ulearfcn

Mask 29 29 29

IP Addr. 10.31.197.64 10.31.197.41 40 50240 40 4001/4002/4003 6/7/8 123/124/125 10614

10.88.46.68 10.31.169.201 260 66 124 40 401/402/403 401/402/403 10241/10242/10243 5MHz 3500 21500

Port 49152 49153…

Mask 26 29

SBTS commissioning Important Parameters for SCF Creation

“sbtsName, sbtsId”

24

RA23104EN03GLA2

© 2016 Nokia


BTSSCL: Site Configuration for LTE Object btsName btsId==lnbtsId==sbtsId IP planned for LTE, U/C in the same vlan

25

RA23104EN03GLA2

© 2016 Nokia


“mPlaneIpAddress” Common management plane IP for 2G, 3G and LTE oamIpAddress once was IP for iOMS, now not used

LNBTS Object. LNBTS ID

enbName cannot have special character, like “_”, or the S1 setup will be rejected by MME in the reason “unknown eNB name”

26

RA23104EN03GLA2

© 2016 Nokia


MCC and MNC

27

RA23104EN03GLA2

© 2016 Nokia


LNCEL Object: LNBTS IDx256+LcrId, LcrId always 1,2,and 3, but BTS ID will always be different, so LNCEL will be different in the whole PLMN under NetAct

28

RA23104EN03GLA2

© 2016 Nokia


“pMax” power level PCI, Physical Layer Cell ID, 0-503, acting as Scrambling code in 3G, separate LTE cells.

TAC: Tracking Area Code, same as LAC/RAC, MME should include the same TAC

29

RA23104EN03GLA2

© 2016 Nokia


MME IP address, mandatory, for S1 setup request

Bandwidth and frequency number for DL/UL

The conversion between frequency number and absolute frequency can use ”ARFCN Calculator”

30

RA23104EN03GLA2

© 2016 Nokia


BTSSCW: Site Configuration for WCDMA wbtsId

31

RA23104EN03GLA2

© 2016 Nokia


sctpFarEndSubnetIpAddress and sctpPortMin==should match with RNC signaling subnet cPlane and uPlane IP address in same VLAN “identifier” should match with IPBR ID in the RNC

32

RA23104EN03GLA2

© 2016 Nokia


LCELGW: Managed object for WCEL

WCEL Id list

33

RA23104EN03GLA2

© 2016 Nokia


Define UARFCN , Power for WCEL

34

RA23104EN03GLA2

© 2016 Nokia

SBTS commissioning Important Parameters for SCF Creation BTSSCC: Site configuration for GSM BTS

mPlaneLocal/RemoteIpAddressOmusig to be matched with BSC SCTP Association

35

RA23104EN03GLA2

© 2016 Nokia


LCELC: Managed object for GSM cell

36

RA23104EN03GLA2

© 2016 Nokia


Synchronization setting: ToP Frequency is used

S Plane IP on BTS, the same as M Plane IP

ToP Server IP: 10.88.20.222

37

RA23104EN03GLA2

© 2016 Nokia


VLAN 421 for common MPlane and SPlane

VLAN 422 for GSM UPlane and CPlane

VLAN 423 for WCDMA UPlane and CPlane

VLAN 424 for LTE UPlane and CPlane

38

RA23104EN03GLA2

© 2016 Nokia


VLAN 421 for common MPlane and SPlane

39

RA23104EN03GLA2

© 2016 Nokia


40

RA23104EN03GLA2

© 2016 Nokia

SBTS commissioning GSM Integration parameters verification

41

RA23104EN03GLA2

© 2016 Nokia

SBTS commissioning WCDMA Integration parameters verification

42

RA23104EN03GLA2

© 2016 Nokia


43

RA23104EN03GLA2

© 2016 Nokia


LCELC: Managed object for GSM cell

44

RA23104EN03GLA2

© 2016 Nokia


45

RA23104EN03GLA2

© 2016 Nokia

SBTS WebUI

46

RA23104EN03GLA2

© 2016 Nokia

WebUI Introduction • SBTS WebUI replaces BTS Site Manager -

Legacy BTS SM cannot be used with SBTS SBTS WebUI cannot be used with legacy BTS

WebUI

• No new SW needed -

SBTS

Before SRAN BTSSM software was needed on client side

• Only web browser needed -

Chrome latest version available Internet Explorer 11 Firefox latest version available

local

• Managing SBTS as one entity

WebUI

• One view over all RATs -

View to RAT specific parameters View to common parameters

remote

• Local and remote usage possible For internal use 47

RA23104EN03GLA2

© 2016 Nokia

WebUI Functionality • SBTS Configuration • SBTS Software management WebUI

• SBTS Hardware/Software status view -

software status and version information

-

equipment view

• SBTS Fault/alarm state view

SBTS

local

• SBTS Snapshot creation, view, and file transfer • Initiation of off-line test and creation of test report

WebUI

• Multiple simultaneous WebUI sessions are possible

remote For internal use 48

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning with WebUI

For internal use 49

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning SBTS configuration plan provisioning Configuration provisioning with SBTS Element Manager (WebUI) • • • •

50

Select SBTS SCF using “Browse” Select BTS profile if not found Click “Start update” SBTS configuration plan is validated and activated

RA23104EN03GLA2

© 2016 Nokia

SBTS Commissioning SBTS Configuration editing with WebUI SBTS Configuration editing with WebUI • Parameters can be edited in Parameters tab • “Show only edited parameters” can be used to see summary of changes • To activate changes “Save Changes to SBTS” has to be selected • Depending on modified parameters SBTS need to be restarted • “Error/related parameters” section is used to show which parameters modification cannot be done

51

RA23104EN03GLA2

© 2016 Nokia

SBTS Composer UI

For internal use 52

RA23104EN03GLA2

© 2016 Nokia

Composer UI Functionalities Reconfigure • • • • •

Modifying existing parameters Adding new parameters Adding new MO classes Adding new RAT to a site Without changing the profile file

• During rollout to add new RAT to existing site

53

For Internal Use

Commissioning • Commissioning without technology specific files • Commissioning with partial SCF template • A profile file can be changed • During pilot or lab testing, no technology specific files available

RA23104EN03GLA2

© 2016 Nokia

Create file • Partial commissioning file can be available • All parameters can be entered manually • Template for rollouts exists, no site specific parameters defined • Partial file creation: RAT or TRS specific SCF file creation • Full file creation based on technology specific files • A profile file can be defined freely

SBTS Composer UI Reconfigure

Additional RATs can be selected

OPTIONAL: SCF with parameters related to additional RAT can be selected Group parameter can be selected

After edition parameters can be validated and new configuration can be activated

54

For internal use

RA23104EN03GLA2

© 2016 Nokia

Parameters can be edited after clicking ‘Show Parameters’

SBTS Composer UI Commissioning without existing SCF

BTS profile selection

RAT selection

Show and edit parameters


55

For Internal Use

RA23104EN03GLA2

© 2016 Nokia

SBTS Composer UI Commissioning with partial SCF


Existing SCF selection

Parameter groups selection


56

For Internal Use

RA23104EN03GLA2

© 2016 Nokia

Parameter edition

SBTS Composer UI Create file


Existing SCF selection

Parameter groups selection

After edition parameters can be validated and new saved

57

For Internal Use

RA23104EN03GLA2

© 2016 Nokia

Parameter edition

SBTS Composer UI Parameter view

58

For Internal Use

RA23104EN03GLA2

© 2016 Nokia

RA23104EN03GLA2

© 2016 Nokia

04_RA23104EN03GLA2_SRAN16_2_BTS_Commissioning_and_Integration.pdf

Recommend Documents