(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)

IMS Signalling flows for session initiation: Hiding

MO#2 / S-S#1c / MT#2   (page 2 of 3)

- Mobile Origination, located in home network
- Different network operators performing origination and termination,
with configuration hiding by originating network operator
- Mobile Termination, located in home network
MO#2 / S-S#1c / MT#2
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)     p.#1 Top

fig3

3a)  from UE1 to P-CSCF1   (a) (b) (c) (d) (e) (f) Prev Next Up

fig3a

- UE1 determines which media flows should be used for this session, and which codecs should be used for each of those media flows. If there was any change in media flows, or if there was more than one choice of codec for a media flow, then UE1 includes a new SDP offer in the PRACK message sent to UE2. For this example, assume UE1 chooses H.263 as the codec to use for the single video stream. Therefore, UE1 sends a new SDP offer in the PRACK request.
- Request-URI: Takes the value of the Contact header of the received 183 Session Progress response.
- Via: Takes the value of either the IP address or FQDN of the originating UE.
- Cseq: Takes a higher value than that in the previous request.
- Security-Verify: Contains the security agreement as represented by the received Security-Server header.
3b)  from P-CSCF1 to S-CSCF1   (a) (b) (c) (d) (e) (f) Prev Next Up

fig3b

- P-CSCF1 removes the Security-Verify header and associated "sec-agree" option-tags prior to forwarding the request. As the Proxy-Require header is empty, it removes this header completely.
3c)  from S-CSCF1 to I-CSCF1 (THIG)   (a) (b) (c) (d) (e) (f) Prev Next Up

fig3c

3d)  from I-CSCF1 (THIG) to S-CSCF2   (a) (b) (c) (d) (e) (f) Prev Next Up

fig3d

3e)  from S-CSCF2 to P-CSCF2   (a) (b) (c) (d) (e) (f) Prev Next Up

fig3e

3f)  from P-CSCF2 to UE2   (a) (b) (c) (d) (e) (f) Prev Next Up

fig3f

MO#2 / S-S#1c / MT#2
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)     p.#1 Top

fig4

4a)  from UE2 to P-CSCF2   (a) (b) (c) (d) (e) (f) Prev Next Up

fig4a

4b)  from P-CSCF2 to S-CSCF2   (a) (b) (c) (d) (e) (f) Prev Next Up

fig4b

4c)  from S-CSCF2 to ICSCF1 (THIG)   (a) (b) (c) (d) (e) (f) Prev Next Up

fig4c

4d)  from ICSCF1 (THIG) to S-CSCF1   (a) (b) (c) (d) (e) (f) Prev Next Up

fig4d

4e)  from S-CSCF1 to P-CSCF1   (a) (b) (c) (d) (e) (f) Prev Next Up

fig4e

4f)  from P-CSCF1 to UE1   (a) (b) (c) (d) (e) (f) Prev Next Up

fig4f

MO#2 / S-S#1c / MT#2
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)     p.#1 Top

fig5

5a)  from UE1 to P-CSCF1   (a) (b) (c) (d) (e) (f) Prev Next Up

fig5a

- When the resource reservation is completed, UE1 sends the UPDATE request to the terminating endpoint, via the signalling path established by the INVITE request.
- Request-URI: Takes the value of the Contact header of the received 183 Session Progress response.
- Via: Takes the value of either the IP address or FQDN of the originating UE.
- Cseq: Takes a higher value than that in the previous request.
- Security-Verify: Contains the security agreement as represented by the received Security-Server header.
5b)  from P-CSCF1 to S-CSCF1   (a) (b) (c) (d) (e) (f) Prev Next Up

fig5b

- P-CSCF1 removes the Security-Verify header and associated "sec-agree" option-tags prior to forwarding the request. As the Require and Proxy-Require headers are empty, it removes these headers completely.
5c)  from S-CSCF1 to I-CSCF1 (THIG)   (a) (b) (c) (d) (e) (f) Prev Next Up

fig5c

5d)  from I-CSCF1 (THIG) to P-CSCF2   (a) (b) (c) (d) (e) (f) Prev Next Up

fig5d

5e)  from S-CSCF2 to P-CSCF2   (a) (b) (c) (d) (e) (f) Prev Next Up

fig5e

5f)  from P-CSCF2 to UE2   (a) (b) (c) (d) (e) (f) Prev Next Up

fig5f

MO#2 / S-S#1c / MT#2
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)     p.#1 Top

fig6

6a)  from UE2 to P-CSCF2   (a) (b) (c) (d) (e) (f) Prev Next Up

fig6a

6b)  from P-CSCF2 to S-CSCF2   (a) (b) (c) (d) (e) (f) Prev Next Up

fig6b

6c)  from S-CSCF2 to I-CSCF1 (THIG)   (a) (b) (c) (d) (e) (f) Prev Next Up

fig6c

6d)  from I-CSCF1 (THIG) to S-CSCF1   (a) (b) (c) (d) (e) (f) Prev Next Up

fig6d

6e)  from S-CSCF1 to P-CSCF1   (a) (b) (c) (d) (e) (f) Prev Next Up

fig6e

6f)  from P-CSCF1 to UE1   (a) (b) (c) (d) (e) Prev (f) Next Up

fig6f

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