3GPP2 A20-20031013-xxx-Ericsson-TrFO_callflows.

doc

TSG-A
TITLE: Call Flows for Mobile Originated and Mobile Terminated Calls SOURCE: Ericsson Inc Erik Colban 6455 Lusk Blvd San Diego, CA 92121 Erik.Colban@ericsson.con ABSTRACT: This contribution presents mobile originated and mobile terminated call flows associated with support of A1p/A2p RECOMMENDATION: Review and discuss the call flows. INTRODUCTION The contribution proposes Mobile Originated and Mobile Terminated call setup flows using A1p signaling messages. The call flow shows interaction between the MS/RAN/MSCe/MGW. Signaling between the MSCe/MGW is shown as high-level H.248 messaging. For simplicity signaling between the MSCe and CN network entities Ericsson Inc Vibhor Julka 6455 Lusk Blvd San Diego, CA 92121 Vibhor.Julka@ericsson.com

1 2 3 4 5 6

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

1 2 3 4 5 6 7 8 9 10 11 12 13 14

(target MSCe, PSTN etc) is omitted. Specification of this signaling as well as details on the MSCe to MGW signaling is outside the scope of TGS-A. The call flows are applicable to architectures where the transcoders are located either in the RAN or MGW. Additionally, the call flows are applicable to RTO and TrFO scenarios. Also included are some A1p message formats showing the key information elements included in the messages.

1 2 3 4

1. Mobile Originated Call Setup

This section describes a mobile originated call setup.

MS BS MSCe MGW

1 2

Origination [Service Option = EVRC; Alternate SO 13K] BS Ack Order A1p::CM Service Request [Service Option List {EVRC, 13K} ; Bearer Format Capabilities {A2p, other, G711 (opt)} ; RAN Bearer addr/port (opt) ] 3 Traffic Channel Establishment A1p::Assignment Request [Service Option; Bearer Format (optional) ; MGW Bearer addr/port (opt) ] 6 7 Service Option Negotiation A1p::Assignment Complete [Service Option ; Bearer Format ; RAN Bearer addr/port ]

5 H.248 ADD Request/ Reply messages

8 MSCe - CN signaling CN

H.248 ADD Modify/ Reply messages

A1p:: Bearer Request [ MGW Bearer addr/port; bearer format ]

11

10

12

A1p::Bearer Response

Voice Frames
5 6 7

13

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

1) The originating MS (MS-O) sends an origination message to the BS. This message includes the preferred SO along with a list of alternate SO supported by the MS. In this scenario the MS includes the preferred option EVRC and alternative option 13K. 2) The BS sends a BS Ack Order to the MS. 3) The source BS sends an A1p CM ServiceRequest message to the MSCe. The message includes the list of service options received from the MS, the BS Bearer Format Capabilities and optionally the IP address/UDP port to be used for bearer transport. 4) The BS and MS perform radio resource allocation and traffic channel setup. 5) The MSCe request context/resources from the selected MGW and sends an H.248 ADD Request message. This message includes BS addr/port information if received from the BS. The MGW responds with an H.248 ADD Reply message with the MGW IP address assigned for the requested termination. Note that the MSCe can delay this step till after the Assignment Complete is received. 6) The MSCe sends an A1p Assignment Request message to the BS. This message includes the SO that the BS should attempt to negotiate to with the MS, and if available, the MGW addr/port and Bearer format to be used. 7) The BS and MS do service option negotiation using service option proposed by the MSCe 8) The BS returns sends an A1p Assignment Complete message to the MSCe. This message includes the service option negotiated to and the BS bearer addr/port to be used. 9) After the MSCe has secured MGW resources it proceeds with additional Core network signaling based on digit analysis etc. Specification of this procedure is outside the scope of the IOS. 10) If and as needed the MSC can modify/update the resource allocation ad the MGW by sending a H.248 ADD Modify message. The MGW responds with a H.248 ADD Reply message and may include a new MGW addr/port and bearer format. 11) The MSCe sends an A1p Bearer Request Message to inform the BS of any modifcation to the MGW. 12) The BS responds with a A1p Bearer Request Message to the MSCe to acknowledge this change. 13) At this stage a bearer path is established from MS to the MGW and traffic frames can be exchanged.

