4 === PacketCable PCMM ===
6 Develop a PacketCable PCMM/COPS southbound plugin and supporting modules to allow the OpenDayLight controller to provision CMTS as a network element that manages service flows with dynamic QoS.
14 Packet Cable MultiMedia (PCMM) provides an interface to control and management service flow for CMTS network elements. A service flows constitute a DOCSIS data path between a CMTS and a subscriber's cable modem (CM) guaranteed application specific quality of service (QoS), known as Dynamic Quality of Service (DQoS). PCMM offers (MSOs) the ability to deliver new services using existing cable infrastructure. MSOs have already begun to apply PCMM technology for expanding their multimedia service offerings.
15 The PCMM architecture comprises the following components:
17 * The Application Manager, which specifies QoS requirements to the Policy Server on a per-application basis.
18 * The Policy Server, which allocates network resources per subscriber and per application, ensuring that consumption meets MSO priorities.
19 * The Cable Modem Termination System (CMTS), which enforces policies according to bandwidth capacity.
20 * The Cable Modem, which resides on the client side and connects the client's network to the cable system.
22 PacketCable Multimedia defines a service delivery framework that provides general-purpose QoS, event-based accounting, and security functionality founded upon the mechanisms defined in PacketCable 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 generalized for the present purposes. Telephony-specific requirements and interfaces (e.g., call signaling, PSTN interconnection and electronic surveillance) are not part of PacketCable Multimedia, while core functionality such as QoS resource management mechanisms, has been enhanced. Throughout this process, one of the primary objectives of this work has been to leverage and reuse as much of the existing body of PacketCable 1.x investment, knowledge base, and technical functionality as possible. Key features of the described Multimedia service delivery framework include:
24 * Simple, powerful access to DOCSIS QoS mechanisms supporting both time and volume-based network resource authorizations,
25 * Abstract, event-based network resource auditing and management mechanisms,
26 * A robust security infrastructure that provides integrity and appropriate levels of protection across all interfaces.
28 The goal of this project is to utilizes the OpenDayLight controller platform as for the Application Manager and parts of the Policy Server and leverage the as many existing components offered by the platform.
30 The initial southbound transport has been written to the following version of the specification:
31 http://www.cablelabs.com/wp-content/uploads/specdocs/PKT-SP-MM-I05-091029.pdf
35 * Provision a CMTS and an associated Cable Modem to form a Subscriber service for which (service) flows can be established and metered.
36 * Flow Programmer match-only for managing DOCSIS (service) flows
37 * Northbound APIs for provisioning CMTS network elements
38 ** HTML Provisioning Interface
39 * Northbound APIs for provisioning Service Flow values and types
40 * Northbound APIs for provisioning QoS (or metering) parameters
41 * SAL extensions for DOCSIS specific data model and configuration APIs
42 * Southbound PCMM/COPS transport plugin
46 ==== DOCSIS SDN Application Logic ====
48 This component is introduced at the Network Applications Orchestrations and Services layer. The component is proposed as an application responsible for the workflow logic that represents the use cases of interest: L2VPN, Buffer Management, Service Flow QoS Management, and general configuration automation.
50 ==== Flow Programmer ====
52 This standard components exists at the Controller Platform layer and is responsible for programming flows at network elements that register support for flow management. It adheres to this [https://jenkins.opendaylight.org/controller/job/controller-merge/ws/opendaylight/northbound/flowprogrammer/target/site/wsdocs/resource_FlowProgrammerNorthbound.html FlowProgrammer Restful API].
54 ==== PacketCable Manager ====
56 This component is introduced at the Controller Platform layer. This component manages the PCMM/DOCSIS specific attributes that are applied to an existing Service Flow, configuration, and addition and removal of CMTS elements. It should export a PacketCable Manager RESTful API as part of ODL architecture.
60 This component is introduced at the Southbound Interfaces & Protocol Plugins layer. This component is responsible for the PCMM/COPS/PDP functionality required to service requests from PacketCable Manager and FlowManager. Requests are transposed into PCMM Gate Control messages and transmitted via COPS to the CMTS. This plugin adheres to the PCMM/COPS/PDP functionality defined in the [http://www.cablelabs.com/wp-content/uploads/specdocs/PKT-SP-MM-I06-110629.pdf CableLabs specification].
62 == Information and Data Models ==
64 ==== CCAP and DOCSIS 3.1 CMTS YANG Model Support ====
66 Since both devices optionally support the NETCONF protocol, these cable devices also ''optionally'' support YANG data models which are translated into mandatory supported XML Schema data models. The OpenDaylight framework also uses YANG models for their data model representation and tooling.
68 ==== CCAP PCMM Configuration Management Information Model ====
70 The CableLabs CCAP specification defines a UML Class Diagram Information Model for configuration management of PCMM in the CCAP device. This is represented in the figure below.
72 [[Image:PKT-CFG Class Diagram.png]]
74 The above Information Model is translated into the YANG configuration management data module and corresponding XML Schema. Therefore, these objects and attributes can be provisioned via XML configuration files and ''optionally'', if supported, via NETCONF messaging.
77 ==== Openflow Match Action and PCMM Service Flow Comparison ====
79 ===== Openflow Match =====
85 | dlDst (MAC address)||no
87 | dlSrc (MAC address)||no
97 | nwProto (TCP or UDP protocol)||yes
105 | nwDst (Dest IP Address)||yes
109 | nwSrc (Src IP Address)||yes
113 | tpSrc (Source Port)||sourcePortStart
117 | tpDst (Destiation Port)||sourcePortStart
123 | idleTimeout||Timeout active QoS parameters
129 | ||IPv6: Next Header Type, Flow Label, Flags,
134 ===== Openflow Action =====
167 | setVlan||In L2VPN, but not in PCMM
196 ==== PCMM COPS Information Model ====
198 The [http://www.cablelabs.com/specifications/PKT-SP-MM-I06-110629.pdf CableLabs PCMM Specification] defines the COPS PDP to PEP interface via a message set and set of object definitions. The objects carried in the COPS message set can be viewed as the PCMM COPS Information Model for the PCMM COPS interface between the Policy Manager and CMTS. The objects are represented in the table below.
206 | | Transaction Identifier used by the Policy Server to match responses from the CMTS to the previous requests.
210 | | Application Manager ID including the Application Manager Tag (Application responsible for handling the session) and Application Type (Type of application this gate is associated with).
214 | | IPv4 or IPv6 address of the Subscriber for the service request (i.e., CM or CPE of Subscriber)
218 | | Gate Identifier referenced in the command message or referenced by the CMTS for a response message.
223 Defines the following attributes:
231 ** Defines the proper admission control policy or parameters to be applied for this gate. Attributes include:
236 ** Used to identify particular bits within the IPv4 DSCP/TOS byte
238 ** Used in conjunction with the DSCP/TOS Overwrite
243 ** Timers defined per Gate Transition Diagram
247 | | Classifier, Extended Classifier or IPv6 Classifier
255 * Source IPv4 Address
256 * Destination IPv4 Address
262 | | Extended Classifier
267 * IPv4 Source Address
269 * IPv4 Destination Address
270 * IPv4 Destination Mask
273 * Destination Port Start
274 * Destination Port End
289 * Source Prefix Length
290 * Destination Prefix Length
291 * IPv6 Source Address
292 * IPv6 Destination Address
295 * Destination Port Start
296 * Destination Port End
304 | | FlowSpec, DOCSIS Service Class Name, DOCSIS-specific parameters or Upstream Drop
311 * Authorized Envelope
312 ** Token Bucket Rate (r)
313 ** Token Bucket Size (b)
314 ** Peak Data Rate (p)
315 ** Minimum Policed Unit (m)
316 ** Maximum Packet Size (M)
319 * ''Optional'' Reserved Envelope
320 * ''Optional'' Committed Envelope
323 | | DOCSIS Service Class Name
329 | | Best Effort Service
332 * Authorized Envelope
334 ** Request Transmission Policy
335 ** Maximum Sustained Traffic Rate
336 ** Maximum Traffic Burst
337 ** Minimum Reserved Traffic Rate
338 ** Assumed Minimum Reserved Traffic Rate Packet Size
339 ** Maximum Concatenated Burst
340 ** Upstream Peak Traffic Rate
341 ** Required Attribute Mask
342 ** Forbidden Attribute Mask
343 ** Attribute Aggregation Rule Mask
347 * ''Optional'' Reserved Envelope
348 * ''Optional'' Committed Envelope
351 | | Non-Real-Time Polling Service
354 * Authorized Envelope
356 ** Request Transmission Policy
357 ** Maximum Sustained Traffic Rate
358 ** Maximum Traffic Burst
359 ** Minimum Reserved Traffic Rate
360 ** Assumed Minimum Reserved Traffic Rate Packet Size
361 ** Maximum Concatenated Burst
362 ** Nominal Polling Interval
363 ** Upstream Peak Traffic Rate
364 ** Required Attribute Mask
365 ** Forbidden Attribute Mask
366 ** Attribute Aggregation Rule Mask
370 * ''Optional'' Reserved Envelope
371 * ''Optional'' Committed Envelope
374 | | Real-Time Polling Service
377 * Authorized Envelope
378 ** Request Transmission Policy
379 ** Maximum Sustained Traffic Rate
380 ** Maximum Traffic Burst
381 ** Minimum Reserved Traffic Rate
382 ** Assumed Minimum Reserved Traffic Rate Packet Size
383 ** Maximum Concatenated Burst
384 ** Nominal Polling Interval
385 ** Tolerated Poll Jitter
386 ** Upstream Peak Traffic Rate
387 ** Required Attribute Mask
388 ** Forbidden Attribute Mask
389 ** Attribute Aggregation Rule Mask
393 * ''Optional'' Reserved Envelope
394 * ''Optional'' Committed Envelope
397 | | Unsolicited Grant Service
400 * Authorized Envelope
401 ** Request Transmission Policy
402 ** Unsolicited Grant Size
404 ** Nominal Grant Interval
405 ** Tolerated Grant Interval
406 ** Upstream Peak Traffic Rate
407 ** Required Attribute Mask
408 ** Forbidden Attribute Mask
409 ** Attribute Aggregation Rule Mask
413 * ''Optional'' Reserved Envelope
414 * ''Optional'' Committed Envelope
417 | | Unsolicited Grant Service with Activity Detection
420 * Authorized Envelope
421 ** Request Transmission Policy
422 ** Unsolicited Grant Size
424 ** Nominal Grant Interval
425 ** Tolerated Grant Jitter
426 ** Nominal Polling Interval
427 ** Tolerated Poll Jitter
428 ** Upstream Peak Traffic Rate
429 ** Required Attribute Mask
430 ** Forbidden Attribute Mask
431 ** Attribute Aggregation Rule Mask
435 * ''Optional'' Reserved Envelope
436 * ''Optional'' Committed Envelope
439 | | Downstream Service
442 * Authorized Envelope
444 ** Downstream Resequencing
445 ** <Maximum Sustained Traffic Rate
446 ** Maximum Traffic Burst
447 ** Minimum Reserved Traffic Rate
448 ** Assumed Minimum Reserved Traffic Rate Packet Size
449 ** Maximum Downstream Latency
450 ** Downstream Peak Traffic Rate
451 ** Required Attribute Mask
452 ** Forbidden Attribute Mask
453 ** Attribute Aggregation Rule Mask
457 * ''Optional'' Reserved Envelope
458 * ''Optional'' Committed Envelope
466 | | IPv4 Event Generation Info
468 * Primary Record Keeping Server IPv4 Address
469 * Primary Record Keeping Server Port
470 * Secondary Record Keeping Server IPv4 Address
471 * Secondary Record Keeping Server Port
472 * Billing Correlation ID
475 | | IPv6 Event Generation Info
477 * Primary Record Keeping Server IPv6 Address
478 * Primary Record Keeping Server Port
479 * Secondary Record Keeping Server IPv6 Address
480 * Secondary Record Keeping Server Port
481 * Billing Correlation ID
484 | | Volume-Based Usage Limit
489 | | Time-Based Usage Limit
497 ** Information the Policy Server or Application Manager might store on a CMTS.
502 * Time Committed (Sec)
507 * Octet Count (bytes)
510 | | PacketCable Error
513 ** Pre-defined error code
524 * Major Version Number
525 * Minor Version Number
530 * PSID which uniquely identifies the Policy Server
546 * UserID which identifies the user associated with the gate
551 * SharedResourceID is assigned by the CMTS for Multicast Gate requests.
556 == Resources Committed (developers committed to working) ==
558 * [mailto:xsited@yahoo.com Thomas Kee irc:xsited]
559 * [mailto:user@example.com Example irc:]
561 == Initial Committers ==
563 * [mailto:xsited@yahoo.com Thomas Kee irc:xsited]
564 * [mailto:user@example.com Example irc:]
568 * No vendor package names in code
569 * No vendor branding / trademark present in code or output of build
570 * No vendor branding / trademark present in documentation
572 == Meets Board Policy (including IPR) ==