Wireless TopN Improvement

--Documentation

Express
Issue 01

01

Introduction to Wireless Documentation TopN Improvement

Background:

Documentation is determined as the TOP3 improvement project in 2012 Wireless User Group Meeting. Customers voices are our driving focus.
Voices in Wireless User Group Meeting Document Issues on Live Network Customer Satisfaction Survey

New focus Topics in 2013 :

Capacity Monitoring Guide Improvement Parameter Transparency Improvement Hardware Specification Improvement Delta Documentation Improvement Feature Documentation Improvement Troubleshooting Documentation Improvement Counter Documentation Improvement

Documentation TopN Improvement

Operation Roadmap :
Deploy & Verify Apr. 2013 Summarize & Standardize Jun. 2013

Problem Analysis Topic Selection & Proposed Solutions Dec. 2012 Feb. 2013

Rate this Mailer: [ Good ] [ Average ] [ Unsubscribe ] [ Feedback ]

Contact Us: supportmaster@huawei.com

02

Capacity Monitoring Guide Improvement

Customer Concerns:
More detail required on monitoring methodologies for RNC and NodeB. Need RNC & NodeB capacity engineering guide. There should be more on suggestive actions and details on how to do that.

Sub-Project & Objective:

No. Sub-Project Scope Objectives

Added capacity SRAN7.0 and To solve the problem of capacity monitoring by monitoring method later improving monitoring method of each resource item To make the guide easy to find in the Customer Easy to find and SRAN7.0 and 2 documentation system, and convenient to acquire acquire later from the Support website for the customers To improve capacity monitoring method of each Improved capacity SRAN7.0 and 3 monitoring item, including related commands and monitoring method later methods of capacity improvement 1

Highlight Show:
The writing template of capacity monitoring item has been improved, including monitoring principle, the monitoring methods, and recommended measures.

What?

How?

How to?
03

Customer Concerns: Sub-Project & Objective:

No. Sub-Project Reserved parameter 1 transparency improvement Information in 2 meaning improvement Network impact of 3 different value improvement

Parameter Transparency Improvement

Scope SRAN7.0 and later SRAN7.0 and later SRAN7.0 and later Objectives 1.Description reserved parameter document publishes global. 2.The description of used reserved parameter is more clear. 3.More detailed description of disuse mechanism. The meaning is more complete, and its more accurately for user to dispose and plan parameter attribute. Complete network impact of different value, and its more accurately for user to plan or modify parameters value.

Parameters not transparency enough. Lack of important information.

Highlight Show:

In order to let the user understanding the reserved parameter, we will make the following improvement to the document, which named Used Reserved Parameter List . 1.Publishing global as an attachment of release note 2.Description obtaining way in Hedex Used Reserved Parameter List 3.Adding GUL value range, unit, actual value range, recommended value, caution and change reason 4.More detailed description of disuse mechanism Make the meaning more complete, HW will make the following improvement to the meaning. 1. Adding the missing enumerated value meanings Meaning in Parameter List 2.Adding protocol number 3. Specifying functions and scenarios SRAN7.0 has completed 30% parameters which impact on radio network performance is None, SRAN8.0 will complete 40% parameters.
Impact on Radio Network Performance None Impact on Radio Network Performance

If this parameter is set to a small value, call drops will occur due to delayed power control. If this parameter is set to a large value, power consumption and interference on the network increase.

04

Hardware Specification Improvement

Customer Concerns:
Non complete hardware spec and some information is missing. Hardware specification information is so scattered for customers to find. Some descriptions are different between the Hedex and Presales doc., UMTS and LTE.

Sub-Project & Objective:

No.
1 2

Sub-Project
Specification completion improvement

Scope

Objectives

SRAN7.0 To make it easy for customers to find the complete and later information of hardware specification

Specification acquirement SRAN7.0 To make it convenient for customers to find information by and later improving the specification distribution in the documents improvement Specification consistency improvement To make the specification information correct and SRAN7.0 consistent in every modes by improving SRAN specification and later information

Highlight Show:
As to Specification completion improvement, information about signaling specification is added in the overview of SRAN8.0 documents.

05

