ETSI TS 132 531-2017 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Software management (SwM) Concepts and Integration Reference Point (IRP) Req.pdf

1、 ETSI TS 132 531 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Software management (SwM); Concepts and Integration Reference Point (IRP) Requirements (3GPP TS 32.531 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 531 V14.

2、0.0 (2017-04)13GPP TS 32.531 version 14.0.0 Release 14Reference RTS/TSGS-0532531ve00 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 S

3、ous-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 present document shal

4、l 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 drive within ETSI S

5、ecretariat. 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present docume

6、nt, 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 writ

7、ten 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 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMT

8、STMand 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. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Mar

9、ks registered and owned by the GSM Association. ETSI ETSI TS 132 531 V14.0.0 (2017-04)23GPP TS 32.531 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 IP

10、Rs, 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 to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are av

11、ailable on the ETSI Web server (https:/ipr.etsi.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

12、are, or may be, or may become, essential to 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

13、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 terminology In the present document “shall“, “shall not“, “shoul

14、d“, “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 except when used in direct citation. ETS

15、I ETSI TS 132 531 V14.0.0 (2017-04)33GPP TS 32.531 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 Conc

16、epts and background 7g34.1 Business Level Requirements. 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 .

17、7g34.1.2.3 High-level use cases 7g34.1.3 Business Level 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 us

18、e cases 8g34.2 Specification level requirements 8g34.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 .

19、 9g34.2.2.2 Telecommunications resources . 9g34.2.2.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

20、 Use cases . 12g34.2.3.3.1 Use case Non-Automated Software Update 12g34.2.3.3.2 Fallback during Non-Automated Software Update . 13g34.2.3.3.3 Backup Network Element Software Configuration Data . 15g34.2.3.3.4 Restore Network Element Software Configuration Data . 15g3Annex A (informative): Change his

21、tory . 16g3History 17g3ETSI ETSI TS 132 531 V14.0.0 (2017-04)43GPP TS 32.531 version 14.0.0 Release 14Foreword 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 ch

22、ange 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 where: x the first digit: 1 presented to TSG for information; 2 pre

23、sented 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 editorial only changes have been incorporated i

24、n the document. Introduction The present document is 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 an

25、d Integration Reference Point (IRP) Requirements; 32.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 ET

26、SI TS 132 531 V14.0.0 (2017-04)53GPP TS 32.531 version 14.0.0 Release 141 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

27、eNBs. 2 References 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,

28、subsequent revisions do 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 3G

29、PP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 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 an

30、d definitions given in TS 32.101 2, TS 32.102 3 and TS 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 TS 21.905 1, in that order. 3.1 Definitions For the purposes of the present d

31、ocument, the terms and definitions given in 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 TR 21.905 1. Software Management: Activities to control which software is available and/or active in a network ele

32、ment. Automated Software Management: Software Management which 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.

33、Non-Automated Software Management: Software Management which 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. Softwar

34、e Installation: Installation of software puts it into a form suitable for activation or use. ETSI ETSI TS 132 531 V14.0.0 (2017-04)63GPP TS 32.531 version 14.0.0 Release 14Software Activation: Activation of software makes it ready to be used and the software starts providing service. 3.2 Abbreviatio

35、ns For the purposes of the present document, the abbreviations 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 S

36、oftware Management NE Network Element SWM Software Management ETSI ETSI TS 132 531 V14.0.0 (2017-04)73GPP TS 32.531 version 14.0.0 Release 144 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 es

37、tablishment of a new NE in the network should be usable also 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 reg

38、arding the software download, installation, activation and fallback 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

39、.3.1 Actor roles FFS 4.1.3.2 Telecommunications resources FFS 4.1.3.3 High-level use cases FFS ETSI ETSI TS 132 531 V14.0.0 (2017-04)83GPP TS 32.531 version 14.0.0 Release 144.1.4 Business Level Requirements 4 REQ_SW_CON_4 The IRPManager shall be able to predefine which specific software version, co

40、mponent or software package shall be downloaded to one or more 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 gener

41、al SWM REQ_SWM_FUN_1 If a software installation/activation fails, 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 monit

42、or changes in the SW which is present in an NE (newly downloaded/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

43、for the IRPManager to instruct the IRPAgent to trigger a SW 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 n

44、ot sufficient, as soon as possible and before any service affecting 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 V14.0.0 (2017-04)93GPP TS 32.531 version 14.0.0 Release 144.2.1.3 Use cases FFS 4.2

45、.1.3.1 Use case 1 FFS 4.2.2 Specification level requirement 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 regard

46、ing where the IRPManager can interact with ASWM - by suspending 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

47、be possible for an IRPManager to choose/select among them where 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 s

48、top points offered. The IRPManager shall be informed about the 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 ab

49、le to change the content of a created profile and be informed 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