Apn Mobile

7/30/2019 Apn Mobile

1/53

3GPP TS 23.003 V7.3.0 (2007-03)Technical Specification

3rd Generation Partnership Project;Technical Specification Group Core Network and Terminals;

Numbering, addressing and identification(Release 7)

GLOBAL SYSTEM FOR

MOBILE COMMUNICATIONS

R

The present document has been developed within the 3 rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.

The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.

This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.

Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.


2/53

3GPP TS 23.003 V7.3.0 (2007-03)2Release 7T

Keywords

GSM, UMTS, addressing

3GPP

Postal address

3GPP support office address

650 Route des Lucioles - Sophia Antipolis

Valbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Internet

http://www.3gpp.org

Copyright Notification

No part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.

2007, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).

All rights reserved

3GPP


3/53

3GPP TS 23.003 V7.3.0 (2007-03)3Release 7T

Contents

Foreword ............................................................................................................................................................6

1 Scope........................................................................................................................................................71.1 References............................................................................... ................................................................... ........ 71.1.1 Normative references ........................................................ .................................................................. ......... 71.1.2 Informative references............................................................................... ................................................... 91.2 Abbreviations....................................... ..................................................................... ......................................... 91.3 General comments to references.................................................................. .................................................... 101.4 Conventions on bit ordering........................................................... .................................................................. 10

2 Identification of mobile subscribers .......................................................................................................102.1 General..................................................... ................................................................ ........................................ 102.2 Composition of IMSI........................................................... .................................................................... ........ 102.3 Allocation principles...................... ............................................................... ................................................... 112.4 Structure of TMSI.................................................................... ............................................................... ......... 11

2.5 Structure of LMSI.................................................................... ............................................................... ......... 122.6 Structure of TLLI......... ..................................................................... ............................................................... 122.7 Structure of P-TMSI Signature ........................................................................... ............................................. 13

3 Numbering plan for mobile stations.......................................................................................................133.1 General..................................................... ................................................................ ........................................ 133.2 Numbering plan requirements................................................................... ....................................................... 133.3 Structure of MS international PSTN/ISDN number (MSISDN)................ ...................................................... 143.4 Mobile Station Roaming Number (MSRN) for PSTN/ISDN routeing ............................................................ 143.5 Structure of Mobile Station International Data Number.............................. .................................................... 153.6 Handover Number.................................................................... ................................................................ ........ 153.7 Structure of an IP v4 address ........................................................... ................................................................ 153.8 Structure of an IP v6 address ........................................................... ................................................................ 15

4 Identification of location areas and base stations...................................................................................154.1 Composition of the Location Area Identification (LAI) ...................................................................... ............ 154.2 Composition of the Routing Area Identification (RAI) ................................................................. .................. 164.3 Base station identification...................... ............................................................................ .............................. 164.3.1 Cell Identity (CI) and Cell Global Identification (CGI)................................................................... .......... 164.3.2 Base Station Identify Code (BSIC) ...................................................................... ...................................... 174.4 Regional Subscription Zone Identity (RSZI).............................................................................. ..................... 174.5 Location Number ............................................................... ...................................................................... ........ 184.6 Composition of the Service Area Identification (SAI)............................................................ ......................... 18

5 Identification of MSCs, GSNs and location registers ............................................................................185.1 Identification for routeing purposes....... ........................................................................... ............................... 185.2 Identification of HLR for HLR restoration application ................................................................ ................... 19

6 International Mobile Station Equipment Identity and Software Version Number.................................196.1 General..................................................... ................................................................ ........................................ 196.2 Composition of IMEI and IMEISV .................................................................... ............................................. 196.2.1 Composition of IMEI .............................................................. ................................................................... 196.2.2 Composition of IMEISV .................................................................... ........................................................ 206.3 Allocation principles...................... ............................................................... ................................................... 20

7 Identification of Voice Group Call and Voice Broadcast Call Entities..................................................207.1 Group Identities .............................................................. ................................................................ ................. 207.2 Group Call Area Identification .................................................................. ...................................................... 217.3 Voice Group Call and Voice Broadcast Call References................................................................................. 21

8 SCCP subsystem numbers......................................................................................................................22

8.1 Globally standardized subsystem numbers used for GSM/UMTS .................................................................. 228.2 National network subsystem numbers used for GSM/UMTS..................... ..................................................... 22

3GPP


4/53

3GPP TS 23.003 V7.3.0 (2007-03)4Release 7T

9 Definition of Access Point Name...........................................................................................................239.1 Structure of APN ........................................................... ................................................................ .................. 239.1.1 Format of APN Network Identifier ........................................................... ................................................. 239.1.2 Format of APN Operator Identifier ........................................................................... ................................. 239.2 Definition of the Wild Card APN ........................................................... ......................................................... 249.2.1 Coding of the Wild Card APN .......................................................... ......................................................... 24

9.3 Definition of Emergency APN......................................................... ................................................................ 2410 Identification of the Cordless Telephony System entities......................................................................2510.1 General description of CTS-MS and CTS-FP Identities.................................. ................................................ 2510.2 CTS Mobile Subscriber Identities............................ ....................................................................... ................. 2510.2.1 General .......................................................... ................................................................. ............................ 25Composition of the CTSMSI ................................................................. .................................................................. ......... 2510.2.3 Allocation principles .......................................................... ................................................................. ....... 2510.2.4 CTSMSI hexadecimal representation....................................... .................................................................. 2610.3 Fixed Part Beacon Identity ............................................................. ................................................................. 2610.3.1 General .......................................................... ................................................................. ............................ 2610.3.2 Composition of the FPBI.................................................................... ........................................................ 2610.3.2.1 FPBI general structure ................................................................. ......................................................... 2610.3.2.2

FPBI class A............................................................ ...................................................................... ....... 26

10.3.2.3 FPBI class B ............................................................ ...................................................................... ....... 2710.3.3 Allocation principles .......................................................... ................................................................. ....... 2710.4 International Fixed Part Equipment Identity.................. ......................................................................... ......... 2710.4.1 General .......................................................... ................................................................. ............................ 2710.4.2 Composition of the IFPEI .................................................................. ........................................................ 2810.4.3 Allocation principles .......................................................... ................................................................. ....... 2810.5 International Fixed Part Subscription Identity ..................................................................... ............................ 2810.5.1 General .......................................................... ................................................................. ............................ 2810.5.2 Composition of the IFPSI.................................. ....................................................................... .................. 2810.5.3 Allocation principles .......................................................... ................................................................. ....... 29

11 Identification of Localised Service Area ................................................................................................29

12 Identification of PLMN, RNC, Service Area, CN domain and Shared Network Area..........................2912.1 PLMN Identifier .................................................................. ................................................................... ......... 3012.2 CN Domain Identifier ............................................................... .............................................................. ......... 3012.3 CN Identifier ..................................................................... ...................................................................... ......... 3012.4 RNC Identifier ..................................................................... ................................................................... ......... 3012.5 Service Area Identifier................................................................... .................................................................. 3012.6 Shared Network Area Identifier.................................................................... ................................................... 31

13 Numbering, addressing and identification within the IP multimedia core network subsystem .............3113.1 Introduction...................................................... .................................................................... ............................ 3113.2 Home network domain name.............................................................. ............................................................. 3113.3 Private user identity ............................................................... .................................................................. ........ 3213.4 Public User Identity .............................................................. .................................................................. ......... 3213.5

Public service identity (PSI) ................................................................... ......................................................... 32

13.5A Private Service Identity...................... ..................................................................... ......................................... 3313.6 Anonymous User Identity ................................................................ ................................................................ 3313.7 Unavailable User Identity ............................................................... ................................................................. 3313.8 Emergency Public User Identity ..................................................................... ................................................. 33

14 Numbering, addressing and identification for 3GPP System to WLAN Interworking..........................3414.1 Introduction...................................................... .................................................................... ............................ 3414.2 Home network realm .................................................................... .................................................................. .......... 3414.3 Root NAI .......................................................... ................................................................... ............................ 3414.4 Decorated NAI........ ..................................................................... ............................................................ ........ 3514.4A Fast Re-authentication NAI .................................................................... ......................................................... 3514.5 Temporary identities ................................................................ ................................................................ ................. 3614.6 Alternative NAI ............................................................ ................................................................ ............................ 3614.7 W-APN ....................................................... ................................................................ ..................................... 3614.7.1 Format of W-APN Network Identifier .................................................................. ..................................... 3614.7.2 Format of W-APN Operator Identifier ...................................................................... ................................. 37

