diameter specification acision

Diameter Input Interface

Interface Specification

Document Version: 3.0Document Status: ISSUEDDocument Issue Date: April 2011Approved by: Petr Moravec

Diameter_INTMAN_v3.0.doc Version: 3.0Security: Public Status: ISSUEDCopyright © Acision BV 2011 of 52

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.


Table of Contents

1 Introduction .........................................................................................................9

1.1 Overview.................................................................................................................................9

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

2.1 Message Format ................................................................................................................. 10

2.2 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

2.3 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


2.3.5 SMS Request ....................................................................................................... 29

2.3.6 SMS Response .................................................................................................... 37

2.3.7 MMS Request ...................................................................................................... 39

2.3.8 MMS Response ................................................................................................... 43

Appendix A...............................................................................................................46

A.1 Service Type ....................................................................................................................... 46

A.2 Request Type ...................................................................................................................... 46

A.3 CC Action ............................................................................................................................ 46

A.4 CC Flags.............................................................................................................................. 47

A.5 Traffic Type ......................................................................................................................... 47

A.6 Zone Status ......................................................................................................................... 48

A.7 SM Message Type .............................................................................................................. 48

A.8 SM Service Type ................................................................................................................. 48

A.9 MMS Message Type ........................................................................................................... 49

A.10 Message Class.................................................................................................................... 50

A.11 Content Class...................................................................................................................... 50


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


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


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 3rd

Party Applications.

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

Meaning/Used for Example

Courier Refers to keyboard key, system command, label, button, filename, window, or other computer component or output.

DATA directory contains...

Click Close button to...

<courier> Serves as placeholder for variable text that the user will replace as appropriate to its context.

Use file name <entity>.cfg for...

[] Refers user to external documentation listed in References section.

[ETSI 03.38]

Italic Emphasises new word or term of significance. Install procedure on a SUN T1.

% Denotes a Unix regular-user prompt for C shell. % ls

# Denotes a Unix super-user prompt for any shell. # ls

$ Denotes an OpenVMS Digital Command Language prompt.

$ dir

\ (Unix)or–(OpenVMS)

Denotes line continuation; the character should be ignored as the user types the example, and Enter should only be pressed after the last line.

% grep searchforthis \

