IMS Basic Signaling Procedure SIP IMS Procedures

IMS Basic Signaling
Procedure
www.huawei.com
Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.

References
 IMS Solution Manual – Basic Signaling Procedure Volume
Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved. Page 3
Objectives
 Upon completion of this course, you will be able to:

Describe the basic SIP concepts and SIP basic procedure.

Describe the basic registration procedure on the IMS network.
 Describe the basic session procedure on the IMS network.
Contents
1. SIP Overview
2. IMS Registration and Related Procedures
3. IMS Session and Related Procedures
Contents
1. SIP Overview

1.1 SIP Overview

1.2 SIP Message Structure
Origination and Development of SIP
 The SIP was originated in the Mbone (multicast backbone)
experiment in 1996.
 In 1999, the SIP was defined by the IETF-MMUSIC in RFC2543.
 In 1999, the IETF-MMUSIC became the independent SIP task force.
 Later, two SIP-centered task forces, namely, SIPPING and SIMPLE,

were added.
 In July, 2002, the SIP was defined in the new RFC3261.
 Most contents are rewritten and clearer. In addition, certain new

features are added.
 Most contents are backward-compatible with RFC2543.
What’s SIP?
 SIP: Session Initiation Protocol

 Setting up, controlling and tearing down sessions
 SIP is an IETF protocol for multi-media sessions
 Sessions including text, video, voice, etc.
 SIP is one of the Internet protocol
 Text based like HTTP
 Request/Reply protocol
 Widely used for successful Internet
 Can be based on UDP/TCP/SCTP, most of the case now use UDP
Session Related Protocols
 Signaling protocol

�Registration, user locating, and routing
 �Session establishment, modification, and release
 Media transport protocol

�Transmission of voice and video
 SIP – signaling protocol
 Session description (SDP) is separated from session management

(SIP).
Simplified SIP Network Architecture
Request Proxy Server

Determines Where to Send
the Signaling Messages
User Agent SIP Request User Agent

(Client) SIP Request
(Server)
Sends SIP Receives SIP
Requests Requests
SIP Response SIP Response
Media Stream (RTP)
Logical Entities of SIP
 SIP use client/server architecture
Logical SIP entities are:
User Agents (UA) Network Servers

 User Agent Client (UAC):  Register: Maintains the location of SIP
Initiates SIP requests users, sip clients needs to update the
 User Agent Server (UAS): location using register request
 Proxy: decides next hop and forwards
Returns SIP response
request
 Both UAC and UAS can
 Redirect: Accepts SIP request and
terminate a call
translates to new address
Contents
1. SIP Overview

1.1 SIP Overview

1.2 SIP Message Structure
SIP Message Structure
 The SIP consists of three parts:

Message type

Message structure
 Message parameter
Message Types
 SIP messages can be classified into two types:

 Request
 Initiates a session.
 Response
 Responds to a request.
SIP Message Type -- Request
Basic Request Extended Request
 INVITE: to initiate a session  MESSAGE: is applied to IM
 ACK: the response of INVITE  SUBSCRIBE : to subscribe to a notify event
 CANCEL: to cancel a session  NOTIFY: to send a notify event
 UPDATE: to modify the session attributes at

 BYE: to terminate a session
the establishment stage of a call
 REGISTER: to register in a server
 PUBLISH: to distribute its event state to the
 OPTIONS: for querying servers
status server
about their capabilities
 PRACK: to indicate the reliability of a
temporary response
SIP Message Type -- Response
 SIP response type:

1xx: Provisional -- request received, continuing to process the
request;

2xx: Success -- the action was successfully received, understood, and
accepted;

3xx: Redirection -- further action needs to be taken in order to
complete the request;

4xx: Client Error -- the request contains bad syntax or cannot be
fulfilled at this server;

5xx: Server Error -- the server failed to fulfill an apparently valid
request;

6xx: Global Failure -- the request cannot be fulfilled at any server.
SIP Basic Flow
 Session setup  Registration
Client A Proxy A Proxy B Client B Client A Proxy A

INVITE INVITE
Register
100 TRYING INVITE
100 TRYING 401 unauthorized
100 TRYING
Register
180 RINGING
180 RINGING 200 OK
180 RINGING 200 OK
200 OK
200 OK
SIP Message Structure
 SIP is a Text-
based protocol
and comprise
by 3 parts:

Request-Line
 Header

Body

SIP Header Fields
INVITE sip:[email protected] SIP/2.0

