4 Architecture considerations

32.2573GPPCharging managementEdge computing domain chargingRelease 17Telecommunication managementTS

4.1 High-level architectures

4.1.1 High-level 5G System architecture

4.1.1.1 5GS Reference Architecture for Supporting Edge Computing

The 5GS architecture for supporting Edge Computing is defined in 3GPP TS 23.548 [10] based on the reference architectures specified in clause 4.2 of 3GPP TS 23.501 [8].

Figure 4.1.1.1-1 depicts 5GS architecture for non-roaming scenario supporting Edge Computing with UL CL/BP.

Figure 4.1.1.1-1: 5GS providing access to EAS with UL CL/BP for non-roaming scenario

Figure 4.1.1.1-2 depicts 5GS architecture for non-roaming scenario supporting Edge Computing without UL CL/BP.

Figure 4.1.1.1-2: 5GS providing access to EAS without UL CL/BP for non-roaming scenario

4.1.2 High-level architecture for enabling edge applications

The following high-level architectures for enabling edge applications are defined in 3GPP TS 23.558 [9]. Figure 4.1.2‑1 depicts the service based representation of architecture for enabling edge applications.

Figure 4.1.2-1: Architecture for enabling edge applications – service-based representation

Figure 4.1.2-2 depicts the service-based representation for utilization of the 5GS network services.

Figure 4.1.2-2: Utilization of 5GS network services based on the 5GS SBA –
service based representation

Figure 4.1.2-3 depicts the reference point representation of the architecture for edge enabling applications.

Figure 4.1.2-3: Architecture for enabling edge applications – reference points representation

4.2 Edge Computing domain converged charging architecture

4.2.1 Converged charging architecture for 5GS usage based charging for Edge Computing

For 5GS usage based charging for Edge Computing, the 5G data connectivity domain converged charging architecture defined in 3GPP TS 32.255 [11] is applied.

4.2.2 Converged charging architecture with MnS producer enabled by CEF

The CEF consumes the MnS from the MnS producer for EAS management (see 3GPP TS 28.538 [12]), and determines the occurrence of charging events towards to the CHF for converged charging processing. The CDRs generation is performed by the CHF acting as a CDF, which transfers them to the CGF.
Finally, the CGF creates CDR files and forwards them to the BD.

If the CGF is external, the CHF acting as a CDF, forwards the CDRs to the CGF across the Ga interface.
If the CGF is integrated, there is only one internal interface between the CHF and the CGF. In this case, the relationship between CHF and CGF is 1:1. An integrated CGF may support the Ga interface from other CDFs.

When an external CGF is used, this CGF may also be used by other, i.e. non-5GCS, network elements, according to network design and operator decision. It should be noted that the CGF may also be an integrated component of the BD – in this case, the Bd interface does not exist and is replaced by a proprietary solution internal to the BD.

Figure 4.2.2-1 depicts the architectural options for converged charging with support of MnS producer.

Figure 4.2.2-1: Converged charging architecture with MnS producer enabled by CEF

4.2.3 Converged charging architecture with CTF embedded in EES

The EES embedding the CTF, generates charging events towards the CHF for edge enabling services usage.

Figure 4.2.3-1 depicts the architectural options for converged charging of edge enabling services.

Figure 4.2.3-1: Converged charging architecture with CTF embedded in EES

Figure 4.2.3-2 depicts the edge enabling services charging architecture in reference point representation.

Figure 4.2.3-2: Edge enabling services charging architecture in reference point representation