Ce diaporama a bien été signalé.
Le téléchargement de votre SlideShare est en cours. ×

RAN - Intro, I&C & Basic Troubleshooting (3).pptx

Prochain SlideShare
NSA Mobility Managment.pptx
NSA Mobility Managment.pptx
Chargement dans…3

Consultez-les par la suite

1 sur 72 Publicité

Plus De Contenu Connexe

Similaire à RAN - Intro, I&C & Basic Troubleshooting (3).pptx (20)

Plus récents (20)


RAN - Intro, I&C & Basic Troubleshooting (3).pptx

  1. 1. SKY NETWORK EVOLUTION RAN - Intro, I&C & Basic Troubleshooting Debasis Biswas
  2. 2. Agenda Overview of Network Modernization to 4G & 5G RAN for SKY Project. RAN Deployment Scenarios. RAN Product Descriptions. RAN Modernization Approach & Installation Overview. RAN Node Onsite Commissioning & Integration Overview. RAN Node Troubleshooting & O&M Procedures. RAN Node Backup & Restore
  3. 3. Overview of Network Modernization to 4G & 5G RAN for SKY Project.
  4. 4. Telecommunication Journey So far
  5. 5. Why 3G to 4G & 5G
  6. 6. 3GPP Evolution HSUPA MBMS Rel 6 MIMO HOM CPC Rel 7 Rel 4 R99 HSDPA Rel 5 4G Further enhancements WCDMA/HSPA WCDMA HSPA Evolution Rel 8 LTE Advanced Pro Rel 9 Dual Band support IRAT Enhancements LTE Rel 10-13 5G LTE Evolution & NR Rel 15- 3G MIMO, MTC, LAA and D2D enhancements Rel 14- NR
  7. 7. 4G Overview The RAN provides access links between UE and the EPC network. UE: UE includes the end-user terminals such as cell phones and PCs Radio Node: The Radio Node corresponds to eNodeB in 3GPP specifications. It controls the radio connections with connected UE and manages the cell resources, including connection mobility control. eNodeB is a part of LTE radio access network and is the component that allows UEs to connect to the LTE network. The RAN access links are divided into the following planes: User plane: It carries the end-user payload traffic of voice, video, or any data traffic. Control plane: It carries control signaling for user plane traffic. IP Transport Network: The IP transport network provides interconnection between the eNodeBs and the nodes in
  8. 8. 4G Overview EPC: EPC is the IP-based core network between the RAN and other networks. On the user plane, EPC connects the RAN with the SGW, and on the control plane, with the MME. MME: Mobility Management Entity & deals with the EPC control plane, Its role is to manage sessions, authentication, paging, mobility, bearers and roaming. SGW: Serving Gateway & deals with routing and forwarding of user data packets. It also routes incoming and outgoing IP packets for better system collaboration and serves as an anchor for the UE when it moves from one eNodeB to another. PDN-GW: Packet Data Network Gateway. It is the network node that connects the EPC to external IP networks. It routes packets to and from external IP networks. ENM: Ericsson Network Manager provides a Unified Network Management for Radio, Core and associated Transport nodes. NMS: Network Management Station that manages more than one subnetwork
  9. 9. Interfaces of the 4G eNodeB S1: The S1 interface connects the LTE and the EPC for both the user and the control planes. It has two parts: the S1-C, belonging to the control plane and the S1-U, belonging to the user plane. The S1-C connects the eNodeB to the MME and is based on IP transmission. It transmits signaling messages of the radio network layer of the LTE RAN through the Stream Control Transmission Protocol (SCTP)/IP stack. The S1-U connects the eNodeB to the S-GW through the GTP/UDP5/IP stack. X2: Interface provides connectivity between two or more eNodeBs. There are two parts of the X2 interface, the X2-C, the interface between the control planes of eNodeBs, and the X2-U, the interface between the user planes of eNodeBs. The X2-C and the X2-U have the same structure as the S1 interface. Mul: Interface that communicates with the OSS/ENM and carries traditional operation and maintenance data, such as alarms, performance events and software upgrades.
  10. 10. 5G OVERVIEW- Two Type ofArchitecture Tight interworking with 4G. Evolved EPC Existing 4G EPC can be upgraded to support 5G NSA LTE NR 5G Enabled EPC NSA- Non-Standalone “Independent” overlay. New CN Architecture. NR NR New 5G Core SA- Standalone
  11. 11. 5G NSA Architecture NR node LTE node X2 / Xn NR & LTE co-located X2 / Xn X2 /Xn EPC S1-C, U S1-C, U S1-C, U eNB gNB • eNB • LTE node connected via S1 interfaces to EPC • gNB • NR node connected via S1 interfaces to EPC • X2 • X2 is the interconnecting interface betwe en two eNodeBs • Xn • Xn is the interconnecting interface betwe en two gNodeBs
  12. 12. • NR Non-Standalone (NR NSA) introduces the support for the 5G NR air-interface using existing 4G LTE infrastructure. • In E-UTRA-NR Dual Connectivity (EN-DC) the UE is served by two (or more) radio nodes. One is called the master node and the other is called the secondary node. Each radio access connection is providing a leg of the EN-DC. • NR NSA enhances mobile broadband to provide increased data bandwidth and lower latency while maintaining connection reliability through ENDC. • 5G NR node (gNB) is connected to LTE eNB through X2 interface and to EPC/SGW via S1 (user-plane only) interface. • NR gNB is managed by ENM through O&M interface. 5G NSA Overview - ENDC DRB LTE eNB NR UE 5G EPC ENM BBU NR gNB BBU RU RU LTE UE X2 S1 S1 Uu (e)CPRI (e)CPRI
  13. 13. There are several paths to reach a 5G enabled Core and each path will include different objectives in terms of new technology introduction, use cases and time frames. For NSA Different options have been introduced in 3GPP specification (option 3, option 3a and option 3x) depending on which Network Elements (either LTE nodeB, or NR gNB or both) are in charge to manage the user- plane connectivity towards the SGw. Ericsson’s EN-DC solution is based on Option 3x: • LTE eNB terminates the S1 Control Signaling (S1-C) from EPC and Signalling Radio Bearer (SRB) towards the UE. • The User Data Radio Bearer (DRB) is setup either as: • Split bearer: using both LTE and NR radio resources • LTE only bearer: using only LTE radio resources • NR gNB terminates the S1-U user plane of the Split bearer for the NR UE. • LTE eNB terminates the S1-U user plane of the LTE only bearer. • The eNB and gNB have X2-C and X2-U connections, 5G NSA ENDC Overview – Option 3x
  14. 14. Interfaces of the 5G gNodeB S1-C: Connects RAN to EPC(MME). Used for S1-C signaling connection, terminated by the eNodeb. S1-C is terminated by eNB at RAN side. S1-U: Connects RAN i.e eNodeb & gNodeb to EPC(SGW). Carries S1-U user plane bearer. It’s terminated by the eNB for legacy UE’s, and certain bearers of the NR UE such as VoLTE. While it’s terminated by the gNB for the NR UE bearer. X2-C: Connects between eNodeb and gNodeb and carries X2 control signaling. X2-U: Connects between eNodeb and gNodeb and carries user data of Split bearer. LTE-Uu: The LTE-Uu is the radio interface that connects the UEs to the eNodeBs & eNodeB with the UE. It handles all the signaling messages between the eNodeB and the MME as well as the data traffic between the UE and the S-GW. NR-Uu: The NR-Uu interface, connecting the UE to the gNodeb over the air, is used as one of several
  15. 15. Spectrum Details Band Tech Current (MHz) Planned (MHz) 700 4G (FDD) 0 5 2100 3G 5 0 2300 4G (TDD) & 5G NSA 0 4G:10 & 5G:20
  16. 16. 4G & 5G RAN Deployment Scenarios
  17. 17. 4G & 5G RAN Deployment Scenarios
  18. 18. 4G & 5G RAN Deployment Scenarios At 250 tower sites, where 3G Node-Bs are already deployed, the existing infrastructure like tower, shelter, lightning arrestor, earthing, optical connectivity etc to be reutilized. Scenario-1: All 3G NodeBs of these sites to be replaced with eNodeB & gNodeB i.e 4G+5G at 148 tower sites. Scenario-2: All 3G NodeBs of these sites to be replaced with eNodeB i.e Only 4G(FDD) at 102 tower sites. Both Scenario-1 & 2 is Indoor Sites with Shelter. Scenario-3: At 45 new tower sites, 4G eNode-Bs are to be established afresh. The complete infrastructure in terms of ground-based towers as per requirement, earthing, lightning arrestor, L2 Switch fibre connectivity to the nearest network switch, power cabling to the nearest source, etc needs to be provisioned. The equipment/ systems should be IP 65 compliant and will be deployed outdoor. These sites will be only 4G(FDD). These sites are new Greenfield Outdoor site. Scenario-4: 4G Radio coverage to be provided to underground/. multi-story buildings via IBS at 100 Buildings/locations. These sites will be only 4G(TDD). These sites are Indoor site within building i.e IBS.
  19. 19. RAN Deployment Scenario-1 - Site Type- Indoor Site with Shelter. - To be Modernize from 3G to 4G+5G. - 4G+5G Site, with 3 sectors. - 3G NodeB to be De-install. - Total Site Count- 148. - 5G- B40 Band, Radio- 4412, NSA, 20 MHz, 4T4R. - 4G+5G on Same Baseband-6630. - Standby Baseband for Redundancy. - Sync- GPS. - Media- CSR+AFNET
  20. 20. RAN Deployment Scenario-2 - Site Type- Indoor Site with Shelter. - To be modernize from 3G to 4G. - 4G only Site, with 3 sectors. - 3G NodeB to be De-install. - Total Site Count- 102. - 4G on Baseband-6630. - Standby Baseband for redundancy. - Sync- GPS. - Media- CSR+AFNET
  21. 21. RAN Deployment Scenario-3 - Site Type- New Outdoor Site with Encloser for SMPS & Battery. - 4G only Site, with 3 sectors. - Total Site Count- 45. - 4G- B28 Band, Radio- 2219, 5MHz, 2T2R, FDD. - 4G on Baseband-6337. - Standby Baseband for redundancy. - Sync- GPS. - Media- CSR+AFNET
  22. 22. RAN Deployment Scenario-4 - Site Type- IBS at underground/multi-story buildings. - 4G Only Site, with 1 sector along with IBS Antennas & Splitters. - Total Site Count- 100. - 4G- B40 Band, Radio- 4412, 10MHz, - 4G on Baseband-6630. - Sync- GPS. - Media- CSR+AFNET
  23. 23. RAN Deployment Scenario-5 - Site Type- Mobile System, DMRR Vehicle. - 4G Only Site, with 1 sector along with Omni Antenna. - Total Site Count- 74. - 4G- B28 Band, Radio- 2219, 5MHz, - 4G on Baseband-6630. - Sync- GPS. - Media – CSR+AFNET+SATCOM
  24. 24. RAN Product Descriptions
  25. 25. 5G, 4G, 3G and 2G capacity and Mixed Mode capability for 19-inch rack mounting Baseband 6630 - 19 inch wide, 1U high, 350mm deep - 2 x 10/1Gbps ports (SFP+/SFP) - 2 x 100Mbps/1Gbps RJ45 electrical port - Hardware Prepared for Mixed Mode baseband 5G+ 4G - Support for Mixed Mode baseband: LTE + WCDMA LTE + GSM WCDMA + GSM LTE + WCDMA + GSM NR (5G) + LTE - 8 External alarm ports - Dual -48VDC power feeding - 15 x 2.5/4.9/9.8/10.1 Gbps Radio Interface ports 15 CPRI ports (LTE or WCDMA or GSM) or D U x D U x PDU SCU PCF R U S R U S R U S R U S R U S R U S SHU TCU 04 PDU 3.5U subrack TM Space Air restrictor plate incl CM Cable management
  26. 26. Baseband 6630 LTE The hardware is prepared for the following (future) capacities: - Support LTE-FDD and LTE-TDD simultaneously - Up to 8000 connected users - Up to 1440 MHz antenna bandwidth - Up to 2000 FDD or 1000 TDD VoIP users - 24 LTE cells The following downlink & uplink functionality is supported by the hardware: - Up to 2400 Mbps throughput in DL & Up to 1000 Mbps throughput in UL - QPSK, 16QAM, 64QAM & 256QAM in DL & QPSK & 16QAM in UL - Dual TX antenna support (2x2 Tx & Rx diversity) - Quad Tx antenna diversity (4x2 & 4x4 Tx & Rx diversity) NR The hardware is prepared for the following (future) capacities: - Up to 5000 connected users - NR Mid-band 2400 MHz
  27. 27. Attached & Replaceable Fan Unit Two power ports -48 DC (A & B) 2 Optical SFP TXN ports-(A & B) IDLe: 2 ports 15 CPRI ports For connection to Radio’s (2219 & 4412) through 10G SFP Optical Ports :5 Optical Ports :5 Optical Ports :5 TNC & D Data Interface Ethernet TXN RJ45 LMT/Login/O& M TND Port (RJ45) Sync Port GPS (RJ45) SAU Alarm extension kit port (RJ45) 2 External Alarm Ports (RJ45) Grounding Point Environme nt control ports (RJ45 Baseband 6630 Ports & Connectivity
  28. 28. Baseband 6630 Ports & Connectivity Baseband 6630 to be use in Scenario-1/2/4/5
  29. 29. Outdoor compact RAN Compute unit with high capacity NR and LTE Operation and Mixed Mode NR+LTE RAN Processor 6337 - H 508 mm x W 104 mm x D 387 (with protrusion) - 3 x 25/10/1Gbps ports (SFP28/SFP+/SFP) - 1 x 100Mbps/1Gbps RJ45 electrical port - Support for Mixed Mode baseband NR (5G) + LTE - 8 x 2.5/4.9/9.8/10.1/10.3/24.3/25 Gbps Radio Interface ports - 4 External alarm ports LTE Capacities: - Support LTE-FDD and LTE-TDD - Support LTE-FDD and LTE-TDD simultaneously - Support NB-IoT - Up to 8000 connected users - 2400 MHz (CPRI) Antenna BW - 9 sector carriers LTE TDD, AAS M-MIMO - Up to 2000 FDD or 1000 TDD VoIP users - 30 cells NR Capacities: Up to 10000 connected users - Max throughput DL 5-7Gbps UL 2Gbps - NR High band: 2400 MHz (3 sectors, 2 layers, 400MHz carries) - NR Mid-band: 4800 MHz (3 sectors, 16 layers, 100MHz carries) - NR Low band: 2400 MHz (20MHz, 4T4R
  30. 30. Utility outdoor installations on mast, pole, rail, wall, ceiling and strand for sites RAN Processor 6337 Flexibility Mounting Options:
  31. 31. RAN Processor 6337 Ports & Connectivity RAN Processor 6337 to be use in Scenario-3 Only
  32. 32. 4G & 5G Radios — 2TX/2RX — Up to 2x80W — Full IBW (45MHz) — Up to 4 carriers LTE in MIMO — 2x 2.5/4.9/9.8 Gbps CPRI — 20 liter, 21 kg for B28 — -48 VDC 2-wire — AISG RET support — Support for 12dB TMA — 2 external alarm — Convectional cooling — IP 65, -40 to +55 ̊C 700MHz Band (Radio 2219 B28) LTE NR 4T4R LTE 2T2R 2300MHz Band (Radio 4412 B40) — 4TX/4RX — Support split mode (2 x 2T2R ) — Tx Power 4x20W — 60MHz IBW — 2x 2.5/5/9.8Gbps CPRI — 10 liter, 11 kg — -48 VDC 3-wire — AISG RET support — 2 external alarm — Convectional cooling — IP 65, -40 to +55 ̊C Its is 2T2R Radio with 2x80W is compact and coverage-oriented solution. Radio 2219 B28 to be use for 4G in Scenario-1/2/3/5 Its 4T4R Radio with 4x20W. It can be use both for 4G & 5G. Radio 4412 B40 to be use for 5G in Scenario-1 Radio 4412 B40 to be use for 4G in Scenario-4 for IBS.
  33. 33. Radio Ports - RF Port To connect to Antenna. - Data-1/2 – To connect CPRI to Baseband. - ALD – To connect to Remote electrical Tilt i.e RET units. - Power Port – To connect to power source. - Grounding Port – To connect to Earthing/Grounding.
  34. 34. RAN Modernization Approach & Installation Overview.
  35. 35. Modernization Approach Scenario -1 (4G+5G NSA) Parallel Installation Modernization Approach Existing 3G 2 Port Antenna Readiness Existing CABINET Controller Non-E/// 2100 3G Radio 2. Install radios 2219 B28, 4412 B40 with Jumpers and GPS antenna 1. Install and configure BB6630 Activate LTE 700 1. Activate 2300 with NSA Configuration 2. Perform call testing 1. Activate 700 cells 3. Install new six ports antenna Deinstallation 1. De-install 3G Equipment’s as per requirements. LTE, NR WCDMA 2219 B28 L700 BB 6630 4412 B40 NR2300 2. Perform call testing Activate NR NSA 2300 Layers 4. Connect B40 and B28 radios with new antenna Liv e Liv e BB 6630 Standby BBU New Antenna Six Ports
  36. 36. Modernization Approach Scenario -2 (LTE Only) Parallel Installation Modernization Approach Existing 3G 2 Port Antenna Readiness Existing CABINET Controller Non-E/// 2100 3G Radio 2. Install radios 2219 B28 with Jumpers and GPS antenna 1. Install and configure BB6630 Activate LTE 700 1. Activate 700 cells 3. Install new six ports antenna Deinstallation 1. De-install 3G Equipment’s as per requirements. LTE WCDMA 2219 B28 L700 BB 6630 2. Perform call testing 4. Connect B28 radios with new antenna New Antenna Six Ports Liv e BB 6630 Standby BBU
  37. 37. Ericsson Baseband, Radios, GPS & Antennas to Install RAN Equipment to Install Baseband 6630 Or RAN Processor 6337 RRU 2219 B28 GPS RRU 4412 B40 New Antenna Or
  38. 38.  Baseband Scope : Fixing in 19” rack using cage nuts in case of 6630 & Assembly & fixing in case of RP6337, laying power cable & termination, laying TXN cable & termination, alarm extension/termination with SAU, grounding, labelling  RRU Scope : Assembly & fixing, laying power cable & termination, Laying & termination of CPRI's, RET cable & termination, termination of RF connections (using diplexer/combiners if applicable) & Weather proofing, Grounding, Labelling  GPS Scope :Assembly & fixing, Feeder connectorization, laying, termination & weatherproofing, GPS receiver fixing & connectivity in feeder & baseband, grounding, labelling  Antenna Scope : Assembly & fixing, Azimuth & electrical and mechanical setting, Grounding, termination of RF ports & weather proofing, labelling, termination of RET connection RAN Products Installation Scope
  39. 39. Installation Guidelines – Baseband 6630 1. Make sure the 19” Rack/cabinet is connected to ground before installing E/// Baseband in it. 2. Install Baseband in 19” Rack by using cage nuts & tight properly. Use an approved ESD wrist strap connected to grounding. 3. Minimum 30-50 mm free space required at top & bottom side and rear rack wall to BB fan unit for proper cooling 4. Connect Grounding to Baseband. 5. Use 10 -16 AMP MCB for giving -48VDC power to BB 6. Remove Dust covers and connect cables, ensure labelling on both ends of each connected cables. (ensure do not remove un-used port dust cover from baseband) 7. Lay & Terminate TXN cable and do labeling on both end.
  40. 40. GPS, Transmission, DC Power, Alarm Connections on Ericsson Baseband ½’”feeder cable N-male connector to prepare on both end Baseband earthing point -48V DC MCB BOX 10 /16 Amp N-Female to SMA male 1.5mtr pre- feb jumper TSR951339/1500 GPS receiver RPM 1136127 (RJ45– RJ45) GPS SYNC cable GPS ANT. to earth ½” feeder to earth Baseband Power cable with one side pre-feb.connector SAU Alarm extensio n kit GPS Electrical Port TNC Optical Port TNA BASEBAND Indoor Activity Outdoor Activity CSR
  41. 41. Antenna will be of 6 RF ports with RETs: 2 Ports of 700MHz & 4 ports of 2300MHz. Example below. Weather Proofing to be done on both Radio & Antenna end Connections: Radio & Antenna Connections
  42. 42. CPRI Connections Scenario-1: 6630 to 4G(FDD) & 5G RRU RRU 2219 B28 700 Sector 1 DATA port RRU 2219 DATA port RRU 2219 DATA port Sector 2 Sector 3 BASEBAND CPRI PORTS B28 700 B28 700 RRU 4412 B40 2300 Sector 1 DATA port RRU 4412 DATA port RRU 4412 DATA port Sector 2 Sector 3 B40 2300 B40 2300 LTE FDD - 700 5G NSA - 2300
  43. 43. RRU 2219 B28 700 Sector 1 DATA port RRU 2219 DATA port RRU 2219 DATA port Sector 2 Sector 3 BASEBAND CPRI PORTS B28 700 B28 700 LTE FDD - 700 CPRI Connections Scenario-2: 6630 to 4G(FDD) RRU
  44. 44. RP 6337 CPRI PORTS RRU 2219 B28 700 Sector 1 DATA port RRU 2219 DATA port RRU 2219 DATA port Sector 2 Sector 3 B28 700 B28 700 LTE FDD - 700 CPRI Connections Scenario-3: 6337 to 4G(FDD) RRU
  45. 45. BASEBAND CPRI PORTS RRU 4412 B40 2300 Sector 1 DATA port LTE TDD - 2300 CPRI Connections Scenario-4: 6630 to 4G(TDD) RRU
  46. 46. RRU 2219 B28 700 Sector 1 DATA port BASEBAND CPRI PORTS LTE FDD - 700 CPRI Connections Scenario-5: 6630 to 4G(FDD) RRU
  47. 47. Scenario-5: Sample Installed RF Products (Outdoor) RF Ant, GPS & RRU on DMRR-IAF Omni Antenna GPS antenna RRU 2219
  48. 48. RAN Node Onsite Commissioning & Integration Overview.
  49. 49. Physical Tx Connectivity of RAN nodes CSR1 CSR2 LTE + 5G LTE + 5G LTE-eNB Location-1 -LTE+5G Location-2 -LTE 1G 1G 1G 10G 10G 1G 10G 10G 1G 1G 10G 10G 10G 10G 1G 1G LTE-eNB • Each 4G, 4G-5G site location will be having a Cell Site Router i.e CSR • CSR connectivity to AFNET Router for Traffic handover to be extended to Core locations. • CSR at each location will terminate on AFNET routers via 10G long haul link. • Need 2*10G ports per site for CSR connectivity(on all 459 locations) with AFNET Routers MTAS EMM NeLS CSCF EME EDA Ipworks BGCF A-SBG N-SBG A-BGF N-BGF MRS AFG MME EPG3-UP SGW- PGW CP SAPC WMG HSS EMS AFNET RTR -1 AFNET RTR -2 AFNET RTR -3 AFNET RTR -4 AFNET BACKHAUL OM_CN SIG_CN Media_CN VoLTE RAN Core Router 6274(R1) Ext_IPI AFNET ● v 1X10G Link AFNET Router (NCS 5504) NC55 MOD (12x10G) Core Location-1 10G Port OM_CN SIG_CN Media_CN VoLTE RAN Core Router 6274(R1) Ext_IPI AFNET ● v 1X10G Link AFNET Router (NCS 5504) NC55 MOD (12x10G) Core Location-2 10G Port LACP LACP • Intra site routing (eg, between LTE and 5G at Location 1) will be handled by CSR. • Inter Site (Bw Location-1 & Location-2) X2 traffic routing for LTE/5G nodes to be handled by AFNET Routers.
  50. 50. Baseband to CSR Router Transport Connectivity CSR 6672 Sample Location RAN VRF OAM VRF Baseband LTE + 5G OAM 1G Link • Services configured on Baseband – OAM, S1-CP and S1-UP • S1-CP (Control plane) and S1-UP(User plane) traffic segregation on the Baseband. • The S1-CP will communicate with the MME Nodes(Core) and S1-UP will communicate with the SGW Nodes(Core) • Both Control plane and User plane services are integrated in the RAN VRF at each location CSR Nodes which further carry the traffic up to the core nodes via AFNET Backhaul. • The Management of the Baseband is via OAM service which communicates with ENM (Ericsson Network Manager) at core end.
  51. 51. • Three services, Control plane (S1-C), User plane (S1-U) and OAM configured on LTE/5G Baseband Node • Intra site X2 (Between LTE and 5G) will be performed internally BB/CSR. • Inter site X2 routing (Between LTE/5G of different sites) to be performed by AFNET routers. • The Sync for Baseband node at each site will be provided locally using GNSS as a part of solution. • BBU should be having unique enodeb id & gnodeb id through out the network. RAN BBU Tx Solution Strategy Requirements Standard Requirement (LTE & NR Sites) Control Plane(CP) User Plane(UP) OM IP Pool - Baseband One /29 One /29 One /29 VLANs- Baseband 1 1 1 Type of Port - Baseband 1G (Electrical)
  52. 52. Baseband Onsite Commissioning Prerequisites: 1. Commissioning & loading of On-Site Files(OSF) is required for each Baseband Unit (BBU) installed for the sector-based configuration. 2. If your PC has firewall turned on, please disable it. 3. SFTP will not connect to BB6630 if windows firewall is on. 4. Disable all antivirus application that controls the firewall. 5. Turn Off WIFI Network Adapter. Connect Ethernet Cable from PC to Base Band Unit 1. Terminate an Ethernet from your PC to the Base Band Unit LMT Port. Configure Laptop’s IP: 1. Set the IP address of your PC to 2. Set the netmask to 3. Set the default router to 4. The settings above are the default values for BBU hardware. Create Site Folder on PC C- Drive: 1. On PC’s hard drive create Site folder with shortest name possible. ONLY USE THE C: Drive which will provide the shortest path. Example: S01RJCRT01. 2. When using the SFTP server, it is recommended to have one folder that will have all files that will be transfer to the BBU. This folder will contain the BB Upgrade and all files needed to integrate.
  53. 53. Baseband Onsite Commissioning Extract BBU OSF to Site folder 1. Extract script files into your site’s folder create on the PC’s C Drive. 2. OSF have 3 scripts/Files: RBS Summary Site Basic Site Equipment Extract BBU SW Upgrade Package to Site folder 1. SW will be transferred into the BBU as a zipped file. 2. Download SW packages from shared path, if you are unsure on what SW package is required for your Project, contact your next level of support. 3. This type of zip file will need to be copied into your site’s folder. DOT NOT EXTRACT BBU Software. Example: Verify SW Name on RBS Summary File 1. Open the RBS summary file from your Site folder containing your site’s OSF using Note Pad Program and verify that the UP naming is the same as the BBU SW you are having. 2. The SW UP names to match or else the scripts will not run. Start SFTP Server 1. The SFTP application to be downloaded. 2. Username: rbs Password: rbs. 3. Once started, don’t close SFTP SERVER. 4. Root Path: Path to your site folder that contains the OSF and SW.
  54. 54. Baseband Onsite Commissioning BBU Board Restore 1. Connect Laptop to BBU using LMT port. 2. Connect to the BBU board and perform a board restore 3. Open a web browser and go: 4. If the node status is “Node has not been UP” BBU is empty, proceed to the next step. In configured BBU status will be “Node is working”. 5. Perform a “Board Restore” if BBU is Configured BBU, This will restart the board & return it to factory default. Open Web Browser for OSF Loading 1. Launch an internet browser 2. In the address bar, enter in 3. If security certificate is prompted, click on 4. Once connected, you will see example screen below: Input data for OSF Loading 1. Enter in the Laptop’s IP address: 2. Enter in username as “rbs” and password as “rbs”.
  55. 55. Baseband Onsite Commissioning Input data for OSF Loading – Site Installation File (RBS Summary File) 1. Copy your site’s RBS summary File name including the .xml 2. Type / then paste the entire name into the “Site installation file” 3. Example below: Start of OSF Loading 1. Once all the required fields are inputted, the “Download Files” button will be enabled. 2. Click on the Download Files button to start OSF loading. 3. Check Integration logs for progresses of OSF loading.
  56. 56. Baseband Onsite Commissioning Verify Connectivity on SFTP 1. If you have successful started the OSF loading, you will see a connection on the SFTP server. 2. See example below Integrate BBU & Check Integration Log for Progress 1. The RBS Summary File will be used again to continue to Integrate the BBU. 2. Here the RAN HW & Tx definitions are done at BBU with respect to site configuration. 3. BBU will be restarted & the onsite configuration files will be installed. 4. Continue to check the Auto Integration Log Box for progress of integration. Integrate BBU 1. Once the initial loading of the OSF is loaded to about 65% Software Download and Install Complete appears at the bottom of the screen, the option to Integrate the BB6630 will become available. 2. Click on “Integrate”.
  57. 57. Baseband Onsite Commissioning Verify that the Onsite Commissioning is completed successfully. 1. After 10-15 min the Commissioning will be finished. 2. Once the configuration file is completed,the network loader should be at 70% 3. Example below: 4. In order to confirm that the integration completed successfully, Check the LED indications lights on the board, Verify that both the and the TNC LEDs are solid GREEN. 5. Go to web browser on the page & Verify that the node status as “Node is working”. 6. Onsite Commissioning ends here. Further steps can be done Onsite or Remotely.
  58. 58. Baseband Commissioning/Configuration Scripts 1. Baseband will be having 10 different scripts i.e 3 OSF & 7 Remote files/scripts. 2. RBS Summary, Site Basic & Site Equipment scripts are for Onsite Commissioning. Also know as OSF i.e Onsite Files. These are xml files. 3. TN, RN, Post Install scripts can be run in both Onsite or via ENM when Remote connectivity is through. These are know as mos or remote files/scripts. 4. ARNE scripts to be run only Remotely in ENM. 5. RBS Summary- It contains information of SW & which Site Basic & Site Equipment script to define. 6. Site Basic- It contains information of all Tx related information of the site , node fingerprint & node maintenance username & password. 7. Site Equipment- It contains information of Hw to be define & how Hw will connect to BBU. 8. TN- It contains info about Sync, Clock, QoS & additional Tx info. 9. RN- It contains info about plmn, Enb Id, Carrier power, TxRx, earfcn, PCI , Cell BW, TAC, Lat-Long, MME , Relation to other technology, etc. 10.Post Install- It contains additional info of node.
  59. 59. Baseband Remote Integration via ENM The following steps must be executed by the Remote engineer after Onsite Commissioning is done & BBU defined in ENM. 1. Upload with ftp the mos Delta Moshell script to ENM. 2. Open the ENM Application Launcher and click on Shell Terminal on Scripting APP. 3. RESULT: A shell(Advance MO Shell) will be displayed as below: 4. Login to the BBU: ACTION: Type: amos <node IP> lt all RESULT: Login to BBU via shell Terminal & configuration of the node is loaded in it till which it was configured onsite. 5. Load the remaining mos script/file in the BBU: ACTION: Type: run <path of ftp>/<delta name file>.mos lt all RESULT: The new configuration which was in mos script is loaded in the node . Through this step all TN, RN & Post Install mos scripts/files to be run & configurations in each mos scripts are loaded to BBU one by one. 6. After the configuration and in order to assure the fallback procedure, create a Configuration Version (i.e backup) in BBU: ACTION: Type: cvms <name of CV> RESULT: New CV Backup is created with respect to the current configuration of the Baseband.
  60. 60. Baseband License Installation via ENM 1. Open License Administration in ENM > Software Hardware Manager > License Administration, then click Install Key Files. 2. Define the Job Name, and Add Node on which the license will be installed to, then click Next. 3. Select the required license key file, then click Next. 4. Click Validate, if no error, then click Next. 4. Select the Start with ‘Define job and execute immediately’, then click Next. 4. Double check the job details, then click Finish to submit the job. 4. Back to Software Hardware Manager to check the job progress until the job is 100% finished.
  61. 61. RAN Node Troubleshooting & O&M Procedures.
  62. 62. MoShell is a text-based O&M client providing access to the following services: — Configuration Service (CS) — Alarm Service (AS) — Performance Management (PM) Service — Log Service (LS) — OSE shell (COLI) — File transfer (File Transfer Protocol (FTP) / Hypertext Transfer Protocol (HTTP)) Access to all services is supported both in secure mode (secure Common Object Request Broker Architecture ( CORBA), Secure Shell (SSH), Secure File Transfer Protocol (SFTP)) and unsecure mode (unsecure CORBA, Telnet, FTP). Advanced MO Scripting (AMOS) provides a Command-Line Interface (CLI) towards supported Connectivity Packet Platform (CPP), and Transport-based Network Elements. MoShell architecture as shown. BBU is Cello packet platform i.e CPP node, & It have various access methods for different services: — For Managed Services like CS, CORBA is used. — For the command shell, ssh or telnet is used. — To collect PM XML ROP files FTP/SFTP is used. AMOS is part of ENM package for O&M of BBU. What is MoShell
  63. 63. MO Concept of RAN Nodes - The MO i.e Managed Object is a way of modelling resources in a CPP node. - The purpose of the Management Object (MO) is to interface towards the various O&M services described. - The MOs are organized in a hierarchical structure as FDN/LDN/RDN as below: - Each MO instance is uniquely identified in the node by its Local Distinguished Name (LDN). - The highest MO in a node, the so-called root MO is the ManagedElement. This MO represents the whole node. - There is only one instance of the ManagedElement MO in the node and it is referenced by the LDN: ManagedElement=1 - The string at the left of the equal sign is called the MO class (or MO type) and the string at the right of the equal sign is called the MO identity. In the case of the root MO, the MO class is ManagedElement and the identity is 1. - If an MO is located further down in the MO tree, the LDN must contain the MO classes and identities of all the parents of that MO, in a sequence going from the root MO down to the MO in question. See example below:
  64. 64. RAN O&M via MoShell/AMOS Functionality Alarm Service(AS) -The list of active alarms can be retrieved with the commands al to show an overview. alt to show overview + Date & Time ala the same as al, with more details. Configuration Service(CS)- MoShell supports the following 6 operations from the configuration service: Performance Management (PM) Service pmr to show an overview of KPI trend of node. Minimum time interval is 15mins statistic ROP. Produce PM KPI reports. pmx to show counters of KPIs values extractad from the statistic ROP files.
  65. 65. RAN Basic MO Commands for O&M — lt all To load all Mos — st Print state of Mos (operationalState & administrativeState) — pr Print all Mos, Print MO name and proxy ID — get Read atributes from MOs — sts Display current node sync — deb Unlock MOs. — bl Lock Mos — ldeb Unlock main MO and children — lbl Lock main MO and children — bls Soft-lock MOs (MO will handover traffic to other resource) — Set Set an attribute value on one or several MOs — acl List available actions for an MO — acc Execute an MO action. — Cab Display miscellaneous printouts from BBU — cabx Display LED and HW information for all connected HW CV (Configuration Version) Backup Handling — cvcu Display current CV information only — cvls List CVs in BBU — cvmk “cvname” Create a local CV backup — cvset “cvname” Set a CV as startable — cvms “cvname” Create a local CV and make it startable — cvrm “cvname” Remove CV or CVs — cvget Transfer a backup/CV to a Workstation/ENM. — cvput Transfer a backup/CV from a Workstation/ENM to BBU Complete HW/SW inventory via the MO interface. — invh show hardware information — invl show licensing information — invg Display graphical view of CPRI and RF connections PM KPI reports based on counter values — pmr Display the list of reports available for the node — pmrz Display reports in the local time for the Workstation/ENM — pmr –r “x” Display an specific report (“x”) — pmr –m “y” Display reports from an specific period (“y”) — pmx Display counters of KPIs values from the statistic File — pmx –m 1 “z” Display counter value of “z” in last 1 hr.
  66. 66. RAN Basic MO Commands for O&M Check Current Alarm: alt Check status of Radio units: st FieldReplaceableUnit Check Cell Availability: st cell Check Sector status: st sector Check status of MME Termination: st TermPointToMme Check status of X2 Termination: st TermPointToENB Check Alarms: al/alt/ala Check HW,VSWR: cabx Check License and Feature states: invl Check Product, Serial, BER, TXdbm, RXdbm: invxrb Check traffic status: ue print –admitted Check RRU status: st rru Check SAU status: st sau Check earfcn of cell: get . Earfcn Check TAC of cell: get ^EUtranCell ^TAC Check PCI of cell: get ^EUtranCell ^physicalLayerCellId$ Check Power of Carrier: get SectorCarrier Power Check no of Tx in Carrier: get SectorCarrier noOfTxAntennas Check no of Rx in Carrier: get SectorCarrier noOfRxAntennas To Block cell: bl cell To De-Block cell: deb cell To set Carrier power: set SectorCarrier=x configuredMaxTxPower 40000 To set cell TAC: set EUtranCellFDD=xxx tac 7157 Print HW defined in BBU: pr FieldReplaceableUnit= Check Aail. actions on RRU:acl FieldReplaceableUnit=RRU-1 Restart RRU: acc FieldReplaceableUnit=RRU-1 restartUnit Restart the BBU: acc FieldReplaceableUnit=1 restartUnit Check Interface status: st interface Check router: lpr router
  67. 67. RAN Node Backup & Restore.
  68. 68. Baseband Configuration Backup Baseband Configuration Backup can be taken via any of below three process: — Creating Onsite Configuration Version/ Backup at node by connecting directedly to it & transferring the CV to local terminal for future reference. Command- cvget “cvname”. — Creating Configuration Version/ Backup at node by connecting BBU through ENM-AMOS & storing the CV in ENM-AMOS terminal for future reference. Command- cvget “cvname”. — Creating Configuration Version/ Backup at node(s) via ENM- SHM i.e Software Hardware Manager. Here we can take backup of multiple nodes at a time & we can schedule the process too. After job is done it is saved in ENM for future reference. Example of a Site backup after completing the above steps. For site restoration we should refer the latest backup. Site Backup will be having 2 files as below On opening the backupinfo.xml of a Site backup we will be having three details as below: 1. Backup Version or Name. 2. Site id of Backup taken. 3. Available Baseband Software level at the time of backup taken. During restoration with this configuration backup need to have same Software.
  69. 69. Baseband Restoration from Configuration Backup 1. If any site BBU gets faulty then site can be restored with its last taken “Configuration Backup” through onsite engineer. 2. The Site Engineer reaches the site with the Configuration Backup and the software/upgrade package as noted during the CV creation. 3. The new hardware installed on the site is powered on. The laptop is configured with an IP address of, a subnet mask of and a default gateway of 4. Connect node LMT port to laptop that has server application for sftp. Start laptop SFTP server as done during commissioning time. 5. From the web browser of the Laptop, the following URL is accessed. IP to put in Auto integration is User & password as rbs/rbs. 6. The attached Summary File is used to define the correct Software Package Zip File and the Backup Name. 7. The software package and the summary file itself should be present in the Folder as defined on the SFTP server. 7. Enter the SFTP server file path of Restore File in the ‘Site Installation File’ text field 8. After this proceed to “Download files”, Once the files are download the node is ready to log in. 9. Install License Key File. The node is ready to be brought into service. 10.The ease of restoration of the BBU to the last known configuration that was available during backup creation is a simple, quick, and robust procedure
  70. 70. Easy HW Replacement & Site Restoration Background Issue — Complicated and time consuming manual HW replacement procedure as described in previous step. Solution — Easy HW Replacement introduces automated replacement of Basebands in field based on Zero Touch Integration, with ENM. — The configuration from the replaced HW is automatically included on the new HW by restoring node CV. Befits — Solution to increase network performance by fast replacement of Basebands — No need for integration competence or laptop at site. — Faster node recovery & Less time spent on site. Prerequisites The network must be set up i.e, — The end-to-end customer network must be setup for Zero Touch Auto-integration using DHCP — DHCP Server: ENM to act as DHCP Server — DHCP Relay: Site router configuration to act as DHCP Relay — LTE and NR should run in the single Baseband Network Operation Management must have: — Backup shall regularly be uploaded in ENM-SHM for all nodes — License Key Files for all nodes shall always be stored in ENM-SHM — Operational SW package shall always be stored in ENM-SHM
  71. 71. Easy HW Replacement Process Not depended on ENM activity. Replacement can be started before ENM end activities.

Notes de l'éditeur

  • Ericsson 5G RAN System Techniques
  • PC&I-Product configuration and Integration