3GPP


5/53

3GPP TS 23.003 V7.3.0 (2007-03)5Release 7T

14.7.3 Alternative Format of W-APN Operator Identifier ........................................................................ ............ 3714.8 Emergency Realm and NAI decoration for Emergency Cases .................................................................. ............... 38

15 Identification of Multimedia Broadcast/Multicast Service ....................................................................3815.1 Introduction...................................................... .................................................................... ............................ 3815.2 Structure of TMGI .................................................................... ............................................................... ........ 3815.3 Structure of MBMS SAI ............................................................ .............................................................. ........ 39

16 Numbering, addressing and identification within the GAA subsystem .................................................3916.1 Introduction...................................................... .................................................................... ............................ 3916.2 BSF address ............................................................... .................................................................... .................. 39

17 Numbering, addressing and identification within the Generic Access Network....................................4017.1 Introduction...................................................... .................................................................... ............................ 4017.2 Network Access Identifiers.............. ..................................................................... ........................................... 4017.2.1 Home network realm.................................................................. ................................................................ 4017.2.2 Full Authentication NAI............................................................................ ................................................. 4117.2.3 Fast Re-authentication NAI........................... ...................................................................... ....................... 4117.3 Node Identifiers ............................................................... ....................................................................... ......... 4117.3.1 Home network domain name .................................................................... ................................................. 41

17.3.2 Provisioning GANC-SEGW identifier .................................................................. ..................................... 4217.3.3 Provisioning GANC identifier ................................................................. .................................................. 42

18 Addressing and Identification for Voice Call Continuity ......................................................................4318.1 Introduction...................................................... .................................................................... ............................ 4318.2 CS Domain Routeing Number (CSRN) ........................................................................ ................................... 4318.3 IP Multimedia Routeing Number (IMRN)....................................................................................................... 4318.4 VCC Domain Transfer Number (VDN)...................................................................... ..................................... 4318.5 VCC Domain Transfer URI (VDI) .......................................................................... ........................................ 43

Annex A (informative): Colour Codes..................................................................................................44

A.1 Utilization of the BSIC...........................................................................................................................44

A.2 Guidance for planning ............................................................................................................................44

A.3 Example of PLMN Colour Codes (NCCs) for the European region ......................................................45

Annex B (normative): IMEI Check Digit computation....................................................................46

B.1 Representation of IMEI ..........................................................................................................................46

B.2 Computation of CD for an IMEI ............................................................................................................46

B.3 Example of computation ........................................................................................................................46

Annex C (normative): Naming convention ........................................................................................48

C.1 Routing Area Identities ..........................................................................................................................48

C.2 GPRS Support Nodes .............................................................................................................................49

C.3 Target ID ................................................................................................................................................49

Annex D (informative): Applicability and use of the ".3gppnetwork.org" domain name...............50

Annex E (normative): Procedure for sub-domain allocation...........................................................51

Annex F (informative): Change history ...............................................................................................52

3GPP


6/53

3GPP TS 23.003 V7.3.0 (2007-03)6Release 7T

Foreword

This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).

The present document defines the principal purpose and use of International Mobile station Equipment Identities (IMEI)within the digital cellular telecommunications system and the 3GPP system.

The contents of the present document are subject to continuing work within the TSG and may change following formal

TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an

identifying change of release date and an increase in version number as follows:

Version x.y.z

where:

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,

etc.

z the third digit is incremented when editorial only changes have been incorporated in the document.

3GPP


7/53

3GPP TS 23.003 V7.3.0 (2007-03)7Release 7T

1 Scope

The present document defines the principal purpose and use of International Mobile station Equipment Identities (IMEI)

within the digital cellular telecommunications system and the 3GPP system.

The present document defines:

a) an identification plan for mobile subscribers in the GSM system;

b) principles of assigning telephone and ISDN numbers to MSs in the country of registration of the MS;

c) principles of assigning Mobile Station (MS) roaming numbers to visiting MSs;

d) an identification plan for location areas, routing areas, and base stations in the GSM system;

e) an identification plan for MSCs, SGSNs, GGSNs, and location registers in the GSM system;

f) principles of assigning international mobile equipment identities;

g) principles of assigning zones for regional subscription;

h) an identification plan for groups of subscribers to the Voice Group Call Service (VGCS) and to the Voice

Broadcast Service (VBS); and identification plan for voice group calls and voice broadcast calls; an

identification plan for group call areas;

i) principles for assigning Packet Data Protocol (PDP) addresses to mobile stations;

j) an identification plan for point-to-multipoint data transmission groups;

k) an identification plan for CN domain, RNC and service area in the UTRAN system.

l) an identification plan for mobile subscribers in the WLAN system.

m) addressing and identification for routeing within Voice Call Continuity

1.1 References

1.1.1 Normative references

The following documents contain provisions which, through reference in this text, constitute provisions of the present

document.

References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.

For a specific reference, subsequent revisions do not apply.

For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document(including a GSM document), a non-specific reference implicitly refers to the latest version of that document in

the same Release as the present document.

[1] 3GPP TS 21.905: "3G Vocabulary".

[2] 3GPP TS 23.008: "Organization of subscriber data".

[3] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2"

[4] 3GPP TS 23.070: "Routeing of calls to/from Public Data Networks (PDN)".

[5] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage3".

[6] 3GPP TS 29.060: "GPRS Tunnelling protocol (GTP) across the Gn and Gp interface".

3GPP


8/53

3GPP TS 23.003 V7.3.0 (2007-03)8Release 7T

[7] 3GPP TS 43.020: "Digital cellular telecommunications system (Phase 2+); Security related

network functions".

[8] void

[9] 3GPP TS 51.011: " Specification of the Subscriber Identity Module - Mobile Equipment (SIM -

ME) interface".

[10] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".

[11] ITU-T Recommendation E.212: "The international identification plan for mobile terminals and

mobile users".

[12] ITU-T Recommendation E.213: "Telephone and ISDN numbering plan for land Mobile Stations in

public land mobile networks (PLMN)".

[13] ITU-T Recommendation X.121: "International numbering plan for public data networks".

[14] IETF RFC 791: "Internet Protocol".

[15] IETF RFC 2373: "IP Version 6 Addressing Architecture".

[16] 3GPP TS 25.401: "UTRAN Overall Description".

[17] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling".

[18] IETF RFC 2181: "Clarifications to the DNS Specification".

[19] IETF RFC 1035: "Domain Names - Implementation and Specification".

[20] IETF RFC 1123: "Requirements for Internet Hosts -- Application and Support".

[21] IETF RFC 2462: "IPv6 Stateless Address Autoconfiguration".

[22] IETF RFC 3041: "Privacy Extensions for Stateless Address Autoconfiguration in IPv6".

[23] 3GPP TS 23.236: "Intra Domain Connection of RAN Nodes to Multiple CN Nodes".

[24] 3GPP TS 23.228: "IP Multimedia (IM) Subsystem Stage 2"

[25] Void

[26] IETF RFC 3261: "SIP: Session Initiation Protocol"

[27] 3GPP TS 31.102: "Characteristics of the USIM Application."

[28] Void

[29] 3GPP TS 44.118: "Radio Resource Control (RRC) Protocol, Iu Mode".

[30] 3GPP TS 23.073: "Support of Localised Service Area (SoLSA); Stage 2"

[31] 3GPP TS 29.002: "Mobile Application Part (MAP) specification"

[32] 3GPP TS 22.016: "International Mobile Equipment Identities (IMEI)"

[33] Void

[34] Void

[35] 3GPP TS 45.056: "CTS-FP Radio Sub-system"

[36] 3GPP TS 42.009: "Security aspects" [currently not being raised to rel-5 Pete H. looking into it]

[37] 3GPP TS 25.423: "UTRAN Iur interface RNSAP signalling"

[38] 3GPP TS 25.419: "UTRAN Iu-BC interface: Service Area Broadcast Protocol (SABP)"

[39] 3GPP TS 25.410: "UTRAN Iu Interface: General Aspects and Principles"

3GPP


9/53


10/53

