ETSI TR 125 999-2008 Universal Mobile Telecommunications System (UMTS) High Speed Packet Access (HSPA) evolution Frequency Division Duplex (FDD)《全球移动通信系统(UMTS) 高速分组接入(HSPA)的发展 频率双分_1.pdf

《ETSI TR 125 999-2008 Universal Mobile Telecommunications System (UMTS) High Speed Packet Access (HSPA) evolution Frequency Division Duplex (FDD)《全球移动通信系统(UMTS) 高速分组接入(HSPA)的发展 频率双分_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 125 999-2008 Universal Mobile Telecommunications System (UMTS) High Speed Packet Access (HSPA) evolution Frequency Division Duplex (FDD)《全球移动通信系统(UMTS) 高速分组接入(HSPA)的发展 频率双分_1.pdf（61页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 125 999 V7.1.0 (2008-04)Technical Report Universal Mobile Telecommunications System (UMTS);High Speed Packet Access (HSPA) evolution;Frequency Division Duplex (FDD) (3GPP TR 25.999 version 7.1.0 Release 7)ETSI ETSI TR 125 999 V7.1.0 (2008-04) 1 3GPP TR 25.999 version 7.1.0 Release 7 Referen

2、ce RTR/TSGR-0225999v710 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 Individua

3、l copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Fo

4、rmat (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the 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

5、 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: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced

6、except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2008. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI reg

7、istered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 125 999 V7.1.0 (2008-04) 2 3GPP TR 25.999 version 7.1.0 Release 7 Intellectual Property Rights IPRs essential or potentially essentia

8、l 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); Essential, or potentially Essential, IPRs notified

9、to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be

10、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 Partnership Project (3GPP). The prese

11、nt 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 ETSI identities can be found under http

12、:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TR 125 999 V7.1.0 (2008-04) 3 3GPP TR 25.999 version 7.1.0 Release 7 Contents Intellectual Property Rights2 Foreword.2 Foreword.5 1 Scope 6 2 References 6 3 Definitions, symbols and abbreviations .6 3.1 Definitions6 3.2 Abbreviations .6 4 Introduction 7

13、 5 Objectives.7 6 Constraints and requirements .8 6.1 Constraints8 6.2 Requirements8 6.2.1 Requirements for the UTRAN architecture 8 6.2.2 Requirements for the UTRA.9 7 Technical Proposals and Assessment.9 7.1 Architectural solutions .11 7.1.1 Current Release 6 Architecture - Alt 111 7.1.2 Iu with e

14、nhanced SRNC separate from the enhanced collapsed CRNC/DRNC/Node B Alt 212 7.1.2.1 General description .12 7.1.2.2 User Plane .13 7.1.2.3 Control Plane (Radio part) 13 7.1.2.4 Control Plane (Interface part)14 7.1.2.5 Support of legacy UE14 7.1.2.6 Support of legacy networks.15 7.1.2.7 Additional Inf

15、ormation16 7.1.2.8 Open issues .17 7.1.3 PS User Plane /Control Plane split, CP functions in RNC, direct UP tunnel PS CN Node B Alt 318 7.1.3.1 General description .18 7.1.3.2 Protocol architecture .19 7.1.3.3 Control plane.19 7.1.3.4 Support of legacy UEs 20 7.1.3.5 Interworking with legacy archite

16、cture.20 7.1.4 Iu with RNC U-Plane 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 incremented when editori

17、al only changes have been incorporated in the document. ETSI ETSI TR 125 999 V7.1.0 (2008-04) 6 3GPP TR 25.999 version 7.1.0 Release 7 1 Scope The present document has been produced in the scope of the study item on “HSPA Evolution“ 2. The objective of the study item is to develop a framework for th

18、e evolution of the FDD mode of the 3GPP HSPA WCDMA-based radio-access technology beyond Release 7. The present document lists the constraints for the FDD HSPA Evolution beyond release 7 and an assessment of technical proposals and their respective, achievable performance and complexity. 2 References

