Page 15 - Highlight_Issue_3_final_web

Autonomous Network standardization in WG SA5 continued...
Intent driven management (e.g. design phase, deployment phase, Summary
Intent is the expectations including maintenance, optimization etc.). An Intent Reaching full AN needs close collaboration
requirements, goals and constraints given driven Management Service (MnS) is used by multiple partners. Standardization of
to a 3GPP system, without specifying for exchanging information between MnS AN helps to guide the industry moving
how to achieve them. An intent specifies Consumer and MnS Producer. Closed-loop towards this goal in a coordinated manner,
the expectations for a specific service or automation may be utilized to support as the discussion is open and welcoming
network management workflow. 3GPP the fulfilment of intent. In the example of all interested parties working together and
intents could be categorized by user types ANL for network optimization, the intent tackle technical challenges.
(e.g. communication service customer, handling related tasks A and B start being
communication service provider or network achieved as partial autonomy from ANL 4.
operator) or by management scenarios

REL-17 EDGE COMPUTING

AND NETWORK

SLICING CHARGING

By Maryse Gardella, recent past SA5 Vice-Chair
and Gerald Görmer, SA5 Vice-Chair.

The start of “Charging aspects of Edge Computing (EC)” normative Edge Computing Service Providers (ECSP), such as edge enabling
work was approved at TSG#93e, after the study phase was services (e.g. Edge Application Servers (EAS) registration) or
partially concluded. Beyond monetizing usage by end users of 5GS infrastructure resources (e.g. virtual CPU, virtual memory, virtual
EC capabilities (e.g. for accessing Edge applications), monetizing disk and virtual network resources).
usage by providers of EC services is also a key focus.
The figure below shows a preliminary framework for monetizing
One of the covered scenarios is the monetization of the usage usage of edge enabling services, built on the TS 23.558
by Application Service Providers (ASP) of services offered by architecture - extended with charging capabilities.

Edge Data Network
UE Edge
3GPP Core EDGE-7 Application
Server(s)
Network
Application EAS registration, Converged
charging
Client(s) EDGE-3 UE location, system
Session with QoS, (CCS)
AC information
EDGE-5 subscription Nchf
EAS discovery, Application Context Relocation CHF
CTF
EDGE-1 Edge Enabler
Server(s)
EDGE-2 EDGE-9
Edge Enabler
Client EDGE-6
EDGE-4
Edge
Configuration
Server TM
EDGE-8
Initial charging solutions for Network Slicing were introduced in maximum number of concurrent PDU sessions or maximum
Rel-16, on Network slice (NS) management (TS 28.202) and NS number of UEs per NS - are considered for charging solutions.
performance and analytics (TS 28.201). The solutions rely on a These solutions may allow for flexible rating for the Tenant,
new Charging Enabler Function (CEF) which consumes services depending on actual numbers of PDU sessions or UEs per NS.
exposed by Management Service (MnS) Producer and Network NS total volume consumption (aggregated UEs PDU sessions
Data Analytics Function (NWDAF), interacting with the CHF via volume) and total duration (from activation of the first PDU
the SBI Nchf interface.
session to deactivation of the last active one) are additional NS
The Rel-17 NS charging aspects study investigates further areas charging criteria being considered.
for the monetization by Communication Service Providers (CSP)
of NS usage by Tenants. Some scalability attributes of the Generic More about 3GPP WG SA5 and Management, Orchestration and
Network Slice Template (GST) defined by GSMA - such as the Charging is found at: www.3gpp.org/specifications-groups
|
I ssue 03 - O ct ober 2021 15