· Web viewDevelop unified GUI specifications and standards; optimize the iManager 12.0 before September 30, 2012. Sub-Project #3 Result: Improved in five aspects; 110 GUI improvement

WUGM Newsletter 2012.01 open

Huawei Wireless Network User Group Newsletter, Oct 2012OverviewAll eight Top N projects determined at the 2011 Huawei Wireless User Group Meeting (WUG

2011) have now passed the Deploy & Verify phase milestones. In October 2012, Huawei will

select appropriate projects that meet the requirements to summarize and standardize.

WUG 2011 Top N Project MilestonesAll the results of improvements and customer feedback are detailed as follows:

Issue 1: Local SupportSub-Project #1: Frontline Technical Skills ImprovementNo

.

Problem Analysis Proposed Solutions

1 Training and learning

mechanisms need to improve.

Usability of training documents

concerning typical network

problems (relevant to voice,

speed, dropped calls, and IP

problems) needs to improve.

Identify specific team to analyze typical

network problems and complete development

of 34 training courses by Q2 2012.

2 Skills transfer processes from

headquarters to local staff

need to be optimized.

Responsibilities of local offices

Optimize process for skills transfer from

headquarters to local offices: 80% of senior

supervisors will be assigned to oversee transfer

of skills to frontline staff in 2012.

2023-5-7 华为机密，未经许可不得扩散

第 1页, 共 22页


No

.


need to be clearly defined.3 Training programs not

effectively implemented at

local offices. Improvement

targets for local staff skills are

not clearly defined.

Set skills improvement targets and encourage

local staff to self-study. Organize headquarters

experts to deliver training at local offices on a

regular basis (550 local staff will receive

training in 2012). Select key local staff to

attend long-term training programs at R&D on

a regular basis (70 key local staff will receive in

2012).

Sub-Project #1 Result:New 34 typical troubleshooting guides have been published on a support website. We have

pushed them to the frontline through on-site training, the support website and emails to help

engineers improve their technical skills.So far, 75% of senior supervisors have been assigned and are working on skills transfers.Huawei has trained 4,223 staff using four training methods. The total number of trained

engineers increased by 100%.

After one year of improvements:The number of qualified senior engineers increased by 50%;

and qualified mid-level engineers increased by 37%;


第 2页, 共 22页


The frontline-resolved critical issue rate increased by 8%


第 3页, 共 22页


Sub-Project #2: Standardized Network Operations No

.


1 Part-time roles exist in some

network maintenance and

engineering delivery teams,

resulting in insufficient input

for network maintenance.

Reinforce project-based

operations of maintenance

projects. Update appointment of

maintenance teams for Q2 2012.

2 Routine network maintenance

is not effective enough,

resulting in possible risks that

become problems.

Establish mechanism to

implement network maintenance

Standard Operation Procedures

(SOP) on a semi-annual basis.

Sub-Project #2 Result:This year, we have set up maintenance teams for more networks. The changeover rate for

Operation Directors has decreased from 40% to 12%, and the changeover rate for Technical

Directors decreased from 36% to 9%.

Implemented Maintenance SOP on 174 networks during H1 2012. Number of critical issues

decreased by 50%, with a 20% drop in time for recovery.


第 4页, 共 22页


Sub-Project #3: Project Delivery ImprovementNo

.


1 Local delivery teams do not

meet five metrics for project

delivery: network design, site

solution, swap solution,

deployment solution, and

acceptance testing (they are

greatly dependent on

headquarters support in these

areas).

Headquarters to establish five subject matter

teams to develop corresponding guide

documents and tools and transfer required

subject matter skills to local teams to enable

local teams to independently perform these

tasks (for at least 70 projects in 2012).

Sub-Project #3 Result:


第 5页, 共 22页


Optimized delivery of five weak solution areas: Network Design, Effective Site Solutions,

Effective Testing Work, Effective Swapping and Effective BTS Deployment.Practiced 106 projects and trained 1,036 engineers. For Effective Swapping: correct mapping

rate reached 98% after delivery of an Algorithm Parameter Mapping solution; issues related to

antenna system installations were reduced by 90% after delivery of an Antenna System Check

solution.

Issue 2: DocumentationSub-Project #1: Provide “Engineering Guidelines” in Feature Parameter DescriptionNo. Problem Analysis Proposed Solutions1 Standardization

