2nd Carrier Success A1

17
2 nd Carrier Deployment Success in NY MTA H1 2010

Transcript of 2nd Carrier Success A1

Page 1: 2nd Carrier Success A1

2nd Carrier Deployment

Success in NY MTA

H1 2010

Page 2: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 2 (13)

Ny MTA Project scope

› 1600 Sites Target for 2nd Carrier Activation– 1000 Sites – Ericsson– 600 Sites – T-Mobile

› Project was concurrent work with AAV deployment– Teams performed installation of all hardware (both AAV and 2nd Carrier)

› SCOPE OF WORK (2nd Carrier)– Hardware deployment (1000 sites Ericsson)– Scripting (Ericsson)– BSS Checks (added to Ericsson)

› Validation of parameters against hardware (transport, node B, etc.)– Cluster Activation (Ericsson)

› Ericsson provided:– Hardware deployment teams– Remote scripting teams– Local RF support– Remote UTRAN support– Project Management resources

Page 3: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 3 (13)

2nd carrier add High Level process

Site List +RND CIQ

Scripts to create 2nd Carrier cells & Hybrid in

RNC/NodeB

Script Implementation

H/W Installed

Create Neighbor Lists

Create Neighbor Scripts

Implement Neighbor Scripts

Validate Neighbor Load

BSS Check

RTT?Cluster

?

Activate

Clear Alarms / Site Visit /

Re-Load Scripts

NOK

OK

OK

T1’s / Neighbor Revision

NOK

OK

NOK

T-Mobile

Ericsson

On Air

OK

Page 4: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 4 (13)

NY KPI Trends – 2nd Carrier IMPACT

CS NAF RATE

CS DCR RATE

Mac-HS THRoughput

ADM REJECT LACK DL Power

1st Major 2nd Carrier Cluster

launch

CS NAF Steady/Improving

CS DCR Steady/Improving

MAC-HS Throughput Daily

Average increased ~13%

Significant improvement in

raw access failures, admission due to DL power

CS DCR RATE

1st Major 2nd Carrier Cluster

launch

1st Major 2nd Carrier Cluster

launch

1st Major 2nd Carrier Cluster

launch

Page 5: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 5 (13)

Feedback from The Market› From: Bulleri, Roberto [mailto:[email protected]]

Sent: Monday, June 28, 2010 10:06 AMTo: Nader Sheikh; Kevin Leslie; Tom PrzelomiecCc: Nelson Lucier XX; Shaun Pola; John Divilly; Sean Ward X; Mohammad EdaibatSubject: FW: F2 H1 Project "1600" NYMTA Meeting 06.25.10

Nader, Kevin, Tom,› I would like to extend a huge Thanks on behalf of the TMO team to you for the invaluable help and dedication received by your respective direct reports.› I have 11+ years in Telco over 11 different countries and few times I have seen such dedication and commitment.› We exceeded our goals thanks to Sean, John, Mohammad, Nelson and Shaun who consistently went above and beyond.›   › Thx,›  › Roberto Bulleri› NYC Market› T-Mobile› GSM (973) 704-0040› Desk (973) 292-8781› Fax (973) 292-8864› 4 Sylvan Way› Parsippany, NJ (07054) › USA›   ______________________________________________ › From:    Bulleri, Roberto  › Sent:   Friday, June 25, 2010 2:49 PM› To:     Frisch, Mark; Manzo, Nelson; Kumar, Jay; Reehal, Kanwal; Moldoveanu, Cristina; Czumbil, Bob; Fleitas, Roger; Vieira, Luis; Butler, Billie (BJ,  BSS);

Potoczny, Joseph; Krum, Wayne; Williams, Audie (Shannon); D'aleo, Frank; Schuck, Steve; Palmer, Steve; Alcamo, John; Caliente, Christian; Koppa, Rajesh; Heller, Jeff; Hernandez, Marcos; Thomas, Shawn; Tully, Brian; McCord, Adam; Kashefska, Sergie; Jain, Devendra; Ramos, Enrique; Li, Terence; Daniel, Omar; Dragomir, Costel; Mookuparambil, Ruben; Kouidri, Salim; Jalal, Shah; Arceo, Neil; Genova, Tommy; Russo, Jason (NYC OPS); Luke, Stephanie; Ellis, Ian; Tuquero, Jovito; Link, Jonathan; Cooleen, Tom; Wadhwa, Kartar; Kuo, Barry; Gonibeed, Ashwin; Cotter, Michael; Celebi, Bilal; NJ Field Supervisors; Karram, Raymond; Panchal, Raju; Polen, Alison; Wells, Tony; Pino, Ariel; Patel, Kalpesh; Wolak, Joseph; Hewes, Krista; Hoefling, Hans "Chris"; Arrow, Alissa

