U2020 MBB V300R019C10 New Functions and Major Changes-201903

Security Level: Internal
New Functions and Major

Changes of U2020 MBB V3
00R019C10
www.huawei.com
Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.

Contents
 U2020 Alarm Function Changes

 Overview of Alarm Function Evolution
 New Alarm Functions
 Modified Alarm Functions
 U2020 Security Function Changes
 U2020 Engineering Management Function Changes
 U2020 MML Function Changes
 U2020 NBI Changes
 U2020 Resource Changes
 U2020 O&M Function Changes
 Reference Documentation
HUAWEI TECHNOLOGIES CO., LTD. Page 3

Overview of Alarm Function Evolution
I. New Service-oriented Architecture
 U2020 supports alarm management in ultra-large-scale networks in the future, service-level high reliability, and uninterrupted alarm services during
upgrades.
II. Better Alarm Visualization
 The WebUIs conform to Agile UI 2.0 to achieve better O&M experience and are close to operation habits on the traditional OSSs.
 Multi-dimensional alarm monitoring dashboards are provided to help users quickly obtain concerned data with alarm statistics and data drilling.
 The number of tabs and layers is reduced, complying with the flat design principle in the Internet industry and improving usability.
 Settings are completed in one-stop mode and information is displayed in a centralized manner, improving alarm setting efficiency.
 Alarm information display is more flexible (for example, alarm columns can be adjusted and alarm details panel can be expanded), helping users
quickly troubleshoot faults.
III. AI-based Alarm Automation
 According to the time-based dynamic adaptive threshold analysis, U2020 automatically compresses toggling alarms in real time and reduces the
toggling alarms by 90%.
 U2020 learns alarm correlation rules based on PrefixSpan and aPriori, searches for location correlations of alarms, and improves the correlation
accuracy by analyzing alarm object correlation parameters.

Contents


New Function – UI Changes
Background
Alarm operations are moved to the WebUI, proving simplified O&M experience.
Benefits
The alarm WebUI is based on Agile UI 2.0 and the java-based client, proving users with better O&M experience.

New Function – Alarm Dashboard
Background
The alarm dashboard displays alarm statistics clearly, improving O&M efficiency.
Benefits
The alarm dashboard provides the following 5 types of statistical reports:
1. Top 10 alarms: provides statistics on top 10 alarms by alarm ID, helping users quickly identify faults that occur most frequently so that users can know the
focus.
2. Statistics on alarm duration: provides statistics on the number of alarms whose duration is less than 10 minutes, 10 minutes to 1 hour, 1 hour to one day, and
more than one day, so that users can quickly identify the alarms that are recently reported.
3. Top 10 devices: provides statistics on the top 10 devices where alarms most frequently occur so that users can focus on these devices (NEs).
4. Statistics by alarm severity: provides statistics on the number of alarms by alarm severity (critical, major, minor, and warning) so that users can handle
alarms by severity.
5. Statistics by the alarm acknowledgement and clearing status: provides statistics on the number of unacknowledged and uncleared alarms, acknowledged
and uncleared alarms, unacknowledged and cleared alarms, and acknowledged and cleared alarms. Users can view the alarms by alarm processing status.
Restrictions on Scenarios
1. The dashboard statistics varies by the selected filter criteria.
2. The dashboard is not expanded by default. Users need to
click the button in the upper-right corner of the current alarms
page.
Restrictions on Specifications
1. The alarm dashboard is available only for the current
alarms.
2. A maximum of four dashboards can be displayed at a time.

New Function – Intelligent Alarm Association
Background
Traditional alarm correlation processing relies on the preconfigured expert experience. When the network environment or version changes, the rule library must
be updated manually, which is time- and labor-consuming, which does not meet requirements of evolution to automatic network O&M.
Benefits
U2020 provides the intelligent alarm correlation function. U2020 analyzes alarms in multiple scenarios, automatically identifies the correlations between the
alarms, and then generates alarm correlation rules, freeing users from manually analyze, configure, and update correlation rules and thereby improving alarm
processing efficiency.
The automatically obtained correlation rules

are displayed on the Result Rules page
before they are activated. After a rule is
activated, it is moved to the Correlation 1. O&M personnel need to select NEs and manually create
Rules page and takes effect for subsequent
auto-learning tasks.
alarms.
2. The automatically obtained rules do not take effect by
default and need to be activated by O&M personnel after
confirmation.
U2020 allows users to activate a maximum of 1000 alarm
Users need to manually create auto-
learning tasks, specify NEs and time correlation rules.
range of alarm samples. Auto-learning
tasks are classified into one-time tasks
and periodic tasks.

New Function – Intelligent Alarm Compression
Background
Root cause locating and customer appraisal will be affected if there are a large number of toggling alarms. Therefore, toggling alarms must be reduced. In earlier versions,
toggling alarms are suppressed by manually configured suppression rules, which are based on the fault occurrence frequency. However, the fault occurrence frequency varies
among different faults and even in the same fault. It is difficult to determine this frequency among the large number of alarms, let alone adjusting the frequency. Therefore,
U2020 needs to automatically identify the frequency and dynamically adjusts the suppression rules to minimize toggling alarms.
Benefits
U2020 automatically analyzes alarms and generates proper alarm suppression rules. Within the time (time window) specified by the rule, if the number of same alarms reported
by an NE exceeds the preset threshold, U2020 combines the alarms and displays only the first reported alarm on U2020 and NMS, and adds the alarm occurrence times to
additional alarm information. The toggling alarms can be reduced by more than 90%.
1. The function is disabled by default and needs to be manually
Global tuning parameters are used to enabled.
set the range of the time window for 2. The automatically obtained alarm suppression rules take effect by
An auto-learning task is disabled by observing the suppression rules.
default. Users can enable it as required.
default.
After the function is enabled, the clear 3. There are three policies for the customized alarm suppression
alarm corresponding to the alarm that rules:
enters the toggling period is reported one Rule Only Analysis: Rules are analyzed without being displayed on
to multiple periods later. The delay time the Intermittent/Toggling Rules page.
depends on the number of alarm toggling
times. Rule Enable: Obtained rules are displayed on the
Intermittent/Toggling Rules page and take effect by default.
For customized alarm suppression Rule Disable: Obtained rules are displayed on the
rules, O&M personnel can set different Intermittent/Toggling Rules page but do not take effect by default.
tuning range for specified alarms
based on site requirements. U2020
provides certain default rules and Restrictions on Specifications
allows users to customize rules. U2020 supports a maximum of 1000 alarm correlation rules. If the
rule quantity exceeds the threshold, the earliest rule or the rule with
the lowest suppress effect is automatically deleted.

Contents


Modified Function – Shortcut Menu Items Are Replaced with Buttons
Background
1. WebUI needs to provide customers with simpler operations.
2. User operations need to conform to web operation specifications.
Benefits
The shortcut menu items are replaced with one-click operations on the WebUI, improving user operation efficiency and conforming to web operation
specifications.
1. Alarm acknowledgement, unacknowledgement, clearing, and
check are the most frequently used functions and need to be
implemented in one-click mode.
2. Shortcut menu functions, such as alarm masking, frequency
analysis, and intermittent alarm analysis, are infrequently used
and are now placed under Operation > More. The overall WebUI
layout is not affected.
None

Modified Function – Flat Filter Panel
Background
Tabs and layers need to be reduced to comply with the flat design principle in the Internet industry and improve usability.
Benefits
All the filter criteria are clearly displayed on one panel, improving the operation efficiency.
1. The common filter options are tiled for users to set.
2. The filter options that are infrequently used are placed under
More.
None

Modified Function – Template Management in Favorites
Background
Benefits
Templates are easier to use and manage.
1. Templates are managed in favorites, which is close to user habits. Users can click a template name to quickly obtain alarms meeting the template
requirements.
2. Users can use the default templates, add templates to default ones, and set templates that they want to follow.
Templates are available for Current Alarms, Alarm Logs,
Historical Alarms, Event Logs, and Masked Alarms.
Change Item On U2000 On U2020
Template The template status for Users can set default
category the current user can be templates but cannot set
set. The monitor the startup templates and
template, startup monitor templates.
template, and default Users can add templates
template can be set for that they often use to
the current user. favorites. The favorite
templates will be
displayed in Favorite.

Modified Function – Viewing Alarm Details in Collapsible Panel
Background
Benefits
On the expanded panel, users can obtain all required information about an alarm, such as alarm details, root and correlative alarms, maintenance experience,
and comments.
None

Alarm export format Alarms can be Alarms are exported to an
exported as CSV, XLSX or CSV file.
TXT, HTML, PDF, TXT, HTML, XLS, and
XLSX, or XLS files. PDF files are not
supported for now.
Preferences Supported Not supported

Local settings,
sound and color
settings

