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
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.
Page 4
Contents
1.
SIP Overview
2.
IMS Registration and Related Procedures
3.
IMS Session and Related Procedures
Page 5
Contents
1.
SIP Overview
1.1 SIP Overview
1.2 SIP Message Structure
Page 6
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.
Page 7
Whats SIP?
SIP: Session Initiation Protocol
SIP is an IETF protocol for multi-media sessions
Setting up, controlling and tearing down 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
Page 8
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).
Page 9
Simplified SIP Network Architecture

Request Proxy Server
Determines Where to Send
the Signaling Messages
User Agent
(Client)
Sends SIP
SIP Request
SIP Request
Requests
SIP Response
SIP Response
Media Stream (RTP)
Page 10
User Agent
(Server)
Receives SIP
Requests
Logical Entities of SIP
SIP use client/server architecture

Logical SIP entities are:
Network Servers
User Agents (UA)

User Agent Client (UAC):
Initiates SIP requests
User Agent Server (UAS):
Returns SIP response
Both UAC and UAS can
terminate a call
Register: Maintains the location of SIP

users, sip clients needs to update the
location using register request
Proxy: decides next hop and forwards
request
Redirect: Accepts SIP request and
translates to new address
Page 11
Contents
1.
SIP Overview
1.1 SIP Overview
1.2 SIP Message Structure
Page 12
SIP Message Structure
The SIP consists of three parts:
Message type
Message structure
Message parameter
Page 13
Message Types
SIP messages can be classified into two types:
Request
Initiates a session.
Response
Responds to a request.
Page 14
SIP Message Type -- Request

Extended Request
Basic 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
BYE: to terminate a session
UPDATE: to modify the session attributes at
REGISTER: to register in a server

OPTIONS: for querying servers
about their capabilities
the establishment stage of a call

PUBLISH: to distribute its event state to the
status server
PRACK: to indicate the reliability of a
temporary response
Page 15
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.
Page 16
SIP Basic Flow
Client A
Session setup
Proxy A
INVITE
Registration
Proxy B
Client B
INVITE
INVITE
100 TRYING
100 TRYING
Client A
Register
401 unauthorized
100 TRYING
180 RINGING
180 RINGING
180 RINGING
Proxy A
Register
200 OK
200 OK
200 OK
200 OK
Page 17
SIP Message Structure
SIP is a Textbased protocol

and comprise
by 3 parts:
Request-Line
Header
Body
SIP Header Fields

INVITE sip:66500002@191.169.1.110 SIP/2.0
From: <sip:44510000@191.169.1.116>;tag=1ccb6df3
To: <sip:66500002@191.169.1.110>
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:44510000@191.169.1.116:5061>
Supported: 100rel,
Max-Forwards:70
User-agent: Flexit-IMS softphone V1.2D301SP03
Expires:120
Content-Length:230
Content-Type: application/sdp
Page 19
SIP Header Fields
TO the target of this request
FROM the logical identity of the initiator of the request
Cseq command sequence No., unique in the Call-ID range
Consists of a sequence number and a method
Call-ID: A globally unique identifier . Call-ID and tags are used

to identify a dialog.
Via: Identifies the route for the response. The Via field
prevents loops in the message transfer and ensures that the
request and response follow the same path.
Route: It is used to forcibly route a request through the

listed set of proxies.
Contact: It provides an address for direct communication

with the user. It is present in INVITE, ACK, and
REGISTER requests, success responses, call process
responses, and redirection responses
Supported: 100rel,: supporting 1XX responses. A

terminal can return a PRACK response to improve
reliability.
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.
The SIP method must be the same as that carried in the

request.
Record-Route It is added by a proxy in a request to

force subsequent requests in the session to be routed
through the proxy. It is used to create the Route header
field in subsequent requests.
The Via field must contain the branch parameter to identify

