IMS Registration Flow Analysis ISSUE 1.0

Register Flow
Analysis
www.huawei.com
Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.
Foreword
Before this course, the following courses should be

finished:
OZA010003 IMS Basic signaling flow
OZA020001 SIP protocol overview
OZC001301 IMS core O&M
Page2
References
3GPP TS 24228 Internet Protocol (IP) multimedia call

control protocol.
3GPP TS 24229-770 Signaling flows for the IP multimedia

call control
User manual HUAWEI IMS solution \ IMS Basic Flow \

Registration and Deregistration Flows
Page3
Objectives
Upon completion of this course, you will be able to:
Describe the register signaling flow
Explain the fields related to route function in sip header
Explain the fields related to authentication function in SIP

message and Diameter message
Finish the troubleshooting tasks for the register flow
Page4
Contents
1.
Registration Principle
2.
Signaling Analysis for Register Flow
3.
Typical Fault Analysis
Page5
Contents
1.
1.1 Registration Initiated by an IMS SIP User
1.2 Deregistration Flow
1.3 Implicit Registration
Page6
Typical signalling procedures for

Register
Local P-CSCF discovery
ServingCSCF assignment
Registration procedures
Page7
Generic Register Flow
P-CSCF discovery
Route to I-CSCF
S-CSCF assignment
Home
network
HSS
t
Au
on
ticati
n
he set
S-CSCF assignment
Register
P-CSCF
I-CSCF
Register
401
401
401
Page8
S-CSCF
P-CSCF Discovery
UMTS
P
PD
DH
CP
qu
co
xt
nte
o
ati
v
i
t
c
ure
d
e
roc
p
n
allocate IP
address of the
P-CSCF and IP
for UE
GGSN
DNS que
ry/respo
er
y
/r e
sp
on
seIP-CAN
nse
DHCP relay
DHCP server
DNS
other
access
network
s
Page9
S-CSCF Assignment
I-CSCF selects the S-CSCF according to the capabilities of

individual SCSCF
Capability set is used by
I-CSCF to select a SCSCF.
S-CSCF1
Capability 3,4,5
I-CSCF
P-CSCF
service
name
capability
ID
emergency
call
SIP
extending
function 1
Subscribe info of user1:

Mandatory Capability 1,2,3,4
Optional Capability 5 6
HSS
S-CSCF3
SIP
extending
3
function 2
S-CSCF2
Capability 1,2,3,4,5
Capability 1,2,3
Page10
Register Signaling Flow

Home Network
Caller UE
Initiate
register
P-CSCF
1.REGISTER
DNS
I-CSCF
2.DNS Query
3.DNS Query
Resp
4. REGISTER
S-CSCF
HSS
5. Diameter: UAR
6. Diameter: UAA
S-CSCF
assignment
7.REGISTER
Send the authentication

parameters to UE
12. 401
Unauthorized
13.REGISTER
Authentication
response
8.Diameter: MAR
10. 401
Unauthorized
9.Diameter: MAA
11. 401 Unauthorized
14.DNS Query
15.DNS Query
Resp
16. REGISTER
17. Diameter: UAR

18. Diameter: UAA
19.REGISTER
Register
response
24. 200 OK
Download the
authentication sets
23. 200 OK
22. 200 OK
S-CSCF
assignment
20.Diameter: SAR
Download service
profile iFC etc..)
21.Diameter: SAA
AS
25.REGISTER
26. 200 OK
The third party

register
Page11
P-CSCF functions (during registration)

Processes in the P-CSCF during the registration
Check the IMPI IMPU home network
Check the access network
Obtain the address of I-CSCF by home

network name
Handle the sip header
Forward the SIP register request to ICSCF
Page12
I-CSCF functions (during registration)
Processes in the I-CSCF during the registration
Obtain from HSS the Address of the SCSCF
Assign a SCSCF to a user performing SIP

registration
Route a SIP request received from another

network towards the SCSCF.
Page13
S-CSCF functions (during registration)

