Skip Headers
Oracle® Communications Unified Inventory Management Cable TV Technology Pack Implementation Guide
Release 7.2.2

Part Number E36043-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

1 Cable TV Technology Pack Overview

This chapter provides an overview of the Cable TV Technology Pack. The chapter also provides deployment information for the technology pack.

About the Cable TV Technology Pack

Cable television service providers offer broadcast services including basic, tiered, and packaged services, and individual video services such as Video on Demand (VOD). The infrastructure needed to provide such services includes configurations of satellite dishes, receivers, modulators, storage devices, access controllers, and VOD controllers.

Customer premise equipment (CPE), which includes programmable video receivers (set-top boxes) and subscription cards, processes signals received from the provider network and enables subscribers to view, record, and interact with the content.

Driven by the technology implemented in cable television systems, cable television service providers are required to maintain an inventory of the services they provide, devices used to provide service, provisionable video streams, CPE such as set-top boxes and subscription cards assigned to subscribers, the locations where the video services are offered, and the details of subscribers.

Figure 1-1 displays a simplified view of a cable video service.

Figure 1-1 Cable Video Service Overview

Surrounding text describes Figure 1-1 .

In this example, video content is transmitted from various sources to a cable service provider's headend. Each headend represents a facility that supports access controllers, VOD controllers, and other equipment.

The access controller controls and grants access to video services for the set-top box in the home. A VOD controller grants access to VOD entitlements. A single access controller supports multiple subscriptions.

The Cable TV Technology Pack enables you to model provisionable cable video subscription services (such as Basic service, Expanded service, and HBO), the devices on which these services are provisioned, the service locations for these subscriptions, and the supporting logical resources in Oracle Communications Unified Inventory Management (UIM).

The technology pack provides a topological view of the cable service provider's organization, which consists of a multisystem operator, regions, clusters, and offices. The technology pack provides support for modeling and managing logical resources including access controllers, device partitions, and channel map information. It also manages the inventory of the devices on which these services are provisioned, including set-top boxes and subscription cards. The Cable TV Technology Pack also supports the management of provisionable video services.

Figure 1-2 illustrates the specifications used to model a cable video service provider's organization, which includes a multisystem operator, region, cluster, and cable office.

Figure 1-2 Cable Video Service Organization Model

Surrounding text describes Figure 1-2 .

Figure 1-3 illustrates the specifications used to model a cable video service subscription.

Figure 1-3 Cable Video Service Model

Described in the surrounding text.

Figure 1-4 illustrates the specifications used to model a headend profile.

Figure 1-4 Headend Profile Service Configuration Model

Described in the surrounding text.

Figure 1-5 illustrates the specifications used to model a video service subscriber.

Figure 1-5 Video Service Subscriber Model

Described in the surrounding text.

In a cable subscription domain model, the relationship between the subscription, programmable video receiver, subscription card, subscription features, and provisionable video services are managed through the video service.

Cable Video Service Topologies

The topologies in the Cable TV Technology Pack provide a graphical view of the Multi-Service Operator (MSO) organizational structure of the cable service provider's organization. The Cable TV Technology Pack provides topologies for the following networks:

  • MSO Network: An MSO is represented by an Organization (party) with a Party role of Multi-System Operator and by a network that comprises regions.

  • Region Network: A region is represented by a network that comprises clusters.

  • Cluster Network: A cluster is represented by a network that comprises several cable offices. The cable offices can be represented as geographic locations and within the Cluster network.

  • Office Network: An office is represented by a network that comprises controllers that include access controllers and VOD controllers.

Contents of the Cable TV Technology Pack

Table 1-1 describes the contents of the Cable TV Technology Pack, which is delivered as a single ZIP file.

Table 1-1 Cable TV Technology Pack ZIP File Contents

Item Directory

Javadoc

doc/javadocForTechPacks

See "Cable TV Technology Pack Javadoc" for more information.

Super JAR Archive File

deploy/superJarToDeploy

See "Cable TV Technology Pack Super JAR File" for more information.

Components of the Super JAR Archive File

deploy/individualJarsForSuperJar

See "Cable TV Technology Pack Individual Jar Files" for more information.

Cartridge Project ZIP Files and Sample Code

designStudio/cartridgeZips

See "Cable TV Technology Pack ZIP Archive Files" for more information.

Common Library

