3GPP2 X.

S0004-321-E

v 2.0

Date: January 2009

Mobile Application Part (MAP) -

VOICE FEATURE SCENARIOS: CALL DELIVERY

COPYRIGHT
3GPP2 and its Organizational Partners claim copyright in this document and individual OPs may
copyright and issue documents or standards publications in individual Organizationial Partner’s
name based on this document. Requests for reproduction of this document should be directed to the
3GPP2 Secretariat at secretariat@3gpp2.org. Requests to reproduce individual Organizationial Part-
ner’s documents should be directed to that Organizational Partner. See www.3gpp2.org for more
information.
1
2 REVISION HISTORY
3
4 Revision Date Remarks
5
6
X.S0004-321-E v1.0 January 2007 Initial publication.
7 X.S0004-321-E v2.0 January 2009 Addition of sections: 1.13, 1.14,
8 1.15, 1.16 based on Miscellaneous
9 Enhancements 10.0
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

ii
 X.S0004-321-E v2.0

1
2 1 Call Delivery
3
4 This section depicts the interactions between network entities in various situations related to
5
automatic roaming and Call Delivery (CD). These scenarios are informative.
6
7
8
9
1.1 CD Demand Activation or De-Activation
10
11
For a description of the demand activation or deactivation of CD by an authorized MS, see
12
Part 311 Section 2.1.
13
14
15 1.2 CD Invocation to an Idle MS on Another MSC
16
17 This scenario describes call delivery to an MS that is outside the serving area of the MSC where
18 the call originates. MSCs in the functional model described in NAM contain switching functions
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

321-1 Call Delivery

X.S0004-321-E v2.0

only and must interact with their associated HLR and VLR to obtain database information for 1
2
an MS; in a real application, the HLR/VLR functions may be integrated with the MSC.
3
4
5
Originating System Serving System 6
7
8
MSC HLR VLR MSC
9
10
11
call origination
a 12
13
LOCREQ [DGTSDIAL]
b 14
15
LOCREQ [DGTSDIAL] 16
c
17
LRT RRT
ROUTREQ [MSID] 18
d
19

QUALREQ 20
e 21
22
QUALREQ
f 23
QRT RRT QRT 24
qualreq
g 25
26
qualreq 27
h
28
routreq [TLDN] 29
i
30
routreq [TLDN] 31
j 32
TLDNAT 33
locreq [TERMLIST, REDIND]
k 34
35
call setup
l 36
37
38
Figure 1 — CD Invocation to an Idle MS on Another MSC 39
40

a. A call origination and the dialed MS address digits (i.e., directory number) are received 41

by the Originating MSC. 42

43
b. The Originating MSC sends a LOCREQ to the HLR associated with the MS; this 44
association is made through the dialed MS address digits (which may not be the MIN). 45
c. If the dialed MS address digits are assigned to a legitimate subscriber, the HLR sends 46

a ROUTREQ to the VLR where the MS is registered. 47

48
d. The VLR then forwards the ROUTREQ to the current Serving MSC. Note that the MS
49
may have roamed within the domain of the Serving VLR and reported its new location 50
to that VLR (via the new Serving MSC); the Serving VLR may not have reported this 51
change in location to the HLR. 52

In reaction to the ROUTREQ, the Serving MSC consults its internal data structures to 53

determine if the MS is already engaged in a call on this MSC. In this scenario, since 54

the MS is idle, we are assuming that the MS is not known to the Serving MSC. 55
56
e. The Serving MSC may then obtain the service profile of the MS from its VLR by
57
sending it a QUALREQ.
58
59
60

Call Delivery 321-2

 X.S0004-321-E v2.0

1 This step can be eliminated if the service profile is obtained by the Serving MSC prior
2 to the termination attempt (e.g., when the MS registers). Subsequent scenarios do not
3 explicitly show this step; they assume that the Serving MSC either already has the
4 profile available when the ROUTREQ arrives or obtains the profile in a manner similar
5 to that shown here.
6
f. If the MS is unknown to the VLR or if the information requested by the MSC is not
7
8
available at the VLR, the VLR sends a QUALREQ to the HLR associated with the MS.
9 g. The HLR sends a qualreq to the VLR.
10
h. The VLR sends a qualreq to the Serving MSC.
11
12
i. The Serving MSC allocates a TLDN (Temporary Local Directory Number) and returns
13 this information to the VLR in the routreq.
14 j. The VLR sends the routreq to the HLR.
15
k. When the routreq is received by the HLR, it returns a locreq to the Originating
16
17
MSC. The locreq includes routing information in the form of the TerminationList
18
parameter, along with an indication of the reason for extending the incoming call (i.e.,
19 for CD) in the DMH_RedirectionIndicator parameter.
20 l. The Originating MSC establishes a voice path to the Serving MSC using existing
21 interconnection protocols (e.g. SS7) and the routing information specified in the
22
locreq.
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

321-3 Call Delivery

X.S0004-321-E v2.0

1.3 CD Invocation to an Idle, Local MS 1

2
3
This scenario describes CD invocation to an idle MS that is served by the MSC where the call 4
originates. 5
6
7

