Telecom Project Services - Pre-launch SSD / SSV

Software Quality Leaders
Our clients OPEX challenges are our KPIs
Telecommunication Networks – Managed Services Portfolio
TSG (Telecom Services Group) - SoftQL - 2015

Who we are
 IT and Telecommunication consulting services, Incorporated in 2001.
 Over 14 Years of Telecom and IT solutions experience.
 Based in Dallas TX, GDC in India.
 Global Clientele:
o Telecomm Operators and OEMs
o Finance, Insurance and Banking
o Manufacturing and Transportation
 Unique on-site/off-shore delivery platform
 WBENC & HUB Certified

Services Portfolio
Teleco
Managed
Services
Offshore
Consulting
Field
Services
Staffing
Solutions
Software
Applications
Solutions
Enterprise
Solutions

Telecommunication Networks – Pre-Launch
Activity

Site Shakedown (SSD) Phase
The goal of the Site Shakedown (SSD) process is to ensure sites are verified to be free of build,
equipment, installation, commissioning, and integration problems. Sites are required to be at
MS-143 (Integration Complete) stage and pass the SSD criteria before they can be included in
pre-launch tuning. All LTE launch projects, irrespective of number of sites or the nature of the
LTE project (whether initial carrier or carrier add or license protect or spectrum expansion
project) shall adhere to the requirements laid out for SSD phase.
SSV (or In-fill)
The SSV sites are individual sites that are part of a POR/POE area already in commercial service.
In-fill launch process is a more accurate description for this type of launch, but since SSV has
been a more common legacy term it is retained in this document as a substitute term for an in-
fill site. All in-fills must first pass SSD pass criteria.
Initial Carrier Site Shakedown
Site shakedown (SSD) is a name for test activities where certain technical capabilities of
the LTE site(s) are checked before the pre-launch activities can begin. Site shakedowns
shall be performed on all Initial Carrier pre-launch sites.
Cont……

SSD Test Activities
Supplier shall perform the following test activities as part of the Site Shakedown service
for each applicable site:
• Configuration data-fill audit and correction
• Measure DL and UL Throughput
• Measure physical cell ID and check for swapped feeder verification at every site
• integration.
• Handover verification.
• Measure RF Transmit (TX) Path Imbalance.
• Identify high or low UL RSSI through PM counters in case this was not addressed
• during Site integration. If necessary, the Supplier shall bring the issue to the
• party responsible for site integration.
• The Supplier shall communicate errors and issues found during shakedown that
• can be prevented from recurring in other sites to the appropriate organization
• (Turf Supplier/Supplier/Carrier) as part of a process of continuous improvement.

Golden Value Throughput Testing
(During Site Shakedown)
Supplier shall do initial golden value throughput testing to ensure there are no RAN or
transport issues impacting throughput performance.
The golden value throughput test shall be performed in a stationary environment on
each sector in a location where UEs experience optimum RF conditions defined.
The test shall be performed using the Carrier-recommended configuration for the laptop
and the test device (i.e. TCP/ IP MTU, Window size, etc) provided in the SSD Guidelines.
The following SAMPLE - LTE (example) test scenarios shall be performed with pass criteria:
· UDP DL – Pass (>=34Mbps @ 10MHz, >=20Mbps @ 5MHz) **
· UDP UL – Pass (>=16Mbps @ 10MHz, >=7Mbps @ 5MHz) **
· TCP DL – Pass (>=31Mbps @ 10MHz, >=19Mbps @ 5 MHz) **
· TCP UL – Pass (>=14Mbps @ 10MHz, >=6Mbps @ 5MHz) **
** The pass criterion is applicable to Ethernet virtual circuit capacities of 40 – 100
Mbps.
Where throughput values do not meet the pass criteria above, Supplier shall make
best effort to promptly resolve the issue else Supplier shall engage the Carrier incubation
team for further troubleshooting support.

Shakedown Status
A status shall be reported by Supplier to Carrier as :
I. Pass - No issues with any functionality
II. Fail - A functional element is unavailable, impaired or diminished where additional
troubleshooting and/or a re-visit is required.
III. Pending - Unable to complete the test; reasons might include: site
location is wrong, hardware failure, data is corrupted, drive team could
not locate the site, restricted access to a suitable test location (e.g., gated
community, military base, etc.)
The actual measured throughput values shall be provided as part of the SSD.
Supplier shall provide the status report in Excel format indicating results, number of sites
tested, pass/fail status, and, for sites that fail, an associated failure report with reasons and
next steps.

Drive Route Polygon
Standard Polygon protocol listed below;
· Carrier will provide the sites list to Supplier.
· Supplier will draw up the polygon based on ATOLL (or Carrier Preff.)
· Carrier Market RAN will be responsible for approving the polygon and any
corresponding changes.
· Carrier HQ RAN delegate will be copied in on polygon approval emails.
Drive Route Polygon Outputs
At a minimum, the drive route polygon output will have:
· MapInfo format
· Include the underlying RF coverage of each eNodeB.
· Snapshots of polygon with coverage levels
Upon approval of drive route polygons by Carrier, the Supplier shall upload the drive
route polygon(s) to Actix.

Drive Route Selection criteria
· All sectors of site or cluster sites should be
included in the drive route.
· Routes should check both inter and intra-site
handovers.
· All main streets and key customer locations
must be driven.
· Collect sufficient samples to assist in launch
decisions.
· Exit routes should extend a full 2 tiers to
verify all IRAT success. All key arteries
shall be driven with a minimum of 6-8 exit
routes per cluster (two on each
direction).
. For micro-clusters minimum of 4 exit routes
will be driven.
· IRAT extending to 2 tier boundaries shall be
included in the drive route where applicable.

Submission of Drive Routes to Market and HQ RAN
Supplier shall work closely with carrier RAN engineers on submission package. The form of
the submission package will be provided by the supplier to Carrier for approval before
project commences.
Drive Test Hardware Configuration:
To be decided and agreed by supplier and carrier.
Test Kit Configuration:
To be decided and agreed by supplier and carrier.

Software Quality Leaders
Our clients OPEX challenges are our KPIs
Thank You !!

Telecom Project Services - Pre-launch SSD / SSV

More Related Content

What's hot (20)

Viewers also liked (14)

Similar to Telecom Project Services - Pre-launch SSD / SSV (20)

Recently uploaded (20)

Telecom Project Services - Pre-launch SSD / SSV