lte radio access, rel. rl40

LTE Radio Access, Rel. RL40, Operating Documentation, Issue 02

Guide to LTE Radio Access Operating Documentation

DN0986349

Issue 02Approval Date 2013-01-24

Confidential

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their compo-nents.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Siemens Networks for any additional information.

2 DN0986349


Id:0900d80580997b81Confidential

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 Siemens Networks 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 Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks 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 Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, 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.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2013. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-satzes.

DN0986349 3



Table of contentsThis document has 44 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Documentation for the LTE System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 LTE Radio Access Operating Documentation . . . . . . . . . . . . . . . . . . . . . 91.2 Flexi Multiradio BTS LTE Documentation . . . . . . . . . . . . . . . . . . . . . . . 101.3 NetAct Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.4 EPC Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.5 HSS Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Architecture of LTE Radio Access Operating Documentation . . . . . . . . 112.1 LTE Document List and Guide to LTE Radio Access Operating Documen-

tation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2 Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3 System Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.4 Functional Area Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.5 Feature Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.6 BTS and iOMS Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.7 Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.8 Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.9 Legal, Safety and Environmental Information . . . . . . . . . . . . . . . . . . . . 132.10 How to find Single RAN documentation. . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1 Language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2 Warnings, cautions, notes, and tips. . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3 Font conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.4 Command line conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4 Delivery timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.1 Documentation deliveries in the release development phase . . . . . . . . 204.2 Documentation deliveries in the release maintenance phase . . . . . . . . 20

5 Delivery channels and media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215.1 Online services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215.1.1 Product Information Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215.1.1.1 PIC search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.1.2 Care . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.2 Software-embedded documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.3 Documentation delivered on CD-ROM or DVD . . . . . . . . . . . . . . . . . . . 285.4 Documentation delivered with product hardware. . . . . . . . . . . . . . . . . . 28

6 Delivery formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296.1 Nokia Siemens Networks Electronic Documentation (NED) . . . . . . . . . 296.2 PDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.2.1 Downloading PDF files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316.2.1.1 Downloading a collection of single PDFs. . . . . . . . . . . . . . . . . . . . . . . . 316.2.2 Downloading a full PDF documentation set (ZIP-package) . . . . . . . . . . 33

4 DN0986349



6.2.2.1 Downloadable PDF package with _startup.pdf . . . . . . . . . . . . . . . . . . . . 346.3 Paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376.4 Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376.5 On-line help format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

7 Document identification and versioning system . . . . . . . . . . . . . . . . . . . 387.1 PDF document identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397.2 NED online content identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

8 How to give feedback on documentation . . . . . . . . . . . . . . . . . . . . . . . . 438.1 Problem reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438.2 Giving feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

DN0986349 5



List of figuresFigure 1 LTE solution documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Figure 2 Danger, Warning, Caution icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 3 Note - Notice icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 4 Note - General icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 5 Note - Tip icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 6 Old warning convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 7 Old caution convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 8 Old note convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 9 Old tip convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 10 Product Information Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 11 Explore Product Information Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 12 Browsing products using the Product Finder . . . . . . . . . . . . . . . . . . . . . 22Figure 13 Browsing products using the Product Catalog . . . . . . . . . . . . . . . . . . . . 23Figure 14 Example of Information Center for Flexi BSC . . . . . . . . . . . . . . . . . . . . 24Figure 15 Product Information - Reference Information. . . . . . . . . . . . . . . . . . . . . 25Figure 16 PIC Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Figure 17 Care in NOLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 18 Table of contents for HTML and for PDF. . . . . . . . . . . . . . . . . . . . . . . . 29Figure 19 Opening the browseable NED set in the Nokia Siemens Networks portal.

30Figure 20 Information Center format column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Figure 21 PDF format download check box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 22 PDF format download dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 23 ZIP file download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Figure 24 _startup.pdf file after ZIP extraction. . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Figure 25 Adobe Acrobat Reader - Customize Toolbars . . . . . . . . . . . . . . . . . . . . 36Figure 26 Adobe Acrobat Reader - Page Navigation Toolbar . . . . . . . . . . . . . . . . 36Figure 27 Adobe Acrobat Reader - Previous View and Next View buttons . . . . . . 36Figure 28 PDF cover page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 29 Old PDF document identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 30 New PDF document identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Figure 31 NED information icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Figure 32 NED online content identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 33 Feedback button in NOLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Figure 34 NOLS Support request link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

6 DN0986349



List of tablesTable 1 Flexi Multiradio BTS LTE release documentation . . . . . . . . . . . . . . . . . 10Table 2 Font conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Table 3 Command line conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Table 4 Issue numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

