OCS DCC Interface Reference (Multimedia Message Charging Process EventID ...

OCS
DCC
Reference(Multimedia
Charging Process)
Issue
01
Date
2013-03-05
HUAWEI TECHNOLOGIES CO., LTD.
Interface
Message
Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2013-03-05)
Huawei Proprietary and Confidential

Copyright Huawei
Technologies Co., Ltd.
OCS
DCC Interface Reference(Multimedia Message Charging
Process)
Contents
Contents
1 Multimedia Message Charging Process...........................................1
1.1 Interaction Process.............................................................................................................................................1
1.2 Parameter Description........................................................................................................................................2
1.2.1 Parameters Description of First CCR{Event}..........................................................................................3
1.2.2 Parameters Description of First CCA{Event}..........................................................................................4
1.2.3 Parameters Description of Second CCR{Event}.....................................................................................5
1.2.4 Parameters Description of Second CCA{Event}.....................................................................................6
1.3 AVP Description.................................................................................................................................................7
1.3.1 3GPP-MS-TimeZone AVP........................................................................................................................7
1.3.2 Event-Timestamp AVP.............................................................................................................................8
1.3.3 Auth-Application-Id AVP.........................................................................................................................8
1.3.4 Session-Id AVP.........................................................................................................................................9
1.3.5 Origin-Host AVP.......................................................................................................................................9
1.3.6 Result-Code AVP....................................................................................................................................10
1.3.7 Destination-Realm AVP..........................................................................................................................10
1.3.8 Destination-Host AVP.............................................................................................................................11
1.3.9 Origin-Realm AVP..................................................................................................................................11
1.3.10 CC-Request-Number AVP....................................................................................................................11
1.3.11 CC-Request-Type AVP.........................................................................................................................12
1.3.12 CC-Service-Specific-Units AVP...........................................................................................................12
1.3.13 Requested-Action AVP.........................................................................................................................13
1.3.14 Service-Identifier AVP..........................................................................................................................14
1.3.15 Subscription-Id AVP.............................................................................................................................14
1.3.16 Subscription-Id-Data AVP....................................................................................................................15
1.3.17 Used-Service-Unit AVP........................................................................................................................15
1.3.18 Subscription-Id-Type AVP....................................................................................................................16
1.3.19 Service-Context-Id AVP.......................................................................................................................17
1.3.20 Service-Information AVP.....................................................................................................................17
1.3.21 PS-Information AVP.............................................................................................................................18
1.3.22 MMS-Information AVP........................................................................................................................19
1.3.23 Originator-Address AVP.......................................................................................................................20
1.3.24 Address-Data AVP................................................................................................................................20
Issue 01 (2013-03-05)

Copyright Huawei
ii
OCS
Process)
Contents
1.3.25 Address-Type AVP................................................................................................................................21

1.3.26 VASP-Id AVP........................................................................................................................................21
1.3.27 VAS-Id AVP..........................................................................................................................................21
1.3.28 Recipient-Address AVP........................................................................................................................22
1.3.29 Priority AVP..........................................................................................................................................22
1.3.30 Message-ID AVP..................................................................................................................................23
1.3.31 Message-Type AVP...............................................................................................................................24
1.3.32 Message-Size AVP................................................................................................................................25
1.3.33 MO_msc_addr AVP..............................................................................................................................25
1.3.34 MT_msc_addr AVP..............................................................................................................................25
1.3.35 Service-Id AVP.....................................................................................................................................26
1.3.36 need-cnfm AVP.....................................................................................................................................26
1.3.37 MSG-Seq AVP......................................................................................................................................27
1.3.38 MSG-Send-Result AVP........................................................................................................................27
1.3.39 RN-Prefix AVP.....................................................................................................................................27
1.3.40 Recipient_Type AVP.............................................................................................................................28
1.3.41 CC-Money AVP....................................................................................................................................28
1.3.42 Exponent AVP.......................................................................................................................................28
1.3.43 Unit-Value AVP....................................................................................................................................29
1.3.44 Value-Digits AVP..................................................................................................................................29
1.3.45 Calling-CellID-Or-SAI AVP.................................................................................................................30
1.3.46 IN-Information AVP.............................................................................................................................31
1.3.47 Subscriber-Pay-Type AVP....................................................................................................................32
1.3.48 Called-CellID-Or-SAI AVP..................................................................................................................33
1.3.49 Access-Network-Type AVP..................................................................................................................33
Issue 01 (2013-03-05)

Copyright Huawei
iii
OCS
Process)
1 Multimedia Message Charging Process
Multimedia Message Charging

Process
About This Chapter

This section describes the multimedia message charging process in DCC application through
an example.
1.1 Interaction Process
1.2 Parameter Description
1.3 AVP Description
This section describes the AVPs in the CCR and CCA messages.
1.1 Interaction Process

The CBSOCS does the rating and charging for MMS service on DCC interface based on IEC
(Immediate Event Charging) mode, in which the MMSC is client, and CBSOCS is a server.
Figure 1-1 shows the multimedia message charging process.
Issue 01 (2013-03-05)

Copyright Huawei
OCS
Process)
Figure 1.1 Multimedia message charging process
MMSC: Multimedia Message Service Center

CBP: Convergent Billing Point
The detailed process is as follows:

