1. Improvements on U2000-MBB(Originally Referred to As M2000) V200R014 Product Documentations

2. Contents Change in the Product Name from M2000 to U2000
Improvements on U2000 Product Documentation
Improvements on Introduction to U2000 Feature
Improvements on Feature Description
Improvements on ATAE Cluster System Product Documentation
Improvements on Northbound Interface Documentations
Added "Contact Huawei technical support" for Obtaining Required Documents from Software Center

3. Change in the Product Name from M2000 to U2000
Unified OSS Brand
M2000
U2000 V200R014Cxx
U2000
Supports smooth upgrade, license reuse, and
reuse of the exist hardware.
U2000
U2000 V200R014Cyy
Depends on market requirements.
Now
2014
future
Huawei will use U2000 as a unified name for the OSS solution. This change will take place in 2014.
After the name is changed, the C version is used to distinguish between the U2000 for MBB and the U2000 for FBB.
Note: The C version of the U2000 for MBB ranges from 00 to 49, and the C version of the U2000 for FBB ranges from 50 to 99.
For details, contact Huawei technical support to obtain Huawei PCN M Name Change from M2000 to U2000.

4. Improvements on Introduction to U2000 Feature (1)
Voice of customers: It is hard to find the feature description documents corresponding to the feature list.
Action:
Feature Description Document
Operation and Maintenance Document
Parameter Description Document
Value:
Helps users quickly find different types of documents corresponding to the feature list.
Implemented in:
Issue 01 of U2000 V200R014C00

5. Improvements on Introduction to U2000 Feature (2)
Voice of customers: If a menu on the client is unavailable, how can I know whether this menu is controlled by a
license.
Action:
The License Control Function Menu List is added, which provides the mapping between the menus controlled by licenses, their licenses, and feature IDs.
Value:
Helps users quickly know whether a menu is controlled by a license when the menu is unavailable or is not displayed on the client.
Implemented in:
Issue 01 of U2000 V200R014C00
New

6. Moved from a third-level node to a first-level node
Improvements on Introduction to U2000 Feature (3)
Voice of customers: The contents in Introduction to U2000 Feature need to be improved.
Actions:
Introduction to U2000 Feature is moved from a third-level node to a first-level node in the document navigation tree.
The OSS14.0 column is added, which identifies feature changes in the new version.
Values:
Helps users quickly find Introduction to U2000 Feature.
Helps users quickly learn about the changes in the version.
Implemented in:
Issue 01 of U2000 V200R014C00 1
Moved from a third-level node to a first-level node 2
New

7. Obtaining the Introduction to U2000 Feature
2. Select a version.
3. Obtain the U2000 product documentation in HedEx format.
4. Obtain the mapping between features and the product documentation.
1. Log in to
5. Obtain the mapping between features, licenses, and portals on GUIs.

8. Improvements on Feature Description
Voice of customers: What is the optimization on new features in the feature description documents?
Action:
From M2000 V200R013C00, feature descriptions are regularly added based on the feature list and the feature descriptions are regularly optimized based on customer's requirements.
M2000 V200R012
M2000 V200R013
U2000 V200R014
New

9. Improvements on ATAE Cluster System Product Documentation (1) - Added Description Documents
Voice of customers: The ATAE hardware alarm report path is not provided.
Action:
The OSMU Faulty Management Description document is added.
Value:
Helps users know the OSMU fault management solution, including the fault management system architecture and alarm report paths.
Implemented in:
ATAE V200R002C00

10. Improvements on ATAE Cluster System Product Documentation (2) - Added Routine Hardware Maintenance
Voice of customers: The routine maintenance guide related to the ATAE hardware is not provided.
Action:
The Hardware Routine Maintenance document is added.
Value:
Guides users to perform routine maintenance on the ATAE hardware.
Implemented in:
ATAE V200R002C00

11. Improvements on ATAE Cluster System Product Documentation (3) - Added Abbreviations
Voice of customers: What are the meanings of hardware-related abbreviations in the ATAE cluster documents?
Action:
The Abbreviation node is added.
Value:
Helps users learn about the abbreviations related to the ATAE cluster system.
Implemented in:
ATAE V200R002C00

12. Improvements on ATAE Cluster System Product Documentation (4) - Added Indicator Introduction
Voice of customers: How can I determine whether the ATAE hardware is running properly?
Action:
Introduction to indicators is added to the Hardware Description node.
Value:
Guides users to check whether the ATAE hardware is running properly.
Implemented in:
ATAE V200R002C00

