1 1 2 3 4 5

X20-20040419-012

TSG-X CSN

6TITLE: 7 8 CFD for No Page Response LMSD (PSTN) 9 10SOURCE: 11

12 13 Marvin Bienn Lee Valerius bienn@nortelnetworks.com valerius@nortelnetworks.com 972-685-0883 972-684-5526 14 15 16ABSTRACT: 17 18This contribution proposes a message flow diagram for LMSD Step-2 CFD invocation 19where the Originating MSCe receives an ISUP call origination message and the MS does 20not responding to a page. 21 22This contribution includes revisions agreed to by TSG-X CSN LMSD Ad-hoc group on 2 23April 2004. 24 25 26 27RECOMMENDATION: 28 29Review, discuss, and adopt the recommendation in Section 3. 30

X20-20040419-012

11. Introduction 2 3This contribution provides a LMSD Step-2 message flow for CFD (Call Forwarding 4Default) invocation due to MS not responding to page. 5 6 7 82. Discussion 9 10This section proposed new text for PN-xxxx. 11 12X.X.X CFD Invocation with No Response to Page (PSTN) 14This scenario describes CFD invocation due to MS not responding to page. The Originating 15MSCe receives an ISUP call origination message. 16 17
13

1
Originating Network

X20-20040419-012
Serving Network

MSCe

HLR

MGW

VLR

MSCe

MGW

BS

SS7: IAM TIA-41: LOCREQ [DGTSDIAL] TIA-41: ROUTREQ [MSID] TIA-41: ROUTREQ [MSID] TIA-41: routreq [TLDN] TIA-41: routreq [TLDN] TIA-41: locreq [TRMLIST, REDIND] H248: ADD [trunk, recvonly]; ADD [RTP, sendrecv] H248: Reply [SDP-O] SIP-T/SIP: INVITE [IAM, SDP-OS] SIP-T/SIP: 180 Ringing [ACM] or 183 Session Progress [ACM] IOS: PAGING REQUEST SS7:ACM H.248: MODIFY [Ringback]; H248: Reply [] SIP-T/SIP: PRACK SIP-T/SIP: 200 OK Page Timeout TLDNAT

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
RDRT

TIA-41: REDREQ[REDREASON] TIA-41: TRANUMREQ[ REDREASON] TTNRT

20 21 22 23 24 25 26 27 28

TIA-41: tranumreq [TRMLIST, REDIND]

TIA-41: redreq SIP-T/SIP: CANCEL (REL) SIP-T/SIP: 487 Request Terminated SIP-T/SIP: 200 OK H248: MODIFY[Ringback] SUBTRACT[RTP] H248: Reply [] SS7: Call Forward Setup or SIP-T/SIP: INVITE(IAM)

1 2 3 4 5 6 2

Figure x: CFD Invocation with No Response to Page (PSTN)

1.

A call origination and the dialed MS address digits (i.e., directory number) are received by the Originating MSCe. 3

1 1 2 3 4 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 2
2.

X20-20040419-012 The Originating MSCe sends a LOCREQ [41-1] to the HLR associated with the MS; this association is made through the dialed MS address digits (which may not be the MIN). 3. If the dialed MS address digits are assigned to a legitimate subscriber, the HLR sends a ROUTREQ [41-1] to the VLR where the MS is registered. 4. The VLR then forwards the ROUTREQ to the current Serving MSCe. In reaction to the ROUTREQ the Serving MSCe consults its internal data structures to determine if the MS is already engaged in a call on this MSCeS. 5. The Serving MSCe allocates a TLDN (Temporary Local Directory Number) and returns this information to the VLR in the routreq [41-1]. The Serving MSCe starts timer TLDNAT. 6. The VLR sends the routreq to the HLR. 7. When the routreq is received by the HLR, it returns a locreq [41-1] to the Originating MSCe. The locreq includes routing information in the form of the TerminationList parameter [41-1], along with an indication of the reason for extending the incoming call (i.e., for CD) in the DMH_RedirectionIndicator parameter [41-1]. The Originating MSCe translates the TLDN to an IP address. 8. The Originating MSCe establishes a context with an Originating MGW. The H.248 message consists of two ADD commands. The first ADD command establishes a termination to the PSTN communication channel (e.g., DS0 on a T1 or E1 line) that corresponds to the incoming IAM (Initial Address Message) with a mode set to recvonly. The termination is set to this mode for fraud prevention. The second ADD command establishes a termination for a bearer channel using RTP. 9. The Originating MGW replies to the H.248 message. The Reply message contains the SDP-O, the local SDP for the Originating MGW. SDP-O contains an IP address, a UDP Port number, and a list of Codecs that the Originating MGW supports for sending and receiving. 10. The Originating MSCe sends an INVITE [RFC3261] message to the Serving MSCe containing the IAM message and SDP-OS. . SDP-OS may be identical to SDP-O (e.g., the Originating MSCe may elect to modify SDPO). The Serving MSCe will use the TLDN to make the association with the MSID received in the ROUTREQ message (Step-4). 11. The Serving MSCe shall send either a 180 Ringing [RFC3261] [RFC3272] message or a 183 Session Progress [RFC3261] message to the Originating MSCe. The message contains an ACM [Q763]. If the Serving MSCe elects to initiate ringback then a 180 Ringing message is sent, otherwise a 183 Session Progress [RFC3261] [RFC3272] message is sent. 12. After receiving an INVITE message (Step-10) the Serving MSCe sends a Paging Request message to the BS to initiate a mobile terminated call setup scenario. 4