From: <sip:[email protected]>;tag=1ccb6df3
To: <sip:[email protected]>
CSeq: 1 INVITE
Call-ID: 20973e49f7c52937fc6be224f9e52543@sx3000
Via:SIP/2.0/UDP server9.example.com;branch=z9hG4kb77ef4c23
Via: SIP/2.0/UDP 191.169.1.116:5061;branch=z9hG4bkbc427dad6
Record-Route:<sip:server9.example.com.lr>
Route:<sip:server10.example.com.lr>
Contact: <sip:[email protected]:5061>
Supported: 100rel,
Max-Forwards:70
User-agent: Flexit-IMS softphone V1.2D301SP03
Expires:120
Content-Length:230
Content-Type: application/sdp
SIP Header Fields
 TO ： the target of this request  Record-Route ： It is added by a proxy in a request to
 FROM ： the logical identity of the initiator of the request force subsequent requests in the session to be routed
through the proxy. It is used to create the Route header
 Cseq ： command sequence No., unique in the Call-ID range
field in subsequent requests.
 Consists of a sequence number and a method  Route: It is used to forcibly route a request through the

The SIP method must be the same as that carried in the listed set of proxies.
request.
 Contact: It provides an address for direct communication

 Call-ID: A globally unique identifier . Call-ID and tags are used with the user. It is present in INVITE, ACK, and
to identify a dialog. REGISTER requests, success responses, call process
responses, and redirection responses
 Via: Identifies the route for the response. The Via field
prevents loops in the message transfer and ensures that the  Supported: 100rel,: supporting 1XX responses. A
request and response follow the same path. terminal can return a PRACK response to improve
 The Via field must contain the branch parameter to identify reliability.
the transaction.
 Max-Forwards: It limits the number of hops a request can
transit on the way to its destination. The error response is
483(too many hops). It is used in request messages only.
SIP Extension Header
 Example
REGISTER sip ： registrar.bplace.com SIP/2.0

Via ： SIP/2.0/UDP 8.27.2.102 ： 10226;branch=z9hG4bod840d0w
Via ： SIP/2.0/UDP 8.27.22.224 ： 5061;branch=z9hG4bKnashds7
;received=192.0.2.4
To ： B <sip ： [email protected]>;
From ： B <sip ： [email protected]>;tag=456248
P-Access-Network-Info ： 3GPP-UTRAN-TDD;utran-cell-id-3gpp=234151D0FCE
P-Visited-Network-ID ： "8.27.2.102" SIP extension
P-Charging-Vector ： icid-value="8.27.2.102.3348465999.3157.14" header
Call-ID ： [email protected]
CSeq ： 1826 REGISTER
Contact ： <sip ： [email protected] ： 5061>;
Expires ： 7200
Content-Length ： 0
Some Extension Header Examples in IMS
Extension Header Function

Examples
P-Access-Network-Info Is used by the SIP UA to transfer access network
technologies to the service proxy
P-Visited-Network-ID Is used to relay the identification of the visited domain to the
registrar and proxy in the home realm
P-Charging-Vector Cooperates with the P-Charging-Function-Address header
field to transfer charging information over the network
P-Asserted-Identity Formally indicate the calling party ID
Service-Route Used to inform the S-CSCF IP for P-CSCF during Register
Path Used to inform the P-CSCF IP for S-CSCF during Register
SDP Example (Explanations of
Related Parameters)
v=0
o=HuaweiSoftX3000 868 868 IN IP4 10.216.9.200
s=Sip Call
c=IN IP4 10.216.6.108
t=0 0
m=audio 17368 RTP/AVP 8
a=rtpmap ： 8 PCMA/8000
SDP Parameter
Remarks
Parameter Name
v Version number v=0
o Origin containing o=<user name> <session id> <version> <network

name type> <address type> <address>
s Subject
c Connection Connection IP address(10.216.6.108)
t Time t=<start time> <stop time>
m Media Media format (audio); Port number(17368)
a Attribute Media encoding (PCM A Law); Sample rate (8000Hz)
Contents
1. SIP Overview
IMS User Registration Procedure
S-CSCF
HSS
Register
I-CSCF
Register
P-CSCF
Register
UE
Contents
2. Procedures Related to IMS Registration

2.1 Local P-CSCF discovery
2.2 Serving‑CSCF assignment
2.3 Registration procedure
P-CSCF Discovery
S-CSCF
HSS
Register
I-CSCF
Register
P-CSCF
Register
U
E
Proxy‑CSCF Discovery
 Proxy-CSCF discovery

