name: FQDN
full_form: Fully Qualified Domain Name
context: The NRF FQDN for an NRF in an operator's PLMN shall be constructed by prefixing the Home Network Domain Name (see clause 28.2) of the PLMN in which the NRF is located with the label "nrf." as described below: - nrf.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org If the SUPI of the UE for construction of the NRF FQDN is of a type other than IMSI (e.g., NSI such as user@operator.com), the NRF FQDN of an NRF in an operator's SNPN, if not pre-configured in the NF, shall be constructed by prefixing the Home Network Domain Name (see clause 28.2) of the SNPN in which the NRF is located with the label "nrf."e.g. - nrf.operator.com : - nrf.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org (for SNPN scenarios where NID is available) If the SUPI of the UE for construction of the NRF FQDN is of type IMSI, the NID is not available to the NF. Therefore, the NRF FQDN of an NRF in an operatorâs SNPN, if not pre-configured in the NF, is that of the NRF of the PLMN that owns the MCC and MNC as described below: - nrf.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org
description: A Fully Qualified Domain Name (FQDN) is a complete domain name for a computer or host on the internet, including all higher-level domains up to the top-level domain. In the context of 3GPP specifications, specifically within the Numbering, addressing and identification document (TS 23.003), an NRF FQDN refers to the unique identifier used by the Network Repository Function (NRF) in a Public Land Mobile Network (PLMN) or a Shared Network Provider Network (SNPN). The construction of the NRF FQDN involves prefixing the Home Network Domain Name with the label 'nrf.' and may include elements such as MCC, MNC, NID, and 3gppnetwork.org to uniquely identify an NRF within a network.
explanation: FQDN is classified as an Identifier because it serves as a unique identifier for the Network Repository Function (NRF) in both PLMN and SNPN scenarios. The detailed construction rules provided in the context highlight its role in distinguishing between different NRFs based on their location within the network, aligning with 3GPP's specifications for numbering, addressing, and identification.
section_title: 28.3.2.3.2 Format of NRF FQDN
biotag_Context: O,B-Network Function,B-Parameter,O,O,B-Network Function,O,O,O,B-Network,O,O,O,O,O,O,B-Network,I-Network,O,O,O,O,O,O,O,B-Network,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Device,O,O,O,O,B-Network Function,B-Parameter,O,O,O,O,O,O,B-Parameter,O,B-Network Function,O,O,O,O,B-Network Function,B-Parameter,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,I-Network,O,O,O,O,O,O,O,B-Network,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,B-Device,O,O,O,O,B-Network Function,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Network Function,B-Parameter,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network,O,O,O,B-Parameter,O,B-Parameter,O,O,O,O,O
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,B-Parameter,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,B-Network,I-Network,I-Network,I-Network,O,O,O,O,B-Network,O,B-Network,O,O,O,O,O,B-Network Function,B-Parameter,O,O,O,B-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O