Modified Function – Correlation Rules
Background
The latest industry terms and specifications are used for correlation analysis.
Benefits
Industry terms and specifications are used to redefine the analysis rules based on the original frequency analysis and intermittent analysis rules, facilitating user understanding.
None
Frequency analysis is Frequency analysis rule: When Aggregation rules: After a rule is set, when the
replaced with the number of alarms or events number of times that an alarm (with the same alarm
aggregation rules. generated within a specified name, alarm ID, and alarm group ID) is reported by
Avalanche alarms and period exceeds the specified the same NE in a specified period meets the trigger
toggling alarms are threshold, the alarms or events condition, the aggregation starts and a new
replaced with are handled based on the aggregated alarm is generated. All the alarms that
aggregation alarms. specified policy. meet the condition are marked as the original
alarms. When the number of times that an alarm
(with the same alarm name, alarm ID and alarm
group ID) is reported by the same NE meets the
termination condition, the aggregation stops.

Modified Function – Management of Remote Notification
Templates
Background
In earlier versions, users need to set notification contents each time they set a remote notification rule, affecting O&M efficiency.
Benefits
1. Notification templates are managed on a specific page. Users can use default templates, customize a template before creating a remote notification rule, or
add, delete, modify, or query a template when creating a remote notification rule.
2. Template parameters and notification contents can be customized, improving usability and readability.
None
Independent remote Supported Not supported
notification client
These parameters in
blue are variables and
can be customized as
required.

Modified Function – Web-based NE Alarm Settings
Background
1. WebUI needs to provide customers with simpler operations.
2. User operations need to conform to web operation specifications.
Benefits
The NE alarm setting function is moved from the java-based client to the web-based client, improving operations efficiency.
1. Frequently used functions, such as import, export, add, and
query, can be implemented with one click.
2. Alarm rules can be selected in batches.
3. A record can be easily modified or undone within the table.
None

Modified Function – Alarm Browse is Unavailable on Topo UI
Description
In previous U2000 version, user can open “Browse Current Alarms” window on Topo UI. This function is unavailable now in U2020 R19B TR5 version. It will be ok
in R19B GA version.

Contents

 Overview of Security Function Evolution
 New Security Functions
 Modified Security Functions

Overview of Security Function Evolution
 Supports security management in the ultra-large-scale networks in the future, service-level high reliability, and uninterrupted security services during upgrades.
II. Better Security O&M Experience
 Provides WebUIs conforming to Agile UI 2.0 to achieve better O&M experience and be close to operation habits on the traditional OSSs.
 Provides clear service data, flat design, reducing displayed dialog boxes and improving the usability.
 Provides one-stop service settings and displays information in a centralized manner, improving security setting experience.
III. Enhance Service Capabilities, Better User Information Management and Management Domain Authorization Experience
 NE authorization management scale is increased.
 Users are classified into local users, remote users, and third-party access users. Differentiated security control policies are used for different types of users.
 Remote authentication servers can be configured on the WebUI, SSO is integrated among systems, improving security O&M experience.

Contents


New Function – A Web Login Entry Is Provided
Background
Traditional OSSs are accessed from a java-based client. During the login, many modules need to be loaded, affecting the efficiency. Now, U2020 provides a web-
based client for login.
Benefits
1. A web login entry is provided and a feature description page is added.
2. Users can log in to U2020 using browsers.
None
Requirements on browsers and resolution are as follows:
Internet Explorer 10.0, Internet Explorer 11.0, Firefox ESR
31.X, Firefox ESR 38.X, Firefox ESR 45.X is recommended.
The recommended resolution is 1920 x 1080 and the
minimum resolution is 1366 x 768.

New Function – Local Users, Remote Users, and Third-party
Access Users Are Provided
Background
Users are classified into local users, remote users, and third-party access users to meet requirements of different scenarios.
Benefits
1. Local users are used for local authorization and login. Remote users are used for centralized authentication. Third-party access users are used for inter-system
access.
2. Differentiated security control policies are provided in different scenarios to facilitate user management.
1. Remote users are used for centralized authentication.
Passwords are not required when a remote user is created.
2. Third-party access users are used for inter-system access
and cannot be used for logging in to the web client.
None

New Function – SSO Provided Among Multiple Systems and
Interconnection Parameters Configured on the WebUI
Background
If multiple products are integrated in a solution, SSO must be supported, and a unified login entry must be provided.
Benefits
1. Multiple systems are integrated with SSO, reducing the number of login times and improving user experience.
2. After SSO is enabled, user and permission can be managed in a unified manner, reducing the workload of inter-system management.
U2020 can function as an SSO server or an SSO client, and
can integrate other products or be integrated.
Multiple-product integration depends on the user model. Only
products that are deployed on the same platform can be
integrated.

New Function – Setting Log Forwarding Rules and Customizing
the Types of Audit Logs to Be Forwarded
Background
The security function on U2020 allows users to set different forwarding rules for system logs, security logs, and operation logs.
Benefits
1. Different forwarding rules can be set for system logs, security logs, and operation logs.
2. The log forwarding can be based on the log level.
None
None

Contents


Modified Function – WebUIs for User Management
Background
1. WebUIs are provided for the user management function.
2. The user information rows can be expanded. The infrequently used functions are placed under More. User status is represented with different colors.
Benefits
1. User information is displayed clearly, helping users quickly view user status.
2. An Operation column is added so that users can quickly reset passwords, delete users, enable or disable users, and copy user information.
1. Users, roles, regions, managed objects, operation
sets, and online users are displayed on the User
Management page in the accordion mode.
2. You can batch create, modify, import, export, move,
and unlock users.
A maximum of 500 users can be imported at a time. User
admin cannot be modified using the imported data.

Modified Function – Role-based Rights Management and
Multiple Management Domains
Background
For role-based rights management, roles are the unit and carrier of rights allocation. Note: The function of a role is similar to that of a user group.
All managed objects, device types, subnets, device sets, and individual devices in management domains are displayed on multiple tab pages.
Benefits
1. Roles can be created by step. You can click Save to quickly complete the step-specific role creation.
2. Management domains can be displayed on multiple tabs. Users, management domains, and operation rights that are bound can be edited separately. The display and
editing operation modes are diversified.
None
None

Modified Function – Optimized Authorization Function for
Management Domains
Background
1. On U2000, there are many management models, the number of bound management objects is not limited, and application rights and device rights are not clearly distinguished. As a result, authorization management is
complex for customers.
2. The cloud-based security function limits the number of bound management objects and provides the guidance on the subnet-based authorization model. All application rights and device rights are displayed separately.
3. Single subnet authorization on U2000 does not affect user's management domains. Single-subnet authorization is removed from the cloud-based security function.
4. Direct single-user authorization may incur a high maintenance workload during permission changes. By default, direct single-user authorization is disabled, and role-based authorization management is recommended
for the cloud-based security function.
Benefits
The optimized authorization function helps users use the authorization model based on roles and subnets to support large-scale NE management scenarios and simplify authorization management.
None
Maximum number of objects (excluding devices) that can be managed by each user or role: 50
Maximum number of devices that can be managed by each user or role: 2000
Maximum number of application-level operation rights that can be bound to each user or role: 2000
Maximum number of device operation sets that can be selected in the object set bound to each user
or role: 100
Maximum number of device operation sets that can be selected in the subnet bound to each user or
role: 100
Maximum number of device operation sets that can be selected in the device set bound to each
user or role: 100
Maximum number of device-level operation rights that can be selected in the device bound to each
user or role: 100
Maximum number of device-level operation rights that can be selected in the device type bound to
each user or role: 100
Maximum number of devices in each device set: 5000
Maximum number of operation rights in each operation set: 2000
In upgrade scenarios, the U2020 with extra-large data can be upgraded, and the number of bound
entries can be decreased but cannot be increased.

Modified Function – Centralized License Management
Background
1. In earlier OSS versions, license query and license capacity alarm configuration are implemented on separated pages, causing redundant information.
2. License information is displayed in modal dialog boxes and multiple modal dialog boxes cannot be opened concurrently.
Benefits
The license query and license capacity alarm configuration pages are integrated.
None
None

Modified Function – Combined the Page for Revoking Licenses and
That for Querying Revocation Code
Background
In earlier versions, license revocation and license revocation code query are performed on two pages.
Benefits
The page for revoking a license and that for querying the license revocation code are combined into the license file query page, improving the usability.
None
None

