CAPv2 Charging Context v1.2

Download as pdf or txt
Download as pdf or txt
You are on page 1of 4
At a glance
Powered by AI
The document describes context specific parameters that could be used for the CAPv2 context and includes limitations to parameters in the CreditControlRecord. It also provides a mapping of parameters and describes changes made in versions 1.2 and 1.1 of the protocol format.

The purpose of this document is to describe the context specific parameters that could be used for the CAPv2 context ([email protected]). The parameters will be a part of the chargingContextSpecific tag included in the CreditControlRecord defined in Reference [1] This document also includes limitations to parameters in the CreditControlRecord defined in Reference [1]

Following parameters could be present in the chargingContextSpecific part of the CreditControlRecord for the CAPv2 charging context ([email protected]): Address-Presentation- Restricted-Indicator, Charging-From-Triggering, Other-Party-Id-Address, Other-Party-Id-Location, Other-Party-Id-MNP-IMSI, Other-Party-Id-MNP-RN, Other-Party-Id-MNP-Result, Subscription-Id-Location, Subscription-Type, Ericsson-Geo-Location-Cell- Identity, Ericsson-Location-Area-Code, Ericsson-Location-MCC-MNC.

CAPv2 Charging Context v1.

CUSTOMER PRODUCT INFORMATION

Page 1 of 4

3/190 59-FAY 302 052/1 Uen

CAPv2 Charging Context v1.2


Enclosure to Detail Record Credit Control
Copyright
Ericsson AB 2010 - All Rights Reserved
Disclaimer
No part of this document may be reproduced in any form without the written permission of
the copyright owner.
The contents of this document are subject to revision without notice due to continued
progress in methodology, design and manufacturing. Ericsson shall have no liability for any
error or damage of any kind resulting from the use of this document.
Trademark List
Ericsson is the trademark or registered trademark of Telefonaktiebolaget LM Ericsson. All
other products or service names mentioned in this document are trademarks of their
respective companies.

Contents
1

Introduction

2
2.1

Parameter limitations
Limitation table

3
3.1

Parameter Mapping
Mapping table

4
4.1
4.2

Protocol Format Changes


Version 1.2
Version 1.1

Reference List

file:///C:/Users/ADMINI~1/AppData/Local/Temp/ALEX_TMP/1207/alex0223.htm

12/12/2014

CAPv2 Charging Context v1.2

Page 2 of 4

1 Introduction
The purpose of this document is to describe the context specific parameters that could be
used for the CAPv2 context ([email protected]). The parameters will be a part of
the chargingContextSpecific tag included in the CreditControlRecord defined in Reference [1]
This document also includes limitations to parameters in the CreditControlRecord defined in
Reference [1]

2 Parameter limitations
The CAPv2 context ([email protected]) limit the value ranges and use of some of
the parameters in the CreditControlRecord.

2.1 Limitation table


Table 1

Parameter limitations

Name
serviceExtension

Valid values

Comment

Not used

serviceIdentifier

0
1
2
3
7

=
=
=
=
=

Voice
Fax
Data
Unknown
Video Telephony

8 = Video Conference
serviceScenario

0 = mobileOriginating
1 = mobileForwarding
2 = mobileTerminating

roamingPosition

0 = insideHPLMN
1 = outsideHPLMN

3 Parameter Mapping
Following parameters could be present in the chargingContextSpecific part of the
CreditControlRecord for the CAPv2 charging context ([email protected]).

3.1 Mapping table


Table 2

Context parameters
Name

Address-PresentationRestricted-Indicator

Parameter
Id
19

Datatype
Unsigned32

Description
The Address-Presentation-Restricted-Indicator
is of type Enumerated and it is used to
determine how Address Presentation
Restriction is set.
Possible values:
PRESENTATION_ALLOWED = 0

Charging-From-Triggering
(PMR308)

16778262

Unsigned32

PRESENTATION_RESTRICTED = 1
ADDRESS_NOT_AVAILABLE = 2

The Charging-From-Triggering is of type


Enumerated and carries an indication whether
charging should be started already at
triggering.

