Mop -lte2100 Addition_2017-04-09_v2
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Mop -lte2100 Addition_2017-04-09_v2 as PDF for free.
More details
- Words: 1,458
- Pages: 11
Suggested LOGO for customer
LTE2100 Layer Addition (Note: update the yellow background area content base on specific change .)
Middle East Region Customized Implementation Solution Template V5.0 Prepared by:
Anan
Date: 30/03/2017
Saleem 84031507 Reviewed by:
ZhuShiche
Date: 30/03/2017
ng 00707424 Approved by:
wangzhen0 0192668
Date: 30/03/2017
Implementation Solution for Change
Contents Live network information ....................................................... Error! Bookmark not defined.
2
3
4
1.1
Live network topology ........................................ Error! Bookmark not defined.
1.2
Business volume ................................................................................................... 4
1.3
Main existing problems ......................................................................................... 4
1.4
Remote access information ................................................................................... 4
Purpose and Requirements ................................................................................................ 4 2.1
Change purpose ..................................................................................................... 4
2.2
Change scenario .................................................................................................... 4
2.3
Change scope & scale ........................................................................................... 6
2.4
Change Period ....................................................................................................... 6
Description of Change and Change Influence................................................................... 6 3.1
NE list & version number or patch number before and after change .................... 6
3.2
Surrounding NEs and version number involved by the change ............................ 6
3.3
Change relevance .................................................................................................. 6
3.4
Description of changed software ........................................................................... 6
3.5
Description of changed hardware .......................................................................... 7
Change Preparations ......................................................................................................... 7 4.1
Composition of Change Team and Responsibility of Team Members ................. 7
Change Team of XX Company .............................................................................................. 7 Huawei Change Team .............................................................................................................. 7 Huawei Support & Guarantee Team ........................................................................................ 7
5
4.2
Check of Equipment Running ............................................................................... 8
4.3
Change Risks and Countermeasures ..................................................................... 8
4.4
Check Before Change ........................................................................................... 8
Operation Steps for Change .............................................................................................. 8 5.1
Change Steps ......................................................................................................... 8
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 2 of 11
Implementation Solution for Change
5.2
Test and Verification ............................................................................................. 9
5.3
Solution for Changeback In the Case of Failure ................................................... 9
5.3.1
Definition of Change Failure ............................................................................... 9
Definition of Change Failure ................................................................................................ 9 Rollback decision ................................................................................................................... 9 5.3.2
Overall Description of Changeback ................................................................... 9
5.3.3
Information Collection Before Changeback .................................................... 10
5.3.4
Changeback Steps ............................................... Error! Bookmark not defined.
5.3.5
Equipment Status Check ................................................................................... 10
5.3.6
Tests After Changeback .................................................................................... 10
5.3.7
Changeback Risk Analysis ............................................................................... 10
5.4 6
Change of Spare Parts and Emergency Workstation........................................... 10
Work After Change ......................................................................................................... 11 6.1
Observation ......................................................................................................... 11
6.2
Provision of Materials ......................................................................................... 11
6.3
Provision of Software.......................................................................................... 11
6.4
Training ............................................................................................................... 11
6.5
Matters Needing Attention .................................................................................. 11
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 3 of 11
Implementation Solution for Change
1.1
Business volume
LTE2100 collocating on the existing LTE1800 using RRU3953 2X80W to be SDR with U2100 which will be shifted from BTS to DBS
1.2
Main existing problems
No any existing problem
1.3
Remote access information
Remote access is not allowed generally but in case of emergency we can ask our BO guy to provide VPN information .i.e. user name and password e.t.c.
2 Purpose and Requirements 2.1
Change purpose
The purpose of the activity is to onair the LTE2100 and shift U2100 from BTS to DBS solution to be SDR UL2100
2.2
Change scenario
U2100 will be shifted from BTS to DBS using RRU3953 Existing U2100 Feeders will be dismantles Exiting WRFU/WRFUe will be dismantled U2100 and LTE1800 BBUs will be interconnected using UCI card UBBPe4 will be added to the LTE1800 BBU to be used as base band resource for LTE2100 LTE2100 bandwidth will be 10MHz Generate script including implementation and the rollback script Open RFC
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 4 of 11
Implementation Solution for Change
Scenarios involved in the solution
Generated Script and Roll Back
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 5 of 11
Implementation Solution for Change
2.3
Change scope & scale
The total scope in 4G6 will be for 864 sites, and currently to be implemented on pilot cluter Damm3 32 sites
2.4
Change Period
Change Date 2017-April-11
Change Start Time 02:00 AM
Change End Time 06:00 AM
3 Description of Change and Change Influence 3.1
NE list & version number or patch number before and after change
NE list and Version will keep same before and after
3.2
Surrounding NEs and version number involved by the change
Not involved
3.3
Change relevance
The change will occure on U2100 and LTE2100
3.4
Description of changed software
U2100 will be shifted from BTS using WRFU/WRFUe to DBS using RRU3953, LTE2100 new layer will be collocated on existing LTE1800
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 6 of 11
Implementation Solution for Change
3.5
Description of changed hardware
U2100 will be shifted from BTS using WRFU/WRFUe to DBS using RRU3953, LTE2100 new layer will be collocated on existing LTE1800 GSM900/1800, LTE1800, and LTE2300 will keep same and no change will be happen
4 Change Preparations 4.1 Composition of Change Team and Responsibility of Team Members Change Team of STC Company
Name
Job Role
Email or Telephone No.
Amir shamshad
Integration Engineer
Ameen Uddin Mohammed
Integration Engineer
0538157699 0534731505
Huawei Change Team Name
Responsibility
Arsalan Mohammed
Chief commander
Telephone No. 0530044467
Huawei Support & Guarantee Team Name
Responsibility
Telephone No. +86 XXXXXXXXX
Staff Name & ID
Supporting overall coordination as the technical expert
Staff Name & ID
Product support contact person
+86 XXXXXXXXX
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 7 of 11
Implementation Solution for Change
4.2
Check of Equipment Running
Before running the script all alarm log should be collected for the last 24 hours including RCN, NodeB, and Enode Blevel and then there should not be any alarm on hardware before start
4.3
Change Risks and Countermeasures
Not involved.
4.4
Check Before Change
No.
Preparations Before Change
Owner
Completion Date
1
Data backup
Change owner
1 day before change date
5 Operation Steps for Change 5.1
Step
Change Steps
Time (local)
Task
Owner
1
02:00-05:00
Onsite installation
Field team
1
02:00-05:00
Implement scripts
Implementation person
1
05:00-05:30
RF parameter configuratio
Imp RF team
1
05:00-06:00
KPI verification
Imp RF team
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 8 of 11
Implementation Solution for Change
5.2
Test and Verification
DT on site will do drive tes to verify the services and no sector swap and HO functionality
5.3
Solution for Changeback In the Case of Failure
5.3.1 Definition of Change Failure Definition of Change Failure After hardware and parameter change if any abnormal behavior observe and in case of KPI degradation then activity should be rolled back to restore the services Rollback decision
SN 1
From Huawei (essential)
Decision Person Haoenlong 00966557443892
Decision Time(Local) Before 05:00
5.3.2 Overall Description of Changeback
SN
Step
Owner
Time (start ,end)
1
After changing the hardware and parameters check all the KPIs and services. If any degradation roll it back to original hardware and roll back the configuration changes on U2100 and LTE1800
Field team
05:00 – 06:00
2
Roll back test: Check the service status and performance and abnormal events. If all are normal then keep monitoring.
Implementation and RF team
05:00 – 06:00
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 9 of 11
Implementation Solution for Change
5.3.3 Information Collection before Changeback Collect data configuration, alarms and script generated
5.3.4 Equipment Status Check After rollback check there should be no new equipment level alarms and all services are running fine.
5.3.5 Tests after Changeback
No.
Operation Item
Operation Method
Owner
Time(Start ,end )
1
No abnormal service KPI
Verify 2G, 3G and LTE1800 service not facing any degradation
Implementation person
05:00 – 06:00
2
No abnormal alarm
Compare the post activity alarm with the alarms being saved before the operation and both should be same
Implementation person
04:00– 05:00
5.3.6 Changeback Risk Analysis
SN
1
5.4
Risk Description
KPI degradation
Possibility
Low
Impact
Countermeasure
High
In case of abnormal KPI on any technology involved in this activity as new configuration and Hardware are added so need to take the correct decision in correct time to do the roll back
Change of Spare Parts and Emergency Workstation All the required material is issued to the field team to be used during the activity as there is a buffer material dispatched to the region in case of material fault
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 10 of 11
Implementation Solution for Change
6 Work after Change 6.1
Observation
Observation Ite m
Expecte d result
Observation Perio
Owner
d (start , end)
Check all alarms
No new
and should be same as
alarm , If
before change
there have
6:00AM- 23:00PM
Implementation/NO C
new alarm it should not affect service
6.2
Provision of Materials
Material is prepared base on approved design from HQ
6.3
Provision of Software
Software version is verified by HQ for the proposed changes
6.4
Training
Sufficient training is delivered to the field teams for the implementation procedured
6.5
Matters Needing Attention
NA
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 11 of 11
LTE2100 Layer Addition (Note: update the yellow background area content base on specific change .)
Middle East Region Customized Implementation Solution Template V5.0 Prepared by:
Anan
Date: 30/03/2017
Saleem 84031507 Reviewed by:
ZhuShiche
Date: 30/03/2017
ng 00707424 Approved by:
wangzhen0 0192668
Date: 30/03/2017
Implementation Solution for Change
Contents Live network information ....................................................... Error! Bookmark not defined.
2
3
4
1.1
Live network topology ........................................ Error! Bookmark not defined.
1.2
Business volume ................................................................................................... 4
1.3
Main existing problems ......................................................................................... 4
1.4
Remote access information ................................................................................... 4
Purpose and Requirements ................................................................................................ 4 2.1
Change purpose ..................................................................................................... 4
2.2
Change scenario .................................................................................................... 4
2.3
Change scope & scale ........................................................................................... 6
2.4
Change Period ....................................................................................................... 6
Description of Change and Change Influence................................................................... 6 3.1
NE list & version number or patch number before and after change .................... 6
3.2
Surrounding NEs and version number involved by the change ............................ 6
3.3
Change relevance .................................................................................................. 6
3.4
Description of changed software ........................................................................... 6
3.5
Description of changed hardware .......................................................................... 7
Change Preparations ......................................................................................................... 7 4.1
Composition of Change Team and Responsibility of Team Members ................. 7
Change Team of XX Company .............................................................................................. 7 Huawei Change Team .............................................................................................................. 7 Huawei Support & Guarantee Team ........................................................................................ 7
5
4.2
Check of Equipment Running ............................................................................... 8
4.3
Change Risks and Countermeasures ..................................................................... 8
4.4
Check Before Change ........................................................................................... 8
Operation Steps for Change .............................................................................................. 8 5.1
Change Steps ......................................................................................................... 8
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 2 of 11
Implementation Solution for Change
5.2
Test and Verification ............................................................................................. 9
5.3
Solution for Changeback In the Case of Failure ................................................... 9
5.3.1
Definition of Change Failure ............................................................................... 9
Definition of Change Failure ................................................................................................ 9 Rollback decision ................................................................................................................... 9 5.3.2
Overall Description of Changeback ................................................................... 9
5.3.3
Information Collection Before Changeback .................................................... 10
5.3.4
Changeback Steps ............................................... Error! Bookmark not defined.
5.3.5
Equipment Status Check ................................................................................... 10
5.3.6
Tests After Changeback .................................................................................... 10
5.3.7
Changeback Risk Analysis ............................................................................... 10
5.4 6
Change of Spare Parts and Emergency Workstation........................................... 10
Work After Change ......................................................................................................... 11 6.1
Observation ......................................................................................................... 11
6.2
Provision of Materials ......................................................................................... 11
6.3
Provision of Software.......................................................................................... 11
6.4
Training ............................................................................................................... 11
6.5
Matters Needing Attention .................................................................................. 11
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 3 of 11
Implementation Solution for Change
1.1
Business volume
LTE2100 collocating on the existing LTE1800 using RRU3953 2X80W to be SDR with U2100 which will be shifted from BTS to DBS
1.2
Main existing problems
No any existing problem
1.3
Remote access information
Remote access is not allowed generally but in case of emergency we can ask our BO guy to provide VPN information .i.e. user name and password e.t.c.
2 Purpose and Requirements 2.1
Change purpose
The purpose of the activity is to onair the LTE2100 and shift U2100 from BTS to DBS solution to be SDR UL2100
2.2
Change scenario
U2100 will be shifted from BTS to DBS using RRU3953 Existing U2100 Feeders will be dismantles Exiting WRFU/WRFUe will be dismantled U2100 and LTE1800 BBUs will be interconnected using UCI card UBBPe4 will be added to the LTE1800 BBU to be used as base band resource for LTE2100 LTE2100 bandwidth will be 10MHz Generate script including implementation and the rollback script Open RFC
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 4 of 11
Implementation Solution for Change
Scenarios involved in the solution
Generated Script and Roll Back
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 5 of 11
Implementation Solution for Change
2.3
Change scope & scale
The total scope in 4G6 will be for 864 sites, and currently to be implemented on pilot cluter Damm3 32 sites
2.4
Change Period
Change Date 2017-April-11
Change Start Time 02:00 AM
Change End Time 06:00 AM
3 Description of Change and Change Influence 3.1
NE list & version number or patch number before and after change
NE list and Version will keep same before and after
3.2
Surrounding NEs and version number involved by the change
Not involved
3.3
Change relevance
The change will occure on U2100 and LTE2100
3.4
Description of changed software
U2100 will be shifted from BTS using WRFU/WRFUe to DBS using RRU3953, LTE2100 new layer will be collocated on existing LTE1800
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 6 of 11
Implementation Solution for Change
3.5
Description of changed hardware
U2100 will be shifted from BTS using WRFU/WRFUe to DBS using RRU3953, LTE2100 new layer will be collocated on existing LTE1800 GSM900/1800, LTE1800, and LTE2300 will keep same and no change will be happen
4 Change Preparations 4.1 Composition of Change Team and Responsibility of Team Members Change Team of STC Company
Name
Job Role
Email or Telephone No.
Amir shamshad
Integration Engineer
Ameen Uddin Mohammed
Integration Engineer
0538157699 0534731505
Huawei Change Team Name
Responsibility
Arsalan Mohammed
Chief commander
Telephone No. 0530044467
Huawei Support & Guarantee Team Name
Responsibility
Telephone No. +86 XXXXXXXXX
Staff Name & ID
Supporting overall coordination as the technical expert
Staff Name & ID
Product support contact person
+86 XXXXXXXXX
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 7 of 11
Implementation Solution for Change
4.2
Check of Equipment Running
Before running the script all alarm log should be collected for the last 24 hours including RCN, NodeB, and Enode Blevel and then there should not be any alarm on hardware before start
4.3
Change Risks and Countermeasures
Not involved.
4.4
Check Before Change
No.
Preparations Before Change
Owner
Completion Date
1
Data backup
Change owner
1 day before change date
5 Operation Steps for Change 5.1
Step
Change Steps
Time (local)
Task
Owner
1
02:00-05:00
Onsite installation
Field team
1
02:00-05:00
Implement scripts
Implementation person
1
05:00-05:30
RF parameter configuratio
Imp RF team
1
05:00-06:00
KPI verification
Imp RF team
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 8 of 11
Implementation Solution for Change
5.2
Test and Verification
DT on site will do drive tes to verify the services and no sector swap and HO functionality
5.3
Solution for Changeback In the Case of Failure
5.3.1 Definition of Change Failure Definition of Change Failure After hardware and parameter change if any abnormal behavior observe and in case of KPI degradation then activity should be rolled back to restore the services Rollback decision
SN 1
From Huawei (essential)
Decision Person Haoenlong 00966557443892
Decision Time(Local) Before 05:00
5.3.2 Overall Description of Changeback
SN
Step
Owner
Time (start ,end)
1
After changing the hardware and parameters check all the KPIs and services. If any degradation roll it back to original hardware and roll back the configuration changes on U2100 and LTE1800
Field team
05:00 – 06:00
2
Roll back test: Check the service status and performance and abnormal events. If all are normal then keep monitoring.
Implementation and RF team
05:00 – 06:00
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 9 of 11
Implementation Solution for Change
5.3.3 Information Collection before Changeback Collect data configuration, alarms and script generated
5.3.4 Equipment Status Check After rollback check there should be no new equipment level alarms and all services are running fine.
5.3.5 Tests after Changeback
No.
Operation Item
Operation Method
Owner
Time(Start ,end )
1
No abnormal service KPI
Verify 2G, 3G and LTE1800 service not facing any degradation
Implementation person
05:00 – 06:00
2
No abnormal alarm
Compare the post activity alarm with the alarms being saved before the operation and both should be same
Implementation person
04:00– 05:00
5.3.6 Changeback Risk Analysis
SN
1
5.4
Risk Description
KPI degradation
Possibility
Low
Impact
Countermeasure
High
In case of abnormal KPI on any technology involved in this activity as new configuration and Hardware are added so need to take the correct decision in correct time to do the roll back
Change of Spare Parts and Emergency Workstation All the required material is issued to the field team to be used during the activity as there is a buffer material dispatched to the region in case of material fault
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 10 of 11
Implementation Solution for Change
6 Work after Change 6.1
Observation
Observation Ite m
Expecte d result
Observation Perio
Owner
d (start , end)
Check all alarms
No new
and should be same as
alarm , If
before change
there have
6:00AM- 23:00PM
Implementation/NO C
new alarm it should not affect service
6.2
Provision of Materials
Material is prepared base on approved design from HQ
6.3
Provision of Software
Software version is verified by HQ for the proposed changes
6.4
Training
Sufficient training is delivered to the field teams for the implementation procedured
6.5
Matters Needing Attention
NA
Technical support website: http://support.huawei.com
Technical support hotline: Fax:
Page 11 of 11
Related Documents
Mop -lte2100 Addition_2017-04-09_v2
October 2019 18
Mop Boxes.pptx
November 2019 13
April Mop
April 2020 8
Mop Pen
November 2019 21
Structuur Mop
December 2019 11
Mop All
October 2019 8More Documents from ""
Mop -lte2100 Addition_2017-04-09_v2
October 2019 18
Chapter 4 Training Need Assessment
November 2019 14
Training Needs Assessment[1]
November 2019 35
The Research Process
November 2019 24