Processes in the S-CSCF during the registration
Check the trust domain and local domain of the

user
Handle the sip header
Authenticate the user
Bind the IMPU and SIP head contact
Download the subscription from HSS
Interaction with Services Platforms for the

support of Services
Page14
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)
Routing Function
Initial Network Entry point

UE Address IMPI IMPU
Final Network Entry point

UE Address, IMPI IMPU
I-CSCF
(in Home network)
HSS or SLF Address
S-CSCF address/name
P CSCF Network ID
Home Network contact Information
No State Information
S-CSCF
(home)
No state information
HSS Address/name
User profile (limited as per
network scenario)
Proxy address/name
P CSCF Network ID
UE IP Address IMPI IMPU
May have session state

Information Sam as during
registration
HSS
User Service Profile
P CSCF Network ID
S-CSCF address/name
UE
(in local network)
Page15
Contents
1.
Page16
Scenario for Deregister
User initiate the deregister
Network initiate the deregister
HSS initiate the deregister
S-CSCF initiate the deregister
Registration timer expires
Page17
User Initiate the Deregister
Switch off the UE
cause
Roaming handover
Page18
HSS Initiate the Deregister
cause
Subscription data changes
The S-CSCF that serves the user changes
Page19
S-CSCF Initiate the Deregister
cause
The S-CSCF needs to be shut down.
The user is a owing subscriber
Page20
The Registration Timer Expires
If an IMS SIP user does not initiate re-registration before the

registration timer expires, the P-CSCF and S-CSCF deregister
the user respectively and carry out third party deregistration
cause
Page21
Contents
1.
Page22
Implicit Registration
Implicit set
Public
User Identity
IMS
Subscription
Private
User Identity
Public
User Identity
Public
User Identity
Implicitly
Registered ID
Set
example for Implicit set

Sip: joe@huawei.com
IMS subscription
joe@huawei.com
Tel:+ 867552610001
Page23
Typical application for the implicit

registration
CS user call IMS user
Implicit set:
sip:joe@huawei.com
tel:+ 867552610001
Route to I-CSCF
according to the
tel No.
HSS
CS/PSTN
MGCF
I-CSCF
1. Invite tel:+ 867552610001
Implicit set download

from HSS during Regist:
sip:joe@huawei.com
tel:+ 867552610001
&
ress CF
d
d
a
sip of S-CS
y
r
2. que ddress
a
get
3.Invite tel:+ 867552610001
S-CSCF
4.
Invite sip:joe@huawei.com
Page24
Implicit Registration flow

HSS
register
MAR
REGISTER sip:191.169.1.110 SIP/2.0

From:<sip:joe@huawei.com>
To: <sip:joe@huawei.com>
200 OK
MAA
S-CSCF
REGISTER sip:191.169.1.110 SIP/2.0

From:< sip:joe@huawei.com>
To: < sip:joe@huawei.com >
P-Associated-URI
< sip:joe@huawei.com >,
<tel :+867552610001 >
S-CSCF insert
the PAssociated-URI
field into the 200
OK header
Page25
Contents
1.
2.
3.
Page26
Contents
2.

2.1 User Identity
2.2 Route Analysis
2.3 Whole Signalling Flow Analysis
Page27
User Identity
User Identity
SIP Header
Created by
From
UE
To
UE
Contact
UE
P-Associated-URI
S-CSCF
Page28
User Identity
UE construct the first REGISTER message
REGISTER sip:huawei.com SIP/2.0

From: <sip:joe@huawei.com>;tag=34bb680f
FROM shows
who initiate the
register
To identify the
users IMPU
Type of the UE
terminal
User-Agent: Huawei-VP8210/1.14.0
Contact: <sip:joe@189.1.20.12
contact identify
the IP address of
current IMPU
Page29
User Identity
UE construct the first REGISTER message
Use the Digest authentication