1.
The MMSC sends a CCR{Event} message to the CBP for charging.
2.
The CBP processes the charging request and sends a CCA{Event} message containing
the processing result to the MMSC.
3.
The MMSC returns the processing result to the subscriber. Then the normal process of
charging for the MMS service online through DCC is complete.
4.
If the MMSC fails to send the multimedia message, the multimedia message fee needs to
be refunded. Then the operations in the dotted black box in Figure 1-1 are performed, the
MMSC sends a CCR{Event} message to the CBP for refund.
5.
The CBP processes the refund request and sends a CCA{Event} message containing the
processing result to the MMSC. Then the process of charging for the MMS service
through DCC is complete.
1.2 Parameter Description

This section describes the AVP parameters that are involved in the preceding interaction
flowchart.
In the following parameters, the parameter whose Data Type is Grouped is an array, and this parameter
contains one or more subparameters.
Issue 01 (2013-03-05)

Copyright Huawei
OCS
Process)
1.2.1 Parameters Description of First CCR{Event}

Figure 1.1 Parameters description of first CCR{Event}: multimedia message charging
AVP
Code
Data Type
Instance
AVP Name
<Session-Id>
263
UTF8String
host1.com;1876543210;5
23
{Origin-Host}
264
DiameterIdentity
host1.com
{Origin-Realm}
296
DiameterIdentity
www.xyz.com
[Destination-Host]
293
DiameterIdentity
OCSService.com
{Destination-Realm}
283
DiameterIdentity
www.huawei.com
{Auth-Application-Id}
258
Unsigned32
4: Indicates the DCCA.
{Service-Context-Id}
461
UTF8String
32270@3gpp.org
{CC-Request-Type}
416
Enumerated
4: Indicates the request of

one-off charging event
control.
{CC-Request-Number}
415
Unsigned32
0: Indicates the first

request in the same
session.
[Event-Timestamp]
55
Time
*[Subscription-Id]
443
Grouped
{Subscription-Id-Type}
450
Enumerated
0: Indicates that the

terminal identity is of the
international E.164 format
that is defined according
to the ITU-TE.164
number scheme.
{Subscription-Id-Data}
444
UTF8String
66890622255
[Service-Identifier]
439
Unsigned32
[Requested-Action]
436
Enumerated
[Service-Information]
873
Grouped
874
Grouped
[3GPP-MSTimeZone]
23
UTF8String
[MMS-Information]
877
Grouped
886
Grouped
899
Enumerated
1: MSISDN
[PS-Information]
[Originator-Address]
[Address-Type]
Issue 01 (2013-03-05)

Copyright Huawei
OCS
Process)
AVP
Code
Data Type
Instance
897
UTF8String
1201
Grouped
[Address-Type]
899
Enumerated
1: MSISDN
[Address-Data]
897
UTF8String
[RN-Prefix]
30808
UTF8String
[Recipient_Type]
30809
Enumerated
1: MM3(e-mail)
[Priority]
1209
Enumerated
1: Normal
[Message-ID]
1210
UTF8String
123456
[Message-Type]
1211
Enumerated
1: m-send-req
[Message-Size]
1212
Unsigned32
[VASP-Id]
1101
UTF8String
[VAS-Id]
1102
UTF8String
[Service-Id]
20506
OctetString
[MO_msc_addr]
20404
UTF8String
[MT_msc_addr]
20405
UTF8String
[MSG-Seq]
20802
UTF8String
[Calling-CellID-OrSAI]
20303
UTF8String
[Called-CellID-OrSAI]
20306
UTF8String
AVP Name
[Address-Data]
[Recipient-Address]
1.2.2 Parameters Description of First CCA{Event}

Figure 1.1 Parameters description of first CCA{Event}: multimedia message charging
AVP
Code
Data Type
Instance
AVP Name
<Session-Id>
263
UTF8String
host1.com;1876543210
;523
{Result-Code}
268
Unsigned32
2001
{Origin-Host}
264
DiameterIdentity
host1.com
{Origin-Realm}
296
DiameterIdentity
www.xyz.com
258
Unsigned32
Issue 01 (2013-03-05)

Copyright Huawei
OCS
Process)
AVP Name
AVP
Code
Data Type
Instance
{CC-Request-Type}
416
Enumerated
4: Indicates the request

of one-off charging
event control.
{CC-Request-Number}
415
Unsigned32

request in the same
session.
873
Grouped
877
Grouped
[MSG-Seq]
20802
UTF8String
[need-cnfm]
20606
Integer32
20300
Grouped
20355
Unsigned32
[MMS-Information]
[IN-Information]
[Subscriber-PayType]
1.2.3 Parameters Description of Second CCR{Event}

Figure 1.1 Parameters description of second CCR{Event}: multimedia message charging
AVP
Code
Data Type
Instance
AVP Name
<Session-Id>
263
UTF8String
host1.com;1876543210;52
3
{Origin-Host}
264
DiameterIdentity
host1.com
{Origin-Realm}
296
DiameterIdentity
www.xyz.com
[Destination-Host]
293
DiameterIdentity
OCSService.com
{Destination-Realm}
283
DiameterIdentity
www.huawei.com
258
Unsigned32
{Service-Context-Id}
461
UTF8String
32270@3gpp.org
{CC-Request-Type}
416
Enumerated

control.
{CC-Request-Number}
415
Unsigned32

request in the same
session.
[Event-Timestamp]
55
Time
*[Subscription-Id]
443
Grouped
Issue 01 (2013-03-05)

Copyright Huawei
OCS
Process)
AVP
Code
Data Type
Instance
450
Enumerated
0: Indicates that the

