1 2 3 1 2 3 4 5 6TITLE: 7 8Mobile-to-Mobile TrFO Call Flow 9 10SOURCE:

X20-20031208-xxx

11
12

Marvin Bienn Lee Valerius Mini Vasudevan Sanket Nesargi

bienn@nortelnetworks.co m valerius@nortelnetworks. com minivas@nortelnetworks. com sanket@nortelnetworks.c om

972-685-0883 972-684-5526 972-685-0799 972-685-0753

13 14 15ABSTRACT: 16 17This contribution proposes a end-to-end TrFO call flow for a Mobile-to-Mobile scenario. 18 19RECOMMENDATION: 20 21Discuss, Review and Adopt the concepts given in the TrFO call flow.

6Nortel Networks grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other 7copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; 8to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it 9may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to 10reproduce in whole or in part such contribution or the resulting Organizational Partner's standards publication. Nortel 11Networks is also willing to grant licenses under such contributor copyrights to third parties on reasonable, non12discriminatory terms and conditions for purpose of practicing an Organizational Partners standard which incorporates 13this contribution. 14 15This document has been prepared by Nortel Networks to assist the development of specifications by 3GPP2. It is 16proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on Nortel Networks. 17Nortel Networks specifically reserves the right to amend or modify the material contained herein and to any intellectual 18property of Nortel Networks other than provided in the copyright statement above.

4 5

1 X20-20031208-xxx 2 3 11 Introduction 2 3This contribution proposes a Mobile-to-Mobile TrFO call flow. 4 5The following TrFO assumptions are made: 6 7 1) The O-MS codec cannot be modified after Assignment Complete (see Steps 7 8 and 25). 9 2) Ringback can optionally occur in the originating network. 10 3) Ringback can optionally occur in the terminating network. 11 4) All SIP Provisional Responses (i.e., all 1xx messages except 100) are sent 12 reliably using PRACK mechanism as defined in [RFC3262]. 13 5) All O-MGW and T-MGW shall support G.711 transcoder. 14 6) If transcoders are a BS (e.g. O-BS or T-BS) then G.711 shall be supported. 15 7) Due to Legacy constraints, no new messages are allowed between the MS 16 and BS. 17 8) Due to Legacy constraints, no messages between the MS and BS can be 18 modified (e.g., addition of new parameters). 19 9) Routing aspects between the O-MSCe and the T-MSCe are presently not 20 discussed. 21 10) ANSI-41 signaling is not addressed. 22 11) The termination network determines if and when Ringback to the O-MS 23 occurs. 24 25 262. MS-to-MS Call Flow

27 28The MS-to-MS call flow is shown in Figure 1. The Call flow steps are described after the 29Figure 1. 30

-2-

1
2 3
O-MS O-BS OMSCe OMGW TMGW TMSCe

X20-20031208-xxx

T-BS

T-MS

2. CM Service Request (O-MS Codec List, O-BS Codec List, Connection info) 3. H.248 ADD (Connection Info) H.248 ADD Reply (Connection Info) 4. Assignment Request (Desired codec, Connection info) 5. SIP -T INVITE (Desired codec, other codecs, Connection info,IAM) 6. Service Negotiation 7. Assignment Complete (Desired Codec)

1. Origination (O-MS Codec List,)

8. RINGING (SIP-T 180) or SESSION PROGRESS (SIP-T 183) (ACM) 9. RINGING Conf (PRACK) 10. RINGING Conf ACK (200 OK PRACK)

12. Ringback (Origination Side)

11. H.248 MODIFY H.248 MODIFY Reply 13.Page Request (Desired Codec)

14. Page Request (Desired Codec) 15. Page Response (T-MS Codec)

16. Page Response (T-MS Codec, T-BS Codec List, Connection info) 17. H.248 ADD (Connection info) H.248 ADD Reply (Connection Info)

18. Offer response (SIP 183) (Chosen Codec, Connection info) 19. Response Conf (PRACK) 20. H.248 MODIFY H.248 MODIFY Reply 21. Bearer Update (Updated Codec) 22. Bearer Update Ack 23. Ringback (Termination side)

24. Response Conf ACK (200 OK PRACK) 25. Assignment Request (Desired Codec, Connection info) 26. Service Negotiation 27. Assignment Complete (Desired Codec) 28.Service Connect 29. IOS: Connect 30. SIP-T 200 OK (INVITE) (ANM) 31. SIP ACK (INVITE) 32. H.248 MODIFY H.248 MODIFY Reply 33. CONNECT

1
2

Figure 1: Call Flow for MS-to-MS Scenario

3 41. The originating MS initiates a call with an Origination message. The codecs supported 5 by the MS are listed in the Origination Message (e.g., O-MS Codec List). 6 72. The O-BS sends a CM Service Request message to the O-MSCe. The message contains: 8 9 A) Codecs supported by the O-MS. This list is obtained from step 1. The O-BS can 10 remove any codec from the O-MS code list (e.g., for voice quality reasons). 4 -3-

