top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

LTE: Is it possible to share an eNodeB among multiple operators dynamically ?

+2 votes
544 views

I understood the basics of MOCN through which same eNodeB is controlled/used by multiple operators. Is it possible to do on dynamic basis ? if yes then what all things need to be coordinated among operators to make it happen smoothly ?

posted Jul 22, 2017 by Vikram Singh

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

2 Answers

0 votes

yes it is possible only if LTE is to be operated in unlicensed mode then eNodeB can be share among multiple Wi-Fi and nearby eNodeB.
or if it works in license mode then as we know LTE works as MIMO then other eNodeB can share among others eNodeB

answer Jul 23, 2017 by Divya Gupta
0 votes

When an eNodeB is going to be shared with multiple operator core network, it means eNodeB is going to make S1-Setup with each MME of different operators. As per my knowledge each MME support one or more tracking areas. In S1-setup request, an eNodeB sends "Supported TAs". Since an eNodeB may have multi-cell support, Supported TAs IE can be a list of tracking areas.
MME matches the received TAs from eNodeB against the configured ones and based on that MME responds to eNodeB.

It means each operator's MME should have support of same tracking area code if we consider one eNodeB which is going to be shared among different operator has only one cell and one cell can broadcast only 1 tracking area. Each operator PLMN would be broadcast in same cell and each cell can broadcast up to 6 PLMNs (one primary and other plmns would be considered as secondary).

In essence, what I think is only common tracking area is pre-requisite to implement MOCN.
I am waiting for others to respond to correct me if I am wrong and enhance my knowledge.

answer Jul 23, 2017 by Ganesh
Similar Questions
+2 votes

If yes then on which parameter basis it identify ?

+1 vote

We know, in lte, an eNodeB can connect to multiple MMEs. Can someone please explain in details ?
Apart from load balancing, is there any other reason ?

+2 votes

Is it possible, source eNodeB has received "handover command" message from MME and now it want to cancel handover procedure ?
What could be the possible reasons when source eNodeB want to cancel ongoing handover procedure ?

+3 votes

What are all aspects need to be considered while enabling sharing ?

0 votes

Is it possible any scenario when sctp communication is up between mme and eNodeB but s1ap wil not be up ?
Is there need to send different alarm for s1ap failure and sctp communication failure as part of fault management . Please, suggest me required spec.

...