1、 ETSI TR 1Universal Mobile TelRedial solutio(3GPP TR 23.9TECHNICAL REPORT 123 903 V13.0.0 (2016elecommunications System (LTE; tion for voice-video switching.903 version 13.0.0 Release 1316-01) (UMTS); ng 13) ETSI ETSI TR 123 903 V13.0.0 (2016-01)13GPP TR 23.903 version 13.0.0 Release 13Reference RTR
2、/TSGS-0223903vd00 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 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 The present
3、 document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI.
4、In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the
5、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 present document, please send your comment to one of the following services: https:/portal.
6、etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified
7、without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of it
8、s Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 123 903 V13.0.0 (2016-01)23GPP TR 23.903 version 13.0.0 Release 13Intell
9、ectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. 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 Right
10、s (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has
11、 been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced 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 Report (TR) has been produced by ETSI 3rd G
12、eneration Partnership Project (3GPP). The present document may refer to technical specifications 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, 3
13、GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Dra
14、fting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 123 903 V13.0.0 (2016-01)33GPP TR 23.903 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal ver
15、bs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 5g33.1 Definitions 5g34 Description of idle mode redial switching between voice and video . 6g34.1 General Description 6g34.2 User initiated switching during an established call 6g34
16、.2.1 Signalling flows and procedures . 6g34.2.2 Future enhancements 8g34.2.2.1 Detection of video calling capability during a voice call 8g34.3 Fallback to voice during an established video call . 9g34.3.1 Signalling flows and procedures . 9g34.3.1.1 Fallback from UTRAN Video to UTRAN Voice call . 9
17、g34.3.1.2 Fallback from UTRAN Video to GERAN Voice call . 10g34.3.2 Future enhancements 11g34.3.2.1 RRC behaviour following degradation of the video RAB 11g34.3.2.2 Interaction with voice mail servers . 11g34.4 Fallback to voice during video call establishment 11g34.4.1 Signalling flows and procedur
18、es . 11g34.4.2 Future enhancements 13g34.4.2.1 How to detect that a voice call might be successful? 13g34.4.2.2 How to avoid video mail box problems? . 13g34.5 Automatic upgrade to video following fallback to voice . 13g35 Interaction with Supplementary Services and other 3GPP Features 14g35.1 Gener
19、al . 14g35.2 Calling Line Identity and Single Numbering Scheme 14g35.3 CAMEL based services triggered by call release and CCBS . 14g35.4 Provision of Multi-Media “Ring Back“ tones to the A party 14g36 O+M, charging and inter-operator and roaming accounting 15g36.1 Call Detail Records and statistics
20、. 15g36.2 Online charging 15g36.3 Tariffing . 15g36.4 Inter-operator accounting . 16g36.5 Roaming accounting . 16g3Annex A: List of CRs needed to other TSs 17g3A.1 General . 17g3A.2 CRs to other specifications already agreed by TSG Plenaries . 17g3A.3 Future CRs that are needed and/or are desirable
21、17g3Annex B: Change history 18g3History 19g3ETSI ETSI TR 123 903 V13.0.0 (2016-01)43GPP TR 23.903 version 13.0.0 Release 13Foreword This Technical Report has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the
22、TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for info
23、rmation; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been
24、incorporated in the document. Introduction Many 3GPP operators regard circuit switched video services as a key part of UMTS. However there is a strong desire to have an effective and user friendly method of switching between voice and video services when the user desires and/or when radio conditions
25、 change and video mode is no longer available. Following a study of alternative mechanisms, this Technical Report describes the idle mode redial mechanism which 3GPP based systems can use to enhance switching between voice and video services. ETSI ETSI TR 123 903 V13.0.0 (2016-01)53GPP TR 23.903 ver
26、sion 13.0.0 Release 131 Scope The present document describes the idle mode redial mechanism which 3GPP based systems can use to enhance switching between circuit switched voice and video services. 2 References The following documents contain provisions which, through reference in this text, constitu
27、te provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non specific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of
28、 a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 44.018: “Mobile radio interface layer 3 specifi
29、cation, Radio Resource Control Protocol“. 3 3GPP TS 48.008: “Mobile-services Switching Centre Base Station System (MSC BSS) interface; layer 3 specification“. 4 3GPP TS 25.331: “Radio Resource Control (RRC) protocol specification“. 5 3GPP TS 22.004: “General on supplementary services“. 6 3GPP TS 45.
30、008: “Radio subsystem link control“. 7 3GPP TS 24.008: “Mobile radio interface Layer 3 specification; Core network protocols; Stage 3“. 8 3GPP TS 23.009: “Handover procedures“. 9 3GPP TS 32.205: “Telecommunication management; Charging management; Charging data description for the Circuit Switched (C
31、S) domain“. 10 3GPP TS 22.082: “Call Forwarding (CF) supplementary services - Stage 1“. 11 3GPP TS 23.082: “Call Forwarding (CF) supplementary services - Stage 2“. 12 3GPP TS 23.205: “Bearer-independent CS Core Network“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of th
32、e present document, the following terms and definitions given in TR 21.905 1 and the following apply. A party: the calling party. B party: the called party. ETSI ETSI TR 123 903 V13.0.0 (2016-01)63GPP TR 23.903 version 13.0.0 Release 134 Description of idle mode redial switching between voice and vi
33、deo 4.1 General Description This “Idle-Mode Redial“ mechanism is a combination of existing Voice call and Video call standards and services. It is a “terminal-centric“ solution that requires only minimal additional support from the UTRAN, GERAN and Core Network. There are 3 main components to the so
34、lution: a) Switching between voice and video during an established call is achieved by one UE releasing the voice (or video) call and then that UE establishing a video (or voice) call with the same destination UE. b) During a video call, the radio coverage at one end may degrade such that the video
35、call cannot be maintained. In this case the video call will be released, and, the UE that initiated the video call can offer to its user an attempt to establish a voice call with the other party. c) The initial establishment of a video call may be unsuccessful, in which case the A party can automati
36、cally establish a voice call. For all these 3 cases, optimisation of the Man Machine Interface in the UE is possible and desirable. NOTE: There may be tradeoffs between speed of redial and interactions with content servers that only support video calls. In particular, the use of the term “automatic“
37、 does not prevent the UE requesting confirmation from the user. It is not the intention of this TR to specify the MMI of UEs, however, this TR does describe some MMI actions solely for the purpose of easing the description of the procedures. 4.2 User initiated switching during an established call 4.
38、2.1 Signalling flows and procedures The successful case of the “B party initiated switch to video“ for UMTS is illustrated in Figure 1. The notation “UE 1“ and “UE 2“ is used (rather than A and B party) because, if the B party (of the voice call) presses the “switch to video“ button, it then becomes
39、 the A party of the subsequent video call. ETSI ETSI TR 123 903 V13.0.0 (2016-01)73GPP TR 23.903 version 13.0.0 Release 13UE 1 4. Disconnect (cause) MSC 1 MSC 2 RNC 2 UE 2 RNC 1 UEs in Voice Call. UE 2 pushes the “change to video” button 5. Iu Rel Cmd 2. REL (cause) 5. Iu Rel Comp 5. Iu Rel Cmd 5. I
40、u Rel Comp 12. ACM 9. Call Proceeding 6. Voice and signaling connection released; idle mode procedures performed; Video call setup by UE 2 3. REL COMP 9. IAM 12. Alerting 4. Release 4. Release Complete 1. Disconnect (cause) 1 Release 1. Release Complete UEs in Video Call 8. RAB Ass Req 8. RB Setup 8
41、. RAB Ass Resp 11. Call Confirmed 10. Setup 11. RAB Ass Req 11. RAB Ass Resp 13. Connect 13. Connect Ack 13. ANM 13. Connect 13. Connect Ack 5. RRC release 5. RRC release 7. RRC setup 7. Initial DT 7. Initial UE msg 7. Setup 10. Paging 10. Paging 10. RRC setup 10. Initial DT 10. Initial UE msg 11. R
42、B Setup 12. Alerting Figure 1: B party initiated switch to video 0) The UEs are in a voice call initiated by UE 1. Following verbal dialogue between User 1 and User 2, they agree that a switch to video is likely to be successful (e.g. because both User 1 and User 2 have video capable handsets, and,
43、they both have “using 3G“ indications visible on their screens). The User of UE 2 pushes the “switch to video“ button (or uses other MMI that provides the same functionality) and UE 2 stores the CLI of UE 1 for use in step 7. NOTE 1: If UE 1 (instead of UE 2) initiated the “switch to video“, then UE
44、 1 stores the previously dialled number for use in step 7. 1) UE 2 releases the voice call. 2) MSC 2 sends a RELEASE message with the release cause. The cause value in the RELEASE message might be changed by transit networks prior to arrival at MSC 1. 3) MSC 1 sends a RELEASE COMPLETE message to MSC
45、 2. 4) MSC 1 releases the voice call with UE 1. 5) MSC 2 and MSC 1 locally release the Iu connections to RNC 2 and RNC 1 (assuming that there are no other CM connections active). RNC 2 and RNC 1 then release the RRC connections (assuming that their mobiles are not in PMM connected state). ETSI ETSI
46、TR 123 903 V13.0.0 (2016-01)83GPP TR 23.903 version 13.0.0 Release 13In order to minimise idle tasks performed by the UE, the following should be performed by Operators which preferentially camp UEs on UMTS: the BSC should include the “Cell selection indicator after release of all TCH and SDCCH“ IE
47、in the Channel Release message (see TS 44.018 2) if the release is done on a GERAN cell and the call was not started on this BSC and the local 2G and 3G cells are in different RAs. NOTE 2: The above text does mean RA. Change of LA always involves change of RA. 6) UE 2 and UE 1 camp on suitable cells
48、 and perform the required idle mode tasks. 7) UE 2 initiates RRC connection setup and sends the Setup message for the video call to MSC 2. The Called Party number is the one stored in step 0. The Setup message should carry extra information to indicate that it is the result of a redial attempt. 8) M
49、SC 2 requests the allocation of radio resources. If the GERAN does not support CS video, then the MSC 2 shall send an A interface Assignment Request message to the BSC including the Service Handover IE set to “Handover to UTRAN or cdma2000 should be performed“ and a Channel Type indicating any value acceptable to the BSC. The BSS handles the Assignment Request message as defined in TS 48.008 3. The interactions between MSC server and MGW can be minimised if the A interface circuit is not allocated. This can be achieved by setting the Channe
