Signalling Flows for the IP Multimedia Call Control

  • Slides: 25
Download presentation
Signalling Flows for the IP Multimedia Call Control in 3 G Wireless Network Master’s

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

Topics • • Introduction Packet Switched Core Network SIP Evolved Core Network Call flow

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

Introduction • 3 G Wireless Network: – Core Network Architecture is changing. • Drivers:

Introduction • 3 G 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 3 G wireless network.

Packet Switched Core Network • GPRS – Introduced Packet Switching Network entities: • Serving

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

Packet Switched Core Network A simple block diagram of a packet switched network. (Solid

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

Session Initiation Protocol (SIP) • Signalling Protocol to handle the multimedia call control. •

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.

Evolved Core Network • Include architectural entities that support the signalling messages to set

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.

Evolved Core Network A simple block diagram of a evolved packet switched network. (Solid

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

Call Flow • Entities in Signalling Path – User ( User Agent Client, User

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.

Complete Signalling Path Mobile Station Serving CSCF Base Station Radio Network Controller GPRS Service

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

SIP Signalling Path Mobile Station Serving CSCF Proxy CSCF • Entities actually involved in

SIP Signalling Path Mobile Station Serving 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.

Design & Implementation • Project simulates all the entities in the SIP signalling path

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

Design & Implementation • Platform: UNIX, Language: C++ • Object Oriented Methodology: – All

Design & Implementation • Platform: UNIX, Language: C++ • Object Oriented Methodology: – All the entities are objects. • Main Objects: – User – Proxy. CSCF – Serving. CSCF – HSS

Design & Implementation • User – Two Process: • User Agent Client – Handles

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.

Design & Implementation • Network (Proxy and Serving CSCF) – Concurrent Server • Fork

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.

Simulation Example • Two Network Domains – ernie. ece. uic. edu – bert. ece.

Simulation Example • Two Network Domains – ernie. ece. uic. edu – bert. ece. uic. edu • Mobile Users – User 1@ernie. ece. uic. edu – User 2@bert. ece. uic. edu • Definitions – Call Origination (Initiating user to Serving. CSCF) – Call Termination (Serving. CSCF to destination user)

Example Scenarios • Scenario 1: – User 1@ernie: • Current Location: ernie, HOME –

Example Scenarios • Scenario 1: – User 1@ernie: • Current Location: ernie, HOME – User 2@bert: • Current Location: ernie, ROAMING • Scenario 2: – User 1@ernie: • Current Location: bert, ROAMING – User 2@bert: • Current Location: ernie, ROAMING

Scenario 1: Registration User 1@ernie Serving CSCF Proxy CSCF HSS Ernie User 2@bert HSS

Scenario 1: Registration User 1@ernie Serving CSCF Proxy CSCF HSS Ernie User 2@bert HSS Bert

Scenario 1: Registration User 1@ernie Serving CSCF Proxy CSCF HSS Ernie User 2@bert HSS

Scenario 1: Registration User 1@ernie Serving CSCF Proxy CSCF HSS Ernie User 2@bert HSS Bert

User 1@ernie calls User 2@bert User 1@ernie Serving CSCF Proxy CSCF HSS Ernie User

User 1@ernie calls User 2@bert User 1@ernie Serving CSCF Proxy CSCF HSS Ernie User 2@bert HSS Bert

Simulation Example • Features implemented – If User 2@bert not registered, error returned. –

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

Proposed Change in the Signalling Path • For Session Initiation, the signalling path may

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

User 1@ernie calls User 2@bert User 1@ernie Serving CSCF Proxy CSCF HSS Ernie User

User 1@ernie calls User 2@bert User 1@ernie Serving CSCF Proxy CSCF HSS Ernie User 2@bert HSS Bert

Results • Proposed change results in decrease in Call Setup Delay. • Caveat: Different

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

Thank You !!

Thank You !!