› Cc:     Ellefson, Tom; Rentko, Roberta› Subject:        F2 H1 Project "1600"  NYMTA Meeting 06.25.10›  ›  › I would like to thank every one of you who contributed to the success of the 2nd Carrier Project.› Thanks to your effort today we have 1,553 2nd Carriers On Air, which represents 95% of our total planned pool for H1 (1644).› Our Power Congestion has been significantly reduced, and our Customer experience substantially improved in terms of Accessibility and Throughput.›   › Thx,

Page 6: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 6 (13)

Lessons learned› 1. ONE TEAM!

– Project was conceived as ~60/40 split for “E///” & “T-Mobile” sites.– This was a nightmare to manage as sites moved through the process from install to activation. The project

process flow evolved to best practice of one team working together. › 2. TURN UP SITES IN LARGE CLUSTERS!

– Initial plan was to keep the 2C cells turned down until signs of congestion on 1C. This resulted in ad hoc turn up and KPI’s suffered.

– Clustered activation of sites was recommended by Ericsson from Day1 and proved to be the best way forward for this project also.

– A safety net approach is recommended here, to limit the traffic on 2C layer through conservative re-selection parameter settings. As the 2C layer is optimized these parameter settings are relaxed to balance the load between layers whilst maintaining an excellent user experience.

› 3. BASELINE PARAMETERS AT THE START!– Baseline parameters for HSPA+ & 2C activation were not established early enough for this project, causing

extensive parameter updates prior to 2C activation– This was a symptom of implementing concurrently with HSPA+ activation program, and also a result of being the

first major 2C rollout in the T-Mobile network,– Future projects would automatically benefit from this experience, and the RND CIQ template has been updated

to capture the required HSPA+/2C parameters during scripting process.› 4. NEIGHBOR MANAGEMENT A MUST!

– Always a challenge in a live network environment– Due to ongoing 1C optimization and the fact that 2C cluster definitions were dynamic as a result of various

factors creating delay (site access for install, T1 delivery, etc)…. the 2C neighbor lists are defined, scripted and loaded as late as possible in the process prior to activation.

– Project team developed a new neighbor management tool (macro) to support this need for J-I-T neighbor list creation

Page 7: 2nd Carrier Success A1
Page 8: 2nd Carrier Success A1

BACK UP SLIDES

Page 9: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 9 (13)

RBS 3106 Capacity Expansion3x1 (40W) => 3x2 (40W)

Radio:3 FU12

+ 3 RU22 40W

Baseband: 1 HS-TX45

+ 1 RAX 2e

Cables: PDU-RU + AUH-PSU

+ RU-RUIF + PSU-Power Bar+ RU-FU + PSU-ACCU

Power Supply Unit (PSU)

UT31E3CA

3106 3x1 40W (AC)UT31HA

3106 3x2 40W (AC)UT31HA + UT31E3CA

Transmission: 1 ET-MFX11

Optional

Page 10: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 10 (13)

RBS 3206 Capacity Expansion3x1 (40W) => 3x2 (40W)

Radio:3 FU12

+ 3 RU22 40W

Baseband: + 1 HS-TX45+ 1 RAX 2e

98

FCU

DC-filt/DCCU

24

ACCU/DCCU

48

B

P

P

P

P

P

FU

1

FU

3

FU

5

AUH

Cable shelf

PDU1

RU

1

RU

3

RU

5

Cable shelf

CBU

RUIF

TXB

RAXB

Cables: PDU-RU

+ RU-RUIF+ RU-FU

Transmission: 1 ET-MFX11

Optional

98

FCU

DC-filt/DCCU

24

ACCU/DCCU

48

B

P

P

P

P

P

FU

1

FU

3

FU

5

AUH

Cable shelf

PDU1

RU

1

RU

3

RU

5

Cable shelf

CBU

RUIF

TXB

RAXB

FU

2

FU

4

FU

6

RU

2

RU

4

RU

6

RAXB

TXB

ETMFX11

UT32H48ARadio: 3x1 40WBaseband: 1 HS-TX45, 1 RAX R2e Transmission: 4 T1

UT32H48A + UT32E3C48ARadio: 3x2 40WBaseband: 2 HS-TX45, 2 RAX R2eOptional: 4 T1 + Ethernet

UT32E3C48A

Page 11: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 11 (13)

RBS 3000 Radio Architecture3x1 Radio Configuration (AWS, 40W)

RBS Antenna Ports

RBS, Sector 1

FU12 21IV

DPX

RX

LNA

LN

A

RU22 21IV40

TX2

TX1

+

MC

PA

RX1A

RX1B

Cables

Radio Block 1

TX1 / RXA

RXB

Data 1

Baseband

Page 12: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 12 (13)

RBS, Sector 1

DPX

RX

LNA

LNA

RU22 21IV40

TX2

TX1

