lte deployment overview a high level view of the lte ran deployment steps

LTE Deployment Overview

A high level view of the LTE RAN deployment steps.

www.wade4wireless.com 1

End to End RAN Deployment


• Understand the steps to deployment.• The Deployment Tasks.• Backhaul and Fronthaul. • Permitting and Zoning Challenges.• Other Challenges.• The HetNet.• Planning Overview.• A Quick Note about Final Acceptance

Understand the steps to deployment.


• Start with the end in mind.• Building the SOW.• Lay out the steps of deployment.• Break it down into each phase.• Build a preliminary timeline.• Prepare for delays up front.

The Deployment Tasks


• Project Management – PM is the overall management of the project. • RF Design – this is generally where the RF team will determine the

need for coverage based of need, complaints, and holes. • Site Acquisition – this is where a team will look at the RF design and

try to find sites that fill the need. • Site Survey – this is where each site will be surveyed or a sample of

sites to make sure the rest of the deployment goes as planned. • Site Design – this is where the site, the individual site will be looked at

and the design will be done.

• Network Design – this is usually the part where they have to assign the name of the site, the IP information, the RF information, the expected neighbor lists, the addition of the site to the core, schedule the date of integration and adding this site to the rest of the neighbors and maybe the cluster. See Backhaul and Fronthaul slide.• Logistics – I would bet most people overlook this and think that it’s part of

installation. • Installation – now you can install the hardware, the backhaul, the fronthaul,

and the power. • Commissioning – this is where you will power up the cell, test the backhaul,

and make updates to the firmware if necessary.



• Integration – this is where you will complete the upgrades, add it to the core, and possibly turn up the site if it’s ready. • Optimization – this is where they will

have the site optimized for peak performance not only with RF, but also downloads, uploads, working with neighboring sites, and so on.



Backhaul and Fronthaul• Backhaul is the link from the eNodeB, macro or small cell, back to the core.• Fronthaul is the link between the BBU and the RRH. Delays matter! So the distance is

limited due to the delay limitations for the data from the BBU to the RRH. • These connections provide challenges to the installation and should be planned out ahead

of time.• Wireless – pay the up front cost and the rent, but can you make a connection to another

location? Usually a very short haul to another site that has fiber to the core.• Copper – Usually through a cable company or an internet provide. This is going to need to

be a VPN connection and may add network delays. Could go to the core or to another site.• Fiber – The preferred way to connect to the core by most carriers, also the most expensive.

There is an upfront cost to installation and a monthly reoccurring fee for the fiber. Generally dark fiber dedicated. Could go to another site or to the core.



Small Cell

InternetMacro

CRAN

Small Cell

Small Cell

Small Cell

MiniMacro

Backhaul to a Macro site

InternetBuilding

CRAN

MiniMacro

CRAN

CRANSmall Cell

MiniMacro

Backhaul to a building

Backhaul and Fronthaul

Permitting and Zoning Challenges• Permitting and zoning has been the reason so many deployments slow down. There are always

problems with permitting and zoning because you are dealing with so many municipalities and cities. It is best to be prepared and know the permitting in the area you’re working. Plan ahead if you can.

• Good drawings matter! You need to be sure that you have acceptable drawing for the local municipality. Sometimes a government agency merely needs to file without going through the permitting process, many public safety teams can do this.

• Most City governments have poles and boxes available for equipment installation. If at all possible, use these assets to mount and store equipment when you start rolling out your mini macro or small cells. They should save you time and money in the rollout.

• Crown Castle installed cabinets on poles ahead of time so that when the small cell or CRAN installations take place they already have the permitting completed. They do not need to do it again. The payoff is huge because all that time waiting for the permit to come back from the local government is done.

• If you are working with a skilled site acquisition team, they should be able to help you move ahead of these issues.


Other Challenges• Power – having the power at the location could become an issue. • Mounting assets – when deploying LTE is the first round you may use towers that have

all the assets you need. When you densify the network you will need to roll out to poles with small cells and mini macro sites. This will pose more challenges.

• PIM testing – there are all kinds of interference, and PIM, Passive Intermodulation, is a big one. Make sure you test all of your sites when they are installed or you may be chasing down problems later.

• Tiger Teams – no one rolls out a system expecting major changes or problems, but it happens. The concept of a Tiger Team is to have teams go around to sites to make mass changes, whether its an antenna change, a hardware replacement, or simply to change jumpers on the tower, keep in mind that Tiger Teams will be an option. It is not cheap to roll out crews to every site the second time, so make sure you know who will pay for it, say the OEM or you. It all depends on why the change is being made.