terminal identity is of the
international E.164 format
that is defined according
to the ITU-TE.164
number scheme.
444
UTF8String
66890622255
[Service-Identifier]
439
Unsigned32
*[Used-Service-Unit]
446
Grouped
417
Unsigned64
[Requested-Action]
436
Enumerated
873
Grouped
877
Grouped
886
Grouped
[Address-Type]
899
Enumerated
1: MSISDN
[Address-Data]
897
UTF8String
1201
Grouped
[Address-Type]
899
Enumerated
1: MSISDN
[Address-Data]
897
UTF8String
[Message-ID]
1210
UTF8String
123456
[MSG-Seq]
20802
UTF8String
[MSG-Send-Result]
20803
Enumerated
AVP Name
[CC-Service-SpecificUnits]
[MMS-Information]
[Recipient-Address]
1.2.4 Parameters Description of Second CCA{Event}

Figure 1.1 Parameters description of second CCA{Event}: multimedia message charging
AVP Name
AVP
Code
Data Type
Instance
<Session-Id>
263
UTF8String
host1.com;1876543210;52
3
{Result-Code}
268
Unsigned32
2001
{Origin-Host}
264
DiameterIdentity
host1.com
{Origin-Realm}
296
DiameterIdentity
www.xyz.com
Issue 01 (2013-03-05)

Copyright Huawei
OCS
Process)
AVP Name
AVP
Code
Data Type
Instance
258
Unsigned32
{CC-Request-Type}
416
Enumerated

control.
{CC-Request-Number}
415
Unsigned32
0: Indicates the first request

in the same session.
873
Grouped
877
Grouped
[MSG-Seq]
20802
UTF8String
[need-cnfm]
20606
Integer32
20300
Grouped
20355
Unsigned32
[MMS-Information]
[IN-Information]
[Subscriber-PayType]
1.3 AVP Description

This section describes the AVPs in the CCR and CCA messages.
1.3.1 3GPP-MS-TimeZone AVP

AVP Name
3GPP-MS-TimeZone
AVP Code
23
AVP Data
Type
UTF8String
Description
Indicate the offset between universal time and local time in steps of
15 minutes of where the MS currently resides.
Issue 01 (2013-03-05)
Length Range: [0,12)

Copyright Huawei
OCS
Process)
1.3.2 Event-Timestamp AVP

AVP Name
Event-Timestamp
AVP Code
55
AVP Data Type
Time
Description
Indicates the time when an event occurs.

The value of this AVP is generated by the DCC client.
The time is conversed from January 1, 1900, 00:00 UTC, in
seconds.
NOTE
UTC: Coordinated Universal Time
1.3.3 Auth-Application-Id AVP

AVP Name
Auth-Application-Id
AVP Code
258
AVP Data Type
Unsigned32
Description
Indicates the unique ID that is used for re-authentication or reauthorization.

The Auth-Application-Id AVP contains the following values:
0: Indicates Diameter common messages
1: Indicates NASREQ
2: Indicates Mobile-IP
The IP address used for the mobile phone to connect to the
internet.
3: Indicates Diameter base accounting
0xffffffff: Indicates the relay
4: Indicates the DCCA
NOTE
DCCA: Diameter Credit Control Application
Issue 01 (2013-03-05)

Copyright Huawei
OCS
Process)
1.3.4 Session-Id AVP

AVP Name
Session-Id
AVP Code
263
AVP Data Type
UTF8String
Description
Identifies a session ID. A session ID uniquely identifies a DCC

session process.
The format is as follows:
<DiameterIdentity>;<high 32 bits>;<low 32 bits>;<optional value>
<DiameterIdentity>: the same as the field in the Origin-Host

AVP
<high 32 bits>: indicates the current time of the system

Type the value in the defined time form of data.
<low 32 bits>: indicates the cycle count-up

The initial value is 0. When you restart the system, set the value
to 0.
<optional value>: indicates reserved values
Separate the preceding fields with the character ";".

For example: host1.com;1876543210;523
1.3.5 Origin-Host AVP

AVP Name
Origin-Host
AVP Code
264
AVP Data Type
DiameterIdentity
Description
Contains the identification of the source point of the operation and

the realm of the operation originator.
Relay agents must not modify this AVP. The value of the OriginHost AVP is guaranteed to be unique within a single host.
Note that the Origin-Host AVP may resolve to more than one
address as the Diameter peer may support more than one address.
For example: host1.com
Issue 01 (2013-03-05)

Copyright Huawei
OCS
Process)
1.3.6 Result-Code AVP

AVP Name
Result-Code
AVP Code
268
AVP Data Type
Unsigned32
Description
Indicates a specified request is successfully fulfilled or fails.

If the host setting the Result-Code AVP is not the host that is
designated in the Origin-Host AVP, a failed Result-Code AVP must
contain the Error-Reporting-Host AVP.
The Diameter protocol provides the following types of error codes.
The error type is judged based on the first digit of an error code.
1xxx: informational
2xxx: success
3xxx: protocol errors
4xxx: transient failure
5xxx: permanent failure
An error type that cannot be identified, that is, the first digit of an
error type is not in the preceding definition, is regarded as a
permanent failure.
1.3.7 Destination-Realm AVP

AVP Name
Destination-Realm
AVP Code
283
AVP Data Type
DiameterIdentity
Description
Indicates the home realm of the destination device. This attribute

