Content for  TR 22.835  Word version:  18.2.0

This use case intends to bring a use case for network slice to support important applications like gaming and online video in a more flexible and efficient way. For gaming or online video applications, the end users, who have subscription with MNOs who may provide multiple network slices to different users or services, may still have different priority or membership e.g. VIP maintained by 3rd party Service Provider (SP). And depending on the priority or membership information from 3rd party SP perspective, based on the agreement between SP and MNO, the UE have different priority for the available network slices. Figure 5.7.1-1 shows an example scenario for this use case.

1. MNO provisioned network slices Slice#1, Slice#2, Slice#3. As an example, Slice#1 is dedicated for online video services for SP#1. Slice#2 is dedicated for gaming for SP#2. Slice#3 is a network slice for eMBB service i.e. text or voice chat, file downloading or web surfing.
2. UE 1 and UE 2 are registered to MNO's 5G network and they have subscription to slice#1, #2 and #3. The owner of UE 1, i.e., User A, have installed Game App x and Video App y. The owner of UE 2, i.e., User B, have installed Game App z and Video App y.
3. User A and User B are high priority users for SP#1 and SP#2 which means when these users start to use game or video app, they can use the corresponding network slice to guarantee their QoS compared with other users with lower priority and the MNO network resource can accommodate high priority users.
4. Due to the fact that the 3rd party SP may roll out new services/applications and the users may change their VIP membership dynamically, the 3rd party needs to negotiate the priority of a network slice for UE per application.

1. MNO and SP have agreements e.g. SLA and Slice#1, Slice#2 and Slice#3 are provisioned.
   1. The MNO provisioned the slices and maintains the user subscription to access these slices. The SP maintains the application related user membership information.
   2. UE 1 and UE 2 may or may not be accessing three slices simultaneously.
2. User A's smart phone UE 1, and User B's smart phone UE 2 turns on and registered to MNO network. After registration, UE 1 and UE 2 are able to access corresponding network slices.
   1. User A can access Slice#1 for online video app x and Slice#2 for gaming, also Slice#3 for other services.
   2. User B can access Slice#1 for online video y and gaming app z, and also Slice#3 for other services.
3. User A and User B started chat and web surfing service, it accesses network Slice#3
4. User A started online video, UE A access to Slice#3 which can only provide a basic SLA for the online video e.g. with lower resolution1.
5. User A's priority for slices is dynamically changed due to the SP side updates e.g. User A changes his/her VIP. membership, thus different SLA is provided to User A's online video via Slice#1..
6. User B started game app, UE B access to Slice #3 which can only provide a basic SLA for the game service e.g. with lower resolution and low latency is not ensured.
7. User B's priority for slices is dynamically changed due to the SP side updates e.g. User B changes his/her VIP membership, thus different SLA is provided to User A's game app via Slice#2.
8. User A's priority for slices are changed back to original value due the SP side update e.g. VIP membership. expired, thus the online video is provided via Slice#3.
9. User B's priority for slices are changed back to original value due to SP side update e.g. VIP membership expired, thus the game app is provided via Slice#3.

In the above service flows, the different slices may be provided by same or different frequency and the coverage may be different. If different slices are deployed in different frequency bands, access of different network slices due to application should not cause degradation of user experiences.

SP and MNO may monitor the QoS of online video and game applications and also support flexible charging for these users which change their priority accessed slices per application.

In Clause 6.1.2 of TS 22.261, network slicing requirements are specified including general, management, network slice constraints and cross-network slice coordination. In clause 6.1.2.2 of TS 22.261, there is a requirement as follows: This requirement enables priority mechanism from network resource configuration perspective. In clause 6.1.2.2 of TS 22.261, there is another requirement as follows: This requirement is from operator perspective and doesn't cover the aspect whether 3rd party application can influent the priority of network slices. The existing requirements for network slicing, e.g. which is cited in this section, is from network resource configuration perspective. However, when UE can access multiple network slices which may be tailored for different applications, there is no support of changing the priority or the preferred network slicing for the UE based on application. And this process cannot be carried out efficiently without standard-based means for MNO and third party to communicate/negotiate the preferred network slices according to application. For this use case, additional two requirements below are considered already supported:

• The 5G system shall support means to dynamically change the UE priority of network slices per application with minimized interruption, according to third party's policy.
• The 5G system shall support mechanisms to allow a 3rd party and the 5G network to negotiate the UE priority of a network slice per application.

No new requirement is derived from this use case.