The procedure of UE getting to know the address of P-CSCF.

In order to communicate with IMS network, UE must know at least 1 IP
address of P-CSCF.
 3 ways for P-CSCF discovery


GPRS procedure

Get the PCSCF IP from GGSN.

DHCP/DNS procedure

DHCP server can provide PCSCF IP/domain name while assign dynamic IP
addresses.

Set the static configuration in UE
P-CSCF Discovery
UMTS
a t ion
t ac ti v GGS allocate IP address
of the P-CSCF and IP
ontex dure N
for UE
D P c proce
P
DNS
query/resp
o nse
qu
er D H C
y/r
es P
po IP
ns
e DHCP relay
DHCP server DNS server
Other access
networks
Contents

2.1 Procedures of Local P-CSCF Discovery
2.2 Procedures of S-CSCF Assignment
2.3 Registration Procedures
S-CSCF Assignment
S-CSCF
HSS
Register
I-CSCF
Register
P-CSCF
Register
U
E
S-CSCF Assignment
 When a user is registered with the network for accessing the IMS service,
the I-CSCF allocates an S-CSCF to the UE.
 The I-CSCF communicates with the HSS by using the Cx interface to obtain
the information required for selecting an S-CSCF.
 If the HSS returns the name of an S-CSCF, the I-CSCF checks the IP
address of the S-CSCF by using the S-CSCF name returned by the
HSS.
 f the HSS returns the capability set of an S-CSCF, the I-CSCF executes
an algorithm according to the capability set of each received S-CSCF to
select an appropriate S-CSCF.
S-CSCF Assignment
 I-CSCF selects the S-CSCF according to their capabilities
 Capability ID and meaning is defined by the operator.
Capability set of every SCSCF

is configured in ICSCF
S-CSCF1
Capability ： 3,4,5
P-CSCF I-CSCF
Service name Capability ID S-CSCF2

User1 Subscribe info of user1: Capability ：
emergency Mandatory Capability ： 1,2,3,4 1,2,3,4,5
call 1 Optional Capability ： 5 ， 6
SIP extending
function 1 2
S-CSCF3
SIP extending 3 Capability ： 1,2,3
function 2 HSS
… …
Contents

2.1 Procedures of Local P-CSCF Discovery
2.2 Procedures of S-CSCF Assignment
2.3 Registration Procedures
Related Concepts of Registration Procedures
 Why registration is required
 Users use IMPUs (SIP URIs) for communication.
 Current IP address of users are mapped to IMPUs.
 The information about the locations and service capabilities of users can be obtained.
 Authentication and authorization during registration ensures network security.
 Home network and the visited network


Home network ： the operator where the user’s information subscribed

Visited network ： when user accesses to the network by other operators, these operator are
called visited network.
 In IMS network, the registration procedures are the same no matter user accesses from the
home network or visited network.
Initial Register in Home or Visited Network
HSS
Home
network
Au atio t
(5 enti
th n
)
c e
(3)
s
S-CSCF assignment
(1) P-CSCF (2) I-CSCF

Register Register (4 S-CSCF
)
(6
(8 (7
)
) ) 401
401 401
Visit Home HSS

network network
Au atio t
(5 enti
th n
)
c se
(3)
S-CSCF assignment
(1) P-CSCF (2) I-CSCF

Register Register (4) S-CSCF
(6
(8 (7
)
) ) 401
401 401
Related Concepts - Authentication
 Authentication
 Authentication is a method used to identify a user and ensure the validity of the user.
 The home network authenticates users by using the user initial registration procedure.
 When a user terminal initiates initial registration, the S-CSCF authenticates the
terminal according to the header field carried in the Register message and the
authentication mode selected when the user is defined on the HSS.
 Currently, the HTTP Digest authentication mode is adopted for fixed terminals. That
is, the authentication is performed on the basis of user names and passwords.
 Authentication and authorization during registration ensures network security.
Related Concepts – Service Profile
 Service profile is the set of service and user related data.


Basic IMS service profile consists of charging address setting, block
setting, registration authority setting, roaming authority setting,
subscription media ID, iFC, and S-CSCF capability set.

iFC is used for SCSCF to trigger the service request to AS.

Store in HSS, and downloaded by SCSCF during the register.
Service Which AS will handle the 3rd