cannot be displayed in a response message.
For example: www.huawei.com
Issue 01 (2013-03-05)

Copyright Huawei
10
OCS
Process)
1.3.8 Destination-Host AVP

AVP Name
Destination-Host
AVP Code
293
AVP Data Type
DiameterIdentity
Description
Indicates the identity of the destination device.

This identity is distributed by the entire network. The peer end of
the Diameter must be unique.
This AVP must be contained in messages that are initiated by an
agent. This AVP can be contained in request messages. This AVP
cannot be contained in answer messages.
For example: cbsocs001.huawei.com
1.3.9 Origin-Realm AVP

AVP Name
Origin-Realm
AVP Code
296
AVP Data Type
DiameterIdentity
Description
Indicates the home realm of the device that initiates DCC messages.
For example: www.xyz.com
1.3.10 CC-Request-Number AVP

AVP Name
CC-Request-Number
AVP Code
415
AVP Data Type
Unsigned32
Description
Indicates the identity of a certain request in a session.

As Session-Id is global unique, different requests and answers can
be matched through Session-Id and CC-Request-Number.
Set CC-Request-Number in INITIAL_REQUEST and
EVENT_REQUEST to 0. Set the first UPDATE_REQUEST to 1,
the second to 2, and set other values according to the previous rule
until the TERMINATION_REQUEST is sent.
Issue 01 (2013-03-05)

Copyright Huawei
11
OCS
Process)
1.3.11 CC-Request-Type AVP

AVP Name
CC-Request-Type
AVP Code
416
AVP Data Type
Enumerated
Description
Indicates the reason for sending a CCR message. This AVP must be
contained in the CCR message.
The CC-Request-Type AVP contains the following values:
1: INITIAL_REQUEST
Indicates that the initial CCR is used to initiate a credit control
session. The session contains the credit control information
about initiating a session.
2: UPDATE_REQUEST
Indicates that the update CCR contains the credit control
information about the sessions of which credit control is set up.
When the re-authorization needs to be initiated, an update CCR
needs to be initiated.
3: TERMINATION_REQUEST
Indicates to interrupt a credit control session by terminating a
credit request.
4: EVENT_REQUEST
Indicates to use EVENT_REQUEST when the session status
need not be maintained by the DCC server. This request contains
all the information about the concerned service. In addition, this
request is the unique request of this service. When CC-RequestType of a CCR message is set to EVENT_REQUEST,
Requested-Action must be contained in the CCR message.
1.3.12 CC-Service-Specific-Units AVP

AVP Name
CC-Service-Specific-Units
AVP Code
417
AVP Data Type
Unsigned64
Description
Indicates the number of the service-related units in a selected

service.
Issue 01 (2013-03-05)

Copyright Huawei
12
OCS
Process)
1.3.13 Requested-Action AVP

AVP Name
Requested-Action
AVP Code
436
AVP Data Type
Enumerated
Description
In a CCR command, if CC-Request-Type is set to

EVENT_REQUEST, you can infer that the Requested_Action
AVP contains the requested action.
The Requested_Action AVP contains the following values:
0: DIRECT_DEBITING
Indicates to deduct the fee directly. To deduct the fee directly is
to deduct the mapping service units from the subscriber account
based on the information about the Requested-Service-Unit
AVP. The Granted-Service-Unit AVP in the CCA contains the
service units that need to be deducted. The service-related AVPs
can contain additional rating information.
1: REFUND_ACCOUNT
Indicates to refund. To refund is to add the mapping service units
to the subscriber account based on the information about the
Requested-Service-Unit AVP. The Granted-Service-Unit AVP
in the CCA contains the service units that need to be added. The
service-related AVPs can contain additional rating information.
2: CHECK_BALANCE
Indicates to check the balance. In this case, check only the
balance of the subscriber account. Do not perform any
operations about account credit reservation. In a CCA command,
the result of balance check is returned through the BalanceResult AVP.
3: PRICE_ENQUIRY
Indicates to query for the price. In this case, neither check the
account balance nor reserve the fee in an account. Instead, return
the price of the requested service through the Cost-Information
AVP in the CCA.
Issue 01 (2013-03-05)

Copyright Huawei
13
OCS
Process)
1.3.14 Service-Identifier AVP

AVP Name
Service-Identifier
AVP Code
439
AVP Data Type
Unsigned32
Description
Indicates the identifier of a service.

The specific service which the request relates to is uniquely
identified by the combination of Service-Context-Id and ServiceIdentifier AVPs.
In a session request, the Service-Identifier AVP applies to the fee
deduction or payback process. The default value 0 is adopted.
In an event request, the following options are available based on
services:
0: All(It is not distinguished, which is used by the MDSP.)
1: MO(P2A)
2: MT(A2P)
4: MMS(MT)
151: fullTrackOnlinePlay
152: fullTrackDownload
153: colorRing
154: ringToneDownload
155: download
156: OnlinePlay
1.3.15 Subscription-Id AVP

AVP Name
Subscription-Id
AVP Code
443
AVP Data Type
Grouped
Description
Indicates the information used to identify the end user of the service
subscription party.
The Subscription-Id AVP is an AVP group. The detailed ABNF
syntax is as follows:
*Subscription-Id ::= <AVP Header: 443>
The Diameter proxy or agent must route based on this field. In the
case of more than one Subscription-Id, the system handles only the
first Subscription-Id.
Issue 01 (2013-03-05)

Copyright Huawei
14
OCS
Process)
1.3.16 Subscription-Id-Data AVP