DN0986349 7

Guide to LTE Radio Access Operating Documentation Summary of changes


Summary of changesChanges between issues 01B (2012-06-25, RL30) and 02 (2013-01-21, RL40)

How to find Single RAN documentation (2.10)New section How to find Single RAN documentation has been added.

Giving feedback (8.2)

• Figure 33 Feedback button in NOLS has been updated to reflect changes made to the Nokia Siemens Networks Online Services portal.

Changes between issues 01A (2011-09-21, RL30) and 01B (2012-06-25, RL30)Figure PDF cover page has been updated.

Changes between issue 01 (2011-06-22, RL30) and 01A (2011-09-21, RL30)Section Summary of changes has been added.

8 DN0986349



Summary of changes

DN0986349 9

Guide to LTE Radio Access Operating Documentation Documentation for the LTE System

Id:0900d8058099bdf9Confidential

1 Documentation for the LTE SystemThis LTE Radio Access documentation set is a publication that contains all operating documentation necessary for the LTE Radio Access system with primary focus on the Flexi Multiradio BTS LTE documentation.

The Nokia Siemens Networks LTE/EPC system consists of a radio and core network as well as a network management system. The radio network part consists of a single node, the evolved node B (eNB). The core network part consists of the Mobility Manage-ment Entity (MME) as well as two gateway functions. In addition, a home subscriber server is part of the LTE system architecture. The following figure shows the different document sets that make up the LTE system-wide customer documentation:

Figure 1 LTE solution documentation

The following sections describe the components of LTE system-wide customer docu-mentation.

1.1 LTE Radio Access Operating DocumentationA set of new feature descriptions is provided at the beginning of a product program to introduce the content of the new release in detail if deemed necessary.

In the trial phase a document set is provided to introduce the new release and/or the trial content to the customers. The set provided supports the trial customers and serves as a reference for planning new software and hardware acquisitions and their impact on the existing network.

A full set of documentation is provided in the piloting phase, and updated in the volume delivery phase.

10 DN0986349


Id:0900d8058099bdf9Confidential

Documentation for the LTE System

1.2 Flexi Multiradio BTS LTE DocumentationThe following table lists the Flexi Multiradio BTS LTE document sets that are published outside the LTE Radio Access Operating Documentation:

1.3 NetAct DocumentationNetAct operating documentation provides information on the LTE specific issues related to the Nokia Siemens Networks NetAct. Release documentation for the NetAct is also delivered.

1.4 EPC DocumentationEPC documentation consists of operating documentation for the Nokia Siemens Networks Flexi Network Server - MME as well as Nokia Siemens Networks Flexi Network Gateway (S-GW and P-GW). Nokia Siemens Networks Flexi NS - MME and Flexi NG release documentation is also delivered.

Operating documentation for the above mentioned network elements is available in the Nokia Siemens Networks extranet portal.

1.5 HSS DocumentationDocumentation related to the IP Multimedia Subystem and CMS-8200 is available in the Nokia Siemens Networks extranet portal.

Name of document set Available formats Available from Description of the document set

Nokia Siemens Networks Flexi Multira-dio BTS LTE Release Documentation

PDF Nokia Siemens Networks extranet: Care

Release Note and other documents that intro-duce this network element release .

Table 1 Flexi Multiradio BTS LTE release documentation

DN0986349 11

Guide to LTE Radio Access Operating Documentation Architecture of LTE Radio Access Operating Documen-tation


2 Architecture of LTE Radio Access Operating DocumentationThe purpose of this section is user orientation and enabling the reader to find information in LTE Radio Access operating documentation.

The LTE Radio Access operating documentation set contains operating documents for:

• LTE system • Flexi Multiradio BTS LTE • iOMS

2.1 LTE Document List and Guide to LTE Radio Access Oper-ating DocumentationThe LTE Document List is the first document in the operating documentation set. It lists the documents of the operating documentation set by information category including the document ID, issue number, and PDF filename.The Guide to LTE Radio Access Oper-ating Documentation is the second document in each operating documentation set. Its purpose is reader orientation.

2.2 ChangesThe Changes section will be included in the second release of a system or product.

The purpose of the Changes section is to make the connection between the previous release and the new release. It introduces the system release briefly by mentioning the key new features as well as the new hardware.

Delta reports for parameters, counters, alarms, and key indicators are also provided. Major changes in the documentation content and structure are also explained. New and removed documents in comparison with the previous release are listed as well, as modified documents impacting the structure of the set.

The Changes document contains a cumulative listing of all of the LTE features that were new or removed in earlier releases.

