What is PacketCable and Its Key Components

PacketCable is a set of specifications for a broadband network architecture that enables the delivery of multimedia services over IP networks. It was developed by CableLabs, a non-profit research and development consortium.

PacketCable's key components include the PacketCable Application Programming Interface (API), which provides a standardized interface for applications to interact with the network, and the PacketCable Management System (PCMS), which manages the network and provides services such as authentication and authorization.

The PacketCable API supports multiple programming languages, including C, C++, and Java, allowing developers to create applications that can communicate with the network. This enables the creation of a wide range of services, from voice over IP to video on demand.

PacketCable's focus on open standards and interoperability makes it an attractive solution for service providers and developers looking to create innovative services and applications.

PacketCable connects three distinct network types: Hybrid Fibre Coaxial (HFC) access networks, Public switched telephone networks (PSTN), and TCP/IP Managed IP networks.

PacketCable's technical architecture is designed to integrate these three network types seamlessly. This allows for a more efficient and reliable exchange of data between different networks.

The three network types that PacketCable interconnects are listed below:

PacketCable relies on several key protocols to function. One of the most important is DOCSIS, which is a standard for data over cable and details mostly the RF band.

DOCSIS is used to provide IP connectivity over cable networks, and in Europe, a variant called EuroDOCSIS is used instead. This is because cable networks in Europe use EuroDOCSIS as the underlying layer.

In addition to DOCSIS, PacketCable also relies on Real-time Transport Protocol (RTP) and Real Time Control Protocol (RTCP) for media transfer. These protocols are crucial for ensuring that audio and video are transmitted smoothly and in real-time.

PacketCable also uses PSTN Gateway Call Signaling Protocol Specification (TGCP), which is an MGCP extension for Media Gateways. This protocol is used for call signaling and is an important part of the PacketCable architecture.

Here are some of the key protocols used by PacketCable:

The versions of this software have undergone significant changes over the years. The first version, 1.0, was released in 2015 and introduced the core functionality of the software.

Broaden your view: Call-recording Software

This early version was not without its limitations, as it only supported a limited number of file formats. The software's user interface was also quite basic.

In 2017, the developers released version 1.5, which added support for more file formats and improved the user interface. This update also introduced a new feature that allowed users to customize the software's settings.

The 1.5 version was a major improvement over the original 1.0, but it still had some quirks. For example, it would sometimes crash when working with large files.

The most significant update was version 2.0, released in 2020. This version introduced a new, more intuitive user interface and improved performance. It also added support for cloud storage and collaboration features.

With version 2.0, the software became a more robust and feature-rich tool.

PacketCable is being widely deployed by operators around the world.

One notable example is B.net in Croatia, which has implemented PacketCable services.

Cable One has also deployed PacketCable system-wide, making it available to all their customers.

Cablevision – Optimum Voice has followed suit, deploying PacketCable system-wide.

Charter has also implemented PacketCable system-wide, expanding their VoIP services.

Other notable deployments include Claro TV in Guatemala, El Salvador, Nicaragua, and Honduras, and Cogeco - Cogeco Home Phone in Canada.

Comcast - Comcast Digital Voice has also deployed PacketCable system-wide, offering VoIP services to their customers.

Cox – Cox Digital Telephone has also implemented PacketCable system-wide, expanding their VoIP services.

Here is a list of some of the notable operators that have deployed PacketCable:

In a PacketCable setup, there are several key components that work together seamlessly. The P-CSCF server is the first point of contact for SIP messages, starting with the REGISTER request.

It's responsible for handling user authentication, using private user information and credentials for digest calculations. The EDVA plays a crucial role in protecting this sensitive information, returning an empty string when trying to retrieve the credentials MIB.

Voice Coders are a crucial component in many systems, and PacketCable voice coders are no exception. The required coders for PacketCable are ITU G.711 (both μ-law and a-law algorithm versions) for versions 1.0 and 1.5.

For version 1.5, additional coders are required: iLBC and BV16. ITU G.711 is a widely used coder, and its inclusion in PacketCable is no surprise.

The specifications also recommend ITU G.728 and ITU G.729 Annex E for use with PacketCable.

Here's a quick rundown of the required coders:

These coders are essential for ensuring high-quality voice communication in PacketCable systems.

POTS is an analogue interface that varies in different parts of the world, with distinct properties for voltages, timings, tones, caller ID delivery, and ringing.

The POTS interface must comply with specific standards, such as GR-909 for PacketCable and ETSI TS 101 909 part 18 for EuroPacketCable.

