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.5 eMLPP call to Priority service subscriber in Priority service + eMLPP network
...

B.5 eMLPP call to Priority service subscriber in Priority service + eMLPP network p. 43

This use case is intended to illustrate that Priority Service is not disturbed by eMLPP for eMLPP calls.

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

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

Use case 5:

An eMLPP subscriber with assigned maximum and default priority (precedence) levels in the range of eMLPP1 - eMLPP7 belongs to a new network (A) supporting both Priority Service and eMLPP or eMLPP only.
The eMLPP subscriber roams to a new network (B) supporting both Priority Service and eMLPP where she will have priority (precedence) levels in the range of eMLPP3 - eMLPP7.
A Service User with an assigned Priority Service level in the range of Priority Service1 - Priority Service5 belongs to a new network (D) supporting Priority Service + eMLPP or Priority Service only.
The Service User roams to a new network (C) supporting both Priority Service and eMLPP.
The eMLPP subscriber in (B) sets up an eMLPP call towards the Service User in (C).
The call is routed via an intermediate non-3GPP network.

In this use case, the call terminating in (C) is treated as a terminating eMLPP call with the priority level either as requested by the calling subscriber at the call set-up in (B) or, if not requested at call set-up, according to the default priority level assigned to the calling eMLPP subscriber. Priority Service calls should not be pre-empted by eMLPP calls.