AVP Name
Subscription-Id-Data
AVP Code
444
AVP Data Type
UTF8String
Description
Indicates the number of the charged party.

Supported the following format for the mobile number:
International prefix + CC + MSISDN
National prefix + MSISDN
CC + MSISDN
MSISDN
Supported the following format for the fixed number:
International prefix + CC + Area Number + PSTN
National prefix + Area Number + PSTN
In this version, supported the following format for the number:
International prefix + CC + Area Number + PSTN
National prefix + Area Number + PSTN
The number format for the MVNO function: CC + MSISDN, and

CC is the code of a country where the SCP system located.
1.3.17 Used-Service-Unit AVP

AVP Name
Used-Service-Unit
AVP Code
446
AVP Data Type
Grouped
Description
Indicates the amount of used non-monetary service units measured

for a particular category to a particular quota type.
The Used-Service-Unit AVP is an AVP group. The detailed ABNF
Used-Service-Unit ::= <AVP Header: 446>
[Reporting-Reason]
[Tariff-Change-Usage]
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input-Octets]
[CC-Output-Octets]
[CC-Service-Specific-Units]
Issue 01 (2013-03-05)

Copyright Huawei
15
OCS
Process)
1.3.18 Subscription-Id-Type AVP

AVP Name
Subscription-Id-Type
AVP Code
450
AVP Data Type
Enumerated
Description
Indicates the type of a user's terminal ID.

The Subscription-Id-Type AVP contains the following values:
0: END_USER_E164
Indicates that the terminal identity is of the international E.164
format defined according to the ITU-T E.164 number scheme.
1: END_USER_IMSI
Indicates that the terminal ID is of the international IMSI format
defined according to the ITU-T E.212 number scheme.
2: END_USER_SIP_URI
Indicates that the terminal ID is the value defined by the SIP
URI AVP.
3: END_USER_NAI
Indicates that the terminal ID is a network access ID.
4: END_USER_PRIVATE
Indicates that the terminal ID is a private ID of a DCC server.
NOTE
IMSI: International Mobile Subscriber Identity
Issue 01 (2013-03-05)

Copyright Huawei
16
OCS
Process)
1.3.19 Service-Context-Id AVP

AVP Name
Service-Context-Id
AVP Code
461
AVP Data Type
UTF8String
Length Range: [0, 63)
Description
Indicates the unique ID (extendable) of a DCC service.

The format of the ID is "service-context" "@" "domain"
The definition of service-context is "[X]" ".""[Y]".
[X]: indicates the type of a service. The value of a service type is

composed of characters.
The applicable values are in, ismp, ccg, message, wlan, DSL,
PSTN-Event, Recharge, and QueryBalance.
[Y]: indicates a terminal type.

The value of a terminal type is composed of characters. If [Y] is
not contained in the definition of service-context, it indicates
the terminal type is GSM.
The applicable values are PSTN, PHS, GSM, and CDMA.
The value of domain is huawei.com.
Fpr PS charging: 32251@3gpp.org
For WLAN charging: 32252@3gpp.org
For IMS charging: 32260@3gpp.org
For MMS service charging: 32270@3gpp.org
For SMS service charging: 32274@3gpp.org
1.3.20 Service-Information AVP

AVP Name
Service-Information
AVP Code
873
AVP Data Type
Grouped
Description
Indicates the basic information about the service.

The Service-Information AVP is an AVP group. The detailed
ABNF syntax is as follows:
Service-Information ::= <AVP Header: 873>
[RTBPInformation]
The Service-Information AVP group varies with different services.

It records the specific information about certain service types, allow
the client to transmit the extra service information, and can be
flexibly extended.
Issue 01 (2013-03-05)

Copyright Huawei
17
OCS
Process)
1.3.21 PS-Information AVP

AVP Name
PS-Information
AVP Code
874
AVP Data Type
Grouped
Description
Indicates the PS service information group, used to store the

information about the volume charging.
The PS-Information AVP is an AVP group. The detailed ABNF
PS-Information ::= <AVP Header: 874>
[3GPP-Charging-Id]
[3GPP-PDP-Type]
[PDP-Address]
[QoS]
[SGSN-Address]
[GGSN-Address]
[CG-Address]
[3GPP-IMSI-MCC-MNC]
[3GPP-GGSN-MCC-MNC]
[3GPP-NSAPI]
[3GPP-Session-Stop-Indicator]
[3GPP-Selection-Mode]
[3GPP-Charging-Characteristics]
[3GPP-SGSN-MCC-MNC]
[3GPP-MS-TimeZone]
[3GPP-CAMEL-Charging-Info]
[Charging-Rule-Base-Name]
[3GPP-User-Location-Info]
[3GPP-RAT-Type]
[PS-Furnish-Charging-Information]
[PDP-Context-Type]
[SP-Id]
[Service-Id]
[Service-Type]
[Content-Id]
[BearerType]
[StartTime]
[StopTime]
[BearerProtocolType]
[ChargingID]
[ServiceLevel]
[Message-Id]
Issue 01 (2013-03-05)

Copyright Huawei
18
OCS
Process)
1.3.22 MMS-Information AVP

AVP Name
MMS-Information
AVP Code
877
AVP Data Type
Grouped
Description
Indicates the MMS information group, used to store the information