2.3 System DescriptionsSystem Descriptions provide an overview of the LTE system, including its architecture, interfaces, and the network management system.

2.4 Functional Area DescriptionsFunctional Area Descriptions describe the existing LTE system functionality, upon which the new features have been built. The information is categorized according to the follow-ing areas:

• Radio Resource Management and Telecom • Transport and Transmission • Operability

12 DN0986349



Architecture of LTE Radio Access Operating Documen-tation

2.5 Feature DescriptionsFeature Descriptions introduce the content of the new release and contain links to further information on each feature such as the related functional areas, parameters, alarms, and feature activation instructions.

Feature descriptions from earlier releases are also included for reference.

2.6 BTS and iOMS DescriptionsDescriptive information about each network element, in this case Flexi Multiradio BTS LTE and iOMS, is also provided. This category provides both product and hardware descriptions for Flexi Multiradio BTS LTE and iOMS.

Product descriptions contain descriptive information about the product and the functions that it provides to users. These documents describe the purpose, objective, and features of the product as well as typical applications, variations, and expansion levels, division into subsystems and functional units, and the purpose and capability of subsystems and functional units.

Hardware descriptions describe the HW and embedded SW architecture of the NE and its sub-systems. The NE HW configuration and different capacity steps are included. Hardware descriptions provide an overview of the HW products or units used in the NE. Hardware unit descriptions provide the key technical data of the unit and describe the mechanical and logical structure and interfaces of the unit.

2.7 InstructionsThe 'how to' instructions for carrying out procedures are arranged according to operator processes, ranging from planning to troubleshooting. Instructions can take various forms, such as step-by-step procedures, use cases, checklists, or system-level guide-lines that provide links to more detailed network level information. The following catego-ries are used:

Plan and Dimension provides network engineering guidelines.

Install and Commission describes the hardware installation procedure from planning the site and unpacking the delivery to assembly and installation, as well as how to commis-sion the network elements once they have been installed.

Integrate and Configure provides instructions for:

• Integrating new equipment to the rest of the network • Configuring the network elements and their interfaces for the first time • Changing and optimizing the configurations as needed

Activate: contains instructions for 'switching on' features when they are taken into use for the first time. This includes instructions for activating, verifying, and de-activating the feature.

Maintain Hardware: describes how to perform routine on-site maintenance tasks on hardware.

Monitor and Measure: combines documents related to monitoring and measuring tasks under one heading. This section contains instructions for the monitoring of the alarm flow and the analysis of incoming monitoring data. Measuring guidelines including mea-suring 'use cases' describe the general principles of how to perform measurements. Measurement and counter descriptions can also be found in this section.

DN0986349 13

Guide to LTE Radio Access Operating Documentation Architecture of LTE Radio Access Operating Documen-tation


Administer: contains instructions for keeping license data up-to-date, taking regular data backups, and for user access management. Instructions for using element management applications are available.

Troubleshoot: contains alarm descriptions and instructions on how to recover from an alarm. Instructions for handling fault situations are included here, for example replacing faulty hardware and step-by-step troubleshooting instructions based on fault symptoms.

Upgrade: covers instructions for upgrading the system and the network elements, as well as taking productizations into use.

2.8 ReferenceThe Reference section contains all of the technical system details that are relevant in many contexts and are therefore often linked with or referred to from other parts of the documentation. The following reference data types are included:

• Alarms • Commands • Compatibility • Counters • Key Performance Indicators • Parameters • General Glossary

2.9 Legal, Safety and Environmental InformationThe Legal, Safety and Environmental Information section contains information on legis-lation and safety issues such as compliance and copyright statements, and environmen-tal information.

2.10 How to find Single RAN documentationDocumentation related to the Single RAN concept is embedded in various places in the documentation set either inside existing documents or as stand-alone documents.

Single RAN documentation is included in the following categories:

• System Description: LTE RAN and EPC System Description • Functional Area Descriptions (Operability): RF Sharing Operability • Features:

– LTE RAN, RL40, Feature Descriptions and Instructions: LTE612: Synchroniza-tion Hub

– Feature Descriptions RL20: LTE649: QoS Aware Ethernet Switching and LTE447: SW support for RF sharing GSM-LTE

• Install and Commission: Creating RF Sharing [Radio Access Technology 1] - [Radio Access Technology 2] Configurations

• Integrate and Configure:– Recommended Configurations for SingleRAN Transport Sharing– Backhaul Sharing QoS Guideline– Configuring and Upgrading [Radio Access Technology 1] - [Radio Access Tech-

nology 2] RF Sharing

14 DN0986349



Architecture of LTE Radio Access Operating Documen-tation

