3GPP LTE Diameter协议最新规范分享

需积分: 10 31 浏览量更新于2024-07-17 收藏 1.82MB PDF 举报

3GPP TS 29.272 V9.4.0（2010年9月发布）是一个关于3GPP演进分组系统(Evolved Packet System, EPS)的关键技术规范，特别关注移动管理实体(Mobility Management Entity, MME)和 Serving GPRS Support Node (SGSN)相关的接口设计，这些接口是基于 Diameter 协议的。Diameter 协议是 LTE 和 4G 网络中的重要通信协议，它主要用于承载会话控制和认证功能，对于网络服务提供商间的信令交互、用户身份管理以及计费服务至关重要。该文档由3GPP（3rd Generation Partnership Project）制定，旨在为下一代无线通信系统的开发提供标准化框架。然而，值得注意的是，这份文档并未经过3GPP组织伙伴的正式批准，仅作为内部研究和发展之用，不推荐直接实施。如果要实现3GPP系统的具体实施规格，应通过3GPP组织伙伴的出版机构获取官方发布的标准和报告。 3GPP TS 29.272 V9.4.0的关键词包括3GPP、LTE和Diameter，反映了它在这些领域的核心作用。版本号为9.4.0，表明这是3GPP Release 9（即LTE Release 9）的一部分，这意味着它是针对早期4G网络技术的一个重要参考文档。 3GPP总部位于法国瓦尔博纳的Sophia Antipolis，设有支持办公室，联系方式包括电话和传真，同时提供了互联网访问地址，以便于获取最新的技术信息和支持。这个文档对理解LTE网络架构，尤其是MME和SGSN的功能划分，以及它们如何通过Diameter协议进行高效通信具有重要意义。此外，对于从事4G网络设计、优化和维护的专业人士，掌握这份规范有助于确保网络的兼容性和性能优化。随着技术的发展，更新的Diameter协议版本可能会包含更多的改进和增强功能，因此，建议查找更近期的资源以获取最新信息。

3GPP

3GPP TS 29.272 V9.4.0 (2010-09)

Release 9

When the HSS receives the Update Location Request, if a 15

digit of the IMEI AVP is received, the HSS may discard

the digit.

If the Update Location Request includes the list of active APNs, the HSS shall delete all the stored dynamic PDN GW

information, if there are any, and then replace them by the PDN GW information received in the list of Active-APN

AVPs.

If the Update Location Request is received over the S6a interface for a user for which the URRP-MME parameter is set

in the HSS, the HSS shall clear the URRP-MME parameter and send an indication to the corresponding Service Related

Entities.

If the Update Location Request is received over the S6d interface for a user for which the URRP-SGSN parameter is set

in the HSS, the HSS shall clear the URRP-SGSN parameter and send an indication to the corresponding Service Related

Entities.

If no result code has been sent to the MME or SGSN so far, the HSS shall include the subscription data in the ULA

command according to the ULR-Flags and the supported/unsupported features of the MME or SGSN, unless an explicit

"skip subscriber data" indication has been received in the request, and shall return a Result Code of

DIAMETER_SUCCESS.

When the APN-Configuration-Profile AVP is present in the Subscription-Data AVP sent within a ULA, the AVP shall

contain at least the default APN Configuration and a Context-Identifier AVP that identifies the per subscriber’s default

APN configuration.

The GPRS Subscription data (if available in the HSS) shall only be present in the ULA command if it was indicated by

the serving node in the ULR-Flags AVP (see clause 7.3.7), or when the subscription data is returned by a Pre-Rel-8

HSS (via an IWF) or when the Update Location Request is received over the S6d interface and there is no EPS

subscription data stored for the subscriber.

The HSS shall use the indication received in the GPRS-Subscription-Data-Indicator for future use in the subscriber data

update procedures.

LCS-Info, Teleservice-List and Call-Barring-Infor-List data shall be included according to the list of supported features

indicated by the serving node (see clause 7.3.10). The check of the SMS supported features, which are only applicable

