3GPP TS 23.003 V12.6.0: GSM与UMTS系统技术规范

需积分: 9 174 浏览量更新于2024-07-21 收藏 518KB PDF 举报

本资源是3GPP（Third Generation Partnership Project）组织发布的标准文档，编号为ETSITS123003V12.6.0（2015年3月），全称为《数字蜂窝移动通信系统（Phase 2+）：通用移动通信系统（UMTS）》。3GPP是一个全球性的标准化机构，致力于制定和维护移动通信技术的规范，如2G、3G和4G网络标准。在3GPP TS 23.003 V12.6.0 Release 12这一版本中，主要关注的是编号、地址分配和标识（Numbering, Addressing, and Identification，NAI）的相关技术。这个技术规格详细规定了GSM (Global System for Mobile Communications) 和 UMTS (Universal Mobile Telecommunications System) 网络中用户设备（UE）的身份标识以及数据传输过程中的路由和寻址机制。它确保了移动通信系统的互联互通性和标准化，对于网络运营商、设备制造商和系统集成商来说，这是构建和维护高效、安全网络架构的基础。该文档可能包含了一些具体技术细节，例如路由算法（如Lucioles路由），这可能是针对网络数据包在不同网络节点间如何高效传输的一种设计。此外，还提到了ETSI（European Telecommunications Standards Institute，欧洲电信标准研究所）的联系信息，这是发布和管理这些标准的机构，任何对文档内容进行修改或复制都必须得到ETSI的书面授权。最后，值得注意的是，这份文档可以通过3GPP的官方网站下载，且纸质版和电子版可能存在差异，官方发布的纸质版为准。这对于开发者和专业人员查阅最新和权威的3GPP标准至关重要，以确保其在实际项目中的应用符合国际标准要求。

ETSI

ETSI TS 123 003 V12.6.0 (2015

03)

3GPP TS 23.003 version 12.6.0 Release 12

- 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 General

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

GSM/UMTS/EPS 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, SGSNs and MME may allocate Temporary

Mobile Subscriber Identities (TMSI) to visiting mobile subscribers. The VLR,SGSN and MME must be capable of

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

An MS may be allocated three TMSIs, one for services provided through the MSC, one for services provided through

the SGSN (P-TMSI for short) and one for the services provided via the MME (M-TMSI part GUTI for short).

For addressing on resources used for GPRS, a Temporary Logical Link Identity (TLLI) is used. The TLLI to use is built

by 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.

MCC

Not more than 15 digits

3 digits

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 MNC

identifies 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.

ETSI

ETSI TS 123 003 V12.6.0 (2015

03)

3GPP TS 23.003 version 12.6.0 Release 12

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, or within an MME and the area controlled by an MME), 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 needed

between 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.

If intra domain connection of RAN nodes to multiple CN nodes as described in 3GPP TS 23.236 [23] is applied in the

MSC/VLR or SGSN, then the NRI shall be part of the TMSI. The NRI has a configurable length of 0 to 10 bits. A

configurable length of 0 bits indicates that the NRI is not used and this feature is not applied in the MSC/VLR or SGSN.

The NRI shall be coded in bits 23 to 14. An NRI shorter than 10 bits shall be encoded with the most significant bit of

the NRI field in bit 23.

The TMSI shall be allocated only in ciphered form. See also 3GPP TS 43.020 [7] and 3GPP TS 33.102 [42].

The network shall not allocate a TMSI with all 32 bits equal to 1 (this is because the TMSI must be stored in the SIM,

and the SIM uses 4 octets with all bits equal to 1 to indicate that no valid TMSI is available).

To allow for eventual modifications of the management of the TMSI code space management, MSs shall not check if an

allocated TMSI belongs to the range allocated to the allocating node. MSs shall use an allocated TMSI according to the

specifications, whatever its value.

2.5 Structure of LMSI

The LMSI consists of 4 octets and may be allocated by the VLR. The VLR shall not allocate the value zero. The value

zero is reserved to indicate that an LMSI parameter sent from the HLR to the VLR shall not be interpreted.

2.6 Structure of TLLI

A TLLI is built by the MS or by the SGSN either on the basis of the P-TMSI (local or foreign TLLI), or directly

(random or auxiliary TLLI), according to the following rules.

ETSI