the transaction.
Page 20
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 b@bplace.com>;
From B <sip b@bplace.com>;tag=456248
P-Access-Network-Info 3GPP-UTRAN-TDD;utran-cell-id-3gpp=234151D0FCE
P-Visited-Network-ID "8.27.2.102"
P-Charging-Vector icid-value="8.27.2.102.3348465999.3157.14"
Call-ID 217944815@8.27.22.224
CSeq 1826 REGISTER
Contact <sip b@8.27.22.224 5061>;
Expires 7200
Content-Length 0
Page 21
SIP extension
header
Some Extension Header Examples in IMS

Extension Header
Examples
Function
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
Page 22
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
Parameter
Name
Version number
Origin containing o=<user name> <session id> <version> <network

name
type> <address type> <address>
Subject
Connection
Connection IP address(10.216.6.108)
Time
t=<start time> <stop time>
Media
Media format (audio); Port number(17368)
Attribute
Media encoding (PCM A Law); Sample rate (8000Hz)
Remarks
v=0
Page 23
Contents
1.
SIP Overview
2.
3.
Page 24
IMS User Registration Procedure

S-CSCF
HSS
Register
I-CSCF
Register
P-CSCF
Register
UE
Page 25
Contents
2. Procedures Related to IMS Registration
2.1 Local P-CSCF discovery
2.2 ServingCSCF assignment
2.3 Registration procedure
Page 26
P-CSCF Discovery
S-CSCF
HSS
Register
I-CSCF
Register
P-CSCF
Register
U
E
Page 27
ProxyCSCF 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
Page 28
P-CSCF Discovery
UMTS
ion
t
a
c ti v
a
t
tex dure
n
o
P c proce
D
P
qu
er D H C
y/r
es P
po
ns
e
Other access
networks
allocate IP address
of the P-CSCF and IP
for UE
GGS
N
DNS
query/resp
o
nse
IP
DHCP relay
DHCP server
DNS server
Page 29
Contents
2. IMS Registration and Related Procedures
2.1 Procedures of Local P-CSCF Discovery
2.2 Procedures of S-CSCF Assignment
2.3 Registration Procedures
Page 30
S-CSCF Assignment
S-CSCF
HSS
Register
I-CSCF
Register
P-CSCF
Register
U
E
Page 31
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.
Page 32
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
P-CSCF
Service name
Capability ID
emergency
call
SIP extending
function 1
SIP extending
function 2
S-CSCF1
Capability 3,4,5
I-CSCF
User1
Subscribe info of user1:

Mandatory Capability 1,2,3,4
Optional Capability 5 6
S-CSCF3
Capability 1,2,3
HSS
S-CSCF2
Capability
1,2,3,4,5
Page 33
Contents
2. IMS Registration and Related Procedures
2.1 Procedures of Local P-CSCF Discovery
2.2 Procedures of S-CSCF Assignment
2.3 Registration Procedures
Page 34
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 users 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.
Page 35
Initial Register in Home or Visited Network

