Content for  TR 22.952  Word version:  17.0.0

Top   Top   Up   Prev   Next
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…


5.13  Priority service call attempt by a non-service-user - Priority service deniedp. 31

This clause illustrates the call setup of a non-Priority Service user attempting a Priority Service call. In this scenario, the user is not subscribed to Priority Service and call setup is not allowed to proceed.
Copy of original 3GPP image for 3GPP TS 22.952, Fig. 5.13: Non-Priority Service user - Denied
Figure 5.13: Non-Priority Service user - Denied
(⇒ copy of original 3GPP image)
A non-Service User dials the Priority Service prefix (e.g., *272) + Destination Number. The MS sends a Channel Request message to the BSS on the RACH channel. Having sent M + 1 Channel Request messages, the MS starts RR timer T3126. M is the value of the parameter "max retrans" broadcast on the BCCH.
Same as described in steps A-E of Clause 5.1.
The MSC/VLR detects the Priority Service prefix (e.g., *272) in the dialled digit string. The MSC/VLR determines from the caller's profile that the caller is not a Service User and rejects the request by stopping all running CC timers, responding with a Release Complete message to the MS with cause #63 "Service or option not available, unspecified", and releasing the MM connection.
On receipt of the Release Complete message, the MS stops all running CC timers and releases the MM connection. The MSC/VLR indicates that the radio resource(s) should be released by sending a Clear Command message to the BSS with cause "Response to MSC invocation".
Same as described in steps M-N of Clause 5.5.

Up   Top   ToC