TD-LTE FWA Technical Requirements

TD-LTE for Fixed Wireless Access
Technical Requirements
All material in this document is confidential information. The confidential may not be disclosed to third parties other than employees and authorized
contractors of H3G except with the express written authorization of H3G. The confidential information must be kept safe and it must not be reproduced or
used for purposes other than those, which H3G has authorized.
Document Title Version: 1.1 File

TD-LTE for Fixed Wireless Access Document1
Date: 13-Apr-2016 H3G, 2017 Pag. 1 of 31

Page left intentionally blank

Date: 13-Apr-2016 H3G, 2017 Pag. 2 of 31

Table of Content
1 DOCUMENT CONTROL.........................................................................................4
2 ACRONYMS ..............................................................................................................5
3 SCOPE ........................................................................................................................6
4 FWA SYSTEM DESCRIPTION ..............................................................................7
4.1 ARCHITECTURE OVERVIEW ....................................................................................................... 8
4.2 SUBSCRIBER BASE SEPARATION ................................................................................................ 8
4.2.1 Solution A Tracking Area - Roaming Restriction per IMSI range .............9
4.2.2 Solution B New PLMN for FWA LTE-TDD network ................................10
5 E-UTRAN TECHNICAL REQUIREMENTS ......................................................11
5.1 HW .............................................................................................................................................. 11
5.1.1 Basic Configuration.....................................................................................11
5.1.2 Evolution .....................................................................................................12
5.2 SW ............................................................................................................................................... 13
5.3 OSS .............................................................................................................................................. 13
5.4 SERVICES..................................................................................................................................... 16
5.4.1 Installation and commissioning ...................................................................16
5.4.2 Network O&M Services ...............................................................................16
5.4.2.1 Spare Parts Management ..........................................................................16
5.4.2.2 First Line Maintenance Service................................................................17
5.4.2.3 Second level support Service ...................................................................17
5.4.2.4 Third level support Service ......................................................................17
5.4.3 Engineering Support Service .......................................................................17
5.4.3.1 Performance evaluation, KPI, enhanced diagnostic .................................18
6 CPE TECHNICAL REQUIREMENTS.................................................................20
6.1 EXTERNAL ANTENNAS .............................................................................................................. 20
7 EXPECTED PERFORMANCE .............................................................................21
7.1.1 Evolution Scenarios .....................................................................................22
8 COMMERCIAL TRIAL PROJECT .....................................................................23
9 DELIVERABLES ....................................................................................................24
10 QUANTITIES ..........................................................................................................25
10.1 EUTRAN .................................................................................................................................... 25
10.2 OSS .............................................................................................................................................. 27
10.3 CPE.............................................................................................................................................. 27
10.4 O&M ........................................................................................................................................... 29
10.4.1 Definitions ...................................................................................................29
10.4.2 Service Level Agreement .............................................................................30

Date: 13-Apr-2016 H3G, 2017 Pag. 3 of 31

1 Document Control
Version Author Description Staus Date

Gennaro DOrio,
Andrea Tchertckoff,
1 First issue Final 11 Apr 2016
Luca Valentini,
Oronzo Barbati
Modified CPEs
1.1 Gennaro DOrio Final 13 Apr 2016
quantities

Date: 13-Apr-2016 H3G, 2017 Pag. 4 of 31

2 Acronyms
Acronyms used in this document
CPE Customer Premises Equipment
MBB Mobile BroadBand
FWA Fixed Wireless Access
CN-EPC Core Network Evolved Packet Core
TDD Time Domain Multiplex
E-UTRAN Evolved UMTS Terrestrial Radio Access Network
OSS Operations Support System
DL/UL Downlink/Uplink
CC-CA Component Carrier Carrier Aggregation
I/F Interface
BF Beamforming
MIMO Multiple Input Multiple Output
CR Change Request
ANR Automatic Neighbour Relations

Date: 13-Apr-2016 H3G, 2017 Pag. 5 of 31

3 Scope
H3G has started a feasibility study for the deployment of a TD-LTE Network to deliver
Fixed Wireless Access Services to Residential/Consumer customers.
This document describes the FWA System and the technical requirements to fullfill by
interested equipment vendors.
The scope is limited to Radio Access Network Equipments and Customer Premises
Equipments (CPEs).
Special requirements to be matched by the Core Network (EPC) shall be highlighted by
equipment vendors.
A not exhaustive list of the items in scope and out of scope is the following
In scope
E-UTRAN HW and SW supply, installation and commissioning
OSS for E-UTRAN
Support for Network Tuning/Optimization
First Line Maintenance
3rd Level Technical Support
Spare Parts Management
CPEs
Out of scope
Radiating Systems supply, installation and commissioning (RF cables, Antennas,
Filters, Multiplexing)
Transmission Network
EPC

Date: 13-Apr-2016 H3G, 2017 Pag. 6 of 31