HSS
)
(5 enti
th n
Au atio t
c e
s
Home
network
(3)
S-CSCF assignment
(1)
P-CSCF
(2)
Register
Register
(8
)
(7
)
I-CSCF
(4
)
(6
)
401
401
401
Home
network
HSS
)
(5 enti
th n
Au atio t
c se
Visit
network
S-CSCF
(3)
S-CSCF assignment
(1)
P-CSCF
(2)
Register
Register
(8
)
(7
)
401
I-CSCF
401
(4)
(6
)
401
S-CSCF
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.
Page 37
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
Block Profile
setting
iFC1
Registration
authority
iFC2
Roaming
authority
iFC3
iFC n
Which AS will handle the 3rd

party register?
Which AS(s) will handle the
caller side services?
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.
Page 39
Registration Procedure
1 Initial register message
2 2nd register message
S-CSCF-A
(15)
(6)
User profile
Authentication
data
HSS-A
(4)
Assign S-CSCF
HSS-A
(5)
(14)
(13)
Register
Register
Assign S-CSCF
(7
)
I-CSCF-A
(12)
(3)
Register
Register
(17)
(8
)
200 OK
401
P-CSCF-A
P-CSCF-A
(2)
(1)
Register
(9
)
(11)
(10)
DNS query
DNS
401
U
E
(16)
200 OK
401
I-CSCF-A
S-CSCF-A
DNS query
Register
(18)
200 OK
U
E
Page 40
Registration Signaling Flow

Home Network
Caller UE
Initiate
register
P-CSCF
1.REGISTER
DNS
I-CSCF
2.DNS Query
3.DNS Query
Resp
4. REGISTER
Send the
authentication
parameters to UE
12. 401
Unauthorized
13.REGISTER
S-CSCF
HSS
S-CSCF
assignment
5. Diameter: UAR
6. Diameter: UAA
7.REGISTER
10. 401
Unauthorized
8.Diameter: MAR
9.Diameter: MAA
11. 401 Unauthorized

14.DNS Query
S-CSCF
assignment
15.DNS Query
Resp
16. REGISTER
17. Diameter: UAR

18. Diameter: UAA
Authentication
response
19.REGISTER
24. 200 OK
Download the
authentication
sets
23. 200 OK
22. 200 OK
20.Diameter: SAR
21.Diameter: SAA
AS
25.REGISTER
26. 200 OK
Download
service
profile iFC
etc..)
3rd party
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
Page 42
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
PCSCF
-> Querying the DNS to obtain the I-CSCF IP address

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
Page 43
Stored Information
Node
Before
Registration
During Registration
After Registration
IMPI, IMPU,
Credentials
Home Domain
Proxy Name/Address
Same as before registration
IMPI,IMPU, Credentials
Home Domain
Proxy Name/Address
P CSCF
(in Home or
Visited network)
DNS address
I-CSCF address/name
UE Address IMPI IMPU
Final Network Entry point

UE Address, IMPI IMPU
S-CSCF address
I-CSCF
(in Home
network)
HSS address
S-CSCF address/name
(temporary)
No State Information
HSS address
HSS Address/name
User profile
P-CSCF address/name
P-CSCF Network ID
UE IP Address, IMPI IMPU
May have session state

Information Same as during
registration
Service profile
P-CSCF address
User Service Profile
P CSCF Network ID
S-CSCF address/name
UE
S-CSCF
(in Home
network)
HSS
Page 44
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
Page 45
User Initiate the Deregister
cause
Switch off the UE

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

The user is a owing subscriber
Page 47
Questions
What are the IMS NEs that perform registration on IMS users?
What are the steps of IMS user registration?
Page 48
Contents
1.
SIP Overview
2.
3.
Page 49
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 callees home network .
AS
Implement service for both caller and callee side.
DNS/
ENUM
DNS: Reply the ICSCF IP address for S-CSCF query
HSS
Only used in the callee part. I-CSCF locate the SCSCF by query the
HSS
ENUM: Map the TEL format IMPU to SIPURI format
Page 50
Procedures Involved in a Session

Procedures involved in the
session
Session
establishment
procedure
Session
release
procedure
Media
negotiation
procedure
Resource
reservation
procedure
Application
service
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.
Page 51
Internal Phases of the IMS Session Procedure

Establishment of sessions include: Origination procedures, SS
procedures and Termination procedures
MO procedure
SS procedure
From the caller UE to
From the S-CSCF/AS
MT procedure
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
Page 52
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
MT
S
S
3.request
Caller part
S-CSCF
Callee part
4.request
I-CSCF
S-CSCF
5.request
2.request
DNS/ENU
M
HSS
P-CSCF
P-CSCF
6.request
1.request
media
Signalin
g
Media
Page 53
DNS&ENUM
ENUM
function
DNS function
+8675528780808
huawei.com
Calling party
Called party
S-CSCF
I-CSCF
PCSCF
HSS
P-CSCF
ENU
M
DNS/ENUM
189.17.2.123
S-CSCF
Media
hwguy@huawei.com
Page 54
Basic Session Establishment

