Page 13 - 3GPP_Highlights_Issue_5_WEB

• An intent specifies the expectations including requirements,
goals and constraints for a specific service or network
management workflow. Intent-driven management is
introduced to reduce the complexity of management without
getting into the intricate detail of the underlying network
resources. Intent-driven management works together with
closed-loop automation to continuously satisfy the intent
expectation provided by consumer as shown in the diagram
right. A closed control loop automatically adjusts and optimizes
the services provided over 5G network based on the various
performance management, QoE input data, and the state of the
5G network (TS 28.312/TS 28.535/TS 28.536).

• Management data analytics provides processing, analyzing data related to network and service events and status with utilizing
AI/ML technologies. Recommendations to enable necessary actions for network and service operations may also be
provided (TS 28.104/TS 28.105).

Support of New Services
• Energy Efficiency (EE) KPIs are defined at various granularity levels of 5G networks including Virtualized Network Function (VNF),
5G Core network function, 5G Core network, NG-RAN, network slice of various types. 5G NRM has been augmented with attributes
capturing customer’s expectations in terms of energy efficiency of the network slice being ordered, in relation with GSMA NG.116
attributes (TS 28.310).
• To support vertical requirements on 5G network, Service level agreement requirements are further standardized into
requirements of RAN, CN and transport network correspondingly (TS 28.541).
• Management of non-public network provides the flexible capabilities to manage SNPN and PNI-NPN according to the different
deployment needs from vertical customers. (TS 28.557)

Monetization capabilities introduced for Release 17

Proximity based services charging (TS 32.277)
Proximity based services support by 5GS introduced in Rel-17, is
enhanced by support of the Converged Charging framework, allowing
monetization by Operators when used by 5G ProSe-enabled UEs
being in proximity to each other using NR. 5G ProSe Direct Discovery
charging relies on the 5G Direct Discovery Name Management
Function (5G DDNMF) embedded Charging Trigger Function (CTF)
using CHF Nchf API during UE 5G ProSe Direct Discovery procedures.
5G ProSe Direct Communication over NR (broadcast mode,
groupcast mode, and unicast mode), used for commercial services,
can be monetized based on QoS amongst other criteria. The split
CTF, between UE CTF-(AMC Accounting Metrics Collection) and 5G ProSe Direct Discovery over PC5 reference point and ProSe UE-to-
DDNMF CTF-(ADF Accounting Data Forwarding) enables usage Network Direct Communication are also covered.
reporting from UE to CHF categorized per QoS Flow.

Edge Computing Charging (TS 32.257)
While end user charging for accessing edge applications is already covered from earlier releases under the existing 5G data connectivity
charging (by using dedicated identifications), new areas of Edge Computing (EC) are extended with Charging capabilities in Rel-17 for:
• Edge enabling services exposed by Edge Computing Service Providers (ECSP) to Application Service Providers (ASP) and ECSP edge enabling
infrastructure resources usage by ASP
• Edge Application Server (EAS) deployment (instantiation, upgrade, termination) by an ECSP for an ASP.

Other Enhancements as Partial Conclusion of Ongoing Studies
Charging for roamers with 5G data connectivity is covered since Rel-15,
however only in home routed scenario. Rel-17 introduces a charging
solution for roamers in local breakout covering both wholesale between
MNOs and UEs retail charging. A new N47 reference point enables per
UE quota management from the Home MNO. More solutions are being
studied in Rel-18.
As the result of Network Slice (NS) study partial conclusion, a simplified
option for NS usage charging based on individual UEs 5G data
connectivity charging is enhanced for Rel-17 in a TS 32.255 Annex D. In
this option, the Converged Charging System (CCS) serves individual UEs
as well as NS Tenants based on internal specific implementation, for the
purpose of monetization by Communication Service Providers (CSP) of
NS usage by Tenants.
|
Issue 05 - No v ember 2 0 22 13