to SGSN, may be skipped if the HSS determines that the serving node is a standalone MME (see clause 7.3.7).

The HSS may use the indication received in the Node-Type-Indicator for future use in the subscriber data update

procedures.

Subscriber-Status AVP shall be present in the Subscription-Data AVP when sent within a ULA. If the value

"OPERATOR_DETERMINED_BARRING" is sent, the Operator-Determined-Barring AVP or HPLMN-ODB AVP

shall also be present in the Subscription-Data AVP, or vice versa.

Access-Restriction-Data AVP shall be present within the Subscription-Data AVP sent within a ULA if at least one of

the defined restrictions applies.

The AMBR AVP shall be present in the Subscription-Data AVP when the Subscription-Data AVP is sent within a ULA.

The EPS-Subscribed-QoS-Profile AVP and the AMBR AVP shall be present in the APN-Configuration AVP when the

APN-Configuration AVP is sent in the APN-Configuration-Profile AVP and when the APN-Configuration-Profile AVP

is sent within a ULA (as part of the Subscription-Data AVP).

For those APNs that have been authorized as a consequence of having the Wildcard APN in the user subscription, the

HSS shall include the specific APN name and associated PDN-GW identity inside the APN context of the Wildcard

APN. This indicates to the MME that the particular APN shall not be cached in the MME and it shall be deleted when

the UE session is terminated.

If a Result Code of DIAMETER_SUCCESS is returned, the HSS shall set the Separation Indication in the response.

If the HSS receives an indication in the ULR command about the homogeneous support of IMS Voice over PS Sessions

in all TA/RAs associated to a serving node, it may use this information in the future in order to skip the T-ADS data

retrieval, as described in clause 5.2.2.1 (IDR/IDA commands).

3GPP

3GPP TS 29.272 V9.4.0 (2010-09)

Release 9

5.2.1.2 Cancel Location

5.2.1.2.1 General

The Cancel Location Procedure shall be used between the HSS and the MME and between the HSS and the SGSN to

delete a subscriber record from the MME or SGSN. The procedure shall be invoked by the HSS and is used:

- to inform the MME or SGSN about the subscriber’s subscription withdrawal or

- to inform the MME or SGSN about an ongoing update procedure i.e. MME or SGSN change.

- to inform the MME or SGSN about an initial attach procedure.

This procedure is mapped to the commands Cancel-Location-Request/Answer (CLR/CLA) in the Diameter application

specified in chapter 7.

Table 5.2.1.2.1/1 specifies the involved information elements for the request.

Table 5.2.1.2.1/2 specifies the involved information elements for the answer.

Table 5.2.1.2.1/1: Cancel Location Request

Information

element name

Mapping to

Diameter AVP

Cat.

Description

IMSI

User-Name

(See IETF

RFC 3588 [4])

This information element shall contain the user IMSI, formatted according

to 3GPP TS 23.003 [3], clause 2.2.

Supported

Features

(See 3GPP TS

29.229 [9])

Supported-

Features

If present, this information element shall contain the list of features

supported by the origin host.

Cancellation

Type

(See 7.3.24)

Cancellation-

Type

Defined values that can be used are:

- MME-Update Procedure,

- SGSN-Update Procedure,

- Subscription Withdrawal,

- Update Procedure_IWF,

- Initial Attach Procedure.

Table 5.2.1.2.1/2: Cancel Location Answer

Information

element name

Mapping to

Diameter AVP

Cat.

Description

Supported

Features

(See 3GPP TS

29.229 [9])

Supported-

Features

If present, this information element shall contain the list of features

supported by the origin host.

Result

(See 7.4)

Result-Code /

Experimental-

Result

The result of the operation.

The Result-Code AVP shall be used to indicate success / errors as defined

in the Diameter Base Protocol.

5.2.1.2.2 Detailed behaviour of the MME and the SGSN

When receiving a Cancel Location request the MME or SGSN shall check whether the IMSI is known.