13. FAQ
Question:
There are two product documentations related to the ATAE cluster system, U2000 Product Documentation and ATAE Cluster System Product Documentation. How can I use them?
Answer:
Refer to the description provided in Wireless OSS Documentation_Issue 01_2014.pdf.

14. Unified documentation navigation architecture
Optimized Navigation Tree (1) – Unified Documentation Architecture
Voice of customers: The documentation navigation tree is different, interfering use habits and increasing the search difficulty.
Action
All northbound documentations use a unified navigation tree.
Value:
Users can quickly find required content.
Implemented in:
Issue 01 of U2000 V200R014C00
Before the improvement:
Unified documentation navigation architecture
Range:
All northbound documentations
File path:
..\ReleaseDoc\CHN\07.Northbound File
After the improvement: 1
Part One
Overview
Part Two
Interconnection commissioning
Part Three
Introduction to configuration files, interfaces, packets, and file export
Part Four
Common Faults and Troubleshooting
Part Five
Appendix (Optional) 2 3 4 5

15. Interface and notification functions added in the navigation tree
Improvements on Northbound Interface Documentations (1) – Added Key Information Sections
Voice of customers: Key information (interface and notification functions and license checking) is not displayed in the navigation tree, causing search inconvenience.
Action:
Key information (interface and notification functions and license checking) is added to the navigation tree.
Value:
Key information is intuitively displayed in the navigation tree, facilitating search.
Implemented in:
Issue 01 of U2000 V200R014C00
Before the improvement:
After the improvement:
Added
Interface and notification functions added in the navigation tree
Range:
All northbound documentations
File path:
..\ReleaseDoc\CHN\07.Northbound File

16. An FAQ added to the U2000 Northbound CORBA Interface Developer Guide
Improvements on Northbound Interface Documentations (2) – Added Network Exception Troubleshooting Cases
Voice of customers: Network exception troubleshooting cases are insufficient.
Action:
The FAQs about network exception troubleshooting methods are provided.
Value:
Users can resolve problems by following the instructions provided in this troubleshooting case when a network exception occurs.
Implemented in:
Issue 01 of U2000 V200R014C00
U2000 Northbound CORBA Interface Developer Guide
An FAQ added to the U2000 Northbound CORBA Interface Developer Guide
Range:
U2000 Northbound CORBA Interface Developer Guide
2000 Northbound CORBA Interface Developer Guide and 1.7.0
File path:
..\ReleaseDoc\CHN\07.Northbound File
Note:
This requirement is from the internal maintenance engineers.

17. Simplifying the operation steps, which reduce from 14 to 4
Improvements on Northbound Interface Documentations (3) – Simplified Operation Procedures
Voice of customers: The operations for interconnecting the alarm SNMP interface are redundant, and optional operations are not marked, misleading users.
Action:
1. The optional operations are marked.
2. The redundant operations for interconnecting the alarm SNMP interface are deleted.
Value:
The operations are simple and clear so that users will not be misled by optional operations.
Implemented in:
Issue 01 of U2000 V200R014C00
Before the improvement:
After the improvement: 1
Marking optional operations and allowing users to perform operations as required 2
Range:
All northbound documentations
U2000 Northbound Alarm SNMP Interface Developer Guide
File path:
..\ReleaseDoc\CHN\07.Northbound File
Simplifying the operation steps, which reduce from 14 to 4

18. Description about the parameters in the exported file is optimized.
Improvements on Northbound Interface Documentations (4) – The formats of configuration export files are optimized
Voice of customers: I do not know the differences between the export of configuration files in the flat and tree export modes.
Action:
The sections of the export of configuration files in the flat and tree export modes are provided in the navigation tree.
The definitions of fields in the exported file are optimized, showing the differences between the export of configuration files in the flat and tree export modes.
Value:
Users can understand the content of the exported file according to the document.
Implemented in:
Issue 01 of U2000 V200R014C00
Export of configuration files in the flat and tree export modes are distinguished in the navigation tree.
Description about the parameters in the exported file is optimized.
Clarifying differences of the export of configuration files in the flat and tree export modes
Range:
U2000 Northbound Configuration File Interface Developer Guide
File path:
..\ReleaseDoc\CHN\07.Northbound File

19. Added "Contact Huawei technical support" for Obtaining Required Documents from Software Center
Voice of customers: The description for downloading software and documents from Software Center is mentioned in
many documents, but I cannot find Software Center at
Action:
"Contact Huawei technical support" is added to the documents.
Value:
Guides users to obtain the required documents.
Implemented in:
U2000 V200R014C00
CME V200R014C00
PRS V200R014C00