ETSI TS 123 003 V12.6.0 (2015

03)

3GPP TS 23.003 version 12.6.0 Release 12

The TLLI consists of 32 bits, numbered from 0 to 31 by order of significance, with bit 0 being the LSB.

A local TLLI is built by an MS which has a valid P-TMSI as follows:

bits 31 down to 30 are set to 1; and

bits 29 down to 0 are set equal to bits 29 to 0 of the P-TMSI.

A foreign TLLI is built by an MS which has a valid P-TMSI as follows:

bit 31 is set to 1 and bit 30 is set to 0; and

bits 29 down to 0 are set equal to bits 29 to 0 of the P-TMSI.

A random TLLI is built by an MS as follows:

bit 31 is set to 0;

bits 30 down to 27 are set to 1; and

bits 0 to 26 are chosen randomly.

An auxiliary TLLI is built by the SGSN as follows:

bit 31 is set to 0;

bits 30 down to 28 are set to 1;

bit 27 is set to 0; and

bits 0 to 26 can be assigned independently.

Other types of TLLI may be introduced in the future.

Part of the TLLI codespace is re-used in GERAN to allow for the inclusion of the GERAN Radio Network Temporary

Identifier in RLC/MAC messages. The G-RNTI is defined in 3GPP TS 44.118 [29].

The structure of the TLLI is summarised in table 1.

Table 1: TLLI structure

26 to 0

Type of TLLI

1 1 T T T T Local TLLI

1 0 T T T T Foreign TLLI

0 1 1 1 1 R Random TLLI

0 1 1 1 0 A Auxiliary TLLI

0 1 1 0 X X Reserved

0 1 0 X X X Reserved

0 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.

ETSI

ETSI TS 123 003 V12.6.0 (2015

03)

3GPP

TS 23.003 version 12.6.0 Release 12

2.8 Globally Unique Temporary UE Identity (GUTI)

2.8.1 Introduction

The purpose of the GUTI is to provide an unambiguous identification of the UE that does not reveal the UE or the user's

permanent identity in the Evolved Packet System (EPS). It also allows the identification of the MME and network. It

can be used by the network and the UE to establish the UE's identity during signalling between them in the EPS. See

3GPP TS 23.401 [72].

The GUTI has two main components:

- one that uniquely identifies the MME which allocated the GUTI; and

- one that uniquely identifies the UE within the MME that allocated the GUTI.

Within the MME, the mobile shall be identified by the M-TMSI.

The Globally Unique MME Identifier (GUMMEI) shall be constructed from the MCC, MNC and MME Identifier

(MMEI).

The MMEI shall be constructed from an MME Group ID (MMEGI) and an MME Code (MMEC).

The GUTI shall be constructed from the GUMMEI and the M-TMSI.

For paging purposes, the mobile is paged with the S-TMSI. The S-TMSI shall be constructed from the MMEC and the

M-TMSI.

The operator shall need to ensure that the MMEC is unique within the MME pool area and, if overlapping pool areas

are in use, unique within the area of overlapping MME pools.

NOTE: In some network sharing cases it is required that the MMEC and NRI values are coordinated between the

sharing operators, as described in 3GPP TS 23.251 [101]. In order to achieve CS/PS coordination in

shared GERAN/UTRAN networks, the MMEC included in the GUTI can be set to identify the CS

operator serving the UE.

The GUTI shall be used to support subscriber identity confidentiality, and, in the shortened S-TMSI form, to enable

more efficient radio signalling procedures (e.g. paging and Service Request).

The format and size of the GUTI is therefore the following:

<GUTI> = <GUMMEI><M-TMSI>,

where <GUMMEI> = <MCC><MNC><MME Identifier>

and <MME Identifier> = <MME Group ID><MME Code>

MCC and MNC shall have the same field size as in earlier 3GPP systems.

M-TMSI shall be of 32 bits length.

MME Group ID shall be of 16 bits length.

MME Code shall be of 8 bits length.

2.8.2 Mapping between Temporary and Area Identities for the EUTRAN

and the UTRAN/GERAN based systems

2.8.2.0 Introduction

This section provides information on the mapping of the temporary and location area identities, e.g. for the construction

of the Routeing Area Update Request message in GERAN/UTRAN or Tracking Area Update Request message in

