ETSI TR 102 019-2002 Services and Protocols for Advanced Networks (SPAN) Design Requirements for ITU J arch J istp and J tgcp (V1 1 1)《高级网络的业务和协议(SPAN) ITU J arch J istp和J tgcp的设计要.pdf

《ETSI TR 102 019-2002 Services and Protocols for Advanced Networks (SPAN) Design Requirements for ITU J arch J istp and J tgcp (V1 1 1)《高级网络的业务和协议(SPAN) ITU J arch J istp和J tgcp的设计要.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 102 019-2002 Services and Protocols for Advanced Networks (SPAN) Design Requirements for ITU J arch J istp and J tgcp (V1 1 1)《高级网络的业务和协议(SPAN) ITU J arch J istp和J tgcp的设计要.pdf（75页珍藏版）》请在麦多课文档分享上搜索。

1、ETSI TR 102 O19 1.1.1 (2002-02) Technical Repor Services and Protocols for Advanced Networks (SPAN); Design requirements for ITU J.arch, J.istp and J.tgcp 2 ETSI TR 102 O19 VI .I .I (2002-02) Reference DTR/SPAN-00001 O Keywords cable, IP, protocol ETSI 650 Route des Lucioles F-O6921 Sophia Antipolis

2、 Cedex - FRANCE Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Siret No 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-prfecture de Grasse (06) No 7803/88 Important notice Individual copies of the present document can be downloaded from: http:l/w.etsi .orq The present

3、document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of

4、the PDF version kept on a specific network drive within 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 3 If you find errors in the pre

5、sent document, send your comment to: Cori vriaht Notifica tion No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecommunications Standards Institute 2002. All rights reserved. ETSI 3 ET

6、SI TR 102 O19 VI .I .I (2002-02) Contents Intellectual Property Rights . .8 Foreword . 8 1 Scope 9 2 References . .9 3 Definitions and abbreviations. 1 O 10 3.1 Definitions . . 10 3.2 Abbreviations . 4 Overview and purpose 11 4.1 History and relationships to other standar 12 4.2 ITU-T IPCablecom ram

7、ework 12 4.2.1 IPCablecom reference architecture. 13 4.2.2 Interfaces . 14 4.2.3 Bundling and unbundling of compone 14 4.2.4 IPCablecom zones and domains . 14 5 Requirements obtained from J.arch 15 5.1 5.1.1 5.1.2 5.1.3 5.2 5.2.1 5.2.2 5.3 5.3.1 5.3.1.1 5.3.1.2 5.3.1.3 5.3.1.4 5.3.1.5 5.3.1.6 5.3.1.

8、7 5.3.1.8 5.3.2 5.3.2.1 5.3.2.2 5.3.2.3 5.3.2.4 5.3.2.5 5.3.2.6 5.3.2.7 5.3.2.8 5.3.2.9 5.3.2.10 5.3.2.1 1 5.3.2.12 5.3.2.13 5.3.2.14 5.3.2.15 5.3.2.16 5.3.2.17 5.3.2.18 5.3.2.19 . 15 . 15 . 15 . 16 . 16 . 16 Three architectures, possible three phases Commercial requirements for IPCablecom Implicit

9、commercial requirements LegaVRegulator observations . . 16 Technical requirements . 17 Architecture goals of J.arch . 17 General architecture goals . . 17 Call signalling requirements . 17 Call features . 18 Quality of Service (QoS) requirements. . 18 Codec and media stream requirements . 19 Device

10、provisioning and OSS requirements 19 Security requirements. . 19 Managed IP network goal . 20 Requirements from components . 20 Trust . .20 Subscriber side requirements 20 MTA Functional requirements 21 Access Node (AN) MTA functional requirements 21 Access Node (AN) MTA managed IP functional requir

11、ements 22 CMS Call agent functions . CMS Announcement controller furictions . .22 . .22 22 22 23 23 23 24 24 24 25 25 25 25 . . MGC functions . . . . . . . . . . 25 26 5.3.2.19.1 . 5.3.2.19.2 . 5.3.2.20 Announcement options . 26 ETSI 4 ETSI TR 102 O19 VI . 1 . 1 (2002-02) 5.3.2.2 1 Security: Privacy