about the MMS charging.
The MMS-Information AVP is an AVP group. The detailed ABNF
MMS-Information ::= <AVP Header: 877>
[Recipient-Address]
[Submission-Time]
[MM-Content-Type]
[Priority]
[Message-ID]
[Message-Type]
[Message-Size]
[Message-Class]
[Delivery-Report-Requested]
[Read-Reply-Report-Requested]
[MMBox-Storage-Requested]
[Applic-ID]
[Reply-Applic-ID]
[Aux-Applic-Info]
[Content-Class]
[DRM-Content]
[Adaptations]
[VASP-Id]
[VAS-Id]
[Service-Id]
[ChargingType]
[Discount]
[MO_msc_addr]
[MT_msc_addr]
[Source_GWID]
[Charge-Date]
[MSG-Seq]
[MSG-Send-Result]
[need-cnfm]
Issue 01 (2013-03-05)

Copyright Huawei
19
OCS
Process)
1.3.23 Originator-Address AVP

AVP Name
Originator-Address
AVP Code
886
AVP Data Type
Grouped
Description
Indicates the address information about a subscriber that sends

multimedia messages.
The Originator-Address AVP is an AVP group. The detailed ABNF
Originator-Address ::= <AVP Header: 886>
[Address-Type]
[Address-Data]
[Address-Domain]
NOTE
In the MMS MO flow, this AVP is set to the subscription ID.
1.3.24 Address-Data AVP

AVP Name
Address-Data
AVP Code
897
AVP Data Type
UTF8String
Description
Indicates the address value.

The address varies according to the value of the Address-Type
AVP.
1.3.25 Address-Type AVP

AVP Name
Address-Type
AVP Code
899
AVP Data Type
Enumerated
Description
Indicates the address type.
Issue 01 (2013-03-05)
0: E-mail address
1: MSISDN
2: IPv4 Address
3: IPv6 Address
4: Numeric Shortcode
5: Alphanumeric Shortcode
6: Other

Copyright Huawei
20
OCS
Process)
1.3.26 VASP-Id AVP

AVP Name
VASP-Id
AVP Code
1101
AVP Data Type
UTF8String
Description
Indicates the ID of the value-added service provider.
1.3.27 VAS-Id AVP

AVP Name
VAS-Id
AVP Code
1102
AVP Data Type
UTF8String
Description
Indicates the ID of the value-added service.
1.3.28 Recipient-Address AVP

AVP Name
Recipient-Address
AVP Code
1201
AVP Data Type
Grouped
Description
Indicates the address information about a subscriber that receives

multimedia messages.
The Recipient-Address AVP is an AVP group. The detailed ABNF
Recipient-Address ::= <AVP Header: 877>
[Address-Type]
[Address-Data]
[Address-Domain]
[Addressee-Type]
[RN-Prefix]
[Recipient_Type]
NOTE
In the MMS MT flow, this AVP is set to the subscription ID.
Issue 01 (2013-03-05)

Copyright Huawei
21
OCS
Process)
1.3.29 Priority AVP

AVP Name
Priority
AVP Code
1209
AVP Data
Type
Enumerated
Description
Indicates the priority of a message.
0: Low
1: Normal
2: High
1.3.30 Message-ID AVP

AVP Name
Message-ID
AVP Code
1210
AVP Data Type
UTF8String
Description
ID that uniquely identifies a multimedia message. In the MMS

refund process, the CBSOCS system uses the ID of a multimedia
message to determine which subscriber needs to be refunded.
NOTE
The AVP is used in MMS process.
Issue 01 (2013-03-05)

Copyright Huawei
22
OCS
Process)
1.3.31 Message-Type AVP
Issue 01 (2013-03-05)

Copyright Huawei
23
OCS
Process)
AVP Name
Message-Type
AVP Code
1211
AVP Data Type
Enumerated
Description
1: m-send-req
2: m-send-conf
3: m-notification-ind
4: m-notifyresp-ind
5: m-retrieve-conf
6: m-acknowledge-ind
7: m-delivery-ind
8: m-read-rec-ind
9: m-read-orig-ind
10: m-forward-req
11: m-forward-conf
12: m-mbox-store-conf
13: m-mbox-view-conf
14: m-mbox-upload-conf
15: m-mbox-delete-conf
101: MOAT
Indicates the message that is sent from a mobile terminal to the

application server of a carrier or Service Provider (SP).
102: AOMT
Indicates the message that is sent from the application server of
a carrier or SP to a mobile terminal.
103: P2PMO
Indicates the point-to-point multimedia message in the calling
flow.
104: MOET
Indicates the message that is sent from a mobile terminal to an
email address.
105: EOMT
Indicates the message that is sent from an email address to a
mobile terminal.
106: DlvRpt
Indicates the report that is sent from the MMS or SMS center to
the mobile-terminal sender.
107: RdRpt
Indicates the report that is forwarded from the MMS or SMS
center to the mobile-terminal sender after the mobile-terminal
receiver reads a message and sends a report to the MMS or SMS
center.
Issue 01 (2013-03-05)
108: Reply

Copyright Huawei
24
OCS
Process)
109: P2PMT
Indicates the point-to-point multimedia message in the called
flow.
110~: Reserved
1.3.32 Message-Size AVP

AVP Name
Message-Size
AVP Code
1212
AVP Data Type
Unsigned32
Description
Indicates the message size.
1.3.33 MO_msc_addr AVP

AVP Name
MO_msc_addr
AVP Code
20404
AVP Data Type
UTF8String
Description
Indicates the MSC address of the roaming area of the message

