Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 26.501  Word version:  18.6.0

Top   Top   Up   Prev   Next
1…   4…   4.0.6…   4.1…   4.2…   4.2.2…   4.3…   4.4   4.5…   4.6…   4.7…   4.7.4…   4.8   4.9…   4.10…   5…   5.2…   5.2.4   5.2.5…   5.3…   5.3.2…   5.4…   5.5…   5.6…   5.7…   5.7.4…   5.7.8   5.8…   5.10…   5.10.5…   5.10.6…   5.11…   5.12…   5.12.4…   5.12.5…   6…   6.2…   6.2.2.2…   6.2.3…   6.3…   6.4…   6.8…   6.9…   6.9.5…   6.9.7   7…   8…   9…   A…   A.4…   A.8   A.9   A.10   A.11   A.12   A.13   A.14   A.15…   A.15.3…   B…   B.3   C…   C.3   C.4   C.5   D…   E…

 

5.3  Provisioning Session for Media Streamingp. 87

5.3.1  Domain modelp. 87

The M1d baseline domain model is depicted in Figure 5.3.1-1 overleaf. It consists of a Provisioning Session, which contains at least one of the following:
  • A Content Hosting Configuration,
  • A Consumption Reporting Configuration which defines consumption measurement, logging, collection and reporting functionality,
  • A Policy Template,
  • A Metrics Reporting Configuration which defines QoE metrics measurement, logging, collection and reporting functionality,
  • An Edge Resources Configuration specifying the requirements for edge processing as defined in TS 23.548 and TS 23.558 in support of the Provisioning Session, including eligibility criteria that indicate the circumstances in which edge computing is to be used for Media Streaming sessions associated with this Provisioning Session and parameters indicating the tolerance of the application for relocation of the Edge AS, or
  • An Event Data Processing Configuration which contains data manipulation instructions to be performed on UE data by the Data Collection AF including, but not limited to, reporting format conversion, data normalisation, domain-specific anonymisation of data and (dis)aggregation of data into exposed events. This entity includes one or more Data Access Profiles, each one defining a specific access level for controlling the event information exposed to an event consumer.
Each Provisioning Session is uniquely identified within the 5GMS System by a Provisioning Session identifier.
When a certain 5GMS feature is selected, the 5GMSd AF compiles the resulting Service Access Information so that the 5GMSd Client can access the services via M4d and/or M5d.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. 5.3.1-1: M1d provisioning domain model
Figure 5.3.1-1: M1d provisioning domain model
(⇒ copy of original 3GPP image)
Up

Up   Top   ToC