1、 ETSI TR 122 908 V14.0.0 (2017-03) Universal Mobile Telecommunications System (UMTS); LTE; Study on Paging Permission with Access Control (PPAC) (3GPP TR 22.908 version 14.0.0 Release 14) TECHNICAL REPORT ETSI ETSI TR 122 908 V14.0.0 (2017-03)13GPP TR 22.908 version 14.0.0 Release 14Reference RTR/TS
2、GS-0122908ve00 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 do
3、cument 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
4、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 doc
5、ument may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/
6、portal.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 mo
7、dified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefi
8、t of its 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 122 908 V14.0.0 (2017-03)23GPP TR 22.908 version 14.0.0 Release 1
9、4Intellectual 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 Propert
10、y Rights (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 search
11、es, has 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 The present document may refer to technical specifi
12、cations 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. Modal
13、 verbs terminology In the present document “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 Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deli
14、verables except when used in direct citation. ETSI ETSI TR 122 908 V14.0.0 (2017-03)33GPP TR 22.908 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 6g33.1 De
15、finitions 6g33.2 Symbols 6g33.3 Abbreviations . 6g34 Use cases 6g34.1 Priority service with congestion of terminating side 6g34.2 Emergency service call back with congestion of terminating side . 7g34.3 Communication between UEs in the same area where access control is performed 8g35 Considerations
16、10g35.1 Considerations with access class control 10g35.2 Considerations with resource reservation of terminating side 11g35.3 Considerations of existing operation and management of access control 11g36 Gap analysis on current services 11g36.1 Current functionality 11g36.2 Paging Permission with Acce
17、ss Control gap analysis 12g36.2.1.1 Existing capability of Service Accessibility 12g36.2.1.2 New Capability required for Paging Permission with Access Control 13g36.2.2.1 Existing capability of queuing and pre-emption . 13g36.2.2.2 New Capability required for Paging Permission with Access Control 14
18、g37 Conclusion 14g3Annex A: Analysis of provisioning of communication between the unauthorised users in the disaster areas . 15g3A.1 Introduction 15g3A.2 Model for analysis 15g3A.2.1 Model case. 15g3A.2.2 System model 15g3A.2.3 Resource allocation . 17g3A.2.4 Access Class Barring . 17g3A.2.5 Conditi
19、on of successful connection establishment 17g3A.3 Analysis 19g3Annex B: Issues 23g3B.1 Introduction 23g3B.2 Issue and conclusion . 23g3Annex C: Change history 24g3History 25g3ETSI ETSI TR 122 908 V14.0.0 (2017-03)43GPP TR 22.908 version 14.0.0 Release 14Foreword This Technical Report (TR) has been p
20、roduced by ETSI 3rd Generation 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 the TSG modify the contents of the present document, it will be re-released by the TSG with an identifyin
21、g 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 indicates TSG approved document under change control. y the second digit is incremented for all changes of
22、substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 122 908 V14.0.0 (2017-03)53GPP TR 22.908 version 14.0.0 Release 141 Scope This Technical Report (TR) presents the resul
23、ts of the Study on Paging Permission with Access Control. The intent of this Study is to assess the ability of 3GPP specifications to meet requirements identified for Paging Permission with Access Control. This Study considers the following aspects: - Identify requirements and aspects for Paging Per
24、mission with Access Control. - Perform a Gap Analysis to assess the ability of existing 3GPP specifications to meet the requirements and aspects. Regarding use-cases, followings should be studied in order to identify issues which are caused by the existing access control mechanism which does not all
25、ow UEs applied the access class restriction to establish terminating calls (non-exhaustive list): - Priority Service. - Emergency Service. - Communication between UEs in the same area where access control is performed This study should focus on providing this service using the CS/PS domain. This stu
26、dy includes the aspect of originating call and terminating call. 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 nu
27、mber, 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 a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that docum
28、ent in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 22.011: “Service accessibility“. 3 3GPP TS 22.067: “enhanced Multi-Level Precedence and Pre-emption (eMLPP); Stage 1“. 4 3GPP TR 22.950: “Priority Service feasibility study“. 5 3GPP TR
29、22.952: “Priority service guide“. 6 3GPP TS 23.067: “enhanced Multi-Level Precedence and Pre-emption (eMLPP) - Stage 2“. 7 3GPP TS 23.122: “Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode“. 8 3GPP TS 24.008: “Mobile radio interface Layer 3 specification; Core network p
30、rotocols; Stage 3“. 9 3GPP TS 24.067: “enhanced Multi-Level Precedence and Pre-emption (eMLPP) - Stage 3“. 10 3GPP TS 25.304: “UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode“. 11 3GPP TS 25.331: “Radio Resource Control (RRC); Protocol Specification“. 12 3GPP TS 43.0
31、22: “Functions related to Mobile Station (MS) in idle mode and group receive mode“. ETSI ETSI TR 122 908 V14.0.0 (2017-03)63GPP TR 22.908 version 14.0.0 Release 1413 3GPP TS 22.101: “Service aspects; Service principles“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of th
32、e present document, the terms and definitions given in TR 21.905 x and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 x. example: text used to clarify abstract rules by applying them literally. 3.2 Symbols For t
33、he purposes of the present document, the following symbols apply: (void) 3.3 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 x and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbrev
34、iation, if any, in TR 21.905 x. (ffs) 4 Use cases 4.1 Priority service with congestion of terminating side There is a priority communication service which is applied to an authorised user (e.g. government, emergency responder) using priority mechanisms such as special access class (i.e. access class
35、es 11 to 15) allocation and high priority level allocation of eMLPP. The service is effective in giving an important direction in disasters (e.g. earthquakes) which direction is to lead to saving life. This direction should be transferred even if terminating side is in congestion caused by traffic u
36、sed for confirmation of the safety of people in the disaster areas because the authorised users orders some agencies or people in the disaster areas to take an action for saving life. Use-cases are described below. (Note: not exclusive) - Case1: Disaster risk management office in government calls to
37、 emergency responder within disaster areas in order to supply temporary service to the disaster areas. - Case2: Ambulance attendant who gets to a rescue site in the disaster areas but does not found out a person calling for help because of unexpected destruction calls to him/her in order to make sur
38、e where he/she is. ETSI ETSI TR 122 908 V14.0.0 (2017-03)73GPP TR 22.908 version 14.0.0 Release 14Figure 4.1-1: Case2 - Case3: Firefighter at a fire of high-rise apartment in the disaster areas calls to a person losing his/her way in order to give out directives on the evacuation. Figure 4.1-2: Case
39、3 Following considerations are identified from subscription aspect. In the case1 both of the originating users and the terminating users are the authorised users. Whereas in the case2 and 3 the originating users are the authorised users and the terminating users are not the authorised users. 4.2 Eme
40、rgency service call back with congestion of terminating side A user in the disaster areas sets up an emergency call and it is unfortunately released. At the condition, emergency agencies, e.g. police, would like to call back to the user. The call back should be established even if the network which
41、the user resides in is in congestion caused by traffic used for confirmation of the safety of people in the disaster areas. ETSI ETSI TR 122 908 V14.0.0 (2017-03)83GPP TR 22.908 version 14.0.0 Release 14Figure 4.2-1: Use-case of emergency call back In Japanese background, the emergency call back is
42、important. The new laws in the field of emergency service will go into effect in 1st April 2008. As one of the service requirements in emergency call, once an emergency call is established it can only be released by the PSAP operator and whenever PSAP request to call back, operator is required to su
43、ccessfully establish the call back to the user who made the emergency call. 4.3 Communication between UEs in the same area where access control is performed There are many earthquakes in Japan and it is hardly possible to predict when and where earthquake happens, therefore the approach to increase
44、installed capacity in all the areas that costs considerable much is impossible. In order to produce communication in congestion conditions in the earthquake, it is not only efficient from installed capacity aspect but also vital from service aspect to perform “access control interval application“ th
45、at description below explains. There is an area where access control is performed. In order to allow all the users in the area to setup calls, broadcasting access class numbers are changed at an interval of some seconds. For example, in an interval UEs with access class 0 can perform setup and UEs w
46、ith access classes 1-9 cannot do setup, in another interval UEs with access class 1 can do setup and UEs with access classes 0, 2-9 cannot do setup. ETSI ETSI TR 122 908 V14.0.0 (2017-03)93GPP TR 22.908 version 14.0.0 Release 14Figure 4.3-1: Access control interval application Due to access control
47、interval application, the communication between the unauthorised users in the disaster areas is possible. The communication helps users in the emergency situation. Following are use cases. - A mother calls to her child to know where he/she is in the disaster areas. - A mother sends a message to her
48、child to know where he/she is in the disaster areas. ETSI ETSI TR 122 908 V14.0.0 (2017-03)103GPP TR 22.908 version 14.0.0 Release 14Figure 4.3-2: Use-case of the communication between the unauthorised users 5 Considerations 5.1 Considerations with access class control Regarding communications in th
49、e condition where the originating users are the authorised users and the terminating users in the disasters are not the authorised users as identified in the use cases in section 4.1, there is an issue that the authorised user cannot access to the unauthorised user in the condition that access class control barring is applied to the unauthorised users. Regarding emergency service call back as identified in section 4.2, there is an issue that emergency service center cannot make callback to the users in the condition that access class co