Originating System 8
9
10
MSC MS HLR 11
12
13
call origination
a 14
15
LOCREQ [DGTSDIAL]
b 16
17
LRT
locreq [TERMLIST, REDIND] 18
c
19
call termination 20
d
21
22

Figure 2 — CD Invocation to an Idle, Local MS 23

24
25
a. A call origination and the dialed MS address digits (i.e., directory number) are received
26
by the Originating MSC.
27
b. The Originating MSC sends a LOCREQ to the HLR associated with the MS; this 28
association is made through the dialed MS address digits (which may not be the MIN). 29
30
c. If the dialed MS address digits are assigned to a legitimate subscriber and the HLR
31
determines that the subscriber is currently served by the Originating MSC, the HLR
32
sends a locreq to the Originating MSC.
33
d. The Originating MSC, recognizing itself as the Serving MSC via the MSCID 34
parameter contained in the TerminationList parameter, then attempts to terminate the 35
call to the MS identified in the locreq. 36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Call Delivery 321-4

 X.S0004-321-E v2.0

1
2
1.4 CD Invocation to a Busy MS
3
4
This scenario describes CD invocation to an MS that is busy in a call outside of the serving area
5
where the call originates.
6
7
8
Originating System Serving System
9
10
11 MSC HLR VLR MSC
12
13
14 call origination
a
15
16 LOCREQ [DGTSDIAL]
b
17
18 ROUTREQ [MSID]
19 c
20
ROUTREQ [MSID]
21 d
22
LRT RRT RRT
routreq [ACCDEN=Busy]
23 e
24
25 routreq [ACCDEN=Busy]
f
26
27 locreq [ACCDEN=Busy]
g
28
29 busy indication
30
h
31
32 Figure 3 — CD Invocation to a Busy MS
33
34 a-d. Same as CD, see Part 321, sec. 1.2, Steps a-d.
35
e. In reaction to the ROUTREQ, the Serving MSC checks its internal data structures and
36
37
determines that the MS is busy in another call. The status of the MS is returned to the
38 VLR by the Serving MSC via the AccessDeniedReason parameter in the routreq.1
39
f. The VLR sends the routreq to the HLR.
40
41
g. The HLR returns the busy status to the Originating MSC in the locreq.
42 h. The Originating MSC then returns a busy indication to the calling party.
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
1
58 In some environments it may be necessary to return a TLDN in addition to, or in place of, the MS status.
59 Handling of these situations is not illustrated by the above figure.
60

321-5 Call Delivery

X.S0004-321-E v2.0

1.5 CD Invocation with No Page Response or No Answer 1

2
3
This scenario describes CD invocation to an MS when no page response or no answer is 4
received by the Serving MSC after TLDN call arrival. 5
6
7
8
Originating System Serving System
9
10
MSC HLR VLR MSC 11
12
13
call origination 14
a
15
LOCREQ [DGTSDIAL] 16
b
17

ROUTREQ [MSID] 18
c 19
20
ROUTREQ [MSID]
d 21
LRT RRT RRT 22
routreq [TLDN]
e 23
24
routreq [TLDN]
25
f
26
locreq [TERMLIST, REDIND] 27
g
28
call setup 29
h 30
31
page or answer
timeout i 32
33
announcement
j 34
35
call release call release
k 36
37
38
Figure 4 — CD Invocation with No Page Response or No Answer 39
40

a-d. Same as CD, see Part 321, sec. 1.2, Steps a-d. 41
42
e-h. Same as CD, see Part 321, sec. 1.2, Steps i-l, respectively.
43
i. Either the MS fails to respond to the page or does not answer after alerting. 44

j. The Serving MSC routes the call to an appropriate tone or announcement. 45

46
k. The call is then disconnected using the protocols defined by the interconnection
47
method. 48
49
50
51
52
53
54
55
56
57
58
59
60

Call Delivery 321-6

 X.S0004-321-E v2.0

1
2
1.6 CD Invocation to an Inaccessible MS
3
4
This scenario describes CD invocation to an MS that is inaccessible due to:
5
• CD inactive,
6
7 • MS inactive
8
9 • MS unregistered.
10
11
12
Originating System
13
14
15 MSC HLR
16
17
call origination
18 a
19
LOCREQ [DGTSDIAL]
20 b
21
LRT
22 locreq [ACCDEN, ANNLIST]
c
23
24 call refusal treatment
d
25
26 call release
27 e
28
29 Figure 5 — CD Invocation to an Inaccessible MS
30
31 a-b. Same as CD, see Part 321, sec. 1.2, Steps a-b.
32
c. The HLR determines that the MS is not accessible (e.g., CD is inactive, MS is inactive,
33
or MS is not registered). The HLR returns a locreq to the Originating MSC including
34
35
the reason for denying access in the AccessDeniedReason parameter.
36 d. The Originating MSC provides treatment to the served MS as implied by the
37 AccessDeniedReason parameter and, if present, the AnnouncementList parameter. In
38 this case, the treatment is to provide call refusal treatment.
39
e. The Originating MSC releases the call.
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

321-7 Call Delivery

X.S0004-321-E v2.0

