Content for TR 22.952 Word version: 18.0.1

0… 4… 4.8… 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 6… A… B B.1 B.2 B.3 B.4 B.5 B.6 B.7 B.8 B.9 C D…

B.1 Priority service call to Priority service subscriber in Priority service + eMLPP network
...

B.1 Priority service call to Priority service subscriber in Priority service + eMLPP network p. 39

This use case is intended to illustrate that the new Priority Service + eMLPP functionality fulfils the Priority Service requirements.

Copy of original 3GPP image for 3GPP TS 22.952, Fig. B.1: Priority Service call to Priority Service subscriber in Priority Service + eMLPP network

Figure B.1: Priority Service call to Priority Service subscriber in Priority Service + eMLPP network
(⇒ copy of original 3GPP image)

Use case 1:

Two Service Users (Priority Service subscribers), each with an assigned Priority Service priority level in the range of Priority Service1 - Priority Service5, belong to two different new networks (A and D) supporting both Priority Service and eMLPP or Priority Service only.
The Service User roam to two different new networks (the Priority Service subscriber in network A roams to network B and the Priority Service subscriber in network D roams to network C) supporting both Priority Service and eMLPP.
The Service User who roamed from network A to network B sets up a Priority Service priority call towards the Service User who roamed from network D to network C.
The call is routed via an intermediate non-3GPP network.

In this use case, the call receives Priority Service treatment (priority access to traffic channels) on the terminating side in (C) according to the Priority Service level Priority Service1 - Priority Service5 as assigned to the Service User calling from (B). Since the end-to-end Priority Service is based on the Priority Service subscription of the calling party, this use case also applies to a called party without Priority Service subscription.

Priority Service calls should not be pre-empted by eMLPP calls.