Content for TS 23.003 Word version: 19.0.0

1… 2… 2.8… 3… 4… 5… 6… 7… 8… 9… 10… 11 12… 13… 14… 15… 16… 17… 18… 19… 19.4… 19.5… 20… 21… 22… 23… 24… 25… 26… 27… 28… 28.3.2.2… 28.3.2.2.6… 28.3.2.3… 28.4… 28.7… 28.8… 29… A… B… C… D E…

22.1 Introduction 22.2 ANDSF Server Name (ANDSF-SN)
...

22 Addressing and identification for ANDSF |R8| p. 99

22.1 Introduction p. 99

This clause describes the format of the parameters needed by the UE to use Access Network Discovery and Selection Function (ANDSF) as specified in TS 23.402.

22.2 ANDSF Server Name (ANDSF-SN) p. 99

22.2.1 General p. 99

ANDSF Server Name (ANDSF-SN) is used by UE to discover ANDSF Server in the network.

22.2.2 Format of ANDSF-SN p. 99

The ANDSF-SN is composed of six labels. The last three labels shall be "pub.3gppnetwork.org". The second and third labels together shall uniquely identify the PLMN. The first label shall be "andsf".

The ANDSF-SN is derived from the IMSI or Visited PLMN Identity as follows:

"andsf.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org"

where:

"mnc" and "mcc" serve as invariable identifiers for the following digits.

When contacting Visited ANDSF (V-ANDSF), the <MNC> and <MCC> shall be derived from the Visited PLMN Identity as defined in clause 12.1.
When contacting Home ANDSF (H-ANDSF), the <MNC> and <MCC> shall be derived from the components of the IMSI defined in clause 2.2.

In order to guarantee inter-PLMN DNS translation, the <MNC> and <MCC> coding used in the "andsf.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" format of the ANDSF-SN shall be:

<MNC> = 3 digits
<MCC> = 3 digits

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 ANDSF-SN.

As an example, the ANDSF-SN OI for MCC 345 and MNC 12 is coded in the DNS as:

"andsf.mnc012.mcc345.pub.3gppnetwork.org".