Block Profile iFC1 party register?
setting
Registration
iFC2 Which AS(s) will handle the
authority
caller side services?
Roaming iFC3
authority
iFC n Which AS(s) will handle the
……
called side services?

Other Related Concepts
 Implicit Registration
 When one IMPI is associated with multiple IMPUs which are in the same IRS,
the registration of all the IMPUs in the IRS can be implemented through the
IMS registration of one IMPU. This is called implicit registration.
 Third-Party Registration
 If a user has subscribed to IMS services, after the user is registered
successfully, the S-CSCF checks the downloaded iFC and triggers the route to
the AS which serves the user.
Registration Procedure
1 － Initial register message 2 － 2nd register message

S-CSCF-A
S-CSCF-A
(6) (15)
Authentication User profile
data
HSS-A HSS-A
(14)
(5) (13) Register
(4) Register
Assign S-CSCF Assign S-CSCF (16)
(7 200 OK
)
401
I-CSCF-A I-CSCF-A
(3) (12)
Register Register
(8 (17)
200 OK
)
401
P-CSCF-A
P-CSCF-A
(1) (2) (11)

Register
DNS query (10) DNS query
(9 DNS Register
(18)
) 200 OK
401
U U
E E
Registration Signaling Flow
Home Network
Caller UE P-CSCF DNS I-CSCF S-CSCF HSS
Initiate 1.REGISTER
2.DNS Query S-CSCF
register 3.DNS Query assignment
Resp
4. REGISTER 5. Diameter: UAR
6. Diameter: UAA
Send the 7.REGISTER
authentication Download the
8.Diameter: MAR authentication
parameters to UE 10. 401 9.Diameter: MAA sets
Unauthorized
12. 401 11. 401 Unauthorized
Unauthorized
13.REGISTER
14.DNS Query
15.DNS Query
S-CSCF
Resp assignment
16. REGISTER
17. Diameter: UAR
Authentication 18. Diameter: UAA Download

response 19.REGISTER service
20.Diameter: SAR profile （ iFC
21.Diameter: SAA etc..)
22. 200 OK
23. 200 OK
24. 200 OK AS
25.REGISTER
3rd party
26. 200 OK
registration

Diameter Message
Message Explanation
UAR User Authorization Request
UAA User Authorization Answer
MAR Multimedia Authentication Request
MAA Multimedia Authentication Answer
SAR Server Assignment Request
SAA Server Assignment Answer
Functions of NEs During Registration
 The following table describes the functions of the main NEs during the registration:
NE Function
-> Checking the IMPI, IMPU, and home domain

-> Querying the DNS to obtain the I-CSCF IP address
PCSCF
based on the home domain and forwarding the initial
registration request
-> Querying the HSS to select an S-CSCF and specifying

ICSCF the S-CSCF
-> Forwarding the registration request to the S-CSCF
-> Downloading authentication data from the HSS to

authenticate the terminal
SCSCF -> Downloading the service subscription data (service
profile) of the user from the HSS
Stored Information
Node Before During Registration After Registration
Registration
IMPI, IMPU, Same as before registration IMPI,IMPU, Credentials
Credentials Home Domain
UE Home Domain Proxy Name/Address
Proxy Name/Address
P － CSCF DNS address I-CSCF address/name Final Network Entry point

(in Home or UE Address ， IMPI ， IMPU UE Address, IMPI ， IMPU
Visited network) S-CSCF address
I-CSCF HSS address S-CSCF address/name No State Information

(in Home (temporary)
network)
HSS address HSS Address/name May have session state
S-CSCF User profile Information Same as during
(in Home P-CSCF address/name registration
network) P-CSCF Network ID Service profile
UE IP Address, IMPI ， IMPU P-CSCF address
HSS User Service Profile P CSCF Network ID S-CSCF address/name
De-registration Procedures
 UE initiated de-registration
 Network initiated de-registration
 HSS initiated the de-registration procedures before the register timer expires
 AS initiated the de-registration procedures before the register timer expires

The register timer expires, network initiated the de-registration procedures
User Initiate the Deregister
Switch off the UE

cause Roaming handover
S-CSCF Initiate the Deregister
The S-CSCF needs to be shut down.

cause The user is a owing subscriber
Questions
 What are the IMS NEs that perform registration on IMS users?
 What are the steps of IMS user registration?