1.7 CD Invocation with Intersystem Paging 1

2
3
This scenario describes CD invocation involving intersystem paging from the serving system to 4
border systems. Intersystem paging may help overcome location uncertainties in border system 5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Call Delivery 321-8

 X.S0004-321-E v2.0

1 areas allowing paging to be performed in border systems and by performing call routing towards
2
the system where the subscriber is found.
3
4
5
6 Originating System Serving System Border System
7
8
9 MSC HLR VLR MSC VLR MSC
10
11
12
13 call origination
14 a
15 LOCREQ [DGTSDIAL]
b
16
ROUTREQ [MSID]
17 c
18 ROUTREQ [MSID]
19
d
20 page request e
21
ISPAGE [PageIndicator]
22 f
23 LRT RRT RRT ISPRT page response g
24
25 QUALREQ
h
26 QUALREQ
27 i
28 qualreq QRT QRT
j
29
qualreq
30 k
31 ispage [TLDN, EXTMSCID(Border)]
32 l
33 routreq [TLDN, MSCID]
m
34
routreq [TLDN, MSCID]
35 n
36 locreq [TERMLIST, REDIND]
37
o
REGNOT
38
p
39
REGNOT
40 q
TLDNAT
41 REGCANC
r
42
43
REGCANC
s
44 RCT RCT regcanc RNT RNT
45 t
46 regcanc
u
47
regnot
48 v
49 regnot
50 w
51 call setup
x
52
53
54
Figure 6 — CD Invocation with Intersystem Paging
55
56 a-d. Same as CD, see Part 321, sec. 1.2, Steps a-d.
57 e-f. Before initiating local paging, at the time of local page initiation or after first page
58 time-out, the Serving MSC may send an ISPAGE to one or more bordering MSCs
59 according to its “topographical map” with a parameter indicating an area where the
60

321-9 Call Delivery

X.S0004-321-E v2.0

subscriber's presence was last detected and a parameter indicating whether to page or 1

just listen for an unsolicited page response. This ISPAGE contains the MSCID of the 2

Originating MSC in order that subsequent message exchanges work properly. The 3

Serving MSC also passes the information needed if call redirection is required. 4
5
The Border MSC that receives the ISPAGE may initiate paging (i.e., if directed).
6
g. If a page response is received at the Border MSC... 7

h. Optionally the Border MSC sends a QUALREQ to the VLR indicating Border Access. 8
9
i. If the service profile of the MS is unknown to the VLR, it sends a QUALREQ to the
10
HLR associated with the MS. 11
j. The HLR sends a qualreq to the Border MSC's VLR, including the MS's service 12
profile information. 13
14
k. The VLR sends a qualreq to the Border MSC, including the MS's service profile
15
information. The Border MSC then assigns the MS to a traffic channel and allocates a
16
TLDN. The Border MSC further confirms the MS's presence (e.g., via SAT detection, 17
through a traffic channel audit, or both). 18
If the MS is authentication capable, optionally authenticate it using a control channel, 19
or a traffic channel (see Part 310). 20
21
l. When the Border MSC assigns the MS to a traffic channel, the Border MSC sends an
22
ispage containing a TLDN and the MSCID of the Border MSC to the Serving MSC.
23
m. The Serving MSC returns a routreq to the Serving VLR with the TLDN contained 24
in the ispage and the MSCID of the Border MSC. 25

n. The Serving VLR returns the routreq to the HLR. 26

27
o. The HLR then sends a locreq to the Originating MSC. The locreq includes 28
routing information in the form of the TerminationList parameter, along with an 29
indication of the reason for extending the incoming call (i.e., for CD) in the 30
DMH_RedirectionIndicator parameter. 31

p. After responding to the ISPAGE, the Border MSC sends a REGNOT to the Border 32
33
VLR.
34
q. The Border VLR sends a REGNOT to the HLR. 35
r. The HLR cancels the registration at the visited serving system by sending a REGCANC 36

to the Serving VLR. 37

38
s. The Serving VLR sends a REGCANC to the Serving MSC.
39
t. The Serving MSC returns a regcanc to the Serving VLR. 40

u. The Serving VLR returns a regcanc to the HLR. 41

42
v. The HLR returns a regnot to the Border VLR. 43
w. The Border VLR returns a regnot to the Border MSC. 44
45
x. The Originating MSC establishes a voice path to the Border MSC using existing
46
interconnection protocols (e.g., SS7) and the routing information specified in the
47
locreq.
48
Note: If the Border MSC must initiate call redirection, the REDREQ is sent from the 49
Border MSC to the Originating MSC. 50
Note: This step is independent of steps p through w and may occur at any time after 51
step o. 52
53
54
55
56
57
58
59
60

Call Delivery 321-10

 X.S0004-321-E v2.0

