name: NSI
full_form: Non-IMSI SUPI
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: Non-IMSI SUPI (NSI) refers to a type of Subscription Permanent Identifier that is not based on the International Mobile Subscriber Identity (IMSI). It can take various forms such as user@operator.com and is used in constructing the NRF FQDN for an NRF in an operator's PLMN or SNPN, especially when the SUPI of the UE is of a type other than IMSI.
explanation: NSI is classified as an Identifier because it serves as a unique identifier for subscribers that do not use traditional IMSI formats. This aligns with the context provided from 3GPP TS 23.003, which discusses numbering, addressing, and identification in telecommunications networks.
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: B-Parameter,I-Parameter,O,O,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,B-Parameter,O,O,B-Network Function,O,O,O,B-Network,O,O,O,O,O,B-Parameter,O,O,B-Device,O,O,O,O,O,O,O