Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TS 32.155
Telecommunication Management –
Requirements Template

Use "3GPP‑Page" to get the Word version, and "ETSI‑search" to get the PDF version
V16.0.0 (PDF)  2020/06  10 p.
V15.0.0  2018/06  10 p.
V14.1.0  2017/12  10 p.
V13.1.1  2016/12  10 p.
V12.0.0  2014/10  10 p.
V11.0.0  2012/09  10 p.
V10.0.0  2011/04  10 p.
V9.0.0  2009/12  10 p.
V8.3.0  2009/03  10 p.
Rapporteur:
Mr. Tovinger, ThomasEricsson LM

Content for  TS 32.155  Word version:  16.0.0

Here   Top

0  IntroductionWord‑p. 4

The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
TS 32.150:
Integration Reference Point (IRP) Concept and definitions;
TS 32.153:
Integration Reference Point (IRP) technology specific templates;
TS 32.154:
Backward and Forward Compatibility (BFC); Concept and definitions;
TS 32.155:
Requirements template;
TS 32.156:
Telecommunication management; Fixed Mobile Convergence (FMC) Model Repertoire.
TS 32.157:
Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template.
Up

1  ScopeWord‑p. 5

The present document contains the template to be used for the production of all Requirements TSs for the 3GPP Telecommunication management.
This template is mainly based on the requirements template (mainly Annex A) in the ITU-T M.3020 recommendation [6].

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, 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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 32.101: "Telecommunication management; Principles and high level requirements".
[3]
TS 32.102: "Telecommunication management; Architecture".
[4]
TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
[5]  Void.
[6]
ITU-T Recommendation M.3020 (07/2011): "Management interface specification methodology".
[7]
3GPP TS 32.761: "E-UTRAN Network Resource Model (NRM) IRP; Requirements".
[8]  Void.
[9]
TS 32.157: "Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template".
Up

3  Definitions, abbreviations

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905, TS 32.101, TS 32.102, TS 32.150, TS 32.157 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.
Up

3.2  Abbreviations

For the purposes of the present document, the abbreviations given in TR 21.905, TS 32.101, TS 32.102, TS 32.150 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.
IRP
Integration Reference Point
IS
Information Service
Up

4  Requirements templateWord‑p. 6

4.0  General

This template is mainly based on the requirements template (mainly Annex A) in the ITU-T M.3020 recommendation [6], and shall be used for the production of all Requirements TSs for the 3GPP Telecommunication management. The template contains two options: Option 1 specified in subclause 4.1, which shall be used for all high-level Requirements TSs for the 3GPP Telecommunication management, and option 2 specified in subclause 4.2, which shall be used for all Integration Reference Point (IRP) specific Requirements TSs such as 3GPP TS 32.761 [7].
Instructions in italics below shall not be included in the Requirements TS.
The introductory clauses (from clause 1 to clause 3) for the Requirements TS should be taken from the 3GPP TS template (i.e. not this requirements template) - see http://www.3gpp.org/ftp/Information/TS_TR_Templates/.
Use the "Heading 1" paragraph style for clause 4, 5 and 6 in the Requirements TS.
Usage of fonts shall be according to the 3GPP TS template.
Up

4.1  Template for high-level Requirements TSs

4  Concepts and background
For production of the contents of this clause, follow the template instructions in ITU-T M.3020 [6] subclause A.2, template clause "1 Concepts and background".
5  Business level requirements
For production of the contents of this subclause, follow the template instructions in ITU-T M.3020 [6] subclause A.2, template clause "2 Business level requirements".
Note on the Use case template: All occurrences of "(*)" in the first column "Use Case Stage" of the Use case template in table A.2, as well as the last row with a NOTE at the end of the table, shall not be included in the requirements TS as these are only template instructions to the TS author. For example, "Goal(*)" shall be converted to "Goal" in the TS. Likewise, for all occurrences of "(M|O)", a choice of M or O shall be made, leaving it as either "(M)" or "(O)" in the TS. For example, "Step n (M|O)" shall be converted to "Step n (M)" or "Step n (O)" in the TS.
6  Specification level requirements
For production of the contents of this subclause, follow the template instructions in ITU-T M.3020 [6] subclause A.2, template clause "3 Specification level requirements".
Note on the Use case template: All occurrences of "(*)" in the first column "Use Case Stage" of the Use case template in table A.2, as well as the last row with a NOTE at the end of the table, shall not be included in the requirements TS as these are only template instructions to the TS author. For example, "Goal(*)" shall be converted to "Goal" in the TS. Likewise, for all occurrences of "(M|O)", a choice of M or O shall be made, leaving it as either "(M)" or "(O)" in the TS. For example, "Step n (M|O)" shall be converted to "Step n (M)" or "Step n (O)" in the TS.
Up

4.2  Template for Integration Reference Point (IRP) specific Requirements TSsWord‑p. 7

4  Concepts and background
For production of the contents of this clause, follow the template instructions in ITU-T M.3020 [6] subclause A.3, template clause "1 Concepts and background".
5  Requirements
For production of the contents of this subclause, follow the template instructions in ITU-T M.3020 [6] subclause A.3, template clause "2 Requirements".
Up

$  Change HistoryWord‑p. 8


Up   Top