Modified Function – MML Rights Management Moved to the
Web Client
Background
The pages for managing MML rights based on subnets, NEs, and rules are combined as one page to facilitate user operations. Users can manage MML rights based on a single
subnet or a type of NEs on the entire network, or set special MML permissions for a single NE.
Benefits
The following three MML rights management functions are supported:
1. You can set the MML rights of a user or a role for an NE type under a subnet. The setting takes effect for all NEs of this type on the subnet and is automatically inherited for
new NEs of this type added to the subnet.
2. You can set the MML rights of a user or role for a type of NEs. The setting takes effect for all NEs of this NE type and is automatically inherited for new NEs of this type.
3. You can set the MML rights of a user or role for an NE. The settings take effect only for the NE.
All rights assigned to a role are automatically inherited by users of this role. The three functions are used for different O&M scenarios, and you can use them as required.
1. Region-based subnet management is
recommended.
2. You are advised to use roles to manage rights.
Users of a role automatically inherit the rights
settings for the role. If a user belongs to multiple
roles, all rights of these roles are granted to the
user.
3. You are advised to manage MML rights by subnet
or NE type. If you want to grant special rights to an
NE, manage this NE separately.
None

Modified Function – MML Command Group Management
Moved to the Web Client
Background
If the default MML command groups of NEs cannot meet the O&M rights requirements, you can customize MML command groups.
Benefits
You can customize MML command groups to specify MML commands that are available for a user.
1. You can set the default MML command groups, such as the basic command group, system command group, alarm query command group, alarm management
command group, performance query command group, and performance management command group.
2. You can customize the MML commands for users to issue commands as required.
None
Restrictions on
Specifications
Currently, a maximum of 500
customized MML command
groups are allowed. The MML
command quantity in a single
MML command group is not
restricted.

Modified Function – Multiple Filter Criteria Provided and Batch
Operations Performed Step by Step
Background
The filter dimensions are added and the UI design is flat, improving usability.
Benefits
1. Users can be filtered by user type, user status, and user name.
2. Batch modification and movement can be performed step by step and user information is clear.
None
Restrictions on
Specifications
A maximum of 100 users can be
modified or moved at a time.
System administrators and default
users cannot be modified in
batches.

Modified Function – Passwords and Personal Information Can
Be Changed on the Personal Settings Page
Background
User information on U2000 does not contain mobile numbers or email addresses. In U2020 V300R019C10, users can change their mobile numbers and email
addresses for remote notifications.
Benefits
1. Users can change personal passwords, mobile numbers, email addresses, and auto-logout timeout duration on the Personal Settings page to reduce the
workload of system administrators.
2. Users can configure their mobile numbers and email addresses for remote notifications.
Restrictions on
Scenarios
None
Restrictions on
Specifications
None

Modified Function – Improved Account Policies for Security in
Cloud-based Networking
Background
Account policies are improved to support security in cloud-based networking. The warning information setting function is added, and sessions that do not meet
the ACL policy can be deleted.
Benefits
1. Default security policies are used by system administrators and default accounts to prevent security policy levels from being reduced and to improve security.
2. Warning information can be customized on the WebUI.
Restrictions on Scenarios Restrictions on Specifications

None None

Modified Function – Optimized Log Query Filter Panel
Background
On the traditional GUI, the filter criteria displayed in the dialog box occupies a large area, and users need to set the filter criteria each time they open the log
query page.
Benefits
1. When users navigate to the log page, logs generated on the last day are displayed by default. This improves usability.
2. The filter panel can be expanded so that much table data can be displayed and many items are available for template operations.
Restrictions on
Scenarios
None
Restrictions on
Specifications
None

Modified Function – MML Command Rights Management and
NE User Management
Background
1. MML command rights management for NE users in U2000 versions is not clearly arranged and is decentralized. In the cloud-based U2020 version, this
function is redesigned, and multiple relevant pages are integrated into one.
2. The WebUI facilitates operations. Users can quickly configure MML command rights on the WebUI without loading client components.
Benefits
1. This function allows you to maintain MML command rights of users or roles by O&M scenario of current NEs.
2. This function is more easy to use than before.
None
None

Contents

 Overview of MML Command Evolution
 New MML Command Functions
 Modified MML Command Functions

Overview of MML Command Evolution
 The service-oriented architecture can support the construction of ultra-large network configuration management capability in the future, service-level
high reliability, and uninterrupted MML services during upgrades.
II. Improved MML Command O&M Experience
 The U2020 WebUI observes Agile UI 2.0 to achieve better O&M experience and close to operation habits of U2000.
 Key pain points related to MML command functions, such as NE selection, command input, parameter display, and command output display, are
resolved based on customer surveys at multiple sites.
 The number of tabs and layers is reduced to comply with the flat design principle of the Internet and improve usability.

Contents


New Function – A Cheat Sheet Is Provided for Shortcut Keys of MM
L Functions
Background
Shortcut keys are provided for some frequently used MML commands, but these shortcut keys are displayed on the UI, which is inconvenient for users.
Benefits
Users can press shift + / to view the cheat sheet of shortcut keys, improving operations efficiency.
Only the frequently used shortcut keys
are listed now. Operations related to
the command output area are not
provided. To obtain all command
output, export it.
None

New Function – Customizing NE Groups When Selecting NEs
Background
Users must select NEs before performing MML command operations. It takes a long time to select NEs, especially when users select a lot of NEs. Although the
existing U2000 allows users to import selected NEs in batches, a local file script is required. Typically, users select NEs in the navigation tree, export the selected
NEs to a local script, and select the script to import NEs if required.
Benefits
You can add the selected NEs in the navigation tree to a user-defined NE group. In follow-up operations, you can select NEs from the user-defined NE group,
improving the operation efficiency.
None
Each user can create a maximum of
100 NE groups.

New Function – Adding Commands to Favorites
Background
During routine O&M, there may be MML commands that are executed frequently. Although executed MML commands can be found in past commands, the number
of past commands that can be displayed in the command history list is limited. When navigating to the MML command page the next time, users still need to search
for the past commands.
Benefits
You can add common commands to favorites. In follow-up operations, you can quickly select commands from favorites, improving operation efficiency.
Restrictions on
Scenarios
None
Restrictions on
Specifications
Each user can add a
maximum of 100
commands to
favorites.

New Function – Exporting MML Command Outputs to CSV Files
Background
MML command outputs can be saved as a TXT file. However, there may be a large number of command parameters, and the command output with a certain
length may be saved in a TXT file. When the text editor is used to open this file, the length of a single command line may reach the specified maximum number of
characters and the command output is automatically displayed in a new line. As a result, the overall layout of the command output is in disorder, jeopardizing
command viewing and editing.
Benefits
If the command outputs are saved as a CSV file, the original attributes are displayed in different columns. The overall display effect is similar to that in tables,
facilitating the command output searching and editing, reserving the command output display effect, and improving operation efficiency.
None
None

Contents


Modified Function – Integrated Command Input Portals and
Search Portals
Background
The U2000 client provides many command input portals and search portals, including the command list and command tree.
Benefits
The U2020 WebUI integrates command input portals and search portals and allows you to switch to the command tree or command list, simplifying operations
and improving operation efficiency.

None None

Modified Function – Optimized Command History Portals
Background
The U2000 client provides multiple command history portals, including the MML command page and history review page.
Benefits
The Command History page simplifies operations, allows you to back fill past commands, re-execute past commands, and view command details and the
number of NEs experiencing command execution failures, improving user experience and operation efficiency.
None
None

Modified Function – Enhanced Parameter Panel
Background
The parameter panel size is limited. A scroll bar is displayed when there are many parameters. In such a case, it is difficult to view all parameters.
Benefits
The enhanced parameter panel improves user experience and operation efficiency.
1. The parameter panel displays mandatory parameters only, facilitating parameter settings.
2. The parameter panel can be displayed separately and zoomed in or out manually to view all parameters.
None
None

Modified Function – Integrated Command Output Panes
Background
The clients of earlier versions display command outputs by pane. The upper pane displays instant command outputs. The lower pane displays subsequent
command outputs and provides the function of subscribing to subsequent command outputs. This function broadcasts events and may display a large number of
command outputs related to other service operations. To query complete command outputs of an asynchronous task, users need to search for and filter the
command outputs. As a result, this process is time-consuming.
Benefits
After command output panes are integrated, the subscription to subsequent command outputs is canceled, subsequent command outputs are processed by
default, and command outputs irrelevant to user operations are not displayed. The integration helps you view complete command outputs, improving user
experience and operation efficiency.

None None

Contents

 Overview of Engineering Management Evolution
 New Engineering Management Functions
 Modified Engineering Management Functions

Overview of Engineering Management Evolution
In U2020 V300, the ATAE OSMU and the vOSMU and integrated into OSMU (management planes are integrated). The OSMU provides
O&M WebUIs and experience.
The OSMU can be deployed in ATAE cluster systems or virtual cluster systems. The display modes and operation guidance of O&M
WebUIs are optimized on the OSMU to improve operation efficiency.
After the integration for ATAE cluster systems

