1、 ETSI TS 1Universal Mobile TelTelecommSoftwarConcepts and Integratio(3GPP TS 32.5TECHNICAL SPECIFICATION132 531 V13.0.0 (2016elecommunications System (LTE; munication management; e management (SwM); tion Reference Point (IRP) Req.531 version 13.0.0 Release 1316-02) (UMTS); equirements 13) ETSI ETSI
2、TS 132 531 V13.0.0 (2016-02)13GPP TS 32.531 version 13.0.0 Release 13Reference RTS/TSGS-0532531vd00 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
3、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 content of any electronic and/or print versions of the presen
4、t 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 Document Format (PDF) version kept on a specific network driv
5、e 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.org/tb/status/status.asp If you find errors in the present d
6、ocument, 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, including photocopying and microfilm except as authorized by
7、 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 Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM
8、, 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 Trade Marks registered and owned by the GSM Association. ETS
9、I ETSI TS 132 531 V13.0.0 (2016-02)23GPP TS 32.531 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
10、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.etsi.org
11、/). 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 the pre
12、sent 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 being re
13、ferences 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“, “will
14、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 531 V13.0.0 (2016-02)33GPP TS 32.531
15、version 13.0.0 Release 13Contents 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 Business Level Requireme
16、nts. 7g34.1.1 Business Level Requirements 1 7g34.1.1.1 Actor roles . 7g34.1.1.2 Telecommunications resources . 7g34.1.1.3 High-level use cases 7g34.1.2 Business Level Requirements 2 7g34.1.2.1 Actor roles . 7g34.1.2.2 Telecommunications resources . 7g34.1.2.3 High-level use cases 7g34.1.3 Business L
17、evel Requirements 3 7g34.1.3.1 Actor roles . 7g34.1.3.2 Telecommunications resources . 7g34.1.3.3 High-level use cases 7g34.1.4 Business Level Requirements 4 8g34.1.4.1 Actor roles . 8g34.1.4.2 Telecommunications resources . 8g34.1.4.3 High-level use cases 8g34.2 Specification level requirements 8g3
18、4.2.1 Specification level requirement on general SWM 8g34.2.1.1 Actor roles . 8g34.2.1.2 Telecommunications resources . 8g34.2.1.3 Use cases . 9g34.2.1.3.1 Use case 1 9g34.2.2 Specification level requirement on Automated SWM 9g34.2.2.1 Actor roles . 9g34.2.2.2 Telecommunications resources . 9g34.2.2
19、.3 Use cases . 10g34.2.2.3.1 Use case Self-Configuration 10g34.2.2.3.1 Use case Automated Software Update 10g34.2.3 Specification level requirement on Non-Automated SWM 11g34.2.3.1 Actor roles . 11g34.2.3.2 Telecommunications resources . 11g34.2.3.3 Use cases . 12g34.2.3.3.1 Use case Non-Automated S
20、oftware Update 12g34.2.3.3.2 Fallback during Non-Automated Software Update . 13g34.2.3.3.3 Backup Network Element Software Configuration Data . 14g34.2.3.3.4 Restore Network Element Software Configuration Data . 15g3Annex A (informative): Change history . 16g3History 17g3ETSI ETSI TS 132 531 V13.0.0
21、 (2016-02)43GPP TS 32.531 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG
22、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 where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates
23、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 editorial only changes have been incorporated in the document. Introduction The present document i
24、s part of a TS-family covering the 3rdGeneration Partnership Project Technical Specification Group Services and System Aspects, Telecommunication management; as identified below: 32.531: Telecommunication management; Software management; Concepts and Integration Reference Point (IRP) Requirements 32
25、.532: Telecommunication management; Software management Integration Reference Point (IRP); Information Service (IS) 32.536: Telecommunication management; Software management Integration Reference Point (IRP); Solution Set (SS) definitions ETSI ETSI TS 132 531 V13.0.0 (2016-02)53GPP TS 32.531 version
26、 13.0.0 Release 131 Scope The present document describes the concepts how SWM of NEs works and what IRP requirements need to be met to support this functionality. In the 3GPP Rel-8 the present document focuses on automated software management of eNBs. 2 References The following documents contain pro
27、visions 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 do not apply. For a non-specific refe
28、rence, 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: “Vocabulary for 3GPP Specifications“. 2 3GPP T
29、S 32.101: “Telecommunication management; Principles and high level requirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 Void. 3 Definitions and abbreviations For the purposes of the present document, the terms and definitions given in TS 32.101 2, TS 32.102 3 and TS 21.90
30、5 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 TS 21.905 1, in that order. 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and
31、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. Software Management: Activities to control which software is available and/or active in a network element. Automated Software Management: Software Management whi
32、ch is performed without the presence of an IRPManager (SWM). An IRPManager may monitor and /or control the software management activities. An IRPAgent receives information to perform the Software Management activities in an autonomous way. Non-Automated Software Management: Software Management which
33、 requires the presence of IRPManager (SWM) to fully control and monitor the software management activities. The IRPAgent receives explicit instructions from the IRPManager about the SW Management activities which shall be performed. Software Installation: Installation of software puts it into a form
34、 suitable for activation or use. ETSI ETSI TS 132 531 V13.0.0 (2016-02)63GPP TS 32.531 version 13.0.0 Release 13Software Activation: Activation of software makes it ready to be used and the software starts providing service. 3.2 Abbreviations For the purposes of the present document, the abbreviatio
35、ns given in TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. ASWM Automated Software Management NASWM Non-Automated Software Management NE Network Element SWM Software Managemen
36、t ETSI ETSI TS 132 531 V13.0.0 (2016-02)73GPP TS 32.531 version 13.0.0 Release 134 Concepts and background 4.1 Business Level Requirements 4.1.1 Business Level Requirements 1 REQ_SW_CON_1 The software management functions used during the establishment of a new NE in the network should be usable also
37、 for software upgrade. 4.1.1.1 Actor roles FFS 4.1.1.2 Telecommunications resources FFS 4.1.1.3 High-level use cases FFS 4.1.2 Business Level Requirements 2 REQ_SW_CON_2 The IRPManager should have monitoring and interaction capabilities regarding the software download, installation, activation and f
38、allback in/to the NE. 4.1.2.1 Actor roles FFS 4.1.2.2 Telecommunications resources FFS 4.1.2.3 High-level use cases FFS 4.1.3 Business Level Requirements 3 REQ_SW_CON_3 The software installation shall have no or limited service impacts. 4.1.3.1 Actor roles FFS 4.1.3.2 Telecommunications resources FF
39、S 4.1.3.3 High-level use cases FFS ETSI ETSI TS 132 531 V13.0.0 (2016-02)83GPP TS 32.531 version 13.0.0 Release 134.1.4 Business Level Requirements 4 REQ_SW_CON_4 The IRPManager shall be able to predefine which specific software version, component or software package shall be downloaded to one or mo
40、re eNodeBs during automated software management procedure. 4.1.4.1 Actor roles FFS 4.1.4.2 Telecommunications resources FFS 4.1.4.3 High-level use cases FFS 4.2 Specification level requirements 4.2.1 Specification level requirement on general SWM REQ_SWM_FUN_1 If a software installation/activation f
41、ails, a software fallback should be done. REQ_SWM_FUN_2 It shall be possible for the IRPManager to retrieve information about the SW which is present in an NE or a group of NEs. REQ_SWM_FUN_3 It shall be possible for the IRPManager to monitor changes in the SW which is present in an NE (newly downlo
42、aded/installed/activated/fallback). REQ_SWM_FUN_4 It shall be possible for the IRPManager to receive alarms in case of failures during the SW-download/installation/activation/fallback. REQ_SWM_FUN_5 Void. REQ_SWM_FUN_6 It shall be possible for the IRPManager to instruct the IRPAgent to trigger a SW
43、fallback in an individual NE or groups of NEs. REQ_SWM_FUN_7 It shall be possible for the IRPManager to instruct the IRPAgent to configure those new mandatory parameters in a new SW version for which no default values are available or are not sufficient, as soon as possible and before any service af
44、fecting errors occur that have impact on the customer and the network. 4.2.1.1 Actor roles FFS 4.2.1.2 Telecommunications resources FFS ETSI ETSI TS 132 531 V13.0.0 (2016-02)93GPP TS 32.531 version 13.0.0 Release 134.2.1.3 Use cases FFS 4.2.1.3.1 Use case 1 FFS 4.2.2 Specification level requirement
45、on Automated SWM REQ_ASWM_FUN_1 It shall be possible for an IRPManager to retrieve - information regarding how an NE or a group of NEs behaves during ASWM, i.e. in which sequence the essential steps of ASWM are executed - information regarding where the IRPManager can interact with ASWM - by suspend
46、ing the ASWM process at one or more ASWM stop points. Steps, their sequence and their stop point qualification are not imposed by the standard. REQ_ASWM_FUN_2 If choices for stop points to suspend the SWM process are offered, then it shall be possible for an IRPManager to choose/select among them wh
47、ere it will suspend (stop) a SWM process (i.e. to ensure fulfillment of pre-conditions for the step like the fulfillment of the presence of required input data for the step). The IRPManager shall be able to read or select or de-select the stop points offered. The IRPManager shall be informed about t
48、he availability of new SW, about the creation and deletion of a profile which is a holder of information regarding the offered SWM steps, the offered sequence of the steps and the configuration steps stop points. The IRPManager should be able to change the content of a created profile and be informe
49、d about the change. REQ_ASWM_FUN_3 It shall be possible for an IRPManager to resume a suspended ASWM process. REQ_ASWM_FUN_4 It shall be possible for IRPManager to retrieve information about the progress of ASWM. REQ_ASWM_FUN_5 The IRPAgent should send a notification when the ASWM process - was suspended - was resumed - was terminated REQ_ASWM_FUN_6 It shall be possible for an IRPManager to terminate a currently ongoing ASWM process for one or multiple NEs. After a termination it is not possible to resume the ASWM process. REQ_ASWM_FUN_7 I