1
2
1.8 CD Invocation with Unsolicited Page Response
3
4
This scenario describes procedures to resolve the unsolicited page response problem for MSs in
5
border systems during call delivery.
6
7
8 Originating System Serving System Border System
9
10
11 MSC HLR VLR MSC VLR MSC
12
13
14
15
call origination
16 a
17
LOCREQ [DGTSDIAL]
18 b
19 ROUTREQ [MSID]
c
20
ROUTREQ [MSID]
21 d
22
page request e
23
LRT RRT RRT
24 page response f
25
QUALREQ
26 g
27 QUALREQ
h
28 QRT
qualreq QRT
29 i
30 qualreq
31 j
32 UNSOLRES [TLDN, EXTMSCID(Border)]
k
33
unsolres [MSCID(Originating)] ORT
34 l
35 routreq [TLDN, MSCID]
36 m
37 routreq [TLDN, MSCID]
n
38
locreq [TERMLIST, REDIND]
39 o
40 REGNOT
41
p
42 REGNOT
q
43 REGCANC TLDNAT
44 r
45 REGCANC
s
46
RCT RCT regcanc RNT RNT
47 t
48
regcanc
49 u
50 regnot
v
51
regnot
52 w
53 call setup
54 x
55
56 Figure 7 — CD Invocation with Unsolicited Page Response
57
58 a-d. Same as CD, see Part 321, sec. 1.2, Steps a-d.
59
60

321-11 Call Delivery

X.S0004-321-E v2.0

e. When the serving system receives a ROUTREQ it initiates paging in its serving area. 1
2
f. The Border MSC receives an unsolicited page response. 3
After the Border MSC receives a page response it can assign the MS to a traffic 4
channel. The Border MSC verifies the presence of the MS in its serving area (e.g. via 5
SAT detection, through a traffic channel audit or both). 6

g. Optionally the Border MSC sends a QUALREQ to the VLR indicating Border Access. 7
8
h. If the service profile of the MS is unknown to the VLR, it sends a QUALREQ to the 9
HLR associated with the MS. 10
i. The HLR sends a qualreq to the Border MSC's VLR, including the MS's service 11

profile information. 12
13
j. The VLR sends a qualreq to the Border MSC, including the MS's service profile
14
information. 15
If the MS is authenticable, optionally authenticate it using a control channel or a traffic 16
channel (see Part 310). 17

k. The Border MSC then allocates a routing alias (TLDN) and sends an UNSOLRES to 18
19
one or more neighboring MSC's.
20
When the Serving MSC receives this UNSOLRES, it stops the paging process. 21
l. The Serving MSC then responds with the unsolres sent to the Border MSC. 22
23
m-x. Same as CD, see Part 321, sec. 1.7, Steps m-x.
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Call Delivery 321-12

 X.S0004-321-E v2.0

1
2
1.9 TLDN Call Arrival with Intersystem Paging
3
4
This scenario describes TLDN Call Arrival at the serving system involving intersystem paging
5
from the serving system to border systems.
6
7
8
Originating System Serving System Border System
9
10
11 MSC AC HLR VLR MSC MSC
12
13
14
call origination
a
15
LOCREQ [DGTSDIAL]
16 b
17 ROUTREQ [MSID]
18
c
19
ROUTREQ [MSID]
d
20 LRT RRT RRT routreq [TLDN]
21 e
22 routreq [TLDN]
f
23 TLDNAT
locreq [TERMLIST, REDIND]
24 g
25
call setup
26 h
27
page request i
28
ISPAGE2 [PageIndicator]
29 j
30 ISPRT
page response k
31
32 ispage2[AuthParameters]
l
33
AUTHREQ
34 m
35 AUTHREQ
36
n
37 AUTHREQ
o
38
authreq
ART ART ART ISSWT
39 p
40 authreq
q
41
42
authreq
r
43 ISSETUP [IMSCCID, EncryptionInformation]
44 s
45 ISSRT
alert t
46
issetup
47 u
48 ISART MS answers v
49
50 ISANSWER
w
51
isanswer ISAT
52 x
53 call setup complete
54
y
55
56 Figure 8 — TLDN Call Arrival with Intersystem Paging
57
58
a-d. Same as CD, see Part 321, sec. 1.2, Steps a-d.
59
60

321-13 Call Delivery

X.S0004-321-E v2.0

e-h. Same as CD, see Part 321, sec. 1.2, Steps i-l. 1
2

NOTE: The events described in Steps i-j could happen at any time in relation to the 3

events described in Steps e-h. 4

5
6
i-j. Before initiating local paging, at the time of local page initiation or after first page
7
time-out, the Serving MSC may send an ISPAGE2 to one or more bordering MSCs
8
according to its “topographical map” with a parameter indicating an area where the
9
subscriber's presence was last detected and a parameter indicating whether to page or
10
just listen for an unsolicited page response.
11
The Border MSC that receives the ISPAGE2 may initiate paging (i.e., if directed). 12
k. If a page response is then received at the Border MSC, it assigns the MS to a traffic 13

channel. The Border MSC further confirms the MS's presence (e.g., via SAT detection, 14

through a traffic channel audit or both). 15

16
l. When the Border MSC assigns the MS to a traffic channel, the Border MSC sends an 17
ispage2 to the Serving MSC. If authentication is to be performed, the ispage2 18
contains the appropriate authentication parameters received from the MS. 19