3GPP TS 23.003 V7.3.0 (2007-03)10Release 7T

1.3 General comments to references

The identification plan for mobile subscribers defined below is that defined in ITU-T Recommendation E.212.

The ISDN numbering plan for MSs and the allocation of mobile station roaming numbers is that defined in ITU-T

Recommendation E.213. Only one of the principles for allocating ISDN numbers is proposed for PLMNs. Only the

method for allocating MS roaming numbers contained in the main text of ITU-T Recommendation E.213 isrecommended for use in PLMNs. If there is any difference between the present document and the ITU-TRecommendations, the former shall prevail.

For terminology, see also ITU-T Recommendations E.164 and X.121.

1.4 Conventions on bit ordering

The following conventions hold for the coding of the different identities appearing in the present document and in other

GSM Technical Specifications if not indicated otherwise:

- the different parts of an identity are shown in the figures in order of significance;

- the most significant part of an identity is on the left part of the figure and the least significant on the right.

When an identity appears in other Technical Specifications, the following conventions hold if not indicated otherwise:

- digits are numbered by order of significance, with digit 1 being the most significant;

- bits are numbered by order of significance, with the lowest bit number corresponding to the least significant bit.

2 Identification of mobile subscribers

2.1 GeneralA unique International Mobile Subscriber Identity (IMSI) shall be allocated to each mobile subscriber in the

GSM/UMTS system.

NOTE: This IMSI is the concept referred to by ITU-T as "International Mobile Station Identity".

In order to support the subscriber identity confidentiality service the VLRs and SGSNs may allocate Temporary Mobile

Subscriber Identities (TMSI) to visiting mobile subscribers. The VLR and SGSNs must be capable of correlating an

allocated TMSI with the IMSI of the MS to which it is allocated.

An MS may be allocated two TMSIs, one for services provided through the MSC, and the other for services provided

through the SGSN (P-TMSI for short).

For addressing on resources used for GPRS, a Temporary Logical Link Identity (TLLI) is used. The TLLI to use is builtby the MS either on the basis of the P-TMSI (local or foreign TLLI), or directly (random TLLI).

In order to speed up the search for subscriber data in the VLR a supplementary Local Mobile Station Identity (LMSI) is

defined.

The LMSI may be allocated by the VLR at location updating and is sent to the HLR together with the IMSI. The HLR

makes no use of it but includes it together with the IMSI in all messages sent to the VLR concerning that MS.

2.2 Composition of IMSI

IMSI is composed as shown in figure 1.

3GPP


11/53

3GPP TS 23.003 V7.3.0 (2007-03)11Release 7T

MCC

Not more than 15 digits

3 di its 2 or 3

MNC MSIN

NMSI

IMSI

Figure 1: Structure of IMSI

IMSI is composed of three parts:

1) Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of domicile of

the mobile subscriber;

2) Mobile Network Code (MNC) consisting of two or three digits for GSM/UMTS applications. The MNCidentifies the home PLMN of the mobile subscriber. The length of the MNC (two or three digits) depends on the

value of the MCC. A mixture of two and three digit MNC codes within a single MCC area is not recommended

and is outside the scope of this specification.

3) Mobile Subscriber Identification Number (MSIN) identifying the mobile subscriber within a PLMN.

The National Mobile Subscriber Identity (NMSI) consists of the Mobile Network Code and the Mobile Subscriber

Identification Number.

2.3 Allocation principles

IMSI shall consist of decimal digits (0 through 9) only.

The number of digits in IMSI shall not exceed 15.

The allocation of Mobile Country Codes (MCCs) is administered by the ITU-T. The current allocation is given in the

COMPLEMENT TO ITU-T RECOMMENDATION E.212 [44].

The allocation of National Mobile Subscriber Identity (NMSI) is the responsibility of each administration.

If more than one PLMN exists in a country, the same Mobile Network Code should not be assigned to more than one

PLMN.

The allocation of IMSIs should be such that not more than the digits MCC + MNC of the IMSI have to be analysed in a

foreign PLMN for information transfer.

2.4 Structure of TMSI

Since the TMSI has only local significance (i.e. within a VLR and the area controlled by a VLR, or within an SGSN and

the area controlled by an SGSN), the structure and coding of it can be chosen by agreement between operator and

manufacturer in order to meet local needs.

The TMSI consists of 4 octets. It can be coded using a full hexadecimal representation.

In order to avoid double allocation of TMSIs after a restart of an allocating node, some part of the TMSI may be related

to the time when it was allocated or contain a bit field which is changed when the allocating node has recovered from

the restart.

In areas where both MSC-based services and SGSN-based services are provided, some discrimination is neededbetween the allocation of TMSIs for MSC-based services and the allocation of TMSIs for SGSN-based services. The

discrimination shall be done on the 2 most significant bits, with values 00, 01, and 10 being used by the VLR, and 11

being used by the SGSN.

3GPP


12/53


13/53

3GPP TS 23.003 V7.3.0 (2007-03)13Release 7T

Table 1: TLLI structure

31 30 29 28 27 26 to 0 Type of TLLI1 1 T T T T Local TLLI1 0 T T T T Foreign TLLI

0 1 1 1 1 R Random TLLI0 1 1 1 0 A Auxiliary TLLI0 1 1 0 X X Reserved0 1 0 X X X Reserved0 0 0 0 G G Part of the assigned G-RNTI

0 0 0 1 R R Random G-RNTI

'T', 'R', 'A' and 'X' indicate bits which can take any value for the type of TLLI. More precisely, 'T' indicates bits derived

from a P-TMSI, 'R' indicates bits chosen randomly, 'A' indicates bits chosen by the SGSN, 'G' indicates bits derived

from the assigned G-RNTI and 'X' indicates bits in reserved ranges.

2.7 Structure of P-TMSI Signature

The P-TMSI Signature consists of 3 octets and may be allocated by the SGSN.

