Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.288  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4…   5…   5A…   6…   6.1.3   6.1.4…   6.1.4.4…   6.1.5…   6.1A…   6.1B…   6.1B.2.3…   6.1C   6.2…   6.2.3…   6.2.6…   6.2.6.2   6.2.6.3…   6.2.6.3.3   6.2.6.3.4   6.2.6.3.5   6.2.6.3.6…   6.2.7…   6.2.8…   6.2.9…   6.2.13…   6.2A…   6.2B…   6.2B.3   6.2B.4…   6.2C…   6.2D…   6.2E…   6.2F…   6.3…   6.4…   6.5…   6.6…   6.7…   6.7.3…   6.7.4…   6.7.5…   6.8…   6.9…   6.10…   6.11…   6.12…   6.13…   6.14…   6.16…   6.17…   6.18…   6.19…   6.20…   6.21…   7…   7.4…   7.7…   7.9…   8…   9…   10… 
7.4 Nnwdaf_DataManagement Service  7.4.1 General  7.4.2 Nnwdaf_DataManagement_Subscribe service operation  7.4.3 Nnwdaf_DataManagement_Unsubscribe service operation  7.4.4 Nnwdaf_DataManagement_Notify service operation  7.4.5 Nnwdaf_DataManagement_Fetch service operation  7.5 Nnwdaf_MLModelProvision services  7.5.1 General  7.5.2 Nnwdaf_MLModelProvision_Subscribe service operation  7.5.3 Nnwdaf_MLModelProvision_Unsubscribe service operation  7.5.4 Nnwdaf_MLModelProvision_Notify service operation  7.6 Nnwdaf_MLModelInfo service  7.6.1 General  7.6.2 Nnwdaf_MLModelInfo_Request service operation 
...

 

7.4  Nnwdaf_DataManagement Service |R17|  p. 294

7.4.1  General  p. 294

Service Description:
This service enables the consumer to subscribe/unsubscribe for data exposed by an NWDAF, fetch the subscribed data. Historical data or runtime data may be obtained using this service.

7.4.2  Nnwdaf_DataManagement_Subscribe service operation  p. 294

Service operation name:
Nnwdaf_DataManagement_Subscribe
Description:
The consumer subscribes to receive data, or if the data is already requested from the NWDAF, then the subscription is updated. The subscription includes service operation specific parameters that identify the data to be provided and may include formatting and processing instructions that specify how the data is to be delivered to the consumer. The consumer may request bulked data related to Analytics, as an alternative to asking individual events (i.e. subscription to multiple event IDs to obtain the data required for an analytics generation). The consumer may also request that data be stored in an ADRF. When historical data is being obtained, the consumer may specify the ID of the ADRF or NWDAF containing the data.
Inputs, Required:
Data Specification, Notification Target Address(es) (+ Notification Correlation ID(s)).
When the required data is data for Event IDs received from NFs, the Data Specification includes set of Event IDs, Event Filter Information, Target of Event Reporting.
When the required data is a bulked data for an Analytics ID, the Data Specification includes Target of Reporting with the Analytics ID to generate bulked data, Target of Analytics reporting and Analytics Filter.
Inputs, Optional:
Service Operation, Time Window, NF (or NF-Set) ID, ADRF or NWDAF hosting ADRF information where data are to be stored, ADRF ID where historical data are stored, Formatting Instructions, Processing Instructions, user consent check information (i.e. an indication that the data consumer has checked user consent), purpose for data collection, Storage Handling Information.
Outputs Required:
When the subscription is accepted: Subscription Correlation ID (required for management of the requested subscription). When the subscription is not accepted, an error response.
Outputs, Optional:
First corresponding event report is included, if available (see clause 4.15.1 of TS 23.502), Requested data.
Outputs, Optional:
First corresponding event report is included, if available (see clause 4.15.1 of TS 23.502), Requested data, Storage Approach (see clause 5B.1).
Up

7.4.3  Nnwdaf_DataManagement_Unsubscribe service operation  p. 295

Service operation name:
Nnwdaf_DataManagement_Unsubscribe
Description:
The NF consumer unsubscribes to the NWDAF for data.
Inputs, Required:
Subscription Correlation ID.
Outputs, Required:
Operation execution result indication.
Outputs, Optional:
The pending data that have not been sent to the consumer yet.

7.4.4  Nnwdaf_DataManagement_Notify service operation  p. 295

Service operation name:
Nnwdaf_DataManagement_Notify
Description:
NWDAF notifies the consumer instance of the requested data, or notifies of the availability of previously subscribed Data when delivery is via an NWDAF. The NWDAF may also notify the consumer instance when Data or Analytics is to be deleted.
Inputs, Required:
Notification Correlation ID, time stamp representing time when NWDAF completed preparation of the requested data.
Inputs, Optional:
  • Requested Data with timestamp;
  • Fetch Instructions;
  • Termination Request;
  • Data or Analytics Deletion Alert.