In addition, an Excel attachment Flexi Multiradio BTS RF Sharing Supported Configura-tions is available in Product Information Center.

DN0986349 15

Guide to LTE Radio Access Operating Documentation Conventions

Id:0900d8058097fb84Confidential

3 Conventions

3.1 LanguageAll operating documentation is published in English.

3.2 Warnings, cautions, notes, and tipsThe conventions of warnings, cautions, notes, and tips are being updated. During the transition period, there are two overlapping systems in use. Therefore, a mix of old and new conventions may be found in operating documentation.

New Danger, Warning, and Caution iconA safety message indicates a dangerous situation where personal injury is possible.

The keywords denote hazard levels with the following meaning:

• DANGER! - Indicates a hazardous situation which, if not avoided, will result in death or serious (irreversible) personal injury.

• WARNING! - Indicates a hazardous situation which, if not avoided, could result in death or serious (irreversible) personal injury.

• CAUTION! - Indicates a hazardous situation which, if not avoided, may result in minor or moderate (reversible) personal injury.

Figure 2 Danger, Warning, Caution icon

New Note - NoticeA property damage message indicates a hazard that may result in equipment damage, data loss, traffic interruption, and so on.

16 DN0986349



Conventions

Figure 3 Note - Notice icon

New Note - GeneralA note provides important information related to the topic, for example, not obvious exceptions to a rule or side effects.

Figure 4 Note - General icon

New Note - TipA tip provides additional information related to the topic which is not essential in the context, but given for convenience.

Figure 5 Note - Tip icon

Old WarningA warning is used to alert the user to precautions needed to protect people. Warnings concern, for example, information about dangerous voltages or actions that could result in bodily harm or injury.

DN0986349 17



Warnings are marked with the following icon:

Figure 6 Old warning convention

Old CautionsA caution is used to alert the user to precautions needed to avoid damage to the product or system, loss of data, or harm to business. Cautions concern, for example, damage caused by electrostatic discharge or actions that can cause lost traffic.

Cautions are marked with the following icon:

Figure 7 Old caution convention

Old NotesA note is used to alert the reader to important information on the proper use of the product, user expectations, error situations, and actions related to these. Notes concern, for example, unauthorized modifications to the product that might affect Nokia Siemens Networks liability, items that might be expected within a product delivery but are not included, and avoidance of errors during operation.

Notes are marked with the following icon:

Figure 8 Old note convention

Old TipsTips provide useful suggestions.

Tips are marked with the following icon:

Figure 9 Old tip convention

3.3 Font conventionsThe following table contains fonts that are used for certain types of data.

18 DN0986349



Conventions

3.4 Command line conventionsThe following conventions are used in the UNIX command lines.

Convention Description

courier Courier is used to indicate:

• commands and script namesFor example: > show which displays platform system information

• paths and file namesFor example: sample_file.cfg

• parameters and valuesFor example: 3GPP-IMSI

• names of processesFor example: gtpdump

italics Italicized text identifies:

• references in PDFs to other information topics • titles or sections of documents • parts of the text that have emphasis

underlined Underlined text identifies links to other information topics in the NED software application.

bold Bold print is used in:

• steps in proceduresFor example: Enter the name of the access point.

• buttons or menu options in a graphical user interfaceFor example: Save

Bold courier commands that you need to input.

For example: iclid

Table 2 Font conventions

Convention Indication

\ For layout purposes, long command lines and the lines in file descriptions and examples, are sometimes split into two or more separate lines. With SQL clauses, UNIX commands and UNIX file descriptions, a backslash at the end of a printed line indicates that the command or example continues on the following line of the document.

For example:

# cat /etc/cmcluster/pkgcomm/control.sh.log │ \grep "crontab" │ more

Do not type the backslash shown in the document when giving a command or using a line from an example.

With MML commands, everything between the initial Z and the semicolon ( ; ) constitutes a single line. For example:

ZWTP:OMU:AS7_U,<PIU-index>,<track>::X25,<PCM-type>,<PCM-number>,TSL,0;

Table 3 Command line conventions

DN0986349 19



<text in angle brackets> Variable user input

Variable data is written between the < and > characters.

For example: <process_name>

[ ] Optional parameters. Indicates that the portion of the command enclosed in square brackets is optional or not always required.

For example:

ZUSU:<unit>[,<index>];

The example shown above indicates that if you are dealing with several units of the same type (for example, the BDCUs), it is necessary to specify the index. With single units (for example, the OMU), the index parameter is not manda-tory.

{ │ } Conditional parameters. Indicates that the portion of the command enclosed in curly brackets is conditional.

For example:

# cmmodpkg { -e │ -d } <package>

