====== Named profiles ======
{{indexmenu_n>4}}
<note>You can name a rate plan (profile for policing) or profile for services and store it in a internal database the UDR. Named Profile (NP) is created once and is used for setting needed service parameters and rate plan limiters for subscribers.</note>

Named profiles have the following advantages over the unnamed profiles:
  - Simplifies administration of users
  - Allows you to find the subscribers with the required profile by profile name
  - Allows you to change the profile to all subscribers with a given named profile simply by changing the profile parameters
  - Allows you to control the restriction on the number of unique named profiles (up to 65535)

Unnamed profiles have the following advantages:
  - No need to have a deal with profile management (create and delete it), the profile is released together with the removal service or subscriber profile
  - No need to invent a profile name

====== Commands with a named profile for policing settings (rate plans) ======
 
Creating a rate plan with a named profile for multiple subscribers
<code>
fdpi_ctrl load profile --policing rate_10_day.cfg --profile.name rate_10
fdpi_ctrl load --policing --profile.name rate_10 --ip 192.168.0.1
fdpi_ctrl load --policing --profile.name rate_10 --ip 192.168.0.2
fdpi_ctrl load --policing --profile.name rate_10 --login kv_111
</code>

View policing settings (rate plan) by named profile
<code>
fdpi_ctrl list profile --policing --profile.name rate_10
</code>

Search subscribers by named profile of a rate plan
<code>
fdpi_ctrl list all --policing --profile.name rate_10
</code>

Delete named profile (The named profile has no subscribers using it to delete)
<code>
fdpi_ctrl del profile --policing --profile.name rate_10
</code>

Change settings for rate plan from dayly to night mode (new settings will apply to all subscribers with the named profile)
<code>
fdpi_ctrl load profile --policing rate_10_night.cfg --profile.name rate_10
</code>

====== Commands for named profile with service settings (configuration parameters) ======

<note important>The profile name is unique for each service, ie profile_1 for service 6 differs from profile_1 for service 10</note>

Create a named profile for subscriber notification and set a named profile for multiple users
<code>
fdpi_ctrl load profile --service 6 --profile.name ads_of_tv_world_football --profile.json '{ "redirect" : "http://mysite.ru/landing_nash_football", "check" : true }'
fdpi_ctrl load --service 6 --profile.name ads_of_tv_world_football --ip 192.168.0.1
fdpi_ctrl load --service 6 --profile.name ads_of_tv_world_football --ip 192.168.0.2
</code>

Compare it with activation of the service with unnamed profile (service parameters are taken from the configuration file dpi)
<code>
fdpi_ctrl load --service 6 --ip 192.168.0.1
fdpi_ctrl load --service 6 --profile.json '{ "redirect" : "http://mysite.ru/landing_nash_football", "check" : true }' --ip 192.168.0.2
</code>

Search subscribers with named profile for service 6
<code>
fdpi_ctrl list all --service 6 --profile.name ads_of_tv_world_football
</code>

Delete named profile (The named profile has no subscribers using it to delete)
<code>
fdpi_ctrl del profile --service 6  --profile.name ads_of_tv_world_football
</code>

Change setting named profile for service (new settings will apply to all subscribers with the named profile)
<code>
fdpi_ctrl load profile --service 6 --profile.name ads_of_tv_world_football --profile.json '{ "redirect" : "http://mysite.ru/landing_nash_football", "check" : true }'
</code>

To list all the created profiles for all services
<code>
fdpi_ctrl list all profile --service
</code>