Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 26.501  Word version:  19.2.0

Top   Top   Up   Prev   Next
1…   4…   4.1…   4.2…   4.3…   4.4   4.5…   4.6…   4.7…   4.8   4.9…   4.10…   4.11…   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.7.9…   5.8…   5.10…   5.10.3   5.10.4   5.10.5…   5.10.6…   5.10.7   5.11…   5.12…   5.12.3   5.12.4…   5.12.5…   5.13…   5.14…   6…   6.2…   6.2.2.2…   6.2.3…   6.3…   6.4…   6.8…   6.9…   6.9.5…   6.9.7   6.9.8…   7…   8…   8.2   9…   A…   A.4…   A.8…   A.11…   A.13…   A.15…   A.16…   B…   C…   D…   E…   F…   G…   G.2…   G.3…   H…

 

F  Network Slice selection for 5GMS |R19|p. 279

F.1  Introductionp. 279

Clause 5 and clause 6 of the present document describe the high-level procedures for downlink and uplink media streaming respectively. As part of these procedures, the 5GMS Application Provider performs service provisioning at the 5GMS AF. The 5GMS-Aware Application subsequently receives Service Access Information from the 5GMS Application Provider over reference point M8 or else the Media Session Handler acquires it directly from the 5GMS AF over reference point M5. This annex describes an example method for network slice selection based on traffic description information inside URSP rules for bootstrapping 5GMS application invocation on a Network Slice.
Up

F.2  Network Slice selection based on Application Descriptor in URSP rulesp. 279

From clause 5.15.5.2.2 of TS 23.501, the UE uses either the URSP rules (which includes the NSSP) or the UE local configuration to determine which PDU Sessions to use to route ongoing application traffic. Clause 6.6.2.1 of TS 23.503 describes the structure of URSP rules. One of the components of a URSP rule is the Traffic description information that helps a UE to identify matching application traffic. Table 6.6.2.1-2 of TS 23.503 specifies a number of Traffic descriptor options, one of which is the Application descriptor that identifies traffic of applications running on the UE. An Application descriptor consists of OS Id and OS App Id properties that are known to both the UE application and the 5GMS Application Service Provider.
Assumptions:
  • The 5GMS-Aware Application developer is aware of different OS App Ids supported by the UE operating system.
Figure F.2-1 below illustrates the procedure for bootstrapping application invocation on a Network Slice.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. F.2-1: Call flow for bootstrapping application invocation on a Network Slice
Up
The steps are as follows:
Step 1.
The 5GMS-Aware Application is installed on the UE, and and is programmed to invoke an OS-specific network connection API using a pre-defined OS App Id supported by the UE operating system.
Step 2.
The 5GMS Application Provider provisions the media streaming session in the 5GMS AF with one or more network slices at reference point M1. The provisioning information may include external application Id information. The 5GMS AF uses this information to synthesise application traffic descriptor information used for application guidance, as specified in clause 4.15.6.10 of TS 23.502.
Step 3.
The 5GMS AF uses the Nnef_ServiceParameter service defined in clause 5.2.6.1 of TS 23.502 to provide application guidance for URSP determination via the NEF as described in clause 4.15.6.10 of TS 23.502, which is eventually delivered to the UE as described in clause 4.15.6.7 of TS 23.502. The application guidance for URSP includes service parameters such as the application traffic descriptor information (synthesised in the previous step) and Route selection parameters (DNN and S-NSSAI) as specified in clause 4.15.6.10 of TS 23.502.
Step 4.
The 5GMS Application Provider may provide Service Access Information to the 5GMS-Aware Application at reference point M8. In the Service Access Information, the 5GMS Application Provider may include information related to Service Operation Points associated with different Network Slices.
Step 5.
The 5GMS-Aware Application initiates a media streaming session with the 5GMS Client at reference point M6. The 5GMS Client uses an OS-specific UE-internal API to request a network connection for use at reference points M5 (step 10) and M4 (step 11).
Step 6.
Based on the OS App Id configured for the 5GMS-Aware Application in step 1, the UE Operating System enables selection of the appropriate Network Slice using the application descriptor present in the traffic description information inside the currently configured URSP rules.
Step 7.
The UE Operating System checks whether a PDU Session already exists in the selected Network Slice and, if so, selects this PDU Session for further interaction with the media streaming endpoints (steps 10 and 11).
Step 8.
Alternatively, if no PDU Session exists in the Network Slice, the UE Operating System creates a PDU Session using the UE-requested PDU Session establishment procedure specified in clause 4.3.2.2 of TS 23.502.
Step 9.
Once the PDU Session is available, the 5GMS Client interacts with DNS system to resolve the IP address of the 5GMS AF and 5GMS AS instances.
Step 10.
The 5GMS Client interacts with the 5GMS AF for media session handling procedures.
Step 11.
The 5GMS Client interacts with the 5GMS AS for media streaming.
Up

Up   Top   ToC