4 FWA System Description
The System under study shall deliver Broad Band services to residential users (fixed-
indoor) in small to medium sized towns not served by Wired BroadBand network (copper or
fiber).
The Radio Technology selected for Network Access is TD-LTE in the 2600MHz Band
(3GPP B38 Operating Band).
Nokia Response: Compliant
The proposed FZHI Flexi RRH 8TX 2600 (Band 38) radio module provides maximized
flexibility, reliability and cost optimization. It is designed to minimize BTS site CAPEX and
OPEX. It can be deployed in small and medium sized towns to provide radio coverage.
Flexi System Module (FSMF) can support several radio access technologies and is not
dependent on the frequency band. When used for LTE the capacity is in terms of the
throughput and the maximum number of cells it can support.
The E-UTRAN nodes will be rolled-out using existing sites infrastructure from the actual
3G/4G H3G Network and the new HW shall integrate with existing HW and infrastructure.
The Flexi Multiradio 10 BTS is designed for easy installation, commissioning and
maintenance.The modular design ensures that the site blends easily into the exisitng sites. The
BTS can be installed on any standard 19 inch rack. Hence, the acceptance of a new site is
easier, and the acquisition time and cost can be minimized. Flexi Multiradio 10 Base Station
can be installed at any existing legacy site and reduces BTS site rental.
The selected solution shall guarantee to fully interoperate with H3G EPC.
Customer base using FWA shall be segregated from customer base using Mobile
BroadBand (MBB) services delivered by H3G 3G/4G live network. That means that the TDD
network shall be completely dedicated for this new FWA offering:
- only FWA customers can have access to TDD network and cannot have access to
UMTS/FDD LTE network
- Non-FWA customers cannot access TDD networks
For this purpose H3G identified two possible architectures described in the following
paragraphs.
The interested equipment vendors shall ensure that no limitation is imposed by E-UTRAN
with respect to such architectures. In addition any additional solution for traffic segregation
can be proposed and documented by them.
The FWA and Non-FWA customers can be segragated can be segragatged with the help of
Nokia application software features like VLAN traffic dfferentaion and Subscriber profile
based mobility. VLAN IDs (IEEE 802.1q) are set per packet, based on the traffic type

Date: 13-Apr-2016 H3G, 2017 Pag. 7 of 31

(U/C/M/S-plane). The mapping table is configurable. Each VLAN is associated with a
dedicated IP address at the eNB.
4.1 Architecture Overview

Scope of this document is to briefly describe, within the scope of the FWA project, the
high-level requirements the eNodeBs LTE TDD supplier shall comply with, in order to
achieve subscriber separation among the two customer bases, namely the Mobile Broad
Band subscriber base and the Fixed Wireless Access subscriber base. During the rest of this
document, we will refer to MBB subscribers and FWA subscribers.
H3G is considering two main technical options, and the LTE-TDD supplier shall be fully
compliant with both of them. Even if solutions are mainly affecting UMTS/ LTE Core
Network configuration, supplier shall carefully evaluate and declare any lack of compliancy
for each of the considered technical options, and highlight any possible limitation / partial
compliancy.
Supplier can make its recommendations, expressing arguments in favour of option A or
option B, and can propose additional alternative solutions, if more appropriate for the goals.
The current working assumption is that new customer should be able to asses by himself
if the LTE-TDD service is available with reasonable good performance at his location (exact
indoor signal level is more tricky to forecast), so its important to avoid any technical solution
that can make LTE-TDD device to temporary use LTE-FDD or WCDMA, leading to wrong
conclusions.
Nokia Response: Noted
4.2 Subscriber base separation

H3G wishes to achieve separation among MBB subscribers and FWA subscribers, to
have a good performance control / understanding of the offered service to FWA subscribers.
The current assumption is that FWA commercial offering will target residential users,
providing a viable alternative to fixed wired broadband access (e.g. typically ADSL) with
comparable or better quality. For this reason it is expected that the LTE-TDD FWA will be
marketed with no, or very high month data volume limit (e.g. flat offer), only in selected
towns, already reached by H3Gs UMTS and LTE-FDD 1800 services.
Subscriber separation solution main goals are:
1. Ensure that MBB subscribers will stay only on LTE FDD and/or WCDMA, without
camping / using LTE-TDD radio resources
2. Ensure that FWA subscribers will stay only on LTE TDD without camping / using
LTE-FDD and/or WCDMA radio resources
3. Cause no degradation of service level neither to MBB subscribers nor FWA
subscribers
4. To be flexible enough to allow for a smooth change of mind in future, e.g. making
possible to later remove, eventually only on certain towns, this strict separation:
essentially H3G wishes to retain the flexibility to make LTE-TDD carriers available

Date: 13-Apr-2016 H3G, 2017 Pag. 8 of 31