If it is not known, a result code of DIAMETER_SUCCESS is returned.

If it is known, the MME or SGSN shall check the Cancellation Type and act accordingly. If a cancellation type of

"Initial Attach Procedure" is received, the MME or SGSN shall not delete the subscription data. For details see 3GPP

TS 23.401[2] and 3GPP TS 23.060[12]. Also in this case a result code of DIAMETER_SUCCESS is returned.

When a UE is served by a single combined MME/SGSN for both E-UTRAN and non-E-UTRAN access, the combined

MME/SGSN shall check the Cancellation-Type. If it indicates Subscription Withdrawal or Update Procedure_IWF, the

3GPP

3GPP TS 29.272 V9.4.0 (2010-09)

Release 9

CLR is processed both in the MME part and in the SGSN part of the combined node. Otherwise, the CLR is processed

only in the affected part of the combined node and subscription data are kept for the not affected part.

5.2.1.2.3 Detailed behaviour of the HSS

The HSS shall make use of this procedure when the subscriber’s subscription is withdrawn by the HSS operator and

when the HSS detects that the UE has moved to a new MME or SGSN area.

The HSS shall include a cancellation type of "Subscription Withdrawal" if the subscriber’s subscription is withdrawn by

the operator and shall include a cancellation type of "MME Update Procedure" if the UE moved to a new MME area

and shall include a cancellation type of "SGSN Update Procedure" if the UE moved to a new SGSN area, and shall

include a cancellation type of "Initial Attach Procedure" if the cancel location is initiated due to an Initial Attach from

the UE.

5.2.1.3 Purge UE

5.2.1.3.1 General

The Purge UE Procedure shall be used between the MME and the HSS and between the SGSN and the HSS to indicate

that the subscriber’s profile has been deleted from the MME or SGSN either by an MMI interaction or automatically,

e.g. because the UE has been inactive for several days.

This procedure is mapped to the commands Purge-UE-Request/Answer (PUR/PUA) in the Diameter application

specified in chapter 7.

Table 5.2.1.3.1/1 specifies the involved information elements for the request.

Table 5.2.1.3.1/2 specifies the involved information elements for the answer.

Table 5.2.1.3.1/1: Purge UE Request

Information

element name

Mapping to

Diameter AVP

Cat.

Description

IMSI

User-Name

(See IETF

RFC 3588 [4])

This information element shall contain user IMSI, formatted according to

3GPP TS 23.003 [3], clause 2.2.

Supported

Features

(See 3GPP TS

29.229 [9])

Supported-

Features

If present, this information element shall contain the list of features

supported by the origin host.

Table 5.2.1.3.1/2: Purge UE Answer

Information

element name

Mapping to

Diameter AVP

Cat.

Description

Supported

Features

(See 3GPP TS

29.229 [9])

Supported-

Features

If present, this information element shall contain the list of features

supported by the origin host.

Result

(See 7.4)

Result-Code /

Experimental-

Result

This IE shall contain the result of the operation.

The Result-Code AVP shall be used to indication success / errors as

defined in the Diameter Base Protocol.

The Experimental-Result AVP shall be used for S6a/S6d errors. This is a

grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id

AVP, and the error code in the Experimental-Result-Code AVP.

The following errors are applicable:

- User Unknown

PUA-Flags

(See 7.3.48)

PUA-Flags

This Information Element shall contain a bit mask. See section 7.3.48 for

the meaning of the bits. It shall be present only when the Result-Code AVP

is DIAMETER_SUCCESS.

3GPP

3GPP TS 29.272 V9.4.0 (2010-09)

Release 9

5.2.1.3.2 Detailed behaviour of the MME and the SGSN

The MME shall make use of this procedure to set the "UE Purged in the MME" flag in the HSS when the subscription

profile is deleted from the MME database due to MMI interaction or after long UE inactivity.

The SGSN shall make use of this procedure to set the "UE Purged in SGSN" flag in the HSS when the subscription

profile is deleted from the SGSN database due to MMI interaction or after long UE inactivity.

