MOCN is one of those great concepts I’d not really come across,
Multi-tenancy on the RAN side of the network, allowing an eNB to broadcast multiple PLMN IDs (MCC/MNC) in the System Information Block (SIB).
It allows site sharing not just on the tower itself, but site sharing on the RAN side, allowing customers of MNO A to see themselves connected to MNO A, and customers from MNO B see themselves as connected to MNO B, but they’re both connected to the same RAN hardware.
Setup in my lab was a breeze; your RAN hardware will probably be different.
In terms of signaling it’s a standard S1AP Setup Request except with multiple broadcast PLMN keys:
MOCN_S1SetupRequest.pcapDownload
Now when I run a manual cell selection on my UE I can see the PLMN 460/11 as well as the Open5gs 00101 PLMN:
What is the maximum number of broadcastPLMN ?
I believe this varies vendor to vendor.
Hi Nick, what type of Radio did you used ? that one has the MOCN list already enabled ? Thanks!
Mi Miguel,
Most radios these days from the big kit vendors support this, I’ve done it on Huawei and Ericsson in production networks.
Cheers,
Nick
Would you be kind enough to share your mme.yaml snippet for multi PLMN?
Hey Paul,
It’s just n PLMN definition stanzas in your config, based on n PLMNs you want.
That is what I figured as well, but I think I must be doing it wrong, I have seen several different formats for the stanza.
gummei:
– plmn_id:
mcc: 999
mnc: 70
mme_gid: 2
mme_code: 1
– pmmn_id:
mcc: 001
mnc: 01
mme_gid: 2
mme_code: 1
tai:
– plmn_id:
mcc: 999
mnc: 70
tac: 1
tai:
– plmn_id:
mcc: 001
mnc: 01
tac: 2
I assume the TAC can be the same, but where I am getting confused is the mme_gid and mme_code. Are you aware if they need to be different?
Thank you for your efforts! I love your website.
I think it might be the two GUMMEIs that are your issue, this is still just one MME, just serving two PLMNs.
Your TACs should be items under the same list, only one `tac:` parameter is allowed, but you can have multiple with the – per the YAML spec.