1
2 3

X20-20031208-xxx

1 2 B) Transcoders supported by the O-BS. This list is referenced as the O-BS codec 3 list. If the O-BS does not support transcoding then the list will be empty. 4 5 Note If a transcoder is placed in the O-BS codec list it implies that for all 6 O-MS codecs listed in (A) the O-BS has the capability and resources 7 to transcode to the codec. 8 9 C) The O-BS connection information. 10 113. The O-MSCe reserves resources on the O-MGW by sending H.248 ADD command. This 12command: 13 A) Contains the O-BS connection info (see step 2) 14 B) Requests setting up two ephemeral terminations 15 C) Specifies the codec type that will be used between the RAN and the O-MGW (e.g., O16 MGW termination towards O-BS). 17 18 The H.248 ADD Reply contains connection information be send the O-BS and the T-MGW. 19 This connection information will allow the O-BS and T-MGW to set-up connections with the 20 O-MGW. 21 224. The O-MSCe sends an Assignment Request containing: 23 A) The Desired codec chosen by the O-MSCe. How the O-MSCe chooses the Desired 24 codec is outside the scope of standardization. 25 B) The O-MGW connection info (see step 3). 26 27 Note 1) In an effort to get a TrFO connection the O-MSCe should attempt to select a codec 28 from the O-MS Codec list (see step 2) as the Desired codec. 29 2) The O-BS and the O-MS shall not change the Desired codec value 30 315. Any time after the H248 Add Reply has been received the O-MSCe sends a SIP-T INVITE 32[RFC3261] [RFC3272] message. The SIP-T INVITE contains: 33 34 A) An ordered list of codecs. The first codec in the list is the Desired codec selected by 35 the O-MSCe (see Step 4). The remainder of the list is chosen by the O-MSCe. How 36 the O-MSCe determines the remainder of the list is outside the scope of 37 standardization. 38 39 Note 1) each codec in the list will have an identifier associated with it. This 40 identifier will associate the codec with the O-MS, O-BS, or O-MGW. This 41 identifier may be used by the T-MSCe during the call set-up process. 42 2) The codec list shall contain G.711. Based on assumption that the O43 MGW and the T-MGW support G.711 transcoding. 44 45 B) O-MGW connection info (e.g., for O-MGW termination towards T-MGW), 46

-4-

1
2 3

X20-20031208-xxx

1 C) An IAM SS7 [Q763] message. 2 36. After receiving the Assignment Request (step 4) the O-BS notifies the O-MS of the chosen 4vocoder as a part of the service negotiation procedure. The O-MS is brought onto a traffic channel. 5 67. The O-BS sends an Assignment Complete message containing the vocoder the O-MS is using. 7 8 Note 1) The O-MS vocoder shall be the same as that in Step 4. 9 2) After the Assignment Complete message the O-MS vocoder cannot be changed until 10 after Call Connect, see Step 35. 11 3) The connection between the O-BS and the O-MGW is established. 12 138. Any time after the SIP-T INVITE has been received (see Step 5) and anytime before Step 1416, the T-MSCe shall send either a RINGING (SIP-T 180) [RFC3261] [RFC 3272] or a SESSION 15PROGESS (SIP-T 183) [RFC3261] [RFC 3272] message to the O-MSCe. The message contains an 16ACM SS7 [Q763] message. 17 18 Note 1) Sending the RINGING (SIP-T 180) informs the O-MSCe that Ringback from the 19 Origination network shall occur. The message also contains an ACM message 20 [Q763]. 21 2) If the T-MSCe does not want to invoke Ringback from the Originating network then 22 a SIP-T 183 message is sent. The message also contains an ACM message [Q763]. 23 249. The O-MSCe acknowledges either the RINGING (SIP-T 180) or the SESSION PROGRESS 25(SIP-T 183) message by sending a PRACK [RFC3262]. 26 2710. The T-MSCe sends a response to the PRACK message (i.e., 200 OK, the request was 28successful). 29 3011. Upon receiving a RINGING (SIP-T 180) message, the O-MSCe shall modify the O-MGW to 31provide ringback to the O-MS. 32 3312. If Step 11 is performed, the O-MGW sends a Ringback signal to the O-MS. 34 3513. Anytime after receiving the SIP INVITE message (see Step 5), the T-MSCe sends a Page 36Request to the T-BS. The Page Request contains the Desired codec for the T-MS. 37 38 Note 1) the T-MSCe determines the Desired codec 39 2) In and effort to get a TrFO connection, the T-MSCe should attempt to select the first 40 codec in the O-MS Codec list (see Step 5) as the desired codec. 41 4214. The T-BS sends a Page Request to the T-MS containing the Desired Codec. 43 4415. The Page Response from the T-MS contains the codec that was selected by the T-MS. 45 4616. The T-BS sends a Page Response to the T-MSCe. The Page Response message contains:

-5-

1
2 3

X20-20031208-xxx

1 2 A) The T-MS Codec (supplied by Step 11) 3 B) The T-BS Codec List (list of available transcoding available by T-BS. Note 4 that if T-BS has no transcoding capability, this list is empty). 5 C) The T-BS connection information. 6 717. After receiving the Page Response (see Step 16) the T-MSCe chooses a T-MGW to service the 8SIP INVITE Request (see Step 5). The MSCe sends the select T-MGW a H.248 message: 9 10 A) The message contains the T-BS connection info (see Step 14). 11 B) The message path is set-up for bi-directional operation 12 C) Ringback may be started towards the O-MGW. 13 14 The T-MGW sends a H.248 ADD Reply containing the T-MGW connection info (e.g., 15 termination point towards T-BS and termination point towards O-MGW). 16 1718. The T-MSCe sends an Offer Response (SIP 183) [RFC3261] message to the O-MSCe. The 18message contains: 19 20 1) The chosen codec. 21 22 Note - Due to the assumption that G711 will be in the list of codecs (see Step 5) 23 there will always be at least one codec that was in the list of codecs sent in Step 24 5. 25 26 2) T-MGW Connection info. 27 2819. The O-MSCe acknowledges the Offer Response (SIP 183) message by sending a PRACK 29message [RFC3262]. 30 3120. The O-MSCe updates the O-MGW terminations using a H.248 MODIFY. 32 33 A) The O-MGW termination towards the T-MGW is supplied with the T-MGW 34 connection info (see Step 18). 35 B) If O-MGW is generating Ringback (Sgenerated by O-MGW is terminated. 36 C) The O-MGW is set-up for bi-directional operation. 37 38 The O-MGW sends a H.248 MODIFY Reply to the MSCe. 39 4021. The O-MSCe sends a new IOS message (referenced as Bearer Update) if transcoding resources 41at the O-BS are required. 42 4322. The O-BS acknowledges the Bearer Update message. 44 4523. If the T-MGW was set-up to provide Ringback, the T-MGW Ringback is sent through the O46MGW to the O-MS.

-6-

1
2 3

X20-20031208-xxx

1 224. After receiving a Response Conf (PRACK) message, the T-MSCe sends a response (e.g., 200 3OK). 4 525. Anytime after Step 16, the T-MSCe sends an Assignment Request to the T-BS. The 6Assignment Request message contains: 7 8 A) The Desired codec 9 B) The T-MGW connection info. 10 11 Note The T-BS and the T-MS shall not change the Desired codec. 12 1326. The T-BS performs service negotiation with the T-MS. The T-MS is brought onto a traffic 14channel. 15 1627. The T-BS sends an Assignment Complete message to the T-MSCe. The message contains the 17T-MS codec. 18 19 Note The T-MS codec of the T-MS will be the same as the Desired codec given in step 25. 2028. When the call is answered by the T-MS, a Service Connect message is sent to the T-BS. 21 2229. The T-BS sends an IOS Connect message to the T-MSCe. The message indicates that the call 23has been answered. 24 2530. After receiving the IOS Connect message (Step 29), the T-MSCe shall send a SIP-T 200 OK 26[RFC3261] [RFC3272] message to the O-MSCe in response to the SIP-T INVITE (Step 5). The 27message contains an ANM SS7 [Q763] message. The message indicates that the terminating side is 28ready for the bearer to be established. 2931. In response to the SIP 200 OK message (Step 30), the O-MGW sends a SIP ACK message to 30the T-MSCe. 31 3232. The T-MSCe sends a H.248 MODIFY to the T-MGW. The message terminates Ringback (if 33applied). 34 35 The T-MGW sends a H.248 MODIFY reply to the T-MSCe. 36 3733. Talking starts. The end-to-end bearer is established between the O-MS and T-MS and the call38setup phase is complete. 39 403. References RFC 3261, "The Session Initiation Protocol". June 2002, IETF, http://www.ietf.org/rfc/rfc3261

41 42[RFC3261] 43 44

-7-

1
2 3

X20-20031208-xxx

1[RFC3262] RFC 3262, " Reliability of Provisional Responses in the Session Initiation 2 Protocol (SIP). June 2002, IETF, http://www.ietf.org/rfc/rfc3262 3 4[RFC3272] RFC 3272, " Session Initiation Protocol for Telephones (SIP-T):Context 5 and Architectures. September 2002, IETF, http://www.ietf.org/rfc/rfc3272. 6 7[Q763] ITU-T Q.763 Signalling System No. 7 ISDN user part formats and codes.

-8-