The network shall not allocate a P-TMSI Signature with all 24 bits equal to 1 (this is because the P-TMSI Signature

must be stored in the SIM, and the SIM uses 3 octets with all bits equal to 1 to indicate that no valid P-TMSI signature

is available.

3 Numbering plan for mobile stations

3.1 General

The structure of the following numbers is defined below:

- the number used by a subscriber of a fixed (or mobile) network to call a mobile station of a PLMN;

- the network addresses used for packet data communication between a mobile station and a fixed (or mobile)

station;

- mobile station roaming numbers.

One or more numbers of the ISDN numbering plan shall be assigned to a mobile station to be used for all calls to thatstation, i.e. the assignment of at least one MSISDN to a mobile station is mandatory.

NOTE: For card operated stations the ISDN number should be assigned to the holder of the card (personal

number).

3.2 Numbering plan requirements

In principle, it should be possible for any subscriber of the ISDN or PSTN to call any MS in a PLMN. This implies that

ISDN numbers for MSs should comply with the ISDN numbering plan in the home country of the MS.

The ISDN numbers of MSs should be composed in such a way that standard ISDN/PSTN charging can be used for calls

to MSs.

It should be possible for each administration to develop its own independent numbering/addressing plan for MSs.

The numbering/addressing plan should not limit the possibility for MSs to roam among PLMNs.

It should be possible to change the IMSI without changing the ISDN number allocated to an MS and vice versa.

In principle, it should be possible for any subscriber of the CSPDN/PSPDN to call any MS in a PLMN. This implies

that it may be necessary for an MS to have a X.121 number.

3GPP


14/53

3GPP TS 23.003 V7.3.0 (2007-03)14Release 7T

In principle, it should be possible for any fixed or mobile terminal to communicate with a mobile terminal using an IP

v4 address or IP v6 address.

3.3 Structure of MS international PSTN/ISDN number(MSISDN)

MS international ISDN numbers are allocated from the ITU-T Recommendation E.164 numbering plan; see also ITU-T

Recommendation E.213. The structure of the MS international ISDN number will then be as shown in figure 2.

mobile number

National (significant)

Mobile station international

ISDN number

CC NDC SN

Figure 2: Number Structure of MSISDN

The number consists of:

- Country Code (CC) of the country in which the MS is registered, followed by:

- National (significant) mobile number, which consists of:

- National Destination Code (NDC) and

- Subscriber Number (SN).

For GSM/UMTS applications, a National Destination Code is allocated to each PLMN. In some countries more than

one NDC may be required for each PLMN.

The composition of the MS international ISDN number should be such that it can be used as a global title address in the

Signalling Connection Control Part (SCCP) for routeing messages to the home location register of the MS. The country

code (CC) and the national destination code (NDC) will provide such routeing information. If further routeing

information is required, it should be contained in the first few digits of the subscriber number (SN).

A sub-address may be appended to an ISDN number for use in call setup and in supplementary service operations where

an ISDN number is required (see ITU-T Recommendations E.164, clause 11.2 and X.213 annex A). The sub-address is

transferred to the terminal equipment denoted by the ISDN number.

The maximum length of a sub-address is 20 octets, including one octet to identify the coding scheme for the

sub-address (see ITU-T Recommendation X.213, annex A). All coding schemes described in ITU-T Recommendation

X.213, annex A are supported in GSM and UMTS.

3.4 Mobile Station Roaming Number (MSRN) for PSTN/ISDNrouteing

The Mobile Station Roaming Number (MSRN) is used to route calls directed to an MS. On request from the Gateway

MSC via the HLR it is temporarily allocated to an MS by the VLR with which the MS is registered; it addresses the

Visited MSC collocated with the assigning VLR. More than one MSRN may be assigned simultaneously to an MS.

The MSRN is passed by the HLR to the Gateway MSC to route calls to the MS.

The Mobile Station Roaming Number for PSTN/ISDN routing shall have the same structure as international ISDN

numbers in the area in which the roaming number is allocated, i.e.:

3GPP


15/53

3GPP TS 23.003 V7.3.0 (2007-03)15Release 7T

- the country code of the country in which the visitor location register is located;

- the national destination code of the visited PLMN or numbering area;

- a subscriber number with the appropriate structure for that numbering area.

The MSRN shall not be used for subscriber dialling. It should be noted that the MSRN can be identical to the MSISDN

(clause 3.3) in certain circumstances. In order to discriminate between subscriber generated access to these numbers andre-routeing performed by the network, re-routeing or redirection indicators or other signalling means should be used, if

available.

3.5 Structure of Mobile Station International Data Number

The structure of MS international data numbers should comply with the data numbering plan of ITU-T

Recommendation X.121 as applied in the home country of the mobile subscriber. Implications for numberinginterworking functions which may need to be provided by the PLMN (if the use of X.121 numbers is required) are

indicated in 3GPP TS 23.070 [4].

3.6 Handover NumberThe handover number is used for establishment of a circuit between MSCs to be used for a call being handed over. Thestructure of the handover number is the same as the structure of the MSRN. The handover number may be reused in the

same way as the MSRN.

3.7 Structure of an IP v4 address

One or more IP address domains may be allocated to each PLMN. The IP v4 address structure is defined in

RFC 791 [14].

An IP v4 address may be allocated to an MS either permanently or temporarily during a connection with the network.

3.8 Structure of an IP v6 address

One or more IP address domains could be allocated to each PLMN. The IP v6 address structure is defined in

RFC 2373 [15].

An IP v6 address may be allocated to an MS either permanently or temporarily during a connection with the network

If the dynamic IPv6 stateless address autoconfiguration procedure is used, then each PDP context, or group of PDP

contexts sharing the same IP address, is assigned a unique prefix as defined in 3GPP TS 23.060 [3].

As described in RFC 2462 [21] and RFC 3041 [22], the MS can change its interface identifier without the GPRS

network being aware of the change.

4 Identification of location areas and base stations

4.1 Composition of the Location Area Identification (LAI)

The Location Area Identification shall be composed as shown in figure 3:

Location Area Identification

MCC MNC LAC

Figure 3: Structure of Location Area Identification

3GPP


16/53

3GPP TS 23.003 V7.3.0 (2007-03)16Release 7T

The LAI is composed of the following elements:

- Mobile Country Code (MCC) identifies the country in which the GSM PLMN is located. The value of the MCC

is the same as the three digit MCC contained in international mobile subscriber identity (IMSI);

- Mobile Network Code (MNC) is a code identifying the GSM PLMN in that country. The MNC takes the same

value as the two or three digit MNC contained in IMSI;

- Location Area Code (LAC) is a fixed length code (of 2 octets) identifying a location area within a PLMN. This

part of the location area identification can be coded using a full hexadecimal representation except for the

following reserved hexadecimal values:

0000, and

FFFE.

These reserved values are used in some special cases when no valid LAI exists in the MS (see 3GPP TS 24.008

[5], 3GPP TS 31.102 [27] and 3GPP TS 51.011 [9]).

A specific GSM PLMN code (MCC + MNC) may be broadcast for mobile stations which are not compatible with

SoLSA and which do not understand the exclusive access indicator (see 3GPP TS 23.073 [30]). The reserved value of

the escape PLMN code is MCC = 901 and MNC = 08.

4.2 Composition of the Routing Area Identification (RAI)

The Routing Area Identification shall be composed as shown in figure 4:

Figure 4: Structure of Routing Area Identification

The RAI is composed of the following elements:

- A valid Location Area Identity (LAI) as defined in clause 4.1. Invalid LAI values are used in some special cases

when no valid RAI exists in the mobile station (see 3GPP TS 24.008 [5], 3GPP TS 31.102 [27] and

3GPP TS 51.011 [9]).

- Routeing Area Code (RAC) which is a fixed length code (of 1 octet) identifying a routeing area within a location

area.

4.3 Base station identification

4.3.1 Cell Identity (CI) and Cell Global Identification (CGI)

The BSS and cell within the BSS are identified within a location area or routeing area by adding a Cell Identity (CI) to

the location area or routeing area identification, as shown in figure 5. The CI is of fixed length with 2 octets and it can

be coded using a full hexadecimal representation.

The Cell Global Identification is the concatenation of the Location Area Identification and the Cell Identity. Cell

Identity shall be unique within a location area.

3GPP


17/53

3GPP TS 23.003 V7.3.0 (2007-03)17Release 7T

MCC LACMNC CI

Location Area Identification

Cell Global Identification (CGI)

Figure 5: Structure of Cell Global Identification

4.3.2 Base Station Identify Code (BSIC)

The base station identity code is a local colour code that allows an MS to distinguish between different neighbouring

base stations. BSIC is a 6 bit code which is structured as shown in Figure 6.

NCC BCC

PLMN colour code BS colour code

3 bits3 bits

Figure 6: Structure of BSIC

In the definition of the NCC, care should be taken to ensure that the same NCC is not used in adjacent PLMNs which

may use the same BCCH carrier frequencies in neighbouring areas. Therefore, to prevent potential deadlocks, a

definition of the NCC appears in annex A. This annex will be reviewed in a co-ordinated manner when a PLMN is

created.

4.4 Regional Subscription Zone Identity (RSZI)

A PLMN-specific regional subscription defines unambiguously for the entire PLMN the regions in which roaming is

allowed. It consists of one or more regional subscription zones. The regional subscription zone is identified by a

Regional Subscription Zone Identity (RSZI). A regional subscription zone identity is composed as shown in figure 7.

NDCCC ZC

Zone Code, Two octets

RSZI

Figure 7: Structure of Regional Subscription Zone Identity (RSZI)

The elements of the regional subscription zone identity are:

1) the Country Code (CC) which identifies the country in which the PLMN is located;

2) the National Destination Code (NDC) which identifies the PLMN in that country;

3) the Zone Code (ZC) which identifies a regional subscription zone as a pattern of allowed and not allowed

location areas uniquely within that PLMN.

CC and NDC are those of an ITU-T E.164 VLR or SGSN number (see clause 5.1) of the PLMN; they are coded with a

trailing filler, if required. ZC has fixed length of two octets and is coded in full hexadecimal representation.

RSZIs, including the zone codes, are assigned by the VPLMN operator. The zone code is evaluated in the VLR or

SGSN by information stored in the VLR or SGSN as a result of administrative action. If a zone code is received by a

3GPP


18/53

3GPP TS 23.003 V7.3.0 (2007-03)18Release 7T

VLR or SGSN during updating by the HLR and this zone code is related to that VLR or SGSN, the VLR or SGSN shall

be able to decide for all its MSC or SGSN areas and all its location areas whether they are allowed or not allowed.

