Installation instructions Product Family: Technical Support Solution (TSS)
Products: eNodeB settings for LTE Cell Trace
Confidential
© Nokia Solutions and Networks 2014
This material, including documentation and any related computer programs, is protected by copyright controlled by Nokia Solutions and Networks. All rights are reserved. Copying, including reproducing, storing, adapting or translating, any or all of this material requires the prior written consent of Nokia Solutions and Networks. This material also contains confidential information, which may not be disclosed to others without the prior written consent of Nokia Solutions and Networks.
Confidential
© Nokia Solutions and Networks 2014
Table of Contents 1.
FOREWORD .................................................................................... 5
2.
PREREQUISITE INFORMATION ..................................................... 6
3.
CONFIGURATION OF LTE ENODEB CELL TRACE....................... 7
3.1
Step 1: Reconfiguration of commissioning file ......................................... 7
3.2
Step 2: Activation of cell trace under LNBTS object ................................ 8
3.3
Step 3: Creation of CTRLTS object ............................................................. 8
3.4
Step 4: Setting CTRLTS-1 Properties ......................................................... 9
3.5
Step5: Setting CTRLTS object parameters................................................ 9
3.6
Step6: 3rd party trace reporting .................................................................. 9
3.7
Step7: Trace reporting mode ....................................................................10
3.8
Step8: Vendor specific extension tracing ................................................11
3.9
Step9: Adding MTRACE object ...................................................................11
3.10
Step10: Setting MTRACE object properties ............................................12
3.11
Step11: Setting MTRACE object properties ............................................13
3.12
Step12: MTRACE Cell vendor specific tracing .........................................14
3.13
Step13: MTRACE E-UTRAN trace identifier ..............................................14
3.14
Step14: Sending reconfiguration data to eNodeB .................................15
3.15
Use of copy MTRACE function ...................................................................16
3.16
Meaning of exclamation mark....................................................................17
4.
DISCLAIMER .................................................................................18
Confidential © Nokia Solutions and Networks 2014 LTE eNB Cell Trace Configuration Instructions v101
Contact: Contact your local Nokia Networks support
Change History Version 101
Status
Date
Comments
11-12-2014
Confidential © Nokia Solutions and Networks 2014 LTE eNB Cell Trace Configuration Instructions v101
1. FOREWORD In this document it is described how Cell Trace parameters are set to eNodeB via Site Element Manager. Print Screen pictures used in this document are taken from following SEM version. This document does not cover cell trace parameter configuration and activation via NetAct tools.
Picture 1: Used Site Element Manager Version
Confidential
© Nokia Solutions and Networks 2014
2. PREREQUISITE INFORMATION This document describes step-by-step instructions how to configure eNodeB to send cell trace data towards Message Collection Platform/Message Analysis Platform via Site Element Manager (SEM). Described steps in this document should be performed in presented order. Prerequisite information which is needed for configuration includes NetAct IP address, Message Collection Platform (server/pc) IP address and eNodeB Cell id’s. It is also recommended to check possible firewall settings in case firewall is located between eNodeB’s and Message Collection Platform server/pc. Firewall must be open for TCP/UDP traffic via port 49151. Also ensure that cell trace license is activated at eNodeB’s. Without a valid license it is not possible to activate cell trace. Operation of Message Collection Platform and Message Analysis Platform is controlled via license. In order to retrieve your license please be in contact with your local Nokia Networks contact.
Confidential
© Nokia Solutions and Networks 2014
3. CONFIGURATION OF LTE ENODEB CELL TRACE 3.1
Step 1: Reconfiguration of commissioning file
Picture 2: Cell trace activation parameter is available under LNBTS object. In case eNodeB is already in operational mode its configuration needs to be modified. Open SEM connection and choose Commissioning. Select Commissioning type Reconfiguration and press Next at the bottom of the page. Continue pressing Next button several times until window, presented in Picture 3, opens. In this SEM version wanted page is 32/36 but it may be something else. It may change in other SEM versions depending on technology and SW release in question. Remember to save original commissioning file in safe location.
Confidential
© Nokia Solutions and Networks 2014
3.2
Step 2: Activation of cell trace under LNBTS object
Picture 3: Cell trace activation parameter is available under LNBTS object. Cell trace is activated under LNBTS object by changing the status of Activate cell trace from false to true. This step can be performed as a first step of reconfiguration but can also be performed as a very last step when all needed parameters are set. Order really doesn’t matter since all parameters are sent towards eNodeB as a last step in the end of the commissioning.
3.3
Step 3: Creation of CTRLTS object
Picture 4: Adding CTRLTS object New CTRLTS object can be added by right mouse click over LNBTS object. Only one CTRLTS object per eNodeB can be added.
Confidential
© Nokia Solutions and Networks 2014
3.4
Step 4: Setting CTRLTS-1 Properties
Picture 5: CTRLTS object properties rd
It is important to check that value 49151 is set for 3 party tool trace port number. 49151 is the correct value when Message Collection Platforms MegaPlexer and/or L3DC for Traffica is used. User also needs to enter valid NetAct IP address here. Also OMS trace port number is set here.
3.5
Step5: Setting CTRLTS object parameters
Picture 6: CTRLTS parameters There are additional parameters under CTRLTS-1 object that needs to be configured. These are: • • •
rd
3 party trace reporting Trace reporting mode Vendor specific extension tracing ( from RL55/RL70 onwards)
Properties window will open when clicking selected parameter.
3.6
Step6: 3rd party trace reporting
Confidential
© Nokia Solutions and Networks 2014
rd
Picture 7: 3 party trace reporting-1 There are two properties that need to be configured: • •
rd
3 party cell trace reporting rd 3 party UE trace reporting
Both ones are set as true.
3.7
Step7: Trace reporting mode
Picture 8: Trace reporting mode-1 There are two properties that need to be configured: • •
Cell trace reporting mode UE trace reporting mode
Both ones are set as Online.
Confidential
© Nokia Solutions and Networks 2014
3.8
Step8: Vendor specific extension tracing
Picture 9: Vendor specific extension tracing-1 TA (timing advance) tracing can be set here on when status is set as true.
3.9
Step9: Adding MTRACE object
Picture 10: Adding new MTRACE object New MTRACE object can be added by right mouse click or by pressing New MTRACE button on the bottom of the page when CTRLTS object is selected. One MTRACE object needs to be created for each eNodeB cell from where cell trace needs to be forwarded onwards. If cell trace needs to be forwarded to e.g. two separate locations (servers and or pc’s) then two different MTRACE objects must be created for the cell. Please notice that maximum 12 MTRACE objects can be created per one eNodeB.
Confidential
© Nokia Solutions and Networks 2014
3.10 Step10: Setting MTRACE object properties
Picture 11: MTRACE object default values When new MTRACE object is added it will present factory default values (picture 11).
Confidential
© Nokia Solutions and Networks 2014
3.11
Step11: Setting MTRACE object properties
Picture 12: MTRACE object properties Under MTRACE one needs to configure several different parameters. • • • •
• •
Cell trace session identifier Accepted values 0…11. Max 12 cells supported. If eNodeB has e.g. 3 cells cell trace can be sent to 4 separate trace collection location. rd 3 party tool cell trace port number In Nokia systems default port is 49151 Cell identifier this value can be checked under LNBTS object (Picture 13). In case same cell trace is sent to several location Cell identified is same for all of them. Trace collection entity IP address here one needs to enter Message Collection Platform server/pc IP address. If cell trace data from one cell needs to be sent e.g. to two separate server/pc then each dedicated MTRACE object must be created for each server/pc. Trace RRC, S1 and X2 setting Available statues are: None, All and Special select All. If special is selected then also message category needs to be defined. Trace RRC, S1 and X2 msg category Available states for trace message category are: Empty, All, UEspecific and nonUEspecific.
Current version of this document doesn’t cover configuration of special cell trace measurements.
Confidential
© Nokia Solutions and Networks 2014
Picture 13: LTE cell configuration identifier
3.12
Step12: MTRACE Cell vendor specific tracing
Picture 14: MTRACE Cell vendor specific tracing MTRACE Cell vendor specific tracing is a parameter which describes whether tracing of instantaneous timing advance (TA) value on cell level as part of vendor specific extension is enabled or not.
3.13
Step13: MTRACE E-UTRAN trace identifier
Picture 15: E-UTRAN trace identifier E-UTRAN trace identifier is used to identify UE trace session and is a unique identifier to identify a trace session globally. This contains trace reference and trace recording session reference. • •
MCC MNC
Confidential
mobile country code mobile network code
© Nokia Solutions and Networks 2014
•
3.14
Trace ID Trace ID can be set as a same as cell id but when cell trace from one cell is sent to two or more separate server/pc Trace ID value must be unique within eNodeB one could give Trace ID 12033 for the first server/pc, 22033 to the second one and 32033 to possible third one.
Step14: Sending reconfiguration data to eNodeB
Picture 15: Sending reconfiguration data to eNodeB When all needed parameters are set and there is no exclamation mark visible anywhere one may press Next button in order to proceed commissioning. Save the reconfigured commissioning file for later usage and documentation purposes and send data to eNodeB. Sometimes eNodeB doesn’t make site reset but sometimes that will happen automatically. If site reset happens it will take some minutes until eNodeB is again in operational state.
Confidential
© Nokia Solutions and Networks 2014
3.15
Use of copy MTRACE function
Picture 13: MTRACE copy function Newly added MTRACE object can be used as a source for new MTRACE object. AT the bottom of the SEM one is able to find New, Delete, Copy and Compare buttons. When one uses copy function duplicate MTRACE object will be created. One needs to enter unique MTRACE id and change e.g. Cell id. If there is something wrong in the settings one is informed about it via exclamation mark icon. Normally this is related to missing MTRACE id and duplicate EUTRAN cell id.
Confidential
© Nokia Solutions and Networks 2014
3.16
Meaning of exclamation mark
Picture 13: MTRACE copy function If there is something wrong in the parameter settings one is informed about it via exclamation mark icon. During cell trace configuration this is normally related to missing MTRACE id and/or duplicate E-UTRAN trace identifier Trace ID.
Confidential
© Nokia Solutions and Networks 2014
4. DISCLAIMER The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is” and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia will, if deemed necessary by Nokia, explain issues which may not be covered by the document. Nokia correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © Nokia Solutions and Networks 2014. All rights reserved.
Confidential
© Nokia Solutions and Networks 2014