Procedure Between IMS Users
Calling party
S-CSCF-A
Called party
I-CSCF-B
Invite
183
HSS-A
183
Invite
HSS-B
Invite
I-CSCF-A
S-CSCF-B
183
DNS/ENUM
Invite
183
P-CSCF-A
P-CSCF-B
Invite
Invite
183
183
media
Page 55
Processing of Service Triggering

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

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

IMS called party
PSTN
calling party
I-CSCF-A
HSS-A
Invite
Invite
S-CSCF-A
PSTN/PLMN
MGCF
IAM
Invite
P-CSCF-A
Invite
UMG
Page 58
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.
Page 59
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.
Page 60
Session Signaling Procedure of IMS Users

UE1/PCSCF1
SCSCF1/AS1
INVITE
SCSCF2/AS2
ICSCF2
INVITE
INVITE
183
183
183
PRACK
PRACK
200 OK(PRACK)
UPDATE
PCSCF2/UE2
INVITE
183
PRACK
200 OK(PRACK)
200 OK(PRACK)
UPDATE
UPDATE
PRACK
PRACK
200 OK
(UPDATE)
180
Ringing
PRACK
200 OK
200 OK
200 OK
200 OK
(UPDATE)
180 Ringing
200 OK
(INVITE)
ACK
200 OK
(UPDATE)
180 Ringing
200 OK
(INVITE)
ACK
180 Ringing
200 OK
(INVITE)
The session is
established.
200 OK
(INVITE)
ACK
The IMS user

performs
media
negotiation to
determine the
media IP
address,
media stream
type, and
coding/decodi
ng methods.
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.
OK, lets exchange

the information
We have to use the

same media type
and codec
Support
:
Support:
Audio
G.729
Audio
G.729
H.263
Page 62
Media Characteristics Negotiation

Media
Characteristics
A SIP Message INVITE
are described in
the SDP in the
SIP message
Support codec
types
Page 63
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)
Page 64
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?
Page 65
Summary
In this course, the following topics are covered:
IMS protocol
IMS registration procedure
IMS session procedure
Page 66
Thanks
www.huawei.com

IMS Basic Signaling Procedure (SIP&amp;IMS Procedures)

Uploaded by

Document Information

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&amp;IMS Procedures)

Uploaded by

Copyright:

Available Formats

IMS Basic Signaling

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

IMS Solution Manual Basic Signaling Procedure Volume

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

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.

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

IMS Registration and Related Procedures

IMS Session and Related Procedures

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

1.1 SIP Overview

1.2 SIP Message Structure

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

Origination and Development of SIP

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

SIP: Session Initiation Protocol

SIP is an IETF protocol for multi-media sessions

Setting up, controlling and tearing down sessions

Sessions including text, video, voice, etc.

SIP is one of the Internet protocol

Text based like HTTP

Widely used for successful Internet

Can be based on UDP/TCP/SCTP, most of the case now use UDP

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

Session Related Protocols

Registration, user locating, and routing

Session establishment, modification, and release

Media transport protocol

Transmission of voice and video

SIP signaling protocol

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

Simplified SIP Network Architecture

Media Stream (RTP)

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

Logical Entities of SIP

SIP use client/server architecture

User Agents (UA)

Register: Maintains the location of SIP

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

1.1 SIP Overview

1.2 SIP Message Structure

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

SIP Message Structure

The SIP consists of three parts:

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

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

SIP Message Type -- Request

ACK: the response of INVITE

SUBSCRIBE : to subscribe to a notify event

CANCEL: to cancel a session

NOTIFY: to send a notify event

BYE: to terminate a session

UPDATE: to modify the session attributes at

REGISTER: to register in a server

the establishment stage of a call

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

SIP Message Type -- Response

SIP response type:

1xx: Provisional -- request received, continuing to process the

2xx: Success -- the action was successfully received, understood, and

3xx: Redirection -- further action needs to be taken in order to

4xx: Client Error -- the request contains bad syntax or cannot be

IMS Basic Signaling Procedure (SIP&IMS Procedures)

IMS Basic Signaling Procedure (SIP&IMS Procedures)