data/*.dat

$ search [.data]*.dat -

searchforthis

- Bridges two keystrokes that should be pressed If Ctrl-C does not work, use Ctrl-Alt-


Typeface/ Symbol

Meaning/Used for Example

simultaneously. Del.

Denotes a “note”, a piece of text alongside the normal text requiring extra attention.

Note that the system is usually...


1 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.


2 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 e-mail address

1 E.164 (MSISDN)

2 IPv4 Address

3 IPv6 Address

4 Numeric Shortcode

5 Alphanumeric Shortcode

6 E.212 (e.g. IMSI)

7 SIP URI

8 Account ID

9 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.


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 3830 >

[ 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.


0 Route on GT

1 Route on SSN

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.


2.2.12 SCCP-Address AVP

The SCCP-Address AVP (AVP code 3003) is of type Grouped.


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 high-level classification of the commodity.


1 SMS

2 DATA

3 Content

4 MMS

5 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.


Commodity-Info :: = < AVP Header: 3011 3830 >

{ Commodity-Id }

[ Commodity-Sub-Id ]

[ Commodity-Description ]

2.2.17 Content-Type AVP

The Content-Type AVP (AVP code 3016) is of type Unsigned64 and it identifies the well-known media types. The values are taken from the OMNA WSP Content Type Codes database.


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.


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.


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.


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.


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.

Address 3000 Acision Grouped M, V P Y

Address-Data 3002 Acision UTF8String M, V P Y

Address-Domain 3066 Acision UTF8String M.V P Y

Address-Type 3001 Acision Enumerated M, V P Y

APN 3030 Acision UTF8String M, V P Y

Authorized-QoS 3031 Acision UTF8String M, V P Y

Billing-Code 3032 Acision UTF8String M, V P Y

CC-Flags 3028 Acision Enumerated M, V P Y

Cell-Id 3038 Acision OctetString M, V P Y

Charged-Address 3039 Acision Address M, V P Y

Charged-IMSI 3040 Acision Address M, V P Y

Commodity-Info 3011 Acision Grouped M, V P Y

Commodity-Description 3014 Acision UTF8String M, V P Y



Commodity-Id 3012 Acision Enumerated M, V P Y

Commodity-Sub-Id 3013 Acision UTF8String M, V P Y

Concatenation-Info 3018 Acision Grouped M, V P Y

Concatenation-Current-Segments

3020 Acision Unsigned32 M, V P Y

Concatenation-Max-Segments


Concatenation-Reference


Content-Info 3015 Acision Grouped M, V P Y

Content-Additional-Type 3017 Acision UTF8String M, V P Y

Content-Type 3016 Acision Unsigned64 M, V P Y

Content-Class 3051 Acision Enumerated M, V P Y

Content-Size 3065 Acision Unsigned32 M, V P Y

GGSN-Address 3052 Acision Address M, V P Y

Location 3053 Acision Address M, V P Y

Location-Area-Code 3054 Acision OctetString M, V P Y

Merchant 3055 Acision Address M, V P Y

MMS-Address 3056 Acision Address M, V P Y

MMS-Message-Class 3057 Acision Enumerated M, V P Y

MMS-Message-Size 3058 Acision Unsigned32 M, V P Y

MMS-Message-Type 3059 Acision Enumerated M, V P Y

Operator-Id 3060 Acision UTF8String M, V P Y

Originator-Address 3061 Acision Address M, V P Y

Originator-Global-Title 3062 Acision SCPP-Address M, V P Y

Originator-IMSI 3063 Acision Address M, V P Y

Originator-Point-Code 3064 Acision Unsigned32 M, V P Y

Payload-Info 3022 Acision Grouped M, V P Y

Payload-Encoding 3023 Acision Enumerated M, V P Y

Payload-Locking-Shift-Tab


Payload-Num-Chars 3025 Acision Unsigned32 M, V P Y

Payload-Single-Shift-Tab


Payload-Size 3024 Acision Unsigned32 M, V P Y

QoS 3033 Acision OctetString M, V P Y



Recipient-Address 3034 Acision Address M, V P Y

Recipient-Global-Title 3035 Acision SCPP-Address M, V P Y

Recipient-IMSI 3036 Acision Address M, V P Y

Recipient-Point-Code 3037 Acision Unsigned32 M, V P Y

SCCP-Address 3003 Acision Grouped M, V P Y

SCCP-GT-ADDR 3009 Acision OctetString M, V P Y

SCCP-GT-NAI 3007 Acision Unsigned32 M, V P Y

SCCP-GT-NP 3008 Acision Unsigned32 M, V P Y

SCCP-PC 3006 Acision Unsigned32 M, V P Y

SCCP-RI 3004 Acision Enumerated M, V P Y

SCCP-SSN 3005 Acision Unsigned32 M, V P Y

SCCP-TT 3010 Acision Unsigned32 M, V P Y

SGSN-Address 3041 Acision Address M, V P Y

SGSN-MCC-MNC 3029 Acision Address M, V P Y

SM-Msg-Type 3042 Acision Enumerated M, V P Y

SM-Service-Type 3043 Acision Enumerated M, V P Y

SMSC-Address 3044 Acision OctetString M, V P Y

Target-Address 3045 Acision Address M, V P Y

Tariff-Group 3046 Acision Unsigned32 M, V P Y

Traffic-Type 3047 Acision Enumerated M, V P Y

Validity-Period 3048 Acision Unsigned32 M, V P Y

Zone-Name 3049 Acision UTF8String M, V P Y

Zone-Status 3050 Acision Enumerated M, V P Y

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.


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

TypeCodeVendor

Description


AVP

TypeCodeVendor

Description

Session-Id

OctetString

263

This field identifies uniquely a session.

This must remain same for INITIAL, UPDATE and TERMINATE requests within a session.

CC-Request-Number

Unsigned32

415

This field uniquely identifies each request within a session.

As Session-Id AVPs are globally unique, the combination of Session-Id and CC-Request-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

Unsigned32

439

Service Identifier. Set to DATA. See A.1

CC-Request-Type

Enumerated

416

Contains the reason for sending the credit-control request message.

Possible values are INITIAL_REQUEST, UPDATE_REQUEST, TERMINATE_REQUEST or EVENT_REQUEST. See A.2

Requested-Action

Enumerated

436

Contains the requested action when the CC-Request-Type is set to EVENT_REQUEST. See A.3

CC-Flags

Enumerated

3028

Acision

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

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

Time

55

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

3GPP-MS-TimeZone

OctetString[4]

23

10415

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


AVP

TypeCodeVendor

Description

Charged-Address

Address

3039

Acision

Address of charged party (MSISDN).

Charged-IMSI

Address

3040

Acision

IMSI of charged party.

Originator-Address

Address

3061

Acision

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

QoS

OctetString

3033

Acision

Requested Quality of Service.

Traffic-Type

Enumerated

3047

Acision

Type of traffic being used. See A.5

APN

UTF8String

3030

Acision

Access Point Name.

Target-Address

Address

3045

Acision

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

GGSN-Address

Address

3052

Acision

GGSN IP Address of the request originator.


AVP

TypeCodeVendor

Description

SGSN-Address

Address

3041

Acision

SGSN IP Address of the request originator.

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

SGSN-MCC-MNC

Address

3029

Acision

SGSN_MCC_MNC of the request originator in E.164 format.

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

Location-Area-Code

OctetString

3054

Acision

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

This will be in format as follows:

<MCC><MNC><LAC>

Cell-Id

OctetString

3038

Acision

This field relates to Identity of the cell in which the served subscriber is located.

This will be in format as follows:

<MCC><MNC><LAC><CI>

Requested-Service-Unit

Grouped

437

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

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-Unit

Grouped

446

Used Service Units before or after the tariff switch.

This field is applicable only for UPDATE and TERMINATE requests.

Rating-Group

Unsigned32

432

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

This parameter is provided by the charging trigger point.

Operator-Id

UTF8String

3060

Acision

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.

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


AVP

TypeCodeVendor

Description

Zone-Name

UTF8String

3049

Acision

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

Zone-Status

Enumerated

3050

Acision

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

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 >

< Session-Id >

{ Result-Code }

{ Origin-Host }

{ Origin-Realm }


{ CC-Request-Type }


[ CC-Session-Failover ]

[ Granted-Service-Unit ]


[ 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 ]


*[ AVP ]

Table 2-3: Data Response – AVPs

AVP

TypeCodeVendor Id

Description

Session-Id

OctetString

263



CC-Request-Type

Enumerated

416

Contains the reason for sending the credit-control request message.

Possible values are INITIAL_REQUEST, UPDATE_REQUEST, TERMINATE_REQUEST or EVENT_REQUEST. See A.2

CC-Request-Number

Unsigned32

415




Service-Identifier

Unsigned32

439

Service Identifier. Set to DATA. See A.1

Result-Code

Unsigned32

268

Credit Control Response code. This field holds the status of charging request processed by ACE.

Granted-Service-Unit

Grouped

431

Granted Service Units.

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

Unsigned32

448

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


AVP

TypeCodeVendor Id

Description

Authorized-QoS

UTF8String

3031

Acision

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

Cost-Information

Grouped

423

This parameter will contain the cost of service returned by ACE.

Tariff-Group

Unsigned32

3046

Acision

Contains the tariff group identifier, returned by ACE.

Zone-Name

UTF8String

3049

Acision


Zone-Status

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.



< Session-Id >

{ Origin-Host }

{ Origin-Realm }




{ CC-Request-Type }




[ User-Name ]

[ Origin-State-Id ]

[ Event-Timestamp ]






[ Charged-Address]

[ Charged-IMSI ]

[ Location ]

[ Validity-Period ]

[ Merchant ]

[ APN ]

[ Commodity-Info ]

[ Target-Address ]

*[ Content-Info ]

[ Traffic-Type ]

[ Rating-Group ]

[ CC-Flags ]


*[ Proxy-Info ]

*[ Route-Record ]

*[ AVP ]

Table 2-4: Content Request – AVPs

AVP

TypeCodeVendor Id

Description

Session-Id

OctetString

263



Service-Identifier

Unsigned32

439

Service Identifier. Set to CONTENT. See A.1

CC-Request-Type

Enumerated

416

Contains the reason for sending the credit-control request message. Set to EVENT_REQUEST for CONTENT. See A.2

Requested-Action

Enumerated

436

Contains the requested action when the CC-Request-Type is set to EVENT_REQUEST.

Set to DIRECT_DEBITING for charging the service.

Set to REFUND_ACCOUNT for refunding the service.

See A.3


AVP

TypeCodeVendor Id

Description

CC-Flags

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

Time

55


3GPP-MS-TimeZone

OctetString[4]

23

10415


Charged-Address

Address

3039

Acision

Address of charged party (MSISDN). This is the buyer/user of the service.

Charged-IMSI

Address

3040

Acision


Location

Address

3053

Acision

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

Validity-Period

Unsigned32

3048

Acision

Contains the longest interval in hours, between a DEBIT and corresponding REFUND requests.

The value determines the minimum interval the request is stored in the cache on the ACE for REFUND operations.

Merchant

Address

3055

Acision

The address of the merchant selling the commodity or the service provider as Alphanumeric Shortcode.


AVP

TypeCodeVendor Id

Description

APN

UTF8String

3030

Acision

Access Point Name.

Commodity-Info

Grouped

3011

Acision

The commodity/service requested/used by the user.


Grouped

437

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.

E.g. Number of events for SMS & MMS, octets for DATA, CONTENT, MMS & CSD, time for DATA & CSD.

Target-Address

Address

3045

Acision

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

Content-Info

Grouped

3015

Acision

Type of content being accessed.

Traffic-Type

Enumerated

3047

Acision

Type of traffic being used. See A.5

Rating-Group

Unsigned32

432



2.3.4 Content Response





< Session-Id >

{ Result-Code }

{ Origin-Host }

{ Origin-Realm }


{ CC-Request-Type }





[ Rating-Group ]

[ Cost-Information]







[ Validity-Time]

[ Validity-Period ]

[ Tariff-Group ]

[ Zone-Name ]

[ Zone-Status ]

*[ Redirect-Host]



*[ Proxy-Info ]

*[ Route-Record ]

*[ Failed-AVP ]

*[ AVP ]

Table 2-5: Content Response – AVPs

AVP

TypeCodeVendor Id

Description

Session-Id

OctetString

263



CC-Request-Type

Enumerated

416

Contains the reason for sending the credit-control request message. Set to EVENT_REQUEST for CONTENT. See A.2


AVP

TypeCodeVendor Id

Description

CC-Request-Number

Unsigned32

415




Service-Identifier

Unsigned32

439

Service Identifier. Set to CONTENT. See A.1

Result-Code

Unsigned32

268


Validity-Period

Unsigned32

3048

Acision

Contains the longest interval in hours, between a DEBIT and corresponding REFUND requests.

The value determines the minimum interval the request is stored in the cache on the ACE for REFUND operations.

Granted-Service-Unit

Grouped

431

Granted Service Units.

Either time or octets can be filled for Data service.

Validity-Time

Unsigned32

448

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

Cost-Information

Grouped

423


Tariff-Group

Unsigned32

3046

Acision



AVP

TypeCodeVendor Id

Description

Zone-Name

UTF8String

3049

Acision

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

Zone-Status

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.



< Session-Id >

{ Origin-Host }

{ Origin-Realm }




{ CC-Request-Type }



[ User-Name ]

[ Origin-State-Id ]

[ Event-Timestamp ]






[ 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 ]


[ Concatenation-Info ]

[ Payload-Info]

[ Billing-Code ]

[ SMSC-Address ]

[ Rating-Group ]

[ SGSN-Address ]

[ CC-Flags ]


*[ Proxy-Info ]

*[ Route-Record ]

*[ AVP ]

Table 2-6: SMS Request – AVPs

AVP

TypeCodeVendor Id

Description

Session-Id

OctetString

263



Service-Identifier

Unsigned32

439

Service Identifier. Set to SMS. See A.1

CC-Request-Type

Enumerated

416

Set to EVENT_REQUEST for SMS. See A.2 for supported request types.

Requested-Action

Enumerated

436


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

CC-Flags

Enumerated

3028

Acision



See A.4

Event-Timestamp

Time

55



AVP

TypeCodeVendor Id

Description

3GPP-MS-TimeZone

OctetString[4]

23

10415


Charged-Address

Address

3039

Acision

Address of charged party. (MSISDN).

Charged-IMSI

Address

3040

Acision


Originator-Address

Address

3061

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

Originator-IMSI

Address

3063

Acision

IMSI of request originator in E.212 format.

Originator-Global-Title

SCPP-Address

3062

Acision

This field carries the originating Global Title (SCCP address).

Originator-Point-Code

Unsigned32

3064

Acision

This field carries the originating Point Code (SCCP address).

Recipient-Address

Address

3034

Acision

Address of the recipient.


AVP

TypeCodeVendor Id

Description

Recipient-IMSI

Address

3036

Acision

IMSI of recipient in E.212 format.

Recipient-Global-Title

SCPP-Address

3035

Acision

This field carries the terminating Global Title (SCCP address).

Recipient-Point-Code

Unsigned32

3037

Acision

This field carries the terminating Point Code (SCCP address).

SM-Msg-Type

Enumerated

3042

Acision

Specifies the type of SMS (e.g, MO, MT, AO, AT). See A.7

SM-Service-Type

Enumerated

3043

Acision

Specifies the type of SMS service (e.g. Buffered Notification, Delivery Notification, etc.). See A.8

Concatenation-Info

Concatenation

3018

Acision

Concatenation information related to one segment of a segmented message.

Payload-Info

Payload

3022

Acision

Encoding size in bytes and number of characters.

Billing-Code

UTF8String

3032

Acision

VAS Billing Code (e.g. billingFiledUCP or billingFieldSMPP in spbp).


AVP

TypeCodeVendor Id

Description

SMSC-Address

OctetString

3044

Acision

Address of the SMSC.


Grouped

437

Cost of service for rated requests.

Rating-Group

Unsigned32

432



SGSN-Address

Address

3041

Acision



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.


ACE/AFG3rd Party

ApplicationCS

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

CCA ( Result-Code =DIAMETER_SUCCESS)

Answer from the charging system

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

ACE/AFG3rd Party

ApplicationCS

CCR (O riginator-Address, Recipient-Address,SM -Msg-Type=M O,Concatenation -Current-Segm ent=1,Concatenation-Max-Segments=5,Requested-Action=DIRECT_DEBITING , etc) Request




CCR (O riginator-Address, Recipient-Address,SM -Msg-Type=M O,Concatenation -Current-Segm ent=5,Concatenation-Max-Segments=5,Requested-Action=DIRECT_DEBITING , etc)

Requestto the charging system

Answer from the charging systemCCA ( Result-Code =

DIAMETER _SUCCESS)

Figure 2: MO Concatenated Message – Charge All Segments Success


ACE/AFG3rd Party

ApplicationCS

CCR (O riginator-Address, Recipient-Address,SM -Msg-Type=M T,Concatenation-Current-Segm ent=1,Concatenation-Max-Segments=5,Requested-Action=DIRECT_DEBITING , etc) Request


CCA ( Result-Code =DIAMETER_SUCCESS/FAILURE )


CCR (O riginator-Address, Recipient-Address,SM -Msg-Type=M T,Concatenation-Current-Segm ent=5,Concatenation-Max-Segments=5,Requested-Action=DIRECT_DEBITING , etc)

Result of first segm ent issent backCCA ( Result-Code =

DIAMETER _SUCCESS/FAILURE)

Figure 3: MT Concatenated Message

2.3.5.2 Notifications

Following Figures describe notifications which are used for roaming.


ACE/AFG3rd Party

ApplicationCS

CCR (O riginator-Address, Recipient-Address,SM -Msg-Type=M T,Requested-Action=DIRECT_DEBITING , etc) Request




CCR (O riginator-Address, Recipient-Address,SM -Msg-Type=M T,SM -Service-Type=DELV_NOTIF, etc)

Destination MSC is checkedand the message is ignoredwhen it is the sam e aslocal.

CCA ( Result-Code =DIAMETER _SUCCESS

The new rate is recalculated and if destination M SC isroaming refund is performed.

Refund requestto the charging system


New debit requestto the charging system


Figure 4: MT Roaming Success


ACE/AFG3rd Party

ApplicationCS

CCR (O riginator-Address, Recipient-Address,SM -Msg-Type=M T,Requested-Action=DIRECT_DEBITING , etc) Request




CCR (O riginator-Address, Recipient-Address,SM -Msg-Type=M T,SM -Service-Type=DELV_NOTIF, etc)

Destination MSC is checkedand the message is ignoredwhen it is the sam e aslocal.

CCA ( Result-Code =DIAMETER _SUCCESS)

The new rate is recalculated and if destination M SC isroaming refund is performed.

Refund requestto the charging system


New debit requestto the charging system

An error answer from the charging system

The rate is stored locallyand retried later

Figure 5: MT Roaming Failure

2.3.6 SMS Response




< Session-Id >

{ Result-Code }

{ Origin-Host }

{ Origin-Realm }


{ CC-Request-Type }





[ Rating-Group ]


[ Cost-Information]







[ Tariff-Group ]

[ Zone-Name ]

[ Zone-Status ]

*[ Redirect-Host]



*[ Proxy-Info ]

*[ Route-Record ]

*[ Failed-AVP ]

*[ AVP ]

Table 2-7: SMS Response – AVPs

AVP

TypeCodeVendor Id

Description

Session-Id

OctetString

263



Service-Identifier

Unsigned32

439

Service Identifier. Set to SMS. See A.1

Result-Code

Unsigned32

268


Cost-Information

Grouped

423


Tariff-Group

Unsigned32

3046

Acision



AVP

TypeCodeVendor Id

Description

Zone-Name

UTF8String

3049

Acision


Zone-Status

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.



< Session-Id >

{ Origin-Host }

{ Origin-Realm }




{ CC-Request-Type }



[ User-Name ]

[ Origin-State-Id ]

[ Event-Timestamp ]






[ Charged-Address]

[ Charged-IMSI ]

[ Originator-Address]

[ GGSN-Address ]

[ SGSN-Address ]

[ SGSN-MCC-MNC ]

*[ Recipient-Address]

[ MMS-Address ]

[ MMS-Message-Type ]

[ MMS-Message-Size ]


[ MMS-Message-Class ]

[ Content-Class ]

*[ Content-Info ]

[ Billing-Code ]

[ Rating-Group ]

[ CC-Flags ]


*[ Proxy-Info ]

*[ Route-Record ]

*[ AVP ]

Table 2-8: MMS Request – AVPs

AVP

TypeCodeVendor Id

Description

Session-Id

OctetString

263



CC-Request-Number

Unsigned32

415

This field uniquely identifies each request within a multi-recipient MMS request, when MMSC split the whole request into multiple requests. Combination of Session-Id and CC-Request-Number) can be used to match responses with requests.

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

Unsigned32

439

Service Identifier. Set to MMS. See A.1

CC-Request-Type

Enumerated

416

Set to EVENT_REQUEST for MMS. See A.2

Requested-Action

Enumerated

436


Set to REFUND_ACCOUNT for refunding the service.

See A.3

CC-Flags

Enumerated

3028

Acision



See A.4


AVP

TypeCodeVendor Id

Description

Event-Timestamp

Time

55


3GPP-MS-TimeZone

OctetString[4]

23

10415


Charged-Address

Address

3039

Acision

Address of charged party (MSISDN).

Charged-IMSI

Address

3040

Acision


Originator-Address

Address

3061

Acision

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

GGSN-Address

Address

3052

Acision

GGSN IP Address of the request originator.

SGSN-Address

Address

3041

Acision



SGSN-MCC-MNC

Address

3029

Acision

SGSN_MCC_MNC of the request originator in E.164 format.

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


AVP

TypeCodeVendor Id

Description

Recipient-Address

Address

3034

Acision

List of recipients.

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

Address

3056

Acision

IP address or domain name of MMS Relay/Server.

MMS-Message-Type

Enumerated

3059

Acision

Type of message. See A.9

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

Unsigned32

3058

Acision

Total Message Size.

MMS-Message-Class

Enumerated

3057

Acision

Message Class. See A.10

Content-Class

Enumerated

3051

Acision

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

Content-Info

Grouped

3015

Acision

Details of individual content types in MMS.


AVP

TypeCodeVendor Id

Description

Billing-Code

UTF8String

3032

Acision

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


Grouped

437

Cost of service for rated requests.

Rating-Group

Unsigned32

432



2.3.8 MMS Response




< Session-Id >

{ Result-Code }

{ Origin-Host }

{ Origin-Realm }


{ CC-Request-Type }





[ Rating-Group ]

[ Cost-Information]







[ Tariff-Group ]

[ Zone-Name ]

[ Zone-Status ]

*[ Redirect-Host]




*[ Proxy-Info ]

*[ Route-Record ]

*[ Failed-AVP ]

*[ AVP ]

Table 2-9: MMS Response – AVPs

AVP

TypeCodeVendor Id

Description

Session-Id

OctetString

263



CC-Request-Number

Unsigned32

415

This field uniquely identifies each request within a multi-recipient MMS request, when MMSC split the whole request into multiple requests. Combination of Session-Id and CC-Request-Number can be used to match responses with requests.

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

Unsigned32

439

Service Identifier. Set to MMS. See A.1

Result-Code

Unsigned32

268


Cost-Information

Grouped

423


Tariff-Group

Unsigned32

3046

Acision


Zone-Name

UTF8String

3049

Acision



AVP

TypeCodeVendor Id

Description

Zone-Status

Enumerated

3050

Acision



Appendix A.

A.1 Service Type

Table A-1: Service Type

Value Name Description

0x01 SMS SMS service

0x02 DATA Session based DATA service

0x03 CONTENT CONTENT and event based DATA service

0x04 MMS MMS service

0x06 VOICE VOICE service

0x07 IMS IMS service

0x05 SYSTEM_EVENT Event within System. Used for EDR

A.2 Request Type

Table A-2: Request Type


0x01 INITIAL_REQUEST An Initial request is used to initiate a credit-control session, and contains credit control information that is relevant to the initiation.

0x02 UPDATE_REQUEST 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 re-authorization is needed at the expiry of the allocated quota or validity time.

0x03 TERMINATE_REQUEST A Termination request is sent to terminate a credit-control session and contains credit-control information relevant to the existing session.

0x04 EVENT_REQUEST An Event request is used when there is no need to maintain any credit-control session state in the credit-control 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.

A.3 CC Action

Table A-3: CC Action




0x00 DIRECT_DEBITING 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-Control-Answer command contains the debited units, the Cost-Information 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-Control-Answer 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-Control-Answer 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 Credit-Control-Answer Command.

A.4 CC Flags

Table A-4: CC Flags


0x00 HOT_BILLING Hot billing request.

0x01 FORCE ACE will charge the request locally if no billing system balance is available.

A.5 Traffic Type

Table A-5: Traffic Type


0x01 UDP User Datagram Protocol

0x02 TCP Transmission Control Protocol

0x03 FTP File Transfer Protocol

0x04 HTTP Hypertext Transfer Protocol

0x05 WSP Wireless Session Protocol

0x06 MMS Multimedia Message Service



0x07 WTLS Wireless Transaction Layer Security

0x08 SMTP Simple Mail Transfer Protocol

0x09 POP3 Post office Protocol 3

0x0A IMAP4 Internet Message Access Protocol

0x0B RTP Real Time Transport Protocol

0x0C RTSP Real Time Streaming Protocol

0x0D SMS Short Message Service

0x0E SFTP Secured File Transfer Protocol

0x0F HTTPS Hypertext Transfer Protocol Secure

0x10 SCTP Stream Control Transmission Protocol

A.6 Zone Status

Table A-6: Zone Status


0x01 IN Subscriber is inside Zone

0x02 OUT Subscriber is outside Zone

0x03 SUSPENDED Zone service is suspended

A.7 SM Message Type

Table A-7: SM Message Type


0x00 MO Mobile Originated

0x01 MT Mobile Terminated

0x02 AO Application Originated

0x03 AT Application Terminated

A.8 SM Service Type

Table A-8: SM Service Type


0x00 BUFF_NOTIF Buffered Notification

0x01 DELV_NOTIF Delivered Notification

0x02 U_DELIV_NOTIF Nondelivered Notification

0x03 U_COND_FWD Unconditional Forwarding



0x04 COND_FWD Conditional Forwarding

0x05 S_COND_FWD Switched Conditional Forwarding

0x06 SUB_BAR_LS Subscriber Barred Last Resort

0x07 MSG_BAR_LS Message Barred Last Resort

0x08 PROV Provisioning

0x09 RLY_PATH Reply Path

0x0A SMS_CMD SMS Command

0x0B EMAIL_CPY Email Copy

A.9 MMS Message Type

Table A-9: MMS Message Type


0x00 unknown Unknown message type.

0x01 m-send-req Please refer [OMA_2] for details.

0x02 m-send-conf Please refer [OMA_2] for details.

0x03 m-notification-ind Please refer [OMA_2] for details.

0x04 m-notifyresp-ind Please refer [OMA_2] for details.

0x05 m-retrieve-conf Please refer [OMA_2] for details.

0x06 m-acknowledge-ind Please refer [OMA_2] for details.

0x07 m-delivery-ind Please refer [OMA_2] for details.

0x08 m-read-rec-ind Please refer [OMA_2] for details.

0x09 m-read-orig-ind Please refer [OMA_2] for details.

0x0A m-forward-req Please refer [OMA_2] for details.

0x0B m-forward-conf Please refer [OMA_2] for details.

0x0C m-mbox-store-req Please refer [OMA_2] for details.

0x0D m-mbox-store-conf Please refer [OMA_2] for details.

0x0E m-mbox-view-req Please refer [OMA_2] for details.

0x0F m-mbox-view-conf Please refer [OMA_2] for details.

0x10 m-mbox-upload-req Please refer [OMA_2] for details.

0x11 m-mbox-upload-conf Please refer [OMA_2] for details.

0x12 m-mbox-delete-req Please refer [OMA_2] for details.

0x13 m-mbox-delete-conf Please refer [OMA_2] for details.

0x14 m-mbox-descr Please refer [OMA_2] for details.

0x15 m-delete-req Please refer [OMA_2] for details.

0x16 m-delete-conf Please refer [OMA_2] for details.

0x17 m-cancel-req Please refer [OMA_2] for details.

0x18 m-cancel-conf Please refer [OMA_2] for details.


A.10 Message Class

Table A-10: Message Class


0x00 Personal Personal Message

0x01 Advertisement Advertisement

0x02 Informational Information/Notifications

0x03 Auto Automatically generated messages

A.11 Content Class

Table A-11: Content Class


0x00 text Please refer [OMA_1] for details.

0x01 image-basic Please refer [OMA_1] for details.

0x02 image-rich Please refer [OMA_1] for details.

0x03 video-basic Please refer [OMA_1] for details.

0x04 video-rich Please refer [OMA_1] for details.

0x05 mega pixel Please refer [OMA_1] for details.

0x06 content-basic Please refer [OMA_1] for details.

0x07 content-rich Please refer [OMA_1] for details.


References

[1] [3GPP_32.299] 3GPP TS 32.299 V9.2.0: Diameter Charging Specification

[2] [RFC_4006] Diameter Credit-Control Application


Version History

Version Status Date Details of Changes Author(s) Approver(s)

0.1 DRAFT 15-03-2011 Initial version Jan Somr

0.2 DRAFT 25-03-2011 Doc template Lenka Strnadova

1.0 ISSUED 28-03-2011 Approved and issued version Petr Moravec

1.1 DRAFT 29-03-2011 Update after review Lenka Strnadova

2.0 ISSUED 31-03-2011 Approval Petr Moravec

1.2 DRAFT 07-04-2011 Updated after review Jan Somr

1.3-1.4 DRAFT 13-04-2011 Updated after review Jan Somr

2.5 DRAFT 18-04-2011 Version revision Lenka Strnadova

3.0 ISSUED 18-04-2011 Approval Ralph Woodman

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

diameter specification acision

Documents

prior written

roam ing refund

field uniquely

field identifies

diameter input

mt roaming

mt concatenated

coordinated