12、 and fraud prevention . 26 5.3.2.22 Time of day requirements . 26 5.3.2.23 Clocks . 27 5.3.2.24 IP addressing . 27 5.3.2.24.1 One CM and one MTA 27 5.3.2.24.2 Dynamic IP addressing 27 5.3.2.25 Packet prioritization 27 5.3.2.26 Fax support 27 5.3.2.27 Analogue modem support . 28 6 Requirements obtain

13、ed from J.istp . 28 6.1 6.1.1 6.1.2 6.1.2.1 6.1.2.2 6.1.2.3 6.1.2.4 6.1.2.5 6.1.2.6 6.1.2.7 6.2 6.2.1 6.2.1.1 6.2.1.2 6.2.1.3 6.2.1.4 6.2.1.5 6.2.1.6 6.2.1.7 6.2.2 6.2.2.1 6.2.2.2 6.2.2.3 6.2.2.4 6.2.2.5 6.2.2.6 6.2.3 6.2.3.1 6.2.3.2 6.2.3.3 6.2.3.4 6.2.3.5 6.2.3.6 6.2.3.7 6.2.3.8 6.2.3.9 6.2.3.10 6

14、.2.3.1 1 6.2.3.12 6.2.3.13 6.2.3.14 6.2.3.15 6.2.3.16 6.2.4 6.2.4.1 6.2.4.2 6.2.4.3 6.2.4.4 6.2.4.5 6.2.4.6 6.2.4.7 Overview 28 Scope 28 What is J.istp? . 28 Note on SG and ISTP 29 Protocol distribution in IPCablecom elements 29 General ISTP functions . 29 ISTP specification goals 30 ISTP in decompo

15、sed IPCablecom gateway . 30 Areas beyond the scope of J.istp . 31 ISTP and IETF 31 J.istp: Technical requirements 31 J.istp: Framework and architecture requirements . 31 High Level SG/ISTP requirements . 31 Support of J.arch framework service goals . 32 SG SS7 temnation requirements . 32 Functional

16、SG signalling requirements . 32 Functional SG interface requirements . 33 Architecture Zone/Domain goals 33 Reliable underlying transport 33 J.istp: Availability and Performance Requirements 34 Distribution model Background 34 Distribution Model 34 34 35 Call Performance 35 Traffic Performance 35 J.

17、istp: Distribution mod 36 Bi-directional mapping among components 36 Numbering: MGC name to IP addres 36 Numbering: circuits and transactions 36 Message distribution 36 37 37 Initialization 37 Recovery . 37 Dynamic provisioning updates 38 Administration 38 ISTP Security 38 Maintenance 38 Measurement

18、 . 39 Alarms . 39 SG management notification . 39 J.istp: SS7 related protocol requirements 39 ISTP protocol requirements 39 ISTP connection requirements 40 ISTP SS7 encoding requirements 40 ISTP load-sharing and sequencing 40 Circuit registration and activation . 40 Transaction subsystem registrati

19、on . 41 Message failure detection and handling 41 . . . Congestion 39 ETSI 5 ETSI TR 102 O19 VI .I .I (2002-02) 6.2.4.8 Heartbeat 41 6.2.4.9 Signalling accessibility procedures. 41 6.2.4.10 SG congestion handling 42 6.2.4.1 1 IPCablecom component management procedures .42 6.2.4.12 IP usage 6.2.5 J.i

20、stp: Future work 42 7 . . .42 Requirements obtained from J.tgcp . .43 7.1 7.1.1 7.1.2 7.1.2.1 7.1.2.2 7.1.2.3 7.1.2.4 7.1.2.5 7.2 7.2.1 7.2.1.1 7.2.1.2 7.2.1.3 7.2.1.4 7.2.1.5 7.2.1.6 7.2.2 7.2.2.1 7.2.2.2 7.2.2.3 7.2.2.4 7.2.2.5 7.2.2.6 7.2.2.7 7.2.2.8 7.2.2.9 7.2.2.10 7.2.2.1 1 7.2.2.12 7.2.2.13 7

21、.2.3 7.2.3.1 7.2.3.2 7.2.3.3 7.2.3.4 7.2.3.5 7.2.3.6 7.2.3.7 7.2.4 7.2.4.1 7.2.4.2 7.2.4.3 7.2.4.4 7.2.4.5 7.2.4.6 7.2.4.7 7.2.4.8 7.2.5 7.2.5.1 7.2.6 7.2.6.1 7.2.6.2 7.2.6.3 7.2.6.4 Overview . Scope . What is J.tgcp? . Note on MG, MGC, TGCP and MGCI . .43 TGCP in the protocol stack . .44 J.tgcp Tru