etch Instructions indicate whether the data are to be fetched by the Consumer. If the data are to be fetched, the fetch instructions include an address from which the data may be fetched, one or more Fetch Correlation IDs and a deadline to fetch the data (Fetch Deadline).
Termination Request indicates that NWDAF requests to terminate the data management subscription, i.e. NWDAF will not provide further notifications related to this subscription.
Pending Notification Cause indicates the cause of the pending notification of the stored unsent data, e.g., the data cannot be collected any more due to UE moved out of NWDAF serving area.
Data or Analytics Deletion Alert is described in clause 5B.1.
Outputs, Required:
Operation execution result indication.
Outputs, Optional:
Data or Analytics Retrieval Indication.
The Data or Analytics Retrieval Indication may be sent if the notification contains a Data or Analytics Deletion Alert. The Data or Analytics Retrieval Indication indicates if the consumer will retrieve stored data or analytics prior to deletion (see clause 6.2B.3)
Up

7.4.5  Nnwdaf_DataManagement_Fetch service operation  p. 296

Service operation name:
Nnwdaf_DataManagement_Fetch
Description:
Consumer retrieves from the NWDAF subscribed data (which is regarded as a kind of data), as indicated by Fetch Instructions from Nnwdaf_DataManagement_Notify.
Inputs, Required:
Set of Fetch Correlation ID(s).
Inputs, Optional:
None.
Outputs, Required:
Operation execution result indication.
Outputs, Optional:
Requested data.

7.5  Nnwdaf_MLModelProvision services |R17|  p. 296

7.5.1  General  p. 296

Service Description:
This service enables the consumer to receive a notification when an ML Model matching the subscription parameters becomes available.
When the subscription is accepted by the NWDAF containing MTLF, the consumer NF, receives from the NWDAF an identifier (Subscription Correlation ID) allowing to further manage (modify, delete) this subscription. The modification of ML Model subscription can be enforced by NWDAF based on operator policy and configuration.

7.5.2  Nnwdaf_MLModelProvision_Subscribe service operation  p. 296

Service operation name:
Nnwdaf_MLModelProvision_Subscribe
Description:
Subscribes to NWDAF ML Model provision with specific parameters.
Inputs, Required:
(set of) Analytics ID(s) defined in Table 7.1-2, Notification Target Address (+ Notification Correlation ID).
Inputs, Optional:
  • Subscription Correlation ID (in the case of modification of the ML Model subscription).
  • For each Analytics ID the following parameters may be provided: ML Model Filter Information to indicate the conditions for which ML Model for the analytics is requested and Target of ML Model Reporting as defined in clause 6.2A.2, Requested representative ratio, ML Model Target Period, Use case context, Inference Input Data information, indication of support for multiple ML Models, multiple ML Models Filter Information to indicate the conditions for which multiple ML Models are requested, ML Model Interoperability Information.
  • NF consumer information, ML Model Reporting Information, Time when model is needed, ML Model Monitoring Information (including e.g. desired ML Model metric, ML Model monitoring reporting mode, ML Model Accuracy Threshold, DataSetTag and ADRF ID, ML Model identifier), Expiry time.
Outputs Required:
When the subscription is accepted: Subscription Correlation ID (required for management of this subscription), Expiry time (required if the subscription can be expired based on the operator's policy).
Outputs, Optional:
None.
Up

7.5.3  Nnwdaf_MLModelProvision_Unsubscribe service operation  p. 297

Service operation name:
Nnwdaf_MLModelProvision_Unsubscribe
Description:
unsubscribe to NWDAF ML Model provision.
Inputs, Required:
Subscription Correlation ID.
Inputs, Optional:
None.
Outputs, Required:
Operation execution result indication.
Outputs, Optional:
None.

7.5.4  Nnwdaf_MLModelProvision_Notify service operation  p. 297

Service operation name:
Nnwdaf_MLModelProvision_Notify
Description:
NWDAF notifies the ML Model information to the consumer instance which has subscribed to the specific NWDAF service.
Inputs, Required:
Notification Correlation Information, Set of:
  • the tuple (Analytics ID, one or more tuples of unique ML Model identifier and the information as defined in clause 6.2A.2).
Inputs, Optional:
ML Model Accuracy Information.
Outputs, Required:
Operation execution result indication.
Outputs, Optional:
None.

7.6  Nnwdaf_MLModelInfo service |R17|  p. 297

7.6.1  General  p. 297

Service description:
this service enables the consumer to request and get from NWDAF containing MTLF ML Model Information.

7.6.2  Nnwdaf_MLModelInfo_Request service operation  p. 297

Service operation name:
Nnwdaf_MLModelInfo_Request
Description:
The consumer requests NWDAF ML Model Information.
Inputs, Required:
(Set of) Analytics ID(s) defined in Table 7.1-2.
Inputs, Optional:
  • For each Analytics ID the following parameters may be provided: ML Model Filter Information to indicate the conditions for which ML Model for the analytics is requested and Target of ML Model Reporting as defined in clause 6.2A.2, Requested representative ratio, ML Model Target Period, Use case context, Inference Input Data Information, indication of support for multiple ML Models, multiple ML Models Filter Information to indicate the conditions for which multiple ML Models are requested, ML Model Interoperability Information.
  • Vendor ID.
  • ML Model Accuracy Monitoring Information.
Outputs, Required:
Set of:
  • the tuple (Analytics ID, one or more tuples of unique ML Model identifier and the information as defined in clause 6.2A.2.
Outputs, Optional:
ML Model Accuracy Information.
Up

Up   Top   ToC