requirements for the

content of documents

should be made

clearer.

Improve writing standards, specify

requirements for content accuracy, and

add example cases as reference.

2 In “Parameter

Reference” documents,

description of

restrictions between

parameters needs to

improve.

In SingleRAN7.0 “Parameter Reference”,

improvements will be made to the

description of parameter

interdependencies between frequently

used commands.

In SingleRAN8.0 “Parameter Reference”,

improvements will be made in the

description of parameter

interdependencies involved in all major

commercially used features.3 In “MML Command In SingleRAN7.0 “MML Command


第 6页, 共 22页


Reference” documents,

default values for some

parameters need to be

completed.

Reference” documents, check default

values for all parameters, locate default

values for parameters related to the set

command, and complete all missing

default values.

Sub-Project #1 Results:The template’s optimization of “Feature Parameter Description” has been achieved:

Detailed descriptions for engineering guideline have been added to “Feature Parameter

Description,” which was implemented in the following versions:SingleRAN 6.0 (GBSS13.0 / RAN13.0 / eRAN2.1)SingleRAN 7.0 (GBSS14.0 / RAN14.0 / eRAN3.0)Feedback from customers:Thanks, improvement look very promising, you should publish it to all the customers. (From

Teliasonera Finland)Implemented enhancements are very much appreciated by DT.Design Team had the chance

to work with the enhanced FPD already. (From T-Mobile Germany)Sub-Project #2: Optimize Parameter Reference & MML Command ReferenceNo. Problem Analysis Proposed Solutions


第 7页, 共 22页


1 Document template

needs to improve to meet

the engineering needs of

customers.

Analyze missing content in instructions for

engineering deployment of features, optimize

document template.

2 The Feature Configuration

part includes only

descriptions about

"activation, deactivation,

and verification," which

cannot adequately guide

feature deployment.

Add the following information about engineering

deployment to the new and enhanced features in

the SingleRAN7.0 “Feature Parameter Description”

documents:

Feature enablement recommendation: advises when

and where to enable a feature or a combination of

features

Information collection prior to deployment: provides

information to be collected before a feature is

deployed

Network planning: provides recommendations,

principles, key tips, and restriction information about

radio frequency planning, networking planning, and

hardware planning

Feature deployment: describes processes,

requirements, data preparation, precautions,

hardware installation, activation, configuration,

enablement observations, and adjustment for

feature deployment

Performance optimization: provides information

about performance monitoring and guidance for

incumbent network parameter adjustment


第 8页, 共 22页


Sub-Project #2 Results:Optimized more than 5,000 unclear descriptions, providing more accurate information.

Documentation issues were reduced by 30%. For example:

Added more than 400 parameter relationships, ensuring visibility for all relevant parameter

changes. For example:

Added more than 300 default values for SET commands. For example:

Feedback from customers:There have been significant improvements in the amount of details provided in the

documentation (From Bell Canada)Sub-Project #3: Streamline Document Obtaining & Feedback ChannelNo. Problem Analysis Proposed Solutions

1 Information about

documentation

organizations and access

channel to product

documentation are not

well communicated to all

local offices and

customers.

From SingleRAN7.0 on, add information about

access channel to the document packages on the

support website for the LMT and M2000 clients.

From SingleRAN8.0 on, embed HedEx

documentation in product packages to implement

automatic installation and upgrade HedEx

documentation. (Huawei e-document Explorer)

Publicize Huawei’s documentation system and

access to documentation for local offices and


第 9页, 共 22页


customers on a regular basis.

2 Some customers do not

have necessary

permissions for the

Huawei Support website.

Review customers’ accounts and permissions for

the support website and optimize the account

application methods.

Sub-Project #3 Results:The following platform has been improved:HedEx: Added documentation overview chapter for how to obtain different components

(SingleRAN7.0).M2000/LMT Software: Automatic reminders of document package download, whenever you

upgrade the network (SingleRAN8.0).Customers can much more easily obtain documentation:Streamlined more than 30,000 old customer accounts.Added more than 3,000 new customer accounts.

Issue 3: O&M (E2E Network Management) Sub-Project #1: Control of Northbound Interface ChangesNo. Problem Analysis Proposed Solutions1 O&M baseline needs to be

