(Logo Tech-invite)  

a Portal devoted to SIP and surrounding technologies

  (World Map)    
    Search Home Site Map Contact
 SIP/IMS Standardization
> IETF Standardization Process
> RFCs related to SIP (4 p.) o
> SIP-SIPPING-SIMPLE... I-Ds (22 p.) o
> Audio-Video Transport RFCs (2 p.)
> 3GPP Specifications (12 p.)
> OMA Specifications related to SIP
> TISPAN NGN Specifications (3 p.) o
> SIP Topics
> IMS Topics
 SIP/IMS Call Flows
> RFC3261's Example
> Basic -- RFC3665
> SIP PSTN -- RFC3666 (3 p.)
> SIP Service Examples (19 p.)
> IMS Signaling Flows (35 p.)
 SIP/IMS Architecture
> SIP Protocol Structure
> Dialogs & Routing
> UMTS Network Evolution
 Security
> PKIX-TLS-SMIME... Standards (20 p.) o
> Cryptography Basics
> ASN.1 for PKI Certificate & CRL Profile
> ASN.1 for CMS
> RFC3280's Certificate Examples (4)
> RFC4134's CMS-S/MIME Examples (14)
> RFC4474's SIP Authentication Service
> SSL/TLS Time-Diagrams
> IPSec Guides
 ABNF Grammars
> ABNF Notation & Rules
> URI Generic Syntax
> ABNF for SIP
> SIP Messages & URIs
> SIP Header Fields
> MIME Media Types
> ABNF for SDP
> ABNF for MSRP
> ABNF for MRCPv2
> ABNF for RTSP 2.0
> Internet Message Format
 DiffServ CoS Simulation
> IPVCoSS Simulator
> IP-VPN Case Study
  o (daily updated)

3GPP TS 24.228 -- IMS Signalling flows for Session Initiation

Registration: Non Hiding
> User not registered
> Reregistration
> Subscription by UE
> Subscription by P-CSCF
> Deregistration by S-CSCF
> Deregistration by HSS
> Network-initiated deregistration
> Network initiated re-authentication
 
Registration: Hiding
> User not registered
>
 
Mobile initiated deregistration
 
Session Initiation: Non Hiding
> MO#1a / S-S#1a / MT#1a
> MO#2 / S-S#2 / MT#2
> CS-O / S-S#2 / MT#2
> MO#2 / S-S#3 / CS-T
> MO#2 / S-S#2 / MT#1c
 
Session Initiation: Hiding
> MO#1b / S-S#2 / MT#2
> MO#2 / S-S#1b / MT#2
> MO#2 / S-S#1c / MT#2
> MO#2 / S-S#1d / MT#2
 

Non Hiding: MO#2 / S-S#3 / CS-T

- Mobile Origination, located in home network
- PSTN Termination performed by Home Network of Originator
- CS Network Termination

fig0

MO#2 / S-S#3 / CS-T
1) INVITE (UE1 to UE2) 2) 183 Session Progress 3) PRACK (UE1 to UE2) 4) 200 OK   Prev Next
5) UPDATE (UE1 to UE2) 6) 200 OK 7) 180 Ringing (INVITE) 8) PRACK (UE1 to UE2)     a)
9) 200 OK 10) 200 OK (INVITE) 11) ACK (UE1 to UE2)       Top

fig1

1a)  from UE1 to P-CSCF1   (a) (b) (c) (d) Prev Next Up

fig1a

- UE#1 builds an SDP offer containing bandwidth requirements and characteristics for each set of codecs that it is capable of supporting for this session. It assigns local port numbers for each possible media flow. UE#1 is willing to establish a multimedia session comprising a video stream and an audio stream. The video stream supports two codecs, either H.263 or MPEG-4 Visual. The audio stream supports the AMR codec.
- Request-URI: contains the international E.164 number from the user.
- Via: contains the IPv6 address or FQDN (fully qualified domain name) of the originating UE.
- Route: contains the P-CSCF address learnt during P-CSCF discovery, plus the elements from the Service-Route header from registration. The P-CSCF URI contains the port number learnt during the security agreement negotiation.
- P-Preferred-Identity: the user provides a hint about the identity to be used for this session.
- P-Access-Network-Info: the UE provides the access-type and access-info, related to the serving access.
- Privacy: the user does not require privacy, therefore the Privacy header is set to the value "none" as specified in RFC 3325 and RFC 3323.
- Security-Verify: Contains the security agreement as represented by the received Security-Server header.
1b)  from P-CSCF1 to S-CSCF1   (a) (b) (c) (d) Prev Next Up

fig1b

- S-CSCF#1 validates the service profile of this subscriber and evaluates the initial filter criterias. For this example, assume no Application Server involvement.
- S-CSCF#1 performs an analysis of the destination address, and determines the destination is on the PSTN. S-CSCF forwards the INVITE request to the BGCF in the local network.
1c)  from S-CSCF1 to BGCF1   (a) (b) (c) (d) Prev Next Up

fig1c

- P-Charging-Vector: The S-CSCF passes this header to the BGCF for charging.
- P-Charging-Function-Addresses: The S-CSCF inserts this header to provide the charging function addresses to the BGCF.
1d)  from BGCF1 to MGCF1   (a) (b) (c) (d) Prev Next Up

fig1d

MO#2 / S-S#3 / CS-T
1) INVITE (UE1 to UE2) 2) 183 Session Progress 3) PRACK (UE1 to UE2) 4) 200 OK   Prev Next
5) UPDATE (UE1 to UE2) 6) 200 OK 7) 180 Ringing (INVITE) 8) PRACK (UE1 to UE2)     a)
9) 200 OK 10) 200 OK (INVITE) 11) ACK (UE1 to UE2)       Top

fig2

2a)  from MGCF1 to BGCF1   (a) (b) (c) (d) Prev Next Up

fig2a

2b)  from BGCF1 to S-CSCF1   (a) (b) (c) (d) Prev Next Up

fig2b

2c)  from S-CSCF1 to P-CSCF1   (a) (b) (c) (d) Prev Next Up

fig2c

2d)  from P-CSCF1 to UE1   (a) (b) (c) (d) Prev Next Up

fig2d

  
Last update: January 26, 2008 
  
(to top) © 2005-2008 Joël Repiquet, All Rights Reserved.