Diameter Input Interface

Interface Specification

Document Version: Document Status: Document Issue Date: Approved by:

3.0 ISSUED April 2011 Petr Moravec

Copyright Acision BV 2011 All rights reserved. This document is protected by international copyright law and may not be reprinted, reproduced, copied or utilised in whole or in part by any means including electronic, mechanical, or other means without the prior written consent of Acision BV. Whilst reasonable care has been taken by Acision BV to ensure the information contained herein is reasonably accurate, Acision BV shall not, under any circumstances be liable for any loss or damage (direct or consequential) suffered by any party as a result of the contents of this publication or the reliance of any party thereon or any inaccuracy or omission therein. The information in this document is therefore provided on an as is basis without warranty and is subject to change without further notice and cannot be construed as a commitment by Acision BV. The products mentioned in this document are identified by the names, trademarks, service marks and logos of their respective companies or organisations and may not be used in any advertising or publicity or in any other way whatsoever without the prior written consent of those companies or organisations and Acision BV.

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 2 of 52

Table of Contents
1 Introduction .........................................................................................................9
1.1 Overview.................................................................................................................................9

Interface Description ........................................................................................10

2.1 2.2 Message Format ................................................................................................................. 10 Additional AVPs................................................................................................................... 10 2.2.1 Address-Type AVP .............................................................................................. 10 2.2.2 Address-Data AVP............................................................................................... 10 2.2.3 Address-Domain AVP .......................................................................................... 11 2.2.4 Address AVP........................................................................................................ 11 2.2.5 SCCP-RI AVP ...................................................................................................... 11 2.2.6 SCCP-SSN AVP .................................................................................................. 11 2.2.7 SCCP-PC AVP..................................................................................................... 11 2.2.8 SCCP-GT-NAI AVP ............................................................................................. 11 2.2.9 SCCP-GT-NP AVP .............................................................................................. 11 2.2.10 SCCP-GT-ADDR AVP ......................................................................................... 11 2.2.11 SCCP-TT AVP ..................................................................................................... 11 2.2.12 SCCP-Address AVP ............................................................................................ 12 2.2.13 Commodity-Id AVP .............................................................................................. 12 2.2.14 Commodity-Sub-Id AVP....................................................................................... 12 2.2.15 Commodity-Description AVP ............................................................................... 12 2.2.16 Commodity-Info AVP ........................................................................................... 12 2.2.17 Content-Type AVP ............................................................................................... 12 2.2.18 Content-Additional-Type AVP .............................................................................. 13 2.2.19 Content-Size AVP ................................................................................................ 13 2.2.20 Content-Info AVP ................................................................................................. 13 2.2.21 Concatenation-Max-Segments AVP .................................................................... 13 2.2.22 Concatenation-Current-Segment AVP................................................................. 13 2.2.23 Concatenation-Reference AVP............................................................................ 13 2.2.24 Concatenation-Info AVP ...................................................................................... 13 2.2.25 Payload-Encoding AVP........................................................................................ 13 2.2.26 Payload-Size AVP................................................................................................ 13 2.2.27 Payload-Num-Chars AVP .................................................................................... 14 2.2.28 Payload-Single-Shift-Tab AVP............................................................................. 14 2.2.29 Payload-Locking-Shift-Tab AVP .......................................................................... 14 2.2.30 Payload-Info AVP................................................................................................. 14 Credit Control Messages..................................................................................................... 16 2.3.1 Data Request ....................................................................................................... 16 2.3.2 Data Response .................................................................................................... 21 2.3.3 Content Request .................................................................................................. 23 2.3.4 Content Response ............................................................................................... 26
Version: 3.0 Status: ISSUED Page 3 of 52

2.3

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

2.3.5 2.3.6 2.3.7 2.3.8

SMS Request ....................................................................................................... 29 SMS Response .................................................................................................... 37 MMS Request ...................................................................................................... 39 MMS Response ................................................................................................... 43

Appendix A...............................................................................................................46
A.1 A.2 A.3 A.4 A.5 A.6 A.7 A.8 A.9 Service Type ....................................................................................................................... 46 Request Type ...................................................................................................................... 46 CC Action ............................................................................................................................ 46 CC Flags.............................................................................................................................. 47 Traffic Type ......................................................................................................................... 47 Zone Status ......................................................................................................................... 48 SM Message Type .............................................................................................................. 48 SM Service Type ................................................................................................................. 48 MMS Message Type ........................................................................................................... 49

A.10 Message Class .................................................................................................................... 50 A.11 Content Class...................................................................................................................... 50

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 4 of 52

List of Tables
Table Preface-1: Typographic Conventions .............................................................................................7 Table 2-1: AVPs Summary Table .......................................................................................................... 14 Table 2-2: Data Request AVPs .......................................................................................................... 17 Table 2-3: Data Response AVPs ....................................................................................................... 22 Table 2-4: Content Request AVPs ..................................................................................................... 24 Table 2-5: Content Response AVPs .................................................................................................. 27 Table 2-6: SMS Request AVPs .......................................................................................................... 30 Table 2-7: SMS Response AVPs ....................................................................................................... 38 Table 2-8: MMS Request AVPs.......................................................................................................... 40 Table 2-9: MMS Response AVPs....................................................................................................... 44 Table A-1: Service Type ........................................................................................................................ 46 Table A-2: Request Type....................................................................................................................... 46 Table A-3: CC Action ............................................................................................................................. 46 Table A-4: CC Flags .............................................................................................................................. 47 Table A-5: Traffic Type .......................................................................................................................... 47 Table A-6: Zone Status.......................................................................................................................... 48 Table A-7: SM Message Type ............................................................................................................... 48 Table A-8: SM Service Type.................................................................................................................. 48 Table A-9: MMS Message Type ............................................................................................................ 49 Table A-10: Message Class .................................................................................................................. 50 Table A-11: Content Class .................................................................................................................... 50

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 5 of 52

List of Figures
Figure 1: MO Concatenated Message Charge First Segment Success ............................................ 34 Figure 2: MO Concatenated Message Charge All Segments Success ............................................. 34 Figure 3: MT Concatenated Message ................................................................................................... 35 Figure 4: MT Roaming Success ............................................................................................................ 36 Figure 5: MT Roaming Failure............................................................................................................... 37

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 6 of 52

Preface
Purpose
The purpose of this document is to define a Diameter Input Interface for DATA, CONTENT, SMS and MMS online charging.

Audience
The target audience of this document is Acision customers.

Scope
The scope of the document is to define a Diameter Input Interface for 3 Party Applications.
rd

Organisation
The document is structured as follows: Chapter 1 provides an Introduction. Chapter 2 provides a detailed Diameter Input Interface description.

Typographic Conventions
In this document, the typographic conventions listed in Table Preface-1 are used. Table Preface-1: Typographic Conventions
Typeface/ Symbol Courier Meaning/Used for Example

Refers to keyboard key, system command, label, button, filename, window, or other computer component or output. Serves as placeholder for variable text that the user will replace as appropriate to its context. Refers user to external documentation listed in References section. Emphasises new word or term of significance. Denotes a Unix regular-user prompt for C shell. Denotes a Unix super-user prompt for any shell. Denotes an OpenVMS Digital Command Language prompt. Denotes line continuation; the character should be ignored as the user types the example, and Enter should only be pressed after the last line.

DATA directory contains... Click Close button to... Use file name <entity>.cfg for... [ETSI 03.38]

<courier>

[]

Italic % # $

Install procedure on a SUN T1. % ls # ls $ dir

\ (Unix) or (OpenVMS) -