For details of assignment of RSZI and of ZC as subscriber data see 3GPP TS 23.008 [2].

For selection of RSZI at location updating by comparison with the leading digits of the VLR or SGSN number and for

transfer of ZC from the HLR to VLR and SGSN see 3GPP TS 29.002 [31].

4.5 Location Number

A location number is a number which defines a specific location within a PLMN. The location number is formatted

according to ITU-T Recommendation E.164, as shown in figure 8. The Country Code (CC) and National Destination

Code (NDC) fields of the location number are those which define the PLMN of which the location is part.

CC NDC LSP

Figure 8: Location Number Structure

The structure of the locally significant part (LSP) of the location number is a matter for agreement between the PLMN

operator and the national numbering authority in the PLMN's country. It is desirable that the location number can be

interpreted without the need for detailed knowledge of the internal structure of the PLMN; the LSP should therefore

include the national destination code in the national numbering plan for the fixed network which defines the geographic

area in which the location lies.

The set of location numbers for a PLMN shall be chosen so that a location number can be distinguished from the

MSISDN of a subscriber of the PLMN. This will allow the PLMN to trap attempts by users to dial a location number.

4.6 Composition of the Service Area Identification (SAI)

Void (see subclause 12.5).

5 Identification of MSCs, GSNs and location registers

5.1 Identification for routeing purposes

MSCs, GSNs and location registers are identified by international PSTN/ISDN numbers and/or Signalling Point Codes

("entity number", i.e., "HLR number", "VLR number", "MSC number", "SGSN number" and "GGSN number") in each

PLMN.

Additionally SGSNs and GGSNs are identified by GSN Addresses. These are the SGSN Address and the GGSN

Address.

A GSN Address shall be composed as shown in figure 9.

GSN Address

Address Type Address Length Address

2 bits 6 bits 4 to 16octets

Figure 9: Structure of GSN Address

3GPP


19/53

3GPP TS 23.003 V7.3.0 (2007-03)19Release 7T

The GSN Address is composed of the following elements:

1) The Address Type, which is a fixed length code (of 2 bits) identifying the type of address that is used in the

Address field.

2) The Address Length, which is a fixed length code (of 6 bits) identifying the length of the Address field.

3) The Address, which is a variable length field which contains either an IPv4 address or an IPv6 address.

Address Type 0 and Address Length 4 are used when Address is an IPv4 address.

Address Type 1 and Address Length 16 are used when Address is an IPv6 address.

The IP v4 address structure is defined in RFC 791 [14].

The IP v6 address structure is defined in RFC 2373 [15].

5.2 Identification of HLR for HLR restoration application

HLR may also be identified by one or several "HLR id(s)", consisting of the leading digits of the IMSI (MCC + MNC +

leading digits of MSIN).

6 International Mobile Station Equipment Identity andSoftware Version Number

6.1 General

The structure and allocation principles of the International Mobile station Equipment Identity and Software Version

number (IMEISV) and the International Mobile station Equipment Identity (IMEI) are defined below.

The Mobile Station Equipment is uniquely defined by the IMEI or the IMEISV.

6.2 Composition of IMEI and IMEISV

6.2.1 Composition of IMEI

The International Mobile station Equipment Identity (IMEI) is composed as shown in figure 10.

IMEI 15 digits

TAC

8 digits

SNR

6 digits

s are

1 digit

Figure 10: Structure of IMEI

The IMEI is composed of the following elements (each element shall consist of decimal digits only):

- Type Allocation Code (TAC). Its length is 8 digits;

- Serial Number (SNR) is an individual serial number uniquely identifying each equipment within the TAC. Its

length is 6 digits;

- Spare digit: this digit shall be zero, when transmitted by the MS.

3GPP


20/53


21/53

3GPP TS 23.003 V7.3.0 (2007-03)21Release 7T

within a PLMN. However, no uniqueness is required between the sets of Group IDs. These sets may be intersecting or

even identical, at the option of the network operator.

The Group ID is a number with a maximum value depending on the composition of the voice group call reference or

voice broadcast call reference defined in section 7.3.

For definition of Group ID on the radio interface, A interface and Abis interface, see 3GPP TS 44.068 [46] and 3GPP

TS 44.069 [47].

For definition of Group ID coding on MAP protocol interfaces, see 3GPP TS 29.002 [31].

VGCS or VBS shall also be provided for roaming. If this applies, certain Group IDs shall be defined as supra-PLMN

Group IDs which have to be co-ordinated between the network operators and which shall be known in the networks andin the SIM.

The format of the Group ID is identical for VBS and VGCS.

7.2 Group Call Area Identification

Grouping of cells into specific group call areas occurs in support of both the Voice Group Call Service and the VoiceBroadcast Service. These service areas are known by a "Group Call Area Identity" (Group Call Area Id). No restrictions

are placed on what cells may be grouped into a given group call area.

The Group Call Area ID is a number uniquely assigned to a group call area in one network and with a maximum value

depending on the composition of the voice group call reference or voice broadcast reference defined under 7.3.

The formats of the Group Call Area ID for VGCS and the Group Call Area ID for VBS are identical.

7.3 Voice Group Call and Voice Broadcast Call References

Specific instances of voice group calls (VGCS) and voice broadcast calls (VBS) within a given group call area are

known by a "Voice Group Call Reference" or by a "Voice Broadcast Call Reference" respectively.

Each voice group call or voice broadcast call in one network is uniquely identified by its Voice Group Call Reference or

Voice Broadcast Call Reference. The Voice Group Call Reference or Voice Broadcast Call Reference is composed of

the Group ID and the Group Call Area ID. The composition of the group call area ID and the group ID can be specific

for each network operator.

For definition of Group Call Reference (with leading zeros inserted as necessary) on the radio interface, A interface and

Abis interface, see 3GPP TS 24.008 [5], 3GPP TS 44.068 [46] and 3GPP TS 44.069 [47].

For definition of Group Call Reference (also known as ASCI Call Reference, Voice Group Call Reference or Voice

Broadcast Call Reference) coding on MAP protocol interfaces, see 3GPP TS 29.002 [31].

The format is given in figure 12.

GroupCallArea ID

Group ID

Voice Group Call Reference /Voice Broadcast Call Reference

Figure 12: Voice Group Call Reference / Voice Broadcast Call Reference

3GPP


22/53

3GPP TS 23.003 V7.3.0 (2007-03)22Release 7T

8 SCCP subsystem numbers

Subsystem numbers are used to identify applications within network entities which use SCCP signalling. In GSM and

UMTS, subsystem numbers may be used between PLMNs, in which case they are taken from the globally standardized

range (1 - 31) or the part of the national network range (129 - 150) reserved for GSM/UMTS use between PLMNs. For

use within a PLMN, they are taken from the part of the national network range (32 - 128 & 151 - 254) not reserved forGSM/UMTS use between PLMNs.

8.1 Globally standardized subsystem numbers used forGSM/UMTS

The following globally standardised subsystem numbers have been allocated for use by GSM/UMTS:

0000 0110 HLR (MAP);

0000 0111 VLR (MAP);

0000 1000 MSC (MAP);

0000 1001 EIR (MAP);

0000 1010 is allocated for evolution (possible Authentication Centre).

8.2 National network subsystem numbers used for GSM/UMTS

The following national network subsystem numbers have been allocated for use within GSM/UMTS networks:

1111 1001 PCAP;

1111 1010 BSC (BSSAP-LE);

1111 1011 MSC (BSSAP-LE);

1111 1100 SMLC (BSSAP-LE);

1111 1101 BSS O&M (A interface);

1111 1110BSSAP (A interface).

The following national network subsystem numbers have been allocated for use within and between GSM/UMTS

networks:

1000 1110 RANAP;

1000 1111 RNSAP;

1001 0001 GMLC (MAP);

1001 0010 CAP;

1001 0011gsmSCF (MAP) or IM-SSF (MAP) or Presence Network Agent;

1001 0100 SIWF (MAP);

1001 0101 SGSN (MAP);

1001 0110 GGSN (MAP).

3GPP


23/53

3GPP TS 23.003 V7.3.0 (2007-03)23Release 7T

9 Definition of Access Point Name

In the GPRS backbone, an Access Point Name (APN) is a reference to a GGSN. To support inter-PLMN roaming, the

internal GPRS DNS functionality is used to translate the APN into the IP address of the GGSN.

