Siemens Policy Manager

8/19/2019 Siemens Policy Manager

http://slidepdf.com/reader/full/siemens-policy-manager 1/21

Siemens Policy Manager 3.0

Customer Feature Description: BC ResetExtension

A50016-E5830-M100-2-7618

RE085_003975



Restricted © Siemens Convergence Creators GmbH, 2015. All rights reserved.

All trademarks and copyrights are the property of their respective owners.The reproduction, transmission, translation or any other exploitation of this document or its content is not

permitted without express written authority. Offenders will be liable for damages. All rights reserved,

including any rights created by patent grant or registration of a utility model or of a design right.

All rights of technical modification are reserved.

Publisher:

Siemens Convergence Creators GmbH

CEE RC-AT CVC TM LTE

Autokaderstrasse 29

A-1210 Vienna



Siemens Policy Manager 3.0 - Customer Feature Description: BC Reset Extension

| page 3

Contents

1 Change History ............................................................................................ 5

2 Summary of Changes .................................................................................. 6

2.1 Changes in the feature ............................................................................................................... 6

3 References .................................................................................................. 7

4 Introduction .................................................................................................. 8

5 Benefits ....................................................................................................... 9

5.1 Benefits for the operator ........................................................................................................... 9

5.2 Benefits for the end user ........................................................................................................... 9

6 Requirements for using the feature ............................................................ 10

6.1 Software ................................................................................................................................... 10

6.2 Hardware .................................................................................................................................. 10

6.3 Firmware .................................................................................................................................. 10

6.4 Products ................................................................................................................................... 10

6.5 Other requirements ................................................................................................................. 10

6.6 Backward compatibility ............................................................................................................ 10

7 Functionality .............................................................................................. 11

8 Use cases .................................................................................................. 12

9 Network impacts ........................................................................................ 13

9.1 Network operations ................................................................................................................. 13

9.2 System performance ................................................................................................................ 13

9.3 System attributes and parameters .......................................................................................... 13

9.4 Nodes ....................................................................................................................................... 13

9.5 Interworking features .............................................................................................................. 13

10 Engineering considerations ..................................................................... 14

10.1 Database changes .................................................................................................................... 14

10.2 Files .......................................................................................................................................... 14

10.3 Parameters ............................................................................................................................... 14

10.4 Provisioning .............................................................................................................................. 14

10.5 Statistics ................................................................................................................................... 14

10.6 Capacity .................................................................................................................................... 14

10.7 Billing ........................................................................................................................................ 14

10.8 Restrictions ............................................................................................................................... 15



1 Change History

page 4 |

10.9 Compliance ............................................................................................................................... 15

11 Interfaces ................................................................................................ 16

11.1 Operator interfaces .................................................................................................................. 16

11.1.1 Command ..................................................................................................................................................... 16

11.1.2 GUI changes ................................................................................................................................................. 16

11.1.3 Alarms .......................................................................................................................................................... 16

11.2 Subscriber interfaces ................................................................................................................ 16

11.3 External interfaces ................................................................................................................... 16

12 Accronyms .............................................................................................. 17

13 Index ....................................................................................................... 21




| page 5

1 Change History

Version Date Description of Changes

A50016-E5820-M100-1-7618 9 June 2015 Initial version.

A50016-E5830-M100-1-7618 23 June 2015 Doc-Id updated.

A50016-E5830-M100-2-7618 30 September 2015 Update for P7



2 Summary of Changes

| page 6

2 Summary of Changes

2.1 Changes in the feature

Change Description Release

New feature 3.0




| page 7

3 References

ID Title

[RE085_003975]Focal Point Request RE085_003975 (2015-06-09) "BC Reset

Extension"

[29.212]3GPP TS 29.212 "Policy and Charging Control over Gx reference

point (Release 11)", Rel. 11.14

[29.214] 3GPP TS 29.214 "Policy and Charging Control over Rx referencepoint", Rel 11.14

[29.213]3GPP TS 29.213 "Policy and Charging Control signalling flows and

Quality of Service (QoS) parameter mapping", Rel11.13

[23.203]3GPP TS 29.203 "Policy and Charging Control Architecture",

Rel11.15

[23.401] 3GPP TS 23.401 "E-UTRAN Access", Rel 11.11



4 Introduction

| page 8

4 Introduction

This extension adds operator a possibility to define new cycling periods (quarterly, half-yearly and yearly) for

packages and to specify time of day at which the bill-cycle reset will occur.




| page 9

5 Benefits

5.1 Benefits for the operator

With this feature a higher variety of use cases related to Fair Use Policy (FUP) can be deployed, as

packages are not restricted to daily, weekly or monthly billcylce reset.

5.2 Benefits for the end user



6 Requirements for using the feature

| page 10

6 Requirements for using the feature