improved.

Improve O&M baseline in Q2 2012: reinforce O&M

planning and design baseline restrictions.From SingleRAN8.0 on, realize consistent alarms

and consistent software upgrade model.2 O&M changes and

interconnection interfaces

changes occur due to

software upgrade.

Minimize changes of O&M model and northbound

interfaces for SingleRAN7.0.

3 Northbound interfaces are

not strictly frozen within

Northbound control team monitors the freezing of

northbound interfaces within three months prior to


第 10页, 共 22页


three months prior to the

GA point.

GA on a regular basis and ensures the accuracy of

interface documents.

Sub-Project #1 Result:To resolve O&M planning and design restrictions, we outputted an O&M baseline “Operational

Process and Pain Point Overview” to guide SingleRAN 8.0 planning and design.Achieved minimal changes to O&M models and northbound interfaces.

Succeeded to freeze northbound interfaces within three months prior to GA in SingleRAN 7.0.Sub-Project #2: O&M Efficiency ImprovementNo. Problem Analysis Proposed Solutions1 Focus on MBB O&M

scenarios, provide

high efficiency

features

Capacity Visibility: Through use of the network capacity

monitor tool, detected the cell with capacity bottleneck on

GIS system, and auto analysis issue by network KPI

Efficient Network Tuning: Optimized the BTS refarming

solution, the new program will improve the efficiency by 90%

Whole Network Configuration Verification: Data consistency

across OSS system verification to ensure the consistency and

validity of the data configuration of the entire network to

protect the terminal user quality of service and experience



第 11页, 共 22页


Capacity Visibility for Precise Expansion: New PRS (Performance Surveillance) tool provides

MBB capacity visibility and locates RAN bottlenecks.Efficient Network Tuning: Time reduced to 1/10Simplified MML Commands and Optimized Mechanism

Cross-OSS Parameter Consistency Check: Time significantly reducedReduced time spent on auditing whole-network parameter consistency from 24 hours to 1

hourSub-Project #3: GUI Usability ImprovementNo. Problem Analysis Proposed Solutions1 GUI design does not

meet customers’

habits.

Develop unified GUI specifications and

standards; optimize the iManager 12.0 before

September 30, 2012.

Sub-Project #3 Result:Improved in five aspects; 110 GUI improvement requirements have been fulfilled for iManager

12.0.


第 12页, 共 22页


Feedback from customer:Operations teams have stated that improvements for the M2000 GUI over the last release

(R12) are very impressive and do meet most requirements. (From DT)

Issue 4: CapacitySub-Project #1: Improve Capacity Planning CapabilityNo. Problem Analysis Proposed Solutions

1

Capacity visibility

tools or services

need to be

developed.

Include capacity visibility tools to be used for regular planning.

Provide capacity visibility reports in the Performance

Surveillance (PRS) by Q3 2012 and GUI support in 2013.

Give guidance service about capacity planning to customers

by Q3 2012.

Sub-Project #1 Result:Capacity monitor will be changed from a counter to a GUI in 2012 Q3, which is clearer in

observing resource usage and finding bottlenecks.Close to a 20% improvement in air interface capacity in RAN14.0.Sub-Project #2: Improve Capacity Processing EfficiencyNo. Problem Analysis Proposed Solutions1 A resource sharing

mechanism should be

developed between RNCs

For SinleRAN8.0, launch new BSC6910 that supports

dynamic configuration of CP/UP and CP pool, and

BSC6910 supports forming the RNC pool with BSC6900.


第 13页, 共 22页


No. Problem Analysis Proposed Solutionsand between SPUs within

the same RNCs.2 NodeB signaling

processing capability

needs to improve.

Increase NodeB signaling processing capability of

SingleRAN7.0 to ten times higher than that of

SingleRAN6.0.

Sub-Project #2 Result:BSC6910 (new RNC) will improve capacity efficiency by supporting pools on three levels:

dynamic CP/UP on one board, CP pool and UP pool between boards in RNC, pool between

RNCs. BSC6910 will be GA in 2013 Q2.Signaling capacity for NodeB has been improved to 1,500 CNBAP/s from 250 CNBAP/s for

SingleRAN 8.0 with new hardware.Sub-Project #3: Ensure KPIs for Key EventsNo. Problem Analysis Proposed Solutions1 VIP assurance needs

