1 / 25

Signalling Flows for the IP Multimedia Call Control in 3G Wireless Network

This master's project explores the signalling flows involved in IP multimedia call control within a 3G wireless network, focusing on the packet switched core network, evolved core network, and call flow design and implementation. The project demonstrates the end-to-end call setup in an all IP network.

january
Télécharger la présentation

Signalling Flows for the IP Multimedia Call Control in 3G Wireless Network

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Signalling Flows for the IP Multimedia Call Control in 3G Wireless Network Master’s Project By Sanjeev Kayath

  2. Topics • Introduction • Packet Switched Core Network • SIP • Evolved Core Network • Call flow • Design and Implementation • Results

  3. Introduction • 3G Wireless Network: • Core Network Architecture is changing. • Drivers: • Demand for data and multimedia services in mobile environment. • Popularity of IP networks. • Goal: • An all IP core network supporting data and multimedia services in 3G wireless network.

  4. Packet Switched Core Network • GPRS • Introduced Packet Switching Network entities: • Serving GPRS support node (SGSN) • Gateway GPRS support node (GGSN) • Mobile Station needs to perform • Attach and Detach procedure • Context Activation procedure

  5. Packet Switched Core Network A simple block diagram of a packet switched network. (Solid lines: Data transfer and Signaling interface. Dotted lines: Signaling Interface)

  6. Session Initiation Protocol (SIP) • Signalling Protocol to handle the multimedia call control. • An application layer protocol to create and terminate multimedia sessions. • Supports • User Location • User Capability • User Availability • Messages: INVITE, ACK, BYE, REGISTER.

  7. Evolved Core Network • Include architectural entities that support the signalling messages to set up multimedia calls: • Call State Control Function (CSCF) • User communicates with CSCF at application layer, using SIP messages. • CSCF is equivalent to a SIP server. • Signalling path is different from media flow path.

  8. Evolved Core Network A simple block diagram of a evolved packet switched network. (Solid lines: Data transfer and Signaling interface. Dotted lines: Signaling Interface)

  9. Call Flow • Entities in Signalling Path • User ( User Agent Client, User Agent Server) • Network • Serving CSCF • Acts as a registrar. • Routes incoming and outgoing requests. • Proxy CSCF • Immediate contact point of mobile station. • HSS • Location Database.

  10. Complete Signalling Path Mobile Station Mobile Station Serving CSCF Serving CSCF Base Station Base Station Proxy CSCF Radio Network Controller Radio Network Controller Proxy CSCF GPRS Service Node GPRS Service Node

  11. SIP Signalling Path Mobile Station Mobile Station Serving CSCF Serving CSCF Proxy CSCF Proxy CSCF • Entities actually involved in session set up/termination. • Message exchange at the application layer, intermediate entities are not aware of these messages.

  12. Design & Implementation • Project simulates all the entities in the SIP signalling path and shows the end-to-end call set up. • User and network entities interact at the application layer: • Use socket services • UDP transport protocol

  13. Design & Implementation • Platform: UNIX, Language: C++ • Object Oriented Methodology: • All the entities are objects. • Main Objects: • User • ProxyCSCF • ServingCSCF • HSS

  14. Design & Implementation • User • Two Process: • User Agent Client • Handles User Interface and initiates a call. • User Agent Server • Listens for incoming calls. • Synchronization: • Semaphore Locking.

  15. Design & Implementation • Network (Proxy and Serving CSCF) • Concurrent Server • Fork a process to service incoming request. • Main process loops infinitely to listen to incoming request. • Synchronized access to database, HSS. • Semaphore locking.

  16. Simulation Example • Two Network Domains • ernie.ece.uic.edu • bert.ece.uic.edu • Mobile Users • User1@ernie.ece.uic.edu • User2@bert.ece.uic.edu • Definitions • Call Origination (Initiating user to ServingCSCF) • Call Termination (ServingCSCF to destination user)

  17. Example Scenarios • Scenario 1: • User1@ernie: • Current Location: ernie, HOME • User2@bert: • Current Location: ernie, ROAMING • Scenario 2: • User1@ernie: • Current Location: bert, ROAMING • User2@bert: • Current Location: ernie, ROAMING

  18. Scenario 1: Registration User1@ernie ServingCSCF ServingCSCF Proxy CSCF HSS HSS User2@bert Bert Ernie

  19. Scenario 1: Registration User1@ernie ServingCSCF ServingCSCF Proxy CSCF HSS HSS User2@bert Bert Ernie

  20. User1@ernie calls User2@bert User1@ernie ServingCSCF ServingCSCF Proxy CSCF HSS HSS User2@bert Bert Ernie

  21. Simulation Example • Features implemented • If User2@bert not registered, error returned. • If User2@bert busy, Destination busy returned. • On receiving call, User2@bert may accept the call or reject the call. • User1@ernie can hang up to terminate the session.

  22. Proposed Change in the Signalling Path • For Session Initiation, the signalling path may not include the ServingCSCF of the origination part. • User profile can be downloaded to ProxyCSCF at the time of registration. • ProxyCSCF performs the service control functionality instead of the ServingCSCF.

  23. User1@ernie calls User2@bert User1@ernie ServingCSCF ServingCSCF Proxy CSCF HSS HSS User2@bert Bert Ernie

  24. Results • Proposed change results in decrease in Call Setup Delay. • Caveat: Different Network Operators may not delegate service control to ProxyCSCF. • Simulation demonstrates the signalling path for end-to-end call set up in “All IP” network.

  25. Thank You !!

More Related