9.1 Structure of APN

The APN is composed of two parts as follows:

The APN Network Identifier; this defines to which external network the GGSN is connected and optionally arequested service by the MS. This part of the APN is mandatory.

The APN Operator Identifier; this defines in which PLMN GPRS backbone the GGSN is located. This part ofthe APN is optional.

The APN Operator Identifier is placed after the APN Network Identifier. An APN consisting of both the Network

Identifier and Operator Identifier corresponds to a DNS name of a GGSN; the APN has, after encoding as defined in theparagraph below, a maximum length of 100 octets.

The encoding of the APN shall follow the Name Syntax defined in RFC 2181 [18], RFC 1035 [19] and RFC 1123 [20].

The APN consists of one or more labels. Each label is coded as a one octet length field followed by that number of

octets coded as 8 bit ASCII characters. Following RFC 1035 [19] the labels shall consist only of the alphabetic

characters (A-Z and a-z), digits (0-9) and the hyphen (-). Following RFC 1123 [20], the label shall begin and end with

either an alphabetic character or a digit. The case of alphabetic characters is not significant. The APN is not terminated

by a length byte of zero.

NOTE: A length byte of zero is added by the SGSN at the end of the APN before interrogating a DNS server.

For the purpose of presentation, an APN is usually displayed as a string in which the labels are separated by dots (e.g.

"Label1.Label2.Label3").

9.1.1 Format of APN Network Identifier

The APN Network Identifier shall contain at least one label and shall have, after encoding as defined in subclause 9.1

above, a maximum length of 63 octets. An APN Network Identifier shall not start with any of the strings "rac", "lac","sgsn" or "rnc", and it shall not end in ".gprs". Further, it shall not take the value "*".

In order to guarantee uniqueness of APN Network Identifiers within or between GPRS PLMN, an APN Network

Identifier containing more than one label shall correspond to an Internet domain name. This name should only be

allocated by the PLMN if that PLMN belongs to an organisation which has officially reserved this name in the Internet

domain. Other types of APN Network Identifiers are not guaranteed to be unique within or between GPRS PLMNs.

An APN Network Identifier may be used to access a service associated with a GGSN. This may be achieved by

defining:

- an APN which corresponds to a FQDN of a GGSN, and which is locally interpreted by the GGSN as a requestfor a specific service, or

- an APN Network Identifier consisting of 3 or more labels and starting with a Reserved Service Label, or anAPN Network Identifier consisting of a Reserved Service Label alone, which indicates a GGSN by the nature of

the requested service. Reserved Service Labels and the corresponding services they stand for shall be agreed

between operators who have GPRS roaming agreements.

9.1.2 Format of APN Operator Identifier

The APN Operator Identifier is composed of three labels. The last label (or domain) shall be "gprs". The first and

second labels together shall uniquely identify the GPRS PLMN.

For each operator, there is a default APN Operator Identifier (i.e. domain name). This default APN Operator Identifier

is derived from the IMSI as follows:

3GPP


24/53

3GPP TS 23.003 V7.3.0 (2007-03)24Release 7T

"mnc.mcc.gprs"

where:

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

and are derived from the components of the IMSI defined in subclause 2.2.

This default APN Operator Identifier is used in inter-PLMN roaming situations when attempting to translate an APN

consisting only of a Network Identifier into the IP address of the GGSN in the HPLMN. The PLMN may provide DNStranslations for other, more human-readable, APN Operator Identifiers in addition to the default Operator Identifier

described above.

In order to guarantee inter-PLMN DNS translation, the and coding used in the

"mnc.mcc.gprs" format of the APN OI shall be:

= 3 digits

= 3 digits

If there are only 2 significant digits in the MNC, one "0" digit is inserted at the left side to fill the 3 digits

coding of MNC in the APN OI.

As an example, the APN OI for MCC 345 and MNC 12 will be coded in the DNS as "mnc012.mcc345.gprs".

9.2 Definition of the Wild Card APN

The APN field in the HLR may contain a wild card APN if the HPLMN operator allows the subscriber to access any

network of a given PDP Type. If an SGSN has received such a wild card APN, it may either choose the APN NetworkIdentifier received from the Mobile Station or a default APN Network Identifier for addressing the GGSN when

activating a PDP context.

9.2.1 Coding of the Wild Card APNThe wild card APN is coded as an APN with "*" as its single label, (i.e. a length octet with value one, followed by theASCII code for the asterisk).

9.3 Definition of Emergency APN

The Emergency APN (Em-APN) for the support of IMS Emergency calls shall take the form of a common, reserved

Network Identifier of the form "sos".

For IMS Emergency call over PS domain emergency APN shall contain only Em-APN (Network Identifier).

As an example, Em-APN coding in DNS, when the given PS domain operators MCC is 345 and MNC is 12, shall be

the following:

"sos.mnc012.mcc345.gprs"

where:

"sos" is the Em-APN Network Identifier;

"mnc012.mcc345.gprs" is the given operators APN Operator Identifier.

3GPP


25/53

3GPP TS 23.003 V7.3.0 (2007-03)25Release 7T

10 Identification of the Cordless Telephony Systementities

10.1 General description of CTS-MS and CTS-FP IdentitiesEvery CTS-FP broadcasts a local identity - the Fixed Part Beacon Identity (FPBI) - which contains an Access Rights

Identity. Every CTS-MS has both an Access Rights Key and a CTS Mobile Subscriber Identity (CTSMSI). These

operate as a pair. A CTS-MS is allowed to access any CTS-FP which broadcasts an FPBI which can be identified by

any of the CTS-MS Access Rights Keys of that CTS-MS. The CTS-MS Access Rights Key contains the FPBI and the

FPBI Length Indicator (FLI) indicating the relevant part of the FPBI used to control access.

10.2 CTS Mobile Subscriber Identities

10.2.1 General

Each CTS-MS has one or more temporary identities which are used for paging and to request access. The structure and

allocation principles of the CTS Mobile Subscriber Identities (CTSMSI) are defined below.

Composition of the CTSMSI

bit No 22 1+-------------------------------------------+

| | |+----------------------+Type||

CTSMSI 22 bits

Figure 13: Structure of CTSMSI

The CTSMSI is composed of the following elements:

- CTSMSI Type. Its length is 2 bits;

- Significant Part. Its length is 20 bits.

The following CTSMSI Type values have been allocated for use by CTS:

00 Default Individual CTSMSI;

01 Reserved;

10 Assigned Individual CTSMSI;

11 Assigned Connectionless Group CTSMSI.

10.2.3 Allocation principles

The default Individual CTSMSI contains the least significant portion of the IMSI. This is the default CTS-MS identity.

Assigned CTSMSIs are allocated by the CTS-FP during enrolment, registration and other access procedures. Significant

Part of the assigned CTSMSI shall be allocated in the range 00001-FFFFE. CTS-FP shall not allocate Significant Part

equal to 00000 or to FFFFF and shall not allocate Assigned CTSMSI using Reserved Type value. Such assignments

shall be ignored by the CTS-MS.

Assigned CTSMSIs are allocated in ciphered mode.

NOTE: The assigned individual CTSMSI should be updated whenever it is sent in clear text on the CTS radio

interface during RR connection establishment.

3GPP


26/53

3GPP TS 23.003 V7.3.0 (2007-03)26Release 7T

The value FFFFF from the set of Assigned Connectionless Group CTSMSI shall be considered in all CTS-MS as the

value of the Connectionless Broadcast Identifier.

10.2.4 CTSMSI hexadecimal representation

The 22 bits of CTSMSI are padded with 2 leading zeroes to give a 6 digit hexadecimal value.

EXAMPLE: binary CTSMSI value: 11 1001 0010 0000 1011 1100

hexadecimal CTSMSI value: 39 20 BC.

10.3 Fixed Part Beacon Identity

10.3.1 General

Each CTS-FP has one Fixed Part Beacon Identity known by the enrolled CTS-MSs. The FPBI is periodically broadcaston the BCH logical channel so that the CTS-MSs are able to recognise the identity of the CTS-FP. The FPBI contains

an Access Rights Identity.

Enrolled CTS-MSs shall store the FPBI to which their assigned CTSMSIs are related.

Below the structure and allocation principles of the Fixed Part Beacon Identity (FPBI) are defined.

