5 Functional operation in PLMN
22.0243GPPDescription of Charge Advice Information (CAI)Release 17TS
For applicable calls, the PLMN shall send the CAI message to the MS immediately the called party answers. The PLMN derives the values of the elements to be sent in the CAI message in the following way:
5.1 Outgoing calls
The local PLMN, be it the HPLMN or the VPLMN, always sets values of e1, e2, e4, e5, e6 and e7 in terms of units of the LPLMN and according to its own tariff structure.
Element e3 is set according to variables of the LPLMN and the relevant HPLMN. If the LPLMN is the HPLMN (i.e. the MS is in its Home PLMN) then e3 shall be simplified to unity.
There shall be only one value of e3 for a given combination of HPLMN and VPLMN. This value may be simply loaded into the VMSC of the LPLMN using the Man Machine Interface commands, since it is not expected to vary frequently and is independent of the type of outgoing call.
5.2 Incoming calls
For incoming calls the HPLMN determines the tariff and this tariff is dependent on the LPLMN of the MS. Therefore all the CAI elements are set according to the HPLMN tariff as a function of LPLMN.
In the case of the LPLMN being the HPLMN these elements may be set to zero assuming the HPLMN does not charge for incoming calls.
For roaming (i.e. where the LPLMN is not the HPLMN), in order to charge for incoming calls, the VPLMN must be provided with specific CAI values as defined by each HPLMN (e1i through e7i inclusive). This may be achieved by loading the offered HPLMN derived values via the VPLMN MMI.
Each VPLMN will require a set of 7 values per HPLMN with which the VPLMN has a roaming agreement i.e.:
e1i(h), e2i(h), e3(h), e4i(h), e5i(h), e6i(h) and e7i(h).
These are derived by:
e1i(h)=e1H(h)/e3(h);
e4i(h)=e4H(h)/e3(h);
e5i(h)=e5H(h)/e3(h);
where :
h represents the ‘h’th HPLMN with a roaming relationship with the VPLMN;
i indicates the CAI element as determined by the ‘h’th HPLMN, for the charging of incoming calls;
the same value of e3 is used for both incoming and outgoing calls;
exH(h) represents the value of the element x, given in terms of HPLMN units;
exi(h) represents the value of the element x as handled by the VPLMN.
Annex A (informative):
Change history
|
Change history |
|||||||||||
|
TSG SA# |
SA Doc. |
SA1 Doc |
Spec |
CR |
Rev |
Rel |
Cat |
Subject/Comment |
Old |
New |
WI |
|
Jun 1999 |
GSM 02.24 |
Transferred to 3GPP SA1 |
7.0.0 |
||||||||
|
SA#04 |
22.024 |
Transferred to 3GPP SA1 |
3.0.0 |
||||||||
|
SP-05 |
SP-99479 |
S1-99613 |
22.024 |
001 |
R99 |
D |
Editorial changes for alignment |
3.0.0 |
3.0.1 |
Editorial changes |
|
|
SP-11 |
SP-010065 |
S1-010258 |
22.024 |
Rel-4 |
Transferred to 3GPP Release 4 |
3.0.1 |
4.0.0 |
||||
|
SP-16 |
SP-020267 |
S1-021043 |
22.024 |
Rel-5 |
Updated from Rel-4 to Rel5 |
4.0.0 |
5.0.0 |
||||
|
SP-26 |
SP-040744 |
S1-040997 |
22.024 |
Rel-6 |
Updated from Rel-5 to Rel-6 |
5.0.0 |
6.0.0 |
||||
|
SP-28 |
SP-050211 |
S1-050397 |
22.024 |
003 |
– |
Rel-6 |
A |
AoC for SCUDIF |
6.0.0 |
6.1.0 |
TEI |
|
SP-36 |
22.024 |
Rel-7 |
Updated from Rel-6 to Rel-7 |
6.1.0 |
7.0.0 |
||||||
|
SP-42 |
– |
– |
Rel-8 |
Updated from Rel-7 to Rel-8 |
7.0.0 |
8.0.0 |
|||||
|
SP-46 |
– |
– |
– |
– |
– |
– |
Updated to Rel-9 by MCC |
7.0.0 |
9.0.0 |
||
|
2011-03 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
9.1.0 |
10.0.0 |
|
|
2012-09 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-11 version (MCC) |
10.0.0 |
11.0.0 |
|
|
2014-10 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-12 version (MCC) |
11.0.0 |
12.0.0 |
|
|
2015-12 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-13 version (MCC) |
12.0.0 |
13.0.0 |
|
|
2017-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-14 by MCC |
13.0.0 |
14.0.0 |
|
|
2018-06 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-15 by MCC |
14.0.0 |
15.0.0 |
|
|
2020-07 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-16 by MCC |
15.0.0 |
16.0.0 |
|
|
2022-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-17 by MCC |
16.0.0 |
17.0.0 |
|