1. The OSMU allows you to switch to the device panel page of the original ATAE OSMU.
2. The GUI style is changed, and the layout of menus and buttons is optimized to improve usability.
 The plan management function is added to the OSMU.
 Maintenance tasks are executed based on the wizard.
 One page is used to manage the services of boards and systems.
 The version information of the U2020, operating systems, databases, and cluster systems can be queried.
After the integration for virtual cluster systems

1. The system monitoring page is optimized, and operation setting pages are integrated to improve usability.
2. The hardware alarm reporting process specific to virtualization pre-integration is optimized. The OSMU can directly forward
hardware alarms to the U2020.
3. The OSMU allows you to register FusionSphere API interconnection information.
4. The OSMU allows you to register CSM interface interconnection information.

Contents


New Engineering Management Functions
No. New Engineering Management Function Benefit
1 The cloud-based OSMU supports product software uninstallation. The OSMU allows you to uninstall product software.
On the Service page, you can monitor running status of service processes
and databases, and start or stop processes.
The service management page of the OSMU provides the system On the Node page, you can monitor resource status of each node and set
monitoring function. thresholds.
2
(This function is moved from the U2000 client to OSMU.) On the Relational Database page, you can monitor running status of the
relational databases and set thresholds.
On the Redis Database page, you can monitor running status of the Redis
databases and set thresholds.
The cloud-based OSMU WebUI supports the backup of the dynamic
3 data for OSS products. The OSMU WebUI allows you to back up the dynamic data of OSS products.
(This function is moved from the U2000 client to OSMU.)
The cloud-based OSMU supports the configuration of scheduled
backup parameters. The OSMU allows you to configure scheduled backup parameters, including
4 one-time backup and periodic backup.
(This function is moved from the U2000 client to OSMU.)
The cloud-based OSMU supports emergency system configurations. The OSMU WebUI provides the portal for configuring the emergency system
5
(This function is moved from the U2000 OSMU to OSMU.) for the U2020.

Modified Function – Portal for System Monitoring
Change Description
Before: Monitor > System Monitor > Browser > Service Monitor on the U2000 client
After: Application > Service Management > Service Monitoring on the OSMU client
The display style is changed, and the monitoring data table is optimized.
The overall layout is more reasonable and the operations about settings are combined, facilitating users in service setting.

Modified Function – Portal for System Backup
Change Description
Before: Maintenance > Backup Management > System Backup on the U2000 client
After: Backup and Restore > Backup Data > Backup Product Data on the OSMU client
The U2020 data backup and restoration function is moved to the OSMU, facilitating users in management.

Contents


Modified Function – Integrated Management Planes and
Modified Portal for Changing IP Addresses
Background
1. Based on the integration of the management planes for the ATAE platform and E9000 platform, all functions and GUIs related to the vOSMU are updated to
those of the OSMU.
2. Based on the high reliability solution requirements, the portal for IP address modification is changed.
Change Description
1. All functions and GUIs related to the vOSMU are updated to those of the OSMU.
2. If the service IP address of the U2020-M node needs to be changed in an HA system, the Configure IP Address tab is changed to Configure Floating IP
Address.
Impact
You cannot perform operations on the U2020-M node on the Configure IP Address tab page.

Contents


NBI Changes
Major NBI changes are as follows:
1. NBIs (excluding customized NBIs and CORBA 1.2.0 interface) support NR NEs. Supported NR NE types include
BTS3900, BTS5900, BTS5900 5G, and BTS3900 5G.
2. The northbound alarm SNMP interface is now configured on the U2020 client instead of on the OSMU client.
3. If you need to configure the northbound performance file interface (NE-based) on the server, configure it on any
slave server where the ossmediation service resides, instead of on the master server.
4. For details about NBI changes, see U2020 Northbound Interface Changes.

Northbound Alarm File Interface Changes
Background
After the web-based client is used and microservices are added to the server, the U2020 master server needs to communicate with each microservice and external node in real time as a bus. The
improving management capability requires more CPU resources and memory on the U2020 master server. For the timeliness and stability of core services on the master server, FMService is
migrated from the master server to the slave servers. In this way, the pressure on the master server is reduced and the timeliness of alarm services are guaranteed.
Impact
Interfaces that are not affected: Alarm CORBA interfaces, alarm streaming interfaces, and alarm SNMP interfaces.
Interfaces that are affected: Alarm file interfaces. If an upper-layer NMS is connected to an alarm file interface, the upper-layer NMS must be connected to the server with FMService is deployed.
(How Do I View Information about the Homing Server of FMService?)
Impact Analysis U2020 System Type Scale Description of FMService Homing Server
1. The alarm file interface is a non-real-time 1200 equivalent NEs or more Migrated from the master service board to slave service board 3.
interface. Alarm/event log export tasks over alarm ATAE cluster system
800 equivalent NEs or less No changes
file interfaces are suspended by default in Task Migrated from the master service VM to the VM where FMService
Virtual cluster system All supported specifications
resides.
Management of U2020. The execution period is
set to once a day by default.
2. Fields, field sequence, and field names contained
in the exported alarm file must be manually
customized on the server. The operation is
complex.
Based on the above two points, operators usually
use real-time alarm interfaces, such as alarm
CORBA, alarm streaming, and alarm SNMP
interfaces. Alarm file interfaces are seldom used.
3. The upper-layer NMSs need to be slightly
modified. Users only need to set the FTP server IP
address to that of the homing server of FMService.

Northbound Alarm File Interface Changes – How Do I View
Information about the Homing Server of FMService?
Step1: Log in to the OSMU. Step 3: Click Services, search for the keyword U2020/FM/ and click the search result.
Step2: Choose Application > Service Management > System Step 4: Record the node name of the desired FMService service.
Monitoring > U2020.
Step 5: Obtain the IP address of the server based on the node name.

Contents


Resource Usage Changes from V200R018C10 to V300R019C10
The average CPU usage increases by about 20% because the cloud-based platform occupies CPU resources.
Resource Deployment After Upgrade to U2020 Cause
The average CPU usage increases by about
Master server After the cloud-based evolution, new microservices occupy resources.
20%.
The average CPU usage increases by about Some processing capabilities of the java client are moved to the server (website services are added) due to the web-
Slave server 1
15%. based reconstruction.
The average CPU usage increases by about If the U2020 management capability is 800 or 1200 equivalent NEs, FMA is migrated to this server, and the average
Slave server 2
10%. CPU usage increases by 10%. In other scenarios, the CPU usage does not increase.
The average CPU usage increases by about If the U2020 management capability is 1200 equivalent NEs or higher, apps for cloud-based alarm services are added
Slave server 3
10%. to the server, and the average CPU usage increases by 10%. In other scenarios, the CPU usage does not increase.
The average CPU usage increases by about After the cloud-based platform is used, resource consumption increases, and the number of microservices accessing
Master database server
5%. the database increases.
Other slave servers Basically unchanged
Slave database server Basically unchanged
The remaining memory decreases by about 10 GB due to cloud-based reconstruction.

The resource consumption increases after the cloud-based platform is used, and the overhead of
Master server The average remaining memory decreases by about 15 GB.
microservices increases.
Slave server 1 The average remaining memory decreases by about 5 GB. After web-based reconstruction, some functions of the java client are processed by the server.
If the U2020 management capability is 800 or 1200 equivalent NEs, FMA is migrated to this server, and the
Slave server 2 The average remaining memory decreases by about 5 GB.
average remaining memory decreases by about 5 GB. In other scenarios, the memory does not decrease.
If the U2020 management capability is 1200 equivalent NEs or higher, apps for cloud-based alarm services
Slave server 3 The average remaining memory decreases by about 5 GB. are added to the server, and the average remaining memory decreases by about 5 GB. In other scenarios,
the memory does not decrease.
The management planes are combined. Consumption for the resource monitoring and service deployment
Master database server The average remaining memory decreases by about 1 GB.
increases.
The management planes are combined. Consumption for the resource monitoring and service deployment
Slave database server The average remaining memory decreases by about 500 MB.
increases.

Resource Usage Changes from V300R019C00 to V300R019C10
The average CPU usage increases by about 10% because the cloud-based alarm and security functions occupy resources.

The average CPU usage increases by
Master server The cloud-based alarm and security functions occupy CPU resources.
about 10%.
The average CPU usage increases by If the U2020 management capability is 800 or 1200 equivalent NEs, FMA is migrated to this server, and the average
Slave server 2
about 10%. CPU usage increases by 10%. In other scenarios, the CPU usage does not increase.
If the U2020 management capability is 1200 equivalent NEs or higher, apps for cloud-based alarm services are
The average CPU usage increases by
Slave server 3 added to the server, and the average CPU usage increases by 10%. In other scenarios, the CPU usage does not
about 10%.
increase.
The average CPU usage increases by After the cloud-based platform is used, resource consumption increases, and the number of microservices
Master database server
about 5%. accessing the database increases.
The average remaining memory decreases by about 5 GB because the cloud-based alarm and security functions consume resources.

