4 Architecture considerations

32.2763GPPCharging managementRelease 17Telecommunication managementTSVoice Call Service (VCS) charging

4.1 High level Voice Call Service (VCS) architecture

The high level 3G logical architecture in TS 23.002 [103] is used for CS domain charging as in TS 32.250 [10]. Figure 4.1.1 shows the CAMEL entities as described in TS 23.002 [103]. Refer to TS 23.002 [103] for a description of the reference points not covered in the present document.

NOTE: Most CAMEL-specific interfaces have no particular name. They are designated by the name of the two entities they link together, e.g. "the gsmSSF-gsmSCF interface".

NOTE: The bold lines are used for interfaces supporting user data only, the dashed lines are used for interfaces supporting signalling only.

Figure 4.1.1: Configuration of CAMEL entities

CS domain online charging is implemented by CAMEL techniques as described in TS 23.078 [207] and TS 29.078 [212], i.e. outside the scope of the 32 series of charging TSs.

4.2 VCS charging – Offline charging architecture

Not specified in the present document.

4.3 VCS charging – Online charging architecture

As an alternative to direct CAMEL-based online charging of subscribers for voice calls, an online charging interface between a voice Proxy Function and the OCS is established. The concept of voice call shall be interpreted as any CS call, whatever the teleservice used (speech, 3.1 kHz audio, Fax, or CS data) except CS video telephony calls (BS 37, 64 kbit/s unrestricted digital info mode). The voice control architecture is shown in Figure 4.3.1.

Figure 4.3.1: VCS from a Proxy Function online charging architecture

The signalling between the CS domain elements and a voice Proxy Function is implemented by CAMEL techniques as described in TS 23.078 [207] and TS 29.078 [212], i.e. outside the scope of the 32 series of charging TSs. The interface between a voice Proxy Function and the OCS utilizes Diameter Ro for the voice call service online charging as specified in the present document and utilizes the Proxy Function for mapping between CAMEL and Diameter as specified in TS 32.293 [56].