designStudio/libForStudioDesignTime

See "Common Library" for more information.

Sample Ant Build Scripts

designStudio/sampleBuildScripts

See "Cable TV Technology Pack Sample Ant Build Scripts" for more information.

Sample XML for Web Service Requests

test/webServiceRequestXML

See "Cable TV Technology Pack Web Service Samples" for more information.

Readiness Data

test/readinessDataLoader

See "Cable TV Technology Pack Readiness Data" for more information.


Cable TV Technology Pack Javadoc

From the javadocForTechPacks directory, open the javadoc_rel.date.time.build.zip file and extract the javadoc directory. Double-click the extracted javadoc/index.html file to access the Javadoc provided with the Cable TV Technology Pack, including information that summarizes classes, methods, and parameters.

Cable TV Technology Pack Super JAR File

The Cable TV Technology Pack super JAR file contains the entire contents of the technology pack and is ready for deployment using the Cartridge Deployer Tool. You use the Cartridge Deployer Tool to simultaneously deploy multiple cartridges to UIM run-time environments.

See UIM Cartridge and Technology Pack Guide for more information about the Cartridge Deployer Tool.

Cable TV Technology Pack Individual Jar Files

In addition to the deployable super JAR file, technology packs include individually JAR files. Deploying individual JAR files may be required if you extend a cartridge in Oracle Communications Design Studio.

JAR files must be deployed in the order shown below to ensure that all dependencies are met.

  • ora_uim_common_cartproj-*.jar,\

  • ora_uim_party_customer_cartproj-*.jar,\

  • ora_uim_service_location_cartproj-*.jar,\

  • ora_uim_address_cartproj-*.jar,\

  • ora_uim_us_address_cartproj-*.jar,\

  • ora_uim_canada_address_cartproj-*.jar,\

  • ora_uim_norway_address_cartproj-*.jar,\

  • ora_uim_uk_address_cartproj-*.jar,\

  • ora_uim_saudi_arabia_address_cartproj-*.jar,\

  • ora_uim_video_cartproj-*.jar,\

  • ora_uim_video_characteristics_cartproj-*.jar,\

  • ora_uim_video_subscription_cartproj-*.jar,\

  • ora_uim_video_infrastructure_cartproj-*.jar,\

  • ora_uim_video_configuration_cartproj-*.jar

Note:

The asterisk in the JAR file names in the previous list represent a five-segment release version number followed by a build number. The five-segment release version numbers represent the:
  • Major Version Number

  • Minor Version Number

  • Maintenance Pack

  • Generic Patch

  • Customer Patch

Cable TV Technology Pack ZIP Archive Files

The Cable TV Technology Pack comprises a number of cartridges, which can be divided into three broad categories:

Address, Location, and Party Cartridges

The address, location, and party cartridges include entities that are used by data networking and cable TV entities to define places and people in the network. There are separate address cartridges for several different cartridges as well as generic service location and address cartridges. The country-specific cartridges provide similar capabilities with minor variations based on local standards.

The address, location, and party cartridges are:

  • Address cartridge: ora_uim_address

  • Canada address cartridge: ora_uim_canada_address

  • Norway address cartridge: ora_uim_norway_address

  • Saudi Arabia address cartridge: ora_uim_saudi_arabia_address

  • United Kingdom address cartridge: ora_uk_address

  • United States address cartridge: ora_uim_us_address

  • Service location cartridge: ora_uim_service_location

  • Party cartridge: ora_uim_party_customer

See Chapter 2, "Address, Location, and Party Content" for more information.

Cable TV Cartridges

The cable TV cartridges model the capabilities specific to cable TV technology.

The cable TV cartridges are:

  • Characteristics cartridge: ora_uim_video_characteristics

  • Infrastructure cartridge: ora_uim_video_infrastructure

  • Subscription cartridge: ora_uim_video_subscription

  • Configuration cartridge: ora_uim_video_configuration

  • Video cartridge: ora_uim_video

See Chapter 3, "Cable TV Content" for more information.

Common Library

The common library is a JAR file that provides utility methods that are independent of the technology domain. These utility methods can be used across multiple technology packs, so they reside in a common JAR file that is included in multiple technology packs.

The common library is:

  • ora_uim_commonLib.jar

See Chapter 4, "Common Content" for more information.

Note:

The common library is not considered a cartridge because it does not contain content that can be imported into Design Studio to view. The common library contains Java class files only; it does not contain the viewable Java source files from which the classes are compiled.

Cable TV Technology Pack Sample Ant Build Scripts

The Cable TV Technology Pack includes sample Ant build scripts for automating cartridge project builds. See Design Studio Installation and System Administration Guide for more information about automating builds.

Cable TV Technology Pack Web Service Samples

The Cable TV Technology Pack includes sample XML files that you can use as a starting point for customizing the Service Fulfillment Web service requests provided with the technology pack. See "Using the UIM Service Fulfillment Web Service" for more information.

Cable TV Technology Pack Readiness Data

The Cable TV Technology Pack includes SQL scripts to load a UIM database with seed data for testing. Use these SQL files to generate scenarios when learning and testing the functionality in the technology pack. Run the SQL files only once, and only after you deploy the Cable TV Technology Pack into UIM.

Note:

Oracle does not recommend that you use these SQL scripts in a production environment.

Opening the Technology Pack in Design Studio

You can open individual ZIP files in Design Studio to review or extend the Cable TV Technology Pack. See the Design Studio Help and UIM Developer's Guide for information about opening files in Design Studio.

See UIM Concepts for guidelines and best practices for extending technology packs. See "Extending the Cable TV Technology Pack" for detailed information about extending the Cable TV Technology Pack.

Using the Cable TV Technology Pack

To use the Cable TV Technology Pack:

Deploying the Cable TV Technology Pack

Oracle recommends that you use the Cartridge Deployer Tool to deploy the Cable TV Technology Pack super JAR archive file to a UIM run-time environment. Deploying the technology pack with the Cartridge Deployer Tool ensures that all cartridges and dependencies are deployed in the proper order. See UIM Cartridge and Technology Pack Guide for more information about the Cartridge Deployer Tool.

Important:

Before deploying the Cable TV Technology Pack, you must deploy the base cartridges if not previously deployed. For information on how to deploy the base cartridges, see UIM Cartridge and Technology Pack Guide.

For information about deploying individual cartridges into a UIM test environment, see the Design Studio Help. For information about deploying a cartridge into a UIM production environment, see UIM Cartridge and Technology Pack Guide.

Defining Cable-Specific Inventory Items

Readiness steps require that you define cable-specific inventory items that enable you to provision cable services prior to actually provisioning the cable services to end customers. Readiness steps are performed in the UIM user interface. The required readiness steps are:

  • Define cable access controllers

  • Define cable device partitions

  • Define subscription media streams

  • Map provisionable media streams to the controller

Optional readiness steps include:

  • Associate device partitions to access controllers

  • Define the headend

  • Associate the controller and device partition to the headend

  • Define programmable video receivers

    (The receivers are created by the Web service if they do not already exist.)

  • Define subscription cards

    (The cards are created by the Web service if they do not already exist.)

Many of these steps are further explored through an example, as described in Chapter 6, "Cable TV Technology Pack Service Example".

Using the UIM Service Fulfillment Web Service

Detailed information on using the UIM Service Fulfillment Web service is described in Chapter 7, "Automating Cable Services through Web Services".

Enabling Debugging of Validation and Assignment Rules

The validation and assignment rules included with the Cable TV Technology Pack include debugging code that displays messages you can monitor by using the logging capabilities supplied by WebLogic Server. See UIM System Administrator's Guide for more information about logging. The debugging code allows you to observe the behavior of the validation and assignment rules and diagnose any issues that arise.

To enable debugging of validation and assignment rules:

  1. Open the loggingconfig.xml file, typically found in uim.home\config.

  2. Add the following entries to the file:

    <logger name="oracle.communications.inventory.techpack.video" additivity="false">
    <level value="debug" />
    <appender-ref ref="stdout"/>
    <appender-ref ref="rollingFile"/>
    </logger>
    
    <logger name="oracle.communications.inventory.techpack.video.impl" additivity="false">
    <level value="debug" />
    <appender-ref ref="stdout"/>
    <appender-ref ref="rollingFile"/>
    </logger>
    
    <logger name="oracle.communications.rules" additivity="false">
    <level value="debug" />
    <appender-ref ref="stdout"/>
    <appender-ref ref="rollingFile"/>
    </logger>
    
  3. Save and close the file.

  4. Restart the server.