The average remaining memory
Master server The cloud-based alarm and security functions occupy memory.
decreases by about 5 GB.
The average remaining memory If the U2020 management capability is 800 or 1200 equivalent NEs, FMA is migrated to this server, and the average
Slave server 2
decreases by about 5 GB. remaining memory decreases by about 5 GB. In other scenarios, the memory does not decrease.
If the U2020 management capability is 1200 equivalent NEs or higher, apps for cloud-based alarm services are
The average remaining memory
Slave server 3 added to the server, and the average remaining memory decreases by about 5 GB. In other scenarios, the memory
decreases by about 5 GB.
does not decrease.
Master database server Basically unchanged

Contents

 U2020 Security Function Chang
es
 U2020 Engineering Managemen
t Function Changes
 Configuration Management
 Performance Management
 Software Management
 Tracing and monitoring
 SON
 Others

Added NSA Reports to RAN Reports (V300R019C00)
Change Description
1. LTE NSA reports are added to LTE RAN reports.
2. NR NSA reports are added to NR RAN reports.

Added Precise Demarcation on Base Station Disconnection Alarms
Background
If ALM-301 NE Is Disconnected or ALM-40012 NE Is Disconnected is reported, U2020 provides alarm details to improve the accuracy of root cause
demarcation.
Change Description
The root cause demarcation capability for ALM-301 and ALM-40012 is optimized. U2020 accurately identifies the causes, such as power supply failures or
transmission faults. For example, if the disconnection is caused by handshake timeout, U2020 further checks whether the timeout is caused by power supply
failures or transmission interruptions.
The detection is initiated upon the timeout of two handshakes between U2020 and an NE. The detection time ranges from the time when two handshakes
time out to the time when six handshakes time out. Therefore, the alarm reporting performance is not jeopardized, that is, alarm reporting is not delayed.
Before the Change
After the Change

Contents

es
 U2020 Engineering Managemen
t Function Changes
 Trace and Monitoring
 SON
 Others

Performance Management: Enabled the Wireless FMA to Subscribe
to One-Minute Real-time Monitoring Data (V300R019C00)
Background
After troubleshooting a fault, the wireless FMA needs to collect one-minute real-time monitoring data to check whether the fault is rectified. Therefore, U2020 needs to report one-
minute real-time monitoring data to the wireless FMA.
Change Description
1. You can select KPIs in the Select Scenario dialog box shown below on the wireless FMA. The wireless FMA then delivers them to the real-time monitoring module of U2020. After
receiving the one-minute KPI subscription information, the real-time monitoring module creates a monitoring task and delivers it to NEs.
2. After receiving the data reported by NEs, the real-time monitoring module forwards the data to the wireless FMA.
Precautions
An NE supports only one subscription task at a time. Therefore, U2020, mAOS, and wireless FMA cannot deliver a one-minute subscription task to an NE at the same time.

Contents

es
 U2020 Engineering Management
Function Changes
 SON
 Others

Software Management Expert: Optimized the Retry Mechanism for a
n Upgrade Failure (V300R019C00)
Background
When you use Software Management Expert to upgrade base stations, Software Management Expert does not identify error types and uses a unified retry mechanism for all upgrade
failures or errors. However, the simple retry is meaningless and prolongs the upgrade duration in some error scenarios, for example, if the NE reports an error indicating that the hot
patch, cold patch, or basic version is incorrect. Therefore, the retry mechanism needs to be optimized to identify scenarios without requiring the retry, improving upgrade efficiency and
quality.
Change Description
Software Upgrade Expert now identifies error types during the base station upgrade, and the retry mechanism has been optimized. The details are as follows:
1. If U2020 is abnormal or the transmission network between U2020 and NEs is abnormal, use the original retry mechanism.
2. If an NE is abnormal, the system determines the capability and the retry field of the NE and determines whether to retry.
Impact
1. If exceptions cannot be resolved through automatic retry, for example, the software packages do not match, the system reports an error immediately to request manual
intervention. This shortens the problem solving time.
2. If exceptions may be resolved through automatic retry, the system automatically retries to reduce errors and manual intervention and improve operation efficiency.

Software Management Expert: Enhanced the Upgrade Function (V300R019C00)
Background: The remote upgrade team proposes the following requirements: For the base station upgrade based on Software Management Expert, automatic functions should be added. The functions
include displaying the countdown for scheduled batch tasks, automatically grouping NEs, prompting messages and triggering rings upon download failures, and triggering rings upon termination of
automatic group activation. After the modification, Software Management Expert improves the automation capability, effectively controls risks, and improves O&M intelligence, usability, and friendliness.
Create an upgrade project. Change Description

1. The countdown of scheduled batch tasks is displayed on the GUI.
Original procedure Create an upgrade batch. 2. Automatic grouping is available and allows for original inter-site relationships, preventing
New procedure sites that need to be upgraded together from being divided into different groups.
Check risks. 3. Messages are prompted and rings are triggered upon download failures.
4. A dialog box is displayed, and rings are triggered upon termination of automatic grouping
1. The function of displaying the countdown of
Download software. the scheduled task execution is added. execution.
2. The function of prompting messages and
(Optional) Perform the pre- triggering rings upon download failures is added.
activation risk check.
up The function of displaying the
gro .
i nal ode ged Set execution mode.
countdown of the scheduled
ig m a n task execution is added.
or ion nch
e t
Th tiva ns u
a mai
c
Set grouping data.
re
Activate software.
The automatic grouping
Group NEs.
function is added.
The function of displaying a

Activate each group. dialog box and triggering rings
upon activation termination is
added.
Verify the upgrade and

generate an upgrade report. Note: Typically, group activation is
used for remote upgrade at sites in
Japan and Romania.

Software Management Expert: Enhanced the Base Station Risk Che
ck Function (V300R019C00)
Background
For the base station upgrade based on Software Management Expert, the risk check for the internal relationship of the Cloud BB (USU and base station) is
not supported. In addition, the alarm risk items in the risk check result are displayed with other risk items. As a result, the alarm risk items are hard to be
identified and classified.
Original procedure Create an upgrade project. Change Description

New procedure
1. Cloud BB risk check items have been added during the OSS environment
Create an upgrade batch. check.
2. The summary result of alarm risk check items has been added to the NE
risk check summary report.
The risk check for the Cloud
Check risks.
BB has been added.
Download software.
(Optional) Perform the pre-

activation risk check. Impact
After the modification, the risk check capability is enhanced, and all alarm risk
Activate software. items can be identified, improving O&M intelligence, usability, and friendliness.
Verify the upgrade and The alarm risk check result has
generate an upgrade report. been added to the risk check
report.

Software Management Expert: Provided Foolproof for the Number of NEs Activated in Bat
ches and That of NEs Automatically Activated by Group (V300R019C00)
Background
When Software Management Expert is used to upgrade base stations in countries outside China, no thresholds are specified to control the number of NEs activated in batches and that
of NEs automatically activated by group, which may lead to risks. Therefore, it is recommended that the secondary authentication mode for China be used and opened in countries
outside China, improving upgrade security.
Change Description
1. The Secondary Authorization submenu has been added to the Security menu for you to set secondary authentication.
2. Function restrictions on and determination of secondary authentication are added to Software Management Expert for upgrade.
Impact
1. For sites that have high security requirements on the upgrade using the Software Management Expert, you can enable secondary authentication and set related thresholds to
improve operation security and reduce upgrade risks.
2. For sites that have no security requirements on the upgrade using the Software Management Expert, secondary authentication is disabled by default, which does not affect user
experience and reduces the learning costs brought by version upgrades.

Software Management Expert: Allowing Users to Click a Button to Navigate to t
he Page for Collecting RFC Review Data (V300R019C00)
Background
Currently, collecting risk check data only cannot meet risk review requirements of base station upgrades. You also need to use the NIC or other tools to collect RFC data and
return the data to second-line engineers for review. This procedure is complex and not easy to use.
Change Description
The procedure for collecting RFC data is simplified.
1. The Software Management Expert allows you to navigate to the NIC collection page and click a button to obtain RFC review data.
2. You can click a button to obtain RFC review data during the period from the time when a task batch is created to the time when the download phase starts.
This button indicates that a risk check

task is unexecuted. In this case, the
collected data does not contain risk
check results.
This button indicates that a risk check task

is executed. In this case, the collected data
contains risk check results