sender.
1.3.34 MT_msc_addr AVP

AVP Name
MT_msc_addr
AVP Code
20405
AVP Data Type
UTF8String
Description
Issue 01 (2013-03-05)
Indicates the MSC address of the roaming area of the message

receiver.

Copyright Huawei
25
OCS
Process)
1.3.35 Service-Id AVP

AVP Name
Service-Id
AVP Code
20506
AVP Data Type
OctetString
Description
Indicates the service ID, which uniquely identifies a service.

NOTE
The AVP is used in GPRS process.
1.3.36 need-cnfm AVP

AVP Name
need-cnfm
AVP Code
20606
AVP Data
Type
Integer32
Description
Indicates the information need to be confirmed.

In a CCR message,
0: indicates that the information does not need to be confirmed.
1: indicates that the information needs to be confirmed.
The default value -1 indicates that the CBSOCS system determines

whether the information needs to be confirmed.
In a CCA message,
0: indicates that the information does not need to be confirmed.
1: indicates that the information needs to be confirmed.
If the value of this AVP is 0 in a CCR message, the value returned in

the corresponding CCA message is also 0. If the value of this AVP is 1
in a CCR message, the value returned in the corresponding CCA
message is also 1. If the value of this AVP is -1 in a CCR message, the
value returned in the corresponding CCS message depends on the
configuration in the CBSOCS system.
1.3.37 MSG-Seq AVP

AVP Name
MSG-Seq
AVP Code
20802
AVP Data Type
UTF8String
Description
Issue 01 (2013-03-05)
Indicates the message sequence number.

Copyright Huawei
26
OCS
Process)
1.3.38 MSG-Send-Result AVP

AVP Name
MSG-Send-Result
AVP Code
20803
AVP Data Type
Enumerated
Description
Indicates the result of sending a message.
0: The message fails to be sent.
1: The message is sent successfully.
1.3.39 RN-Prefix AVP

AVP Name
RN-Prefix
AVP Code
30808
AVP Data Type
UTF8String
Description
Indicates RN-prefix of the received number.

If the received number is a number portability subscriber, MMSC
must fill in RN-Prefix through this field.
1.3.40 Recipient_Type AVP

AVP Name
Recipient_Type
AVP Code
30809
AVP Data Type
Enumerated
Description
Indicates recipient type of the received number.
Issue 01 (2013-03-05)
0: MM1 (mobile)
1: MM3 (e-mail)
5: MM4 (other operator's destination)
4: MM7 (VAS or short code)

Copyright Huawei
27
OCS
Process)
1.3.41 CC-Money AVP

AVP Name
CC-Money
AVP Code
413
AVP Data Type
Grouped
Description
Indicates the total amount of the specified currency.

The CC-Money AVP is an AVP group. The detailed ABNF syntax is
as follows:
CC-Money ::= <AVP Header: 413>
{Unit-Value}
[Currency-Code]
1.3.42 Exponent AVP

AVP Name
Exponent
AVP Code
429
AVP Data Type
Integer32
Description
Indicates the exponential part in the Unit-Value AVP.

If Exponent is missing, then the exponent is set to 0 by default.
Issue 01 (2013-03-05)

Copyright Huawei
28
OCS
Process)
1.3.43 Unit-Value AVP

AVP Name
Unit-Value
AVP Code
445
AVP Data Type
Grouped
Description
Indicates a numeral, which is defined by both Value-Digits and

Exponent, in an exponential form. If Exponent does not exist, then
the exponent is 0 by default.
The relational expression is as follows:
Unit-Value = Value-Digits AVP * 10^Exponent
For example, the indication of 2.3 is as follows:
Unit-Value = 2.3
Value-Digits = 23
Exponent = -1
The Unit-Value AVP is an AVP group. The detailed ABNF syntax is

as follows:
Unit-Value ::= <AVP Header: 445>
{Value-Digits}
[Exponent]
1.3.44 Value-Digits AVP

AVP Name
Value-Digits
AVP Code
447
AVP Data
Type
Integer64
Description
Indicates the valid numerals in Unit-Value.

If a numeric value is different from the original numeric value due to
the missing decimal, enter the exponent of ten in Exponent.
For example, for the numeric value 0.05, the Value-Digits AVP must
be set to 5 and the Exponent AVP must be set to -2.
Issue 01 (2013-03-05)

Copyright Huawei
29
OCS
Process)
1.3.45 Calling-CellID-Or-SAI AVP

AVP Name
Calling-CellID-Or-SAI
AVP Code
20303
AVP Data Type
UTF8String
Description
Issue 01 (2013-03-05)
Indicates the cell ID that the calling party visits.

Copyright Huawei
30
OCS
Process)
1.3.46 IN-Information AVP
Issue 01 (2013-03-05)

Copyright Huawei
31
OCS
Process)
AVP Name
IN-Information
AVP Code
20300
AVP Data Type
Grouped
Description
Indicates the intelligent network information.

