end-to-end user-centric session with qos continuity€¦ · end-to-end user-centric session with...
Post on 21-Apr-2018
239 Views
Preview:
TRANSCRIPT
End-to-end User-centric session with QoS continuity
Speaker: Yijun WUNoëmie SIMONI
TELECOM ParisTechComputer of Science and Networks Department © ETSI 2009. All rights reserved
STF 360
STQ Workshop - 1 & 2 July 2009
Index
� Requirements of user-centric session� Specification---User case and scenarios� QoS control and management in ETSI and 3GPP (Sequen ce
diagrams)� Proposition: QoS continuity
2
� Accessibility of the service using any terminal according the user preference
� User-centric session for the user’s workflow (One
User centric QoS requirements
3
user’s workflow (One session for different services)
� Dynamic selection of connectivity.
� Personalization of the service � Composition of service� User’s preferences
Specification---User case
Home Network Environment
1
2
Horizontal handover S
ervice brokerS
CIM
IMS
CN
1
AN 1
AN 2
One session
8:30h
AS22
AS13
SP1
SP2
CNG
AS12AS33
AS11 AS31
4
Office
Service layer
User centric end-to-end session (QoS continuity acc ording to user’s preference)
Terminal mobilityApplication Server(Service mobility)
Service orchestration
User mobility
CN
3
Heterogeneous network(access and core network )
Horizontal handover
(within same access network )
Media dataAS: Application ServerAN: Access NetworkCN: Core NetworkSP: Service provider
Vertical handover(between heterogeneous accesses)
AN 2
One session
11h
AS22
Service broker
SC
IM
IMS
CN
2
AS11 AS31
AS23
AN 3
CPE
Scenario 1 (User mobility)
Initiator: TerminalDecider: Access networkExecutor: Access network
5
PDP sessionSIPDiameterOthers
Scenario 2(Service mobility/User mobility/ vertical handover)
Gm
IMS
Core
S-CSCF
I-CSCF
Rxe2 Gq’
SP1
AS33
SP2
AS11 AS31
AS22
S-CSCFI-CSCF
ISC
IMS
Core
UPSF
CxCx
UPSF
P-CSCF
AS12ISC
Initiator: ASDecider: NetworkExecutor: Network
6
Gm
GGSN
AN
e1
SGSN
BTSUm
Iu-ps
RNC
Iub
NASSe4
CPE
E3(CW
MP)
a1/a
3
Access network IP Backbone
C-BGF I-BGFIP-edgeABG
AN
e1
e1
Re
Ia(H
.248
)
Ia(H
.248)PDP context
QoS tunnel QoS tunnelQoS tunnel
RACS
Gx
PCRF
SIPDiameterOthersPDP session/Connectivity session
Scenario 3(Terminal mobility/Horizontal handover)
Initiator: Access NetworkDecider: Access NetworkExecutor: Access Network
7
PDP sessionSIPDiameterOthers
NGN QoS control (ETSI TISPAN/3GPP)
NASS
AF(e.g. P-CSCF)
A-RACF SPDF
1AuthenticationAutorisationConfiguration
2GmService Request(e.g. SIP INVITE)
3
Resource and policy Request
RACS4
ISC
Gq+e4
Re Ia
8
UE BGF AS
Resource and policy Request
5Policy and resource enforcement
UE
AF(e.g. P-CSCF)
PCRF
GGSN(PCEF) AS
2
3
5
GxPolicy Request
RxPolicy Request
1 GmService Request(e.g. SIP INVITE)
AuthenticationAuthorisationConfiguration
ETSI TISPAN
3GPP
4
Policy and resource Enforcement
SIPDiameterOthers
ISC
IP-Edge
Re Ia
AAA Server
ETSI QoS Control: NASS authentification 1
UE NACFAMF UAAF CLF RACS
1. PPP setup
2. Access request
3. Access response
4. Configuration
request
5. Network location info
6. IP address and other
configuration info7. PPP response
8. DHCP INFORM
and Option 1209 Network location
P-CSCF I-CSCF UPSF S-CSCF
NASS
9
and Option 9. Network location
info request
10. Network location info
11. Network location
info reponse
12. DHCP response (P-
CSCF address)
13. Register
14. CLF Query (IP Address)
15. CLF Response (Location info)16. Register (P-
Access Network-info)17. UAR
18. UAA
19. Register (P-Access Network-info)
20. MAR
21. MAA
(Line-ID)22. SAR
23. SAA
24. OK
S-CSCF selection
User profile check
Compare line ID
SIPDiameterOthers
ETSI QoS Control : Service request, resource reserva tion, policy control
UE IP Edge SPDF P-CSCF S-CSCF ASABG UPFS
8. Invite
9. 183
progress
C/I-BGF NASS A-RACS
1. SIP Invite
2.Invite
NASS Authentification & Network attachment
6.SAR
User profile data
7. SAA
RACS
NASS User profile
information sent over the
I-CSCF
3. LIR
4. LIA 5. Invite
Get the informations of
the connection
downlink from media
description in the SDP
52
10
SIPDiameterOthers
Determines whether the
request information received
from the application function is
consistent with the policy rules
defined in the SPDF.
progress10. 183
progress
Define service
information
11. Diameter
AAR
14. Diameter
AAA
Media (RTP)
Resource admission control
Access profile
push
12.Admisssion
Request
Request resource
Cnf13. Response
admission control
e4 interface comprises
QoS profile information
and initial gate setting
information.
18. Open gate
Open gate
17. Diameter
AAR
15. Offer
response
20. Diameter
AAA
16. Response
conf (opt SDP)
21. 200 OK
19. Open gate
response
Bgf_reqBgf_Cnf
3GPP QoS control 52
UE GGSN(PCEF) PCRF P-CSCF S-CSCF AS12SGSN
3. Invite
(SDP)
4. Invite
HSS
7. Invite
1. GMM
attachment2. Active PDP
context Invite:
Session transfer ID
<destination address>
Via: <UE IP>
Route: <P-CSCF address>
...
SDP: <Caller supported codec list>Get the informations of the
connection downlink from
media description in the
SDP
I-CSCF
5. LIR
6. LIA
11
Check service information. Compare
with the policy rules of operations
and authorize the QoS resource and
give authorization token to P-CSCF
19. CCA
11. 183
progress12. 183
progressDefine service information
13. Diameter AAR: Request the authorization token and service information
14. Diameter
AAA
20. Active PDP context
response21. Response
Media (RTP)
8. SAR(Service
assignment req)
9. SAA10. Invite
The capabilities of the AS
returned along the signalling path, in
a 183 (Session Progress) provisional
response.
Mapping SDP QoS parameters to
UMTS QoS parameters
16. Active PDP context request
(contain binding infos)17. Create PDP context request
(contains binding infos)18. CCR
Mapping authorized IP QoS parameters to
authed UMTS QoS parameters Compare
UMTS QoS in PDP context and the authed
parameters
15. Offer
response
SIPDiameterOthers
Proposition: QoS continuity
� Five dimensions� Architecture : 4 layers (User, Terminal, access/cor e network and
service layer), 3 elements (Node, Link, Network)� Organization : Initial/decision/execution� Protocol : session based, session binding, cross la yers (service,
transport, user), interface converged,� Information: Infoware (operator’s database +) and I nfosphere (User
12
� Information: Infoware (operator’s database +) and I nfosphere (User profile), QoS model (4 criteria et 3 values)
� Function: Dynamic Management and control of QoS
Core Core
Service networkService network
End-to-end U
ser centric Session
End-to-End User centric session QoS signaling
QoS signalling
13
Access Network 1
Seamless Userware
Access Network 2
Access Network 3
Core Network Network
InfosphereAmbientGrid
end User centric S
ession
VPSN: Service and network integration
VPSN VSC
X
QoS signalling
14
Sub-Networks
X
VPSN: Virtual Private Service Network
VSC: Virtuelle Service Community
QoS signaling trigger events
� State Change Events� QoS in contract� QoS out contract� QoS Parameters Modification
� QoS Going Down In contract
15
� Service Initiated Events
contract
ModificationQoS going-
down
Out contract
QoS negociation
Service
Demanded QoSService
Offered QoS
Negociation
Desirable QoS
Request
Capable QoS
Offer
16
User Provider
Perceived QoS
ServiceAvailabilityReliabilityDelayCapacity
Core networkFour criteria
AccessNetworkFour •criteria Terminal
•Four criteria
Contracted QoS
Provided QoS
ServiceAvailability Reliability DelayCapacity
Core networkFour criteria
AccessnetworkFour criteria Terminal
Four criteria
Infosphere
UPSF+/HSS+
Procedure of flow 1: User initial
Information update
1
Gx+
Cx UPSF
e4
Binding information User data
Binding informationAuthorized QoS
NASS
InitiatorDeciderExecutor
S-CSCF
NegotiationNegotiation
2
3 8
User data
AS
AF
AS
Infosphere
AS
P-CSCF
In/Out contract
17
UserRe
e4Binding informationAuthorized QoS
Resource reservation
Authorized IP level QoS
Binding information
Requested IP level QoS
Compare and to enforce
6
Request and binding information
access profile
9
User data
4
57
User data
SIPDiameterOthers
Network node
RACSInfosphere
Service Session
PDP Context 1
UE 1
Media component informationGCID, GGSN address, Bearer Type 1, etcSession and UE informationSession IDEquipment ID,QoS & Charging conditions
Media component information
UEinformationEquipment ID,Session IDI/O Information (Bearer address)User informationUser IDQoS & Charging preference
Service level informationSCID,Service ID,SLA, etcSession level informationSession IDQoS&
UE 2
Session binding
18
IMS Session
PDP Context 2
Session level information
ICID, Session ID,etc Service, Media component information ans UE informa tionService ID, SDP data, Equipment ID, etc
Media component informationGCID, GGSN address, Bearer Type 2, etc.Session and UE informationSession IDEquipment ID,QoS & Charging conditions
QoS&Charging conditions
UEinformationEquipment ID,Session IDI/O Information(Bearer address)User informationUser IDQoS & Charging preference
End-to-End User-centric Session Binding
Conclusion
� We identify the scenarios representing and concerni ng to the NGN context (Heterogeneity and mobility) through a user case.
� We study the QoS aspects in an E2E user-centric session from user’s view.
19
session from user’s view.� We isolate and identify the components who play the
important roles for interworking between service an d user in order to QoS continuity
� We propose the QoS signalling in the service layer (VPSN) and cross-layered session binding for the Qo S continuity.
End-to-End User-centric session with QoS continuity
� We identify the scenarios representing and concerni ng to the NGN context (Heterogeneity and mobility) throug h a user case. We study the QoS aspects in an E2E user-centr ic session from user’s view. We isolate and identify t he components who play the important roles for interwo rking between service and user in order to QoS continuity .
20
between service and user in order to QoS continuity .� Key words: User-centric session, QoS continuity, IM S (SIP,
Diameter)� Speaker: Yijun WU
top related