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 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.8 An eMLPP subscriber roams to a Priority service + eMLPP network and initiates a call with the Priority service service code
...

B.8 An eMLPP subscriber roams to a Priority service + eMLPP network and initiates a call with the Priority service service code p. 46

This use case is intended to illustrate that eMLPP subscribers are not able to initiate Priority Service calls.

Copy of original 3GPP image for 3GPP TS 22.952, Fig. B.8: An eMLPP subscriber roams to a Priority Service + eMLPP network and initiates a call with the Priority Service service code

Figure B.8: An eMLPP subscriber roams to a Priority Service + eMLPP network and initiates a call with the Priority Service service code
(⇒ copy of original 3GPP image)

Use case 8:

An eMLPP subscriber belongs to a new network (A) supporting both Priority Service and eMLPP.
The eMLPP subscriber roams to a new network (B) supporting both Priority Service and eMLPP.
The eMLPP subscriber in (B) tries to initiate a Priority Service call using the Priority Service service code.
The call set-up is rejected by network (B).

In this use case, the attempted call set-up attempt in (B) is denied as the eMLPP subscriber is not allowed to initiate Priority Service calls.