in future also to MBB subscribers, if WCDMA + LTE-FDD radio resources should
become too congested.
5. Reasonably easy to maintain over time Commented [MS(-I1]: Carlo

The FWA and Non-FWA customers can be segragated can be segragatged with the help of
Nokia application software features like VLAN traffic dfferentaion and Subscriber profile
based mobility. VLAN IDs (IEEE 802.1q) are set per packet, based on the traffic type
(U/C/M/S-plane). The mapping table is configurable. Each VLAN is associated with a
dedicated IP address at the eNB.
4.2.1 Solution A Tracking Area - Roaming Restriction per IMSI range

This solution will assign a contiguous IMSI block to FWA subscribers, and separate TAs
for LTE-FDD and LTE-TDD, even in the same geographical area. In the EPC, MMEs will be
configured to make distinction between the two ranges, allowing only FWA subscribers to
register on LTE-TDD TAs, while rejecting roaming of MBB subscribers (including
international roamers). In the same way, MMEs will not allow FWA subscribers to roam on
LTE-FDD, avoiding flat internet subscribers to overload LTE-FDD carriers and to take
advantage of a premium tariff on mobile devices like smartphone / tablets.
This option is the preferred one for the time being.
Should H3G need to reconsider LTE-TDD TAs restriction in future, it will be a simple
change of setting, in the relevant areas.
IMSI
TAC id roaming
range
X [A] allowed
HSS/HLR X [B] restricted
Y [B] allowed
Y [A] restricted
Different TAC for LTE RAT

per-IMSI range
roaming restrictions
SGSN
MME
LTE FDD Carrier RNC
WCDMA Carriers Iub
S1
LTE TDD Carrier eNodeB
NodeB
Mobile User
(IMSI range A)
TACid = X
FWA User
TACid = Y (IMSI range B)
Figure 1: Roaming restrictions per TAC/IMSI range


Date: 13-Apr-2016 H3G, 2017 Pag. 9 of 31

4.2.2 Solution B New PLMN for FWA LTE-TDD network
This solution will introduce a new PLMN (222-xx) for LTE-TDD FWA network,
requiring FWA-specific USIMs provisioning. In this scenario, if a single eNodeB will
provide FDD/TDD service in the same area, it shall support multiple-PLMN ids.
While this separation is cleaner, it appears also more inflexible. In particular, if at a
later stage, H3G will reconsider the separation, to open LTE-TDD carrier also to MBB
subscribers, it should deploy more complex solutions, e.g. EHPLMN, requiring additional
work and tuning.
Allowed
Profile type
PLMN
Mobile User
(WCDMA / LTE- 222-99
FDD)
HSS/HLR
FWA User
222-xx
(LTE-TDD)
Served PLMNs for LTE RAT:

PLMNID_TDD, PLMNID_FDD
MME
LTE FDD Carrier RNC
WCDMA Carriers Iub
S1
LTE TDD Carrier eNodeB
NodeB
PLMN id = 222-99
Mobile User
(PLMN FDD)
FWA User
PLMN id = 222-xx
(PLMN TDD)
Figure 2: Separate PLMN id solution (simplified architecture)


Date: 13-Apr-2016 H3G, 2017 Pag. 10 of 31

5 E-UTRAN Technical Requirements
The following requirements define the main aspects to be fulfilled by the selected
solution.
Some degree of freedom are intentionally left for the equipment vendors to suggest their
own solution aiming to maximize perfomance of the system in terms of
Network Capacity and Coverage
Peak bitrate
Scalability
Ease of installation
Operation and maintenance
Flexi Multiradio 10 Base Station can be used to build coverage and capacity. A high cell
capacity and wide coverage per site means fewer sites which makes building a network more
cost-effective. Flexi Multiradio 10 Base Station can be installed at any existing legacy site
and reduces BTS site rental costs because a BTS-specific cabinet or extra floor space is no
longer needed on the site. Simplicity and speed of maintenance improves operational
reliability. Maintenance is improved by module integration and automatic fault detection
procedures. Special attention has been paid to Flexi Multiradio 10 Base Station software start
time, reducing, for instance, downtime when a new software package is put into use.
5.1 HW
This document describe requirements to be fulfilled by E-UTRAN HW equipment.
While out of scope for this document, specific requirements to be imposed on EPC to
better exploit advanced E-UTRAN features must be highlighted by the equipment vendors.
Two configurations are depicted, with Basic Configuration being the target for first
deployment.
5.1.1 Basic Configuration

The E-UTRAN for initial deploying shall guarantee full support for TD-LTE as defined in
3GPP TS36 series.
The initial network configuration shall be
Both 2T2R and 4T4R at eNode side and:
- 2R CPEs (2x2 MIMO) indoor and outdoor, and/or
- 4R CPEs (4x4 MIMO) indoor and outdoor
DL-UL configurations #1 and #2 as defined in 3GPP TS36.211 Table 4.2-2 shall
be supported
GPS kit for tight TDD synchronization
BW: 20MHz in 2600MHz B38 Band
Total TX DL Power = 80W per sector
- 40W+40W for 2T2R

Date: 13-Apr-2016 H3G, 2017 Pag. 11 of 31

- 20W+20W+20W+20W for 4T4R
For transport over S1 interface the new HW shall use on-site available transport network,
equipped with Gigabit Ethernet physical I/F
The vendors shall provide a detailed description of any proprietary feature (if any) useful
to improve performance (expecially in terms of both capacity and coverage).
For details please refer to the proposed application software list in the pricing file.
5.1.2 Evolution
After initial deployment, network shall be easily scalable by upgrading to advanced
features.
Capacity/coverage increase shall be obtained by expanding Multi Antenna System
capabilities supporting 8T8R at eNodeB side for Beam Forming (BF) and other MIMO
techniques.
Flexi Multiradio 10 BTS supports various MIMO techniques in order to increase the capacity
of the base station. Transmission mode 8 is a new transmission mode introduced in Rel 9.
Two code words are transmitted simultaneously in beamforming mode, which is also known
as dual layer beamforming. Comparing with single layer beamforming, one additional code
word is weighted by a vector, and combined with the first precoded code word to form the
transmitted data for each antenna. A total of two weighting vectors should be derived for dual
layer beamforming.
Dual Stream beamforming introduces capacity gain (~10% compared to single stream
beamforming).
The Downlink SU MIMO (8x4) with TM9 feature comprises the following aspects:
up to four spatial multiplexing layers in downlink using transmission mode 9 (TM9)
dynamic switching between 14 spatial layers for TM9 UEs, based on RI/PMI reports
from UEs (fast MIMO mode switch)
pre-configured 8 port CSI-RS resource allocation and dynamic CSI-RS on/off
switch,based on the availablity of TM9 UEs in the network
4Rx UEs (category 5 and higher; 3GPP Rel. 10 UE capabilities) with up to four
spatial multiplexing layers and TM9 UE's capability based transmission mode
configuration and codebook restriction of TM9 to 4 layers
Flexi Multiradio BTS applies eight antenna ports to support interconnection with antenna
systems with an 8Tx antenna in a downlink direction and provides 10 MHz, 15 MHz, and 20
MHz bandwidths.
The Vendors shall describe and offer any new technology evolution which brings a significant Commented [MS(-I2]: Carlo
improvements in terms of both capacity and coverage. The reference timeframe is 5 years
from now.

Date: 13-Apr-2016 H3G, 2017 Pag. 12 of 31

Nokia FastMile delivers high-speed broadband to residential customers in rural areas. The
end-to-end approach ensures high data rates and enables a minimum throughput to be
guaranteed. It also enables high capacity by utilizing advanced antenna topology and
interference mitigation technologies. For mobile operators, this is an opportunity to address a
new customer base with help of their existing LTE network and spectrum assets, while the
wireline operators can further expand the reach of their services.
5.2 SW
Considering the two architectures decribed in Section 4 the Vendor shall offer all radio
functionalities necessary to fully interoperate with the two solutions identified. Any missing
functionality not priced and listed in the Vendors proposal which prevents in part or totally
the correct interwork with the two solutions will be completely free of charge for H3G. Commented [MS(-I3]: Carlo

All Network Elements shall be equipped with the SW needed for best performance,
(capacity and coverage maximization) and easy tuning and optimization (e.g. ANR).
Nokia software features like UL IRC receiver feature introduce an IRC (Interference
Rejection Combining) receiver in UL for interference rejection. It is targeted to further
improve the UL performance in network scenarios with spatially colored interference. This
feature allows H3G to serve more UEs in UL - direction, due to the improved performance
and quality.
The application feature 29 km cell range increases the coverage area and can be extended to
77km with the Cell radius max 77 km SW feature if required.
ANR feature supports the automatic setup of neighbor cell relations in LTE (intra /inter-
frequency) triggered by any LTE user equipment (UE). The ANR feature works for intra LTE
intra-frequency and inter-frequency use cases with respect to generation of an inter-frequency
PCI/RF/IP address look-up table, and intra-frequency usage in the eNodeB per cell.
The Vendors shall describe in details and offer all the functionalities useful in order to
improve the capacity and/or the coverage of the system. The improvements figures shall be
declared and should come from field measurements if available and/or simulation results. Commented [MS(-I4]: Carlo

No specific license limitations on number of Connected Users and throughput shall be
present in the offer.
Annual SW upgrade (testing and rollout) shall be offered.
For details refer to the pricing file.
5.3 OSS

Date: 13-Apr-2016 H3G, 2017 Pag. 13 of 31

The vendor shall provide at least two OSS fully redundant high-availability, carrier-grade
servers, capable to monitor all the LTE-TDD eNodes installed, to be placed in two different
data centers.
Nokia NetAct supports and proposes Disaster Recovery solution which offers increased
protection against manmade and natural disasters. The Disaster Recovery solution locates two
NetAct clusters in different data centers, supporting unlimited distance between the data
centers. With this design, a disaster at one site does not disable the entire solution; operations
can be restarted using a standby system. A disaster can be any event that unexpectedly
interrupts service in an entire data center, such as a fire, earthquake, severe problem in a
network connection, human error, or an act of sabotage.
Main requirements for OSS are:
Compliancy to FCAPS model, offering the typical Fault, Configuration, Accounting,
Performance, Security framework
Nokia Response: Partially Compliant

Nokia NetAct FCAPS model supports Fault, Configuration, Adminstration, Performance and
Security management. However, Accounting is not supported in NetAct.
For more details, refer to Nokia NetAct_Product Description.pdf.
The OSS SW shall be aligned with the eNode LTE SW and shall be tested together.
Nokia provides the aligned and well-tested software which is to be deployed in operational
environment.
OSS Northbound interfaces shall be 3GPP compliant
All the northbound interfaces proposed in the current solution are 3GPP compliant.
OSS shall support commercial HW provided by major supplier (e.g. HP, Oracle,
IBM)
Nokia NetAct proposed in the current offer is based on HP hardware and Linux operating
system with oracle database. Below mentioned are some details of the NetAct hardware:
Servers, Rack and Chassis of HP
Storages of EMC VNX
DCN - Routers of Cisco and Switches of HP
The OSS systems shall provide a Configuration management tool, through which it
shall be possible, also by mean of automated scheduled jobs to:
- collect and read the history of projected configuration
- collect and read the history of implemented configuration

Date: 13-Apr-2016 H3G, 2017 Pag. 14 of 31

- retrieval of parameter configured in the live network
- retrieval of HW/SW in live network (Network Inventory)
- GUI and text/file editor which allow insert/modify/delete the project
configuration
- configuration script generation
Nokia NetAct Configurator offers comprehensive functionality for configuration management
with common processes and data storage in multi-technology radio networks. Automated
network planning and network consistency checking actions can be carried out with easy-to-
use tools. NetAct Configurator enables flexible and automatic workflows for fast network
roll-out and expansions as well as controlling the related processes. The configuration
management application provides a various set of tools to perform different configuration
related tasks in the network.
With CM History feature in configuration management, a user can track parameter
changes in the network in order to analyze configuration related problems, moreover,
the history report results can prove useful when planning future configuration
changes
CM History keeps record of every configuration change in the network as all the
configuration changes are updated in Configurator database via events or upload. A
specific synchronize operation ensures that the latest information in CM History
corresponds the content of the online Configurator database. CM History records are
stored both for actual and reference configuration
CM Editor tool in configuration management application is used for creating, editing
and visualizing configuration plans and templates as well as managing and
manipulating parameters (minor edit to mass modification) configured in the live
network
Hardware inventory management is integrated into NetAct Configurator tools. This
enables easy access to hardware inventory data due to rich data browsing feature set
of Configurator. A dedicated CM Editor view to view only hardware data of network
elements is pre-defined. The centralized Hardware Management facilitates operating
the network more efficiently, thus achieving savings and building a reliable balance
sheet of network assets. The operator can handle daily software management tasks
easily with the help of NetAct SW Manager and NE Backup tool. With the help of
XML based inventory data export NBI offered in the current solution, all this
inventory information both HW and SW can be sent to the 3rd party systems.
CM Editor tool in configurationa management application is used for creating, editing
and visualizing (GUI) configuration plans and templates as well as managing and
manipulating parameters (minor edit to mass modification)
Nokia NetAct configuration management application functionalities support
configuration script generation
Comprehensive set of performance counters shall be available in 3GPP format


Date: 13-Apr-2016 H3G, 2017 Pag. 15 of 31

Nokia NetAct supports the performance data in XML format which is 3GPP compliant.
Network element counters for performance management are compliant with industry
standards and most of them are compliant with 3GPP 32- series.
Tracing capability and traces analysis (cell and IMSI tracing)
Nokia NetAct supports Trace based Troubleshooting for LTE feature which allows to activate
and then manage subscriber traces and cell traces for LTE radio network (eNB). Based on the
traces operator can provide deep analysis and find the root cause of the problem in LTE
network or solve the subscriber complaints.
Bulk alarm exporting in text/csv file format
3GPP Rel6 CORBA FM NBI is offered in the current solution for exporting alarms from
Nokia NetAct to 3rd party systems.
5.4 Services
5.4.1 Installation and commissioning
The vendor shall ensure and shall be responsible for
correct installation of HW, using qualified and certified personnel
correct configuration of eNodeBs parameters as by design phase
correct integration of eNodeB in H3G Network
eNodeB visibility in OSS
5.4.2 Network O&M Services

Two possible scenarios are requested for quotation:
A. Full O&M turn key service, where the Vendor is responsible for first level
maintenance service (swap and repair field service), spare part management,
second level support service (network monitoring, troubleshooting, field
dispatching, trouble ticketing to 3rd level) and 3rd level support service (help desk,
remote troubleshooting, fault fixing)
B. Mixed scenario where the Vendor is responsible for field service, spare part
management, and 3rd line support, while H3G/Outsurcer is in charge of second
level network operation.
Nokia Response: Noted
5.4.2.1 Spare Parts Management

The vendor shall provide the car kit for FSA people. What boards must be included into
the car kit shall be proposed by vendor and agreed with Outsourcer people. The Number of
Car kits must be such to maintain H3Gs OOS events to a minimum as in estimated to be at

Date: 13-Apr-2016 H3G, 2017 Pag. 16 of 31

least 50 kits and in any case dimensioned to grant faulty HW replacement SLA specified in
first line maintenance services.
The vendor shall provide a Swap repair service of replacing faulty cards and is
responsible for the management of its centres for faulty cards reception and repairing. Vendor
is responsible for packing and shipping faulty HW to its repair center and to store repaired
parts and spares in its own wharehouses or the appropriate destination as requested by H3G
5.4.2.2 First Line Maintenance Service

The vendor shall provide a First Line Maintenance Service to provide an ON SITE service
to replace faulty cards. The vendor will provide a service with a 4 Hour SLA (Ticket open to
Ticket Close and enodeB correctly working) for urban/suburban sites (60% sites) and an 8 Hour
SLA for rural Sites (40% Sites).
5.4.2.3 Second level support Service Commented [MS(-I5]: Saverio
Second line support include network monitoring, fault management, fault diagnosis and/or
monitoring made necessary to solve the system problem. The fault analysis may lead to a remote
action (3rd level support escalation) to solve the problem and/or coordination with first line
management for troubleshooting and/or problem fix.
5.4.2.4 Third level support Service

Third line support include:
Help desk service (Advice, Consultation and Guidance, Trouble ticket collecting,
coordination of engineers or experts for fault fixing)
Technical support (remote or if necessary on site troubleshooting, fault
neutralization according to SLA)
Software correction service (if required by fault analisys/solution emergency
patching for fault neutralization according to SLA, loading of emergency patch on
faulty network elements)
Nokia Response: Compliant.
For compliance on SLA refer to response for clause number 10.4.2
5.4.3 Engineering Support Service

Equipment vendors shall provide over time technical support for
Performance Tuning / Optimization
Parameter change (scripts for massive changes)
Change Request definition (to change non optimal SW behaviours)
Test bed and field acceptance activities related to new SW (main release and/or
maintenance release), new configuration, new HW including IoT between NW
equipment and existing and/or later introduced CPEs)Massive roll-out of new
SW releases and of Maintenance SW releases

Date: 13-Apr-2016 H3G, 2017 Pag. 17 of 31

KPIs definition for a complete supervision and management of the system as
better described uin next section
Scope of IoT shall be limited to 2 months per year
5.4.3.1 Performance evaluation, KPI, enhanced diagnostic

Supplier shall provide a comprehensive set of KPI (Key Performance Indicator) formulas,
detailing counters, counters stepping logic and any other relevant information. Proposed
KPIs must cover at least the following topics:
Cell Availabilty Time / Percentage
Accessibility Success Rate
Abnormal TDD-LTE session release rate (Drop FR%)
Data Volume Exchanged (Downlink / Uplink)
Average LTE power utilization
Average number of LTE connected user
Average number of active LTE users (e.g. with data on DL / UL buffer)
separately for DL and UL
UL Noise level (PUSCH / PUCCH)
Average Baseband resource utilization
Average Radio resource utilization
Synchronization quality
S1 discarded / loss Ethernet Frames
Air interface NACK rate
Reported CQI levels distribution
MIMO (rank) usage level
MCS (Modulation Code Scheme) distribution
Average scheduled LTE-TDD cell data throughput (separately for DL and UL)
Average user LTE-TDD data throughput (separately for DL and UL)
Average user LTE-TDD data throughput (separately for DL and UL) excluding
transients (e.g. speedtest like measurements)
User LTE-TDD data throughput distribution (allowing k-th percentile
evaluation), seperately for DL and UL, if available
Any additional KPI / formula able to address:
Congestion events
Traffic loss
Service degradation (sleeping cells, poor synchronization, excessive interference,
unstable interfaces / boards etc.)
Report Operating Period (ROP) files should be available with 15 min. granularity.
Since the LTE-TDD FWA service should perceived by customers as a solid ADSL
alternative, any other enriched diagnostic, e.g. to troubleshoot / analyze end-user

Date: 13-Apr-2016 H3G, 2017 Pag. 18 of 31

performance (signal level, speedtest like throughput, CPE issues etc.), preferably in a real-
time fashion, should be described and offered as part of the solution. Commented [MS(-I6]: Carlo - CPE

For details refer to Nokia LTE Performance Measurements and Key Performance
Indicators.xls.

Date: 13-Apr-2016 H3G, 2017 Pag. 19 of 31

6 CPE Technical Requirements Commented [MS(-I7]: Carlo - CPE
Two main typologies of CPEs shall be provided

1. Indoor CPE: an indoor WiFi router supporting TD-LTE in Band38
2. Outdoor CPE: an outdoor installable equipment which shall allow to reduce
Building Penetration Loss experienced by the user, as well as shall use antennas
with higher gain (possibly sectorial beam) with respect to Indoor CPEs. Two
subtypologies have been furtherly identified
a. Integrated WiFi module: the CPE is an outdoor WiFi router supporting
TD-LTE in Band 38
b. Indoor WiFi module: the CPE is composed of an external modem,
supporting TD-LTE in band 38 (to improve indoor coverage) connected
to an indoor WiFi router via a cable
The main requirements for CPEs defined above are listed in the enclosed Excel file.
The vendors shall fill in all the field of the relevant worksheets
3ITA-CTO-TH-Technic
al requirements CPE TDD_v5.xlsx
6.1 External antennas

In order to increase the indoor coverage, H3G is evaluating the possibility to adopt an
external antenna.
The main requirements for the antenna are listed in the Excel file enclosed below.
The vendors shall fill in all the field of the relevant worksheets
3ITA-CTO-TH-Technic
al requirements LTE TDD External antenna_v5.xlsx

Date: 13-Apr-2016 H3G, 2017 Pag. 20 of 31

7 Expected Performance Commented [MS(-I8]: Carlo
The following performance figures shall be provided by Vendors

A. Theoretical User peak bitrate (UL/DL from config data)
The proposed Flexi Mutiradio 10 BTS has a Peak DL throughput is 110 Mbit/s, Peach UL
throughput is 20 Mbit/s per cell with MIMO 2x2. The peak DL throughput with MIMO 4x4 is
220 Mbit/s per cell.
B. Good Coverage User Bitrate (UL/DL)
C. Cell Border User Bitrate (UL/DL)
D. Average Cell Throughput (UL/DL Capacity) Commented [MS(-I9]: Carlo
All the values shall be as measured from real networks, if available. If figures coming
from live networks are not available, the Vendors shall provide results from simulations,
specifying the simulation process and tools adopted.
For real networks data, the technical solution shall be fully characterized by providing the
relevant set of data as the Inter Site Distance, EUTRAN configuration, RF configuration,
Bandwidth, CPEs charateristics, typical land usage data etc.
For simulations purpose the following assumptions shall stand:
Bandwidth 20MHz
UL-DL configuration 2 scenarios shall be evaluated
Downlink-to-
Uplink- Subframe number
Uplink
downlink
Switch-point
configuration
periodicity
0 1 2 3 4 5 6 7 8 9
1 5 ms D S U U D D S U U D
2 5 ms D S U D D D S U D D
The table above is extracted from 3GPP TS36.211 Table4.2-2
Special subframe configuration The best configuration supported by UTRAN equipments shall be selected from table
4.2-1 in 3GPP TS36.211 in order to maximize DL cell throughput, still matching with
ISD constraints
CPE Both indoor and outdoor CPEs, with both 2R and 4R, as from previous section 6, shall
be considered in simulations
Site RF configuration PTX as from technical offering (80W)

Antenna Gain = 18dBi, Feeder Loss=2dB, NO TMA
ISD Varying in the range [800m 2000m] with special focus on ISD=1400m
Network Load 3 Scanarios shall be evaluated

Low load: 20%
Medium Load: 50%
High Load: 90%

Date: 13-Apr-2016 H3G, 2017 Pag. 21 of 31

The table below shows the scenarios to be evaluated.
The vendor is requested to fill up the following tables with A, B, C, D performances
figures as defined above. The Vendors shall detail and specifiy where the performances
figures come from (simulation, field measurements,..)
Moreover the Vendor is requested to add other scenarios considering any other HW e SW
functionalities which are supposed to bring further improvements.
CPE A B C D
eNodeB UL:DL UL:DL UL:DL UL:DL

Type #Receivers
1 2 1 2 1 2 1 2
Indoor 2R (MIMO 22)

2T2R
Outdoor 2R (MIMO 22)
2R (MIMO 22)
Indoor
4R (MIMO 44)
4T4R
2R (MIMO 22)
Outdoor
4R (MIMO 44)
7.1.1 Evolution Scenarios

The Vendor shall consider any evolutions (both HW and SW) foreseen in its roadmap in a
time frame of 5 years which will increase the performances of the systems (e.g. MIMO 8x8,
Massive MIMO, etc.).
The proposed HW has been considered keeping in mind the future evolutions (both HW and
SW). The features and functionalities in the Nokia roadmap will be evaluated and deployed as
per H3Gs requiremnts.
Performances increase shall be described and performances figures provided considering
the CPE listed in the above table and more powerful CPE if any. Commented [MS(-I10]: Carlo - CPE

Date: 13-Apr-2016 H3G, 2017 Pag. 22 of 31

8 Commercial Trial Project
In order to better assess performance in live network functioning, H3G will start a
commercial trial in some small towns.
Once the system will be fully tested and integrated in H3G network, real commercial
proposals will be offered to H3G customers.
This project will involve a number of towns in the range of 3 to 5 (about 20 eNodeBs).
In the context of such a trial, the vendors shall provide:
HW supply, installation and commissioning
MIMO 4x4 and 4 way receiver diversity shall be implemented and
performances evaluated (comparing MIMO 2x2 and 2 way Receiver
diversity)
SW Functionalities needed for performances increase (as declared by the
vendor) shall be evaluated
CPEs will be provided by both H3G and the Vendor. CPEs 4T4R shall be
available as far as outdoor CPEs. Commented [MS(-I11]: Carlo
Lab test for IOT with H3G network and with CPEs
Field test
- Collecting measurements via OSS and Drive Test
- Perfomance tuning
- Coverage and capacity measurement
- Results reporting
Proper counters for systems monitoring shall be identified and activates, KPI
shall be designed and implemented and integration with Radio and CN
monitoring systems will take place.
Complete management of the system shall be in charge of the vendor.

Date: 13-Apr-2016 H3G, 2017 Pag. 23 of 31

9 Deliverables Commented [MS(-I12]: Marta
Delivering of the following documents shall be considered mandatory to allow H3G to

evaluate the technical proposals. Vendors not delivering one or more of these documents shall
not be taken into account during the evaluation phase
Detailed Product Technical Description for EUTRAN HW and SW features
- Vendor product documentation
- 3GPP compliance status (specify the currently supported release)
- Compliance status for all of the sections of the present document
- Roadmaps
Detailed Product Technical Description for proposed CPEs
- Vendor product documentation
- Excel files attached to section 6 filled in
- Timeframe availability and middle-term roadmaps for both CPEs and
external antennas
Detailed Description of OSS
Documents describing KPIs formulas as per paragraph 5.4.3.1
Pictures and pdf files of the final site solutions (it should appear clear the size of
the final site using the Vendors HW products available) for two site
configurations:
- 3 sectors, MIMO 2x2, 40+40W
- 3 Sectors, MIMO 4x4, 20+20+20+20W
Heritage from commercial LT-TDD Networks for both MBB and FWA services
Coverage and capacity estimation as described in section 7. The documents shall
show the details of calculations/simulations and highlight the impact of System
configuration on coverage, peak rate and capacity. The Vendor should consider
the possibility of sharing proprietary tools for network dimensioning and
simulation
In order to demonstrate their own heritage from existing live networks using TD-
LTE (if any), the vendor shall provide on field measurements supporting
theoretical computations for coverage, peak rate and capacity
Roadmaps

Date: 13-Apr-2016 H3G, 2017 Pag. 24 of 31

10 Quantities
Different scenarios have been targeted by H3G involving different quantities for
EUTRAN equipments and CPEs.
The scenarios are described below and provide the main canvas for commercial proposal
from vendors.
10.1 EUTRAN
For EUTRAN deployment, four main scenarios shall be considered
A. 1000 sites deployed in 2 years
B. 2000 sites deployed in 2 years
C. 3000 sites deployed in 3 years
D. 4000 sites deployed in 3 years
The deployement can be assumed to be linear in time, so sites per year are easily derived
from figures above.
Foar each of the 4 scenarios above, 4 subscenarios shall be considered, each with a
varying percentage of 4T4R eNodeBs supporting MIMO 44,
1. 0% of eNodeBs shall support MIMO 44 (All eNodeBs shall support 2T2R
only)
2. 30% of eNodeBs shall support MIMO 44
The table 10.1-I below summarizes the above scenarios and provide the canvas for the
matrix to fullfill by vendors for commercial proposal

Date: 13-Apr-2016 H3G, 2017 Pag. 25 of 31

Scenario/Rollout Ref. ID 4T4R eNodeBs
A1 0%
A
A2 30%
1000 sites in 2
A3 60%
years
A4 100%
B1 0%
B
B2 30%
2000 sites in 2
B3 60%
years
B4 100%
C1 0%
C
C2 30%
3000 sites in 3
C3 60%
years
C4 100%
D1 0%
D
D2 30%
4000 sites in 3
D3 60%
years
D4 100%
Table 10.1-I Summary of deployement scenarios


Date: 13-Apr-2016 H3G, 2017 Pag. 26 of 31

10.2 OSS
For each of the 4 deployment scenarios A, B, C and D described in section 10.1, the
vendor shall provide HW, SW and I&C for full management of the Radio Network, with full
support for requirements in section 5.3
Nokia NetAct management system is offered with full support of requirements as per section
5.3 in all the 4 deployment scenarios A, B, C and D for the H3G network.
The vendor shall guarantee that no operative limitation will be imposed by the OSS
configuration and/or dimensioning.
Nokia NetAct imposes as such no limitations but of course there are some general
recommendations regarding the environment in which NetAct is to be operated. For example:
temperature range, humidity, etc. All the details regarding these specifications will be povided
to the H3G at the time of system delivery.
10.3 CPE Commented [MS(-I13]: Carlo- CPE
For CPEs, three main scenario shall be considered

A. 50,000 CPEs in 1 year
B. 200000 CPEs in 2 years
C. 400000 CPEs in 2 years
For each scenario above, two working hypotheses stand

Hypothesis I: Indoor only CPEs
Hypothesis S: split consisting of 40% Indoor CPEs and 60% of Outdoor CPEs
shall be considered.
For each case above, an additional splitting over the number of receive antenna shall be
considered
1. 100% 2R CPEs
2. 50% 2R CPEs + 50% 4R CPEs
3. 100% 4R XCPEs
The table 10.2-I below summarizes the above scenarios and provide the canvas for the
matrix to fullfill by vendors for commercial proposal

Date: 13-Apr-2016 H3G, 2017 Pag. 27 of 31

Indoor CPEs Outdoor CPEs
Scenario Ref. ID
2R 4R 2R 4R
A.I.1 50000 0
A
50000 A.I.2 25000 25000
CPEs
A.I.3 0 50000
B.I.1 100000 0
Indoor only CPEs
B
100000 B.I.2 50000 50000
CPEs
B.I.3 0 100000
N.A.
C.I.1 200000 0
C
200000 C.I.2 100000 100000
CPEs
C.I.3 0 200000
D.I.1 400000 0
D
400000 D.I.2 200000 200000
CPEs
D.I.3 0 400000
A.S.1 20000 0 30000 0
A
50000 A.S.2 10000 10000 15000 15000
40%Indoor / 60%Outdoor CPEs
CPEs
A.S.3 0 20000 0 30000
B.S.1 40000 0 60000 0
B
100000 B.S.2 20000 20000 30000 30000
CPEs
B.S.3 0 40000 0 60000
C.S.1 80000 0 120000 0
C
200000 C.S.2 40000 40000 60000 60000
CPEs
C.S.3 0 80000 0 120000
D.S.1 160000 0 240000 0
D
400000 D.S.2 80000 80000 120000 120000
CPEs
D.S.3 0 160000 0 240000
Table 10.2-I Summary of CPEs quantities per scenario

Date: 13-Apr-2016 H3G, 2017 Pag. 28 of 31

10.4 O&M
For each of the 4 deployment scenarios A, B, C and D described in section 10.1, the
vendor shall provide the O&M Service as described in section 5.4.1.
10.4.1 Definitions
The SLAs defined in tables 10.4.1-I and 10.4.1-II shall be applicable in the scenarios A
and B as described in section 5.4.2.
The following classifications for incidents will stand
Critical incidents are problems which severely affect service, capacity/traffic, billing,
and data process capabilities. Critical problems require immediate corrective action,
regardless of time of the day or day of the week.
For example:
- A total system failure
- 15% or more reduction in traffic capacity or data process capability
- Any harm to person due to the use of the equipment
Major incidents are problems which seriously affect system operation, maintenance
and administration. Major problems require immediate attention and succeeding
planned corrective action. The urgency of major severity is less than of critical
severity because of a less immediate or impending impact on system performance,
end-users, operation and revenue.
For example:
- 10% to 15 % reduction in traffic, capacity or data process capability
- Reduction in measurement function for capacity/traffic
- Any loss of diagnostic capability and/or visibility of management or
maintenance
- Degradation of the systems ability to raise critical or major alarm
- Billing error rate exceeds acceptable value
- Performance reduction of billing or system databases
Minor incidents are problems that are not viewed as critical or major. A minor
problem may have impact on one or limited number of users. Minor problems neither
significantly impair the functioning of the system nor significantly affect service to
end-users. These problems are tolerable during system use.
Also, the following definitions are valid

On-Time Delivery shall mean the percentage of order/items accepted on the
customer requests. It measures timeliness of delivery of services to customers.
Official Fix Time shall mean the interval from receiving the request from
customer to the time when the problem is eliminated with a permanent solution.

Date: 13-Apr-2016 H3G, 2017 Pag. 29 of 31

Response Time shall mean the interval from receiving the request from customer
to the time of the first telephone reply from ZTE personnel.
Restoration Time shall mean the interval from receiving the request from
customer to the time when the impacted function/business is restored or
neutralized. It is also named as Neutralization Time.
CD means Calendar Days
10.4.2 Service Level Agreement

The SLAs defined in tables 10.4.2-I and 10.4.2-II shall be applicable in the scenarios A
and B as described in section 5.4.2.
1st Level 2nd Level
98% of the faults shall be managed and solved within 4HH

100% of the faults shall be managed and solved within 8HH
A
Solving time shall be meaured starting at first alarm detection by
2nd Level Support Team
98% of the faults shall be managed and solved

within 4HH
100% of the faults shall be managed and solved
B within 8HH N.A.
Solving time shall be meaured starting at ticket

opening by H3G Outsourcer in charge of 2 nd Level
Support
Table 10.4.2-I SLAs for 1st and 2nd Level Support
Incident type
Critical Major Minor
Service Availability 7x24 7x8 5x8
Response Time 15min 30min 30min
Restoration Time 4 HH 8 HH 10 CD
Official Fix Time 3 CD 15 CD 30 CD
Official Fix Time
30 CD 90 CD <180 CD
(if escalated to R&D)
On-Time Delivery 100% 98% 95%
Language English/Italian
Table 10.4.2-II SLAs for 3rd Level Support

Nokia Response: Partially Compliant.

Date: 13-Apr-2016 H3G, 2017 Pag. 30 of 31

Nokia guarantees a compiance level of 90%, The default support language is English. Major
tickets will be managed on a 5x8 bases. Refer to table below for SLA offered by Nokia.
Service Category Action GOLD
Initial response 1h
Major fault Prio1 Workaround 2wd
Final Correction 4 weeks
Initial response 1h
Trouble Resolution Medium fault Prio2 Workaround 1week
Final Correction 2 months
Initial response 8h
Minor fault Prio3 Workaround n/a
Final Correction 4months
Initial response 4h
Urgent request
Answer 3wd
Technical Query
Initial response 1wd
General request
Answer 1week
Service Category Action GOLD
Emergency Remote Initial Response 15min

Critical
Support
Restoration 4h

Date: 13-Apr-2016 H3G, 2017 Pag. 31 of 31

TD-LTE FWA Technical Requirements

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TD-LTE FWA Technical Requirements

Uploaded by

Copyright:

Available Formats

TD-LTE for Fixed Wireless Access

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 1 of 31

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 2 of 31

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 3 of 31

Version Author Description Staus Date

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 4 of 31

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 5 of 31

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 6 of 31

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 7 of 31

4.1 Architecture Overview

4.2 Subscriber base separation

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 8 of 31

Nokia Response: Compliant

4.2.1 Solution A Tracking Area - Roaming Restriction per IMSI range

Different TAC for LTE RAT

Figure 1: Roaming restrictions per TAC/IMSI range

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 9 of 31

Served PLMNs for LTE RAT:

Figure 2: Separate PLMN id solution (simplified architecture)

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 10 of 31

5.1.1 Basic Configuration

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 11 of 31

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 12 of 31

Nokia Response: Compliant

Nokia Response: Compliant

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 13 of 31

Nokia Response: Partially Compliant

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 14 of 31

Comprehensive set of performance counters shall be available in 3GPP format

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 15 of 31

5.4.2 Network O&M Services

5.4.2.1 Spare Parts Management

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 16 of 31

5.4.2.2 First Line Maintenance Service

5.4.2.3 Second level support Service Commented [MS(-I5]: Saverio

5.4.2.4 Third level support Service

5.4.3 Engineering Support Service

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 17 of 31

5.4.3.1 Performance evaluation, KPI, enhanced diagnostic

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 18 of 31

Nokia Response: Compliant

Document Title Version: 1.1 File

Date: 13-Apr-2016 H3G, 2017 Pag. 19 of 31

Two main typologies of CPEs shall be provided

6.1 External antennas