(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: CS-O / S-S#2 / MT#2

- CS Network originated Session routed towards IM CN subsystem, through MGCF
- Single Network Operator performing Origination and Termination
- Mobile Termination, located in home network

fig0

CS-O / S-S#2 / 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)       Top

fig1

- The MGCF in the IM subsystem is a SIP endpoint that initiates requests on behalf of the CS Networks origination and Media Gateway. The subsequent nodes consider the signalling as if it came from a S-CSCF. The MGCF incorporates the network security functionality of the S-CSCF. This MGCF does not invoke Service Control, as this may be carried out in the CS Networks or at the terminating S-CSCF.
- The CS Network establishes a bearer path to the MGW, and signals to the MGCF with a IAM message, giving the trunk identity, destination information and optionally the continuity indication.
- The MGCF initiates a H.248 command, to seize the trunk and an IP port.
1a)  from MGCF1 to I-CSCF1   (a) (b) (c) (d) Prev Next Up

fig1a

- Request-URI: Contains the international E.164 number from the user, as obtained from CS Networks signalling.
- Via: Contains the IP address or FQDN of the originating MGCF.
- P-Asserted-Identity: The MGCF inserts the TEL URL containing the subscriber number, as received from the CS network.
- P-Charging-Vector: The MGCF inserts this header and populates the icid parameters with a globally unique value.
- Contact: SIP URI that contains the IP address or FQDN of the MGCF.
- SDP: Contains a preconfigured set of codecs supported by the MGW.
1b)  from I-CSCF1 to S-CSCF2   (a) (b) (c) (d) Prev Next Up

fig1b

- The I-CSCF does not add itself to the Record-Route header, as it has no need to remain in the signalling path once the session is established.
1c)  from S-CSCF2 to P-CSCF2   (a) (b) (c) (d) Prev Next Up

fig1c

1d)  from P-CSCF2 to UE2   (a) (b) (c) (d) Prev Next Up

fig1d

- Via: The P-CSCF adds the port number negotiated during the security agreement and the comp=sigcomp parameter to its Via header.
- Record-Route: The P-CSCF adds the port number negotiated during the security agreement and the comp=sigcomp parameter to its own URI.
- P-Media-Authorization: A P-CSCF generated authorization token. This particular example shows a Policy-Element generated by "pdf1.home1.net" with credentials "31S14621".
CS-O / S-S#2 / 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)       Top

fig2

2a)  from UE2 to P-CSCF2   (a) (b) (c) (d) Prev Next Up

fig2a

- P-Access-Network-Info: the UE provides the access-type and access-info, related to the serving access network.
- To: a tag is added to the To header.
- Contact: contains a SIP URI with the IP address or FQDN of the UE; it includes the comp=sigcomp parameter.
- SDP: the SDP contains the set of codecs supported by UE; it requests a confirmation of the QoS preconditions for establishing the session.
2b)  from P-CSCF2 to S-CSCF2   (a) (b) (c) (d) Prev Next Up

fig2b

- Record-Route: the P-CSCF rewrites the Record-Route header field value to remove the port number used for the security association and the comp=sigcomp parameter from its own URI.
- P-Asserted-Identity: P-CSCF inserts the default SIP URI of the user in the P-Asserted-Identity header field.
2c)  from S-CSCF2 to I-CSCF1   (a) (b) (c) (d) Prev Next Up

fig2c

- P-Charging-Vector: The S-CSCF adds the identifier of its own network to the terminating Inter Operator Identifier (IOI) parameter of this header and puts back the originating IOI parameter.
- P-Charging-Function-Addresses: The S-CSCF passes this header to the I-CSCF for charging.
2d)  from I-CSCF1 to MGCF1   (a) (b) (c) (d) Prev Next Up

fig2d

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