The example above indicates that you must select either the -e or the -d option when you enter the command.

Convention Indication

Table 3 Command line conventions (Cont.)

20 DN0986349


Id:0900d805807e0196Confidential

Delivery timing

4 Delivery timingDocumentation deliveries are tied to release phases and milestones. The following section demonstrates the timescale for the delivery of all official documentation in each release.

4.1 Documentation deliveries in the release development phaseThe term 'pre-release documentation' refers to any document sets that are published prior to the customer piloting phase. A pre-release documentation set is typically pub-lished around the release trial delivery. Earlier pre-release publications are also possible if judged necessary based on customer needs. Pre-release documentation is usually issued in draft state, because the information it contains does not always reflect the final implementation of the software or hardware, nor has the software and hardware been fully tested by the time of publication. Pre-release documentation deliveries do not usually include the complete set of operating documentation but consists of a selection of documents.

The first complete and approved set of operating documentation is issued when the release is made available for piloting. The final, approved set of operating documenta-tion, including modifications made based on items detected during piloting, is published when the release is made available for volume delivery.

4.2 Documentation deliveries in the release maintenance phaseUser needs are the main factor in determining the scope and timing of documentation updates in the maintenance phase. Documentation is updated and delivered as needed until the product or system reaches the end of its lifecycle.

The delivery of updated documents during maintenance phase is made either:

• as a new issue of the full operating documentation set, or • as a documentation change delivery including a selection of updated documents (in

urgent update needs).

In the cases of critical errors and their corrections, a documentation change note can be published to inform the customer about the error found and the upcoming correction.

DN0986349 21

Guide to LTE Radio Access Operating Documentation Delivery channels and media

Id:0900d8058099cdb5Confidential

5 Delivery channels and mediaThere are several delivery channels and media through which documentation is pub-lished to customers, depending on the product and the type of documentation required. This section describes each of these options.

The primary delivery channel is the Nokia Siemens Networks portal.

5.1 Online servicesProduct Information Center (PIC) is the primary online service channel for delivering documentation. It is accessible via Nokia Siemens Networks Online Services (NOLS).

5.1.1 Product Information CenterProduct Information Center (PIC) is a portal application that provides access to Nokia Siemens Networks product overviews and technical documentation.

Figure 10 Product Information Center

An introduction to Product Information Center can be found in the Explore Product Infor-mation Center section.

Figure 11 Explore Product Information Center

Using Product Information CenterThe Product Information link is available in the primary navigation of NOLS portal. Select the desired product and you will be guided to the Information Center for the product. Each product in Nokia Siemens Networks portfolio has an Information Center, where the Overview section introduces the product, and the Documentation section provides access to detailed technical documentation. It can be browsed online or downloaded as needed in various formats.

The Information Center of a product or a system can be found by using one of the fol-lowing options:

22 DN0986349



Delivery channels and media

• Product Finder: Search the full Nokia Siemens Networks product portfolio by browsing by category and sub-category, or search using a keyword or phrase.Users have the option to select whether Product Finder shows only the products that their company has purchased from Nokia Siemens Networks (My company prod-ucts) or all Nokia Siemens Networks products.The Information Center can be accessed by selecting the product from the list and clicking Go.In addition, products can be searched by typing a keyword.

Figure 12 Browsing products using the Product Finder • Product Catalog: By switching to the Product Catalog view, you can browse

products through a categorized product map. Products are listed by categories and subcategories.Users have the option to select whether Product Finder shows only the products that their company has purchased from Nokia Siemens Networks (My company prod-ucts) or all Nokia Siemens Networks products.The Information Center can be accessed by clicking the product name.

DN0986349 23



Figure 13 Browsing products using the Product Catalog

For example, the Information Center for Flexi BSC looks as follows:

24 DN0986349




Figure 14 Example of Information Center for Flexi BSC

The Information Center contains the following main features:

• The Overview tab introduces the product and provides the related marketing mate-rial. The Overview tab is active by default once you enter the product’s Information Center. From this page you find generic information about the product, like: Key functionality, Key benefits, Product details (if available), a Read more section with additional information, and Downloadable product/system descriptions and fact-sheets.

• The Documentation tab provides a comprehensive list of the latest documentation available for the selected product. It begins with the newest first and includes NED libraries which can be downloaded and installed in the NED software application. The list can be filtered. Find the documentation set needed as follows:– The list of documents can be sorted by date (default), format, content type,

release and title. Direct links to NED online libraries (when available) are pre-sented with quick link icons.

DN0986349 25



– The Documentation details page can be accessed by clicking the document title. It presents additional information of the document or document set, and includes links to online documents and downloadable content.