Software Management Expert: Enhanced Creation of Upgrade Batches
Background
In earlier versions, upgrade batches have to be created one by one. To release manpower, GTAC requires that base station upgrades be automated to
the utmost. That is, Software Management Expert automatically plans and creates upgrade batches, saving manpower and improving O&M experience.
Change Description
Original Creation of an upgrade
project 1. The following function is added: automatic plan and batch creation of upgrade batches.
Procedure
New Automatic plan 2. Base stations (such as MBTS) to be upgraded are batched based on their subnets and correlations,
Creation of upgrade
Procedure batches
and batch and the preset conditions.
creation of
upgrade batches
Risk check
Automatic plan and batch

Software download creation of upgrade
batches
(Optional) Pre-activation
risk check
Automatic
Software activation
batching
Post-upgrade verification
and report
Impact
Software Management Expert becomes more automated, saving manpower and improving O&M experience.

Software Management Expert: Enhanced Rectification of Faults Detected in Ris
k Check
Background
After completing risk check, Software Management Expert provides only risk items and their information, but does not provide fast fault rectification
capabilities. Maintenance personnel have to be highly skilled and take a long period of time to rectify faults.
Change Description
Original Creation of an upgrade
project 1. During risk check, U2020 identifies faults and generates a fault rectification script.
Procedure
2. U2020 allows users to export the fault rectification script from the risk check summary report in one-
New Creation of upgrade
Procedure click mode.
batches For fast
fault 3. The fault rectification script can be used to create an MML script task for fault rectification.
rectification, Note: A fault rectification script is used to rectify faults of an NE batch, not an NE.
Risk check a fault
rectification
script can
Software download be exported
from the
risk check A fault rectification script can Creating an
summary be exported from the risk MML script task
(Optional) Pre-activation check summary report in
report in
risk check one-click mode.
one-click
mode.
Software activation
and report
Impact
The fault rectification capability of Software Management Expert is enhanced, improving O&M experience.

Contents

 U2020 Engineering Management F
unction Changes
 SON
 Others

Trace and Monitoring: Increased Trace Data Amount for UMPTg Boards
Background
Packet sending capabilities of UMPTg boards of NR NEs are improved. As a result, the volume of cell DT trace data may reach 100 Mbit/s, up to 25 Mbit/s
even after data compression.
However, the OM capability tested in the lab is only about 24 Mbit/s, which is substandard.
Change Description
1. For cell DT trace, the trace and monitoring module establishes links to NR NEs separately. A maximum of three links are allowed to a single NE.
2. U2020 can store compressed code streams. The code stream files can be opened using only the backend parsing tool (offline FMA or trace viewer).
Restrictions
1. U2020 provides a maximum of 10 GB space (provides only 4 GB space if the management capability is 100 or 200 equivalent NEs) to store NR cell DT
trace data. If the data volume exceeds the limit, the cell DT trace task is suspended.
2. U2020 supports a maximum of five concurrent trace items.
Application Scenario
Cell DT trace results can be downloaded from U2020 and used to locate TTI scheduling problems.

Trace and Monitoring: Optimized the Detailed UMTS UE Trace Function (V300R0
19C00)
Background
When locating voice problems on an RNC, users need to manually select the following events:
DPCCH Search/Power Ctrl/DPCCH Demod, DCH Channel Decoding, IUB Interface Trace, Sig Inner Interface Trace, Trans Inner Message, R99 User Cctrch Para Info
Statistic, DCH Data Frame Transfer.Srb, DCH Data Fp Statistic, DCH Data FrameTransfer.Srb, and Downlink Power Control
When locating KPI problems, users need to manually change the default values of the parameters of the DPCCH Search/Power Ctrl/DPCCH Demod event.
Change Description
The default parameters of the DPCCH Search/Search/Power

Ctrl/DPCCH Demod event are modified to reduce manual
The AMR check box is added. When AMR is selected, the operations.
events required for locating voice problems are automatically
selected.

Trace and Monitoring: Added the Zstd Compression Algorithm for Trace Stream
Data of Base Stations to U2020 (V300R019C00)
Background
The Zstd compression algorithm is introduced to the NE platform to compress trace data and report the compressed data to U2020. The compression speed of the Zstd
compression component is faster than that of the zlib component, and the file generated after compression is smaller. Therefore, it is expected that the Zstd compression
component can be supported in U2020 V300R019C10.
Change Description
1. The function of parsing Zstd-compressed tracing packets has been added to the FARS.
2. The compression format ZST has been added when users export data on the FARS.
The compression format ZST is added to the

Export File dialog box for users to select after
users click Export.

Trace and Monitoring: Optimized NSA 4G and 5G UE Trace (V300R019C00)
Background
In U2020 versions earlier than V300R019C10, base stations need to be selected for NSA UE detail trace on 5G NEs. This operation takes a long time and is
inconvenient.
Change Description
In V300R019C10, NR Virtual UE Trace and NSA Virtual UE Trace are added. If the end-to-end (E2E) trace for these functions is enabled on the core network
(CN), CN NEs start the virtual UE trace on NR base stations without selecting a specific base station on U2020.
If RAN base stations and CN NEs are managed by the same U2020 system, LTE/EPC End-to-End User Trace is recommended. If RAN base stations and CN
NEs are managed by different U2020 systems, NR Virtual UE Trace or NSA Virtual UE Trace is recommended.
Query combined results of LTE

Virtual UE Trace and NR Virtual
UE Trace.
On this page, set parameters, such as

PLMN and User trace ID.

Contents

 U2020 Security Function Change
s
 U2020 Engineering Management
Function Changes
 SON
 Others

SON: Added NR ANR Optimization Advice in Controlled Mode
Background
NR NEs support the ANR function, and U2020 needs to support the ANR optimization advice in controlled mode.
Change Description
Added NR ANR optimization advise in controlled mode.
In controlled mode, NEs report neighboring cell optimization advice to U2020. Users then can query and deliver the optimization advice to add neighboring
cells.
Navigation path: SON > NR ANR
Select NEs before a query.
Deliver, reject, or export optimization advice.
Overshoot
coverage check

SON: Assigning IPv6 Addresses to Base Stations Using DHCPv6
Background
IPv6 addresses need to be assigned to base stations using DHCPv6.
Change Description
U2020 V300R019C10 can assign IPv6 addresses using DHCPv6 for site deployment.
Only MBTSs, eNodeBs, and gNodeBs support DHCPv6. Port 547 must be enabled on the firewall in advance.
Base stations and U2020 are all deployed in IPv6 networking, and base station OMCHs use IPv6 addresses.
Added the IP Type parameter.
Related fields are displayed in IPv6 format.

SON: Automatically Setting NE Engineering Status to Maintenance Mode Durin
g Site Deployment
Background
During site deployment, U2020 has not synchronized NE engineering status, and NEs have not been connected. Therefore, U2020 reports an NE
disconnection alarm, affecting user experience.
Change Description
U2020 V300R019C10 automatically sets engineering status of NEs created during site deployment to maintenance mode. The NE disconnection alarm can
be masked by the engineering field.
Site deployment Changed to the INSTALL state.
Changed to INSTALL.

SON: Remote Virtual Dialing Test – Background
Background
In about 30% of site deployment scenarios, transmission links cannot be made available at a time. According to government regulations, some operators can activate base
stations only a certain period of time after they are deployed. As a result, hardware installation, project quality verification, and service dialing tests cannot be completed at a
single site visit in the engineering phase. Dialing tests for basic services must be performed at another site visit after transmission links are available and carriers are activated.
This function enables U2020 to search for UEs that meet requirements, maps UE behavior with test items, and perform remote dialing tests on basic services, reducing
repeated site visits.
Engineering phase during site deployment Engineering phase during site deployment
Remote and
First site visit Second site visit First site visit automatic
Engineering Dialing test Engineering Dialing test
Hardware Software Transmission Hardware Software Transmission
quality on basic quality on basic
installation commissioning deployment installation commissioning deployment
verification services verification services
WCS client
Change Description
WCS provides UIs for virtual dialing tests, while U2020 supports only import and export of test data. 6. Displays dialing test results.
1. Set parameters.
WCS imports user settings to U2020 offline, and U2020 exports test results to WCS offline.
The procedure is as follows: WCS
1. On WCS, users set virtual dialing test parameters, such as test NEs, cells, and time. 5. Exports dialing test
2. Imports parameter
results as files to
2. Users export parameter settings from WCS as files and import the files to the U2020 client settings as files
WCS.
offline. to U2020.
U2020
3. U2020 parses the files, obtains user settings, issues MML commands to the NEs to start dialing
tests, and queries test progress. 3. Issues MML command to start dialing tests and queries test results.
4. The base station controller and base stations interact with UEs to start subscriber service
Base station
measurement. controller
3.1. Starts 4. Starts subscriber
5. After dialing tests are complete, users export test results as files from U2020 and import the files 4. Starts subscriber eNodeB
measurement and service measurement.
to WCS offline. reports measurement service
6. WCS parses the files and displays dialing test results. results. measurement.
GBTS/
NodeB

