1、 ETSI TS 1Universal Mobile TelTelecommNConcep(3GPP TS 32.1TECHNICAL SPECIFICATION132 130 V13.0.0 (2016elecommunications System (LTE; munication management; Network sharing; cepts and requirements .130 version 13.0.0 Release 1316-02) (UMTS); 13) ETSI ETSI TS 132 130 V13.0.0 (2016-02)13GPP TS 32.130 v
2、ersion 13.0.0 Release 13Reference RTS/TSGS-0532130vd00 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
3、 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 electronic and/or print versions of the present document shall not be modified without the
4、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 (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the prese
5、nt 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.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of t
6、he 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, including photocopying and microfilm except as authorized by written permission of ETSI. The content of t
7、he 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 Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of
8、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 Marks registered and owned by the GSM Association. ETSI ETSI TS 132 130 V13.0.0 (2016-02)23GPP TS 3
9、2.130 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 essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR
10、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 available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no inves
11、tigation, 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 are, or may be, or may become, essential to the present document. Foreword This Technical Specif
12、ication (TS) 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 deliverabl
13、es. 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“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interprete
14、d 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 TS 132 130 V13.0.0 (2016-02)33GPP TS 32.130 version 13.0.0 Release 13Contents Intellectua
15、l Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Concepts and background 7g34.1 RAN sharing scenarios . 7g34.2 Management architecture . 8g35 Busines
16、s level requirements . 9g35.1 Requirements 9g35.1.1 Requirements for the OAM 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 t
17、he third digit is incremented when editorial only changes have been incorporated in the document. Introduction Network sharing is emerging as a mechanism for operators to substantially and sustainably improve network costs and to efficiently utilize network capacity. The traditional model of single
18、ownership of all network layers and elements is being challenged and more and more operators are adopting network sharing as a means of cutting the heavy costs involved in initial roll-out, capital expenditure (CAPEX) and operational expenditure (OPEX). In general, an increasing number of operators
19、are sharing their mobile networks. Main arguments presented are: - Increased rollout speed. - Quickly expanding coverage to meet customer demand for wider coverage. - Sharing low traffic areas. - Sharing high license burdens. - Lower CAPEX and OPEX. Network sharing has some major implications on the
20、 operations of the network. Alignment on operational priorities, common network planning/evolution strategy, sharing end user data/subscriber data, sharing performance data, alarms etc. in the shared network need to be considered carefully. Privacy, security and competitive information are also impo
21、rtant for the operations of a shared network. ETSI ETSI TS 132 130 V13.0.0 (2016-02)53GPP TS 32.130 version 13.0.0 Release 131 Scope The present document describes concepts and high-level requirements for the Operations, Administration, Maintenance and Provisioning (OAM Principles and high level req
22、uirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 3GPP TS 36.300: “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2“. 5 3GPP TS 23.251: “Network sharing; Architecture and fun
23、ctional description“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 32.101 2, TS 32.102 3 and TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the same
24、 term, if any, in TS 32.101 2, TS 32.102 3 and TR 21.905 1, in that order. Organizational roles: Master Operator (MOP): In Radio Access Network (RAN) and/or Core Network (CN) sharing scenarios, deployment and daily operation of shared network elements are entrusted to a single Actor, called the Mast
25、er Operator. The Master Operator provides network and OAM see TS 2in a 2G Radio Access Network (res- Gateway Core Network (GWCN; seeare shared but also part or all of theIn MOCN, POPs have a common S-RAN, havthe same frequency on the S-RAN. Figure 4.1-1: MIn GWCN, besides sharing Radio Access Net cl
26、ause 4.1). ETSI ETSI TS 132 1307r CN DM etwork Manager r RAN DM orks background enarios ngst which one category is RAN sharing which can be dgories: s infrastructure sharing (including site sharing). work elements of the RAN are shared: S 23.251 5), i.e. BTSs / BSCs (respectively NodeBs / RNrespecti
27、vely a 3G Radio Access Network and an E-UTRAsee TS 23.251 5), in which not only the Radio Access NeCore Network elements (there is no passive core netwoh e their individual Core Network and their own PLMN ultiple Operator Core Network (MOCN) work nodes, the POPs also share Core Network nodes (3 V13.
28、0.0 (2016-02)e divided into the RNCs and eNodeBs) RA network); Network elements rk sharing). N code(s), and use s (see TS 23.251 5 3GPP TS 32.130 version 13.0.0 Release 13Figure 4.14.2 Management archThe management architecture for MOCN is dmodel (TS 32.101 2). Figure 4.2-1In the MOCN scenario, all
29、cells of the S-RANThe management architecture for GWCN is dmodel (TS 32.101 2). ETSI ETSI TS 132 1308.1-2: GateWay Core Network (GWCN) hitecture s depicted in figure 4.2-1. It is compliant with 3GPP mana: Management architecture for MOCN A are shared between POPs. s depicted in figure 4.2-2. It is c
30、ompliant with 3GPP mana3 V13.0.0 (2016-02)nagement reference nagement reference 3GPP TS 32.130 version 13.0.0 Release 13Figure 4.2-25 Business level r5.1 Requirements 5.1.1 Requirements for theREQ-NS_GEN-CON-1 The MOPSR-Dany of the following radio access technologiei/ GERAN; ii/ UTRAN; iii/ E-UTRAN.
31、 REQ-NS_GEN-CON-2 The MOPSR-Daccording to any of the following scenarios: i/ Multi-Operator Core Network ii/ Gateway Core Network. REQ-NS_GEN-CON-3 The MOPSR-Dthe shared resources belong to. REQ-NS_GEN-CON-4 The MOPSR-DPOPs share each cell. REQ-NS_GEN-CON-5 Any POP shall bewhether they are attached
32、to the POP own RAa/ this is compliant with the RAN sharing b/ user consent for participation in MDT iREQ-NS_GEN-CON-6 The MOP shall bsession, on the portion of the S-RAN that the MOP NM, provided a/ only the POP related subscriber data areETSI ETSI TS 132 1309: Management architecture for GWCN l req
33、uirements the OAM and T is respected. l be able, on behalf of any POP, to activate an area-based he POP shares and on the POP subscribers only, from the are collected; 3 V13.0.0 (2016-02)to manage S-RAN of to manage S-RAN to know which POPs configure which on its subscribers, d trace / MDT he MOP RA
34、N DM or ETSI ETSI TS 132 130 V13.0.0 (2016-02)103GPP TS 32.130 version 13.0.0 Release 13b/ this is compliant with the RAN sharing contract; and c/ user consent for participation in MDT is respected. REQ-NS_GEN-CON-7 The MOP shall be able, on behalf of multiple POPs, to activate an area-based trace /
35、 MDT session, on the portion of the S-RAN that each POP shares and on each POP subscribers only, from the MOP RAN DM or MOP NM, provided: a/ each POP has access only to its subscriber data (i.e. not to other POPs subscriber data); b/ this is compliant with the RAN sharing contract; and c/ user conse
36、nt for participation in MDT is respected. 5.1.2 Requirements for the OA UEs from POP A and POP B are served in the S-RAN in a first come first served mode; - MOP is responsible for configuring the S-RAN accordingly. 3GPP TS 32.130 version 13.0.0 Release 13Figure 5.4.1-1: Fully5.4.2 Alarm raised on a
37、 shIn this use case, an alarm is raised on cell #1 oPOPs A and B are informed by the MOP of thMOP. Figure 5.4.2-1. HandliETSI ETSI TS 132 13011ll pooled radio resources between two POPs shared cell (MOCN scenario) 1 of a shared (e)NodeB. According to the RAN sharing agf e occurrence of this new alar
38、m, as well as of the alarm dling of an alarm raised on a shared cell (MOCN) 3 V13.0.0 (2016-02)agreement, the two clearance by the 3GPP TS 32.130 version 13.0.0 Release 135.4.3 Single DM for managIn this use case, Operator A is a POP and manis both MOP and POP and manages S-RAN aOperator B has sever
39、al possibilities: Example #1: configure, NE per NE, whichExample #2: define two separate groups o- one for the S-RAN NEs it sha(e)NodeBs; and - one for its own (non-shared) RAFigure 5.4.3-1: SingleETSI ETSI TS 132 13012aging S-RAN and POP own RAN anages its own (non-shared) NEs from its POP-RAN-DMnd
40、 its own (non-shared) NEs from a single DM. ic POPs share the cells that it manages; or s of BTSs / (e)NodeBs: sh ll then configure which POPs share the cells of this groR N NEs. gle DM for managing both S-RAN and own RAN 3 V13.0.0 (2016-02)M while Operator B oup of BTSs / ETSI ETSI TS 132 130 V13.0
41、.0 (2016-02)133GPP TS 32.130 version 13.0.0 Release 136 Specification level requirements 6.1 Requirements REQ-NS_GEN-FUN-1 The IRPAgent shall support a capability allowing the IRPManager to configure which POPs share each cell. REQ-NS_GEN-FUN-2 The IRPAgent shall support a capability allowing the IR
42、PManager to know which POPs share each cell. REQ-NS_GEN-FUN-3 In GWCN, the IRPAgent shall support a capability allowing the IRPManager to configure which POPs share each core network element. REQ-NS_GEN-FUN-4 In GWCN, the IRPAgent shall support a capability allowing the IRPManager to know which POPs
43、 share each core network element. 6.2 Actor roles See clause 5.2. 6.3 Telecommunications resources See clause 5.3. 6.4 Use cases See clause 5.4. ETSI ETSI TS 132 130 V13.0.0 (2016-02)143GPP TS 32.130 version 13.0.0 Release 13Annex A (informative): Network sharing agreement Prior to any network shari
44、ng deployment, the MOP and the POPs have to agree on legal, financial, technical and operational aspects. Among operational aspects, the network sharing agreement captures the following (non-exhaustive list): - Organizations involved (i.e. Operators) and their roles in the network sharing deployment
45、. - Exhaustive list of shared and unshared resources in the shared network. - Rights attached to each role (e.g. rights to configure network resources, rights to receive alarms, etc.). - Duties attached to each role (e.g. obligation for the MOP to provide POPs with monthly KPIs, etc.). - Delegations
46、 (if any) given by any organization to another organization. - Service Level Agreements (SLAs). ETSI ETSI TS 132 130 V13.0.0 (2016-02)153GPP TS 32.130 version 13.0.0 Release 13Annex B (informative): Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New 2014-12 SA#66 SP-140795 Presented for approval 1.2.0 2.0.0 2014-12 Version after approval 2.0.0 12.0.0 2016-01 - - - - Update to Rel-13 version (MCC) 12.0.0 13.0.0 ETSI ETSI TS 132 130 V13.0.0 (2016-02)163GPP TS 32.130 version 13.0.0 Release 13History Document history V13.0.0 February 2016 Publication