The combined MME/SGSN shall make use of this procedure to set the "UE Purged in MME" and "UE Purged in

SGSN" flags in the HSS when the subscription profile is deleted from the common MME/SGSN database due to MMI

interaction or after long UE inactivity on all registered accesses.

When receiving a Purge UE response from the HSS the MME shall check the Result Code. If it indicates success, the

MME shall check the PUA flag "freeze M-TMSI", and if set freeze the M-TMSI i.e. block it for immediate re-use.

When receiving a Purge UE response from the HSS the SGSN shall check the Result Code. If it indicates success, the

SGSN shall check the PUA flag "freeze P-TMSI", and if set freeze the P-TMSI i.e. block it for immediate re-use.

When receiving a Purge UE response from the HSS the combined MME/SGSN shall check the Result Code. If it

indicates success, the combined MME/SGSN shall check the PUA flag "freeze M-TMSI" and "freeze P-TMSI", and if

set freeze the M-TMSI and/or the P-TMSI i.e. block it for immediate re-use.

5.2.1.3.3 Detailed behaviour of HSS

When receiving a Purge UE request the HSS shall check whether the IMSI is known.

If it is not known, a result code of DIAMETER_ERROR_USER_UNKNOWN shall be returned.

If it is known, the HSS shall set the result code to DIAMETER_SUCCESS and compare the received identity in the

Origin-Host with the stored MME-Identity and with the stored SGSN-Identity.

If the received identity matches the stored MME-identity and the stored SGSN-Identity, the HSS shall set the PUA flags

"freeze M-TMSI" and "freeze P-TMSI" in the answer message and set the flag "UE purged in MME" and set the flag

"UE purged in SGSN";

If the received identity matches the stored MME-identity but not the stored SGSN-identity, the HSS shall set the PUA

flag "freeze M-TMSI" and clear the PUA flag "freeze P-TMSI" in the answer message and set the flag "UE purged in

MME";

If the received identity matches the stored SGSN-identity but not the stored MME-identity, the HSS shall set the PUA

flag "freeze P-TMSI" and clear the PUA flag "freeze M-TMSI" in the answer message and set the flag "UE purged in

SGSN";

If the received identity does not match the stored MME-identity and does not match the stored SGSN-identity, the HSS

shall clear the PUA flags "freeze M-TMSI" and "freeze P-TMSI in the answer message.

5.2.2 Subscriber Data Handling Procedures

5.2.2.1 Insert Subscriber Data

5.2.2.1.1 General

The Insert Subscriber Data Procedure shall be used between the HSS and the MME and between the HSS and the

SGSN for updating certain user data in the MME or SGSN in the following situations:

- due to administrative changes of the user data in the HSS and the user is now located in an MME or SGSN, i.e. if

the user was given a subscription and the subscription has changed;

- the operator has applied, changed or removed Operator Determined Barring for this user;

- activate subscriber tracing in the MME or the SGSN;

- to indicate to the MME or SGSN that the HSS has requested to be notified when the UE has become reachable;

- to request from the MME or SGSN the necessary data to support the T-ADS functionality;

- to retrieve location information and/or state information from the MME or the SGSN.

剩余87页未读，继续阅读

这个书生有点意思

粉丝: 39
资源: 114

3GPP LTE Diameter协议最新规范分享

Diameter协议：新一代AAA架构的全能解决方案

"Jquery_render.pdf"：jqplot 渲染器简介和属性解释

3GPPTS 29.272 V15.8.0: 4G LTE MME-HSS Diameter协议中英文对照

信息安全_数据安全_4G_to_5G_Evolution：In-Depth_Security_Perspective.pdf

29272-930_NAS.doc

kamailio-4.4.2_src.tar.gz

中国电信Diameter协议---Cx和Dx接口规范要求.pdf

MIL-STD-133B_NOTICE-1.016132.PDF

erlang-diameter-19.3.6.4-1.el7.x86_64.rpm

最新资源