SON: Remote Virtual Dialing Test – GUI Description
GUI Description
Navigation path: SON > Remote Virtual Dialing Test RemoteSvsTest.
Example import file xml
Import a
task file.
1
Batch operations
2 Delete
a task.
Start a task.
Stop a task. Export

task results.

SON: Added NR CODR
Background
NR cell outage detection and recovery (CODR) is evolved from LTE CODR, aiming to improve reliability and competition of NR networks.
Navigation path
Change Description
Added the NR CODR function.
1. Cell outage detection is based on alarms and abnormal KPIs.
2. The following self-healing methods are supported: base station
reset, cell reactivation, BBP reset, BBP reset by power-off, RRU
reset, and RRU reset by power-off.
Note: This function is provided on the WebUI.
Cell outage page: displays the current and historical outage cell list. The
current outage cell list allows you to select a self-healing method.
Parameter setting page: displays basic parameters, KPI thresholds,

and NE monitoring parameters.

Contents

 U2020 Engineering Management Fu
nction Changes
 SON
 Others

Stand-Alone License Management: Optimized the Offline Adjustment Template Export
ed in the License Capacity Adjustment Function (V300R019C00)
Background
The offline NE adjustment template for the ESDP is different from that for U2020 with a stand-alone license used. Therefore, users cannot quickly export the template from U2020 and
then import it to the ESDP.
Change Description
1. The NE ID or Node ID column has been added to the template, but users do not need to fill in the column.
2. The sequence of columns in the template for U2020 is the same as that for the ESDP.
3. The data area starts from cell B7. That is, the first column is empty. The data area starts from the second column and the seventh row.
4. The name of the sheet is Config Data.
Example before modification
ESDPWithoutRev ESDPWithRevoc
ocationCode-before ationCode-before
Example after modification
ESDPWithoutRev ESDPWithRevoc
ocationCode-after ationCode-after

WebNIC: Importing Extended Packages of iSStar
Background
WebNIC can provide MML collection items for N-2 NE versions only after the mediation is upgraded. Data that cannot be collected for an existing scenario
group using the collection script of the mediation now can be collected using extended script packages of iSStar. This function can be used for all scenario
groups.
Change Description
Collection items are decoupled from NE mediation. Collection items can be added for NEs of inventory versions.
The extended package for a scenario group can be used for each scenario in the scenario group after being imported to WebNIC.
How do I import an extended package?

1. Choose Scenario Management.
2. In the navigation tree, choose Extended Packages. In the right pane, click Import.
How do I obtain a rule file?
Obtain the rule file from data users.
How do I enable the function?
You do not need to enable the function. An extended package is for a specific scenario group. During execution of
a scenario group, the collection commands in the extended package are automatically executed.

WebNIC: Changed the CHR/MR Data Control Method
Background
CHR and MR data can be stored on Trace Server only after storage parameters are configured on OSMU of Trace Server, which is inconvenient.
Change Description
Navigation path: Settings > MR/CHR Storage Setting
On WebNIC, users can set the duration for storing CHR and MR data on Trace Server. The data can be stored by time or by NE. By default, CHR and MR
data is stored by NE for seven days.

EMS FMA: Quick Demarcation Using the Call Chain in Cloud-based Networking
Background
Unlike the traditional architecture, which uses the NE partition binding and service binding model, the service-oriented architecture covers multiple
microservices in a service scenario and uses random routes, posing challenges in fast fault locating and demarcation.
Change Description
EMS FMA uses a distributed call chain trace technology to provide precise fault demarcation.
1. Currently, only MML command issuing is supported. By default, only the MML service is deployed on multiple instances. With the multi-instance
reconstruction, more scenarios will be supported.
2. EMS FMA displays the calling process during MML command delivery.
3. EMS FMA can accurately locate failed services, improving diagnosis efficiency.

NE Backup: Allowing Users to Select NEs of Multiple Types or NEs on the Entir
e Network (V300R019C00)
Background
The NE backup function allows users to manually back up, restore, and query NE data only by NE type. Users cannot select NEs on the entire network or NEs of multiple
types.
Change Description
In the NE Backup window, the Type drop-down list has been added to the NE Backup and Configuration and Inventory Data Export tab pages so that users can select
NEs of multiple types or NEs on the entire network.
Impact
After the modification, users can select concerned NEs at a time as required. This improves operation efficiency and O&M usability and friendliness.

Configuration and Inventory Data Export: Allowing Users to Choose BTSs Associated
with the CU-DU Split from the NE Navigation Tree (V300R019C00)
Background
CU-DU Split NEs are connected to U2020 for NE configuration and inventory data export. The function of quickly selecting associated NEs in CU-DU Split O&M needs to be
supported.
Change Description
When users right-click the RANCU_ENB, or RANCU_GNB in the NE navigation tree and then choose Check the corresponding BTS from the shortcut menu, the
associated BTS will be selected.

NE License Management: Enhanced the Function of Allocating License Data to Tele
com Operators During NodeB License Management (V300R019C00)
Background
During NodeB license management, when a new license file is used in RAN Sharing scenarios, the license data must be allocated to telecom operators. Currently, users must
manually enter the data. The license data cannot be extracted from allocated data of other license files. The usability is poor. After the modification, users can use the export and import
functions to quickly allocate license data to telecom operators.
Change Description
1. In RAN Sharing scenarios, the Export Distribute to Operator menu has been added to the shortcut menu displayed when users right-click a license record. With this function,
users can export data to be allocated to telecom operators.
2. The Import button has been added to the Distribute to Operator dialog box. Users can click this button to import data to be allocated to telecom operators.

NE License Statistics: Provided the Function of Collecting Statistics on NE Lice
nses on the Entire Network (V300R019C00)
Background
User (service) requirements: Users want to know how to quickly learn the usage of NE licenses on the entire network (including the network-wide license usage report and
dynamic license usage curve), and require data support and guidance for license sales. After the modification, users can use the network-wide NE license statistics function
to obtain the usage of NE licenses to support license sales and improve O&M usability and friendliness.
Change Description
1. Users now can query and export license usage statistics reports of the following NEs: NodeB, eGBTS, eNodeB, gNodeB, RFA, BSC6900, and BSC6910. The statistical
dimensions include the entire network, version, and controller.
2. Users can query and view the curve showing historical records of dynamic license usage (90 days at most).

U2020 License: Optimized U2020 Features and Added Cloud-based Features
(V300R019C00)
Background
During the long-term evolution, the number of U2020 features keeps growing and reaches more than 150. Among the large number of U2020 features, it is
difficult for customers to select an appropriate feature, and cloud-based capabilities are not prominent due to a large number of minor features.
Change Description
1. In the cloud-based U2020 version, features are streamlined and integrated. Simplified features include ten major features and some version value features
2. The following cloud-based capabilities are added: Load Balance, App-level HA, App Independent Upgrade, and Smooth App-level Scale Out.
Four Four Two auxiliary
Version value
Ten major U2020 feature expresses experts solution
features(minor features)
(major features)
Fault Ma nagement Performance Manag ement Auxiliary device
Fault Performance Intelligent Express Expert
Northbound interconnection and
Management Management Alarm Value-added feature package Value-added feature package integration
Express Expert File Interface for fault management, for performance
Correlation This solution contain features
including remote alarm management, including real- related to engineering platforms
reporting and alarm rules time monitoring and event- and device interconnection,
based counters including the Citrix, NTP, remote
Configuration ES, and OSMU 1:1 redundancy
Network Northbound Remote
features. Considering hardware
Management Additional Redundancy Configuration Management
Trace Expert Network Trace Expert
or device interconnection may
Express Interface Solution Express incur costs, the license fee for
Value-added feature package for Value-added feature package
interconnection and
configuration management, for network tracing, related to
interconnection is charged only
inheriting all value-added original enhanced trace
once, regardless of devices to be
features of the CME features
interconnected.
Device Network Planning Security Intelligent
Management & Optimization Northbound Development
Express Expert Interface Platform Netwo rk Planning &
Device M anagemen t Express Optim iza tion Exp ert
Network planning and
Security and auxiliary
Management features related to solution
optimization features,
devices, assets, and hardware, If external devices are not
Feature Scenario NE/U2020 including inventory management
including D-SON, energy
Network Sharing Configuration N+1 version saving, and pico base station involved, this solution is not
Operation and antenna management intended for specific features,
Expert Northbound Interface decoupling
deployment
Express but is used to enhance or
support U2020 capabilities,
such as security hardening,
Network Sharing Expert co-management of microwave
Sharing features, including transmission energy and
Auxiliary device Security and Signaling Feature Operatio n Expre ss
Feature O&M functions RAN sharing and co-base devices, and visibility of small
interconnection and auxiliary solution Collection station management cell base stations
integration Management
Impact
The U2020 features are simplified, clear, and neat on the customer plane and sales plane. This improves the usability and friendliness of O&M and sales.