+

MC

PA

RX1A

RX1B

TX1 / RXA to antenna 1Data 1

FU12 21IV

RBS Antenna Ports (2)

DPX

RX

LNA

LNA

RU22 21IV40

TX2

TX1

+

MC

PA

RX1A

RX1B

TX2 / RXB to antenna 2Data 1

FU12 21IV

Radio Block 3

Baseband

RBS 3000 Radio Architecture3x2 Radio Configuration (AWS, 40W + 40W)

Page 13: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 13 (13)

Radio Cable KitsRBS 3206

1a: RPM 777 05/00600

1b: RPM 777 05/00600

2a: RPM 777 05/00600

2b: RPM 777 05/00600

3a: RPM 777 06/00420

3b: RPM 777 06/00420

4a: RPM 513 2175/00720

4b: RPM 513 2175/00720

5: RPM 513 2174/00380

RBS 3106

1a: RPM 777 05/00225

1b: RPM 777 05/00225

2a: RPM 777 05/00225

2b: RPM 777 05/00225

3a: RPM 777 06/00360

3b: RPM 777 06/00360

4a: RPM 513 2175/00500

4b: RPM 513 2175/00500

5: RPM 513 2197/00360

Page 14: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 14 (13)

MACRO RBS TYPES with HSPA/E-UL

Case Configuration HS Resources

HS-TX45

HS-TX60

DL CE/cc

RAX R2(e)

1 3X1 1 1 44 1

2 3X1 and AAV 2 2¹ 172 1 to 3¹

3 4X1 and AAV 3 2 86 2 to 3¹

4 3X2 R99 on C1 1 2 107 2

5 3X2 2 2 65 2

6 3X2 3 2 44 2

7 3X2 and AAV 3 1 1¹ 74 2 to 3¹

Assumption: R99, 16QAM,64QAM, Dyn. Code allocation, HS 32 users/cc, EUL 32 users/cc

(¹) : BOM calls for 1 HS-TX45 and 1 RAX on 3x1, 2 HS-TX45 and 2 RAX on 3x2, additional RAX and CE being added through FCP process –

Page 15: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 15 (13)

HSDPA baseband evolution (W10)

1 HS-TX45

WCDMA 3x11 HSDPA resource

2 HS-TX45

WCDMA 3x12nd HS Code Increment

WCDMA 3x23rd HS Code Increment

2 HS-TX45

15 codes1 x16Mbps

41 codes3x16Mbps

60 codes3x21Mbps

WCDMA 3x24th HS Code Increment

Multi-Carrier

2 HS-TX45

78 codes3x32Mbps

78 codes3x64Mbps

WCDMA 3x2No Code changeMulti-Carrier +

MIMO activated W11

1 DUW-30

16 Mbps* 48 Mbps* 63 Mbps* 96 Mbps* 192 Mbps** Peak layer one throughput and will vary based on cell configuration and traffic load

42Mbps

Page 16: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 16 (13)

Baseband Channel AllocationDL HW Channel Element Capacity (R99 + HSDPA + EUL)

1-15 codes

1-15 codes

1-15 codes

Sector 1

Sector 2

Sector 3

f1 (3x1)R99+HSPA32 users/cc

f2 (3x1)R99+HSPA32 users/cc

Case 6 (Two HSPA Carriers)• 2 HS-TX 45 cards• 60 HS Codes, 3 resource IDs• Dynamic Code Allocation• R99+HSDPA(32 users/cc) +

EUL(32 users/cc)

262 CE1-15 codes

1-15 codes

1-15 codes

Case 5 (Two HSPA Carriers)• 2 HS-TX 45 cards• 30 HS Codes, 2 resource IDs• Dynamic Code Allocation• R99+HSDPA(32 users/cc) +

EUL(32 users/cc)

1-13 codes

1-13 codes

1-13 codes

Sector 1

Sector 2

Sector 3

f1 (3x1)R99+HSPA32 users/cc

f2 (3x1)R99+HSPA32 users/cc

390 CE1-13 codes

1-13 codes

1-13 codes

Page 17: 2nd Carrier Success A1

Commercial in confidence | 2010-07-15 | Page 17 (13)

Baseband Channel AllocationDL HW Channel Element Capacity (R99 + HSDPA + EUL)

1-15 codes

1-15 codes

1-15 codes

Sector 1

Sector 2

Sector 3

f1 (3x1)R99+HSPA32 users/cc

f2 (3x1)R99+HSPA32 users/cc

Case 7 (Two HSPA Carriers with AAV)

• 1 HS-TX 45 + 1 HS-TX 60 cards• 60 HS Codes, 3 resource IDs• Dynamic Code Allocation• R99+HSDPA(32 users/cc) +

EUL(32 users/cc)

518 CE1-15 codes

1-15 codes

1-15 codes