The HetNet


• The Het Net doesn’t just include macro and small cells, but it could also include Wi-Fi. It is all the devices. Just make sure you have them all in one system working together, like an orchestra playing all the different instruments into one beautiful song. That’s right, they all work together. Take a look at the picture below and you will get an idea of the Het Net coverage.• Per Google: “A heterogeneous network is

a network connecting computers and other devices with different operating systems and/or protocols. For example, local area networks (LANs) that connect Microsoft Windows and Linux based personal computers with Apple Macintosh computers are heterogeneous.”

Planning Overview• Planning - taking all that you know and putting together a timeline for completion while

preventing potential problems. Problems, like missing steps in the scope of work, unrealistic schedules, and incomplete BOMs. Prepare for problems by planning to prevent them before they happen. So guess, why do I have planning so far down in this book?

• RF Design – When doing the RF design you will need the entrance criteria which will be all the OEM specifications, the coverage area, the antenna information, and the customer expectations for coverage. Then you could predict the expected coverage. This will not be the end, of course, because you will need to provide the information to the site acquisition teams. They will look for sites in your given area then give you realistic site locations where there are real mounting assets. Then the RF Design team will need to refine the proposed RF heat maps to predict coverage. They will make recommendations to set the antenna elevation and azimuth. They will predict the potential RF dead zones. They should also make power recommendations for each site.


Planning Overview• Project Management – This is a key role since the PM will have responsibility for the project

roll out. The PM will be the contact to the customer. The PM will be responsible for the completion dates and setting the completion expectations. If the project is falling behind the PM needs to inform everyone of when, why, and what to do to improve. Measure and correct, this is what the PM will be responsible for. That is why they fill out so many reports. Tracking is the key function of the PM. Each milestone needs to be completed for each contractor to get paid and for the PM to get paid. Make sure the roll-out dates are realistic. If

• Site Acquisition – This team will take the information from the RF Design teams and locate sites in a region. They will work with the RF team until sites are found. There is so much more they need to know in today’s roll outs. The details are needed for the region and for each site. They will need to know where to get power, if it is available at the site, if they can include it in the lease, what it will cost. It’s the same with backhaul. Like where the closest fiber ring is or what connections are available or if they can connect wireless backhaul to the asset. They have to know all of this to move ahead.


Planning Overview• Site Survey and Design – This team should survey the sites and draw

up a design for each site. They will need to consider how to mount, where to get power, backhaul location, and how to attach the pole. The survey will make a huge difference in what and how everything is mounted. The drawings that they put together for permitting, installation, and closeout and possibly in the leasing agreement are the key to success. • Network Design – In all honesty this is done by a group that should

already know what they are in for and how much will need to be done. These groups generally have an understanding of the network and what will be involved.


Planning Overview• Installation – While this is something that most think they know how

to do, and generally the one thing that everyone thinks they can do better. Pricing is often cut here first because it is something that the PM thinks manpower can be controlled, but generally if the PM does not plan properly. They can push the installers to work faster, but then mistakes are made and corners are cut. • Commissioning – This may or may not be an engineer that goes on

site. In this phase the power, backhaul, fronthaul, and all connections need to be ready. The PM will need to verify all of this for the commissioning engineer.


Planning Overview• Integration – This is planned to be done with the commissioning engineer

on site so they will all need to work together. Plan accordingly. If you plan to have the integration team work while the installer is on site then make sure the installer is aware that he will not only have to stay on site for an extra amount of time, but there will be testing after the integration is complete. • Testing – There needs to be testing done at the site. With LTE, it is

generally data uploads and downloads that are tested. The backhaul is also tested. If this is a small cell then the installer may be given a device to test. Plan to take the time to test. Ask if e911 has to be tested. If the system has voice, in this case VoLTE, then in the US e911 had to be tested.


Planning Overview• Optimization – the planning for this will be with the drive/walk teams to

come out during turn up so that the site is doing what the RF Design team said it would so. • Inspections – If there is an inspection then this will happen after the

installation and possibly after the integration. • Fiber backhaul and budgets – The thing that I bring up over and over again

is the backhaul issues because it is a real problem and one that should be worked out ahead of time. The backhaul or fronthaul needs to be defined and planned out prior to any installation. • Wireless backhaul and budgets - What about wireless for the backhaul or

