1、 ETSI TR 122 978 V14.0.0 (2017-03) Universal Mobile Telecommunications System (UMTS); LTE; All-IP network (AIPN) feasibility study (3GPP TR 22.978 version 14.0.0 Release 14) TECHNICAL REPORT ETSI ETSI TR 122 978 V14.0.0 (2017-03)13GPP TR 22.978 version 14.0.0 Release 14Reference RTR/TSGS-0122978ve00
2、 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 document can be
3、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 case of any ex
4、isting 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 document may be s
5、ubject 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:/portal.etsi.or
6、g/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 modified without
7、 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 benefit of its Membe
8、rs. 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 978 V14.0.0 (2017-03)23GPP TR 22.978 version 14.0.0 Release 14Intellectual
9、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 Property Rights (IPRs
10、); 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 searches, has been c
11、arried 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 specifications or rep
12、orts 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 verbs termino
13、logy 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 deliverables excep
14、t when used in direct citation. ETSI ETSI TR 122 978 V14.0.0 (2017-03)33GPP TR 22.978 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 6g3Introduction 6g31 Scope 7g32 References 7g33 Definitions, symbols and abbreviations . 8g33.1
15、Definitions 8g33.2 Abbreviations . 9g34 Objectives and Drivers for progression to an AIPN . 9g34.1 High Level Objectives 9g34.2 Motivations and Drivers . 10g34.2.1 User related and social drivers 10g34.2.1.1 Consumer trend demanding diversification of mobile services 10g34.2.1.2 Human need to be abl
16、e to interact with his personal environment 11g34.2.1.3 Social behaviour and the need to understand ones environment 11g34.2.1.4 The social trend of increasing differences in income within societies. . 11g34.2.1.5 The need to satisfy user experience of early-adopters 12g34.2.2 Drivers from a Busines
17、s perspective . 12g34.2.2.1 Mobile industry anticipating PS traffic to surpass CS . 12g34.2.2.2 Desire of AIPN operators to encompass various access systems that are not specified by 3GPP . 12g34.2.2.3 Marriage of IT- and telecom world . 13g34.2.2.4 Need for increased system efficiency leading to su
18、bstantial cost reduction in terms of both equipment (CAPEX), and operational (OPEX) costs. . 14g34.2.2.5 Trend of the industry to align along the structure: access / transport / control / services 14g34.2.2.6 Fixed/Mobile network convergence 15g34.2.3 Drivers from a Technology perspective 15g34.2.3.
19、1 Evolution of next generation radio access systems (3GPP specified) . 15g34.2.3.2 Progress of broadband wireless IP-based networks (non-3GPP specified) . 15g34.2.3.3 Progress in ad-hoc networking for user defined services. . 15g34.2.3.4 Dawning of new, radio based services (e.g. Personal Networks,
20、RFIDs, multi-hop access networks) . 16g34.2.3.5 Reconfigurable Radio (Software Defined Radio - SDR) 16g34.2.3.6 Web services . 16g34.2.3.7 Multi-access 17g34.2.3.8 Progress of advanced Traffic Engineering Technologies 17g34.3 Impacts to current models for the 3GPP System 17g34.3.1 Impacts to current
21、 charging models 18g34.3.2 Impacts to current business models 18g34.3.3 Impacts to current service models . 19g35 End-user and AIPN operator aspects of an AIPN 20g35.1 AIPN Vision . 20g35.1.1 Key aspects of an AIPN 20g35.1.1.1 Common IP-based network . 20g35.1.1.2 Support of a variety of different a
22、ccess systems (existing and future) 21g35.1.1.3 Take advantage of convergence of telecommunications and IT industries towards IP technology 21g35.1.1.4 Advanced mobility management: 21g35.1.1.5 Enhanced session management: 22g35.1.1.6 Access system selection 22g35.1.1.7 Enhanced services . 22g35.1.1
23、.8 Enhanced network performance 23g3ETSI ETSI TR 122 978 V14.0.0 (2017-03)43GPP TR 22.978 version 14.0.0 Release 145.1.1.9 Network extensibility/composition . 23g35.1.1.10 Network management . 23g35.1.1.11 Maintenance and improvement of the level of security and privacy functionality 23g35.1.1.12 Qu
24、ality of Service . 24g35.1.1.13 Terminal, Subscription and User identification. 24g35.1.1.14 Flexible future development 24g35.1.1.15 Identity Federation 24g35.1.2 Continued support of 3GPP system key aspects within an AIPN . 25g35.1.2.1 Efficiency of resource usage . 25g35.1.2.2 Charging 25g35.1.2.
25、3 Roaming 25g35.2 Evolution of the 3GPP system to an AIPN . 25g35.2.1 Requirements for the evolution of the 3GPP system to an AIPN . 25g35.2.1.1 Build upon existing 3GPP capabilities 25g35.2.1.2 Access systems 26g35.2.1.3 Security and Privacy . 26g35.2.1.4 Network and mobility . 26g35.2.1.5 Evolutio
26、n of 3GPP to keep current and facilitate new business models . 26g35.2.1.6 Lawful Intercept 27g35.2.2 Relationship of the AIPN to existing capabilities 27g35.2.2.1 Reuse of legacy infrastructure . 27g35.2.2.2 Reuse of legacy terminals . 27g35.3 Migration and cost effective introduction of new techno
27、logy 27g35.4 Security and Privacy considerations . 28g35.4.1 Security Considerations 28g35.4.1.1 Threat environment . 29g35.4.1.2 Network heterogeneity and traffic protection 29g35.4.2 Privacy considerations 29g36 Capability expansion required for the introduction of an AIPN 30g36.1 Existing capabil
28、ities suitable for an AIPN . 30g36.2 New capabilities required for an AIPN 30g36.2.1 Enhanced network performance . 30g36.2.1.1 IP-based routing and addressing . 31g36.2.2 Support of a variety of different access systems (existing and future) 31g36.2.2.1 Access system selection 32g36.2.3 Enhanced Mo
29、bility 32g36.2.3.1 Heterogeneous Access Systems Mobility . 32g36.2.3.2 Heterogeneous mobility mechanisms 33g36.2.3.3 Frequent mobility 34g36.2.4 Optimised IP session control 34g36.2.5 Enhanced support of IP traffic 35g36.2.5.1 Support of increased IP traffic demand . 35g36.2.5.2 Ability to effective
30、ly handle a variety of different types of IP traffic . 35g36.2.6 Enhanced Quality of Service 35g36.2.7 Personal Network, Personal Area Network (PAN), Ad-hoc Network and Moving Network Support . 36g37 Conclusions 37g37.1 Roadmap for work within Rel-7 . 38g37.1.1 New requirements for introduction to t
31、he 3GPP specifications in Rel-7 38g37.1.2 Impact on specifications in Rel-7 . 38g37.2 Overall conclusion 42g3Annex A: Mapping of AIPN Motivations to Key Aspects of an AIPN 43g3Annex B: Use cases for AIPN key aspects 44g3B.1 Resilience in the presence of network disruptions and intermittent connectiv
32、ity . 44g3B.2 Service adaptation to terminal capabilities . 45g3B.3 Facilitate integration of networks with different administrative domains (e.g. handle negotiation of administrative issues, security, trust, etc) . 46g3Annex C: Use cases for Security . 47g3C.1 User issues 47g3ETSI ETSI TR 122 978 V
33、14.0.0 (2017-03)53GPP TR 22.978 version 14.0.0 Release 14C.1.1 Ensure privacy and authenticity so that the user can trust the information he is receiving. This should cover private user to private user communications as well as private user to service provider communications 47g3C.1.2 Multiple user
34、identities: Users should be able to have multiple identities from different providers, with the relationship between identities hidden to particular providers (thus supporting privacy) . 48g3C.2 Network issues . 49g3C.2.1 Fast re-authentication shall be possible 49g3Annex D: Security Issues . 51g3D.
35、1 Trust domains . 51g3D.2 Trust establishment. 52g3D.3 Network heterogeneity and traffic protection . 52g3D.4 End-to-end protection . 52g3Annex E: Use cases for Personal Network (PN), Personal Area Network (PAN), Ad-hoc Network and Moving Network Support . 53g3E.1 Personal Network (PN) 53g3E.1.1 Use
36、 case 1: PN with the terminal away from the user 53g3E.2 Personal Area Network (PAN) . 54g3E.2.1 Use case 2: Multiple devices held by the same user . 54g3E.2.1.1 Use case 2a: Subscription data within one device only . 54g3E.2.1.2 Use case 2b:Relationship between Personal Network and Personal Area Ne
37、twork 55g3E.2.3 Impact on an AIPN: 55g3E.3 Ad-hoc Network . 56g3E.3.1 Use Case 1: Formation of an Ad-hoc Network . 56g3E.3.2 Use Case 2: Movement of an Ad-hoc Network 56g3E.3.3 Use case 3: Multiple users within the home . 56g3E.34 Impact to an AIPN 57g3E.4 Moving Network 57g3E.4.1 Use case 1: Moving
38、 Base Station 57g3E.4.2 Use case 2: Wireless Access Router . 58g3E.4.3 Use Case 3: Mobile Router . 59g3E.4.4 Impact to an AIPN 59g3Annex F (Informative): Use Cases for Session Mobility . 60g3F.1 Use Case 1: Redirection of a video stream to the terminal away from the user 60g3F.2 Use case 2: Seamless
39、 mobility of sessions between terminals . 60g3Annex G: Change history 62g3History 63g3ETSI ETSI TR 122 978 V14.0.0 (2017-03)63GPP TR 22.978 version 14.0.0 Release 14Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The contents of the present do
40、cument 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 wher
41、e: 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 i
42、ncremented when editorial only changes have been incorporated in the document. Introduction The 3GPP system currently supports GERAN and UTRAN based Access Networks in conjunction with Circuit-Switched and Packet-Switched Core Network domains and IP Multimedia CN subsystem. The All-IP concept was in
43、itially introduced within 3GPP in Rel-4 with the standardisation of the MSC Server - MGW split core network architecture for the CS domain and extended from Rel-5 by the standardisation of the IP Multimedia CN sub-system. WLAN as an alternative access system to access services of the mobile core net
44、work is recognized from Rel-6 onwards. In order for the 3GPP system to cope with the rapid growth in IP data traffic, the packet-switched technology utilised within 3G mobile networks requires further enhancement. A continued evolution and optimisation of the system concept is also necessary in orde
45、r to maintain a competitive edge in terms of both performance and cost. It is anticipated that the progression towards an All-IP Network (AIPN) may enable leverage of information technology (IT) hardware and software with general-purpose, and mobile network specific software that should provide cost
46、 reduction (CAPEX and OPEX) for infrastructure equipment and applications of 3GPP based mobile networks. Moreover, it is important to ensure compliance with Internet protocols within future developments of the 3GPP system. Additionally, the following aspects identified within TR 21.902 “Evolution of
47、 3GPP System” 2 are considered relevant to the long-term evolution of the 3GPP system: - A seamless integrated network comprising a variety of networking access systems connected to a common IP based network supported by a centralised mobility manager - A similarity of services and applications acro
48、ss the different systems is beneficial to users - 3GPP should focus on the inter-working between 3GPP Mobile Networks and other Networks considering mobility, high security, charging and QoS management Taking the above into consideration it is necessary to further define the All-IP Network (AIPN) co
49、ncept, explore user, business and technological drivers and evaluate the feasibility of evolving the 3GPP system towards an All-IP Network (AIPN). Furthermore, aspects of the 3GPP system requiring enhancement need to be identified and developed in accordance with this common vision. This report discusses the concept of an “All-IP“ network. In the context of this report the term “All-IP“ does not just refer to the transport protocol used within the 3GPP network. 3GPP Release 5 and Release 6 network can already be implemented just using IP transport and could in that sense