A cable modem with POTS interfaces is called an E-MTA (Embedded Multimedia Terminal Adapter), or an E-DVA (Embedded Digital Voice Adapter), depending on the terminology used.

The E-MTA or E-DVA is a crucial component in cable modem systems, and understanding its properties is essential for proper functioning.

Intriguing read: Telephone VoIP Adapter

The telephony part of an E-MTA or E-DVA is managed through its own set of MIB modules. These modules are used to configure settings, including those related to the POTS interface properties.

The PacketCable MIBs, however, are not detailed enough to express all European country variations. This led to the creation of international versions of these MIBs, which are used by EuroPacketCable.

An important consequence of this difference is incompatibility between PacketCable and EuroPacketCable E-MTA/E-DVA provisioning. This incompatibility affects both configuration files and SNMP messages used in provisioning flows.

Here are some specific ways in which PacketCable and EuroPacketCable differ:

A typical PacketCable 2.0 configuration file is often much larger than a minimal configuration file. If you're just getting started, you can often get by with a smaller configuration file, but other MIBs might be needed to set specific values.

PacketCable and EuroPacketCable have distinct digital certificate hierarchies due to the use of different root certificates.

These separate certificate hierarchies allow for distinct certificate authorities, which is a key aspect of their public key infrastructure (PKI).

The PKI is based on robust security mechanisms, providing a solid foundation for secure data transmission.

Digital certificates are a crucial part of this infrastructure, and they vary between PacketCable and EuroPacketCable.

The P-CSCF server is the target for SIP messages, starting with the REGISTER request. This is the first point of contact for users linked to the operator domain.

The P-CSCF server uses private user information for authentication purposes. It plays a key role in digest calculations.

An EDVA will return an empty string when trying to retrieve the credentials MIB to protect the vital secret. This is done to keep the user's credentials secure.

Applications and profiles are used to configure telephony functionality on a device, allowing multiple users to access the same set of applications by pointing them to the same profile.

A profile contains a set of desired functions, which can include call features such as "Digit Map" and "Basic Call".

Having multiple users share the same profile implies they will both have access to the same set of applications, or call features.

In some cases, different users may require different digit maps, but still share basic call functions. This can be achieved by creating two profiles, one for each user, with the second digit map defined in pktcEUERSTDigitMapProfileTable.2.

For your interest: Call Center Ip Phone

CableLabs hosts interoperability testing events, such as the one that included MetaSwitch infrastructure for cable digital telephony.

Dozens of cable operators are already delivering advanced digital telephony services based on MetaSwitch's softswitch and applications solutions.

MetaSwitch tested its advanced IMS core infrastructure and MetaSphere application server at a weeklong event held at the PacketCable Application Lab in Louisville, Colo.

Nine other equipment vendors participated in the testing, which focused on pre-PacketCable 2.0 IMS core networks, voice application servers, and voice clients.

Check this out: Multimedia Telephony

MetaSwitch was one of three vendors that tested both IMS core session control (CSCF) as well as voice application server functionality.

The testing achieved significant levels of interoperability for SIP-based voice services across equipment combinations from the participating manufacturers.

The PacketCable Application Lab serves as a venue for network equipment providers and application developers to test and demonstrate innovative applications for voice, multimedia, wireless, business, and converged services.

CableLabs will host additional events for the lab and make it available on an ongoing basis for participating vendors to use as a development and testing resource.

A fresh viewpoint: OpenCable Application Platform

PacketCable 2.0 provisioning uses applications to configure telephony functionality on the device.

This allows multiple users to get the same functionality by simply pointing them to the same profile.

A profile contains a set of desired functions, which can include call features like "Digit Map" and "Basic Call".

These call features are stored in tables, such as pktcEUERSTDigitMapProfileTable.2 and pktcEUERSTBasicCallTable.1.

In some cases, multiple profiles may be created to accommodate different user needs, but in our scenario, both users share the same profile.

Recommended read: Call Origination

PacketCable is a game-changer for the cable industry.

By providing a standardized framework for voice over IP (VoIP) and other multimedia services, PacketCable enables cable operators to offer a wider range of services to their customers.

PacketCable's architecture is based on the Data Over Cable Service Interface Specification (DOCSIS) standard, which provides the foundation for high-speed data services.

This means that PacketCable can take advantage of existing DOCSIS infrastructure, reducing the need for new hardware and infrastructure investments.

PacketCable has been widely adopted by cable operators, with many major players already implementing the technology.

By leveraging PacketCable, cable operators can improve their competitiveness and offer more innovative services to their customers.

Discover more: DOCSIS