Академический Документы
Профессиональный Документы
Культура Документы
(IMS)
BT
Mobility Research Unit, pp B28/2B, Adastral Park, Ipswich IP5 3RE, UK.
viraj.abhayawardhana@bt.com
Network Performance Group, pp MLB4/1A, Adastral Park, Ipswich IP 3RE, UK.
ruth.babbage@bt.com
I. I NTRODUCTION
The IP multimedia Subsystem (IMS) was first defined by
the 3rd Generation Partnership Project (3GPP) in Release 5 as
the core network architecture for the 3G cellular system. Its
an open-systems architecture that supports a range of IP-based
services over both PS and CS networks. It enables peer-to-peer
real time services, such as voice and video. It has a common
session control layer based on Session Initiation Protocol
(SIP) [1], which gives the ability to manage parallel user
services and mix different multimedia in a single or parallel
sessions. It is also access independent, hence subsequent
releases of the 3GPP standards have seen it opened to Wireless
LANs (R6) and Fixed networks (R7). This will pave the way
for Fixed-Mobile Convergence (FMC).
British Telecom (BT) has identified the importance of IMS
and has taken the radical step of embarking on a 10-year plan
worth 10 billion to completely overhaul the core network to
one based on the IMS model. Having modified the IMS model
to particularly suit BTs requirements, the BT model is called
the 21st Century Network (21CN).
At the heart of the IMS model is the Home Subscriber
Server (HSS), the master database which holds both the
783
UE
P-CSCF
REGISTER
PS
REGISTER
SIP AS
HSS
S-CSCF
UAR
UAA
Ph
IMS
Challenge
Application Server
Layer
I-CSCF
Sh
HSS
Session Control
Layer
ISC
ISC
Cx
S-CSCF Selection
REGISTER
MAR
MAA
Cx
UNAUTHORIZED
I-CSCF
P -CSCF
Mw
UNAUTHORIZED
UNAUTHORIZED
S -CSCF
Mw
REGISTER
REGISTER
UAR
UAA
Fig. 1.
REGISTER
Response
Transport
Layer
DSL,802.11,
GPRS, WCDMA..
SIP
Diameter
Authentication
SAR
S-CSCF Reg. &
User Profile Download
SAA
Fig. 2.
UE 1 &
P-CSCF1
S-CSCF 1
I-CSCF 2
HSS
UE 2 &
P-CSCF2
S-CSCF 2
INVITE
TRYING
Evaluation of IFC
INVITE
TRYING
LIR
LIA
INVITE
TRYING
Evaluation of IFC
Negotiate
INVITE
TRYING
Select Common SDP
SESSION IN
PROGRESS
SESSION IN
PROGRESS
SESSION IN
PROGRESS
SESSION IN
PROGRESS
PRACK
PRACK
OK
OK
Acknowledge
UPDATE
UPDATE
OK
OK
RINGING
RINGING
Alert
Reservation Conf.
PRACK
OK
PRACK
OK
Finalise
OK
OK
OK
OK (on INVITE)
OK (on INVITE)
Alert user
Accept session
ACK
ACK
Media Flow
Fig. 3.
IMS Session setup call flows (both users in the same network)
interaction with the HSS during negotiation to locate the SCSCF address assigned to the UE at the terminating end. A SIP
message carries an Session Description Protocol (SDP) part
in the body of the message that describes the media available
at either end. The first INVITE, SESSION IN PROGRESS
and PRACK messages are used by the two UEs to negotiate the
media that will be used to establish the session. Please refer [6]
for more details. Please note that some intermediate flows are
not shown after the SESSION IN PROGRESS message in
figure 3 and are denoted by dashed arrows. They should flow
similar to the detailed ones shown on top of the figure, but
without any HSS interactions.
Presence is one of the most important services that could
be provided by the IMS and could easily be reused by other
services. The PS holds presence information of presentities,
which watchers subscribe to. Any changes of presence state
784
UE
S-CSCF 1
I-CSCF 2
HSS
S-CSCF 2
Description
Perc. of users registered at BH, a
Perc. of users that are permanently registered, b
Perc. of users that register everyday, c
No. of times a user registers per day, d
Re-registrations per registered user per hour, e
Perc. of registrations in BH, f
Originating sessions/reg. user in BH, g
Overall terminating session/user in BH, h
Perc. sessions terminated while user not registered, i
Perc. of UE-initiated de-registrations, j
Perc. of NW-initiated de-registrations, k
AS contacts/user in BH, l
AS subs. to notification/user in BH, m
Perc. of users that use presence, n
No. of presence watchers per user, o
No. of new watcher subscriptions/reg. user in BH, p
No. of presence status changes/reg. user in BH, q
PS
SUBSCRIBE
Evaluation of IFC
Subscribe
SUBSCRIBE
LIR
LIA
SUBSCRIBE
Evaluation of IFC
Notify
SUBSCRIBE
OK
NOTIFY
OK
Fig. 4.
OK
OK
OK
NOTIFY
OK
TABLE I
A SSUMPTIONS MADE FOR THE IMS TRAFFIC MODEL
Amount
80%
60%
20%
2
1
25%
1.5
1.5
10%
95%
5%
0.125
0.0625
20%
10
0.25
1
2M subs
56
444
750
83
53
3
69
35
11
11
7222
4M subs
111
889
1500
167
106
6
139
69
22
22
14444
22
44
TABLE II
M AJOR TRAFFIC F LOWS
785
Use case
Cx
Sh
Px
SIP Message
INVITE (no authentication)
INVITE (digest authentication)
SESSION INPROGRESS
PRACK
OK
RINGING
ACK
BYE
REGISTER (no authentication)
REGISTER (digest authentication)
UNAUTHORIZED
SUBSCRIBE (digest authentication)
NOTIFY
Registration
Re-registration
Session terminationuser registered
Session terminationuser unregistered
De-registrationUE initiated
De-registrationNW ini.(timeout)
De-registrationadmin initiated
User profile download
Subscribe to
notification
New watcher subs.
2
1
1
1
1
1
1
1
1
size (bytes)
930
1280
910
450
990
450
630
510
490
810
680
900
550
TABLE V
SIP MESSAGE SIZES
1
1
TABLE III
Interface
Cx
Cx
Cx
Cx
Sh
Sh
Px
Message type/sec in BH
UAR/UAA
MAR/MAA
SAR/SAA
LIR/LIA
UDR/UDA
SNR/SNA
LIR/LIA
2M subs
600
60
190
830
70
40
20
4M subs
1200
110
390
1700
140
70
40
TABLE IV
M ESSAGES PER INTERFACE
B. Latency calculations
The second part of the model calculates the latency of the
procedures. IMS session setup is of particular interest since it
is critical in terms of user experience (i.e. until the RINGING
message). Both users were assumed to be roaming to find the
scenario that would have the longest possible call flow for
session set up. Please refer to [6] for the complete call flows.
The figures presented in section II do not assume any roaming
scenarios.
Table V lists the typical SIP message sizes taken from a
lightly loaded test network at the UE to P-CSCF interface.
Processing times at each node for each message type were also
measured. It should be noted that due to the light load, these
processing times are a best case. Since the test measurements
did not cover all the message types that appear in the three
call flows being considered, the processing times used for
the latency calculations are merely approximate best guesses
based on the available measurements. It was noted that the
processing times for each message at each node were much
greater than the transmission times (hop latencies). Note that
all links were assumed to be wired. Hence, it was decided to
assign a hop latency based on link type, rather than precisely
calculating it based on message lengths and transmission link
speeds.
Each link was assigned to be either a LAN or a WAN,
786
Procedure
Cx Registration
Cx Call setup
Px subs. to watcher
Total hop
(s)
0.164
0.434
0.122
Total destination
(s)
0.435
0.762
0.255
Overall total
(s)
0.599
1.196
0.377
TABLE VI
L ATENCY FOR EACH PROCEDURE (HSS LATENCY IS 50 MS )
Procedure
Cx Registration
Cx Call setup
Px subs. to watcher
Total hop
(s)
0.164
0.434
0.122
Total destination
(s)
0.635
0.812
0.305
Overall total
(s)
0.799
1.246
0.427
TABLE VII
L ATENCY FOR EACH PROCEDURE (HSS LATENCY IS 100 MS )
R EFERENCES
[1] J. Rosenberg et al., SIP: Session Initiation Protocol, Tech. Rep. RFC
3261, IETF, June 2002.
[2] P. Calhoun et al., Diameter base protocol, Tech. Rep. RFC 3588, IETF,
September 2003.
[3] H. Schulzrinne and J. Rosenberg, The session initiation protocol:
Internet-centric signaling, IEEE Communication Magazine, pp. 134
141, October 2000.
[4] S. Faccin, P. Lalwany, and B. Patil, IP multimedia services: analysis of
Mobile IP and SIP interactions in 3G networks, IEEE Communication
Magazine, pp. 113120, January 2004.
[5] K. Wong and V. Varma, Supporting real-time IP multimedia services in
UMTS, IEEE Communication Magazine, pp. 134141, October 2000.
[6] 3GPP TS 24.228 v5.13.0 (2005-06), Signaling flows for the IP Multimedia call control based on SIP and SDP; Stage 3 (Release 5), June
2005.
[7] 3GPP TS 24.229 v6.9.0 (2005-12), IP Multimedia call control protocol
based on SIP and SDP; Stage 3 (Release 6), December 2005.
[8] 3GPP TS 29.228 v6.9.0 (2005-12), IP Multimedia subsystem Cx and
Dx interfaces; Signaling flows and message contents (Release 6),
December 2005.
[9] 3GPP TS 24.141 v6.5.0 (2005-09), Presence service using IP Multimedia core network subsystem; Stage3 (Release 6), September 2005.
[10] 3GPP TS 29.328 v6.8.0 (2005-12), IP Multimedia subsystem Sh
interface; Signalling flows and message contents (Release 6), September
2005.
[11] H. Hannu, Signaling compression (SigComp) requirements and assumptions, Tech. Rep. RFC 3322, IETF, January 2003.
[12] Nortel Networks, A comparison between GERAN packet-switched call
setup using SIP and GSM circuit-switched call setup using RIL3-CC,
RIL3-MM, RIL3-RR and DTAP, Rev. 0.4, Tech. Rep. GP-000508,
3GPP TSG GERAN 2, November 2000.
787