22、nking Gateway Document. . . .44 First level decomposition of a Managed IP Network . . .44 Areas beyond the scope of J.tgcp . 45 J.tgcp: Technical requirements 45 J.tgcp: Framework and Architecture Requirements . 45 45 Support of J.arch fiamework service goals High level control requirements . 45 Hig

23、h level IP side management requirements . .46 TGCP high level trunk side requirements . .46 Other Trunking Gateway Requirements .46 Distribution model .47 J.tgcp: MGCI API requirements . .47 Model and naming convention .47 Endpoint name .47 Trunk name . .47 Call and Connection names . . 48 MGC namin

24、g . . 48 MGC name binding . . 48 Digit Maps . 48 Packages . 48 Experimental Packages . . .49 Wildcard support . 49 Events and Signals on connections 49 Session Description Protocol 50 Gateway control functions 50 50 Commands 50 Calls 50 Connection mode parameter. 51 Audio connection modes . 51 Loop-

25、back and continuity testing 51 Continuity test (COT) . t message and parameters . Notification request CO Dynamic configuration of events . Event requests . . . Requirements from notific Default vs. dynamically set events . Not requirements . 55 Requirements from create connection message and parame

26、ters 55 Connection definition. 55 Local connection characteristics 55 Local connection options for IP security 56 Local connection LI requirements 56 ETSI 6 ETSI TR 102 O19 VI .I .I (2002-02) 7.2.6.5 7.2.6.6 7.2.7 7.2.7.1 7.2.7.2 7.2.8 7.2.8.1 7.2.8.2 7.2.8.3 7.2.9 7.2.9.1 7.2.9.2 7.2.9.3 7.2.10 7.2

27、.10.1 7.2.11 7.2.11.1 7.2.12 7.2.12.1 7.2.12.2 7.2.12.3 7.2.13 7.2.13.1 7.2.13.2 7.2.13.3 7.2.13.4 7.2.13.5 7.2.13.6 7.2.13.7 7.2.13.8 7.2.13.9 7.2.13.10 7.2.13.11 7.2.13.12 7.2.13.13 7.2.13.14 7.2.14 7.2.14.1 7.2.14.2 7.2.14.3 7.2.14.4 7.2.14.5 7.2.14.6 7.2.14.7 7.2.14.8 7.2.14.9 7.2.14.10 7.2.14.1

28、1 7.2.14.12 7.2.14.13 7.2.14.14 7.2.14.15 7.2.14.16 7.2.14.17 7.2.15 7.2.15.1 7.2.15.2 7.2.15.3 7.2.15.4 7.2.15.5 7.2.16 7.2.16.1 Remote connections . . 56 Local connection modes . . 56 Requirements from ModiSl 57 ModiSl connection . . 57 Synchronized create and modiSl connecti . 57 parameters 58 De

29、lete message usage . . 58 Return performance data . 58 Synchronized not and delete connection . 58 arameters 58 Delete connection forced by MG . . 58 Delete multiple or all connections 59 Auditing . . 59 Requirements from audit endpoint message and parameters . .59 Audit endpoint . 59 Requirements f

30、rom audit c and parameters . 60 Auditing connections . . 60 Requirements from restart in progress message and parameters . .60 Restart in progress . 60 Restart method types . 60 MG restart in progress response . 61 J.tgcp: API recovery requirements . 61 Autonomous fault detec . 61 Endpoint/MGC recov