19、 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, subsequent revisions d

20、o 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.905: “Vocabular

21、y for 3GPP Specifications“. 2 3GPP TD RP-060217: “Work Item Description on Scope of future FDD HSPA Evolution“. Suppote Team note: Reference 2 is not legitimate. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 2

22、1.905 1 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 1. HSPA: In the present document, the acronym HSPA (High Speed Packet Access) is used to qualify the FDD mode features HSDPA (High Speed Downlink Packet

23、 Access) and Enhanced Uplink as defined in the Release 7 version of the 3GPP Specifications. Backward Compatibility: In the present document, Backward Compatibility means the ability of an HSPA infrastructure to simultaneously allocate radio resources on one single carrier to post-release 7 terminal

24、s and terminals compliant with previous releases of the 3GPP specifications without performances degradation for either type of terminal. It is understood that in that case the performance enhancements targeted in this document would only apply to post-release 7 terminals and that the full potential

25、 of system performance enhancements would only be achievable if all terminals operating simultaneously on a single carrier were post-release 7 terminals. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation define

26、d in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. CAPEX Capital expenditure CS Circuit SwitchedDRX Discontinuous Reception ETSI ETSI TR 125 999 V7.1.0 (2008-04) 7 3GPP TR 25.999 version 7.1.0 Release 7 HSPA High Speed Packet Access LTE:

27、Long Term Evolution MIMO Multiple Input Multiple Output NAS Non Access Stratum OPEX Operational expenditure QoS Quality of Service PS Packet Switched TCP Transmission Control Protocol UE User Equipment 4 Introduction The Study Item Description on “HSPA Evolution“ 2 was approved by the 3GPP TSG RAN #

28、31 plenary meeting in March 2006. The importance of on-going and future efforts to enhance the capabilities and performance of HSPA-based radio networks is widely recognised by 3GPP operators. HSPA networks will form an integral part of future 3G systems and as they evolve, should provide a smooth m

29、igration path towards LTE. HSPA operators are just as interested in the potential performance and cost savings which may be achieved through HSPA Evolution as they are in the future LTE system. Critical elements of such evolution should include reduced latency, higher user data rates, improved syste

30、m capacity and coverage and reduced cost for the operator while maintaining the highest possible level of backward compatibility. 5 Objectives Beyond Release 7, the following elements should be considered as guiding principles for HSPA Evolution: 1. HSPA Spectrum Efficiency, Peak Data Rate and Laten

31、cy should continue to evolve favourably. The tradeoffs necessary to achieve performance comparable to LTE in 5 MHz should be analyzed; 2. HSPA and its evolution should facilitate the joint technology operation with LTE and offer a smooth migration path towards LTE (Long Term Evolution). The possibil

32、ity to adopt common elements or a common functional split with LTE and the possibility to re-use the evolved Core Network defined as part of the System Architecture Evolution (SAE) study should be analyzed as well; 3. Evolved HSPA should be able to operate as a packet-only network based on utilizati

33、on of the high speed data channels only (HS-DSCH, E-DCH and associated channels); 4. HSPA Evolution shall be backward compatible in the sense that legacy terminals (R99-DCH and HSPA mobiles) shall be able to share the same carrier with terminals implementing the latest features of the HSPA Evolution

34、 track without any performance degradation; 5. Ideally, existing infrastructure should only need a simple upgrade to support the features defined as part of the HSPA Evolution. Thus, the study should focus on improving the system performances for services delivered through the PS-domain including vo

35、ice and multimedia conversational services. In relation to this study item, TSG-RAN should establish a reference performance set for HSPA release 7. Rather than relying on new simulation results, it is recommended that this performance set is derived from on-going activities related to the performan