m. If authentication is indicated, the Serving MSC then sends an AUTHREQ to the VLR. 20
21
n. The VLR may send the AUTHREQ to the HLR.
22
o. If received, the HLR forwards the AUTHREQ to the AC. 23

p. The AC sends an authreq to the HLR, including the Voice Privacy Mask 24
25
(VPMASK) and Signaling Message Encryption Key (SMEKEY) associated with this
26
system access.
27
q. The HLR forwards the authreq to the VLR. 28

r. The VLR sends the authreq to the serving MSC. 29

30
s. The serving MSC sends an ISSETUP to the Border MSC to perform call setup
31
actions. The ISSETUP contains the circuit ID of the intersystem trunk facility. The 32
ISSETUP may also contain EncryptionInformation. 33
34
Encryption Information: 35

[CDMAPLCM] CDMAPrivateLongCodeMask. Include if 36

O
available. 37
38
[SMEKEY] SignalingMessageEncryptionKey. Include if O 39
available.
40
[VPMASK] VoicePrivacyMask. Include if available. O 41
42
t. The Border MSC connects the path and alerts the mobile. 43
44
u. The Border MSC then sends an issetup to the Serving MSC. The Serving MSC then
45
connects the backward call path to the inter-MSC trunk.
46
v. The MS answers the alert. 47

w. The Border MSC sends an ISANSWER to the Serving MSC. 48

49
x. The Serving MSC sends an isanswer to the Border MSC. 50
y. The Serving MSC then connects the call path in both directions to the inter-MSC trunk 51
to the Border MSC, completing the call setup process. 52
53
54
55
56
57
58
59
60

Call Delivery 321-14

 X.S0004-321-E v2.0

1
2
1.10 TLDN Call Arrival with No Page Response to Intersystem
3 Paging
4
5 This scenario describes intersystem paging from the serving system to border systems, when a
6 call has arrived at the serving system via a TLDN and the result is no page response from either
7 the serving system or border system.
8
9
10
11 Originating System Serving System Border System
12
13
14
MSC HLR VLR MSC MSC
15
16
call origination
17 a
18 LOCREQ [DGTSDIAL]
b
19
ROUTREQ [MSID]
20 c
21
ROUTREQ [MSID]
22 d
LRT RRT RRT
23 routreq [TLDN]
e
24
routreq [TLDN]
25 f
26
TLDNAT
locreq [TERMLIST, REDIND]
27
g
28
call setup
h
29
30 page request i
31 ISPAGE2 [PageIndicator]
j
32
ISPRT
33 timeout k
34
announcement
35 l
36 call release
m
37
38 n
39
Figure 9 — TLDN Call Arrival with No Page Response to Intersystem Paging
40
41
a-j. Same as CD, see Part 321, sec. 1.9, Steps a-j.
42
43 k. The Serving MSC times out waiting for a page response from both the border system
44 and itself.
45 l. The Serving MSC provides an appropriate announcement to the calling party.
46
47
m. The calling party releases the call.
48
49
50
51
52
53
54
55
56
57
58
59
60

321-15 Call Delivery

X.S0004-321-E v2.0

1.11 TLDN Call Arrival with No Answer After Intersystem 1

2
Paging, Call Release Initiated by Serving MSC 3
4
This scenario describes intersystem paging from the serving system to border systems, when a 5
call has arrived at the Serving MSC via a TLDN and the Serving MSC time-outs waiting for 6

answer notification from the Border MSC. 7

8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Call Delivery 321-16

 X.S0004-321-E v2.0

1
2
3
4
5 Originating System Serving System Border System
6
7
8 MSC AC HLR VLR MSC MSC
9
10
call origination
11 a
12 LOCREQ [DGTSDIAL]
b
13
14 ROUTREQ [MSID]
c
15
ROUTREQ [MSID]
16 d
17 LRT RRT RRT routreq [TLDN]
e
18
routreq [TLDN]
19 f
20
TLDNAT
locreq [TERMLIST, REDIND]
21 g
22 call setup
h
23
24 page request i
25 ISPAGE2 [PageIndicator]
26
j
ISPRT
27 page response k
28
ispage2 [AuthParameters]
29 l
30 AUTHREQ
m
31
32
AUTHREQ
n
33
AUTHREQ
34 o
ART ART ART ISSWT
35 authreq
p
36
authreq
37 q
38 authreq
39 r
40 ISSETUP [IMSCCID, EncryptionInformation]
s
41
ISSRT
42 alert t
43 issetup
44
u
ISART
45
timeout v
46
FACREL
47 w
48 CTT facrel
x
49
50 announcement
y
51
call release
52 z
53
54
Figure 10 — TLDN Call Arrival with No Answer After Paging, Call Release Initiated by Serving
55
MSC
56
57
a-u. Same as CD,see Part 321, sec. 1.9, Steps a-u.
58
59 v. The Serving MSC times out waiting for answer notification from the Border MSC.
60

321-17 Call Delivery

X.S0004-321-E v2.0

w. The Serving MSC sends a FACREL to the Border MSC. 1

2
x. The Border MSC sends a facrel to the Serving MSC. 3
y. The Serving MSC provides an appropriate announcement to the calling party. 4
5
z. The Serving MSC releases the call.
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Call Delivery 321-18

 X.S0004-321-E v2.0

