Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑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… 
6.2.2.2 Baseline provisioning procedure  6.2.2.3 Baseline provisioning procedure with authorisation 
...

 

6.2.2.2  Baseline provisioning procedure |R18|  p. 156

This clause describes the baseline procedure to provision the features using the 5GMS System.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. 6.2.2.2-1: High-level procedure for provisioning the 5GMS System for uplink media streaming sessions
Figure 6.2.2.2-1: High-level procedure for provisioning the 5GMS System for uplink media streaming sessions
(⇒ copy of original 3GPP image)
Up
Steps:
Step 1.
The 5GMSu Application Provider authenticates itself with the system. This procedure reuses existing authentication/authorization procedures, e.g., as defined for CAPIF TS 23.222.
Step 2.
The 5GMSu Application Provider creates a Provisioning Session, providing its 5GMSu Application Provider identifier as input. 5GMSu Application Provider queries the capabilities and authorized features.
Step 3.
The 5GMSuApplication Provider specifies one or more 5GMSu features in the Provisioning Session. A set of authorized features is activated, such as content dynamic policy; network assistance; and content publishing (including egest). When the content publishing feature is offered and selected, the 5GMS Application Provider provides a Content Publishing Configuration to configure the content publishing behaviour of the 5GMSu AS (see next step), including selecting the uplink ingest protocol and format, content preparation and egest protocol and format.
When the dynamic policy feature is offered and selected, the 5GMSu Application Provider specifies a set of policies which can be invoked for the uplink streaming session. The UE becomes aware of the selected policies in the form of a list of valid Policy Template Ids.
When the edge computing feature is offered and selected, the 5GMSu Application Provider provides one or more Edge Resources Configurations that can be used to support either client-driven management or Application Provider-driven management of edge resources associated with the Provisioning Session.
Step 4.
When content publication is desired, the 5GMSu AF interacts with the 5GMSu AS at reference point M3u to configure any necessary Server Certificates and/or Content Publishing Templates and to allocate resources for M2u egest protocol and format by means of a Content Publishing Configuration. The 5GMSu AS responds to the 5GMSu AF with the M2u content egest address.
Step 5.
The 5GMSu AF compiles the Service Access Information. The Service Access Information contains access details and options such as the Provisioning Session identifier, M5u (Media Session Handling) addresses for uplink entry point, dynamic policy, network assistance, etc.
Step 6.
The 5GMSu AF provides the results to the 5GMSu Application Provider.
The following steps:
Step 7.
When the 5GMSu Application Provider has selected full Service Access Information, the results are provided in the form of addresses and configurations for M2u (content egest), M5u (Media Session Handling) and M4u (Media Uplink Streaming). The 5GMSu Application Provider provides a subset of this information to the 5GMSu-Aware Application through M8u.
Step 8.
When the 5GMSu-Aware Application decides to activate the streaming service transmission, the Service Access Information is provided to the 5GMSu Client.
Step 9.
The 5GMSu Client requests the 5GMSu AF to initialise uplink media streaming (M5u), including reservation of any resources required for content preparation.
Or, alternatively:
Step 10.
The 5GMS-Aware Application requests the 5GMSu Client to start an uplink streaming session (M6u/M7u).
Step 11.
When the 5GMSu Application Provider has delegated Service Access Information handling to the 5GMS System, a reference to the Service Access Information (e.g. an URL) is provided. The Media Session Handler fetches the full Service Access Information later from the 5GMSu AF.
Then:
Step 12.
The 5GMSu Client streams the content to the 5GMSu AS.
Step 13.
When content publishing is offered and has been selected in step 4, the 5GMSu Application Provider can start retrieving the content from the M2u egest interface.
Optionally:
Step 14.
The 5GMSu Application Provider may update the Provisioning Session.
According to schedule, or upon request by the 5GMSu-Aware Application:
Step 15.
The 5GMSu Application Provider may manually terminate the Provisioning Session (at any time). All associated resources are released. Content may be removed from the 5GMSu AS. The 5GMSd Application Provider may configure a schedule for Provisioning Session termination.
Step 16.
The 5GMSu AF sends a notification to the 5GMSu Client upon Provisioning Session termination.
The 5GMSu AF may request the creation or reuse of one or more network slices for ingesting the content of the provisioned session. If more than one network slice is provisioned for the ingest of the content of a session, the list of allowed S-NSSAIs shall be conveyed to the target UE (e.g. through URSP or through M8u, step 7, or M5u, step 10).
Up

6.2.2.3  Baseline provisioning procedure with authorisation |R18|  p. 158