fronthaul? Is this a viable alternative? DO you need line of site?


Planning Overview• Wired backhaul and budgets – I always thought that the DOCSIS

connection would be a great small cell backhaul connection. You have power and internet all in one.


A Quick Note about Final Acceptance• When the site is up an running and integrated, then testing needs to

be done:• ATP – Acceptance Test Plan will need to be setup and automated as much as

possible, testing at each site on each eNodeB, even if it’s a small cell• E911 testing will need to be coordinated and completed• Optimization will need to completed, the site will need to be optimized into

the cluster to:• Avoid self interference• Handoff properly to neighbors• Each eNode B will need to be tested, macro, small cell, or CRAN• Insure interoperability with cluster



• http://wade4wireless.com/2015/11/12/wireless-deployment-handbook-for-lte-small-cells-and-das/• http://wade4wireless.com

There is help out there for deployment, resources you can use.

http://wade4wireless.com/2015/11/12/wireless-deployment-handbook-for-lte-small-cells-and-das/

http://wade4wireless.com/


http://wade4wireless.com/2015/11/12/wireless-deployment-handbook-for-lte-small-cells-and-das/

Naming Overview (Abbreviations and Acronyms)


• Het Net – A Heterogeneous Network is a network that includes multiple transmissions using multiple ways to deliver data. Per Wikipedia, “A heterogeneous network is a network connecting computers and other devices with different operating systems and/or protocols. For example, local area networks (LANs) that connect Microsoft and Linux based personal computers with Apple Macintosh computers are heterogeneous. The word heterogeneous network is also used in networks using different access technologies. For example, a wireless network which provides a service through a wireless LAN and is able to maintain the service when switching to a cellular network is called a wireless heterogeneous network.” Another good resource is http://www.3gpp.org/hetnet if you’re interested. Really, what we are looking at for the carrier is how to deliver the wireless data/voice using macro, small cells, indoor, and even Wi-Fi to the customer. So this network is going to deliver the data using multiple devices, technologies, and frequencies.

https://en.wikipedia.org/wiki/Computer_network

https://en.wikipedia.org/wiki/Computer

https://en.wikipedia.org/wiki/Operating_system

https://en.wikipedia.org/wiki/Protocol_(computing)

https://en.wikipedia.org/wiki/Local_area_network

https://en.wikipedia.org/wiki/Linux

https://en.wikipedia.org/wiki/Personal_computer

https://en.wikipedia.org/wiki/Apple_Computer

https://en.wikipedia.org/wiki/Macintosh

https://en.wikipedia.org/wiki/Wireless_LAN

https://en.wikipedia.org/wiki/Cellular_network

http://www.3gpp.org/hetnet



• BBU – this is for Base Band Unit. This is the unit that interfaces between the backhaul and the RRH. It will process the incoming data to be sent to the RRH for transmission to the end user. This unit can be run on AC or DC. Generally with a small cell it is part of the small cell, not a separate unit. In most configurations this would be standalone unit. This is the case for a macro site or a CRAN site. • hBBU – This would be a host BBU, also called a BBU hotel,

where a BBU would connect to remote radio heads at another location.


• RRH – Remote Radio Head – this is the RF unit that is not attached to a BBU. It could be on a tower where the BBU is on the ground in a cabinet and the RRH is up on the tower with the antennas. They split them to save on RF loss in the cables and to save on real estate on the ground. However, now you are using more real estate on the tower, and increasing the loading on the tower. In a DAS setting, indoor or outdoor, it would be the RF unit, (radio) that would be mounted with behind the antenna or attached to the antenna.



• CRAN – this is for Centralized RAN, where you would have the controller, a BBU, in one area and it would control several RRHs as part of a distributed radio system. This setup, indoors or outdoors could be part of a DAS system. The RRH could be at the top of a pole, other parts of a building, or a few miles away mounted on a light pole. The BBU may be located on a different location than the RRH. This is pretty common in today’s world. You know that on the towers they put the BBU on the ground and the RRH is up on the tower with the antenna. So just imagine now that they put the BBU in a basement and the RRH’s are spread throughout the building. They may also have the BBU in a closet at a building and spread the RRH’s all over town to get the RF where the people are, to distribute the radio heads and antennas. This could be part of a DAS system where they rely on the CPRI, (common public radio interface), to be connected to fiber for the “fronthaul” which is like the backhaul but to go from the BBU to the RRH, forward! Currently there are several limitations which mostly have to do with timing. They can only travel so far before they would time out. That limits distance at this time. The cloud may change that soon. When they locate many BBUs in a remote location for widely distributed RRHs, they call that a BBU hotel, a term that means that many BBUs for multiple locations are in one spot. I believe that with the cloud this may change because BBUs will be located farther and farther away.