36、ce evaluation of new enhancements like HSDPA MIMO or LTE. This reference performance set should be used to set the absolute performance targets for HSPA Evolution and to evaluate the potential improvements provided by solutions proposed in the scope of the study. ETSI ETSI TR 125 999 V7.1.0 (2008-04

37、) 8 3GPP TR 25.999 version 7.1.0 Release 7 6 Constraints and requirements NOTE: This chapter will capture text on the constraints for HSPA evolution including on legacy issues, backward compatibility, architecture, impact on LTE, Node B and UTRA, software and hardware upgrades, complexity issues, ac

38、ceptable impacts on UEs, protocol reuse/requirements, signalling and physical channel limitations, etc. 6.1 Constraints a) HSPA Evolution should be capable of being implemented through a re-use of the release 7 RAN architecture. However, proposals to modify the RAN architecture should also be consid

39、ered within the scope of HSPA Evolution, provided full interworking to a legacy release 7 architecture is supported. b) The RAN-CN functional split can be reviewed providing that it results in significant performance and/or improvements and facilitate the migration towards LTE/SAE without significan

40、t complexity increase. c) Evolved HSPA should have a minimum impact on Node Bs, to allow for simple upgrades; Reuse of the existing Node B hardware by HSPA Evolution is essential. This does not preclude hardware upgrades to support additional functionality (e.g. to increase processing power, RNC fun

41、ctionality, etc.). d) Evolved HSPA protocol architecture shall have minimum impact on UEs especially in terms of complexity, to allow for easy introduction. e) R99-DCH and legacy HSPA UEs shall be able to share the same carrier with terminals implementing the latest features of the HSPA Evolution wi

42、thout any performance degradation. f) Intra- and inter-system mobility performance shall be no worse than R7. 6.2 Requirements 6.2.1 Requirements for the UTRAN architecture a) Should provide a low complexity, low cost and smooth migration of HSPA towards evolved UMTS (SAE/LTE). b) Should reduce user

43、 plane latency to legacy (R5,6 it is possible to route the user plane (Iu-PS) also via SGSN. The use of Iu interface ensures that the system can utilise the existing core network. Interoperability with legacy architecture or 2G is also ensured. Additionally, it is possible to use Iur interface betwe

44、en RNC and Evolved HSPA NodeB as the latter has full RNC functionality. In summary, the described solution is characterised by the following features: - Evolved Node Bs have a direct IP broadband connection towards the Packet Core for PS traffic. - A flat RAN architecture, allowing delay optimisatio

45、n and scalability without capacity bottlenecks. - RNC is not needed at all for pure PS carrier, i.e. in stand-alone deployment. - RNC is used to implement CS support and therefore CS core is not changed at all in carrier sharing deployment. - Stand-alone scenario requires minimal changes or no chang

46、es for the current specifications and network elements: - RNC ID in TS 25.413 range extension in RANAP etc, if very large evolved HSPA networks are deployed (refer to 7.4). - Optionally, new HLR parameter “PS only network allowed“, if operator offers true PS-only HSPA access (without CS service enab

47、ling handover), then “PS only network allowed“ parameter in HLR could be useful for roaming cases. TS 22.011, 24.008, 23.060, 21.101, 23.122. - Carrier sharing scenario requires changes for Iur interface, the required changes to specification are FFS. 7.1.4.1 User plane User Plane protocol stack for

48、 HSPA traffic is Iu-PS (GTP-U/UDP/IP). In case of one tunnel approach the User plane is directly between evolved HSPA NodeB and GGSN. In carrier sharing case, non-HSPA traffic goes to RNC on Iur. Uplink Macro Diversity Stand-alone deployment scenario ETSI ETSI TR 125 999 V7.1.0 (2008-04) 223GPP TR 2

49、5.999 version 7.1.0 Release 7 Flat architecture is optimized for intra Node B uplink MDC for user plane. In case of inter-NodeB MDC, it is possible to apply a Serving Node B Drift Node B scenario. In the flat architecture, the operator needs investigate, whether to use MDC or not. For example, NodeB with good sensitivity can lead to situation where link budget is downlink limited and MDC is not needed at all. Carrier sharing deployment scenario MDC can be used for non HSPA traffic served by the RNC. Header Compression Stand-alone deployment