1
2
1.12 TLDN Call Arrival with No Answer After Intersystem
3 Paging, Call Release Initiated by Border MSC
4
5 This scenario describes intersystem paging from the serving system to border systems, when a
6 call has arrived at the Serving MSC via a TLDN and the Border MSC does not receive answer
7 from an alerting MS.
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

321-19 Call Delivery

X.S0004-321-E v2.0

1
2
3
4
Originating System Serving System Border System 5
6
7
MSC AC HLR VLR MSC MSC 8
9

call origination 10
a 11
LOCREQ [DGTSDIAL] 12
b
13
ROUTREQ [MSID] 14
c
15
ROUTREQ [MSID]
d 16
LRT RRT RRT routreq [TLDN] 17
e
18
routreq [TLDN]
f 19

locreq [TERMLIST, REDIND] TLDNA 20

g 21
call setup 22
h
23
page request i 24

ISPAGE2 [PageIndicator] 25
j 26
ISPRT
page response k 27
28
ispage2[AuthParameters]
l 29
AUTHREQ 30
m
31
AUTHREQ 32
n
33
AUTHREQ
o 34
authreq ART ART ART ISSWT
35
p
36
authreq
q 37

authreq 38
r 39
ISSETUP [IMSCCID, EncryptionInformation] 40
s
41
ISSRT alert t 42

issetup 43
u 44
ISART answer timeout v 45
46
FACREL
w 47
facrel
CTT 48
x
49
announcement 50
y
51
call release
z 52
53
54
Figure 11 — TLDN Call Arrival with No Answer After Intersystem Paging, Call Release Initiated
55
by Border MSC
56
57
a-u. Same as CD, see Part 321, sec. 1.9, Steps a-u. 58
v. The Border MSC times out waiting for the MS to answer the alert. 59
60

Call Delivery 321-20

 X.S0004-321-E v2.0

1 w. The Border MSC then sends a FACREL to the Serving MSC, to release the intersystem
2
trunk facility. The Border MSC also releases the traffic channel.
3
4
x. The Serving MSC sends a facrel to the Border MSC.
5 y. The Serving MSC provides an appropriate announcement to the calling party.
6
z. The Serving MSC releases the call.
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

321-21 Call Delivery

X.S0004-321-E v2.0

1.13 CD Invocation with No Answer or No Page Response plus 1

2
Transfer to HLR Inhibited 3
4
This scenario describes CD invocation to an MS when no page response or no answer is 5
received by the Serving MSC after TLDN call arrival. The Originating MSC transfer to the 6

HLR was inhibited, and announcements are based on the Serving MSC provided 7

RedirectionReason. 8
9
10
11

Originating System Serving System 12

13
14
MSC HLR VLR MSC
15
16
17
call origination
a 18
19
LOCREQ [DGTSDIAL, TRANSCAP]
b 20
21
ROUTREQ [MSID, TRANSCAP] 22
c
23
ROUTREQ [MSID, TRANSCAP] 24
d
LRT RRT 25
RRT
routreq [TLDN] 26
e 27

routreq [TLDN] 28
f 29
TLDNAT
30
locreq [TERMLIST, REDIND]
g 31
32
call setup
h 33
34
page or answer 35
timeout i
36
REDREQ [REDREASON, CMDCODE] 37
j
38
RDRT
redreq [ ] 39
k 40
41
call release
l 42
43
announcement
m 44
45
call release
46
n
47
48

Figure 12 — CD Invocation with No Answer or No Page Response plus Transfer to HLR Inhibited 49
50
51
a. A call origination and the dialed MS address digits (i.e., directory number) are received by
52
the Originating MSC.
53
b. The Originating MSC sends a LOCREQ to the HLR associated with the MS; this association 54
is made through the dialed MS address digits (which may not be the MIN), in this case also 55
included is TRANSCAP set to indicate the Originating System is capable of supporting 56

enhanced call redirection (e.g., generating tones and announcements). 57

58
59
60

Call Delivery 321-22

 X.S0004-321-E v2.0

1 c. If the dialed MS address digits are assigned to a legitimate subscriber, the HLR sends a
2
ROUTREQ (including MSID and TRANSCAP) to the VLR where the MS is registered.
3
4
d. The VLR then forwards the ROUTREQ (including MSID and TRANSCAP) to the current
5 Serving MSC.
6 e-h Same as CD, Section 1.2, Steps i-l.
7
i. In this case, the called MS either does not answer the page or does not answer after alerting.
8
9
j. Since the received TRANSCAP has informed the Serving MSC that the Originating MSC
10
is capable of supporting enhanced call redirection. The Serving MSC sends (to the Origi-
11
nating MSC) a REDREQ with REDREASON set to identify the redirection reason and
12
CMDCODE set to deny TRANUMREQ initiation.
13 k. The Originating MSC acting on the received CMDCODE returns a redreq (without
14 attempting a TRANUMREQ toward the HLR).
15 l. The Originating MSC releases the inter-MSC voice path.
16
m. The Originating MSC provides the appropriate tone or announcement (per the received
17
REDREASON) to the calling party.
18
19 n. The Originating MSC releases the call.
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

