ETSI TR 149 995-2016 Digital cellular telecommunications system (Phase 2+) General Packet Radio Service (GPRS) Interworking between modified Public Land Mobile Network (PLMN) suppo.pdf

《ETSI TR 149 995-2016 Digital cellular telecommunications system (Phase 2+) General Packet Radio Service (GPRS) Interworking between modified Public Land Mobile Network (PLMN) suppo.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 149 995-2016 Digital cellular telecommunications system (Phase 2+) General Packet Radio Service (GPRS) Interworking between modified Public Land Mobile Network (PLMN) suppo.pdf（13页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 1Digital cellular telecoGeneral PacInterworking between m(PLMN) supporting(3GPP TR 49.9TECHNICAL REPORT 149 995 V13.0.0 (2016communications system (Phaacket Radio Service (GPRS); n modified Public Land Mobileng GPRS and legacy GPRS mo.995 version 13.0.0 Release 13GLOBAL SYSTEMOBILE COMMUN16

2、-01) hase 2+); ile Network mobiles 13) TEM FOR ICATIONSRETSI ETSI TR 149 995 V13.0.0 (2016-01)13GPP TR 49.995 version 13.0.0 Release 13Reference RTR/TSGG-0149995vd00 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

3、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 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

4、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 any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable

5、Document Format (PDF) 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 http:/portal.etsi

6、.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/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical,

7、 including 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 Stand

8、ards Institute 2016. 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

9、 Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 149 995 V13.0.0 (2016-01)23GPP TR 49.995 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these es

10、sential 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 Secretariat. Latest upda

11、tes 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 updates on the ETSI Web serv

12、er) 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 Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or G

13、SM 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 verbs terminology In the present document “shall“, “shall not“, “sh

14、ould“, “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 deliverables except when used in direct citation.

15、ETSI ETSI TR 149 995 V13.0.0 (2016-01)33GPP TR 49.995 version 13.0.0 Release 13Contents 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 beh

16、aviour during one phase contention 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 mobil

17、es . 7g35.3 Early Classmark Sending 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 Supp

18、ort of Legacy mobiles . 8g35.5 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 . 9g3

19、5.6.3 Implementation requirements . 9g35.6.4 Support of Legacy mobiles . 9g3Annex A: Change history 11g3History 12g3ETSI ETSI TR 149 995 V13.0.0 (2016-01)43GPP TR 49.995 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP).

20、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 identifying change of release date and an increase in version number

21、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 substance, i.e. technical enhancements, corrections, update

22、s, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 149 995 V13.0.0 (2016-01)53GPP TR 49.995 version 13.0.0 Release 131 Scope This report describes issues relating to the GPRS specifications, which lead to the specifications being

23、 modified after the placement of 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) imp

24、lementations of the GPRS specifications. 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

25、 scope of the present document. 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

26、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 document in the same Release as the pr

27、esent document. 1 3GPP TR 21.905: “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 res

28、ult late changes have been made 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

29、 clarifies any recommended measures 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

30、 and network) this TR specifies the 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 rem

31、ainder of this TR describes how to overcome the possible impacts of the above factors. ETSI ETSI TR 149 995 V13.0.0 (2016-01)63GPP TR 49.995 version 13.0.0 Release 135 Specific implementation on the radio interface 5.1 MS behaviour during one phase contention resolution 5.1.1 Justification It has be

32、en found that in some instances the 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 sha

33、ll accept a Packet Uplink Assignment 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 shal

34、l transmit a Packet Control Acknowledgment 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

35、control blocks 3 A mobile station 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 da

36、ta intended to another mobile station, 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 m

37、obiles shall support the basic contention 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 fou

38、r 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 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

39、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 where two operators have a CS roaming agreement but no GPRS roaming agreement the GPRS specifications cause the user“s SIM to be invalidated for GPRS service. This means, fo

40、r example, that a user roaming from 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 net

41、work which provided GPRS service. ETSI ETSI TR 149 995 V13.0.0 (2016-01)73GPP TR 49.995 version 13.0.0 Release 135.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 mobile“s GPRS Attach requ

42、est with a new GMM cause code “GPRS 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 ca

43、use code it shall not attempt a new 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 swit

44、ched off. The list is introduced 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 cau

45、se value within four months of the 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 origi

46、nal state and removes the information 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 dow

47、n in 5.2.3, operating in a network 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 t

48、owards 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 wil

49、l not spontaneously send a CLASSMARK 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 classma