Contents


Reference Documentation
For detailed changes on licenses, ports, alarms, events, NBIs,

Some major changes may be presented in PCNs.
operation rights, and U2020 GUIs, see the U2020
V300R019C10 release documents.
Obtain the PCNs at http://support.huawei.com/.
Obtain the release documents at http://support.huawei.com/ by
selecting the version and document type.

Thank you
www.huawei.com
Copyright©2019 Huawei Technologies Co., Ltd. All Rights Reserved.

The information in this document may contain predictive statements including, without limitation, statements regarding the future financial and operating
results, future product portfolio, new technology, etc. There are a number of factors that could cause actual results and developments to differ materially
from those expressed or implied in the predictive statements. Therefore, such information is provided for reference purpose only and constitutes neither
an offer nor an acceptance. Huawei may change the information at any time without notice.
Function Not Supported - Multi-Column Alarm Sorting
Background
Due to a large amount of code in the traditional version, U2020 functions are migrated to the web client by priority. Multi-column alarm sorting, whether
supported or not, does not affect the alarm function, and therefore will be migrated later. Alarm sorting will be supported in the GA version of V300R019C10.
Impact on O&M Alternative Solution

Users cannot sort alarms in multiple columns on the U2020 client, affecting 1. U2020 V300R019C10 supports single-column alarm sorting, as shown
O&M efficiency. in the following figure.
2. If users want to sort alarms in multiple columns, they can export alarms
to an Excel file and then sort alarms.
Follow-up Plan
This function will be supported in the GA version of U2020 V300R019C10.

Deleted Function - Displaying Current Alarms by Status (Four Panes)
Background
N/A
Impact on O&M Alternative Solution

Users cannot view current alarms in the four statuses on one page. From The U2020 alarm UI provides a variety of filter combinations for users to
an actual perspective, this function has great limitations. view current alarms in desired statuses.
Follow-up Plan
This function has been deleted.

Software Management Expert: Enhanced Upgrade Automation Capabi
lities (Not Delivered in TR5)
Background
In earlier versions, each upgrade phase (risk check, download, and activation) has to be manually triggered. With cloud-based management of services,
upgrade automation becomes urgent. To release manpower, GTAC requires that the upgrade procedure be automated to the utmost. That is, Software
Management Expert automatically checks for risks based on rules, saving manpower and improving O&M experience.
Original Creation of an upgrade Change Description

Procedure project
1. U2020 automatically performs each upgrade phase based on user-defined upgrade rules.
New
Creation of upgrade 2. U2020 automatically checks for faults and rectifies faults based on upgrade rules (for example, by
Procedure
batches removal, deletion, or soldering). If soldering is required, U2020 displays a message or rings to alert
users of the soldering.
Risk check 3. Manual intervention is supported during an automatic upgrade.
4. An automatic upgrade continues after soldering is complete.
Software download This function is not
delivered yet. The
diagram for this
(Optional) Pre-activation
risk check function will be
provided after delivery.
Software activation
and report
Impact
Software Management Expert becomes more automated, saving manpower and improving O&M experience.

Added the Real – Time Performance Northbound Interface (Not Deli
vered in TR5)
Background
Users can obtain real-time NE performance data to monitor NE faults and view or analyze KPI data in real time during key event assurance, key area assurance, and
quick verification of NE fault rectification.
Benefits
Users create northbound performance monitoring tasks as required on U2020. U2020 exports performance data of managed RAN NEs (such as GBSS, WRAN, eRAN,
and NR NEs) into files by task every minute. Upper-layer NMSs then obtain these files from a specified directory on the U2020 server using SFTP.
This function requires the real-time
Select
object performance monitoring license and
type. Select real-time performance northbound
objects.
interface licenses.
Maximum number of monitored objects:
1500
Select Maximum number of objects in a single
counters. task: 300
Maximum number of counters in a
View single task: 25
tasks.

Functions That Are Not Supported by the NBIs
The NBIs do not support the following functions:
1. The northbound alarm file interface does not support the export of HTML and XML files.
2. The northbound alarm file interface does not support the export of specified alarm
names.
3. The northbound interfaces for fault databases and that for the ATAE cluster emergency
system fault databases are not supported.

Modified Function – Installation, Upgrade, and Capacity Expansion
(Not Delivered in TR5)
Background
After the cloud-based platform is used, services and microservices are the basic deployment units. The logic for processing the microservices of installation,
upgrade, and capacity expansion is the same.
Change Description
 Installation, uninstallation, upgrade, and capacity expansion are
accessed from the Manage Product Software page of OSMU.
 The Manage Product Software page shows the historical deployment,
upgrade, and capacity expansion tasks and the task details.

U2020 MBB V300R019C10 New Functions and Major Changes-201903

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

U2020 MBB V300R019C10 New Functions and Major Changes-201903

Загружено:

Авторское право:

Доступные форматы

Security Level: Internal

New Functions and Major

Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.

 U2020 Alarm Function Changes

HUAWEI TECHNOLOGIES CO., LTD. Page 3

HUAWEI TECHNOLOGIES CO., LTD. Page 4

 U2020 Alarm Function Changes

HUAWEI TECHNOLOGIES CO., LTD. Page 5

HUAWEI TECHNOLOGIES CO., LTD. Page 6

HUAWEI TECHNOLOGIES CO., LTD. Page 7

The automatically obtained correlation rules

HUAWEI TECHNOLOGIES CO., LTD. Page 8

HUAWEI TECHNOLOGIES CO., LTD. Page 9

 U2020 Alarm Function Changes

HUAWEI TECHNOLOGIES CO., LTD. Page 10

HUAWEI TECHNOLOGIES CO., LTD. Page 11

HUAWEI TECHNOLOGIES CO., LTD. Page 12

HUAWEI TECHNOLOGIES CO., LTD. Page 13

Change Item On U2000 On U2020

Preferences Supported Not supported

HUAWEI TECHNOLOGIES CO., LTD. Page 14

HUAWEI TECHNOLOGIES CO., LTD. Page 15

HUAWEI TECHNOLOGIES CO., LTD. Page 16

HUAWEI TECHNOLOGIES CO., LTD. Page 17

HUAWEI TECHNOLOGIES CO., LTD. Page 18

 U2020 Alarm Function Changes

HUAWEI TECHNOLOGIES CO., LTD. Page 19

HUAWEI TECHNOLOGIES CO., LTD. Page 20

 U2020 Alarm Function Changes

HUAWEI TECHNOLOGIES CO., LTD. Page 21

HUAWEI TECHNOLOGIES CO., LTD. Page 22

HUAWEI TECHNOLOGIES CO., LTD. Page 23

HUAWEI TECHNOLOGIES CO., LTD. Page 24

HUAWEI TECHNOLOGIES CO., LTD. Page 25

 U2020 Alarm Function Changes

HUAWEI TECHNOLOGIES CO., LTD. Page 26

HUAWEI TECHNOLOGIES CO., LTD. Page 27

HUAWEI TECHNOLOGIES CO., LTD. Page 28

HUAWEI TECHNOLOGIES CO., LTD. Page 29

HUAWEI TECHNOLOGIES CO., LTD. Page 30

HUAWEI TECHNOLOGIES CO., LTD. Page 31

HUAWEI TECHNOLOGIES CO., LTD. Page 32

HUAWEI TECHNOLOGIES CO., LTD. Page 33

HUAWEI TECHNOLOGIES CO., LTD. Page 34

HUAWEI TECHNOLOGIES CO., LTD. Page 35

Restrictions on Scenarios Restrictions on Specifications

HUAWEI TECHNOLOGIES CO., LTD. Page 36

HUAWEI TECHNOLOGIES CO., LTD. Page 37

HUAWEI TECHNOLOGIES CO., LTD. Page 38

 U2020 Alarm Function Changes

HUAWEI TECHNOLOGIES CO., LTD. Page 39

HUAWEI TECHNOLOGIES CO., LTD. Page 40

 U2020 Alarm Function Changes

HUAWEI TECHNOLOGIES CO., LTD. Page 41

HUAWEI TECHNOLOGIES CO., LTD. Page 42

HUAWEI TECHNOLOGIES CO., LTD. Page 43

HUAWEI TECHNOLOGIES CO., LTD. Page 44

HUAWEI TECHNOLOGIES CO., LTD. Page 45

 U2020 Alarm Function Changes

HUAWEI TECHNOLOGIES CO., LTD. Page 46

Restrictions on Scenarios Restrictions on Specifications

HUAWEI TECHNOLOGIES CO., LTD. Page 47

HUAWEI TECHNOLOGIES CO., LTD. Page 48

HUAWEI TECHNOLOGIES CO., LTD. Page 49