1 1 2 3 4 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 2
13.

X20-20040419-012 The Originating MSCe sends an ACM back towards the originating exchange. If the Originating MSCe received a 180 Ringing message (Step 11), the Originating MSCe sends an H.248 message containing a MODIFY command to the Originating MGW. The MODIFY command initiates Ringback for the termination towards the originating exchange. The Originating MGW acknowledges the H.248 message with a Reply message. The Originating MSCe sends a PRACK message to the Serving MSCe. The Serving MSCe sends a 200 OK response to the PRACK message to the Originating MSCe. After receiving an INVITE message (Step-10) the Serving MSCe sends a Paging Request message to the BS to initiate a mobile terminated call setup scenario. When the inter-MSCe call is received at the Serving MSCe, the MS is paged (Step-15). The MS fails to respond to the page before the Page Timeout timer expires. The Serving MSCe sends an REDREQ [41-1] message to the Originating MSCe, indicating that the call is being redirected due to a no page response condition. The Originating MSCe is able to redirect the call; therefore, it sends a TRANUMREQ [41-1] to the HLR requesting the forward-to number appropriate for this condition from the MSs service profile. The HLR sends the tranumreq to the Originating MSCe, including the appropriate forward-to number in the TerminationList parameter, along with an indication of the reason for extending the incoming call (i.e., for CFD) in the DMH_RedirectionIndicator parameter. When the tranumreq is received from the HLR, the Originating MSCe sends a redreq to the Serving MSCe. The Originating MSCe releases the inter-MSCe call. The Originating MSCe sends a CANCEL message to Serving MSCe. In this scenario the CANCEL message contains a REL message. The Serving MSCe sends a 487 Request Terminated message to the Originating MSCe. The Message is a response to the INVITE message (Step-10). The Serving MSCe answers the CANCEL request by sending a 200 OK message to the Originating MSCe. Upon sending the redreq message (see Step-20) to the Serving MSCe, the Originating MSCe sends the Originating MGW an H.248 message. The H.248 message contains a SUBTRACT command to remove the RTP termination from the context and if Ringback was initiated (Step 13) a 5

14.

15.

16. 17. 18.

19.

20.

21.

22.

23. 24.

25.

26. 27.

1 1 2

X20-20040419-012 MODIFY command to remove the Ringback towards the originating exchange

3 28. The Originating MGW replies to the H.248 message with a Reply message. 4 29. The Originating MSCe initiates call forwarding using the specified forward5 to number. Depending upon the forward-to number the Originating MSCe 6 will initiate the forward-to call using either ISUP or SIP-T/SIP signaling. 7 83. Recommendation 9 10Adopted the call flow in Section 2 for inclusion into the LMSD Step-2 baseline. 11 124. References 13 14 15[RFC3261] RFC 3261, "The Session Initiation Protocol". June 2002, IETF, 16 http://www.ietf.org/rfc/rfc3261 17 18[RFC3262] RFC 3262, Reliability of Provisional Responses in the Session Initiation 19 Protocol (SIP). June 2002, IETF, http://www.ietf.org/rfc/rfc3262 20 21[RFC3272] RFC 3272, " Session Initiation Protocol for Telephones (SIP-T): Context 22 and Architectures. September 2002, IETF, 23 http://www.ietf.org/rfc/rfc3272. 24 25[Q763] ITU-T Q.763 Signalling System No. 7 ISDN user part formats and codes. 26 27[41-1] ANSI/TIA/EIA-41-D Cellular Radiotelecommunications Intersystem Operations, 28 December 1997 29 30 31