RRH

RRH

RRH

AntennaAntennaAntenna

FronthaulBBU

RRH

Backhaul

EPC

Front

haul

Antenna

Fronthau

l

Fronthaul


• Macro site – this is generally a full blown site, it could be at a tower or on a building top or even a stealth site. It generally consists of fiber backhaul, battery backup, a large BBU, several RRHs and several antennas. It would make up several sectors, usually pointing in many directions. It would also have a router that would connect it back to the core, which generally is a fiber backhaul, but it could be wireless. It generally isn’t copper but it could be. • BTS – Base Transceiver Station – the RF base station.• eNodeB – Evolved Node B from the E-UTRAN This included the air interface, the BTS, and the

interface to the EPC, the evolved packet core. This would normally be all of the equipment at the cell site.• E-UTRAN – evolved universal terrestrial Radio access network. This would be all of the cell sites

in the network.• UE – User Equipment, this is generally the cell phone, smart phone, tablet, or any end user

wireless device. The user would be the person carrying the device using the wireless connection.



• Small Cell: The small cell where the unit has everything included, except maybe the router, but the BBU, (broadband unit) and the Radio Head are all in one unit. Generally small cells radiate less than 5 watts outside and less than 1 watt indoors.

• Femto Cell: A small cell. It would be very small and one that normally would self-configure and you could plug into any internet access for backhaul. It may be something to put in a home or a small business to improve coverage. It would cover a small area to provide better signal and offloading. Usually just for a few UE connections, maybe up to 10. Most of the time it just connects to the internet, like someone’s cable modem.

• Pico Cell: This is slightly bigger than the Femto, usually for a mid-sized business, small bus station, or a smaller public area to connect maybe 10 to 100 connections at any given time.

• Micro Cell: This is usually a bigger unit that can handle medium stadiums or a train station or airport. This term is not used so much anymore because they just call it a small cell.

• Metro Cell: This term was used for larger outdoor metro areas where the loading could be greater than 100 users at any given time. But let’s face it, they are commonly called small cells.

• Indoor small cell: It is a small cell that is mounted inside a building to provide coverage and /or offloading of the Macro site. This unit would not be weather proofed.

• Outdoor Small Cell: It is a small cell mounted outdoors to help with coverage and off loading of the Macro site. This unit would be weatherproofed and it may need a sun shield.



• Mini-Macro – this is generally a medium power eNodeB that is installed similar to a one sector macro site. It would be a single sector cell site, lower power, with a single antenna. There will be variations but generally a stand-alone, medium power cell site. Since it would resemble a smaller Macro site, it would have a larger cabinet to host the BBU and the router mounted at the same location as the RRH. The RRH would be up on the pole or tower or building with the antenna

• vRAN or cRAN – this stand for virtualized RAN and cloud RAN. These generally are part of a CRAN but the vRAN and cRAN will, (in theory)be able to use standard networking protocols to communicate to between the BBU and the RRH. These systems are out there but not generally available at this writing but they should be release very soon.

• DSCS - Distributed Small Cell System is where you would deploy small cells, (and maybe Wi-Fi) like you would with a DAS system. These would be stand alone all-inclusive small cells with integrated antennas. They would be connected to the EPC with fiber or CAT5 or some type of wireless backhaul.

• DAS – Distributed antenna system. This could be 1) an eNodeB feeds the RF distribution system and RF cables run from the central area to each antenna remotely which is similar to most iDAS, (indoor DAS) systems or 2) there could be a central hBBU (host BBU) that uses fiber or CAT 5 to feed several radio heads with antennas which is common in oDAS (outdoor DAS). Together they form a solution for coverage. There are many more DAS solutions, but for LTE let’s stick to these 2.

• . www.wade4wireless.com 27


Take Notes!• ________________________________________________________• ________________________________________________________• ________________________________________________________• ________________________________________________________• ________________________________________________________• ________________________________________________________• ________________________________________________________• ________________________________________________________• ________________________________________________________



lte deployment overview a high level view of the lte ran deployment steps

Documents