focus on internet & telecom standardization topics

hist. pages: SIP/IMS, SEC...
  Home Search
Organizations
# IETF   # 3GPP   # ETSI
# Alliances, Fora, & other SDOs
Standardization work
# IETF WGs: RFCs   # RFC index
# 3GPP Specifications  
# ETSI TISPAN NGN   # ETSI SCP
# SIP RFC3261's Example  
# SIP Protocol Structure  
# SIP Dialogs & Routing  
# SIP Service Examples  
# SIP Authentication Service  
# ABNF Grammars  
# IMS Signalling flows  
# 2G-3G Network Evolution  
# Cryptography Basics  
# SSL/TLS Sequence Charts  
# PKI Certificate Examples  
# PKI's ASN.1 Definitions  
# CMS Examples  
# CMS's ASN.1 Definitions  
# Network Simulation  

Session Initiation IMS Signalling flows
Hiding: MO#2 / S-S#1d / MT#2

- Mobile Origination, located in home network
- Different network operators performing origination and termination, with configuration hiding by terminating network operator
- Mobile Termination, located in home network
Top Prev Next Start   IMS Signaling Flows
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
 

MO#2 / S-S#1d / 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

- UE1 is located in the home network, and determines the P-CSCF via the CSCF discovery procedure.
- During registration, the home network allocates an S-CSCF in the home network.
1a)  from UE1 to P-CSCF1   (a) (b) (c) (d) (e) (f) Prev Next Up

- UE1 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. UE1 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, including the port number negotiated during the security agreement, plus the elements from the Service-Route header from registration.
- P-Preferred-Identity: The user provides a hint about the identity to be used for this session.
- P-Access-Network-Info: UE1 provides the access-type and access-info, related to the serving access network.
- 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.
- Contact: SIP URI that contains the IP address or FQDN of the originating UE. It also contains the port number where the UE wants to receive protected messages.
- 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) (e) (f) Prev Next Up

- P-CSCF1 adds itself to the Record-Route header and Via header. As the request is forwarded to an interface that is not compressed, the own P-CSCF SIP URI does not contain the "comp=sigcomp" parameter.
- 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.
- P-Asserted-Identity: P-CSCF1 inserts the SIP URI in the P-Asserted-Identity header field and it also removes the P-Preferred-Identity header field.
- P-Charging-Vector: P-CSCF1 inserts this header and populates the icid parameters with a globally unique value.
1c)  from S-CSCF1 to I-CSCF2 (THIG)   (a) (b) (c) (d) (e) (f) Prev Next Up

- S-CSCF1 performs an analysis of the destination address, and determines the network operator to whom the destination subscriber belongs. S-CSCF1 forwards the INVITE request to I-CSCF2, the well-known entry point of the destination network.
- Request-URI: In the case where the Request-URI of the incoming INVITE request to S-CSCF contains a TEL-URL, it has to be translated to a globally routable SIP-URL before applying it as Request-URI of the outgoing INVITE request. For this address translation the S-CSCF uses the services of an ENUM-DNS protocol according to RFC 2916, or any other suitable translation database.
- P-Charging-Vector: S-CSCF1 adds the identifier of its own network to the originating Inter Operator Identifier (IOI) parameter of this header.
1d)  from I-CSCF2 (THIG) to S-CSCF2   (a) (b) (c) (d) (e) (f) Prev Next Up

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

- Route: Built from the Path header stored at registration.
- Via:/Record-Route: S-CSCF2 adds itself.
- P-Called-Party-ID: Includes the dialled URL with its parameters.
1f)  from P-CSCF2 to UE2   (a) (b) (c) (d) (e) (f) Prev Next Up

- Via: P-CSCF2 adds the port number negotiated during the security agreement and the comp=sigcomp parameter to its own entry.
- Record-Route: P-CSCF2 adds the port number negotiated during the security agreement and the comp=sigcomp parameter to its own SIP 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".
MO#2 / S-S#1d / 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

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

- P-Access-Network-Info: UE2 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 terminating UE.
- SDP: Contains the set of codecs supported by UE2. It requests a confirmation of the QoS preconditions for establishing the session.
2b)  from P-CSCF2 to S-CSCF2   (a) (b) (c) (d) (e) (f) Prev Next Up

- Record-Route: P-CSCF2 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-CSCF2 inserts the default SIP URI of the user in the P-Asserted-Identity header field.
2c)  from S-CSCF2 to I-CSCF2 (THIG)   (a) (b) (c) (d) (e) (f) Prev Next Up

- P-Charging-Vector: S-CSCF2 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: S-CSCF2 passes this header to I-CSCF2 for charging.
2d)  from I-CSCF2 (THIG) to S-CSCF1   (a) (b) (c) (d) (e) (f) Prev Next Up

- Record-Route: I-CSCF2 tokenizes the entries of its own network.
2e)  from S-CSCF1 to P-CSCF1   (a) (b) (c) (d) (e) (f) Prev Next Up

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

- P-Media-Authorization: a P-CSCF generated authorization token. This particular example shows a Policy-Element generated by "pdf1.home1.net" with credentials "9BV3072". "00" at the end of the authorization token is required to pad to a multiple of 4 bytes.
- Record-Route: P-CSCF1 rewrites the Record-Route header to add the port number negotiated during the security agreement and the comp=sigcomp parameter to its own SIP URI.
Last update: November 19, 2009 
© 2005-2010 Joël Repiquet, All Rights Reserved.