1 2 3 4 5

2. Mobile Terminated Call Setup

This section describes a mobile terminated call setup.

MS

BS

MSCe 1 A1p::Paging Request [ Service Option EVRC]

MGW

MSCe - CN signaling

CN

GPM [ Service Option] 3 Page Response [Service Option = EVRC; Alternate SO 13K] BS Ack Order A1p::Paging Response [Service Option List {EVRC, 13K} ; Bearer Format Capabilities {A2p, other, G711 (opt)} ; RAN Bearer addr/port (opt) ] 6 Traffic Channel Establishment A1p::Assignment Request [Service Option; Bearer Format (optional) ; MGW Bearer addr/port (opt) ] 9
10

4 5

8 H.248 ADD Request/ Reply messages

Service Option Negotiation

A1p::Assignment Complete [Service Option ; Bearer Format ; RAN Bearer addr/port ]

12

11

MSCe - CN signaling

CN

H.248 ADD Modify/ Reply messages

A1p:: Bearer Request [ MGW Bearer addr/port ]

14

13

15

A1p::Bearer Response

Alert With Info

16

MS Ack Order
17

Connect Order
18

BS Ack Order

20

19

A1p::Connect
20

MSCe - CN signaling

CN

22

Voice Frames

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 44 45

1) The MSCe based on signaling with the CN determines that an incoming call terminated to a mobile with its domain. 2) The MSCe sends an A1p Paging Request message and includes the (preferred) service option to be paged with. In this call flow the Page Request message contains an EVRC service option. 3) The BS sends a GPM to the MS. 4) The BS responds with a Page Response message. This message included the preferred SO along with a list of alternate service options. In this scenario the MS includes the preferred service option EVRC and alternative option 13K 5) The BS sends a BS Ack Order to the MS. 6) The source BS sends an A1p Paging Response message to the MSCe. The message includes the list of service options received from the MS, the BS Bearer Format Capabilities and optionally the IP address/UDP port to be used for bearer transport. 7) The BS and MS perform radio resource allocation and traffic channel setup. 8) The MSCe request context/resources from the selected MGW and sends an H.248 ADD Request message. This message includes BS addr/port information if received from the BS. The MGW responds with an H.248 ADD Reply message with the MGW IP address assigned for the requested termination. Note that the MSCe can delay this step till after the Assignment Complete is received. 9) The MSCe sends an A1p Assignment Request message to the BS. This message includes the SO that the BS should attempt to negotiate to with the MS, and if available, the MGW addr/port and Bearer format to be used. 10) The BS and MS do service option negotiation using service option proposed by the MSCe 11) The BS returns sends an A1p Assignment Complete message to the MSCe. This message includes the service option negotiated to and the BS bearer addr/port to be used. 12) After the MSCe has secured MGW resources it proceeds with additional Core network signaling in response to the mobile termination requested in step 1. Specification of this procedure is outside the scope of the IOS. 13) If and as needed the MSC can modify/update the resource allocation ad the MGW by sending a H.248 ADD Modify message. The MGW responds with a H.248 ADD Reply message and may include a new MGW addr/port and bearer format. 14) The MSCe sends an A1p Bearer Request Message to inform the BS of any modifcation to the MGW. 15) The BS responds with a A1p Bearer Request Message to the MSCe to acknowledge this change. 16) The BS sends the Alert with Information Message to the MS to cause ringing at the MS. 17) The MS acknowledges the reception of the Alert with Information Message by transmitting the MS Acknowledgement Order. 18) When the call is answered at the MS, a Connect Order, with acknowledgement required, is transmitted to the BS.

1 2 3 4 5 6 7 8

19) The BS sends a A1p Connect message to the MSCe to indicate that the call has been answered. 20) The MSCe performs signaling to instruct the CN to stop ringtone to the calling party and connect the voice path. 21) At this stage a bearer path is established from MS to the MGW and traffic frames can be exchanged.

1 2

3. A1p Messages

3 4

