Residential subscriber configuration

Overview

The XML API uses the ressubscr package to create and manage residential subscribers. A residential subscriber is an end recipient of multiple service offering, such as VoD, VoIP, or other triple play applications. A residential subscriber host, which is sometimes called a subscriber host or a host, is an end device, such as a computer or set-top box that connects to the provider network and receives the service traffic.

In the context of the XML API, a residential subscriber, which is sometimes called a subscriber, has a unique identifier that associates a group of end-user devices with policies. A subscriber can be associated with multiple SAPs on multiple NEs, and a customer can be associated with multiple subscribers.

To configure residential subscriber management on the NFM-P, create and configure the following components, depending on the service delivery model:

  • subscriber identification policy

  • subscriber profile

  • SLA profile

  • subscriber explicit map

  • ANCP policy

  • MSAP policy

  • host tracking policy

  • category map policy

  • credit control policy

  • IGMP policy

  • BGP peering policy

  • diameter policy

  • subscriber multicast CAC policy

A host requires subscriber-profile and SLA-profile associations to access the network. Profiles define service attributes for hosts such as scheduling, accounting, security, and traffic prioritization by application type. A profile uses existing NFM-P policy definitions and allows the customization of policy parameters using override values.

See “Residential subscriber management” in the NSP NFM-P Classic Management User Guide for more information about residential subscriber management, including prerequisites and workflows.

Residential subscriber related packages

Example

The following example outlines what is required for an XML request to create a subscriber identification policy for residential subscribers.

Subscriber identification policy creation parameters

Figure 19-24: Subscriber identification policy creation request example
<generic.GenericObject.configureChildInstance xmlns="xmlapi_1.0">
   <deployer>immediate</deployer>
   <synchronousDeploy>true</synchronousDeploy>
   <distinguishedName>Subscriber Identification Policy</distinguishedName>
   <childConfigInfo>
      <subscrident.Policy>
         <actionMask>
            <bit>create</bit>
         </actionMask>
         <displayedName/>          
          ..
         <children-Set>
            <subscrident.SubscrProfileEntry>
               <actionMask>
                  <bit>create</bit>
               </actionMask>
               <displayedName>Subscr Profile 4</displayedName>
               <subscrProfilePointer>Subscriber Profile:Subscriber Profile Example 10</subscrProfilePointer>
               <subscrIdentPolicyName/>
            </subscrident.SubscrProfileEntry>
         </children-Set>
      </subscrident.Policy>
   </childConfigInfo>
</generic.GenericObject.configureChildInstance>