file:///C:/Users/ADMINI~1/AppData/Local/Temp/ALEX_TMP/1207/alex0223.htm

12/12/2014

CAPv2 Charging Context v1.2

Page 3 of 4

Possible value
CHARGING_FROM_TRIGGER_APPLICABLE = 1
Other-Party-Id-Address

16778219

PartyInformation

The Other-Party-Id-Address holds an identifier


of the other party involved in a service. The
other party is related to the session/event but
not charged for the service. The other party
could be e.g. a calling party, a called party, a
redirecting party, a sender or a receiver;
depending on service.

Other-Party-Id-Location

16778221

UTF8String

The Other-Party-Id-Location holds the location


information of the other party in a service.
Valid characters are 0-9, A-F, a-f, * and #.

Other-Party-Id-MNP-IMSI

16778223

UTF8String

The Other-Party-Id-MNP-IMSI holds the E.212


IMSI format of the other party involved in a
service. Note: This is a generic IMSI i.e. it is
not tied necessarily to the subscriber. MCC and
MNC values in this IMSI point to the
subscription network of the other party. First
part of the MSIN identifies MVNO.

Other-Party-Id-MNP-RN

16778220

UTF8String

The Other-Party-Id-MNP-RN holds the Routing


Number of the other party involved in a
service.
Valid characters are, 0-9,*,#,a,b,c

Other-Party-Id-MNP-Result

16778222

Unsigned32

The Other-Party-Id-MNP-Result holds


information whether a MNP request was
completed successfully or whether an error
occurred.
Possible values:
2001 - Success

3001 - Failed to connect

5001 - Parameter error


5002 - Subscriber unknown
5003 - Other error
5004 - Non-portable number

Subscription-Id-Location

16778217

UTF8String

The Subscription-Id-Location is used to define


the location of the subscriber.
Valid characters are 0-9, A-F, a-f, * and #.

Subscription-Type

16778224

Unsigned32

The Subscription-Type is used to identify the


subscription type. Subscription Type is a value
that associates a mobile subscriber to a group
with certain characteristics. It is set in the
HLR.
Valid values are 1 - 127

Ericsson-Geo-Location-CellIdentity

16778251

OCTET STRING

The Cell Identity (CI) where the end-user is


currently at consists of 2 octets. The
parameter holds an OctetString. Bit 8 of octet
1 is the MSB and bit 1 of octet 2 the LSB.
Coding using full hexadecimal representation
shall be used.

Ericsson-Location-Area-Code

16778250

OCTET STRING

The parameter carries the Location Area Code


(LAC) where the end-user is currently at. The
parameter holds an OctetString. The location
area code (LAC) consists of 2 octets, bit 8 of
octet 1 is the MSB and bit 1 of octet 2 the LSB.
Coding using full hexadecimal representation
shall be used.

Ericsson-Location-MCC-MNC

16778249

UTF8String

The parameter carries the MCC and MNC


representing country and network where the
end-user is currently at. The parameter holds
an UTF8String.

4 Protocol Format Changes


4.1 Version 1.2

file:///C:/Users/ADMINI~1/AppData/Local/Temp/ALEX_TMP/1207/alex0223.htm

12/12/2014

CAPv2 Charging Context v1.2

Table 3

Page 4 of 4

Protocol Format Changes in Version 1.2

Changes compared to Version 1.1

Comment

Added context parameter Address-Presentation-Restricted-Indicator.


Added context parameter Charging-From-Triggering.
Changed parameter Id for Address-Presentation-Restricted-Indicator

4.2 Version 1.1


Table 4

Protocol Format Changes in Version 1.1

Changes compared to Version 1.0

Comment

Added context parameter Ericsson-Geo-Location-Cell-Identity.


Added context parameter Ericsson-Location-Area-Code.
Added context parameter Ericsson-Location-MCC-MNC.

Reference List
Ericsson Documents
[1] Detail Record Parameter List Credit Control Record, 7/190 59-FAY 302 024/1 Uen.

file:///C:/Users/ADMINI~1/AppData/Local/Temp/ALEX_TMP/1207/alex0223.htm

12/12/2014

You might also like