10.3.2 Composition of the FPBI

10.3.2.1 FPBI general structure

bit No 19 1+-------------------------------------+

| | |+-------------------+Type| Significant Part |

FPBI 19 bits

Figure 14: General structure of FPBI

The FPBI is composed of the following elements:

- FPBI Type. Its length is 2 bits;

- FPBI Significant Part. Its length is 17 bits.

NOTE: The three LSBs bits of the FPBI form the 3-bit training sequence code (TSC). See 3GPP TS 45.056 [35].

The following FPBI Type values have been allocated for use by CTS:

00 FPBI class A: residential and single-cell systems;

01 FPBI class B: multi-cell PABXs.

All other values are reserved and CTS-MSs shall treat these values as FPBI class A.

10.3.2.2 FPBI class A

This class is intended to be used for small residential and private (PBX) single cell CTS-FP.

3GPP


27/53

3GPP TS 23.003 V7.3.0 (2007-03)27Release 7T

bit No 19 1++-------------------------------------

|0 0| |++-------------------

Type| PN |F

FPBI 19 bits

Figure 15: Structure of FPBI class A

The FPBI class A is composed of the following elements:

- FPBI Class A Type. Its length is 2 bits and its value is 00;

- Fixed Part Number (FPN). Its length is 17 bits. The FPN contains the least significant bits of the Serial Number

part of the IFPEI.

The FPBI Length Indicator shall be set to 19 for a class A FPBI.

10.3.2.3 FPBI class B

This class is reserved for more complex private installation such as multi-cell PABXs.

bit No 19 1+-------------------------------------+

|0 1| |+-------------------+Type| CNN + FPN + RPN |

FPBI 19 bits

Figure 16: Structure of FPBI class B

The FPBI class B is composed of the following elements:

- FPBI Class B Type. Its length is 2 bits and its value is 01;

- CTS Network Number (CNN). Its length is defined by the manufacturer or the system installer;

- Fixed Part Number (FPN). Its length is defined by the manufacturer or the system installer;

- Radio Part Number (RPN) assigned by the CTS manufacturer or system installer. Its length is defined by the

manufacturer or the system installer.

NOTE: RPN is used to separate a maximum of 2RPN length different cells from each other. This defines a cluster of

cells supporting intercell handover. RPN length is submitted to a CTS-MS as a result of a successful

attachment.

The FPBI Length Indicator shall be set to (2 + CNN Length) for a class B FPBI.


The FPBI shall be allocated during the CTS-FP initialisation procedure. Any change to the value of the FPBI of a givenCTS-FP shall be considered as a CTS-FP re-initialisation; i.e. each enrolled CTS-MS needs to be enrolled again.

FPBI are not required to be unique (i.e. several CTS-FP can have the same FPBI in different areas). Care should be

taken to limit CTS-MS registration attempts to a fixed part with the same FPBI as another fixed part.

10.4 International Fixed Part Equipment Identity

10.4.1 General

The structure and allocation principles of the International Fixed Part Equipment Identity (IFPEI) are defined below.

3GPP


28/53

3GPP TS 23.003 V7.3.0 (2007-03)28Release 7T

10.4.2 Composition of the IFPEI

6 digits 2d 6 digits 2d+-----------++---++-----------++---+

| || || || |+- +-----++--++------++--

TAC FAC SNR SVNIFPEI 16 digits

Figure 17: Structure of IFPEI

The IFPEI is composed of the following elements (each element shall consist of decimal digits only):

- Type Approval Code (TAC). Its length is 6 decimal digits;

- Final Assembly Code (FAC). Its length is 2 decimal digits;

- Serial NumbeR (SNR). Its length is 6 decimal digits;

- Software Version Number (SVN) identifies the software version number of the fixed part equipment. Its lengthis 2 digits.

Regarding updates of the IFPEI: the TAC, FAC and SNR shall be physically protected against unauthorised change (see

3GPP TS 42.009 [36]); i.e. only the SVN part of the IFPEI can be modified.


The Type Approval Code (TAC) is issued by a central body.

The place of final assembly (FAC) is encoded by the manufacturer.

Manufacturers shall allocate unique serial numbers (SNR) in a sequential order.

The Software Version Number (SVN) is allocated by the manufacturer after authorisation by the type approval

authority. SVN value 99 is reserved for future use.

10.5 International Fixed Part Subscription Identity

10.5.1 General

The structure and allocation principles of the International Fixed Part Subscription Identity (IFPSI) are defined below.

10.5.2 Composition of the IFPSI

No more than 15 digits

3d 3d |+-----++-----++------//--------+

| || || |+---++---++---//----+

MCC CON FPIN |

NFPSI

IFPSI

Figure 18: Structure of IFPSI

The IFPSI is composed of the following elements (each element shall consist of decimal digits only):

3GPP


29/53

3GPP TS 23.003 V7.3.0 (2007-03)29Release 7T

- Mobile Country Code (MCC) consisting of three digits. The MCC identifies the country of the CTS-FP

subscriber (e.g. 208 for France);

- CTS Operator Number (CON). Its length is three digits;

- Fixed Part Identification Number (FPIN) identifying the CTS-FP subscriber.

The National Fixed Part Subscriber Identity (NFPSI) consists of the CTS Operator Number and the Fixed PartIdentification Number.


IFPSI shall consist of decimal characters (0 to 9) only.

The allocation of Mobile Country Codes (MCCs) is administered by the ITU-T.

The allocation of CTS Operator Number (CON) and the structure of National Fixed Part Subscriber Identity (NFPSI)

are the responsibility of each National Regulation Authority.

CTS Operators shall allocate unique Fixed Part Identification Numbers.

11 Identification of Localised Service Area

Cells may be grouped into specific localised service areas. Each localised service area is identified by a localised

service area identity (LSA ID). No restrictions are placed on what cells may be grouped into a given localised service

area.

The LSA ID can either be a PLMN significant number or a universal identity. This shall be known both in the networks

and in the SIM.

The LSA ID consists of 24 bits, numbered from 0 to 23, with bit 0 being the LSB. Bit 0 indicates whether the LSA is a

PLMN significant number or a universal LSA. If the bit is set to 0 the LSA is a PLMN significant number; if it is set to

1 it is a universal LSA.

The LSA ID shall be composed as shown in figure 19:

1 bit

LSA ID

23 bits

MSB LSB

Figure 19: Structure of LSA ID

12 Identification of PLMN, RNC, Service Area, CN domainand Shared Network Area

The following clauses describe identifiers which are used by both the CN and the UTRAN across the Iu interface. For

identifiers which are solely used within the UTRAN, see 3GPP TS 25.401 [16].

NOTE: in the following subclauses, the double vertical bar notation || indicates the concatenation operator.

3GPP


30/53

3GPP TS 23.003 V7.3.0 (2007-03)30Release 7T

12.1 PLMN Identifier

A Public Land Mobile Network is uniquely identified by its PLMN identifier. PLMN-Id consists of Mobile Country

Code (MCC) and Mobile Network Code (MNC).

- PLMN-Id = MCC || MNC

The MCC and MNC are predefined within a UTRAN, and set in the RNC via O&M.

12.2 CN Domain Identifier

A CN Domain Edge Node is identified within the UTRAN by its CN Domain Identifier. The CN Domain identifier is

used over UTRAN interfaces to identify a particular CN Domain Edge Node for relocation purposes. The CN Domain

identifier for Circuit Switching (CS) consists of the PLMN-Id and the LAC, whereas for Packet Switching (PS) it

consists of the PLMN-Id, the LAC, and the RAC of the first accessed cell in the target RNS.

The two following CN Domain Identifiers are defined:

- CN CS Domain-Id = PLMN-Id || LAC

- CN PS Domain-Id = PLMN-Id || LAC || RAC

The LAC and RAC are defined by the operator, and set in the RNC via O&M.

For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413 [17].

12.3 CN Identifier

A CN node is uniquely identified within a PLMN by its CN Identifier (CN-Id). The CN-Id together with the PLMN

identifier globally identifies the CN node. The CN-Id together with the PLMN-Id is used as the CN node identifier in

RANAP signalling over the Iu interface.

Global CN-Id = PLMN-Id || CN-Id

The CN-Id is defined by the operator, and set in the nodes via O&M.


