IR.92 CR1006
Transcript of IR.92 CR1006
![Page 1: IR.92 CR1006](https://reader030.fdocuments.us/reader030/viewer/2022020715/577cd73e1a28ab9e789e746e/html5/thumbnails/1.jpg)
7/27/2019 IR.92 CR1006
http://slidepdf.com/reader/full/ir92-cr1006 1/4
Page 1 of 4
34_00310[Meeting Document Number] IR.92 T12
IR.92 Supplementary Service Settingsfallback procedure
Meeting Information
Meeting Name and Number RILTE 34
Meeting Date 09 September 2013
Meeting Location San Francisco USA
Docum ent Information
Document Author Mari Melander (Telekom Deutschland GmbH)
Additional Contributors [List of contributors]
Document Creation Date 23 September 2013Document Status Approval
Security Classification Non-confidential
Document Summary
IR.92 T12 IR.92 Supplementary Service Settings fallback procedure
Version History (to be completed by editor)
Date Version Author / Comments
23.09.2013 1 Mari Melander (Telekom Deutschland GmbH)/Initial version
25.09.2013 2 Mari Melander (Telekom Deutschland GmbH)/ updated doc numbers andproposal from Ralf Keller (Ericsson)
27.9.2013 3 Mari Melander (Telekom Deutschland GmbH)/ addressing comments from MarkMcGinley (AT&T)
1.10.2013 4 Mari Melander (Telekom Deutschland GmbH)/ addressing comments from RickyKaura (Samsung)
4.10.2013 5 Mari Melander (Telekom Deutschland GmbH)/ addressing comments from IvoSedlacek (Ericsson)
4.10.2013 6 Mari Melander (Telekom Deutschland GmbH)/ addressing comments from RickyKaura (Samsung)
7.10.2013 7 Mari Melander (Telekom Deutschland GmbH)/ addressing comments from RickyKaura (Samsung), Ivo Sedlacek (Ericsson) and Nick Russel (BlackBerry)
7.10.2013 8 Mari Melander (Telekom Deutschland GmbH)/ addressing comments from RickyKaura (Samsung)
10.10.2013 9 Mari Melander (Telekom Deutschland GmbH)/ addressing comments received inRILTE 34 meeting
11.10.2013 10 Mari Melander (Telekom Deutschland GmbH)/ addressing comments from RickyKaura (Samsung)
11.10.2013 11 Mari Melander (Telekom Deutschland GmbH)/ addressing comments from Ralf Keller (Ericsson)
© GSMA © 2013. The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept anyresponsibility for, and disclaims liability for the accuracy or completeness or timeliness of the information contained i n this document. The information contained in thisdocument may be subject to change without prior notice. This document has been classified according to the GSMA Document Confidentiality Policy. GSMA meetingsare conducted in full compliance with the GSMA Antitrust Policy.
![Page 2: IR.92 CR1006](https://reader030.fdocuments.us/reader030/viewer/2022020715/577cd73e1a28ab9e789e746e/html5/thumbnails/2.jpg)
7/27/2019 IR.92 CR1006
http://slidepdf.com/reader/full/ir92-cr1006 2/4
Page 2 of 4
1
![Page 3: IR.92 CR1006](https://reader030.fdocuments.us/reader030/viewer/2022020715/577cd73e1a28ab9e789e746e/html5/thumbnails/3.jpg)
7/27/2019 IR.92 CR1006
http://slidepdf.com/reader/full/ir92-cr1006 3/4
Change Request Sheet
Document Information Document Title & Official Doc No IR.92 IMS Profile for Voice and SMS v7.0 (Current)
Document Type Non-binding Permanent Reference Document
Change Request Number and Title IR.92 T12 IR.92 Supplementary Service Settings fallback procedure
Is this a new document or a Major
or Minor Change?Major Change
Should this CR result in a major or
minor version increment?Major Version
Submitted by
(Change Request Author or Editor)Mari Melander (Telekom Deutschland GmbH)
Submitted on behalf of
(Group or Project)
[Submitted on behalf of]
Document Summary
What are the reasons for and
benefits of creating this document
or Change Request?
As currently defined, IR.92 UE configures Supplementary Services via XCAP
always. If the user is not a VoLTE user, this will fail. Therefore a fallback
mechanism is needed defining that the UE shall configure the Supplementary
Services in CS domain. As mentioned in the the LS in document 34_017
received in this meeting, such a mechanism is defined by 3GPP in Release
12 version of TS 24.623. This CR proposes to profile in IR.92, how VoLTE
UEs shall use this mechanism.
Which Sections of the document
are affected? A.4
What are the impacts on other
GSMA Official Documents for example, PRDs, White Papers,
Position Statements?
None
Are there similar or related new
documents or Change Requests
going through the approval
process?
None
Document Qual i ty Review (to be completed by reviewer)
DAG Coordinator
Date of QA
Comments
Name of Reviewer Javier Sendin
Date of Review 23 September 2013
Comments Suggested changes in Cover Sheet
![Page 4: IR.92 CR1006](https://reader030.fdocuments.us/reader030/viewer/2022020715/577cd73e1a28ab9e789e746e/html5/thumbnails/4.jpg)
7/27/2019 IR.92 CR1006
http://slidepdf.com/reader/full/ir92-cr1006 4/4
GSM Association Non-confidential
IR.92 Supplementary Service Settings fallback procedure
Page 4 of 4
A.1 IMS Voice service settings management when using CS access
The UE must use service setting management as defined in Section 2.3.2.
Note: This applies also when UE is using CS network for voice service
IfIf the network does not allow the user to use VoLTE, and the UE attempts to perform
service setting management via XCAP and the network sends back a failure code HTTP 403
(Forbidden) which fails as described in Release 12 version of 3GPP TS 24.623 subclause
5.3.1.2, becauseindicating that supplementary services configuration settings are not
allowed via XCAP for the user, , because the user supplementary services configuration
settings are not allowed via X, CAP, then until after a power off/power on or change of
USIM/ISIMSIM:
the UE shall not perform supplementary service management settings via XCAP
until after a power off/power on or change of USIM; and
the UE shall instead attempt to perform service setting management in CS
domainthe UE shall attempt to perform service setting management in CS
domain as described in Release 12 version of 3GPP TS 24.623. The UE shall
retry XCAP for service settings management after a power off/power on.
NOTE: the above description is the default behaviour, which can be overwritten with by
operator configuration.
Formatted: Bulleted + Level: 1 + Aligned a0.5" + Tab after: 0.75" + Indent at: 0.75",Tab stops: Not at 0.5"
Formatted: Bullets and Numbering