ETSI TS 102 879-2010 Access Terminals Transmission and Multiplexing (ATTM) IPCablecom Services for delivering multimedia and voice over DOCSIS network infrastructure (V1 1 1)《接入 终端_1.pdf

1、 ETSI TS 102 879 V1.1.1 (2010-06)Technical Specification Access, Terminals, Transmission and Multiplexing (ATTM);IPCablecom Services for delivering multimedia and voiceover DOCSIS network infrastructureETSI ETSI TS 102 879 V1.1.1 (2010-06)2Reference DTS/ATTM-003007 Keywords cable, IPCable, PSTN ETSI

2、 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 Individual copies of the present document can be do

3、wnloaded 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 Document Format (PDF). In case of dispute, the refere

4、nce 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 current status of this and other ETSI documents i

5、s 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 reproduced except as authorized by written permission

6、. 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 ETSI registered for the benefit of its Members. 3G

7、PPTM 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 GSM logo are Trade Marks registered and owned by

8、the GSM Association. ETSI ETSI TS 102 879 V1.1.1 (2010-06)3Contents Intellectual Property Rights 7g3Foreword . 7g31 Scope 8g31.1 Purpose . 8g31.2 Relation to IPCablecom 1.x 8g32 References 9g32.1 Normative references . 10g32.2 Informative references 10g33 Definitions and abbreviations . 11g33.1 Defi

9、nitions 11g33.2 Abbreviations . 11g34 Void 13g35 Technical Overview . 13g35.1 QoS Background 13g35.1.1 DOCSIS QoS Summary 13g35.1.1.1 DOCSIS 3.0 Multicast QoS Framework . 15g35.1.2 IPCablecom 1.x QoS Summary 15g35.2 Architecture 16g35.2.1 Client Types 17g35.2.2 IPCablecom Multimedia Devices . 17g35.

10、2.2.1 Application Server (AS) 19g35.2.2.2 Application Manager (AM) . 19g35.2.2.3 Policy Server (PS) . 19g35.2.2.3.1 Stateful and Stateless Policy Servers . 20g35.2.2.3.2 Modification of Requests and Responses by Policy Servers . 21g35.2.2.4 Cable Modem Termination System (CMTS) 21g35.2.2.5 Record Ke

11、eping Server (RKS) 21g35.2.3 IPCablecom Multimedia Interfaces 21g35.2.3.1 Client and Application Manager Interface (mm-7) . 23g35.2.3.2 Application Manager and Policy Server Interface (pkt-mm-3) . 23g35.2.3.3 Policy Server and CMTS Interface (pkt-mm-2) 23g35.2.3.4 Record Keeping Server and Policy Se

12、rver Interface (pkt-mm-4) and Record Keeping Server and CMTS Interface (pkt-mm-5) . 24g35.2.3.5 Client and Application Server Interface (mm-12) . 24g35.2.3.6 Application Server and Application Manager Interface (pkt-mm-11) 24g35.2.4 State Information 24g35.2.4.1 Application State . 24g35.2.4.2 QoS R

13、esource State . 25g36 Authorization Interface Description . 25g36.1 Gates: The Framework for QoS Control 25g36.1.1 Gate Identification (GateID) . 27g36.1.2 Application Manager Identification (AMID) 27g36.1.3 Subscriber Identification (SubscriberID) 28g36.1.4 Gate Specification (GateSpec) 28g36.1.5 C

14、lassifier . 29g36.1.6 Traffic Profile . 31g36.1.6.1 FlowSpec . 32g36.1.6.2 DOCSIS Service Class Name . 32g36.1.6.3 DOCSIS Specific Parameterization 32g36.1.6.4 Upstream Drop 33g36.1.7 Event Generation Info . 33g36.1.8 Time-Based Usage Limit 33g36.1.9 Volume-Based Usage Limit 33g3ETSI ETSI TS 102 879

15、 V1.1.1 (2010-06)46.1.10 Opaque Data . 33g36.1.11 Gate Time Info 33g36.1.12 Gate Usage Info 33g36.1.13 User Identification (UserID) . 34g36.1.14 Shared Resource Identification (SharedResourceID) . 34g36.2 Gate Transitions . 34g36.2.1 Authorized 35g36.2.2 Reserved . 36g36.2.3 Committed 37g36.2.4 Comm

16、itted-Recovery 38g36.3 COPS Profile for IPCablecom Multimedia 39g36.4 Gate Control Protocol Message Formats 41g36.4.1 COPS Common Message Format . 41g36.4.2 Additional COPS Objects for Gate Control 42g36.4.2.1 TransactionID 43g36.4.2.2 AMID 44g36.4.2.3 SubscriberID . 44g36.4.2.4 GateID . 44g36.4.2.5

17、 GateSpec . 45g36.4.2.6 Classifiers 46g36.4.2.7 Traffic Profiles 50g36.4.2.7.1 Flow Spec 50g36.4.2.7.2 DOCSIS Service Class Name 51g36.4.2.7.3 Best Effort Service 52g36.4.2.7.4 Non-Real-Time Polling Service 53g36.4.2.7.5 Real-Time Polling Service. 54g36.4.2.7.6 Unsolicited Grant Service 56g36.4.2.7.