E-UTRAN.

ETSI

ETSI TS 123 003 V12.6.0 (2015

03)

3GPP TS 23.003 version 12.6.0 Release 12

In GERAN and UTRAN:

<P-TMSI/TLLI> includes the mapped NRI

P-TMSI shall be of 32 bits length where the two topmost bits are reserved and always set to '11'. Hence, for a UE which

may handover to GERAN/UTRAN (based on subscription and UE capabilities), the corresponding bits in the M-TMSI

are set to '11' (see subclause 2.8.2.1.3).

3GPP TS 23.236 [23] specifies that the NRI field is of variable length and shall be mapped into the P-TMSI starting at

bit 23 and down to bit 14. The most significant bit of the NRI is located at bit 23 of the P-TMSI regardless of the

configured length of the NRI. To support mobility between GERAN/UTRAN and E-UTRAN, the NRI length is limited

to a maximum of 8 bits to be compatible for the mapping to MME Code within GUTI (see subclause 2.8.2.2).

The P-TMSI and NRI are defined elsewhere in this specification.

In the case of a combined MME-SGSN node, the NRI of the SGSN part and the MME code of the MME part, refer to

the same combined node. RAN configuration allows NAS messages on GERAN/UTRAN and E-UTRAN to be routed

to the same combined node. The same or different values of NRI and MME code may be used for a combined node.

2.8.2.1 Mapping from GUTI to RAI, P-TMSI and P-TMSI signature

2.8.2.1.1 Introduction

This subclause addresses the case when a UE moves from an MME to an SGSN. The SGSN may be either an S4 SGSN

or a Gn/Gp SGSN.

2.8.2.1.2 Mapping in the UE

When a UE moves from an E-UTRAN to a GERAN/UTRAN, the UE needs to map the GUTI to an RAI, a P-TMSI and

a P-TMSI Signature, for them to be sent to the SGSN. For GERAN, the TLLI is derived from the P-TMSI by the UE

and is a foreign TLLI (see subclause 2.6).

The mapping of the GUTI shall be done to the combination of RAI of GERAN / UTRAN and the P-TMSI:

E-UTRAN <MCC> maps to GERAN/UTRAN <MCC>

E-UTRAN <MNC> maps to GERAN/UTRAN <MNC>

E-UTRAN <MME Group ID> maps to GERAN/UTRAN <LAC>

E-UTRAN <MME Code> maps to GERAN/UTRAN <RAC> and is also copied into the 8 Most Significant Bits of

the NRI field within the P-TMSI;

E-UTRAN <M-TMSI> maps as follows:

- 6 bits of the E-UTRAN <M-TMSI> starting at bit 29 and down to bit 24 are mapped into bit 29 and down to

bit 24 of the GERAN/UTRAN <P-TMSI>;

- 16 bits of the E-UTRAN <M-TMSI> starting at bit 15 and down to bit 0 are mapped into bit 15 and down to

bit 0 of the GERAN/UTRAN <P-TMSI>;

- and the remaining 8 bits of the E-UTRAN <M-TMSI> are mapped into the 8 Most Significant Bits of the <P-

TMSI signature> field.

The UE shall fill the remaining 2 octets of the <P-TMSI signature> according to subclauses 9.1.1, 9.4.1, 10.2.1,

or 10.5.1 of 3GPP TS.33.401 [89] , as appropriate, for RAU/Attach procedures.

For UTRAN, the 10-bit long NRI bits are masked out from the P-TMSI and are also supplied by the UE to the RAN

node as IDNNS (Intra Domain NAS Node Selector) (see 3GPP TS 23.236 [23]). However, the RAN configured NRI

length should not exceed 8 bits.

剩余91页未读，继续阅读

baidu_29881501

粉丝: 0
资源: 1

3GPP TS 23.003 V12.6.0: GSM与UMTS系统技术规范

3GPP_GSM_TS0710_ts_101369v070200p.pdf

ts_13814101v150000p (1)_3gpp5g_TS38.141_5GNR_3GPP_TS_3GPPTS38_

3GPP ts_126267v160000p.pdf

Specs_GSM_3GPP_

ts_102_613v090200p_swp协议

ts_136331v130000p_lterrc_

ts_129060v110700p

ts_100557v042400p

最新资源