1. Call flows for resource allocations of Mmed calls Ericsson September 6, 2000 Vancouver

2. Call from PSTN to Mmed user in Home Network User BRANAGC-BWMSCMMGCFMGW IAM SIP INVITE 100 Resource reservation QoS Request QoS decision Resource request Resource result 100 180 200 180 ACM 200 Ack ANM One way voice/Ringing tone Both way RTPBoth way voice Resource reservation result

3. User ARANAGC-BWMSCMMGCFMGW SIP INVITE Resource reservation QoS Request QoS decision Resource request Resource result 100 183 200 Ack One way voiceBoth way RTP Both way voice Resource reservation result Call from Mmed user to PSTN 183 100 IAM ACM ANM Both way RTP

4. Call from Mmed user to Mmed user served by the same RAN User ARANAGC-BWMSCM SIP INVITE Resource reservation QoS Request QoS decision Resource request Resource result 200 Ack Both way RTP Resource reservation result 100 User B QoS Request QoS decision Resource request Resource result Ack Resource reservation Resource reservation result 183 200

5. Call from PSTN to Mmed user roaming in a visited network User BRANAGC-BWMSCMMGCFMGW IAM SIP INVITE 100 Resource reservation QoS Request QoS decision Resource request Resource result 100 180 200 180 ACM 200 Ack ANM One way voice/Ringing tone Both way RTPBoth way voice Resource reservation result homevisited

6. Conclusion The above examples show a model whereby resources could be requested by the MS instead of MGCF or SCM requesting the resources on the user’s behalf. This is a model allowing more intelligence to be pushed to the end-terminals. The call flows focus on the call control and resource requests procedure. Authorization of resources is not shown in order to not crowd the call flows.