ETSI ES 283 039-2-2010 Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) NGN Congestion and Overload Control Part 2 Core GOCAP and N_1.pdf

1、 ETSI ES 283 039-2 V3.1.1 (2010-01)ETSI Standard Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);NGN Congestion and Overload Control;Part 2: Core GOCAP and NOCA Entity Behavioursfloppy3ETSI ETSI ES 283 039-2 V3.1.1 (2010-01)2Reference DES/TISPAN-03034

2、-2-NGN-R3 Keywords control, quality, protocol 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/88 Important notice I

3、ndividual copies of the present document can be downloaded from: http:/www.etsi.org The present 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 Doc

4、ument Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of 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

5、 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 following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be rep

6、roduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2010. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of

7、ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the

8、 GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI ES 283 039-2 V3.1.1 (2010-01)3Contents Intellectual Property Rights 7g3Foreword . 7g31 Scope 8g32 References 8g32.1 Normative references . 8g32.2 Informative references 9g33 Definitions and abbreviations . 9g33.1 Defini

9、tions 9g33.2 Abbreviations . 9g34 Control Architecture . 10g34.1 Description of NOCA Components 10g34.2 Detailed Description of NOCA Components and Behaviour . 12g34.2.1 Overview 12g34.2.2 Control Adaptor (CAProcess) . 14g34.2.2.1 Control Adaptor Data 14g34.2.2.2 CAProcess signals . 15g34.2.2.3 Cont

10、rol Adaptor Behaviour . 15g34.2.2.4 Generating Control Adaptor Input 19g34.2.3 Control Distribution (SDL: CDProcess) . 19g34.2.3.1 Control Distribution data . 19g34.2.3.2 Control Distribution Signals . 20g34.2.3.3 Control Distribution Behaviour . 20g34.2.4 CDRestriction . 23g34.2.4.1 CDRestriction D

11、ata . 24g34.2.4.2 CDRestrictor Signals. 24g34.2.4.3 CDRestrictor Behaviour 25g34.2.5 Restrictor Manager (RMProcess) . 28g34.2.5.1 Restrictor Manager Data . 29g34.2.5.2 Restrictor Manager Signals . 30g34.2.5.3 Restrictor Manager Behaviour 30g34.2.6 Restrictor 33g34.2.6.1 Restrictor data . 34g34.2.6.2

12、 Restrictor signals . 34g34.2.6.3 Restrictor behaviour 34g34.2.7 GOCAP Transport 35g34.2.7.1 The structure of the GOCAP transport layer. 35g34.2.7.2 Channel Manager 37g34.2.7.2.1 Channel Manager Data 37g34.2.7.2.2 Channel Manager Signals 37g34.2.7.2.3 Channel Manager Behaviour . 38g34.2.7.3 Shim Pro

13、cess . 39g34.2.7.3.1 Shim Process Signals . 39g34.2.7.3.2 Shim Process Behaviour 39g34.2.7.4 GocapListener . 40g34.2.7.5 SessionHandler 40g35 GOCAP over Diameter 40g35.1 Introduction 40g35.2 Use of the Diameter base protocol . 41g35.2.1 Advertising GOCAP support 41g35.2.2 Securing Diameter messages

14、41g35.2.3 Accounting functionality 41g35.2.4 GOCAP commands. 41g35.2.4.1 AA-Request (AAR) command 41g3ETSI ETSI ES 283 039-2 V3.1.1 (2010-01)45.2.4.2 AA-Answer (AAA) Command . 42g35.2.4.3 Profile-Update-Request (PUR) command . 42g35.2.4.4 Profile-Update-Answer (PUA) command . 43g35.2.4.5 Session-Ter

15、mination-Request (STR) command 43g35.2.4.6 Session-Termination-Answer (STA) command 43g35.2.4.7 Abort-Session-Request (ASR) command 44g35.2.4.8 Abort-Session-Answer (ASA) command 44g35.2.5 AVP definitions 44g35.2.5.1 Auth_Scope . 45g35.2.5.2 AVP GOCAP-Body 45g35.2.6 Restrictions on AVP values 45g35.

16、2.6.1 Auth-Request-Type . 45g35.2.6.2 Auth-Session-State AVP . 45g35.3 Procedures to be used with Diameter messages . 45g35.3.1 Introduction. 45g35.3.2 Diameter ChannelManager . 46g35.3.3 Diameter Shim 46g35.3.3.1 Diameter Shim data . 47g35.3.3.2 Diameter shim behaviour 47g35.3.3.3 Generating PUR me