to be improved and

service assurance

solutions need to be

optimized.

For SingleRAN7.0, ensure system stability and service

experience through intelligent access controls. For

SingleRAN8.0, provide resource reserves for VIP customers to

ensure access and service experience.

Sub-Project #3 Result:In RAN 14.0, new features are provided to ensure KPIs and VIP user experience during key

events: Intelligent Access Control doubles access users; Platinum User Experience Guarantee

solution provides assurance for VIP users.


第 14页, 共 22页


Issue 5: Knowledge SharingSub-Project #1: Establish a Two-Way Interaction PlatformNo. Problem Analysis Proposed Solutions1 Knowledge sharing

needs to be optimized

to meet customer

concerns, like industry

changes, operation

experience, etc.

“Knowledge Sharing” is an all-encompassing topic concerning

our customers’ expectations to be able to share information

with each other on a variety of issues such as:

Operations experience and industry best practices

Network issues and advice for efficient operations of Huawei

networks

Applications of new technologies

Industry developments that change network deployment and

operations

2 Knowledge sharing

needs to establish a

two-way interaction

platform.

The current plan is to develop a channel within the existing

framework of Huawei’s web services, and allow registered

customers to search and select information according to their

own interests

Sub-Project #1 Result:A customer knowledge sharing forum is available nowThree main topics: industry insight, wireless technologies and O&M experience; more than 30

articles available at its launchVisit http://forum.huawei.com/ for registering, log-in and learning or sharing experienceSub-Project #2: Local Expert Training ProgramsNo. Problem Analysis Proposed Solutions1 Huawei need to

increase skills among

the people we meet

Huawei improve staff skill by the following ways:

Sparkle 2012 training program

“Zhu Jian Action” training program


第 15页, 共 22页


Global wireless expert (GEO) joint meeting

Sub-Project #2 Result:“Sparkle” local face to face training has been delivered during the first half of 2012 as follows:80 classes in 13 regionsStaff coverage rate: 67.7% Special training in 10 regions: DoneLocal staff satisfaction score: 78.1“Zhu Jian Action” training program (HQ-Local remote training) has been running since 2012

Q3 148 classes and 6,106 attendances from May to Aug. in total40+ sessions each month, nearly 40 attendees per sessionGUL classes: 50%, RF network planning: 27%Global wireless experts (GEO) meeting every month: More than 170 attendees globally each

month

Issue 6: Software Upgrade/PatchesSub-Project #1: Patch Implementation ImprovementNo. Problem Analysis Proposed Solutions1 A regular patch

implementation

communication

mechanism should be

established at local

offices.

Huawei’s Assurance & Managed Service Department

(AMS) issues an official document that requires that

patch implementation plans for the future three

months must be developed with customers for

commercial networks.

2 Unified plans for patch

implementation for

different products

Local service operation directors or CTOs update

patch implementation plans for all the product lines

on the networks they are responsible for and conduct


第 16页, 共 22页


should be made. regular communication with customers.

Sub-Project #1 Result:At the end of 2011, the notification Notice Concerning Implementing Version & Patch

Management was published which demands frontline engineers communicate three-month

version and patch plans to the customer. Until now, 95% of wireless networks have been

successfully implemented.


第 17页, 共 22页


Sub-Project #2: Patch Planning ImprovementNo. Problem Analysis Proposed Solutions1 Patches are not released by

headquarters on time as

planned.

Fully consider risks in patch plans and

communicate with customers in advance when

exceptions occur.2 Patch release notes are not

updated in time when patch

scope changes.

Improve patch release process from

headquarters and require that Bug Fix Lists

should be updated on time when patch scope

changes.

Sub-Project #2 Result:By optimizing the patch development process, patch planning punctuality rate reached zero

deviations since June 2012.

By improving IT platform efficiency, frontline engineers can get patch plans and all fixed-bug

lists ahead of time.Sub-Project #3: Patch Quality ImprovementNo. Problem Analysis Proposed Solutions1 Design of patch application

scenarios needs to

improve.

Improve library of patch application scenarios to

guide development design and verification

Sub-Project #3 Result:In order to enhance the quality of patches, we designed test strategies based on patch

requirements, commercial scenarios and patch documents.


