9 * In describing the role of the CMTS network element, it is important to
10 * consider the relation among DOCSIS, PacketCable 1.x and PacketCable
11 * Multimedia functionality. While each of these suites of specifications
12 * addresses a specific set of functional requirements, each has also been
13 * defined in such a way that corresponding implementations may be constructed
14 * in a modular manner; either PacketCable 1.x or PacketCable Multimedia Gate
15 * Control may be layered on top of a DOCSIS 1.1 or greater CMTS foundation,
16 * with the option of adding additional, complementary functionality as business
17 * indicates. Further, it should be emphasized that it is a significant asset of
18 * the PacketCable architecture that both telephony and Multimedia variants
19 * employ considerable architectural similarity, leading to potential reuse in
20 * the underlying Gate management models.
23 * The PacketCable Multimedia CMTS is a generalized version of the PacketCable
24 * 1.x CMTS that has been defined in order to deliver telephony services in
25 * PacketCable 1.x networks. The CMTS is responsible for fulfilling requests for
26 * QoS that are received from one or more Policy Servers. It performs this
27 * function by installing Gates, which are similar to the Gates defined in [14];
28 * Gates allow the subscriber's cable modem to request network resources from
29 * the CMTS through the creation of dynamic DOCSIS flows with guaranteed levels
30 * of QoS. The CMTS also sends Event Messages detailing actual usage of QoS
31 * resources to the Record Keeping Server.
34 * The CMTS acts as a server (PS should send OPN message to CMTS to initiate
35 * communication), and acts as a client for the rest of the exchange process.
40 public interface ICMTS extends IPCMMServer {
42 // generates a GateID and assigns it to the IPCMMGate.
44 static final short DEFAULT_R_TYPE = (short) 0x08;
45 static final short DEFAULT_M_TYPE = (short) 0;