The IN-Information AVP is an AVP group. The detailed ABNF
IN-Information ::= <AVP Header: 20300>
[Calling-Party-Address]
[Called-Party-Address]
[Real-Called-Number]
[Connect-Called-Number]
[Called-Short-Number]
[Group-Number]
[Specific-Output]
[Charge-Flow-Type]
[Calling-Partys-Category]
[Calling-Vlr-Number]
[Calling-CellID-Or-SAI]
[Calling-LAI]
[Called-Vlr-Number]
[Called-CellID-Or-SAI]
[Called-LAI]
[Called-IMEI]
[Calling-IMEI]
[Original-Called-Party-Id]
[High-Layer-Compatibility]
[Additional-Calling-Party-Number]
[Bearer-Capability]
[Bearer-Capability2]
[EventType-BCSM]
[Redirecting-Party-Id]
[Redirection-Information]
[Redirection-Reason]
[UE-IMSI]
[Tele-Service-Code]
[Bearer-Service-Code]
[Call-Reference-Number]
[MSC-Address]
[GMSC-Address]
[Time-Zone]
[IN-Service-Indicator]
[Recharge-Information]
[Account-Type]
[Service-Type]
[Account-Query-Method]
[Charge-ConfirmFlag]
[UserPassWd]
[CC-Time]
[Access-Method]
[Charge-Method]
[Total-Cost-Flag]
[CC-Money]
Issue 01 (2013-03-05)

Copyright Huawei
32
OCS
Process)

[CC-Total-Octets]
*[AccountInfo]
[AoC-Information]
[Access-Code]
[Calling-Party-NP]
[Called-Party-NP]
[SSP-Time]
[Call-Forward-Indicator]
[Service-Free-Indicator]
*[Account-Change-Info]
[MSCId]
[sessioninfo]
*[Notice-Infomation]
[CC-Input-Octets]
[version]
[CC-Output-Octets]
[CC-Service-Specific-Units]
[Route-Prefix]
[Subscriber-Pay-Type]
[Alert-Level]
[ActivePeriod]
[graceperiod]
[disableperiod]
[MIN]
[Conference-Call-Indicator]
[SubCOSID]
[ActiveMethod]
[OperatorID]
[Service-Key]
[Call-Type]
[Calling-Short-Number]
[FunctionFlag]
[Manager-Status]
1.3.47 Subscriber-Pay-Type AVP

AVP Name
Subscriber-Pay-Type
AVP Code
20355
AVP Data
Type
Unsigned32
Description
Indicates the payment type of a subscriber.
Issue 01 (2013-03-05)

Copyright Huawei
33
OCS
Process)
1.3.48 Called-CellID-Or-SAI AVP

AVP Name
Called-CellID-Or-SAI
AVP Code
20306
AVP Data Type
UTF8String
Description
Indicates the cell ID that the called party visits.
1.3.49 Access-Network-Type AVP

AVP Name
Access-Network-Type
AVP Code
20804
AVP Data Type
Unsigned32
Description
Indicates the network access type.

The values are as follows:
100: PSTN
101: PBX
102: PHS
200: GSM
201: GPRS
202: EDGE
300: CDMA
301: CDMA 450
400: WCDMA
500: TD-SCDMA
600: IP/IMS
601: WIFI
602: WIMAX
Others are to be extended.

NOTE
PSTN: Public Switched Telephone Network
Issue 01 (2013-03-05)
PBX: Private Branch Exchange
PHS: Personal Handyphone System
GSM: Global System for Mobile communications
EDGE: Enhanced Data rates for GSM Evolution
TD-SCDMA: Time Division-Synchronous Code Division Multiple Access
WIFI: Wireless Fidelity
WIMAX: Worldwide Interpretability for Microwave Access

Copyright Huawei
34

OCS DCC Interface Reference (Multimedia Message Charging Process EventID ...

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OCS DCC Interface Reference (Multimedia Message Charging Process EventID ...

Uploaded by

Copyright:

Available Formats

OCS

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

1.3.25 Address-Type AVP................................................................................................................................21

Huawei Proprietary and Confidential

1 Multimedia Message Charging Process

Multimedia Message Charging

About This Chapter

1.1 Interaction Process

Huawei Proprietary and Confidential

1 Multimedia Message Charging Process

Figure 1.1 Multimedia message charging process

MMSC: Multimedia Message Service Center

The detailed process is as follows:

The MMSC sends a CCR{Event} message to the CBP for charging.

1.2 Parameter Description

Huawei Proprietary and Confidential

1 Multimedia Message Charging Process

1.2.1 Parameters Description of First CCR{Event}

4: Indicates the DCCA.

4: Indicates the request of

0: Indicates the first

0: Indicates that the

Huawei Proprietary and Confidential

1 Multimedia Message Charging Process

1.2.2 Parameters Description of First CCA{Event}

4: Indicates the DCCA.

Huawei Proprietary and Confidential

1 Multimedia Message Charging Process

4: Indicates the request

0: Indicates the first

1.2.3 Parameters Description of Second CCR{Event}

4: Indicates the DCCA.

4: Indicates the request of

0: Indicates the first

Huawei Proprietary and Confidential

1 Multimedia Message Charging Process

0: Indicates that the

1.2.4 Parameters Description of Second CCA{Event}

Huawei Proprietary and Confidential

1 Multimedia Message Charging Process

4: Indicates the DCCA.

4: Indicates the request of

0: Indicates the first request

1.3 AVP Description

1.3.1 3GPP-MS-TimeZone AVP

Length Range: [0,12)

Huawei Proprietary and Confidential

1 Multimedia Message Charging Process

1.3.2 Event-Timestamp AVP

AVP Data Type

Indicates the time when an event occurs.

1.3.3 Auth-Application-Id AVP

AVP Data Type

Indicates the unique ID that is used for re-authentication or reauthorization.

0: Indicates Diameter common messages

3: Indicates Diameter base accounting