第 18页, 共 22页


Through September 2012, the number of network problems has been reduced by 33.4%, and

the number of required patches has been reduced by 16.4%.

Issue 7: LifecycleSub-Project #1: EOX CommunicationNo

.


1 The EOX operation process

should be optimized and

some local offices have not

effectively performed their

EOX communication

duties.

Optimize the EOX operation process and clearly define

the initiation time, operation period, organizations, and

local offices’ responsibilities. Promote local offices to

actively communicate with customers on a regular basis

and conduct the first round of communication in Q2 2012.

Sub-Project #1 Result:In 2012, we developed a new dedicated IT support system (Front Communication Workflow) to

support EOX communications. Based on the new platform, EOX information is exchanged

more efficiently and communication processes are visible and clear for each step.We also added clear schedules for EOX communications in the EOX/PCN operation process

(EOX communications twice a year).2012 H1 EOX communications were based on new IT systems. Customer communications will

be finished by 9/30/2012.Sub-Project #2: EOX Documents Quality ImprovementNo Problem Analysis Proposed Solutions


第 19页, 共 22页


.1 Capability of document

writers needs to

improve and design of

document templates

should be optimized.

Develop the requirements for writing EOX documents and

require SE participation as a key role.

Optimize EOX document templates and add key information

that customers focus on (such as the specifications and

compatibility of new hardware and suggestions for

customers after hardware replacement).

Improve review checklist for EOX documents.

Sub-Project #2 Result:Based on the feedback from frontline staff and customers, we optimized the EOX document

template by adding descriptions:CompatibilitiesSpecification comparisonsCustomer changesResponse suggestionsWe have released the latest EOX documents for 2012 H1.Sub-Project #3: Hardware Compatibility EnhancementNo

.


1 Communication with

customers about O&M is

not effective enough and

design specifications need

to improve.

Collect and summarize customer feedback, complete

design specifications, and improve hardware

compatibility by Q2 2012.

Sub-Project #3 Result:In 2012, we developed compatibility criteria to maintain hardware design standards and

reduce the impact of hardware upgrades on customer network operations.


第 20页, 共 22页


Issue 8: Smartphone Ecosystem/Industry AlignmentSub-Project #1: Hot Topic Issues Collected & Solution PromotedNo

.


1 Platform and solutions Regular meetings

Hot topic issues collection

Sub-Project #1 Result:Operator hot topic issues collectedSolutions promoted accordingly Series of whitepapers for better smartphone networks and user experience released based on

real network issuesSub-Project #2: Industrywide Smartphone Initiative No

.


1 Industrywide

Smartphone Initiative

Proposed cooperation

Discussing within industries bodies

Sub-Project #2 Result:Cooperation proposed to identify: Common issues found in the industry created by SmartphonesIndustry requirements that can address those issuesSub-Project #3: mLAB Openness, Innovative Solutions, Apps Evaluation SystemNo

.


1 mLAB Openness,

Innovative Solutions,

Apps Evaluation

System

mLABs established for long-term openness, innovative

solutions

Creation of an Apps Evaluation System using the Apps

Insider tool



第 21页, 共 22页


Established mLABs in Shanghai and Silicon ValleymLABs outputted series of insight reports about: FaceTime, iOS and Android behavior

analysis, future network traffic forecastsCompleted development of Apps Insider tool; Apps Insider used to analyze and generation

solutions for better network friendliness and more balanced user experience

The main white papers can be downloaded from Huawei website:http://www.huawei.com/en/industry/huawei-voices/index.htmPaper1: Analyzing the Network Friendliness of Mobile ApplicationsPaper2: Smartphone Solutions white paperPaper3: Future smartphone solution white paperFor all Top Issues spanning from 2011 to 2012, Huawei would like to thank the following

operators for their collaboration and support: TELUS, Telenor, Bell Canada, Ufone, Vodafone,

Belgacom, Zain, Telefonica, Maxis, Deutsche Telekom, TeliaSonera, Optus, Mobinil,

FT&Orange, PCCW, Etisalat, Robi Axiata, China Unicom, and BYT. Their help has allowed

Huawei to further improve itself and become the industry-leading company that it is today.As always, your feedback on our progress is welcome. Please send any comments to:[email protected]

View the previous newsletter


第 22页, 共 22页