1、 ETSI TS 132 130 V14.0.0 (2017-05) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Network sharing; Concepts and requirements (3GPP TS 32.130 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 130 V14.0.0 (2017-05)13GPP TS 32.130 version 14.0.0
2、Release 14Reference RTS/TSGS-0532130ve00 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 Impor
3、tant 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 prior written
4、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 present document sh
5、ould 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/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the f
6、ollowing 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 the P
7、DF 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 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI
8、 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. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Associati
9、on. ETSI ETSI TS 132 130 V14.0.0 (2017-05)23GPP TS 32.130 version 14.0.0 Release 14Intellectual 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 m
10、embers 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 updates are available on the ETSI Web server (https:/ipr.e
11、tsi.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 server) which are, or may be, or may become, essential to
12、the present document. Foreword This Technical Specification (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 b
13、eing 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“, “should“, “should not“, “may“, “need not“, “will“,
14、 “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. ETSI ETSI TS 132 130 V14.0.0 (2017-05)33GPP TS
15、32.130 version 14.0.0 Release 14Contents Intellectual 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 scena
16、rios . 7g34.2 Management architecture . 8g35 Business 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. te
17、chnical enhancements, corrections, updates, etc. z the 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 utiliz
18、e network capacity. The traditional model of single 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 (O
19、PEX). In general, an increasing number of operators 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
20、. Network sharing has some major implications on the 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
21、, security and competitive information are also important for the operations of a shared network. ETSI ETSI TS 132 130 V14.0.0 (2017-05)53GPP TS 32.130 version 14.0.0 Release 141 Scope The present document describes concepts and high-level requirements for the Operations, Administration, Maintenance
22、 and Provisioning (OAM Principles and high level requirements“. 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 3G
23、PP TS 23.251: “Network sharing; Architecture and functional description“. 6 3GPP TS 36.314: “Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 Measurements“ 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 32.1
24、01 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 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/
25、or Core Network (CN) sharing scenarios, deployment and daily operation of shared network elements are entrusted to a single Actor, called the Master Operator. The Master Operator provides network and OAM see TS 23.251 5), i.e. BTSs / BSCs (respectively NodeBs / RNCs and eNodeBs) in a 2G Radio Access
26、 Network (respectively a 3G Radio Access Network and an E-UTRA network); - Gateway Core Network (GWCN; see TS 23.251 5), in which not only the Radio Access Network elements are shared but also part or all of the Core Network elements (there is no passive core network sharing). In MOCN, POPs have a c
27、ommon S-RAN, have their individual Core Network and their own PLMN code(s), and use the same frequency on the S-RAN. Figure 4.1-1: Multiple Operator Core Network (MOCN) In GWCN, besides sharing Radio Access Network nodes, the POPs also share Core Network nodes (see TS 23.251 5 clause 4.1). ETSI ETSI
28、 TS 132 130 V14.0.0 (2017-05)83GPP TS 32.130 version 14.0.0 Release 14Figure 4.1-2: GateWay Core Network (GWCN) 4.2 Management architecture The management architecture for MOCN is depicted in figure 4.2-1. It is compliant with 3GPP management reference model (TS 32.101 2). Figure 4.2-1: Management a
29、rchitecture for MOCN In the MOCN scenario, all cells of the S-RAN are shared between POPs. The management architecture for GWCN is depicted in figure 4.2-2. It is compliant with 3GPP management reference model (TS 32.101 2). ETSI ETSI TS 132 130 V14.0.0 (2017-05)93GPP TS 32.130 version 14.0.0 Releas
30、e 14Figure 4.2-2: Management architecture for GWCN 5 Business level requirements 5.1 Requirements 5.1.1 Requirements for the OAM ii/ UTRAN; iii/ E-UTRAN. REQ-NS_GEN-CON-2 The MOPSR-DM shall support a capability allowing the MOP-NM to manage S-RAN according to any of the following scenarios: i/ Multi
31、-Operator Core Network ii/ Gateway Core Network. REQ-NS_GEN-CON-3 The MOPSR-DM shall support a capability allowing the MOP-NM to know which POPs the shared resources belong to. REQ-NS_GEN-CON-4 The MOPSR-DM shall support a capability allowing the MOP-NM to configure which POPs share each cell. REQ-N
32、S_GEN-CON-5 Any POP shall be able to activate a signaling-based trace / MDT session on its subscribers, whether they are attached to the POP own RAN or to the S-RAN, provided: a/ this is compliant with the RAN sharing contract; and b/ user consent for participation in MDT is respected. REQ-NS_GEN-CO
33、N-6 The MOP shall be able, on behalf of any POP, to activate an area-based trace / MDT session, on the portion of the S-RAN that the POP shares and on the POP subscribers only, from the MOP RAN DM or MOP NM, provided a/ only the POP related subscriber data are collected; ETSI ETSI TS 132 130 V14.0.0
34、 (2017-05)103GPP TS 32.130 version 14.0.0 Release 14b/ 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 / MDT session, on the portion of the
35、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 consent for participation in MDT is respe
36、cted. 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. Figure 5.4.1-1: Fully pooled radio resources between two POPs 5.4.2 Alarm raised on a shared cell (MOCN scenario) In thi
37、s use case, an alarm is raised on cell #1 of a shared (e)NodeB. According to the RAN sharing agreement, the two POPs A and B are informed by the MOP of the occurrence of this new alarm, as well as of the alarm clearance by the MOP. Figure 5.4.2-1. Handling of an alarm raised on a shared cell (MOCN)
38、ETSI ETSI TS 132 130 V14.0.0 (2017-05)123GPP TS 32.130 version 14.0.0 Release 145.4.3 Single DM for managing S-RAN and POP own RAN In this use case, Operator A is a POP and manages its own (non-shared) NEs from its POP-RAN-DM while Operator B is both MOP and POP and manages S-RAN and its own (non-sh
39、ared) NEs from a single DM. Operator B has several possibilities: Example #1: configure, NE per NE, which POPs share the cells that it manages; or Example #2: define two separate groups of BTSs / (e)NodeBs: - one for the S-RAN NEs it shall then configure which POPs share the cells of this group of B
40、TSs / (e)NodeBs; and - one for its own (non-shared) RAN NEs. Figure 5.4.3-1: Single DM for managing both S-RAN and own RAN 5.4.4 Management of measurements for cross-operator accounting based on data volume and QoS The operator has made an agreement to act as a Master Operator, MOP, for another oper
41、ator (Participating Operator, POP) for RAN sharing. The agreement is regulated in an SLA, which states the following: The QoS profile criteria ARP-1 10 and GBR-5 for QCI-4 and QCI-8 is supported. The DL QCI-4, GBR-5, and ARP-1 10 is charged by x Euro per Mbit, while UL QCI-4, GBR-5, and ARP-1 10 is
42、charged by y Euro per Mbit. QCI-8 is charged z Euro per Mbit regardless of QoS. For cross operator accounting purpose, the network needs to provide data volume measurements with high reliability for the used QoS profile criteria to the MOP. ETSI ETSI TS 132 130 V14.0.0 (2017-05)133GPP TS 32.130 vers
43、ion 14.0.0 Release 146 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 IRPManager to know which POPs share
44、 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 share each core network element.
45、 REQ-NS_PM-FUN-W The IRPAgent shall have the capability to support subscription of UL and DL data volume measurements per QoS profile criteria for cross operator accounting purpose from the IRPManager. The QoS profile criteria may include one or more of the following criteria: one QCI indicator, one
46、 GBR Indicator, one ARP Indicator, where: - a QCI Indicator identifies one specific QCI value. If the indicator is not set then all QCI values should be taken into account. - a GBR Indicator identifies one GBR range value defined by the management system. If the indicator is not set then all GBR ran
47、ges should be taken into account. - an ARP Indicator identifies one ARP priority value. If the indicator is not set then all ARP priority values should be taken into account. REQ-NS_PM-FUN-X The IRPAgent shall support the IRPManager setting the reliability for the counter instances in a measurement
48、job. The detailed definition of reliability is vendor specific. REQ-NS_PM-FUN-Y The IRPAgent shall support up to a maximum number of 200 recorded counter instances per granularity period of data volume measurements for cross operator accounting purpose. REQ-NS_PM-FUN-Z The IRPAgent shall support the
49、 IRPManager to access a file containing data volume measurements for cross operator accounting purposes every granularity period. 6.2 Actor roles See clause 5.2. 6.3 Telecommunications resources See clause 5.3. 6.4 Use cases 6.4.1 Management of measurements for cross-operator accounting based on data volume and QoS The network manager requests a measurement job for data volume measurements for shared network for charging purposes with high reliability, for a subset of data volume counters per shared PLMN, per UL/DL traffic directi
