1、 ETSI TR 149 995 V15.0.0 (2018-07) 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 15.0.0 Release 15) TECHNICAL REPORT GLO
2、BAL SYSTEM FOR MOBILE COMMUNICATIONSRETSI ETSI TR 149 995 V15.0.0 (2018-07)13GPP TR 49.995 version 15.0.0 Release 15Reference RTR/TSGR-0649995vf00 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. ETSI 2018. All rights reserved. DECTTM, PL
8、UGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo
9、are trademarks registered and owned by the GSM Association. ETSI ETSI TR 149 995 V15.0.0 (2018-07)23GPP TR 49.995 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
10、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); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Se
11、cretariat. 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 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 update
12、s on the ETSI Web server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as bei
13、ng the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Report (TR
14、) 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 identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cro
15、ss 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“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of t
16、he 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 V15.0.0 (2018-07)33GPP TR 49.995 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2
17、g3Modal 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 contention resolution 6g35.1.1 Justification . 6g35.1.2 Solution . 6g35.1.3 Implementation requirements . 6g
18、35.1.4 Support of Legacy mobiles . 6g35.2 Roaming . 6g35.2.1 Justification . 6g35.2.2 Solution . 6g35.2.3 Implementation requirements . 7g35.2.4 Support of Legacy mobiles . 7g35.3 Early Classmark Sending on PBCCH cell 7g35.3.1 Justification . 7g35.3.2 Solution . 7g35.3.3 Implementation requirements
19、. 7g35.3.4 Support of Legacy mobiles . 7g35.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 Two-message packet downlink assignment on CCCH . 8g35.5.1 Justification . 8g35.5.2 Solution . 8g35.5.
20、3 Implementation requirements . 8g35.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 requirements . 9g35.6.4 Support of Legacy mobiles . 9g3Annex A: Change history 11g3History 12g3ETSI ETSI TR 149
21、 995 V15.0.0 (2018-07)43GPP TR 49.995 version 15.0.0 Release 15Foreword This Technical Specification 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. Sho
22、uld 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 greate
23、r 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 incorporated in the document. ETSI ETSI TR 149 995 V1
24、5.0.0 (2018-07)53GPP TR 49.995 version 15.0.0 Release 151 Scope This report describes issues relating to the GPRS specifications, which lead to the specifications being modified after the placement of GPRS compliant mobiles into the market place. Where possible the present report clarifies any recom
25、mended 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 specifications. For each issue this report also defines the time after which all new GPRS mobiles are requi
26、red 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. 2 References The following documents contain provisions which, through reference in this text, const
27、itute 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
28、 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.905: “Vocabulary for 3GPP Specifications“. 3 Abbreviations Abbreviations used in the present docu
29、ment 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 to the specifications. This has lead to the situation where existing GPRS mobiles (i.e. those
30、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 measures which may be adopted by the GPRS infrastructure to enable interworking to be obtained betwee
31、n 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 the point in time at which the specification modification come into force. After this point in t
32、ime 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 to overcome the possible impacts of the above factors. ETSI ETSI TR 149 995 V15.0.0 (2018-07)63G
33、PP TR 49.995 version 15.0.0 Release 155 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 the one phase contention resolution procedure leads to interoperability issues. 5.1.2 Solution T
34、o 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 Assignment addressing it by the uplink TFI or TLLI; the mobile station shall act on this message accor
35、ding 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 Acknowledgment in the block specified in uplink. 2 A mobile station may act on the other non-distrib
36、ution 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 shall not answer to a polling request received in a Packet Uplink Ack/Nack message in case it
37、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 station, it is required that a mobile station in contention resolution phase shall not accept a PA
38、CKET 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 contention resolution procedure (covered by points 1, 2, and 3) as soon as the relevant specifica
39、tion (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 specification (GSM 04.60 v6.12.0) being published by 3GPP. 5.1.4 Support of Legacy mobiles In order to
40、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 rejected by the receiving LLC entity. 5.2 Roaming 5.2.1 Justification It has been found that w
41、here 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 from his home network into a visited network and back to his home network will see an inconsiste
42、nt 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. 5.2.2 Solution To avoid the SIM being invalidated unnecessarily TSG CN#11 agreed to a modific
43、ation to the GPRS specifications, which allows a network to reject a mobiles GPRS Attach request with a new GMM cause code “GPRS services not allowed in the current PLMN“. ETSI ETSI TR 149 995 V15.0.0 (2018-07)73GPP TR 49.995 version 15.0.0 Release 15The new rejection cause value “GPRS services not
44、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 new GPRS attach before entering a new PLMN on which it hasnt be rejected with the same cause aft
45、er 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 in order to avoid subsequent registration attempts if either the MS (in class C mode), or the u
46、ser (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 the relevant specification (04.08 v6.14.0) being published by 3GPP. 5.2.4 Support of Legacy mobil
47、es 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 information indicating that the SIM is invalid for GPRS service. The use of cause value #14 (or any ot
48、her 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 network using Network Mode of Operation I (NMO I), may lead to those legacy mobiles not receiving ser
49、vice (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 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 CLASSMARK CHANGE message when a call is initiated, and the Classmark 3 IE w