% grep searchforthis \ data/*.dat $ search [.data]*.dat searchforthis

Bridges two keystrokes that should be pressed

If Ctrl-C does not work, use Ctrl-Alt-

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 7 of 52

Typeface/ Symbol

Meaning/Used for simultaneously. Denotes a note, a piece of text alongside the normal text requiring extra attention.

Example Del. Note that the system is usually...

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 8 of 52

Introduction
This document provides the specification of the Acision Diameter Input Interface, its AVPs and messages.

1.1 Overview
Online charging for both events and sessions between a 3rd Party Application and the AFG/ACE should be performed using the Acision Diameter Input Interface which is based on the Ro reference point. The Ro reference point as described in the 3GPP TS 32.299 [1] is used with additional AVPs as defined in the present document.

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 9 of 52

Interface Description
2.1 Message Format
The format of Diameter messages defined in this document is based directly on the 3GPP TS 32.299 [1] document. The following symbols are used in the message format definitions: <AVP> indicates a mandatory AVP with a fixed position in the message. {AVP} indicates a mandatory AVP in the message. [AVP] indicates an optional AVP in the message. *AVP indicates that multiple occurrences of an AVP are possible.

2.2 Additional AVPs

This section describes all used AVPs which extend the base Ro reference point as described in the 3GPP TS 32.299 [1] document. 2.2.1 Address-Type AVP The Address-Type AVP (AVP code 3001) is of type Enumerated and indicates the type of address carried within an Address information AVP. It has the following values: 0 1 2 3 4 5 6 7 8 9 e-mail address E.164 (MSISDN) IPv4 Address IPv6 Address Numeric Shortcode Alphanumeric Shortcode E.212 (e.g. IMSI) SIP URI Account ID Other

2.2.2 Address-Data AVP The Address-Data AVP (AVP code 3002) is of type UTF8String and it contains the address information formatted according to the type of address indicated in the Address-Type AVP.

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 10 of 52

2.2.3 Address-Domain AVP The Address-Domain AVP (AVP code 3066) is of type UTF8String and it contains Domain Name, if the address is of type email/IPv4/IPv6/URI. This field shall optionally contain the MSC or SGSN address if the address is E.164 or E.212. 2.2.4 Address AVP The Address AVP (AVP code 3000) is of type Grouped. It has the following ABNF grammar: Address :: = < AVP Header: 3000 [ Address-Type ] [ Address-Data ] [ Address-Domain ] 2.2.5 SCCP-RI AVP The SCCP-RI AVP (AVP code 3004) is of type Enumerated and it contains the address indicator. It has the following values: 0 1 Route on GT Route on SSN 3830 >

2.2.6 SCCP-SSN AVP The SCCP-SSN AVP (AVP code 3005) is of type Unsigned32 and it contains the SSN. 2.2.7 SCCP-PC AVP The SCCP-PC AVP (AVP code 3006) is of type Unsigned32 and it contains the Point Code. 2.2.8 SCCP-GT-NAI AVP The SCCP-GT-NAI AVP (AVP code 3007) is of type Unsigned32 and it contains the GT Nature of address indicator. For possible values see [ITU-T_Q.713]. 2.2.9 SCCP-GT-NP AVP The SCCP-GT-NP AVP (AVP code 3008) is of type Unsigned32 and it contains the GT Numbering Plan. For possible values see [ITU-T_Q.713]. 2.2.10 SCCP-GT-ADDR AVP The SCCP-GT-ADDR AVP (AVP code 3009) is of type OctetString and it contains the GT address. 2.2.11 SCCP-TT AVP The SCCP-TT AVP (AVP code 3010) is of type Unsigned32 and it contains the Translation Type.

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 11 of 52

2.2.12 SCCP-Address AVP The SCCP-Address AVP (AVP code 3003) is of type Grouped. It has the following ABNF grammar: SCCP-Address :: = < [ [ [ [ [ [ [ AVP Header: 3003 3830 > SCCP-RI ] SCCP-SSN ] SCCP-PC ] SCCP-GT-NAI ] SCCP-GT-NP ] SCCP-GT-ADDR ] SCCP-TT ]

2.2.13 Commodity-Id AVP The Commodity-Id AVP (AVP code 3012) is of type Enumerated and it represents the highlevel classification of the commodity. It has the following values: 1 2 3 4 5 SMS DATA Content MMS CSD (Circuit Switched data service)

2.2.14 Commodity-Sub-Id AVP The Commodity-Sub-Id AVP (AVP code 3013) is of type UTF8String and it enables further classification of the commodity. E.g. it could be a picture for the MMS. MO_COPY for the SMS, etc. 2.2.15 Commodity-Description AVP The Commodity-Description AVP (AVP code 3014) is of type UTF8String and it contains text description of the commodity. 2.2.16 Commodity-Info AVP The Commodity-Info AVP (AVP code 3011) is of type Grouped and it represents the commodity/service requested/used by the user. It has the following ABNF grammar: Commodity-Info :: = { [ [ 2.2.17 Content-Type AVP The Content-Type AVP (AVP code 3016) is of type Unsigned64 and it identifies the wellknown media types. The values are taken from the OMNA WSP Content Type Codes database.
Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011 Version: 3.0 Status: ISSUED Page 12 of 52

< AVP Header: 3011 3830 > Commodity-Id } Commodity-Sub-Id ] Commodity-Description ]

2.2.18 Content-Additional-Type AVP The Content-Additional-Type AVP (AVP code 3017) is of type UTF8String and it contains any additional information beyond well-known media types. 2.2.19 Content-Size AVP The Content-Size AVP (AVP code 3065) is of type Unsigned32 and it contains size in bytes of the specified content. 2.2.20 Content-Info AVP The Content-Info AVP (AVP code 3015) is of type Grouped and it contains type of content being accessed. It has the following ABNF grammar: Content-Info :: = < AVP Header: 3015 3830 > { Content-Type } { Content-Size } [ Content-Additional-Type ] 2.2.21 Concatenation-Max-Segments AVP The Concatenation-Max-Segments AVP (AVP code 3019) is of type Unsigned32 and it contains the number of segments. 2.2.22 Concatenation-Current-Segment AVP The Concatenation-Current-Segment AVP (AVP code 3020) is of type Unsigned32 and it contains Sequence number of the current segment. 2.2.23 Concatenation-Reference AVP The Concatenation-Reference AVP (AVP code 3021) is of type Unsigned32 and it contains the reference number. 2.2.24 Concatenation-Info AVP The Concatenation-Info AVP (AVP code 3018) is of type Grouped. It has the following ABNF grammar: Concatenation-Info :: = < AVP Header: 3018 3830 > { Concatenation-Max-Segments } { Concatenation-Current-Segment } { Concatenation-Reference } 2.2.25 Payload-Encoding AVP The Payload-Encoding AVP (AVP code 3023) is of type Enumerated and it contains all possible encodings. 2.2.26 Payload-Size AVP The Payload-Size AVP (AVP code 3024) is of type Unsigned32 and it contains message payload size in bytes.

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 13 of 52

2.2.27 Payload-Num-Chars AVP The Payload-Num-Chars AVP (AVP code 3025) is of type Unsigned32 and it contains Number of characters in the message. 2.2.28 Payload-Single-Shift-Tab AVP The Payload-Single-Shift-Tab AVP (AVP code 3026) is of type Unsigned32 and it defines what National Language Single Shift Table is specified in the UDH of the SM (GSM specific, see [3GPP_23.038]). 2.2.29 Payload-Locking-Shift-Tab AVP The Payload-Locking-Shift-Tab AVP (AVP code 3027) is of type Unsigned32 and it defines what National Language Locking Shift Table is specified in the UDH of the SM (GSM specific, see [3GPP_23.038]). 2.2.30 Payload-Info AVP The Payload-Info AVP (AVP code 3022) is of type Grouped. It has the following ABNF grammar: Payload-Info :: = < AVP Header: 3022 3830 > { Payload-Encoding } { Payload-Size } { Payload-Num-Chars } [ Payload-Single-Shift-Tab ] [ Payload-Locking-Shift-Tab ]

Table 2-1: AVPs Summary Table

Name Code Vendor Type Must May May Encr. Y Y Y Y Y Y Y Y Y Y Y Y Y

Address Address-Data Address-Domain Address-Type APN Authorized-QoS Billing-Code CC-Flags Cell-Id Charged-Address Charged-IMSI Commodity-Info Commodity-Description

3000 3002 3066 3001 3030 3031 3032 3028 3038 3039 3040 3011 3014

Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision

Grouped UTF8String UTF8String Enumerated UTF8String UTF8String UTF8String Enumerated OctetString Address Address Grouped UTF8String

M, V M, V M.V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V

P P P P P P P P P P P P P

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 14 of 52

Name

Code

Vendor

Type

Must

May

May Encr. Y Y Y Y

Commodity-Id Commodity-Sub-Id Concatenation-Info Concatenation-CurrentSegments Concatenation-MaxSegments ConcatenationReference Content-Info Content-Additional-Type Content-Type Content-Class Content-Size GGSN-Address Location Location-Area-Code Merchant MMS-Address MMS-Message-Class MMS-Message-Size MMS-Message-Type Operator-Id Originator-Address Originator-Global-Title Originator-IMSI Originator-Point-Code Payload-Info Payload-Encoding Payload-Locking-ShiftTab Payload-Num-Chars Payload-Single-ShiftTab Payload-Size QoS

3012 3013 3018 3020

Acision Acision Acision Acision

Enumerated UTF8String Grouped Unsigned32

M, V M, V M, V M, V

P P P P

3019

Acision

Unsigned32

M, V

3021

Acision

Unsigned32

M, V

3015 3017 3016 3051 3065 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3022 3023 3027

Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision

Grouped UTF8String Unsigned64 Enumerated Unsigned32 Address Address OctetString Address Address Enumerated Unsigned32 Enumerated UTF8String Address SCPP-Address Address Unsigned32 Grouped Enumerated Unsigned32

M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V

P P P P P P P P P P P P P P P P P P P P P

Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y

3025 3026

Acision Acision

Unsigned32 Unsigned32

M, V M, V

P P

Y Y

3024 3033

Acision Acision

Unsigned32 OctetString

M, V M, V

P P

Y Y

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 15 of 52

Name

Code

Vendor

Type

Must

May

May Encr. Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y

Recipient-Address Recipient-Global-Title Recipient-IMSI Recipient-Point-Code SCCP-Address SCCP-GT-ADDR SCCP-GT-NAI SCCP-GT-NP SCCP-PC SCCP-RI SCCP-SSN SCCP-TT SGSN-Address SGSN-MCC-MNC SM-Msg-Type SM-Service-Type SMSC-Address Target-Address Tariff-Group Traffic-Type Validity-Period Zone-Name Zone-Status

3034 3035 3036 3037 3003 3009 3007 3008 3006 3004 3005 3010 3041 3029 3042 3043 3044 3045 3046 3047 3048 3049 3050

Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision Acision

Address SCPP-Address Address Unsigned32 Grouped OctetString Unsigned32 Unsigned32 Unsigned32 Enumerated Unsigned32 Unsigned32 Address Address Enumerated Enumerated OctetString Address Unsigned32 Enumerated Unsigned32 UTF8String Enumerated

M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V M, V

P P P P P P P P P P P P P P P P P P P P P P P

2.3 Credit Control Messages

This section describes credit control messages for Data, Content, SMS and MMS online charging. Three cases for control of user credit are distinguished by the 3GPP TS 32.299 [1] specification: IEC (Immediate Event Charging), ECUR (Event Charging with Unit Reservation), SCUR (Session Charging with Unit Reservation). For now only IEC and SCUR are supported for the following services: SMS, MMS and Content services IEC; Data service SCUR. Both IEC and SCUR call flow scenarios are described in more detail in the Figure 6.3.3 and Figure 6.3.5 of the 3GPP TS 32.299 [1] document. 2.3.1 Data Request The CCR message, indicated by the Command-Code field set to 272 is sent by the Client to the AFG/ACE in order to request credits for a data service.

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 16 of 52

The CCR message format is based on the 3GPP TS 32.299 [1] Ro reference point request message. <Credit-Control-Request> ::= < Diameter Header: 272, REQ, PXY > < { { { { { { { [ [ [ [ [ [ [ [ *[ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ *[ *[ *[ Session-Id > Origin-Host } Origin-Realm } Destination-Realm } Auth-Application-Id } Service-Context-Id } CC-Request-Type } CC-Request-Number } Destination-Host ] User-Name ] Origin-State-Id ] Event-Timestamp ] Service-Identifier ] Requested-Service-Unit ] Requested-Action ] Termination-Cause ] Used-Service-Unit ] 3GPP-MS-TimeZone ] Charged-Address ] Charged-IMSI ] Originator-Address ] QoS ] Traffic-Type ] APN ] Target-Address ] GGSN-Address ] SGSN-Address ] SGSN-MCC-MNC ] Location-Area-Code ] Cell-Id ] Rating-Group ] Operator-Id ] Zone-Name ] Zone-Status ] CC-Flags ] CC-Correlation-Id ] Proxy-Info ] Route-Record ] AVP ]

Table 2-2: Data Request AVPs

AVP Type Code Vendor Description

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 17 of 52

AVP Type Code Vendor Session-Id

Description

This field identifies uniquely a session.

OctetString 263 CC-Request-Number

This must remain same for INITIAL, UPDATE and TERMINATE requests within a session. This field uniquely identifies each request within a session.

Unsigned32 415

As Session-Id AVPs are globally unique, the combination of Session-Id and CCRequest-Number AVPs is also globally unique and can be used in matching messages with confirmations.

The value for this field must be set to 1 for INITIAL_REQUEST and incremented sequentially for each UPDATE_REQUEST within the session. TERMINATE_REQUEST will have the last number in the sequence. Service-Identifier Service Identifier. Set to DATA. See A.1

Unsigned32 439 CC-Request-Type Contains the reason for sending the credit-control request message.

Enumerated 416 Requested-Action

Possible values are INITIAL_REQUEST, UPDATE_REQUEST, TERMINATE_REQUEST or EVENT_REQUEST. See A.2 Contains the requested action when the CC-Request-Type is set to EVENT_REQUEST. See A.3

Enumerated 436 CC-Flags Set to HOT_BILLING if the message is a HotBilling (offline) request.

Enumerated 3028 Acision

Set to FORCE if the message is a force charge request. ACE will charge the request locally if no billing system balance is available.

See A.4 Event-Timestamp Represents the number of seconds since 0h on 1 January 1900 with respect to the Coordinated Universal Time (UTC).

Time 55 3GPP-MS-TimeZone The timezone is reported as related time zone, related to GMT, in multiples of quarter of an hour.

OctetString[4] 23 10415

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 18 of 52

AVP Type Code Vendor Charged-Address

Description

Address of charged party (MSISDN).

Address 3039 Acision Charged-IMSI IMSI of charged party.

Address 3040 Acision Originator-Address Address of request originator (charged party). (E.g. MSISDN, IPv4, IPv6, etc).

Address 3061 Acision QoS Requested Quality of Service.

OctetString 3033 Acision Traffic-Type Type of traffic being used. See A.5

Enumerated 3047 Acision APN Access Point Name.

UTF8String 3030 Acision Target-Address Address of target the user is trying to access. This field may contain both URL and Domain, or any one of them.

Address 3045 Acision GGSN-Address GGSN IP Address of the request originator.

Address 3052 Acision

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 19 of 52

AVP Type Code Vendor SGSN-Address

Description

SGSN IP Address of the request originator.

Address 3041 Acision SGSN-MCC-MNC

Note: One of SGSN or GGSN address must be present. Preferably SGSN address or both.

SGSN_MCC_MNC of the request originator in E.164 format.

Address 3029 Acision Location-Area-Code

This field shall be optionally used for roaming identification instead of SGSN-Address.

This field uniquely identifies a LA (Location Area) within a PLMN (Public Land Mobile Network).

OctetString 3054 Acision Cell-Id This will be in format as follows: <MCC><MNC><LAC> This field relates to Identity of the cell in which the served subscriber is located.

OctetString 3038 Acision Requested-Service-Unit

This will be in format as follows: <MCC><MNC><LAC><CI>

Requested Service Units. Also cost of service for rated requests can be provided.

Grouped 437 Used-Service-Unit

Note: This field is optional since the OCF may decide the units to be allocated. Allocation is not necessarily based on the requested service unit. Used Service Units before or after the tariff switch.

Grouped 446 Rating-Group

This field is applicable only for UPDATE and TERMINATE requests.

Contains the identifier of a rating group. All the services subject to the same rating type are part of the same rating group.

Unsigned32 432 Operator-Id This parameter is provided by the charging trigger point. Operator Identifier. This field will contain the operator identifier for a particular subscriber. The operator may be the base operator or an MVNO. Charging Trigger Point can supply this information if it is known.

UTF8String 3060 Acision This field is currently not used in ACE. Reserved for future use.

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 20 of 52

AVP Type Code Vendor Zone-Name

Description

Location of subscriber (zone name of subscriber as reported by ALG)

UTF8String 3049 Acision Zone-Status Location of subscriber (zone status of subscriber as reported by ALG). See A.6

Enumerated 3050 Acision

2.3.2 Data Response The CCA message, indicated by the Command-Code field set to 272 is sent by the AFG/ACE to the Client in order to reply to the CCR. The CCA message format is based on the 3GPP TS 32.299 [1] Ro reference point answer message. <CCA> ::= < Diameter Header: 272, PXY > < { { { { { { [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ *[ [ [ *[ *[ *[
Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Session-Id > Result-Code } Origin-Host } Origin-Realm } Auth-Application-Id } CC-Request-Type } CC-Request-Number } CC-Session-Failover ] Granted-Service-Unit ] Service-Identifier ] Rating-Group ] Cost-Information] Low-Balance-Indication ] Remaining-Balance ] Final-Unit-Indication ] Check-Balance-Result ] Credit-Control-Failure-Handling ] Direct-Debiting-Failure-Handling ] Validity-Time] Tariff-Group ] Zone-Name ] Zone-Status ] Redirect-Host] Redirect-Host-Usage ] Redirect-Max-Cache-Time ] Proxy-Info ] Route-Record ] Failed-AVP ]
Version: 3.0 Status: ISSUED Page 21 of 52

*[ AVP ]

Table 2-3: Data Response AVPs

AVP Type Code Vendor Id Session-Id This field identifies uniquely a session. Description

OctetString 263 CC-Request-Type

This must remain same for INITIAL, UPDATE and TERMINATE requests within a session. Contains the reason for sending the credit-control request message.

Enumerated 416 CC-Request-Number

Possible values are INITIAL_REQUEST, UPDATE_REQUEST, TERMINATE_REQUEST or EVENT_REQUEST. See A.2 This field uniquely identifies each request within a session.

Unsigned32 415

As Session-Id AVPs are globally unique, the combination of Session-Id and CCRequest-Number AVPs is also globally unique and can be used in matching messages with confirmations.

The value for this field must be set to 1 for INITIAL_REQUEST and incremented sequentially for each UPDATE_REQUEST within the session. TERMINATE_REQUEST will have the last number in the sequence. Service-Identifier Service Identifier. Set to DATA. See A.1

Unsigned32 439 Result-Code Credit Control Response code. This field holds the status of charging request processed by ACE.

Unsigned32 268 Granted-Service-Unit Granted Service Units.

Grouped 431

Currently either time or octets can be filled for Data service.

In future, it shall be possible to populate both time and octets in this field. This will be possible when ACE is extended to allocate both time and data in response to a single DATA charging request. Validity-Time Contains the validity time of the granted service units in seconds.

Unsigned32 448

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 22 of 52

AVP Type Code Vendor Id Authorized-QoS

Description

Allowed QoS for the allocated/granted quota. ACE returns this to UGC after the rating/quota allocation.

UTF8String 3031 Acision Cost-Information This parameter will contain the cost of service returned by ACE.

Grouped 423 Tariff-Group Contains the tariff group identifier, returned by ACE.

Unsigned32 3046 Acision Zone-Name Location of subscriber (zone name of subscriber as reported by ALG)

UTF8String 3049 Acision Zone-Status Location of subscriber (zone status of subscriber as reported by ALG). See A.6

Enumerated 3050 Acision

2.3.3 Content Request The CCR message, indicated by the Command-Code field set to 272 is sent by the Client to the AFG/ACE in order to request credits for a content service. The CCR message format is based on the 3GPP TS 32.299 [1] Ro reference point request message. <Credit-Control-Request> ::= < Diameter Header: 272, REQ, PXY > < { { { { { { { [
Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Session-Id > Origin-Host } Origin-Realm } Destination-Realm } Auth-Application-Id } Service-Context-Id } CC-Request-Type } CC-Request-Number } Destination-Host ]
Version: 3.0 Status: ISSUED Page 23 of 52

[ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ *[ [ [ [ [ *[ *[ *[

User-Name ] Origin-State-Id ] Event-Timestamp ] Service-Identifier ] Requested-Service-Unit ] Requested-Action ] Termination-Cause ] 3GPP-MS-TimeZone ] Charged-Address] Charged-IMSI ] Location ] Validity-Period ] Merchant ] APN ] Commodity-Info ] Target-Address ] Content-Info ] Traffic-Type ] Rating-Group ] CC-Flags ] CC-Correlation-Id ] Proxy-Info ] Route-Record ] AVP ]

Table 2-4: Content Request AVPs

AVP Type Code Vendor Id Session-Id This field identifies uniquely a session. Description

OctetString 263 Service-Identifier

This must remain same for INITIAL, UPDATE and TERMINATE requests within a session. Service Identifier. Set to CONTENT. See A.1

Unsigned32 439 CC-Request-Type Contains the reason for sending the credit-control request message. Set to EVENT_REQUEST for CONTENT. See A.2

Enumerated 416 Requested-Action Contains the requested action when the CC-Request-Type is set to EVENT_REQUEST.

Enumerated 436 Set to DIRECT_DEBITING for charging the service.

Set to REFUND_ACCOUNT for refunding the service.

See A.3 Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011 Version: 3.0 Status: ISSUED Page 24 of 52

AVP Type Code Vendor Id CC-Flags

Description

Set to HOT_BILLING if the message is a HotBilling (offline) request.

Enumerated 3028 Acision

Set FORCE if the message is a force charge request. ACE will charge the request locally if no billing system balance is available.

See A.4 Event-Timestamp Represents the number of seconds since 0h on 1 January 1900 with respect to the Coordinated Universal Time (UTC).

Time 55 3GPP-MS-TimeZone The timezone is reported as related time zone, related to GMT, in multiples of quarter of an hour.

OctetString[4] 23 10415 Charged-Address Address of charged party (MSISDN). This is the buyer/user of the service.

Address 3039 Acision Charged-IMSI IMSI of charged party.

Address 3040 Acision Location MSC or SGSN address of the charged party in E.164 format. If not provided, the subscriber location will be considered as HOME.

Address 3053 Acision Validity-Period Contains the longest interval in hours, between a DEBIT and corresponding REFUND requests.

Unsigned32 3048 Acision Merchant The address of the merchant selling the commodity or the service provider as Alphanumeric Shortcode. The value determines the minimum interval the request is stored in the cache on the ACE for REFUND operations.

Address 3055 Acision

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 25 of 52

AVP Type Code Vendor Id APN

Description

Access Point Name.

UTF8String 3030 Acision Commodity-Info The commodity/service requested/used by the user.

Grouped 3011 Acision Requested-Service-Unit Requested volume in time, octets or number of events. Also cost of service for rated requests can be provided. Only one of these fields shall be filled.

Grouped 437 E.g. Number of events for SMS & MMS, octets for DATA, CONTENT, MMS & CSD, time for DATA & CSD. Target-Address Address of target the user is trying to access. This field may contain both URL and Domain, or any one of them.

Address 3045 Acision Content-Info Type of content being accessed.

Grouped 3015 Acision Traffic-Type Type of traffic being used. See A.5

Enumerated 3047 Acision Rating-Group Contains the identifier of a rating group. All the services subject to the same rating type are part of the same rating group.

Unsigned32 432 This parameter is provided by the charging trigger point.

2.3.4 Content Response The CCA message, indicated by the Command-Code field set to 272 is sent by the AFG/ACE to the Client in order to reply to the CCR.

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 26 of 52

The CCA message format is based on the 3GPP TS 32.299 [1] Ro reference point answer message. <CCA> ::= < Diameter Header: 272, PXY > < { { { { { { [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ *[ [ [ *[ *[ *[ *[ Session-Id > Result-Code } Origin-Host } Origin-Realm } Auth-Application-Id } CC-Request-Type } CC-Request-Number } CC-Session-Failover ] Granted-Service-Unit ] Service-Identifier ] Rating-Group ] Cost-Information] Low-Balance-Indication ] Remaining-Balance ] Final-Unit-Indication ] Check-Balance-Result ] Credit-Control-Failure-Handling ] Direct-Debiting-Failure-Handling ] Validity-Time] Validity-Period ] Tariff-Group ] Zone-Name ] Zone-Status ] Redirect-Host] Redirect-Host-Usage ] Redirect-Max-Cache-Time ] Proxy-Info ] Route-Record ] Failed-AVP ] AVP ]

Table 2-5: Content Response AVPs

AVP Type Code Vendor Id Session-Id This field identifies uniquely a session. Description

OctetString 263 CC-Request-Type

This must remain same for INITIAL, UPDATE and TERMINATE requests within a session. Contains the reason for sending the credit-control request message. Set to EVENT_REQUEST for CONTENT. See A.2

Enumerated 416

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 27 of 52

AVP Type Code Vendor Id CC-Request-Number

Description

This field uniquely identifies each request within a session.

Unsigned32 415

As Session-Id AVPs are globally unique, the combination of Session-Id and CCRequest-Number AVPs is also globally unique and can be used in matching messages with confirmations.

The value for this field must be set to 1 for INITIAL_REQUEST and incremented sequentially for each UPDATE_REQUEST within the session. TERMINATE_REQUEST will have the last number in the sequence. Service-Identifier Service Identifier. Set to CONTENT. See A.1

Unsigned32 439 Result-Code Credit Control Response code. This field holds the status of charging request processed by ACE.

Unsigned32 268 Validity-Period Contains the longest interval in hours, between a DEBIT and corresponding REFUND requests.

Unsigned32 3048 Acision Granted-Service-Unit Granted Service Units. The value determines the minimum interval the request is stored in the cache on the ACE for REFUND operations.

Grouped 431 Validity-Time

Either time or octets can be filled for Data service.

Contains the validity time of the granted service units in seconds.

Unsigned32 448 Cost-Information This parameter will contain the cost of service returned by ACE.

Grouped 423 Tariff-Group Contains the tariff group identifier, returned by ACE.

Unsigned32 3046 Acision

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 28 of 52

AVP Type Code Vendor Id Zone-Name

Description

Location of subscriber (zone name of subscriber as reported by ALG).

UTF8String 3049 Acision Zone-Status Location of subscriber (zone status of subscriber as reported by ALG). See A.6

Enumerated 3050 Acision

2.3.5 SMS Request The CCR message, indicated by the Command-Code field set to 272 is sent by the Client to the AFG/ACE in order to request credits for a SMS service. The CCR message format is based on the 3GPP TS 32.299 [1] Ro reference point request message. <Credit-Control-Request> ::= < Diameter Header: 272, REQ, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Auth-Application-Id } { Service-Context-Id } { CC-Request-Type } { CC-Request-Number } [ Destination-Host ] [ User-Name ] [ Origin-State-Id ] [ Event-Timestamp ] [ Service-Identifier ] [ Requested-Service-Unit ] [ Requested-Action ] [ Termination-Cause ] [ 3GPP-MS-TimeZone ] [ Charged-Address] [ Charged-IMSI ] [ Originator-Address] [ Originator-IMSI ] [ Originator-Global-Title ] [ Originator-Point-Code ] [ Recipient-Address] [ Recipient-IMSI ] [ Recipient-Global-Title ] [ Recipient-Point-Code ] [ SM-Msg-Type ] [ SM-Service-Type ]
Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011 Version: 3.0 Status: ISSUED Page 29 of 52

[ [ [ [ [ [ [ [ *[ *[ *[

Concatenation-Info ] Payload-Info] Billing-Code ] SMSC-Address ] Rating-Group ] SGSN-Address ] CC-Flags ] CC-Correlation-Id ] Proxy-Info ] Route-Record ] AVP ]

Table 2-6: SMS Request AVPs

AVP Type Code Vendor Id Session-Id This field identifies uniquely a session. Description

OctetString 263 Service-Identifier

This must remain same for INITIAL, UPDATE and TERMINATE requests within a session. Service Identifier. Set to SMS. See A.1

Unsigned32 439 CC-Request-Type Set to EVENT_REQUEST for SMS. See A.2 for supported request types.

Enumerated 416 Requested-Action Set to DIRECT_DEBITING for charging the service.

Enumerated 436 CC-Flags

Set to REFUND_ACCOUNT for refunding the service. See A.3

Set to HOT_BILLING if the message is a HotBilling (offline) request.

Enumerated 3028 Acision

Set FORCE if the message is a force charge request. ACE will charge the request locally if no billing system balance is available.

See A.4 Event-Timestamp Represents the number of seconds since 0h on 1 January 1900 with respect to the Coordinated Universal Time (UTC).

Time 55

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 30 of 52

AVP Type Code Vendor Id 3GPP-MS-TimeZone

Description

The timezone is reported as related time zone, related to GMT, in multiples of quarter of an hour.

OctetString[4] 23 10415 Charged-Address Address of charged party. (MSISDN).

Address 3039 Acision Charged-IMSI IMSI of charged party.

Address 3040 Acision Originator-Address Address of request originator (charged party). (e.g. MSISDN, IPv4, IPv6, etc).

Address 3061 Originator-IMSI IMSI of request originator in E.212 format.

Address 3063 Acision Originator-Global-Title This field carries the originating Global Title (SCCP address).

SCPP-Address 3062 Acision Originator-Point-Code This field carries the originating Point Code (SCCP address).

Unsigned32 3064 Acision Recipient-Address Address of the recipient.

Address 3034 Acision

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 31 of 52

AVP Type Code Vendor Id Recipient-IMSI

Description

IMSI of recipient in E.212 format.

Address 3036 Acision Recipient-Global-Title This field carries the terminating Global Title (SCCP address).

SCPP-Address 3035 Acision Recipient-Point-Code This field carries the terminating Point Code (SCCP address).

Unsigned32 3037 Acision SM-Msg-Type Specifies the type of SMS (e.g, MO, MT, AO, AT). See A.7

Enumerated 3042 Acision SM-Service-Type Specifies the type of SMS service (e.g. Buffered Notification, Delivery Notification, etc.). See A.8

Enumerated 3043 Acision Concatenation-Info Concatenation information related to one segment of a segmented message.

Concatenation 3018 Acision Payload-Info Encoding size in bytes and number of characters.

Payload 3022 Acision Billing-Code VAS Billing Code (e.g. billingFiledUCP or billingFieldSMPP in spbp).

UTF8String 3032 Acision

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 32 of 52

AVP Type Code Vendor Id SMSC-Address

Description

Address of the SMSC.

OctetString 3044 Acision Requested-Service-Unit Cost of service for rated requests.

Grouped 437 Rating-Group Contains the identifier of a rating group. All the services subject to the same rating type are part of the same rating group.

Unsigned32 432 SGSN-Address This parameter is provided by the charging trigger point. SGSN IP Address of the request originator.

Address 3041 Acision

Note: One of SGSN or GGSN address must be present. Preferably SGSN address or both.

2.3.5.1

Concatenated Messages

There are two approaches for rating and charging of concatenated MO messages which are supported. The system can rate only the first segment of a message and ignore all the remaining segments (Figure 1) or rate all the segments separately (Figure 2). The MT concatenated messages are processed in the following way. Only the first segment is rated and sent to the charging system. The stored result of first segment is then sent to all subsequent segments (

Figure 3). The refund request is always applied to all segments. So, all money is refunded in case a single segment is not delivered.

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 33 of 52

3rd Party Application

ACE/AFG

CS

CCR (Originator-Address, Recipient-Address, SM-Msg-Type=MO, Concatenation-Current-Segment=1, Concatenation-Max-Segments=5, Requested-Action=DIRECT_DEBITING, etc)

Request to the charging system Answer from the charging system

CCA ( Result-Code = DIAMETER_SUCCESS)

CCR (Originator-Address, Recipient-Address, SM-Msg-Type=MO, Concatenation-Current-Segment=2 5, Concatenation-Max-Segments=5, Requested-Action=DIRECT_DEBITING, etc)

The remaining segments are ignored

Figure 1: MO Concatenated Message Charge First Segment Success

3 rd P arty A p plica tio n

A C E /A F G

CS

C C R (O riginator-A ddress , R ecipient-A ddress , S M -M sg -T ype =M O , C on catenation -C u rrent-S egm ent= 1, C oncatenation -M ax -S egm ents=5, R equested -A ction =D IR E C T _D E B ITIN G , etc)

R equest to the charging system

C C A ( R esult-C ode = D IA M E TE R _S U C C E S S )

A nsw er from the charging system

C C R (O riginator-A ddress , R ecipient-A ddress , S M -M sg -T ype =M O , C on catenation -C u rrent-S egm ent= 5, C oncatenation -M ax -S egm ents=5, R equested -A ction =D IR E C T _D E B ITIN G , etc)

R equest to the charging system

C C A ( R esult-C ode = D IA M E TE R _S U C C E S S )

A nsw er from the charging system

Figure 2: MO Concatenated Message Charge All Segments Success

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 34 of 52

3 rd P arty A p plica tio n

A C E /A F G

CS

C C R (O riginator-A ddress , R ecipient-A ddress , S M -M sg -T ype =M T , C on catenation -C u rrent-S egm ent= 1, C oncatenation -M ax-S egm ents=5, R equested-A ction =D IR E C T _D E B ITIN G , etc)

R equest to the charging system

C C A ( R esult-C ode = D IA M E TE R _S U C C E S S /F A ILU R E )

A nsw er from the charging system

C C R (O riginator-A ddress , R ecipient-A ddress , S M -M sg -T ype =M T , C on catenation -C u rrent-S egm ent= 5, C oncatenation -M ax-S egm ents=5, R equested-A ction =D IR E C T _D E B ITIN G , etc)

C C A ( R esult-C ode = D IA M E TE R _S U C C E S S /FA ILU R E )

R esult of first segm ent is sent back

Figure 3: MT Concatenated Message

2.3.5.2

Notifications

Following Figures describe notifications which are used for roaming.

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 35 of 52

3 rd P arty A p plica tio n

A C E /A F G

CS

C C R (O riginator-A ddress , R ecipient-A ddress , S M -M sg -T ype =M T , R equested-A ction =D IR E C T _D E B ITIN G , etc)

R equest to the charging system

C C A ( R esult-C ode = D IA M E TE R _S U C C E S S )

A nsw er from the charging system

C C R (O riginator-A ddress , R ecipient-A ddress , S M -M sg -T ype =M T , S M -S ervice-Type= D E LV _N O T IF , etc)

D estination M S C is checked and the m essage is ignored w hen it is the sam e as local. T he new rate is recalculated and if destination M S C is roam ing refund is perform ed. R efund request to the charging system A nsw er from the charging system N ew debit request to the charging system A nsw er from the charging system

C C A ( R esult-C ode = D IA M E TE R _S U C C E S S

Figure 4: MT Roaming Success

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 36 of 52

3 rd P arty A p plica tio n

A C E /A F G

CS

C C R (O riginator-A ddress , R ecipient-A ddress , S M -M sg -T ype =M T , R equested-A ction =D IR E C T _D E B ITIN G , etc)

R equest to the charging system

C C A ( R esult-C ode = D IA M E TE R _S U C C E S S )

A nsw er from the charging system

C C R (O riginator-A ddress , R ecipient-A ddress , S M -M sg -T ype =M T , S M -S ervice-Type= D E LV _N O T IF , etc)

D estination M S C is checked and the m essage is ignored w hen it is the sam e as local. T he new rate is recalculated and if destination M S C is roam ing refund is perform ed. R efund request to the charging system A nsw er from the charging system N ew debit request to the charging system A n error answ er from the charging system The rate is stored locally and retried later

C C A ( R esult-C ode = D IA M E TE R _S U C C E S S )

Figure 5: MT Roaming Failure

2.3.6 SMS Response The CCA message, indicated by the Command-Code field set to 272 is sent by the AFG/ACE to the Client in order to reply to the CCR. The CCA message format is based on the 3GPP TS 32.299 [1] Ro reference point answer message. <CCA> ::= < Diameter Header: 272, PXY > < { { { { { { [ [ [ [
Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Session-Id > Result-Code } Origin-Host } Origin-Realm } Auth-Application-Id } CC-Request-Type } CC-Request-Number } CC-Session-Failover ] Granted-Service-Unit ] Service-Identifier ] Rating-Group ]
Version: 3.0 Status: ISSUED Page 37 of 52

[ [ [ [ [ [ [ [ [ [ *[ [ [ *[ *[ *[ *[

Cost-Information] Low-Balance-Indication ] Remaining-Balance ] Final-Unit-Indication ] Check-Balance-Result ] Credit-Control-Failure-Handling ] Direct-Debiting-Failure-Handling ] Tariff-Group ] Zone-Name ] Zone-Status ] Redirect-Host] Redirect-Host-Usage ] Redirect-Max-Cache-Time ] Proxy-Info ] Route-Record ] Failed-AVP ] AVP ]

Table 2-7: SMS Response AVPs

AVP Type Code Vendor Id Session-Id This field identifies uniquely a session. Description

OctetString 263 Service-Identifier

This must remain same for INITIAL, UPDATE and TERMINATE requests within a session. Service Identifier. Set to SMS. See A.1

Unsigned32 439 Result-Code Credit Control Response code. This field holds the status of charging request processed by ACE.

Unsigned32 268 Cost-Information This parameter will contain the cost of service returned by ACE.

Grouped 423 Tariff-Group Contains the tariff group identifier, returned by ACE.

Unsigned32 3046 Acision

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 38 of 52

AVP Type Code Vendor Id Zone-Name

Description

Location of subscriber (zone name of subscriber as reported by ALG)

UTF8String 3049 Acision Zone-Status Location of subscriber (zone status of subscriber as reported by ALG). See A.6

Enumerated 3050 Acision

2.3.7 MMS Request The CCR message, indicated by the Command-Code field set to 272 is sent by the Client to the AFG/ACE in order to request credits for a MMS service. The CCR message format is based on the 3GPP TS 32.299 [1] Ro reference point request message. <Credit-Control-Request> ::= < Diameter Header: 272, REQ, PXY > < { { { { { { { [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ *[ [ [ [
Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Session-Id > Origin-Host } Origin-Realm } Destination-Realm } Auth-Application-Id } Service-Context-Id } CC-Request-Type } CC-Request-Number } Destination-Host ] User-Name ] Origin-State-Id ] Event-Timestamp ] Service-Identifier ] Requested-Service-Unit ] Requested-Action ] Termination-Cause ] 3GPP-MS-TimeZone ] Charged-Address] Charged-IMSI ] Originator-Address] GGSN-Address ] SGSN-Address ] SGSN-MCC-MNC ] Recipient-Address] MMS-Address ] MMS-Message-Type ] MMS-Message-Size ]
Version: 3.0 Status: ISSUED Page 39 of 52

[ [ *[ [ [ [ [ *[ *[ *[

MMS-Message-Class ] Content-Class ] Content-Info ] Billing-Code ] Rating-Group ] CC-Flags ] CC-Correlation-Id ] Proxy-Info ] Route-Record ] AVP ]

Table 2-8: MMS Request AVPs

AVP Type Code Vendor Id Session-Id This field identifies uniquely a session. Description

OctetString 263 CC-Request-Number

This must remain same for INITIAL, UPDATE and TERMINATE requests within a session. This field uniquely identifies each request within a multi-recipient MMS request, when MMSC split the whole request into multiple requests. Combination of SessionId and CC-Request-Number) can be used to match responses with requests.

Unsigned32 415 The value for this field must be set to 1 for the request for first recipient and incremented sequentially for requests for each recipient until the last recipient. Service Identifier. Set to MMS. See A.1

Service-Identifier

Unsigned32 439 CC-Request-Type Set to EVENT_REQUEST for MMS. See A.2

Enumerated 416 Requested-Action Set to DIRECT_DEBITING for charging the service.

Enumerated 436

Set to REFUND_ACCOUNT for refunding the service.

See A.3 CC-Flags Set to HOT_BILLING if the message is a HotBilling (offline) request.

Enumerated 3028 Acision

Set FORCE if the message is a force charge request. ACE will charge the request locally if no billing system balance is available.

See A.4

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 40 of 52

AVP Type Code Vendor Id Event-Timestamp

Description

Represents the number of seconds since 0h on 1 January 1900 with respect to the Coordinated Universal Time (UTC).

Time 55 3GPP-MS-TimeZone The timezone is reported as related time zone, related to GMT, in multiples of quarter of an hour.

OctetString[4] 23 10415 Charged-Address Address of charged party (MSISDN).

Address 3039 Acision Charged-IMSI IMSI of charged party.

Address 3040 Acision Originator-Address Address of request originator (charged party). (e.g. MSISDN, IPv4, IPv6, etc).

Address 3061 Acision GGSN-Address GGSN IP Address of the request originator.

Address 3052 Acision SGSN-Address SGSN IP Address of the request originator.

Address 3041 Acision SGSN-MCC-MNC

Note: One of SGSN or GGSN address must be present. Preferably SGSN address or both.

SGSN_MCC_MNC of the request originator in E.164 format.

Address 3029 Acision

This field shall be optionally used for roaming identification instead of SGSNAddress.

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 41 of 52

AVP Type Code Vendor Id Recipient-Address

Description

List of recipients.

Address 3034 Acision

If the locations of recipients are known, Address-Domain avp of Address for each recipient must be filled with the location information.

List size must be 1 for one-to-one MMS or when MMSC splits the multi-recipient message into separate messages for each recipient. MMS-Address IP address or domain name of MMS Relay/Server.

Address 3056 Acision MMS-Message-Type Type of message. See A.9

Enumerated 3059 Acision

The enumeration shall be set to unknown (0x00) when the charging trigger point is not aware of the Message Type.

For e.g. UGC shall set the enumeration to unknown (0x00) for messages other than MM1 (i.e. MM3/MM4/MM7) MMS-Message-Size Total Message Size.

Unsigned32 3058 Acision MMS-Message-Class Message Class. See A.10

Enumerated 3057 Acision Content-Class Content of the MM to the highest content class to which the MM belongs, as defined in OMA - MMS Encapsulation. See A.11

Enumerated 3051 Acision Content-Info Details of individual content types in MMS.

Grouped 3015 Acision

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 42 of 52

AVP Type Code Vendor Id Billing-Code

Description

This field shall contain the VAS Billing Code / Service Descriptor information.

UTF8String 3032 Acision Requested-Service-Unit Cost of service for rated requests.

Grouped 437 Rating-Group Contains the identifier of a rating group. All the services subject to the same rating type are part of the same rating group.

Unsigned32 432 This parameter is provided by the charging trigger point.

2.3.8 MMS Response The CCA message, indicated by the Command-Code field set to 272 is sent by the AFG/ACE to the Client in order to reply to the CCR. The CCA message format is based on the 3GPP TS 32.299 [1] Ro reference point answer message. <CCA> ::= < Diameter Header: 272, PXY > < { { { { { { [ [ [ [ [ [ [ [ [ [ [ [ [ [ *[ [ [
Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Session-Id > Result-Code } Origin-Host } Origin-Realm } Auth-Application-Id } CC-Request-Type } CC-Request-Number } CC-Session-Failover ] Granted-Service-Unit ] Service-Identifier ] Rating-Group ] Cost-Information] Low-Balance-Indication ] Remaining-Balance ] Final-Unit-Indication ] Check-Balance-Result ] Credit-Control-Failure-Handling ] Direct-Debiting-Failure-Handling ] Tariff-Group ] Zone-Name ] Zone-Status ] Redirect-Host] Redirect-Host-Usage ] Redirect-Max-Cache-Time ]
Version: 3.0 Status: ISSUED Page 43 of 52

*[ *[ *[ *[

Proxy-Info ] Route-Record ] Failed-AVP ] AVP ]

Table 2-9: MMS Response AVPs

AVP Type Code Vendor Id Session-Id This field identifies uniquely a session. Description

OctetString 263 CC-Request-Number

This must remain same for INITIAL, UPDATE and TERMINATE requests within a session. This field uniquely identifies each request within a multi-recipient MMS request, when MMSC split the whole request into multiple requests. Combination of SessionId and CC-Request-Number can be used to match responses with requests.

Unsigned32 415 The value for this field must be set to 1 for the request for first recipient and incremented sequentially for requests for each recipient until the last recipient. Service Identifier. Set to MMS. See A.1

Service-Identifier

Unsigned32 439 Result-Code Credit Control Response code. This field holds the status of charging request processed by ACE.

Unsigned32 268 Cost-Information This parameter will contain the cost of service returned by ACE.

Grouped 423 Tariff-Group Contains the tariff group identifier, returned by ACE.

Unsigned32 3046 Acision Zone-Name Location of subscriber (zone name of subscriber as reported by ALG)

UTF8String 3049 Acision

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 44 of 52

AVP Type Code Vendor Id Zone-Status

Description

Location of subscriber (zone status of subscriber as reported by ALG). See A.6

Enumerated 3050 Acision

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 45 of 52

Appendix A.
A.1 Service Type
Table A-1: Service Type
Value 0x01 0x02 0x03 0x04 0x06 0x07 0x05 Name SMS DATA CONTENT MMS VOICE IMS SYSTEM_EVENT Description SMS service Session based DATA service CONTENT and event based DATA service MMS service VOICE service IMS service Event within System. Used for EDR

A.2 Request Type

Table A-2: Request Type
Value 0x01 Name INITIAL_REQUEST Description An Initial request is used to initiate a credit-control session, and contains credit control information that is relevant to the initiation. An Update request contains credit-control information for an existing credit-control session. Update credit-control requests should be sent every time a credit-control reauthorization is needed at the expiry of the allocated quota or validity time. A Termination request is sent to terminate a credit-control session and contains credit-control information relevant to the existing session. An Event request is used when there is no need to maintain any credit-control session state in the creditcontrol server. This request contains all information relevant to the service, and is the only request of the service. The Requested- Action AVP must be included in the request message when CC-Request-Type is set to EVENT_REQUEST.

0x02

UPDATE_REQUEST

0x03

TERMINATE_REQUEST

0x04

EVENT_REQUEST

A.3 CC Action
Table A-3: CC Action
Value Name Description

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 46 of 52

Value 0x00

Name DIRECT_DEBITING

Description This indicates a request to decrease the end user's account according to information specified in the Requested-Service-Unit AVP.

The Granted-Service-Unit AVP in the Credit-ControlAnswer command contains the debited units, the CostInformation AVP indicates the cost of the service and the Remaining-Balance AVP may be also included. 0x01 REFUND_ACCOUNT This indicates a request to increase the end user's account according to information specified in the Requested-Service-Unit AVP.

The Granted-Service-Unit AVP in the Credit-ControlAnswer command contains the refunded units. 0x02 CHECK_BALANCE This indicates a balance check request. In this case, the checking of the account balance is done without any credit reservation from the account.

The Check-Balance-Result AVP in the Credit-ControlAnswer command contains the result of the balance check. 0x03 PRICE_ENQUIRY This indicates a price enquiry request. In this case, neither checking of the account balance nor reservation from the account will be done; only the price of the service will be returned in the Cost-Information AVP in the CreditControl-Answer Command.

A.4 CC Flags
Table A-4: CC Flags
Value 0x00 0x01 Name HOT_BILLING FORCE Description Hot billing request. ACE will charge the request locally if no billing system balance is available.

A.5 Traffic Type

Table A-5: Traffic Type
Value 0x01 0x02 0x03 0x04 0x05 0x06 Name UDP TCP FTP HTTP WSP MMS Description User Datagram Protocol Transmission Control Protocol File Transfer Protocol Hypertext Transfer Protocol Wireless Session Protocol Multimedia Message Service

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 47 of 52

Value 0x07 0x08 0x09 0x0A 0x0B 0x0C 0x0D 0x0E 0x0F 0x10

Name WTLS SMTP POP3 IMAP4 RTP RTSP SMS SFTP HTTPS SCTP

Description Wireless Transaction Layer Security Simple Mail Transfer Protocol Post office Protocol 3 Internet Message Access Protocol Real Time Transport Protocol Real Time Streaming Protocol Short Message Service Secured File Transfer Protocol Hypertext Transfer Protocol Secure Stream Control Transmission Protocol

A.6 Zone Status

Table A-6: Zone Status
Value 0x01 0x02 0x03 Name IN OUT SUSPENDED Description Subscriber is inside Zone Subscriber is outside Zone Zone service is suspended

A.7 SM Message Type

Table A-7: SM Message Type
Value 0x00 0x01 0x02 0x03 Name MO MT AO AT Description Mobile Originated Mobile Terminated Application Originated Application Terminated

A.8 SM Service Type

Table A-8: SM Service Type
Value 0x00 0x01 0x02 0x03 Name BUFF_NOTIF DELV_NOTIF U_DELIV_NOTIF U_COND_FWD Description Buffered Notification Delivered Notification Nondelivered Notification Unconditional Forwarding

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 48 of 52

Value 0x04 0x05 0x06 0x07 0x08 0x09 0x0A 0x0B

Name COND_FWD S_COND_FWD SUB_BAR_LS MSG_BAR_LS PROV RLY_PATH SMS_CMD EMAIL_CPY

Description Conditional Forwarding Switched Conditional Forwarding Subscriber Barred Last Resort Message Barred Last Resort Provisioning Reply Path SMS Command Email Copy

A.9 MMS Message Type

Table A-9: MMS Message Type
Value 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0A 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 Name unknown m-send-req m-send-conf m-notification-ind m-notifyresp-ind m-retrieve-conf m-acknowledge-ind m-delivery-ind m-read-rec-ind m-read-orig-ind m-forward-req m-forward-conf m-mbox-store-req m-mbox-store-conf m-mbox-view-req m-mbox-view-conf m-mbox-upload-req m-mbox-upload-conf m-mbox-delete-req m-mbox-delete-conf m-mbox-descr m-delete-req m-delete-conf m-cancel-req m-cancel-conf Description Unknown message type. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details. Please refer [OMA_2] for details.

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 49 of 52

A.10 Message Class

Table A-10: Message Class
Value 0x00 0x01 0x02 0x03 Name Personal Advertisement Informational Auto Description Personal Message Advertisement Information/Notifications Automatically generated messages

A.11 Content Class

Table A-11: Content Class
Value 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07 Name text image-basic image-rich video-basic video-rich mega pixel content-basic content-rich Description Please refer [OMA_1] for details. Please refer [OMA_1] for details. Please refer [OMA_1] for details. Please refer [OMA_1] for details. Please refer [OMA_1] for details. Please refer [OMA_1] for details. Please refer [OMA_1] for details. Please refer [OMA_1] for details.

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 50 of 52

References
[1] [2] [3GPP_32.299] 3GPP TS 32.299 V9.2.0: Diameter Charging Specification [RFC_4006] Diameter Credit-Control Application

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 51 of 52

Version History
Version 0.1 0.2 1.0 1.1 2.0 1.2 1.3-1.4 2.5 3.0 Status DRAFT DRAFT ISSUED DRAFT ISSUED DRAFT DRAFT DRAFT ISSUED Date 15-03-2011 25-03-2011 28-03-2011 29-03-2011 31-03-2011 07-04-2011 13-04-2011 18-04-2011 18-04-2011 Details of Changes Initial version Doc template Approved and issued version Update after review Approval Updated after review Updated after review Version revision Approval Jan Somr Jan Somr Lenka Strnadova Ralph Woodman Lenka Strnadova Petr Moravec Author(s) Jan Somr Lenka Strnadova Petr Moravec Approver(s)

Document derived from Template Version 6.0 Generic Document Template Standard (APL_DOC_GENERIC_TEMPLATE_STANDARD.dot).

Diameter_INTMAN_v3.0.doc Security: Public Copyright Acision BV 2011

Version: 3.0 Status: ISSUED Page 52 of 52