6.1 Software

This feature requires the Siemens Policy Manager3.0.

6.2 Hardware

No new hardware is required to support the feature.

6.3 Firmware

None.

6.4 Products

This feature is supported by the Siemens Policy Manager3.0 incl. supported SPRs (One-NDS Extension

Package for the Siemens Policy Manager and Embedded SPR).

6.5 Other requirements

None.

6.6 Backward compatibility

This feature is not affecting backward compatibility.




| page 11

7 Functionality

A package is considered outdated and will be detected as invalid by the bill-cycle validity check

mechanism when its cycle reset date (ActiveExpiryDate) lies in the past.

When packages are fetched for a subscriber at the session initiation, validity check of each cycling

package is done and each package for which bill-cycle is invalid needs to be processed just as bill-cycle

has just occurred for that package. Counters will be reset and the next bill-cycle reset date is calculated

based on the current date, the package cycle, the cycle reset point and the cycle reset time.

The same calculation is done if the bill cycle reset occurs during and ongoing session

In Siemens Policy Manager 3.0 the validity check is enhanced so that not only date but also time-of-dayis taken into consideration. Additionally the package cycles "quarter", "half-year" and "year" are

supported.

Several examples of calculation of next bill-cycle occurrence:

Next bill cycle / ActiveExpiryDate =

