ETSI TS 129 368-2016 Universal Mobile Telecommunications System (UMTS) LTE Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS.pdf

1、 ETSI TS 1Universal Mobile TelTsp interface protocFunction (MTC-IWF) a(3GPP TS 29.3TECHNICAL SPECIFICATION129 368 V13.1.0 (2016elecommunications System (LTE; tocol between the MTC Interw) and Service Capability Serve.368 version 13.1.0 Release 1316-03) (UMTS); r orking er (SCS) 13) ETSI ETSI TS 129

2、368 V13.1.0 (2016-03)13GPP TS 29.368 version 13.1.0 Release 13Reference RTS/TSGC-0329368vd10 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 enregi

3、stre la Sous-Prfecture 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 docu

4、ment shall not be modified 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 with

5、in ETSI Secretariat. 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 http:/portal.etsi.org/tb/status/status.asp If you find errors in the present documen

6、t, please send 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 writt

7、en permission 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 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTS

8、TMand the ETSI 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

9、 TS 129 368 V13.1.0 (2016-03)23GPP TS 29.368 version 13.1.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 no

10、n-members, 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/). Pu

11、rsuant to the 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 d

12、ocument. Foreword 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 referenc

13、es to the corresponding 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“,

14、“can“ and “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 368 V13.1.0 (2016-03)33GPP TS 29.368 versio

15、n 13.1.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Symbols 7g33.3 Abbreviations . 7g34 Tsp reference point . 7g34.1 Tsp Reference model 7g34

16、.2 Functional elements 8g34.2.1 SCS . 8g34.2.2 MTC-IWF . 8g35 Procedures over Tsp reference point 9g35.1 General . 9g35.2 Reference number handling 9g35.3 MTC-IWF selection . 9g35.4 MTC-IWF load control 9g35.5 Request and confirmation of a device trigger . 10g35.6 Notification of Device trigger 10g3

17、5.7 Request and confirmation of a device trigger recall request 11g35.8 Request and confirmation of a device trigger replace request 11g36 Tsp protocol 12g36.1 Protocol support . 12g36.1.1 Use of Diameter base protocol 12g36.1.2 Transport protocol 13g36.1.3 Advertising Application Support 13g36.2 In

18、itialization and maintenance of connection and session 13g36.3 Security on the Tsp interface 13g36.3.1 General 13g36.3.2 Mutual authentication . 13g36.3.3 Security profiles 14g36.4 Tsp specific AVPs 14g36.4.1 General 14g36.4.2 Device-Action AVP 15g36.4.3 Device-Notification AVP . 15g36.4.4 Trigger-D

19、ata AVP 16g36.4.5 Payload AVP 16g36.4.6 Action-Type AVP . 16g36.4.7 Priority-Indication AVP 16g36.4.8 Reference-Number AVP. 17g36.4.9 Request-Status AVP . 17g36.4.10 Delivery-Outcome AVP . 18g36.4.11 Application-Port-Identifier AVP 18g36.4.12 Old-Reference-Number AVP 19g36.4.13 Feature-Supported-In-

20、Final-Target AVP 19g36.5 Tsp re-used AVPs . 19g36.5.1 General 19g36.5.2 Supported-Feature-List AVP 20g3ETSI ETSI TS 129 368 V13.1.0 (2016-03)43GPP TS 29.368 version 13.1.0 Release 136.5.2.1 Use of the Supported-Features AVP . 20g36.5.2.2 Supported-Feature-List AVP for the Tsp application . 20g36.6 T

21、sp Messages . 21g36.6.1 Command-Code Values 21g36.6.2 Device-Action-Request (DAR) command 21g36.6.3 Device-Action-Answer (DAA) command 21g36.6.4 Device-Notification-Request (DNR) command 22g36.6.5 Device-Notification-Answer (DNA) command 22g3Annex A (informative): Tsp Message Flows. 23g3A.1 General

22、. 23g3A.2 Tsp Submission, T4 Delivery . 23g3A.3 Tsp failed Submission 24g3A.4 Tsp Submission, Failed T4 Delivery 25g3A.5 Tsp Recall Submission, Recall Success . 26g3A.6 Tsp Recall Submission, Recall Failure . 27g3A.7 Tsp Replace Submission, Replace Success 27g3A.8 Tsp Replace Submission, Replace Fai

23、lure . 28g3Annex B (informative): Change history . 30g3History 31g3ETSI ETSI TS 129 368 V13.1.0 (2016-03)53GPP TS 29.368 version 13.1.0 Release 13Foreword This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject

24、 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 dig

25、it: 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 ed

26、itorial only changes have been incorporated in the document. ETSI ETSI TS 129 368 V13.1.0 (2016-03)63GPP TS 29.368 version 13.1.0 Release 131 Scope The present document provides the stage 3 specification of the Tsp reference point for the present release. The functional requirements and the stage 2

27、specifications of the Tsp reference point are contained in TS 23.682 2. The Tsp reference point lies between the Service Capability Server (SCS) and the Machine Type Communication Inter Working Function (MTC-IWF). 2 References The following documents contain provisions which, through reference in th

28、is 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 non-specific reference, the latest version applie

29、s. 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 Specifications“. 2 3GPP TS 23.682: “Architecture enhancem

30、ents to facilitate communications with packet data networks and applications“. 3 3GPP TS 29.329: “Sh Interface based on the Diameter protocol“. 4 IETF RFC 791: “Transmission Control Protocol“. 5 IETF RFC 2234: “Augmented BNF for syntax specifications“. 6 IETF RFC 3588: “Diameter Base Protocol“. 7 IE

