4 Management service template (stage 1)

32.1603GPPManagement and orchestrationManagement service templateRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

4.1 General

This template shall be used for the production of all requirement specifications for management and orchestration of 3GPP networks.

Instructions in italics below shall not be included in the requirements specifications.

Usage of fonts shall be according to the 3GPP drafting rules in TR 21.801 [5] for a TS (with some basic examples given in the 3GPP TS template).

4.2 Template for requirement specifications

X Management capabilities

X.a <Management capability name>

The management capability name above shall be replaced with the name of the management capability which is to be specified.

X.a.1 Description

For production of the contents of this clause, describe general information about the management capability.

X.a.2 Use cases

X.a.2.b <XXX Use case> <label>

For production of the contents of this clause, describe the motivation for one or more of the requirements in R4.c (referring to the requirement label(s)). The use case should also be labelled. The use case is not to clarify how to use a certain feature, and detailed sequence diagrams are not needed for a use case. The use case is to describe what are the benefits of the capability, what it is good for. High level diagrams including sequence diagrams may still be included if needed in order to better describe the use cases and motivate the corresponding requirements.

The format of the use case label is UC-xx-yy, where xx represents the abbreviation of the management capability name, yy is the serial number under the corresponding management capability category.

X.a.3 Requirements

For production of the contents of this subclause, describe the management capability requirements which are exposed to the consumer. Each requirement shall have a requirement label.

The format of the requirement label is REQ-xx-yy-zz, where xx is a unique abbreviation of the service/function, yy is MC (Management Capability) and zz is the serial number under the corresponding management capability category.

All requirements shall be motivated by either a use case or a textual motivation (also figures are allowed).

Editor’s Notes: The format of the requirement label should align with 3GPP-wide labels if there is any decision on that (currently under SA discussion).

Requirement label	Description	Related use case(s)/Motivation