Contact: <sip:joe@189.1.20.12
Authorization: Digest username =
joe@huawei.com
realm = huawei.com
For Digest
authentication,
username should be
same with users IMPI
Page30
User Identity
S-CSCF construct the 200 OK message, send back the

implicit registration set
SIP/2.0 200 OK
Contact: <sip:joe@189.1.20.12>
P-Associated-URI < sip:joe@huawei.com >,<tel
867552610001>
P-Associated-URI
contains the implicit
registration IMPU
Page31
Contents
2.

2.1 User Identity
2.2 Route Analysis
Page32
Main Fields Related to Route in SIP Header
The fields in SIP header related to Route

SIP Header
Function
Created by
route
Route the Request message
UE and CSCF
via
Route the Response message
every sip elements that

the request message
passed by
path
Service-route
Used for S-CSCF to record P-
P-CSCF in the REGIST
CSCF address of the users
message
Used for UE and P-CSCF to
S-CSCF in the 200OK
record S-CSCF address of the
message
users
Page33
Route
Route filed is used to forcibly route a request through the listed

set of proxies
Construction: In register flow , sub-flow P-CSCF discovery and

S-CSCF assignment are used to find out the route information.
P obtain I-CSCF address by querying the
DNS, and put it in layer3 packet as
destination address instead of inserting it
to the route field
DNS
1.register
route:
pcscf.huawei.com
2.register
no route field
P-CSCF
Pcscf.huawei.com
After P-CSCF discovery

flow, UE obtain P-CSCF
address and put it in the
route field
3.register
I-CSCF
route:
scscf.huawei.com
S-CSCF
scscf.huawei.com
After S-CSCF assignment

flow, I-CSCF obtain S-CSCF
address and put it in the
route field
Via
The Via header field is

used to save the path
taken by the request and
identifies the location
where the response is to
be sent
REGISTER
Via: 190.1.10.2
Via: 190.1.10.1
Via: 189.1.20.1
the construction of the

via header
the proxy server must

add its address in a
new Via header field
that is put before the
3.I-CSCF insert its own

address on the top
2.P-CSCF insert its own
address on the top
1.UE insert its own
address
401/200
Via: 190.1.10.2
Via: 190.1.10.1
Via: 189.1.20.1
I-CSCF remove its own

address, and forward it to
P
P-CSCF remove its own
address, and forward it to
UE
existing Via
Page35
Path
REGISTER
Path: the SIP URI identifying

the P-CSCF
Indicate requests routed in
P insert its own

addrsss in path
field
register
this direction of the path (i.e.
P-CSCF
Pcscf.huawei.com
from the S-CSCF to the Ptreated as for the mobile-
it receives the REGISTER

message
invite
P-CSCF
invit
e
route:
pcscf.huawei.com
P-CSCF insert its own

address in path header when
S-CSCF will save this
S-CSCF
SESSION
The construction of path

header
I-CSCF
S save the value of

path field as P-CSCF
address
CSCF) are expected to be

terminating case
path:
pcscf.huawei.com
register
register
S use the address in path

field to add a new route,
and forward the message
to callees P-CSCF
address
for Huawei
the useTechnologies
of
Copyright
2006
Co., Ltd. All rights reserved.
Page36
S-CSCF
Service-route
Service-route: the SIP

URI identifying the SCSCF
Indicate requests
REGISTER
P save S addrsss by
service-route
200 OK
200 OK
I-CSCF
P-CSCF
routed via the service

CSCF to the S-CSCF)
mobile-originating case.
SESSION
invite
The construction of
service-route header
S-CSCF insert its own

address in serviceroute header during
200OK
S-CSCF
S insert its own