Contents
1. SIP Overview
Session Procedure Related Network Nodes
UE Main Functions
P-CSCF 1: Caller part: the 1st contact point to access to the IMS
2: Callee part: P-CSCF forwards the messages to the callee
S-CSCF Realize the call control function for both caller part and callee part
I-CSCF Contact point to access to the callee’s home network .
AS Implement service for both caller and callee side.
DNS/ DNS: Reply the ICSCF IP address for S-CSCF query
ENUM ENUM: Map the TEL format IMPU to SIPURI format
HSS Only used in the callee part. I-CSCF locate the SCSCF by query the
HSS
Procedures Involved in a Session
Procedures involved in the

session
Session Session
establishment release
procedure procedure
Media Resource Application

negotiation reservation service
procedure procedure session
procedure
 Session procedure of the application service

In the session procedure, the AS processes the
corresponding service. In the basic call procedure,
no AS is involved.
Internal Phases of the IMS Session Procedure
 Establishment of sessions include: Origination procedures, SS
procedures and Termination procedures
MO procedure SS procedure MT procedure
 From the caller UE to  From the S-CSCF/AS  From the S-CSCF/AS

the S-CSCF/AS where in the caller part to the where the callee UE
the caller UE registered S-CSCF/AS in the registered to the callee
callee part UE
Simple Model for Call Procedure
 During a call between IMS users, the P-CSCF, I-CSCF, and S-CSCF completes the
entire signaling routing procedure.
MO S MT
S
3.request 4.request Callee part

Caller part
S-CSCF I-CSCF S-CSCF
2.request 5.request
DNS/ENU
M HSS
P-CSCF P-CSCF
1.request 6.request
media
Signalin
Media
g
DNS&ENUM
ENUM
DNS function function
huawei.com +8675528780808
Calling party Called party

S-CSCF
I-CSCF
S-CSCF
P- HSS
CSCF P-CSCF
DNS/ENUM ENU
M
189.17.2.123 Media [email protected]
Basic Session Establishment
Procedure Between IMS Users
S-CSCF-A I-CSCF-B
Invite
183
HSS-A
183 Invite HSS-B
Invite
I-CSCF-A
S-CSCF-B
DNS/ENUM
183
Invite
183
P-CSCF-A
P-CSCF-B
Invite Invite
183
183
media
Processing of Service Triggering

AS-A AS-B
HSS-B
Invite 3 Invite 4 Invite 7 Invite 8
Invite 5 Invite 6
S-CSCF-A
HSS-A 183
I-CSCF-B S-CSCF-B
Invite 2
183 Invite 9
I-CSCF-A 183
DNS/ENUM
P-CSCF-B
P-CSCF-A
Invite 1 Invite 10
183 183
IP media stream
IMS User Call to a PSTN User
IMS calling PSTN called party

party
S-CSCF-A
Invite
HSS-A
Fail
Query
I-CSCF-A Tel MGCF PST
Invite
IAM N
Invite
P-CSCF-A ENUM
Media
control
Invite
UMG
PSTN User Call to an IMS User
IMS called party PSTN

I-CSCF-A
calling party
HSS-A
Invite Invite
S-CSCF-A
MGCF PSTN/PLMN
IAM
Invite
P-CSCF-A
Invite
UMG
Routing During the Session
Establishment Procedure
 MO procedure (Mobile origination)

From the calling UE to the P-CSCF:
The UE obtains the P-CSCF address through P-CSCF discovery and thus routes the call
to the P-CSCF.
 From the calling P-CSCF to the calling S-CSCF:
Both the UE and P-CSCF obtain the S-CSCF address through the registration procedure.
 SS procedure
 From the calling S-CSCF to the called I-CSCF:
The host part (domain name) of the public user identity of the callee is resolved through
DNS. The calling S-CSCF receives an I-CSCF address returned by DNS.
Routing During the Session Establishment
Procedure (2)
 MT procedure (Mobile termination)
 From the called I-CSCF to the called S-CSCF:
Serving as the ingress of the home network of the callee, the I-CSCF queries the local
HSS to obtain the S-CSCF address selected by the callee during the registration.
 From the called S-CSCF to the called P-CSCF:
The called S-CSCF obtains the address of the called P-CSCF during the registration of the
callee. Note that the S-CSCF, serving as the registrar, converts the SIP URI of the called
UE into the contact address.
 From the called P-CSCF to the called UE:
The message is forwarded to the called UE according to the contact address of the called
UE.
Session Signaling Procedure of IMS Users
UE1/PCSCF1 SCSCF1/AS1 ICSCF2 SCSCF2/AS2 PCSCF2/UE2
INVITE
INVITE INVITE
INVITE
183 The IMS user

