network sharing

Driver:

The operators are facing unprecedented challenges in particular during these recession days.

- decreased in voice revenues

- maintaining profit

The solution would naturally be on two aspects:

- generating new revenue by introducing new services, such as mobile broadband, mobile TV, SDP (iTunes, Nokia OVI store), etc

- cost reduction

RAN sharing is one solution leading to cost reduction, other options such as complete network outsourcing,

network O&M outsourcing are also worth considering, depends on operators' specific situation.

Solution:

Site sharing installs two or more operators' network equipments (mostly RAN) on the same site/tower. This is the simplest way, no much requirement to eNB (as eNB are still seperate). Backhaul traffic aggregation plays the most important role in cost saving in this case.

Real RAN sharing shares the same eNB with two or more operators. This requires some specific features within eNB to enable the sharing.

- multi- PLMN-id broadcast. The eNB can be configured to broadcast more than one set of PLMN-ids and more than one set of SIBs - as if two networks co-exist.

- VLAN. eNB needs to support VLAN so that each operator use one or more VLANs

- multiple IP address. The eNB should be addressed by different IP address on different operator's network

- resource allocation/balancing. The eNB should support configuration that its resource (HW, radio, etc) can be divided between the operators so that the system is not overwhelmed by a single operator's traffic.

- independent QoS management. However, the eNB should treat each operators traffic independently so that each operator has its own scheduling, RRM, QoS managment policy.

Architecture

Two types of RAN sharing architecture is defined.

- The first is called GWCN, where both GW and RAN are shared

- The second is called MOCN, where eNB connects to different MME/GW from each operator.

Most likely the second option will be more popular.