321-23 Call Delivery

X.S0004-321-E v2.0

1.14 CD Invocation with No Answer or No Page Response plus 1

2
Transfer to HLR Inhibited and Serving MSC Identified 3

Announcements 4
5
6
This scenario describes CD invocation to an MS when no page response or no answer is
7
received by the Serving MSC after TLDN call arrival. The Originating MSC transfer to the
8
HLR was inhibited, and announcements are based on the Serving MSC provided
9
RedirectionReason and AnnouncementList. 10
11
12
13
Originating System Serving System
14
15
MSC HLR VLR MSC 16
17
18
call origination 19
a
20
LOCREQ [DGTSDIAL, TRANSCAP] 21
b
22

ROUTREQ [MSID, TRANSCAP] 23

c 24
25
ROUTREQ [MSID, TRANSCAP]
d 26
LRT RRT RRT 27
routreq [TLDN]
e 28
29
routreq [TLDN]
f 30
TLDNAT 31
locreq [TERMLIST, REDIND] 32
g
33
call setup 34
h
35
36
page or answer
timeout i 37
38
REDREQ [REDREASON, ANNLIST, CMDCODE]
j 39
RDRT 40
redreq [ ]
k 41
42
call release 43
l
44
announcement 45
m
46
call release 47
n 48
49
50
Figure 13 — CD Invocation with No Answer or No Page Response plus Transfer to HLR Inhibited 51
and Serving MSC Identified Announcements 52
53
a-i Same as CD, Section 1.13. 54
j. Since the received TRANSCAP has informed the Serving MSC that the Originating MSC 55
is capable of supporting enhanced call redirection. The Serving MSC sends (to the Origi- 56
nating MSC) a REDREQ with REDREASON set to identify the redirection reason, 57
ANNLIST set to identify the calling party announcement, and CMDCODE set to deny 58
TRANUMREQ initiation. 59
60

Call Delivery 321-24

 X.S0004-321-E v2.0

1 k. The Originating MSC acting on the received CMDCODE returns a redreq (without
2 attempting a TRANUMREQ toward the HLR) and applies the calling party announcement(s)
3 identified by the received ANNLIST.
4
l-n Same as CD, Section 1.13.
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

321-25 Call Delivery

X.S0004-321-E v2.0

1.15 CD Invocation with No Answer or No Page Response plus 1

2
Transfer to HLR Inhibited and Serving MSC Identified 3

Announcements in the Called Party Preferred Language 4

5
6
This scenario describes CD invocation to an MS when no page response or no answer is
7
received by the Serving MSC after TLDN call arrival. The Originating MSC transfer to the
8
HLR was inhibited, and announcements are based on the Serving MSC provided
9
RedirectionReason, AnnouncementList, and called party PreferredLanguage. 10
11
12
13
Originating System Serving System
14
15
MSC HLR VLR MSC 16
17
18
call origination 19
a
20
LOCREQ [DGTSDIAL, TRANSCAP] 21
b
22

ROUTREQ [MSID, TRANSCAP] 23

c 24
25
ROUTREQ [MSID, TRANSCAP]
d 26
LRT RRT RRT 27
routreq [TLDN]
e 28
29
routreq [TLDN]
f 30
TLDNAT 31
locreq [TERMLIST, REDIND] 32
g
33
call setup 34
h
35
36
page or answer
timeout i 37
38
REDREQ [REDREASON, ANNLIST, PLANGIND, CMDCODE]
j 39
RDRT 40
redreq [ ]
k 41
42
call release 43
l
44
announcement 45
m
46
call release 47
n 48
49
50
Figure 14 — CD Invocation with No Answer or No Page Response plus Transfer to HLR Inhibited 51
and Serving MSC Identified Announcements in the Called Party Preferred Language 52
53
a-i Same as CD, Section 1.13. 54
j. Since the received TRANSCAP has informed the Serving MSC that the Originating MSC 55
is capable of supporting enhanced call redirection. The Serving MSC sends (to the Origi- 56
nating MSC) a REDREQ with REDREASON set to identify the redirection reason, 57
ANNLIST set to identify the calling party announcement, PLANGIND set to identify the 58
called party preferred language, and CMDCODE set to deny TRANUMREQ initiation. 59
60

Call Delivery 321-26

 X.S0004-321-E v2.0

1 k. The Originating MSC acting on the received CMDCODE returns a redreq (without
2 attempting a TRANUMREQ toward the HLR) and applies the calling party announcement(s)
3 identified by the received ANNLIST in the called party preferred language identified by the
4 received PLANGIND.
5
l-n Same as CD, Section 1.13.
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

321-27 Call Delivery

X.S0004-321-E v2.0

1.16 CD Invocation with improved Intersystem Paging to an 1

2
Idle MS 3
4
This scenario describes CNIP invocation to a idle, authorized MS that is the forwarded-to party 5
of a call redirection. 6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Call Delivery 321-28

 X.S0004-321-E v2.0

