Page 17 - 3GPP_Highlights_Issue_5_WEB

In order to support this extended architecture, additional data protection mechanisms were deemed necessary by SA4. When the
collection of UE data is provisioned by an ASP at the Data Collection AF, a number of data processing instructions can be specified
to limit the UE data exposed to event consumers. These instructions are expressed in the form of Data Access Profiles as follows:

• For a particular event type, the exact parameters to be • Multiple Data Access Profiles can be provisioned for a given
collected can be limited by each Data Access Profile. event type to vary the data restrictions imposed on different
This permits compliance with one of the key principles of event consumers. When more than one Data Access Profile
data protection legislation that only data necessary for is provisioned, the Data Collection AF selects one based on
specific purposes should be collected. local policy when it receives a new subscription request from
• In addition, each metric of collected UE data can be an event consumer.
summarised along the axes of time, user and/or location • As part of the authorisation procedure for event consumers,
using an aggregation function. For example, rather the Data Collection AF may also collaborate with an external
than exposing events detailing the service experienced Authorization AS, following a similar message exchange
by individual UEs, a particular Data Access Profile may pattern to OAuth.
expose only maximum, minimum and mean average values
aggregated over five-minute intervals.

Instantiation of the reference architecture

The reference architecture for UE data collection, reporting in Release 17 for the 5G Media Streaming (5GMS) data domain.
and exposure defined in TS 26.531 is abstract in the sense that Summarised in the figure below, the detailed definition can be
it is intended to be instantiated inside the architecture of other found in TS 26.501.
data domains. One such instantiation has been defined by SA4

Media Session 5GMS AF
Handler
Network Any NF
Direct UE data Data Collection Event NWDAF Data Analytics (Data analytics
Data Collection reporting AF exposure (Event consumer) exposure consumer)
Client (Event
producer)
Event Figure 3
UE UE data reporting exposure 5GMS
Application Provider
5GMS AS
(Data Collection Event
Client) Consumer AF

Here, the Data Collection Client is realised by the existing
UE-side Media Session Handler component. This uses Future work
existing consumption reporting and QoE metrics reporting
mechanisms to report collected UE data to a Data Collection SA4 expects to instantiate the UE data collection, reporting and
AF realised by the existing 5GMS Application Function. Thus, exposure architecture in other data domains in subsequent
consumption and QoE metrics can be exposed as events 3GPP releases. Hence, there may be more than one concrete
to downstream event exposure subscribers such as a 5GMS instantiation of the Data Collection AF in a given 5G System
Application Provider’s Event Consumer AF. deployment, one for each data domain. And there may be
multiple logical Data Collection Clients running on a UE.
Similarly, invocations of standard media streaming features
such as dynamic QoS policies and network assistance that are Meanwhile, in Release 18, SA2 is studying the feasibility of
already logged by the 5GMS AF can also be exposed as events. exposing the data analytics output of the NWDAF back to UEs
Finally, the media streaming application logs collected by in order to drive feedback loops for Artificial Intelligence and
the 5GMS Application Server can be passed on to the Data Machine Learning applications.
Collection AF for exposure as events. In all, five new event
types are defined in TS 26.532 for these 5GMS features, and
the corresponding data types for exposing them to event
consumers have been added to TS 29.517 by CT3.

|
Issue 05 - No v ember 2 0 22 17