17、ssages 49g35.3.4 Diameter Listener . 50g35.3.4.1 Diameter session initiation 51g35.3.4.2 Diameter session termination 52g35.3.4.3 Gocap commands 52g35.3.5 Diameter Session Handler 52g35.3.6 GOCAP Timers 54g35.4 Diameter MSC charts . 54g35.4.1 Simple Diameter session . 54g36 GOCAP over SIP . 56g36.1

18、General . 56g36.2 Overview 57g36.2.1 GOCAP Slave . 57g36.2.1.1 Subscription 57g36.2.1.2 Receiving Notifications . 57g36.2.2 GOCAP Master. 58g36.2.2.1 Subscription 58g36.2.2.2 Notification . 58g36.3 Detailed procedures 59g36.3.1 Introduction. 59g36.3.2 GOCAP Master . 59g36.3.2.1 SIP ChannelManager 59

19、g36.3.2.2 SIP Shim . 60g36.3.2.2.1 SIP Shim data 60g36.3.2.2.2 SIP shim behaviour 60g36.3.2.2.3 Generating NOTIFY messages 62g36.3.3 GOCAP slave 63g36.3.3.1 SIP Listener . 63g36.3.3.1.1 SIP Session initiation . 64g36.3.3.1.2 Session termination . 65g36.3.3.1.3 Gocap commands 65g36.3.3.2 SIP Session

20、Handler 65g3Annex A (normative): ASN.1 data types and signal definitions . 67g3A.1 ASN.1 definitions . 67g3A.2 Signals 69g3A.3 SDL description 70g3Annex B (normative): Congestion_Control event package 71g3B.1 Event Package Name 71g3ETSI ETSI ES 283 039-2 V3.1.1 (2010-01)5B.2 Event Package Parameters

21、 71g3B.3 SUBSCRIBE Bodies 71g3B.4 Subscription Duration. 71g3B.5 NOTIFY Bodies . 71g3B.6 Notifier Processing of SUBSCRIBE Requests. 71g3B.7 Notifier Generation of NOTIFY Requests . 71g3B.8 Subscriber Processing of NOTIFY Requests . 72g3B.9 Subscriber Generation of SUBSCRIBE Requests 72g3B.10 Handlin

22、g of Forked Requests . 72g3B.11 Rate of Notifications 72g3B.12 State Agents 72g3B.13 Use of URIs to Retrieve State 72g3Annex C (normative): XML Schema 73g3C.1 Introduction 73g3C.2 XML Schema specification 73g3Annex D (informative): Generating System_state data 77g3D.1 Introduction 77g3D.2 Background

23、 77g3D.3 Modelling CPU load . 78g3D.4 Single processing system 79g3D.4.1 Arrival rate and Goal rate . 79g3D.4.2 Scheduling the update 80g3D.4.3 Updating the arrival rate . 80g3D.4.4 Updating the goal rate 80g3D.4.5 Variables. 82g3D.4.6 Initialisation 82g3D.4.7 Configurable Parameters 83g3D.5 Multipl

24、e processing subsystems . 83g3D.5.1 Scheduling the update 85g3D.5.2 Updating the arrival rate . 85g3D.5.3 Updating the goal rate 85g3D.5.4 Special design considerations . 86g3D.5.4.1 AS unavailability 86g3D.5.4.2 Late or missing updates 86g3Annex E (informative): Message Sequence Charts (Transport I

25、ndependent) 87g3E.1 Adding sources . 87g3E.1.1 Overview 87g3E.1.2 Data flows for addition of a source 89g3E.2 Deleting sources . 91g3E.3 Overload onset and abatement . 92g3E.3.1 Overview of overload onset and abatement . 92g3E.3.2 Detailed view of data flows in overload . 94g3E.4 Audit . 95g3E.5 Swi

26、tching to local restriction 96g3ETSI ETSI ES 283 039-2 V3.1.1 (2010-01)6Annex F (informative): Adaptation behaviour discussion 99g3F.1 Adaptation algorithm behaviour . 99g3F.2 Adaptation and control termination 102g3F.3 Capacity Modification Factor . 103g3Annex G (informative): Bibliography . 104g3H

27、istory 105g3ETSI ETSI ES 283 039-2 V3.1.1 (2010-01)7Intellectual 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