address in serviceroute field in 200 ok
message
route (i.e. from the Pare treated as for the
200 OK
invite
S-CSCF
P-CSCF
P use the address in

service-route field to
construct the route field,
and forward the message
directly to S-CSCF
P-CSCF will save this
address
useTechnologies
for
Copyright
2006and
Huawei
Co., Ltd. All rights reserved.
Page37
Route analysis
1.UE discovery P-CSCF
2.register
REGISTER sip:huawei.com
SIP/2.0
Route:190.1.10.1
Via: SIP/2.0/UDP
189.1.20.12:5060;branch
=z9hG
189.1.20.1
2
3. P-CSCF query I-CSCF address

4. Add items into sip header
REGISTER sip:huawei.com
SIP/2.0
Via: SIP/2.0/UDP
190.1.10.1:5060;branch=z9h
G
Via: SIP/2.0/UDP
189.1.20.12:5060;branch=z9
hG
Path: pcscf.huawei.com
pcscf.huawei.com
190.1.10.1
Route:190.1.10.3
Via: SIP/2.0/UDP
190.1.10.2:5060;branch=z9hG
Via: SIP/2.0/UDP
190.1.10.1:5060;branch=z9hG
Via: SIP/2.0/UDP
189.1.20.12:5060;branch=z9hG
from DNS
icscf.huawei.com
190.1.10.2
5.I-CSCF select S-CSCF

6.add items into sip head
7. Forward REGEIST
scscf.huawei.com
190.1.10.3
Route analysis (Cont.)

icscf.huawei.com
190.1.10.2
SIP/2.0 200 OK
Via: SIP/2.0/UDP
190.1.10.1:5060;branch=z9hG
Via: SIP/2.0/UDP
189.1.20.12:5060;branch=z9hG
Serviceroute:origscscf.huawei.com
12.200OK
189.1.20.1 13.200OK
pcscf.huawei.com
2
14.UE store service-route
190.1.10.1
header
SIP/2.0 200 OK
Via: SIP/2.0/UDP
189.1.20.12:5060;branch=z9hG
Serviceroute:orig@scscf.huawei.com
scscf.huawei.com
190.1.10.3
8.S-CSCF complete auth

9.S store the path header
10.S add items to sip header
11.Send back 200OK
SIP/2.0 200 OK
Via: SIP/2.0/UDP
190.1.10.2:5060;branch=z9hG
Via: SIP/2.0/UDP
190.1.10.1:5060;branch=z9hG
Via: SIP/2.0/UDP
189.1.20.12:5060;branch=z9hG
Serviceroute:orig@scscf.huawei.com
Contents
2.

2.1 User Identity
2.2 Route Analysis
Page40
REGISTER
S-CSCF-A
Home Network
HSS-A
I-CSCF-A
Visited Network
P-CSCF-A
contruct register message

Register IMPU/IMPI/IP
Page41
UE construct the REGISTER message

(1)
// home network
// UEs IP
// P-CSCFs IP
// IMPU
// IMPU
// UE report its own IP , P/ will bind it together with ues

IMPU
// IMPI
// UEs type ,which will be used in session

flow
Page42
REGISTER
S-CSCF-A
Home Network
HSS-A
I-CSCF-A
Forward the message (3)

Register
P-CSCF-A
Visited Network
P handling register message(2)

Page43
P handle the REGISTER message (2)
Check the access network information
According to data configuration PACN, users IP will be

checked.
If the users IP is not in the range defined in PACN , P-CSCF

will reject the users access
Page44
Query the IP address of I-CSCF
Find the users home network

DNS
according to the Request_URI
DNS then translate the home
(1)huawei.com
network to the IP address of I-
(2)190.1.10.2
CSCF
DNS then send back the I-CSCF

IP
P-CSCF then put this IP address
(3)register
P-CSCF
REGISTER sip: huawei. com
SIP/2.0
Via: SIP/2.0/UDP
189.1.20.12:5060;branch=z9hG
into destination part in layer3

IP packet instead of inserting it
into ROUTE field in application
I-CSCF
190.1.10.2
Page45
Change the SIP header
Insert the path field in SIP header
Insert the P-Charging-Vector icid-value field in SIP header
Insert the P-visited-Network-ID field in SIP header
Page46
P-CSCF forward the message (3)
// P-CSCF IP
address
// UE IP
// UE IP
// P-CSCF insert its own

// P-Visited-Network-ID usually should address
be same with the hostname of
P-CSCF
// P-CSCF generate
ICID
Page47
REGISTER
S-CSCF-A
Home Network
HSS-A
UAR
HSS feedback S-CSCF UAA
Register(7)
address or subscribers
capabilities (5)
I-CSCF-A
I-CSCF select S-CSCF (6)

I-CSCF check the trust domain(4)
Register
P-CSCF-A
Visited Network

Page48
I-CSCF handle the REGISTER message (4)
I-CSCF check the trust domain
If the message is from the trust domain, then I-CSCF

continues to process
If the message is not from the trust domain ,then I-CSCF will
reject the user s register request.
I-CSCF query the S-CSCF address
I-CSCF sends the Diameter message UAR to HSS
Page49
HSS handle the UAR/UAA message

(5)
HSS will do:
Check the roam restrict by P-Visited-Network-ID
Check the auth restrict

UAR
(user data: Visited-NetworkIdentifier :pcscf.huawei.com)
register (P-Visited-NetworkID:pcscf.huawei.com)
I-CSCF
HSS
Visited network list for
userA:
P-CSCF
pcscf.huawei.com
pcscf.china.com
userA
Page50
HSS handle the UAR/UAA message

(5)
HSS will do:
Response the UAA message to I-CSCF
If the user subscribe the certain S-CSCF , HSS will feedback

the address of S-CSCF
If the user does not subscribe the S-CSCF , HSS will feedback
the users capabilities
If the user does not subscribe the users capabilities either,

HSS will feedback Null. In this case ,I-CSCF will choose a SCSCF.
Information above will be send to I-CSCF by Diameter

message UAA
Page51
I-CSCF select the S-CSCF (6)
I-CSCF completes the S-CSCF assignment
According to the information ([ Server-Name ],[ ServerCapabilities ] ) in UAA message, I-CSCF complete the SCSCF selection
Change the Request_URI to S-CSCF address
I-CSCF will put the S-CSCF IP address into destination

part in layer3 IP packet instead of into ROUTE field.
Page52
I-CSCF forward the REGISTER to S-CSCF(7)

// request URI is changed to S-CSCF
address
Page53
REGISTER
S-CSCF-A
Authentication set (8)

HSS-A
UAR
MAR
MAA
HSS feedback S-CSCF UAA

address or subscribers
capabilities (5)
Register(7)
401(9)
I-CSCF-A
Home Network
I-CSCF select S-CSCF (6)

I-CSCF check the trust domain(4)
Register
401(10)
Visited Network
P-CSCF-A
401(11)
Page54
S-CSCF handle the REGISTER

message
S-CSCF check the trust domain
If the message is from the trust domain, then S-CSCF

continues to process
If the message is not from the trust domain ,then S-CSCF will
reject the user s register request.
Check the register status
If the user is not registered, send Diameter message MAR to

HSS to download the authentication set.
Page55
HSS handle the MAA/MAR message

(8)
HSS receives MAR message from S-CSCF
// S-CSCF hostname
// HSS hostname
// IMPI
// IMPU
// authentication type
// S-CSCF address
Page56

(8)
HSS sends MAA message to S-CSCF
// Diameter-success
// HSS hostname
// IMPI
// IMPU
// authentication set
Page57
S-CSCF generate 401 for challenge

Before S-CSCF send 401 unauthorize message
S-CSCF check the local domain (SLNID)
If the message is from local domain ,then keep the charging

info
If the message is NOT from local domain, then delete the

charging info
S-CSCF add the tag into TO field in SIP header
Insert the authentication set into 401message to

authenticate UE
Eg: WWW-Authenticate: Digest realm="ims1.huawei.com",

nonce="ODm3yAJ7/xhAqZ3TYqjYRQ==",algorithm=MD5
Page58
S-CSCF send 401 to I-CSCF,P-CSCF,UE (9)

(10)(11)
// 401 message
// S-CSCF add tag
authentication set, IK and CK

will be stored in P-CSCF . And
they will not be sent to UE
Page59
REGISTER 2nd REGISTER

message
S-CSCF
Home Network
HSS
I-CSCF-A
I-CSCF
AS
Visited Network
P-CSCF
UE sends the response

by the second REGISTER
(12)
Page60
UE generate the second

REGISTER(12)
UE according to the authentication set , works out the
Response
The response will be included in the second REGISTER

message.
// the response calculated by UE
Page61

message
Home Network
HSS
UAA
HSS feedback S-CSCF

UAR
address (14)
S-CSCF
Register (15)
I-CSCF
Register
(response)
AS
(13)
Visited Network
P-CSCF

(12)
Page62
P-CSCF/I-CSCF handle the 2nd REGISTER

message (12)(13)(14)(15)
The route for the second REGISTER message:
UE to P-CSCF: P-CSCF discorvery (12)
P-CSCF to I-CSCF : DNS translation (13)
I-CSCF to S-CSCF : S-CSCF assignment ( HSS feedback the

S-CSCF address) (14)
I-CSCF forward the REGISTER message to S-CSCF (15)
Page63
HSS report S-CSCF address by UAA

(14)
// S-CSCF address
Page64

message
Download user data (17)
HSS
Home Network
SAR/SAA
UAA
HSS feedback S-CSCF

UAR
address (14)
S-CSCF
Register (15)
200 OK (18)
I-CSCF
AS
Register
(response)
(13)
S-CSCF compare the RES with XRES (16)
200 OK (19)
Visited Network
P-CSCF

(12)
200 OK (20)
Page65
S-CSCF handle the REGISTER

message
S-CSCF compares the Response with expect response

(XRES)
UE generate RES
S-CSCF have the expect response
For the success, above two should be same
After the authentication success
S-CSCF sends Diameter message SAR to HSS to download

the subscriber data.
Page66
HSS handle the SAA/SAR message

(17)
HSS receives SAR message from S-CSCF
// S-CSCF hostname
// HSS hostname
// IMPI
// IMPU
// S-CSCF address
Page67

(17)
HSS sends SAA message to S-CSCF
// subscriber data
Page68
S-CSCF generate 200OK

Before S-CSCF send 200 OK message, S-CSCF should
Bind the IMPU and UEs IP address
Store P-CSCF address by the path field
Insert P-Associated-URI , with the other IMPUs subscribed in

HSS
Insert service-route, with its own address
Service-Route: <sip:orig@scscf.ims1.huawei.com:10020;lr;Dpt=27244;ca=c2lwOis4Njc1NTI2MTAwMDJAMTg5LjEuMjAuNjU6NDg3Mjg!>
UE will put service-route in route field in the following INVITE

message
Copyright
2006
Huawei Technologies
Ltd. All rights
reserved. Page69
When
S-CSCF
receives Co.,
INNVITE
message,
it will
use orig to
S-CSCF send 200OK to I-CSCF,P-CSCF,UE

(18)(19)(20)
// 200OK
// S-CSCF add tag
// the implicit register set

// bind the UE IP with IMPU
Page70
P-CSCF handle the 200 OK (19)
Check the local domain (LMDI)
If the S-CSCF is belong to local domain ,then keep the

charging address
If the S-CSCF is NOT belong to local domain, then delete the

charging address and use the local charging address.
Page71
Contents
1.
2.
3.
Page72
Typical case 1:
Phenomenon
When user registered to the network, CSCF rejected the

request.
the failure cause was Requestfromnontrusteddomain
1.register
1.register
P-CSCF
3.403
I-CSCF
S-CSCF
4.403
Page73
Typical case 1:
Analysis
I-CSCF reject the request.
Check the trust domain configuration on I-CSCF
It was found out that there is no configuration about the trust

domain
1.register
joy@huawei.com
1.register
4.40
3

Via: SIP/2.0/UDP pcscf.huawei.com:5060;branch=z9hG
Via: SIP/2.0/UDP joy@huawei.com:5060;branch=z9hG
P-CSCF
pcscf.huawei.com
3.403
I-CSCF Trust domain: none
Page74
Typical case 1:
Solution
During the register flow, I-CSCF will check the trust domain to
decide whether permit the user continue registering or not.
Add the following configuration on I-CSCF

ADDTDMI:TDID=1,ADDRT=DOMAINNAME,DN="huawei.com";
Page75
Typical case 2:
Phenomenon
When user registered to the network, I-CSCF send back

the 403Forbidden , the failure cause was
Roamingrestricted
HSS
1.register
1.register
P-CSCF
3.403
I-CSCF
S-CSCF
4.403
Page76
Typical case 2:
Analysis
1.I-CSCF feedback the 403, means that HSS reject the request.
2.Check the user subscription data in HSS, normal.
3.Check the Diameter message the error code from HSS is
DIAMETER_ERROR_ROAMING_NOT_ALLOWED(5004) means
there was a fault when HSS compare the users visited network
with Visited-Network-Identifier that I-CSCF sent to HSS.
Page77
Typical case 2:
Analysis
4.Check the VNTPL in HSS and P-CSCF local network ID , they were
not same
HSS compares the P-visited-network

with the visited network ID, if they a
not same, then reject the register
1.register

P-visited-network-ID: p.huawei.com
1.register
4.403
P-CSCF
Local network
ID:
p.huawei.com
3.403
HSS
I-CSCF
Page78
Visited network ID:

pcscf.huawei.com
Typical case 2:
Solution
change the parameter local network ID in P-CSCF data
configuration to the same value with the one defined in HSS
MOD PCSCF: PID=0, LNID="pcscf.huawei.com",
Page79
Summary
Register flow include two sub-flow:P-CSCF discovery and SCSCF assignment
Please trace the whole signaling for register ,and analysis the
sip header.
Page80
Thank you
www.huawei.com

IMS Registration Flow Analysis ISSUE 1.0

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

IMS Registration Flow Analysis ISSUE 1.0

Încărcat de

Drepturi de autor:

Formate disponibile

Register Flow

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

Before this course, the following courses should be

OZA010003 IMS Basic signaling flow

OZA020001 SIP protocol overview

OZC001301 IMS core O&M

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

3GPP TS 24228 Internet Protocol (IP) multimedia call

3GPP TS 24229-770 Signaling flows for the IP multimedia

User manual HUAWEI IMS solution \ IMS Basic Flow \

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

Upon completion of this course, you will be able to:

Describe the register signaling flow

Explain the fields related to route function in sip header

Explain the fields related to authentication function in SIP

Finish the troubleshooting tasks for the register flow

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

Signaling Analysis for Register Flow

Typical Fault Analysis

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

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

Typical signalling procedures for

Local P-CSCF discovery

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

Generic Register Flow

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

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

I-CSCF selects the S-CSCF according to the capabilities of

Subscribe info of user1:

Register Signaling Flow

Send the authentication

11. 401 Unauthorized

17. Diameter: UAR

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

The third party

P-CSCF functions (during registration)

Check the IMPI IMPU home network

Check the access network

Obtain the address of I-CSCF by home

Handle the sip header

Forward the SIP register request to ICSCF

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

I-CSCF functions (during registration)

Processes in the I-CSCF during the registration

Obtain from HSS the Address of the SCSCF

Assign a SCSCF to a user performing SIP

Route a SIP request received from another

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

S-CSCF functions (during registration)

Check the trust domain and local domain of the

Handle the sip header

Authenticate the user

Bind the IMPU and SIP head contact

Download the subscription from HSS

Interaction with Services Platforms for the

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

Same as before registration

Initial Network Entry point

Final Network Entry point

HSS or SLF Address

May have session state

User Service Profile

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

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