If packageCycle = 'day' then consider current date & CycleResetTime (e.g. current time =

201501151000Z and CycleResetTime =’1600’ => ActiveExpiryDate = 201501151600Z

If packageCycle = ‘week’ then consider current date & CycleResetPoint & CycleResetTime (e.g. current

time = 201501151000Z (Thursday), CycleResetPoint = ‘0’ (Monday) and CycleResetTime =’0730’ =>

ActiveExpiryDate = 201501190730Z (Monday)

If packageCycle = ‘month’ then consider current date & CycleResetPoint & CycleResetTime (e.g.

current time = 201501151000Z, CycleResetPoint = ‘10’ (10th day of month) and CycleResetTime

=’1159’ => ActiveExpiryDate = 201502101159Z

If packageCycle = ‘quarter’ then consider current date & CycleResetPoint & CycleResetTime (e.g.

current time = 201501151000Z, CycleResetPoint = ‘75’ (75th day of each 3 month (quarter) =16.3) and

CycleResetTime =’2230’ => ActiveExpiryDate = 201503162230Z

If packageCycle = ‘halfyear’ then consider current date & CycleResetPoint & CycleResetTime (e.g.

current time = 201501151000Z, CycleResetPoint = ‘43’ (43rd day of each 6 month (half year)=12.2) and

CycleResetTime =’2345’ => ActiveExpiryDate = 201502122345Z

If packageCycle = ‘year’ then consider current date & CycleResetPoint & CycleResetTime (e.g. currenttime = 201501151000Z, CycleResetPoint = ‘273’ (273rd day of the year=30.9) and CycleReset Time

=’0200’ => ActiveExpiryDate = 201509300200Z



8 Use cases

| page 12

8 Use cases

None.




| page 13

9 Network impacts

9.1 Network operations

None.

9.2 System performance

No impact.

9.3 System attributes and parameters

None.

9.4 Nodes

None.

9.5 Interworking features

None.



10 Engineering considerations

| page 14

10 Engineering considerations

10.1 Database changes

Data model schema is enhanced in the way that:

The “packageCycle” is enhanced with the new values: ‘Quarter’, ‘Halfyear’ and ‘Year’.

New attribute ‘cycleResetTime’ is added in the oc:pcrfPackageInstance and oc:pcrfGroupProf.

10.2 Files

None.

10.3 Parameters

None.

10.4 ProvisioningIn order to take into account this feature, database has to be extended as stated in 'Database changes'.

10.5 Statistics

None.

10.6 Capacity

Capacity remain the same.

10.7 Billing

None.




| page 15

10.8 Restrictions

None.

10.9 Compliance

This feature is compliant with 3GPP specifications:

ID Title

[29.214]3GPP TS 29.214 "Policy and Charging Control over Rx reference

point", Rel 11.14

[29.213]3GPP TS 29.213 "Policy and Charging Control signalling flows and

Quality of Service (QoS) parameter mapping", Rel11.13

[29.212]3GPP TS 29.212 "Policy and Charging Control over Gx reference

point (Release 11)", Rel. 11.14

[23.203]3GPP TS 29.203 "Policy and Charging Control Architecture",

Rel11.15

[23.401] 3GPP TS 23.401 "E-UTRAN Access", Rel 11.11



11 Interfaces

| page 16

11 Interfaces

11.1 Operator interfaces

11.1.1 Command

None.

11.1.2 GUI changes

No impact on Policy builder.

11.1.3 Alarms

None.

11.2 Subscriber interfaces

None.

11.3 External interfaces

None.




| page 17

12 Accronyms

Abbreviation Meaning

2G/3G, 2G3G, 2g3g 2nd / 3rd - Generation Cell-Phone Technology

AF Application Function

AMBR Aggregate Maximum Bit Rate

APN Access Point Name

ARP Allocation Retention Priority

AVP Attribute Value Pair

BBERF Bearer Binding and Event Reporting Function

CConditional. A conditional AVP is included in the message if a

certain condition is fulfilled.

CCA Credit-Control-Answer (CC-Answer)

CCR Credit-Control-Request (CC-Request)

CLI Command Line Interface

CSD Circuit Switched Data

CSG Closed Subscriber Group

CSV Comma-Separated Value

DB Database

DN Distinguished Name

DNS Domain Name System

EP Expansion Package

EPC Evolved Packet Core

EPS Evolved Packet System

EUTRAN Evolved Universal Terrestrial Radio Access

FQDN Fully Qualified Domain Name

FUP Fair Use Policy

GBR Guaranteed Bit Rate



12 Accronyms

| page 18

GERAN GSM EDGE Radio Access Network

GGSN

Gateway GPRS Support Node (gateway between a

GPRS/UMTS wireless data network and other PDN (e.g.

Internet))

GPRS General Packet Radio Service

GSM Global System for Mobile Communications

GUI Graphic User Interface

HA Home Agent

IBC Initial Balance Check

IETF Internet Engineering Task Force

IMEI International Mobile Equipment Identity

IMS IP Multimedia Subsystem

IMSI International Mobile Subscriber Identity

IP Internet Protocol

IPsec Internet Protocol Security

LDAP Lightweight Directory Access Protocol

LTE Long Term Evolution

MMandatory. A mandatory AVP must be included in the

message.

MBR Maximum Bit Rate

MCC

Mobile Country Code. The MCC is part of the International

Mobile Subscriber Identity (IMSI) number, which uniquely

identifies a particular subscriber, and is stored on a (usually)

removable SIM card.

MCD Media Component Description

MD5 Message-Digest algorithm 5

MNCMobile Network Code (uniquely identifies a mobile phone

operator/carrier)

MSC Message Sequence

MSC Media-Sub-Component

MSISDN Mobile Subscriber Integrated Services Digital Network Number

MPS Multimedia Priority Service




| page 19

NBM Network Based Mobility

NeMIP Network Multi-Purpose Inter-Services Platform

NDS Network Directory Service

OOptional. An optional AVP is not necessarily included in the

message but can be handled in case of occurrence.

OCS Online charging system

OFCS Offline charging system

PAP Password Authentication Protocol

PCC Policy and Charging Control

PCEF Policy and Charging Enforcement Function

P-CSCF Proxy Call Session Control Function

PCRF Policy and Charging Rule Function

PDN Packet Data Network

PDN-GW Packet Data Network Gateway

PGW Provisioning Gateway

PMIP Proxy Mobile IP

PS Packet Switched

QCI QoS Class Identifier

QoS Quality of Service

RAA Re-Auth-Answer (RA-Answer)

RAR Re-Auth-Request (RA-Request)

RADIUS Remote Authentication Dial In User Service

RFC Request for Comments

SA Security Association

SDF Service Data Flow

SOAP Simple Object Access Protocol

SPML Services Provisioning Markup Language

SPR Subscriber Profile Repository

SUMDB Service Usage Monitoring DataBase

UE User Equipment



12 Accronyms

| page 20

UID User ID

UTRAN UMTS Terrestrial Radio Access Network

VSA Vendor Specific Attribute

XML Extensible Markup Language

XSD XML Schema Definition




| page 21

13 Index

A

Accronyms • 17 Alarms • 16 B

Backward compatibility • 10 Benefits • 9 Benefits for the end user • 9 Benefits for the operator • 9 Billing • 14

C

Capacity • 14 Change History • 5 Changes in the feature • 6 Command • 16 Compliance • 15 D

Database changes • 14 E

Engineering considerations • 14 External interfaces • 16 F

Files • 14 Firmware • 10 Functionality • 11 G

General information • 8 GUI changes • 16 H

Hardware • 10 I

Interfaces • 16 Interworking features • 13

N Network impacts • 13 Network operations • 13 Nodes • 13 O

Operator interfaces • 16 Other requirements • 10

P

Parameters • 14 Products • 10 Provisioning • 14 R

References • 7

Requirements for using the feature • 10 Restrictions • 15 S

Software • 10 Statistics • 14 Subscriber interfaces • 16 Summary of Changes • 6 System attributes and parameters • 13 System performance • 13 U

Use cases • 12

Siemens Policy Manager

Documents

Transcript of Siemens Policy Manager