28、 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 (http:/webapp.etsi.org/IPR/home.asp). Pursua

29、nt 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 docum

30、ent. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 2 of a multi-part deliverable covering NGN Overload and Congestion Control as identified

31、 below: Part 1: “Overview“; Part 2: “Core GOCAP and NOCA Entity Behaviours“; Part 3: “Overload and Congestion Control for H.248 MG/MGC“; Part 4: “Adaptative Control for the MGC“; Part 5: “ISDN overload control at the Access Gateway“. ETSI ETSI ES 283 039-2 V3.1.1 (2010-01)81 Scope The present docume

32、nt describes the core features of the NGN Overload Control Architecture (NOCA) and the Generic Overload Control Application Protocol (GOCAP). While it is usual for the architectural components to be specified separately from the protocols that are used to communicate between them, the performance re

33、quirements of overload controls are such that the coupling between architecture, protocol and implementation is very strong. This means that the present document specifies the architecture, entity behaviours and protocol for the core NOCA/GOCAP together. The way GOCAP and the NOCA entities are deplo

34、yed to control traffic that uses a specific application protocol is profiled via additional small shim specifications. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisio

35、ns do not apply. Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative reference

36、s. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative refe

37、rences The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. 1 ETSI TS 182 018: “Telecommun

38、ications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Control of Processing Overload; Stage 2 Requirements“. 2 IETF RFC 3588: “Diameter Base Protocol“. 3 IETF RFC 4005: “Diameter Network Access Server Application“. 4 ETSI TS 133 210: “Digital cellular telecommunica

39、tions system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; 3G security; Network Domain Security (NDS); IP network layer security (3GPP TS 33.210)“. 5 ETSI TS 129 329: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE;

40、 Sh interface based on the Diameter protocol; Protocol details (3GPP TS 29.329 version 8.4.0 Release 8)“. 6 IETF RFC 3265: “Session Initiation Protocol (SIP)-Specific Event Notification“. ETSI ETSI ES 283 039-2 V3.1.1 (2010-01)92.2 Informative references The following referenced documents are not es

41、sential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. i.1 ETSI ES 283 039-4: “Telecommunications and Internet converged Services and

42、Protocols for Advanced Networking (TISPAN); NGN Overload Control Architecture; Part 4: Adaptative Control for the MGC“. i.2 IETF RFC 4662: “A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the pr

43、esent document, the terms and definitions given in TS 182 018 1 and the following apply: application: software component(s) running on a system to provide service to end users or support the management of the system NOTE: In the present document the term application excludes those software component

44、s that implement the NOCA. application protocol: protocol used to enable application instances to communicate control variable: time-varying parameter used to control actuators in a feedback loop, calculated on the basis of the target and measured values of some system quantity feedback loop: contro

45、l mechanism where the result of changing an actuator is used (“fed back“) into the algorithm used to calculate future changes load control: mechanism for controlling the workload of a system overload: system workload exceeds a defined threshold of the processing capacity of that system source: syste

46、m that generates workload for another system target: system that receives workload from another system workload: amount of processing work a system has to perform 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AAA AA-Answer API Application Programming

47、Interface ASA Abort-Session-Answer ASR Abort-Session-RequestAVP Attribute-Value Pair CA Control AdaptorCD Control Distribution CDR CDRestriction CEA Capabilities-Exchange-Answer CER Capabilities-Exchange-Request CM Channel Manager FQDN Fully Qualified Domain Name GOCAP Generic Overload Control Appli

48、cation Protocol ETSI ETSI ES 283 039-2 V3.1.1 (2010-01)10IP Internet Protocol ISUP Integrated Service Digital Network User Part NGN Next Generation Network NOCA NGN Overload Control Architecture PUA Profile-Update-Answer PUR Profile-Update-RequestRM Restrictor Manager SCTP Stream Control Transmissio

49、n Protocol SDL Specification and Description Language SIP Session Initiation Protocol SLA Service Level Agreement STA Session-Termination-AnswerSTR Session-Termination-Request TCP Transmission Control Protocol4 Control Architecture 4.1 Description of NOCA Components Figure 1: Control components implementing a feedback control path The NGN Overload Control Architecture (NOCA) aims to provide feedback based processing load control for hosts that implement the functionality of NGN (and other) networks. Each feedback control loop indicated by the ovals in Fi