– Documents can then be browsed online or downloaded as needed in the various formats available (for example; NED document sets, PDFs, Microsoft Excel spreadsheets).

Reference Information

Figure 15 Product Information - Reference Information

Section Reference Information is a web interface to a database where users can retrieve the most up-to-date reference information, that is, Alarm, BTS Fault, Parameter, Counter, and Key Performance Indicator descriptions. Users can browse these data type descriptions and export as Excel format. Users are also able to export comparison data between two releases in Excel format. The availability of these information types in this web interface varies depending on the product.

5.1.1.1 PIC searchPIC Search is available from the PIC sidebar on the right-hand side of the user interface.

Figure 16 PIC Search

How to SearchType your search query in the search box and hit Enter or click the Search button. Search will look for the Product Information Center content which matches your query.

Users have an option to select whether search is targeted to:

1. My company products (predefined list of Nokia Siemens Networks products based on customer profile), or

2. All Nokia Siemens Networks products

26 DN0986349




g Search results only contain content to which the user has access.

Search filteringYou can further refine the search results by selecting the following content filters:

• Product • Release • Content type • Format

The number of search hits per filtering criteria is displayed in parentheses ( ) after the filtering values are ranked accordingly. The number of listed filters per each section is limited to 100. You can combine different filtering values from each section in any order, and the list of results will be updated accordingly.

g Only filter values for which there are search results are displayed.

Search resultsSearch results are displayed with the following data:

• search result link • date • short description with highlighted search keywords • link to referrer page

The number of search results is displayed at the top of the search results list. This number states the number of documents or document sets that match your query.

g One document or document set can contain several hits and therefore the number of hits displayed for the filtering criteria is usually much higher.

Display optionsUse this option to get more or less results per page. 20/50/100 results are available per page.

SortingIt is possible to sort by relevance or date. You can sort the list of search results by rele-vance (default) and date by clicking the corresponding links located above the list of results.

Quick linksIn addition to actual links to search results, dedicated quick link icons are displayed for NED online document sets and product overview content of a product when applicable. Quick links provide instant access to browse NED document sets online and help to quickly spot and access the Information Center of a certain product.

Referrer page linksReferrer page links are displayed below the search result title and description. This link shows the document or document set location within PIC, and provides access for example to the Document Details page with additional information about the search result.

Search tipsIt is recommended not to include the following characters in search strings:

DN0986349 27



• full stop (.) • comma (,) • semicolon (;) • colon (:) • other special characters

5.1.2 CareCare supports operation and maintenance activities by offering efficient online tools. It helps you find the latest Software, Change Deliveries, and Hardware related information quickly and easily. If you need support, you can submit a Help Desk case 24 hours a day via the online Help Desk Service. The status of submitted cases can be followed in real time.

Figure 17 Care in NOLS

SW Release DocumentationSoftware release documentation is delivered through the NOLS Software Delivery service together with software packages. The Software Delivery service can be found under the Care section in NOLS.

5.2 Software-embedded documentationEmbedded documentation inside a software application usually means an online help. Online helps are available for the graphical user interfaces of each software application.

28 DN0986349




5.3 Documentation delivered on CD-ROM or DVDDocumentation on CD-ROM or DVD can be ordered through the Nokia Siemens Networks logistics system. Contact your local account team for placing an order in the system.

An operating documentation CD-ROM or DVD is issued on a need basis when the release is made available for volume delivery. Updates are available via portal only.

5.4 Documentation delivered with product hardwarePrinted versions of quick guides are delivered as part of the base station hardware.

DN0986349 29

Guide to LTE Radio Access Operating Documentation Delivery formats


6 Delivery formats

6.1 Nokia Siemens Networks Electronic Documentation (NED)NED is a software application for delivering documentation and viewing it in standard web browsers which can be downloaded from NOLS. The current NED application version used in all new deliveries is NED 6. NED 6 is backward compatible with NED 5.2, NED 5.3, NED 5.4, and NED 5.5.

In most cases, NED deliveries contain documentation in two formats, namely HTML and PDF. In the Table of contents view, the content is organized in topics for easy browsing on the computer display. In the PDF table of contents, the same content is available for downloading and printing. Content is identical in both formats.

Figure 18 Table of contents for HTML and for PDF

NED deliveries that contain only PDFs can also be used, mainly in the case of pre-release phase documentation. In a PDF-only NED, there is only one Table of contents view.

For more information on the features and the use of the NED software application, see the NED user guides and training material in the Nokia Siemens Networks portal under NED.

NED in the Nokia Siemens Networks portalThe Nokia Siemens Networks portal is the main delivery channel for NED documenta-tion. NED libraries can be browsed on-line or downloaded onto a PC or server.

