ETSI TS 129 202-2016 Universal Mobile Telecommunications System (UMTS) Signalling System No 7 (SS7) signalling transport in core network Stage 3 (V13 0 0 3GPP TS 29 202 version 13.pdf

《ETSI TS 129 202-2016 Universal Mobile Telecommunications System (UMTS) Signalling System No 7 (SS7) signalling transport in core network Stage 3 (V13 0 0 3GPP TS 29 202 version 13.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 129 202-2016 Universal Mobile Telecommunications System (UMTS) Signalling System No 7 (SS7) signalling transport in core network Stage 3 (V13 0 0 3GPP TS 29 202 version 13.pdf（24页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 1Universal Mobile TelSignallisignalling t(3GPP TS 29.2TECHNICAL SPECIFICATION129 202 V13.0.0 (2016elecommunications System (lling System No. 7 (SS7) g transport in core network; Stage 3 .202 version 13.0.0 Release 1316-01) (UMTS); 13) ETSI ETSI TS 129 202 V13.0.0 (2016-01)13GPP TS 29.202 ve

2、rsion 13.0.0 Release 13Reference RTS/TSGC-0429202vd00 Keywords 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-Prfecture de Grasse (06) N 7803

3、/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 modified without the prior

4、 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. Users of the present do

5、cument 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 document, please send your comment to one of the fo

6、llowing 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 permission of ETSI. The content of the PD

7、F 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, UMTSTMand the ETSI logo are Trade Marks of ETSI

8、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 202 V13.0.0 (2016-01)23GPP TS 29.202

9、 version 13.0.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, and can be found in ETSI SR 000 3

10、14: “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 the ETSI IPR Policy, no investigat

11、ion, 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. Foreword This Technical Specificati

12、on (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 corresponding ETSI deliverables. T

13、he 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 “cannot“ are to be interpreted as

14、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 202 V13.0.0 (2016-01)33GPP TS 29.202 version 13.0.0 Release 13Contents Intellectual Pro

15、perty Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Introduction 6g35 Protocol architectures . 7g35.1 Protocol ar

16、chitecture in the case of MTP-based SS7 signalling transport network 7g35.2 Protocol architecture in the case of IP-based SS7 signalling transport network 7g35.2.1 M3UA . 7g35.2.2 MTP3-M2PA . 7g35.3 Protocol architecture in the case of ATM-based SS7 signalling transport network . 8 g3Annex A (Normat

17、ive): The use of M3UA in 3GPP networks . 9g3A.1 Scope 9g3A.2 Introduction 9g3A.3 Protocol conformance to RFC 4666 . 10g3Annex B (Informative): The use of M2PA in 3GPP networks 18g3B.1 Scope 18g3B.2 Introduction 18g3B.3 Protocol conformance to RFC 4165 . 18g3Annex C (informative): Change history . 22

18、g3History 23g3ETSI ETSI TS 129 202 V13.0.0 (2016-01)43GPP TS 29.202 version 13.0.0 Release 13Foreword This Technical Specification 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 foll

19、owing 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

20、 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 doc

21、ument. ETSI ETSI TS 129 202 V13.0.0 (2016-01)53GPP TS 29.202 version 13.0.0 Release 131 Scope The present document defines the possible protocol architectures for transport of SS7 signalling protocols in Core Network. 2 References The following documents contain provisions which, through reference i

22、n 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 non-specific reference, the latest version applies.

23、 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. 2.1 Normative references 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 ITU-T Recommend

24、ation Q.701: “Functional description of the message transfer part (MTP) of signalling system No. 7“. 3 ITU-T Recommendation Q.702: “Signalling data link“. 4 ITU-T Recommendation Q.703: “Signalling link“. 5 ITU-T Recommendation Q.704: “Signalling network functions and messages“. 6 ITU-T Recommendatio

25、n Q.705: “Signalling network structure“. 7 ITU-T Recommendation Q.706: “Message transfer part signalling performance“. 8 RFC 2960: “Stream Control Transmission Protocol“. 9 ITU-T Recommendation G.804: “ATM cell mapping into Plesiochronous Digital Hierarchy (PDH)“. 10 ITU-T Recommendation I.112: “Voc

26、abulary of terms for ISDNs“. 11 ITU-T Recommendation I.361: “B-ISDN ATM layer specification“. 12 ITU-T Recommendation I.363.5: “B-ISDN ATM Adaptation Layer specification: Type 5 AAL“. 13 ITU-T Recommendation Q.2110: “B-ISDN ATM adaptation layer - Service specific connection oriented protocol (SSCOP)

27、“. 14 ITU-T Recommendation Q.2140: “B-ISDN ATM adaptation layer - Service specific coordination function for signalling at the network node interface (SSCF at NNI)“. 15 ITU-T Recommendation Q.2210: “Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.214

28、0“. 17 RFC 3309: “SCTP Checksum Change“. 18 RFC 4666:Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)“. ETSI ETSI TS 129 202 V13.0.0 (2016-01)63GPP TS 29.202 version 13.0.0 Release 1319 RFC 4165: Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) -User Peer

29、-to-Peer Adaptation Layer (M2PA)“. 2.2 Informative references 16 RFC 2719: “Framework Architecture for Signalling Transport“. 3 Definitions 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 defin

30、ed in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. (no further terms defined) 3.2 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 docu

31、ment takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. AAL5 ATM Adaptation Layer type 5 ATM Asynchronous Transfer Mode IP Internet Protocol MTP Message Transfer Part MTP1 Message Transfer Part layer 1 MTP2 Message Transfer Part layer 2 MTP3 Message Transfer Part

32、layer 3 M2PA Message Transfer Part 2 -User Peer-to-Peer Adaptation Layer M3UA MTP3-User Adaptation PDH Plesiochronous Digital Hierarchy SSCF Service Specific Coordination Function SSCOP Service Specific Connection Oriented Protocol SCCP Signalling Connection Control Part SCTP Stream Control Transmis

33、sion Protocol SDH Synchronous Digital Hierarchy TCAP Transaction Capabilities Application Part 4 Introduction The Core Network enables the transport of SS7 signalling protocols between two entities by means of different underlying networks (e.g. MTP-based, IP-based or ATM-based). The transport of SS

34、7 signalling protocol messages of any protocol layer that is identified by the MTP level 3 layer, in SS7 terms, as a user part (MTP3-user) shall be accomplished in accordance with the protocol architecture defined in the following sub-clauses. The list of these protocol layers includes, but is not l

35、imited to, Signalling Connection Control Part (SCCP). The transport of protocols which can be identified as SCCP-users, like for example TCAP, and in turn the transport of TCAP-users like MAP and CAP, shall also be accomplished in accordance with the defined protocol architectures, since their proto

36、col messages are transferred as SCCP payload. ETSI ETSI TS 129 202 V13.0.0 (2016-01)73GPP TS 29.202 version 13.0.0 Release 135 Protocol architectures 5.1 Protocol architecture in the case of MTP-based SS7 signalling transport network The transport of an MTP3-user signalling messages shall be accompl

37、ished in accordance with the relevant ITU-T Recommendations 2, 3, 4, 5, 6, 7. The protocol architecture applicable in the case of MTP-based SS7 signalling transport network is shown in Figure 5.1/1 MTP3-User MTP3 MTP2 MTP1 Figure 5.1/1: Protocol architecture in the case of MTP-based SS7 signalling t

38、ransport network 5.2 Protocol architecture in the case of IP-based SS7 signalling transport network 5.2.1 M3UA The transport of an MTP3-user signalling messages shall be accomplished in accordance with the architecture defined by the “Framework Architecture for Signalling Transport“ 16, by “Stream C

39、ontrol Transmission Protocol“8 and by the IETF document available in Annex A. An implementation of SCTP to this document shall use the checksum method specified in RFC 3309 17 instead of the method specified in RFC 2960 8. The M3UA protocol architecture applicable in the case of IP-based SS7 signall

40、ing transport network is shown in Figure 5.2/1 MTP3-User M3UA SCTP IP Figure 5.2/1: M3UA architecture in the case of IP-based SS7 signalling transport network The definition of the use of M3UA in 3GPP core network is provided in Annex A to this specification. 5.2.2 MTP3-M2PA An MTP3 signalling messa

41、ge can also be transported by M2PA, which shall be accomplished in accordance with IETF RFC 416519. The M2PA protocol architecture applicable in the case of IP-based SS7 signalling transport network is shown in Figure 5.2/2 MTP3 M2PA SCTP IP ETSI ETSI TS 129 202 V13.0.0 (2016-01)83GPP TS 29.202 vers

42、ion 13.0.0 Release 13Figure 5.2/2: M2PA architecture in the case of IP-based SS7 signalling transport network The definition of the use of M2PA in 3GPP core network is provided in Annex B to this specification. 5.3 Protocol architecture in the case of ATM-based SS7 signalling transport network The t

43、ransport of an MTP3-user signalling messages shall be accomplished in accordance with the relevant ITU-T Recommendations 9, 10, 11, 12, 13, 14, 15 The protocol architectures applicable in the case of ATM-based SS7 signalling transport network are shown in Figure 5.3/1. ATM over SDH MTP3-User MTP3 B

44、SSCF SSCOP AAL5 ATM ATM over PDH MTP3-User MTP3 B SSCF SSCOP AAL5 G.804 Figure 5.3/1: Protocol architectures in the case of ATM-based SS7 signalling transport network ETSI ETSI TS 129 202 V13.0.0 (2016-01)93GPP TS 29.202 version 13.0.0 Release 13Annex A (Normative): The use of M3UA in 3GPP networks

45、A.1 Scope This annex defines the application of M3UA in 3GPP core networks. The purpose of the Annex is to ensure the interoperability of different implementations of M3UAs used by different operators and vendors. This is achieved by: - Clarifying certain concepts which are used in RFC 4666; - Defin

46、ing those features in RFC 4666 for which support is mandatory; - Defining those features in the RFC 4666 for which support is optional; - Defining those features in RFC 4666 which shall not be used; The specification is intended for interfaces between network domains, however, it can also be used in

47、side one network domain, and constitutes a minimum set of M3UA requirements to be supported between IP nodes and between IP nodes and SGW nodes in a 3GPP network. A.2 Introduction M3UA may be used on a number of interfaces in a 3GPP core network. The annex is intended for the interface called A and

48、C in figure 1. A is the Interface between two IP nodes that are equipped with SCTP, M3UA and a M3UA user. Examples of M3UA user are BICC, H.248, SCCP and ISUP. The interface can be used inside one network domain but also to interconnect network domains. Interface B can be used between network domain

49、s and inside network domains. Interface B is not in the scope for this annex, however, use of Q.701-Q.705 or Q.2210 on interface B is already standardised; in addition, M2PA is also endorsed for interface B in accordance with Annex B. Interface C is the interface between a node including SCTP, M3UA and a M3UA user and a node including SCTP, M3UA and M3UAsignalling gateway functions This interface is inside one network domain. Interfaces A and C are similar. The main difference is that in