1、 ETSI TR 149 995 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); General Packet Radio Service (GPRS); Interworking between modified Public Land Mobile Network (PLMN) supporting GPRS and legacy GPRS mobiles (3GPP TR 49.995 version 14.0.0 Release 14) TECHNICAL REPORT GLO
2、BAL SYSTEM FOR MOBILE COMMUNICATIONSRETSI ETSI TR 149 995 V14.0.0 (2017-04)13GPP TR 49.995 version 14.0.0 Release 14Reference RTR/TSGR-0649995ve00 Keywords GSM 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
3、 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present 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 elec
4、tronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. 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 (PD
5、F) version kept on a specific network 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 https:/portal.etsi.org/TB/ETSIDelive
6、rableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/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, includin
7、g photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Inst
8、itute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit 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 Ma
9、rks registered and owned by the GSM Association. ETSI ETSI TR 149 995 V14.0.0 (2017-04)23GPP TR 49.995 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential I
10、PRs, 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 available from the ETSI Secretariat. Latest updates are a
11、vailable on the ETSI Web server (https:/ipr.etsi.org/). 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 in ETSI SR 000 314 (or the updates on the ETSI Web server) which
12、 are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identi
13、ties. 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 verbs terminology In the present document “should“, “should not“, “may“, “ne
14、ed 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 deliverables except when used in direct citation. ETSI ETSI TR 149 995 V14.0.0 (2
15、017-04)33GPP TR 49.995 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Abbreviations . 5g34 General . 5g35 Specific implementation on the radio interface 6g35.1 MS behaviour during one phase content
16、ion resolution 6g35.1.1 Justification . 6g35.1.2 Solution . 6g35.1.3 Implementation requirements . 6g35.1.4 Support of Legacy mobiles . 6g35.2 Roaming . 6g35.2.1 Justification . 6g35.2.2 Solution . 7g35.2.3 Implementation requirements . 7g35.2.4 Support of Legacy mobiles . 7g35.3 Early Classmark Sen
17、ding on PBCCH cell 7g35.3.1 Justification . 7g35.3.2 Solution . 7g35.3.3 Implementation requirements . 7g35.3.4 Support of Legacy mobiles . 8g35.4 Conditions for IOV reset 8g35.4.1 Justification . 8g35.4.2 Solution . 8g35.4.3 Implementation requirements . 8g35.4.4 Support of Legacy mobiles . 8g35.5
18、Two-message packet downlink assignment on CCCH . 8g35.5.1 Justification . 8g35.5.2 Solution . 8g35.5.3 Implementation requirements . 9g35.5.4 Support of Legacy mobiles . 9g35.6 Negotiation of SNDCP compression entities . 9g35.6.1 Justification . 9g35.6.2 Solution . 9g35.6.3 Implementation requiremen
19、ts . 9g35.6.4 Support of Legacy mobiles . 9g3Annex A: Change history 11g3History 12g3ETSI ETSI TR 149 995 V14.0.0 (2017-04)43GPP TR 49.995 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present doc
20、ument 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 identifying change of release date and an increase in version number as follows: Version x.y.z where
21、: 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 substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is in
22、cremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 149 995 V14.0.0 (2017-04)53GPP TR 49.995 version 14.0.0 Release 141 Scope This report describes issues relating to the GPRS specifications, which lead to the specifications being modified after the placement o
23、f GPRS compliant mobiles into the market place. Where possible the present report clarifies any recommended measures which may be adopted by the GPRS infrastructure to enable interworking to be obtained between the GPRS infrastructure and legacy Mobile Station (MS) implementations of the GPRS specif
24、ications. For each issue this report also defines the time after which all new GPRS mobiles are required to meet the modified specifications. The lifetime of the herein described measures together with their potential impact on optimal network performance is out of the scope of the present document.
25、 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 reference, subsequen
26、t 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. 1 3GPP TR 21.90
27、5: “Vocabulary for 3GPP Specifications“. 3 Abbreviations Abbreviations used in the present document are listed in 3GPP TR 21.905 1. 4 General In the implementation of the GPRS standard it has been found that some aspects of GPRS have not been fully covered and as a result late changes have been made
28、 to the specifications. This has lead to the situation where existing GPRS mobiles (i.e. those already in the field) no longer aligned with the latest version of the specifications. These legacy mobiles will not be modified; however, where possible the present report clarifies any recommended measur
29、es which may be adopted by the GPRS infrastructure to enable interworking to be obtained between the GPRS infrastructure and these legacy Mobile Station (MS). In addition and to ensure sufficient time for implementation and testing of modified GPRS implementation (MS and network) this TR specifies t
30、he point in time at which the specification modification come into force. After this point in time all new GPRS mobiles will be required to support the modified specification and all GPRS networks will be expected to handle the new mobile behaviour correctly. The remainder of this TR describes how t
31、o overcome the possible impacts of the above factors. ETSI ETSI TR 149 995 V14.0.0 (2017-04)63GPP TR 49.995 version 14.0.0 Release 145 Specific implementation on the radio interface 5.1 MS behaviour during one phase contention resolution 5.1.1 Justification It has been found that in some instances t
32、he one phase contention resolution procedure leads to interoperability issues. 5.1.2 Solution To avoid interoperability issues, TSG GERAN#3 agreed on the following mobile station behaviour during the contention resolution phase (CR 04.60-A952): 1 A mobile station shall accept a Packet Uplink Assignm
33、ent addressing it by the uplink TFI or TLLI; the mobile station shall act on this message according to the procedures defined in packet transfer mode during operation on an uplink TBF. If a valid RRBP field is received as part of this message, the mobile station shall transmit a Packet Control Ackno
34、wledgment in the block specified in uplink. 2 A mobile station may act on the other non-distribution messages addressing the mobile station with the TFI or TLLI, and may transmit a Packet Control Acknowledgment when a valid RRBP field is received in downlink RLC/MAC control blocks 3 A mobile station
35、 shall not answer to a polling request received in a Packet Uplink Ack/Nack message in case it includes a TLLI addressing another mobile station; then an ambiguous word is deleted in 3GPP TS 04.60 sub-clause 10.4.5. 4 To prevent a mobile station receiving downlink data intended to another mobile sta
36、tion, it is required that a mobile station in contention resolution phase shall not accept a PACKET DOWNLINK ASSIGNMENT nor a PACKET TIMESLOT RECONFIGURE message, whatever the address used in these assignment messages. 5.1.3 Implementation requirements All new GPRS mobiles shall support the basic co
37、ntention resolution procedure (covered by points 1, 2, and 3) as soon as the relevant specification (GSM 04.60 v6.12.0) is published by 3GPP. All new GPRS mobiles shall support the complete contention resolution procedure (covered by points 1, 2, 3, and 4) within four months of the relevant specific
38、ation (GSM 04.60 v6.12.0) being published by 3GPP. 5.1.4 Support of Legacy mobiles In order to force the rejection of occasional LLC frames that may be received by the wrong mobile station, ciphering needs to be applied. This will cause an LLC frame that is received by the wrong mobile station to be
39、 rejected by the receiving LLC entity. 5.2 Roaming 5.2.1 Justification It has been found that where two operators have a CS roaming agreement but no GPRS roaming agreement the GPRS specifications cause the users SIM to be “invalidated for GPRS service”. This means, for example, that a user roaming f
40、rom his home network into a visited network and back to his home network will see an inconsistent level of GPRS service. In other words a service which was working (before the user roamed) will no longer be working even though the user has returned to the original network which provided GPRS service
41、. ETSI ETSI TR 149 995 V14.0.0 (2017-04)73GPP TR 49.995 version 14.0.0 Release 145.2.2 Solution To avoid the SIM being invalidated unnecessarily TSG CN#11 agreed to a modification to the GPRS specifications, which allows a network to reject a mobiles GPRS Attach request with a new GMM cause code “GP
42、RS services not allowed in the current PLMN“. The new rejection cause value “GPRS services not allowed in this PLMN“(#14) can be indicated to the MS during GPRS attach, detach and RAU in a PLMN which does not offer GPRS roaming to that MS. When an MS receives this cause code it shall not attempt a n
43、ew GPRS attach before entering a new PLMN on which it hasnt be rejected with the same cause after the last switch on. In order to memorise the PLMNs on which the MS has been rejected with #14, a new PLMN list is introduced, which should be deleted when the MS is switched off. The list is introduced
44、in order to avoid subsequent registration attempts if either the MS (in class C mode), or the user (in class A/B mode) triggers a PLMN reselection after reception of #14. 5.2.3 Implementation requirements All new GPRS mobiles shall support the handling of the new cause value within four months of th
45、e relevant specification (04.08 v6.14.0) being published by 3GPP. 5.2.4 Support of Legacy mobiles To restore the SIM to proper operation for GPRS service the user needs to power off and on the mobile. As defined by the specifications, this resets the SIM to its original state and removes the informa
46、tion indicating that the SIM is invalid for GPRS service. The use of cause value #14 (or any other cause value which is not defined in the reference specification of the MS), towards some of the roaming legacy mobiles which were implemented prior to the date laid down in 5.2.3, operating in a networ
47、k using Network Mode of Operation I (NMO I), may lead to those legacy mobiles not receiving service (see 04.08 subclauses 4.2.4.2.2 and 4.7.3.1.5). This means that the behaviour of some roaming legacy mobiles may be unpredictable in NMO I if cause value #14 is used towards those legacy mobiles. 5.3
48、Early Classmark Sending on PBCCH cell 5.3.1 Justification It was found that the Early Classmark Sending Capability (ECSC) bit is present on BCCH in SI3 but is not present on PBCCH. If the MS considers that early classmark sending is not allowed by the network, it will not spontaneously send a CLASSM
49、ARK CHANGE message when a call is initiated, and the Classmark 3 IE will not be received by the network. This may result in that the MS will not receive expected service from the network based on actual MS capabilities. Three different mobile implementations have been identified for a GPRS R97 mobile on a PBCCH cell: a) The MS systematically reads SI3 on BCCH and uses the ECSC value, b) When the MS does not read SI3, it systematically sends early classmark message, c) When the MS does not read SI3, the MS never sends early classmark message. 5.3.2 Solution TSG
