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:

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

• Residential subscriber manage - ressubscr

• Subscriber profile - subscrprofile

• Subscriber identification - subscrident

• Subscriber authentication - subscrauth

• Subscriber explicit map - subscrexpmap

• SLA profile - slaprofile

• ANCP policy - ancp

• ARP host - arp

• Credit control policy - crdtctrl

• Diameter policy - diameter

• MSAP policy - msapolicy

• PPP management - ppp, ppoe

• MSAP, group interface, IGMP host tracking, subscriber interface - vprn, ies

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

• method - generic.GenericObject.configureChildInstance

• distinguishedName - Subscriber Identification Policy. The FDN can be determined by looking at the Parent Hierarchy of the class to be created in the XML API Reference

• childConfigInfo - creates and configures the following policy parameters:

  • Policy object- subscrident.Policy

  • <displayedName> - assigns a unique name

  • <children-Set>- tag to enclose children objects

         •   Subscriber profile entry object- subscrident.SubscrProfileEntry

         •   <displayedName> - assigns a name

         •   <subscrProfilePointer>- pointer to the subscriber profile

         •   <subscrIdentPolicyName> - name of the subscriber identification profile

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>

© 2024 Nokia. Nokia Confidential Information

Use subject to agreed restrictions on disclosure and use.