18、7 Unsolicited Grant Service with Activity Detection . 57g36.4.2.7.8 Downstream Service 59g36.4.2.7.9 Upstream Drop 60g36.4.2.8 Event Generation Info . 61g36.4.2.9 Volume-Based Usage Limit 62g36.4.2.10 Time-Based Usage Limit 62g36.4.2.11 Opaque Data 63g36.4.2.12 Gate Time Info 63g36.4.2.13 Gate Usage

19、 Info 63g36.4.2.14 IPCablecom Error . 64g36.4.2.15 Gate State 65g36.4.2.16 Version Info 66g36.4.2.17 PSID 66g36.4.2.18 Synch Options . 66g36.4.2.19 Msg Receipt Key. 67g36.4.2.20 UserID . 67g36.4.2.21 SharedResourceID . 67g36.4.3 Gate Control Messages . 67g36.4.3.1 Profile for Application Manager to

20、Policy Server Interface 68g36.4.3.2 Profile for Policy Server to CMTS Interface . 69g36.5 Gate Control Protocol Operation 70g36.5.1 Initialization Sequence 70g36.5.2 Operation Sequence 71g36.5.3 Procedures for Validating Resource Envelopes 72g36.5.3.1 Flow Spec 73g36.5.3.2 DOCSIS Service Class Name

21、. 73g36.5.3.3 DOCSIS Service Flow Parameters 73g36.5.3.3.1 Upstream Encodings 73g36.5.3.3.2 Downstream Encodings. 74g36.5.3.4 Upstream Drop 74g36.5.4 Procedures for Authorizing Resources through a Gate . 74g36.5.4.1 Procedures for Authorizing Multicast Gates . 75g36.5.5 Procedures for Querying a Gat

22、e 76g36.5.6 Procedures for Modifying a Gate 76g36.5.6.1 Procedures for Modification of Multicast Gates . 77g3ETSI ETSI TS 102 879 V1.1.1 (2010-06)56.5.7 Procedures for Supporting Usage Limits 77g36.5.7.1 Procedures For Supporting Volume-Based Usage Limits . 78g36.5.7.2 Procedures For Supporting Time

23、-Based Usage Limits . 78g36.5.7.3 Resource and Error Recovery . 78g36.5.7.4 Tracking Time-Based and Volume-Based Usage Limits 79g36.5.8 Procedures for Deleting a Gate . 79g36.5.8.1 Procedures for Deleting Multicast Gates . 79g36.5.9 Procedure for Committing a Gate . 80g36.5.9.1 Procedure for Committ

24、ing a Multicast Gate . 80g36.5.10 Termination Sequence 80g36.5.11 Procedures for Multiple Grants Per Interval . 80g36.5.12 Procedures for Identifying a PDP to a PEP . 81g36.5.13 Procedures for Delivering Gate-Report-State Messages . 82g36.5.14 Procedures for Gate Control Operations Initiated by a Po

25、licy Server 82g36.5.15 Procedures for State Synchronization . 82g36.5.15.1 Initiating State Synchronization 83g36.5.15.2 Full Synchronization . 83g36.5.15.3 Incremental Synchronization. 83g36.5.15.4 Reporting Gate State Information . 84g36.5.15.5 Completing the Synchronization . 84g36.5.15.6 Relayin

26、g Out of Sync Data . 85g36.5.15.7 Synchronization with Stateless Policy Servers 85g36.5.16 Procedures for Confirming PDP Receipt of Messages . 85g36.5.17 Procedures for Indicating Updated or Lost Shared Resource . 86g37 Event Messaging Interface Description 86g37.1 Introduction 86g37.2 Record Keepin

27、g Server Requirements . 88g37.3 General IPCablecom Multimedia Network Element Requirements . 88g37.3.1 Element ID 88g37.3.2 Timing 88g37.3.3 Primary and Secondary RKS Considerations . 88g37.3.4 Interaction with IPCablecom RKS 89g37.4 Event Messages for IPCablecom Multimedia 89g37.4.1 Policy Events 8

28、9g37.4.1.1 Policy_Request 90g37.4.1.2 Policy_Delete 90g37.4.1.3 Policy_Update . 91g37.4.2 QoS Events . 92g37.4.2.1 QoS_Reserve . 92g37.4.2.2 QoS_Commit 92g37.4.2.3 QoS_Release . 93g37.4.3 Time_Change 93g37.5 Event Messaging Attributes for IPCablecom Multimedia 94g37.5.1 EM_Header Attribute Structure

29、 96g37.5.2 Billing Correlation ID (BCID) Field Structure . 97g37.5.3 Status Field Structure 98g37.5.4 QoS Descriptor Attribute Structure 99g37.6 RADIUS Accounting Protocol . 99g37.6.1 Authentication and Confidentiality . 100g37.6.2 Standard RADIUS Attributes . 100g37.6.3 IPCablecom RADIUS Accounting

