Section: 28.2 Home Network Domain
Content: The Home Network Domain for 5GC shall be in the format specified in IETF RFC 1035 [19] and IETF RFC 1123 [20] and shall be structured as: "5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org", where "<MNC>" and "<MCC>" fields correspond to the MNC and MCC of the operator's PLMN. Both the "<MNC>" and "<MCC>" fields are 3 digits long. If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the NF service endpoint format for inter PLMN routing. As an example, the Home Network Domain for MCC 345 and MNC 12 is coded as: "5gc.mnc012.mcc345.3gppnetwork.org". The Home Network Domain for a Stand-alone Non-Public Network (SNPN) shall be in the format specified in IETF RFC 1035 [19] and IETF RFC 1123 [20] and, if not pre-configured in the NF, shall be structured as: "5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org", where <MNC> and <MCC> shall be encoded as specified above, and the NID shall be encoded as hexadecimal digits as specified in clause 12.7. As an example, the Home Network Domain for MCC 345, MNC 12 and NID 000007ed9d5 (hexadecimal: assignment mode = 0, PEN = 00007ed9, NID code = d5) is coded as: "5gc.nid000007ed9d5.mnc012.mcc345.3gppnetwork.org". NOTE: For interworking with an SNPN (e.g. discovery of AMFs from an SNPN by a shared NG RAN), the above sub-domain can be used when the MCC, MNC and NID uniquely identifies the SNPN. For signalling within an SNPN, the above sub-domain can be used regardless of whether the MCC, MNC and NID uniquely identifies the SNPN or not.