1、 ETSI TR 1Universal Mobile TelStudy on Serv(3GPP TR 22.9TECHNICAL REPORT 122 986 V13.0.0 (2016elecommunications System (ervice Specific Access Contro.986 version 13.0.0 Release 1316-01) (UMTS); rol 13) ETSI ETSI TR 122 986 V13.0.0 (2016-01)13GPP TR 22.986 version 13.0.0 Release 13Reference RTR/TSGS-
2、0122986vd00 Keywords 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 document
3、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. In case of
4、 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 document m
5、ay 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.etsi.org/P
6、eople/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 without th
7、e 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 its Members.
8、 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 122 986 V13.0.0 (2016-01)23GPP TR 22.986 version 13.0.0 Release 13Intellectual Pro
9、perty 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 Rights (IPRs);
10、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 been carr
11、ied 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 Generation
12、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, 3GPP and ET
13、SI 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 Drafting Rule
14、s (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 122 986 V13.0.0 (2016-01)33GPP TR 22.986 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs termino
15、logy 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 5g33.1 Definitions 5g33.2 Symbols 5g33.3 Abbreviations . 5g34 Use Cases . 6g35 Considerations 6g36 Candidate Requirements. 6g37 Conclusion 7g3Annex A: Change history 8g3History 9g3ETSI ETSI TR
16、 122 986 V13.0.0 (2016-01)43GPP TR 22.986 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 TSG and may change following formal TSG approval. Should
17、 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 information; 2 presented to TSG for approval; 3 or greater i
18、ndicates 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 incorporated in the document. Introduction In an emergen
19、cy situation, like Earthquake or Tsunami, degradation of quality of service may be experienced. Degradation in service availability and performance can be accepted in such situations, but mechanisms are desirable to minimize such degradation and maximize the efficiency of the remaining resources. Wh
20、en Domain Specific Access Control (DSAC) mechanism was introduced for UMTS, the original motivation was to enable PS service continuation during congestion in CS Nodes in the case of major disaster like an Earthquake or a Tsunami. In fact, the use case of DSAC in real UMTS deployment situation has b
21、een to apply access control separately on different types of services, such as voice and other packet-switched services. For example, people“s psychological behaviour is to make a voice call in emergency situations and it is not likely to change. Hence, a mechanism will be needed to separately restr
22、ict voice calls and other services. As EPS is a PS-Domain only system, DSAC access control does not apply. This SSAC TR identifies specific features useful when the network is subjected to decreased capacity and functionality. Considering the characteristics of voice and non-voice calls in EPS, requ
23、irements of the SSAC could be to restrict the voice calls and non-voice calls separately. For a normal paid service there are QoS requirements. The provider can choose to shut down the service if the requirements cannot be met. In an emergency situation the most important thing is to keep communicat
24、ion channels uninterrupted, therefore the provider should preferably allow for a best effort (degradation of) service in preference to shutting the service down. During an emergency situation there should be a possibility for the service provider also to grant services, give extended credit to subsc
25、ribers with accounts running empty. Under some circumstances (e.g. the terrorist attack in London on the 7 of July in 2005), overload access control may be invoked giving access only to authorities or a predefined set of users. It is up to national authorities to define and implement such schemes. E
26、TSI ETSI TR 122 986 V13.0.0 (2016-01)53GPP TR 22.986 version 13.0.0 Release 131 Scope This Technical Report (TR) presents the results of the Study on Service Specific Access Control (SSAC). The intent of this Study is to assess the ability of 3GPP specifications to meet requirements identified for S
27、ervices Specific Access Control. This Study considers the following aspects: - Study use cases and clarify issues in SSAC in EPS. - Describe the considerations and the problems with existing access control, which are identified in the use cases - Identify candidate requirements and aspects for provi
28、ding SSAC in EPS. 2 References The following documents contain provisions which, through reference in this text, constitute 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 ref
29、erence, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of 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
30、. 1 3GPP TR 21.905: Vocabulary for 3GPP Specifications. 2 3GPP TR 23.898: “Access Class Barring and Overload Protection (ACBOP)“ 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following apply.
31、A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. 3.2 Symbols For the purposes of the present document, the following symbols apply: 3.3 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1
32、and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. ETSI ETSI TR 122 986 V13.0.0 (2016-01)63GPP TR 22.986 version 13.0.0 Release 134 Use Cases Use case 1 Japanese operators provide Disaster Me
33、ssage Board services whenever a major disaster has happened such as an earthquake, tsunami or typhoon. This service enables the large number of subscribers to access the message board in order to post or retrieve information concerning the safety of individuals in the affected area with their mobile
34、 phones during a major disaster. The human psychological behaviour is to make a voice call in emergency situations. Thus increased voice traffic consumes too much bandwidth for accessing other services such as the Disaster Message Board and/or data services (e.g. SMS). Hence, a limiting mechanism is
35、 required to differentiate bandwidth consuming real-time services (e.g. Voice) from bandwidth-efficient data service to access to e.g. a Disaster Message Board. Use case 2 As described in the Use case 1 above, subscribers may wish to make voice calls to check on the safety of individuals and it may
36、cause congestion. Under such a situation, prioritised subscribers (e.g. governmental, military civil authorities ) and (depending on national regulation) access to emergency services should still be allowed access to EPS, while voice calls for other subscribers are restricted. 5 Considerations In UM
37、TS, Domain Specific Access Control (DSAC) has been introduced. According to Section 4.1.1 of TR23.898 x, the original motivation was to enable PS service continuation during congestion in CS nodes. Although that was the original motivation, operators have been using DSAC to restrict CS calls while p
38、ermitting PS sessions. Operators want to avoid service discontinuity in the packet data services due to the congestion in the voice calls side. Consequently, the use case of DSAC in a real deployment situation has been to apply access control separately on different types of services, such as voice
39、and other packet-switched services. The voice services will be provided by MMTeL using IMS in EPS; however the VoIP will be used in the same way as the existing CS-domain voice services (e.g. including Emergency Calls). This means customer experience per Service in EPS is not different from UMTS. It
40、 is reasonable that DSAC principles are to be applied in the PS-domain only EPS as well. However, EPS is a PS-Domain only system, so the Domain Specific way of access control cannot be applied as it is now. Hence, Service Specific Access Control (SSAC) has to be specified and introduced to EPS. 6 Ca
41、ndidate Requirements The following is the principle for the Service Specific Access Control. 1. The EPS shall provide a capability to apply independent access control for telephony services (MMTEL) and other data services, for mobile originating session requests from idle-mode. 2. The EPS shall prov
42、ide a capability to assign a service probability factor for each of MMTEL voice and MMTEL video: - assign a barring rate (percentage) commonly applicable for Access Classes 0-9; - assign a flag barring status (barred /unbarred) for each Access Class in the range 11-15. SSAC shall not apply to Access
43、 Class 10. 3. The SSAC shall be provided by the VPLMN based on operator policy without accessing the HPLMN. 4. The SSAC shall provide mechanisms to minimize service availability degradation (i.e. radio resource shortage) due to the mass simultaneous mobile originating session requests and maximize t
44、he availability of the wireless access resources for non-barred services. ETSI ETSI TR 122 986 V13.0.0 (2016-01)73GPP TR 22.986 version 13.0.0 Release 137 Conclusion This Technical Report (TR) on Study on Service Specific Access Control (SSAC) identified the requirements for SSAC and considered the
45、following aspects: - Use cases were documented and issues clarified for SSAC in EPS. - Considerations were described as well as problems with existing access control, which are identified in the use cases. - Candidate requirements and aspects were identified for providing SSAC in EPS. From this stud
46、y, it is concluded the following: - EPS is a PS-Domain only system, so the Domain Specific way of access control cannot be applied as it is now. Hence, Service Specific Access Control (SSAC) has to be specified and introduced to EPS. SSAC shall provide mechanisms to minimize service availability deg
47、radation (i.e. radio resource shortage) due to the mass simultaneous mobile originating session requests and maximize the availability of the wireless access resources for non-barred services. It is also concluded that the content of this TR be used as a basis for further work within 3GPP. ETSI ETSI
48、 TR 122 986 V13.0.0 (2016-01)83GPP TR 22.986 version 13.0.0 Release 13Annex A: Change history Change history TSG SA# SA Doc. SA1 Doc Spec CR Rev Rel Cat Subject/Comment Old New WI SP-42 SP-080786 S1-084390 22.986 - - Rel-9 - One-step-approved at SA#42 1.0.0 9.0.0 SSAC 2011-03 - - - - - - - Update to
49、 Rel-10 version (MCC) 9.0.0 10.0.0 2012-09 - - - - - - - Updated to Rel-11 by MCC 10.0.0 11.0.0 2014-10 Updated to Rel-12 by MCC 11.0.0 12.0.0 2015-12 - - - - - - - Updated to Rel-13 by MCC 12.0.0 13.0.0 ETSI ETSI TR 122 986 V13.0.0 (2016-01)93GPP TR 22.986 version 13.0.0 Release 13History Document history V13.0.0 January 2016 Publication
