Packetcable 2.0 Overview (Part 2 of 4)

Print This Page

PacketCable 2.0 Architecture—SIP/QoS

Introduction
This article is the second in a four part series (the first was printed in the November/December 2006 issue of this newsletter) that explains the PacketCable™ 2.0 network architecture. The first article (located in CED at http://www.cedmagazine.com/article/CA6398269.html) describes the PacketCable 2.0 project design goals, strategic drivers, and architecture. This current article discusses the PacketCable specification's use of the Session Initiation Protocol (SIP) and how it integrates with the PacketCable Multimedia specification. Subsequent articles will discuss the provisioning, management, and security framework as well as the future of the PacketCable 2.0 project.

The PacketCable 2.0 specification is based upon the Third Generation Partnership Project (3GPP) IP Multimedia Subsystem (IMS), which uses SIP for session control. SIP provides the foundation for a service delivery platform that is a key aspect of the IMS and the PacketCable 2.0 network. By using SIP in conjunction with PacketCable Multimedia, the PacketCable 2.0 network architecture allows cable operators to create a holistic service framework on top of their DOCSIS network deployments without precluding other access technologies.

Session Initiation Protocol (SIP)
SIP is used for creating and managing communication sessions in IP-based networks. The protocol is defined by the Internet Engineering Task Force (IETF), the standards body that has defined most of the foundational protocols for the Internet and World Wide Web. SIP follows the Internet paradigm that favors end-to-end communication and distributed functionality. One of the strong features of SIP is its extensibility - new messages and attributes can be easily defined. Also, SIP provides built-in mechanisms to support interoperability so that end points with disparate capabilities can still communicate with each other.

SIP and its extensions provide the following capabilities:

Multimedia session establishment. Enables a user to establish a multimedia communications session with another user on the network. The term "multimedia" refers to the multiple types of media that can be carried in a session, such as audio, video, text, etc. Two endpoints can establish or modify a session by exchanging information that describes the attributes of the session, such as what type of media coding to use and where to send the media.

User mobility and registration. Allows a user to be contacted using a single identifier, even as the user changes network attachment points (user mobility). Also, a user can have multiple simultaneous network attachment points (e.g., WiFi and Ethernet). User mobility and the ability to support multiple attachment points are enabled by the SIP registration procedure. When a user first appears on the network as a result of logging in or powering up a device, the registration procedure binds the user identity to the user's current physical attachment address on the network. This binding is maintained as long as the user remains at that physical address.

Event notification. Provides a framework that allows an entity to subscribe to an event of interest and be notified when that event takes place. In other words, SIP can obtain the status of a given resource and track changes in that status. For example, an application could subscribe to the presence state of a user (see below) to determine when the user is available to accept new calls.

Presence. Enables more effective communication by allowing users to advertise their availability and willingness to communicate. Presence can be thought of as dynamic information about a particular user that is made available to applications or other users. A widely used application that leverages presence is Instant Messenger (IM), whose "buddy list" allows a user to see who is available for messaging.

Decentralized Application Control
One of the chief characteristics that distinguishes the PacketCable 2.0 network architecture from the PacketCable 1.0 and 1.5 (herein referred to as 1.x) network architectures is the nature of application control. As shown in Figure 1, a PacketCable 1.x network is built around a centralized architecture in which the application logic plus the non-application-specific support functions, such as user authentication, service authorization and message routing, are all controlled by the Call Management Server (CMS). This application-centric approach works well for residential telephony, a well-defined service with simple end-point devices.

A PacketCable 2.0 network, on the other hand, is required to support multiple applications and to provide a platform on which new, yet-to-be-defined applications can be introduced easily. To meet this requirement, PacketCable 2.0's network architecture decouples application control from the application-independent support functions. As shown in Figure 1, the PacketCable 2.0 base network architecture provides all the support functions, such as authentication, authorization, and routing. The application logic resides in Application Servers and clients that plug into standard interfaces to utilize the support services of the base architecture. PacketCable 2.0's decoupling of application logic from the support functions promises to deliver many benefits for cable operators, such as:

• Re-use of core network components across multiple applications
• Favorable scaling and reliability models
• Reduced time-to-market for new services

For consumers, the primary benefit will be a variety of new services that enhance their overall cable experience.

Figure 1. Application Control in PacketCable 1.x and 2.0

Next story