...
| Object | Description |
|---|
Product | The product holds information about the capacity of the counters, the enforcements and notifications that should be triggered at specific capacity levels, the interval at which the counters should be reset, how many counters to retain at reset, and, if the product stops, fallthrough in the usage recording process. Since a product is used by buckets it is important not to remove products in use. |
ProductMapping | A flexible mapping table used to map from an external representation to a list of products. The external representation can be, for instance, a rating group, or a combination of rating group and time period classification. The mapping should not include any information related to a specific subscriber. |
SubscriberProfile | Subscriber profiles are used for associating different products to different profiles. The subscribers will then have access to the products associated with their subscriber profile. |
Overview of the Product Data Model
The different UDRs within the Product Data Model are connected as follows:
...
Overview of the Product Data Model
ProductMapping UDR
In the ProductMapping UDR you set up the priority for the product mapping, the rating groups, etc that the product mapping should use, and the products that should be applied.
...
| Info |
|---|
| title | Example - ProductMapping UDR |
|---|
|
The following values: | Code Block |
|---|
ID=101
Priority=1
Arguments=[4]
Targets=[100,110]
ID=102
Priority=3
Arguments=[8]
Targets=[100] |
will give the following setup: The first product mapping, with ID 101, has a higher priority than the second, with ID 102. The first product mapping refers to rating group 4, while the second product mapping refers to rating group 8. The first product mapping references product 100 and 110, while the second product mapping references product 100.
|
Product UDR
The Product UDR holds information about the capacity of the counters, the enforcements and notifications that should be triggered at specific capacity levels, the interval at which the counters should be reset, and how many counters to retain at reset. If StopFallthrough is set to yes, counting for this product should prevent counting in buckets connected to lower priority products. Since a product is used by buckets it is important not to remove products in use.
...
| Info |
|---|
| title | Example - Products UDR |
|---|
|
The following values: | Code Block |
|---|
ID=100
Name='GOLD'
Capacitites=[101, 102]
Duration=7
DurationUnit=3
Enforcements=[605]
Notifications=[1,3,5]
ResetType=2
ResetInterval=1
ResetIntervalUnit=3
RetainedCounters=10
Periods=[503]
StartTime='2011-06-01 00:00:00'
StopTime='2011-09-01 00:00:00'
StopFallthrough=true
StopAtCapacity=true
ID=110
Name='SILVER'
Capacitites=[101]
Duration=24
DurationUnit=2
Enforcements=[605]
Notifications=[2,4]
ResetType=2
ResetInterval=1
ResetIntervalUnit=4
RetainedCounters=2
Periods=[504]
StartTime='2011-01-01 00:00:00'
StopTime='2012-01-01 00:00:00'
StopFallthrough=true
StopAtCapacity=true |
will give the following setup: The two products have the IDs 100 and 110, which are used by both PCC Rules and PCC Buckets, and have the names Gold and Silver . The Gold product uses capacities 101 and 102, while the Silver product only uses capacity 101. The Gold product will be available for 7 days from the time you start to use it, while the Silver product will be available for 24 hours from the time you start to use it. Both products use the enforcement 605. The Gold product will receive notifications 1, 3 and 5, while the Silver product will receive notifications 2 and 4. The reset and retained counters settings for the Gold product will reset the product once every day, based on date, and discreet usage counter statistics will be kept for 10 days. The reset and retained counters settings for the Silver product will reset the product once every week, based on date, and discreet usage counter statistics will be kept for 2 weeks. The Gold product will be active during the time periods stated in the Periods list 503, while the Silver product will be active during the time periods stated in the Periods list 504. The Gold product will start on the 1st of June and end on the 1st of September, 2011, while the Silver product will start on the 1st of January, 2011 and end on the 1st of January, 2012. For both products, counting will stop once the bucket for the respective product is full.
|
SubscriberProfile UDR
In the SubscriberProfile UDR you can configure different subscriber profiles. The profiles associate subscriber types with certain products, and many subscribers can share the same profile.
...
| Info |
|---|
| title | Example - SubscriberProfile UDR |
|---|
|
The following values: | Code Block |
|---|
ID=10
Name='STAR'
Products=[100,110,120]
ID=20
Name='MEDIUM'
Products=[110] |
will give the following setup: The two subscriber profiles with IDs 10 and 20 has the names Start and Medium . The subscribers belonging to the Start profile will have access to products 100, 110 and 120, while the subscribers belonging to the Medium profile will only have access to product 110.
|
Capacity UDR
In the Capacity UDR you define the capacity for counter items. A capacity is used for measuring threshold values for enforcements and notifications.
...
| Info |
|---|
| title | Example - Capacity UDR |
|---|
|
The following values: | Code Block |
|---|
ID=101
Capacity=400000
CapacityUnit=0
CounterType=2
ID=102
Capacity=100000
CapacityUnit=1
CounterType=1 |
will give the following setup: The two capacities have the IDs 101 and 102, which are used by the Product UDR. The first capacity refers to the total amount of bytes, while the second capacity refers to the output bytes. The first capacity has a limit of 400000 bytes (unit=0), while the second capacity has a limit of 100000 kB (unit=1).
|
Enforcement UDR
The Enforcement UDR sets a threshold for when an enforcement should be triggered, and is used by both the Product UDR and PCC Rules. A Product can use one or several enforcements. When the usage exceeds enforcement threshold, the enforcement will be applied. When a new enforcement is triggered a new PCC rule should be applied.
...
| Info |
|---|
| title | Example - Enforcement UDR |
|---|
|
The following values: | Code Block |
|---|
ID=605
CounterType=1
Level=0.75
Name='LEVEL_75'
ID=607
CounterType=1
Level=0.5
Name='LEVEL_50' |
will give the following setup: The two enforcements have the IDs 605 and 607, which are used by the Products UDR. Both enforcements refers to output traffic. The first enforcement is triggered at 75 %, while that second enforcement is triggered at 50 %. The name of the first enforcement is LEVEL_75 , while the name of the second enforcement is LEVEL_50 , and these names can be used in attributes in RulesMapping, for example.
|
Notification UDR
With the Notification UDR you can configure notifications to be sent out at different usage levels. Each product can use several notifications.
...