1
2
3
4
Originating System Serving System Border System -1 Border System -2
5
6
7 MSC HLR VLR MSC VLR-1 MSC-1 VLR-2 MSC-2
8
9
call origination
10 a
11 LOCREQ [DGTSDIAL]
12
b
13 ROUTREQ [MSID]
c
14
ROUTREQ [MSID]
15 d
16
page request e
17
18
ISPAGE [PageIndicator, PageResponseTime, PageCount]
f
19
ISPAGE [PageIndicator, PageResponseTime, PageCount]
20 g
21 LRT RRT RRT ISPRT
page timeout h
22
23 page timeout i
24
25
page response j
26 QUALREQ
k
27
QUALREQ
28 l
29 QRT QRT
qualreq
30
m
31
qualreq
n
32
ispage [TLDN, EXTMSCID(BORDER)]]
33 o
34 RELEASE [MIN, IMSI]
p
35
36 release
q
37
routreq [TLDN, MSCID]
38 r
39 routreq [TLDN, MSCID]
s
40
locreq [TERMLIST, REDIND]
41 t
42 REGNOT
43 u
44 REGNOT
v
45
REGCANC TLDNAT
46 w
47
REGCANC
48
x
RCT RCT RNT RNT
49 regcanc
y
50
regcanc
51 z
52 regnot
aa
53
54
regnot
ab
55
call setup
56 ac
57
58
59 Figure 15 — CD Invocation with improved Intersystem Paging to an Idle MS
60

321-29 Call Delivery

X.S0004-321-E v2.0

a-d. Same as CD, see Part 321, sec. 1.2, Steps a-d. 1
2
e-g. Before initiating local paging, at the time of local page initiation or after first page time-
3
out, the Serving MSC may send an ISPAGE to one or more bordering MSCs (e.g., Border
4
Systems-1 and -2) according to its “topographical map” with a parameter indicating an area
5
where the subscriber’s presence was last detected and a parameter indicating whether to
6
page or just listen for an unsolicited page response. This ISPAGE contains the MSCID of
7
the Originating MSC in order that subsequent message exchanges work properly; the
8
PageResponseTime and the PageCount parameters respectively inform the border of the
9
maximum time it has to complete the paging process, and the recommended maximum
10
number of pages that it is expected to do it in.
11
h-i. No page responses are received by any of the Border MSCs during the first page attempt, 12
so the Border MSCs attempt a second page... 13
j. When a page response is received at the Border MSC-1... 14
15
k. Optionally the Border MSC-1 sends a QUALREQ to the VLR indicating Border Access.
16
l. If the service profile of the MS is unknown to the VLR, it sends a QUALREQ to the HLR 17
associated with the MS. 18
m. The HLR sends a qualreq to the Border MSC’s VLR, including the MS’s service profile 19
information. 20

n. The VLR sends a qualreq to the Border MSC, including the MS’s service profile infor- 21

mation. The Border MSC-1 then assigns the MS to a voice/traffic channel and allocates a 22

TLDN. The Border MSC further confirms the MS’s presence (e.g., via SAT detection, 23

through a voice channel audit, or both). 24

25
If the MS is authentication capable, optionally authenticate it using a control channel (see
26
Part 310), or a voice channel (see Part 310).
27
o. When the Border MSC-1 assigns the MS to a voice/traffic channel, the Border MSC-1 sends 28
an ispage containing a TLDN and the MSCID of the Border MSC to the Serving MSC. 29
p. Optionally, the Originating MSC sends a RELEASE to the Border MSC (e.g., MSC-2) that 30
may still be paging the MS, in order to free paging resources identified per the MIN/IMSI. 31
This RELEASE stops ongoing paging and frees related resources. 32

q. The Border MSC-2 responds with a release, in replacement of the ispage. 33

34
r. The Serving MSC returns a routreq to the Serving VLR with the TLDN contained in the
35
ispage and the MSCID of the Border MSC.
36
s. The Serving VLR returns the routreq to the HLR. 37
t. The HLR then sends a locreq to the Originating MSC. The locreq includes routing 38
information in the form of the TerminationList parameter, along with an indication of the 39
reason for extending the incoming call (i.e., for CD) in the DMH_RedirectionIndicator 40
parameter. 41
42
u. After responding to the ISPAGE, the Border MSC sends a REGNOT to the Border VLR.
43
v. The Border VLR sends a REGNOT to the HLR. 44
w. The HLR cancels the registration at the visited serving system by sending a REGCANC to 45
the Serving VLR. 46

x. The Serving VLR sends a REGCANC to the Serving MSC. 47

48
y. The Serving MSC returns a regcanc to the Serving VLR.
49
z. The Serving VLR returns a regcanc to the HLR. 50
aa. The HLR returns a regnot to the Border VLR. 51

ab. The Border VLR returns a regnot to the Border MSC. 52

53
ac. The Originating MSC establishes a voice path to the Border MSC using existing intercon-
54
nection protocols (e.g., SS7) and the routing information specified in the locreq.
55
Note: If the Border MSC must initiate call redirection, the REDREQ is sent from the Border 56
MSC to the Originating MSC. 57
58
59
60

Call Delivery 321-30