30、-Request Packet Syntax 101g38 Security Requirements . 101g38.1 CMTS - CM QoS Interface (pkt-mm-1) . 102g38.2 Policy Server - CMTS COPS Interface (pkt-mm-2) . 102g38.3 Application Manager - Policy Server COPS Interface (pkt-mm-3) 102g38.4 Policy Server - RKS Event Message Interface (pkt-mm-4) . 103g3

31、8.5 CMTS - RKS Event Message Interface (pkt-mm-5) 103g39 Mapping a FlowSpec Traffic Profile to DOCSIS . 103g39.1 Mapping FlowSpecs to DOCSIS Scheduling Types 103g39.2 Mapping FlowSpecs to DOCSIS Traffic Parameters . 104g3ETSI ETSI TS 102 879 V1.1.1 (2010-06)69.3 DOCSIS Upstream Parameters . 106g39.3

32、.1 Unsolicited Grant Scheduling (UGS) . 107g39.3.2 Real-Time Polling Scheduling 107g39.3.3 Best Effort Scheduling 108g39.3.4 Upstream Packet Classification Encodings . 108g39.3.4.1 DOCSIS Upstream Packet Classification Requests 108g39.4 DOCSIS Downstream Parameters 109g39.4.1 Downstream QoS Encoding

33、s for Guaranteed Service 109g39.4.2 Downstream QoS Encodings for Controlled Load Service 110g39.4.3 Downstream Packet Classification Encodings 111g39.4.3.1 DOCSIS Downstream Packet Classification Requests . 111g310 Message Flows . 112g310.1 Basic Message Sequence 112g310.2 Detailed Message Sequence

34、. 114g3Annex A (informative): Guidelines for Version Number Assignment . 132g3Annex B (informative): Bibliography . 134g3History 135g3ETSI ETSI TS 102 879 V1.1.1 (2010-06)7Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The

35、 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 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available fro

36、m the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). 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 ETS

37、I 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 Specification (TS) has been produced by ETSI Technical Committee Access, Terminals, Transmission and Multiplexing (ATTM). ETSI ETSI TS 102 879 V1.1.1 (

38、2010-06)81 Scope The present document specifies IPCablecom, (also referred to as PacketCable) multimedia services over DOCSIS. 1.1 Purpose The intent of the present document is to support the deployment of general Multimedia services by providing a technical definition of several IP-based signalling

39、 interfaces that leverage core QoS and policy management capabilities native to DOCSIS Versions 1.1 and greater. Throughout the present document, the term DOCSIS will be used to refer to any DOCSIS version greater than or equal to 1.1. For the purposes of the present document, Multimedia services ma

40、y be defined as IP-based services (e.g. online gaming, video-conferencing, streaming media, etc.) requiring QoS-based network resources (as contrasted with services such as web browsing, e-mail, instant messaging and file-sharing that are commonly provided using best-effort flows). While telephony o

41、r voice-based services are not specifically excluded from this definition, the IPCablecom 1.x set of specifications provide coverage specific to this type of service delivery, and, therefore, those specifications should be consulted as appropriate. IPCablecom Multimedia defines a service delivery fr

42、amework that provides general-purpose QoS, event-based accounting, and security functionality founded upon the mechanisms defined in IPCablecom 1.x. However, due to the broader spectrum of applications and services addressed by this initiative, each of these functional areas has been revisited and g

43、eneralized for the present purposes. Telephony-specific requirements and interfaces (e.g. call signalling, PSTN interconnection and electronic surveillance) are not part of IPCablecom Multimedia, while core functionality such as QoS resource management mechanisms, has been enhanced. Throughout this

44、process, one of the primary objectives of this work has been to leverage and reuse as much of the existing body of IPCablecom 1.x investment, knowledge base, and technical functionality as possible. Key features of the described Multimedia service delivery framework include: Simple, powerful access

45、to DOCSIS QoS mechanisms supporting both time and volume-based network resource authorizations. Abstract, event-based network resource auditing and management mechanisms. A robust security infrastructure that provides integrity and appropriate levels of protection across all interfaces. As outlined

46、in the technical report 15, the current scope of the present document is limited to network-based QoS resource management and usage auditing capabilities. This approach was motivated by several criteria, including rapid time-to-market for QoS-enhanced Multimedia services (which may take the form of

47、new applications or existing applications retrofitted per the present document), the absence of QoS signalling requirements on CPE devices, and security assurances provided by an absence of client-based QoS signalling. In addition, the QoS signalling mechanisms outlined herein provide the foundation

48、 for client-based QoS signalling mechanisms which may be defined in the future. As such scenarios have already been considered and documented in the technical report, one of the secondary goals of the present document is to provide for smooth migration to a client-based model as market and technolog

49、y advances dictate. It should also be noted that the scope of the QoS framework defined in the present document is limited to the access network and that the choice of specific backbone QoS strategies is left as an administrative decision to be addressed by each service provider as it deems best. 1.2 Relation to IPCablecom 1.x Since its inception the IPCablecom initiative has been positioned as an IP-based Multimedia service deployment infrastructure, exploiting and enhancing the underlying QoS capabilities of the DOCSIS access network. Based on market demand and techn