NED online browsing does not require the installation of the NED software application. To open browseable NED content, navigate to the document set in question and click on the Browse online document set link as shown in the following figure:

30 DN0986349



Delivery formats

Figure 19 Opening the browseable NED set in the Nokia Siemens Networks portal

To download a NED package, the NED software application must be installed on your computer locally or on a server. This option allows you to download NED files and inte-grate them with NED documentation sets that have been previously installed.

Instructions for downloading NED packages can be found in the Nokia Siemens Networks portal on all NED delivery pages. Instructions for installing the NED software application and the installation package itself can also be found in the Nokia Siemens Networks portal.

6.2 PDFEach full NED delivery includes the documentation both in HTML and PDF format. PDFs are delivered both within the NED software application (See Table of contents for HTML and for PDF) and as a separate downloadable set of PDF documentation only with contents equivalent to the NED software application.

Sometimes documents are published as PDFs only; either as a collection of single PDF documents or a downloadable PDF ZIP-package. The main reasons for mere PDF deliv-eries are:

• Content is time critical

DN0986349 31



• Pre-release or draft content that will later be replaced by an operating documenta-tion set

• Number of documents is very small

6.2.1 Downloading PDF filesDownload PDF files if you use Adobe Acrobat Reader to view documents. Create a folder for the PDF files on your local directory or server.

g You cannot install these documents to your local directory or server with the NED software application.

6.2.1.1 Downloading a collection of single PDFsIn the Information Center (Example of Long Term Evolution in Figure 20 Information Center format column), there is a column that shows the format available. Select the title to see more document details.

32 DN0986349



Delivery formats

Figure 20 Information Center format column

In Document details, check the file in Downloads and click Download selected files.

DN0986349 33



Figure 21 PDF format download check box

The File download dialog appears. Save the PDF file to your local directory or server.

Figure 22 PDF format download dialog box

If you select more than one file when downloading multiple PDF files, the files are auto-matically zipped into one file for downloading. Click Download selected files and the documents will be downloaded to a defined location. See Downloading a full PDF doc-umentation set (ZIP-package) for extraction instructions.

6.2.2 Downloading a full PDF documentation set (ZIP-package)If you select to download a ZIP-package, click Download selected files and the docu-ments will be downloaded to a defined location as a ZIP file.

34 DN0986349



Delivery formats

Figure 23 ZIP file download

After the download is complete, unzip the ZIP file in your local directory or server.

6.2.2.1 Downloadable PDF package with _startup.pdfDocument sets include a _startup.pdf file. Open it and click the titles in the table of contents to navigate to the desired PDF file.

DN0986349 35



Figure 24 _startup.pdf file after ZIP extraction

t If you do not have the navigation buttons Previous View and Next View available on your Adobe Reader user interface, it is advisable to add them. This helps you to navigate back to the document set table of contents once you have opened a document. The instructions for that below:

36 DN0986349



Delivery formats

Figure 25 Adobe Acrobat Reader - Customize Toolbars

Figure 26 Adobe Acrobat Reader - Page Navigation Toolbar

Figure 27 Adobe Acrobat Reader - Previous View and Next View buttons

DN0986349 37



6.3 PaperPaper is the primary delivery media for quick guides.

6.4 Microsoft ExcelAlarm, counter, BTS fault, and parameter descriptions as well as comparison reports between releases can be exported as Microsoft Excel format from the Reference Infor-mation web interface in PIC. For the time being, parameter comparison reports cannot be exported in Microsoft Excel format.

6.5 On-line help formatAn on-line help is available for the graphical user interface of the element management applications.

38 DN0986349


Id:0900d805809474d8Confidential

Document identification and versioning system

7 Document identification and versioning systemFor identifying Nokia Siemens Networks operating documentation, documents are numbered and given a version. Documents that are published in draft status have a draft label.

The document identification and versioning system is changing and during the transition period there are two different systems in use.

Identification Numbers and CodesIdentification numbers and codes are used for identifying documents, parts of a docu-ment, or entire document sets. The identification numbers and codes are unique, that is, one number or code is available for one item only.

VersionIssue numbering enables the reader to differentiate between previous and current versions of documents. The basic rule is that the higher the number the more recent the copy in question is.

DN0986349 39

Guide to LTE Radio Access Operating Documentation Document identification and versioning system


7.1 PDF document identification

Figure 28 PDF cover page

Document setDocument sets are identified with their title and issue number.

Each document set is given an issue number that appears as part of the document set title. Every time a document set is updated and published, the issue number increases.

