3GPP TSG CT4 Meeting #84 C4-183470

was C4-183281
was C4-183014
KunMing, P.R. China; 16th – 20th April 2018
CR-Form-v11.2

CHANGE REQUEST
23.003 CR 500 rev 2 Current version: 15.3.0
For HELP on using this form: comprehensive instructions can be found at
http://www.3gpp.org/Change-Requests.

Proposed change affects: UICC apps ME Radio Access Network Core Network X

Title: NRF FQDN specification for NRF discoverability

Source to WG: Orange
Source to TSG: CT4
Work item code: 5GS_Ph1-CT Date: 2018-04-03
Category: B Release: Rel-15
Use one of the following categories: Use one of the following releases:
F (correction) Rel-8 (Release 8)
A (mirror corresponding to a change in an earlier Rel-9 (Release 9)
release) Rel-10 (Release 10)
B (addition of feature), Rel-11 (Release 11)
C (functional modification of feature) Rel-12 (Release 12)
D (editorial modification) Rel-13 (Release 13)
Detailed explanations of the above categories can Rel-14 (Release 14)
be found in 3GPP TR 21.900. Rel-15 (Release 15)
Rel-16 (Release 16)
Reason for change: TS 23.501 sub-clause 6.3.1 specifies that for NF discovery across PLMNs, the
requester NF provides the NRF the PLMN ID of the target NF. The NRF in the
local PLMN reaches the NRF in the target PLMN by forming a target PLMN
specific query using the PLMN ID provided by the requester NF.

NF Service NRF in serving NRF in Home

Consumer PLMN PLMN

1.
Nnrf_NFDiscovery_Request
2. Nnrf_NFDiscovery_Request/
Response

3. Nnrf_NFDiscovery_Request
Response

In addition the current CR specifies the PLMN level NRF Fully Qualified Domain
Name. Defining a PLMN level FQDN allows an NF to query a DNS to resolve the
FQDN into the IP address(es) and automatically connect to the NRF for
registering into the PLMN level NRF and consuming the Nnrf_NFDiscovery
Service without any required configuration.
 NF Service Consumer NRF

1.Nnrf_
NFManagement_NFRegister_request

2. Store NF profile

3. Nnrf_
NFManagement_NFRegister_response

Figure 4.17.1-1: Nnrf_NF Registration procedure

Other NRFs such as the slice specific and the shared slice ones would require
more complex structure of the NRF FQDN sub-domain to allow automatic
connection to them. It is not required by stage 2 and therefore is not covered by
the present CR.
Summary of change: An NRF FQDN structure is specified and a general subclause that explains when
and how to use it
Consequences if not
approved:
Clauses affected: 28.3.2.X
Y N
Other specs X Other core specifications TS/TR ... CR ...
affected: X Test specifications TS/TR ... CR ...
(show related CRs) X O&M Specifications TS/TR ... CR ...

Other comments:
 * * * First Change * * * *

28.3.2.X PLMN level and Home NF Repository Function (NRF) FQDN

28.3.2.X.1 General
When an NF is instantiated, it may register with a PLMN level NF Repository Function (NRF). It may then discover
other NF instance(s) in the 5GC by querying the PLMN level NRF. The IP address of the PLMN level NRF can be
provisioned into the NF, or the NF can be pre-configured with the FQDN of the PLMN level NRF. If the PLMN level
NRF addresses and FDQN are not provisioned into the NF, the NF self-constructs the PLMN level NRF FQDN as per
the format specified in subclause 28.3.2.X.2.

For NF discovery across PLMNs, the NRF (e.g vNRF) shall self-construct the PLMN level NRF FQDN of the target
PLMN (e.g hNRF) as per the format specified in subclause 28.3.2.X.2, if the NRF has not obtained the NRF FQDN of
the target PLMN.

28.3.2.X.2 Format of NRF FQDN

The NRF FQDN shall be constructed by prefixing the Home Network Domain Name (see subclause 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

* * * End of Changes * * * *