12.4 RNC Identifier

An RNC node is uniquely identified by its RNC Identifier (RNC-Id). The RNC-Id of an RNC is used in the UTRAN, in

a GERAN which is operating in GERAN Iu mode and between them. A BSC which is part of a GERAN operating in Iu

mode is uniquely identified by its RNC Identifier (RNC-Id). The RNC-Id of a BSC is used in a GERAN which is

operating in GERAN Iu mode, in the UTRAN and between them. RNC-Id together with the PLMN identifier globally

identifies the RNC. The RNC-Id on its own or the RNC-Id together with the PLMN-Id is used as the RNC identifier inthe UTRAN Iub, Iur and Iu interfaces. The SRNC-Id is the RNC-Id of the SRNC. The C-RNC-Id is the RNC-Id of thecontrolling RNC. The D-RNC-Id is the RNC Id of the drift RNC.

- Global RNC-Id = PLMN-Id || RNC-Id

The RNC-Id is defined by the operator, and set in the RNC via O&M


For the usage of this identifier on Iur-g, see 3GPP TS 43.130 [43].

12.5 Service Area Identifier

The Service Area Identifier (SAI) is used to identify an area consisting of one or more cells belonging to the same

Location Area. Such an area is called a Service Area and can be used for indicating the location of a UE to the CN.

3GPP


31/53

3GPP TS 23.003 V7.3.0 (2007-03)31Release 7T

The Service Area Code (SAC) together with the PLMN-Id and the LAC constitute the Service Area Identifier.

- SAI = PLMN-Id || LAC || SAC

The SAC is defined by the operator, and set in the RNC via O&M.


3GPP TS 25.423 [37] and 3GPP TS 25.419 [38] define the use of this identifier in RNSAP and SABP signalling.

A cell may belong to one or two Service Areas. If it belongs to two Service Areas, one is applicable in the Broadcast(BC) domain and the other is applicable in both the CS and PS domains.

The Broadcast (BC) domain requires that its Service Areas each consist of only one cell. This does not limit the use of

Service Areas for other domains. Refer to 3GPP TS 25.410 [39] for a definition of the BC domain.

12.6 Shared Network Area Identifier

The Shared Network Area Identifier (SNA-Id) is used to identify an area consisting of one or more Location Areas.

Such an area is called a Shared Network Area and can be used to grant access rights to parts of a Shared Network to a

UE in connected mode (see 3GPP TS 25.401 [39]).

The Shared Network Area Identifier consists of the PLMN-Id followed by the Shared Network Area Code (SNAC).

- SNA-Id = PLMN-Id || SNAC

The SNAC is defined by the operator.


13 Numbering, addressing and identification within the

IP multimedia core network subsystem13.1 Introduction

This clause describes the format of the parameters needed to access the IP multimedia core network subsystem. For

further information on the use of the parameters see 3GPP TS 23.228 [24] and 3GPP TS 29.163 [63]. For more

information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document. For

more information on the ".invalid" top level domain see IETF RFC 2606 [64].

13.2 Home network domain name

The home network domain name shall be in the form of an Internet domain name, e.g. operator.com, as specified inIETF RFC 1035 [19].

If there is no ISIM application, the UE shall derive the home network domain name from the IMSI as described in the

following steps:

1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27]) and

separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning;

2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" domain

name;

3. add the label "ims." to the beginning of the domain.

An example of a home network domain name is:

IMSI in use: 234150999999999;

3GPP


32/53

3GPP TS 23.003 V7.3.0 (2007-03)32Release 7T

Where:

MCC = 234;

MNC = 15;

MSIN = 0999999999,

Which gives the home network domain name: ims.mnc015.mcc234.3gppnetwork.org

13.3 Private user identity

The private user identity shall take the form of an NAI, and shall have the form username@realm as specified in clause

2.1 of IETF RFC 4282 [53].

NOTE: It is possible for a representation of the IMSI to be contained within the NAI for the private identity.

If there is no ISIM application, the private user identity is not known. If the private user identity is not known, the

private user identity shall be derived from the IMSI.

The following steps show how to build the private user identity out of the IMSI:

1. use the whole string of digits as the username part of the private user identity;

2. convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in subclause 13.2.

The result will be a private user identity of the form "@ims.mnc.mcc.3gppnetwork.org". For

example: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the private user identity then takes the form

[email protected]

13.4 Public User Identity

The Public User Identity shall take the form of either a SIP URI (see IETF RFC 3261 [26]) or a tel URL (see IETF RFC3966 [45]). A SIP URI for a Public User Identity shall take the form "sip:user@domain". SIP URI comparisions shall be

performed as defined in IETF RFC 3261 [26], section 19.1.4.

If there is no ISIM application to host the public user identity, a temporary public user identity shall be derived, basedon the IMSI. The temporary public user identity shall be of the form "user@domain" and shall therefore be equal to the

private user identity. The private user identity is derived as described in subclause 13.2. That is, the private user identity

will be appended to the string "sip:"

EXAMPLE: "sip:[email protected]".

13.5 Public service identity (PSI)

The public service identity shall take the form of either a SIP URI (see IETF RFC 3261 [26]) or a Tel URI (see IETFRFC 3966 [45]). A public service identity identifies a service, or a specific resource created for a service on an

application server. The domain part is pre-defined by the IMS operators and the IMS system provides the flexibility to

dynamically create the user part of the PSIs.

The PSIs are stored in the HSS either as a distinct PSI or as a wildcarded PSI. A distinct PSI contains the PSI that is

used in routing , whilst a wildcarded PSI represents a collection of PSIs. Wildcarded PSIs enable optimisation of the

operation and maintenance of the nodes. A wildcarded PSI consists of a delimited regular expression located either in

the userinfo portion of the SIP URI or in the telephone-subscriber portion of the Tel URI. The regular expression in the

wildcarded PSI shall take the form of Extended Regular Expressions (ERE) as defined in chapter 9 in IEEE 1003.1-

2004 Part 1 [60]. The delimiter shall be the exclamation mark character ("!").

When stored in the HSS, the wildcarded PSI shall include the delimiter character to indicate the extent of the part of the

PSI that is wildcarded. It is used to separate the regular expression from the fixed part of the wildcarded PSI.

Example: The following PSI could be stored in the HSS - "sip:chatlist!.*[email protected]".

3GPP


33/53

3GPP TS 23.003 V7.3.0 (2007-03)33Release 7T

When used on an interface, the PSI may include the delimiter character. The inclusion of the delimiter character

within the PSI may allow the HSS to perform the matching of the PSI with the wildcarded PSIs stored in the HSS morerapidly and hence process messages faster (this potential optimisation is dependent upon HSS implementation).

However, if the delimiter character is not included in the PSI in the interface message, the matching of the PSI to the

PSIs stored in the HSS shall still be completed.

Example: The following PSIs communicated in interface messages to the HSS will match to the wildcarded PSI of

"sip:chatlist!.*[email protected]" stored in the HSS:

sip:[email protected]





13.5A Private Service IdentityThe Private Service Identity is applicable to a PSI user and is similar to a Private User Identity in the form of a Network

Access Identifier (NAI), which is defined in IETF RFC 4282 [53]. The Private Service Identity is operator defined and

although not operationally used for registration, authorisation and authentication in the same way as Private User

Identity, it enables Public Service Identities to be associated to a Private Service Identity which is required for

compatibility with the Cx procedures.

13.6 Anonymous User Identity

The Anonymous User Identity shall take the form of a SIP URI (see IETF RFC 3261 [26]). A SIP URI for anAnonymous User Identity shall take the form "sip:user@domain". The user part shall be the string "anonymous" and the

domain part shall be the string "anonymous.invalid". The full SIP URI for Anonymous User Identity is thus:

"sip:[email protected]"

For more information on the Anonymous User Identity and when it is used, see 3GPP TS 29.163 [63].

13.7 Unavailable User Identity

The Unavailable User Identity shall take the form of a SIP URI (see IETF RFC 3261 [26]). A SIP URI for an

Unavailable User Identity shall take the form "sip:user@domain". The user part shall be the string "unavailable" and the

domain part shall be the string "unknown.invalid". The full SIP URI for Anonymous User Identity is thus:

"sip:[email protected]"

For

Apn Mobile

Documents

Transcript of Apn Mobile