A1p CM Service Request This message is sent from the BS to the MSCe to request a mobile originated call service. Information Element .. Service Option List BS Bearer Capabilities BS Transport Address Section Reference . xxx xxx xxx Element Direction BS -> MSCe BS -> MSCe BS -> MSCe BS -> MSCe O O O O
a b c

Type C R R C

5 6 7 8 9 10 11 12 13 14 15

a. b. c.

This IE contains the requested service option along with Alternate service options supported received from the MS. This IE contains a list of the bearer capabilities supported at the BS. This list includes e.g. support for G711, A2p formats. Included if the BS can allocate resources necessary for processing the call. This IE contains the IPv4 or IP v6 address along with the UDP port to be used at the BS for bearer transport (This is similar to the BS selecting a preferred CIC in the CM Service Request message)

16 17 18 19

A1p Assignment Request This message is sent from the MSCe to the BS to request that the BS assign radio resources, the attributes of which are defined within the message. The message may include the MGW bearer transport information if needed for the call. Information Element .. Service Option MGW Bearer Capabilities MGW Transport Address Section Reference . xxx xxx xxx Element Direction MSCe -> BS MSCe -> BS MSCe -> BS MSCe -> BS O O O O
a b c

Type C R O O

20 21 22 23 24 25 26 27

a. b. c.

This IE contains the service option that the BS should attempt to negotiate the MS to. If included, this indicates the bear capability to be used for the call. If included, this indicated the IPv4 or IP v6 address along with the UDP port to be used for the bearer transport to the MGW.

1 2 3 4

A1p Assignment Complete This message is sent from the BS to the MSCe to indicate that the requested assignment has been complete. This message includes the bear format and address to be used by the BS for the call. Information Element .. Service Option BS Bearer Capabilities BS Transport Address Section Reference . xxx xxx xxx Element Direction BS -> MSCe BS -> MSCe BS -> MSCe BS -> MSCe O O O O
a b c

Type C R R R

5 6 7 8 9 10

a. b. c.

This IE contains the negotiated service option between the MS and the BS. This IE contains the bear format to be associated with the call. The IE contains the IPv4 or IP v6 address along with the UDP port to be used at the BS for bearer transport.

11 12

A1p Paging Response This message is sent from the BS to the MSCe in response to a GPM Information Element .. Service Option List BS Bearer Capabilities BS Transport Address Section Reference . xxx xxx xxx Element Direction BS -> MSCe BS -> MSCe BS -> MSCe BS -> MSCe O O O O
a b c

Type C R R C

13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

a. b. c.

This IE contains the requested service option along with Alternate service options supported received from the MS. This IE contains a list of the bearer capabilities supported at the BS. This list includes e.g. support for G711, A2p formats. Included if the BS can allocate resources necessary for processing the call. This IE contains the IPv4 or IP v6 address along with the UDP port to be used at the BS for bearer transport ( This is similar to the BS selecting a preferred CIC in the Paging Response message)

2 3 4

A1p Connect This message is sent from the BS to the MSCe to indicate that the call has been accepted by the called user. Information Element .. Section Reference . Element Direction BS -> MSCe O Type C

5 6

7 8 9 10

A1p Bearer Request This message is sent from the MSCe to the BS to request a change in the either the bearer format or bearer transport address associated with the call.

Information Element .. BS Bearer Capabilities BS Transport Address

11 12 13 14 15

Section Reference . xxx xxx

Element Direction BS -> MSCe BS -> MSCe BS -> MSCe O O O

a b

Type C O O

a. b.

If included, this indicates the bear capability to be used for the call. If included, this indicated the IPv4 or IP v6 address along with the UDP port to be used for the bearer transport to the MGW.

16 17 18 19

A1p Bearer Response This message is sent from the BS to the MSE to indicate that the requested assignment has been complete

Information Element .. BS Bearer Capabilities BS Transport Address

20 21 22 23 24

Section Reference . xxx xxx

Element Direction BS -> MSCe BS -> MSCe BS -> MSCe O O O

a b

Type C O O

a. b.

This IE contains the bear format to be associated with the call. The IE contains the IPv4 or IP v6 address along with the UDP port to be used at the BS for bearer transport.

10