How does the DOCSIS 1.0+ architecture work?
A. Let’s take an example where subscriber Mr. X has joined your service and wants the following service package: • One data service with peak upstream (US) rate 128 kBps, peak digital signal (DS) rate 2 Mbps • Two virtual phone lines Here are the steps to follow: • The provisioning system prepares a configuration file for the ITCM subscriber using any off-the-shelf DOCSIS 1.0 style configuration file editor. The configuration file contains: • A regular DOCSIS 1.0 style Class of Service setting for the data service with US rate 128 kBps, peak DS rate 2 Mbps. • A vendor-specific encoding called “number of phone lines”, set to 2. • A vendor-specific encoding called “per IP precedence rate limit tuple”, which sets downstream rate limits for IP packets of special precedence. • The ITCM downloads this configuration file at the time of registration, and sends the provisioning information to the DOCSIS 1.0+ CMTS. • When CMTS receives the registration request (REG-REQ), it creates a local datab