ETSI TS 124 228-2006 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) Signalling flows for the IP multimedia call control bas.pdf

1、 ETSI TS 124 228 V5.15.0 (2006-09)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);Signalling flows for the IP multimedia call controlbased on Session Initiation Protocol (SIP) andSession Description Protocol (SDP);Stage

2、3(3GPP TS 24.228 version 5.15.0 Release 5)GLOBAL SYSTEM FOR MOBILE COMMUNICATIONSRETSI ETSI TS 124 228 V5.15.0 (2006-09) 1 3GPP TS 24.228 version 5.15.0 Release 5 Reference RTS/TSGC-0124228v5f0 Keywords GSM, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 4

3、2 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in mor

4、e than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific ne

5、twork drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the

6、 present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.

7、European Telecommunications Standards Institute 2006. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trad

8、e Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 124 228 V5.15.0 (2006-09) 2 3GPP TS 24.228 version 5.15.0 Release 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ET

9、SI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is availa

10、ble from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced

11、 in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specificatio

12、ns or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp . ETSI ETSI

13、 TS 124 228 V5.15.0 (2006-09) 3 3GPP TS 24.228 version 5.15.0 Release 5 Contents Intellectual Property Rights2 Foreword.2 Foreword.8 1 Scope 9 2 References 9 3 Definitions and abbreviations.10 3.1 Definitions10 3.2 Abbreviations .10 4 Methodology 11 4.1 Key required to interpret signalling flows11 4

14、.1.1 Key required to interpret signalling flow contents tables .11 4.1.2 Key required to interpret signalling flow figures11 4.1.2a Key required to interpret the storage information tables.11 4.1.3 Functional entities covered in example flows.12 4.2 Notation conventions12 4.2.1 Introduction.12 4.2.2

15、 User Identities.12 4.2.3 Network Entities .13 4.2.4 Configuration hiding.15 4.2.5 User Roaming Procedures 15 4.3 Document Structure16 5 Elements of signalling flows for provision of IP-connectivity network (Informative)16 5.1 Introduction 16 5.2 PDP context activation and P-CSCF discovery procedure

16、s .16 5.2.1 Introduction.16 5.2.2 DHCP procedure for P-CSCF discovery 16 5.2.3 GPRS procedure for P-CSCF discovery .18 5.3 End-to-End QoS and signalling call flows interactions19 5.3.1 Mobile Originating with Service-based Local Policy, without resource reservation protocol, only GPRS procedures19 5

17、.3.2 Mobile Termination, with Service-based Local Policy, without resource reservation protocol, only GPRS procedures22 5.3.3 Mobile originated sessions requesting the establishment of QoS preconditions and coordination with GPRS bearer level.25 5.3.4 Mobile Terminated sessions requesting the establ

18、ishment of QoS preconditions and coordination with GPRS bearer level.27 5.3.5 P-CSCF Functionalities in End-to-End QoS and Signalling Mobile Originating Interactions with service-based local policy.30 5.3.6 P-CSCF Functionalities in End-to-End QoS and Signalling Mobile Terminating Interactions with

19、service-based local policy.31 6 Signalling flows for REGISTER (non hiding) (Informative).32 6.1 Introduction 32 6.2 Registration signalling: user not registered 32 6.3 Registration signalling: reregistration - user currently registered.44 6.4 Registration signalling: mobile initiated deregistration

20、(not provided)48 6.5 UE subscription for the registration state event package48 6.6 P-CSCF subscription for the registration state event package (without I-CSCF providing configuration independence).52 6.7 Notifying of the network-initiated deregistration event .56 6.7.1 Network-initiated deregistra

21、tion event occurs in the S-CSCF 56 6.7.2 Network-initiated deregistration event occurs in the HSS 59 ETSI ETSI TS 124 228 V5.15.0 (2006-09) 4 3GPP TS 24.228 version 5.15.0 Release 5 6.7.3 Network-initiated deregistration upon UE roaming and registration to a new network - assumes that the previous r

22、egistration has not expired 62 6.8 Network initiated re-authentication64 6.9 Registration error conditions 66 6.9.1 Reregistration - failure of reregistration66 6.9.2 User not registered, user not allowed to roam / user unknown .67 6.9.3 Registration failure user authentication failure68 7 Signallin

23、g flows for session initiation (non hiding) (Informative).71 7.1 Introduction 71 7.2 Origination procedures .71 7.2.1 Introduction.71 7.2.2 MO#1a72 7.2.2.1 (MO#1a) Mobile origination, roaming (S-S#1a, MT#1a assumed) 72 7.2.2.2 Failure in termination procedure.93 7.2.2.3 Session abandoned, or resourc

