Nokia Academy
RA4140 FL16 Feature Delta
Operability Features
LTE Features
Copyright and confidentiality
The contents of this document are proprietary and confidential property of Nokia Solutions and Networks. This document is provided subject to confidentiality obligations of the applicable agreement(s).
This document is intended for use of Nokia Solutions and Networks customers and collaborators only for the purpose for which this document is submitted by Nokia Solutions and Networks. No part of this document may be reproduced or made available to the public or to any third party in any form or means without the prior written permission of Nokia Solutions and Networks. This document is to be used by properly trained professional personnel. Any use of the contents in this document is limited strictly to the use(s) specifically created in the applicable agreement(s) under which the document is submitted. The user of this document may voluntarily provide suggestions, comments or other feedback to Nokia Solutions and Networks in respect of the contents of this document ("Feedback"). Such Feedback may be used in Nokia Solutions and Networks products and related
specifications or other documentation. Accordingly, if the user of this document gives Nokia Solutions and Networks feedback on the contents of this document, Nokia Solutions and Networks may freely use, disclose, reproduce, license, distribute and otherwise commercialize the feedback in any Nokia Solutions and Networks product, technology, service, specification or other documentation.
Nokia Solutions and Networks operates a policy of ongoing development. Nokia Solutions and Networks reserves the right to make changes and improvements to any of the products and/or services described in this document or withdraw this document at any time without prior notice. The contents of this document are provided "as is". Except as required by applicable law, no warranties of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose, are made in relation to the accuracy, reliability or contents of this document. NOKIA SOLUTIONS AND NETWORKS SHALL NOT BE
RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT or for any loss of data or income or any special, incidental, consequential, indirect or direct damages howsoever caused, that might arise from the use of this document or any contents of this document.
This document and the product(s) it describes are protected by copyright according to the applicable laws.
Nokia is a registered trademark of Nokia Corporation. Other product and company names mentioned herein may be trademarks or trade names of their
respective owners.
•
LTE565: SW Download Progress Indicator
•
LTE580: Session Login Delay for BTS
•
LTE643: Multiple Read Sessions for BTS Site Manager
•
LTE955: IPv6 for Management Plane
•
LTE967: Password Aging and Account Locking
•
LTE1203: Load-based Power Saving with Tx Path Switching Off
•
LTE1235: Optimization of PRACH/RACH Power
•
LTE1308: MDT Cell Trace Enhancements
•
LTE1462: Neighbor Optimization: Non reachable neighbors
•
LTE1982: Additional PM Counters for MOCN-network-sharing Performance Monitoring
•
LTE1992: Flexi HW Replacement - Detect and Restore
•
LTE2029
: Flexible Neighbor Configurations
•
LTE2060: Add New Frequency or Cell without Reset
•
LTE2199: Configurable Buffering Time for Protocol Tracing
•
LTE2250: Syslog Substring-triggered Automated Snapshot Collection
•
LTE2341: System Upgrade to FDD-LTE 16
•
LTE2374: Vendor Certificate Management for FZC
•
LTE2378: FSM D/E (FSMr2) Support after FDD-LTE 15A
•
LTE2379: SFP Monitoring on RP3/CPRI
•
LTE2438: GNSS - Operation Mode and Tracking
•
LTE2442: Preventing Accidental Cell Activation
•
LTE2446: PM Counters for VoLTE Handover
•
LTE2491: LTE Site Element Manager Parameter Search
•
LTE2539: MRO InterRat UTRAN
•
LTE2556: Flexi Multiradio BTS Rx-sniffing Enhancements
•
LTE2593: SW License Management in LTE
• The LTE565: SW Download Progress Indicator feature introduces an improved mechanism to indicate the progress of the Base Transceiver Station's (BTS) mass software (SW) download operation for NetAct user. The LTE565: SW Download Progress Indicator feature is added to NetAct SW management application.
• Note: The BTS site manager (BTSSM) also displays progress.
• The LTE565: SW Download Progress Indicator feature introduces the reporting of a software download progress by the LTE BTS. These progress indications are generated periodically by the BTS and delivered via the OMS to NetAct, where they are displayed to the operator. The progress is reported by NetAct, both for a mass SW download operation (as a whole) and individually for each network element.
- Note: The SW update operations originating from NetAct cause progress to be sent to NetAct and the SW update operations originating from the BTSSM cause progress to be delivered to the BTSSM.
• The progress information is collected from the network and the percentage of the total download completion is shown in the SW Manager application in NetAct's Configuration application set.
• Software download progress will not be reported by the FSMr2-based BTSs. Software progress will only be reported by the FSMr3 and later BTSs.
• SW download progress is reported during BTS software updates and antenna line device (ALD) software updates, both of which have the same operation and maintenance (O&M) messaging interaction.
LTE580 Session login delay for BTS
•
This feature introduce a delay
between consecutive failed
login attempts and an account
locking period for operator
user accounts with access to
the
BTS Site Manager or
Transport Web page.
LTE580 Session login delay for BTS
• Session login delay and temporary account locking are applied for logins with a local or remote connected BTS Site Manager or with a web browser accessing to the Transport Web page. It prevents brute force attacks against a BTS by a delay between consecutive logins with invalid credentials and temporary account locking if a given maximum number of invalid login attempts within a certain time are exceeded.
• The BTS applies login delay in common for both invalid local operator user ID or password and for Centralized Network Element User Management (CNUM) managed invalid user ID or passwords. This means that each invalid login disables the login capability for all users for the duration of the configured delay time.
• A temporary account locking is applied to individual users. The temporary account locking for CNUM managed user is directly handled by CNUM, the BTS takes only care about the temporary account locking for the local operator user account. In case the local operator account is locked the BTS sends an alarm to NetAct, the alarm is cleared when the account gets unlocked again.
• The behavior of session login is defined by the applied login delay, the number of failed login attempts during the failed logon counting period and the user account locking duration.
• * The delay time between the failed login attempt and the next possible login attempt is configurable in BTS. This period starts or is re-started each the time when a user provides wrong ID or password. When the number of tolerated failed login attempt is exceeds the account is locked for the time specified by the user account lockout duration. The time is
LTE580 Session login delay for BTS
• * The maximum number of allowed consecutive failed login attempts allowed for a user in 'Failed login counting period' a user is configurable in BTS for the local operator user account and by CNUM for the centralized managed operator users. A Login attempt is only counted as failed in case the password is wrong. Failed logins due to wrong user ID or expired passwords are not counted. After exceeding the count, account is blocked for the duration of the account locking setting. The BTS sends an alarm in case the local operator user account gets locked and clears the alarm when the count is reset.
• The count is reset for non-locked users - when the user does a successful login
- when the Failed login counting period expires - when the BTS restart/reset
• The count is reset for locked users
LTE580 Session login delay for BTS
Configuration for BTS
• The feature can be configured with the BTS Site Manager and NetAct Configurator. Please note that the corresponding CNUM settings are done independently and are common for all BTS managed by one Netact.
Session login enabling/disabling
• In case the Maximum failed login attempts is equal 0 the feature is inactive; the feature is by default active
Session Login delay
• Configurable between 1 sec and 10 sec - default value is 1 sec
Failed login counting period
• Configurable between 1 min and 1440 min, default 5 min
Maximum failed login attempts during 'Failed login counting period'
LTE643 Multiple read sessions for BTS Site Manager
• Read only access privileges are introduces for users managed by Centralized NE User Management (CNUM) and support for multiple sessions for BTS Site Manger and Transport Web Page are enabled. Benefit to the customer: Enhanced security access control settings for operator users with parallel access by multiple operator users to same BTS.
• This feature enables ability to support multiple parallel user sessions for operator users with BTS Site Mangers and Transport Web Page.
Privilege Management:
• The single local operator user account has always "read/write" privileges. For managed users accounts now either "read/write" or only "read only" privileges can be assigned.
LTE643 Multiple read sessions for BTS Site Manager
BTS Site Manager
• The BTS Site Manager allows choosing between "read/write" and "read only" login mode. Although a operator user account may have "read/write" privileges the user can decide to just establish a "read-only" session.
• Authorization rules are that only one user with "read-write" access rights is allowed to login at the time. Further users are allowed to login with "read-only" rights. The maximum number of possible parallel session is 5.
• Once the first user with "read/write" privilege is active and another user with same privilege tries to log in - and the max. number of sessions is not reached - the request is rejected and the user is prompted with the information that a login with "Read-only" would be possible. The user may now try to login in "read only" mode.
• In case 5 sessions are already active the next login is rejected and the user is prompted that the number of parallel session has exceeded.
LTE643 Multiple read sessions for BTS Site Manager
Transport Web Page
• Depending on the user account privileges the Web Server presents either a start page with "read/write" capabilities or a limited start page with "read-only" capabilities.
• There are no authorization rules, i.e. there is no restriction on the number of users with "read-write" privileges logged in at the time. The maximum number of possible parallel session is 9.
• In case 9 HTTP/TCP sessions are already active the next login is rejected and the user is prompted that the number of parallel session has exceeded.
LTE643 Multiple read sessions for BTS Site Manager
•
The Read-only mode can
be enabled either
through the
Commissioning Wizard
Security
page or later
through
IP Security
.
LTE643 Multiple read sessions for BTS Site Manager
•
In case there is an
active connection with
write access rights
existing already when
attempting a new
connection, the Site
Manager allows only
read-only
LTE643 Multiple read sessions for BTS Site Manager
•
Before
Connecting
,
check the field
Read-only access
LTE643 Multiple read sessions for BTS Site Manager
•
When connected
in
Read-only
mode, a
notification
window pops up
informing about
your access
rights.
LTE955: IPv6 for Management Plane
•
The LTE955: IPv6 for Management Plane
feature allows the use of IPv6 in the entire
management plane (M-plane).
•
The LTE955: IPv6 for Management Plane
feature enables the eNB to be operated with
IPv6 in the management plane. The eNB can
work with either IPv4 or IPv6 on O&M.
•
Based on RFC 4213 Basic Transition
Mechanisms for IPv6 Hosts and Routers, all
radio access (RA) network entities must
support IPv6 on the management plane.
LTE955: IPv6 for Management Plane
•
If the LTE955: IPv6 for Management Plane feature is activated:
-
The eNB provides M-plane connectivity on either IPv6 or IPv4.
-
The following applications must work with either IPv6 or IPv4 and in single stack:
• BTS site manager (BTSSM)
- Note: Local BTSSM connectivity remains on IPv4 using private addresses.
• iOMS • NetAct
• network services, which include Dynamic Host Configuration Protocol (DHCP), Network Time Protocol (NTP), Lightweight Directory Access Protocol (LDAP), and Certificate Management Protocol (CMP) • all additional services, which include Remote Syslog, TCE, and Traffica
LTE967 Password aging and account locking
•
This feature introduces password aging and account locking for operator user
accounts to access to the
BTS Site Manager
or
Transport Web page
.
•
In addition, this feature also applies to the BTS site manager limited CLI batch scripts, as
they login to BTS using operator user accounts.
•
BTS is responsible for lifetime verification of local accounts, and providing status to BTS
site Manager and transport web page. LDAP server (on NetAct) is responsible for the
lifetime verification of and the Centralized NE User Management (CNUM) accounts and
providing status to the BTS. For
CNUM accounts, BTS informs BTS site Manager and transport web page about the state
of CNUM accounts.
LTE967 Password aging and account locking
•
BTS checks the lifetime for operator local user accounts only when it is time
synchronized with an external source. When BTS is not time synchronized, BTS grants
access but creates a user event log entry indicating the skipped check. LDAP server on
NetAct is assumed to have correct time, and hence does not perform time sync checks.
•
BTS site manager, transport web page and batch scripts inform users at login time if a
password is close to expire or have already expired.
Password life time close to expire (Both local and CNUM accounts)
•
BTS site manager, transport web page and batch scripts show a warning to the user that
her account will expire soon; access is granted.
Password life time expired, but grace attempts still available (CNUM accounts only)
•
BTS site manager, transport web page and batch scripts show a warning to the users
that the account expired but they still have grace login attempts; access is granted.
LTE967 Password aging and account locking
Password life time expired, and grace attempts not available (Both local and CNUM accounts) For local accounts
• BTS Site Manager shows an error message that the password expired and prompts the operator to enter the old password, and new password 2 times.
• Then the site manager requests BTS to update the local account with the new password. • Access to BTS is granted after successful password update.
• Transport web page and batch scripts show an error message that the password expired. Access to BTS is not granted
For CNUM accounts
- LDAP server locks the account.
- BTS site manager, transport web page and batch scripts display an error message that the password expired
LTE967 Password aging and account locking
Configuration
• On NetAct CNUM LDAP server, one password policy applies to all CNUM accounts. Operator can turn on/off password policy for CNUM users, and configure expiry period, warning period, and number of grace login attempts after expiry. This functionality exists prior to LTE967.
• For the BTS the feature configuration can be done with NetAct Configurator or BTS Site Manager. Please note that the corresponding CNUM settings are done independently and are common for all BTS managed by one Netact.
• It is possible to activate the lifetime check independently for the local account and remote CNUM accounts.
Local operator user account lifetime check
• It is enabled/disabled by the 'Local user account expiry period - if set to '0' the check the password aging check is deactivated.
CNUM operator user account lifetime check
LTE967 Password aging and account locking
Local user account expiry period
• Number of days after last password change, when the local user account on BTS expires, and BTS forces the user to change her password, it is configurable between 1 days and 9999 days. The default value is set to '0', meaning BTS does not expire local user accounts (recommended value is 90 days).
Local user account warning period
• Number of days prior to local account expiry date, when BTS starts displaying a warning to the user that her account is about to expire, it is
configurable between 1 days and 9999 days. The default value is set to '0', meaning BTS does not
◄ Back
The LTE1203 – Load-based Power Saving with Tx Path Switching Off feature provides energy saving modes, in case of a low-load period, for cells configured for MIMO operations.
The cells in the eNB can be grouped for power saving mode. These power group cells have the same coverage and the load-based power saving cell switch off order (lbpsCellSOOrder) parameter defines the order in which the power group cells are switched off.
Benefits of the feature:
• Power saving during off-peak hours, which results in OPEX savings by: • Monitoring of the system to increase or reduce capacity as required,
• Efficiently limiting capacity based on load that allows to switch off paths of the system, • Reduction of the capacity of each power group to only that which is required by the UEs
being serviced by the commercial system,
• Provides history of the power saving mode events for each eNB resource that is controlled by the LTE1203 feature.
LTE1203 – Load-based Power Saving with Tx Path Switching Off
Feature Overview
The LTE1203 – Load-based Power Saving with Tx Path Switching Off feature uses separate minimum and maximum load thresholds to support different default values from those defined in the LTE1103 – Load-based Power Saving for Multi-layer Networks feature. The LTE1203 feature calculates the power group load using the offset cell capacity of reduced Tx path cells.
Page: 26
Number: 1 Author: Presenter Subject: Presentation Notes Date: 2/4/2016 2:48:15 AM
Each eNB independently decides the power saving state of its power group cells. LTE1203 does not support any X2 data exchange between eNBs.
LTE1203 uses the same power group and cell switch off order parameters, the same power group and cell switch-off order determination algorithms, the same last cell switch off enabled parameter, and the same load counters that are defined for LTE1103.
In order to support different default values, LTE1203 uses separate minimum and maximum load thresholds than those defined for LTE1103.
LTE1203 – Load-based Power Saving with Tx Path Switching Off
Feature Overview
The cells in the eNB can be grouped for power saving mode. These power group cells have the same coverage and the load-based power saving cell switch off order (lbpsCellSOOrder) parameter defines the order in which the power group cells are switched off.
For power groups with cells that are configured for the NxN MIMO operation mode, the operator can activate the LTE1203 feature to save energy during a low load by switching off a set of cell’s Tx paths. 1
Page: 27
Number: 1 Author: Presenter Subject: Presentation Notes Date: 2/4/2016 2:48:15 AM
When the resulting number of Tx antennas in the power saving mode is 2, each antenna must correspond to a different polarization. The reduction of transmission antennas also affects the available set of
transmission modes. In case precoding vector switching (PVS) was activated in a cell for the primary synchronization signal (PSS)/secondary synchronization signal (SSS) and/or positioning reference signal (PRS), proper coding will be applied in the 2Tx cell. If a cell was modified to the 1Tx mode, PVS cannot be used. For the 2Tx or 4Tx cells, the UEs needs to reconnect, and the best transmission modes will be used from the available ones at the target number of Tx antennas. When exiting the power saving mode, transmission on the previously muted antennas will resume with normal functionality after a cell reset.
LTE1235: Optimization of PRACH/RACH Power
• The LTE1235: Optimization of PRACH/RACH Power feature ensures that the physical random access channel (PRACH)/random access channel (RACH) power is adapted in the network autonomously, based on real network performance. The power is as low as possible for low interference, but it is high enough to avoid unnecessary retransmissions.
• Manual tuning of the Preamble initial received target power (ulpcIniPrePwr) parameter to achieve an optimal preamble power setting per cell is no longer required
• Optimization of the RACH preamble power settings decreases interference between UEs which impacts on fastest accessing to the cell.
• The eNB will continually measure the cell’s interference level to keep the preamble power low enough for excessive
interference not to be created. The measurements will be averaged over a period of time. At the end of the averaging interval, the preamble power will be set to the cell’s average interference power increased by a configurable offset (typical offset value is 10 dB).
• If the newly calculated preamble power has changed by more than a configurable threshold, the new preamble power setting is broadcast in SIB2. Otherwise, the current preamble power is unchanged.
- Note: The PRACH offset and maximum rate of SIB2 updates are configurable.
• To ensure the dynamic preamble power adjustments work as desired, RACH preamble information is collected from a sampling of UEs via the RRC UE information procedure and is reported via RACH preamble statistics. An additional counter based on UE RACH feedback allows performance monitoring:
- a number of UEs with RACH success after a single preamble transmission - a number of UEs with RACH success after multiple preamble transmissions
LTE1308: MDT Cell Trace Enhancements
•
The LTE1308: MDT Cell Trace Enhancements feature provides the following benefits:
-
The operator can collect global positioning system (GPS) location information from the
capable user equipment (UEs).
-
Periodic measurements retrieve valuable data from the terminals and use them in
cell-trace-based MDT.
•
The LTE1308: MDT Cell Trace Enhancements feature supports the following
functions:
-
GPS location report
-
maximum number of UEs used in MDT
-
selection of UEs with dedicated capabilities for MDT
-
user consent for MDT
LTE1462: Neighbor Optimization: Non reachable neighbors
• The LTE1462: Neighbor Optimization: Non-reachable Neighbors feature provides the following benefits:
- The UE might try handover towards PRACH-non-reachable neighbors. This handover will fail most probably. Therefore blacklisting these neighbors will result in less handover failures.
- The iSON Manager automatically detects and optionally blacklists neighbor relations, where the geographical distance between the antennas of two neighboring cells is larger than the sum of the maximum cell sizes given by the corresponding PRACH settings. Because the handover between PRACH-non-reachable neighbors will fail, blacklisting these neighbors will reduce the number of failed handovers.
• The LTE1462: Neighbor Optimization: Non-reachable Neighbors feature executes a consistency check of the current radio configuration planned cell range versus a maximal achievable or allowed cell range due to the physical random access channel (PRACH) configuration.
• During the check, the current available configuration of a cell with the geo-location and the available neighbor relations are compared with the radio parameters set for this cell. The feature checks whether the PRACH-defined cell radius of two proposed neighbors (for example, based on automated neighbor relation ANR) overlap, based on the PRACH settings of those neighbors. In case the cell areas based on the PRACH settings do not overlap, there is a high probability that handover between both cells fails, and therefore, the neighbor relation is proposed to be blacklisted.
• Based on this information, the operator may start subsequent adaptations in the network configuration. For the PRACH configuration, the zero correlation zone is the major criterion to be checked.
• In LTE the settings of PRACH (preamble format, number of cyclic shifts) define the maximum possible size of a cell, irrespective of the signal strength or signal quality. If the distance between the antennas of two neighboring cells is larger than the sum of the corresponding PRACH-defined cell sizes, any handover between the two cells runs a high risk of failure; these are "PRACH-non-reachable" neighbors.
LTE1982: Additional PM Counters for MOCN-network-sharing Performance Monitoring
•
The LTE1982: Additional PM Counters for MOCN-network-sharing Performance Monitoring
feature introduces new performance measurements to provide feedback for a network's load
monitoring and capacity adjustments of a shared network.
•
The LTE1982: Additional PM Counters for MOCN-network-sharing Performance Monitoring
feature introduces new counters that are included in the following functionalities:
- PM counters related to the average number of radio resource control (RRC)- connected UEs per public land mobile network identity (PLMN-ID)
- PM counters related to the packet data convergence protocol (PDCP) service data unit (SDU) data volume per PLMN-ID
- PM counters related to the average number of active UEs with data in buffer uplink/downlink (UL/DL) per PLMN-ID
- PM counters related to the average scheduled internet protocol (IP) throughput UL per QCI per PLMN-ID
- PM counters related to the average scheduled IP throughput DL per quality of service class identifier (QCI) per PLMN-ID.
LTE1992: Flexi HW Replacement - Detect and Restore
• The LTE1992: Flexi HW Replacement - Detect and Restore feature introduces an automated method to restore the software and configuration on the eNB's system module that has been installed to replace the existing, defective hardware. Instead of restoring the eNB from a created configuration plan, the eNB is restored from a plan created automatically by NetAct. The plan is created from the eNB's actual configuration that was
previously synchronized and stored in NetAct's configuration management CM history database. • The LTE1992: Flexi HW Replacement - Detect and Restore feature provides the following benefits:
- Saves time when manually configuring a HW replacement.
- Simplification of the restoration and configurations process of a HW replacement.
• The LTE1992: Flexi HW Replacement - Detect and Restore feature enables NetAct Configurator to restore the previous eNB's software and configuration data to the new eNB system module. The process takes place, based on the last updated configuration in NetAct Configurator. The same software version and configuration data as on the replaced system module hardware are restored from NetAct Configurator CM History database. The LTE1992: Flexi HW Replacement - Detect and Restore feature’s functionality does not need to be
LTE1992: Flexi HW Replacement - Detect and Restore
• The replaced eNB sends the information to the OMS along with a commissioning request. After this, the OMS set a notification describing the configuration change in the NetAct Configurator. To begin the restoration process for the eNB, the workflow engine configures the necessary parameter as following:
• It is needed to trigger the NetAct Configurator "Prepare for configuration restore" workflow for a specified eNB prior to triggering autoconnection for that eNB.
• NetAct Configurator prompts to specify the autoconnection identification option and select option of eNB configuration restore.
- select of the automatic option is desired to have NetAct Configurator automatically trigger the "Restore configuration automatically" workflow, when polling has determined that the eNB has requested commissioning
- select of the manual option is desired when is decision for manually trigger the "Restore configuration manually" workflow engine and indicate a timeframe in NetAct's Configurator CM History database to create a plan for that eNB
• If the automatic option was selected, NetAct Configurator executes the following:
- to specify a time, a date in history from which to generate a plan from to restore the eNB from actual configuration - NetAct Configurator confirms that the activeSWRelease parameter exists in the actual configuration for the eNB at the
• Formerly called Flexible neighbor configurations
Purpose
• Overload protection in the eNB:
Stop ANR if the maximum number of allowed neighbor objects is reached.
Sum of LNADJ + LNADJL + LNREL + LNADJW + LNRELW + LNADJG + LNRELG + LNADJX + LNRELX+… The maximum number is a configurable parameter.
Benefit for the customer
• Prevention of eNB restarts due to exceeded maximum number of neighbor objects
• Support of neighbor eNBs with maximum of 256 cells
• Automatic resolution of X2 links with incomplete information
Alarms
• “Overload monitoring: High number of neighbor related objects”
• “Overload detected: max number of neighbor relation objects reached”
LTE2029 Extend amount of neighboring cells with overload control in eNB
LTE2029 consists of 3 subfeatures:A. support of neighbor eNBs with up to 256 cells (max. 256 LNADJL per LNADJ), formerly limited to 64. (lab test requires an eNB simulator)
B. overload protection in the eNB based on the number of neighbor related objects
The maximum number of neighbor objects is configurable. Default and maximum value is 4000; it may be modified to a smaller value, e.g. for test purposes.
The number of current neighbor objects is the sum of the following objects:
LNADJ + LNADJL + LNREL (LTE neighbors)
+ LNADJW + LNRELW (WCDMA neighbors)
+ LNADJG + LNRELG (GSM neighbors)
+ LNADJT + LNRELT (TD-SCDMA neighbors)
+ LNADJX + LNRELX (CDMA2000 neighbors)
• If the number of neighbor related objects has reached maxNumAnrMoiAllowed, then ANR will not be able to create further neighbor related objects; further creation of neighbor related objects via plan
provisioning is restricted.
• A minor alarm will be raised if the number of neighbor related objects reaches 80 % of the configured maximum: High number anr moi reached.
• A major alarm will be raised if the number of neighbor related objects reaches the configured maximum:
Max number anr moi reached.
LTE2029 Extend amount of neighboring cells with overload control in eNB
C. A neighbor cell check will run periodically, with configurable parameters for start time and periodicity. It will detect LNADJ with incomplete neighbor cell data and will trigger a repetition of X2 setup for such LNADJ (“incomplete” means LNADJ with missing LNADJL).
An LNADJ has to meet these two conditions, in order to be considered as incomplete: • LNADJ with X2 available
• The LTE2060: Add New Frequency or Cell without Reset feature provides the following benefits:
- reduces impact on cells in service during configuration extensions and re-configurations - reduces system downtime by preventing an eNB restart in many upgrade scenarios
• Configuring new cells and adding new RF and baseband (BB) hardware currently requires an eNB restart on every occasion. This involves service outage of all existing cells. The feature supports configuration of new cells and addition of new BB, RF, and ALD hardware (only with a newly added RF module) without an eNB restart in many scenarios which are relevant for typical customer upgrade situations such as introduction of an additional frequency layer into an existing network.
• Without the knowledge of eNB internal DSP deployment algorithms, it is not possible to know in advance if a specific upgrade scenario is possible without a site restart. A configurable eNB behavior protects them from an unintended site restart and service outage. There is an option to select if a site restart is not acceptable. If not, the plan file activation will be rejected by the eNB.
• Carrier aggregation (CA) between a newly added cell and existing cells can be configured without an eNB restart. Also, the uplink coordinated multipoint transmission (UL CoMP) can be configured without restart, provided the UlComp is already enabled and digital signal processor (DSP) pools need not be rearranged.
• Within the scope of the LTE2060: Add New Frequency or Cell Without Reset feature, there are still the following restrictions:
- rearranging existing DSP pools still requires reloading the DSP SW, which requires temporary dropping of all cells from affected FSP cards - changing the Activate flexible base band usage (actFlexBbUsage) parameter no longer requires an eNB restart, but all cells will be temporary
dropped
- configuring the dual mode with CPRI RF modules requires an eNB restart - a DSP or FSP reset is required for fiber lengths longer than 10 km
•
The LTE2199: Configurable Buffering Time for Protocol Tracing feature introduces
trace reports that can be sent by the evolved Node B (eNB) with configurable
buffering time.
•
Feature introduces trace reports that can be sent by the eNB with configurable
buffering time; a single trace report consists of multiple records.
-
The trace records are buffered in the eNB for up to 2000 milliseconds (ms), or until a trace
report reaches a defined size.
•
It is possible to configure the maximum buffering time to a lower value to reduce the
delay with the LTE2199: Configurable Buffering Time for Protocol Tracing feature.
-
The maxBufferingTime MTRACE parameter configures the maximum buffering time for
trace records. The buffering time can be configured per trace session with values that
ranges from 50 to 2000 ms.
◄ Back
The LTE2250: Syslog Substring-triggered Automated Snapshot Collection feature is an extension of the LTE1099: Event-Triggered Symptom Data Collection and Provisioning
feature's concept of an automatic fault-triggered BTS symptom data (troubleshooting logs) collection. This model allows commissioning a BTS with the new category of
automated snapshot collection trigger, based on a single substring occurrence found in the syslog stream.
Benefits of LTE2250:
• Ability to set the generic trigger to collect a snapshot based on any BTS event which is visible in the syslog stream,
• Ability to work separately, without any external tools.
LTE2250 – Syslog Substring-triggered Automated Snapshot Collection
Triggering Fault or Syslog string
LTE2250 – Syslog Substring-triggered Automated Snapshot Collection
The LTE2250 – Syslog Substring-triggered Automated Snapshot Collection feature allows commissioning a BTS with the new category of an automated snapshot collection trigger, based on a single substring occurrence in the syslog stream.
The following safety mechanisms are built in:
• A minimum of 10-characters-long defined clause on a searched string – it is necessary to avoid accidents that would trigger a snapshot too often,
• A graceful period defined – a given string is being searched continuously; once it has been found, the search stops to protect the system against a flood of snapshots,
• Allows five snapshots triggered maximum per 24h per BTS.
The LTE2250 – Syslog Substring-triggered Automated Snapshot Collection feature is configurable in parallel with the LTE1099 – Event-triggered Symptom Data Collection and
LTE2341 System Upgrade to FDD-LTE 16
•
This is the system upgrade support for LTE releases.
•
It enables the smooth upgrade from major release (RLxx) N-2 to release N in
the overall network.
•
LTE releases are recently scheduled with half year release cycles. With N-2
system release upgrade support NSN enables that operator has not
necessarily to follow each half year release, but can consider to do only one
system upgrade during one year, but still have full smooth upgrade support.
•
The upgrade is supported from RL70 (NetAct 8 EP2) to FDD-LTE 16 (NetAct16)
or from FDD-LTE 15A (NetAct8 15.5) to FDD-LTE 16 (NetAct 16).
•
For Flexi Zone the system upgrade path from RL70 or LTE 15A to
LTE2341 System Upgrade to FDD-LTE 16
• General feature support as general part of system upgrade feature setup
1) The upgrade from release N-2 or N-1 to release N is possible in one step. No intermediate SW versions are necessary to be installed.
The impacted NEs are the Flexi Multiradio BTS, NetAct with all LTE relevant applications including Optimizer, Trace Viewer, the Northbound interfaces, the iOMS, Traffica and Layer3 Data Collector with its applications, as L3 data analyzer.
2) The upgrade paths have to consider both Flexi Multiradio platforms FSMr3 and FSIH in following way:· FSMr3 to FSMr3This is valid for configurations which can be fulfilled with FSMr3 configurations in N-2 or N-1.· FSMr2 to FSMr2This is valid for configurations which can be fulfilled with FSMr2 configuration in N-2 or N-1. Note that as specified in LTE2378, the FSMr2 SW is frozen on FDD-LTE15A. The LTE16 software packages may contain FDD-LTE 15A updates for FSMr2 but the FSMr2 will report its sw version as FDD-LTE 15A.
• Note: The FSMr2 software is frozen for release FDD-LTE 15A. NetAct and OMS must support an FDD-LTE 15A adaptation for the FSMr2 in release FDD-LTE 16.
FL16 Upgrade Top Down Approach
Software fallback
• Software fallback is an automatic activation of an earlier SW version that is active before the SW upgrade and is stored in the eNB. Fallback is triggered when the eNB or iOMS is unable to activate its new software version or use a new database configuration version. If the eNB does not locally store the complete fallback SW for all the hardware (HW) units, it may request from NetAct a software update for the latest active software build for a managed HW module compatible with the eNB software version. Only after the SW download from NetAct can service be re-established. After the successful fallback, the passive software build is active in all the HW units and service can be re-established. Any configuration updates done with the new SW will be lost, since the eNB takes the configuration database into service that fits to the fallback SW.
• NOTE: In case of minor failures, no SW fallback will be initiated but the error information will be indicated. The failures are logged in a non-volatile memory and include a detailed information about the reason of the failure.
Software rollback
• SW rollback is a manually initiated SW fallback using the BTSSM or NetAct SWM. The operator can trigger SW rollback when key services are not activated successfully after the SW upgrade. Note that SW rollback is only guaranteed if the source SW version has not been removed or overwritten in a non-volatile storage (NVS). SW rollback is done with the SW stored in the passive file system and no SW download from the server is part of the operation. If the passive SW has been overwritten with a different SW version, the rollback to the former release is not possible.
Page: 45
Number: 1 Author: Presenter Subject: Presentation Notes Date: 2/4/2016 2:48:18 AM Software downgrade must not be executed. A software downgrade to an earlier SW version is not guaranteed and might end up in an uncommissioned state of the eNB.
A software rollback to the stored SW load restores the earlier configuration. If there has been a major network reconfiguration after the upgrade, such as reconfiguring the eNB from IPv4 to IPv6, then network connectivity issues can occur after the rollback. Reconfigurations after the SW upgrade must be evaluated before triggering SW rollback to avoid service outage.
LTE2378: FSM D/E (FSMr2) Support after FDD-LTE 15A
•
The LTE2378: FSM D/E (FSMr2) Support after FDD-LTE 15A feature introduces the
system module FSM D/E (FSMr2) support after the FDD-LTE 15A release, which is the
final release for the introduction of the new features on the FMSr2. The features
introduced after the FDD-LTE 15A will not be available for the FSMr2.
•
The FDD-LTE 16 contains a dedicated software for the FSMr2. These software
packages include the FDD-LTE 15A or the subsequent maintenance packages. After
the upgrade to FDD-LTE 16 or later releases, the FSM D/E (FSMr2) will indicate an
FL15A version as the active and passive software versions.
•
Note: The FSMr2 software is frozen for release FDD-LTE 15A. NetAct and OMS
LTE2379 SFP monitoring on RP3/CPRI
This feature introduces possibility to monitor SFP in BTS SM
and NetAct.
BTS SM shows the SFP online diagnostic information:
SFP Vendor - SFP Serial - SFP Type
- Module temperature
- Transceiver Tx supply voltage - Transceiver Tx bias current - Transceiver Tx power - Transceiver Rx optical power - SFP wavelength
- SFP Transmission mode - SFP Transmission rate - Transmission distance
- Tx Power High Alarm threshold - Tx Power Low Alarm threshold - Tx Power High Warning threshold - Tx Power Low Warning threshold - Rx Power High Alarm threshold - Rx Power Low Alarm threshold - Rx Power High Warning threshold - Rx Power Low Warning threshold - Temperature High Alarm threshold
LTE2379 SFP monitoring on RP3/CPRI
Not all parameters are available for all SFP. Not supported functionality in BTS SM are shown as "N/A"BTS SM support on-demand polling and shows data from both ends of the link, near end and far end.
Through BTS SM it is possible to monitor BER and set the cumulative LCV (bit error) counter to zero
NetAct shows the SFP general information SFP Vendor
SFP Serial SFP Type
Transmission distance
Tx Power High Alarm threshold Tx Power Low Alarm threshold Tx Power High Warning threshold Tx Power Low Warning threshold Rx Power High Alarm threshold Rx Power Low Alarm threshold Rx Power High Warning threshold Rx Power Low Warning threshold Temperature High Alarm threshold Temperature Low Alarm threshold
Information about SFP are gathering into separate file with ring buffer which is included in Snapshot. HW platform support FDD/TDD
•
SFP data is
presented in the
Radio Network
Configuration page,
where SFP-# appears
as a new Managed
Object (MO) under
MRBTS.
•
Displayed data is
based on the SFP‘s
built-in diagnostic
function.
LTE2379 SFP monitoring on RP3/CPRI
•
This feature introduces new capabilities in the
BTS site manager (BTSSM) and NetAct for
monitoring SFP information in long term
evolution (LTE) network. A new SFP monitoring
diagnostics is introduced. In this diagnostics, the
BTSSM monitors and shows the available SFP
dynamic information periodically. This diagnostic
can be run before or after the commissioning.
Dynamic data is as follows:
- Module temperature
- Transceiver transmission (TX) supply voltage - Transceiver TX bias current
- Transceiver TX power
LTE2438: GNSS - Operation Mode and Tracking
• The LTE2438: GNSS - Operation Mode and Tracking feature introduces the possibility to select the operation mode and to track the detected satellites.
• Feature provides the capability to select the type of GNSS synchronization from the following control modes:
- GPS only - GLONASS only
- All-in-view (for example, GPS + GLONASS)
GNSS receiver GPS support GLONASS support Module
FYGA supported not supported FSMF, FSIH
FYGB supported supported FSMF, FSIH
FYGD supported not supported FSMF, FSIH
FYGE supported not supported FSMF, FSIH
FYGG supported supported FSMF, FSIH
FYGH supported not supported FSIH
OPUS-5 supported not supported FZM (FWBA, FWBB, FWDA, FWEA, FWFA, FWGB, FWHA, FWHD, FWHE, FWHF, FWHN, FWHO, FWIB, FWND)
LTE2438: GNSS - Operation Mode and Tracking
•
NetAct provides the following:
- Indication of the currently selected control mode - Capability to change the control mode
- Performance management (PM) to track the GNSS synchronization performance - Active GNSS receiver type
- GNSS receiver unit name
•
The BTS site manager (BTSSM) provides the following:
- Indication of the currently selected control mode - Capability to change the control mode
- PM to track the GNSS synchronization performance
- Constellation mode along with the control mode for a given receiver - Additional information for tracking satellites:
• Type (GPS or GLONASS) • GNSS receiver unit name
LTE2442: Preventing Accidental Cell Activation
• Currently The Flexi Multiradio BTS support Administrative STate (AST) to locking cell objects as only a mechanism to lock/unlock the cell.
• This feature introduce the possibility to prevent accidentally unlock the cell by introducing new a parameter: preventCellActivation
• Feature dependency: When preventCellActivation is active then AST can't be in unlocked state.
• preventCellActivation parameter can be changed without BTS restart (modifiable online).
• To unlock the cell operator need to change parameter AST to unlock and preventCellActivation to False.
• State Management in NetAct give the possibility to display the status of preventCellActivation parameter but without the possibility to change the state.
• preventCellActivation parameter can be changed only via commissioning. (Changing parameter
value by direct operation is not possible). • Default value of preventCellActivation is False.
LTE2442: Preventing Accidental Cell Activation
• Range: Type: Boolean Default value: false
• Related parameters: administrativeState in LNCEL
• Related parameters' description: If administrativeState is set to 'unlocked', then preventCellActivation shall be set to 'false'. If preventCellActivation is set to 'true', then administrativeState shall be set to 'locked' or 'shutting down'.
• Modification type: Online • Related functions: Operability
• Related features: LTE2442 Preventing accidental cell activation
• Parameter name: Prevent cell activation
• Parameter short name: preventCellActivation
• Full description: This parameter prevents cell activation. If this parameter is set to true, then the cell can't be set to unlocked. • Managed object class: LNCEL • Managed object full name: LTE BTS
LTE2442: Preventing Accidental Cell Activation
• When trying to unlock a cell from NetAct for which the Prevent cell activation is set to true, a corresponding error message will occur.
LTE2446: PM Counters for VoLTE Handover
•
The LTE2446: PM Counters for VoLTE Handover feature introduces VoLTE QoS Class
Identifier 1 (QCI1)-specific PM counters. These counters are important because
VoLTE is a very end-user-sensitive application for which the customer can monitor
mobility behavior and an HO success rate separately.
•
The LTE2446: PM Counters for VoLTE Handover feature introduces PM counters
which enable monitoring success rates in intra-radio access technology (RAT) mobility
scenarios with active VoLTE calls. The new counters are included in the following
functionalities:
-
PM counters for S1 HO
-
PM counters for X2 HO
-
PM counters for intra-eNB HO
LTE2491: LTE Site Element Manager Parameter Search
• Search function on RNW
configuration page has been further improved by:
- Providing a List of search results incl. Parameter short names, values and short descriptions - Adjustable search options that
allow for more detailed filtering of search results (next slide).
- Also parameters not existing in the current configuration can be found by checking Show all.
LTE2491: LTE Site Element Manager Parameter Search
• the search options should be
used carefully, especially if the exact name of the parameter in question is unknown.
• Example: the actual Physical
layer cell identity of this eNB‘s
cells will only be found from the search word PCI , if either
Related parameters or Related
parameters description is
checked. The default selection Parameter name and
Parameter short name will not lead to the desired result.
LTE2539: MRO InterRat UTRAN
• The LTE2539: MRO inter-RAT UTRAN feature improves the handover performances between the different technologies. The focus of this feature is the interworking between LTE and UTRAN.
• Improves the handover performance between LTE and UTRAN. Main purpose of this functionality is to minimize the negative effects caused by the handover threshold not being optimally set, which results in handover failures or radio link failures.
- The B2 threshold2 represents the threshold for the target UTRAN cell measurement (the target cell must be higher (stronger) than this value). The goal of the B2 threshold2 optimization is to adjust the threshold (increase or decrease) in an effort to minimize subsequent radio link failures (RLF) and handover failures across all UTRAN neighbors associated with a specific UTRAN frequency. The feature optimizes both the data-only B2 threshold2 as well as the new VoLTE-specific B2 threshold2 for WCDMA, which was added as part of the LTE64: Service-based Handover Thresholds feature.
• The following inter-RAT handover failure use cases are minimized between LTE and UTRAN:
- Too Late inter-RAT HO from LTE to 3G
- Too Early inter-RAT HO with an HO failure from LTE to 3G
• The LTE2539: MRO inter-RAT UTRAN feature provides an automatic method, implemented in iSON Manager, for optimizing the B2 threshold2 measurement threshold which is used to trigger handover to UTRAN. The feature LTE2539: MRO inter-RAT UTRAN complements feature LTE1749: MRO InterRAT UTRAN, which comprises the eNB part of MRO InterRAT UTRAN.
• At a high level, the eNB is responsible for collecting PM counters which track the number of radio link failure events and handover failure events related to the mobility to UTRAN. These PM counters are provided by the
LTE2556: Flexi Multiradio BTS Rx-sniffing Enhancements
• The LTE2556: Flexi Multiradio BTS Rx-sniffing Enhancements feature is an enhancement of the
LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing feature.
• The LTE2556: Flexi Multiradio BTS Rx-sniffing Enhancements feature provides the following
benefits:
- increases the quality of Rx RF-sniffing tests by adding new use cases for external and self-interference detection and PIM fault localization
- increases the scope of Rx RF-sniffing to cover the Rel. 3/4 RF hardware as well
- removes the necessity for costly and labor-intensive site portable PIM analyzers to be used
• The LTE2556: Flexi Multiradio BTS Rx-Sniffing Enhancements feature adds supports for distance to
passive inter-modulation product (DTP) measurements to derive fault positions within the antenna network. Passive inter-modulation products (PIM) is the unwanted signal or signals generated by the non-linear mixing of two or more frequencies in a passive (or linear) device such as a connector or cable. Possible sources for PIM could be:
- coax jumper/cable connectors - power divider
LTE2593: SW License Management in LTE
•
The LTE2593: SW License Management in LTE feature introduces a mechanism of
managing licensed features by using Software License Keys (SW LKs) in the LTE. In this
new and simplified approach the SW LKs control licensed features with minimized
impact on eNodeBs. This feature is applicable to the FDD-LTE technology.
•
The LTE2593: SW License Management in LTE feature provides the following benefits:
-
Fully automatic mechanism: The License management runs in the background, and it
requires minimal operational work.
-
Flexibility: The SW LKs are not physically installed on the eNodeB, but they are handled in
the CLS.
-
One common CLS for complete customer's network: Pools are not split into NetAct
LTE2593: SW License Management in LTE
•
The LTE2593: SW License Management in LTE feature introduces a mechanism for managing
physical SW LKs in LTE.
- The Centralized License Server (CLS) is an application that provides a central control point for sharing a right-to-use (RTU) based on SW LKs. There is one CLS per whole operator’s network. The network is divided into NetAct Regional Cluster (NetAct RCs). Each NetAct RC collects configuration data and counter information.
- The SW Entitlement Manager (SWEM) is a component of the existing SW Asset Monitoring (SWAM). The SWEM continuously checks the NetAct database and it collects configuration data for relevant Sales Items (SIs).
- If a demand for an LK increases, license capacity stored in the Pool LKs is assigned, and a right-to-use is granted for the related eNB. The LK is not downloaded to the network element (NE), but stay in the CLS (bookkeeping via SWEM).