Hardware Specifications Documentation of GU Controller

Delta Documentation Improvement
Customer Concerns:
Absent known issues or resolved issues from Release Notes(RN) Incomplete information about parameter and counter changes Unclear description of changes

Sub-Project & Objective:

No. 1 Sub-Project Scope Objectives

Complete SRAN7.0 Release Notes and later issues Clear SRAN7.0 description of and later changes

1. All known network issues are provided. 2. More issues related to KPIs and counters are provided and identified. 1. The description in solution impact of Release Notes is more clear. 2. Detailed reasons for parameter changes are provided. 3. Description of the reasons for counter changes is clear and exact.

Highlight Show:

Adding descriptions about KPI impacts of issue changes

Improving detailed descriptions about changes

06

Feature Documentation Improvement

Customer Concerns:
There are some missing feature activation procedures. Algorithm description for very detail features still needs improvement. Improve the feature descriptions by adding the way to follow their benefit.

Sub-Project & Objective:

No. Sub-Project Scope Objectives

1 2
3

Adding the missing feature activation procedures

Improving the descriptions about key feature algorithm

SRAN7.0 and later SRAN7.0 and later

To guide customers to activate feature more accurately

To make customers to understand the feature principles more easily

To help customers to judge how to use the features

SRAN7.0 Improving the obscure descriptions and later about benefit and restriction

Highlight Show:
Improved chapters
About This Document Overview Introduction Benefits Architecture [Feature Component] Principles Improvements Related Features Network Impact System Capacity Network Performance Engineering Guidelines When to Use Required Information Planning Deployment Troubleshooting Parameters Counters

Improved points

Improving the unclear descriptions about benefits Adding the missing descriptions about algorithm Improving descriptions about usage scenario restriction Adding the missing activation procedures Adding related alarm information

07

Troubleshooting Documentation Improvement

Customer Concerns:
There are no descriptions about the alarm reasons and recovery conditions. Alarm processing procedures are not distinguished into long-distance and near-end operations, thus it is not convenient to submit issue e-flow.

Sub-Project & Objective:

No. 1 Sub-Project Scope Objectives Improvement of alarm reference completion Improvement of 2 distinguishing long-distance and near-end operations 3 Improvement of alarm processing procedures SRAN7.0 To make customers know the network issues and and later whether thresholds can be set SRAN7.0 To make it convenient for customers to submit issue and later e-flow. To guide new employees to process alarm step by SRAN7.0 step with detailed procedures, and make it and later convenient for maintenance engineers to use alarm reference

Highlight Show:
The following figure represents the improvement of alarm reference completion. SRAN7.0 SRAN8.0

08

Counter Documentation Improvement

Customer Concerns:
Counter reference need to be consistent with NBI-Lists(e.g. visible 0 counters, column names, Units). Combining and sort all counters using the same trigger point and explain the difference between the counters on one page (for handover and RAB chapters). NBI Lists: 2G Counter name = 3G Counter description. Need to be consistent!

Sub-Project & Objective:

No. Sub-Project Scope Objectives

2
3 4 5

Improvement of intermediate counters transparency Combination of pages describing counters using the same trigger point Improvement of column name consistency between Counter Reference and NBI-Lists Improvement of unit consistency of Counter Reference and NBI-Lists Improvement of consistency between counter name and counter description

SRAN8.0 and later SRAN8.0 and later

To help customers understand counter calculation principles To reduce document size to make it easy to read and search

SRAN8.0 and To make it convenient to search later SRAN8.0 and later SRAN8.0 and later To ensure the unit consistency of the same counters between the two documents To improve usage flexibility and make it easy to read by unifying modes

Highlight Show:
The improvements of Sub-Project 1 are as follows: 1. Add all the visible 0 counters in the Performance Counter summary to keep consistent with NBI list. 2. Add all the visible 0 counters description in the Counter Reference, as the following example. (A=B/C where B and c are visible 0 counters. We will put the description of B and C with A in the same page in order to shorten the documentation.)

SRAN7.0

SRAN8.0

Note: 1. A is visible=1 counter. 2. B and C is visible=0 counter.

09

One Documentation,

One Satisfaction

10