Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : LAST MILE TECHNOLOGIES - Let's Discuss Them Here -- Ignore unavailable to you. Want to Upgrade?

To: Kenneth E. De Paul who wrote (5698)	10/29/1999 4:26:00 PM
From: DenverTechie	Read Replies (2) \| Respond to of 12823

Ken, the CMTS plays several roles related toQoS in an IP cable telephony system. You would have to ask about this, right? Not a simple area by any means, but I'll take a shot at it. And you are correct, there are direct connections to the CableLabs OpenCable/PacketCable initiatives. Please excuse if I can't talk about the proprietary stuff here and just provide generalities. But trust me, next time you might not want to know. Well, here goes. Wish me luck. Between the BHI (Broadband Home Interface) and the CMTS, PacketCable PQOS (Provisioned QoS) can be used. This provides for the reservation and activation of bandwidth on a per call basis. It also ensures a low latency "constant-bit-rate-like" service. It is the BHI that actually controls the QoS in this part of the network, using a packetization algorithm that is synchronized with the IP frame synch rate. The CMTS also performs a "policing" function by checking a software setting according to the user profile as the call is established. For security: DQoS (Dynamic Quality of Service)is employed using a Gate implemented in the CMTS as recommended in the CableLabs Dynamic Quality of Service Specification. This ensures that only those sessions authorized by a "call server" receive high quality service. The "call server" performs the function of a gate controller and will use an IPSec secure protocol to communicate with the Gate/CMTS to open enhanced QoS flows for individual calls. Then there are "policy servers" behind firewalls to ensure that the "call servers" are accessed only for the services they are meant to deliver. But in actuality, the primary controllers of QoS are various servers, agents, gateways and network element managers. Quality of Service in this type of network is established more on a logical basis than on a hardware or "box" basis. As an example, one set of servers contain code across various parts of the network that comprises a "Quality of Service Manager" which resides strictly in software. It allows the setup, configuration and management of different QoS levels based on user profiles. It enables configuration of IP QoS traffic filters associated with predefined service flows. There is of course much more, but you get the idea and flavor of how it works from this I hope. Tried to keep it simple.....failed.