Beruflich Dokumente
Kultur Dokumente
Introduction to Core
Network Maintenance
Solution(CMS)
www.huawei.com
CMS Overview
Maintenance Tools Desktop Overview
Maintenance Documentation Overview
Version Planning and Feedback Channel
CMS
Maintenance Tools Desktop Maintenance
Documentation
Health check
Emergency
Log analysis
KPI analysis
Information
NE patch
handling
upgrade
collection
CN Related Recommended
maintenance SOP SOP software
SOP documents
Note:
Non-VTS software for MSOFTX3000 refers to InfoCollector V100R100C00SPC106
and HCT V100R100C00SPC103 , which are integrated into the Tools Software
Management page of the VTS console.
GU HLR9820 V900R003
HLR V9R3 N/A
CDMA HLR9820 V9
Note:
The maintenance tools of the STP, GGSN, SBC, and HLR9820 V900R003 are integrated into the Tools Software Management page of the VTS
console based on the CMS solution requirements. This facilitates automatic tool upgrade and download.
The maintenance tools of the STP include SG7000 Manex HCT and InfoCollector Tool and STP V800 health check tool.
The maintenance tool of the GGSN is MBB Gateway Inspect Tool V1.1.0.
The maintenance tool of the SBC is SBC Mul Inspect Check Tool V1.20
The maintenance tool of HLR9820 V900R003 is SingleSDBTOOL GU&CDMA Autocheck V100R001C01SPC020.
The IMS8.1 can use the VTS as its maintenance tool by manually installing the VTS mediation packages before the GA of CMS V100R001C01.
The tool is free-of-installation and only needs to be
The tool installation takes about 1.5 hours
and the installation may fail due to uncompressed, which takes about 10 minutes.
Both English and Chinese languages can be
complicated installation procedure.
Only one language can be installed on a installed on a computer.
computer.
The versatile tools suite (VTS) and NE The VTS and NE mediation packages can Tool
mediation packages are not released be automatically upgraded after Management
in a specified website. installation.
There are too many NE mediation The NEs maps NE mediation packages
packages with unclear mapping clearly.
relationship. The Maintenance tools are integrated and
Maintenance tools and tool patches provided on the VTS console.
are not listed.
The number of product application Template
The CN has more than 100 application scenarios is reduced to less than five by
using a unified scenario naming mode. Baseline for Tools
scenarios because of different naming
conversions. Report templates are unified.
All product reports are non-standard, Prewarning and rectification checks are
lacking some items such as fault impact added.
and fault handling suggestion. The template baseline for the maintenance
tool is provided.
Documents cannot be easily obtained because
they are not released in a specified path.
The maintenance SOP is released on the
HedEx platform.
Documents
You do not know which maintenance documents
The standard maintenance SOP and relevant
are for your use because they are not classified.
Any update in maintenance documents cannot document hyperlinks are provided for frontline
be reached to the frontline engineers in time. engineers.
The CMS minimizes skill requirements on frontline engineers and maximizes the check scope and depth.
CMS Overview
Maintenance Tools Desktop Overview
Maintenance Documentation Overview
Version Planning and Feedback Channel
Basic Functions
Network information collection
NE patch upgrade
Maintenance
New Features
Tools
Desktop Tool recommendation and
application management
Automatic upgrade of
tool patches
Automatic upgrade of
tool versions
After the CMS is adopted, massive CN collection scenarios are optimized to the following four
collection scenarios:
Accident analysis scenario: Supports quick fault feedback, analysis, and rectification. Information collected in this scenario
can be used to rectify 80% faults and locate 30% faults.
Offline health check scenario: Provides data for offline health check.. Information collected in this scenario can be used
for health check in various scenarios.
Common fault analysis scenario: Provides default information required for troubleshooting. Information collected in this
scenario can be used to locate 50% faults.
Extended information for fault analysis scenario: Provides supplementary information for troubleshooting. Information
collected in this scenario and that in the common fault analysis scenario can be used to locate 80% faults.
Tips
For the information collection, it is advised to adopt the policy More Information Collected Once, Multiple Feedbacks on
Demand.
1.When detecting a fault, use the information collection tool to collect information in the common fault analysis scenario and
extended information for fault analysis scenario.
2.When submitting a problem ticket, provide only information collected from the common fault analysis scenario. The
information collected in the extended information for fault analysis scenario is provided on request.
After the
optimization
After the CMS is adopted, massive CN check scenarios are optimized to the following four
check scenarios:
Inspection scenario: Supports the preventive maintenance for the delivery of the customer support
service.
Deployment and cutover scenario: Checks the device deployment and cutover.
Equipment status check scenario: Ensures that the equipment is operating properly. It is advised to
perform this check before and after major operations.
Prewarning and rectification check scenario: Checks prewarning and rectification items.
Automatically upgrades or
installs VTS mediation
packages online.
Automatically upgrades or
installs common maintenance
tools such as MAINEX.
Implements automatic
upgrade after logging in the
VTS console using the
correct w3 account.
After deploying the maintenance tools desktop, you can use the tool software management function on the VTS platform
to provide common maintenance tools (such as the MAINEX and KPI analysis tool) for frontline engineers to manage
tool installation, uninstallation, update, upgrade, and application.
CMS Overview
Maintenance Tools Desktop Overview
Maintenance Documentation Overview
Version Planning and Feedback Channel
You can obtain the latest maintenance SOP quickly, as HedEx Lite checks for the latest version of the
maintenance SOP on the support website every 48 hours and notifies you if the latest version is
available.
CMS Overview
Maintenance Tools Desktop Overview
Maintenance Documentation Overview
Version Planning and Feedback Channel
Feedback Channel
Requirement Feedback Channel
For any requirement in maintenance tools and documents, submit a request management (RM) workflow
by choosing Core Net > OSS AND SERVICE > CN Maintenance Solution RAT.
Problem Feedback Channel
For maintenance tool problems detected outside China, submit iCare problem tickets with the
product type set to Core Network OSS&Service to the xx GTAC-Core Network-OSS&Service-
PSE group. The maintenance tool problems detected in China need to be submitted to the
product group because China tool group has not been established.
For maintenance document problems, submit iCare problem tickets to the xx GTAC-Core
Network-OSS&Service-PSE group.