31、ery model . Detection of lost association Repetition mechanism. . Repeat transmssion algorithm . Repeat algorithm timers . Requirements from Delete Connection (fiom Requirements from Delete Race conditions . Restart execution Disconnected end nt . . 64 Consistent return . . 65 .65 . 65 Command Heade

32、r . . 65 Command line . . 65 Requested verb naming. . 66 Transition identity handling . 66 Name and protocol version coding . 66 Parameter lines. . . 67 Requirements on parameters in parameter line . . 67 Response header .67 Retry at the protocol levels . 68 Post-retry at the protocol level . . 68 P

33、iggy-backing protocol . 68 Transaction identifier sharing . . 68 . 69 Provisional response . . 70 Security . 70 . 70 . 70 Continuity tone (COT) and fax tone . 71 Call tones . . 71 Operation failure . 71 Long duration and medi . 71 Introduction . 71 ETSI 7 ETSI TR 102 O19 VI . 1 . 1 (2002-02) Outgoin

34、g operator service package eventdsignals 72 7.2.16.2 7.2.16.3 MF temnating protocol package . 73 7.2.17 Future work . 73 Annex A: Bibliography 74 History 75 ETSI 8 ETSI TR 102 O19 VI .I .I (2002-02) Intellectual Property Rights IPRs essential or potentially essential to the present document may have

35、 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 O00 314: “Intellectual Property Rights (7PRs); Essential, orpotentially Essential, IPRs notlJied to ETSI in respect ofETSI standards

36、“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (5). Pursuant 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 O00

37、 3 14 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Services and Protocols for Advanced Networks (SPAN). The present document describes the requirements

38、 used in the design and specification of the general architecture, the IPCablecom Signalling Transport Protocol (ISTP), and the Trunking Gateway Control Protocol of the ITU IPCablecom set of specifications. The requirements listed in the present document have been obtained by reverse engineering of

39、the specific ITU Recommendations, i.e. J.istp or ITU-T RecommendationJ. 165 2 for the IPCablecom Signalling Transfer Protocol, J.arch or ITU-T Recommendation J.160 i for the architectural framework, and J.tgcp or ITU-T Recommendation J.171 3 for the Tninkng Gateway Control Protocol. ETSI 9 ETSI TR 1

40、02 O19 VI .I .I (2002-02) 1 Scope The present document specifies the design and specification requirements obtained from reverse engineering a set of ITU recommendations, consisting of J. arch (architectural framework), J.istp (IPCablecom Signalling Transfer Protocol), and J.tgcp (Tninkng Gateway Co

41、ntrol Protocol). These documents are part of a set of ITU documents describing the IPCablecom framework and its subparts. These documents are based on the Packetcable 1 .O specifications written by CableLabs in the United States, and modified to meet more global requirements and formatting conventio

42、ns of the ITU. The requirements obtained from reversed the specified documents can be explicitly listed or implied, commercial or technical. The present document does not contain all of the IPCablecom requirements, which cover a set of documents addressing additional areas of quality of service, sec

43、urity, lawful intercept, network interface, remote digital thermals, on network call singling, managed object provisioning, event messaging, and other major areas. Some operator requirements (example: billing, OSS presentation, etc.) are deliberately not covered in IPCablecom; these are considered n

44、ormal to vendor/operation (RFQ/RFI) negotiations to meet subscriber needs in a market. These operational requirements are not covered here except where they are defiied in the source documentation. In the present document, all requirements have been presented with “MUST“, “SHALL“, “SHOULD“, or “MAY“

45、 as the active verb. “It“ in the present document when coupled to a requirement refers to IPCablecom in general. In particular, must and must no were used instead of shall or shall not to spec requirements, should or should not were used to spec recommendations, may or may not were used to spec perm

46、issions or possibilities, and can or can not were not used to spec possibly. The present document contains the original requirements as created for the Packetcable 1 .O specifications (written by CableLabs in the United States). These base requirements can be realized by using other protocol stacks

47、and are not restricted to those specified in the present document. The base requirements that are implied by the protocols should be included in any protocol implementation. 2 Re fe re nces For the purposes of this Technical Report (TR) the following references apply: il ITU-T Recommendation J. 160

48、(J.arch): “Architectural framework for the delivery of time critical services over cable television networks using cable modems“. ITU-T Recommendation J. 165 (J.istp): “IPCablecom Signalling Transport Protocol“ ITU-T Recommendation J. 171 (J.tgcp): “IPCablecom Tninkng Gateway Control Protocol“. ITU-

49、T Recommendation J. 1 12: “Transmission systems for interactive cable television services“. 21 31 41 51 61 ITU-T Recommendation G.7 1 1 : “Pulse code modulation (PCM) of voice frequencies“ ITU-T Recommendation J. 162: “Network call signalling protocol for the delivery of time critical services over cable television networks using cable modems“. ITU-T Recommendation E. 164: “The international public telecommunication numbering plan“ 71 SI 91 lo1 i 11 121 i31 i41 IETF RFC 1899: “Request for Comments Summary RFC Numbers 1800-1 899“. IETF RFC 189