This clause describes the baseline procedure to provision the features using the 5GMS System with authorisation of the 5GMSu Application Provider to support subsequent authorisation of media session handling for uplink media streaming per clause 5.2.5. When CAPIF is used, the authorization server is realised by the CAPIF core function, as shown in Figure 6.2.2.3-1 (a). Otherwise, the authorization server is realised by the 5GMSu AF, as shown in Figure 6.2.2.3-1 (b).
Copy of original 3GPP image for 3GPP TS 26.501, Fig. 6.2.2.3-1: Alternative deployments of authorization server
Figure 6.2.2.3-1: Alternative deployments of authorization server
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 26.501, Fig. 6.2.2.3-2: High-level procedure for provisioning the 5GMS System for uplink media streaming sessions
Figure 6.2.2.3-2: High-level procedure for provisioning the 5GMS System for uplink media streaming sessions
(⇒ copy of original 3GPP image)
Up
Steps:
Step 1.
The 5GMSu Application Provider discovers the address (URL) of the 5GMSu AF (M1) for Session Provisioning. During the self-onboarding procedure, the 5GMSu Application Provider obtains the API access credentials.
Step 2.
The 5GMSu Application Provider authenticates itself with the system. This procedure reuses existing authentication/authorisation procedures, e.g., leveraging CAPIF-1/1e TS 23.222 or by the 5GMSu AF acting as OAuth authorization server. The 5GMSu AF acts as OAuth resource server. The 5GMSu Application Provider obtains an access token which is used for any subsequent operation invocations at reference point M1. The 5GMSu Application Provider creates a Provisioning Session, providing its 5GMSu Application Provider identifier as input. 5GMSu Application Provider queries the capabilities and authorised features.
Step 3.
The 5GMSuApplication Provider specifies one or more 5GMSu features in the Provisioning Session. A set of authorised features is activated, such as content dynamic policy; network assistance; and content publishing (including egest).
When the content publishing feature is offered and selected, the 5GMS Application Provider provides a Content Publishing Configuration to configure the content publishing behaviour of the 5GMSu AS (see next step), including selecting the uplink ingest protocol and format, content preparation and egest protocol and format.
When the dynamic policy feature is offered and selected, the 5GMSu Application Provider specifies a set of policies which can be invoked for the uplink streaming session. The UE becomes aware of the selected policies in the form of a list of valid Policy Template Ids.
When the edge computing feature is offered and selected, the 5GMSu Application Provider provides one or more Edge Resources Configurations that can be used to support either client-driven management or Application Provider-driven management of edge resources associated with the Provisioning Session.
Step 4.
When content publication is desired, the 5GMSu AF interacts with the 5GMSu AS at reference point M3u to configure any necessary Server Certificates and/or Content Publishing Templates and to allocate resources for M2u egest protocol and format by means of a Content Publishing Configuration. The 5GMSu AS responds to the 5GMSu AF with the M2u content egest address.
Step 5.
The 5GMSu AF compiles the Service Access Information. The Service Access Information contains access details and options such as the Provisioning Session identifier, M5u (Media Session Handling) addresses for uplink entry point, dynamic policy, network assistance, etc.
Step 6.
The 5GMSu AF provides the results to the 5GMSu Application Provider.
The following steps:
Step 7.
When the 5GMSu Application Provider has selected full Service Access Information, the results are provided in the form of addresses and configurations for M2u (content egest), M5u (Media Session Handling) and M4u (Media Uplink Streaming). The 5GMSu Application Provider provides a subset of this information to the 5GMSu-Aware Application through M8u.
Step 8.
When the 5GMSu-Aware Application decides to activate the streaming service transmission, the Service Access Information is provided to the 5GMSu Client.
Step 9.
The 5GMSu Client requests the 5GMSu AF to initialise uplink media streaming (M5u), including reservation of any resources required for content preparation.
Or, alternatively:
Step 10.
The 5GMS-Aware Application requests the 5GMSu Client to start an uplink streaming session (M6u/M7u).
Step 11.
When the 5GMSu Application Provider has delegated Service Access Information handling to the 5GMS System, a reference to the Service Access Information (e.g. an URL) is provided. The Media Session Handler fetches the full Service Access Information later from the 5GMSu AF.
Then:
Step 12.
The 5GMSu Client streams the content to the 5GMSu AS.
Step 13.
When content publishing is offered and has been selected in step 4, the 5GMSu Application Provider can start retrieving the content from the M2u egest interface.
Optionally:
Step 14.
The 5GMSu Application Provider may update the Provisioning Session.
According to schedule, or upon request by the 5GMSu-Aware Application:
Step 15.
The 5GMSu Application Provider may manually terminate the Provisioning Session (at any time). All associated resources are released. Content may be removed from the 5GMSu AS. The 5GMSd Application Provider may configure a schedule for Provisioning Session termination.
Step 16.
The 5GMSu AF sends a notification to the 5GMSu Client upon Provisioning Session termination.
The 5GMSu AF may request the creation or reuse of one or more network slices for ingesting the content of the provisioned session. If more than one network slice is provisioned for the ingest of the content of a session, the list of allowed S-NSSAIs shall be conveyed to the target UE (e.g. through URSP or through M8u, step 7, or M5u, step 10).
Up

Up   Top   ToC