31、TF RFC 4006: “Diameter Credit Control Application“. 8 IETF RFC 4960: “Stream Control Transmission Protocol“. 9 IETF RFC 5719: “Updated IANA Considerations for Diameter Command Code Allocations“. 10 3GPP TS 33.210: “Network Domain Security (NDS); IP network layer security“. 11 3GPP TS 33.310: “Networ

32、k Domain Security (NDS); Authentication Framework (AF)“. 12 3GPP TS 29.336: “Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications“. 13 3GPP TS 29.303: “Domain Name System Procedures; Stage 3“. 14 3GPP TS 23.003: “Numbering, addressing and ident

33、ification“. 15 3GPP TS 23.040: “Technical realization of the Short Message Service (SMS)“. 16 3GPP TS 29.229: “Cx and Dx interfaces based on the Diameter protocol“. 17 3GPP TS 29.337: “Diameter-based T4 interface for communications with packet data networks and applications“. 18 IETF RFC 6733: “Diam

34、eter Base Protocol“. ETSI ETSI TS 129 368 V13.1.0 (2016-03)73GPP TS 29.368 version 13.1.0 Release 133 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following apply. A term defined in the present

35、 document takes precedence over the definition of the same term, if any, in TR 21.905 1. 3.2 Symbols For the purposes of the present document, no symbols are defined. 3.3 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbrev

36、iation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. AVP Attribute Value Pair CEA Capabilities-Exchange-Answer CER Capabilities-Exchange-RequestDAA Device-Action-Answer DAR Device-Action-RequestDNA Device-Notification-Answer DN

37、R Device-Notification-Request DNS Domain Name System ESP Encapsulating Security Payload IKE Internet Key Exchange IWF Inter Working Function MTC Machine Type Communication PKI Public key infrastructure SCS Service Capability Server TLS Transport Layer Security 4 Tsp reference point 4.1 Tsp Reference

38、 model The Tsp reference point is defined between the Service Capability Server (SCS) and the Machine Type Communication Inter Working Function (MTC-IWF). The relationships between the different functional entities involved are depicted in figure 4.1.1. ETSI ETSI TS 129 368 V13.1.0 (2016-03)83GPP TS

39、 29.368 version 13.1.0 Release 13Services Capability Server ( SCS ) Tsp MTC - IWF SMS - SC / GMSC / IWMSC T 4 S 6 m Rf / Ga Um / Uu / LTE - Uu MTC UE Application UE RAN HSS Application Server ( AS ) CDF /CGF SGSN/MME/MSC Control plane User plane Figure 4.1.1: Tsp reference point at 3GPP Architecture

40、 for Machine -Type Communication 4.2 Functional elements 4.2.1 SCS The SCS is the entity which connects MTC application servers to the 3GPP network to enable them to communicate through specific 3GPP defined services with UEs used for MTC and with the MTC-IWF in the HPLMN. The SCS offers capabilitie

41、s for use by one or multiple MTC application servers. An SCS can be connected to one or more MTC-IWFs. The SCS is controlled by the operator of the HPLMN or by a MTC Service Provider. 4.2.2 MTC-IWF The MTC-IWF resides in the HPLMN. An MTC-IWF could be a standalone entity or a functional entity of an

42、other network element. The MTC-IWF hides the internal PLMN topology and relays or translates information sent over Tsp to invoke specific functionality in the PLMN. An MTC-IWF can be connected to one or more SCSs. The functionality of the MTC-IWF includes the following: - terminates the Tsp, S6m, T4

43、 and Rf/Ga reference points; - supports ability to authorize the SCS before communication establishment with the 3GPP network; - supports ability to authorize control plane requests from an SCS; - supports the following device trigger functionality: - reception of a device trigger request from SCS;

44、- reception of a device trigger recall/replace request from SCS; - reporting to the SCS the acceptance or non-acceptance of the device trigger request; - reporting to the SCS the acceptance or non-acceptance of the device trigger recall/replace request; - reports to the SCS the success, failure or u

45、nconfirmed outcome of a device trigger delivery; ETSI ETSI TS 129 368 V13.1.0 (2016-03)93GPP TS 29.368 version 13.1.0 Release 13- reports to the SCS the success, failure or unconfirmed outcome of the device trigger recall/replace request; - provides load control information to SCS as part of the res

46、ponse to trigger requests; - supports ability for secure communication between the 3GPP network and the SCS. The architecture allows the use of multiple MTC-IWFs within a HPLMN. 5 Procedures over Tsp reference point 5.1 General The following procedures apply over the Tsp reference point: - Request a

47、nd confirmation of a device trigger - Notification of a device trigger - Recalling or replacing of an already submitted device trigger 5.2 Reference number handling The reference number shall be assigned by the SCS. The reference number shall be provided by the SCS to the MTC-IWF in the first proced

48、ure initiated for a specific target of a specific action request (e.g. for a device trigger request towards a specific MTC device). The MTC-IWF and SCS shall use this reference number for all consecutive related procedures (e.g. for a confirmation of device trigger and notification of device trigger

49、). The reference number shall be kept in MTC-IWF and in SCS until all related procedures for a specific target of a specific action request initiated by the SCS are completed (e.g. until the notification of device trigger is completed). For each new specific action request other than Device Trigger Recall Request, the SCS shall assign a reference number, which is different from any other reference number it has previously assigned to any other another action request with not yet completed related procedures. 5.3 MTC-IWF selection