Sran16 2 Feature Descriptions and Instructions(1)
January 18, 2017 | Author: vusal | Category: N/A
Short Description
Download Sran16 2 Feature Descriptions and Instructions(1)...
Description
Nokia Networks
Single RAN, Rel. SRAN 16.2, Operating Documentation, Issue 03 SRAN 16.2, Feature Descriptions DN09218825 Issue 01E Approval Date 2016-06-16
SRAN 16.2, Feature Descriptions
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof. The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of the process of continuous development and improvement of the documentation. This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the right to change any such information and statements without notice. Nokia Solutions and Networks has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product will be uninterrupted or error-free. NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT. This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © 2016 Nokia Solutions and Networks. All rights reserved.
f
Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for any additional information.
2
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table of Contents This document has 366 pages
Summary of changes................................................................... 31
1
Introduction to SRAN 16.2 features............................................. 33
2
2.2.1.6
Descriptions of radio resource management and telecom features. 34 SR001052: Feature parity with FDD-LTE 16 newly developed features........................................................................................ 34 Description of SR001052: Feature parity with FDD-LTE 16 newly developed features.......................................................................34 Benefits........................................................................................ 34 Requirements...............................................................................34 Functional description.................................................................. 34 System impact..............................................................................35 SR001052: Feature parity with FDD-LTE 16 newly developed features management data.......................................................... 35 Sales information......................................................................... 35 SR001007: SBTS feature parity in SRAN 16.2............................ 35 Description of SR001007: SBTS feature parity in SRAN 16.2..... 35 Benefits........................................................................................ 36 Requirements...............................................................................36 Functional description.................................................................. 36 System impact..............................................................................36 SR001007: SBTS feature parity in SRAN 16.2 management data.. 37 Sales information......................................................................... 37
3 3.1 3.1.1 3.1.1.1 3.1.1.2 3.1.1.3 3.1.1.4 3.1.1.5
Descriptions of transport and transmission features.................... 38 SR000371: 1000Base-BX Optical GE Interface...........................38 Description of SR000371: 1000Base-BX Optical GE Interface....38 Benefits........................................................................................ 38 Requirements...............................................................................38 Functional description.................................................................. 38 System impact..............................................................................39 SR000371: 1000Base-BX Optical GE Interface management data. 40 Sales information......................................................................... 40 SR000369: 1000Base-LX Optical GE Interface........................... 41 Description of SR000369: 1000Base-LX Optical GE Interface.... 41 Benefits........................................................................................ 41 Requirements...............................................................................41 Functional description.................................................................. 41 System impact..............................................................................42
2.1 2.1.1 2.1.1.1 2.1.1.2 2.1.1.3 2.1.1.4 2.1.1.5 2.1.1.6 2.2 2.2.1 2.2.1.1 2.2.1.2 2.2.1.3 2.2.1.4 2.2.1.5
3.1.1.6 3.2 3.2.1 3.2.1.1 3.2.1.2 3.2.1.3 3.2.1.4
Issue: 01E
DN09218825
3
SRAN 16.2, Feature Descriptions
3.2.1.5 3.2.1.6 3.3 3.3.1 3.3.1.1 3.3.1.2 3.3.1.3 3.3.1.4 3.3.1.5 3.3.1.6 3.4 3.4.1 3.4.1.1 3.4.1.2 3.4.1.3 3.4.1.4 3.4.1.5 3.4.1.6 3.5 3.5.1 3.5.1.1 3.5.1.2 3.5.1.3 3.5.1.4 3.5.1.5 3.5.1.6 3.6 3.6.1 3.6.1.1 3.6.1.2 3.6.1.3 3.6.1.4 3.6.1.5 3.6.1.6 3.7 3.7.1 3.7.1.1 3.7.1.2 3.7.1.3 3.7.1.4 3.7.1.5 3.7.1.6
4
SR000369: 1000Base-LX Optical GE Interface management data. 42 Sales information......................................................................... 43 SR000368: 1000Base-SX Optical GE Interface...........................43 Description of SR000368: 1000Base-SX Optical GE Interface....43 Benefits........................................................................................ 43 Requirements...............................................................................44 Functional description.................................................................. 44 System impact..............................................................................45 SR000368: 1000Base-SX Optical GE Interface management data. 45 Sales information......................................................................... 46 SR000370: 1000Base-ZX Optical GE Interface...........................46 Description of SR000370: 1000Base-ZX Optical GE Interface....46 Benefits........................................................................................ 46 Requirements...............................................................................46 Functional description.................................................................. 46 System impact..............................................................................47 SR000370: 1000Base-ZX Optical GE Interface management data. 48 Sales information......................................................................... 48 SR000788: 1PPS&ToD Sync from External GNSS receiver........49 Description of SR000788: 1PPS&ToD Sync from External GNSS receiver........................................................................................ 49 Benefits........................................................................................ 49 Requirements...............................................................................49 Functional description.................................................................. 49 System impact..............................................................................50 SR000788: 1PPS&ToD Sync from External GNSS receiver management data........................................................................ 51 Sales information......................................................................... 52 SR000600: Backup IPsec Tunnel................................................ 52 Description of SR000600: Backup IPsec Tunnel......................... 52 Benefits........................................................................................ 52 Requirements...............................................................................53 Functional description.................................................................. 53 System impact..............................................................................54 SR000600: Backup IPsec Tunnel management data.................. 54 Sales information......................................................................... 56 SR000366: BTS Firewall..............................................................56 Description of SR000366: SBTS Firewall.................................... 56 Benefits........................................................................................ 56 Requirements...............................................................................56 Functional description.................................................................. 56 System impact..............................................................................57 SR000366: SBTS Firewall management data............................. 58 Sales information......................................................................... 59
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.8 3.8.1 3.8.1.1 3.8.1.2 3.8.1.3 3.8.1.4 3.8.1.5 3.8.1.6 3.9 3.9.1 3.9.1.1 3.9.1.2 3.9.1.3 3.9.1.4 3.9.1.5 3.9.1.6 3.10 3.10.1 3.10.1.1 3.10.1.2 3.10.1.3 3.10.1.4 3.10.1.5 3.10.1.6 3.11 3.11.1 3.11.1.1 3.11.1.2 3.11.1.3 3.11.1.4 3.11.1.5 3.11.1.6 3.12 3.12.1 3.12.1.1 3.12.1.2 3.12.1.3 3.12.1.4 3.12.1.5 3.12.1.6
Issue: 01E
SR000402: BTS QoS Support for Terminated and Routed Traffic... 59 Description of SR000402: BTS QoS Support for Terminated and Routed Traffic...............................................................................59 Benefits........................................................................................ 59 Requirements...............................................................................59 Functional description.................................................................. 59 System impact..............................................................................63 SR000402: BTS QoS Support for Terminated and Routed Traffic management data........................................................................ 64 Sales information......................................................................... 70 SR000847: BTS Synchronization Mode Support......................... 70 Description of SR000847: BTS Synchronization Mode Support...... 70 Benefits........................................................................................ 71 Requirements...............................................................................71 Functional description.................................................................. 71 System impact..............................................................................73 SR000847: BTS Synchronization Mode Support management data.............................................................................................. 74 Sales information......................................................................... 75 SR000365: Electrical 100/1000-Base-T Interface........................76 Description of SR000365: Electrical 100/1000-Base-T Interface..... 76 Benefits........................................................................................ 76 Requirements...............................................................................76 Functional description.................................................................. 76 System impact..............................................................................77 SR000365: Electrical 100/1000-Base-T Interface management data.............................................................................................. 78 Sales information......................................................................... 79 SR000350: Ethernet Termination................................................. 79 Description of SR000350: Ethernet Termination.......................... 79 Benefits........................................................................................ 79 Requirements...............................................................................79 Functional description.................................................................. 80 System impact..............................................................................80 SR000350: Ethernet Termination management data................... 81 Sales information......................................................................... 83 SR000344: Fast IP Rerouting...................................................... 83 Description of SR000344: Fast IP Rerouting............................... 83 Benefits........................................................................................ 84 Requirements...............................................................................84 Functional description.................................................................. 84 System impact..............................................................................85 SR000344: Fast IP Rerouting management data........................ 85 Sales information......................................................................... 87
DN09218825
5
SRAN 16.2, Feature Descriptions
3.13 3.13.1 3.13.1.1 3.13.1.2 3.13.1.3 3.13.1.4 3.13.1.5 3.13.1.6 3.14 3.14.1 3.14.1.1 3.14.1.2 3.14.1.3 3.14.1.4 3.14.1.5 3.14.1.6 3.15 3.15.1 3.15.1.1 3.15.1.2 3.15.1.3 3.15.1.4 3.15.1.5 3.15.1.6 3.16 3.16.1 3.16.1.1 3.16.1.2 3.16.1.3 3.16.1.4 3.16.1.5 3.16.1.6 3.17 3.17.1 3.17.1.1 3.17.1.2 3.17.1.3 3.17.1.4 3.17.1.5 3.17.1.6 3.18 3.18.1 3.18.1.1 3.18.1.2
6
SR000870: Flexible IP Addressing for PKI.................................. 87 Description of SR000870: Flexible IP Addressing for PKI........... 87 Benefits........................................................................................ 87 Requirements...............................................................................87 Functional description.................................................................. 87 System impact..............................................................................88 SR000870: Flexible IP Addressing for PKI management data.... 88 Sales information......................................................................... 89 SR000360: IP Transport Network Measurements........................89 Description of SR000360: IP Transport Network Measurements..... 89 Benefits........................................................................................ 89 Requirements...............................................................................90 Functional description.................................................................. 90 System impact..............................................................................96 SR000360: IP Transport Network Measurements management data.............................................................................................. 97 Sales information......................................................................... 98 SR000439: IPSec Emergency Bypass.........................................99 Description of SR000439: IPSec Emergency Bypass..................99 Benefits........................................................................................ 99 Requirements...............................................................................99 Functional description.................................................................. 99 System impact............................................................................100 SR000439: IPSec Emergency Bypass management data.........101 Sales information....................................................................... 101 SR000356: IPsec for BTS.......................................................... 102 Description of SR000356: IPsec for BTS................................... 102 Benefits...................................................................................... 102 Requirements.............................................................................102 Functional description................................................................ 102 System impact............................................................................104 SR000356: IPsec for BTS management data............................ 104 Sales information....................................................................... 107 SR000396: IPv4 based Iub........................................................ 107 Description of SR000396: IPv4 based Iub................................. 107 Benefits...................................................................................... 107 Requirements.............................................................................107 Functional description................................................................ 107 System impact............................................................................108 SR000396: IPv4 based Iub management data.......................... 109 Sales information........................................................................110 SR000397: IPv4 based Packet Abis Transport.......................... 110 Description of SR000397: IPv4 based Packet Abis Transport... 110 Benefits.......................................................................................110 Requirements............................................................................. 111
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.18.1.3 3.18.1.4 3.18.1.5 3.18.1.6 3.19 3.19.1 3.19.1.1 3.19.1.2 3.19.1.3 3.19.1.4 3.19.1.5 3.19.1.6 3.20 3.20.1 3.20.1.1 3.20.1.2 3.20.1.3 3.20.1.4 3.20.1.5 3.20.1.6 3.21 3.21.1 3.21.1.1 3.21.1.2 3.21.1.3 3.21.1.4 3.21.1.5 3.21.1.6 3.22 3.22.1 3.22.1.1 3.22.1.2 3.22.1.3 3.22.1.4 3.22.1.5 3.22.1.6 3.23 3.23.1 3.23.1.1 3.23.1.2 3.23.1.3 3.23.1.4
Issue: 01E
Functional description.................................................................111 System impact............................................................................ 112 SR000397: IPv4 based Packet Abis Transport management data.. 112 Sales information........................................................................114 SR000395: IPv4 based S1/X2....................................................114 Description of SR000395: IPv4 based S1/X2.............................114 Benefits.......................................................................................114 Requirements............................................................................. 114 Functional description.................................................................114 System impact............................................................................ 115 SR000395: IPv4 based S1/X2 management data......................115 Sales information........................................................................118 SR001003: IPv4 based SBTS Management Plane.................... 118 Description of SR001003: IPv4 based SBTS Management Plane... 118 Benefits.......................................................................................118 Requirements............................................................................. 118 Functional description.................................................................118 System impact............................................................................ 119 SR001003: IPv4 based SBTS Management Plane management data.............................................................................................119 Sales information....................................................................... 120 SR000589: IPv4/IPv6 Transport Stack.......................................120 Description of SR000589: IPv4/IPv6 Transport Stack................120 Benefits...................................................................................... 120 Requirements.............................................................................120 Functional description................................................................ 121 System impact............................................................................122 SR000589: IPv4/IPv6 Transport Stack management data.........122 Sales information....................................................................... 126 SR000361: Link Supervision with BFD...................................... 126 Description of SR000361: Link Supervision with BFD............... 126 Benefits...................................................................................... 126 Requirements.............................................................................127 Functional description................................................................ 127 System impact............................................................................128 SR000361: Link Supervision with BFD management data........ 128 Sales information....................................................................... 129 SR000465: Local and Remote IP Traffic Capturing................... 130 Description of SR000465: Local and Remote IP Traffic Capturing.. 130 Benefits...................................................................................... 130 Requirements.............................................................................130 Functional description................................................................ 130 System impact............................................................................132
DN09218825
7
SRAN 16.2, Feature Descriptions
3.23.1.5 3.23.1.6 3.24 3.24.1 3.24.1.1 3.24.1.2 3.24.1.3 3.24.1.4 3.24.1.5 3.24.1.6 3.25 3.25.1 3.25.1.1 3.25.1.2 3.25.1.3 3.25.1.4 3.25.1.5 3.25.1.6 3.26 3.26.1 3.26.1.1 3.26.1.2 3.26.1.3 3.26.1.4 3.26.1.5 3.26.1.6 3.27 3.27.1 3.27.1.1 3.27.1.2 3.27.1.3 3.27.1.4 3.27.1.5 3.27.1.6 3.28 3.28.1 3.28.1.1 3.28.1.2 3.28.1.3 3.28.1.4 3.28.1.5 3.28.1.6 3.29 3.29.1
8
SR000465: Local and Remote IP Traffic Capturing management data............................................................................................ 132 Sales information....................................................................... 133 SR000770: LTE Dual U-plane IP addresses.............................. 133 Description of SR000770: LTE Dual U-plane IP addresses....... 133 Benefits...................................................................................... 133 Requirements.............................................................................133 Functional description................................................................ 133 System impact............................................................................135 SR000770: LTE Dual U-plane IP addresses management data...... 135 Sales information....................................................................... 136 SR000176: ML-PPP termination................................................ 136 Description of SR000176: ML-PPP termination......................... 136 Benefits...................................................................................... 136 Requirements.............................................................................137 Functional description................................................................ 137 System impact............................................................................138 SR000176: ML-PPP termination management data.................. 138 Sales information....................................................................... 143 SR000382: Multiple VLAN interfaces.........................................143 Description of SR000382: Multiple VLAN interfaces..................143 Benefits...................................................................................... 143 Requirements.............................................................................143 Functional description................................................................ 144 System impact............................................................................144 SR000382: Multiple VLAN interfaces management data...........145 Sales information....................................................................... 146 SR000386: QoS Aware Ethernet Switching............................... 146 Description of SR000386: QoS Aware Ethernet Switching........ 146 Benefits...................................................................................... 146 Requirements.............................................................................147 Functional description................................................................ 147 System impact............................................................................148 SR000386: QoS Aware Ethernet Switching management data. 149 Sales information....................................................................... 151 SR000954: SBTS Common Transport....................................... 151 Description of SR000954: SBTS Common Transport................ 151 Benefits...................................................................................... 151 Requirements.............................................................................151 Functional description................................................................ 152 System impact............................................................................153 SR000954: SBTS Common Transport management data......... 154 Sales information....................................................................... 154 SR001103: SBTS Flexible Sync Input Priority............................154 Description of SR001103: SBTS Flexible Sync Input Priority.....154
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.29.1.1 3.29.1.2 3.29.1.3 3.29.1.4 3.29.1.5 3.29.1.6 3.30 3.30.1 3.30.1.1 3.30.1.2 3.30.1.3 3.30.1.4 3.30.1.5 3.30.1.6 3.31 3.31.1 3.31.1.1 3.31.1.2 3.31.1.3 3.31.1.4 3.31.1.5 3.31.1.6 3.32 3.32.1 3.32.1.1 3.32.1.2 3.32.1.3 3.32.1.4 3.32.1.5 3.32.1.6 3.33 3.33.1 3.33.1.1 3.33.1.2 3.33.1.3 3.33.1.4 3.33.1.5 3.33.1.6 3.34 3.34.1 3.34.1.1
Issue: 01E
Benefits...................................................................................... 155 Requirements.............................................................................155 Functional description................................................................ 155 System impact............................................................................155 SR001103: SBTS Flexible Sync Input Priority management data... 155 Sales information....................................................................... 156 SR000367: Small Form Factor Pluggable Slot (SFP slot)......... 157 Description of SR000367: Small Form Factor Pluggable Slot (SFP slot)............................................................................................ 157 Benefits...................................................................................... 157 Requirements.............................................................................157 Functional description................................................................ 157 System impact............................................................................158 SR000367: Small Form Factor Plugable Slot (SFP slot) management data...................................................................... 158 Sales information....................................................................... 159 SR000403: Source based routing in BTS.................................. 159 Description of SR000403: Source based routing in BTS........... 159 Benefits...................................................................................... 159 Requirements.............................................................................159 Functional description................................................................ 160 System impact............................................................................161 SR000403: Source based routing in BTS management data.... 162 Sales information....................................................................... 162 SR000357: Symmetrical E1 Interface........................................ 162 Description of SR000357: Symmetrical E1 Interface................. 162 Benefits...................................................................................... 163 Requirements.............................................................................163 Functional description................................................................ 163 System impact............................................................................164 SR000357: Symmetrical E1 Interface management data.......... 164 Sales information....................................................................... 166 SR000376: Synchronization from 2.048MHz signal...................166 Description of SR000376: Synchronization from 2.048MHz signal.. 166 Benefits...................................................................................... 166 Requirements.............................................................................166 Functional description................................................................ 167 System impact............................................................................167 SR000376: Synchronization from 2.048MHz signal management data............................................................................................ 167 Sales information....................................................................... 168 SR000377: Synchronization from PDH interface....................... 168 Description of SR000377: Synchronization from PDH interface...... 168 Benefits...................................................................................... 168
DN09218825
9
SRAN 16.2, Feature Descriptions
3.34.1.2 3.34.1.3 3.34.1.4 3.34.1.5 3.34.1.6 3.35 3.35.1 3.35.1.1 3.35.1.2 3.35.1.3 3.35.1.4 3.35.1.5 3.35.1.6 3.36 3.36.1 3.36.1.1 3.36.1.2 3.36.1.3 3.36.1.4 3.36.1.5 3.36.1.6 3.37 3.37.1 3.37.1.1 3.37.1.2 3.37.1.3 3.37.1.4 3.37.1.5 3.37.1.6 3.38 3.38.1 3.38.1.1 3.38.1.2 3.38.1.3 3.38.1.4 3.38.1.5 3.38.1.6 3.39 3.39.1 3.39.1.1 3.39.1.2 3.39.1.3 3.39.1.4
10
Requirements.............................................................................168 Functional description................................................................ 169 System impact............................................................................169 SR000377: Synchronization from PDH interface management data............................................................................................ 169 Sales information....................................................................... 170 SR001041: Synchronization Holdover Support..........................170 Description of SR001041: Synchronization Holdover Support...170 Benefits...................................................................................... 170 Requirements.............................................................................171 Functional description................................................................ 171 System impact............................................................................171 SR001041: Synchronization Holdover Support management data.. 172 Sales information....................................................................... 172 SR000385: Synchronization Hub............................................... 173 Description of SR000385: Synchronization Hub........................ 173 Benefits...................................................................................... 173 Requirements.............................................................................173 Functional description................................................................ 173 System impact............................................................................176 SR000385: Synchronization Hub management data................. 177 Sales information....................................................................... 177 SR000375: Synchronous Ethernet.............................................178 Description of SR000375: Synchronous Ethernet......................178 Benefits...................................................................................... 178 Requirements.............................................................................178 Functional description................................................................ 178 System impact............................................................................179 SR000375: Synchronous Ethernet management data...............180 Sales information....................................................................... 181 SR000650: TDM fallback for GSM Application.......................... 181 Description of SR000650: TDM fallback for GSM Application... 181 Benefits...................................................................................... 181 Requirements.............................................................................181 Functional description................................................................ 181 System impact............................................................................183 SR000650: TDM fallback for GSM Application management data.. 184 Sales information....................................................................... 185 SR000384: Timing over Packet Resilience................................ 185 Description of SR000384: Timing over Packet Resilience......... 185 Benefits...................................................................................... 185 Requirements.............................................................................185 Functional description................................................................ 185 System impact............................................................................188
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.39.1.5 3.39.1.6 3.40 3.40.1
3.41.1.6
SR000384: Timing over Packet Resilience management data.. 189 Sales information....................................................................... 190 SR000374: Timing over Packet with Frequency Sync............... 190 Description of SR000374: Timing over Packet with Frequency Sync........................................................................................... 190 Benefits...................................................................................... 190 Requirements.............................................................................191 Functional description................................................................ 191 System impact............................................................................192 SR000374: Timing over Packet with Frequency Sync management data...................................................................... 193 Sales information....................................................................... 195 SR000383: Timing over Packet with phase synchronization..... 195 Description of SR000383: Timing over Packet with phase synchronization.......................................................................... 195 Benefits...................................................................................... 195 Requirements.............................................................................195 Functional description................................................................ 195 System impact............................................................................198 SR000383: Timing over Packet with phase synchronization management data...................................................................... 199 Sales information....................................................................... 200
4 4.1
Descriptions of operability features............................................ 201 SR000832: Flexi BTS and its Transport Parameter Categorization . 201 Description of SR000832: Flexi BTS and its Transport Parameter Categorization ........................................................................... 201 Benefits...................................................................................... 201 Requirements.............................................................................201 Functional description................................................................ 201 System impact............................................................................202 SR000832: Flexi BTS and its Transport Parameter Categorization management data...................................................................... 202 Sales information....................................................................... 202 SR001453: Offline SCF Conversion from Three Dedicated RATs to SRAN..................................................................................... 203 Description of SR001453: Offline SCF Conversion from Three Dedicated RATs to SRAN...........................................................203 Benefits...................................................................................... 203 Requirements.............................................................................203 Functional description................................................................ 203 System impact............................................................................205 SR001453: Offline SCF Conversion from Three Dedicated RATs to SRAN management data....................................................... 205 Sales information....................................................................... 206 SR000989: SBTS - Minimizing Drive Tests (MDT).....................206
3.40.1.1 3.40.1.2 3.40.1.3 3.40.1.4 3.40.1.5 3.40.1.6 3.41 3.41.1 3.41.1.1 3.41.1.2 3.41.1.3 3.41.1.4 3.41.1.5
4.1.1 4.1.1.1 4.1.1.2 4.1.1.3 4.1.1.4 4.1.1.5 4.1.1.6 4.2 4.2.1 4.2.1.1 4.2.1.2 4.2.1.3 4.2.1.4 4.2.1.5 4.2.1.6 4.3
Issue: 01E
DN09218825
11
SRAN 16.2, Feature Descriptions
4.3.1 4.3.1.1 4.3.1.2 4.3.1.3 4.3.1.4 4.3.1.5 4.3.1.6 4.4 4.4.1 4.4.1.1 4.4.1.2 4.4.1.3 4.4.1.4 4.4.1.5 4.4.1.6 4.4.2 4.4.3 4.5 4.5.1 4.5.1.1 4.5.1.2 4.5.1.3 4.5.1.4 4.5.1.5 4.5.1.6 4.6 4.6.1 4.6.1.1 4.6.1.2 4.6.1.3 4.6.1.4 4.6.1.5 4.6.1.6 4.7 4.7.1 4.7.1.1 4.7.1.2 4.7.1.3 4.7.1.4 4.7.1.5 4.7.1.6
12
Description of SR000989: SBTS - Minimizing Drive Tests (MDT).... 206 Benefits...................................................................................... 206 Requirements.............................................................................206 Functional description................................................................ 206 System impact............................................................................207 SR000989: SBTS - Minimizing Drive Tests (MDT) management data............................................................................................ 207 Sales information....................................................................... 208 SR000910: SBTS Antenna Line Management...........................208 Description of SR000910: SBTS Antenna Line Management....208 Benefits...................................................................................... 208 Requirements.............................................................................208 Functional description................................................................ 209 System impact............................................................................209 SR000910: SBTS Antenna Line Management management data... 209 Sales information........................................................................211 SRAN supported MHAs..............................................................211 SRAN supported RETs...............................................................213 SR000918: SBTS Basic Performance Management................. 214 Description of SR000918: SBTS Basic Performance Management ................................................................................................... 214 Benefits...................................................................................... 214 Requirements.............................................................................214 Functional description................................................................ 214 System impact............................................................................217 SR000918: SBTS Basic Performance Management management data............................................................................................ 217 Sales information....................................................................... 219 SR001005: SBTS Channel bandwidth RTU...............................219 Description of SR001005: SBTS Channel bandwidth RTU........219 Benefits...................................................................................... 220 Requirements.............................................................................220 Functional description................................................................ 220 System impact............................................................................220 SR001005: SBTS Channel bandwidth RTU management data.221 Sales information....................................................................... 221 SR001185: SBTS Composer UI................................................. 222 Description of SR001185: SBTS Composer UI.......................... 222 Benefits...................................................................................... 222 Requirements.............................................................................222 Functional description................................................................ 222 System impact............................................................................227 SR001185: SBTS Composer UI management data................... 227 Sales information....................................................................... 227
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.8 4.8.1 4.8.1.1 4.8.1.2 4.8.1.3 4.8.1.4 4.9 4.9.1 4.9.1.1 4.9.1.2 4.9.1.3 4.9.1.4 4.9.1.5 4.9.1.6 4.10 4.10.1 4.10.1.1 4.10.1.2 4.10.1.3 4.10.1.4 4.10.1.5 4.10.1.6 4.11 4.11.1 4.11.1.1 4.11.1.2 4.11.1.3 4.11.1.4 4.11.1.5 4.11.1.6 4.12 4.12.1 4.12.1.1 4.12.1.2 4.12.1.3 4.12.1.4 4.12.1.5 4.12.1.6 4.13 4.13.1 4.13.1.1 4.13.1.2 4.13.1.3
Issue: 01E
SR001118: SBTS Configuration File Conversion from WCDMA or LTE............................................................................................. 228 Description of SR001118: SBTS Configuration File Conversion from WCDMA or LTE..................................................................228 SR001118 benefits..................................................................... 228 SR001118 functional description................................................ 228 SR001118 system impact...........................................................228 SR001118 reference data...........................................................229 SR000929: SBTS Configuration Management.......................... 230 Description of SR000929: SBTS Configuration Management .. 230 Benefits...................................................................................... 230 Requirements.............................................................................230 Functional description................................................................ 230 System impact............................................................................231 SR000929: SBTS Configuration Management management data.. 232 Sales information....................................................................... 233 SR000930: SBTS Configuration Validation................................ 233 Description of SR000930: SBTS Configuration Validation ........ 233 Benefits...................................................................................... 233 Requirements.............................................................................233 Functional description................................................................ 234 System impact............................................................................236 SR000930: SBTS Configuration Validation management data.. 236 Sales information....................................................................... 237 SR000908: SBTS Crypto Agent.................................................237 Description of SR000908: SBTS Crypto Agent..........................237 Benefits...................................................................................... 237 Requirements.............................................................................237 Functional description................................................................ 237 System impact............................................................................238 SR000908: SBTS Crypto Agent management data...................239 Sales information....................................................................... 239 SR001004: SBTS Data User RTU............................................. 239 Description of SR001004: SBTS Data User RTU...................... 239 Benefits...................................................................................... 240 Requirements.............................................................................240 Functional description................................................................ 240 System impact............................................................................240 SR001004: SBTS Data User RTU management data............... 241 Sales information....................................................................... 242 SR000940: SBTS Diagnostics and Self Test............................. 242 Description of SR000940: SBTS Diagnostics and Self Test...... 242 Benefits...................................................................................... 242 Requirements.............................................................................242 Functional description................................................................ 243
DN09218825
13
SRAN 16.2, Feature Descriptions
4.13.1.4 4.13.1.5 4.13.1.6 4.14 4.14.1 4.14.1.1 4.14.1.2 4.14.1.3 4.14.1.4 4.14.1.5 4.14.1.6 4.15 4.15.1 4.15.1.1 4.15.1.2 4.15.1.3 4.15.1.4 4.15.1.5 4.15.1.6 4.16 4.16.1 4.16.1.1 4.16.1.2 4.16.1.3 4.16.1.4 4.16.1.5 4.16.1.6 4.17 4.17.1 4.17.1.1 4.17.1.2 4.17.1.3 4.17.1.4 4.17.1.5 4.17.1.6 4.18 4.18.1 4.18.1.1 4.18.1.2 4.18.1.3 4.18.1.4 4.18.1.5 4.18.1.6 4.19
14
System impact............................................................................243 SR000940: SBTS Diagnostics and Self Test management data..... 243 Sales information....................................................................... 244 SR000904: SBTS DNS Support.................................................244 Description of SR000904: SBTS DNS Support .........................244 Benefits...................................................................................... 244 Requirements.............................................................................245 Functional description................................................................ 245 System impact............................................................................245 SR000904: SBTS DNS Support management data...................246 Sales information....................................................................... 246 SR000959: SBTS Energy saving............................................... 246 Description of SR000959: SBTS Energy saving........................ 246 Benefits...................................................................................... 246 Requirements.............................................................................247 Functional description................................................................ 247 System impact............................................................................248 SR000959: SBTS Energy saving management data................. 248 Sales information....................................................................... 248 SR000920: SBTS Fault Management........................................249 Description of SR000920: SBTS Fault Management.................249 Benefits...................................................................................... 249 Requirements.............................................................................249 Functional description................................................................ 249 System impact............................................................................250 SR000920: SBTS Fault Management management data..........250 Sales information....................................................................... 252 SR000911: SBTS HW Management.......................................... 252 Description of SR000911: SBTS HW Management................... 252 Benefits...................................................................................... 252 Requirements.............................................................................252 Functional description................................................................ 252 System impact............................................................................253 SR000911: SBTS HW Management management data............ 253 Sales information....................................................................... 255 SR001015: SBTS Incremental Power RTU................................255 Description of SR001015: SBTS Incremental Power RTU.........255 Benefits...................................................................................... 255 Requirements.............................................................................255 Functional description................................................................ 256 System impact............................................................................256 SR001015: SBTS Incremental Power RTU management data. 257 Sales information....................................................................... 257 SR001057: SBTS inheritance of Network Resiliency for mcBSC.... 258
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.19.1 4.19.1.1 4.19.1.2 4.19.1.3 4.19.1.4 4.19.1.5 4.19.1.6 4.20 4.20.1 4.20.1.1 4.20.1.2 4.20.1.3 4.20.1.4 4.20.1.5 4.20.1.6 4.21 4.21.1 4.21.1.1 4.21.1.2 4.21.1.3 4.21.1.4 4.21.1.5 4.21.1.6 4.22 4.22.1 4.22.1.1 4.22.1.2 4.22.1.3 4.22.1.4 4.22.1.5 4.22.1.6 4.23 4.23.1 4.23.1.1 4.23.1.2 4.23.1.3 4.23.1.4 4.23.1.5 4.23.1.6 4.24 4.24.1
Issue: 01E
Description of SR001057: SBTS inheritance of Network Resiliency for mcBSC.................................................................................. 258 Benefits...................................................................................... 258 Requirements.............................................................................258 Functional description................................................................ 258 System impact............................................................................259 SR001057: SBTS inheritance of Network Resiliency for mcBSC management data...................................................................... 260 Sales information....................................................................... 260 SR000924: SBTS Intelligent shut down..................................... 260 Description of SR000924: SBTS Intelligent shut down.............. 260 Benefits...................................................................................... 261 Requirements.............................................................................261 Functional description................................................................ 261 System impact............................................................................261 SR000924: SBTS Intelligent shut down management data....... 262 Sales information....................................................................... 263 SR000937: SBTS LTE trace.......................................................263 Description of SR000937: SBTS LTE Trace.............................. 263 Benefits...................................................................................... 263 Requirements.............................................................................263 Functional description................................................................ 263 System impact............................................................................264 SR000937: SBTS LTE Trace management data....................... 264 Sales information....................................................................... 266 SR000942: SBTS Manual Commissioning and system setup... 266 Description of SR000942: SBTS Manual Commissioning and system setup.............................................................................. 266 Benefits...................................................................................... 266 Requirements.............................................................................266 Functional description................................................................ 266 System impact............................................................................267 SR000942: SBTS Manual Commissioning and system setup management data...................................................................... 268 Sales information....................................................................... 268 SR000921: SBTS NE3S WS NetAct integration........................ 268 Description of SR000921: SBTS NE3S WS NetAct integration. 268 Benefits...................................................................................... 268 Requirements.............................................................................269 Functional description................................................................ 269 System impact............................................................................270 SR000921: SBTS NE3S WS NetAct integration management data ................................................................................................... 270 Sales information....................................................................... 271 SR000906: SBTS Nokia Service Account Management............271 Description of SR000906: SBTS Nokia Service Account Management.............................................................................. 271
DN09218825
15
SRAN 16.2, Feature Descriptions
4.24.1.1 4.24.1.2 4.24.1.3 4.24.1.4 4.24.1.5 4.24.1.6 4.25 4.25.1 4.25.1.1 4.25.1.2 4.25.1.3 4.25.1.4 4.25.1.5 4.25.1.6 4.26 4.26.1 4.26.1.1 4.26.1.2 4.26.1.3 4.26.1.4 4.26.1.5 4.26.1.6 4.27 4.27.1 4.27.1.1 4.27.1.2 4.27.1.3 4.27.1.4 4.27.1.5 4.27.1.6 4.28 4.28.1 4.28.1.1 4.28.1.2 4.28.1.3 4.28.1.4 4.28.1.5 4.28.1.6
16
Benefits...................................................................................... 272 Requirements.............................................................................272 Functional description................................................................ 272 System impact............................................................................273 SR000906: SBTS Nokia Service Account Management management data...................................................................... 274 Sales information....................................................................... 275 SR000726: SBTS Object Model.................................................275 Description of SR000726: SBTS Object Model..........................275 Benefits...................................................................................... 275 Requirements.............................................................................275 Functional description................................................................ 275 System impact............................................................................276 SR000726: SBTS Object Model management data...................277 Sales information....................................................................... 277 SR000900: SBTS Operator Account Management....................277 Description of SR000900: SBTS Operator Account Management... 277 Benefits...................................................................................... 277 Requirements.............................................................................278 Functional description................................................................ 278 System impact............................................................................279 SR000900: SBTS Operator Account Management management data............................................................................................ 280 Sales information....................................................................... 280 SR000845: SBTS Operator Certificate Management................ 281 Description of SR000845: SBTS Operator Certificate Management.............................................................................. 281 Benefits...................................................................................... 281 Requirements.............................................................................281 Functional description................................................................ 281 System impact............................................................................283 SR000845: SBTS Operator Certificate Management management data............................................................................................ 284 Sales information....................................................................... 286 SR001244: SBTS PAoTDM for Flexi BSC with transport media converter.................................................................................... 286 Description of SR001244: SBTS PAoTDM for Flexi BSC with transport media converter.......................................................... 286 Benefits...................................................................................... 286 Requirements.............................................................................287 Functional description................................................................ 287 System impact............................................................................287 SR001244: SBTS PAoTDM for Flexi BSC with transport media converter management data...................................................... 288 Sales information....................................................................... 288
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.29 4.29.1 4.29.1.1 4.29.1.2 4.29.1.3 4.29.1.4 4.29.1.5 4.29.1.6 4.30 4.30.1 4.30.1.1 4.30.1.2 4.30.1.3 4.30.1.4 4.30.1.5 4.30.1.6 4.31 4.31.1 4.31.1.1 4.31.1.2 4.31.1.3 4.31.1.4 4.31.1.5 4.31.1.6 4.32 4.32.1 4.32.1.1 4.32.1.2 4.32.1.3 4.32.1.4 4.32.1.5 4.32.1.6 4.33 4.33.1 4.33.1.1 4.33.1.2 4.33.1.3 4.33.1.4 4.33.1.5 4.33.1.6 4.34 4.34.1
Issue: 01E
SR001027: SBTS PAoTDM for GSM dedicated mode with mcBSC ................................................................................................... 288 Description of SR001027: SBTS PAoTDM for GSM dedicated mode with mcBSC......................................................................288 Benefits...................................................................................... 289 Requirements.............................................................................289 Functional description................................................................ 289 System impact............................................................................289 SR001027: SBTS PAoTDM for GSM dedicated mode with mcBSC management data...................................................................... 290 Sales information....................................................................... 290 SR000928: SBTS Plug and Play................................................290 Description of SR000928: SBTS Plug and Play.........................290 Benefits...................................................................................... 290 Requirements.............................................................................291 Functional description................................................................ 291 System impact............................................................................293 SR000928: SBTS Plug and Play management data..................293 Sales information....................................................................... 293 SR001000: SBTS RF Sharing RTU........................................... 294 Description of SR001000: SBTS RF Sharing RTU.................... 294 Benefits...................................................................................... 294 Requirements.............................................................................294 Functional description................................................................ 294 System impact............................................................................295 SR001000 - SBTS RF Sharing RTU management data............ 296 Sales information....................................................................... 296 SR000907: SBTS Security for Local Management Ports...........296 Description of SR000907: SBTS Security for Local Management Ports...........................................................................................296 Benefits...................................................................................... 296 Requirements.............................................................................297 Functional description................................................................ 297 System impact............................................................................298 SR000907: SBTS Security for Local Management Ports management data...................................................................... 298 Sales information....................................................................... 298 SR000913: SBTS Signed SW....................................................299 Description of SR000913: SBTS Signed SW.............................299 Benefits...................................................................................... 299 Requirements.............................................................................299 Functional description................................................................ 299 System impact............................................................................301 SR000913: SBTS Signed SW management data......................301 Sales information....................................................................... 302 SR000902: SBTS sRIO Link Layer Security.............................. 302 Description of SR000902: SBTS sRIO Link Layer Security....... 302
DN09218825
17
SRAN 16.2, Feature Descriptions
4.34.1.1 4.34.1.2 4.34.1.3 4.34.1.4 4.34.1.5 4.34.1.6 4.35 4.35.1 4.35.1.1 4.35.1.2 4.35.1.3 4.35.1.4 4.35.1.5 4.35.1.6 4.36 4.36.1 4.36.1.1 4.36.1.2 4.36.1.3 4.36.1.4 4.36.1.5 4.36.1.6 4.37 4.37.1 4.37.1.1 4.37.1.2 4.37.1.3 4.37.1.4 4.37.1.5 4.37.1.6 4.38 4.38.1 4.38.1.1 4.38.1.2 4.38.1.3 4.38.1.4 4.38.1.5 4.38.1.6 4.39 4.39.1 4.39.1.1 4.39.1.2 4.39.1.3 4.39.1.4
18
Benefits...................................................................................... 302 Requirements ............................................................................302 Functional description................................................................ 302 System impact............................................................................303 SR000902: SBTS sRIO Link Layer Security management data...... 304 Sales information....................................................................... 305 SR000794: SBTS SW License Management.............................305 Description of SR000794: SBTS SW License Management......305 Benefits...................................................................................... 305 Requirements.............................................................................305 Functional description................................................................ 305 System impact............................................................................307 SR000794: SBTS SW License Management management data..... 307 Sales information....................................................................... 308 SR000912: SBTS SW Management.......................................... 308 Description of SR000912: SBTS SW Management................... 308 Benefits...................................................................................... 308 Requirements.............................................................................308 Functional description................................................................ 309 System impact............................................................................310 SR000912: SBTS SW Management management data............ 310 Sales information........................................................................311 SR000938: SBTS SW upgrade/update...................................... 311 Description of SR000938: SBTS SW upgrade/update .............. 311 Benefits.......................................................................................311 Requirements............................................................................. 311 Functional description................................................................ 312 System impact............................................................................312 SR000938: SBTS SW upgrade/update management data........312 Sales information....................................................................... 313 SR000909: SBTS Trusted Boot................................................. 313 Description of SR000909: SBTS Trusted Boot.......................... 313 Benefits...................................................................................... 313 Requirements.............................................................................313 Functional description................................................................ 313 System impact............................................................................315 SR000909: SBTS Trusted Boot management data................... 315 Sales information....................................................................... 316 SR000903: SBTS User Event Logging...................................... 316 Description of SR000903: SBTS User Event Logging............... 316 Benefits...................................................................................... 316 Requirements ............................................................................316 Functional description................................................................ 317 System impact............................................................................318
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.39.1.5 4.39.1.6 4.40 4.40.1
4.42.1.6 4.43 4.43.1 4.43.1.1 4.43.1.2 4.43.1.3 4.43.1.4 4.43.1.5 4.43.1.6
SR000903: SBTS User Event Logging management data........ 318 Sales information....................................................................... 319 SR000846: SBTS Vendor Certificate Management................... 319 Description of SR000846: SBTS Vendor Certificate Management.. 319 Benefits...................................................................................... 319 Requirements.............................................................................319 Functional description................................................................ 319 System impact............................................................................321 SR000846: SBTS Vendor Certificate Management management data............................................................................................ 321 Sales information....................................................................... 322 SR000713: SBTS Web UI.......................................................... 322 Description of SR000713: SBTS Web UI................................... 322 Benefits...................................................................................... 322 Requirements.............................................................................322 Functional description................................................................ 322 System impact............................................................................325 SR000713: SBTS Web UI management data............................ 326 Sales information....................................................................... 326 Troubleshooting login issues in Internet Explorer...................... 327 SR000996: SRAN Clock Time Management............................. 331 Description of SR000996: SRAN Clock Time Management...... 331 Benefits...................................................................................... 332 Requirements.............................................................................332 Functional description................................................................ 332 System impact............................................................................332 SR000996: SRAN Clock Time Management management data..... 333 Sales information....................................................................... 333 SR000899: SRAN Support of TLS 1.2....................................... 333 Description of SR000899: SRAN Support of TLS 1.2................ 333 Benefits...................................................................................... 333 Requirements.............................................................................334 Functional description................................................................ 334 System impact............................................................................334 SR000899: SRAN Support of TLS 1.2 management data......... 335 Sales information....................................................................... 335
5 5.1
Descriptions of BTS site solution features................................. 336 SR001067: Adding Low Power RRH (2Tx/2Rx 4.0 RRH-family) to SBTS-configurations.................................................................. 336 Description of SR001067: Adding Low Power RRH (2Tx/2Rx 4.0 RRH-family) to SBTS configurations..........................................336 Benefits...................................................................................... 336 Requirements.............................................................................336 Functional description................................................................ 336
4.40.1.1 4.40.1.2 4.40.1.3 4.40.1.4 4.40.1.5 4.40.1.6 4.41 4.41.1 4.41.1.1 4.41.1.2 4.41.1.3 4.41.1.4 4.41.1.5 4.41.1.6 4.41.2 4.42 4.42.1 4.42.1.1 4.42.1.2 4.42.1.3 4.42.1.4 4.42.1.5
5.1.1 5.1.1.1 5.1.1.2 5.1.1.3
Issue: 01E
DN09218825
19
SRAN 16.2, Feature Descriptions
5.1.1.4 5.1.1.5 5.1.1.6 5.2 5.2.1 5.2.1.1 5.2.1.2 5.2.1.3 5.2.1.4 5.2.1.5 5.2.1.6 5.3 5.3.1 5.3.1.1 5.3.1.2 5.3.1.3 5.3.1.4 5.3.1.5 5.3.1.6 5.4 5.4.1 5.4.1.1 5.4.1.2 5.4.1.3 5.4.1.4 5.4.1.5 5.4.1.6 5.5 5.5.1 5.5.1.1 5.5.1.2 5.5.1.3 5.5.1.4 5.5.1.5 5.5.1.6 5.6
20
System impact............................................................................337 SR001067: Adding Low Power RRH (2Tx/2Rx 4.0 RRH-family) to SBTS-configurations management data.................................... 337 Sales information....................................................................... 338 SR001346: FXFA, FXFC, FXCA, FXCB radios support in SBTS..... 338 Description of SR001346: FXFA, FXFC, FXCA, FXCB radios support in SBTS......................................................................... 338 Benefits...................................................................................... 338 Requirements.............................................................................338 Functional description................................................................ 338 System impact............................................................................339 SR001346: FXFA, FXFC, FXCA, FXCB radios support in SBTS management data...................................................................... 339 Sales information....................................................................... 339 SR001347: High-capacity SBTS-installations............................ 339 Description of SR001347: High-capacity SBTS-installations..... 339 Benefits...................................................................................... 340 Requirements.............................................................................340 Functional description................................................................ 340 System impact............................................................................340 SR001347: High-capacity SBTS-installations management data.... 341 Sales information....................................................................... 341 SR000601: Initial SBTS Configurations for ETSI market with 6Gbps OBSAI radio units........................................................... 341 Description of SR000601: Initial SBTS Configurations for ETSI market with 6 Gbps OBSAI Radio units .................................... 341 Benefits...................................................................................... 341 Requirements.............................................................................342 Functional description................................................................ 342 System impact............................................................................343 SR000601: SBTS configurations with 6 Gbps OBSAI Radio units management data...................................................................... 343 Sales information....................................................................... 344 SR001268: Initial SBTS configurations for China market.......... 344 Description of SR001268: Initial SBTS configurations for China market........................................................................................ 344 Benefits...................................................................................... 344 Requirements.............................................................................344 Functional description................................................................ 344 System impact............................................................................345 SR001268: Initial SBTS configurations for China market management data...................................................................... 346 Sales information....................................................................... 346 SR001253: Initial SBTS-configurations with 2x FSMF System Modules......................................................................................346
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
5.6.1 5.6.1.1 5.6.1.2 5.6.1.3 5.6.1.4 5.6.1.5 5.6.1.6 5.7 5.7.1 5.7.1.1 5.7.1.2 5.7.1.3 5.7.1.4 5.7.1.5 5.7.1.6 5.8 5.8.1 5.8.1.1 5.8.1.2 5.8.1.3 5.8.1.4 5.8.1.5 5.8.1.6 5.9 5.9.1 5.9.1.1 5.9.1.2 5.9.1.3 5.9.1.4 5.9.1.5 5.9.1.6 5.10 5.10.1 5.10.1.1 5.10.1.2 5.10.1.3
Issue: 01E
Description of SR001253: Initial SBTS configurations with 2x FSMF System Modules..............................................................346 Benefits...................................................................................... 346 Requirements.............................................................................347 Functional description................................................................ 347 System impact............................................................................347 SR001253: Initial SBTS configurations with 2x FSMF System Modules management data........................................................348 Sales information....................................................................... 348 SR001356: New SBTS-profile for High-sector RRH-deployment.... 348 Description of SR001356: New SBTS-profile for High-sector RRHdeployment.................................................................................348 Benefits...................................................................................... 348 Requirements.............................................................................348 Functional description................................................................ 349 System impact............................................................................349 SR001356: New SBTS-profile for High-sector RRH-deployment Management Data......................................................................349 Sales information....................................................................... 350 SR000999: SBTS configurations with 3G OBSAI radios........... 350 Description of SR000999: SBTS configurations with 3 Gbps OBSAI radios............................................................................. 350 Benefits...................................................................................... 350 Requirements.............................................................................350 Functional description................................................................ 350 System impact............................................................................351 SR000999: SBTS configurations with 3 Gbps OBSAI radios management data...................................................................... 352 Sales information....................................................................... 352 SR001036: SBTS LTE-GSM and WCDMA-GSM configurations with 3GBps OBSAI radios.......................................................... 352 Description of SR001036: SBTS LTE-GSM and WCDMA-GSM configurations with 3GBps OBSAI radios...................................352 Benefits...................................................................................... 353 Requirements.............................................................................353 Functional description................................................................ 353 System impact............................................................................354 SR001036: SBTS LTE-GSM and WCDMA-GSM configurations with 3GBps OBSAI radios management data............................ 354 Sales information....................................................................... 355 SR001226: SBTS profiles for Indian customer and FXEE PIM avoidance configurations........................................................... 355 Description of SR001226: SBTS profiles for Indian customer and FXEE PIM avoidance configurations..........................................355 Benefits...................................................................................... 355 Requirements.............................................................................355 Functional description................................................................ 355
DN09218825
21
SRAN 16.2, Feature Descriptions
5.10.1.4 5.10.1.5 5.10.1.6 5.11 5.11.1 5.11.1.1 5.11.1.2 5.11.1.3 5.11.1.4 5.12 5.12.1 5.12.1.1 5.12.1.2 5.12.1.3 5.12.1.4 5.12.1.5 5.12.1.6 5.13 5.13.1 5.13.1.1 5.13.1.2 5.13.1.3 5.13.1.4 5.13.1.5 5.13.1.6
22
System impact............................................................................357 SR001226: SBTS profiles for Indian customer and FXEE PIM avoidance configurations........................................................... 357 Sales information....................................................................... 358 SR001167: SBTS support for FXEF Flexi RFM 3-pipe 1800 240W. 358 SR001167: SBTS support for FXEF Flexi RFM 3-pipe 1800 240W. 358 SR001167 benefits..................................................................... 358 SR001167 functional description................................................358 SR001167 system impact...........................................................359 SR001167 reference data.......................................................... 359 SR000972: SBTS System Module Sharing RTU....................... 360 Description of SR000972: SBTS System Module Sharing RTU...... 360 Benefits...................................................................................... 360 Requirements.............................................................................360 Functional description................................................................ 361 System impact............................................................................361 SR000972: SBTS System Module Sharing RTU management data............................................................................................ 362 Sales information....................................................................... 362 SR000944: Supported RF HW in SBTS.....................................363 Description of SR000944: Supported RF HW in SBTS..............363 Benefits...................................................................................... 363 Requirements.............................................................................363 Functional description................................................................ 363 System impact............................................................................365 SR000944: Supported RF HW in SBTS management data.......365 Sales information....................................................................... 366
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
List of Figures
Issue: 01E
Figure 1
Primary and secondary IPsec tunnels................................................ 54
Figure 2
Example configuration of hierarchical shaping mechanism................60
Figure 3
Example configuration of hierarchical shaping mechanism (extended view)................................................................................................... 62
Figure 4
Example of enqueuing outgoing traffic............................................... 63
Figure 5
Supported Ethernet interface configurations ..................................... 77
Figure 6
Ethernet termination........................................................................... 80
Figure 7
Single backhaul link network scenario................................................85
Figure 8
Dual backhaul link network scenario.................................................. 85
Figure 9
Flexible IP Addressing for PKI............................................................88
Figure 10
Example measurement configuration with SBTS in any RAT mode #1.. 91
Figure 11
Example measurement configuration with SBTS in any RAT mode #2.. 92
Figure 12
Example measurement configuration with SBTS in WCDMA mode #1. 93
Figure 13
Example measurement configuration with SBTS in WCDMA mode #2. 94
Figure 14
Example measurement configuration with SBTS in LTE mode.......... 95
Figure 15
Example measurement configuration with SBTS in any RAT mode #3.. 96
Figure 16
Traffic path depending on the SBTS mode.......................................100
Figure 17
IPv4/IPv6 Transport Stack................................................................ 122
Figure 18
Single-hop BFD session network scenario.......................................127
Figure 19
Traffic capturing mechanism.............................................................131
Figure 20
LTE Dual U-plane IP addresses overview........................................ 135
Figure 21
ML-PPP termination......................................................................... 138
Figure 22
Multiple VLAN interfaces.................................................................. 144
Figure 23
Scheduling and shaping of the aggregated traffic............................ 148
Figure 24
Example configuration with two U-plane addresses.........................161
Figure 25
Example of SBTS synchronization configuration #1.........................174
Figure 26
Example of SBTS synchronization configuration #2.........................175
Figure 27
Example of SBTS synchronization configuration #3.........................175
Figure 28
Example of SBTS synchronization configuration #4.........................176
Figure 29
TDM fallback mechanism................................................................. 182
Figure 30
ToP Master protection with Load Sharing.........................................188
Figure 31
PTP/UDP/IP with Unicast operation................................................. 197
Figure 32
PTP/Ethernet with Multicast operation............................................. 198
Figure 33
Offline conversion from three dedicated RATs to SBTS................... 204
Figure 34
Figure 1 SBTS – Minimizing Drive Test (MDT).................................207
DN09218825
23
SRAN 16.2, Feature Descriptions
24
Figure 35
SRAN Performance Management Architecture................................215
Figure 36
Parameters tab................................................................................. 222
Figure 37
Error during validation phase............................................................223
Figure 38
Toggling faults...................................................................................223
Figure 39
RET parameters............................................................................... 224
Figure 40
SBTS Composer UI main view......................................................... 225
Figure 41
SBTS Validation Architecture........................................................... 234
Figure 42
Crypto agent mechanism and secure file storage............................ 238
Figure 43
SRAN 16.2 DNS lookup process......................................................245
Figure 44
Radio connections in dedicated and RF-Sharing modes................. 247
Figure 45
SBTS inheritance of Network Resiliency for mcBSC........................259
Figure 46
SBTS commissioning overview........................................................ 267
Figure 47
NetAct and SBTS management architecture....................................269
Figure 48
Overview of interfaces used for configuring SBTS Nokia Service Account.............................................................................................273
Figure 49
SRAT and SRAN architecture comparison....................................... 276
Figure 50
Operator Account Management in SRAN provides a high level view of the SRAN architecture related to Operator Account Management...278
Figure 51
Multi-layered public key infrastructure (PKI) architecture................. 282
Figure 52
The SR001244 feature data flow architecture.................................. 287
Figure 53
SBTS Security for Local Management Ports.................................... 297
Figure 54
Nokia Software authentication process............................................ 300
Figure 55
Communication between secure environments................................303
Figure 56
SRAN 16.2 licensing mechanism principles concept....................... 306
Figure 57
SRAN 16.2 architecture concept...................................................... 309
Figure 58
Trusted Boot Agent order of boot execution..................................... 314
Figure 59
SBTS certificates.............................................................................. 320
Figure 60
SBTS Web UI in new architecture.................................................... 323
Figure 61
SBTS Element Manager example window....................................... 325
Figure 62
Entering the IP address.................................................................... 327
Figure 63
Internet options.................................................................................327
Figure 64
Trusted sites..................................................................................... 328
Figure 65
Sites button.......................................................................................329
Figure 66
Trusted sites..................................................................................... 330
Figure 67
Adding the IP to the list.....................................................................331
Figure 68
BTS profile: L4_1-2, LTE dedicated, 3 RRHs, I-type........................ 337
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
List of Tables
Issue: 01E
Table 1
New alarms.........................................................................................40
Table 2
New parameters................................................................................. 40
Table 3
Sales information................................................................................40
Table 4
New alarms.........................................................................................43
Table 5
New parameters................................................................................. 43
Table 6
Sales information................................................................................43
Table 7
New alarms.........................................................................................45
Table 8
New parameters................................................................................. 46
Table 9
Sales information................................................................................46
Table 10
New alarms.........................................................................................48
Table 11
New parameters................................................................................. 48
Table 12
Sales information................................................................................48
Table 13
New BTS faults...................................................................................51
Table 14
New parameters................................................................................. 52
Table 15
Sales information................................................................................52
Table 16
New alarms.........................................................................................55
Table 17
New parameters................................................................................. 55
Table 18
Sales information................................................................................56
Table 19
New counters......................................................................................58
Table 20
New parameters................................................................................. 58
Table 21
Sales information................................................................................59
Table 22
New counters......................................................................................64
Table 23
New parameters................................................................................. 69
Table 24
Sales information................................................................................70
Table 25
New alarms and faults........................................................................ 74
Table 26
New parameters................................................................................. 75
Table 27
Sales information................................................................................75
Table 28
New alarms.........................................................................................78
Table 29
New parameters................................................................................. 79
Table 30
Sales information................................................................................79
Table 31
New alarms and faults........................................................................ 81
Table 32
New counters......................................................................................81
Table 33
New parameters................................................................................. 82
Table 34
Sales information................................................................................83
Table 35
New parameters................................................................................. 86
Table 36
Sales information................................................................................87
Table 37
New parameters................................................................................. 89
Table 38
Sales information................................................................................89
DN09218825
25
SRAN 16.2, Feature Descriptions
26
Table 39
New alarms and faults........................................................................ 97
Table 40
New counters......................................................................................97
Table 41
New parameters................................................................................. 97
Table 42
Sales information................................................................................98
Table 43
New alarms.......................................................................................101
Table 44
New parameters............................................................................... 101
Table 45
Sales information..............................................................................101
Table 46
New alarms.......................................................................................104
Table 47
New counters....................................................................................105
Table 48
New parameters............................................................................... 105
Table 49
Sales information..............................................................................107
Table 50
New parameters............................................................................... 109
Table 51
Sales information.............................................................................. 110
Table 52
New parameters............................................................................... 113
Table 53
Sales information.............................................................................. 114
Table 54
New counters.................................................................................... 116
Table 55
New parameters............................................................................... 116
Table 56
Sales information.............................................................................. 118
Table 57
New parameters............................................................................... 120
Table 58
Sales information..............................................................................120
Table 59
New alarms and faults...................................................................... 123
Table 60
New counters....................................................................................123
Table 61
New parameters............................................................................... 124
Table 62
Sales information..............................................................................126
Table 63
New alarms.......................................................................................128
Table 64
New parameters............................................................................... 129
Table 65
Sales information..............................................................................129
Table 66
New alarms.......................................................................................132
Table 67
Sales information..............................................................................133
Table 68
New parameters............................................................................... 136
Table 69
Sales information..............................................................................136
Table 70
New alarms and faults...................................................................... 138
Table 71
New counters....................................................................................139
Table 72
New parameters............................................................................... 140
Table 73
Sales information..............................................................................143
Table 74
New counters....................................................................................145
Table 75
New parameters............................................................................... 146
Table 76
Sales information..............................................................................146
Table 77
New counters....................................................................................149
Table 78
New parameters............................................................................... 149
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Issue: 01E
Table 79
Sales information..............................................................................151
Table 80
New parameters............................................................................... 154
Table 81
Sales information..............................................................................154
Table 82
New alarms.......................................................................................156
Table 83
New BTS faults.................................................................................156
Table 84
New parameters............................................................................... 156
Table 85
Sales information..............................................................................156
Table 86
New alarms.......................................................................................158
Table 87
New parameters............................................................................... 159
Table 88
Sales information..............................................................................159
Table 89
New parameters............................................................................... 162
Table 90
Sales information..............................................................................162
Table 91
New alarms.......................................................................................164
Table 92
New counters....................................................................................165
Table 93
New parameters............................................................................... 165
Table 94
Sales information..............................................................................166
Table 95
New alarms and faults...................................................................... 167
Table 96
New parameters............................................................................... 168
Table 97
Sales information..............................................................................168
Table 98
New alarms and faults...................................................................... 169
Table 99
New parameters............................................................................... 170
Table 100
Sales information..............................................................................170
Table 101
New parameters............................................................................... 172
Table 102
Sales information..............................................................................172
Table 103
Synchronization inputs and outputs supported by SBTS................. 174
Table 104
New parameters............................................................................... 177
Table 105
Sales information..............................................................................177
Table 106
New alarms and faults...................................................................... 180
Table 107
New parameters............................................................................... 180
Table 108
Sales information..............................................................................181
Table 109
New parameters............................................................................... 184
Table 110
Sales information..............................................................................185
Table 111
Example configuration of Acceptance masters table........................188
Table 112
New alarms and faults...................................................................... 189
Table 113
New parameters............................................................................... 189
Table 114
Sales information..............................................................................190
Table 115
New alarms and faults...................................................................... 193
Table 116
New counters....................................................................................193
Table 117
New parameters............................................................................... 194
Table 118
Sales information..............................................................................195
DN09218825
27
SRAN 16.2, Feature Descriptions
28
Table 119
New alarms and faults...................................................................... 199
Table 120
New counters....................................................................................199
Table 121
New parameters............................................................................... 200
Table 122
Sales information..............................................................................200
Table 123
Sales information..............................................................................202
Table 124
Sales information..............................................................................206
Table 125
Sales information..............................................................................208
Table 126
BTS faults related to SR000910: SBTS Antenna Line Management..... 209
Table 127
Counters related to SR000910: SBTS Antenna Line Management....... 211
Table 128
Sales information.............................................................................. 211
Table 129
SRAN compatible MHA units............................................................ 211
Table 130
SRAN compatible legacy MHA units................................................ 212
Table 131
SRAN compatible RET units............................................................ 213
Table 132
SRAN compatible legacy RET units................................................. 213
Table 133
New parameters............................................................................... 218
Table 134
Sales information..............................................................................219
Table 135
New parameters............................................................................... 221
Table 136
Sales information..............................................................................221
Table 137
Sales information..............................................................................227
Table 138
SR001118 sales information............................................................. 230
Table 139
Related parameters.......................................................................... 232
Table 140
Sales information..............................................................................233
Table 141
Sales information..............................................................................237
Table 142
Sales information..............................................................................239
Table 143
Related existing counters................................................................. 241
Table 144
Related new counters.......................................................................241
Table 145
Sales information..............................................................................242
Table 146
New counters....................................................................................244
Table 147
Sales information..............................................................................244
Table 148
New parameters............................................................................... 246
Table 149
Sales information..............................................................................246
Table 150
Sales information..............................................................................248
Table 151
New alarms.......................................................................................251
Table 152
New parameters............................................................................... 251
Table 153
Sales information..............................................................................252
Table 154
New alarms and faults...................................................................... 254
Table 155
New parameters............................................................................... 254
Table 156
Sales information..............................................................................255
Table 157
New parameters............................................................................... 257
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Issue: 01E
Table 158
Sales information..............................................................................257
Table 159
New parameters............................................................................... 260
Table 160
Sales information..............................................................................260
Table 161
New Alarms...................................................................................... 262
Table 162
New BTS faults.................................................................................262
Table 163
New parameters............................................................................... 262
Table 164
Sales information..............................................................................263
Table 165
New parameters............................................................................... 265
Table 166
Sales information..............................................................................266
Table 167
Sales information..............................................................................268
Table 168
New parameters............................................................................... 271
Table 169
Sales information..............................................................................271
Table 170
New parameters............................................................................... 274
Table 171
Sales information..............................................................................275
Table 172
Sales information..............................................................................277
Table 173
New parameters............................................................................... 280
Table 174
Sales information..............................................................................280
Table 175
New BTS faults.................................................................................284
Table 176
New parameters............................................................................... 285
Table 177
Sales information..............................................................................286
Table 178
Related existing parameters.............................................................288
Table 179
Sales information..............................................................................288
Table 180
Sales information..............................................................................290
Table 181
Sales information..............................................................................293
Table 182
New parameters............................................................................... 296
Table 183
Sales information..............................................................................296
Table 184
New parameters............................................................................... 298
Table 185
Sales information..............................................................................298
Table 186
Sales information..............................................................................302
Table 187
New alarms.......................................................................................304
Table 188
New BTS faults.................................................................................304
Table 189
Sales information..............................................................................305
Table 190
New alarms.......................................................................................308
Table 191
Sales information..............................................................................308
Table 192
New parameters............................................................................... 311
Table 193
Sales information.............................................................................. 311
Table 194
Sales information..............................................................................313
Table 195
New alarms.......................................................................................315
Table 196
New faults.........................................................................................315
Table 197
Sales information..............................................................................316
DN09218825
29
SRAN 16.2, Feature Descriptions
30
Table 198
Sales information..............................................................................319
Table 199
Sales information..............................................................................322
Table 200
New parameters............................................................................... 326
Table 201
Sales information..............................................................................326
Table 202
New parameters............................................................................... 333
Table 203
Sales information..............................................................................333
Table 204
New parameters............................................................................... 335
Table 205
Sales information..............................................................................335
Table 206
Sales information..............................................................................338
Table 207
Sales information..............................................................................339
Table 208
Sales information..............................................................................341
Table 209
Sales information..............................................................................344
Table 210
Sales information..............................................................................346
Table 211
Sales information..............................................................................348
Table 212
Sales information..............................................................................350
Table 213
Related existing parameters.............................................................352
Table 214
Sales information..............................................................................352
Table 215
Sales information..............................................................................355
Table 216
Sales information..............................................................................358
Table 217
SR001167 sales information.............................................................360
Table 218
New parameters............................................................................... 362
Table 219
Sales information..............................................................................362
Table 220
Supported RF HW for SRAN16, 6 Gbps OBSAI.............................. 363
Table 221
Supported RF HW for SRAN16, 3 Gbps OBSAI.............................. 364
Table 222
Sales information..............................................................................366
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Summary of changes
Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues. Changes between issues 01D (2016-04-22, SRAN 16.2) and 01E (2016-06-16, SRAN 16.2) New features in Single RAN 16.2, Operating Documentation, Issue 03 There are no new features in Single RAN 16.2, Operating Documentation, Issue 03. Modified features in Single RAN 16.2, Operating Documentation, Issue 03 • • • • •
SR000713: SBTS Web UI SR001118: SBTS Configuration File Conversion from WCDMA or LTE SR001185: SBTS Composer UI SR001453: Offline SCF conversion from three dedicated RAT to SRAN SR000903: SBTS User Event Logging
Removed features in Single RAN 16.2, Operating Documentation, Issue 03 There are no removed features in Single RAN 16.2, Operating Documentation, Issue 03. Changes between issues 01C (2016-03-24, SRAN 16.2) and 01D (2016-04-22, SRAN 16.2) New features in Single RAN 16.2, Operating Documentation, Issue 02, Change Delivery 01 There are no new features in Single RAN 16.2, Operating Documentation, Issue 02, Change Delivery 01. Modified features in Single RAN 16.2, Operating Documentation, Issue 02, Change Delivery 01 • • •
SR000360: IP Transport Network Measurements SR000713: SBTS Web UI SR000924: SBTS Intelligent shut down
Removed features in Single RAN 16.2, Operating Documentation, Issue 02, Change Delivery 01 There are no removed features in Single RAN 16.2, Operating Documentation, Issue 02, Change Delivery 01. Changes between issues 01B (2015-12-16, SRAN 16.2) and 01C (2016-03-24, SRAN 16.2) New features in Single RAN 16.2, Operating Documentation, Issue 02 • • •
Issue: 01E
SR001167: SBTS Support for FXEF Flexi RFM 3-pipe 1800 240W SR001346: FXFA, FXFC, FXCA, FXCB radios support in SBTS SR001347: High-capacity SBTS-installations
DN09218825
31
Summary of changes
SRAN 16.2, Feature Descriptions
• •
SR001356: New SBTS-profile for high-sector RRH-deployment SR001453: Offline SCF conversion from three dedicated RAT to SRAN
Modified features in Single RAN 16.2, Operating Documentation, Issue 02 • • • • • •
SR000383: Timing over Packet with phase synchronization SR000385: Synchronization Hub SR000402: BTS QoS Support for Terminated and Routed Traffic SR001118: SBTS Configuration file conversion from WCDMA or LTE SR001185: SBTS Composer UI SR001244: SBTS PAoTDM for Flexi BSC with transport media converter
Removed features in Single RAN 16.2, Operating Documentation, Issue 02 There are no removed features in Single RAN 16.2, Operating Documentation, Issue 02.
32
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Introduction to SRAN 16.2 features
1 Introduction to SRAN 16.2 features This document is a part of Features section and provides feature descriptions for the SRAN 16.2 release. Note that the subchapter Interdependencies between features lists only the dependencies among Nokia Single RAN features. If a feature has no specific hardware requirements, it means that only Flexi Multiradio 10 System Module (FSMF) must be used.
g
Issue: 01E
Note: The Feature List for Single RAN and WCDMA/GSM/LTE-FDD Features Supported in Single RAN, and Activating and deactivating SRAN features with SBTS Element Manager documents are a part of the Features section.
DN09218825
33
Descriptions of radio resource management and telecom features
SRAN 16.2, Feature Descriptions
2 Descriptions of radio resource management and telecom features 2.1 SR001052: Feature parity with FDD-LTE 16 newly developed features 2.1.1 Description of SR001052: Feature parity with FDD-LTE 16 newly developed features Introduction to the feature This feature introduces parity between the SRAN 16.2 release and FDD-LTE 16 newlydeveloped features.
2.1.1.1
Benefits End-user benefits The SR001052: Feature parity with FDD-LTE 16 newly developed features feature combines the end-user benefits of FDD-LTE 16 newly developed features, for example higher throughput, better coverage, and shorter web browsing delays. Operator benefits The SR001052: Feature parity with FDD-LTE 16 newly developed features feature makes FDD-LTE 16 features available to the operator at the earliest possible time.
2.1.1.2
Requirements Hardware requirements This feature requires no new or additional hardware.
2.1.1.3
Functional description This feature introduces FDD-LTE 16 features to SRAN customers at the earliest possible time. The following FDD-LTE 16 features are inherited to SRAN 16.2: • • • • • • • • • • •
34
LTE44: 64 QAM in UL LTE915: S1 eNode B configuration update LTE1059: Uplink multi-cluster scheduling LTE1203: Load based Power Saving with Tx path switching off LTE1235: Optimization of PRACH/RACH power LTE1541: Advanced SCell measurement handling LTE1638: Inter-frequency RSTD measurement support LTE1709: Liquid Cell LTE1819: Data Session Profiling LTE1891: eNode B power saving - Micro DTX LTE1982: Additional PM-counters for MOCN-network sharing performance monitoring
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
• • • • • • • • • • • • • • • • •
Descriptions of radio resource management and telecom features
LTE1987: Downlink Adaptive Close Loop SU MIMO (4x4) LTE2026: RRC Signaling Robustness - downlink LTE2098: VoLTE uplink coverage boosting LTE2115: Dual transmission mode 1 operation LTE2162: SRVCC for network deployments not supporting PSHO LTE2167: Additional Carrier Aggregation band combinations 3CC - I LTE2200: Additional carrier aggregation band combinations – III LTE2205: Configurable uplink interference regions LTE2206: Extended RLF handling LTE2210: Intra-frequency load balancing extensions LTE2233: N-out-of-M downlink carrier aggregation LTE2275: PCell swap LTE2351: S1 based handover towards CSG cells LTE2390: MME Selection based upon only MMEC and PLMN ID LTE2446: PM counters for handover of VoLTE LTE2465: CSG cell support LTE2505: Access Class Barring skip
For information on the FDD-LTE 16 features, see the Single RAN, Rel. 16.2, Operating Documentation/Features/FDD-LTE16, Feature Descriptions and Instructions available in Nokia Networks Online Services (NOLS).
2.1.1.4
System impact System impact can be found in the relevant FDD-LTE 16 feature documentation. For more information, see the Single RAN, Rel. 16.2, Operating Documentation/Features/FDD-LTE16, Feature Descriptions and Instructions available in Nokia Networks Online Services (NOLS).
2.1.1.5
SR001052: Feature parity with FDD-LTE 16 newly developed features management data For information on related alarms, counters, key performance indicators, and parameters, see relevant FDD-LTE 16 feature documentation. For more information, see the Single RAN, Rel. 16.2, Operating Documentation/Features/FDD-LTE16, Feature Descriptions and Instructions available in Nokia Networks Online Services (NOLS).
2.1.1.6
Sales information Sales information can be found in the relevant FDD-LTE 16 feature documentation. For more information, see the Single RAN, Rel. 16.2, Operating Documentation/Features/FDD-LTE16, Feature Descriptions and Instructions available in Nokia Networks Online Services (NOLS).
2.2 SR001007: SBTS feature parity in SRAN 16.2 2.2.1 Description of SR001007: SBTS feature parity in SRAN 16.2 Introduction to the feature
Issue: 01E
DN09218825
35
Descriptions of radio resource management and telecom features
SRAN 16.2, Feature Descriptions
The SR001007: SBTS feature parity in SRAN 16.2 feature provides the foundation for feature parity with dedicated technologies, and enables the usage of these features in SBTS.
2.2.1.1
Benefits End-user benefits The SR001007: SBTS feature parity in SRAN 16.2 feature combines the end-user benefits of GSM/WCDMA/FDD-LTE features introduced by this feature. Operator benefits The SR001007: SBTS feature parity in SRAN 16.2 feature enables the usage of GSM/WCDMA/FDD-LTE features in one common solution – SBTS.
2.2.1.2
Requirements Hardware requirements This feature requires no new or additional hardware.
2.2.1.3
Functional description This feature introduces parity between the SRAN 16.2 release and new GSM 16, WCDMA 16, and FDD-LTE 16 features developed with these releases. SRAN 16.2 also supports features that were already available before GSM 16, WCDMA 16, FDD-LTE 16 releases, with a few exceptions. SRAN defines its own transport and operability feature set making some of the RAT specific features no longer applicable in SRAN (SBTS) mode. All SBTS configurations are separately defined and any exception to compatibility requirements is provided in the Single RAN, Rel. SRAN 16.2, Operating Documentation/Integrate and Configure document. For information on Single RAN 16.2 features and supported dedicated RAT features, see the Feature List for Single RAN and WCDMA/GSM/LTE-FDD Features Supported in Single RAN available in the Single RAN, Rel. SRAN 16.2, Operating Documentation/Features document.
2.2.1.4
System impact System impact information can be found in the relevant RAT feature documentation available in Nokia Networks Online Services Online (NOLS). For more information on the GSM 16, WCDMA 16, and FDD-LTE 16 RAT feature documentation, see the Single RAN, Rel. SRAN 16.2, Operating Documentation/Features document. For more information on the feature documentation before GSM 16, WCDMA 16, FDDLTE 16 releases, see the RAT Features from Previous Releases document available in Nokia Networks Online Services (NOLS).
36
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
2.2.1.5
Descriptions of radio resource management and telecom features
SR001007: SBTS feature parity in SRAN 16.2 management data For information on related alarms, counters, key performance indicators, and parameters, see the relevant RAT feature documentation available in Nokia Networks Online Services Online (NOLS). For more information on the GSM 16, WCDMA 16, and FDD-LTE 16 RAT feature documentation, see the Single RAN, Rel. SRAN 16.2, Operating Documentation/Features document. For more information on the feature documentation before GSM 16, WCDMA 16, FDDLTE 16 releases, see the RAT Features from Previous Releases document available in Nokia Networks Online Services (NOLS).
2.2.1.6
Sales information Sales information can be found in the relevant RAT feature documentation available in Nokia Networks Online Services Online (NOLS). For more information on the GSM 16, WCDMA 16, and FDD-LTE 16 RAT feature documentation, see the Single RAN, Rel. SRAN 16.2, Operating Documentation/Features document. For more information on the feature documentation before GSM 16, WCDMA 16, FDDLTE 16 releases, see the RAT Features from Previous Releases document available in Nokia Networks Online Services (NOLS).
Issue: 01E
DN09218825
37
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
3 Descriptions of transport and transmission features 3.1 SR000371: 1000Base-BX Optical GE Interface 3.1.1 Description of SR000371: 1000Base-BX Optical GE Interface Introduction to the feature This feature introduces a bidirectional, single-fiber 1000Base-BX optical Gigabit Ethernet (GE) interface.
3.1.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides a cost efficient, single-fiber 1000Base-BX optical GE interface. The interface is mainly designed for inter-cell site connectivity and last mile connectivity.
3.1.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF) or Flexi Multiradio BTS Transport Sub-Module FTIF.
3.1.1.3
Functional description This feature enables operation of the 1000Base-BX optical GE interface. The interface is provided by a transport small form factor pluggable transceiver module (SFP transceiver module) connected to an SFP slot of the SBTS. The 1000Base-BX optical GE interface operates over a single fiber (single-mode). This is achieved by using different wavelengths for signal transmission and reception. This interface type is divided into 2 subtypes: 1000Base-BX-D (downstream) and 1000BaseBX-U (upstream). Main properties of the 1000Base-BX optical GE interface: • • • • • • •
38
provided by a SFP transceiver module (compliant with INF-8074i standards) transmission distance of up to 10 km 1000Base-BX10-D transmits at 1490 nm wavelength and receives at 1310 nm wavelength 1000Base-BX10-U transmits at 1310 nm wavelength and receives at 1490 nm wavelength auto-negotiation supported full duplex transmission mode only (also advertised by the auto-negotiation function) designed for inter-cell site connectivity or last mile connectivity
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
•
g
Descriptions of transport and transmission features
ensured interoperability with other network elements Note: Non-standard 1000Base-BX GE interface variants support extended ranges (up to 120 km). These variants can use different wavelengths compared to the standard variant. As a result of this only 1000Base-BX transceivers of the same type are to be used.
Nokia recommends to use the following sales items for the provision of this feature: • •
473386A FOS1 SFP 1000Base-BX 10km, 1490nm/1310nm 473387A FOS2 SFP 1000Base-BX 10km, 1310nm/1490nm
Other SFP transceiver modules may also be used if they comply with the requirements listed below: • • • • • • •
g
SFP Multi-Sourcing Agreement (MSA) compliant laser class 1 compliant industrial temperature range: -40°C to +85°C provide extraction bail latch actuator be identified as 1000Base-BX type (SFP E²PROM Address A0h byte 6 = “40h”) LOS detection pin supported SFP modules with MSA direct actuator, with push type ring or without any extraction handle must not be used Note: Nokia does not guarantee proper operation for devices other than recommended.
By default only one Ethernet interface is supported. More interfaces can by activated by software license key.
3.1.1.4
System impact Interdependencies between features This feature requires the feature: •
SR000367: Small Form Factor Pluggable Slot (SFP slot)
Affected features: •
There are features that rely on the existence of an Ethernet interface. This feature is one of the available options for providing an Ethernet interface.
Exemplary features that require an Ethernet interface: • •
SR000350: Ethernet Termination SR000375: Synchronous Ethernet
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools If the inserted SFP does not comply with the requirements, an alarm (ID 61050) is raised and the laser is not switched on.
Issue: 01E
DN09218825
39
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Impact on system performance and capacity This feature provides 1000 Mbps bandwidth for the client feature SR000350: Ethernet Termination.
3.1.1.5
SR000371: 1000Base-BX Optical GE Interface management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 1: New alarms lists alarms introduced with this feature. Table 1
New alarms
Alarm ID 61029
Alarm name LOS on unit $U, interface $IF
BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 2: New parameters lists parameters introduced with this feature. Table 2
New parameters
Full name
3.1.1.6
Managed object
Label of the connector by the Ethernet link
connectorLabel
MOCx
Speed and duplex configuration
speedAndDuplex
ETHLK
Sales information Table 3
40
Abbreviated name
Sales information
BSW/ASW
License control in network element
BSW
-
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
3.2 SR000369: 1000Base-LX Optical GE Interface 3.2.1 Description of SR000369: 1000Base-LX Optical GE Interface Introduction to the feature This feature introduces a medium-haul 1000Base-LX optical Gigabit Ethernet (GE) interface.
3.2.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides a cost efficient medium-haul 1000Base-LX optical GE interface. The interface is mainly designed for inter-cell site connectivity and last mile connectivity.
3.2.1.2
Requirements Hardware requirements This feature requires to Flexi Multiradio 10 System Module (FSMF) or Flexi Multiradio BTS Transport Sub-Module FTIF.
3.2.1.3
Functional description This feature enables operation of the 1000Base-LX optical GE interface. The interface is provided by a transport small form factor pluggable transceiver module (SFP transceiver module) connected to a SFP slot of the SBTS. Main properties of the 1000Base-LX optical GE interface: • • • • • • • • •
provided by a SFP transceiver module (compliant with INF-8074i standards) compliance with IEEE 802.3-2012, clause 38.4 wavelength: 1310 nm (1270-1355 nm) transmission distance of at least 5000 m (with 10 µm single-mode fiber) transmission distance of at least 550 m (with 62,5 µm multi-mode fiber) auto-negotiation supported full duplex transmission mode only (also advertised by the auto-negotiation function) ensured interoperability with other network elements designed for inter-cell site connectivity or last mile connectivity
Nokia recommends to use the following sales item for the provision of this feature: 471880A FOSC Optical SFP 1000Base-LX 1310nm SM. Other SFP transceiver modules may also be used if they comply with the requirements listed below: • •
Issue: 01E
SFP Multi-Sourcing Agreement (MSA) compliant laser class 1 compliant
DN09218825
41
Descriptions of transport and transmission features
• • • • •
g
SRAN 16.2, Feature Descriptions
industrial temperature range: -40°C to +85°C provide extraction bail latch actuator be identified as 1000Base-LX type (SFP E²PROM Address A0h byte 6 = “02h”) LOS detection pin supported SFP modules with MSA direct actuator, with push type ring or without any extraction handle must not be used Note: Nokia does not guarantee proper operation for devices other than recommended.
By default only one Ethernet interface is supported. More interfaces can by activated by software license key.
3.2.1.4
System impact Interdependencies between features This feature requires the feature: •
SR000367: Small Form Factor Pluggable Slot (SFP slot)
Affected features: •
There are features that rely on the existence of an Ethernet interface. This feature is one of the available options for providing an Ethernet interface.
Exemplary features that require an Ethernet interface: • •
SR000350: Ethernet Termination SR000375: Synchronous Ethernet
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools If the inserted SFP does not comply with the requirements, an alarm (ID 61050) is raised and the laser is not switched on. Impact on system performance and capacity This feature provides 1000 Mbps bandwidth for the client feature SR000350: Ethernet Termination.
3.2.1.5
SR000369: 1000Base-LX Optical GE Interface management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 4: New alarms lists alarms introduced with this feature.
42
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 4
Descriptions of transport and transmission features
New alarms
Alarm ID 61029
Alarm name LOS on unit $U, interface $IF
Faults There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 5: New parameters lists parameters introduced with this feature. Table 5
New parameters
Full name
3.2.1.6
Abbreviated name
Managed object
Label of the connector by the Ethernet link
connectorLabel
MOCx
Speed and duplex configuration
speedAndDuplex
ETHLK
Sales information Table 6
Sales information
BSW/ASW
License control in network element
BSW
-
3.3 SR000368: 1000Base-SX Optical GE Interface 3.3.1 Description of SR000368: 1000Base-SX Optical GE Interface Introduction to the feature This feature introduces a short-haul 1000Base-SX optical Gigabit Ethernet (GE) interface.
3.3.1.1
Benefits End-user benefits
Issue: 01E
DN09218825
43
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
This feature does not affect the end-user experience. Operator benefits This feature provides a cost efficient short-haul 1000Base-SX optical GE interface. The interface is mainly designed for connectivity within the limits of a cell site.
3.3.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF) or Flexi Multiradio BTS Transport Sub-Module FTIF.
3.3.1.3
Functional description This feature enables operation of the 1000Base-SX optical GE interface. The interface is provided by a transport small form factor pluggable transceiver module (SFP transceiver module) connected to a SFP slot of the SBTS. Main properties of the 1000Base-SX optical GE interface: • • • • • • • •
provided by a SFP transceiver module (compliant with INF-8074i standards) compliance with IEEE 802.3-2012, clause 38.3 wavelength: 850 nm transmission distance of up to 220 m (with 62.5 µm multi-mode fiber) transmission distance of up to 500 m (with 50 µm multi-mode fiber) auto-negotiation supported full duplex transmission mode only (also advertised by the auto-negotiation function) ensured interoperability with other network elements
Nokia recommends to use the following sales item for the provision of this feature: 471881A FOSD Optical SFP 1000Base-SX 850nm MM. Other SFP transceiver modules may also be used if they comply with the requirements listed below: • • • • • • •
g
SFP Multi-Sourcing Agreement (MSA) compliant laser class 1 compliant industrial temperature range: -40°C to +85°C provide extraction bail latch actuator be identified as 1000Base-SX type (SFP E²PROM Address A0h byte 6 = “01h”) LOS detection pin supported SFP modules with MSA direct actuator, with push type ring or without any extraction handle must not be used Note: Nokia does not guarantee proper operation for devices other than recommended.
By default only one Ethernet interface is supported. More interfaces can by activated by software license key.
44
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.3.1.4
Descriptions of transport and transmission features
System impact Interdependencies between features This feature requires the feature: •
SR000367: Small Form Factor Pluggable Slot (SFP slot)
Affected features: •
There are features that rely on the existence of an Ethernet interface. This feature is one of the available options for providing an Ethernet interface.
Exemplary features that require an Ethernet interface: • •
SR000350: Ethernet Termination SR000375: Synchronous Ethernet
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools If the inserted SFP does not comply with the requirements, an alarm (ID 61050) is raised and the laser is not switched on. Impact on system performance and capacity This feature provides 1000 Mbps bandwidth for the client feature SR000350: Ethernet Termination.
3.3.1.5
SR000368: 1000Base-SX Optical GE Interface management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 7: New alarms lists alarms introduced with this feature. Table 7
New alarms
Alarm ID 61029
Alarm name LOS on unit $U, interface $IF
BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters
Issue: 01E
DN09218825
45
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Table 8: New parameters lists parameters introduced with this feature. Table 8
New parameters
Full name
3.3.1.6
Abbreviated name
Managed object
Label of the connector by the Ethernet link
connectorLabel
MOCx
Speed and duplex configuration
speedAndDuplex
ETHLK
Sales information Table 9
Sales information
BSW/ASW
License control in network element
BSW
-
3.4 SR000370: 1000Base-ZX Optical GE Interface 3.4.1 Description of SR000370: 1000Base-ZX Optical GE Interface Introduction to the feature This feature introduces a long-haul 1000Base-ZX optical Gigabit Ethernet (GE) interface.
3.4.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides an SBTS integrated cost efficient long-haul 1000Base-ZX optical GE interface. The interface is mainly designed for long distance inter-cell site connectivity in rural areas, railroad tracks or highways.
3.4.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF) or Flexi Multiradio BTS Transport Sub-Module FTIF.
3.4.1.3
Functional description This feature enables operation of the 1000Base-ZX optical GE interface. The interface is provided by a transport small form factor pluggable transceiver module (SFP transceiver module) connected to an SFP slot of the SBTS.
46
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Main properties of the 1000Base-ZX optical GE interface: • • • • • •
provided by an SFP transceiver module (compliant with INF-8074i standards) wavelength: 1550 nm transmission distance of up to 70 km (with 9 µm single-mode fiber) auto-negotiation supported full duplex transmission mode only (also advertised by the auto-negotiation function) designed for inter-cell site connectivity
SFP transceiver modules may be used to provision this feature if they comply with the requirements listed below: • • • • • • •
SFP Multi-Sourcing Agreement (MSA) compliant laser class 1 compliant industrial temperature range: -40°C to +85°C provide extraction bail latch actuator be identified as 1000Base-LX type (SFP E²PROM Address A0h byte 6 = “02h”) LOS detection pin supported SFP modules with MSA direct actuator, with push type ring or without any extraction handle must not be used
By default only one Ethernet interface is supported. More interfaces can by activated by software license key.
3.4.1.4
System impact Interdependencies between features This feature requires the feature: •
SR000367: Small Form Factor Pluggable Slot (SFP slot)
Affected features: •
There are features that rely on the existence of an Ethernet interface. This feature is one of the available options for providing an Ethernet interface.
Exemplary features that require an Ethernet interface: • •
SR000350: Ethernet Termination SR000375: Synchronous Ethernet
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools If the inserted SFP does not comply with the requirements, an alarm (ID 61050) is raised and the laser is not switched on. Impact on system performance and capacity This feature provides 1000 Mbps bandwidth for the client feature SR000350: Ethernet Termination.
Issue: 01E
DN09218825
47
Descriptions of transport and transmission features
3.4.1.5
SRAN 16.2, Feature Descriptions
SR000370: 1000Base-ZX Optical GE Interface management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 10: New alarms lists alarms introduced with this feature. Table 10
New alarms
Alarm ID 61029
Alarm name LOS on unit $U, interface $IF
BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 11: New parameters lists parameters introduced with this feature. Table 11
New parameters
Full name
3.4.1.6
Managed object
Label of the connector by the Ethernet link
connectorLabel
MOCx
Speed and duplex configuration
speedAndDuplex
ETHLK
Sales information Table 12
48
Abbreviated name
Sales information
BSW/ASW
License control in network element
BSW
-
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
3.5 SR000788: 1PPS&ToD Sync from External GNSS receiver 3.5.1 Description of SR000788: 1PPS&ToD Sync from External GNSS receiver Introduction to the feature This feature enables the SBTS to synchronize in frequency, phase, and time from an external Global Navigation Satellite System (GNSS) receiver.
3.5.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • •
3.5.1.2
synchronization can be provided to the SBTS in a remote area (for example an island) network level phase and time synchronization which is required for some LTE radio applications can be supported
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF) and the External GNSS receiver.
g 3.5.1.3
Note: SRAN16.2 system supports the following External GNSS receiver: GPS GLONASS Receiver Antenna (FYGB). The FYGB supports GPS and GLONASS systems.
Functional description The external GNSS receiver is a device that receives and digitally processes signals from a GNSS satellite constellation. Using information provided by the external GNSS receiver, SBTS recovers frequency, phase, and time synchronization with an accuracy required by the most demanding radio applications. An SBTS obtains the following information from a GNSS receiver: •
•
Issue: 01E
1PPS (one pulse per second) signal 1PPS output and data signals conform to the RS-422 standard. The GNSS receiver also reports time information related to each preceding 1PPS on a dedicated serial port and it can accept an external event input (command packet) and report time stamps in response to an event input signal. Time-of-Day (ToD)
DN09218825
49
Descriptions of transport and transmission features
• •
•
g
SRAN 16.2, Feature Descriptions
The provided ToD information is either GPS or UTC time. The UTC-GPS offset (leap seconds) is also provided to enable the SBTS to determine both UTC time and GPS time. GNSS coordinates: longitude, latitude and altitude values GNSS receiver identification information GNSS receiver can identify itself to the SBTS and, if necessary, report any inability to recover frequency, phase or time synchronization. additional information (for example quantization error) Note: The configuration of time zone cannot be derived through GNSS receiver and is done during site commissioning.
The SBTS can be configured in two modes: •
•
frequency synchronization mode In frequency synchronization mode the 1PPS signal is used to provide network level frequency synchronization. The ToD can be used to provide system time information for O&M (Operation and Management) purposes such as time stamp for messages, alarms, notifications and performance measurement files, trace records, and log files. phase synchronization mode In phase synchronization mode the 1PPS&ToD signal is used for network level phase synchronization and system frame number (SFN) alignment. The ToD together with the rising edge of the 1PPS pulse is used to calculate the accurate SFN value. The ToD is used also for system time information. The quantization error is used to reduce the effective amount of jitter on the PPS pulse.
The GNSS receiver operates under control of the SBTS and is connected directly to the Sync Input of the SBTS using a combined power and control cable. The maximum cable delay is 2000ns. The accurate total cable delay is to be configured. The cable length should not exceed 300m. The GNSS receiver requires signal from 1 satellite in case of frequency synchronization, and 4 satellites in case if additionally time and phase synchronization are needed.
3.5.1.4
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
50
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.5.1.5
Descriptions of transport and transmission features
SR000788: 1PPS&ToD Sync from External GNSS receiver management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms Table 13: New BTS faults lists BTS faults introduced with this feature. Table 13
Fault ID
g
New BTS faults
Fault name
Reported alarms
1898
PPS reference missing
7108 BASE STATION SYNCHRONIZATION PROBLEM
4011
GPS Receiver alarm: control interface not available
7108 BASE STATION SYNCHRONIZATION PROBLEM
4122
GPS receiver alarm: not 7108 BASE STATION SYNCHRONIZATION tracking satellites PROBLEM
4124
GPS receiver alarm: no stored position
7108 BASE STATION SYNCHRONIZATION PROBLEM
4123
GPS receiver alarm: survey in progress
7108 BASE STATION SYNCHRONIZATION PROBLEM
4125
GPS receiver alarm: position questionable
7108 BASE STATION SYNCHRONIZATION PROBLEM
4126
GPS receiver alarm: EEPROM invalid
7108 BASE STATION SYNCHRONIZATION PROBLEM
4153
Reference clock missing 7108 BASE STATION SYNCHRONIZATION in startup PROBLEM
4210
External GPS receiver in holdover
7108 BASE STATION SYNCHRONIZATION PROBLEM
Note: The fault External GPS receiver in holdover applies to GNSS receivers that support the holdover functionality. GNSS receivers supporting holdover functionality are to be introduced in further SRAN releases. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 14: New parameters lists parameters introduced with this feature.
Issue: 01E
DN09218825
51
Descriptions of transport and transmission features
Table 14
New parameters
Full name
g 3.5.1.6
SRAN 16.2, Feature Descriptions
Abbreviated name
Managed object
External GNSS antenna altitude
antennaAltitude
GNSSE
External GNSS antenna latitude
antennaLatitude
GNSSE
External GNSS antenna longitude
antennaLongitude
GNSSE
Connection signal propagation delay
connectionSignalPropagation GNSSE Delay
GNSSE object identifier
gnsseId
GNSSE
Holdover mode configuration
holdOverModeConfig
GNSSE
Output LNA power supply
outputLnaPowerSupply
GNSSE
Synchronization reference source list
referenceSourceList
SYNC
Input reference
inputReference
SYNC
Input reference priority
inputReferencePriority
SYNC
Note: GNSS receivers supporting Holdover mode configuration and Output LNA power supply are to be introduced in further SRAN releases.
Sales information Table 15
Sales information
BSW/ASW
License control in network element
ASW
Pool license
3.6 SR000600: Backup IPsec Tunnel 3.6.1 Description of SR000600: Backup IPsec Tunnel Introduction to the feature This feature enables geo-redundant security gateway (SEG) deployments by supporting establishment of alternative IPsec tunnels for the same traffic.
3.6.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature enables service continuation after a security gateway (site) disaster without site visit. Network domain security is completely maintained even in case of severe network/security infrastructure failures.
52
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.6.1.2
Descriptions of transport and transmission features
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.6.1.3
Functional description This feature supports the configuration of an alternative IPsec tunnel to allow georedundant security gateway deployments to enable site disaster recovery. Only one tunnel is active and carries traffic at a time. Security gateways themselves are not aware of their geo-redundant deployment because there is no control plane between them. To use this feature, the security gateways need to support tunnel-supervision-based route injection. The SBTS supports configuration of two tunnels with the same traffic selectors, one marked as primary, other marked as secondary tunnel. Multiple primary and secondary tunnel pairs are supported. These can be used for traffic separation. The SBTS monitors the primary tunnel and the related peer security gateways using dead peer detection (DPD). Once the DPD session indicates unavailability of the primary tunnel and/or SEG the SBTS tries to establish the secondary tunnel. In addition manual switchover using management command is supported. The switchback happens either manually using management command or automatically, depending on the configuration. •
•
In case of the automatic mode the SBTS continuously tries to establish the primary tunnel while traffic is transported through the secondary tunnel. The switchback happens as soon as this operation is successful. In case of the manual mode, a fail-safe measure is provided. It prevents the SBTS from remaining on the secondary path and unnecessary service outage in case of double failure. When the SBTS notices that the secondary tunnel fails it retries primary tunnel establishment.
To prevent SEGs from getting overloaded by tunnel setup requests, the switchover/switchback request time is controlled by configurable timers and optional randomization on top. The switchover/switchback happens per tunnel. In context of this feature a tunnel is defined as an Internet Key Exchange security association (IKE SA) with one or more related IPsec security associations (IPsec SAs). Feature is interoperable with: • • • •
transport layer redundancy mechanisms (for example Fast IP Rerouting or SCTP Multihoming) core/controller redundancy mechanisms (S1-flex and RNC resiliency) LTE505: Transport Separation for RAN Sharing feature SR000439: IPsec Emergency Bypass
A switchover of a particular tunnel does not impact other tunnels. For example in case of using LTE505: Transport Separation for RAN Sharing feature, a switchover among SEGs does not impact service of the other operator.
Issue: 01E
DN09218825
53
Descriptions of transport and transmission features
Figure 1
SRAN 16.2, Feature Descriptions
Primary and secondary IPsec tunnels
IP network Primary IPsec Tunnel
SEG A
Tunnel supervision BTS
Secondary IPsec Tunnel
SEGB
SEGsinjectroutesdependentonIPsecSA status
3.6.1.4
System impact Interdependencies between features This feature requires the following feature: •
SR000356: IPsec for BTS
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.6.1.5
SR000600: Backup IPsec Tunnel management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 16: New alarms lists alarms introduced with this feature.
54
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 16
Descriptions of transport and transmission features
New alarms
Alarm ID
Alarm name
61643
IPSec tunnel switchover
BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 17: New parameters lists parameters introduced with this feature. Table 17
New parameters
Full name
Issue: 01E
Abbreviated name
Managed object
IKE protection group instance identifier
ikeProtGrpId
IKEPROTGRP
IKE protection state
ikeProtState
IKEPROTGRP
List of IKE profiles
ikepList
IKEPROTGRP
IKE profile identifier
ikepId
IKEPROTGRP
Role
role
IKEPROTGRP
Switchback mode
switchBackMode
IKEPROTGRP
Switch request
switchRequest
IKEPROTGRP
Maximum switch time
switchTimeMax
IKEPROTGRP
Minimum switch time
switchTimeMin
IKEPROTGRP
IKE profile reference
ikepRef
SECPOL
Feature activation flag for backup IPsec tunnel
actIpSecBkupTun
TNL
DN09218825
55
Descriptions of transport and transmission features
3.6.1.6
SRAN 16.2, Feature Descriptions
Sales information Table 18
Sales information
BSW/ASW
License control in network element
ASW
Pool license
3.7 SR000366: BTS Firewall 3.7.1 Description of SR000366: SBTS Firewall Introduction to the feature This feature provides a firewall functionality which blocks the traffic from unwanted sources and disables access to restricted services and applications.
3.7.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature increases SBTS security and thus provides better network operation.
3.7.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.7.1.3
Functional description This feature provides a firewall functionality which blocks the traffic from unwanted sources and disables access to restricted services and applications. The firewall functionality is performed by the SBTS. The main firewall mechanisms are: packet filtering to discard unwanted packets and rate limiting for overload protection. Packet filtering The packet filtering mechanism analyzes packets received by the network element. Packets can bypass the firewall only if they come from known sources or are related to intended services; other packets are discarded. The packet filtering is performed only for ingress traffic; the outgoing traffic is not filtered. Two types of filtering are supported: • •
56
stateless filtering stateful filtering
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Stateless packet filtering is performed on the IP layer. Filtering rules are applied for traffic initiated by the communication peer. The following IP header fields are checked against the existing filter rules: • • • •
source IP address destination IP address source and destination ports transport layer (L4) protocol
Stateless filtering rules are automatically derived and configured within the SBTS based on the information about supported services and interworking nodes. The firewall filter rules cannot be configured manually. WCDMA user plane filtering rules are automatically configured based on IP address and UDP port selected locally, and IP address and UDP port received from RNC. Stateful packet filtering is performed for SCTP, BFD, IKE, ToP, NTP, SSH, CMP, XoH, HTTP(s), R&D services and ICMP traffic. Stateful packet filtering of the incoming O&M packets is also supported. Rate limiting Rate limiting is performed for ingress and egress traffic. The rate limit is configured depending on the hardware and the resources of the concerned SBTS subsystem. Ingress rate limiting protects internal subsystems against overload caused by misconfiguration of a peer device or by an attacker. The rate limiting mechanism aggregates different traffic flows and applies the rate limit to the aggregate. The typical aggregates are: • • • • • • •
user plane traffic control plane traffic management plane traffic ICMP traffic ARP traffic TWAMP & UDFP echo serer service OAM traffic
Egress rate limiting is performed only for Internet Control Message Protocol (ICMP) traffic. This mechanism helps to avoid ICMP overload and prevent the network element from participating in denial of service (DoS) attacks. The SBTS firewall also implements spoof prevention, protection against oversized packets, brute-force attacks, SYN flood attacks, LAND attacks, Ping of Death/Jolt attacks, and Teardrop attacks. The discarded packets are divided into two categories: • •
packets discarded because of the filter violations packets discarded because of the ingress rate limiting
The numbers of packets discarded in each category are available as counters.
3.7.1.4
System impact Interdependencies between features This feature requires the following feature:
Issue: 01E
DN09218825
57
Descriptions of transport and transmission features
•
SRAN 16.2, Feature Descriptions
SR000589: IPv4/IPv6 Transport Stack
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity When multiple RATs are operated on the SBTS a small impact on performance is expected due to high number of filtering rules.
3.7.1.5
SR000366: SBTS Firewall management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters Table 19: New counters lists counters introduced with this feature. Table 19
New counters
Counter ID
Counter name
Measurement
M51219C0
ipRmDroppedPacketsRateLimiting
IP filtering Statistics
M51219C1
ipRmDroppedPacketsFiltering
IP filtering Statistics
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 20: New parameters lists parameters introduced with this feature. Table 20
New parameters
Full name
Abbreviated name
IP filtering measurement interval
58
DN09218825
ipFilteringInterval
Managed object PM
Issue: 01E
SRAN 16.2, Feature Descriptions
3.7.1.6
Descriptions of transport and transmission features
Sales information Table 21
Sales information
BSW/ASW
License control in network element
BSW
-
3.8 SR000402: BTS QoS Support for Terminated and Routed Traffic 3.8.1 Description of SR000402: BTS QoS Support for Terminated and Routed Traffic Introduction to the feature This feature provides mechanisms of shaping of an egress traffic and DSCP to PCP mapping. With this feature, the SBTS operates the QoS mechanisms on the IP Layer and Ethernet/PPP/ML-PPP Layer in order to adjust different SBTS data flows with the demands of different RATs and different transport networks.
3.8.1.1
Benefits End-user benefits This feature provides that the end-users obtained QoS is optimized within the targets determined by the operator. Operator benefits This feature introduces that the network traffic is adjusted by the SBTS with an appropriate transport network QoS classes provided. This mechanism can fulfill the operators own requirements for separating, limiting, and measuring the traffic of the different RATs or the traffic of the services within it. This feature enables the usage of many different types of transport networks and configurations of those networks.
3.8.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.8.1.3
Functional description The traffic of different planes and different services has different demands for example concerning throughput, delay, and delay variation. In addition, the characteristics of the transport network determine the demands of the SBTS traffic on how the SBTS must accumulate traffic flows and shape the accumulated traffic flows. The operators have certain demands concerning how to split the bandwidth offered by a certain transport network among RATs and how to limit the traffic within the certain RAT. This feature provides mechanisms of shaping of an egress traffic and configurable DSCP to PCP mapping. Within this feature, the SBTS operates the QoS mechanisms on the IP Layer
Issue: 01E
DN09218825
59
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
and Ethernet/PPP/ML-PPP Layer in order to adjust different SBTS data flows with the demands of different RATs and different transport networks. With the provided mechanisms, the egress traffic is transferred in a prioritized manner and the impacts of delays and packet losses in network element transport and the mobile backhaul are decreased. In the ingress direction, the performance measurements counters are provided. This feature provides the hierarchical scheduling and shaping mechanisms of accumulated traffic flows. The internal IP-Router of an SBTS routes the packets of different applications and planes of different RATs towards the network IP interfaces. Behind the internal IP-Router, there are first level scheduler and shaper blocks which multiplex and schedule the traffic of one or more network IP interfaces in a QoS aware manner, and shape the accumulated traffic flows to a configurable peak rate and a configurable burst size. In some cases when more first level schedulers and shapers are configured for the network IP interfaces, the mechanism of flow classifier is utilized to determine to which block the egress packets must be forwarded. In addition within the presented feature, the second level scheduler and shaper blocks are provided to limit and prioritize the total of traffic towards a certain Ethernet MAC interface or PPP/MLPPP interface. Figure 2
Example configuration of hierarchical shaping mechanism
FIRST LEVEL SCHEDULER T EF3 QUEUE EF2 QUEUE
T – NEEDED!FOR!GSM!ONLY SP
SP SHAPER
EF1 QUEUE AF4 QUEUE
SP2
LTE
SHAPER
THERE ARE!DEFINED!GUARANTEED!RATES PER ACCUMULATED!FLOW!=!WEIGHTS
AF3 QUEUE
APPL. AF2 QUEUE
WFQ T
AF1 QUEUE
R!O!U T I!N!G
BE QUEUE SECOND!LEVEL SCHEDULER THERE ARE!DEFINED!MAX!RATES PER ACCUMULATED!FLOW
WFQ
SP
SHAPER
FIRST LEVEL SCHEDULER T EF3 QUEUE EF2 QUEUE
SP
SP SHAPER
EF1 QUEUE
WCDMA APPL.
AF4 QUEUE
SP2
SHAPER
AF3 QUEUE AF2 QUEUE AF1 QUEUE
WFQ
NETWORK!IP INTERFACE T
BE QUEUE
On the example configuration, the WCDMA and LTE applications are utilized but other configurations are permitted. The first level scheduler-shaper block has three queues managed with the strict priority scheduler and five queues managed with the weighted priority scheduler and configurable weights. The strict priority traffic is shaped to a configurable bandwidth with the shaper which places a limit on the strict priority traffic and protects the network from the undue amount of the strict priority traffic. The outputs, which come from the strict priority shaper and the weighted priority scheduler, are then
60
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
managed with next strict priority scheduler. The output of this scheduler is then shaped with the shaping function limiting the egress rate and burst size of the first level block. In addition, the weighted and the first strict priority schedulers apply a Δt mechanism, mandatory only with the GSM configuration. This mechanism verifies the timestamps and drops the packets remaining longer in the queue than the defined time. In the direct mapping, one first level scheduler takes traffic from one network IP interface, 1:1. In the configurations that require more flexibility, one first level scheduler can take traffic from multiple network IP interfaces, N:1. On the other hand, when the flow classifiers are configured, the traffic incoming from a single network IP interface can be split into multiple first level schedulers, 1:N. The first level schedulers perform the packet queuing mechanism based on IP header information but the complete L2 frames are considered additionally. There are many ways how to utilize the first level scheduler and shaper blocks. In the most simple configuration, there is just one first level block for one L2 interface. But when an operator wants to limit (in a multi-RAT configuration) the bandwidth of the WCDMA U-plane traffic, the traffic can be routed then via a specific first level scheduler and the peak rate for this traffic type can be configured. The scheduling weight can be determined with the first level scheduler blocks but the second level scheduler blocks perform the shaping operation of the total of traffic.
Issue: 01E
DN09218825
61
Descriptions of transport and transmission features
Figure 3
SRAN 16.2, Feature Descriptions
Example configuration of hierarchical shaping mechanism (extended view)
SHAPER ETHERNET SWITCH FIRST LEVEL SCHEDULER
SHAPER FIRST LEVEL SCHEDULER
SHAPER SECOND LEVEL SCHEDULER
ETHERNET MAC INTERFACE
INTERNAL ETHERNET INTERFACE
ETHPHYS INTERFACE
SWITCHPORT
EXTERNAL ETHERNET INTERFACE SHAPER FIRST LEVEL SCHEDULER
SHAPER
SHAPER SECOND LEVEL SCHEDULER
ETHERNET MAC INTERFACE
ETHPHYS INTERFACE
PPP INTERFACE
E1OR T1 PHYS INTERFACE
FIRST LEVEL SCHEDULER
SHAPER FIRST LEVEL SCHEDULER
SHAPER FIRST LEVEL SCHEDULER
SHAPER
SHAPER SECOND LEVEL SCHEDULER .. .. .. .. ..
SHAPER SECOND LEVEL SCHEDULER
.. .. .. .. ..
PPP INTERFACE
E1OR T1 PHYS INTERFACE
FIRST LEVEL SCHEDULER
This feature provides also the second level scheduler and shaper blocks. The blocks multiplex the traffic from the first level schedulers and shape the peak rate of the accumulated outgoing traffic flow. The second level block does not queue the traffic coming from the first level blocks and the packets wait in the first level block until the moment when they are scheduled by the second level block. This is important in order to avoid dropping packets in a non-QoS aware manner and to guarantee that a packet which is utilizing a strict priority queue can overtake all the packets which utilize the weighted fair queuing mechanism of the same first level block. The weighted fair queuing in the second level sheduler and sharper block is utilized to multiplex the traffic of the first level schedulers and shapers. In the common configurations, each second level block is allocated with just a single first level block. But when multiple accumulated traffic flows are transferred throughout the same interface and the peak rates of the flows must be controlled individually, multiple first level blocks must be configured. There is one second level scheduler-shaper block related with each PPP/ML-PPP and Ethernet interface. In addition, one second level block can handle multiple network IP interfaces only when utilizing the Ethernet interfaces.
62
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Figure 4
Descriptions of transport and transmission features
Example of enqueuing outgoing traffic
TYPE!1 FLOWS!FROM DIFFERENT NETWORK!IP INTERFACES ARE!SHAPED TOGETHER
FIRST LEVEL BLOCK APPL.!1 CLASSIFY APPL.!2
TYPE!2 FLOWS ARE SHAPED!PER NETWORK!IP INTERFACE – ONE!SHAPER PER!INTERFACE
FIRST LEVEL BLOCK
R CLASSIFY
APPL.!3
O
EF!1 EF!2 EF!3 AF!4 AF!3 AF!2 AF!1 BE
EF!1 EF!2 EF!3 AF!4 AF!3 AF!2 AF!1 BE
S P
W F
SHAPER
S P
Q
SHAPER
S P
SHAPER
W F
Q
S P
ToP TRAFFIC
SHAPER
SECOND!LEVEL BLOCK
U FIRST LEVEL BLOCK APPL.!4
T CLASSIFY APPL.!5
I
EF!1 EF!2 EF!3 AF!4 AF!3 AF!2 AF!1 BE
S P
W F
SHAPER
W F
Q
S P
SHAPER
ETHERNET PORT
S P
Q
SHAPER
S P
SHAPER
ETHERNET LAYER!OAM
N TYPE!3 FLOWS!FROM THE!SAME NETWORK IP INTERFACE ARE!SHAPED SEPARATELY
FIRST LEVEL BLOCK
G CLASSIFY
APPL.!6
EF!1 EF!2 EF!3 AF!4 AF!3 AF!2 AF!1 BE
W F
NOTE:!ETHERNET OAM!IS PLANNED!FOR!FUTURE RELEASES
S P
Q
SHAPER
S P
SHAPER
FLOW CLASSIFIER FIRST LEVEL BLOCK
APPL.!7
CLASSIFY
EF!1 EF!2 EF!3 AF!4 AF!3 AF!2 AF!1 BE
W F
Q
S P
NETWORK!IP INTERFACE OPTIONAL IPSEC TERMINATION
SHAPER
This feature expects that the DSCP marking mechanism of each egress traffic type is performed by the U-, C-, and M-plane RAT applications. The feature provides the mechanisms configurable on each SBTS independently: configurable DSCP to PCP mapping and to PHB mapping, and configurable ARP traffic PCP marking. The traffic which is originated in the SBTS has the DSCP marking from the application of origin whereas the routed traffic obtains the DSCP marking already at the originating node. In addition, the first level scheduler and shaper blocks utilize the DSCP markings corresponded with each packet to enqueue the egress traffic in the PHB queues. The packets are scheduled based on the strict priority queues and weighted fair queuing mechanism, and the first level blocks must ensure that an egress rate of each accumulated traffic flow cannot surpass the maximum value.
3.8.1.4
System impact Interdependencies between features This feature requires (not in Ethernet network configuration) the feature: •
SR000176: ML-PPP termination
This feature requires (not in ML-PPP network configuration) the feature: •
SR000350: Ethernet Termination
This feature requires the features:
Issue: 01E
DN09218825
63
Descriptions of transport and transmission features
• •
SRAN 16.2, Feature Descriptions
SR000382: Multiple VLAN Interfaces SR000589: IPv4/IPv6 Transport Stack
Related features: • • • • •
SR000356: IPsec for BTS SR000374: Timing over Packet with Frequency Sync SR000383: Timing over Packet with phase synchronization SR000386: QoS Aware Ethernet Switching SR000465: Local and Remote IP Traffic Capturing
Impact on interfaces This feature has an impact on interfaces as beneath: •
The feature provides configurable DSCP to PCP mapping for Ethernet interfaces.
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.8.1.5
SR000402: BTS QoS Support for Terminated and Routed Traffic management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults There are no alarms and faults related to this feature. Measurements and counters Table 22: New counters lists counters introduced with this feature. Table 22
Counter ID
64
New counters
Counter name
Measurement
M51351C0
ifTxOctets_EF1
First Level Scheduler Statistics
M51351C1
ifTxPackets_EF1
First Level Scheduler Statistics
M51351C2
ifTxDropOctets_rate_EF1
First Level Scheduler Statistics
M51351C3
ifTxDropPackets_rate_EF1
First Level Scheduler Statistics
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 22
Counter ID
Issue: 01E
Descriptions of transport and transmission features
New counters (Cont.)
Counter name
Measurement
M51351C4
ifTxDropOctets_delta_EF1
First Level Scheduler Statistics
M51351C5
ifTxDropPackets_delta_EF1
First Level Scheduler Statistics
M51351C6
ifTxOctets_EF2
First Level Scheduler Statistics
M51351C7
ifTxPackets_EF2
First Level Scheduler Statistics
M51351C8
ifTxDropOctets_rate_EF2
First Level Scheduler Statistics
M51351C9
ifTxDropPackets_rate_EF2
First Level Scheduler Statistics
M51351C10
ifTxDropOctets_delta_EF2
First Level Scheduler Statistics
M51351C11
ifTxDropPackets_delta_EF2
First Level Scheduler Statistics
M51351C12
ifTxOctets_EF3
First Level Scheduler Statistics
M51351C13
ifTxPackets_EF3
First Level Scheduler Statistics
M51351C14
ifTxDropOctets_rate_EF3
First Level Scheduler Statistics
M51351C15
ifTxDropPackets_rate_EF3
First Level Scheduler Statistics
M51351C16
ifTxDropOctets_delta_EF3
First Level Scheduler Statistics
M51351C17
ifTxDropPackets_delta_EF3
First Level Scheduler Statistics
M51351C18
ifTxOctets_AF1
First Level Scheduler Statistics
M51351C19
ifTxPackets_AF1
First Level Scheduler Statistics
DN09218825
65
Descriptions of transport and transmission features
Table 22
Counter ID
66
SRAN 16.2, Feature Descriptions
New counters (Cont.)
Counter name
Measurement
M51351C20
ifTxDropOctets_rate_AF1
First Level Scheduler Statistics
M51351C21
ifTxDropPackets_rate_AF1
First Level Scheduler Statistics
M51351C22
ifTxDropOctets_delta_AF1
First Level Scheduler Statistics
M51351C23
ifTxDropPackets_delta_AF1
First Level Scheduler Statistics
M51351C24
ifTxOctets_AF2
First Level Scheduler Statistics
M51351C25
ifTxPackets_AF2
First Level Scheduler Statistics
M51351C26
ifTxDropOctets_rate_AF2
First Level Scheduler Statistics
M51351C27
ifTxDropPackets_rate_AF2
First Level Scheduler Statistics
M51351C28
ifTxDropOctets_delta_AF2
First Level Scheduler Statistics
M51351C29
ifTxDropPackets_delta_AF2
First Level Scheduler Statistics
M51351C30
ifTxOctets_AF3
First Level Scheduler Statistics
M51351C31
ifTxPackets_AF3
First Level Scheduler Statistics
M51351C32
ifTxDropOctets_rate_AF3
First Level Scheduler Statistics
M51351C33
ifTxDropPackets_rate_AF3
First Level Scheduler Statistics
M51351C34
ifTxDropOctets_delta_AF3
First Level Scheduler Statistics
M51351C35
ifTxDropPackets_delta_AF3
First Level Scheduler Statistics
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 22
Descriptions of transport and transmission features
New counters (Cont.)
Counter ID
Issue: 01E
Counter name
Measurement
M51351C36
ifTxOctets_AF4
First Level Scheduler Statistics
M51351C37
ifTxPackets_AF4
First Level Scheduler Statistics
M51351C38
ifTxDropOctets_rate_AF4
First Level Scheduler Statistics
M51351C39
ifTxDropPackets_rate_AF4
First Level Scheduler Statistics
M51351C40
ifTxDropOctets_delta_AF4
First Level Scheduler Statistics
M51351C41
ifTxDropPackets_delta_AF4
First Level Scheduler Statistics
M51351C42
ifTxOctets_BE
First Level Scheduler Statistics
M51351C43
ifTxPackets_BE
First Level Scheduler Statistics
M51351C44
ifTxDropOctets_rate_BE
First Level Scheduler Statistics
M51351C45
ifTxDropPackets_rate_BE
First Level Scheduler Statistics
M51351C46
ifTxDropOctets_delta_BE
First Level Scheduler Statistics
M51351C47
ifTxDropPackets_delta_BE
First Level Scheduler Statistics
M51352C0
ifTxOctets_2ndScheduler
Second Level Scheduler Statistics
M51352C1
ifTxPackets_2ndScheduler
Second Level Scheduler Statistics
M51352C6
ifTxOctets_ToP_2ndScheduler
Second Level Scheduler Statistics
M51352C7
ifTxPackets_ToP_2ndScheduler
Second Level Scheduler Statistics
DN09218825
67
Descriptions of transport and transmission features
Table 22
Counter ID
SRAN 16.2, Feature Descriptions
New counters (Cont.)
Counter name
Measurement
M51352C8
ifTxOct_Disc_ToP_2ndSched
Second Level Scheduler Statistics
M51352C9
ifTxPkt_Disc_ToP_2ndSched
Second Level Scheduler Statistics
M51353C0
ifRxOctets_EF1
IP PHB Statistics
M51353C1
ifRxPackets_EF1
IP PHB Statistics
M51353C2
ifRxOctets_EF2
IP PHB Statistics
M51353C3
ifRxPackets_EF2
IP PHB Statistics
M51353C4
ifRxOctets_EF3
IP PHB Statistics
M51353C5
ifRxPackets_EF3
IP PHB Statistics
M51353C6
ifRxOctets_AF1
IP PHB Statistics
M51353C7
ifRxPackets_AF1
IP PHB Statistics
M51353C8
ifRxOctets_AF2
IP PHB Statistics
M51353C9
ifRxPackets_AF2
IP PHB Statistics
M51353C10
ifRxOctets_AF3
IP PHB Statistics
M51353C11
ifRxPackets_AF3
IP PHB Statistics
M51353C12
ifRxOctets_AF4
IP PHB Statistics
M51353C13
ifRxPackets_AF4
IP PHB Statistics
M51353C14
ifRxOctets_BE
IP PHB Statistics
M51353C15
ifRxPackets_BE
IP PHB Statistics
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 23: New parameters lists parameters introduced with this feature.
68
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 23
Descriptions of transport and transmission features
New parameters
Full name
Issue: 01E
Abbreviated name
Managed object
Total shaper burst size
sbsTotal
ETHIF
Include Ethernet overhead when shaping
shapingOverhead
ETHIF
Total shaper information rate
sirTotal
ETHIF
Default first level scheduler
defaultFstschId
FLOWCL
Flow classifier identifier
flowClId
FLOWCL
IP interface identifier list
ipIfIdList
FLOWCL
Flow classifier rule set
ruleSet
FLOWCL
– First level scheduler identifier
– fstSchId
FLOWCL
– Order number of policy
– orderNumber
FLOWCL
– Source ip address
– srcIpAddr
FLOWCL
– Source subnet prefix length
– srcSubnetPrefixLength
FLOWCL
User label
userLabel
FLOWCL
First level scheduler identifier
fstSchId
FSTSCH
IP interface identifier list
ipIfIdList
FSTSCH
Shaper burst size
sbs
FSTSCH
WFQ weight assigned by second level scheduler
scdschWfqWeight
FSTSCH
Shaper information rate
sir
FSTSCH
SP queue shaping rate limiter
spShapingRate
FSTSCH
User label
userLabel
FSTSCH
Queue weight list
wfqWeightList
FSTSCH
– Assured forwarding class 1 weight value
– weightAF1
FSTSCH
– Assured forwarding class 2 weight value
– weightAF2
FSTSCH
– Assured forwarding class 3 weight value
– weightAF3
FSTSCH
– Assured forwarding class 4 weight value
– weightAF4
FSTSCH
DN09218825
69
Descriptions of transport and transmission features
Table 23
New parameters (Cont.)
Full name
3.8.1.6
SRAN 16.2, Feature Descriptions
Abbreviated name
Managed object
– Best effort weight value
– weightBE
FSTSCH
First level scheduler statistics measurement interval
firstLevelSchedulerStatisticsI nterval
PM
PHB statistics measurement interval
ipPerHopBehaviourStatisticsI nterval
PM
Second level scheduler statistics measurement interval
secondLevelSchedulerStatisti PM csInterval
Priority bit value for ARP traffic
arpPcp
QOS
Table for mapping DSCPs to PHBs and PCP bits
dscpMap
QOS
– differentiated services code point (DSCP) – dscp value
QOS
– Queue
– queue
QOS
– VLAN priority bits
– vlanPrio
QOS
Quality of service identifier
qosId
QOS
Sales information Table 24
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
3.9 SR000847: BTS Synchronization Mode Support 3.9.1 Description of SR000847: BTS Synchronization Mode Support Introduction to the feature This feature enables that the SBTS can be configured to operate in the frequency synchronization or phase (and time) synchronization mode.
70
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.9.1.1
Descriptions of transport and transmission features
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides support for the frequency and phase (and time) synchronization and thus the operators can preferentially determine the type of synchronization support that meets their demands.
3.9.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.9.1.3
Functional description Overview This feature enables that the SBTS can be configured to operate in the frequency synchronization or phase (and time) synchronization mode and thus the operators can preferentially determine the type of synchronization support that meet their demands. When an SBTS operates in the frequency synchronization mode, it is frequency synchronized to its synchronization source by tuning its oscillator in accordance with the synchronization input. The generated radio frame in the air interface is frequency synchronized to synchronization sources. This synchronization mode has two kinds: •
•
frequency synchronization mode at network level - when the synchronization sources are frequency synchronized and traceable back to Primary Reference Clock (PRC), an SBTS is frequency synchronized to other SBTSs or network elements frequency synchronized to the same PRC. frequency synchronization mode at site level - when the synchronization sources are not traceable back to PRC, an SBTS is frequency synchronized to its synchronization source only and is not frequency synchronized to other SBTSs and network elements within the network.
When an SBTS operates in the phase synchronization mode, it is phase and time synchronized to its synchronization source by tuning its oscillator in accordance with the synchronization input. This synchronization mode has two kinds: •
•
phase and time synchronization at network level - when the synchronization sources are phase and time synchronized, and they are traceable back to Primary Time Reference Clock (PRTC), an SBTS can achieve phase and time synchronization at network level meaning that itself is phase and time synchronized to other SBTSs or network elements that are phase and time traceable to the same PRTC. phase and time synchronization at site level - when the synchronization sources are not traceable back to PRTC, an SBTS is phase and time synchronized to its synchronization source only and is not phase and time synchronized to other SBTSs and network elements within the network.
Frequency synchronization mode
Issue: 01E
DN09218825
71
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
When the SBTS is frequency synchronized, the radio interface carrier frequency is obtained from the frequency synchronous input signal. In this mode, the sequence numbering and phase of the radio interface frames can be random. When during the SBTS startup, there is no valid synchronization input signal, the SBTS continues the startup operation and can go into operation mode in free-run mode. An alarm is generated. In this situation, the SBTS internal oscillator clock is utilized to provide the system clock generation and the synchronization output signals. When an external synchronization source is not provided, the system clock generation is obtained from the SBTS internal oscillator clock. When this internal oscillator clock also cannot be adapted, then the SBTS operates in free-run mode. This behavior does not make a big difference from the functional point of view with the exception that any mechanisms (phase synchronization, adaptive holdover algorithm) which depend on certain tuning operations cannot operate in free-run mode. The carrier frequency accuracy in the radio interface must be in the range ± 50ppb as determined in the 3GPP recommendation. This requirement must be also met in the moment when the synchronization reference source changes. Phase and time synchronization mode When the SBTS is phase and time synchronized, it is able to generate a radio frame which is in phase with transition of absolute time reference (UTC) in the case of the phase and time synchronization at network level. In the case of the phase and time synchronization at site level, the generated radio frame of the SBTS is phase and time synchronized to its synchronization source. When the SBTS obtains the phase synchronization signal from its synchronization input interface, the SBTS is able to compensate the propagation delay between the synchronization source and the synchronization input interface. The SBTS generates the System Frame Number (SFN) based on the receiving time information from the synchronization reference sources. When the SBTS regains the synchronization to an external synchronization reference source (for example when changing from the holdover mode), then it checks if the utilized sequence numbering is matched with the values calculated from the time information. In the situation of a mismatch, the SBTS compensates the SFN values to the values calculated in the new calculation. In phase and time synchronization mode, in order to ensure that the SBTS is able to generate accurate frame adjustment in the air interface and prevent performance degradation of phase and time synchronization dependent radio applications, a valid phase synchronization input is required during the SBTS startup. When there is no valid phase synchronization input signal, the SBTS cannot go into operation. An alarm is generated. When the appropriate phase synchronization input is obtained, the SBTS continues the startup operation. In phase and time synchronization mode, the SBTS supports flexible adjustment of the phase of the radio interface system frames on its radio interface. The phase shifting is administered with a configurable parameter. When the parameter is configured to the default value 0us, the 10ms radio interface frames start in nominal position in which it is adjusted with the rising edge of the 1pps synchronization input pulse. When the parameter is configured with the positive values, the start of the radio interface frames is delayed when compared to the nominal position. With the negative values of the parameter, the start of the radio interface frames is done sooner when compared to the nominal position. Troubleshooting mechanisms
72
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
The feature provides certain mechanisms for troubleshooting the synchronization problems in the SBTS. One of them is an internal frequency synchronization reference modification through the manual configuration. With this mechanism, the operator can configure the internal frequency synchronization reference in the SBTS without continuous tuning against an external synchronization reference. The value range must contain the whole tuning range of the internal frequency synchronization reference. The minimum resolution of the internal frequency synchronization reference manual configuration must be 2ppb. With the manual configuration mechanism, the operator can determine whether the external synchronization networks do not operate as demanded and whether the SBTS operates appropriately. The operator must perform the manual configuration mechanism with caution and the SBTS must be blocked prior to make any modifications through the mechanism. The internal frequency synchronization reference modifications by manual configuration do not suspend any other synchronization mechanisms and the mechanisms continue the normal operation mode. The feature provides support the accelerated tuning mechanisms which tune the internal phase and frequency in the SBTS with the external synchronization references. The mechanisms simplify the synchronization troubleshooting and the operator can quickly provide the synchronization in the SBTS again when the synchronization in the SBTS is mistuned. The accelerated tuning mechanisms accelerate the synchronization tuning at minimum by five times when compared to the normal tuning mechanism. When being at phase synchronization mode, the tuning mechanism acceleration is stopped when the mechanism attains the thresholds: the frequency accuracy threshold defined as 30ppb and the phase accuracy threshold defined as 200ns. When the Timing over Packet mechanism is an active synchronization reference, the phase accuracy threshold is defined as 400ns. When being at frequency synchronization mode, the tuning mechanism acceleration is stopped after the determined time duration and when the mechanism attains the frequency accuracy threshold defined as 30ppb. This time duration conforms to the certain synchronization reference and cannot take more than 30 minutes. The operator must perform the synchronization tuning acceleration with caution and the SBTS must be blocked prior to make any modifications through the acceleration mechanisms. The synchronization accuracy requirements may be violated when performing the acceleration of the synchronization tuning mechanisms. The feature provides the synchronization log having the synchronization tuning history data gathered from the certain time period. With the synchronization log the operator can perform the troubleshooting and the root cause identification of the synchronization problems. The synchronization log can contain the synchronization tuning data from at minimum the past 14 days. One data entry is added to the synchronization log per 20minutes time period. This is the maximum time period. The data entries can be added more frequently but this may require more memory. The SBTS has an interface which enables the operator to download and read the synchronization log to troubleshoot the problems with the synchronization. The synchronization log contains: tuning value which conforms to an internal frequency synchronization reference (average tuning value in the determined time period), timestamp in UTC time standard when a certain data entry is added to the synchronization log, active synchronization reference source type, an estimation of the clock frequency difference between the internal frequency reference and the active external frequency reference, active tuning mode at the time of addition a certain data entry which can be normal/accelerated/manual synchronization tuning value configuration.
3.9.1.4
System impact Interdependencies between features
Issue: 01E
DN09218825
73
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
This feature affects the feature: SR000385: Synchronization Hub
•
This feature is the precondition for the features: SR000374: Timing over Packet with Frequency Sync SR000375: Synchronous Ethernet SR000376: Synchronization from 2.048MHz signal SR000377: Synchronization from PDH interface SR000383: Timing over Packet with phase synchronization SR000788: 1PPS&ToD Sync from External GNSS receiver SR001103: SBTS Flexible Sync Input Priority
• • • • • • •
Related feature: SR001041: Synchronization Holdover Support
•
Impact on interfaces This feature has an impact on interfaces as beneath: The feature provides configuration of an air interface offset timing. The feature provides management interface for control and fault management.
• •
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.9.1.5
SR000847: BTS Synchronization Mode Support management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults Table 25: New alarms and faults lists alarms and faults introduced with this feature. Table 25
BTS Fault ID
74
New alarms and faults
BTS Fault name
Reported alarms
9
Difference between BTS 7108 BASE STATION SYNCHRONIZATION master clock and PROBLEM reference frequency
16
Unit synchronization failed
7101 RESET NOTIFICATION 7108 BASE STATION SYNCHRONIZATION PROBLEM
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 25
BTS Fault ID
Descriptions of transport and transmission features
New alarms and faults (Cont.)
BTS Fault name
Reported alarms
1817
Oven oscillator heating failure
1818
BTS master clock tuning 7108 BASE STATION SYNCHRONIZATION failure PROBLEM
1819
Oven oscillator clock missing
7108 BASE STATION SYNCHRONIZATION PROBLEM
4019
Master unit has lost connection to the slave unit
7101 RESET NOTIFICATION
Phase error exceeds 5 us limit
7108 BASE STATION SYNCHRONIZATION PROBLEM
6280
7108 BASE STATION SYNCHRONIZATION PROBLEM
7108 BASE STATION SYNCHRONIZATION PROBLEM
Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 26: New parameters lists parameters introduced with this feature. Table 26
New parameters
Full name
3.9.1.6
Managed object
BTS synchronization mode
btsSyncMode
SYNC
Manual frame timing adjustment
manualFrameTimingAdjustm ent
SYNC
Synchronization object identifier
syncId
SYNC
Sales information Table 27
Issue: 01E
Abbreviated name
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
DN09218825
75
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
3.10 SR000365: Electrical 100/1000-Base-T Interface 3.10.1 Description of SR000365: Electrical 100/1000-Base-T Interface Introduction to the feature Feature SR000365: Electrical 100/1000-Base-T Interface introduces one or more 100Base-TX/1000Base-T physical Ethernet interfaces at an SBTS.
3.10.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • •
3.10.1.2
local site connectivity (for example connecting an SBTS to an external transport device deployed at the same site) compliance with IEEE 802.3 ensures interoperability with other network elements
Requirements Hardware requirements This feature requires to Flexi Multiradio 10 System Module (FSMF) or Flexi Multiradio BTS Transport Sub-Module (FTIF).
3.10.1.3
Functional description SR000365: Electrical 100/1000-Base-T Interface introduces one or more 100BaseTX/1000Base-T physical Ethernet interfaces at an SBTS. The feature describes the general functions of the physical layer including the physical coding sublayer (PCS) of an Ethernet interface. Main functionalities introduced with SR000365: Electrical 100/1000-Base-T Interface feature: • •
• •
•
76
providing one or more 100Base-TX/1000Base-T physical Ethernet interfaces according to IEEE 802.3-2012 automatic MDI/MDIX detection and swapping of RX/TX directions Automatic MDI/MDIX detection helps to avoid problems when using wrong cables and simplifies installation of the equipment. full-duplex transmission mode only available autonegotiation: line rates of 100/1000 Mbps are negotiated With autonegotiation the link partners select the technology which offers the highest bandwidth and is supported by both of them. When autonegotiation is disabled, an Ethernet interface operates in a forced mode (100 Mbps, full duplex). For 1000Base-T autonegotiation is mandatory. link speed downshift (1000Base-T to 100Base-TX)
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
• •
• •
Descriptions of transport and transmission features
When 1000Base-T gets negotiated but link establishment with 1000Base-T fails, link speed downshift switches to 100Base-TX. RJ-45 (8P8C) connector with IEEE 802.3-2012 compliant pinning master/slave clock selection function (for 1000Base-T) One link partner takes the role of a clock master and provides the clock reference to the other link partner. The other link partner takes the role of a clock slave, recovers clock, and transmits its own signal with exactly the same speed as the clock master. Transmitting at the same speed enables implementation of echo cancellation, which improves the signal-to-noise ratio. 100 ohm impedance outdoor overvoltage protection with use of shielded twisted pair cable
Validation of the Ethernet interfaces utilization in FSMr3 Transport network should validate that the user configuration regarding Ethernet interfaces applies to the support and constraints of the BTS types. With outdoor unit the following figure illustrates the supported Ethernet interface configurations. Figure 5
Supported Ethernet interface configurations
FSM (FSMr3)
RP3-01/EIF sharedport (usedasEIF)
•
ComboPort
ETHLK
ETHLK
ETHLK
ETHLK
ETHLK
- Administrative State -ethLkId=0-1
- Administrative State -ethLkId=0-2
- Administrative State -ethLkId=1-1
- Administrative State -ethLkId=1-3
- Administrative State -ethLkId=1-2
- Administrative State -ethLkId=1-4
FSMEIF1
FSMEIF2
FTIFEIF1
FTIF EIF3
FTIF EIF2
FTIF EIF4
OnlyoneEIFportcanbeused
OnlyoneEIFportcanbeused
Resulting from above figure up three Ethernet interfaces can be used. All interfaces related to one combo port are mutual exclusive, those are: – –
•
ComboPort
ETHLK
SingleEIFport, nodependency
•
FTIF
FTIF-EIF1 and FTIF-EIF3 FTIF-EIF2 and FTIF-EIF4
In case the shared RP3-01/TRS interface is configured as transport interface, the multiplexed Ethernet port, i.e. FTIF-EIF1 and FTIF-EIF3 from transport unit cannot be used anymore.
By default only one Ethernet interface is supported. More interfaces can by activated by software license key.
3.10.1.4
System impact Interdependencies between features There are features that rely on the existence of an Ethernet interface. This feature is one of the available options for providing an Ethernet interface. Exemplary features that require an Ethernet interface: •
Issue: 01E
SR000350: Ethernet Termination
DN09218825
77
Descriptions of transport and transmission features
•
SRAN 16.2, Feature Descriptions
SR000375: Synchronous Ethernet
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: • •
•
•
3.10.1.5
The feature provides 100 Mbps (100Base-TX) or 1000 Mbps (1000Base-T) bandwidth for the client feature SR000350: Ethernet Termination. With autonegotiation the link partners select the technology which offers the highest bandwidth and is supported by both of them. If the cell site device connected to an SBTS element advertises only 100Base-TX technology, then the Ethernet link provides 100 Mbps. Depending on the BTS RAT, overall site capacity and related mobile backhaul bandwidth, operating at 100Base-TX can lead to a delay of Ethernet frames and potential congestion. The offered link speed downshift function can result in rare cases where an Ethernet interface is operating unexpectedly at 100Base-TX operation mode. The user can read the status of the autonegotiation and receives an alarm in case of link speed downshift, so he can take actions in case 100Base-TX is not a desired operation mode.
SR000365: Electrical 100/1000-Base-T Interface management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 28: New alarms lists alarms introduced with this feature. Table 28
New alarms
Alarm ID
Alarm name
61029
LOS on unit $U, interface $IF
61607
Auto-negotiation mismatch, on unit $U, Ethernet interface $IF
BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature.
78
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Parameters Table 29: New parameters lists parameters introduced with this feature. Table 29
New parameters
Full name
3.10.1.6
Abbreviated name
Managed object
Clock mode configuration
clockMode
MOCx
Label of the connector by the ethernet link
connectorLabel
ETHLK
Sales information Table 30
Sales information
BSW/ASW
License control in network element
ASW
Pool license
3.11 SR000350: Ethernet Termination 3.11.1 Description of SR000350: Ethernet Termination Introduction to the feature This feature introduces the Ethernet Layer 2 termination on the SBTS. The feature provides primary functions of an Ethernet Interface Service for the IP/Ethernet Layer applications (Synchronous Ethernet, Ethernet switching, Ethernet OAM, IPv4 and IPv6 transport standards) focusing on the Ethernet framing-related functions among the MAC Layer and Physical Layer [IEEE 802.3].
3.11.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the primary functions needed with the Ethernet interface comprising the Ethernet termination and Ethernet forwarding. The Jumbo frame is accommodated to support increased overhead due to the IPv6 transport standard.
3.11.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
Issue: 01E
DN09218825
79
Descriptions of transport and transmission features
3.11.1.3
SRAN 16.2, Feature Descriptions
Functional description This feature introduces the Ethernet Layer 2 termination on the SBTS. The feature provides primary functions of an Ethernet Interface Service for the IP/Ethernet Layer applications (Synchronous Ethernet, Ethernet switching, Ethernet OAM, IPv4 and IPv6 transport standards) focusing on the Ethernet framing-related functions among the MAC Layer and Physical Layer [IEEE 802.3]. This feature provides support for one VLAN/Ethernet interface of one MAC entity communicating towards the IP Layer. The mechanisms for VLAN support each type of Ethernet frames with the exception of Ethernet control plane frames. In addition, the administration of an unique MAC address on the Ethernet interface, and the administrative state management of the Ethernet interface are provided. This feature defines the Ethernet jumbo frame support of at least 2000 octets size and provides Ethernet port mirroring and ingress rate limiting. The ingress rate limiting protects the SBTS uplink traffic bandwidth from the uncontrolled and inordinate uplink traffic chained via the SBTS integrated Ethernet switch. The ingress rate limiting is determined on the ingress port and is switched off by default. Figure 6
Ethernet termination
OSIREFERENCE MODEL LAYERS
LANCSMA/CDLAYERS
APPLICATION PRESENTATION
HIGHERLAYERS
SESSION
LLC(LOGICAL LINKCONTROL)OROTHERMACCLIENT
TRANSPORT
OAM(OPTIONAL)
NETWORK
MACCONTROL (OPTIONAL)
DATA LINK
MAC-MEDIA ACCESSCONTROL
PHYSICAL
PHYSICAL LAYER
EthernetTermination
3.11.1.4
System impact Interdependencies between features This feature requires one of the features: • • • • •
SR000365: Electrical 100/1000-Base-T Interface SR000368: 1000Base-SX Optical GE Interface SR000369: 1000Base-LX Optical GE Interface SR000370: 1000Base-ZX Optical GE Interface SR000371: 1000Base-BX Optical GE Interface
This feature is the precondition for the features: • • •
SR000375: Synchronous Ethernet SR000382: Multiple VLAN Interfaces SR000386: QoS Aware Ethernet Switching
This feature is the precondition (not in ML-PPP network configuration) for the features: •
80
SR000402: BTS QoS Support for Terminated and Routed Traffic
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
•
Descriptions of transport and transmission features
SR000589: IPv4/IPv6 Transport Stack
Impact on interfaces This feature has an impact on interfaces as beneath: • • •
The feature enables the SBTS to use VLAN-based IP network connectivity for RAN connectivity. The feature provides support for one VLAN/Ethernet interface of one MAC entity communicating towards the IP Layer. The feature provides support for one VLAN interface of one SBTS.
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.11.1.5
SR000350: Ethernet Termination management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults Table 31: New alarms and faults lists alarms and faults introduced with this feature. Table 31
BTS Fault ID 61029
New alarms and faults
BTS Fault name
LOS on unit $U, interface $IF
Reported alarms
61029 LOS on unit $U, interface $IF
Measurements and counters Table 32: New counters lists counters introduced with this feature. Table 32
New counters
Counter ID
Issue: 01E
Counter name
Measurement
M51300C0
EthIfInUnknownVlan
Ethernet Interface Statistics
M51300C1
EthIfInEthTypeMismatch
Ethernet Interface Statistics
M51300C2
EthIfInFrames
Ethernet Interface Statistics
M51300C3
EthIfInOctets
Ethernet Interface Statistics
M51300C4
EthIfOutFrames
Ethernet Interface Statistics
DN09218825
81
Descriptions of transport and transmission features
Table 32
SRAN 16.2, Feature Descriptions
New counters (Cont.)
Counter ID
Counter name
Measurement
M51300C5
EthIfOutOctets
Ethernet Interface Statistics
M51300C6
EthIfInPrioTaggedFrames
Ethernet Interface Statistics
M51301C0
EthIfInFrames
Ethernet Link Statistics
M51301C1
EthIfInOctets
Ethernet Link Statistics
M51301C2
EthIfOutFrames
Ethernet Link Statistics
M51301C3
EthIfOutOctets
Ethernet Link Statistics
M51301C4
EthIfInFrameError
Ethernet Link Statistics
M51301C5
EthIfInDiscRateLimiting
Ethernet Link Statistics
M51301C7
EthIfInFramesBroadcast
Ethernet Link Statistics
M51301C9
EthIfOutFramesBroadcast
Ethernet Link Statistics
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 33: New parameters lists parameters introduced with this feature. Table 33
New parameters
Full name
82
Abbreviated name
Managed object
Ethernet interface instance identifier
ethifId
ETHIF
Reference to an external or internal bridgeport
linkSelector
ETHIF
MAC address
macAddr
ETHIF
Priority tagging at transmit direction
txPriorityTagging
ETHIF
User label
userLabel
ETHIF
Administrative state of the Ethernet link
administrativeState
ETHLK
Ethernet link
ethlkId
ETHLK
Ethernet interface ingress rate limiter
l2IngressRate
ETHLK
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 33
Descriptions of transport and transmission features
New parameters (Cont.)
Full name
3.11.1.6
Abbreviated name
Managed object
Operational state of the Ethernet link
operationalState
ETHLK
User label
userLabel
ETHLK
connection time out
connectionTimeout
ETHMIRROR
Instance identifier of the mirror object
ethMirrorId
ETHMIRROR
Enable port mirroring
portMirroringEnabled
ETHMIRROR
Procedural Status
proceduralStatus
ETHMIRROR
Destination
destination
ETHMIRRORSET
Instance identifier of the ethernet mirror object
ethMirrorSetId
ETHMIRRORSET
Source
source
ETHMIRRORSET
Source direction
sourceDirection
ETHMIRRORSET
Ethernet services root object identifier
ethsvcId
ETHSVC
Ethernet IF statistics measurement interval
ethernetInterfaceStatisticsInte PM rval
Ethernet link measurement interval
ethernetLinkInterval
PM
Sales information Table 34
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
3.12 SR000344: Fast IP Rerouting 3.12.1 Description of SR000344: Fast IP Rerouting Introduction to the feature This feature provides support for transport path redundancy by rerouting procedure among static routes in case of a path failure. The path failure detection and supervision are based on the Bidirectional Forwarding Detection (BFD) network protocol.
Issue: 01E
DN09218825
83
Descriptions of transport and transmission features
3.12.1.1
SRAN 16.2, Feature Descriptions
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature enables to create more robust networks by applying the redundant backhaul connections.
3.12.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.12.1.3
Functional description This feature provides a transport path protection mechanism with short failure detection and failover times, through switching among the pre-configured primary and alternative path in a path failure situation. The network elements (NE(s)) are provisioned with two routes, out of which one is configured as the Primary Path and the other one as the Alternative Path. BFD sessions, determined for failure detection, operate among the network element and the router, which is representing the next hop of the path. In the router(s), the route to the network element is also connected to the BFD session. This redundancy concept is based on a Network Layer path supervision mechanism (using BFD) which triggers a path rerouting procedure in the Primary Path failure situation. The rerouting procedure depends on the element perspective: •
•
Network element perspective - when the BFD session state goes down, the Primary Path is taken out of usage and the Alternative Path is selected, which provides the transport path via the secondary router. When the BFD session state is up again, the Primary Path is taken into use after expiration of configurable timer. Router perspective - the primary router detects route availability towards the network element via the BFD session directly. By means of a routing protocol, the two routers exchange this information. Based on this, the packets are sent to the network element directly or via the other router. An alternative method can be also used in which two BFD sessions are configured per peer interface, one per router. A higher amount of BFD sessions is required then, but the alternative method does not depend on the routing protocol in the router side.
This feature can be used with either one or two physical connections to the backhaul network. In the single backhaul link scenario, the NE utilizes one backhaul interface which is connected to the L2 network to two or more routers. In dual backhaul link network scenario, the internal switch within the NE is in use. This enables a scenario in which two routers are directly connected via two backhaul interfaces.
84
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Figure 7
Descriptions of transport and transmission features
Single backhaul link network scenario primarypath BFD
secondarypath
Figure 8
Dual backhaul link network scenario
primarypath BFD
secondarypath
3.12.1.4
System impact Interdependencies between features This feature requires the features: • •
SR000386: QoS Aware Ethernet Switching SR000589: IPv4/IPv6 Transport Stack
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: •
3.12.1.5
The feature provides support for up to 16 BFD sessions - one BFD session can be determined with relation to one action trigger.
SR000344: Fast IP Rerouting management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Issue: 01E
DN09218825
85
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Alarms and faults There are no alarms and faults related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 35: New parameters lists parameters introduced with this feature. Table 35
New parameters
Full name
86
Abbreviated name
Managed object
List of static IPv4 routes
staticRoutes
IPRT
– trigger identifier
– triggerId
IPRT
– Preference value of the route
– preference
IPRT
Preference value of the route
preference
IPRTV6
trigger identifier
triggerId
IPRTV6
Feature activation flag for Fast IP Rerouting actFastIpRerouting
TNL
False to true delay
false2TrueDelay
TRIGGER
List of considerable items
itemList
TRIGGER
– Item identifier
– itemId
TRIGGER
– item pointer
– itemPointer
TRIGGER
Logical operation
logic
TRIGGER
State of the trigger
state
TRIGGER
TRIGGER object identifier
triggerId
TRIGGER
True to false delay
true2FalseDelay
TRIGGER
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.12.1.6
Descriptions of transport and transmission features
Sales information Table 36
Sales information
BSW/ASW
License control in network element
ASW
Pool License
License control attributes ON/OFF
3.13 SR000870: Flexible IP Addressing for PKI 3.13.1 Description of SR000870: Flexible IP Addressing for PKI Introduction to the feature This feature enables the usage of a dedicated IP address for Public Key Infrastructure (PKI)/certificate management procedures in the SBTS.
3.13.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature allows to deploy Internet Protocol Security (IPsec) for the management plane (M-plane) without applying IPsec to PKI/certificate management traffic. If it is not possible to reach the PKI system from the SBTS M-plane address, this feature allows to configure a dedicated IP address for certificate management operations in SBTS. This adress can be different from the M-plane address.
3.13.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.13.1.3
Functional description This feature enables the use of an arbitrary IP address for PKI/certificate management procedures. This is particularly useful, when the PKI systems, like Certificate Management Protocol (CMP) or Lightweight Directory Access Protocol (LDAP) server, cannot be reached from the SBTS M-plane address, for example when all traffic from this address is expected to be encapsulated by IPsec. In case that certificate management traffic is not encrypted, usually an SBTS network interface IP address is used as the IP address for certificate management. Certificate Management Protocol (CMP) is an example of certificate management trafic. The IP address used by certificate management can be dedicated for this purpose or shared with other applications, such as M-plane. By default M-plane IP address is used for certificate management.
Issue: 01E
DN09218825
87
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
When CMP or Lightweight Directory Access Protocol (LDAP) uses the IPsec tunnel, the CMP/LDAP SBTS IP address should be the M-plane IP address. Figure 9 NewIP addressin backhaul domain
Flexible IP Addressing for PKI
Unprotected domain(backhaul)
CA
eNB CA
M
SEG I
U
IPsec Tunnel
C
VirtualIP address
EPC (protecteddomain)
InterfaceIP address
3.13.1.4
System impact Interdependencies between features This information is to be provided in a further delivery. Impact on interfaces This information is to be provided in a further delivery. Impact on network and network element management tools This information is to be provided in a further delivery. Impact on system performance and capacity This information is to be provided in a further delivery.
3.13.1.5
SR000870: Flexible IP Addressing for PKI management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature.
88
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 37: New parameters lists parameters introduced with this feature. Table 37
New parameters
Full name
Abbreviated name
Source IP address used for CMP/CRL Servers
3.13.1.6
srcIpForCmpCrl
Managed object CERTH
Sales information Table 38
Sales information
BSW/ASW
License control in network element
BSW
-
3.14 SR000360: IP Transport Network Measurements 3.14.1 Description of SR000360: IP Transport Network Measurements Introduction to the feature This feature provides an active measurement and supervision of the IP transport network conditions in the mobile backhaul between two points. The measurement procedures are defined in the RFC862 document and in Appendix I in the RFC5357 document. The measurement point can be the SBTS, the RNC, the site router (with the UDP echo mechanism only), and an external additional measurement equipment. The measurement originator generates the test traffic and analyzes the outcomes of the measurement. The measurement responder must transmit back the test traffic to the measurement originator.
3.14.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits
Issue: 01E
DN09218825
89
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
This feature provides that the operator is able to monitor the IP transport network conditions and quickly identify the potential service degradations. The measurements provide an indication of potential violations against Service Level Agreement (SLA). In addition, the built-in network measurements obsolete the need for an external measurement equipment for IP transport network supervision and troubleshooting.
3.14.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.14.1.3
Functional description Overview This feature provides an active measurement and supervision of the IP transport network conditions in the mobile backhaul between two points. The measurement procedures are defined in the RFC862 document and in Appendix I in the RFC5357 document. The measurement point can be the SBTS, the RNC, the site router (with the UDP echo mechanism only), and an external additional measurement equipment. The measurement originator generates the test traffic and analyzes the outcomes of the measurement. The measurement responder must transmit back the test traffic to the measurement originator. The aim of the measurement is to make an estimation of the performance and quality of the mobile backhaul for each QoS class independently, provided with different and configurable DiffServ Code points. The measurement configuration can be done through the management interface/commissioning file of the certain network element. The feature provides support for three different measurement mechanisms which can be configured on the SBTS - the TWAMP sender mechanism, the TWAMP responder mechanism (reflector), and the UDP echo mechanism. The UDP echo mechanism is provided to support the measurement originators without the TWAMP measurement mechanisms, as determined in the RFC862 document. The SBTS can be the measurement originator or only the measurement responder. When an SBTS is the measurement originator, the SBTS generates the test traffic, adds the timestamp in the moment when transmitting the test traffic to the measurement responder, adds the another timestamp when receiving back the test traffic, analyzes the outcomes of the measurement, and generates statistics provided to the operator. When an SBTS is the measurement responder, the SBTS adds the timestamp when receiving the test traffic, and adds the another timestamp when the test traffic is transmitted back to the measurement originator. The UDP echo mechanism reflects the UDP echo test traffic originated from other network elements and just transmits back the test traffic without adding any timestamps. The feature provides support for up to 10 TWAMP sender measurement sessions configured on the SBTS. The TWAMP sender measurement sessions can be active concurrently. When the condition of the IP transport network falls below a certain configured threshold, the alarms are raised. The maximum rate of the incoming combined UDP echo traffic and TWAMP traffic is limited to 100pps in the SBTS. The measurements gathered at the sender point are: Round-trip time (RTT) measurement provided as Maximum, Minimum, and Average Packet Delay, and the Packet Loss measurement. The measurements can be stopped manually.
90
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Example #1 This example measurement configuration includes the SBTS in any RAT mode (which means WCDMA mode, LTE mode, and GSM mode) and the external additional measurement equipment (for example Accedian V-NID). In this measurement configuration, the SBTS operates as the TWAMP sender, and the external additional measurement equipment utilizes the UDP echo mechanism or the TWAMP responder mechanism. The additional measurement equipment is connected to the site router. During the configuration of the measurement, the operator must provide the measurement source and destination ports. The configuration can be done through the management interface/commissioning file. The TWAMP measurement source port defined for the SBTS is the port number from the range 5001–5010. The measurement destination port for the additional equipment acting as the TWAMP responder must be configured based on the additional equipment documentation. The UDP echo mechanism utilizes the destination standardized port number 7. When an SBTS is the measurement originator, the SBTS generates the test traffic, adds the timestamp in the moment when transmitting the test traffic to the measurement responder, adds the another timestamp when receiving back the test traffic, analyzes the outcomes of the measurement, and generates statistics provided to the operator. Figure 10
Example measurement configuration with SBTS in any RAT mode #1
MME
TWAMP TEST MESSAGES
SBTS!RUNS TWAMP SENDER AT PORTS!5001 TO!5010
SAE-GW
SITE!ROUTER
ToP MASTER
CARRIER!ETHERNET SBTS – ANY RAT MODE TWAMP SENDER
BSC
RNC ACCEDIAN!V-NID!SUPPORTS!RFC862 AND RUNS!UDP ECHO!SERVER AT PORT 7 OR ACCEDIAN!V-NID!SUPPORTS!RFC5357 AND RUNS TWAMP REFLECTOR AT DEFINED!PORT
Issue: 01E
DN09218825
ACCEDIAN!V-NID UDP ECHO!SERVER OR TWAMP REFLECTOR
91
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Example #2 This example measurement configuration includes the SBTS in any RAT mode (which means WCDMA mode, LTE mode, and GSM mode) and the external additional measurement equipment (for example Accedian V-NID). In this measurement configuration, the external additional measurement equipment is the TWAMP sender, and the SBTS utilizes the UDP echo mechanism or the TWAMP responder mechanism. During the configuration of the measurement, the operator must provide the measurement source and destination ports. The configuration can be done through the management interface/commissioning file. The measurement source port for the external additional measurement equipment, which operates as the TWAMP sender, must be configured based on the additional equipment documentation. The measurement destination port defined for the SBTS is the port number 5018. The UDP echo mechanism utilizes the destination standardized port number 7. When an SBTS is the measurement responder, the SBTS adds the timestamp when receiving the test traffic, and adds the another timestamp when the test traffic is transmitted back to the measurement originator. The UDP echo mechanism reflects the UDP echo test traffic originated from other network elements and just transmits back the test traffic without adding any timestamps. Figure 11
Example measurement configuration with SBTS in any RAT mode #2
MME
TWAMP TEST MESSAGES
SBTS!RUNS!UDP ECHO!SERVER AT PORT 7 OR SBTS!RUNS TWAMP REFLECTOR AT PORT 5018
SAE-GW
SITE!ROUTER
ToP MASTER
CARRIER!ETHERNET SBTS – ANY RAT MODE UDP ECHO!SERVER OR TWAMP REFLECTOR
BSC
RNC ACCEDIAN!V-NID!SUPPORTS!RFC5357 AND RUNS TWAMP SENDER AT DEFINED!PORT
ACCEDIAN V-NID TWAMP SENDER
92
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Example #3 This example measurement configuration comprises the SBTS in WCDMA mode only and the RNC. In this measurement configuration, the SBTS utilizes the TWAMP sender mechanism, and the RNC utilizes the UDP echo mechanism or the TWAMP responder mechanism. During the configuration of the measurement, the operator must provide the measurement source and destination ports. The configuration can be done through the management interface/commissioning file. The TWAMP measurement source port defined for the SBTS is the port number from the range 5001–5010. The measurement destination port defined for the RNC is the port number 1000. The UDP echo mechanism utilizes the destination standardized port number 7. When an SBTS is the measurement originator, the SBTS generates the test traffic, adds the timestamp in the moment when transmitting the test traffic to the measurement responder, adds the another timestamp when receiving back the test traffic, analyzes the outcomes of the measurement, and generates statistics provided to the operator. Figure 12
Example measurement configuration with SBTS in WCDMA mode #1
TWAMP TEST MESSAGES!VIA IUB!INTERFACE
SBTS!RUNS TWAMP SENDER AT PORTS!5001 TO!5010
SITE!ROUTER
MME
SAE-GW
ToP MASTER
CARRIER!ETHERNET SBTS – WCDMA MODE TWAMP SENDER
BSC
RNC!SUPPORTS!RAN1900 THAT RUNS!UDP ECHO!SERVER AT PORT 7 OR RNC!SUPPORTS!RAN2255 THAT RUNS TWAMP REFLECTOR AT PORT 1000
RNC UDP ECHO!SERVER OR TWAMP REFLECTOR
Example #4 This example measurement configuration comprises the SBTS in WCDMA mode only and the RNC. In this measurement configuration, the RNC utilizes the TWAMP sender mechanism, and the SBTS utilizes the UDP echo mechanism or the TWAMP responder mechanism. During the configuration of the measurement, the operator must provide the measurement source and destination ports. The configuration can be done through the management interface/commissioning file. The TWAMP measurement source port determined for the RNC is the port number 5000. The TWAMP measurement destination
Issue: 01E
DN09218825
93
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
port defined for the SBTS is the port number 5018. The UDP echo mechanism utilizes the destination standardized port number 7. When an SBTS is the measurement responder, the SBTS adds the timestamp when receiving the test traffic, and adds the another timestamp when the test traffic is transmitted back to the measurement originator. The UDP echo mechanism reflects the UDP echo test traffic originated from other network elements and just transmits back the test traffic without adding any timestamps. Figure 13
Example measurement configuration with SBTS in WCDMA mode #2
TWAMP TEST MESSAGES!VIA IUB!INTERFACE
SBTS!RUNS!UDP ECHO!SERVER AT PORT 7 OR SBTS!RUNS TWAMP REFLECTOR AT PORT 5018
SITE!ROUTER
MME
SAE-GW
ToP MASTER
CARRIER!ETHERNET SBTS – WCDMA MODE UDP ECHO!SERVER OR TWAMP REFLECTOR
BSC
RNC!SUPPORTS!RAN2255 THAT RUNS TWAMP SENDER AT PORT 5000
RNC TWAMP SENDER
Example #5 This example measurement configuration includes one SBTS in LTE mode only and the another one SBTS also in LTE mode only. One of them utilizes the TWAMP sender mechanism, and the other one utilizes the TWAMP responder mechanism. During the configuration of the measurement, the operator must provide the measurement source and destination ports. The measurement configuration can be done through the management interface/commissioning file. The TWAMP measurement source port defined for the SBTS is the port number from the range 5001–5010 and the TWAMP measurement destination port is the port number 5018. When an SBTS is the measurement originator, the SBTS generates the test traffic, adds the timestamp in the moment when transmitting the test traffic to the measurement responder, adds the another timestamp when receiving back the test traffic, analyzes the outcomes of the measurement, and generates statistics provided to the operator. When an SBTS is the measurement responder, the SBTS adds the timestamp when receiving the test traffic, and adds the another timestamp when the test traffic is transmitted back to the
94
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
measurement originator. The UDP echo mechanism reflects the UDP echo test traffic originated from other network elements and just transmits back the test traffic without adding any timestamps. Figure 14
Example measurement configuration with SBTS in LTE mode
TWAMP TEST MESSAGES!VIA S1/X2!INTERFACE
MME
SBTS!RUNS TWAMP SENDER AT PORTS!5001 TO!5010 SAE-GW
SITE!ROUTER
SBTS – LTE!MODE TWAMP SENDER
ToP MASTER
CARRIER!ETHERNET
BSC
SBTS – LTE!MODE TWAMP REFLECTOR RNC SBTS!RUNS TWAMP REFLECTOR AT PORT 5018
Example #6 This example measurement configuration includes the SBTS in any RAT mode (which means WCDMA mode, LTE mode, and GSM mode) and the site router. In this measurement configuration, the SBTS is the TWAMP sender, and the site router can be configured as the UDP echo mechanism only (currently there are no site routers which provide complete support for the TWAMP measurement mechanisms). During the configuration of the measurement, the operator must provide the measurement source and destination ports. The measurement configuration can be done through the management interface/commissioning file. The TWAMP measurement source port defined for the SBTS is the port number from the range 5001–5010. The UDP echo mechanism utilizes the destination standardized port number 7. When an SBTS is the measurement originator, the SBTS generates the test traffic, adds the timestamp in the moment when transmitting the test traffic to the measurement responder, adds the another timestamp when receiving back the test traffic, analyzes the outcomes of the measurement, and generates statistics provided to the operator.
Issue: 01E
DN09218825
95
Descriptions of transport and transmission features
Figure 15
SRAN 16.2, Feature Descriptions
Example measurement configuration with SBTS in any RAT mode #3
MME
TWAMP TEST MESSAGES
SBTS!RUNS TWAMP SENDER AT PORTS!5001 TO!5010
SITE!ROUTER UDP ECHO!SERVER
SAE-GW
ToP MASTER
CARRIER!ETHERNET SBTS – ANY RAT MODE TWAMP SENDER
BSC
SITE!ROUTER!SUPPORTS!RFC862 AND RUNS!UDP ECHO!SERVER AT PORT 7
3.14.1.4
RNC
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has an impact on network element management tools as beneath: •
The feature provides means for an active measurement of the IP transport network conditions.
Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: •
• •
96
The feature provides support for up to 10 TWAMP sender measurement sessions configured on the SBTS. The TWAMP sender measurement sessions can be active concurrently. The feature provides the measurement which has a minor influence on the SBTS performance when transceiving the measurement traffic. The feature provides the measurement in which the TWAMP and UDP traffic has a minor influence on the capacity of the transport interface, and the operator must consider this capacity.
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.14.1.5
Descriptions of transport and transmission features
SR000360: IP Transport Network Measurements management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults Table 39: New alarms and faults lists alarms and faults introduced with this feature. Table 39
BTS Fault ID
New alarms and faults
BTS Fault name
Reported alarms
61610
TWAMP RTT threshold crossed on session $id
61610 TWAMP RTT threshold crossed
61611
TWAMP PLR threshold crossed on session $id
61611 TWAMP PLR threshold crossed
Measurements and counters Table 40: New counters lists counters introduced with this feature. Table 40
New counters
Counter ID
Counter name
Measurement
M51331C0
avgRTT
TWAMP Statistics
M51331C1
maxRTT
TWAMP Statistics
M51331C2
minRTT
TWAMP Statistics
M51331C3
lostTwampMessages
TWAMP Statistics
M51331C4
txTwampMessages
TWAMP Statistics
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 41: New parameters lists parameters introduced with this feature. Table 41
New parameters
Full name
Abbreviated name
IP applications object identifier
Issue: 01E
DN09218825
ipAppId
Managed object IPAPP
97
Descriptions of transport and transmission features
Table 41
New parameters (Cont.)
Full name
3.14.1.6
Abbreviated name
Managed object
TWAMP reflector and udp echo flag config per IP address
twampReflectorConfig
IPAPP
– TWAMP reflector enabled
– twampReflectorEnabled
IPAPP
– TWAMP application or IP interface address
– twampReflectorLocalIpAddre ss
IPAPP
– TWAMP reflector udp echo enabled
– twampReflectorUdpEchoEna bled
IPAPP
Rate at which TWAMP sender sends out messages
twampSenderMessageRate
IPAPP
TWAMP statistics measurement interval
twampStatisticsInterval
PM
Administartive State of the TWAMP measurement session
administrativeState
TWAMP
TWAMP session destination IP address
destIpAddress
TWAMP
TWAMP session destination port
destPort
TWAMP
TWAMP test message size
messageSize
TWAMP
Packet loss ratio alarm threshold
plrAlarmThreshold
TWAMP
Round-trip-time alarm threshold
rttAlarmThreshold
TWAMP
TWAMP initiator messages source IP address
sourceIpAddress
TWAMP
DSCP value for TWAMP message transmission
twampDscp
TWAMP
Twamp object identifier
twampId
TWAMP
Sales information Table 42
98
SRAN 16.2, Feature Descriptions
Sales information
BSW/ASW
License control in network element
ASW
Pool License
DN09218825
License control attributes ON/OFF
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
3.15 SR000439: IPSec Emergency Bypass 3.15.1 Description of SR000439: IPSec Emergency Bypass Introduction to the feature This feature provides the possibility to completely deactivate the IPsec function at the SBTS in case of a severe IPsec failure. After deactivating IPsec, the SBTS enters into IPsec Emergency Bypass mode. The switching between IPsec Emergency Bypass mode and IPsec mode is exclusively controlled by the operator and does not require a site visit.
3.15.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • •
3.15.1.2
limiting the mobile services outage time in case of a severe IPsec cluster failure remote SBTS management (even if management plane is protected by IPsec)
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.15.1.3
Functional description The SBTS supervises the status of the configured IPsec tunnels. An IPsec tunnel is defined as Internet Key Exchange security association (IKE SA) with one or more related IPsec security associations (IPsec SAs). In case SBTS cannot establish an IKE SA and/or IPsec SA or an established one becomes non-operational it enters into IPsec Emergency Bypass probing state. During the probing state the following operations are performed: • •
SBTS continuously tries to re-establish non-operational SAs. SBTS periodically attempts to reach an operator controlled server to check permissions for switching off IPsec. The IP address of the control server and the timer that specifies in what time interval SBTS accesses the control server are configurable.
Entering the probing state after a failure takes up to five minutes. The exact time depends on the nature of the failure and dead peer detection (DPD). If SBTS in probing state manages to reestablish all failed SAs, it exits the probing state. After identifying a severe IPsec failure, the operator makes the control server accessible, for example by reconfiguring the core network edge router and/or the security gateway. If the control server is accessible and provides the valid return message, SBTS enters into IPsec Emergency Bypass active state.
Issue: 01E
DN09218825
99
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
In the IPsec Emergency Bypass active state all traffic is sent unprotected. Consequently, only unprotected ingress traffic is accepted. SBTS exits the IPsec Emergency Bypass active state after receiving an operator command from SBTS management interface or after SBTS reboot. After exiting IPsec Emergency Bypass active state, IPsec is operational again and SBTS tries to establish all SAs. The feature does not allow switching-off IPsec selectively per policy, but deactivates IPsec completely. Thus it is not suitable for scenarios where multiple security gateways are connected to the SBTS (in this case SR000600: Backup IPsec Tunnel is a more suitable alternative). Figure 16
Traffic path depending on the SBTS mode
Control Server
Permissioncheckoutside tunnel
Untrusted network
Trusted network
BTS
NormalIPsecmode IPsecbypassmode
3.15.1.4
SecurityGW
System impact Interdependencies between features This feature requires the following feature: •
SR000356: IPsec for BTS
Related feature: •
SR000600: Backup IPsec Tunnel
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
100
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.15.1.5
Descriptions of transport and transmission features
SR000439: IPSec Emergency Bypass management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 43: New alarms lists alarms introduced with this feature. Table 43
New alarms
Alarm ID 61639
Alarm name IPsec emergency bypass active
BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 44: New parameters lists parameters introduced with this feature. Table 44
New parameters
Full name
3.15.1.6
Managed object
IPsec emergency bypass control server IP address
ipSecEmBypassCtrlIpAddr
IPSECC
IPsec emergency bypass exit active state request
ipSecEmBypassExit
IPSECC
IPsec emergency bypass ping timer
ipSecEmBypassPingTimer
IPSECC
IPsec emergency bypass state
ipSecEmBypassState
IPSECC
Sales information Table 45
Issue: 01E
Abbreviated name
Sales information
BSW/ASW
License control in network element
BSW
-
DN09218825
101
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
3.16 SR000356: IPsec for BTS 3.16.1 Description of SR000356: IPsec for BTS Introduction to the feature This feature introduces IPsec for the SBTS. This functionality provides encryption, integrity protection, and communication peer authentication according to 3GPP standard TS33.210. The feature applies to the backhaul interfaces.
3.16.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides increased security of the control, user, synchronization and management planes on Transport Network Layer. The IPsec function is compliant with Internet Engineering Task Force (IETF) standards and the 3GPP defined IP layer security architecture.
3.16.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.16.1.3
Functional description IPsec can be applied to all SBTS-initiated and SBTS-terminated IP traffic but it can also be globally disabled. IPsec connections to different peer-entities can be configured independently in terms of security settings (for example different setting for neighboring SBTSs, core nodes, and selected planes). Selected connections to remote peers can be excluded from IPsec (bypassing traffic). The SBTS supports: • • •
multiple Internet Key Exchange (IKE) security associations (SAa) multiple IPsec security associations (SAs) multiple IPsec security associations per IKE security association
The capabilities supported by IPsec: •
services: – – – –
•
protocols: –
102
confidentiality integrity protection data origin authentication anti-replay protection
encapsulating security payload (ESP, according to RFC4303)
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
• • •
•
– –
– –
– – – –
IKEv2 (according to RFC5996) Diffie-Hellman: Group 2 (1024-bit MODP) Diffie-Hellman: Group 14 (2048-bit MODP) dead peer detection perfect forward secrecy
pseudo-random function: –
•
digital certificates in X.509v3 format
key exchange: –
•
IP address fully qualified domain name (FQDN) distinguished name
data used for authentication: –
•
HMAC-SHA1-96 (according to RFC2404)
data used for identification: –
•
AES-CBC with 128-bit key (according to RFC3602) 3DES (according to RFC2451 and RFC2405) NULL (according to RFC2410)
integrity protection algorithm: –
•
sequence number: 32-bit or 64-bit (extended sequence numbers, ESN) tunnel mode for encrypted packets the DSCP value of the inner packet is copied to the outer packet
encryption/ciphering algorithms: –
•
Descriptions of transport and transmission features
HMAC-SHA1 (according to RFC2104)
security association establishment modes: – –
initiator/responder mode (SBTS initiates IKE SAs and related IPsec SAs as needed, but also responds to establishments requests from the peer) responder only mode (SBTS never actively initiates IKE SAs and related IPsec SAs, but only waits for establishments requests from the peer)
Further aspects of the IP security implementation: • • • • • •
Issue: 01E
control, user, management, and synchronization plane traffic separation is supported IPsec tunnels can terminate either at interface IP address or virtual IP address simultaneous transport of inner IPv4 and IPv6 packets within one IPv4 IPsec tunnel is supported simultaneous use of other security protocols is possible (for example TLS) compatible with self-organizing networks (SON) auto-connection mechanism narrowing function for the traffic selector is provided
DN09218825
103
Descriptions of transport and transmission features
3.16.1.4
SRAN 16.2, Feature Descriptions
System impact Interdependencies between features This feature requires the following features: •
SR000589: IPv4/IPv6 Transport Stack
This feature is a precondition for the following features: • •
SR000439: IPSec Emergency Bypass SR000600: Backup IPsec Tunnel
Related features: • • •
SR000908: SBTS Crypto Agent SR000366: BTS Firewall SR000845: SBTS Operator Certificate Management
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity Application of IPsec adds additional overhead to the backhaul traffic, thus impacting transmission efficiency.
3.16.1.5
SR000356: IPsec for BTS management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 46: New alarms lists alarms introduced with this feature. Table 46
New alarms
Alarm ID
Alarm name
61644
IKE authentication failure
61645
IKE SA failure
61646
IPSec SA failure
61030
Dead Peer Detected
BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters
104
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Table 47: New counters lists counters introduced with this feature. Table 47
New counters
Counter ID
Counter name
Measurement
M51216C0
receivedESPpackets
IPSEC SA Statistics
M51216C1
antiReplayErrors
IPSEC SA Statistics
M51216C2
espCryptographicErrors
IPSEC SA Statistics
M51216C3
trafficSelectorMismatch
IPSEC SA Statistics
M51216C4
sentESPPackets
IPSEC SA Statistics
M51217C0
sentPacketMatchDiscPol
IPSEC Statistics
M51217C1
ipsecSaNotFound
IPSEC Statistics
M51217C2
receivedPacketMatchDefPol
IPSEC Statistics
M51217C3
receivedPacketMatchBypassPol
IPSEC Statistics
M51217C4
receivedPacketMatchDiscPol
IPSEC Statistics
M51217C5
recvUnprotPacketMatchProtPol
IPSEC Statistics
M51217C6
sentPacketMatchDefPol
IPSEC Statistics
M51217C7
sentPacketBypassPol
IPSEC Statistics
M51217C8
failedSAEstablishments
IPSEC Statistics
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 48: New parameters lists parameters introduced with this feature. Table 48
New parameters
Full name
Issue: 01E
Abbreviated name
Managed object
IKE SA connection establishment mode
connectionEstablishmentMod IKEP e
DPD delay time
dpdDelay
IKEP
IKE diffie-hellman group
ikeDiffHellGrp
IKEP
IKE layer encryption method
ikeEncryptionMethod
IKEP
DN09218825
105
Descriptions of transport and transmission features
Table 48
New parameters (Cont.)
Full name
106
SRAN 16.2, Feature Descriptions
Abbreviated name
Managed object
IKE association maximum lifetime
ikeMaxLifeTime
IKEP
IKE SA configuration object identifier
ikepId
IKEP
IPsec perfect forward secrecy enabled
ipsecPerfForwSecEnabled
IKEP
Local IPsec tunnel endpoint IP address
localTunnelEndpoint
IKEP
Remote IPsec tunnel endpoint IP address
remoteTunnelEndpoint
IKEP
User label
userLabel
IKEP
IKE DSCP
ikeDscp
IPSECC
IP fragmentation algorithm selection for IPsec Tunnels
ipFragmentationAlgorithm
IPSECC
IPsec enabling switch
ipSecEnabled
IPSECC
IPsec configuration identifier
ipSeccId
IPSECC
Anti-replay enabling switch
antiReplayEnabled
IPSECP
Size of the anti-replay window
antiReplayWindowSize
IPSECP
Encryption method
encryptionMethod
IPSECP
Extended sequence number mode
extendedSequenceNumberM IPSECP ode
IPsec profile object identifier
ipSecpId
IPSECP
PFS Diffie-Hellman group
pfsDiffHellGrp
IPSECP
Security association maximum lifetime
saMaxLifeTime
IPSECP
User label
userLabel
IPSECP
IPSec SA statistics measurement interval
ipSecSaStatisticsInterval
PM
IPSec statistics measurement interval
ipSecStatisticsInterval
PM
IKE profile reference
ikepRef
SECPOL
IPsec action status
ipSecAction
SECPOL
IPsec profile identifier
ipsecpId
SECPOL
Policy order number
policyOrderNumber
SECPOL
Security policy configuration object identifier
secPolId
SECPOL
Traffic selector list
trafficSelectorList
SECPOL
Local IP address
localIpAddress
SECPOL
Port number of the local IP address
localIpPort
SECPOL
Local IP prefix length
localIpPrefixLength
SECPOL
Protocol information
protocol
SECPOL
Remote IP address
remoteIpAddress
SECPOL
Port of the remote IP address
remoteIpPort
SECPOL
Remote IP prefix length
remoteIpPrefixLength
SECPOL
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 48
Descriptions of transport and transmission features
New parameters (Cont.)
Full name
Abbreviated name
User label
3.16.1.6
userLabel
Managed object SECPOL
Sales information Table 49
Sales information
BSW/ASW
License control in network element
ASW
Pool license
3.17 SR000396: IPv4 based Iub 3.17.1 Description of SR000396: IPv4 based Iub Introduction to the feature This feature provides SBTS with functionalities that support the WCDMA Iub interface user plane and control plane.
3.17.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides cost efficient transport network for Iub traffic. As a result of this OPEX and CAPEX savings are achieved.
3.17.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.17.1.3
Functional description This feature, together with selected SRAN transport features, is referred to as WCDMA Adapter and can perform WCDMA NodeB transport functions. The feature provides WCDMA-specific functionalities that support WCDMA Iub interface user plane and control plane (U-plane and C-plane). IPv4 based Iub is supported over Ethernet or ML-PPP.
g
Issue: 01E
Note: The management plane (M-plane) common for all RATs is specified in SR001003: IPv4 based SBTS Management Plane.
DN09218825
107
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
This feature makes use of IPv4 transport functions (including UDP, TCP, and SCTP) introduced by the feature SR000589: IPv4/IPv6 Transport Stack, and provides the following WCDMA applications: • •
WCDMA U-plane transport over FP/UDP/IPv4 (compliant with 3GPP 25.434, 25.426) WCDMA C-plane transport over SCTP/IPv4 (compliant with 3GPP 25.432)
This feature allows binding the configured IP addresses to: • •
WCDMA user plane WCDMA control plane
In the simplest configuration all U/C-plane WCDMA applications are bound to a single IP interface address. The operator can also configure separate IP addresses for each WCDMA application. Applications can be bound to interface IP addresses (including plain, logical and alias IP addresses) or to virtual IP addresses. This feature provides configurable traffic marking for the WCDMA traffic: • •
DSCP values for the U-plane uplink traffic are received by C-plane signaling (NBAP). DSCP value for C-plane traffic is manually configurable through the management system.
Additionally, the Connection Admission Control (CAC) procedure is used to ensure that there are enough transport resources to handle a newly requested call with the required quality of service (QoS). • •
WCDMA BTS (NodeB) performs CAC for U-plane data in uplink on Iub. RNC performs CAC for U-plane data in downlink.
CAC monitors whether there is a sufficient transport bandwidth available to provide a guaranteed bit rate for a new IP connection. The bit rate of a new IP connection is calculated based on parameters sent by RNC using NBAP. A new IP connection is accepted only if there is sufficient uplink capacity available. The bandwidth reservations for C- and M-planes are done through dimensioning and they are not performed by CAC.
3.17.1.4
System impact Interdependencies between features This feature requires the following features: • • • • •
SR000589: IPv4/IPv6 Transport Stack SR000402: BTS QoS Support for Terminated and Routed Traffic SR000382: Multiple VLAN interfaces SR000176: ML-PPP termination SR000350: Ethernet Termination
Related features: • •
SR000954: SBTS Common Transport SR001003: IPv4 based SBTS Management Plane
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools
108
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.17.1.5
SR000396: IPv4 based Iub management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 50: New parameters lists parameters introduced with this feature. Table 50
New parameters
Full name
Issue: 01E
Abbreviated name
Managed object
Control plane DSCP
cPlaneDscp
BTSSCW
List of control plane configurations
cPlaneList
BTSSCW
C-plane configurations list identifier
identifier
BTSSCW
IPv4 address
ipV4Address
BTSSCW
SCTP maximum payload size
sctpMaxPayloadSize
BTSSCW
Minimum SCTP port number
sctpPortMin
BTSSCW
RNC configuration
rncConfigList
BTSSCW
RNC identifier
identifier
BTSSCW
Far end SCTP subnet IP address
sctpFarEndSubnetIpAddress
BTSSCW
Far end SCTP subnet prefix length
sctpFarEndSubnetPrefixLeng BTSSCW th
DN09218825
109
Descriptions of transport and transmission features
Table 50
New parameters (Cont.)
Full name
3.17.1.6
SRAN 16.2, Feature Descriptions
Abbreviated name
Managed object
User plane IP address list
uPlaneList
BTSSCW
Committed bit rate
committedBitRate
BTSSCW
User plane configurations list identifier
identifier
BTSSCW
IPv4 address
ipV4Address
BTSSCW
Maximum UDP port number
udpPortMax
BTSSCW
Minimum UDP port number
udpPortMin
BTSSCW
Feature activation flag for IPv4 based Iub
actIpV4BasedIub
TNL
Sales information Table 51
Sales information
BSW/ASW
License control in network element
ASW
Pool license
3.18 SR000397: IPv4 based Packet Abis Transport 3.18.1 Description of SR000397: IPv4 based Packet Abis Transport Introduction to the feature This feature provides the GSM Packet Abis specific functionality to support IPv4 protocol over the Ethernet and TDM interfaces of the SBTS (user and control plane) as well as the SBTS remote management (management plane).
3.18.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides a more cost efficient transport network for the GSM Abis interface which results in OPEX and CAPEX savings.
110
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.18.1.2
Descriptions of transport and transmission features
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.18.1.3
Functional description The feature uses the IPv4 transport functions introduced by the feature SR000589: IPv4/IPv6 Transport Stack and provides functionalities to support GSM Packet Abis interface user and control plane of the SBTS as well as the SBTS management plane. Both Packet Abis over Ethernet and Packet Abis over TDM are supported. This feature provides the following GSM applications: • •
GSM user plane transport support based on NSN-RTP/UDP/IPv4 (compliant with 3GPP TR43.903) GSM control and management plane support based on SCTP/IPv4 (compliant with RFC4960)
IP addressing In the simplest configuration, all U/C/M-plane applications are bound to one single IP interface address. Applications can be bound to interface IP addresses (including alias IP addresses) or to virtual IP addresses. It is possible to configure up to four IP addresses: • • • •
GSM user plane circuit switched domain GSM user plane packet switched domain GSM control plane GSM OMUSIG management plane
The IP addresses are configured in the following way: • •
binding of the C/U-Plane applications is done based on the information sent by BSC using Abis O&M interface binding of the GSM OMUSIG M-plane applications is configured via SBTS O&M interface
Traffic marking Traffic in the U/C/M-plane is marked by the GSM RAT application: • •
DSCP values for GSM OMUSIG M-plane are configured using SBTS O&M interface DSCP values for U/C/M-Plane are sent by BSC using Abis O&M interface (these values overwrite the DSCP value configured for GSM OMUSIG M-plane)
Maximum transmission unit (MTU) size: To determine maximum packet size, the Path MTU Discovery (PMTUD) technique is used. This functionality is required to minimize fragmentation and avoid packet loss. PMTUD is automatically applied to U-plane IP addresses. Bandwidth congestion control The feature implements the bandwidth utilization measurement as well as the post processing of these measurements. The post processing is performed based on committed information rate (CIR) and utilization thresholds received from BSC.
Issue: 01E
DN09218825
111
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Delta t scheduling This feature uses delta t scheduling provided by the feature SR000402: BTS QoS Support for Terminated and Routed Traffic. This mechanism enables to establish the maximum age of a packet. Before sending, the transport software checks the age field and drops outdated packets. IP header compression This feature uses ML/MC-PPP and header compression support provided by the feature SR000176: ML-PPP termination. Packet Abis delay measurement This feature implements a UDP-based round-trip time (RTT) measurement which measures the RTT of GSM U-plane packets between SBTS and BSC. The RTT measurements are provided to BSC upon request. Counters This feature implements GSM specific counters for bandwidth utilization, SCTP, RTP and UDP. These counters are accessible via BSC.
3.18.1.4
System impact Interdependencies between features This feature requires the following features: • • • •
SR000589: IPv4/IPv6 Transport Stack SR000402: BTS QoS Support for Terminated and Routed Traffic SR000176: ML-PPP termination SR000954: SBTS Common Transport
Related features: • •
SR000918: SBTS Basic Performance Management SR000920: SBTS Fault Management
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.18.1.5
SR000397: IPv4 based Packet Abis Transport management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms
112
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 52: New parameters lists parameters introduced with this feature. Table 52
New parameters
Full name
Issue: 01E
Abbreviated name
Managed object
IUA acknowledge timer
iuaAckTimerOmuSig
BTSSCC
Management plane DSCP for OMUSIG
mPlaneDscpOmuSig
BTSSCC
Management plane local IP address for OMUSIG
mPlaneLocalIpAddressOmuS BTSSCC ig
Bundling enabled
sctpBundlingEnabledOmuSig BTSSCC
Heartbeat interval
sctpHbIntervalOmuSig
BTSSCC
SCTP maximum payload size
sctpMaxPayloadSize
BTSSCC
Maximum retransmission association
sctpMaxRetransAssocOmuSi BTSSCC g
Maximum retransmission path
sctpMaxRetransPathOmuSig
BTSSCC
Minimum SCTP port
sctpPortOmuSig
BTSSCC
Initial retransmission timeout
sctpRtoInitOmuSig
BTSSCC
Maximum retransmission timeout
sctpRtoMaxOmuSig
BTSSCC
Minimum retransmission timeout
sctpRtoMinOmuSig
BTSSCC
Selective acknowledge period
sctpSackPeriodOmuSig
BTSSCC
User-CS supervision packet timer value
ucsSupervisionPktTimerValue BTSSCC
UDP maximum datagram size
udpMaxDatagramSize
BTSSCC
User-PS supervision packet timer value
upsSupervisionPktTimerValu e
BTSSCC
Feature activation flag for IPv4 based Packet Abis TRS
actIpV4BasedPktAbTrs
TNL
DN09218825
113
Descriptions of transport and transmission features
3.18.1.6
SRAN 16.2, Feature Descriptions
Sales information Table 53
Sales information
BSW/ASW
License control in network element
ASW
Pool license
3.19 SR000395: IPv4 based S1/X2 3.19.1 Description of SR000395: IPv4 based S1/X2 Introduction to the feature This feature provides functionalities that support the LTE user and control plane on the S1 and X2 interfaces using IPv4 network protocol.
3.19.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides a 3GPP standard-conform backhaul solution for LTE S1 and X2 transport.
3.19.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.19.1.3
Functional description This feature, together with selected SRAN transport features, provides LTE-specific transport functionalities. Therefore, this feature is also called LTE Adapter. LTE Adapter can work as a dedicated eNB or concurrently with other Adapters (GSM-, WCDMA Adapter), as a part of SRAN technology. The feature provides LTE-specific functionalities to support: • •
LTE user plane and control plane (U-plane and C-plane) on S1 interface LTE user plane and control plane (U-plane and C-plane) on X2 interface
This feature utilizes IPv4 transport functions (including UDP, TCP, and SCTP) introduced by the feature SR000589: IPv4/IPv6 Transport Stack, and provides the following LTE applications: • •
LTE U-plane transport over GTP-U/UDP/IPv4 (compliant with 3GPP 36.414, 36.424) LTE C-plane transport over SCTP/IPv4 (compliant with 3GPP 36.412, 36.422)
This feature allows configured IP addresses to be bound to:
114
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
• •
Descriptions of transport and transmission features
LTE user plane (identical address for S1 and X2) LTE control plane (identical addresses for S1 and X2), for S1 SCTP multi-homing is supported (feature provides configurable secondary C-plane address)
It is also possible to configure one single IP address for all of the planes mentioned above. The applications can be bound to interface IP addresses (including plain, logical, and alias IP addresses) or to virtual IP addresses (binding is controlled by SR000589: IPv4/IPv6 Transport Stack feature). This feature provides configurable traffic marking for the LTE traffic: • •
DSCP values for the U-plane traffic (configurable per QCI value) DSCP values for the C-plane traffic (directly configurable through the management system)
Based on these markings, the generic capabilities provided by the SR000402: BTS QoS Support for Terminated and Routed Traffic feature are used to implement transport layer QoS. Additionally, SR000395: IPv4 based S1/X2 feature provides the Measurement Based Transport Admission Control (MB-TAC) function. The MB-TAC function admits further waiting guaranteed bit rate (GBR) connections as long as the measured total bit rate of all GBR connections does not exceed the configured transport capacity for GBR traffic.
3.19.1.4
System impact Interdependencies between features This feature requires the following feature: • •
SR000589: IPv4/IPv6 Transport Stack SR000402: BTS QoS Support for Terminated and Routed Traffic
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.19.1.5
SR000395: IPv4 based S1/X2 management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters
Issue: 01E
DN09218825
115
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Table 54: New counters lists counters introduced with this feature. Table 54
New counters
Counter ID
Counter name
Measurement
M51332C0
tacSuccessfulGbrNormal
S1 X2 TAC Statistics
M51332C1
tacSuccessfulGbrHandover
S1 X2 TAC Statistics
M51332C2
tacSuccessfulGbrEmergency
S1 X2 TAC Statistics
M51332C3
tacRejectedGbrNormal
S1 X2 TAC Statistics
M51332C4
tacRejectedGbrHandover
S1 X2 TAC Statistics
M51332C5
tacRejectedGbrEmergency
S1 X2 TAC Statistics
M51332C6
tacUlGbrRateMean
S1 X2 TAC Statistics
M51332C7
tacUlGbrRateMax
S1 X2 TAC Statistics
M51332C8
tacDlGbrRateMean
S1 X2 TAC Statistics
M51332C9
tacDlGbrRateMax
S1 X2 TAC Statistics
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 55: New parameters lists parameters introduced with this feature. Table 55
New parameters
Full name
116
Abbreviated name
Managed object
Control plane DSCP
cPlaneDscp
BTSSCL
Control plane configuration list
cPlaneList
BTSSCL
IPv4 address 1
ipV4Address1
BTSSCL
IPv4 address 2
ipV4Address2
BTSSCL
SCTP association failure retransmission counter
sctpAssociationMaxRetrans
BTSSCL
SCTP heartbeat message interval
sctpHeartbeatInterval
BTSSCL
SCTP maximum payload size
sctpMaxPayloadSize
BTSSCL
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 55
Descriptions of transport and transmission features
New parameters (Cont.)
Full name
g
Managed object
SCTP path failure retransmission counter
sctpPathMaxRetrans
BTSSCL
Maximum retransmission timeout
sctpRtoMax
BTSSCL
Minimum retransmission timeout
sctpRtoMin
BTSSCL
Selective acknowledge delay
sctpSackDelay
BTSSCL
Selective acknowledge frequency
sctpSackFreq
BTSSCL
Maximum time to wait for a new SCTP establishment
sctpSetUpTimeMax
BTSSCL
Wait time before starting SCTP init after shutdown
sctpWaitTimeInitSeqRetry
BTSSCL
Transport admission control
tacList
BTSSCL
TAC limit GBR emergency
tacLimitGbrEmergency
BTSSCL
TAC limit GBR handover
tacLimitGbrHandover
BTSSCL
TAC limit GBR normal
tacLimitGbrNormal
BTSSCL
User plane configuration list
uPlaneList
BTSSCL
IPv4 address 1
ipV4Address1
BTSSCL
TAC statistics measurement interval
s1X2TacStatisticsInterval
PM
Feature activation flag for IPv4 based S1 X2
actIpV4BasedS1X2
TNL
Note: With this feature, exactly one U-plane IP address (ipV4Address1) and two Cplane IP addresses (ipV4Address1, ipV4Address2) are supported. This means: • •
Issue: 01E
Abbreviated name
The ipV4Address1 entry below the User plane configuration list in the Table 55: New parameters is a subordinate element of the uPlaneList. The ipV4Address1 and ipV4Address2 entries below the Control plane configuration list in the Table 55: New parameters are subordinate elements of the cPlaneList.
DN09218825
117
Descriptions of transport and transmission features
3.19.1.6
SRAN 16.2, Feature Descriptions
Sales information Table 56
Sales information
BSW/ASW
License control in network element
ASW
Pool license
3.20 SR001003: IPv4 based SBTS Management Plane 3.20.1 Description of SR001003: IPv4 based SBTS Management Plane Introduction to the feature This feature provides the management plane connectivity from the SBTS towards Web UI and NetAct. The connectivity uses IPv4 transport stack. The presented feature also provides the IP Layer configuration parameters that are needed to connect the management plane from the SBTS towards Web UI and NetAct.
3.20.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the management plane connectivity from the SBTS towards Web UI and NetAct.
3.20.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.20.1.3
Functional description This feature provides the management plane connectivity from the SBTS towards Web UI and NetAct. The connectivity uses IP transport stack. The SBTS has exactly one management plane IP address, which can be dedicated to M-plane or shared with other applications. When sharing the management plane IP address with other applications, management plane traffic is identified by means of the Layer 4 protocol and the port number information. This feature binds the management plane applications to the appropriate IP addresses and L4 ports. Any port used for management connections cannot be shared by other applications on the same IP address and same transport protocol. The management plane can bind to interface IP address or virtual IP address. The presented feature also provides the IP Layer configuration parameters that are needed to connect the management plane from the SBTS towards Web UI and NetAct.
118
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
This feature enables to bind configured IP addresses to SBTS management plane TCP and UDP (NTP and DNS) using IP. Additional protocols (FTP, SOAP) are required. The management plane has own DSCP marking for the egress traffic which is directly configurable through the management system. The management plane supports the TLS1.2 encryption. The security of management plane interfaces can be increased by providing encryption, integrity protection and communication peer authentication with IPsec [RFC4301]. The management plane protection functions are optional features and provided with separate licenses. The protection functions are not within the content of the presented feature. The management plane consists of many applications using different Layer 4 protocols: UDP for the time retrieval through NTP and for DNS, and TCP for the SBTS NE3S connection towards Web UI and NetAct.
3.20.1.4
System impact Interdependencies between features This feature requires the feature: •
SR000589: IPv4/IPv6 Transport Stack
This feature affects the feature: •
SR000921: SBTS NE3S WS NetAct integration
This feature is the precondition for the feature: •
SR000954: SBTS Common Transport
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.20.1.5
SR001003: IPv4 based SBTS Management Plane management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults There are no alarms and faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters
Issue: 01E
DN09218825
119
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Table 57: New parameters lists parameters introduced with this feature. Table 57
New parameters
Full name
Abbreviated name
Management plane DSCP
mPlaneDscp
MPLANE
Management plane IP address of the SBTS mPlaneIpAddress
3.20.1.6
Managed object
MPLANE
Sales information Table 58
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
3.21 SR000589: IPv4/IPv6 Transport Stack 3.21.1 Description of SR000589: IPv4/IPv6 Transport Stack Introduction to the feature This feature provides a generic IPv4/IPv6 dual stack for the external network interfaces and therefore enables the IP transport mechanism in accordance with the 3GPP standards. The feature represents the generic IP Layer functions that can be used by the connections of the U-, C-, M-, and S-plane and by the transport network control plane protocols (for example BFD mechanism).
3.21.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the foundation for the IP-based Iub, IP-based S1/X2, IP-based M-, and S-plane, and IP-based Packet Abis, and thus enables to utilize the state-of-the-art and profitable packet transport in mobile backhaul.
3.21.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
120
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.21.1.3
Descriptions of transport and transmission features
Functional description This feature provides the IPv4/IPv6 dual stack for the external transport interfaces. This dual stack can be used for the connections of the U-, C-, M-, and S-plane, and for the transport network control plane protocols. This feature introduces only the Transport Layer foundation for these functions, the applications are subject to further features. IPv4 and IPv6 can be used simultaneously (dual stack support), but features which take advantage of this generic protocol stack may introduce configuration restrictions. The generic IPv6 functions (for example neighbor discovery) are active when at least one IPv6 address is defined in the SBTS. The generic multicast transmission is supported for IPv4 only since generic IPv6 multicast support is not provided within this feature. The SBTS supports static routing of packets which are generated by the SBTS itself. The mechanism is supported for all U-, C-, M-, and S-plane packets for both IPv4 and IPv6. In order to support redundant static routes, route preferences are provided (also for the default routes). IP packets are fragmented in accordance with configured Maximum Transmission Units (MTUs) of the different Data Link Layer interfaces and reassembled when needed. In addition, the feature provides a route MTU parameter permitting to control fragmentation for certain destination IP addresses/subnets. This can be used for distinguishing different target MTUs for different RATs. In addition, the support for the control of the SCTP and TCP segment sizes is provided with this feature in order to avoid fragmentation of these packets. Based on the RFC2460 standard, the IPv6 packets which are forwarded, are not fragmented and reassembled. This feature provides support for ICMPv4 and ICMPv6 for diagnosis and error reporting methods: ping, traceroute responder (UDP), and On demand Path MTU Discovery. The On demand Path MTU Discovery can be performed during commissioning and on user demand. The measured PMTU is displayed and in the case of a mismatch with the configured MTU, an alarm is raised. This feature introduces the generic IP termination functions that can be used on the provided types of address: physical interface address, logical (VLAN) interface address and virtual (loopback interface) address. The U-, C-, M-, and S-plane functions must be configured to these addresses with certain restrictions of use which may apply. In addition, an alias (secondary) IP address is supported for physical and logical interfaces. On the same interface, the alias addresses can be placed in the same subnet or in different subnets. The IP addresses on different logical interfaces (VLANs) or different physical interfaces need to be configured to different subnets. This feature provides support for UDP, TCP, and SCTP Transport Layer protocols. The UDP protocol is utilized for the user plane protocols, TCP protocol is utilized for the management plane protocols, and SCTP for the control plane and GSM management plane protocols. The SCTP support comprises of the single-homed, asymmetrically multi-homed (two IP addresses in the peer and only one in the SBTS), and symmetrically multi-homed (two IP addresses in both ends) methods. The SCTP associations endpoints can use a single or two different physical interfaces. The SBTS permits running different UDP, TCP, and SCTP based applications on the same IP address based on distinct Transport Layer port numbers.
Issue: 01E
DN09218825
121
Descriptions of transport and transmission features
Figure 17
SRAN 16.2, Feature Descriptions
IPv4/IPv6 Transport Stack GSM
WCDMA
LTE
UDP / TCP /SCTP IPv6
IPv4 Ethernet L1
IP /Ethernet Network
Ethernet
3.21.1.4
System impact Interdependencies between features This feature requires (not in Ethernet network configuration) the feature: •
SR000176: ML-PPP termination
This feature requires (not in ML-PPP network configuration) the feature: •
SR000350: Ethernet Termination
This feature is the precondition for the features: • • • • • • • • •
SR000344: Fast IP Rerouting SR000356: IPsec for BTS SR000395: IPv4 based S1/X2 SR000396: IPv4 based Iub SR000397: IPv4 based Packet Abis Transport SR000402: BTS QoS Support for Terminated and Routed Traffic SR000403: Source based routing in BTS SR000770: LTE Dual U-plane IP addresses SR001003: IPv4 based SBTS Management Plane
Impact on interfaces This feature has an impact on interfaces as beneath: •
The feature provides the IPv4/IPv6 dual stack for the external transport interfaces.
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.21.1.5
SR000589: IPv4/IPv6 Transport Stack management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults
122
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Table 59: New alarms and faults lists alarms and faults introduced with this feature. Table 59
BTS Fault ID 61632
New alarms and faults
BTS Fault name
Dup Addr detected $duplicateIpv6Address
Reported alarms
61632 Dup Addr detected $duplicateIpv6Address
Measurements and counters Table 60: New counters lists counters introduced with this feature. Table 60
New counters
Counter ID
Issue: 01E
Counter name
Measurement
M51321C0
ifInOctets
IP Interface Statistics
M51321C1
ifInPackets
IP Interface Statistics
M51321C2
ifOutOctets
IP Interface Statistics
M51321C3
ifOutPackets
IP Interface Statistics
M51321C4
ifInErrors
IP Interface Statistics
M51321C5
ifOutFragPackets
IP Interface Statistics
M51321C6
ifOutFragments
IP Interface Statistics
M51322C0
ipv4InOctets
IP V4 Address Statistics
M51322C1
ipv4InPackets
IP V4 Address Statistics
M51322C2
ipv4OutOctets
IP V4 Address Statistics
M51322C3
ipv4OutPackets
IP V4 Address Statistics
M51322C4
ipv4InReassembledPackets
IP V4 Address Statistics
M51322C5
ipv4InErrors
IP V4 Address Statistics
M51324C0
discIpReassemblyTimedoutPkts
IP Node Statistics
M51324C1
ipReassemblyError
IP Node Statistics
M51324C2
ipTooBigPackets
IP Node Statistics
M51325C0
tcpInPackets
TCP/UDP Statistics
DN09218825
123
Descriptions of transport and transmission features
Table 60
SRAN 16.2, Feature Descriptions
New counters (Cont.)
Counter ID
Counter name
Measurement
M51325C1
tcpInOctets
TCP/UDP Statistics
M51325C2
tcpOutPackets
TCP/UDP Statistics
M51325C3
tcpOutOctets
TCP/UDP Statistics
M51326C0
sctpInPackets
SCTP Statistics
M51326C1
sctpInOctets
SCTP Statistics
M51326C2
sctpOutPackets
SCTP Statistics
M51326C3
sctpOutOctets
SCTP Statistics
M51327C0
ipv6InOctets
IP V6 Address Statistics
M51327C1
ipv6InPackets
IP V6 Address Statistics
M51327C2
ipv6OutOctets
IP V6 Address Statistics
M51327C3
ipv6OutPackets
IP V6 Address Statistics
M51327C4
ipv6InReassembledPackets
IP V6 Address Statistics
M51327C5
ipv6InErrors
IP V6 Address Statistics
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 61: New parameters lists parameters introduced with this feature. Table 61
New parameters
Full name
124
Abbreviated name
Managed object
Layer 2 interface reference
interfacePtr
IPIF
Local IP address list
ipAddrList
IPIF
– Identifier of the IP address configuration
– ipAddrIdentifier
IPIF
– IP address
– localIpAddr
IPIF
– Local IP prefix length
– localIpPrefixLength
IPIF
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 61
Descriptions of transport and transmission features
New parameters (Cont.)
Full name
Issue: 01E
Abbreviated name
Managed object
IP interface object
ipIfId
IPIF
Maximum transfer unit
ipMtu
IPIF
User label
userLabel
IPIF
ARP cache validity period
arpCacheValidity
IPNO
ICMP DSCP
icmpDscp
IPNO
Enable response to ICMP traffic
icmpResponseEnabled
IPNO
IP node configuration identifier
ipNoId
IPNO
IP reassembly timeout
ipReassemblyTimeout
IPNO
Neighbor solicitation message retransmit timer
retransTimer
IPNO
IPv4 routing table identifier
ipRtId
IPRT
List of static IPv4 routes
staticRoutes
IPRT
– Destination IP address of the route
– destIpAddr
IPRT
– Destination IP prefix length
– destinationIpPrefixLength
IPRT
– IP address of the next hop of the route
– gateway
IPRT
– Preferred source IPv4 address
– preSrcIpv4Addr
IPRT
– IP mtu for the route
– routeIpMtu
IPRT
User label
userLabel
IPRT
IPv6 routing table identifier
ipRtV6Id
IPRTV6
Static IPv6 routes
staticIpv6Routes
IPRTV6
– Destination IPv6 address of the static route
– destIpv6Addr
IPRTV6
– Destination IPv6 prefix length
– destinationIpv6PrefixLength IPRTV6
– Gateway IPv6 address
– gatewayIpv6Addr
IPRTV6
– Preferred source IPv6 address
– preSrcIpv6Addr
IPRTV6
DN09218825
125
Descriptions of transport and transmission features
Table 61
SRAN 16.2, Feature Descriptions
New parameters (Cont.)
Full name
3.21.1.6
Abbreviated name
Managed object
– IP mtu for the route
– routeIpMtu
IPRTV6
User label
userLabel
IPRTV6
IP fragmentation algorithm selection for IPsec Tunnels
ipFragmentationAlgorithm
IPSECC
IPv4 multicast used link layer interface
ipIfId
MCAPP
Multicast application identifier
mcAppId
MCAPP
IP interface statistics measurement interval
ipInterfaceStatisticsInterval
PM
IP node measurement interval
ipNodeStatisticsInterval
PM
IP statistics measurement interval
ipV4InterfaceStatisticsInterval PM
IP statistics measurement interval
ipV6InterfaceStatisticsInterval PM
SCTP statistics measurement interval
sctpStatisticsInterval
PM
TCP UDP statistics measurement interval
tcpUdpStatisticsInterval
PM
Sales information Table 62
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
3.22 SR000361: Link Supervision with BFD 3.22.1 Description of SR000361: Link Supervision with BFD Introduction to the feature This feature supports supervision of the SBTS transport links using Bidirectional Forwarding Detection (BFD).
3.22.1.1
Benefits The SR000361: Link Supervision with BFD provides the following benefits:
126
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
• •
3.22.1.2
Descriptions of transport and transmission features
allows close monitoring of the transport connection allows quick failover in the downlink direction (when this feature is used together with HSRP-like mechanism, failover in the uplink direction is also ensured)
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.22.1.3
Functional description Bidirectional Forwarding Detection (BFD) is a link supervision protocol for monitoring connectivity in packet networks. This feature implements single-hop BFD (RFC5881) and multi-hop BFD (RFC5880) support. BFD establishes a session between the SBTS and a suitable peer entity such as an edge router, RNC/BSC or security gateway. Both ends start to send BFD control packets. If no BFD control packet is received from the peer within a negotiated BFD time interval, BFD reports a link failure. Single-hop BFD sessions are used to monitor IP connectivity between two directly connected systems, whereas multi-hop BFD sessions can be created among systems which are reachable through the IP layer. The main difference between single- and multihop BFD is the usage of the time-to-live (TTL) field in the BFD packets. BFD packets can be encapsulated into IPsec and carried inside an IPsec tunnel. In this scenario the peer of the respective BFD session needs to be capable of terminating IPsec or a security gateway (SecGW) needs to be located at the end of the tunnel in case a BFD session is established with a peer behind the SecGW. BFD is used as input for SR000344: Fast IP Rerouting feature. For the purpose of this feature one or more BFD sessions are coupled to so-called action triggers. The action triggers can be bound to routing entries in the routing table. Only asynchronous mode is supported, not demand mode or echo modes. Figure 18
Single-hop BFD session network scenario
Uplink/Downlink Traffic BFD
HSRP
Issue: 01E
DN09218825
127
Descriptions of transport and transmission features
3.22.1.4
SRAN 16.2, Feature Descriptions
System impact Interdependencies between features This feature requires an IP interface. The version of the IP interface and used link layer technology is not relevant for the BFD operation. However, IP version must be the same for the BFD session and the interface (for example IPv6 BFD session cannot be established on an IPv4 interface). This feature is the precondition for the feature: •
SR000344: Fast IP Rerouting
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity The ongoing BFD sessions increase the load in the network. Additional load depends on the number of BFD sessions, receive and transmit intervals of BFD packets and detection time which determines how fast the SBTS detects a failure. Increased load may affect network performance and capacity.
3.22.1.5
SR000361: Link Supervision with BFD management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 63: New alarms lists alarms introduced with this feature. Table 63
New alarms
Alarm ID
Alarm name
61022
BFD group $bfdGrpId down
61605
BFD $session down, ingress, $sourceIP to $destinationIP
61606
BFD $session down, egress, $sourceIP to $destinationIP
BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature.
128
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Parameters Table 64: New parameters lists parameters introduced with this feature. Table 64
New parameters
Full name
3.22.1.6
Managed object
BFD session activation
bfdActivation
BFD
BFD session admin down state control
bfdAdminUp
BFD
Destination IP address for the BFD session bfdDestIpAddr
BFD
BFD session lost packets detection time multiplier
bfdDetectMult
BFD
BFD dscp
bfdDscp
BFD
BFD session object identifer
bfdId
BFD
Source IP address for the BFD session
bfdSrcIpAddr
BFD
UDP source port of the BFD session
bfdSrcUdpPort
BFD
BFD session type
bfdType
BFD
Desired minimum BFD control word transmit interval
desMinTxInt
BFD
Required minimum BFD control word receive interval
reqMinRxInt
BFD
User label
userLabel
BFD
BFD group instance identifier
bfdGrpId
BFDGRP
Reference to or more BFD sessions
bfdIdList
BFDGRP
Sales information Table 65
Issue: 01E
Abbreviated name
Sales information
BSW/ASW
License control in network element
BSW
-
DN09218825
129
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
3.23 SR000465: Local and Remote IP Traffic Capturing 3.23.1 Description of SR000465: Local and Remote IP Traffic Capturing Introduction to the feature This feature enables capturing of ingress and egress IP traffic of the SBTS and to download it for later root cause analysis.
3.23.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • • • • • • •
3.23.1.2
Enables remote and local SBTS traffic capturing to detect unexpected SBTS behavior and evaluate network performance. Enables capturing of user, control, management, and synchronization plane traffic. Enables capturing of the IP packet transport including U-plane headers related to a single UE. Enables monitoring of decrypted traffic. Captured files can be included into the ticket to speed up root cause analysis and reduce time of problem resolving. Provides time, cost and effort savings due to lower number of site visits. Provides simple and reliable interface to configure the IP traffic capturing even in fault or congestion situations.
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.23.1.3
Functional description Feature overview This feature allows capturing of control, management, synchronization, and user plane IP packet information. Capturing of IPv4 and IPv6 packets is supported. Capturing of IP traffic is supported in two different ways: •
130
The IP packets are streamed to a storage device or a laptop connected to the Ethernet port of the SBTS (local management port or backhaul interface port). The IP packets can only be streamed to a storage device connected to the same LAN. The output data rate of local streaming via local management port is limited to Fast Ethernet since the local management port does not support Gigabit Ethernet. Local streaming towards a transport port supports Gigabit Ethernet.
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
•
Descriptions of transport and transmission features
The IP packets are captured into a compressed libpcap file which is stored in SBTS RAM. This file can be downloaded using local or a remote connection (for example with Network Operations Centre). The maximal size of a libpcap file before compression is 150 MB and it contains the capturing history concerning only limited period of time. The file can be optionally protected with a password. The reason for holding the libpcap file within RAM instead of flash memory is that the captured data cannot be hacked in case of SBTS hardware theft.
The feature is configured using a Web UI where a user selects the following: • •
capturing point whether to include or exclude U-plane traffic capturing Excluding U-plane traffic capturing maximizes the capturing duration. In order to maintain end user privacy and to comply with legal regulations in certain countries, user plane payload is never captured. If user plane is selected, only user plane header information is captured (UE level headers for LTE and transport headers for GSM and WCDMA).
Capture point Depending on the location of the selected capture point in the traffic path, different traffic is captured: •
•
IP traffic to/from the SBTS At this capture point the traffic is captured non-fragmented and IPsec decrypted (if IPsec is in use). TLS-encrypted M-plane is still encrypted (if TLS is in use). At this capture point downlink traffic is not filtered by the system firewall, uplink traffic has already passed it. Capturing at this point simplifies the troubleshooting since it allows accessing the decrypted traffic. The capturing is independent of the used data link layer protocol (for example Ethernet or IP/ML-PPP). IP traffic to/from the SBTS captured at the transport network interfaces At this capture point the traffic is captured fragmented and encrypted (if IPsec is in use). Only the first fragment is captured completely (except the end user plane payload or the encrypted part of the packet ciphered with IPsec), further fragments of a packet are captured only with their IP header information.
At both capture points, traffic is captured in both ingress and egress direction.
g
Note: In case of SBTS with multiple system modules, the capture points are located on the main system module. Figure 19
Traffic capturing mechanism Local Access
Network OperationsCenter LocalandRemote TrafficCapturing
IPsec BTS
Issue: 01E
O&M DCN
DN09218825
mcRNC,mcBSC MME/SAE
131
Descriptions of transport and transmission features
3.23.1.4
SRAN 16.2, Feature Descriptions
System impact Interdependencies between features Related feature: •
SR000350: Ethernet Termination
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity IP traffic capturing uses the same resources as normal SBTS services. Therefore, it is possible that concurrently run IP traffic capturing and SBTS services affect each others work. When there is high traffic it can result in captured packets being dropped.
3.23.1.5
SR000465: Local and Remote IP Traffic Capturing management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 66: New alarms lists alarms introduced with this feature. Table 66
New alarms
Alarm ID 61641
Alarm name IP Traffic Capturing Ongoing [port $port,] [mac $m]
BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
132
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.23.1.6
Descriptions of transport and transmission features
Sales information Table 67
Sales information
BSW/ASW
License control in network element
BSW
-
3.24 SR000770: LTE Dual U-plane IP addresses 3.24.1 Description of SR000770: LTE Dual U-plane IP addresses Introduction to the feature This feature introduces the possibility of using a second S1 U-plane IP address for SBTS. This functionality permits traffic separation based on two U-plane addresses.
3.24.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature allows the operator to distribute S1 U-plane traffic to two IP addresses. It enables the utilization of two physical Ethernet interfaces: 2xGE (Gigabit Ethernet) or 2xFE (Fast Ethernet). The backhaul transport traffic of the SBTS can exceed 1GE throughput. Different end to end paths through the transport network can be used at the same time. The UE flows are intact and remain in order.
3.24.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.24.1.3
Functional description Dual U-plane address selection algorithm for S1 traffic Path supervision The operator can supervise the availability of paths between SBTS and SGWs associated with dual U-plane addresses via the GPRS Tunneling Protocol – user plane (GTP-U) supervision path. The availability status of paths is then used to select the Uplane address. Paths for which no availability status information is provided are considered available by SBTS. Address assignment algorithm for S1 traffic A UE connected to the Single RAN system uses only one LTE Dual U-plane IP address for S1 user traffic. The address is selected during the context setup phase (Initial Context Setup or Handover).
Issue: 01E
DN09218825
133
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
The dual U-plane address selection algorithm for S1 traffic always selects the least used U-plane address. The usage of a U-plane address is measured by the number of UEs assigned to that address. This approach ensures optimum load distribution in an environment where connections are consecutively set up and released. If a path becomes temporarily unavailable and then becomes available again, this algorithm enforces fast return to an approximate 50% load distribution. It means that new connections are assigned to the respective U-plane address until 50% of UE distribution is accomplished. If both paths are unavailable and the connection between SBTS and SGW is lost, the UE traffic is handled as it normally would be, that is as if the feature was not implemented. If a GTP-U path becomes unavailable, all impacted UEs are released using S1 partial reset. This behavior continues independently, regardless if one or both paths become unavailable. The address selection algorithm has the following results: • • •
•
g
About half of the UEs are assigned to each U-plane address. Accordingly, on average 50% S1 user traffic load per U-plane IP address is expected over time. The assignment of U-plane IP address is based on load distribution. There is no distinction between traffic types because IP addresses are assigned per UE, not per bearer. GBR (guaranteed bit rate) and non-GBR (non-guaranteed bit rate) UE traffic goes over the same path. The external Ethernets are recommended to be of the same kind (both GE or FE but not mixed GE and FE). The reason is that the algorithm distributes the user traffic more or less equally to each U-plane address. Note: The FTIF is needed only in case the SR000770: LTE Dual U-plane IP addresses feature is used to distribute the U-plane traffic to different interfaces with the same physical layer (optical or electrical). The FTIF is not mandatory.
Dual U-plane address selection algorithm for X2 traffic (data forwarding) The X2 traffic of the UE is mapped to the main U-plane address U1. Compared to S1 traffic the X2 user traffic is small. Therefore a possible asymmetry in traffic load distribution is accepted. The following scenarios are used in case of path failure (S1 traffic): • •
If a path which is supervised via GTP-U supervision path is signaled as unavailable, all bearers associated with UEs connected over this path are released. The other UEs associated with the non-failing GTP-U path are not released and remain operational.
Dual U-plane address selection algorithm for X2 traffic uses the same mechanism as the GTPU path-supervision implementation. No new connections are accepted for a failed path until the failed path becomes operational again. This is a consequence of using the address selection/load distribution algorithm.
134
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Figure 20
Descriptions of transport and transmission features
LTE Dual U-plane IP addresses overview
SBTS
Load(bearer)distribution
C
Tunnel1
M S
VLAN1
U1 Switch Router
Tunnel2 VLAN2
U2
ExamplewithIPsec U1,U2-User-planeIP M-Management-plane C-S1/X2Control-plane S-Synchronization-plane
3.24.1.4
Physicalinterface Logicalinterface(e.g.VLAN)
System impact Interdependencies between features This feature is the precondition for the feature: •
SR000395: IPv4 based S1/X2
Impact on interfaces This feature has an impact on interfaces as beneath: •
More than one physical interface can be used for backhaul.
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature is used to increase the user data throughput of the network between SBTS and SGWs. For example, if the 2xGE is used for connecting SBTS to the transport network, theoretically a throughput of up to 2 Gb/s can be achieved.
3.24.1.5
SR000770: LTE Dual U-plane IP addresses management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Issue: 01E
DN09218825
135
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 68: New parameters lists parameters introduced with this feature. Table 68
New parameters
Full name
Abbreviated name
IPv4 address 2
3.24.1.6
ipV4Address2
Managed object BTSSCL
Sales information Table 69
Sales information
BSW/ASW
License control in network element
BSW
-
3.25 SR000176: ML-PPP termination 3.25.1 Description of SR000176: ML-PPP termination Introduction to the feature This feature introduces one ML-PPP interface on the SBTS based on the RFC1990. This enables to utilize the TDM infrastructure to transport the IPv4 transport protocols (Abis, Iub) towards the SBTS interfaces.
3.25.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits
136
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
This feature enables to utilize the existing TDM infrastructure in IPv4-based transport ensuring that transport network does not need to be promptly updated to Ethernet. By management command the operator can configure the minimum set of PPP options and ensure maximum interworking with other hardware.
3.25.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF). This feature requires Flexi Multiradio BTS Transport Sub-Module FTIF.
3.25.1.3
Functional description This feature introduces one Multilink-PPP (ML-PPP) interface based on the RFC1990 and ensures the ML-PPP termination of the SBTS terminated and external traffic. This enables to utilize the TDM infrastructure to transport the IPv4 transport protocols (Abis, Iub) towards the SBTS interfaces and thus there is no need to promptly update the complete transport network to Ethernet. The mechanism does not support IPv6. The ML-PPP standard permits to combine multiple PPP links into ML-PPP bundle. The presented feature supports one ML-PPP bundle. The ML-PPP bandwidth can be determined, with 64 kbps gradation, from 128 kbps up to the bandwidth of eight E1/T1 connections. This feature permits to configure PPP and UDP/IP header compression [RFC2509] providing optimized bandwidth of the TDM connections. The feature introduces a new parameter to define the minimum set of PPP options and ensure maximum interworking with other hardware. In addition, the feature provides the Multiclass ML-PPP (MCMP) mechanism [RFC2686]. The mechanism provides configurable DSCP values into MCMP priority mapping. On FSMr3, the ML-PPP termination and Integrated CESoPSN mechanism cannot operate concurrently. The IP header compression mechanism is defined with RFC2507 and can be used for compression of the UDP/IP headers per hop over PPP links. The header compression mechanism utilizes the situation that the most of the header information remains unchanged during the lifetime of a packet stream. When the header compression mechanism begins to operate, the fields of the full header, which remain unchanged, do not need to be transferred again and are stored as a context at both ends. When the mentioned fields change, the full header is transferred again to update the context. The mechanism of IP header compression for the TCP header is not supported on the SBTS. The Multilink Protocol (MP) permits to combine multiple physical links into the virtual link with greater bandwidth than any of the single links. The MP can be optimized for transmission of real-time applications (for example voice) over low bitrate links, comprising the Multiclass ML-PPP (MCMP) mechanism. The purpose of the MCMP mechanism is to minimize the end-to-end delay and be able to suspend a packet when a more urgent packet is to be transmitted. This can be done defining the multiple classes which permits running Multilink multiple times over one link, each class providing a different priority.
Issue: 01E
DN09218825
137
Descriptions of transport and transmission features
Figure 21
SRAN 16.2, Feature Descriptions
ML-PPP termination
ML -PPP TDM nxE1/T1 BTS1
3.25.1.4
ML -PPP gateway
System impact Interdependencies between features This feature affects the features: • •
SR000402: BTS QoS Support for Terminated and Routed Traffic SR000589: IPv4/IPv6 Transport Stack
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: • •
3.25.1.5
The feature provides decreased system occupancy as the transport capacity is confined to 8 x 2M. The feature provides the transport interface capacity to be confined to N x E1/T1 connections where N is the number of those connections.
SR000176: ML-PPP termination management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults Table 70: New alarms and faults lists alarms and faults introduced with this feature. Table 70
BTS Fault ID
138
New alarms and faults
BTS Fault name
Reported alarms
61250
IPCP Failure
61250 IPCP Failure
61251
LCP Failure
61251 LCP Failure on Interface $IF
61622
MLPPP link Degrade
61622 MLPPP link Degrade
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 70
BTS Fault ID 61252
Descriptions of transport and transmission features
New alarms and faults (Cont.)
BTS Fault name
PPP Interface down
Reported alarms
61252 PPP Interface down
Measurements and counters Table 71: New counters lists counters introduced with this feature. Table 71
New counters
Counter ID
Issue: 01E
Counter name
Measurement
M51303C0
Unavailable Seconds
PDH Interface
M51303C1
Errored Seconds
PDH Interface
M51303C2
Severely errored seconds
PDH Interface
M51303C3
Background Block Errors
PDH Interface
M51304C0
pppTxOctets
PPP Multi Link Statistics
M51304C1
pppRxOctets
PPP Multi Link Statistics
M51304C2
pppTxPackets
PPP Multi Link Statistics
M51304C3
pppRxPackets
PPP Multi Link Statistics
M51304C4
pppDiscardedPackets
PPP Multi Link Statistics
M51304C5
pppTxFragments
PPP Multi Link Statistics
M51304C6
pppRxFragments
PPP Multi Link Statistics
M51304C7
pppTxPacketsBypass
PPP Multi Link Statistics
M51304C8
pppRxPacketsBypass
PPP Multi Link Statistics
M51304C9
pppRxOctetsBypass
PPP Multi Link Statistics
M51304C10
pppTxOctetsBypass
PPP Multi Link Statistics
M51304C11
pppDroppedPackets
PPP Multi Link Statistics
M51305C0
pppTxOctets
PPP Single Link Statistics
M51305C1
pppRxOctets
PPP Single Link Statistics
DN09218825
139
Descriptions of transport and transmission features
Table 71
SRAN 16.2, Feature Descriptions
New counters (Cont.)
Counter ID
Counter name
Measurement
M51305C2
pppTxPackets
PPP Single Link Statistics
M51305C3
pppRxPackets
PPP Single Link Statistics
M51305C4
pppDiscardedPackets
PPP Single Link Statistics
M51306C0
pppTxOctetsHDLC
PPP Link Statistics
M51306C1
pppRxOctetsHDLC
PPP Link Statistics
M51306C2
pppTxPacketsHDLC
PPP Link Statistics
M51306C3
pppRxPacketsHDLC
PPP Link Statistics
M51306C4
pppDiscardedPacketsHDLC
PPP Link Statistics
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 72: New parameters lists parameters introduced with this feature. Table 72
New parameters
Full name
140
Abbreviated name
Managed object
Dynamically negotiated IP addresses
dynamicIpAddrList
IPIF
– Negotiated local ip address
– negLocalIpAddr
IPIF
– Negotiated remote ip address
– negRemoteIpAddr
IPIF
Layer 2 interface reference
interfacePtr
IPIF
Local IP address list
ipAddrList
IPIF
– Identifier of the IP address configuration
– ipAddrIdentifier
IPIF
– IP address
– localIpAddr
IPIF
Access control field compression result
acfcResult
P3LP
Access control field compression target
acfcTarget
P3LP
FRLI identifier
frliId
P3LP
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 72
Descriptions of transport and transmission features
New parameters (Cont.)
Full name
Issue: 01E
Abbreviated name
Managed object
LCP echo enabled
lcpEchoEnabled
P3LP
LCP echo interval
lcpEchoInterval
P3LP
Local MRU result
localMruResult
P3LP
Local MRU target
localMruTarget
P3LP
Magic number usage
magicNumberUsage
P3LP
Operational state
operationalState
P3LP
PPP link identifier
p3lpId
P3LP
Protocol field compression result
pfcResult
P3LP
Protocol field compression target
pfcTarget
P3LP
Remote MRU
remoteMru
P3LP
Administrative state
administrativeState
P3ML
DSCP to MCMP class2 mapping
dscpToMcmpClass2Map
P3ML
– Differentiated services code point (DSCP) – dscp
P3ML
– MCMP class
– mcmpClass
P3ML
DSCP to MCMP class4 mapping
dscpToMcmpClass4Map
P3ML
– Differentiated services code point (DSCP) – dscp value
P3ML
– MCMP class
– mcmpClass
P3ML
Endpoint discriminator usage enabled
endPointDiscriminatorUsage Enabled
P3ML
Endpoint discriminator result
endpointDiscriminatorResult
P3ML
F max period peer
fMaxPeriodPeer
P3ML
F max time peer
fMaxTimePeer
P3ML
IP header compression result
ipHeaderCompressionResult
P3ML
IP header compression usage
ipHeaderCompressionUsage
P3ML
DN09218825
141
Descriptions of transport and transmission features
Table 72
New parameters (Cont.)
Full name
142
SRAN 16.2, Feature Descriptions
Abbreviated name
Managed object
IPCP encapsulation
ipcpEncapsulation
P3ML
Local MRRU result
localMrruResult
P3ML
Local MRRU target
localMrruTarget
P3ML
Max header peer
maxHeaderPeer
P3ML
Fragment size in egress direction
mpFragmentSize
P3ML
Multi-class result
multiClassResult
P3ML
Multi-class target
multiClassTarget
P3ML
Non TCP space peer
nonTcpSpacePeer
P3ML
Operational state
operationalState
P3ML
P3LP identifier
p3LpId
P3ML
PPP multi-link identifier
p3mlId
P3ML
Remote MRRU result
remoteMrru
P3ML
Short sequence number format result
shortSeqNbrFormatResult
P3ML
Short sequence number format usage enabled
shortSeqNbrFormatUsageEn abled
P3ML
Administrative state
administrativeState
P3SL
F max period peer
fMaxPeriodPeer
P3SL
F max time peer
fMaxTimePeer
P3SL
IP header compression result
ipHeaderCompressionResult
P3SL
IP header compression usage
ipHeaderCompressionUsage
P3SL
Max header local target
maxHeaderPeer
P3SL
Non TCP space peer
nonTcpSpacePeer
P3SL
Operational state
operationalState
P3SL
P3LP identifier
p3LpId
P3SL
PPP single-link identifier
p3slId
P3SL
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 72
Descriptions of transport and transmission features
New parameters (Cont.)
Full name
3.25.1.6
Abbreviated name
Managed object
PPP link statistics measurement interval
pppLinkStatisticsInterval
PM
PPP multi-link statistics measurement interval
pppMultiLinkStatisticsInterval
PM
PPP single-link statistics measurement interval
pppSingleLinkStatisticsInterv al
PM
Sales information Table 73
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
3.26 SR000382: Multiple VLAN interfaces 3.26.1 Description of SR000382: Multiple VLAN interfaces Introduction to the feature This feature enables to configure more than one VLAN interface in the SBTS and enables the operator to tag the IP/Ethernet egress traffic with different VLAN IDs. The VLAN IDs can be utilized to separate different traffic types and exploit different paths within the transport network.
3.26.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature enables the operator to transmit different traffic types with different properties, to aggregate the same traffic types from many SBTSs into one VLAN, and to prioritize the traffic with VLAN IDs. The simplified mapping of the SBTS traffic types to different traffic streams on the transport network is provided.
3.26.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
Issue: 01E
DN09218825
143
Descriptions of transport and transmission features
3.26.1.3
SRAN 16.2, Feature Descriptions
Functional description This feature enables to configure more than one VLAN interface in the SBTS and enables the operator to tag the IP/Ethernet egress traffic with different VLAN IDs. The VLAN IDs can be utilized to separate different traffic types and exploit different paths within the transport network. The mechanisms of IP routing provide the ability to differentiate traffic to different VLAN interfaces which obtain different VLAN tagging corresponded with them. The VLAN interface can be configured with the VLAN ID parameter from 1 to 4094. VLAN ID=0 is not permitted. When the priority-tagging mechanism is enabled for the plain Ethernet interface, then the priority-tagged frame (VLAN ID=0) is added to the plain Ethernet interface. This feature enables to concurrently configure more than one VLAN interface, additionally to the plain Ethernet interface with the limitation that each VLAN interface configured at the same Ethernet MAC must have different VLAN ID parameter. Figure 22
Multiple VLAN interfaces
SBTS
DSL VLANtermination/ Siterouter
VLAN1 VLAN2 VLAN3 SBTS
Ethernet
Ethernetchainingscenario
3.26.1.4
System impact Interdependencies between features This feature requires one of the features: • • • •
144
SR000365: Electrical 100/1000-Base-T Interface SR000368: 1000Base-SX Optical GE Interface SR000369: 1000Base-LX Optical GE Interface SR000370: 1000Base-ZX Optical GE Interface
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
•
Descriptions of transport and transmission features
SR000371: 1000Base-BX Optical GE Interface
This feature requires the feature: •
SR000350: Ethernet Termination
This feature affects the feature: •
SR000402: BTS QoS Support for Terminated and Routed Traffic
Impact on interfaces This feature has an impact on interfaces as beneath: •
The feature provides support for more than one VLAN interface of one SBTS.
Impact on network and network element management tools This feature has an impact on network management tools as beneath: •
The feature provides support for more than one VLAN interface and the network management tools must validate the creation mechanism of those interfaces.
Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.26.1.5
SR000382: Multiple VLAN interfaces management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults There are no alarms and faults related to this feature. Measurements and counters Table 74: New counters lists counters introduced with this feature. Table 74
New counters
Counter ID
Counter name
Measurement
M51302C0
EthVlanIfInEthTypeMismatch
VLAN Statistics
M51302C1
EthIfInFrames
VLAN Statistics
M51302C2
EthIfInOctets
VLAN Statistics
M51302C3
EthIfOutFrames
VLAN Statistics
M51302C4
EthIfOutOctets
VLAN Statistics
Key performance indicators There are no key performance indicators related to this feature. Parameters
Issue: 01E
DN09218825
145
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Table 75: New parameters lists parameters introduced with this feature. Table 75
New parameters
Full name
3.26.1.6
Abbreviated name
Managed object
VLAN IF statistics measurement interval
vlanStatisticsInterval
PM
User label
userLabel
VLANIF
Vlan ID
vlanId
VLANIF
Vlan interface identifier
vlanIfId
VLANIF
Sales information Table 76
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
3.27 SR000386: QoS Aware Ethernet Switching 3.27.1 Description of SR000386: QoS Aware Ethernet Switching Introduction to the feature This feature provides Ethernet switching between the available Ethernet interfaces in the SBTS for co-location and chaining scenarios. Quality of service (QoS) and VLAN awareness are supported.
3.27.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • • • •
146
allows separation of traffic flows on Ethernet level by means of separate Ethernet broadcast domains (VLANs) eliminates the need for an external device for providing Ethernet switching functionality enables traffic aggregation in co-location scenarios enables chaining of BTSes
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.27.1.2
Descriptions of transport and transmission features
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.27.1.3
Functional description The feature introduces: • • •
configurable basic switching configurable VLAN aware processing (VLAN ingress filtering, learning, switch lookup, egress processing) configurable QoS processing per physical interface (QoS classification, egress scheduling and shaping)
Basic switching The feature enables configurable switching between the external Ethernet interfaces. To enable basic switching and activate the feature the following must be performed: • •
switching between physical interfaces parameter activation configuration of physical ports Each physical port can be activated at the system startup.
An important part of the basic switching functionality is the handling of MAC address learning. The information at which port each MAC address is received is stored in the Forwarding Database (FDB). VLAN awareness If switching between physical Ethernet interfaces is enabled, it is possible to also enable VLAN awareness. When VLAN awareness is enabled the following applies: •
• • •
•
•
The FDB becomes VLAN aware. The VLAN-ID of a received frame is stored in FDB, so it is possible to differentiate between frames sent from the same source (MAC address) but different VLANs (VLAN-ID). This mechanism is called independent VLAN learning (IVL). It is possible to configure which frame types (all, tagged only, untagged + prioritytagged only) are accepted in the ingress direction. For each port a configurable Port Default VLAN (PVID) is defined, to determine the forwarding of received untagged and priority-tagged frames. For each port a configurable Port Default Priority (PCP) is defined, to determine the QoS behavior of received untagged and priority-tagged frames at the switch egress port, and in the next Ethernet network segment. It is possible to configure to which VLAN-IDs each external switch-port belongs (for the internal switch-port it is done automatically). A frame can only egress on those ports that are members of the frame's VLAN-ID. To determine the egress port for a frame the FDB has to be checked for the frame's MAC address and VLAN-ID. If the PVID configured on the egress port is the same as the VLAN-ID of the received frame, the VLAN tag of the out-going frame is removed.
Quality of service (QoS) processing
Issue: 01E
DN09218825
147
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
If switching between physical Ethernet interfaces is enabled, it is possible to also enable QoS awareness. In order to support QoS awareness the system provides a set of queues scheduled with a strict priority or configurable weighted priority for each egress port. The egress frames are enqueued in these queues based on a selectable classification criteria (IP DSCP, VLAN-PCP or VLAN-ID) with its configured queue mapping. When the traffic is sorted to the queues, the scheduler stage selects which frame is the next to transmit (SP first, then the WQ with the highest configured weight). Before the frames are transmitted the shaper checks that the configured shaper rate and the configurable burst size are met. Figure 23
Scheduling and shaping of the aggregated traffic
Multiradio 10BTS
SiteRouter IP /Ethernet Backhaul
OtherBTS
]
low priority
]
high priority
ethernetshapinglevel
] low priority
]
UplinktrafficBTS#1
]
low priority
]
high priority
high priority
Aggregateduplinktraffic
UplinktrafficBTS#2
3.27.1.4
System impact Interdependencies between features This feature requires the following feature: •
SR000350: Ethernet Termination
This feature is a precondition for the features: • •
SR000589: IPv4/IPv6 Transport Stack SR000402: BTS QoS Support for Terminated and Routed Traffic
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools.
148
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.27.1.5
SR000386: QoS Aware Ethernet Switching management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters Table 77: New counters lists counters introduced with this feature. Table 77
New counters
Counter ID
Counter name
Measurement
M51363C0
EthVlanIfDiscFrames
Bridge Port Statistics
M51363C1
DiscardedTxFrames_EF
Bridge Port Statistics
M51363C2
DiscardedTxFrames_AF1
Bridge Port Statistics
M51363C3
DiscardedTxFrames_AF2
Bridge Port Statistics
M51363C4
DiscardedTxFrames_AF3
Bridge Port Statistics
M51363C5
DiscardedTxFrames_AF4
Bridge Port Statistics
M51363C6
DiscardedTxFrames_BE
Bridge Port Statistics
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 78: New parameters lists parameters introduced with this feature. Table 78
New parameters
Full name
Issue: 01E
Abbreviated name
Managed object
Switch port acceptable frame types
acceptableFrameTypes
BRGPRT
Bridge port object identifier
brgPrtId
BRGPRT
Bridge port statistics interval
bridgePortStatisticsInterval
BRGPRT
Ethernet link identifier
ethlkId
BRGPRT
DN09218825
149
Descriptions of transport and transmission features
Table 78
SRAN 16.2, Feature Descriptions
New parameters (Cont.)
Full name
150
Abbreviated name
Managed object
Flush fdb on LOS mode
flushFdbOnLos
BRGPRT
Layer 2 switch burst size
l2BurstSize
BRGPRT
Ethernet interface shaper rate
l2ShaperRate
BRGPRT
Layer 2 switch member VLAN identifier list
l2VlanIdList
BRGPRT
Upper value of VLAN identifier range
highValue
BRGPRT
Low value of VLAN identifier range
lowValue
BRGPRT
Default VLAN identifier for layer 2 switching portDefaultVlanId
BRGPRT
Port default VLAN priority
portDefaultVlanPriority
BRGPRT
Internal Bridge port object identifier
iBrgPrtId
IBRGPRT
Default VLAN identifier for layer 2 switching portDefaultVlanId
IBRGPRT
Port default VLAN priority
portDefaultVlanPriority
IBRGPRT
DSCP to queue mapping
dscpToQueueMap
L2SWI
Differentiated services code point (DSCP) value
dscp
L2SWI
queue
queue
L2SWI
Enable layer 2 QoS awareness per switchport
l2QoSEnabled
L2SWI
L2 switch identifier
l2SwiId
L2SWI
Enable layer 2 switching between physical ports
l2SwitchingEnabled
L2SWI
Switch-port scheduler weight for forwarding l2WeightAF1 class AF1
L2SWI
Switch-port scheduler weight for forwarding l2WeightAF2 class AF2
L2SWI
Switch-port scheduler weight for forwarding l2WeightAF3 class AF3
L2SWI
Switch-port scheduler weight for forwarding l2WeightAF4 class AF4
L2SWI
Switch-port scheduler weight for forwarding l2WeightBE class BE
L2SWI
PCP to queue mapping
pcpToQueueMap
L2SWI
PCP value
pcp
L2SWI
queue
queue
L2SWI
Priority queue for non-classified traffic
priorityQueueNonClassified
L2SWI
QoS classification mode
qosClassificationCriteria
L2SWI
VLAN aware switching enable
vlanAwarenessEnabled
L2SWI
VLAN ID to queue mapping
vlanIdToQueueMap
L2SWI
queue
queue
L2SWI
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 78
Descriptions of transport and transmission features
New parameters (Cont.)
Full name
3.27.1.6
Abbreviated name
Managed object
Upper value of VLAN identifier range
vlanIdHighValue
L2SWI
Low value of VLAN identifier range
vlanIdLowValue
L2SWI
Bridge port statistics measurement interval
bridgePortStatisticsInterval
PM
Sales information Table 79
Sales information
BSW/ASW
License control in network element
BSW
-
3.28 SR000954: SBTS Common Transport 3.28.1 Description of SR000954: SBTS Common Transport Introduction to the feature This feature provides common transport for the SBTS and depicts how GSM, WCDMA, and LTE share the SBTS transport resources concurrently whereas the entire system appears on the Transport Layer towards the network as one single IP host.
3.28.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides common transport for the SBTS meaning that multiple operability mechanisms in single RAT GSM, WCDMA, and LTE configurations are unified into common operability mechanisms in single SBTS configuration making unified transport performance, fault, and configuration management. In addition, the entire system appears on the Transport Layer towards the transport network as one single IP host. The common transport feature is planned to be compatible to the current multi-operator configurations, and the existing properties of different RATs are maintained.
3.28.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
Issue: 01E
DN09218825
151
Descriptions of transport and transmission features
3.28.1.3
SRAN 16.2, Feature Descriptions
Functional description This feature provides common transport for the SBTS. The entire system appears on the Transport Layer towards the network as one single IP host. The SBTS consists of one or more core modules and the connected baseband processing units. One of the core modules, the primary module, provides all backhaul connections. The modules are connected by a secure internal bus which is transparent to the Transport Layer from the outside. This feature, apart from the standalone mode, ensures concurrent support for the transport modes: LTE - S1/X2 over IP/Ethernet, WCDMA - Iub over IP/Ethernet (IP Iub), and GSM - Packet Abis over IP/Ethernet and Packet Abis over TDM. The common transport supports also a single GSM, WCDMA, and LTE base station instance. The site synchronization source can be one single external synchronization source and the mechanisms of synchronization are provided with the dedicated features. The site synchronization is propagated among the modules. The primary module terminates two Ethernet Transport interfaces. With an optional FTIF Transport Sub-Module, three Ethernet Transport interfaces are provided. The Ethernet Transport interfaces can be utilized in many purposes, for example, in backhaul connection (comprising redundancy and capacity extension) and in transport chaining. With the common transport mechanism, the TDM IP interfaces can be utilized concurrently with the Ethernet Transport interfaces and they can be utilized in backhaul and other purposes (for example frequency synchronization). The SBTS supports one module with TDM IP interfaces at the same time, the primary module. The RAT-specific Admission and Congestion Control mechanisms remain applicable and operate independently in SBTS: WCDMA - Connection Admission Control, LTE Measurement Based Transport Admission Control, and GSM - Packet Abis Congestion Control mechanism. This feature assumes that each RAT has its own statically determined bandwidth for committed bitrate traffic which means that existing dimensioning plans and rules can be reused as the RAT-specific admission control mechanisms are reused appropriately. This feature provides flexible approach of IP addressing. The IP addresses can be dedicated or shared among the RATs and planes. The IP address sharing among WCDMA/LTE Control Plane and GSM Management/Control Plane in SBTS requires appropriate network planning of the SCTP ports which must not overlap. The default configurations of traffic types other than SCTP, among RATs and planes, have specific dependencies. The modifications of the default configurations require that the ports cannot overlap. The SBTS has one management plane (M-plane) IP address which is dedicated or shared with other applications. The applications can bind to interface, alias, and virtual IP addresses. The SBTS can operate with a single IP address for U-, C-, M-, and S-plane, in one extreme. In other extreme, the SBTS can operate with different Uplane and C-plane IP addressing configuration. The common transport provides configurable post-fragmentation and pre-fragmentation mechanisms, and concurrent reassembly of both of these modes. The fragmentation mode selection applies in the entire SBTS. The post-fragmentation mechanism provides IP Layer fragmentation after an IPsec encapsulation whereas the pre-fragmentation mechanism provides IP Layer fragmentation performed prior to an IPsec encapsulation mechanism. The SBTS provides the flexibility to freely map individual traffic flows to an any IPsec security association which can be dedicated to a certain RAT, dedicated to a certain plane of a certain RAT, or shared among multiple RATs. The SBTS can be
152
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
connected to single IPsec gateway managing all RATs or concurrently to different IPsec gateways, for example one operating in management traffic and one operating in production traffic or one operating in each RAT configuration. The common transport ensures that the Transport interface MTUs: the Ethernet interface MTU and the ML-PPP interface MTU are mutually independent. In addition to the Transport interface MTU, the SBTS optionally supports the Route MTUs to support numerous network scenarios with varying MTUs beyond the last mile. This permits applying different packet sizes to the traffic of different RATs and planes. When the Route MTUs are not applied, the construction of packets is only defined with the configuration of the MTU of the Transport interface. The transport configuration management in the SBTS is managed via the SBTS configuration tools. The transport function in the SBTS is operated via an unified object model that holds RAT-agnostic and RAT-specific objects and parameters. The generic transport features package and the object model do not depend on the deployed RATs combination. The common transport ensures that the transport software assets are protected with the SRAN software asset protection framework. The common transport provides unified transport fault management in which the alarms and faults are reported via the SBTS fault management framework. The common transport L1, L2, and L3 faults are in principle RAT-agnostic. On the other hand, the L2 and L3 faults may have a RAT-specific meaning, depending on the configuration. The alarms and faults are reported in the management connection towards the O&M components. The common transport provides unified transport performance management. The transport performance monitoring data is gathered via the SBTS performance management framework. The common transport L2 and L3 measurements are in principle RAT-agnostic. On the other hand, the measurements may have a RAT-specific meaning, depending on the determined configuration. The transport performance monitoring data is gathered in the management connection towards the O&M components.
3.28.1.4
System impact Interdependencies between features This feature requires the features: • • • • •
SR000395: IPv4 based S1/X2 SR000396: IPv4 based Iub SR000397: IPv4 based Packet Abis Transport SR000589: IPv4/IPv6 Transport Stack SR001003: IPv4 based SBTS Management Plane
Related features: • • • • •
SR000176: ML-PPP termination SR000350: Ethernet Termination SR000356: IPsec for BTS SR000402: BTS QoS Support for Terminated and Routed Traffic SR000403: Source based routing in BTS
Impact on interfaces
Issue: 01E
DN09218825
153
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.28.1.5
SR000954: SBTS Common Transport management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults There are no alarms and faults related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 80: New parameters lists parameters introduced with this feature. Table 80
New parameters
Full name
Abbreviated name
Transport network layer identifier
3.28.1.6
tnlId
Managed object TNL
Sales information Table 81
Sales information
BSW/ASW
License control in network element
ASW
Pool License
License control attributes / License capacity unit Capacity / BTS
3.29 SR001103: SBTS Flexible Sync Input Priority 3.29.1 Description of SR001103: SBTS Flexible Sync Input Priority Introduction to the feature
154
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
This feature enables the SBTS to freely configure the priority of synchronization sources. The priority can be configured regardless of whether synchronization sources come from core modules or transport interfaces.
3.29.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The operator can flexibly design a synchronization redundancy solution according to the available synchronization sources and preferences.
3.29.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.29.1.3
Functional description This feature allows the user to freely configure the priority of synchronization sources in the priority list according to the operator deployment strategy. For example, Timing over Packet (ToP) with phase synchronization can be set as a primary synchronization source and Global Navigation Satellite System (GNSS) receiver as a secondary one.
3.29.1.4
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.29.1.5
SR001103: SBTS Flexible Sync Input Priority management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 82: New alarms lists alarms introduced with this feature.
Issue: 01E
DN09218825
155
Descriptions of transport and transmission features
Table 82
SRAN 16.2, Feature Descriptions
New alarms
Alarm ID
Alarm name
7651
BASE STATION OPERATION DEGRADED
26629
BASE STATION NOTIFICATION
BTS faults and reported alarms Table 83: New BTS faults lists BTS faults introduced with this feature. Table 83
New BTS faults
Fault ID 3080
Fault name BTS reference clock missing
Reported alarms 7652 BASE STATION NOTIFICATION 7651 BASE STATION OPERATION DEGRADED
Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 84: New parameters lists parameters introduced with this feature. Table 84
New parameters
Full name
3.29.1.6
Managed object
Synchronization reference source list
referenceSourceList
SYNC
Input reference
inputReference
SYNC
Input reference priority
inputReferencePriority
SYNC
Sales information Table 85
156
Abbreviated name
Sales information
BSW/ASW
License control in network element
BSW
-
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
3.30 SR000367: Small Form Factor Pluggable Slot (SFP slot) 3.30.1 Description of SR000367: Small Form Factor Pluggable Slot (SFP slot) Introduction to the feature This feature introduces a small form factor pluggable slot (SFP slot).
3.30.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides SFP slot for Multi-Source Agreement (MSA) compliant SFP transceiver module.
3.30.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.30.1.3
Functional description This feature introduces an SFP slot. SFP slots enable the SBTS products to make use of optical SFP transceiver modules. The main functionalities introduced with SR000367: Small Form Factor Pluggable Slot (SFP slot) feature: • •
• • • •
SFP transceiver module detection SFP transceiver type validation The validation ensures that only SFP transceivers belonging to laser class 1 are used. Products belonging to laser class 1 are considered safe during use. basic SFP diagnostic support SFP transceiver power consumption up to 2.5 watt (depending on SBTS hardware) LOS detection pin support field pluggable and replaceable
Inserted SFP transceiver modules must meet the following conditions: • • • • •
Issue: 01E
SFP Multi-Sourcing Agreement (MSA) compliant laser class 1 compliant industrial temperature range: -40°C to +85°C provide extraction bail latch actuator be identified as LX type (SFP E²PROM Address A0h byte 6 = “02h”), SX type (SFP E²PROM Address A0h byte 6 =“01h”), or BX type (SFP E²PROM Address A0h byte 6 =“40h”).
DN09218825
157
Descriptions of transport and transmission features
• •
SRAN 16.2, Feature Descriptions
LOS detection pin supported SFP modules with MSA direct actuator, with push type ring or without any extraction handle must not be used
By default only one Ethernet interface is supported. More interfaces can by activated by software license key.
3.30.1.4
System impact Interdependencies between features This feature is a prerequisite for the following features: • • • •
SR000368: 1000Base-SX Optical GE Interface SR000369: 1000Base-LX Optical GE Interface SR000370: 1000Base-ZX Optical GE Interface SR000371: 1000Base-BX Optical GE Interface
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools If the inserted SFP does not comply with the requirements, an alarm (ID 61050) is raised and the laser is not switched on. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.30.1.5
SR000367: Small Form Factor Plugable Slot (SFP slot) management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 86: New alarms lists alarms introduced with this feature. Table 86
New alarms
Alarm ID
Alarm name
61079
SFP HW Failure on unit $U, interface $IF Customer
61050
Missing or non-compliant SFP module on unit $U, interface $I
61029
LOS on unit $U, interface $IF
BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators
158
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
There are no key performance indicators related to this feature. Parameters Table 87: New parameters lists parameters introduced with this feature Table 87
New parameters
Full name
3.30.1.6
Abbreviated name
Managed object
Label of the connector by the ethernet link
connectorLabel
CONx
Speed and duplex configuration
speedAndDuplex
ETHLK
Sales information Table 88
Sales information
BSW/ASW
License control in network element
ASW
Pool license
3.31 SR000403: Source based routing in BTS 3.31.1 Description of SR000403: Source based routing in BTS Introduction to the feature This feature extends the routing capabilities of the SBTS node by taking into consideration the source IP address, in addition to the destination IP address, in the mechanism of route selection. The mechanism supports IPv4 and IPv6.
3.31.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature improves the IP addressing flexibility by a more sophisticated routing mechanism, and may obsolete the need for address replanning and reconfiguration during network migration for Single RAN scenarios, in which merging of multiple different transport networks operating on the identical/overlapping IP subnets, in core domain, must be performed.
3.31.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
Issue: 01E
DN09218825
159
Descriptions of transport and transmission features
3.31.1.3
SRAN 16.2, Feature Descriptions
Functional description Overview This feature introduces policy-based routing functionality on the SBTS. Based on the configured routing policies, the packets are processed through different routing tables to apply different static routes to packets carrying the same destination IP address and different source IP address. The SBTS routing capabilities are extended by taking into consideration the source IP address, in addition to the destination IP address. The mechanism supports IPv4 and IPv6. This feature enables a mechanism that when using different source IP addresses for different traffic, the same IP addresses can be supported in peer side. This is ensured by dedicated routing tables based on appropriate policies. In certain cases, the intermediate transport network may also need to support policy-based routing. In addition, the mechanism, introduced with this feature, is applied for each type of traffic plane and is appropriate for each type of egress unicast IP packet, independent of the application with which the packet is formed. This feature is not applied for routing traffic to the SBTS subnet. This subnet is directly configured within the SBTS and cannot overlap with the addresses on the core network, which means that this subnet is reached without using the source-based routing mechanism. When the IP packets have to be transmitted from the SBTS through two different physical interfaces, the relation among the network IP and physical interfaces must be determined by configuring the Ethernet switching functionality accordingly. Route lookup More than one routing table can be configured, each table can contain static routes which are utilized for ordinary destination-based routing using the longest prefix match mechanism. By the Linux implementation, the route lookup procedure with two steps is performed. The first step utilizes the policies to determine one out of multiple routing tables. The policies take the source IP address into account - the policies are specified with a subnet. The second step is based on configured routes in each routing table, the destination-based routing with longest prefix match mechanism is utilized. When the procedure does not find any route in the table, the next policy is utilized in the search mechanism. The route lookup procedure considers only one routing table as the main one. The main table handles all the packets for which no policy or no route is found. When the configuration of policies is omitted, then the same behavior as without this feature is obtained. There is one main routing table each for the IPv4 and IPv6. The main routing table is identified by the name of the managed object. In the system, direct routes are automatically added to the main routing table, and not to the additional routing tables. Without the added direct routes, the IP packets for directly connected hosts are transmitted to the next-hop gateway first. In order to avoid this behavior, the operator must manually add direct routes to the additional routing tables. The policies contain an IP subnet and a pointer to the routing table. An IP packet matches a policy when its source address is in the subnet - the packet is routed based on entries of the routing table to which the policy is pointing. Policies are searched in a determined order and the order is defined by the operator. IP packets which do not match any policy are managed based on the main routing table. When the subnets of the policies do not overlap, the mechanism searches for routes only within the one of additonal routing tables and potentially within the main table.
160
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Example In the example configuration, the SBTS is defined with two U-plane adresses, 10.1.1.1 and .9, and there is just one network gateway with the 20.1.1.1 IP address which is determined from the /30 subnet. The two routing tables contain one route to network gateway but with different next-hop gateways, 10.1.1.2 and .10. The main routing table contains just a default route to certain next-hop gateway with an a.b.c.d address. In the example configuration, an egress IP packet with the 10.1.1.9 source IP address matches the second policy, and the routing is determined with the Table_3. The next-hop gateway for this packet has the 10.1.1.10 IP address. In this example, there is no need to configure the direct routes in the additional routing tables since the only other host in the network interfaces subnets is the particular next-hop gateway. Figure 24
Example configuration with two U-plane addresses
Table_2 ROUTINGPOLICIES
DestIP
nbr
SrcIP
Subnet
Routing table
1
10.1.1.1
/30
Table_2
2
10.1.1.9
/30
Table_3
20.1.1.0
Subnet Nexthop /30
10.1.1.2
Table_3 DestIP 20.1.1.0
Subnet Nexthop /30
10.1.1.10
maintable PACKETSNOTMATCHED BY POLICIES AREROUTED BASEDONMAINTABLE
3.31.1.4
DestIP 0.0.0.0
Subnet Nexthop /0
a.b.c.d
System impact Interdependencies between features This feature is the precondition (in certain network configurations) for the feature: •
SR000770: LTE Dual U-plane IP addresses
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has an impact on network management tools as beneath: •
The feature provides the configuration of multiple routing tables which can be monitored with the network mananagement tools.
Impact on system performance and capacity This feature has no impact on system performance or capacity.
Issue: 01E
DN09218825
161
Descriptions of transport and transmission features
3.31.1.5
SRAN 16.2, Feature Descriptions
SR000403: Source based routing in BTS management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults There are no alarms and faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 89: New parameters lists parameters introduced with this feature. Table 89
New parameters
Full name
3.31.1.6
Abbreviated name
Managed object
Routing policies
routingPolicies
RTPOL
– Order number of policy
– orderNumber
RTPOL
– Source IP address
– srcIpAddress
RTPOL
– Source IP prefix length
– srcIpPrefixLength
RTPOL
– Reference to routing table
– routingTablePtr
RTPOL
– User label
– userLabel
RTPOL
IP routing policy identifier
rtPolId
RTPOL
Sales information Table 90
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
3.32 SR000357: Symmetrical E1 Interface 3.32.1 Description of SR000357: Symmetrical E1 Interface Introduction to the feature
162
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
This feature provides a standard symmetrical E1 physical interface.
3.32.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The support of standard E1 interfaces allows the connection of widely available TDM based infrastructure.
3.32.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio BTS Transport Sub-Module (FTIF).
3.32.1.3
Functional description This feature provides one or more symmetrical E1 interfaces at an SBTS. The scope of the feature is the physical layer and parts of the data link layer. The electrical E1 interface introduces: • • •
• •
electrical characteristics compliant with ITU-T G.703 (11/2001) and EN 300166 (09/2001) bit rate compliant with ITU-T G.703 and EN 300166 (09/2001): 2048 kbit/s +/- 50ppm jitter and wander according to ITU-T G.823 (traffic interface) The intrinsic jitter on the transmit interfaces of interface units is in accordance with the ITU-T G.813. impedance: 120 Ohm connector type/pin-out: RJ48C Transport Sub-module FTIF supports two E1 interfaces on one 8P8C connector, first E1 interface uses RJ48C pin-out, second E1 interface uses the 4 pins not allocated by RJ48C.
There is always a valid E1 signal present on all ports even if the interface itself is not activated (SR000377: Synchronization from PDH interface). Details of electrical E1 interface features: • • •
g
Note: The long haul mode describes, in the context of an E1 interface, the maximum allowable attenuation of the received E1 signal. A short haul mode or an automatic detection of long/short haul is not supported. •
Issue: 01E
Shielded twisted pair cable (for example 472427A, FTCY, 15m with one open end) is used. High-density Bipolar 3 (HDB3) line code is compliant with ITU-T G.703 and EN 300166 (09/2001). The E1 receiver interfaces support only long haul mode.
Double Frame and CRC-4 Multiframe structure is supported according to ITU-T G.704 and ITU-T G.706.
DN09218825
163
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Supervision/Maintenance Process: •
•
•
Remote Alarm Indicator (RAI)/Remote Defect Indication (RDI) A-bit usage compliant with ITU-T G.775 (EN 417-5-1 subclause 7.2.1 and 7.2.2) is supported. After detection of defects (dLOS, dAIS, dLOF) consequent action RDI is generated. Remote Error Indicator (REI) E-bit usage compliant with ITU-T G.704 and ITU-T G.706 (EN 417-5-1 subclause 7.2.1 and 7.2.2) is supported. Consequent action REI is performed according to received Near End Block Errors and CRC-4 Multiframe Alignment process. Plesiochronous Digital Hierarchy (PDH) transmission path is declared as nonoperational for the next higher layer if any transmission path defect (dLOS, dAIS or dLOF/LOMF) is detected. If 10E-3 Bit Error Rate (BER) is measured, the E1 PDH transmission path is declared as non-operational as well.
Two E1 interfaces are included in Basic Software (BSW). An additional two E1 interfaces are optional software (SW) functionality. It is included to the SRAN SW asset protection framework which is defined by feature SR000794: SBTS SW License Management. The usage of this feature is monitored by a SW Activation flag. The functionality can be deactivated. In case it is not possible to deactivate the functionality (for example, when the SBTS M-plane connectivity is lost) the SBTS is blocked from further use.
3.32.1.4
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.32.1.5
SR000357: Symmetrical E1 Interface management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 91: New alarms lists alarms introduced with this feature. Table 91
New alarms
Alarm ID
164
Alarm name
61028
LOF on unit $U, interface $IF
61029
LOS on unit $U, interface $IF
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 91
Descriptions of transport and transmission features
New alarms (Cont.)
Alarm ID
Alarm name
61040
Interface under test on unit $U, interface $IF for $T minutes
61104
EBER on unit $U, interface $IF
61150
LOMF on unit $U, interface $IF
61151
AIS on unit $U, interface $IF
61152
RDI on unit $U, interface $IF
BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters Table 92: New counters lists counters introduced with this feature. Table 92
New counters
Counter ID
Counter name
Measurement
M51303C0
Unavailable Seconds
PDH Interface
M51303C1
Errored Seconds
PDH Interface
M51303C2
Severely errored seconds
PDH Interface
M51303C3
Background Block Errors
PDH Interface
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 93: New parameters lists parameters introduced with this feature. Table 93
New parameters
Full name
Issue: 01E
Abbreviated name
Managed object
Fractional interface identifier
frliId
FRLI
PDH interface identifier
ppttId
FRLI
Time slot sequence
timeSlotSequence
FRLI
PDH interface measurement interval
pdhInterfaceStatisticsInterval
PM
DN09218825
165
Descriptions of transport and transmission features
Table 93
New parameters (Cont.)
Full name
3.32.1.6
SRAN 16.2, Feature Descriptions
Abbreviated name
Managed object
Administrative state
administrativeState
PPTT
Interface
interface
PPTT
PDH line type
pdhLineType
PPTT
PDH interface identifier
ppttId
PPTT
Sales information Table 94
Sales information
BSW/ASW
License control in network element
ASW
Pool license
3.33 SR000376: Synchronization from 2.048MHz signal 3.33.1 Description of SR000376: Synchronization from 2.048MHz signal Introduction to the feature This feature provides the SBTS frequency synchronization from the 2.048 MHz signal which is introduced via the synchronization input interface of the SBTS. This mechanism of synchronization is based on the ITU-T G.703 standard.
3.33.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature introduces the SBTS frequency synchronization mechanism from the 2.048 MHz G.703 signal which is a standard signal supported by any type of BTS and many measurement instruments.
3.33.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
166
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.33.1.3
Descriptions of transport and transmission features
Functional description This feature provides the SBTS frequency synchronization from the 2.048 MHz signal which is introduced via the synchronization input interface of the SBTS. This mechanism of synchronization is based on the ITU-T G.703 standard. The mechanism provides frequency synchronization only.
3.33.1.4
System impact Interdependencies between features This feature requires the feature: •
SR000847: BTS Synchronization Mode Support
This feature is the precondition for the feature: •
SR000385: Synchronization Hub
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.33.1.5
SR000376: Synchronization from 2.048MHz signal management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults Table 95: New alarms and faults lists alarms and faults introduced with this feature. Table 95
BTS Fault ID 1899
New alarms and faults
BTS Fault name
2M external reference missing
Reported alarms
7108 BASE STATION SYNCHRONIZATION PROBLEM
Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters
Issue: 01E
DN09218825
167
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Table 96: New parameters lists parameters introduced with this feature. Table 96
New parameters
Full name
3.33.1.6
Abbreviated name
Managed object
EXT2M object identifier
ext2mId
EXT2M
Synchronization reference source list
referenceSourceList
SYNC
– Input reference
– inputReference
SYNC
– Input reference priority
– inputReferencePriority
SYNC
Sales information Table 97
Sales information
BSW/ASW
License control in network element
ASW
Pool License
License control attributes ON/OFF
3.34 SR000377: Synchronization from PDH interface 3.34.1 Description of SR000377: Synchronization from PDH interface Introduction to the feature This feature provides the SBTS frequency synchronization from the PDH interface meaning the synchronization via an E1 interface of the SBTS. This mechanism of synchronization is based on the ITU-T G.703 standard.
3.34.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature introduces the SBTS frequency synchronization mechanism which can be provided from the PDH interfaces currently operating on the network.
3.34.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF). This feature requires Flexi Multiradio BTS Transport Sub-Module FTIF.
168
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.34.1.3
Descriptions of transport and transmission features
Functional description This feature provides the SBTS frequency synchronization from the PDH interface meaning the synchronization via an E1 interface of the SBTS. This mechanism of synchronization is based on the ITU-T G.703 standard. The E1 connection clock is traceable to the Primary Reference Clock (PRC). The mechanism provides frequency synchronization only.
3.34.1.4
System impact Interdependencies between features This feature requires the feature: •
SR000847: BTS Synchronization Mode Support
This feature is the precondition for the feature: •
SR000385: Synchronization Hub
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.34.1.5
SR000377: Synchronization from PDH interface management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults Table 98: New alarms and faults lists alarms and faults introduced with this feature. Table 98
BTS Fault ID 4300
New alarms and faults
BTS Fault name
PDH reference missing
Reported alarms
7108 BASE STATION SYNCHRONIZATION PROBLEM
Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature.
Issue: 01E
DN09218825
169
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Parameters Table 99: New parameters lists parameters introduced with this feature. Table 99
New parameters
Full name
3.34.1.6
Abbreviated name
Managed object
PDH object identifier
pdhId
PDH
PDH interface used for PDH reference
ppttId
PDH
Synchronization reference source list
referenceSourceList
SYNC
– Input reference
– inputReference
SYNC
– Input reference priority
– inputReferencePriority
SYNC
Sales information Table 100
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
3.35 SR001041: Synchronization Holdover Support 3.35.1 Description of SR001041: Synchronization Holdover Support Introduction to the feature This feature allows the SBTS to continue its service when synchronization references are lost. In such case the service can be continued without performance degradation for a limited period of time.
3.35.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature ensures that the SBTS remains in service when synchronization source is lost. Therefore the users are not impacted. Holdover performance also provides the operator sufficient time to visit the site and fix the problem. Site visit is required for this purpose.
170
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.35.1.2
Descriptions of transport and transmission features
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.35.1.3
Functional description This feature ensures that the SBTS is able to perform holdover function when synchronization sources are lost. For a limited period of time the SBTS can maintain the ongoing service without performance degradation. Frequency Holdover Performance Requirement The SBTS can operate without a frequency synchronization reference. Frequency accuracy of +/- 50ppb in the air interface compared to Primary Reference Clock (PRC) can be maintained for at least 14 days, provided that the SBTS has been turned on and supplied with accurate and stable frequency synchronization reference for at least 7 days. Phase Holdover Performance Requirement The SBTS based on Flexi Multiradio System Module (FSMF) can operate without phase and time synchronization references with the following holdover performance: • •
10us for 8 hours 3us for 6 hours
The phase accuracy refers to phase alignment accuracy between radio frame generated on the air interface and Primary Reference Time Clock (PRTC). The following conditions must be met to provide holdover performance: • •
The SBTS has been powered on and supplied with accurate phase synchronization sources for at least 7 days. Constant temperature is assumed during holdover.
Performance is typical (90% of the time) but not guarantee (100% of the time).
3.35.1.4
System impact Interdependencies between features This feature requires the feature: •
SR000847: BTS Synchronization Mode Support
This feature affects the features: • •
SR000385: Synchronization Hub SR000554: Sync Hub Direct Forward
Related feature: •
SR000956: SBTS Startup and runtime management
Impact on interfaces
Issue: 01E
DN09218825
171
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity The performance of holdover is an important factor which determines: • •
3.35.1.5
the time for which a BTS can keep the 3GPP frequency accuracy requirements at the air interface. the time for which a BTS can keep the phase accuracy requirements needed by the RAT-specific phase synchronization dependent radio services.
SR001041: Synchronization Holdover Support management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 101: New parameters lists parameters introduced with this feature. Table 101
New parameters
Full name
Abbreviated name
Climate control OCXO temperature learning
3.35.1.6
climateControlOcxoTemperature CLIC Learning
Sales information Table 102
172
Managed object
Sales information
BSW/ASW
License control in network element
BSW
-
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
3.36 SR000385: Synchronization Hub 3.36.1 Description of SR000385: Synchronization Hub Introduction to the feature This feature enables an SBTS to provide synchronization reference to the another SBTS and other connected nodes (other network elements, BTSs from the other RATs) via multiple synchronization output options, derived from the synchronization input. In addition, the feature provides the summary of synchronization input sources and synchronization outputs which are supported by an SBTS.
3.36.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the benefit that there is only one single synchronization source for an entire SRAN site or chained SBTSs. This brings the CAPEX and OPEX savings of synchronization mechanism, for example one GNSS operates with multiple SBTSs.
3.36.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF). This feature requires Flexi Multiradio BTS Transport Sub-Module FTIF to provide PDH synchronization output.
3.36.1.3
Functional description Overview This feature enables an SBTS to provide synchronization reference to the another SBTS and other connected nodes (other network elements, BTSs from the other RATs) via multiple synchronization output options, derived from the synchronization input. In addition, the feature provides the summary of synchronization input sources and synchronization outputs which are supported by an SBTS. This feature enables and disables multiple synchronization output options: PDH synchronization, 2.048MHz, and 1PPS output signals. When the PDH generation is not enabled, the SBTS continues to provide the PDH synchronization output signal on the synchronization interface but with an arbitrary frequency value. Independently from the synchronization mode, the SBTS can provide the mechanism of synchronization hub which can be utilized to provide frequency synchronization on an SBTS site. Both PDH and 2.048MHz synchronization chains can be composed. When the entire feature is not activated, the PDH operates in a plesynchronous operation mode.
Issue: 01E
DN09218825
173
Descriptions of transport and transmission features
Table 103
SRAN 16.2, Feature Descriptions
Synchronization inputs and outputs supported by SBTS
Input / Output
Input
Output
Synchronization method
Physical interface
synchronization from 1PPS&ToD of external GNSS Receiver
sync input interface
synchronization from 2.048MHz signal
sync input interface
synchronization from PDH interface
PDH interface on FTIF
Timing over Packet with frequency synchronization
Ethernet interface
Timing over Packet with phase synchronization
Ethernet interface
Synchronous Ethernet
Ethernet interface
1PPS output
sync output interface
PDH synchronization output
PDH interface on FTIF
2.048MHz synchronization output
sync output interface
Example #1 This configuration assumes that the 2.048MHz and PDH synchronization outputs are provided by an SBTS. The SBTS operates in frequency synchronization mode and is connected to the synchronization sources other than SBTS. The permitted synchronization sources are presented in Figure 25: Example of SBTS synchronization configuration #1. The SBTS can provide frequency synchronized reference signal to the connected SBTS/BTS/node through the 2.048MHz and PDH outputs. Figure 25
Example of SBTS synchronization configuration #1 SBTS/BTS/ node PDH
GPS/GNSSRECEIVER 2.048MHz
2.048MHz
SYNCHRONOUSETHERNET PDH
SBTS
ToP WITH FREQUENCY SYNCHRONIZATION
174
DN09218825
SBTS/BTS/ node
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Example #2 This configuration assumes that the 2.048MHz and PDH synchronization outputs are provided by an SBTS. This configuration can be considered as a sub-set of the configuration in the first example. The SBTS operates as Sync Hub Slave in frequency synchronization mode and is connected to the SBTS PDH/2MHz synchronization signal provided from the Sync Hub Master. The SBTS Sync Hub Slave can provide frequency synchronized reference signal to the connected SBTS/BTS/node through the 2.048MHz and PDH outputs. Figure 26
Example of SBTS synchronization configuration #2
SBTS/BTS/ node
SBTS/BTS/ node PDH
SBTS/BTS/ node PDH 2.048MHz
SBTS/BTS/ node
PDH
2.048MHz
2.048MHz
SBTS/BTS/ node
SBTS SyncHubSlave
SBTS/BTS/ node
Example #3 This configuration assumes that the 2.048MHz and PDH synchronization outputs are provided by an SBTS which operates in phase synchronization mode. The permitted synchronization sources are presented in Figure 27: Example of SBTS synchronization configuration #3. The SBTS can provide frequency synchronized reference signal to the connected SBTS/BTS/node through the 2.048MHz and PDH outputs. Figure 27
Example of SBTS synchronization configuration #3
SBTS/BTS/ node
1PPS/ToD GPS/GNSSRECEIVER
2.048MHz
ToP WITHPHASESYNCHRONIZATION
PDH
SBTS SBTS/BTS/ node
Issue: 01E
DN09218825
175
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Example #4 This configuration assumes that the 1pps measurement signal is provided as a synchronization output by an SBTS which synchronizes to any synchronization source and operates in any synchronization mode. The operator can utilize the 1pps synchronization output signal as an input for delta measurements at an oscilloscope. By comparing the 1pps synchronization output signal to a dependable GPS receiver 1pps synchronization reference signal, the operator can verify whether the frequency and phase accuracy of an air interface is sufficient. When an SBTS works in phase synchronization mode, the operator can utilize the 1pps synchronization output signal as an input for a phase delta measurement to a dependable GPS receiver 1pps synchronization reference signal at an oscilloscope. When the GPS receiver 1pps synchronization input signal is utilized as reference for the measurements, the delay generated by the cable length from the GPS receiver to the synchronization input must be considered manually. When an SBTS works in frequency synchronization mode, the operator can utilize the 1pps synchronization output signal as an input for a frequency delta measurement to a dependable GPS receiver 1pps synchronization reference signal at an oscilloscope. Figure 28
Example of SBTS synchronization configuration #4 PDH
GPS/GNSSRECEIVER 2.048MHz SYNCHRONOUSETHERNET ToP WITH FREQUENCY SYNCHRONIZATION ToP WITH PHASESYNCHRONIZATION
3.36.1.4
1PPS
SBTS
System impact Interdependencies between features This feature requires one of the features: • • • • • •
SR000374: Timing over Packet with Frequency Sync SR000375: Synchronous Ethernet SR000376: Synchronization from 2.048MHz signal SR000377: Synchronization from PDH interface SR000383: Timing over Packet with phase synchronization SR000788: 1PPS&ToD Sync from External GNSS receiver
Impact on interfaces This feature has an impact on interfaces as beneath: •
The feature affects the external transport interfaces and synchronization outputs.
Impact on network and network element management tools This feature has no impact on network management or network element management tools.
176
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.36.1.5
SR000385: Synchronization Hub management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults There are no alarms and faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 104: New parameters lists parameters introduced with this feature. Table 104
New parameters
Full name
3.36.1.6
Managed object
CLOCKOUTPUTS object identifier
clockoutputsId
CLOCKOUTPUTS
Output configuration of 1PPS/ToD clock signal
outputConfiguration1Pps
CLOCKOUTPUTS
Output configuration of 2.048MHz clock signal
outputConfiguration2M048
CLOCKOUTPUTS
Output configuration of PDH clock signal
outputConfigurationPdh
CLOCKOUTPUTS
BTS synchronization mode
btsSyncMode
SYNC
Synchronization reference source list
referenceSourceList
SYNC
– Input reference
– inputReference
SYNC
Sales information Table 105
Issue: 01E
Abbreviated name
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
DN09218825
177
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
3.37 SR000375: Synchronous Ethernet 3.37.1 Description of SR000375: Synchronous Ethernet Introduction to the feature This feature provides Synchronous Ethernet (SyncE) mechanism as an optional synchronization source for frequency synchronization of the SBTS. This mechanism of synchronization is based on ITU-T Recommendation G.8261, ITU-T Recommendation G.8262 and ITU-T Recommendation G.8264.
3.37.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature introduces the mechanism which provides an accurate frequency synchronization reference for the SBTS via the packet network, comparable with SDH synchronization mechanism. In contrast to other packet-based synchronization mechanisms, the provided stability of recovered frequency does not depend on the network load or network impairments, as an example delay variation.
3.37.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.37.1.3
Functional description Overview This feature, in accordance with the ITU-T Recommendation G.8261, ITU-T Recommendation G.8262 and ITU-T Recommendation G.8264, introduces the mechanism of frequency synchronization distribution in the SBTS. The frequency data is obtained from the directly connected (next-hop) Ethernet switch or IP router via the Ethernet interface. When the Synchronous Ethernet mechanism operates on each transport node, the operator can determine a completely frequency-synchronized Ethernet network. In contrast to the TDM network, this frequency accuracy is not required for the proper operation of the data plane in the transport network, but rather to provide the devices connected to the transport network with an access to the reference clock. Synchronization Status Messages This feature provides the reception of Synchronization Status Messages (SSMs), in accordance with the ITU-T G.8264 standard, in order to validate the status of the synchronous Ethernet signal. The Synchronization Status Messages are a fundamental part of Synchronous Ethernet standards. The SSMs provide a mechanism for downstream Ethernet networks elements to determine the traceability of the
178
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
synchronization reference back to the PRC or the highest clock within the network. The operation mode of Synchronous Ethernet can be switched between operation with and without SSMs determined: •
•
3.37.1.4
In operation with SSMs enabled - the incoming Synchronous Ethernet signal is considered valid in the SBTS synchronization when the Quality Level (QL) which is contained in Synchronization Status Messages is equal or better than the operator configurable threshold (for example Primary Reference Clock PRC, Primary Reference Source PRS, Stratum 2 ST2, and Synchronization Supply Units SSU-A and SSU-B) and considered as invalid in the SBTS synchronization when the QL contained in the incoming Synchronization Status Messages is worse than the configured threshold. An alarm is generated when no valid SSM is obtained within a certain time interval. The defined threshold maps the QL into two groups: PRC/PRS (default) and ST2/SSU. The operator must take into account that the lower quality of provided Synchronous Ethernet signal is good enough to perform frequency synchronization. In normal conditions, the incoming reference is traceable to the Primary Reference Clock. In fault conditions, some of the clocks in the synchronization distribution chain enter hold-over mode or free-run mode and consequently the reference signal is not utilized as synchronization source signal anymore. The SBTS tries to switch to an alternative synchronization source and an alarm is raised. In operation with SSMs disabled - the QL of the incoming Synchronous Ethernet is always considered valid. The Synchronous Ethernet signal is synchronized to the Primary Reference Clock and the timing can be recover from an Ethernet interface which is traceable to the PRC. When the signal on the Ethernet interface is lost, an alarm is generated. Without SSM support, the network planning and the configuration of the network must be performed carefully. There is a risk of misconfiguration and the Ethernet signal may not carry timing reference to PRC. In addition, without SSM support, the hold-over and free-run modes cannot be configured on intermediate nodes in a synchronization distribution chain.
System impact Interdependencies between features This feature requires the feature: •
SR000847: BTS Synchronization Mode Support
This feature is the precondition for the feature: •
SR000385: Synchronization Hub
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
Issue: 01E
DN09218825
179
Descriptions of transport and transmission features
3.37.1.5
SRAN 16.2, Feature Descriptions
SR000375: Synchronous Ethernet management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults Table 106: New alarms and faults lists alarms and faults introduced with this feature. Table 106
BTS Fault ID
New alarms and faults
BTS Fault name
Reported alarms
61623
SyncE SSM Timed Out on unit $UID, interface $IF
7108 BASE STATION SYNCHRONIZATION PROBLEM
61624
SyncE Quality Level Degraded on unit $UID, interface $IF
7108 BASE STATION SYNCHRONIZATION PROBLEM
4299
Synchronous Ethernet reference missing
7108 BASE STATION SYNCHRONIZATION PROBLEM
Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 107: New parameters lists parameters introduced with this feature. Table 107
New parameters
Full name
180
Abbreviated name
Managed object
Clock mode configuration
clockMode
ETHLK
Ethernet interface used for SyncE reference
ethlkId
SYNCE
Acceptable SSM level
ssmAcceptanceLevel
SYNCE
SSM enabling flag
ssmEnabled
SYNCE
SSM message timeout
ssmTimeout
SYNCE
SYNCE object identifier
synceId
SYNCE
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.37.1.6
Descriptions of transport and transmission features
Sales information Table 108
Sales information
BSW/ASW
License control in network element
ASW
Pool License
License control attributes ON/OFF
3.38 SR000650: TDM fallback for GSM Application 3.38.1 Description of SR000650: TDM fallback for GSM Application Introduction to the feature This feature provides a transport backup path for an SBTS with GSM operating Packet Abis over Ethernet.
3.38.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature enables GSM service continuation in case of packet network unavailability.
3.38.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.38.1.3
Functional description Functional overview This feature provides a transport backup path for an SBTS operating Packet Abis over Ethernet. In case the packet network becomes unavailable it is possible to use an existing time-division multiplexing (TDM) connection and operate Packet Abis over MLPPP. The packet network is monitored by single or multiple Bidirectional Forwarding Detection (BFD) sessions. Depending on the use case, single hop or multi hop BFD sessions are applied. These sessions can be individually configured for use inside or outside of an IPSec tunnel. The status changes in BFD session trigger changes to: • •
Issue: 01E
routing entries to transmit the traffic over TDM links. IPSec policies to disable the encryption of GSM traffic (if IPsec is applied to Packet Abis traffic across the packet network).
DN09218825
181
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
A routing decision in downlink is made by the transport network, depending on the BFD status. The BSC receives a routing update via the dynamic routing. No traffic with exception to GSM traffic, is affected. IP addresses remain unchanged, regardless of whether GSM function is available using packet backhaul during normal operation or using TDM while fallback is active. While fallback is active, GSM BTS functions and transport functions (fault monitoring, performance monitoring and selected status information) can be monitored using GSM BSC O&M connection. The feature assumes that TDM ML-PPP terminates in a dedicated media conversion router. This ensures that media conversion is not affected in case of outage of the packet network due to broadcast or Address Resolution Protocol (ARP) storms. When the network recovers after a failure and the BFD sessions are up again, the SBTS delays the reinstallation of the bound static routes and IPsec policies for a configurable time. The changes to routing table and IPsec policies and thus the switching between Packet Abis over IP/Ethernet and Packet Abis over TDM do not require a GSM reset. TDM links can be continuously supervised by optional PPP echo to monitor the state of the backup path while not carrying GSM traffic.
g
Note: Alternatively, an additional BFD session can be used. This function is however not provided by this feature. Selection of the synchronization source is independent of the switchover and is based on the configured synchronization hierarchy. During TDM fallback the SBTS might select TDM as well as the synchronization source. Figure 29
TDM fallback mechanism SecGW 20.20.10.1
EthernetIF 10.10.10.10 VirtualIF 10.10.20.11WCDMA 10.10.20.12LTE 10.10.20.13GSM 10.10.20.14M-plane
PSec UDP/P Ethernet
10.10.10.1
40.40.30.2
40.40.30.1 AR
Access Network BFDMH1/2
10.10.20.2PPP 10.10.20.1 2GUP/CP/MP IP ML-PPP E1/TDM
PE
Aggregation Network
40.40.10.2 Metric10 40.40.10.1 40.40.20.1
NoIPecvia TDMforGSM Metric100 MSR 40.40.20.2
BSC 40.40.20.9
Relationship to other redundancy mechanisms There are networks which support redundant packet network paths to the SBTS with respect to a single BSC and fast IP rerouting or any dynamic routing protocol is applied. In this case, customer needs to ensure by proper timer configuration that these mechanisms are used first and the other packet network path is used instead of TDM. There are networks which support a backup IPsec gateway. In this case the operator needs to ensure that the backup IPsec tunnel is used first and the backup IPsec gateway is used instead of TDM.
182
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
In any case it needs to be ensured that the BFD session(s) which are selected as a trigger for TDM fallback are terminated at a location in the network that is common for both packet network paths to the SBTS and both IPsec gateways. In case BSC redundancy/pooling is applied, TDM fallback provides only a backup path for the primary BSC. BTS solution details This feature introduces the SBTS capability to logically combine the status of multiple BFD sessions and install or uninstall static routes and IPsec policies based on the outcome: •
• •
As long as the BFD session or logically combined BFD sessions are up, bound static routes are applied based on the given metric/preference values and longest prefix match rules. As long as the BFD session or all logically combined BFD sessions are down, bound IPsec policy rules are applied. When the BFD session and all logically combined BFD sessions are down, TDM fallback path is used.
The configuration in SBTS needs to ensure that these BFD session(s) are never carried using the TDM path. The feature builds on the following existing functionalities: • •
The BFD session(s) can start at any configured virtual, alias, or BTS interface IP address. The GSM application can be bound to any configured virtual, alias, or BTS interface IP address, and can be separated from other applications.
For efficient configuration in case of network layer backhaul, one virtual IP address is used to exclusively bind GSM application and for the BFD sessions. BSC/BSC site solution details mcBSC L3 connectivity is applied. That means that routing is enabled on basic mcBSC modules. In addition to the BSC site routers, a dedicated media conversion router is connected directly to the Ethernet backhaul interfaces of the two mcBSC basic modules. All routers including the mcBSC need to share the same open shortest path first (OSPF) domain.
3.38.1.4
System impact Interdependencies between features This feature requires the following features: • • • • • •
SR000176: ML-PPP Termination SR000350: Ethernet Termination SR000361: Link Supervision with BFD SR000344: Fast IP Rerouting SR000356: IPsec for BTS BSS101431: L3 Connectivity for Multicontroller BSC
Related features: •
Issue: 01E
SR000600: Backup IPsec Tunnel
DN09218825
183
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: • • •
3.38.1.5
System performance and capacity are not degraded. The switchover time must be less than one second starting from the fault detection. The overall GSM radio application performance is limited by the currently available bandwidth of the transport connections.
SR000650: TDM fallback for GSM Application management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no measurements or counters related to this feature. Parameters Table 109: New parameters lists parameters introduced with this feature. Table 109
New parameters
Full name
184
Abbreviated name
Managed object
Trigger identifier
triggerId
IPRT
Trigger identifier
triggerId
IPRTV6
Trigger identifier
triggerId
SECPOL
False to true delay
false2TrueDelay
TRIGGER
List of considerable items
itemList
TRIGGER
item pointer
itemPointer
TRIGGER
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 109
Descriptions of transport and transmission features
New parameters (Cont.)
Full name
3.38.1.6
Abbreviated name
Managed object
Logical operation
logic
TRIGGER
TRIGGER object identifier
triggerId
TRIGGER
True to false delay
true2FalseDelay
TRIGGER
Sales information Table 110
Sales information
BSW/ASW
License control in network element
BSW
-
3.39 SR000384: Timing over Packet Resilience 3.39.1 Description of SR000384: Timing over Packet Resilience Introduction to the feature This feature enables the usage of more than one Timing over Packet (ToP) Master for mechanism of SBTS synchronization. Having the ToP Masters (timing masters) at different sites provides protection against network malfunctions. This mechanism of synchronization is based on the IEEE1588v2-2008 standard.
3.39.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the operator possible redundancy of the ToP Master equipment and therefore increasing the reliability of the synchronization. The feature provides protection against the timing master and network malfunctions.
3.39.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.39.1.3
Functional description Overview
Issue: 01E
DN09218825
185
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
This feature enables the usage of more than one Timing over Packet (ToP) Master for mechanism of SBTS synchronization. Having the ToP Masters (timing masters) at different sites protects against network malfunctions. The ToP Slaves (timing slaves) are configured to connect with up to four ToP Masters within the network and synchronize with one of them at a time. The ToP Master selection is based on the configurable Acceptance master table which contains the ToP Masters to which the ToP Slaves are permitted to synchronize. The IP address and the priority of each ToP Master are provided within the table. The Acceptance master table has up to four entries which are corresponded with the accepted clock class quality. The table is configurable. The permitted values are determined in accordance to the profile. In the IEEE profile, the permitted values are 6, 7, 13, and 14. In the ITU-T Opt I, the permitted values are 84, 90, and 96 whereas in the ITU-T Opt II profile - the 80, and 86 values are permitted. This feature enables various redundancy schemes in the SBTS. The supported protection schemes are 1+1 and N:1. In the 1+1 protection, there is one active ToP Master and the other one for protection. In the N:1 protection, there are N active ToP Masters and one ToP Master for protection. In addition, this feature enables the configuration of the system in a manner that each of the N ToP Masters is defined as a primary ToP Master for the group of ToP Slaves and some of the capacity of each ToP Master is provided for protection of this group. This feature provides two different operation modes for SBTS synchronization: •
•
operation mode I) The timing slave in the SBTS requests the Announce messages from each of the timing masters in the SBTS. By receiving the Announce messages from the timing masters, the SBTS is continuously notified of the presence of the timing masters within the network. The Sync messages are requested only from the timing master which has the highest priority in the SBTS. By receiving the Sync messages from the timing master of the highest priority, the SBTS synchronizes with it. When the active timing master fails, a timing slave requests the Sync messages from a timing master which has the next priority and tries to synchronize with it. When the highest priority timing master is active again, the timing slave synchronizes with it again. operation mode II) The timing slave in the SBTS requests the Announce messages only from the timing master which has the highest priority in the SBTS. When this master fails, the Announce messages are requested from the next timing master in the priority order and simultaneously, a timing slave requests the Announce messages from all the timing masters of the higher priority. In this way, a timing slave is able to detect when the timing masters having the higher priority appear back from the malfunction and can synchronize with it again.
The advantage of operation mode I) is that a timing slave is continuously aware which timing masters are active on the network. In operation mode II), the master of the next priority is not necessarily active and this can be detected only after requesting Announce messages from the timing masters. 1:1 ToP Master protection In the 1:1 protection of ToP Master scenario, there is one active timing master and the other one is configured for protection. This scenario utilizes the operation mode I). The timing slave within the SBTS is configured with the IP addresses of both masters. The timing slave gets the Announce messages from both masters, the Sync messages are transmitted only from the active timing master. When the active timing master fails, the
186
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
timing slave requests Sync messages from the other timing master and switches the synchronization to the other timing master. When the first timing master is active again, synchonization is switched again to the first timing master. N:1 Master protection In the N:1 protection of ToP Master scenario, there are N active timing masters and one timing master configured for protection. In this scenario, each of the N masters is the primary timing master for a group of timing slaves. This scenario utilizes the operation mode II). The Acceptance master table of each SBTS is configured with the IP address of the primary timing master and with the IP address of the master for protection. Normally, timing slaves receive the Announce and Sync messages only from the primary timing master. When the primary timing master fails, each of the affected timing slaves requests the Announce and Sync messages from the protection master and switches the synchronization to it. At the same time, the timing slave continues to request the Announce messages from the primary timing master. In this way, the timing slave can detect when the primary timing master is active again and can synchronize with it again. When the primary timing master is active again, the timing slave stops to request the Announce and Sync messages from the secondary timing master and releases the obtained occupancy of the secondary timing master. The N:1 protection can be also configured to utilize the operation mode I) in which the Announce messages are constantly requested by the timing slaves from the secondary master. ToP Master protection with Load Sharing The ToP Master protection can be also configured in a manner in which each of the N masters is defined as a primary timing master for a group of timing slaves and certain amount of the capacity of each primary timing master is designated for the protection mechanism of a group of timing slaves. This scenario utilizes the operation mode II). Example In the example configuration (when both of two ports of each timing master are determined), there are four SBTS groups, each with up to 750 timing slaves. The four groups of SBTSs are configured to operate with four timing masters, and each timing master can operate with up to 750 timing slaves. The remaining capacity of each timing master is designated for protection mechanism which means that the other timing masters are evenly utilized by the other SBTS groups as protection master.
Issue: 01E
DN09218825
187
Descriptions of transport and transmission features
Figure 30
SRAN 16.2, Feature Descriptions
ToP Master protection with Load Sharing
SBTS groups
SLAVE
SLAVE
SLAVE
SLAVE
ToP Masters
M1
group1
M2
group2
Packet network M3
group3
M4
group4
Table 111
Example configuration of Acceptance masters table
SBTS group 1
SBTS group 2
Number of an SBTS N=1–250 N=251–500 N=501–750 N=1–250 N=251–500 N=501–750 Primary master
M1
M1
M1
M2
M2
M2
Protection master
M2
M3
M4
M1
M3
M4
SBTS group 1
SBTS group 2
Number of an SBTS N=1–250 N=251–500 N=501–750 N=1–250 N=251–500 N=501–750
3.39.1.4
Primary master
M3
M3
M3
M4
M4
M4
Protection master
M1
M2
M4
M1
M2
M3
System impact Interdependencies between features This feature requires the feature: •
SR000374: Timing over Packet with Frequency Sync
Impact on interfaces This feature has an impact on interfaces as beneath:
188
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
•
Descriptions of transport and transmission features
The feature provides the mechanism in which an SBTS can address up to four ToP Masters within the network but they must be configured first in the SBTS.
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: •
3.39.1.5
The feature provides the mechanism in which an SBTS can address up to four ToP Masters within the network but the capacity demands of ToP Master must be accommodated in the protection schemes.
SR000384: Timing over Packet Resilience management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults Table 112: New alarms and faults lists alarms and faults introduced with this feature. Table 112
BTS Fault ID 61631
New alarms and faults
BTS Fault name
ToP master service $IP unusable
Reported alarms
7108 BASE STATION SYNCHRONIZATION PROBLEM
Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 113: New parameters lists parameters introduced with this feature. Table 113
New parameters
Full name
Issue: 01E
Abbreviated name
Managed object
Accepted clock quality list (frequency)
acceptedClockQualityFreq
TOPF
ToP announce message mode
announceRequestMode
TOPF
ToP ieee telecom profile selection
ieeeTelecomProfile
TOPF
ToP masters properties table
topMasters
TOPF
DN09218825
189
Descriptions of transport and transmission features
Table 113
New parameters (Cont.)
Full name
3.39.1.6
SRAN 16.2, Feature Descriptions
Abbreviated name
Managed object
– IP Address of the ToP master
– masterIpAddr
TOPF
– Configured priority 1 for ToP master
– priority_1
TOPF
– Configured priority 2 for ToP master
– priority_2
TOPF
TOPF object identifier
topfId
TOPF
Sales information Table 114
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
3.40 SR000374: Timing over Packet with Frequency Sync 3.40.1 Description of SR000374: Timing over Packet with Frequency Sync Introduction to the feature This feature provides Timing over Packet (ToP) with frequency synchronization mechanism. The SBTS can be frequency synchronized to the ToP Master over the packet-based backhaul network. This mechanism of synchronization is based on the IEEE1588-2008 PTPv2 standard.
3.40.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature enables the operator to take complete advantage of the packet networks. When the packet network has sufficient quality, the SBTS can be accurately frequency synchronized to the ToP Master. This brings CAPEX and OPEX savings as TDM links and additional equipment are not required any more for SBTS frequency synchronization mechanism.
190
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.40.1.2
Descriptions of transport and transmission features
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF). This feature requires ToP Master to provide the synchronization to the SBTS.
3.40.1.3
Functional description Overview This feature provides Timing over Packet (ToP) with frequency synchronization mechanism over the packet-based backhaul network, based on IEEE15888-2008 PTPv2 standard. The mechanism comprises of the timing master named ToP Master, and the timing slaves named ToP Slaves. The timing master is a dedicated time server synchronized to the Primary Reference Clock (PRC) whereas the timing slave is embedded within the SBTS. The timing master provides the synchronization for the timing slaves by sending synchronization (SYNC) messages, which carry a timestamp, through the packet-based backhaul network, and the timing slaves recover the synchronization reference from these messages. The synchronization messages are transmitted over PTPv2/UDP/IPv4/Ethernet protocol. Unicast negotiation is used for communication among the timing slaves and the timing master. Timing over Packet mechanism is based on the IEEE1588-2008 standard features: •
•
•
•
•
Issue: 01E
timing master - timing master is synchronized to the Primary Reference Clock (PRC) and sends the synchronization messages to the timing slaves. The timing slaves within the SBTS are configured with the IP address of the timing master. In order to obtain more reliability, the timing master supports redundancy. When the primary timing master fails, the redundant master is taken into operation and adopts the IP address from the primary timing master. At any given time, only one timing master, either the primary or the redundant one, can be active. Viewed from the timing slave placed within the SBTS, there is one single IP address under which it finds the timing master (one and only) that is active in the system. When a switchover from primary timing master to redundant timing master takes place, the timing slave must determine the MAC address of the active timing master. timing slave - timing slave recovers the frequency synchronization from the synchronization messages transmitted by the timing master. The timing slave generates an indication when it is out of lock. The maximum locking time value of timing slave is fifteen minutes. The locking time achieved with a certain synchronization packet rate depends on the packet delay variation in the network among the timing master and the timing slave. High packet delay variation can provide longer locking times. synchronization (SYNC) messages - synchronization messages carry the primary timing data provided from the timing master to the timing slaves and they are timestamped both at the transmission and at the receipt of the message. More information on synchronization and other message types is provided in the PTP general and event messages section. unicast - unicast is the communication mode in which the timing master sends synchronization messages to the timing slave via PTP unicast mode based on the PTP/UDP/IPv4/Ethernet protocol. unicast detection and unicast negotiation - unicast detection and unicast negotiation mechanisms are used for configuring the slave and to start unicast communication among the timing master and the timing slaves. Unicast detection means that the
DN09218825
191
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
timing slave is configured with the address of the timing master. The use of unicast detection/unicast negotiation has the advantage that when the new timing slaves are added to the network, only the timing slaves must be configured then. More information on unicast negotiation mechanism is provided in the PTP unicast negotiation section. PTP general and event messages The IEEE1588-2008 standard determines various message types. The timing master and the timing slaves communicate through the messages in accordance to the PTP protocol with a protocol stack that has UDP/PTP/IP hierarchy. In case of frequency synchronization, only the synchronization (SYNC) messages are required. The synchronization messages are the event messages. They are time-stamped both at the transmission and at the receipt of the message. A port with a 319 number is defined for UPD source and destination port for event messages. The SYNC messages are used to generate and communicate the timing information which is required to synchronize the timing slaves with the timing master. The timing master and the timing slaves, apart from the synchronization messages, provide support for the general messages: signaling (SIGNALING) message and announce (ANNOUNCE) messages. The general messages has the UDP source and destination port with a 320 port number. The signaling messages are used for unicast negotiation mechanism among the timing master and the timing slaves whereas the announce messages are used to determine the synchronization hierarchy. The announce messages are also utilized to find the best master clock under use of the best master clock algorithm. PTP unicast negotiation The PTP unicast negotiation mechanism is utilized to initiate and maintain a unicast connection among the timing master and timing slave. By the unicast negotiation mechanism, the timing slave requests the timing master to transmit unicast announce and synchronization messages to the timing slave. The communication is carried out with Request_Unicast_Transmission TLV and Grant_Unicast_Transmission TLV. The timing slave transmits a signaling message with Request_Unicast_Transmission TLV which comprises of the requested message rate, type (synchronization or announce), and the requested duration of unicast transmission. The announce message rate is determined to a fixed value of one message transmitted once for two seconds. The synchronization message rate can be defined from 8, 16, and 32 times for a second with default value of 16. The timing master confirms then the requested unicast transmission with Grant_Unicast_Transmission TLV which contains the granted duration and the granted message rate. When the requested message rate cannot be provided, the timing master rejects the request through setting the duration field to 0. Once a unicast transmission is determined, the timing master transmits the announce and synchronization messages to the timing slave until the grant duration expires. The timing slave requests a new unicast grant well before the current grant duration expires. When the unicast grant is not received (for example due to the transport failures), the timing slave repeats the request after a five seconds timeout. The request repeat is performed two more times when the grant is not received. When the grant is still not obtained, the timing slave raises an alarm.
3.40.1.4
System impact Interdependencies between features This feature requires the feature:
192
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
•
Descriptions of transport and transmission features
SR000847: BTS Synchronization Mode Support
This feature is the precondition for the features: • •
SR000384: Timing over Packet Resilience SR000385: Synchronization Hub
Impact on interfaces This feature has an impact on interfaces as beneath: •
The feature provides the mechanism in which an SBTS supports a single IP address communicating towards the ToP Master system.
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.40.1.5
SR000374: Timing over Packet with Frequency Sync management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults Table 115: New alarms and faults lists alarms and faults introduced with this feature. Table 115
BTS Fault ID
New alarms and faults
BTS Fault name
Reported alarms
61631
ToP master service $IP unusable
7665 BASE STATION TRANSMISSION ALARM
4298
ToP reference missing
7108 BASE STATION SYNCHRONIZATION PROBLEM
4323
ToP configuration mismatch
7108 BASE STATION SYNCHRONIZATION PROBLEM
Measurements and counters Table 116: New counters lists counters introduced with this feature. Table 116
Counter ID M51361C0
Issue: 01E
New counters
Counter name topRxFreqSyncMsg
DN09218825
Measurement TOP FreqSync Statistics
193
Descriptions of transport and transmission features
Table 116
SRAN 16.2, Feature Descriptions
New counters (Cont.)
Counter ID
Counter name
Measurement
M51361C1
topMinFreqSyncError
TOP FreqSync Statistics
M51361C2
topAvgFreqSyncError
TOP FreqSync Statistics
M51361C3
topMaxFreqSyncError
TOP FreqSync Statistics
M51361C4
topFreqSyncSLS
TOP FreqSync Statistics
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 117: New parameters lists parameters introduced with this feature. Table 117
New parameters
Full name
194
Abbreviated name
Managed object
TOP FreqSync statistics measurement interval
topFreqSyncStatisticsInterval
PM
Synchronization reference source list
referenceSourceList
SYNC
– Input reference
– inputReference
SYNC
– Input reference priority
– inputReferencePriority
SYNC
Synchronization plane DSCP
sPlaneDscp
TOP
Synchronization plane IP address
sPlaneIpAddress
TOP
ToP domain number
topDomainNumber
TOP
TOP object identifier
topId
TOP
Accepted clock quality list (frequency)
acceptedClockQualityFreq
TOPF
ToP ieee telecom profile selection
ieeeTelecomProfile
TOPF
ToP masters properties table
topMasters
TOPF
– IP Address of the ToP master
– masterIpAddr
TOPF
Synchronisation message rate
syncMessageRate
TOPF
TOPF object identifier
topfId
TOPF
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
3.40.1.6
Descriptions of transport and transmission features
Sales information Table 118
Sales information
BSW/ASW
License control in network element
ASW
Pool License
License control attributes ON/OFF
3.41 SR000383: Timing over Packet with phase synchronization 3.41.1 Description of SR000383: Timing over Packet with phase synchronization Introduction to the feature This feature enables phase and time synchronization of an SBTS via the packet network. Phase and time synchronization mechanism is mandatory in FDD LTE mode in certain advanced applications (for example in the eICIC). This mechanism of synchronization is based on the IEEE1588-2008 PTPv2 standard.
3.41.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides that the GPS equipment is not mandatory anymore to be connected with an SBTS to provide phase and time synchronization to this SBTS. In addition, the feature provides that, as phase and time synchronization can now be provided in areas where the GPS equipment cannot be placed, the flexibility of the site deployment mechanism is enhanced.
3.41.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
3.41.1.3
Functional description Overview This feature enables phase and time synchronization of an SBTS via the packet network. Phase and time synchronization mechanism is mandatory in FDD LTE mode in certain advanced applications (for example in the eICIC). The synchronization reference is provided via the Timing over Packet mechanism. With the introduced feature, this mechanism is enhanced and includes now phase and time synchronization.
Issue: 01E
DN09218825
195
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Timing over Packet mechanism is based on the IEEE1588-2008 PTPv2 standard. The entire solution includes the timing grandmaster named ToP Master, intermediate nodes with and without the on-path PTP support - transparent/boundary clock mechanisms, and the timing slaves named ToP Slaves embedded in the SBTS. The timing grandmaster requires a timing reference traceable to standardized timescale. The timing grandmaster is time adjusted to the GPS time and PTP time which are the standardized continuous timescales. The timing grandmaster can be connected to multiple SBTSs concurrently meaning that having to deploy the GPS equipment at each SBTS is not mandatory anymore. The communication among the timing slaves and the timing grandmaster is based on the bidirectional communication mechanism: synchronization, announce, delay response, and follow up messages are transmitted from the timing grandmaster to the timing slaves, and the timing slaves transmit the delay request to the grandmaster. The boundary clock has multiple master and slave ports and operates as a master to the next clock in the synchronization chain. The first boundary clock in chain communicates with the grandmaster and the timing slave embedded in the SBTS communicates directly only with the nearest boundary clock. The boundary clock mechanism terminates the PTPv2 protocol, the transparent clock does not. This clock enables the residence time correction field. Both mechanisms can be combined. This feature provides different operation modes: •
•
PTP/UDP/IPv4/Ethernet with Unicast operation - this mode is recommended for the configuration with only partial PTP on path support. The timing slave is not directly connected to the node with the on-path PTP support and not all intermediate nodes provide the on-path support. The timing slave can be directly connected to the node with the on-path PTP support but still there are intermediate nodes which do not provide the on-path support in the synchronization chain. This mode can also be configured in a full on path support but this means that the configuration has to be performed in each on-path support node which increase the complexity of the configuration. PTP/Ethernet with Multicast operation - this mode is recommended for the network configuration with the full on-path PTP support. The timing slave is directly connected to the node with the on-path PTP support and all intermediate nodes among the grandmaster and the slaves provide the on-path support - boundary clock mechanism/transparent clock mechanism.
PTP/UDP/IP with Unicast operation Timing over Packet with phase synchronization operates with partial on-path PTP timing configuration and utilizes the recommended Unicast operation mode. In this timing configuration, one or more routers in the timing network works as an intermediate node with the boundary clock mechanism. Other routers do not have any PTP mechanisms and they transmit the PTP data without performing any modifications. Partial on-path configuration helps the operators to reduce the expense in upgrading the timing network with the on-path support. But on the other hand, this comes at the expense of that the phase synchronization accuracy in the timing slave is decreased. The operators have to perform a careful analysis and design of the timing network to have appropriate compromise between the expense of the partial on-path support and the accuracy of the phase synchronization required in certain applications.
196
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of transport and transmission features
Figure 31
PTP/UDP/IP with Unicast operation BC – BOUNDARY CLOCK E2ETC – END TO!END TRANSPARENT CLOCK GM – GRANDMASTER!CLOCK M – IEEE1588!MASTER!PORT S – IEEE1588!SLAVE!PORT
S E2ETC BC
E2ETC S M
S
E2ETC S
CONTROLLER M
E2ETC
1588 GM
TIME REFERENCE
S SBTS
PTP |!UDP |!IP UNICAST
PTP/Ethernet with Multicast operation Timing over Packet with phase synchronization operates with full on-path PTP timing configuration and utilizes the recommended Multicast operation mode. In this timing configuration, each network element on a PTP traffic path among the timing grandmaster and the embedded slave supports the end-to-end transparent clock/boundary clock mechanism. The configuration presented below includes an L2 switch and L3 routers among the timing grandmaster and the embedded slaves but the configuration can also contains the L2 switches only. Routers and switches must provide the boundary clock mechanism which supports the PTP communication operating in the Ethernet multicast communication mode. Ethernet multicast is the most convenient communication mode when each network element in the timing configuration supports the transparent clock mechanism/boundary clock mechanism. The Ethernet multicast communication mode corresponds to the multicast address. This multicast address can be either forwardable or non-forwardable multicast address, as determined in the IEEE1588-2008 PTPv2. The forwardable multicast address is a predefined standard multicast address. When this address is utilized, the network elements without the on-path support, transmit the PTP data to the next network element in the chain. The non-forwardable multicast address is an adress which is limited for the linkconstrained protocols. With this multicast address, the network elements, which do not provide the on-path support, cannot transmit the PTP data to the next network element, and the PTP communication is limited to the local link only. The network element, which provides the boundary clock, cannot transmit the PTP data, independently from the used multicast address. This means that the PTP frames are terminated at the boundary clock and are not further transmitted in the timing network operating in the Ethernet multicast communication mode.
Issue: 01E
DN09218825
197
Descriptions of transport and transmission features
Figure 32
SRAN 16.2, Feature Descriptions
PTP/Ethernet with Multicast operation
PTP |!ETHERNET MULTICAST BC – BOUNDARY CLOCK E2ETC – END TO!END TRANSPARENT CLOCK GM – GRANDMASTER!CLOCK M – IEEE1588!MASTER!PORT S – IEEE1588!SLAVE!PORT
BC M
S E2ETC E2ETC
BC
S M S E2ETC S
CONTROLLER M
BC
E2ETC
1588 GM
M
TIME REFERENCE
S S SBTS
PTP |!ETHERNET MULTICAST
Both unicast and multicast modes support the end-to-end transparent clocks among the grandmaster and the embedded slaves. The transparent clocks, from the PTP grandmaster and embedded slaves point of view, are transparent with the exception when they populate the residence time correction field provided to the synchronization and delay request messages. This correction field can be utilized by the timing slave to compensate the inherent delay introduced by the node with the transparent clock mechanism and thus increase the accuracy of the phase synchronization.
3.41.1.4
System impact Interdependencies between features This feature requires the feature: •
SR000847: BTS Synchronization Mode Support
This feature affects the features: • • •
SR000350: Ethernet Termination SR000402: BTS QoS Support for Terminated and Routed Traffic SR000589: IPv4/IPv6 Transport Stack
This feature is the precondition for the feature: •
SR000385: Synchronization Hub
Impact on interfaces This feature has an impact on interfaces as beneath:
198
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
•
Descriptions of transport and transmission features
The feature provides the management interface of the embedded timing slave to configure the embedded timing slave clock, obtain the performance and fault data, and the internal and external interface to provide phase and time output data.
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: •
3.41.1.5
The feature has an impact on the performance of the dependent features when the determined phase synchronization accuracy of an SBTS is not maintained.
SR000383: Timing over Packet with phase synchronization management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults Table 119: New alarms and faults lists alarms and faults introduced with this feature. Table 119
BTS Fault ID
New alarms and faults
BTS Fault name
Reported alarms
4298
ToP reference missing
7108 BASE STATION SYNCHRONIZATION PROBLEM
4323
ToP configuration mismatch
7108 BASE STATION SYNCHRONIZATION PROBLEM
Measurements and counters Table 120: New counters lists counters introduced with this feature. Table 120
Counter ID
Issue: 01E
New counters
Counter name
Measurement
M51362C0
topRxPhaseSyncMsg
TOP PhaseSync Statistics
M51362C1
topMinPhaseSyncError
TOP PhaseSync Statistics
M51362C2
topAvgPhaseSyncError
TOP PhaseSync Statistics
M51362C3
topMaxPhaseSyncError
TOP PhaseSync Statistics
M51362C4
topPhaseSyncSLS
TOP PhaseSync Statistics
DN09218825
199
Descriptions of transport and transmission features
SRAN 16.2, Feature Descriptions
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 121: New parameters lists parameters introduced with this feature. Table 121
New parameters
Full name
3.41.1.6
Managed object
TOP PhaseSync statistics measurement interval
topPhaseSyncStatisticsInterv al
PM
Synchronization reference source list
referenceSourceList
SYNC
– Input reference
– inputReference
SYNC
– Input reference priority
– inputReferencePriority
SYNC
Synchronization plane DSCP
sPlaneDscp
TOP
Synchronization plane IP address
sPlaneIpAddress
TOP
ToP domain number
topDomainNumber
TOP
TOP object identifier
topId
TOP
Accepted clock quality table (phase)
acceptedClockQualityPhase
TOPP
ToP master
topMasters
TOPP
– IP address of the ToP master
– masterIpAddr
TOPP
Phase error compensation
phaseErrorComp
TOPP
Synchronisation message rate
syncMessageRate
TOPP
ToP communication mode
topComMode
TOPP
ToP over Ethernet multicast address
topEthMulticastAddress
TOPP
TOPP object identifier
toppId
TOPP
Sales information Table 122
200
Abbreviated name
Sales information
BSW/ASW
License control in network element
ASW
Pool License
DN09218825
License control attributes ON/OFF
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
4 Descriptions of operability features 4.1 SR000832: Flexi BTS and its Transport Parameter Categorization 4.1.1 Description of SR000832: Flexi BTS and its Transport Parameter Categorization Introduction to the feature This feature introduces parameter categories called Basic and Advanced for all Flexi BTS and Flexi BTS Transport configuration management parameters which are managed with NetAct CM Editor and/or NetAct Plan Editor applications.
4.1.1.1
Benefits End-user benefits This feature does not affect end user experience. Operator benefits Operators can reduce its operating expenses (OPEX) by simplification of the plan file and limitation on the number of basic parameters to be managed via NetAct CM tools: • • •
4.1.1.2
simplified network parametrization, faster product roll outs and less effort for competence development, reduces human effort needed for daily BTS maintenance tasks.
Requirements Hardware requirements This feature does not require any new or additional hardware.
4.1.1.3
Functional description This feature extends the LTE BTS concept of CM (configuration management) parameter categorization for: • • • • • •
GSM Flexi BTS CM parameters, GSM BTS Flexi Transport CM parameters, WCDMA Flexi BTS CM parameters, WCDMA Flexi BTS Transport CM parameters, SBTS CM parameters, common Flexi BTS Transport CM parameters.
Basic parameters category is meant for parameters used during cell deployment that are adjusted to particular scenario. Advanced parameters category holds the network optimization and fine tuning parameters (including those related to advanced or complex features).
Issue: 01E
DN09218825
201
Descriptions of operability features
SRAN 16.2, Feature Descriptions
NetAct CM Editor and NetAct Plan Editor allow operator to select and use any of following UI filtering options for CM parameters: • • •
4.1.1.4
all parameters (all parameters are visible), basic parameters (parameters belonging to basic category are visible), advances parameters (parameters belonging to advanced category are visible).
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.1.1.5
SR000832: Flexi BTS and its Transport Parameter Categorization management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Commands There are no commands related to this feature.
4.1.1.6
Sales information Table 123
Sales information
BSW/ASW BSW
202
License control in network element -
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
4.2 SR001453: Offline SCF Conversion from Three Dedicated RATs to SRAN 4.2.1 Description of SR001453: Offline SCF Conversion from Three Dedicated RATs to SRAN Introduction to the feature This feature introduces a Site Configuration File (SCF) conversion script which supports offline conversion from two or three existing BTSs of different technologies to one SBTS. This feature provides a procedure to simplify offline migration of two or three different RAT configurations to one SBTS as well. For instructions on 3RAT SCF merge script instruction, see Release Documentation > SBTS16.2_1.0_3-RAT_Merge_script_instructions available in NOLS.
4.2.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • • •
4.2.1.2
Introducing the SCF conversion script to support the merge of existing two or three BTSs of different technologies into one SBTS. Helping the customer at SCF creation as a part of the migration process from two or three dedicated RATs to SRAN. Enabling faster migration process when introducing SRAN.
Requirements Software requirements The SCFs files used as an input for the SCF conversion script can come from the following software releases: • • •
LTE releases: LN7.0 or FL15A WCDMA releases: WN9.1 or WBTS16 GSM release: GF16.0
The SCF output file, which is a result of SCF conversion script usage, has to be used with SBTS 16.2 software. Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.2.1.3
Functional description Offline conversion from two or three dedicated RATs to one SBTS
Issue: 01E
DN09218825
203
Descriptions of operability features
SRAN 16.2, Feature Descriptions
The SCF conversion script supports a merger of two or three commissioning files (SCFs) from existing BTSs into one SBTS SCF. The existing SCFs come from different technologies. Additionally, an SBTS profile is required. The input SCFs should match the SBTS profile and they cannot exceed the configuration included in the SBTS profile. Acceptable input variants are as follows: • • •
LTE SCF, WCDMA SCF, SBTS profile LTE SCF, GSM SCF, SBTS profile LTE SCF, WCDMA SCF, GSM SCF, SBTS profile
The LTE SCF file is a master data for this merger, hence it is mandatory. All parameters by default come from the LTE SCF file. These parameters are checked with other SCFs from WCDMA and/or GSM. Possible conflicts are visible in a report generated after the script execution.
g
Note: The SCF conversion script is helpful in defining an SBTS SCF from two or three RATs legacy SCFs. But before loading the merged SBTS SCF file on SBTS, manual check is needed. In case of any parameters conflicts, the operator has to update these parameters manually. The following releases are supported: • • • • •
RL70 FL15A RU50EP1 WCDMA16 GF16
Figure 33
Offline conversion from three dedicated RATs to SBTS
SBTS profile
LTESCF mandatory
WCDMA SCF
GSMSCF
SBTS16.2 SCF
Note that the functionality of migration a single SCF to an SBTS SCF is described by the SR001118: SBTS Configuration file conversion from WCDMA or LTE feature. Migration report
204
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
Migration process delivers a detailed migration report. Any additional manual corrections are possible to perform in the output SCF file. Migration report informs a user of all conducted operations, enables detection of inconsistencies or provides missing parameters. The migration report contains the following entries: 1. Basic information: • • •
Date and time of migration operation Software versions used as input SCF files Selected SBTS profile
2. Parameters that require the user attention (conflicts or missing parameters): • •
Parameters/MOs conflicts Missing parameters/MOs
3. New antenna line (ANTL) mapping 4. New cell mapping 5. The list of operations
4.2.1.4
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.2.1.5
SR001453: Offline SCF Conversion from Three Dedicated RATs to SRAN management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters
Issue: 01E
DN09218825
205
Descriptions of operability features
SRAN 16.2, Feature Descriptions
There are no parameters related to this feature.
4.2.1.6
Sales information Table 124
Sales information
BSW/ASW
License control in network element
Basic Software (BSW)
No
4.3 SR000989: SBTS - Minimizing Drive Tests (MDT) 4.3.1 Description of SR000989: SBTS - Minimizing Drive Tests (MDT) Introduction to the feature This feature introduces 3GPP standardized MDT measurement support for SBTS.
4.3.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides OPEX savings by minimizing the need for drive testing.
4.3.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.3.1.3
Functional description The Nokia MDT feature is designed to replace expensive drive testing and is intended for use during network deployment, optimization and operation. The MDT feature is designed to provide a sufficient amount of data in a simple and cost efficient way to allow the operator to make a complete analysis of the network behavior in an area. As a result of this the coverage can be optimized. The MDT feature offers: • •
MDT measurements are added in the Trace Data. Different pre-defined MDT profiles which can be selected in NetAct Trace Viewer application by an operator.
Nokia MDT is based on the existing definitions of MDT 3GPP 37.320 Rel10. However, support of Rel10 is not required from UEs and infrastructure. This feature is designed to work with UEs with Rel8 or Rel9.
206
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
The measurement requests the UE to create a large load on the network. Therefore it is not recommended to apply the MDT feature to the whole network at the same time. The main focus of the MDT feature is to provide the MDT measurements for upper layer applications. The data is available to NetAct Trace Viewer or to 3rd party IP addresses, such as protocol analyzers. MDT measurements are part of the Cell Trace functionality. Figure 34
Figure 1 SBTS – Minimizing Drive Test (MDT)
DCH
RNC
SBTS (LTE+ WCDMA)
4.3.1.4
Data Collector
Trace Viewer
Data Collector
Traffica CLA Etc.
System impact Interdependencies between features This feature requires the feature: •
SR000937: SBTS LTE Trace
This feature includes the support for the following features: • • •
g
LTE953: Minimization of Drive Tests LTE1049: MDT - UE measurement logs RAN2496: 3GPP Minimization of the Drive Tests Note: NOTE: SR000989: SBTS Minimizing Drive Tests works under the same licenses as the above features
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.3.1.5
SR000989: SBTS - Minimizing Drive Tests (MDT) management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms
Issue: 01E
DN09218825
207
Descriptions of operability features
SRAN 16.2, Feature Descriptions
There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
4.3.1.6
Sales information Table 125
Sales information
BSW/ASW
License control in network element
ASW
-
4.4 SR000910: SBTS Antenna Line Management 4.4.1 Description of SR000910: SBTS Antenna Line Management Introduction to the feature With SR000910: SBTS Antenna Line Management feature, the operator is able to operate and maintain antenna line devices (RETs and MHAs) that are connected to the SBTS. RET (Remote Electrical Tilt) is a device that allows the operator to optimize the network by adjusting remotely the down tilt of an antenna without visiting the site. MHA (Mast Head Amplifier) is an external low noise amplifier that optimize uplink performance by compensating the loss of an antenna feeder, and improving signal-tonoise ratio (SNR).
4.4.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits With this feature, the operator can optimize network performance using RET and MHA devices.
4.4.1.2
Requirements Hardware requirements This feature adds support for AISG 2.0 compatible single/multi RETs and MHAs. For the list of MHA units recommended by Nokia, see SRAN supported MHAs.
208
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
For the list of supported RET units recommended by Nokia, see SRAN supported RETs.
g 4.4.1.3
Note: Nokia does not guarantee proper operation for devices other than recommended. The maintenance support, including potential malfunctions fixing, is limited to the devices officially approved by Nokia.
Functional description This feature provides support for RET and MHA devices. RET support covers Nokia approved single-RET and multi-RET devices. RET devices are connected to the Radio Module via an integrated RET port (using RS458 connector) or via RF-antenna port (in the second case additional devices are required, for example Bias-T unit). If the MHA unit is used in the configuration, RS485 connector from the MHA unit can be used to connect RET. RET chaining is also supported by this feature. With RET support, the operator can detect, commission, control and monitor RET devices. MHA support covers Nokia approved single- and dual band MHAs. With MHA support, the operator can detect, commission, operate and monitor MHAs. Nokia BTS supports AISG 2.0 MHAs and Current Window Alarming (CWA) MHAs.
4.4.1.4
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: • •
4.4.1.5
Usage of MHA optimizes uplink performance by compensating the loss of antenna feeder. RET facilitates the network coverage adjustments.
SR000910: SBTS Antenna Line Management management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. BTS faults and reported alarms Table 126 Fault ID
BTS faults related to SR000910: SBTS Antenna Line Management Fault name
Reported alarms Alarm ID
1806
Issue: 01E
Communication failure
DN09218825
7101
Alarm name
RESET NOTIFICATION
209
Descriptions of operability features
Table 126 Fault ID
SRAN 16.2, Feature Descriptions
BTS faults related to SR000910: SBTS Antenna Line Management (Cont.) Fault name
Reported alarms Alarm ID
1834
1835
1836
1837
1838
1842
Alarm name
7104
CELL SERVICE PROBLEM
7105
RAT BASE STATION PROBLEM
7106
SINGLE RAN BASE STATION PROBLEM
Mast Head Amplifier above current window fault
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
Mast Head Amplifier below current window fault
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
Antenna line failure
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
Antenna line device HW failure
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
Antenna line device missing software
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
MHA unit operation failure
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
MHA operation failure
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
VSWR major alarm
VSWR minor alarm
RET antenna control failure
1843 1844 1845 1846 1847
1848
1869
1870
1871
Antenna line device operation failure
1872 1873 1874 4069
RS485 IUANT port failure 7100 7104
210
DN09218825
HARDWARE PROBLEM CELL SERVICE PROBLEM
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
Table 126
BTS faults related to SR000910: SBTS Antenna Line Management (Cont.)
Fault ID
Fault name
Reported alarms Alarm ID
4235
4270
Alarm name
out of range
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
MHA in bypass mode
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
Measurements and counters Table 127
Counters related to SR000910: SBTS Antenna Line Management
Counter ID
Counter name
Measurement SBTS Antenna Line
M40001 AVERAGE VALUE OF VSWR C0
Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
4.4.1.6
Sales information Table 128
g
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
Note: The usage of RET and MHA units is to be licensed as ASW in future SRAN releases.
4.4.2 SRAN supported MHAs List of Masthead Amplifier (MHA) units supported by SRAN system. Table 129
SRAN compatible MHA units
Name
Issue: 01E
Band
Control Protocol
Number of antenna ports
Sales code
FLPA
APT700 (low band)
AISG 2.0
2
473052A
FLPB
APT700 (high band)
AISG 2.0
2
473053A
FLMB
800
AISG 2.0
2
472979A
MDTB
850
AISG 2.0 or Current Window Alarm
2
473060A
DN09218825
211
Descriptions of operability features
Table 129
SRAN 16.2, Feature Descriptions
SRAN compatible MHA units (Cont.)
Name
Band
Number of antenna ports
Sales code
MDGB
900
AISG 2.0 or Current Window Alarm
2
473058A
MDDB
1800
AISG 2.0 or Current Window Alarm
2
472980A
MDPB
1900
AISG 2.0 or Current Window Alarm
2
473059A
WMHD
2100
AISG 2.0 or Current Window Alarm
2
471443A
FLHA
2600
AISG 2.0
2
472105A
FLDA
EU800/900
AISG 2.0 (two AISG modems)
2
CS7299440
FLDB
EU800/900
AISG 2.0 (two AISG modems)
4
473050A
FLGA
1800/2100
AISG 2.0 (two AISG modems)
2
472962A
FLGC
1800/2100
AISG 2.0 (two AISG modems)
4
473051A
FLSA
1800/2600
AISG 2.0 (two AISG modems)
2
473054A
FLSB
1800/2600
AISG 2.0 (two AISG modems)
4
473055A
FLTA
2100/2600
AISG 2.0 (two AISG modems)
2
473056A
FLTB
2100/2600
AISG 2.0 (two AISG modems)
4
473057A
Table 130
SRAN compatible legacy MHA units
Name
212
Control Protocol
Band
Control Protocol
Number of antenna ports
Sales code
MDDA
1800
AISG 2.0 or Current Window Alarm
2
CS7299220
FLMA
800
AISG 2.0
2
CS7299113
MDGA
900
AISG 2.0 or Current Window Alarm
2
CS7299111
MDTA
850
AISG 2.0 or Current Window Alarm
2
CS7299112
WMHA
2100
Current Window Alarm
2
CS72995
WMHB
2100
Current Window Alarm
2
CS7299515/CS7 2995
WMHC
2100
Current Window Alarm
2
470057A
WMHD
2100
AISG 2.0 or Current Window Alarm
2
471443A
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
4.4.3 SRAN supported RETs List of Remote Electrical Tilt (RET) units supported by SRAN system. Table 131
SRAN compatible RET units Name
Sales code
Manufacturer
Manufacturer code
Electronic Tilt Adjuster (RTAB)
469760A.102
CommScope (Andrew)
ATM200-A20
Electronic Tilt Adjuster (AccuRET)
472977A.101
CommScope (Andrew)
AccuRET-A20
Electronic Tilt Adjuster
469759A.209
Kathrein
86010148v01
Electronic Tilt Adjuster (iRET)
473084A.101
Kathrein
86010149
Electronic Tilt Adjuster (FlexRET)
473085A.101
Kathrein
86010153
Electronic Tilt Adjuster (RTAG)
472085A.105
Tongyu
TYRCUB20(F1V4)(A2)
Electronic Tilt Adjuster (RTAH)
472268A.101
CellMax
CMA-RET/RTU
Electronic Tilt Adjuster
473245A.101
RFS
ACU-A20-S
Table 132
SRAN compatible legacy RET units Name
Sales code
Manufacturer
Manufacturer code
Electronic Tilt Adjuster (RTAA)
469759A.207
Kathrein
86010118
Electronic Tilt Adjuster (RTAA)
469759A.208
Kathrein
86010148
Electronic Tilt Adjuster (RTAA)
469759A.209
Kathrein
86010148v01
Electronic Tilt Adjuster (RTAB)
469760A.102
CommScope (Andrew)
ATM200-A20
Electronic Tilt Adjuster (RTAG)
472085A.102
Tongyu
TY-RCUB20
Electronic Tilt Adjuster (RTAG)
472085A.103
Tongyu
TY-RCUB20
Electronic Tilt Adjuster (RTAG)
472085A.104
Tongyu
TY-RCUB20
Electronic Tilt Adjuster (RTAG)
472085A.105
Tongyu
TYRCUB20(F1V4)(A2)
For more information on RET, see Real Tilt Product Description in Antenna Systems Operating Documentation. To find Antenna Systems Operating Documentation, follow the path:
NOLS > Product Information Center (PIC) > Categories: Auxiliary Equipment > Subcategories: Antenna Systems > Products: Antenna Systems > Tab: Documentation > Antenna Systems, Operating Documentation, Issue 06
Issue: 01E
DN09218825
213
Descriptions of operability features
SRAN 16.2, Feature Descriptions
4.5 SR000918: SBTS Basic Performance Management 4.5.1 Description of SR000918: SBTS Basic Performance Management Introduction to the feature This feature provides basic performance management functionalities to SBTS: the administration, creation, collection, storage and transport, and presentation of SBTS performance management data. Real-time monitoring is not covered by this feature.
4.5.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature allows the operator to retain the same performance management process as they have had in a previous radio access technology (RAT) and reuse the existing tools and competence for SBTS performance management.
4.5.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.5.1.3
Functional description This feature provides Basic Performance Management functionalities to the Single RAN BTS. Real time measurements are not in the scope of this feature. Instead, the focus is on supporting administration, collection, storage, transfer, and presentation of performance measurement data. Performance measurements are used in network planning, troubleshooting, and for general monitoring of the mobile network. Performance measurement (PM) data is collected in performance counters. For administrative purpose, the performance counters are grouped into performance measurements. Key performance indicators (KPIs) are calculated in NetAct Reporter as a function of one or more performance counters. The values of the performance counters are generated by the corresponding Data Providers. These Data Providers are activated either during a certain event (for triggerbased performance counters) or after a certain amount of time (for sample-based performance counters). Each activation of a Data Provider results in an instantaneous value, which is then processed according to the performance counter definition. Data Providers produce these instantaneous counter values during the whole measurement period. At the end of the measurement period the Data Providers produce the final performance counter value, and report it for further storing and transferring to NetAct. Once the final counter value is reported, the performance counter value is reset. The new measurement period is started and the PM counter data is produced again.
214
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
For instance, if a performance counter shows the average number of users (a samplebased counter), then the instantaneous number of users is calculated after each defined sample interval. The respective Data Provider sums up all the sampled values and counts the number of samples in the overall sum. At the end of the measurement period the Data Provider divides the overall sum of users by the number of samples, thus producing the average number of users. This value is then reported for further processing and reset, so that the counting can start from zero at the beginning of the next measurement period. The performance counters are reported to NetAct together at the end of the upload period. Having shorter measurement periods and longer upload periods serves to minimize the number of file uploads to NetAct. Performance Management architecture in Single RAN can be depicted as follows: Figure 35
SRAN Performance Management Architecture
NBI
ReportingSuite
NetAct
RNC PM file
RNC
BSC PM file SBTS PM file
BSC
SBTS datavia Abis
WebUI
SBTS
The main difference compared to legacy radio access technology (RAT) architecture is the lack of an OMS mediator server between SBTS and NetAct. As a consequence, direct communication between SBTS and NetAct is established. Administration of Measurements
Issue: 01E
DN09218825
215
Descriptions of operability features
SRAN 16.2, Feature Descriptions
The lengths of individual SBTS measurements are configured by defining them in the SBTS configuration file. Allowed measurement period lengths are: 0min, 15min, 30min, 60min, 6hrs, 12hrs, and 24hrs. Setting the length to 0min means that the measurement is disabled, so the counters belonging to that measurement are not produced by corresponding Data Providers and their values are not reported for further processing. In addition, the upload period for all PM measurements in SBTS is configurable. There is one value for all measurements. The measurements are uploaded once their respective measurement periods have completed, so the upload period may be configured independently of the measurement periods. All SBTS measurements may be configured through NetAct. The SBTS Web UI supports the configuration of measurements for WCDMA, LTE, and SBTS common measurements. For GSM measurements, configuration is also possible by using the BSC MML. The measurement periods and upload period are synchronized to the beginning of the hour, so that it is possible to meaningfully combine PM measurement data from different SBTSs when generating reports in NetAct. For example, if the measurement period is 15 minutes, then it can start at the 0th, 15th, 30th, and 45th minute of each hour. If the upload period is 1 hour, then at the beginning of each hour PM measurement data will be uploaded to NetAct. PM Data Collection The SBTS produces PM measurement data continuously according to the SBTS measurement configuration settings. In order for the SBTS to produce PM measurement data, the SBTS clock must be in Network Time Protocol (NTP) sync mode, otherwise the time of the PM measurement data is not aligned between SBTSs and reports generated in NetAct are not meaningful. At the end of the performance measurement interval, the SBTS collects the final PM measurement data values, and forwards these for further processing. PM Data Storage in SBTS The SBTS keeps a short history of PM measurement data history (around 24 hours worth) locally. This history buffer is located in volatile memory, so after SBTS reset the PM history data is lost. If the PM history buffer overflows, the oldest PM measurement data is removed to allow storage of newer PM measurements. PM Data Transfer After receiving PM measurement data from the Data Providers and reaching the upload period, the SBTS creates one compressed OMeS file and forwards this file to NetAct using the NE3S interface. The SBTS OMeS file contains all LTE, WCDMA, and SBTS common measurements that are produced by that SBTS. The GSM measurements are delivered to the BSC as they are in non-SRAN GSM systems currently, with the exception of VSRW and RSSI related counters that become common measurements instead. PM Data Storage in NetAct The PM measurement data is stored in the NetAct PM database when it is received. The PM measurement data is available for operator processing in NetAct at most 15 minutes after expiration of the respective upload period in the SBTS. NetAct keeps the last 14 days of PM measurement data in the database, so that history reports from PM measurements can be generated. PM Data Presentation
216
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
The latest PM measurement data and a short history is visible in the SBTS Web UI. The Web UI has some basic reporting functionalities, so that addition or removal of individual PM counters does not create unnecessary maintenance efforts. PM counters may also be filtered by RAT. The Web UI also shows counter descriptions as found in RISE. Licensed PM measurements/counters All existing BTS measurements that are licensed in dedicated RATs are licensed as well in SRAN in SBTS. Any new SBTS licensed measurements/counters will have dedicated SBTS licenses. In GSM and WCDMA there exist counters with dedicated licenses located outside of the BTS. In the case of WCDMA, those counters are controlled by long term on/off RNC licenses. In GSM, a similar mechanism exists in BSC for RSSI and VSWR counters. As SRAN SBTS counters are sent directly to NetAct, the special handling of these licensed counters is located in NetAct. In case of these counters, NetAct inspects the license status in the RNC/BSC and stores or drops the data as appropriate. For compatibility reasons, the licensed counters/measurements are visible in SBTS Web UI regardless of the license status.
4.5.1.4
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.5.1.5
SR000918: SBTS Basic Performance Management management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters All measurements and counters are provided by this feature, there are no measurements or counters directly related to the operation of this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters
Issue: 01E
DN09218825
217
Descriptions of operability features
SRAN 16.2, Feature Descriptions
Table 133: New parameters lists parameters introduced with this feature. Table 133
New parameters
Full name
Abbreviated name
Managed object
LTE cell availability
mtCellAvailability
PM
LTE cell load
mtCellLoad
PM
LTE cell resource
mtCellRes
PM
LTE cell throughput
mtCellThruput
PM
WBTS cell throughput
mtCellThrWBTS
PM
LTE eNB load
mteNBload
PM
LTE EPS bearer
mtEPSBearer
PM
LTE EUTRA carrier frequency
mtEutraFrequency
PM
WBTS frame protocol
mtFrameProtWBTS
PM
WBTS FSM level monitoring
mtFSMLevelMon
PM
LTE GNSS
mtGNSS
PM
LTE handover RLF trigger
mtHoRlf
PM
WBTS HSPA scheduler monitoring
mtHSPASchedMon
PM
WBTS HSPA
mtHSPAWBTS
PM
WBTS extension HSPA
mtHSPAWBTSExt
PM
LTE inter-eNB handover
mtIntereNBHo
PM
LTE inter-system handover
mtInterSysHo
PM
LTE handover to eHRPD per eHRPD bandclass
mtInterSysHoEhrpdBc
PM
LTE neighbour cell related inter-system handover GSM
mtInterSysHoGsmNb
PM
LTE neighbor cell related inter-system handover UTRAN
mtInterSysHoUtranNb
PM
LTE intra-eNB handover
mtIntraeNBHo
PM
LTE neighbour cell related handover
mtintraLTEHoNb
PM
LTE handover
mtLTEHo
PM
LTE M3 SCTP statistics
mtM3SctpStatistics
PM
LTE MAC
mtMAC
PM
LTE MBMS
mtMBMS
PM
LTE mobility events
mtMobilityEvents
PM
LTE MRO UTRAN
mtMroUtran
PM
LTE MRO UTRAN frequency related
mtMroUtranFrequency
PM
LTE network sharing
mtNetwSharing
PM
WBTS Operator Specific Statistics
mtOperSpecStat
PM
218
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 133
Descriptions of operability features
New parameters (Cont.)
Full name
Abbreviated name
Managed object
WBTS PIC pool
mtPICPoolWBTS
PM
LTE power and quality DL
mtPowQualDL
PM
LTE power and quality UL
mtPowQualUL
PM
LTE QoS
mtQoS
PM
LTE radio bearer
mtRadBearer
PM
LTE RAN sharing
mtRanSharing
PM
LTE RRC
mtRRC
PM
LTE S1AP
mtS1AP
PM
LTE S1 SCTP statistics
mtS1SctpStatistics
PM
SBTS antenna line management
mtSBTSAntennaLine
PM
SBTS SI monitoring
mtSBTSSIMon
PM
WBTS signaling load
mtSignLoadWBTS
PM
LTE SINR
mtSINR
PM
LTE transport load
mtTranspLoad
PM
LTE UE and service differentiation
mtUEandServiceDiff
PM
LTE UE state
mtUEstate
PM
WBTS level monitoring
mtWBTSLevelMon
PM
WBTS R99 HW resource
mtWBTSR99Res
PM
LTE X2AP
mtX2AP
PM
LTE X2 SCTP statistics
mtX2SctpStatistics
PM
SBTS performance measurement data reporting reportingIntervalPm interval
4.5.1.6
PMCADM
Sales information Table 134
Sales information
BSW/ASW
License control in network element
BSW
-
4.6 SR001005: SBTS Channel bandwidth RTU 4.6.1 Description of SR001005: SBTS Channel bandwidth RTU Introduction to the feature
Issue: 01E
DN09218825
219
Descriptions of operability features
SRAN 16.2, Feature Descriptions
This feature introduces license control for channel bandwidth configuration. The granularity on license control is 1 MHz channel bandwidth. License control is performed by applying SRAN's license framework as described in SR000794: SBTS SW License Management.
4.6.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits One common sales item simplifies license management for invoicing channel bandwidth.
4.6.1.2
Requirements Hardware requirements This feature does not require any new or additional hardware.
4.6.1.3
Functional description This feature introduces license control for channel bandwidth configuration. The granularity on license control is 1 MHz channel bandwidth. License control is performed by applying SRAN's license framework as described in SR000794: SBTS SW License Management. Channel bandwidth is configured per SRAN BTS and has granularity of 1MHz. The SBTS channel bandwidth is calculated by summing up the bandwidth configured for all WCDMA and LTE cells, and GSM TRXs. In the case that a non-integer number of licenses would be required, it is rounded down to the closest integer. This rounding applies to the SBTS total bandwidth, and not to the individual cells. To enable license control in SBTS, a new read only parameter is introduced, which provides the total amount of 1MHz licenses needed. This parameter is visible in NetAct and the Software Entitlement Manager (SWEM) will check the activation parameter and compare with licenses available via CLS. If license capacity is missing then a general limitation action will be applied. Examples LTE111@1,4MHz configuration requires 3 cells x 1,4MHz = 4,2MHz channel bandwidth. 4,2 licenses are required which is rounded down to 4 x 1MHz licenses. WCDMA333 configuration requires 9 x 5MHz = 45MHz bandwidth, so 45 licenses are required. GSM 222 configuration requires 6 x 0,2MHz = 1,2MHz bandwidth. Only 1 license is required.
4.6.1.4
System impact Interdependencies between features This feature requires the following feature:
220
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
•
Descriptions of operability features
SR000794: SBTS SW License Management
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.6.1.5
SR001005: SBTS Channel bandwidth RTU management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 135: New parameters lists parameters introduced with this feature. Table 135
New parameters
Full name
Abbreviated name
Number of channel bandwidth steps
4.6.1.6
CAPCFG
Sales information Table 136
Issue: 01E
numberOfChannelBandwidth Steps
Managed object
Sales information
BSW/ASW
License control in network element
ASW
Pool license
DN09218825
221
Descriptions of operability features
SRAN 16.2, Feature Descriptions
4.7 SR001185: SBTS Composer UI 4.7.1 Description of SR001185: SBTS Composer UI Introduction to the feature SBTS Composer UI is a high level wizard for performing SBTS commissioning.
g 4.7.1.1
Note: This feature will be available in future releases.
Benefits This feature introduces the following benefits to the operator: • •
4.7.1.2
Guided manual commissioning wizard for site setup without a ready-made site configuration file (SCF). SBTS site parameter planning by creating a template file or a full SCF.
Requirements Hardware requirements This feature does not require any new or additional hardware.
4.7.1.3
Functional description The SR001185: SBTS Composer UI feature introduces a guided manual commissioning mechanism, which allows for site configuration file (SCF) creation and modification. The SBTS Composer UI is available directly from SBTS Element Manager. No additional software is required. The SBTS Composer UI complies with all the web browsers that support the SBTS Element Manager, as listed below: • • •
Chrome, latest available version, 32 bit version is suggested, for both the Windows and Linux operating systems. Internet Explorer 11, latest available version, with latest updates installed, for the Windows operating system. Firefox, latest available 32 bit version, for both the Windows and Linux operating systems.
For more information on the SBTS Element Manager, see SR000713: SBTS Web UI feature description. Starting options The SBTS Composer UI can be accessed from several different locations in the SBTS Element Manager: •
By selecting the Parameters tab in the main view. Figure 36
222
Parameters tab
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
•
In the Site Management ► Software and configuration update tab when an error is found in the validation phase of the configuration update. Figure 37
•
Error during validation phase
In the Site Management ► Active Faults tag by clicking the Edit icon on toggling faults. In the Active Faults tag an Edit icon is shown for the faults which can be defined as toggling faults. Clicking this icon opens the Parameter editor. The specific fault is filtered and the user can set toggling fault related parameters. Figure 38
Issue: 01E
Descriptions of operability features
Toggling faults
DN09218825
223
Descriptions of operability features
•
g
In the Site Management ► HW View ► Additional information for RET balloon message by using Edit RET parameters link. The link in the balloon message opens the Parameter editor where selected RET related parameters are filtered by default. Note: The same behavior is applied for MHA additional information balloon message. Figure 39
•
g
SRAN 16.2, Feature Descriptions
RET parameters
In the Automatic disconnection information dialog. The SBTS Element Manager session has a timeout, which indicates for how long a session can remain idle. This timeout is a configurable parameter (sbtsEMSessionTimeout). When the notification of an automatic disconnection is given, the link for editing that parameter is provided. Note: The SBTS Composer UI can be accessed even if the SBTS is not operational (uncommissioned).
User interface
224
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
The main view of the SBTS Composer UI comprises three tables: Commissioning Settings, Configuration Group, and Parameters. Figure 40
SBTS Composer UI main view
The SBTS Composer UI provides following functionalities in the user interface: Displaying current active profile name and information
The user can display current active profile information while hovering over the i-icon in the Commissioning Settings table.
Error notifications
The interface displays graphical notifications (yellow triangles) in the Configuration Group table in case of detected errors.
Filters and multifilters
The user can filter data in the Parameters table by column or by combination of different column filters (multi-filter).
The use of SBTS Composer UI The SBTS Composer UI supports the following procedures:
Issue: 01E
DN09218825
225
Descriptions of operability features
• • •
SRAN 16.2, Feature Descriptions
Reconfiguring Commissioning File creation
Within the above scenarios, the SBTS Composer UI introduces the following functionalities: •
g
Note: The parameter groups can also be imported from other valid SBTS SCFs. Up to five SCFs can be imported with one parameter group for each file. The SBTS Composer UI verifies the SCFs and their parameter groups, given the SCFs are in .xml format. This way, the parameter groups selected from SCFs are already pre-validated before clicking Show Parameters button. Each parameter group can be picked only once. • • • • • •
g
Displaying and editing managed objects and paramaters within an SCF.
Providing profile files by uploading from local PC, network drive or reading them from SBTS. When no SCF is selected, creating default parameters with default values based on BIM. Merging SCFs. Validating SCFs. Sending SCFs to the BTS. Saving created full or partial SCFs to a PC or network drive. Note: Saving is possible only in Create file procedure.
The Reconfigure procedure is performed by changing any of the current parameters without changing the profile file (for example during rollout to add a new radio access technology to an existing site). The Commissionig procedure can be performed without technology specific files or with partial SCF template. During commissioning a profile file can be changed. The Create file procedure can be performed with no SCF available or with partial SCF available. All parameters can be entered manually. The user can perform a full SCF creation or a partial SCF creation for specific RAT or TRS. To complete the above procedures the following generic user scenario applies: 1. Selecting the commissioning type: Reconfigure, Commissioning, Create file. 2. Selecting a BTS profile (optional). 3. Selecting technologies for the particular site (optional). SCFs can be selected as input.
g
Note: In case of selecting WCMDA/LTE/GSM as a Target RAT in the Composer UI, the respective BTSSCW/BTSSCL/BTSSCC managed objects must be defined in the commissioning file. Otherwise, the Composer UI creates a needed MO automatically. In this case, the user does not need to create these objects again. 4. By clicking Show parameters the parameters are shown in the parameter (PE) table according to the technology selections. At this stage the parameters are validated lightly to provide information on the missing parameters - the mandatory parameters, missing information and errors are displayed.
226
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
5. Starting validation of the parameters. Validation errors are listed in the error table. The user can return to the previous step to correct the errors. 6. Activating the configuration (in case of commissioning and reconfiguring procedures). 7. Saving the SCF locally (in case of file creation procedure).
4.7.1.4
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.7.1.5
SR001185: SBTS Composer UI management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Commands There are no commands related to this feature.
4.7.1.6
Sales information Table 137
Sales information
BSW/ASW BSW
Issue: 01E
License control in network element -
DN09218825
227
Descriptions of operability features
SRAN 16.2, Feature Descriptions
4.8 SR001118: SBTS Configuration File Conversion from WCDMA or LTE 4.8.1 Description of SR001118: SBTS Configuration File Conversion from WCDMA or LTE Benefits, functionality, system impact, reference data, instructions of the feature. The SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature provides a tool for site configuration file (SCF) conversion from LTE/WCDMA SCF to Single RAN BTS SCF.
4.8.1.1
SR001118 benefits The SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature simplifies the conversion from WCDMA/LTE BTS to SBTS.
4.8.1.2
SR001118 functional description The SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature introduces the possibility to convert an existing eNodeB/WBTS site configuration file (SCF) to SBTS SCF. The user performs this operation manually using SCF conversion script. The following conversion paths are supported: • • • •
conversion of RL70 SCF to SRAN16.2 SCF (for an SBTS working in LTE dedicated mode) conversion of RU50 EP1 SCF to SRAN16.2 SCF (for an SBTS working in WCDMA dedicated mode) conversion of LTE 15A SCF to SRAN16.2 SCF (for an SBTS working in LTE dedicated mode) conversion of WCDMA 16 SCF to SRAN16.2 SCF (for an SBTS working in WCDMA dedicated mode)
For instructions on how to use the script, see Release Documentation > How to use SCF conversion script. The feature also provides the capability to reuse the transport configuration from an existing WBTS/eNodeB SCF and establish M-plane connection to NetAct after a remote SBTS software download. The SCF conversion and the transport configuration reuse are parts of the migration procedure from WBTS/eNodeB to SBTS, which is to be supported in further SRAN releases.
4.8.1.3
SR001118 system impact SR001118: SBTS Configuration File Conversion from WCDMA or LTE impact on features, and system performance. Interdependencies between features
228
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
The SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature impacts the following feature: •
SR000942: SBTS Manual Commissioning and System Setup The SR000942: SBTS Manual Commissioning and System Setup feature provides local commissioning function that can be used instead of manual migration procedures.
Impact on interfaces The SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature has no impact on interfaces. Impact on network management tools The SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature has no impact on network management tools. Impact on system performance and capacity The SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature has no impact on system performance or capacity.
4.8.1.4
SR001118 reference data SR001118: SBTS Configuration File Conversion from WCDMA or LTE requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements The SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature requires Flexi Multiradio 10 System Module (FSMF). Alarms There are no alarms related to the SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature. BTS faults and reported alarms There are no faults related to the SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature. Commands There are no commands related to the SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature. Measurements and counters There are no measurements or counters related to the SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature. Key performance indicators There are no key performance indicators related to the SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature. Parameters
Issue: 01E
DN09218825
229
Descriptions of operability features
SRAN 16.2, Feature Descriptions
There are no parameters related to the SR001118: SBTS Configuration File Conversion from WCDMA or LTE feature. Sales information Table 138
SR001118 sales information
Product structure class
License control
Basic Software (BSW)
-
Activated by default Yes
4.9 SR000929: SBTS Configuration Management 4.9.1 Description of SR000929: SBTS Configuration Management Introduction to the feature In SRAN 16.2, the SBTS is represented as a single entity, not as separate, per-RAT entities as is currently. This feature provides the SBTS configuration management operations, including support for configuration plan preparation, validation, and provisioning, configuration upload, and configuration synchronization by means of a robust notification mechanism and upload operations. Configuration validation is supported as well.
4.9.1.1
Benefits End-user benefits This feature does not affect end-user benefits. Operator benefits This feature benefit operator as follows: • •
4.9.1.2
operator ensures configuration management at SBTS level is consistent, operator can manage SBTS as a single entity within the configuration management operations.
Requirements Hardware requirements This feature does not require any new or additional hardware.
4.9.1.3
Functional description Prior to SRAN 16.2, each radio access technology (RAT) comprising a single radio access network BTS (SBTS), executes as an individual, single- RAT BTS. Dedicated system module (SM) establishes its own, individual management plane (M-plane) interface over its own RAT-specific operations, administration, and maintenance (OAM) functions. This approach forced the operator to separately configure each RAT, according to RAT-specific object model. The operator also needed to manually ensure the configuration consistency of the SBTS unit as a whole.
230
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
SRAN 16.2 introduces a new SBTS architecture, in which all of the RAT-specific applications are operated from a single system module (with extension modules, if required, based on the configuration). This architecture manages the SBTS using common OAM software that provides a single, NE3S-based M-plane interface over which OAM functions are regulated. In SRAN 16.2, the configuration of the SBTS is organized around a common object model that integrates a common BTS hardware object model, a common BTS transport object model, and RAT-specific object models into a single SBTS object model. This feature implements the configuration management (CM) functions for an SBTS utilizing the new architecture, as it includes the following configuration management operations of SBTS: • • • •
configuration generation, configuration provisioning, configuration activation, configuration upload and change notification mechanism.
Configuration generation provides the SBTS with hardware configuration details based on predefined templates for the supported BTS configurations. This approach ensures robust configuration without exposing the internal details of the BTS to the end user. Configuration provisioning supports the following: • • • • • • • • • • • •
configuration management plan based on provisioning, separation of download and activation, managing exceptions or errors in configuration, direct activation, delta configuration support, automatic lock, online parameter changes, transport configuration fallback (as well as BTS fallback as a whole), emergency plan management, avoiding resets due to changes in configuration, providing options for either best-effort or best consistency provisioning, reviewing/checking the plan by the operator, and changes before download and activation in BTS.
Configuration synchronization supports the following: • •
4.9.1.4
configuration upload, robust change notification mechanism.
System impact Interdependencies between features • •
Issue: 01E
SR000726: SRAN BTS Object Model introduces the common SRAN BTS object model required as the basis for the CM-related operations. SR000921: SBTS NE3S WS NetAct integration introduces the functionalities related to SBTS integration with NetAct.
DN09218825
231
Descriptions of operability features
• • •
SRAN 16.2, Feature Descriptions
SR000928: SBTS Plug and Play introduces automated commissioning function, commissioning is required before configuration management is performed. SR000930: SBTS Configuration Validation provides implementation of the SBTS validation function. SR000942: SBTS Manual Comissioning and system setup introduces manual commissioning function, commissioning is required before configuration management is performed.
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.9.1.5
SR000929: SBTS Configuration Management management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters The following table lists parameters related to this feature. Table 139
Related parameters Full name
232
Abbreviated name
Managed object
Cancel delay for the external alarm
cancelDelay
EACA
Description
descr
EACA
External alarm connector
eacConnector
EACA
External alarm connector object identifier
eacaId
EACA
Module id
hwModuleRef
EACA
In use
inUse
EACA
Polarity
polarity
EACA
Alarm severity
severity
EACA
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 139
Descriptions of operability features
Related parameters (Cont.) Full name
Abbreviated name
Managed object
Start delay for the alarm
startDelay
EACA
Description
descr
EACC
External control connector
eacConnector
EACC
External control connector object identifier
eaccId
EACC
Module id
hwModuleRef
EACC
In use
inUse
EACC
Initial state
initState
EACC
Commands There are no commands related to this feature.
4.9.1.6
Sales information Table 140
Sales information
BSW/ASW BSW
License control in network element -
4.10 SR000930: SBTS Configuration Validation 4.10.1 Description of SR000930: SBTS Configuration Validation Introduction to the feature This feature introduces SBTS validation of both, hardware and logical radio configuration. Validation can be performed offline before the actual SBTS commissioning, and on-line with the real SBTS where the rules are also checked against the actual hardware. Configuration validation is supported from both NetAct and Web UI.
4.10.1.1
Benefits End-user benefits This feature does not affect end user experience. Operator benefits Configuration validation from both NetAct and Web UI level.
4.10.1.2
Requirements Hardware requirements This feature does not require any new or additional hardware.
Issue: 01E
DN09218825
233
Descriptions of operability features
4.10.1.3
SRAN 16.2, Feature Descriptions
Functional description SRAN16.2 introduces a new single RAN BTS (SBTS) architecture, in which all of the RAT-specific BTS applications execute on a single system module (with extension modules, if required, based on the configuration). This architecture manages the SBTS using common (rather than RAT-specific) OAM software that provides a single, NE3Sbased M-plane interface over which OAM functions are invoked. This feature introduces configuration management (CM) validation for the SBTS utilizing new architecture. Validation ensures that the configuration of the SBTS conforms to a set of validation rules. This feature provides the implementation of these validation rules for the SBTS. Before the SBTS's configuration is modified, the associated changes are first validated against the SBTS's validation rules. If the configuration change properly conforms to the validation rules, the change is allowed to be activated within the SBTS. If the configuration change does not conform to the rules it is rejected and a report describing the validation rules that were violated along with the managed objects and/or parameter values that violated the rules is generated and provided to the operator. With new architecture, the SBTS's OAM functionality is divided into two major architectural components. The Site OAM component provides site wide OAM functions, including configuration validation. This component also terminates the SBTS's NE3S interface towards NetAct. The Node OAM component implements node-specific OAM functions including node initialization, maintenance of the node-specific database, and RAT-specific application surveillance. Following feature illustrates new architecture. Figure 41
SBTS Validation Architecture
NetAct SCF
Offlinevalidation Scallableparallelprocessing
SBTS SBTS SBTS
WebUI
Onlinevalidation,distributed
234
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
The location of the Site OAM function within the network changes as part of the SBTS commissioning workflow. During pre-commissioning, the Site OAM function is located outside of the SBTS, as a service within NetAct, this allows the SBTS to be preconfigured and the configuration is validated prior to the availability of the actual SBTS. After commissioning, the site OAM function migrates to the SBTS itself, this promotes the scalability of site-specific OAM functions that are applicable to multiple SBTSs. The site OAM function can also be deployed outside of the RAN architecture, on a PC, such deployment provides means to execute (in particular for test purposes) the validation function outside of target platforms. In SRAN16.2, the configuration of the SBTS is organized around a common object model that unifies a common BTS hardware object model, a common BTS transport object model and RAT-specific object models into a single SBTS object model. In addition to the managed objects and parameters that define the SBTS object model, the object model contains the SBTS validation rules. The Site OAM component implements the SBTS validation function for a particular release of the SBTS object model based on the validation rules defined within the model. Changes to the validation implementation (due to, for example, new or updated validation rules) require a software update of the Site OAM component. In general, the SBTS validation rules can be broadly categorized by their complexity as simple and logical validation rules. Simple validation rules Simple validation rules consist of rules on managed object parameters that define types, ranges, and, for string-based parameters, validation patterns that define format of stringbased values. These validation rules are primarily, according to syntax, checks that are used to ensure that the SBTS's configuration, and any modifications to it, conforms to the SBTS object model. They are specified by object modelers as metadata within PDDB. In SRAN16.2 there are several thousand simple validation rules defined as part of the SBTS object model. Logical validation rules Logical validation rules consist of rules between multiple managed object classes and/or parameters. These rules are logic checks that collectively ensure that the SBTS object model, as a whole, is valid. Such rules may be defined for managed objects associated with one or more RATs. In the current, non-SBTS products, there are approximately: • • •
400 LTE specific validation rules 500 transport specific validation rules 250 common rules, applicable to the BTS platform irrespective of the RAT deployed.
Validation execution All configuration changes, regardless of whether they originate from NetAct (via invocation of the NE3S validate operation) or from the Web UI, must be validated against the SBTS's validation rules. The validation of any configuration change is a multi-step process consisting of the following tasks: 1. The configuration change is validated against the simple validation rules defined within the PDDB/NIDD metadata. Including checks for unknown managed object classes and parameters.
Issue: 01E
DN09218825
235
Descriptions of operability features
SRAN 16.2, Feature Descriptions
2. The configuration change is validated against the related conditions, if such validation rules exist. To perform these validations, any configuration differences are combined with the actual configuration of the BTS to create a proposed SBTS configuration. The proposed configuration is then validated against the logical validation rules to ensure that configuration deltas, when applied to the SBTS configuration, will result in a valid SBTS configuration. 3. The configuration change is validated against hard-coded rules. However, for cases where the complexity of the rule requires hard-coding, the configuration change is validated against the applicable hard-coded rules. 4. The configuration change is validated against the BTS profile assigned to the SBTS. Additionally, validation of the configuration change against the present, physical SBTS hardware is performed if the SBTS has been commissioned. There are two main aspects to this validation: ensuring that the hardware installed within the SBTS matches the expected hardware types and cabling requirements associated with the BTS Profile active within the SBTS and ensuring that the configuration is appropriate for the hardware actually installed within the SBTS. Validation against physically installed hardware is only possible if the SBTS Site OAM component (providing the validation implementation) is deployed within the physical BTS. When the Site OAM component is deployed as a service within NetAct, prior to the commissioning of the physical SBTS, no physical hardware is yet available and, therefore, such hardware validation cannot be performed.
4.10.1.4
System impact Interdependencies between features • •
SR000726: SRAN BTS Object Model introduces the common SRAN BTS object model required as the basis for the configuration management validation operations. SR000929: SBTS Configuration Management provides the infrastructure necessary for the invocation of the SBTS validation functionality.
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity when the number of users does not exceed the licensed maximum.
4.10.1.5
SR000930: SBTS Configuration Validation management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature.
236
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Commands There are no commands related to this feature.
4.10.1.6
Sales information Table 141
Sales information
BSW/ASW BSW
License control in network element -
4.11 SR000908: SBTS Crypto Agent 4.11.1 Description of SR000908: SBTS Crypto Agent Introduction to the feature This feature introduces the software-based crypto agent mechanism. The crypto agent mechanism supports the secure file storage, secure key storage, and cryptographic procedures.
4.11.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides enhanced data security management. The data is protected with the secure environment and cryptographic procedures.
4.11.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.11.1.3
Functional description This feature introduces the software-based crypto agent mechanism. The crypto agent mechanism supports the secure file storage, secure key storage, and cryptographic procedures. The SBTS modules with crypto agent mechanisms operated with Linux, provide a secure environment that guarantee the secure storage of the keys. The crypto agent mechanism provides operations through a common API. The mechanism ensures that unencrypted keys are never leaked from the secure environment. The private keys
Issue: 01E
DN09218825
237
Descriptions of operability features
SRAN 16.2, Feature Descriptions
operations are performed within the crypto agent mechanism. Along with the improvement in key storage security, the crypto agent mechanism provides also an API for the secure file storage to decode and encode files with crypto agent mechanism. Even when software changes to the operating system are performed, the data remain uncorrupted. Figure 42
Crypto agent mechanism and secure file storage
SBTSModules Applications UNIXsocket
Crypto Agent
FileSystem CRA Server
KeyStorage
CRA Services Encrypted file
Encrypted file
Encrypted file
The mechanism maintains the key hierarchy in which chosen keys are encrypted with parent key and only encrypted keys are exported and stored onto the file system. The encrypted data can only be decrypted with the storage root key (SRK) generated automatically at the first startup of the crypto agent mechanism. The storage root key is connected to the board where the storage root key generation is performed through the passphrase generation mechanism. The storage root key is decrypted through the generated passphrase. Passphrases are randomly generated and are known only to the mechanism of the crypto agent. The RSA keys are stored within the crypto agent mechanism. PSK and RefNum are stored within the encrypted file system.
4.11.1.4
System impact Interdependencies between features This feature is a prerequisite for the following features: • •
238
SR000845: Operator certificate management SR000846: Vendor certificate management
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.11.1.5
SR000908: SBTS Crypto Agent management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
4.11.1.6
Sales information Table 142
Sales information
BSW/ASW
License control in network element
BSW
-
4.12 SR001004: SBTS Data User RTU 4.12.1 Description of SR001004: SBTS Data User RTU Introduction to the feature This feature introduces common license item for number of data users. Data users include data users from LTE and HSxPA. In current release that sales item is trust based, but protected by physical LKs in upcoming SRAN release by applying SRAN license framework.
Issue: 01E
DN09218825
239
Descriptions of operability features
4.12.1.1
SRAN 16.2, Feature Descriptions
Benefits End-user benefits This feature does not affect end user experience. Operator benefits One common sales item simplifies license management for invoicing number of data users.
4.12.1.2
Requirements Hardware requirements This feature does not require any new or additional hardware.
4.12.1.3
Functional description This feature measures SRAN data users by using new not modifiable counters reported in new 40000 - SBTS SI Monitoring (SBTS) measurement: • • •
M40000C0: MAXIMUM NUMBER OF ACTIVE LTE UEs M40000C1: MAXIMUM NUMBER OF HSUPA USERS M40000C2: MAXIMUM NUMBR OF HSDPA USERS
These measurements are working in the same way as the existing measurements: M8018C1, M5008C18, M5008C21, but are not modifiable by users. In current SRAN 16.2 implementation the Sales Item "SBTS Data User RTU" is trust based, as NetAct support is provided in the next release. With NetAct support, the behavior will be as described below. Depending on the sales item to be selected, OSS SWEM (Software Entitlement Manager) periodically either checks the counter values, averaged over 14 days, or alternatively checks the daily max values. Applying SRAN's licensing framework as described in SR000794:SBTS SW License Management, OSS SWEM periodically verifies, if enough license capacity is existing. If not, capacity is limited by reducing the number of data users to a value supported by licenses. SWEM initiates a configuration management command for related SBTS to achieve that (this limitation is planned for future SRAN 16 releases). In SBTS the meaning of following counters is changed. Counters listed below, do not show the actual number of HSPA users, but the number of HSPA users limited because of lack of licenses: • •
4.12.1.4
M5008C40 CONFIGURED HSDPA USERS CONF_HSDPA_USERS M5008C41 CONFIGURED HSUPA USERS CONF_HSUPA_USERS
System impact Interdependencies between features The following features are prerequisite for this feature: • •
240
SR000794: SBTS SW License Management OSS_FC_014460_ NE_Radio_SRAN: SRAN 16A Management Functionality
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.12.1.5
SR001004: SBTS Data User RTU management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters Table 143: Related existing counters lists existing counters related to this feature. Table 143
Related existing counters
Counter ID
Counter name
Measurement
M8018C1
Active UE per eNB
8018 - LTE eNB Load (WBTS)
M5008C21
MAXIMUM NUMBER OF HSDPA USERS
5008 - WBTS level monitoring (WBTS)
M5008C18
MAXIMUM NUMBER OF HSUPA USERS
5008 - WBTS level monitoring (WBTS)
M5008C40
CONFIGURED HSDPA USERS
CONF_HSDPA_USERS
M5008C41
CONFIGURED HSUPA USERS
CONF_HSUPA_USERS
Table 144: Related new counters lists new counters related to this feature. Table 144
Related new counters
Counter ID
Issue: 01E
Counter name
Measurement
M40000C0
MAXIMUM NUMBER OF ACTIVE LTE UEs
40000 - SBTS SI Monitoring (SBTS)
M40000C1
MAXIMUM NUMBR OF HSDPA USERS
40000 - SBTS SI Monitoring (SBTS)
DN09218825
241
Descriptions of operability features
Table 144
SRAN 16.2, Feature Descriptions
Related new counters (Cont.)
Counter ID
Counter name
M40000C2
MAXIMUM NUMBR OF HSUPA USERS
Measurement 40000 - SBTS SI Monitoring (SBTS)
Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Commands There are no commands related to this feature.
4.12.1.6
Sales information Table 145
Sales information
BSW/ASW BSW
License control in network element BTS LK
4.13 SR000940: SBTS Diagnostics and Self Test 4.13.1 Description of SR000940: SBTS Diagnostics and Self Test Introduction to the feature This feature introduces SBTS self-test and diagnostics. The diagnostic tests are executed from the Web UI.
4.13.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the same diagnostics and self-test functions that are already used in LTE/WCDMA and so are easier to adopt by the operator. Key diagnostics functions and self-testing make it possible to identify hardware failures in commissioning and troubleshooting, leading to reduced downtimes.
4.13.1.2
Requirements Hardware requirements
242
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
This feature requires Flexi Multiradio 10 System Module (FSMF).
4.13.1.3
Functional description This feature provides diagnostics and self-tests for SBTS troubleshooting. The SBTS troubleshooting data collection can be triggered in the SBTS Web UI. The data is saved either in an attached PC running Web UI or in the NetAct file system. The key diagnostics and tests are: • • • • • • •
4.13.1.4
SBTS self-test and diagnostics POST (Power On Self Test) IP ping-test Black Box (not user initiated) EAC (External alarms) test Test Clock Output diagnostic test Input Voltage Monitoring diagnostic test
System impact Interdependencies between features This feature depends on the following features: • • • • •
SR000713: SRAN Web UI SR000929: SBTS Configuration Management SR000726: SBTS Object Model SR000920: Fault Management for SBTS SR000385: Synchronization Hub
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.13.1.5
SR000940: SBTS Diagnostics and Self Test management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters
Issue: 01E
DN09218825
243
Descriptions of operability features
SRAN 16.2, Feature Descriptions
Table 146: New counters lists counters introduced with this feature. Table 146
New counters
Counter ID
Counter name
Measurement
M40003C0
MINIMUM INPUT VOLTAGE IN RADIO MODULES
40003: SBTS RFM Energy Monitoring
M40003C1
MAXIMUM INPUT VOLTAGE IN RADIO MODULES
40003: SBTS RFM Energy Monitoring
Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
4.13.1.6
Sales information Table 147
Sales information
BSW/ASW
License control in network element
BSW
-
4.14 SR000904: SBTS DNS Support 4.14.1 Description of SR000904: SBTS DNS Support Introduction to the feature This feature introduces support for DNS resolution for addresses given by a Full Qualified Domain Name (FQDN) into the corresponding IP address. Once, the SBTS is configured with one or more DNS servers, the DNS server will provide the FQDN-to-IP address.
4.14.1.1
Benefits End-user benefits This feature does not affect end user experience. Operator benefits The possibility to configure the SBTS to use DNS, provides the operator with Full Qualified Domain Name for specified/selected destinations instead of fixed IP-address. This leads to OPEX savings when the IP configuration of networks peers need to be changed, for example, for the URL within operator certificates to address revocation list server.
244
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.14.1.2
Descriptions of operability features
Requirements Hardware requirements This feature does not require any new or additional hardware.
4.14.1.3
Functional description SBTS applications that require FQDN-to-IP address look-up can use the DNS service. The DNS client, included in the SBTS and configured through the SBTS object model, queries the primary or secondary DNS Server to resolve the FQDN, which returns the corresponding IP address assigned to the repository. Supported functions: • • •
DNS Protocol according to RFC 1034 and RFC 1035, name lookup to resolve FQDN to allocated IP address, support of DNS protocol via UDP or TCP,
Reverse lookup, that is providing the FQDN which belongs to a given IP address, is not supported. Figure 43
SRAN 16.2 DNS lookup process. NameServer
DNS
2.FQDN
3.IP address
1.FQDN
4.IP packet
SBTS
4.14.1.4
Network Peer
System impact Interdependencies between features This feature is a prerequisite for the SR000845: SBTS Operator Certificate Management feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
Issue: 01E
DN09218825
245
Descriptions of operability features
4.14.1.5
SRAN 16.2, Feature Descriptions
SR000904: SBTS DNS Support management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults There are no alarms and faults related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 148: New parameters lists parameters introduced with this feature. Table 148
New parameters
Full name
4.14.1.6
Abbreviated name
Managed object
DNS object identifier
dnsId
DNS
IP address of the primary DNS server
serverIpAddressPrimary
DNS
IP address of the secondary DNS server
serverIpAddressSecondary
DNS
Sales information Table 149
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
4.15 SR000959: SBTS Energy saving 4.15.1 Description of SR000959: SBTS Energy saving Introduction to the feature This feature provides the support for existing energy saving features in SBTS. The energy saving mode in SBTS will be supported in Single-RAT and Multi-RAT mode.
4.15.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
246
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
Operator benefits The operator can use energy saving features with SBTS in dedicated radio and RFSharing mode.
4.15.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.15.1.3
Functional description This feature provides SBTS Energy saving functionality. The current radio technology solutions all support releasing the power amplifier (PA) resources based on low traffic, time of day or by an operator defined profile. The relevant features in 2G, 3G and 4G are RG301936: Intelligent MCPA TRX Shutdown, RAN955: Power Saving Mode for BTS, and LTE1103: Load Based Power Saving for Multi-layer Networks respectively. This feature combines those features so they can be used in dedicated radio mode (one radio per RAT) or in RF-Sharing mode. Figure 44
Radio connections in dedicated and RF-Sharing modes
GSM O WCDMA
A M
LTE
SBTS-DedicatedRadioModules
GSM O WCDMA
A M
LTE
SBTS-RFSharedRadioModules
In the case that all the radio resources are released from the shared PA by the RATs, the PA enters stand-by mode automatically. When any of the RATs requires radio resources the PA is powered on.
Issue: 01E
DN09218825
247
Descriptions of operability features
4.15.1.4
SRAN 16.2, Feature Descriptions
System impact Interdependencies between features This feature requires the RAT-specific features for each technology: • • •
RG301936: Intelligent MCPA TRX Shutdown RAN955: Power Saving Mode for BTS LTE1103: Load Based Power Saving for Multi-layer Networks
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.15.1.5
SR000959: SBTS Energy saving management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
4.15.1.6
Sales information Table 150
248
Sales information
BSW/ASW
License control in network element
ASW
Existing RAT-specific feature licenses and sales items are used: •
RG301936
•
RAN955
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 150
Descriptions of operability features
Sales information (Cont.)
BSW/ASW
License control in network element •
LTE1103
4.16 SR000920: SBTS Fault Management 4.16.1 Description of SR000920: SBTS Fault Management Introduction to the feature This feature introduces integrated fault management for SBTS.
4.16.1.1
Benefits End-user benefits This feature does not affect end-user experience. Operator benefits Integrated troubleshooting over several network technologies results in reduced OPEX costs.
4.16.1.2
Requirements Hardware requirements This feature does not require any new or additional hardware.
4.16.1.3
Functional description From network alarm management point of view, the SBTS is handled as one entity. However alarms for LTE, WCDMA and GSM cells and Base Stations are reported for legacy BTS and Cell objects. Alarms include information on which technology and which cell/cells are affected with impact level (critical, major, minor and so on). All alarms are routed through one NE3S interface to NetAct, therefore WCDMA related SBTS alarms are not visible from RNC/OMS, and not all GSM alarms are visible on the BSC. However, certain GSM alarms required for state management of the BCF are routed to the BSC. All SBTS alarms and faults are visible locally or remotely from SBTS Web UI or NetAct Monitor application. SRAN fault management consists of the following functions: • • • • •
Issue: 01E
SBTS reports common and transport alarms to NetAct through NE3S Web Service (NES3 WS). SBTS reports LTE specific RNW alarms to NetAct through NE3S WS. SBTS reports WCDMA specific RNW alarms to NetAct through NE3S WS. SBTS reports GMS specific RNW alarms to NetAct through NE3S WS. SBTS reports alarms to Web UI through REST API (including common and transport alarms and LTE, WCDMA, GSM specific RNW alarms).
DN09218825
249
Descriptions of operability features
• • • • • • • • • • • • •
4.16.1.4
SRAN 16.2, Feature Descriptions
SBTS fills alarms fields that was traditionally (prior to Single RAN) filled by the mediator, leaving NetAct User experience largely unchanged. SBTS handles toggling alarms. SBTS maintains fault history. SBTS stores fault history in System Module Black box. NetAct displays alarms reported by SBTS with the NetAct Monitor (default view). NetAct displays SBTS alarms reported by SBTS, OMS/RNC and BSC in an aggregated view with the NetAct Monitor. NetAct displays context sensitive alarm/fault related documentation. NetAct handles SBTS alarm ACKs and alarm cancellations. NetAct provides the possibility for the operator to initiate upload of SBTS alarms. SBTS alarm synchronization between the SBTS and NetAct is supported through the NE3S WS (automatic and operator initiated synchronization). Web UI displays alarms reported by the SBTS (includes common and transport alarms, as well as technology specific RNW alarms. Web UI displays context sensitive alarm/fault related documentation. Web UI provides the possibility for the operator to display SBTS alarm and fault history.
System impact Interdependencies between features Following features are preconditions for this feature: • • • • • •
SR000726: SRAN BTS Object Model SR000921: SBTS NE3S WS NetAct integration SR000942: SBTS Manual Commissioning and system setup SR000928: SBTS Plug and Play SR000927: SBTS BTS O&M i/f replacement with NBAP for RNC communication SR000926: GSM DSP SW adaptation to new SRAN BTS O&M architecture
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools NetAct is modified to handle alarms from the SBTS and provide an aggregated view of the RATs supported on the SBTS. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.16.1.5
SR000920: SBTS Fault Management management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms The following table lists alarms introduced with this feature.
250
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 151
Descriptions of operability features
New alarms Alarms ID
Alarm name
7100
HARDWARE PROBLEM
7101
RESET NOTIFICATION
7102
RESOURCE BLOCKED BY USER
7103
EXTERNAL ALARM NOTIFICATION
7104
CELL SERVICE PROBLEM
7105
RAT BASE STATION PROBLEM
7106
SINGLE RAN BASE STATION PROBLEM
7107
BASE STATION CONNECTIVITY PROBLEM
7108
BASE STATION SYNCHRONIZATION PROBLEM
7109
BASE STATION SECURITY PROBLEM
7208
LOCAL BLOCK
7600
BCF FAULTY
7602
BCF NOTIFICATION
7606
TRX FAULTY
7607
TRX OPERATION DEGRADED
7625
PS U-PLANE CONNECTION FAILURE
7995
MAINS BREAKDOWN WITH BATTERY BACKUP
Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters The following table lists parameters introduced with this feature. Table 152
New parameters Full name
Abbreviated name
Managed object
Toggling alarm suppression list alToggSuppList
MGMNT
Toggling alarm amount
alToggAmount
MGMNT
Toggling clearance time
alToggClearenceTime
MGMNT
Toggling alarm condition time
alToggConditonTime
MGMNT
BTS fault name
faultName
MGMNT
Suppression of toggling alarms inUse in use
MGMNT
Commands There are no commands related to this feature.
Issue: 01E
DN09218825
251
Descriptions of operability features
4.16.1.6
SRAN 16.2, Feature Descriptions
Sales information Table 153
Sales information
BSW/ASW BSW
License control in network element -
4.17 SR000911: SBTS HW Management 4.17.1 Description of SR000911: SBTS HW Management Introduction to the feature This feature reports 3GPP compliant hardware inventory by the SBTS.
4.17.1.1
Benefits End-user benefits This feature does not affect end user experience. Operator benefits Operator can view all and modify passive 3GPP compliant SBTS hardware via SBTS Element Manager and NetAct.
4.17.1.2
Requirements Hardware requirements This feature does not require any new or additional hardware.
4.17.1.3
Functional description This Feature implements 3GPP compliant BTS hardware model and hardware inventory reported by the SBTS. Following functionalities are supported: •
HW Management modeling as defined in 3GPP: – –
•
HW management via NE3S (CM operations): –
252
3GPP TS 32.622 for managed element and 32.692 ALT1 for inventory unit. Hardware database is available in SBTS.
Nokia provides the HW profiles for supported SBTS configurations. If the hardware is changed, removed or added, a notification is automatically sent and no extra upload is needed. A notification includes the information on the change. All hardware that can communicate with the system module and report its own inventory data, that contains a serial number, product code, and so on is included in the hardware inventory data. Physically detectable hardware is reported
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
– – •
Descriptions of operability features
independent on configuration, for example, if a piece of hardware is detected but is not defined in a profile or SCF, it will be reported. Absent hardware will not be reported even if it's defined in the selected profile. SBTS hardware view is available via SBTS Element Manager and NetAct CM Configurator. User can manually add, remove and modify passive HW via Web UI and NetAct.
SBTS hardware inventory view is licensed in NetAct (it is always available with SBTS Element Manager: – – – –
Automatic hardware change notification is triggered to NetAct on changes. Hardware inventory information is stored in NetAct (network wide hardware inventory). Hardware browsing is available in NetAct. Possible to trigger inventory upload by NetAct. Upload includes all active SBTS hardware detected by SBTS SW and created passive hardware units.
Hardware inventory data is available also via NetAct NBI.
4.17.1.4
System impact Interdependencies between features Related features: • • • •
SR000929: SBTS Configuration Management SR000726: SBTS Object Model SR000921: SBTS NE3S WS NetAct integration SR000713: SBTS Web UI
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools The SBTS HW inventory data is available also from NetAct's NBI. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.17.1.5
SR000911: SBTS HW Management management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults Table 154: New alarms and faults lists alarms and faults related to this feature.
Issue: 01E
DN09218825
253
Descriptions of operability features
SRAN 16.2, Feature Descriptions
Table 154
New alarms and faults
BTS Fault ID 10
BTS Fault name
No connection to unit
4052
Reported alarms
7100 HARDWARE PROBLEM 7101 RESET NOTIFICATION 7104 CELL SERVICE PROBLEM
94
Unknown HW resource
7100 HARDWARE PROBLEM 7104 CELL SERVICE PROBLEM
95
Unit not supported by running SW
7100 HARDWARE PROBLEM
61201
Transport module missing: $U
7100 HARDWARE PROBLEM
61634
Unsupported HW device 7100 HARDWARE PROBLEM
12
Baseband resources mapping to cells failure
7104 CELL SERVICE PROBLEM
7105 RAT BASE STATION PROBLEM
Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 155: New parameters parameters introduced with this feature. Table 155
New parameters
Full name
254
Abbreviated name
Managed object
Inventory unit type
inventoryUnitType
PSSUNT
Manufacturer data
manufacturerData
PSSUNT
Passive unit identifier
passuntId
PSSUNT
Serial number
serialNumber
PSSUNT
Unit position
unitPosition
PSSUNT
Vendor name
vendorName
PSSUNT
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 155
Descriptions of operability features
New parameters (Cont.)
Full name
4.17.1.6
Abbreviated name
Managed object
Vendor unit family type
vendorUnitFamilyType
PSSUNT
Vendor unit type number
vendorUnitTypeNumber
PSSUNT
Version number
versionNumber
PSSUNT
Sales information Table 156
Sales information
BSW/ASW
License control in network element
ASW
NetAct LK
License control attributes ON/OFF
4.18 SR001015: SBTS Incremental Power RTU 4.18.1 Description of SR001015: SBTS Incremental Power RTU Introduction to the feature This feature introduces a common license for output power, independent of the technology it applies to, that uses the license framework as described in SR000794: SBTS SW License Management.
4.18.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits One common sales item simplifies license management of incremental output power handling. Commercial aspects are simplified as no technology-specific planning is required, and operationally the field engineer does not need to cross-check power output between technologies.
4.18.1.2
Requirements Hardware requirements This feature does not require any new or additional hardware.
Issue: 01E
DN09218825
255
Descriptions of operability features
4.18.1.3
SRAN 16.2, Feature Descriptions
Functional description This feature introduces one common incremental output power license. The total output power is divided in steps of 20 W with one license required for each step, independently of the used technology. The first 20W per Radio Frequency Module (RFM) power amplifier is free. Higher RFM power levels and additional power amplifiers (PA) are activated with 20W incremental power licenses. Licenses are counted per PA and power increases less than 20W are not shared between PAs - for example, 30W of power on three PAs requires 3 licenses for the additional 10W on each PA. To enable license control in SBTS, a new read only parameter is introduced, which provides the total amount of 20W licenses needed. This parameter is visible in NetAct and the Software Entitlement Manager (SWEM) checks the activation parameter and compares with the licenses available through CLS. If license capacity is missing then a general limitation action is applied. Examples •
•
1 x 60W 3TX 6RX RFM (3 PAs) with 3+3+3A at 20W: Power per PA: (20W + 20W + 20W) = 60W Licenses per PA required: (60W - 20W) / 20W = 2 (the first 20W per PA is free) 2 additional licenses are needed per PA, for a total of 6 licenses. 3 x 40W 2TX 2RX RFM (one PA used) with 3+3+3A at 10W: Power per PA: (10W + 10W + 10W) = 30W Licenses per PA required: (30W - 20W) / 20W = 1 (the first 20W per PA is free, a full 20W license is required for the additional 10W) 1 additional license is needed per PA, for a total of 3 licenses
RF Sharing In the case of RF Sharing, the license logic follows these rules: •
•
•
4.18.1.4
GSM - WCDMA RF-Sharing WCDMA gets the first 20W per PA from the RFM. All higher power levels for WCDMA and all power for GSM are enabled with 20W power licenses. WCDMA - LTE RF-Sharing WCDMA gets the first 20W per PA from the RFM. All higher power levels for WCDMA and all power for LTE are enabled with 20W power licenses. GSM - LTE RF-Sharing LTE gets the first 20W per PA from the RFM. All higher power levels for LTE and all power for GSM are enabled with 20W power licenses.
System impact Interdependencies between features This feature requires the following feature: •
SR000794: SBTS SW License Management
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools
256
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.18.1.5
SR001015: SBTS Incremental Power RTU management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 157: New parameters lists parameters introduced with this feature. Table 157
New parameters
Full name
Abbreviated name
Number of incremental power steps
4.18.1.6
numberOfIncrementalPowerS CAPCFG teps
Sales information Table 158
Issue: 01E
Managed object
Sales information
BSW/ASW
License control in network element
ASW
Pool license
DN09218825
257
Descriptions of operability features
SRAN 16.2, Feature Descriptions
4.19 SR001057: SBTS inheritance of Network Resiliency for mcBSC 4.19.1 Description of SR001057: SBTS inheritance of Network Resiliency for mcBSC Introduction to the feature This feature provides GSM radio network protection against complete Multicontroller BSC (mcBSC) failures. This feature inherits from GSM feature RG301939: Network Resiliency for mcBSC.
4.19.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature enables the operator a quick recovery of GSM service after a failure of protected mcBSC site, for example in case of a fire accident, a flooding or an earthquake. The resiliency of protected mcBSC is supported with semiautomatic and fast switchover to the backup mcBSC. There is no need for manual reconfiguration in Base Station System (BSS) or core network when backup mcBSC starts its operation after protected mcBSC failure.
4.19.1.2
Requirements Hardware requirements This feature requires the following hardware components: • •
4.19.1.3
Flexi Multiradio 10 System Module (FSMF) Multicontroller BSC Product configurations with BCN-B and BMPP2-B (HW Rel2)
Functional description This feature provides GSM radio network protection against mcBSC failures. This feature inherits from GSM feature RG301939: Network Resiliency for mcBSC. This feature implements a concept for mcBSC resiliency. A pair of mcBSC is defined, one mcBSC is protected and the other one is the backup. In the normal situation the backup mcBSC does not carry any traffic. When a fault occurs in protected mcBSC, the traffic can be redirected and handled by backup mcBSC. Configuration is synchronized from the protected mcBSC to the backup mcBSC. In case of failure of the protected mcBSC, the backup mcBSC takes over traffic after a command from the operator. One backup mcBSC can serve up to 16 protected mcBSCs. Dual homed SBTSs are switched over from the protected mcBSC to the backup mcBSC. The operator can also trigger switchover back to the protected mcBSC after it is restored from backup media.
258
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
The SBTS can have signaling connection to protected or backup mcBSC. Only one signaling connection is possible at a time. When SBTS loses the connection to the protected mcBSC, it tries to establish a signaling connection to the backup mcBSC. Both backup mcBSC or protected mcBSC can request to initiate the switchover procedure. Values of the Cell Global Identifier (CGI) and other radio parameters remain the same after the serving mcBSC is changed. If secure associations are used, the SBTS can be connected to additional Serving Gateway (S-GW). The SBTS has connections to two S-GWs at the same time. There are separate S-GWs for protected and backup mcBSCs. After a switchover from protected to backup mcBSC, the core network still sees the same signaling points, the same Location Area (LA) or Routing Area (RAs) and the same SBTSs/cells. The mcBSC switchover always means mcBSC restart. Figure 45
SBTS inheritance of Network Resiliency for mcBSC
BackupBSC
NetAct
Packet Abis
SBTS
AoIP AoIP
CSCore
Gb/IP
Packet Abis
Gb/IP
mcBSC outofservice
4.19.1.4
PSCore
System impact This feature is implemented for GSM/2G BSS. Single RAN inherits the resiliency for mcBSC. Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
Issue: 01E
DN09218825
259
Descriptions of operability features
4.19.1.5
SRAN 16.2, Feature Descriptions
SR001057: SBTS inheritance of Network Resiliency for mcBSC management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 159: New parameters lists parameters introduced with this feature. Table 159
New parameters
Full name
4.19.1.6
Managed object
Management plane backup remote IP address for OMUSIG
mPlaneRemoteIpAddressOm BTSSCC uSig2
Switchover fail timer
switchoverFailTimer
BTSSCC
Switchover start timer
switchoverStartTimer
BTSSCC
Sales information Table 160
g
Abbreviated name
Sales information
BSW/ASW
License control in network element
ASW
-
Note: License control for this feature is the same as for RG301939: Network Resiliency for mcBSC feature.
4.20 SR000924: SBTS Intelligent shut down 4.20.1 Description of SR000924: SBTS Intelligent shut down Introduction to the feature
260
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
This feature introduces the possibility to shut down the SBTS in a controlled way, and to do that separately for each RAT.
4.20.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature optimizes the use of one battery backup system on a high-capacity SBTS, especially in sites that operate as important transmission hub nodes. With the Intelligent shut down feature, separate backup systems for SBTS and transmission are unnecessary. One RAT may be shut down on a multi-RAT system without affecting the others.
4.20.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.20.1.3
Functional description This feature introduces the possibility to shut down the SBTS, cells or module controller in a predefined way, making it possible to optimize SBTS on-air availability with battery backup systems. The SBTS with battery backup system supports an intelligent SBTS site power shutdown procedure in the event of an AC power failure. During the commissioning of each site, the operator can define different shutdown timers and priorities for the SBTS sectors and carriers. Intelligent shutdown is activated from the power systems by activating one external alarm connection (EAC) line on FSM1 in Flexi BTS. The SBTS shuts down in a way that the SBTS state is known at all times, and logs may be collected.
4.20.1.4
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
Issue: 01E
DN09218825
261
Descriptions of operability features
4.20.1.5
SRAN 16.2, Feature Descriptions
SR000924: SBTS Intelligent shut down management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 161: New Alarms lists alarms introduced with this feature. Table 161
New Alarms
Alarm ID
Alarm name
7100
HARDWARE PROBLEM
7104
CELL SERVICE PROBLEM
7995
MAINS BREAKDOWN WITH BATTERY BACKUP
BTS faults and reported alarms Table 162: New BTS faults lists BTS faults introduced with this feature. Table 162
New BTS faults
Fault ID 37
Fault name
Reported Alarms
Mains power break, running battery backup
7100 HARDWARE PROBLEM
38
Delayed cell shutdown alarm
7104 CELL SERVICE PROBLEM
39
Immediate cell shutdown alarm
7104 CELL SERVICE PROBLEM
7995 MAINS BREAKDOWN WITH BATTERY BACKUP
Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 163: New parameters lists parameters introduced with this feature. Table 163
New parameters
Full name
Abbreviated name
Intelligent shutdown timeout
262
intShutdownTimeout
DN09218825
Managed object LCELL
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 163
Descriptions of operability features
New parameters (Cont.)
Full name
4.20.1.6
Abbreviated name
Managed object
Intelligent shutdown timeout
intShutdownTimeout
LCELW
Mains power alarm connector reference
mainsPowerAlarmConnectorR MGMNT ef
Intelligent shutdown in use
intShutdownInUse
SBTS
Sales information Table 164
Sales information
BSW/ASW
License control in network element
ASW
Pool license
4.21 SR000937: SBTS LTE trace 4.21.1 Description of SR000937: SBTS LTE Trace Introduction to the feature This feature provides identical trace functionality to two existing LTE trace features, LTE433: LTE Trace for cell and LTE163: Subscriber and equipment trace.
4.21.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides trace functionality for the LTE RAT in SRAN that is equivalent to the trace functionality in existing LTE networks, reducing complexity and OPEX.
4.21.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.21.1.3
Functional description This feature brings two LTE trace functionalities SBTS: Subscriber and equipment trace and Cell trace. Subscriber and equipment trace:
Issue: 01E
DN09218825
263
Descriptions of operability features
SRAN 16.2, Feature Descriptions
The subscriber and equipment trace supports the tracing for a specific IMSI or IMEI and it provides detailed subscriber-oriented information at the call level for one or more specific mobile(s). The traces are activated on demand. The trace session activation and deactivation is triggered by the core network. Within the SBTS the trace session for the specific LTE subscriber is started on receipt of a S1AP message from the core network. The trace session in SBTS is deactivated when it receives the trace deactivation message from the core network or the last connection for the traced subscriber is released. Trace data is stored in NetAct and presented by NetAct Trace Viewer. NetAct Trace Viewer is also used to set the trace parameters. The Nokia "Subscriber and Equipment Trace" solution follows the general definitions recommended by 3GPP TS 32.421 and 32.422. Cell trace: During Cell Trace, all the UEs in a target cell that are in connected state are traced simultaneously. The target cell is defined by the operator. Cell Trace supports tracing the network layer contents of S1-AP, X2-AP and eUu RRC messages of the control plane. The user plane is not traced. Cell trace is activated with NetAct Trace Viewer application, and the data can be collected directly to NetAct Trace Viewer for evaluation.
4.21.1.4
System impact Interdependencies between features This feature requires the following features: • •
SR000921: SBTS NE3S WS NetAct integration SR000929: SBTS Configuration Management
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.21.1.5
SR000937: SBTS LTE Trace management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature.
264
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 165: New parameters lists parameters introduced with this feature. Table 165
New parameters
Full name
Abbreviated name
Managed object
Trace control identifier
ctrlTsId
CTRLTS
3rd party trace reporting
extTraceReporting
CTRLTS
3rd party cell trace reporting
extCellTraceRep
CTRLTS
3rd party UE trace reporting
extUeTraceRep
CTRLTS
Maximum UE trace sessions allowed
maxUeTraceSessions
CTRLTS
3rd party tool trace port number
tceTracePortNum
CTRLTS
Trace reporting mode
traceRepMode
CTRLTS
Cell trace reporting mode
cellTraceRepMode
CTRLTS
UE trace reporting mode
ueTraceRepMode
CTRLTS
UE active trace sessions present flag
ueActiveTrcSessFlag
CTRLTS
Vendor specific extension tracing
vendorSpecTracing
CTRLTS
TA tracing
taTracing
CTRLTS
Activate cell trace
actCellTrace
LNBTS
Activate subscriber and equipment trace
actSubscriberTrace
LNBTS
Cell trace mode
cellTrcMode
MTRACE
E-UTRAN trace identifier
eutranTraceId
MTRACE
Cell trace session identifier
mTraceId
MTRACE
3rd party tool cell trace port number
tceCellTracePortNum
MTRACE
Trace collection entity IP address
tceIpAddress
MTRACE
Issue: 01E
DN09218825
265
Descriptions of operability features
4.21.1.6
Sales information Table 166
g
SRAN 16.2, Feature Descriptions
Sales information
BSW/ASW
License control in network element
ASW
NetAct LK
Note: Note: Existing NetAct (LTE) licenses are valid for this feature: SI RL000145.T and SI RL000146.T
4.22 SR000942: SBTS Manual Commissioning and system setup 4.22.1 Description of SR000942: SBTS Manual Commissioning and system setup Introduction to the feature This feature introduces manual commissioning and site setup with local management tools.
4.22.1.1
Benefits End-user benefits This feature does not affect end-user experience. Operator benefits Site commissioning and setup with the use of Web UI or NetAct.
4.22.1.2
Requirements Hardware requirements This feature does not require any new or additional hardware.
4.22.1.3
Functional description Migration and commissioning involves a sequence of tasks, such as visual checks and inspections and parameter and software configurations, to ensure that the stand-alone equipment in question has been properly installed, has no faulty modules and is ready for integration. The generic commissioning steps are presented in Figure 46: SBTS commissioning overview. For more information on SBTS commissioning, go to the Migration to SBTS and Commissioning SBTS document.
266
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Figure 46
Descriptions of operability features
SBTS commissioning overview Start
Localconnection
Remoteconnection
SCFconversion
SWUpdatetoSRANSW usingSiteManager.
Sitereset
SCFandprofile uploadusing SBTSElementManager
Sitereset
Integration toNetAct
4.22.1.4
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity
Issue: 01E
DN09218825
267
Descriptions of operability features
SRAN 16.2, Feature Descriptions
This feature has no impact on system performance or capacity.
4.22.1.5
SR000942: SBTS Manual Commissioning and system setup management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults There are no alarms and faults related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
4.22.1.6
Sales information Table 167
Sales information
BSW/ASW
License control in network element
BSW
-
License control attributes -
4.23 SR000921: SBTS NE3S WS NetAct integration 4.23.1 Description of SR000921: SBTS NE3S WS NetAct integration Introduction to the feature This feature enables the SBTS to integrate directly to NetAct using the HTTPS-based Nokia internal NE3S WS interface. This interface is highly scalable and provides inbuilt support for security.
4.23.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The SBTS NE3S integration provides a flat operation, administration and maintenance (OAM) architecture without unnecessary mediation devices. The OMS unit is no longer needed for SBTS.
268
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.23.1.2
Descriptions of operability features
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.23.1.3
Functional description SRAN16 introduces a new SBTS architecture, in which all of the radio access technology (RAT)-specific applications execute on a single system module (with extension modules if required) in the SBTS. This feature allows the management of the SBTS using common, rather than RAT-specific, OAM software using a single direct, NE3S WS based M-plane interface to NetAct. There is no mediation platform (OMS) in between the NetAct and SBTS in this architecture. Figure 47
NetAct and SBTS management architecture
NetAct NE3S Manager(CM)
NE3S Interface
RemoteSBTSService SBTS adaptor
SiteOAM
NE3SManager (non-CM)
NE3S Mediation NE3S Mediation
NE3S Interface NE3SconnectionforCM NE3SconnectionforNon-CM(otherFA)
SiteOAM
SBTSSystemModule AlreadyIntegrated SBTS
To support the NE3S WS interface, NetAct hosts two NE3S WS managers: one for handling configuration management operations for the SBTS and the other for handling the rest of the OAM operations, such as fault management and performance management operations, for the SBTS. Therefore, there are two corresponding NE3S WS connections between a SBTS and NetAct. Similarly, to support the NE3S WS interface, SBTS hosts a NE3S WS agent service in the Site OAM component that handles the two NE3S WS connections to NetAct and treats them as one logical NE3S WS connection. Over the NE3S WS interface, NetAct sees Physical SBTS (P-SBTS) that is physically installed in the RAN and connected to NetAct. The P-SBTS connects over a NE3S WS interface to the NetAct NE3S WS managers.
Issue: 01E
DN09218825
269
Descriptions of operability features
SRAN 16.2, Feature Descriptions
The NE3S WS interface supports the following message types: • •
Synchronous messages from NetAct to SBTS (and in-band responses from the SBTS) Asynchronous messages and notifications from SBTS to NetAct (and acknowledgements from NetAct)
This feature supports security of the NE3S WS interface between the SBTS (either virtual or physical) and NetAct. This includes setting up the HTTP over TLS connection and mutual authentication during NE3S WS registration. For better security, NE3S WS uses HTTP over TLS by default. However, the operator may choose to turn TLS off if it is not required. The NetAct NE3S WS interface implements the following authentication methods: • •
For HTTP a username/password pair is used during establishment of the HTTP session. For TLS: –
•
4.23.1.4
If an operator PKI-signed certificate is available and TLS is turned on (the default), then operator PKI-signed certificates are used for establishment of the TLS session between NetAct and P-SBTS.
For NE3S WS registration, self-signed certificates that are packaged as part of the NetAct and SBTS software builds are used for vendor authentication during NE3S WS registration.
System impact Interdependencies between features This feature requires the following features as prerequisites: • • • • •
SR000846: SBTS Vendor Certificate Management SR000845: SBTS Operator Certificate Management SR000900: SBTS Operator Account Management SR000899: SRAN Support for TLS1.2 SR001003: IPv4 based SBTS Management Plane
Impact on interfaces This feature provides the SBTS NE3S interface to NetAct. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.23.1.5
SR000921: SBTS NE3S WS NetAct integration management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms
270
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 168: New parameters lists parameters introduced with this feature. Table 168
New parameters
Full name
4.23.1.6
Abbreviated name
Managed object
Management plane DSCP
mPlaneDscp
MPLANE
Management plane IP address
mPlaneIpAddress
MPLANE
Management plane object identifier
mplaneId
MPLANE
TLS usage towards the operation and maintenance system
oamTls
MPLANE
Sales information Table 169
Sales information
BSW/ASW
License control in network element
BSW
-
4.24 SR000906: SBTS Nokia Service Account Management 4.24.1 Description of SR000906: SBTS Nokia Service Account Management Introduction to the feature The SR000906: SBTS Nokia Service Account Management feature provides the operator the mechanism to manage the SBTS Service Account from security aspect. The inroduced functions allows the operator the following acivities: •
Issue: 01E
Managing the Service Account password and the Service Account key based authentication for access to the SBTS via the Secure Shell (SSH) connection.
DN09218825
271
Descriptions of operability features
• •
4.24.1.1
SRAN 16.2, Feature Descriptions
Controlling the access (enable/disable) to the SSH and Research and Development (R&D) Ports. Setting a value for activity and delay timers for the SSH login.
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides remote and local access to the Nokia Service Account that is administered by the operator.
4.24.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.24.1.3
Functional description This feature improves the security of the SBTS Service Account and all associated access services. The Service Account is used by Nokia field service technicians when responding to service calls. The Service Account enables access to the SBTS over Secure Shell (SSH). SSH provides secure system administration. The access is granted after entering the username and password or through key based authentication. A Nokia default user account is accessible via the username: "toor4nsn". This feature enables the operator to configure: • •
• •
g
Service Account password - The operator can change the password of the default Nokia account, so it is known only to him. Up to 10 SSH public keys - The SSH public keys are used for authentication and can be used instead of the password. Internodal system module (master to slave and slave to master) is password-based in case of multiple system module configuration. SSH Client Alive Timer session inactivity timer - The inactivity timer is used to automatically close the SSH session. Range: 1 to 60 min, default value: 45 min. Session login delay timer value - The session login delay timer value specifies the time between login failure and the next login attempt. Range: 1 to 60 seconds, default value: 10 seconds. Note: The Session login delay timer value is randomly spread by plus or minus up to 25% of actual setting for security robustness.
• •
SSH access control - The SSH access can be enabled or disabled, by default it is disabled. R&D service port activation - The R&D service port can be enabled or disabled, by default it is disabled.
All local and remote logins to the SBTS Service Account, activation and deactivation of R&D services, SSH sessions, and executed commands are logged at the SBTS. This information is stored as an RUEM log file and contains user ID, start time, and end time of each session.
272
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
g
Descriptions of operability features
Note: In the RUEM log only events originating from WebUI are logged. Changes done via NetAct are not logged in the RUEM logfile. The configuration can be performed using: • • •
g
Web UI (configuration of a single SBTS) NetAct configurator application (configuration of the SSH public keys and SSH parameters) NetAct network element access control (mass password distribution to a list of SBTSs under one NetAct) Note: The SSH and R&D access settings are not persistent across reboot/restart operation.
Figure 48
Overview of interfaces used for configuring SBTS Nokia Service Account
NetAct!framework “Configurator”
“NetAct!NEAC Tool”
Security!credential mass!configuration
Service SBTS Access Operator configuration user NE3S REST
SSH Nokia Service user
4.24.1.4
SBTS
Local!BTS SSH!account
SSH Access
System impact Interdependencies between features This feature requires the features: • • • •
SR000713: SBTS Web UI SR000900: SBTS Operator Account Management SR000903: SBTS User Event Logging SR000921: SBTS NE3S WS NetAct Integration
This feature is a prerequisite for the following feature: •
SR000942: SBTS Manual Commissioning and system setup
Impact on interfaces
Issue: 01E
DN09218825
273
Descriptions of operability features
SRAN 16.2, Feature Descriptions
The NE3S interface between SBTS and NetAct is adapted to support the update of the Service Account password and input of parameters by the operator. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.24.1.5
SR000906: SBTS Nokia Service Account Management management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 170: New parameters lists parameters introduced with this feature. Table 170
New parameters
Full name
274
Abbreviated name
Managed object
Security administration identifier
secadmId
SECADM
Service account SSH status
serviceAccountSshStatus
SECADM
Service port status
servicePortStatus
SECADM
Service user public keys
serviceUserPublicKeys
SECADM
Key description
keyDescription
SECADM
Key value
keyValue
SECADM
SSH client alive timer
sshClientAliveTimer
SECADM
SSH session login delay Timer
sshSessionLoginDelayTimer
SECADM
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.24.1.6
Descriptions of operability features
Sales information Table 171
Sales information
BSW/ASW
License control in network element
BSW
-
4.25 SR000726: SBTS Object Model 4.25.1 Description of SR000726: SBTS Object Model Introduction to the feature This feature introduces the universal information model and site configuration for the SBTS. The model contains RAT, transport network layer, synchronization and hardware configuration. Logical RAT radio network parameters (RNW) models are compatible with single RAT (SRAT) models. Hardware, transport and synchronization models are new and specific to SBTS. The model is structured under a new SBTS root object.
4.25.1.1
Benefits End-user benefits This feature does not affect end user experience. Operator benefits Common object model for SBTS enables management of a whole SBTS architecture (all RATs), while reusing the RNW definitions especially from LTE, saves effort for the operator.
4.25.1.2
Requirements Hardware requirements To be defined.
4.25.1.3
Functional description Prior to SRAN16.2, all radio access technologies (RATs) worked together within a single site in a concurrent manner with independent configurations and management planes. Starting from SRAN16.2, an integrated SRAN BTS is introduced with common transport and a unified management plane. The following figure shows the structural differences in the architecture between the current single RAT and the new SRAN O&M architecture.
Issue: 01E
DN09218825
275
Descriptions of operability features
Figure 49
SRAN 16.2, Feature Descriptions
SRAT and SRAN architecture comparison
SRAT Architecture
SRAN Architecture
NetAct Applications Q3
NES3
NWI3
3GOMS
BSC
4GOMS
3GOMS
RNC
BSC
RNC Web UI
2G SEM
3G SEM
4G SEM
2GBTS
3GBTS
4GBTS
SBTS SiteOAM
The SBTS uses a integrated information model, which contains the radio network, hardware, transport network layer (TNL), synchronization and operational M-plane configuration. The model is structured under a new SBTS root object, which acts as the globally unique identifier for SBTS. The logical RNW part of the model is compatible with single RAT releases. LTE cell model under LNCEL object is the same both for SBTS and LTE specific eNB. This allows the same RNW model to be used in both planning and operating stages, making the SBTS an integral part of the radio network also during mixed network scenarios. SBTS information model provides relations between the SBTS and the corresponding logical RNW objects controlled by the RNC and BSC. Nokia NetAct provides a visual interface in which the operational relations between units can be managed. The SBTS hardware is covered by one common hardware model. SBTS internal details are automatically generated based on BTS hardware profiles to simplify planning and to avoid configuring unnecessary internal details. All supported SBTS profile configurations are provided by Nokia and correspondingly identified within the model information. Transport network layers and synchronization models are SBTS specific and support the new functionality and architecture. TNL hardware configuration is closely integrated with the common hardware model. SBTS information model also includes operational part related to M-plane and other SBTS specific configuration.
4.25.1.4
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity
276
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
This feature has no impact on system performance or capacity.
4.25.1.5
SR000726: SBTS Object Model management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Commands There are no commands related to this feature.
4.25.1.6
Sales information Table 172
Sales information
BSW/ASW BSW
License control in network element -
4.26 SR000900: SBTS Operator Account Management 4.26.1 Description of SR000900: SBTS Operator Account Management Introduction to the feature This feature provides account management capabilities for the user accounts that are used to log in to the Web UI on the SBTS. The access to the SBTS is granted by a single local operator user account and multiple remote user accounts handled by the NetAct Centralized Network element User Management (CNUM) application.
4.26.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits
Issue: 01E
DN09218825
277
Descriptions of operability features
SRAN 16.2, Feature Descriptions
Enhanced risk management is achieved because of controlled and protected local and remote access security and preventive measures against brute force attacks.
4.26.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.26.1.3
Functional description This feature provides support for both local and remote user accounts and associated management for Web UI access. There are two types of account that are used for managing the SBTS: •
•
local user account This is a single account on the SBTS which is defined by an operator username/password and has administrator privileges. The password is stored in the SBTS local secure environment and is cryptographically hashed and accompanied by a random salt. The default username is "nemuadmin" and the default password "nemuuser". These default credentials must be changed by the operator during site commissioning and they must be regularly updated to keep the SBTS hardened against attacks. The given administrator privileges cannot be modified/lowered. remote user accounts (CNUM accounts) These are created and managed in NetAct. The communication between the SBTS and NetAct CNUM LDAP server uses only the credential-based bind (not anonymous bind), and is secured by secure LDAP if TLS support is activated for the SBTS.
Figure 50
Operator Account Management in SRAN provides a high level view of the SRAN architecture related to Operator Account Management
NetActframework WebBrowser
CNUM
LDAP query: user-id/pwd? LocalBTS User Account Lastlogin
WebBrowser
Lastlogin
BTS CNUMuser accounts
This feature provides enhanced security mechanisms for the user accounts to prevent brute force attacks. These mechanisms include session login delay and account locking.
278
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
• • •
Descriptions of operability features
Permanent account locking - an account with an expired password is permanently locked until the password is changed. Session login delay - if a user enters an incorrect password, the user is not allowed to attempt to log in again for a configurable amount of time. Temporary account locking - if a user enters an incorrect password for a configurable number of times in a row, the account is locked temporarily before they can attempt to log in again. An alarm is generated if the number of unsuccessful attempts exceeds a configurable threshold.
This feature allows the operator to specify the following configuration information: • • •
• •
•
4.26.1.4
Local user account username and password. This can be configured either from NetAct for multiple SBTSs or from Web UI for one particular SBTS. Remote user accounts usernames and passwords. This can be configured from NetAct User Management GUI. Session delay time - the length of time that the system waits after a user enters incorrect login credentials before allowing the user to attempt to log in again from Web UI. This can be configured either from NetAct for multiple SBTSs or from Web UI for one SBTS. Maximum number of failed login attempts – the account is temporarily locked after this number of failed login attempts, and must be unlocked by an administrator. Temporary account locking time/reset time - when an account is temporarily locked, the system waits this amount of time before allowing the user to attempt to log in again from Web UI. This can be configured either from NetAct for multiple SBTSs or from Web UI for one SBTS. Failed logins alarm threshold (applies to both local and remote users) - an alarm is raised after this number of failed login attempts. This should be less than or equal to the "Maximum number of failed login attempts". This can be configured either from NetAct for multiple SBTSs or from Web UI for one SBTS.
System impact Interdependencies between features This feature requires the following features: • • •
SR000713: SBTS Web UI SR000921: SBTS NE3S WE NetAct Integration SR000903: SBTS User Event Logging
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has an impact on network element management tools as beneath: •
Remote users from NetAct can log in to the SBTS Web UI with their own credentials.
Impact on system performance and capacity This feature has no impact on system performance or capacity.
Issue: 01E
DN09218825
279
Descriptions of operability features
4.26.1.5
SRAN 16.2, Feature Descriptions
SR000900: SBTS Operator Account Management management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 173: New parameters lists parameters introduced with this feature. Table 173
New parameters
Full name
4.26.1.6
Managed object
Instance identifier of the AMGR object
amgrId
AMGR
Check CNUM password policy
checkCnumPasswordPolicy
AMGR
LDAP server TLS access mode
ldapConnectionType
AMGR
Port number of the primary LDAP server
ldapPortPrimary
AMGR
IP address of the primary LDAP server
ldapServerPrimary
AMGR
Local password warning period
localPasswdWarningPeriod
LUAC
Local User Account Identifier
luacId
LUAC
Sales information Table 174
280
Abbreviated name
Sales information
BSW/ASW
License control in network element
ASW
NetAct LK
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
4.27 SR000845: SBTS Operator Certificate Management 4.27.1 Description of SR000845: SBTS Operator Certificate Management Introduction to the feature This feature introduces automated lifecycle management of an X.509 operator certificate. The feature supports multi-layer hierarchical public key infrastructure (PKI), chain of trust and cooperation with another operator’s PKI.
4.27.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • • • • •
4.27.1.2
improvement to system security PKI architecture capable of managing all Nokia RAT technologies mutual authentication based on digital public certificates simplified cooperation between operators in case of RAN sharing 3GPP compliant certificates’ lifecycle management
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.27.1.3
Functional description Supported public key infrastructure (PKI) architecture and chain of trust An SBTS supports multi-layered public key infrastructure (PKI) hierarchy. The operator can divide the PKI architecture into a Root Certificate Authority (Root CA) and multiple subordinate Certificate Authorities (CAs). The SBTS possesses a complete chain of trust that is involved in issuing an operator certificate. The chain of trust consists of all subordinate CA certificates, cross-signed CA certificates and the root CA certificate (a self-signed certificate also referred as the trust anchor). The SBTS and peer entity’s certificate chain of trust support up to three subordinate CAs. The additional subordinate CA certificates used for signing a revocation list do not belong to the SBTS’s chain of trust. The SBTS supports the cooperation with security gateways that belong to a PKI domain of another operator’s network. It is useful for example in case of RAN sharing and can be performed in two ways: • •
Issue: 01E
The root CA certificate of the second PKI is deployed into the SBTS trust pool. The cross-signed certificate of the second PKI is deployed into the SBTS trust pool.
DN09218825
281
Descriptions of operability features
Figure 51
SRAN 16.2, Feature Descriptions
Multi-layered public key infrastructure (PKI) architecture Root Certificate Sub-CA 1 Certificate
SigningHierarchy
Sub-CA 2 Certificate Sub-CA 3 Certificate
NetworkOperator
RANSharingOperator
RootCA Certificate
RootCA Certificate
CRL
CRL
RootCA RAN Operator
CRL
CRL
Subordinate -CA
RootCA RANSharing Operator Subordinate -CA
CRL
Entity Certificate SBTS
NetAct
RootCA Certificate
other vendors NB/eNB
SeGW
SeGW 2nd Operator
Operator certificate and Root CA certificate lifecycle management 1. Automated SBTS operator certificate management The SBTS supports the automated operator certificate enrollment during SBTS commissioning and automated timer controlled update of the operator certificate. Operator’s CA deploys the operator certificate using Certificate Management Protocol version 2 (CMPv2). The deployment process is as follows: •
• •
•
g
The SBTS generates internally a RSA key pair and sends the public key within a CMP initial signing request to the CA. The Nokia SBTS authenticates itself using a Nokia vendor certificate. SBTS also supports alternative authentication methods: authentication by pre-shared secret key and reference number (PSK/Refnum), and authentication by an SBTS self-signed certificate. The CA responds with the signed SBTS operator certificate and the complete chain of trust (including the root CA certificate). The SBTS automatically renews the operator certificate before its lifetime expires. The SBTS generates a new RSA key pair internally and sends the public key within a CMP key update request to the CA. In contrast to the initial signing, the SBTS confirms its identity using the valid operator certificate. The CA responds with a newly signed SBTS operator certificate and all corresponding CA certificates. The root CA certificate is only sent in a CMP initialization response. Note: Trust anchors, cross-signed CA certificates and additional revocation list CA certificates are not automatically updated by CMP, and must be manually updated by the operator network-wide. However, SBTS sends an alarm to NetAct if a trust anchor, cross-signed certificates or additional revocation list CA certificates are close to expiring so that operator can take actions. In case SBTS own trust anchor is close to expiring the operator can initiate a new CMP initialization request.
2. Manual SBTS operator certificate management
282
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
The CMP-based initial signing request and key update request can be triggered on demand by the operator using Web UI or NetAct Certificate Management Tool as well. In case the operator has no online PKI then RSA key pair created offline, SBTS operator certificate, and trust chain certificates can be deployed within a single password protected PKCS#12 file and imported into the SBTS using Web UI.
g
Note: The SBTS does not provide a RSA key export interface for offline certificate signing. Therefore, the RSA key pair must be generated outbound. 3. Manual trust anchor, cross-signed CA certificates and revocation list CA certificates management The trust anchors, cross-signed CA certificates and additional revocation list CA certificates can be added to the SBTS trust pool by provisioning the certificate as PEM file. The PEM file can be imported into the SBTS using Web UI or NetAct Certificate Management Tool. NetAct Certificate Management Tool enables simultaneous deployment to a list of SBTSs under one NetAct.
g
Note: The addition of a new trust anchor, cross-signed CA certificate or revocation list CA certificate does not delete an existing certificate of the same type. Old versions must be removed manually using Web UI or NetAct Certificate Management Tool. Revocation Management The operator can revoke certificates (for example if the private key is compromised or the boundary network element is out of service). The operator’s PKI provides the information about revoked certificates using certificate revocation lists (CRL). The SBTS supports the import of CRL using LDAPv3 from repositories. Stored CRLs are automatically updated by the SBTS. The update can be also triggered by the operator using Web UI or NetAct Certificate Management Tool.
4.27.1.4
System impact Interdependencies between features This feature requires the following features: • •
SR000846: SBTS Vendor Certificate Management SR000921: SBTS NE3S WS NetAct integration
This feature is a prerequisite for the following features: • • • • • •
SR000365: SBTS IPSec SR000713: SBTS Web UI SR000899: SRAN Support of TLS 1.2 SR000921: SBTS NE3S WS NetAct integration SR000928: SBTS Plug and Play SR000937: SBTS monitoring and tracing
Impact on interfaces This feature has an impact on interfaces as beneath:
Issue: 01E
DN09218825
283
Descriptions of operability features
•
SRAN 16.2, Feature Descriptions
NE3S interface between SBTS and NetAct is introduced. This interface enables the operator to configure certificate management parameters using NetAct and to trigger certificate management operations.
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.27.1.5
SR000845: SBTS Operator Certificate Management management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms Table 175: New BTS faults lists BTS faults introduced with this feature. Table 175
Fault ID
New BTS faults
Fault name
Reported alarms
61510
Automatic BTS Operator Certificate retrieval unsuccessful
7109 BASE STATION SECURITY PROBLEM
61074
CRL Update Failure
7109 BASE STATION SECURITY PROBLEM
61616
Vendor BTS certificate is about to expire
7109 BASE STATION SECURITY PROBLEM
61618
BTS and/or peer trust 7109 BASE STATION SECURITY PROBLEM anchor expired or due to expire
Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 176: New parameters lists parameters introduced with this feature.
284
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 176
Descriptions of operability features
New parameters
Full name
Issue: 01E
Abbreviated name
Managed object
CA certificate type
caType
CACERT
Certificate authority certificate identifier
cacertId
CACERT
Certificate fingerprint
fingerprint
CACERT
Certificate issued to
issuedTo
CACERT
Certificate issued by
issuer
CACERT
Certificate serial number
serialNumber
CACERT
CA certificate type
source
CACERT
Certificate valid from
validFrom
CACERT
Certificate valid to
validTo
CACERT
Certification handler identifier
certhId
CERTH
Update time for CA certificate renewal
caCertificateUpdateTime
CMP
CMP server subject name
caSubjectName
CMP
Certificate management protocol identifier
cmpId
CMP
Update time for NE certificate renewal
neCertificateUpdateTime
CMP
CMP server IP address
serverHost
CMP
CMP directory
serverPath
CMP
CMP server port number
serverPort
CMP
CMP state
state
CMP
CRL distribution point configuration identifier
crldpconfigId
CRLDPCONFIG
Primary CRL distribution point URI
primaryCRLDP
CRLDPCONFIG
Secondary CRL distribution point URI
secondaryCRLDP
CRLDPCONFIG
Certificate revocation list handling identifier
crlhId
CRLH
CRL distribution point source
distributionPointSource
CRLH
CRL state
state
CRLH
CRL update period
updatePeriod
CRLH
CRL usage enabled
usageEnabled
CRLH
CRL info identifier
crlinfoId
CRLINFO
CRL distribution point type
distributionPointType
CRLINFO
CRL distribution point URI
distributionPointURI
CRLINFO
CRL last download status
downloadStatus
CRLINFO
Current CRL issuer
issuer
CRLINFO
CRL next update
nextUpdate
CRLINFO
CRLs number of revoked certificates
numOfRevCert
CRLINFO
Current CRL issue date
thisUpdate
CRLINFO
DN09218825
285
Descriptions of operability features
Table 176
SRAN 16.2, Feature Descriptions
New parameters (Cont.)
Full name
4.27.1.6
Abbreviated name
Managed object
CRL update failure reason
updateFailureReason
CRLINFO
Certificate fingerprint
fingerprint
NECERT
Certificate issued to
issuedTo
NECERT
Certificate issued by
issuer
NECERT
NE certificate identifier
necertId
NECERT
Certificate serial number
serialNumber
NECERT
Certificate source
source
NECERT
Certificate valid from
validFrom
NECERT
Certificate valid to
validTo
NECERT
Sales information Table 177
Sales information
BSW/ASW
License control in network element
ASW
Pool license
4.28 SR001244: SBTS PAoTDM for Flexi BSC with transport media converter 4.28.1 Description of SR001244: SBTS PAoTDM for Flexi BSC with transport media converter Introduction to the feature This feature introduces support of SBTS Packet Abis over TDM interface (PAoTDM) for BSC3i 1000 or BSC3i 2000 and Flexi BSC with transport media converter and without IPSec support.
4.28.1.1
Benefits End-user benefits This feature does not affect end-user experience. Operator benefits This feature supports TDM transport reuse with eliminating need to replace existing TDM lines with Ethernet for Abis.
286
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.28.1.2
Descriptions of operability features
Requirements Hardware requirements This feature requires the BSC3i 1000, BSC3i 2000 or Flexi BSC External media converter at BSC site.
4.28.1.3
Functional description The SR001244: SBTS PAoTDM for Flexi BSC with transport media converter feature supports reuse of existing TDM lines for SBTS transmission purposes with Flexi BSC (and BSC3i 1000/2000) when SBTS is used on GSM dedicated mode. This feature enables the operator to: • •
g
configure upper limit for M-plane traffic bandwidth to be used on Abis interface. define the limit onto SBTS. Note: SBTS management plane traffic remains as uncrypted and is directly routed from transport media converter to NetAct.
Figure 52
The SR001244 feature data flow architecture
NetAct
SBTS
Packet Abis overEthernet
Packet Abisover TDM
TRSmedia converter
FlexiBSC
SBTS
4.28.1.4
System impact Interdependencies between features The following features are related to this feature: •
SR001027: SBTS PAoTDM for GSM dedicated mode with mcBSC
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity
Issue: 01E
DN09218825
287
Descriptions of operability features
SRAN 16.2, Feature Descriptions
This feature has no impact on system performance or capacity.
4.28.1.5
SR001244: SBTS PAoTDM for Flexi BSC with transport media converter management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 178
Related existing parameters Full name
Abbreviated name
Managed object
Ingress traffic shaping bandwidth
ingressTrafficShapingB MPLANE andwidth
Ingress traffic shaping enabled
ingressTrafficShapingE MPLANE nabled
Commands There are no commands related to this feature.
4.28.1.6
Sales information Table 179
Sales information
BSW/ASW BSW
License control in network element SBTS
4.29 SR001027: SBTS PAoTDM for GSM dedicated mode with mcBSC 4.29.1 Description of SR001027: SBTS PAoTDM for GSM dedicated mode with mcBSC Introduction to the feature This feature introduces support of Packet Abis over TDM cable (PAoTDM) as an only transport connection for SBTS on GSM dedicated mode.
288
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.29.1.1
Descriptions of operability features
Benefits End-user benefits This feature does not affect end-user experience. Operator benefits Possibility to utilize existing Abis transport network in SRAN.
4.29.1.2
Requirements Hardware requirements This feature does not require any new or additional hardware.
4.29.1.3
Functional description Packet Abis of TDM transport connection can be used with SBTS when running SBTS in GSM dedicated mode. SBTS is running on GSM dedicated mode when the SBTS site is configured for GSM usage only. This feature consists of following main functions: • • •
Configurable upper limit for M-plane traffic bandwidth which is used on Abis interface. IPSec for M-plane traffic within PAoTDM (Packet Abis over TDM). Remote support of operator certificate management for SBTS within PAoTDM (Packet Abis over TDM).
Operator is able to configure upper limit for M-plane traffic bandwidth which is used on Abis interface. Operator defines the limit onto mcBSC site router and SBTS. The parameters are included to SBTS SCF (site configuration file) and supported by NetAct. Operator is able to configure IPSec into use for M-plane traffic within PAoTDM (Packet Abis over TDM) Certificate management is supported within PAoTDM for SBTS.
4.29.1.4
System impact Interdependencies between features The following features need to be activated before activation of the SR001027: SBTS PAoTDM for GSM dedicated mode with mcBSC feature: • •
SR000397: IPv4 based Packet Abis Transport SR000402: BTS QoS Support for Terminated and Routed Traffic
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
Issue: 01E
DN09218825
289
Descriptions of operability features
4.29.1.5
SRAN 16.2, Feature Descriptions
SR001027: SBTS PAoTDM for GSM dedicated mode with mcBSC management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters The feature introduces following new SBTS SCF parameters for shaping definitions: • •
Shaping ON/OFF: this parameter defines whether Abis O&M link shaping is used for the SBTS. Shaping bandwidth: this parameter defines bandwidth which is available for M-plane on Packet Abis traffic in the given link.
Commands There are no commands related to this feature.
4.29.1.6
Sales information Table 180
Sales information
BSW/ASW BSW
License control in network element -
4.30 SR000928: SBTS Plug and Play 4.30.1 Description of SR000928: SBTS Plug and Play Introduction to the feature SBTS Plug & Play concept enables automatic multi-technology site creation within one planning phase. Auto-detection inside RAN BTS for internal O&M connections and only one auto-connection & auto-configuration process from BTS to NetAct. This feature consist of updating the BTS from the factory SW to SBTS SW.
4.30.1.1
Benefits End-user benefits This feature does not affect end user experience.
290
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
Operator benefits Fast deployment of the new SBTS. The manual work required on the site will be minimized as well as the risk of potential typing errors.
4.30.1.2
Requirements Hardware requirements This feature does not require any new or additional hardware.
4.30.1.3
Functional description PnP (plug and play) process is started with the factory default software installed in the System Modules. At the end of the PnP process, the BTS includes the SBTS SW installed and is registered as SBTS in the network. Preparation for SBTS Plug and Play The Preparation includes the virtual SBTS generation with SCF validation besides others like: • • • • • •
SBTS target SW build retrieval from NOLS and storage in NetAct SWM repository. Plan preparation. Plan optimization. Preparation of SBTS identification data (used by PnP server as soon as the node element connects). Virtual SBTS creation. Plan provisioning and validation with virtual SBTS.
SBTS Plug and Play includes several functions: Status indication: There is a autoconnection status indication available in Web UI through the PnP process to inform the user about ongoing actions and their progress. PnP service functionality: In flat O&M architecture the PnP functionality is supported by NetAct. PnP functionality is, for example, the Identification Server. The other important functionality is the SW download support which is needed for downloading the target SBTS SW into the BTS, this is done for initial SW over the BTS O&M interface but later on after the SBTS SW is installed, over the NE3S interface. Auto-connection: Auto-connection including physical interface determination, DHCP communication, VLAN scanning, operator certificate retrieval and secure interface setup are supported by the FDSW for SBTS. Auto-connection functionality is utilizing DHCP. The response from DHCP server provides the parameters to set up a connection to NetAct for CA server, VPN Gateway and PnP server. Auto-configuration: Once the SBTS is registered to the PnP service, the SBTS target SW is downloaded on top of factory default software over the BTS O&M interface and is installed. SBTS target SW, after activated by restart, downloads the configuration file (SCF) including
Issue: 01E
DN09218825
291
Descriptions of operability features
SRAN 16.2, Feature Descriptions
configurations for target RAT/RATs. After that SBTS establishes M-plane connection (like other external connections) based on the stored configuration. NetAct supports SBTS auto-configuration, configuration of BTS identification data as well as pre-configuration of (virtual) SBTS SiteOAM instance with final configuration. Configuration is validated before installation. PnP without DHCP server functionality: PnP process supports manual input for the auto-connection parameters through BTS Site Manager. In case there is no DHCP server available in the network, the transport configuration can be commissioned with the minimum set of parameters. This forces the site installer to enter only these auto connection relevant IP addresses and parameters with the BTS Site Manager. Afterward the BTS connects automatically to to PnP server for identification and for auto configuration with target software for auto configuration. The actual auto-configuration work flow is not impacted. Mandatory configurable parameters are: • • • •
IP address of the eNB / M-Plane subnet mask of the eNB / M-Plane gateway for eNB / M-Plane IP address of the identification Server
Optional configurable parameters are public key infrastructure set parameters: • • • •
IP address of the Certificate Authority (CA) Server (mandatory for public key infrastructure set) port number of CA server (mandatory for public key infrastructure set) subject name for CA server (mandatory for public key infrastructure set) CMP Directory (URL) on CA Server (mandatory for public key infrastructure set, if the IP address of the CA Server is configured and the default directory for HTTP access is different from: "http: //IP@:port/pkix/".
IPsec parameter: IP address of Security Gateway (if configured, the eNB will execute PnP within an IPsec tunnel). PnP Ethernet VLAN parameter: VLAN-ID (VLAN ID will be used by the eNB to connect to the access network for auto-configuration. If not given the eNB will use un-tagged Ethernet frames).
g
Note: The usage of TLS for PnP is not directly configurable. If the PKI set is found configured and operator certificate enrollment was possible the eNB would try to set up a secure TLS connection to the OAM system in probing mode. If the secure set-up fails the eNB will try to setup M-plane connection to OAM system in unsecured mode. Plug and Play Report: While auto-connection and auto-configuration is in progress, important events and status which are required to analyze problems are logged within the PnP report, the PnP report isn't a dedicated file but it is stored and can be uploaded to BTSSM as part of snapshot. The report file contains: • • •
292
all steps of workflow with result, status and results of workflow sub-steps, setup of connection to PKI (if used),
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
• • • •
4.30.1.4
Descriptions of operability features
messages (essential parts) sent and received to/from PKI like Initial request and result (if used), setup of connection to NetAct cluster providing PnP server functionality, messages sent and received to/from the server like connection established indication with response, identification information and all parameters received from Web UI (if any).
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.30.1.5
SR000928: SBTS Plug and Play management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms and faults There are no alarms and faults related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
4.30.1.6
Sales information Table 181
Issue: 01E
Sales information
BSW/ASW
License control in network element
ASW
NetAct LK
License control attributes ON/OFF
DN09218825
293
Descriptions of operability features
SRAN 16.2, Feature Descriptions
4.31 SR001000: SBTS RF Sharing RTU 4.31.1 Description of SR001000: SBTS RF Sharing RTU Introduction to the feature SR001000: SBTS RF Sharing RTU feature introduces the RF Sharing HW activation license, which allows one RF module to be shared by two radio technologies. One common license is introduced by using SRAN's licensing framework (SR000794: SBTS SW License Management) and is applicable for every RF Sharing scenario (GSMWCDMA, GSM-LTE, WCDMA-LTE).
4.31.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • • • •
4.31.1.2
usage of a common hardware for multiple technologies one common license simplification of operational tasks minimized effort in maintaining license management
Requirements Hardware requirements This feature requires no new or additional hardware. Other requirements SBTS is connected to NetAct
4.31.1.3
Functional description This section presents the functional description of the SR001000: SBTS RF Sharing RTU feature. Functional overview RF Sharing allows sharing of different technologies using shared radio modules. Up to 2RAT configurations are possible. The SBTS RF Sharing RTU feature introduces the Radio Sharing SW license by using the SRAN's licensing framework - SR000794: SBTS SW License Management. • • •
294
GSM/WCDMA - 1 license GSM/LTE - 1 license WCDMA/LTE - 1 license
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
A new parameter Number of radio sharing (numberOfRadioSharing), which counts the number of RATs shared within each radio and sums up for all radios is introduced. Number of radio modules shared between the RATs is shown in the Number of radio sharing (numberOfRadioSharing) parameter. The value for one radio module is: • • •
GSM/WCDMA RF Sharing: "1" GSM/LTE RF Sharing: "1" WCDMA/LTE RF Sharing: "1"
If Radio Sharing is not configured, the value for Number of radio sharing (numberOfRadioSharing) is set to “0”. The parameter is updated based on SCF. This parameter is then visible in NetAct database and SWEM checks the activation parameter and compares it periodically with SW license keys available via CLS. If SW license keys are unavailable after trial period, SWEM generates a new SCF for limiting the SBTS. Example SBTS configurations has: • • • •
one radio module shared between GSM and WCDMA two radio modules shared between GSM and LTE two radio modules shared between WCDMA and LTE three radio modules dedicated for LTE
Value of Number of radio sharing (numberOfRadioSharing) parameter is 1+2+2+0=5. It mean this configuration requires 5 SBTS RF Sharing RTU licenses. Reconfiguring RF Sharing Permitted that there are enough granted licenses, users are allowed to use Radio Sharing and SBTS without restrictions. Secure digital media is used to share the right-touse credentials of Radio Sharing function that is granted in the network level by NetAct automatically. No alarms are generated if enough SW license keys for Radio Sharing in the CLS are available.
4.31.1.4
System impact This section describes the impact the SR001000: SBTS RF Sharing RTU feature has on the system. Interdependencies between features The SR000794: SBTS SW License Management feature is a prerequisite for using this feature. Impact on interfaces This feature has no impact on interfaces. Impact on network management tools This feature has no impact on network management tools.
Issue: 01E
DN09218825
295
Descriptions of operability features
SRAN 16.2, Feature Descriptions
Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.31.1.5
SR001000 - SBTS RF Sharing RTU management data This section describes the Management data related to the SR001000: SBTS RF Sharing RTU feature. For information on alarm, counter, key performance indicators, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 182
New parameters Full name
Abbreviated name
Number of radio sharing
4.31.1.6
numberOfRadioSharing
Managed object CAPCFG
Sales information Table 183
Sales information BSW/ASW
ASW
License control in network element Pool license
4.32 SR000907: SBTS Security for Local Management Ports 4.32.1 Description of SR000907: SBTS Security for Local Management Ports Introduction to the feature This feature provides protection of SBTS Local Management Ethernet ports against Layer 2 vulnerabilities.
4.32.1.1
Benefits End-user benefits
296
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
This feature does not affect the end-user experience. Operator benefits This feature provides protection from dangers such as the unauthorized access of intruders connecting to SBTS via local management Ethernet ports.
4.32.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.32.1.3
Functional description Feature SR000907: Security for Local Management Ethernet Ports provides protection from: • •
intercepting internal traffic on external ports attacks such as address resolution protocol (ARP) poisoning to reroute traffic via external ports and back to the rightful recipient
SBTS internal traffic and traffic from/to local management ports available on the SBTS are strictly separated by enabling the SR000907: Security for Local Management Ethernet Ports feature. Internal services are therefore not visible on the management port. The feature can be disabled to allow access to usually locked internal destinations for troubleshooting and diagnosis purposes. The feature is enabled by default. Configuration can be done from NetAct or with the Web UI. Figure 53
SBTS Security for Local Management Ports
WebUl
OAM REST
Issue: 01E
LMP Eth
DN09218825
297
Descriptions of operability features
4.32.1.4
SRAN 16.2, Feature Descriptions
System impact Interdependencies between features This information is to be provided in a further delivery. Impact on interfaces This information is to be provided in a further delivery. Impact on network and network element management tools This information is to be provided in a further delivery. Impact on system performance and capacity This information is to be provided in a further delivery.
4.32.1.5
SR000907: SBTS Security for Local Management Ports management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 184: New parameters lists parameters introduced with this feature. Table 184
New parameters
Full name
Abbreviated name
Ethernet port security enabled
4.32.1.6
SECADM
Sales information Table 185
298
ethernetPortSecurityEnabled
Managed object
Sales information
BSW/ASW
License control in network element
BSW
-
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
4.33 SR000913: SBTS Signed SW 4.33.1 Description of SR000913: SBTS Signed SW Introduction to the feature This feature implements software signature checking using strong cryptographic signed hashes for the contents of each SBTS software release. The hashes are generated at software creation time inside Nokia, and code on the SBTS verifies these signatures when software is being installed. These signature checks provide a strong level of confidence that the software to be installed has not been damaged or tampered with since being released by Nokia.
4.33.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides enhanced risk management because software deliveries cannot be faked or modified after leaving the Nokia software production environment.
4.33.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.33.1.3
Functional description This feature fulfils the 3GPP Security Architecture recommendation TR 33.401 that only authorized software is used and the confidentiality of software transfer to the SBTS is assured. The integrity of a software delivery is ensured in the following sequence: 1. All individual software delivery files forming a certain SRAN release are cryptographically hashed. 2. All hash values are copied into a hash container file. 3. A final hash of the hash container file is calculated in a hash container signature file. 4. The hash container signature file is given as a file digest to the Nokia SWIP (Software Integrity Protection service) which creates and signs a unique and genuine Nokia X.509 software certificate for that software release. 5. The software files, the hash container file, hash container signature file and software certificate are offered for download by operators into their software repositories (all listed within the TargetBD XML file) for further deployment to the SBTS.
g
Note: The software certificate is authorized and authenticated by the Nokia software signing certificate authority trust chain. Software verification by SBTS
Issue: 01E
DN09218825
299
Descriptions of operability features
SRAN 16.2, Feature Descriptions
An SBTS that supports software signing verification is able to download both signed and unsigned software deliveries. For signed software the SBTS downloads the additional files specified in the TargetDB XML that are needed for software signing verification. The SBTS starts the software verification sequence: 1. 2. 3. 4. 5.
SBTS verifies if the software certificate is valid and signed by the Nokia trust chain. SBTS verifies if the hash container file integrity is not corrupted. SBTS downloads all needed software files. SBTS calculates hash values for all individual software delivery files. SBTS verifies if the individual hash values match with the counterpart hash value contained within the hash container file. This ensures that no integrity violation occurred for any files.
If all checks are passed, the new software is accepted and stored into the passive file system ready for activation. In case the software certificate validation fails or any integrity violations are found, all the newly downloaded software files are deleted. A RUEM log file entry is added and an alarm is sent to NetAct. In the case that unsigned software deliveries are downloaded, this information is also logged as a RUEM entry. Figure 54
Nokia Software authentication process
NokiaSWproductionenvironment
NokiaCA certificate
NokiaSW SingingService
SWBuild certificate
SW SWBuildServer
SBTS Integrity?
Certificate?
SW
SWBuild certificate
Certificate
SW
StoreSW infilesystem
Nokia Software Signing Trust chain provision and update
300
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
The Nokia signing trust chain - the Nokia Factory CA certificate and the Nokia Root CA certificate - is part of each signed software delivery, including the associated hash container file, hash container signature file and software certificate. If the Nokia software Signing CA and/or the Nokia Root CA certificate needs to be updated due to any reason, the new certificate files must be delivered within a SRAN software release signed by the current/old valid trust chain, to ensure the authorized update path. When the associated software release is activated, the new certificates are ready for use with the next software delivery.
4.33.1.4
System impact Interdependencies between features This feature requires the following feature: •
SR000909: SBTS Trusted Boot
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.33.1.5
SR000913: SBTS Signed SW management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
Issue: 01E
DN09218825
301
Descriptions of operability features
4.33.1.6
SRAN 16.2, Feature Descriptions
Sales information Table 186
Sales information
BSW/ASW
License control in network element
BSW
-
4.34 SR000902: SBTS sRIO Link Layer Security 4.34.1 Description of SR000902: SBTS sRIO Link Layer Security Introduction to the feature The SRAN system uses Serial Rapid I/O (sRIO) ports to communicate with other modules. The SR000902: SBTS sRIO Link Layer Security feature provides authentication and encryption for the sRIO bus between SRAN modules.
4.34.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits Enhanced risk management is achieved because of improved SBTS software and hardware security.
4.34.1.2
Requirements Hardware requirements This feature is compatible with the following hardware units: • • •
4.34.1.3
FSMF FBBA FBBC
Functional description In SRAN (FSM-r3) hardware architecture, outdoor modules like FSMF and FSMG provide Serial Rapid I/O ports (sRIO) on the front panel, which can be used to connect extension boards to the system module or for communication between control modules. Indoor system modules like FSIF and FSIG provide sRIO interface on the backplane for the same purpose. To protect these interfaces, module authentication and link layer encryption is provided. Local Link Layer Security (LLsec) setup procedure The sRIO ports are open and the filter function is active when they are unconnected. When a new module is connected through the sRIO port to an already operating Flexi System Module, a discovery process starts for the sRIO address assignment. Once
302
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
assigned, the mutual authentication of both modules follows, including the key agreement. Communication between the modules only begins once the modules are authenticated successfully and the confidentiality protection on the link layer is enabled. In case the connection is lost (for example, due to an unplugged cable) the whole setup procedure is performed again to re-establish the connection.
g
Note: The SR000902: SBTS sRIO Link Layer Security provides protection only for Serial Rapid I/O ports. The link layer security is allocated between the sRIO transport layer and the sRIO physical layer. The sRIO transport layer adds the relevant header information to the payload. The payload and the sRIO transport header are confidentially protected. Figure 55
Communication between secure environments
FSMF/FSIH+FBBxextensionmodule Certificate
sRIO sRIO
Certificate sRIOFrontpatchcable: Transmissionsecuredby AES-128ciphering Certificate
sRIO
FSMF/FSIHforcapacityextension Certificate
NokiaNetworksVendor/Module x.509certificate
The link layer algorithm is AES128-CTR, compliant to 3GPP for air-link encryption. The AES algorithm is implemented inside the sRIO chip hardware. It is used only for SRAN internal transport security purposes (communication between secure environments).
4.34.1.4
System impact Interdependencies between features This feature depends on the following feature: •
SR000846: SBTS Vendor Certificate Management
Impact on interfaces
Issue: 01E
DN09218825
303
Descriptions of operability features
SRAN 16.2, Feature Descriptions
On the interfaces which use sRIO, SR000902: SBTS sRIO Link Layer Security provides mutual authentication, key agreement and encryption between SRAN modules. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.34.1.5
SR000902: SBTS sRIO Link Layer Security management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 187: New alarms lists alarms introduced with this feature. Table 187
New alarms
Alarm ID
Alarm name
7650
BASE STATION FAULTY
7651
BASE STATION OPERATION DEGRADED
7652
BASE STATION NOTIFICATION
7653
CELL FAULTY
7654
CELL OPERATION DEGRADED
BTS faults and reported alarms Table 188: New BTS faults lists BTS faults introduced with this feature. Table 188
Fault ID 10
New BTS faults
Fault name No connection to unit
Reported alarms 7650 BASE STATION FAULTY 7651 BASE STATION OPERATION DEGRADED 7652 BASE STATION NOTIFICATION 7653 CELL FAULTY 7654 CELL OPERATION DEGRADED
Measurements and counters There are no measurements or counters related to this feature.
304
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
4.34.1.6
Sales information Table 189
Sales information
BSW/ASW
License control in network element
BSW
-
4.35 SR000794: SBTS SW License Management 4.35.1 Description of SR000794: SBTS SW License Management Introduction to the feature This feature introduces the mechanism for SRAN BTS's SW license management. All licensed features as Capacity Units, STD (standard) features, HVF (High Value Features) and HWA (HW Activation) can be controlled. This feature brings smooth introduction of the licensing mechanism in Single RAN.
4.35.1.1
Benefits End-user benefits This feature does not affect end user experience. Operator benefits Licensing operations are running smoothly in the background. License Management for SRAN is providing a central view and compared to current mechanism is reducing operational effort.
4.35.1.2
Requirements Hardware requirements The new license mechanism is based on NetAct. For standard NetAct installation no additional hardware is needed.
4.35.1.3
Functional description Licensing in SRAN16.2 SRAN 16.2 introduces a new way of handling SW licenses. SBTS SW LK (license keys) are introduced. SW LK are generated from by CLS (Centralized License Server).
Issue: 01E
DN09218825
305
Descriptions of operability features
SRAN 16.2, Feature Descriptions
For SRAN, the new licensing mechanism only applies to SBTS. The licenses are kept in CLS/SWEM. License mechanism as existing for current network elements (RNC, BSC, WBTS, NetAct, OSS) are not changed. SRAN 16.2 license mechanism introduces a network wide pool concept with the use of CLS (Centralized License Server). License pools are no longer split into NetAct clusters. There is one CLS per customer network. In addition, SW license keys will not be physically installed at the SBTS, but kept in the CLS. In case of a missing SW license capacity, an alarm is generated in NetAct to indicate missing license capacity. Figure 56
SRAN 16.2 licensing mechanism principles concept NetActRC# PM SWEM
SBTSs
CM SWLKbasedRTU protectioninCLS
CentralizedSW LicenseServer NetActRC# PM CLS
SWEM
SBTSs
CM
SWLKs
Pools NetActRC# PM SWEM
SBTSs
CM
CLS is connected to the existing NetAct clusters. Each NetAct is running a SWEM (SW Entitlement Manager). SWEM periodically checks the configuration data and it is interworking with CLS to verify, if sufficient SW license capacity is available. In case of missing SW license capacity, OSS SWEM is generating an alarm to indicate missing license capacity. Centralized License Server (CLS) CLS is a centralized application that provides a central control point for sharing Nokia standard license key protected software assets. The CLS provides the following benefits: • •
• •
Complete centralized network management. Network level pooling. (Pooling means that license capacity is allocated from the pool and assigned to the SBTS. But once assigned to the SBTS it is tied to the SBTS and can’t be redistributed.) Automatic network pools. Only one target ID per customer.
CLS introduces the following license management enchancements: •
306
Flexibility for capacity allocation.
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
• • • •
Descriptions of operability features
Uniform, simplified, and user-friendly license management from both operator and Nokia perspectives. Full network view. Full scalability (from small to big networks and the other way around). Fast interfacing (connecting) of new types of network elements.
NetAct Software Entitlement Manager (SWEM) The SWEM is a module of NetAct SWAM application that collects and processes the configuration and measurement data based on customer specific settings. Monitoring data consists of configuration management (CM) parameters. Monitoring modules are product specific elements, which allow an incorporation of specific reporting methods. Monitoring modules particular for each network technology. CLS and SWEM are for software asset monitoring purposes, and allows the following: • •
Periodic checking of functionality used in customer networks. Request licenses from the CLS, based on data received from monitoring modules for particular network technology: –
• • •
4.35.1.4
If not enough licenses are available in the CLS, SWEM will initiate dedicated license missing alarms.
Viewing and exporting monitoring reports. Setting notifications and alarms thresholds. Presenting the license management data in user friendly form.
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.35.1.5
SR000794: SBTS SW License Management management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 190: New alarms lists alarms introduced with this feature.
Issue: 01E
DN09218825
307
Descriptions of operability features
Table 190
SRAN 16.2, Feature Descriptions
New alarms Alarm ID
Alarm name
41003
LICENSE CAPACITY NOT AVAILABLE
Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Commands There are no commands related to this feature.
4.35.1.6
Sales information Table 191
Sales information
BSW/ASW BSW
License control in network element -
4.36 SR000912: SBTS SW Management 4.36.1 Description of SR000912: SBTS SW Management Introduction to the feature The SR000912: SBTS SW Management feature introduces SBTS software management controlled by NetAct and SBTS Web UI. The SBTS software package supplies mandatory software including technology specific components required by the SBTS.
4.36.1.1
Benefits End-user benefits This feature does not affect end user experience. Operator benefits SBTS has a single software delivery that provides the specific software for all three technologies eliminating the need of complex software comparability checks for BTS. SW management actions can be performed with NetAct SW Manager and Web UI.
4.36.1.2
Requirements Hardware requirements This feature does not require any new or additional hardware.
308
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.36.1.3
Descriptions of operability features
Functional description The SR000912: SBTS SW Management feature introduces SBTS software management controlled by the operator from NetAct and via BTS Web UI. The SBTS software package supplies mandatory software including technology specific components required by the SBTS. Only the software components that require updating are downloaded to the SBTS, which reduces time taken to update SBTS SW. SBTS supports automatic fallback to previously installed SW version in case of SW related problems. Figure 57
SRAN 16.2 architecture concept
Pre-integrationuseonly Configurator
SBTS Adapter PnP service
NES3 Mediation
FSMF
SiteOAM
SiteOAM
WebUI
NodeOAM WCDMA
LTE
GSM
Software management operations available from NetAct are: • • • • •
• • •
•
Issue: 01E
SBTS SW download and activation. SBTS SW upload. Up to 250 simultaneous SW management operations. Support for scheduled SW management operations. Possibility to abort SW management operations. Any scheduled operation can be canceled at NetAct before the request is sent to the SBTS. If a request has been sent to the SBTS, only in progress SW download can be aborted. The SBTS will reject a cancel request for an in-progress activation, upload and other similar operations Possibility to monitor SW management operations, progress indication in NetAct SW manager. SW build information and the date of last upgrade/update available in NetAct SW Manager. SW build information available in Configuration Manager (current active SBTS version, date and time it was activated and the corresponding LTE, WCDMA and GSM RAT SW versions that are running on the SBTS). SBTS SW Rollback.
DN09218825
309
Descriptions of operability features
SRAN 16.2, Feature Descriptions
SW management operations available from SBTS Web UI are: • • • • • •
4.36.1.4
SBTS analysis, to ensure that actual upgrade/update procedure can be run successfully. SBTS SW upgrade/update Possibility to monitor SW management operations. Verification if SW upgrade/update has been completed successfully. SW build information and the date of last upgrade/update available in Web UI. SBTS SW Rollback.
System impact Interdependencies between features The following security features are related to the SR000912: SBTS SW Management feature: • •
SR000909: SBTS Trusted Boot. SBTS modules provide a secured bootstrap. Only the integrity checked code is allowed to go into the service. SR000913: SBTS Signed SW. The origin source and integrity of SBTS SW is guaranteed by the authorized Nokia trust chain SW certification. The SBTS checks if the certified SW deliveries are genuine before allowing it to go into service.
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity when the number of users does not exceed the licensed maximum.
4.36.1.5
SR000912: SBTS SW Management management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators introduced with this feature. Parameters The following table lists parameters related to this feature.
310
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Table 192
Descriptions of operability features
New parameters Full name
Abbreviated name
Managed object
Active GSM RAT software version
activeGSMRATSWVersion
SBTS
Active LTE RAT software version
activeLTERATSWVersion
SBTS
Active WCDMA RAT software version
activeWCDMARATSWVersion
SBTS
Commands There are no commands related to this feature.
4.36.1.6
Sales information Table 193
Sales information
BSW/ASW ASW
License control in network element NetAct LK
4.37 SR000938: SBTS SW upgrade/update 4.37.1 Description of SR000938: SBTS SW upgrade/update Introduction to the feature This feature introduces the SW upgrade and update of SBTS support feature via Web UI and from NetAct.
4.37.1.1
Benefits End-user benefits This feature does not affect end user experience. Operator benefits • • • • •
4.37.1.2
Ability to activate new SW functionalities to network. Single SW upgrade operation including SW components for all technologies in the SBTS. Less errors during operation due to hidden complexity within the SBTS Maintaining the network quality by ensuring consistency of the SBTS SW configuration Ensuring the consistency of the SW and operation execution within the SBTS
Requirements Hardware requirements
Issue: 01E
DN09218825
311
Descriptions of operability features
SRAN 16.2, Feature Descriptions
This feature does not require any new or additional hardware.
4.37.1.3
Functional description SRAN SW upgrade order is from top to down: 1. 2. 3. 4.
NetAct, WCDMA OMSs (OMS is required for RNC), Controllers (RNCs/BSCs), SBTSs.
SBTS SW upgrade/update can be done via NetAct or BTS WebUI. NetAct provides SBTS SW upgrade/update for several SBTSs in the same time. The BTS WebUI provides SBTS SW upgrade/update for single SBTS. In SW upgrade SBTS SW packet includes all needed new SW components for SBTS SW release. All SBTS software including RATs SW, O&M SW, TRS SW, Platform SW, BTS WebUI SW are upgraded via the common software management operations triggered from NetAct or the BTS WebUI.
4.37.1.4
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity when the number of users does not exceed the licensed maximum.
4.37.1.5
SR000938: SBTS SW upgrade/update management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
312
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
Commands There are no commands related to this feature.
4.37.1.6
Sales information Table 194
Sales information
BSW/ASW BSW
License control in network element -
4.38 SR000909: SBTS Trusted Boot 4.38.1 Description of SR000909: SBTS Trusted Boot Introduction to the feature This feature enables the secure boot feature of the SBTS hardware and verifies the integrity of the system software to prevent unauthorized modification.
4.38.1.1
Benefits End-user benefit This feature does not affect the end-user experience. Operator benefits This feature provides higher security for base stations, reducing the risk that a sophisticated attacker might install malicious software on the device.
4.38.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.38.1.3
Functional description The Trusted Boot Agent enforces the verification and execution of trusted software in a predefined sequential order. It ensures that modified code is refused by verifying the digest of the boot image and application software with cryptographic techniques that use trusted certificates held in hardware-locked memory. Boot-up phase At the boot-up phase, the Agent examines the software in the following order: 1. boot loader 2. operating system 3. application software
Issue: 01E
DN09218825
313
Descriptions of operability features
SRAN 16.2, Feature Descriptions
Each part of the software must be successfully verified before executing and proceeding to the next step. If software verification fails, the alternative software copy (if present) is verified and if successful, the boot-up continues. If the verification of both the primary and alternative software fails, the boot-up process stops and an on-site visit is necessary. Figure 58
Trusted Boot Agent order of boot execution Writtenand sealedduring manufacturing
Device keys
Digests Fall-back Bootloader
nok
BootLoader ok
Trusted Boot Agent
Digests Fall-back LinuxKernel
nok
Linux
SWintegrity corrupted?
ok
Digests
Alarm NetAct
nok
Application SW
Software update and activation Before the software update, the software update packages are downloaded through a secure channel, stored securely in the network element, and then installed and activated. If the software is not activated directly after it has been downloaded, the steps described in the boot-up phase are to be followed. If the verification of the new software fails, the system module tries to load the previously-used software. If the software download fails or the signature of the software cannot be verified, an alarm is raised and the system module continues the boot-up process with the previously- used software. Failures are logged, and if online connectivity is available, a security alarm is raised to the network management system. Reset button Depending on the length of time the reset button on the system module is pressed, the following occurs: •
•
314
The reset button is pressed for less than five seconds. Normal boot-up is performed. There is no impact on operator secrets such as private keys and certificates, nor on configuration of the network element. The reset button is pressed for more than five seconds. In this case, a “configuration reset” is performed. The configuration is set to the backup directory and some configuration files are deleted. There is no impact on operator secrets. The certificates are valid and remain valid at the next boot-up.
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.38.1.4
Descriptions of operability features
System impact Interdependencies between features This feature requires the following feature: •
SR000846: SBTS Vendor Certificate Management
This feature is a prerequisite for the following feature: •
SR000913: SBTS Signed SW
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.38.1.5
SR000909: SBTS Trusted Boot management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms Table 195: New alarms lists alarms introduced with this feature. Table 195
New alarms
Alarm ID 7106
Alarm name SINGLE RAN BASE STATION PROBLEM
Faults Table 196: New faults lists faults and reported alarms introduced with this feature. Table 196
Fault ID 29, 30
New faults
Fault name BTS SW download or activation failed
Reported alarms 7106 SINGLE RAN BASE STATION PROBLEM
Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature.
Issue: 01E
DN09218825
315
Descriptions of operability features
SRAN 16.2, Feature Descriptions
Parameters There are no parameters related to this feature.
4.38.1.6
Sales information Table 197
Sales information
BSW/ASW
License control in network element
BSW
-
4.39 SR000903: SBTS User Event Logging 4.39.1 Description of SR000903: SBTS User Event Logging Introduction to the feature This feature provides the mechanism to log requests on SBTS which are initiated by the operator using the Web UI. The following events are logged: • •
the requests with impact on SBTS configuration or service the requests that retrieve confidential information from SBTS
Other informative requests are not logged. The users' Secure Shell (SSH) login and logout events on SBTS are logged. Logs include detailed information of the request, such as event time, user name, client IP address, operation type, parameter name or parameter value.
4.39.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature enables the operator to audit configuration changes done on SBTS Web UI with enhanced details like parameter name and value. Erroneous configurations can be identified much faster thus limiting network problems or even network outages.
4.39.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
316
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.39.1.3
Descriptions of operability features
Functional description This feature introduces the mechanism to log Remote User Events on SBTS and upload the logs to NetAct. The logs are called Audit Trail logs. They provide security-relevant chronological evidence of events affecting the SBTS, and thus are useful for the operator for fault analysis. The Audit Trail application, previously used in LTE and WCDMA networks, is split into two functionalities: •
•
Security Log North Bound Interface (SLNBI) The collection, scheduling and forwarding functionality has been moved into NetAct. This is exposed as the SLNBI and it is planned as a part of NetAct16.2 P8 release onwards. SLNBI collects Audit Trail logs from all SBTSs. SLNBI then forwards the logs over the syslog protocol to any SIEM system. Security Information and Event Management (SIEM) system This is the log management application which is a 3rd party Original Equipment Manufacturer (OEM) product. It can process syslog protocol from the SLNBI.
The Audit Trail logs from SBTS are uploaded to NetAct because each SBTS is connected to NetAct. In Single RAN, Remote User Events are the operator’s requests issued through the Web UI or SSH session to SBTS. The operator request is logged only if it impacts SBTS configuration or service or retrieves confidential information from SBTS. The operator request is not logged if it only queries status or non-confidential information from SBTS. This feature creates Audit Trail logs for the operator’s login and logout to SBTS over an SSH session. Audit Trail logging of commands issued in an SSH session is covered by the feature SR000906: SBTS Nokia Service Account Management. The SBTS does not create Audit Trail logs for the operator requests received from NetAct. NetAct keeps internal records of those requests. The records are available to the operator on SIEM system. Audit Trail logs contain detailed information of the operator requests, including the following: • • • • •
who initiated the request (the username) when the request was received (a timestamp with time zone specified) where the request was issued (the source IP address of the request) purpose of the request (name of the operation, target object, parameters and parameter values) status of the request (success or failure, if applicable)
Confidential information in the logs is hidden. This includes, but is not limited to password, certificate reference number, pre-shared keys and private keys. The SBTS has common objects for different radio technologies, but it also has objects specific for one radio technology. It is assumed that radio technology specific objects have unique names. Based on the target object, the user can identify the impacted radio technology of the request in the Audit Trial log. The SBTS internally maintains a log buffer for Audit Trial logs. The buffer is preserved during reset and software update.
Issue: 01E
DN09218825
317
Descriptions of operability features
SRAN 16.2, Feature Descriptions
NetAct SLNBI automatically schedules upload of Audit trial logs from SBTS. SBTS uploads requested logs after receiving upload request from NetAct SLNBI and also initiates upload of an Audit Trail Log when the log is created for an legible user event. If the NetAct connection is down, the buffer can become full. If new logs are created, SBTS can overwrite the oldest logs in the buffer with the new ones. When not uploaded logs are overwritten, a log is created in the buffer to report that event to the operator.
g
4.39.1.4
Note: When the SBTS initiates Audit Trial Log upload, Audit Trial/SLNBI ignores this request, and the Audit Trial Logs are not available in NetAct 16.2 or in earlier releases. Only Audit Trial Logs that are uploaded by NetAct initiated uploads are accepted by Audit Trial/SLNBI.
System impact Interdependencies between features This feature requires the following features: • • •
SR000713: SBTS Web UI SR000906 SBTS Nokia Service Account Management SR000921: SBTS NE3S/WS NetAct Integration
Impact on interfaces The upload of Audit Trail logs can be triggered from NetAct or from SBTS according to "NE3S/Web Service Audit Trail Interface Specification". Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.39.1.5
SR000903: SBTS User Event Logging management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults or reported alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
318
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.39.1.6
Descriptions of operability features
Sales information Table 198
Sales information
BSW/ASW
License control in network element
ASW
NetAct LK
4.40 SR000846: SBTS Vendor Certificate Management 4.40.1 Description of SR000846: SBTS Vendor Certificate Management Introduction to the feature This feature introduces the Nokia vendor certificate which is given to SBTS supported hardware modules during the manufacturing process. The vendor certificate is used to prove the SBTS is a genuine Nokia product and for internal authentication between modules for sRIO Local Link Layer Security or MACsec.
4.40.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits for the operator: • • • •
4.40.1.2
BTSs are given unique, cryptographically protected identities at the manufacturing phase. Nokia vendor certificate authenticates a Nokia SBTS and allows the operator to set up a 3GPP compliant public key infrastructure (PKI) solution. The operator PKI can automatically enroll an X.509 operator certificate. Site visit by our experts during installation of new network elements is not needed.
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.40.1.3
Functional description The manufacturing process of a BTS is extended by the introduction of a Nokia Factory Certification Authority (Factory-CA), and Factory Registration Authority (Factory-RA) which create and sign a vendor certificate for each individual BTS. During BTS system module assembly, private and public key pairs are created. The vendor certificate and the keys are tied to the network element’s serial number.
Issue: 01E
DN09218825
319
Descriptions of operability features
SRAN 16.2, Feature Descriptions
The factories' Production Testing Software (PTS) stores the Nokia vendor certificate, associated RSA key pair, Factory CA certificate, and Nokia Root CA certificate within its protected memory and file system at defined locations. When a customer receives a shipment of new network elements, a list of these elements’ serial numbers is delivered to the customer’s identity management server. Figure 59
SBTS certificates
NokiaFactories
Certificate
Certificate
SBST
NokiaRootCA certificate
Certificate management
Certificate
sRIOLocalLink LayerSecurity
FactoryCA certificate
Certificate MACsec
Certificate
Vendorcertificate formodule
Certificate
....
The network element is authenticated during the first installation at the customer's site. The new identity is automatically verified by the identity management server. The network element is only allowed to connect when its serial number is present in the previously delivered serial number list. Identity management server replaces the preinstalled factory certificate with the one issued by the customer. During the initial start-up of the SBTS hardware, the vendor certificate security credentials are provided to SBTS applications. These applications use the vendor certificate or RSA keys for: •
g
internal authentication of Ethernet peers for MACsec between module Note: This function is not currently supported by SBTS, and is only reserved for future capabilities using the same installed Nokia vendor certificate or module certificate.
•
•
automated X.509 operator certificate enrollment according to 3GPP The X.509 operator certificate enables public key certification based authentication and authorization in operator access networks and management networks. internal authentication of sRIO peers for Local Link Layer Security between modules
This process must be performed in a way which does not corrupt originally stored credentials. Original credentials are needed for example, during migration to other RAT software. Currently, two separate certificates are installed at Nokia Factory: • •
320
Nokia vendor certificate (for X.509 operator certificate enrollment) Nokia module certificate (for link layer security)
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
g 4.40.1.4
Descriptions of operability features
Note: The vendor certificate is also called module certificate if it is used to authenticate modules as peers for sRIO Local Link Layer Security or MACsec using exposed front cabling.
System impact Interdependencies between features This feature requires the feature: •
SR000713: SBTS Web UI
This feature is a prerequisite for the following features: • • •
SR000845: SBTS Operator Certificate Management SR000902: SBTS sRIO Link Layer Security SR000909: SBTS Trusted Boot
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.40.1.5
SR000846: SBTS Vendor Certificate Management management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
Issue: 01E
DN09218825
321
Descriptions of operability features
4.40.1.6
SRAN 16.2, Feature Descriptions
Sales information Table 199
Sales information
BSW/ASW
License control in network element
BSW
-
4.41 SR000713: SBTS Web UI 4.41.1 Description of SR000713: SBTS Web UI Introduction to the feature SBTS Web UI (or SBTS Element Manager) is a local SBTS management tool that uses a web browser, either on PC (recommended) or mobile device.
4.41.1.1
Benefits End-user benefits This feature does not affect end-user experience. Operator benefits The element manager application is always available with correct version. No need to install any management application on local computer.
4.41.1.2
Requirements Hardware requirements This feature does not require any new or additional hardware.
4.41.1.3
Functional description In the SBTS 16.2 software architecture a new web based user interface (UI) tool replaces the old BTS Site Manager as the element manager for the SBTS. This feature combines graphical user interface (GUI) operations performed with the user interface and information to be displayed over several features. The actions required of the network element to operate/utilize the UI are implemented within those dedicated features (for example SBTS HW Management, SBTS Configuration Management, troubleshooting features).
322
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Figure 60
Descriptions of operability features
SBTS Web UI in new architecture BTSprofile generator
SBTSSW
Planningtools RNWand TRS Plan
NetAct NetAct Applications
CNUM
LDAP query
SiteOAM SCF
NE3S
Fragment Applications (CM,SWM, FM,PM)
Configurator generator
NetActSWM
NE3S
BTSprofiles
Real-timePM
BTS
Traffica
SiteOAM REST/HTTP WebUI
LocalBTS User Accounts
WebBrowser
WebServer (Browser)
LocalLogs
BIM API N-API P-API R-API
NodeOAM RAT SWs LTE
WCDMA
GSM
BTSPlatformSW
SRAN 16 introduces a new SBTS architecture where all RAT-specific applications are executed on a single system module(s). The new O&M architecture focuses on decoupling of general management logic from embedded software by implementing layered software architecture, removing mediation (OMS) and utilizing existing interfaces. An essential change is the capability to deploy parts of the configuration management functionality outside of the BTS. The new functionality, Configuration Generator, creates BTS HW configurations (for example baseband resource allocations and routing configurations to the cell-to-antenna mapping) based on Site Configuration File (SCF) and on selected BTS Profile, which are offered by Nokia. Operators select the BTS Profiles which match the used hardware. The new architecture is data and event driven with a minimal software footprint in the embedded SBTS product. The configuration generation functionality is moved into an external server-side function, and the SBTS provides just enough data to activate and maintain the given configuration. The configuration generator downloads the configuration to SBTS OAM using Hypertext Transfer Protocol (HTTP). The SBTS Web UI accesses this information and all remaining data which is needed to manage SBTS locally via the representational state transfer (REST) API (using HTTP operations). The SiteOAM also includes the Web Server for the element manager (SBTS Web UI). A user device (PC, tablet) with a standard Web browser for launching the SBTS Web UI can be connected in one of the following ways: •
Issue: 01E
SBTS Web UI can be physically connected to an Ethernet connector in the system module of the SBTS via Ethernet cable.
DN09218825
323
Descriptions of operability features
•
SRAN 16.2, Feature Descriptions
The SBTS Web UI can be remotely connected through the O&M DCN.
Any LMP port within the SBTS needs to relay on the connection to a fixed local IP address of the Web server. Depending on the selected implementation the LMP ports in the second system module cannot be used in SRAN 16. Supported browsers: • • •
Chrome, latest available version, 32 bit version is suggested, for both Windows and Linux operating systems. Internet Explorer 11, latest available version, with latest updates installed, for Windows operating system. Firefox, latest available 32 bit version, for both Windows and Linux operating systems.
In order to use the SBTS Element Manager, the following client security criteria must be met: • • • •
Java script execution should be enabled. Cookie files should be enabled and accepted by client web browser. Third-party certificates should be set to prompt or enabled option. For best user experience – SBTS IP address should be set in trusted sites for internet options.
The Web server for the SBTS Web UI is provided within the SiteOAM part of the SBTS. In principle, this enables the usage of the Web server also in a remote SiteOAM instance, but whether this is allowed depends on the SiteOAM multiplicity decision in the remote SBTS service in NetAct – in case the SiteOAM instance is made available only for executing a specific management action, the SBTS WUI connection to remote SiteOAM can be prohibited. NetAct integrates the SBTS Web UI to NetAct for remote use. The SBTS Web UI uses the HTTP REST API interface for the communication with the connected node. The SBTS Web UI requires no software installation for the used terminal, only the standard compatible Web browser supported by SBTS Web UI is required. When connected to the Web Server in the SBTS, the browser uploads all necessary files for the SBTS Web UI from the Web Server in the SBTS. The SBTS Web UI provides the comparable views for element management and troubleshooting of a SBTS as the BTS Site Manager does for the BTS in mainstream architecture, however, the configuration validation functions are not available. The SBTS Web UI provides tools to help with the SBTS site commissioning, corresponding to the commissioning wizard used in the BTS Site Manager. The SBTS Web UI is consistent over all RATs. While the existing BTS Site Manager is no longer used for the SBTS, it is still required when new SBTS will be introduced into the network using system module having preSRAN 16 software installed. Then the legacy BTS Site Manager is used for loading the SBTS software to the SBTS for the first time (only for SW upgrade). This is required because the factory delivery software of the FSMF is based on mainstream BTS SW architecture, and does not have Web Server as its SBTS Web UI. The SBTS Web UI cannot be used with a BTS with mainstream BTS SW architecture, and vice versa. Base station info model (BIM) is a core element of the SBTS O&M architecture. It contains provisioned information, detected hardware, status of objects and basically all the information that O&M is involved with. BIM provides an interface for applications (SBTS Web UI, NodeOAM, SiteOAM) to inform when data has been changed (as well
324
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
created or deleted). The data is provided via the REST API interface. BIM holds the BTS information model, the elements, their attributes and relationships and maintains the integrity of the model. It supports network level view, physical view and resource view. Representational state transfer REST architecture is used in web services to abstract the implementation details of the service component implementation. In the SBTS 16.2 software architecture the REST API/HTTP interface is used for communication between the SBTS SiteOAM with the NodeOAM entity. The REST API is used between BTS entities regardless of the physical deployment of the SiteOAM functionality. REST API is also used between SBTS Web UI and SiteOAM. Figure 61
SBTS Element Manager example window
SBTS Element Manager is divided into following pages (tabs): •
g
Note: After blocking/unblocking a module (for the time of reset, until hardware is detected again) and its hot removal (until hardware is detected again) a module disappears from the SBTS Web UI hardware view. • • • •
4.41.1.4
Site Management, which displays SBTS software and hardware information, as well as information on active faults.
Snapshot, which is used to save and open snapshots. Parameters, which is used to view and modify configuration parameters manually. Monitoring and Tests. Certificates.
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces.
Issue: 01E
DN09218825
325
Descriptions of operability features
SRAN 16.2, Feature Descriptions
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.41.1.5
SR000713: SBTS Web UI management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms
g
Note: When displaying details on alarms, the displayed value in the Cleared field is not precise and it does not stand for the clear time of an alarm on a BTS. The value may differ from the actual clear time due to forwarding delay and processing of this information in SBTS WebUI in your browser and also on the time set on the PC itself. Consequently, the Duration field does not display a precise value as well. The correct time of clearing an alarm is displayed in NetAct. There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters The following table lists parameters introduced with this feature. Table 200
New parameters Name
Abbreviated name
Idle time Threshold for SBTS Element Manager sbtsEmSessionTimeout Session
Commands There are no commands related to this feature.
4.41.1.6
Sales information Table 201
Sales information
BSW/ASW BSW
326
License control in network element -
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
4.41.2 Troubleshooting login issues in Internet Explorer In case of security restrictions in Internet Explorer, the user might not be able to log into the SBTS Element Manager. To gain access to the SBTS Element Manager through Internet Explorer, follow the procedure below. Procedure 1
Open Internet Explorer.
2
Enter SBTS IP address in the address bar. Step example Figure 62
Entering the IP address
Step result The login page appears in the browser window.
3
Click Options ► Internet options Step example Figure 63
Issue: 01E
Internet options
DN09218825
327
Descriptions of operability features
SRAN 16.2, Feature Descriptions
Step result The Internet Options popup window appears. 4
Select Security tab. In the section Select a zone to view or change security settings choose Trusted sites option. Step example Figure 64
Trusted sites
Step result New settings collection appears.
328
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
5
Descriptions of operability features
Click Sites button. Step example Figure 65
Issue: 01E
Sites button
DN09218825
329
Descriptions of operability features
6
SRAN 16.2, Feature Descriptions
The Trusted sites pop-up window appears with the IP address of your SBTS automatically entered in the Add this website to the zone field. If there is no IP address of your SBTS, enter it manually into the field. Step example Figure 66
7
Trusted sites
Click Add button. The Add this website to the zone field might not be available due to lack of administrator privileges to change the settings. In this case contact your Windows system administrator for support.
330
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
Step example Figure 67
Adding the IP to the list
Step result The IP address of the SBTS should be added to the list Websites field. 8
Confirm new settings and close window.
9
Press Apply button in Internet Options window and click OK to close the window.
10 Restart Internet Explorer.
Result You should be able to login to the SBTS Element Manager interface.
4.42 SR000996: SRAN Clock Time Management 4.42.1 Description of SR000996: SRAN Clock Time Management Introduction to the feature
Issue: 01E
DN09218825
331
Descriptions of operability features
SRAN 16.2, Feature Descriptions
Time management for Single RAN.
4.42.1.1
Benefits End-user benefits This feature does not affect end user experience. Operator benefits Clock time distribution for the whole SRAN 16 network.
4.42.1.2
Requirements Hardware requirements This feature does not require any new or additional hardware.
4.42.1.3
Functional description Time management functionality in SRAN consist of three main aspects: 1. Clock time delivery in SRAN: • •
for BTS: GPS (if installed) or Timing over Packet (ToP): PTP / IEEE 1588v2 SNTP for: NetAct, RNC, BSC, 2G BTS, 3G BTS, 4G BTS, OMS and SBTS
2. Clock time usage in O&M data in network elements and management elements, utilizes local time in all O&M interfaces for O&M data-NetAct and all other elements continues to use their local time. 3. Clock time presentation in SBTS element manager (Web UI), NetAct and North bound interface (NBI) • •
4.42.1.4
SBTS Web UI uses SBTS local time like BTS Element Manager in WCDMA and in LTE NetAct GUI and NBI uses NetAct local time for SBTS O&M data
System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
332
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
4.42.1.5
Descriptions of operability features
SR000996: SRAN Clock Time Management management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 202: New parameters lists parameters introduced with this feature. Table 202
New parameters Full name
Abbreviated name
NTP alarming threshold
ntpAlarmingThreshold
Managed object TIME
Commands There are no commands related to this feature.
4.42.1.6
Sales information Table 203
Sales information
BSW/ASW BSW
License control in network element -
4.43 SR000899: SRAN Support of TLS 1.2 4.43.1 Description of SR000899: SRAN Support of TLS 1.2 Introduction to the feature This feature provides Transport Layer Security (TLS) support for SRAN network interfaces. TLS 1.2 support is specified by 3GPP Rel. 11.2 Annex E as the default protocol for secure management plane end-to-end communication. Fallback to earlier versions of TLS are supported for those peers and applications that do not support TLS 1.2.
4.43.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Issue: 01E
DN09218825
333
Descriptions of operability features
SRAN 16.2, Feature Descriptions
Operator benefits Enhanced risk management is achieved as a result of improved SRAN network security by protection against eavesdropping and man-in-the-middle attacks. The SBTS and NetAct are compliant to 3GPP Rel. 11.2 security recommendations and known TLS 1.0 vulnerabilities are closed.
4.43.1.2
Requirements Hardware requirements This feature requires Flexi Multiradio 10 System Module (FSMF).
4.43.1.3
Functional description This feature increases the security of SRAN O&M communications by providing encryption, integrity protection and authentication with the Transport Layer Security Protocol (TLS). TLS is a secure communication method for protecting the confidentiality and integrity of management plane communication protocols and file transfers (HTTPS, REST/TLS, WebUI/TLS, NE3S/TLS, LDAPs, Syslog/TLS). TLS is also used for server authentication. The SBTS and NetAct support the Transport Layer Security Protocol version 1.2 (TLS1.2) as specified by Annex E of TS 33.310. This feature also provides fallback capability to TLS1.1 and TLS1.0, when networking with peers or applications that do not support TLS1.2. For example, NetAct supports only TLS1.0 for LDAP. The rules outlining permitted and mandatory cipher suites in the TLS1.2 specification (RFC5246) are followed. The mandatory cipher suite of TLS1.1 (RFC4346) is also supported. In addition to the specifications, the list of available ciphers is enhanced: • •
Cipher suites with Perfect Forwarding Secrecy are supported. Cipher suites with RC4 and with NULL integrity protection (or HASH) are not supported.
For TLS1.2, CompressionMethod.null is supported, and the anonymous key exchange method is not supported. The SBTS supports TLS session time-based secure key renegotiation according to RFC5746, and is controlled by a user configurable timer in SBTS. The timer is common for all peers with the exception of NetAct, which does not support client-initiated timebased key renegotiation; connections to NetAct will not trigger renegotiation. Renegotiation can be completely disabled by setting the renegotiation timer to 0. The SBTS and NetAct use X.509 certificates to authenticate to and accept connections from peers.
4.43.1.4
System impact Interdependencies between features This feature is a prerequisite for the following features: • •
334
SR000713: SRAN Web UI SR000921: SBTS NE3S WS NetAct integration
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of operability features
This feature requires the feature: •
SR000845: SBTS Operator Certificate Management
Impact on interfaces This feature has an impact on interfaces as beneath: •
TLS1.2 is supported on all interfaces. TLS 1.0 and 1.1 are supported for peers and applications that do not support TLS 1.2
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.43.1.5
SR000899: SRAN Support of TLS 1.2 management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 204: New parameters lists parameters introduced with this feature. Table 204
New parameters
Full name
Abbreviated name
TLS renegotiation interval
4.43.1.6
MPLANE
Sales information Table 205
Issue: 01E
tlsRenegotiationInterval
Managed object
Sales information
BSW/ASW
License control in network element
BSW
-
DN09218825
335
Descriptions of BTS site solution features
SRAN 16.2, Feature Descriptions
5 Descriptions of BTS site solution features 5.1 SR001067: Adding Low Power RRH (2Tx/2Rx 4.0 RRH-family) to SBTS-configurations 5.1.1 Description of SR001067: Adding Low Power RRH (2Tx/2Rx 4.0 RRH-family) to SBTS configurations Introduction to the feature This feature introduces SBTS support for Low Power Flexi Multiradio Remote Radio Heads 2Tx/2Rx 4.0 family: FHEI (1800 MHz) , FHDG (900 MHz), and FHGA (2100 MHz) for SBTS configurations.
5.1.1.1
Benefits End-user benefits This feature provides lower power consumption and lower footprint solution that requires smaller cell radius. Operator benefits The feature benefits the operator as follows: • • • •
5.1.1.2
Ability to support 2TX MIMO with medium range output power (2 x 5 W) for hot spot dense urban capacity sites. Easy outdoor installation. Minimal site weight. Minimal complexity while providing high capacity.
Requirements Hardware requirements This feature requires Flexi Multimode System Module FSMF (core module or baseband expansion module FBBC) and up to three RRHs (FHEI/FHGA/FHDG).
5.1.1.3
Functional description The SR001067: Adding Low Power RRH (2Tx/2Rx 4.0 RRH-family) to SBTSconfigurations feature introduces support of Low Power Remote Radio Heads (2Tx/2Rx 4.0 family) for SBTS configurations. Following RRHs (2 x 5 W) are supported: • • •
336
FHEI (1800 MHz) FHDG (900 MHz) FHGA (2100 MHz)
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Figure 68
Descriptions of BTS site solution features
BTS profile: L4_1-2, LTE dedicated, 3 RRHs, I-type
RRH
RRH
RRH
FSMF
Low Power RRH will be released with following configurations on distributed sites. Single band LTE up to 1+1+1 @ 2Tx/2Rx 2x2 MIMO, up to 3x20 MHz*, antenna connection- I-type. Supported LTE bandwidths- 1.4, 3, 5, 10, 15, 20 MHz.
5.1.1.4
System impact Interdependencies between features The following features are related to the SR001067: Adding Low Power RRH (2Tx/2Rx 4.0 RRH-family) to SBTS-configurations feature: • • •
LTE2245: FHEI Flexi Metro RRH 2-pipe 1800 10W LTE2032: FHGA Flexi Metro RRH 2TX 2100R LTE2247: FHDG Flexi Metro RRH 2-pipe 900 10W B
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.1.1.5
SR001067: Adding Low Power RRH (2Tx/2Rx 4.0 RRH-family) to SBTS-configurations management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Issue: 01E
DN09218825
337
Descriptions of BTS site solution features
SRAN 16.2, Feature Descriptions
Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
5.1.1.6
Sales information Table 206
Sales information
BSW/ASW BSW
License control in network element -
5.2 SR001346: FXFA, FXFC, FXCA, FXCB radios support in SBTS 5.2.1 Description of SR001346: FXFA, FXFC, FXCA, FXCB radios support in SBTS 5.2.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The feature enables the operator to use the SBTS solution for 1900 and 850 MHz bands.
5.2.1.2
Requirements Hardware requirements This feature requires no new or additional hardware.
5.2.1.3
Functional description This feature enables the operator to use FXFA, FXFC, FXCA, and FXCB radios on 850 and 1900 MHz bands. One SBTS profile with distributed 3xRFM WCDMA+GSM configuration is added.
338
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
5.2.1.4
Descriptions of BTS site solution features
System impact Interdependencies between features There are no interdependencies between this and the other features. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.2.1.5
SR001346: FXFA, FXFC, FXCA, FXCB radios support in SBTS management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
5.2.1.6
Sales information Table 207
Sales information
BSW/ASW
License control in network element
BSW
-
5.3 SR001347: High-capacity SBTS-installations 5.3.1 Description of SR001347: High-capacity SBTS-installations Introduction to the feature
Issue: 01E
DN09218825
339
Descriptions of BTS site solution features
SRAN 16.2, Feature Descriptions
This feature introduces new SBTS carrier configurations, addressing the needs for highcapacity site solutions with up to five frequency bands, including 2G/3G and/or 2G/LTE RF sharing. The following frequency bands are covered with the least HW footprint: • • • • •
5.3.1.1
800 MHz 900 MHz 1800 MHz 2100 MHz 2600 MHz
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature introduces high-capacity site solutions covering up to five frequency bands (shared and non-shared) with the least HW footprint.
5.3.1.2
Requirements Hardware requirements This feature requires the following baseband modules: • • •
2 FSMF 2 FBBA or 2 FBBC 2 FBBC
For the list of RF units supported by this feature see LWG_2fsm25_1, LWG_2fsm25_2, and LWG_2fsm25_3 SBTS profiles in SBTS Supported Configurations and Creating SBTS Configurations.
5.3.1.3
Functional description This feature introduces support for 3-RAT (LTE-WCDMA-GSM) carrier configurations with two system modules and up to seven RF units. The configurations introduced by this feature are described in LWG_2fsm25_1, LWG_2fsm25_2, and LWG_2fsm25_3 SBTS profiles. For details about these profiles and their full scope, see SBTS Supported Configurations and Creating SBTS Configurations.
5.3.1.4
System impact Interdependencies between features There are no interdependencies between features. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools
340
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of BTS site solution features
This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.3.1.5
SR001347: High-capacity SBTS-installations management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
5.3.1.6
Sales information Table 208
Sales information BSW/ASW
BSW
License control in network element -
5.4 SR000601: Initial SBTS Configurations for ETSI market with 6Gbps OBSAI radio units 5.4.1 Description of SR000601: Initial SBTS Configurations for ETSI market with 6 Gbps OBSAI Radio units Introduction to the feature SR000601: Initial SBTS Configurations for ETSI market with 6 Gbps OBSAI Radio units feature presents initial SBTS configurations with 6 Gbps OBSAI Radio units with Flexi Multiradio 10 System Module (FSMF) and capacity extension sub-modules FBBA/C. Feature introduces sets of configurations for dedicated SBTS technologies but also 2RAT and 3-RAT system module sharing with specific RF sharing on top.
5.4.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits
Issue: 01E
DN09218825
341
Descriptions of BTS site solution features
SRAN 16.2, Feature Descriptions
The feature benefits the operator as follows: • • • •
5.4.1.2
feature allows the operator to use 6 Gbps OBSAI Radio units power and cost savings due to hardware sharing improved customer perception for system sharing support possibility of creating cells with multiple deployment options
Requirements Hardware requirements Feature requires Flexi Multiradio 10 System Module (FSMF) for all configurations. Following hardware is optional for this feature: • •
5.4.1.3
FBBA Flexi Baseband Sub-Module FBBC Flexi Baseband Sub-Module
Functional description This feature introduces configurations with 6 Gbps OBSAI Radio units. Dedicated technology (GSM, LTE, WCDMA), 2-RAT, and 3-RAT configurations are possible. Flexi Multiradio 10 System Module (FSMF) is the only SM supported by this feature. Carrier and TRX allocations are defined as per standard sector configuration types. For details on configurations introduced by this feature, see SBTS Supported Configurations and Creating SBTS Configurations. Feature allows centralized configurations where RF modules are in the same location and several RFMs serve 3 sectors. Radio units Feature introduces configurations with following supported Radio units: • • • • • •
FXDB - 3TX RFM FRGT - 3TX RFM FRGU - 6TX RFM FXED - 6TX RFM FRHC - 6TX RFM FRMC - 6TX RFM
Configurations Feature introduces following configurations: One RAT • • • • • •
342
G1_1 _SUB1 - GSM WG5_1_SUB1 - GSM W2_1_SUB1 - WCDMA W1_1_SUB1 - WCDMA FL1_1_SUB1 - FDD-LTE L1_1 - FDD-LTE
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of BTS site solution features
Two RATs • • • • • •
WG5_1 - WCDMA-GSM WG1_1_SUB1 - WCDMA-GSM WG2_1_SUB1 - WCDMA-GSM LG2_1_SUB1 - LTE-GSM LG6_1_SUB1 - LTE-GSM LG6_1_SUB2 - LTE-GSM
Three RATs •
5.4.1.4
LWG1_4 - LTE-WCDMA-GSM
System impact Interdependencies between features There are no interdependencies between features. Impact on interfaces This feature has no impact on interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature has no impact on system performance and capacity.
5.4.1.5
SR000601: SBTS configurations with 6 Gbps OBSAI Radio units management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
Issue: 01E
DN09218825
343
Descriptions of BTS site solution features
5.4.1.6
SRAN 16.2, Feature Descriptions
Sales information Table 209
Sales information BSW/ASW
BSW
License control in network element -
5.5 SR001268: Initial SBTS configurations for China market 5.5.1 Description of SR001268: Initial SBTS configurations for China market Introduction to the feature The SR001268: Initial SBTS configurations for China market feature defines a set of initial SBTS configurations for China market requirements. RF units are supported in LTE-GSM, LTE-WCDMA, WCDMA-GSM and LTE-WCDMA-GSM RF sharing modes or in dedicated LTE or GSM mode. Only FSM rel.3 (FSMF) is supported.
5.5.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The feature benefits the operator as follows: • •
5.5.1.2
improved customer perception of system sharing support cost reduction
Requirements Hardware requirements This feature requires up to two FSMF Flexi Multiradio System Modules plus up to two FBBA/C extension modules for each SM.
5.5.1.3
Functional description Functional overview The SR001268: Initial SBTS configurations for China market feature defines a set of initial SBTS configurations for China market requirements. Introduced configurations This feature introduces support of following carrier configurations: •
GSM –
•
344
G4_1: Distributed, FSMF+FBBC, six 2Tx/2Rx RRHs
FDD-LTE
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
– – •
– –
LG4_1: Distributed, FSMF+FBBC, six 2Tx/2Rx RRHs LG5_1: Centralized, FSMF+FBBC+FBBC, four 3Tx/6Rx RFMs and one 6Tx/6Rx RFM for dedicated LTE LG5_1: Centralized, FSMF+FBBC+FBBC, four 3Tx/6Rx RFMs and one 6Tx/6Rx RFM for dedicated LTE
LTE-WCDMA – – – –
•
WG4_1: Distributed, FSMF+FBBA/C+FBBA/C, three 2Tx/2Rx RRHs
LTE-GSM –
•
L3_1: Centralized, FSMF+FBBC+FBBC, two 3Tx/6Rx RFM and two 6Tx/6Rx RFMs L4_1: Distributed, FSMF, three 2Tx/2Rx RRHs
WCDMA-GSM –
•
Descriptions of BTS site solution features
LW1_3: Centralized, FSMF+FBBA/C+FBBA/C, two 3Tx/6Rx RFMs LW5_1: Distributed, FSMF+FBBA/C+FBBA/C, three 2Tx/2Rx RRH LW5_2: Distributed, FSMF+FBBA/C+FBBA/C, three 2Tx/2Rx RRH LW5_3: Distributed, FSMF+FBBA/C+FBBA/C, three 2Tx/2Rx RRH
LTE-WCDMA-GSM – – – – – – – –
LWG_2fsm10_1: Centralized, FSMF+FBBA/C+FBBA/C+FSMF+FBBC, five 3Tx/6Rx RFMs LWG_2fsm10_2: Centralized, FSMF+FBBA/C+FBBA/C+FSMF+FBBC, five 3Tx/6Rx RFMs LWG_2fsm12_1: Centralized, FSMF+FBBA/C+FBBA/C+FSMF+FBBC+FBBC, three 6Tx/6Rx RFMs LWG_2fsm12_2: Centralized, FSMF+FBBA/C+FBBA/C+FSMF+FBBC+FBBC, three 6Tx/6Rx RFMs LWG_2fsm14_1: Centralized, FSMF+FBBA/C+FBBA/C+FSMF+FBBC+FBBC, four 3Tx/6Rx RFMs and one 6Tx/6Rx RFM for dedicated LTE LWG_2fsm14_2: Centralized, FSMF+FBBA/C+FBBA/C+FSMF+FBBC+FBBC, four 3Tx/6Rx RFMs and one 6Tx/6Rx RFM for dedicated LTE LWG_2fsm14_3: Centralized, FSMF+FBBA/C+FBBA/C+FSMF+FBBC+FBBC, four 3Tx/6Rx RFMs and one 6Tx/6Rx RFM for dedicated LTE LWG_2fsm15_1: Distributed, FSMF+FBBA/C+FBBA/C+FSMF+FBBC+FBBC, 2Tx/2Rx RRHs and one 4Tx/4Rx RRH for dedicated LTE
For more details about the configurations, see SBTS Supported Configurations.
5.5.1.4
System impact Interdependencies between features There are no interdependencies between features. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools
Issue: 01E
DN09218825
345
Descriptions of BTS site solution features
SRAN 16.2, Feature Descriptions
This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.5.1.5
SR001268: Initial SBTS configurations for China market management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
5.5.1.6
Sales information Table 210
Sales information
BSW/ASW BSW
License control in network element -
5.6 SR001253: Initial SBTS-configurations with 2x FSMF System Modules 5.6.1 Description of SR001253: Initial SBTS configurations with 2x FSMF System Modules Introduction to the feature The SR001253: Initial SBTS configurations with 2x FSMF System Modules feature introduces new SBTS profiles, covering SBTS configurations with 2x FSMF System Modules.
5.6.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
346
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of BTS site solution features
Operator benefits The feature benefits the operator as follows: • •
5.6.1.2
improved customer perception of system sharing support cost reduction
Requirements Hardware requirements This feature requires 2x Flexi Multiradio System Modules FSMF plus up to 4x FBBC baseband extension modules.
5.6.1.3
Functional description The SR001253: Initial SBTS configurations with 2x FSMF System Modules feature introduces set of configurations for the dedicated SBTS technologies, but also 2-RAT and 3-RAT system module sharing with up to 2x FSMF System Modules. New SBTS profiles are introduced for supporting following configurations: • • •
Dedicated GSM-layer plus up to three dedicated LTE layers configurations using 3and 6-pipe RF-modules. Dedicated GSM-layer plus dedicated WCDMA layer plus up to three dedicated LTE layer using 3- and 6-pipe RF-modules. Dedicated GSM-layer plus dedicated WCDMA layer plus up to three dedicated LTE layer configurations using 2- and 4-pipe RRHs.
Two RATs •
LWG_2fsm8_3 - LTE-GSM
Three RATs • •
5.6.1.4
LWG_2fsm16_1 - LTE-WCDMA-GSM LWG_2fsm16_3 - LTE-WCDMA-GSM
System impact Interdependencies between features There are no interdependencies between features. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity when the number of users does not exceed the licensed maximum.
Issue: 01E
DN09218825
347
Descriptions of BTS site solution features
5.6.1.5
SRAN 16.2, Feature Descriptions
SR001253: Initial SBTS configurations with 2x FSMF System Modules management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
5.6.1.6
Sales information Table 211
Sales information
BSW/ASW BSW
License control in network element -
5.7 SR001356: New SBTS-profile for High-sector RRHdeployment 5.7.1 Description of SR001356: New SBTS-profile for Highsector RRH-deployment Introduction to the feature This feature introduces a new SBTS profile with high number of RRHs.
5.7.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature introduces new site solution with high number of RRHs.
5.7.1.2
Requirements Hardware requirements This feature requires the following baseband modules:
348
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
• • •
Descriptions of BTS site solution features
FSMF FBBC FBBA or FBBC
Up to nine RRHs can be acommodated with this profile.The supported RF units are: • • • •
5.7.1.3
FHDB FHEB FHEF FHEG
Functional description This feature introduces support for 3-RAT (LTE-WCDMA-GSM) distributed carrier configuration with up to nine RRHs. The configuration introduced by this feature is described in the LWG26 SBTS profile. For details about LWG26 profile and its full scope, see SBTS Supported Configurations and Creating SBTS Configurations.
5.7.1.4
System impact Interdependencies between features There are no interdependencies between this feature and any other feature. Impact on interfaces feature has no impact on interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.7.1.5
SR001356: New SBTS-profile for High-sector RRH-deployment Management Data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
Issue: 01E
DN09218825
349
Descriptions of BTS site solution features
5.7.1.6
SRAN 16.2, Feature Descriptions
Sales information Table 212
Sales information BSW/ASW
BSW
License control in network element -
5.8 SR000999: SBTS configurations with 3G OBSAI radios 5.8.1 Description of SR000999: SBTS configurations with 3 Gbps OBSAI radios Introduction to the feature SR000999: SBTS configurations with 3 Gbps OBSAI radios feature defines initial SBTS configurations with 3 Gbps OBSAI Radio units with Flexi Multiradio System Module FSMF and capacity extension sub-modules FBBA/C. Feature introduces sets of configurations for the dedicated SBTS technologies but also 2-RAT and 3-RAT system module sharing with specific RF sharing on top.
5.8.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The feature benefits the operator as follows: • • •
5.8.1.2
feature allows the operator to use 3 Gbps OBSAI Radio units power and cost savings due to hardware sharing improved customer perception for system sharing support
Requirements Hardware requirements Feature requires Flexi Multiradio 10 System Module (FSMF) for all configurations. Following hardware is optional for this feature: • •
5.8.1.3
FBBA Flexi Baseband Sub-Module FBBC Flexi Baseband Sub-Module
Functional description SR000999: SBTS configurations with 3 Gbps OBSAI radios feature presents configurations with 3 Gbps OBSAI Radio units. Dedicated technology (LTE only), 2-RAT, and 3-RAT configurations are possible. Flexi Multiradio System Module Rel.3 (FSMF) is the only SM supported by this feature. Carrier and TRX allocations are defined as per standard sector configuration types.
350
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of BTS site solution features
For more details about configurations introduced by this feature, see SBTS Supported Configurations and Creating SBTS Configurations. Feature allows two types of configurations: • •
Centralized - RF modules are in the same location and 1 or 2 RFMs serve 3 sectors Distributed - each sector has its own Radio unit
Radio units Feature introduces configurations with following supported Radio units: • • • • •
FRMB - 2TX RRH FRGQ - 2TX RRH FRLB - 2TX RRH FRGP.A - 3TX RFM FRGP.B - 3TX RFM
Configurations Feature introduces following configurations: One RAT •
L20_1 - FDD-LTE
Two RATs • • •
LW20_1 - LTE-WCDMA LW21_1 - LTE-WCDMA LW21_3 - LTE-WCDMA
Three RATs • •
5.8.1.4
LWG20_1 - LTE-WCDMA-GSM LWG21_1 - LTE-WCDMA-GSM
System impact Interdependencies between features The following features need to be activated: • •
SR000972: SBTS System Module Sharing RTU SR001000: SBTS RF Sharing RTU
Impact on interfaces This feature has no impact on interfaces. Impact on network management tools
Issue: 01E
DN09218825
351
Descriptions of BTS site solution features
SRAN 16.2, Feature Descriptions
This feature has no impact on network management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.8.1.5
SR000999: SBTS configurations with 3 Gbps OBSAI radios management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 213
Related existing parameters Full name
5.8.1.6
Abbreviated name
Managed object
Number of system module sharing
numberOfSystemModuleShari ng
CAPCFG
Number of radio sharing
numberOfRadioSharing
CAPCFG
Sales information Table 214
Sales information BSW/ASW
BSW
License control in network element -
5.9 SR001036: SBTS LTE-GSM and WCDMA-GSM configurations with 3GBps OBSAI radios 5.9.1 Description of SR001036: SBTS LTE-GSM and WCDMAGSM configurations with 3GBps OBSAI radios Introduction to the feature The SR001036: SBTS LTE-GSM and WCDMA-GSM configurations with 3GBps OBSAI radios feature provides support of 3Gbps OBSAI based Triple RF units and RRHs for SBTS configurations. RF units are supported in LTE-GSM and WCDMA-GSM RF sharing mode or in dedicated WCDMA, LTE or GSM mode.
352
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
5.9.1.1
Descriptions of BTS site solution features
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The feature benefits the operator as follows: • •
5.9.1.2
Change of 3G OBSAI radios to 6G OBSAI radios is not necessary for SBTS configurations. Easy implementation of configurations.
Requirements Hardware requirements There are no additional hardware requirements.
5.9.1.3
Functional description The SR001036: SBTS LTE-GSM and WCDMA-GSM configurations with 3GBps OBSAI radios feature introduces the support of 3Gbps OBSAI based Triple RF units and RRHs for SBTS. RF units are supported in LTE-GSM and WCDMA-GSM RF sharing mode or in dedicated WCDMA, LTE or GSM mode. Following are the supported RF Units: •
3x60 W Triple RF Modules: – – –
•
FXDA 900, RFM 3Tx/6Rx Band 8 FXDJ 900J, no support for LTE FXEA 1800, RFM 3Tx/6Rx Band 3
40+40W RRHs: – –
FHDA 900, RRH 2Tx/2Rx Band 8 FHEA 1800, RHH 2Tx/2Rx Band 3
SR001036: SBTS LTE-GSM and WCDMA-GSM configurations with 3GBps OBSAI radios feature introduces support of following carrier configurations: •
WCDMA - GSM 1x RFM: WCDMA 1+1+1 - GSM 6+6+6 – –
WCDMA A-type GSM A-type
2x RFM: WCDMA 1+1+1 - GSM 6+6+6 – –
WCDMA C-type GSM C-type
1-3 x RFM: WCDMA 1+1+1 - GSM 6+6+6 u –
Issue: 01E
WCDMA B-type
DN09218825
353
Descriptions of BTS site solution features
–
SRAN 16.2, Feature Descriptions
GSM B-type
1-3 x RRH: WCDMA 1+1+1 - GSM 6+6+6 – – •
WCDMA A-type GSM A-type
LTE - GSM 2x (2 x RFM: LTE MIMO 2x2 up to 10MHz - GSM 4+4+4) – – – –
15Mhz LTE support with GSM TBD 20MHz LTE not supported with GSM LTE H-type GSM C-type
1-3 x RFM: LTE MIMO 2x2 up to 10MHz - GSM 4+4+4 – – – –
15Mhz LTE support with GSM TBD 20MHz LTE not supported with GSM LTE G-type GSM B-type
2x (1-3 x RRH: LTE MIMO 2x2 up to 10MHz - GSM 4+4+4) – – – –
5.9.1.4
15Mhz LTE support with GSM TBD 20MHz LTE not supported with GSM LTE I-type GSM A-type
System impact Interdependencies between features There are no interdependencies between features. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.9.1.5
SR001036: SBTS LTE-GSM and WCDMA-GSM configurations with 3GBps OBSAI radios management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature.
354
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of BTS site solution features
Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
5.9.1.6
Sales information Table 215
Sales information
BSW/ASW BSW
License control in network element -
5.10 SR001226: SBTS profiles for Indian customer and FXEE PIM avoidance configurations 5.10.1 Description of SR001226: SBTS profiles for Indian customer and FXEE PIM avoidance configurations Introduction to the feature The SR001226: SBTS profiles for Indian customer and FXEE PIM avoidance configurations feature introduces new SBTS profiles to fulfill Indian customer requirements. It also introduces FXEE specific sector configuration to handle PIM impact. Only FSM rel.3 (FSMF) is supported.
5.10.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The feature benefits the operator as follows: • •
5.10.1.2
extended configuration capabilities better performance due to PIM avoidance
Requirements Hardware requirements This feature requires the FSMF Flexi Multiradio System Module.
5.10.1.3
Functional description Functional overview
Issue: 01E
DN09218825
355
Descriptions of BTS site solution features
SRAN 16.2, Feature Descriptions
The SR001226: SBTS profiles for Indian customer and FXEE PIM avoidance configurations feature introduces new 2-RAT and 3-RAT SBTS profiles to fulfil Indian customer requirements. Additionally, it introduces the FXEE specific sector configuration to handle PIM impact. Introduced configurations This feature introduces support for the following carrier configurations. 2 RAT Configurations (WCDMA-GSM mode): • •
BTS profile ID: WG37, Centralized, FSMF+FBBA/C+FBBC, three 3Tx/6Rx RFMs BTS profile ID: WG38, Mixed, FSMF+FBBA/C+FBBA/C, two 3Tx/6Rx RFMs, three 2Tx/2Rx RRHs
3 RAT Configurations: • • • • • • • • • • • • • • • • • • • • •
356
BTS profile ID: LWG1_1, Centralized, FSMF+FBBA/C+FBBA/C, four 3Tx/6Rx RFMs BTS profile ID: LWG4_1, Centralized, FSMF+FBBC+FBBA/C, two 3Tx/6Rx RFMs, two 6Tx/6Rx RFMs BTS profile ID: LWG5_1, Centralized, FSMF+FBBC+FBBA/C, one 3Tx/6Rx RFM, three 6Tx/6Rx RFMs BTS profile ID: LWG38_1, Centralized, FSMF+FBBC+FBBA/C, four 3Tx/6Rx RFMs BTS profile ID: LWG38_2, Centralized, FSMF+FBBC+FBBA/C, four 3Tx/6Rx RFMs BTS profile ID: LWG40_1, Mixed, FSMF+FBBA/C+FBBA/C, one 3Tx/6Rx RFM, one 6Tx/6Rx RFM, three 2Tx/2Rx RRHs BTS profile ID: LWG40_2, Mixed, FSMF+FBBA/C+FBBC, one 3Tx/6Rx RFM, one 6Tx/6Rx RFM, three 2Tx/2Rx RRHs BTS profile ID: LWG38_4, Centralized, FSMF+FBBC+FBBA/C, four 3Tx/6Rx RFMs BTS profile ID: LWG38_5, Centralized, FSMF+FBBC+FBBA/C, four 3Tx/6Rx RFMs BTS profile ID: LWG41_1, Centralized, FSMF+FBBC+FBBA/C, three 3Tx/6Rx RFMs, one 6Tx/6Rx RFM BTS profile ID: LWG41_2, Centralized, FSMF+FBBC+FBBA/C, three 3Tx/6Rx RFMs, one 6Tx/6Rx RFM BTS profile ID: LWG42_1, Centralized, FSMF+FBBC+FBBA/C, two 3Tx/6Rx RFMs, one 6Tx/6Rx RFM BTS profile ID: LWG42_2, Centralized, FSMF+FBBC+FBBA/C, two 3Tx/6Rx RFMs, one 6Tx/6Rx RFM BTS profile ID: LWG43_1, Mixed, FSMF+FBBC+FBBA/C, three 3Tx/6Rx RFMs, three 2Tx/2Rx RRHs BTS profile ID: LWG43_2, Mixed, FSMF+FBBC+FBBA/C, three 3Tx/6Rx RFMs, three 2Tx/2Rx RRHs BTS profile ID: LWG46_1, Centralized, FSMF+FBBC+FBBA/C, three 3Tx/6Rx RFMs, one 6Tx/6Rx RFM BTS profile ID: LWG46_2, Centralized, FSMF+FBBC+FBBA/C, three 3Tx/6Rx RFMs, one 6Tx/6Rx RFM BTS profile ID: LWG47_1, Centralized, FSMF+FBBC+FBBA/C, five 3Tx/6Rx RFMs BTS profile ID: LWG47_2, Centralized, FSMF+FBBC+FBBA/C, five 3Tx/6Rx RFMs BTS profile ID: LWG23_1, Centralized, FSMF+FBBA/C+FBBA/C, three 3Tx/6Rx RFMs, one 6Tx/6Rx RFM BTS profile ID: LWG23_2, Centralized, FSMF+FBBA/C+FBBC, three 3Tx/6Rx RFMs, one 6Tx/6Rx RFM
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
• • • • • •
Descriptions of BTS site solution features
BTS profile ID: LWG24_1, Mixed, FSMF+FBBA/C+FBBC, two 3Tx/6Rx RFMs, one 6Tx/6Rx RFM, three 2Tx/2Rx RRHs BTS profile ID: LWG24_2, Mixed, FSMF+FBBA/C+FBBC, two 3Tx/6Rx RFMs, one 6Tx/6Rx RFM, three 2Tx/2Rx RRHs BTS profile ID: LWG38_3, Centralized, FSMF+FBBC+FBBA/C, two 3Tx/6Rx RFMs, three 2Tx/2Rx RRHs BTS profile ID: LWG42_3, Centralized, FSMF+FBBC+FBBA/C, two 3Tx/6Rx RFMs, one 6Tx/6Rx RFM BTS profile ID: LWG5_2, Centralized, FSMF+FBBA/C+FBBA/C, one 3Tx/6Rx RFM, two 6Tx/Rx RFMs BTS profile ID: LWG49, Centralized, FSMF+FBBC+FBBA/C, five 3Tx/6Rx RFMs
For more details about the configurations see SBTS Supported Configurations.
5.10.1.4
System impact Interdependencies between features There are no interdependencies between features. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.10.1.5
SR001226: SBTS profiles for Indian customer and FXEE PIM avoidance configurations For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
Issue: 01E
DN09218825
357
Descriptions of BTS site solution features
5.10.1.6
SRAN 16.2, Feature Descriptions
Sales information Table 216
Sales information
BSW/ASW BSW
License control in network element -
5.11 SR001167: SBTS support for FXEF Flexi RFM 3pipe 1800 240W 5.11.1 SR001167: SBTS support for FXEF Flexi RFM 3-pipe 1800 240W Benefits, functionality, system impact, reference data, instructions of the feature The SR001167: SBTS support for FXEF Flexi RFM 3-pipe 1800 240W feature introduces support for FXEF radio module in SBTS.
5.11.1.1
SR001167 benefits The SR001167: SBTS support for FXEF Flexi RFM 3-pipe 1800 240W feature provides the following benefits: •
5.11.1.2
introduces support for a light weight, easy to install, and energy-efficient radio module
SR001167 functional description Basic LTE configurations with one FXEF for one sector: • • • • •
1 LTE cell at max 20 MHz LTE bandwidth and 2TX MIMO / 2RX 2 LTE cells at max 20 MHz + max 20 MHz LTE bandwidth and 2TX MIMO / 2RX 8+8, 20+20, 40+40, 60+60 or 80+80 W 2TX per sector (by branch activation and MIMO software licenses) hardware ready for 4RX (support requires 4RX SW licence) 8, 20, 40, 60W or 80W 1TX 2RX mode for 1, 2 or 3 sectors (by branch activation software licenses)
Basic LTE configurations with two FXEF for 2 or 3 sectors: • • • •
358
1+1 or 1+1+1 LTE cells at max 20 MHz LTE bandwidth and 2TX MIMO / 2RX 2+2 or 2+2+2 LTE cells at max 20 MHz + max 20 MHz LTE bandwidth and 2TX MIMO / 2RX 8+8, 20+20, 40+40, 60+60 or 80+80 W 2TX mode per sector (by branch activation and MIMO software licenses) hardware ready for 4RX (support requires 4RX software licence)
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of BTS site solution features
LTE-GSM configurations example: • •
up to 20 MHz LTE (40W) + 4 GSM TRX (4x10W) carriers per TX PA path 5 MHz LTE 2TX MIMO + 6 GSM TRX carriers (3+3) per sector from 2 TX PA pipes (1-3 sectors supported)
Basic GSM configurations: • •
5.11.1.3
4+4+4 at 20W iBW 40 Mhz up to 8 GSM TRX carriers (4+4) per sector from 2 TX PA pipe
SR001167 system impact SR001167: SBTS support for FXEF Flexi RFM 3-pipe 1800 240W impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The SR001167: SBTS support for FXEF Flexi RFM 3-pipe 1800 240W feature is impacted by the following features: •
SR001142: FXEF Flexi RFM 3-pipe 1800 240W The SR001142: FXEF Flexi RFM 3-pipe 1800 240W feature introduces FXEF radio module.
Impact on interfaces The SR001167: SBTS support for FXEF Flexi RFM 3-pipe 1800 240W feature has no impact on interfaces. Impact on network management tools The SR001167: SBTS support for FXEF Flexi RFM 3-pipe 1800 240W feature has no impact on network management tools. Impact on system performance and capacity The SR001167: SBTS support for FXEF Flexi RFM 3-pipe 1800 240W feature has no impact on system performance or capacity.
5.11.1.4
SR001167 reference data SBTS support for FXEF Flexi RFM 3-pipe 1800 240W requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements Alarms There are no alarms related to the SBTS support for FXEF Flexi RFM 3-pipe 1800 240W feature. BTS faults and reported alarms There are no faults related to the SBTS support for FXEF Flexi RFM 3-pipe 1800 240W feature. Commands
Issue: 01E
DN09218825
359
Descriptions of BTS site solution features
SRAN 16.2, Feature Descriptions
There are no commands related to the SBTS support for FXEF Flexi RFM 3-pipe 1800 240W feature. Measurements and counters There are no measurements or counters related to the SBTS support for FXEF Flexi RFM 3-pipe 1800 240W feature. Key performance indicators There are no key performance indicators related to the SBTS support for FXEF Flexi RFM 3-pipe 1800 240W feature. Parameters There are no parameters related to the SBTS support for FXEF Flexi RFM 3-pipe 1800 240W feature. Sales information Table 217
SR001167 sales information
Product structure class
License control
Basic Software (BSW)
-
Activated by default -
5.12 SR000972: SBTS System Module Sharing RTU 5.12.1 Description of SR000972: SBTS System Module Sharing RTU Introduction to the feature SBTS System Module Sharing RTU feature allows sharing of different technologies using one FSMF Core Module with optional FBBA/FBBC baseband extensions sub-modules for multi RAT support. System Module Sharing SW common license key for SBTS (HW sharing license) is introduced using SRAN's licensing framework (SR000794: SBTS SW License Management). It is applicable if RATs are shared within the same plug-in unit.
5.12.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • • • • •
5.12.1.2
360
usage of a common hardware for multiple technologies one common license simplification of operational tasks fewer number of sites needed- savings in energy, site rental and antenna systems minimized effort in maintaining license management
Requirements
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of BTS site solution features
Hardware requirements This feature requires no new or additional hardware. Other requirements SBTS is connected to NetAct
5.12.1.3
Functional description This section describes the functionalities of SR000972: SBTS System Module Sharing RTU feature. Functional overview System module sharing allows sharing of different technologies using one System Module. Up to 2-RATs can be configured on FSMF core module. This feature introduces a common System Module Sharing license by using the SRAN's licensing framework SR000794: SBTS SW License Management. • • •
GSM/WCDMA FSMF - 1 HW sharing license, GSM/LTE FSMF - 1 HW sharing license, RATs on dedicated plug-in-units - no HW sharing licenses.
System Module sharing license is needed when the same FSMF core module is shared between 2 RATs. For example, if GSM and LTE share the system module FSMF, license is required. But in case GSM is running on FSMF core module and LTE is running on the extension sub-module FBBC, the operator does not need license. A new parameter Number of system module sharing (numberOfSystemModuleSharing), which counts the number of RATs shared within the same FSMF core module, is introduced. If System Module Sharing is not configured, the value for Number of system module sharing (numberOfSystemModuleSharing) is set to “0”. The parameter is updated based on SCF. This parameter is then visible in NetAct database while SWEM checks the parameter and compares it periodically with SW license keys available via CLS. If SW license keys are unavailable after trial period, SWEM generates a new SCF for limiting the SBTS. Reconfiguring SM Sharing Given that there are enough granted licenses in the network level, users can set-up and edit System Module Sharing configurations without affecting the performance of the SBTS. Secure digital media is used to share the right-to-use credentials of System Module Sharing function that is granted in the network level by NetAct automatically. No alarms are generated if enough SW license keys for System Module Sharing in the CLS are available.
5.12.1.4
System impact This section describes the impact the SR000972: SBTS System Module Sharing RTU feature has on the system. Interdependencies between features
Issue: 01E
DN09218825
361
Descriptions of BTS site solution features
SRAN 16.2, Feature Descriptions
The SR000794: SBTS SW License Management feature is a prerequisite for using this feature. Impact on interfaces This feature has no impact on interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.12.1.5
SR000972: SBTS System Module Sharing RTU management data This section presents the management data related to the SR000972: SBTS System Module Sharing RTU feature. For information on alarm, counter, key performance indicators, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 218
New parameters Full name
Abbreviated name
Number of system module sharing
5.12.1.6
numberOfSystemModuleShari ng
CAPCFG
Sales information Table 219
Sales information BSW/ASW
ASW
362
Managed object
License control in network element Pool license
DN09218825
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of BTS site solution features
5.13 SR000944: Supported RF HW in SBTS 5.13.1 Description of SR000944: Supported RF HW in SBTS Introduction to the feature The SR000944: Supported RF HW in SBTS feature provides a summarized view of supported RF HW for SBTS describing supported Radio Modules and Remote Radio Heads.
5.13.1.1
Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The feature benefits the operator as follows: • •
5.13.1.2
Information about supported RF HW easily accessible Single source of information and documentation about the supported RF HW for SBTS.
Requirements Hardware requirements This feature requires Flexi Multimode System Module FSMF (core module) or baseband expansion module FBBC and several radios for deploying a configuration.
5.13.1.3
Functional description The SR000944: Supported RF HW in SBTS feature lists Radio Modules and Remote Radio Heads supported in SBTS configurations. This feature specifies which RF-units are supported for: • • • •
dedicated GSM-mode dedicated WCDMA-mode dedicated LTE-mode RF-sharing between RATs
Table 220 Unit
Issue: 01E
Supported RF HW for SRAN16, 6 Gbps OBSAI Band
DL Bandwi dth [MHz]
UL Bandwi dth [MHz]
Support in SBTS for LTE dedicate d mode
Support in SBTS for WCDMA dedicate d mode
Support Support in SBTS in SBTS for GSM for RFS dedicate d mode
Sales Item code
FHDB (RRH)
900
35
35
yes
yes
yes
yes
472649A
FXDB (RFM)
900
35
35
yes
yes
yes
yes
472573A
DN09218825
363
Descriptions of BTS site solution features
Table 220 Unit
Supported RF HW for SRAN16, 6 Gbps OBSAI (Cont.) Band
DL Bandwi dth [MHz]
UL Bandwi dth [MHz]
Support in SBTS for LTE dedicate d mode
Support in SBTS for WCDMA dedicate d mode
Support Support in SBTS in SBTS for GSM for RFS dedicate d mode
Sales Item code
FXJB (RFM)
900J
25
25
yes
yes
yes
yes
472574A
FXEB (RFM)
1800
35
60
yes
n/a
yes
yes
472501A
FXED (RFM)
1800
40
60
yes
n/a
yes
yes
472924A
FRGT (RFM)
2100
60
60
yes
yes
n/a
yes
472810A
FRGS (RFM)
2100
40
40
yes
yes
n/a
yes
472847A
FRGU (RFM)
2100
60
60
yes
yes
n/a
yes
472956A
FRME (RFM)
800
20
30
yes
n/a
n/a
no
472927A
FRHE (RRH)
2600
55
55
yes
n/a
n/a
no
472830A
FRHC (RFM)
2600
40
40
yes
n/a
n/a
no
472656A
FRHF (RFM)
2600
40
40
yes
n/a
n/a
no
472849A
FRMC (RFM)
800
40
40
yes
n/a
n/a
no
472655A
FRPA (RFM)
700
35
35
yes
n/a
n/a
no
472703A
FRPB (RFM)
700
30
30
yes
n/a
n/a
no
472752A
FHEG (RRH)
1800
30
30
yes
n/a
no
no
473044A
FHED (RRH)
1800
60
60
yes
n/a
yes
yes
472829A
FRHG (RRH)
2600
70
70
yes
n/a
n/a
no
473225A
Table 221 Unit
FRGP.A (RFM)
364
SRAN 16.2, Feature Descriptions
Supported RF HW for SRAN16, 3 Gbps OBSAI Band
2100
DL Bandwi dth [MHz]
UL Bandwi dth [MHz]
Support in SBTS for LTE dedicate d mode
Support in SBTS for WCDMA dedicate d mode
Support Support in SBTS in SBTS for GSM for RFS dedicate d mode
20
20
yes
yes
n/a
DN09218825
yes
Sales Item code
472100A
Issue: 01E
SRAN 16.2, Feature Descriptions
Descriptions of BTS site solution features
Table 221 Unit
5.13.1.4
Supported RF HW for SRAN16, 3 Gbps OBSAI (Cont.) Band
DL Bandwi dth [MHz]
UL Bandwi dth [MHz]
Support in SBTS for LTE dedicate d mode
Support in SBTS for WCDMA dedicate d mode
Support Support in SBTS in SBTS for GSM for RFS dedicate d mode
Sales Item code
FRGP.B (RFM)
2100
20
20
yes
yes
n/a
yes
472100B
FRGQ (RRH)
2100
60
60
yes
yes
n/a
yes
472261A
FRLB (RRH)
730
16
16
yes
n/a
n/a
no
472180A
FRMB (RRH)
800EU
30
30
yes
n/a
n/a
no
472291A
System impact Interdependencies between features The following features are related to the SR000944: Supported RF HW in SBTS feature: • •
SR000601: Initial SRAN BTS Configurations SR000999: SBTS configurations with 3G OBSAI radios
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity when the number of users does not exceed the licensed maximum.
5.13.1.5
SR000944: Supported RF HW in SBTS management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.
Issue: 01E
DN09218825
365
Descriptions of BTS site solution features
5.13.1.6
SRAN 16.2, Feature Descriptions
Sales information Table 222
Sales information
BSW/ASW BSW
366
License control in network element -
DN09218825
Issue: 01E
View more...
Comments