Operating documentation change deliveries are always connected with the original pub-lication by a version number. For example, a change delivery with the name GSM/EDGE BSS, Rel. RG10(BSS), Operating Documentation, Issue 01, Document Change Delivery 1 is issued on top of the GSM/EDGE BSS, Rel. RG10(BSS), Operating Docu-mentation, Issue 01. The update is the first documentation change delivery connected with this operating documentation set.

Change deliveries are not versioned, because they are never updated.

LTE Radio Access, Rel RLXX,

Operating Documentation,

Issue XX

Guide to LTE Radio Ac ess Operating

Documentation

c

DNXXXXXX

Issue XX

Approval Date YYY-MM-DD

Document Set Title

Document Title

Document Number

Issue Number

40 DN0986349




DNThe Document Number (DN) is the document identifier. As an example, the document number DN05189701 consists of two parts, namely the prefix DN, and a running number which is unique for each document.

IssueEach document is given an issue number. As a result of the transition period, two systems are used. The example document in Old PDF document identification has the issue number 5-3 and uses the old system. The first digit increases once per system or network element release. The second digit increases every time the document is updated and published within the system or network release.

The new system uses two digits. The digits increase once per system or network element release. Once the document is updated within the system or network release, a letter of the English alphabet is added to indicate the update. See New PDF document identification. All new and updated documents use the new system.

g DRAFT is written next to the issue when it is an approved draft document.

Approval DateThe approval date is the date when the document was approved for customer delivery either in draft (for example, pre-releases) or approved status. The date has the following format: YYYY-MM-DD.

PDF FooterPDF document identification data can also be found in the PDF footer beginning on the second page.

Figure 29 Old PDF document identification

Old New

1-0 01

1-1 01A

1-2 01B

2-0 02

2-1 02A

Table 4 Issue numbers

DN0986349 41

Guide to LTE Radio Access Operating Documentation Document identification and versioning system


Figure 30 New PDF document identification

Object IDOur documentation consists of information units, objects, each of which roughly corre-lates to one chapter in the PDF. Each object version has its own unique identifier that you can see in the online view in NED (see NED online content identification) and in the PDF footer (see New PDF document identification).

7.2 NED online content identificationEach online (HTML) page of NED libraries has its own identification data. It can be found by clicking on the information icon in the upper left-hand corner of the main frame of each page (see NED online content identification).

Figure 31 NED information icon

Object IDs are also used for identifying HTML content.

g Document numbers of online pages do not correspond with PDF document numbers because of the different level of granularity between the two formats. An online page roughly corresponds to a chapter in a PDF document.

42 DN0986349




Figure 32 NED online content identification

DN0986349 43

Guide to LTE Radio Access Operating Documentation How to give feedback on documentation


8 How to give feedback on documentationThere are several ways in which information can be sent to Nokia Siemens Networks regarding documentation. This feedback can take the form of faults that have been found in the documentation itself, or suggestions on how to improve the document. This section describes each of these methods.

8.1 Problem reportingDocumentation-related problems can be reported either to Nokia Siemens Networks Customer Contact Centers or through the NOLS Help Desk. In the NOLS Help Desk, service customers are given direct access to the RESOLVE service request tool where they can create, follow up, and manage their company’s service requests online. Docu-mentation cases are processed according to the same principles as hardware and software cases.

Submit a problem report through the NOLS Help Desk (with the RESOLVE service request tool) or to your local Nokia Siemens Networks contact in cases where:

• Information is incorrect • Information cannot be found, or is difficult to find • Documents do not open or show correctly, links do not work • Problems with downloading NED software, NED libraries, or PDFs • Information is not detailed enough, is missing, or is inconsistent • Information does not support the use of the product

If possible, include the following details in your report:

• Product and/or system name and release • Document set title and build date • Document title • Document Number (DN) • Issue or edition

8.2 Giving feedbackIn cases where you would like to ask about documentation or suggest a development idea but not report your feedback as a fault, there are several channels available for giving this feedback.

NOLS feedbackGive Feedback and View feedback buttons are located on the right-hand side of the browser window and are visible on any page regardless of the location in PIC. The buttons are shown in Figure 33 Feedback button in NOLS. Click on the Give Feedback button, fill in the feedback form, select service Product Information, and submit the form.

44 DN0986349



How to give feedback on documentation

Figure 33 Feedback button in NOLS

NOLS supportAny feedback related to NOLS or any content that can be found in NOLS can be sent to NOLS Support ([email protected]). Find guiding information and the e-mail address by following the Support request link (see Figure NOLS Support request link). The link can be found on each NOLS page in the upper right-hand corner.

Figure 34 NOLS Support request link