183
183 performs
183
media
PRACK PRACK PRACK negotiation to
determine the
200 OK(PRACK) 200 OK(PRACK) media IP
200 OK(PRACK)
address,
UPDATE UPDATE UPDATE media stream
200 OK type, and
200 OK 200 OK
(UPDATE) (UPDATE) (UPDATE) coding/decodi
180 Ringing 180 Ringing 180 Ringing 180 ng methods.
Ringing
PRACK PRACK PRACK
200 OK 200 OK 200 OK
200 OK 200 OK 200 OK

200 OK (INVITE)
(INVITE) (INVITE) (INVITE)
ACK ACK
ACK
The session is
established.
Media Characteristics Negotiation
 The Media Negotiation is the procedures for determining the set of

negotiated characteristics (media type, codec, etc) between the
endpoints of a multi-media session.
 Both sides need to negotiate the media type and the codec which they
are going to use.
We have to use the OK, let’s exchange

same media type the information
and codec
Support Support:
:
Audio
Audio G.729
G.729 H.263
Media Characteristics Negotiation
 Media
A SIP Message “INVITE”
Characteristics
are described in
the SDP in the
SIP message
Support codec
types
Media Characteristics Negotiations
 SIP messages can contain SDP to initiate media negotiation
INVITE （ provided by the first SDP:

required media type and all the codec)
183 （ first response from SDP:

supported media type and the codec)
PRACK （ provided by the second SDP:

negotiated media type and the codec)
200 OK( the second response from SDP:

confirm to the media type and the codec
negotiated)
Questions
 What are the phases of the session establishment procedure?
 What are the main NEs that are passed through in the basic
session establishment procedure?
Summary
 In this course, the following topics are covered:

 IMS protocol
 IMS registration procedure
 IMS session procedure
Thanks
www.huawei.com

IMS Basic Signaling Procedure SIP IMS Procedures

Uploaded by

Copyright:

Available Formats

IMS Basic Signaling Procedure SIP IMS Procedures

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IMS Basic Signaling Procedure SIP IMS Procedures

Uploaded by

Copyright:

Available Formats

IMS Basic Signaling

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.

2. IMS Registration and Related Procedures

3. IMS Session and Related Procedures

 In 1999, the IETF-MMUSIC became the independent SIP task force.

 Later, two SIP-centered task forces, namely, SIPPING and SIMPLE,

 Most contents are rewritten and clearer. In addition, certain new

 SIP: Session Initiation Protocol

 SIP – signaling protocol

 Session description (SDP) is separated from session management

Request Proxy Server

User Agent SIP Request User Agent

SIP Response SIP Response

Media Stream (RTP)

 SIP use client/server architecture

Logical SIP entities are:

User Agents (UA) Network Servers

 SIP messages can be classified into two types:

Basic Request Extended Request

 INVITE: to initiate a session  MESSAGE: is applied to IM

 ACK: the response of INVITE  SUBSCRIBE : to subscribe to a notify event

 CANCEL: to cancel a session  NOTIFY: to send a notify event

 UPDATE: to modify the session attributes at

 Session setup  Registration

Client A Proxy A Proxy B Client B Client A Proxy A

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.

INVITE sip:[email protected] SIP/2.0

 Contact: It provides an address for direct communication

REGISTER sip ： registrar.bplace.com SIP/2.0

Extension Header Function

o Origin containing o=<user name> <session id> <version> <network

2. IMS Registration and Related Procedures

3. IMS Session and Related Procedures

2. Procedures Related to IMS Registration

2.2 Serving‑CSCF assignment

2.3 Registration procedure

 3 ways for P-CSCF discovery

2. IMS Registration and Related Procedures

2.2 Procedures of S-CSCF Assignment

2.3 Registration Procedures

Capability set of every SCSCF

Service name Capability ID S-CSCF2

2. IMS Registration and Related Procedures

2.2 Procedures of S-CSCF Assignment

2.3 Registration Procedures

 Home network and the visited network

(1) P-CSCF (2) I-CSCF

Visit Home HSS

(1) P-CSCF (2) I-CSCF

 Service profile is the set of service and user related data.

Service Which AS will handle the 3rd

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.

1 － Initial register message 2 － 2nd register message

(1) (2) (11)

Authentication 18. Diameter: UAA Download

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.

UAR User Authorization Request

UAA User Authorization Answer

MAR Multimedia Authentication Request