1、 ETSI TS 1Universal Mobile TelDiameter-based T4 Intedata netw(3GPP TS 29.3TECHNICAL SPECIFICATION129 337 V13.2.0 (2017elecommunications System (LTE; terface for communications wet orks and applications .337 version 13.2.0 Release 1317-01) (UMTS); with packet 13) ETSI ETSI TS 129 337 V13.2.0 (2017-01
2、)13GPP TS 29.337 version 13.2.0 Release 13Reference RTS/TSGC-0429337vd20 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfectur
3、e de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be mod
4、ified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
5、Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please s
6、end your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permissi
7、on of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the E
8、TSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 337
9、 V13.2.0 (2017-01)23GPP TS 29.337 version 13.2.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members,
10、and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to t
11、he ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Fo
12、reword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the c
13、orresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “
14、cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 129 337 V13.2.0 (2017-01)33GPP TS 29.337 version 13.2.0 Re
15、lease 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and Abbreviations 7g33.1 Abbreviations . 7g34 General Description 7g35 MTC-IWF SMS-SC (T4) 7g35.1 Introduction 7g35.2 Procedure Descriptions . 7g35.2.1 Dev
16、ice Trigger Procedure . 7g35.2.1.1 General 7g35.2.1.2 Detailed Behaviour of the MTC-IWF . 10g35.2.1.3 Detailed Behaviour of the SMS-SC 10g35.2.2 Delivery Report of Device Trigger . 11g35.2.2.1 General 11g35.2.2.2 Detailed Behaviour of the SMS-SC 12g35.2.2.3 Detailed Behaviour of the MTC-IWF . 13g36
17、Protocol Specification and Implementation . 13g36.1 General . 13g36.1.1 Use of Diameter Base Protocol . 13g36.1.2 Securing Diameter Messages 13g36.1.3 Accounting Functionality . 13g36.1.4 Use of Sessions . 13g36.1.5 Transport Protocol 13g36.1.6 Routing Considerations . 13g36.1.7 Advertising Applicat
18、ion Support 14g36.1.8 Diameter Application Identifier 14g36.1.9 Use of the Supported-Features AVP . 14g36.2 Commands 15g36.2.1 Introduction. 15g36.2.2 Command-Code Values 15g36.2.3 Device-Trigger-Request (DTR) Command 15g36.2.4 Device-Trigger-Answer (DTA) Command . 16g36.2.5 Delivery-Report-Request
19、(DRR) Command . 16g36.2.6 Delivery-Report-Answer (DRA) Command . 16g36.3 AVPs 17g36.3.1 SM-Delivery-Outcome-T4 18g36.3.2 Absent-Subscriber-Diagnostic-T4 19g36.3.3 Serving-Node 19g36.3.4 Additional-Serving-Node 20g36.3.5 Supported-Feature-List AVP for the T4 application . 20g36.3.6 Trigger-Action 21g
20、36.3.7 MTC-Error-Diagnostic . 21g36.3.8 DRMP . 21g37 Result-Code and Experimental-Result Values . 22g37.1 General . 22g37.2 Success . 22g37.3 Permanent Failures . 22g3ETSI ETSI TS 129 337 V13.2.0 (2017-01)43GPP TS 29.337 version 13.2.0 Release 137.3.1 DIAMETER_ERROR_USER_UNKNOWN (5001) 22g37.3.2 DIA
21、METER_ERROR_INVALID_SME_ADDRESS (5530) 22g37.3.3 DIAMETER_ERROR_SC_CONGESTION (5531) . 22g37.3.4 Void 22g37.3.5 DIAMETER_ERROR_TRIGGER_REPLACE_FAILURE (5533) . 22g37.3.6 DIAMETER_ERROR_TRIGGER_RECALL_FAILURE (5534) 22g37.3.7 DIAMETER_ERROR_ORIGINAL_MESSAGE_NOT_PENDING (5535) 22g3Annex A (normative):
22、 Diameter message priority mechanism 23g3A.1 General . 23g3A.2 T4 interface 23g3A.2.1 General 23g3A.2.2 SMS-SC and MTC-IWF behaviour 23g3Annex B (informative): Change history . 24g3History 25g3ETSI ETSI TS 129 337 V13.2.0 (2017-01)53GPP TS 29.337 version 13.2.0 Release 13Foreword This Technical Spec
23、ification has been produced by the 3rdGeneration Partnership Project (3GPP). 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
24、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 f
25、or 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. ETSI ETSI TS 129 337 V13.2.0 (2017-01)63GPP TS 29.337 version 13.2.0 Release 131 Scope The present document descri
26、bes the Diameter based interface between the Machine Type Communications-InterWorking Function (MTC-IWF) and the Short Message Service-Service Centre (SMS-SC) for communications with packet data networks and applications. This specification defines the Diameter application for the T4 reference point
27、 between the MTC-IWF and the SMS-SC. The interactions between the MTC-IWF and the SMS-SC are specified. The stage 2 description for communications with packet data networks and applications (architecture and functionality) is specified in the 3GPP TS 23.682 2. 2 References The following documents co
28、ntain 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.) or non-specific. - For a specific reference, subsequent revisions do not apply. - For a no
29、n-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 TR 21.905: “Vocabulary for 3GPP Specificat
30、ions“. 2 3GPP TS 23.682: “Architecture enhancements to facilitate communications with packet data networks and applications“. 3 IETF RFC 3588: “Diameter Base Protocol“. 4 3GPP TS 33.210: “3G Security; Network Domain Security; IP Network Layer Security“. 5 IETF RFC 4960: “Stream Control Transmission
31、Protocol“. 6 3GPP TS 29.229: “Cx and Dx interfaces based on the Diameter protocol“. 7 3GPP TS 29.228: “IP multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and Message Elements“. 8 3GPP TS 23.003: “Numbering, addressing and identification“. 9 3GPP TS 23.040: “Technical realization of
32、the Short Message Service (SMS)“. 10 IETF RFC 5234: “Augmented BNF for Syntax Specifications: ABNF“. 11 3GPP TS 29.329: “Sh Interface based on the Diameter protocol“. 12 3GPP TS 29.336: “Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications“. 13
33、 3GPP TS 29.338: “Diameter based protocols to support SMS capable MMEs“. 14 3GPP TS 29.173: “Diameter-based SLh interface for Control Plane LCS“. 15 3GPP TS 29.368: “Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS)“. 16 3GPP TS 29.272: “Mobil
34、ity Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol“. ETSI ETSI TS 129 337 V13.2.0 (2017-01)73GPP TS 29.337 version 13.2.0 Release 1317 IETF RFC 4006: “Diameter Credit-Control Application“. 18 IETF RFC 7944: “Diameter Routing Message Priorit
35、y“. 3 Definitions and Abbreviations 3.1 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. ABNF
36、Augmented Backus-Naur Form AVP Attribute-Value Pair C Conditional DRMP Diameter Routing Message Priority IANA Internet Assigned Numbers Authority MTC Machine-Type Communications MTC-IWF MTC Interworking Function O Optional SCS Service Capability Server 4 General Description The T4 reference point be
37、tween the MTC-IWF and the SMS-SC is an intra PLMN interface, as defined in the 3GPP TS 23.682 7. This document describes the T4 interface related procedures, message parameters and protocol specifications. The T4 interface allows transfer of device trigger from MTC-IWF to SMS-SC inside HPLMN domain,
38、 along with the serving SGSN/MME/MSC identities, and allows SMS-SC to report to MTC-IWF the submission outcome of a device trigger and the success or failure of delivering the device trigger to the UE. 5 MTC-IWF SMS-SC (T4) 5.1 Introduction This section describes the Diameter-based T4 interface rela
39、ted procedures and information elements exchanged between the MTC-IWF and the SMS-SC. In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional in the “Cat.“ column. For the correct
40、handling of the Information Element according to the category type, see the description detailed in section 6 of the 3GPP TS 29.228 7. 5.2 Procedure Descriptions 5.2.1 Device Trigger Procedure 5.2.1.1 General This procedure shall be used between the MTC-IWF and the SMS-SC for device trigger. The pro
41、cedure shall be invoked by the MTC-IWF and is used: ETSI ETSI TS 129 337 V13.2.0 (2017-01)83GPP TS 29.337 version 13.2.0 Release 13- to transfer device trigger to SMS-SC inside HPLMN domain; - to transfer to the SMS-SC the identities of the serving MSC or MME but not both, and/or SGSN, and/or IP-SM-
42、GW serving the user for SMS along with device trigger. - to transfer device trigger replace/recall message to SMS-SC inside HPLMN domain. This procedure is mapped to the commands Device-Trigger-Request/Answer in the Diameter application specified in chapter 6. Tables 5.2.1.1/1 and 5.2.1.1/2 detail t
43、he involved information elements. ETSI ETSI TS 129 337 V13.2.0 (2017-01)93GPP TS 29.337 version 13.2.0 Release 13Table 5.2.1.1/1: Device Trigger Request Information Element Name Mapping to Diameter AVP Cat. Description User Identifier (See 3GPP TS 29.336 12) User-Identifier M This information elemen
44、t shall contain the IMSI of the UE the trigger is to be applied, formatted according to 3GPP TS 23.003 8, clause 2.2. This Information Element may contain the international ISDN number of the UE the device trigger was delivered, formatted according to 3GPP TS 23.003 8, clause 3.3. The ISDN number sh
45、all be present if it is available to the MTC-IWF. This Information Element may contain the external identifier of the UE the device trigger was delivered, formatted according to 3GPP TS 23.003 8, clause 19.7.2. The external identifier shall be present if it is available to the MTC-IWF. SM RP SMEA (S
46、ee 3GPP TS 29.338 13) SM-RP-SMEA M This Information Element shall contain the SME address of the Service Capability Server that is requesting a device trigger to the UE. It shall be encoded according to the formatting rules of the address fields described in 3GPP TS 23.040 9. Payload(See 3GPP TS 29.
47、368 15) Payload M This information element shall contain the device triggering payload as received over the Tsp. For device trigger recall, this IE shall be empty. Serving Node Identity (See 3GPP TS 29.173 14) Serving-Node C This information element shall contain the serving node identity, i.e. SGSN
48、/MME/MSC identity serving the UE. It shall be present if it is available to the MTC-IWF, e.g. the MTC-IWF retrieved this information from the HSS. Additional Serving Node Identity (See 3GPP TS 29.173 14) Additional-Serving-Node C This information element shall contain another serving node identity,
49、e.g. SGSN/MME/MSC identity, if there is any serving the UE. There may be multiple instances of this information elements. Trigger Reference Number (See 3GPP TS 29.368 15) Reference-Number C This information element shall contain the Reference Number related to the device trigger request. It shall be present if it is available to the MTC-IWF, e.g. the MTC-IWF received this information over Tsp. Old Trigger Reference Number (See 3GPP TS 29.368 15) Old-Reference-Number C This information element shall contai