24、e failure .96 7.2.3 MO#2100 7.2.3.1 (MO#2) Mobile origination, located in home network (S-S#2, MT#2 assumed) .100 7.2.3.2 Failure in termination procedure.122 7.2.3.3 Session abandoned, or resource failure .125 7.2.4 (CS-O) CS Networks origination130 7.2.4.1 CS Networks originated sessions routed to

25、wards IM CN subsystem (through MGCF) (S-S#2, MT#2 assumed).130 7.2.4.2 CS Networks originated sessions routed towards CS domain (through G-MSC) (not provided) .137 7.2.4.3 CS Networks originated sessions routed either towards IM CN subsystem or towards CS domain (not provided)137 7.2.4.4 Failure in

26、termination procedure.137 7.2.4.5 Session abandoned, or resource failure .139 7.2.5 Error handling: origination procedures (not provided) .141 7.3 S-CSCF (MGCF) to S-CSCF (MGCF) procedures142 7.3.1 Introduction.142 7.3.2 S-S#1a.142 7.3.2.1 (S-S#1a) Different network operators performing origination

27、and termination (MO#1a, MT#1a assumed) .142 7.3.2.2 Termination failure163 7.3.2.3 Origination failure.166 7.3.3 Not applicable.171 7.3.4 Not applicable.171 7.3.5 S-S#2 171 7.3.5.1 (S-S#2) Single network operator performing origination and termination (MO#2, MT#2 assumed) .171 7.3.5.2 (S-S#2) Single

28、 network operator performing origination and termination, terminating UE is busy, and not able or not willing to answer the call (MO#2, MT#2 assumed) .193 7.3.5.3 Origination failure (not provided).195 7.3.6 S-S#3 195 7.3.6.1 (S-S#3) PSTN Termination performed by home network of originator (MO#2 ass

29、umed).195 7.3.7 S-S#4 208 7.3.7.1 (S-S#4) PSTN Termination performed by different operator than origination (MO#2 assumed).208 7.4 Termination procedures224 7.4.1 Introduction.224 7.4.2 MT#1a 224 7.4.2.1 (MT#1a) Mobile termination, roaming (MO#1a, S-S#1a assumed) .224 7.4.2.2 UE-detected failure/res

30、ource failure .245 7.4.2.3 Origination failure.248 7.4.2.4 Mobile termination, roaming, terminal is out of radio coverage (MO#2, S-S#2 assumed) 253 7.4.3 MT#2 253 7.4.3.1 (MT#2) Mobile termination, located in home network (MO#2, S-S#2 assumed).253 7.4.3.2 UE-detected failure/resource failure (not pr

31、ovided)274 7.4.3.3 Origination failure (not provided).274 7.4.4 CS-T274 7.4.4.1 (CS-T) CS Networks termination (MO#2, S-S#3 assumed) .274 7.4.4.2 MGCF-detected failure/resource failure (not provided)281 ETSI ETSI TS 124 228 V5.15.0 (2006-09) 5 3GPP TS 24.228 version 5.15.0 Release 5 7.4.4.3 Originat

32、ion failure (not provided).281 7.4.5 MT#1c 281 7.4.5.1 (MT#1c) Mobile termination, roaming, without I-CSCF in home network providing configuration independence, terminating UE is busy, and not able or not willing to answer the call (MO#2, S-S#2 assumed) 281 7.4.6 MT#2a 287 7.4.6.1 (MT#2a) Mobile ter

33、mination, located in home network, terminating UE is busy, and not able or not willing to answer the call (MO#2, S-S#2 assumed)287 7.4.7 MT#1e 287 7.4.7.1 (MT#1e) Mobile termination, roaming, without I-CSCF in home network providing configuration independence, service is refused by S-CSCF when recei

34、ving INVITE request (MO#2, S-S#2 assumed) .287 7.4.8 Mobile termination, roaming, terminal is out of radio coverage (MO#2, S-S#2 assumed) 289 7.4.9 Mobile termination, unregistered subscriber 289 7.4.9.1 Introduction.289 7.4.9.2 Mobile termination, unregistered subscriber, no services related to unr

35、egistered state 289 7.4.9.3 Mobile termination, unregistered subscriber, services related to unregistered state .294 7.5 Sample multimedia signalling flows: addition of further media streams .298 7.5.1 Introduction.298 7.5.2 Sample multimedia signalling flow - addition of further media - originator

36、and terminator are both roaming and operated by different networks 298 7.5.3 Session attempt rejected by the network due to unauthorized media parameters .326 7.6 Error handling: session initiation (not provided)334 8 Signalling flows for session release (non hiding) (Informative) 334 8.1 Introducti

37、on 334 8.2 Mobile terminal initiated session release334 8.3 PSTN initiated session release (not provided) 339 8.4 Error handling: session release (not provided)339 9 Network initiated procedures (non hiding) (not provided) (Informative) 339 10 Procedures to enable enhanced multimedia services (non h

38、iding) (Informative) 339 10.1 Session hold and resume procedures339 10.1.1 Introduction.339 10.1.2 Mobile-to-mobile session hold and resume procedures339 10.1.3 Mobile-initiated hold and resume of a mobile-PSTN session.350 10.2 Initiating and destination party identification.357 10.2.1 Introduction.

39、357 10.2.2 Session originator desiring privacy in asserted identity358 10.2.3 Session originator without indication of privacy preference 359 10.2.4 Session destination desiring privacy in asserted identity361 10.2.5 Session destination without indication of privacy preference.362 10.3 Procedures fo

40、r codec and media flow negotiations 363 10.3.1 Introduction.363 10.3.2 Codec change within the existing reservation.363 10.3.3 Codec or media flow change requiring new resources and/or authorisation.363 10.3.4 Void 387 10.3.5 Error changing codec or media flows requiring new resources and/or authori

41、sation .387 10.4 Session redirection procedures.395 10.4.1 Introduction.395 10.4.2 Session redirection initiated by S-CSCF to IM CN subsystem (MO#2, MT#2 assumed) 395 10.4.3 Session redirection initiated by S-CSCF to CS-domain (S-S#2, MT#2 assumed)407 10.4.4 Session redirection initiated by S-CSCF t

42、o general endpoint (S-S#2, MT#2 assumed) .415 10.4.5 Void 422 10.4.6 Void 422 10.4.7 Session redirection initiated after bearer establishment422 10.5 Session transfer procedures 436 10.5.1 Introduction.436 10.5.2 Session Transfer initiating a new session .436 10.5.3 Session Transfer replacing an exi

43、sting session .457 10.6 IMS Message Exchange, UEs in different networks 458 ETSI ETSI TS 124 228 V5.15.0 (2006-09) 6 3GPP TS 24.228 version 5.15.0 Release 5 11 Void462 12 Void462 13 Void462 14 Void463 15 Void463 16 Signalling flows for REGISTER (hiding) (Informative)463 16.1 Introduction 463 16.2 Re

44、gistration signalling: user not registered 463 16.3 Registration signalling: reregistration user currently registered473 16.4 Registration signalling: mobile initiated deregistration478 16.5 UE subscription for the registration state event package482 16.6 P-CSCF subscription for the registration sta

45、te event package487 16.7 Notifying of the network initiated deregistration event (not provided)491 16.8 Network initiated re-authentication491 16.9 Registration error conditions 495 16.9.1 Reregistration failure of reregistration.495 17 Signalling flows for session initiation (hiding) (Informative)4

46、98 17.1 Introduction 498 17.2 Origination Procedures.498 17.2.1 Introduction.498 17.2.2 MO#1b498 17.2.2.1 (MO#1b) Mobile origination, roaming (S-S#2, MT#2 assumed)498 17.2.2.2 Failure in termination procedure.524 17.2.2.3 Session abandoned, or resource failure .528 17.3 S-CSCF (MGCF) to S-CSCF (MGCF

47、) procedures533 17.3.1 Introduction.533 17.3.2 S-S#1b 534 17.3.2.1 (S-S#1b) Different network operators performing origination and termination, with configuration hiding by both network operators (MO#2, MT#2 assumed) .534 17.3.2.2 Termination failure (not provided)564 17.3.2.3 Origination failure (n

48、ot provided).564 17.3.3 S-S#1c.564 17.3.3.1 (S-S#1c) Different network operators performing origination and termination, with configuration hiding by originating network operator (MO#2, MT#2 assumed) 564 17.3.3.2 Termination failure (not provided)590 17.3.3.3 Origination failure (not provided).590 1

49、7.3.4 S-S#1d 590 17.3.4.1 (S-S#1d) Different network operators performing origination and termination, with configuration hiding by terminating network operator (MO#2, MT#2 assumed) .590 17.3.4.2 Termination failure (not provided)613 17.3.4.3 Origination failure (not provided).614 17.3.5 Not applicable.614 17.3.6 S-S#3 614 17.3.6.1 (S-S#3) PSTN Termination performed by home network of originator (not provided)614 17.3.7 S-S#4 614 17.3.7.1 (S-S#4) PSTN Termination performed by different operator than origination (not provided) .614 17.4 Termination procedures614 17.4.1 Int