To activate the production of the requested data, a MnS consumer has to
create a 'ManagementDataCollection' object instance on the MnS producer.
The MnS producer will derive multiple jobs ('PerfMetricJob',
'TraceJob') from a single 'ManagementDataCollection' job for collecting
the required management data. Once it receives the measurement from
multiple sources, it consolidates the data into a set of management data
for reporting.
The attribute 'collectionTimeWindow' specifies the time window for which
the management data should be reported.
The attribute 'reportingCtrl' specifies the method and associated
control parameters for reporting the produced management data to MnS
consumers. Three methods are available: file-based reporting with
selection of the file location by the MnS producer, file-based
reporting with selection of the file location by the MnS consumer and
stream-based reporting.
The attribute 'dataScope' configures, whether the management data
should be reported per S-NSSAI or per 5QI, if applicable.";
create a ManagementDataCollection object instance on the MnS producer.
The attribute jobId is used to identify a management data collection
request.
The production and reporting of the management data can be constrained
by conditions such that only when the conditions are satisfied shall
management data collection be enabled. For example, a MnS consumer can
request to create two ManagementDataCollection instances. One can be
configured with high data producing and reporting period on a set of
conditions (e.g, to reduce transmission cost when network performance
metric is in normal range). Another can be configured with low data
producing and reporting period on another set of conditions (e.g. to
enable network optimization when network performance metric is in
abnormal range).
The MnS producer may derive multiple jobs (PerfMetricJob, TraceJob)
from a single ManagementDataCollection job for collecting the required
management data. The jobId of the request is used to identify the
output. The value is also used to correlate the derived jobs which
will have the same jobId value as the ManagementDataCollection.
If the MnS producer receives the collected data from multiple sources,
it will consolidate the data into a set of management data for
reporting based on the value of the attribute consolidateOutput.
For consolidation of file-based management data the attribute
consolidateOutput controls:
- True: the MnS Producer will combine the file output from jobs used
to collect the required management data into a single output file as
follows:
- File is in compressed format, i.e. zip.
- File shall contain individual output files from each configured job
- Each file retains its original filename
- Each file retains it original content
- Consolidated filename uses naming convention defined in,
TS 28.532 clause 11.3.2.1.4 with the following:
- <Type> is a combination of the management data types included in
the consolidated output
- <UniqueIdList> is omitted
- False: the MnS Producer will not combine the output from jobs used to collect the required management data. The MnS Consumer will receive separate output from the derived jobs.
Subject to the reporting method, the MnS Consumer may receive file
related notifications. When consolidated output is selected the
MnS Producer will create file notifications for the consolidated files.
When consolidated output is not selected, the MnS Producer will create
the notification subscriptions on behalf of the MnS Consumer and the
MnS Consumer will receive notifications directly from the derived jobs.
The attribute collectionTimeWindow specifies the time window for which
the management data should be reported. The attributes startTime and
the endTime can be in the past, present or in the future.
The attribute reportingCtrl specifies the method and associated control
parameters for reporting the produced management data to MnS consumers.
Three methods are available: file-based reporting with selection of the
file location by the MnS producer, file-based reporting with selection
of the file location by the MnS consumer and stream-based reporting.
The attribute dataScope configures, whether the management data should
be reported per S-NSSAI or per 5QI or per PLMN, if applicable.
The attribute processMonitor allows the MnS consumer to monitor the
status of the management data collection represented by the object
ManagementDataCollection.
The MnS producer indicates in the attribute progressStateInfo the
