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   None
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… 
10 ADRF Services  10.1 General  10.2 Nadrf_DataManagement service  10.2.1 General  10.2.2 Nadrf_DataManagement_StorageRequest service operation  10.2.3 Nadrf_DataManagement_StorageSubscriptionRequest service operation  10.2.4 Nadrf_DataManagement_StorageSubscriptionRemoval service operation  10.2.5 Nadrf_DataManagement_RetrievalRequest service operation  10.2.6 Nadrf_DataManagement_RetrievalSubscribe service operation  10.2.7 Nadrf_DataManagement_RetrievalUnsubscribe service operation  10.2.8 Nadrf_DataManagement_RetrievalNotify service operation  10.2.9 Nadrf_DataManagement_Delete  10.3 Nadrf_MLModelManagement service  10.3.1 General  10.3.2 Nadrf_MLModelManagement_StorageRequest service operation  10.3.3 Nadrf_MLModelManagement_Delete service operation  10.3.4 Nadrf_MLModelManagement_RetrievalRequest service operation  A Methods to handle NAT on IPv4 between UE and AF  A.1 Methods to handle NAT on IPv4 between UE and AF  $ Change history 

 

10  ADRF Services |R17|  p. 313

10.1  General  p. 313

Table 10.1-1 shows the ADRF services and ADRF service operations.
ADRF service operations may be used to store data or analytics in the ADRF, retrieve data or analytics from an ADRF, or delete data or analytics from an ADRF.
ADRF service operations may also be used to store ML Model(s) or ML Model address(es) in the ADRF, retrieve ML Model(s) from an ADRF or delete ML Model(s) from an ADRF.
Service Name Service Operations Operation Semantics Example Consumer(s)
Nadrf_DataManagementStorageRequestRequest / ResponseDCCF, NWDAF, MFAF
StorageSubscriptionRequestRequest / ResponseDCCF, NWDAF
StorageSubscriptionRemovalRequest / ResponseDCCF, NWDAF
RetrievalRequestRequest / ResponseDCCF, NWDAF
RetrievalSubscribeSubscribe / NotifyDCCF, NWDAF
RetrievalUnsubscribeDCCF, NWDAF
RetrievalNotifyDCCF, NWDAF
DeleteRequest / ResponseDCCF, NWDAF
Nadrf_MLModelManagementStorageRequestRequest / ResponseNWDAF
RetrievalRequestRequest / ResponseNWDAF
DeleteRequest / ResponseNWDAF
Up

10.2  Nadrf_DataManagement service  p. 313

10.2.1  General  p. 313

Service Description:
This service enables the consumer to store, retrieve and remove data or analytics from an ADRF.

10.2.2  Nadrf_DataManagement_StorageRequest service operation  p. 314

Service operation name:
Nadrf_DataManagement_StorageRequest
Description:
The consumer NF uses this service operation to request the ADRF to store data or analytics. Data or analytics are provided to the ADRF in the request message.
Inputs, Required:
Data with timestamp or Analytics with timestamp to be stored, Service operation, Analytics Specification or Data Specification.
"Service Operation" identifies the service used to obtain the data or analytics from a Data Source (e.g. Namf_EventExposure_Subscribe or Nnwdaf_AnalyticsSubscription_Subscribe).
"Analytics Specification or Data Specification" is the "Service Operation" specific required and optional input parameters that identify the data that was stored (e.g. Analytics ID(s) / Event ID (s), Target of Analytics Reporting or Target of Event Reporting, Analytics Filter or Event Filter, etc.). Service Operations and input parameters are defined in clause 7 for NWDAF and in clause 5.2 of TS 23.502 for the other NFs.
Inputs, Optional:
DataSetTag, DSC information, Storage Handling Information, Data Deletion Notification Endpoint (see clause 6.2B.2).
Outputs Required:
Result Indication.
Outputs, Optional:
Storage Transaction Identifier, DataSetTag(s), Storage Approach.
Up

10.2.3  Nadrf_DataManagement_StorageSubscriptionRequest service operation  p. 314

Service operation name:
Nadrf_DataManagement_StorageSubscriptionRequest
Description:
The consumer (NWDAF or DCCF) uses this service operation to request the ADRF to initiate a subscription for data or analytics (see clause 6.2B.3). Data or analytics provided in notifications as a result of the subsequent subscription by the ADRF are stored in the ADRF.
This service operation provides parameters needed by the ADRF to initiate the subscription (to a DCCF or NWDAF).
Inputs, Required:
Service operation, Analytics Specification or Data Specification, Target NF (or Set) to subscribe to for notifications.
"Service Operation" identifies the service used to request data or analytics from a Data Source (e.g. Namf_EventExposure_Subscribe or Nnwdaf_AnalyticsSubscription_Subscribe)
"Analytics Specification or Data Specification" is the "Service Operation" specific required and optional input parameters that identify the data to be collected (e.g. Analytics ID(s) / Event ID (s), Target of Analytics Reporting or Target of Event Reporting, Analytics Filter or Event Filter, etc.). Service Operations and input parameters are defined in clause 7 for NWDAF and in clause 5.2 of TS 23.502 for the other NFs.
"Target NF (or Set) to subscribe to for notifications" may be a DCCF or NWDAF that can provide the data or analytics
Inputs, Optional:
Formatting Instructions, Processing Instructions, DataSetTag, Storage Handling Information, Data Deletion Notification Endpoint (see clause 6.2B.3).
Formatting Instructions and Processing Instructions are as defined in clause 5A.4.
Outputs Required:
Transaction Reference ID, DataSetTag(s) (if any).
Outputs, Optional:
Storage Approach.
Up

10.2.4  Nadrf_DataManagement_StorageSubscriptionRemoval service operation  p. 315

Service operation name:
Nadrf_DataManagement_StorageSubscriptionRemoval
Description:
The consumer NF uses this service operation to request that the ADRF no longer subscribes to data or analytics it is collecting and storing.
Inputs, Required:
Transaction Reference ID provided in the Nadrf_DataManagement_StorageSubscriptionRequest Output.
Inputs, Optional:
None.
Outputs, Required:
one of the following:
  • Transaction Reference ID provided in the Nadrf_DataManagement_StorageSubscriptionRequest Output; or
  • DataSetTag.
Outputs, Optional:
None.

10.2.5  Nadrf_DataManagement_RetrievalRequest service operation  p. 315

Service operation name:
Nadrf_DataManagement_RetrievalRequest
Description:
The consumer NF uses this service operation to retrieve stored data or analytics from the ADRF. The Nadrf_DataManagement_RetrievalRequest response either contains the data or analytics, or provides instructions for fetching the data or analytics. The Nadrf_DataManagement_RetrievalRequest may be unsolicited (e.g. when the consumer itself has known "Storage Transaction Identifier") or sent in response to a Fetch Instructions received from the ADRF in an Nadrf_DataManagement_RetrievalNotify.
Inputs, Required:
one of the following:
  • Storage Transaction Identifier; or
  • Fetch Correlation ID(s) if the RetrievalRequest is in response to a Fetch Instruction received from the ADRF in an Nadrf_DataManagement_RetrievalNotify; or
  • DataSetTag.
Inputs, Optional:
None.
Outputs Required:
Result Indication.
Outputs, Optional:
Data or Analytics, DSC information.
Up

10.2.6  Nadrf_DataManagement_RetrievalSubscribe service operation  p. 315

Service operation name:
Nadrf_DataManagement_RetrievalSubscribe
Description:
The consumer NF uses this service operation to retrieve stored data or analytics from the ADRF and to receive future notifications containing the corresponding data or analytics received by ADRF.
Inputs, Required:
one of the following:
  • Service Operation, Analytics Specification or Data Specification, Time Window; or
  • DataSetTag.
    "Service Operation" identifies the service used to obtain the data or analytics from a Data Source (e.g. Namf_EventExposure_Subscribe or Nnwdaf_AnalyticsSubscription_Subscribe).
    "Analytics Specification or Data Specification" is the "Service Operation" specific required and optional input parameters that identify the data that was stored (e.g. Analytics ID(s) / Event ID (s), Target of Analytics Reporting or Target of Event Reporting, Analytics Filter or Event Filter, etc.). Service Operations and input parameters are defined in clause 7 for NWDAF and in clause 5.2 of TS 23.502 for the other NFs.
    "Time Window" is the start and stop time when the requested data or analytics was collected. If Time Window includes a period in the future, subsequent notifications containing the requested data or analytics received by the ADRF are sent to the notification endpoint.
    "DataSetTag" indicates all data records stored or being collected and stored by ADRF which are associated to that attribute.
Inputs, Optional:
Fetch flag.
Outputs Required:
Result Indication.
Outputs, Optional:
Subscription Correlation ID.
Up

10.2.7  Nadrf_DataManagement_RetrievalUnsubscribe service operation  p. 316

Service operation name:
Nadrf_DataManagement_RetrievalUnsubscribe
Description:
The consumer NF uses this service operation to request that the ADRF no longer sends data or analytics to a notification endpoint.
Inputs, Required:
Subscription Correlation ID.
Inputs, Optional:
None.
Outputs, Required:
Operation execution result indication.
Outputs, Optional:
None.

10.2.8  Nadrf_DataManagement_RetrievalNotify service operation  p. 316

Service operation name:
Nadrf_DataManagement_RetrievalNotify
Description:
This service operation provides consumers with either data or analytics from an ADRF, or instructions to fetch the data or analytics from an ADRF. The notifications are provided to consumers that have subscribed using the Nadrf_DataManagement_RetrievalSubscribe service operation. Historical data or analytics may be retrieved from ADRF storage and data received in the future be sent when obtained by the ADRF. The ADRF may also notify the consumer instance when Data or Analytics is to be deleted.
Inputs, Required:
Notification Correlation Information, time stamp representing time when ADRF completed preparation of the requested data.
Inputs, Optional:
Requested Data or Analytics, Fetch Instructions, Termination Request, DSC information, Data or Analytics Deletion Alert.
Fetch Instructions indicate whether the data or analytics are to be fetched from the ADRF by the Consumer. If the data or analytics 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).
Data or Analytics are fetched using the Nadrf_DataManagement_RetrievalRequest service operation.
Termination Request indicates that the ADRF requests to terminate the subscription, i.e. ADRF will not provide further notifications related to this subscription, e.g. when all data or analytics requested by the consumer have been provided to the consumer.
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

10.2.9  Nadrf_DataManagement_Delete  p. 317

Service operation name:
Nadrf_DataManagement_Delete
Description:
This service operation instructs the ADRF to delete stored data.
Inputs, Required:
One of the following:
  • Storage Transaction Identifier;
  • Service Operation, Analytics Specification or Data Specification and Time Window; or
  • DataSetTag.
Inputs, Optional:
None.
Outputs, Required:
Operation execution result indication.
Outputs, Optional:
None.

10.3  Nadrf_MLModelManagement service |R18|  p. 317

10.3.1  General  p. 317

Service Description:
This service enables the consumer to store and update, retrieve and remove ML Model(s) or ML Model address(es) from an ADRF.

10.3.2  Nadrf_MLModelManagement_StorageRequest service operation  p. 317

Service operation name:
Nadrf_MLModelManagement_StorageRequest
Description:
The consumer NF uses this service operation to request the ADRF to store or update ML Model(s). ML Model(s) or ML Model address(es) stored in NWDAF containing MTLF are provided to the ADRF in the request message.
Inputs, Required:
NF instance ID of the NWDAF containing MTLF and set of:
  • (Updated) ML Model(s); or
  • the tuple (unique ML Model identifier and ML Model file address and (updated) Storage size required for each of the ML Models).
Inputs, Optional:
Allowed NF instance list for the ML Model identifier, Storage Transaction Identifier.
If Storage Transaction Identifier is included in the input, then ADRF updates the ML Model(s) corresponding to the Storage Transaction Identifier with the updated ML model(s) or updated ML Model file address(es) provided by consumer NF. A new Storage Transaction Identifier may be generated and sent to consumer NF by ADRF after the ML Model update process.
Outputs Required:
  • ML Model storage or ML Model Update Result Indication;
  • [Conditional] one or more tuples of unique ML Model identifier and (updated) ML Model address of Model file stored in ADRF.
Outputs, Optional:
Storage Transaction Identifier.
Up

10.3.3  Nadrf_MLModelManagement_Delete service operation  p. 318

Service operation name:
Nadrf_MLModelManagement_Delete
Description:
This service operation instructs the ADRF to delete stored ML Model file(s) or ML Model address(es).
Inputs, Required:
  • Storage Transaction Identifier; or
  • one or more unique ML Model identifier(s).
When a Storage Transaction Identifier is given, ADRF shall delete all the models that stored in the corresponding storage transaction.
Inputs, Optional:
None.
Outputs, Required:
One of the following:
  • Operation execution result indication (i.e. ML Model deleted, ML Model not found, ML Model found but not deleted), if for all of the involved ML Model(s) have the same execution result.
  • One or more tuples (each includes the unique ML Model identifier and corresponding operation execution result indication).
Outputs, Optional:
None.
Up

10.3.4  Nadrf_MLModelManagement_RetrievalRequest service operation  p. 318

Service operation name:
Nadrf_MLModelManagement_RetrievalRequest
Description:
The consumer NF uses this service operation to request the ADRF to get the ML Model(s) stored in ADRF.
Inputs, Required:
  • Storage Transaction Identifier; or
  • one or more tuples of unique ML Model identifier(s).
Inputs, Optional:
None.
Outputs Required:
Result Indication.
  • [Conditional] one or more tuples of unique ML Model identifiers and ML Model address of Model file stored in ADRF.
Outputs, Optional:
None.
Up

A  Methods to handle NAT on IPv4 between UE and AF |R18|  p. 319

A.1  Methods to handle NAT on IPv4 between UE and AF  p. 319

The following methods can be used to handle the case when there is a NAT between the UE and AF for data collection:
  1. Use IPv6 instead of IPv4 and then use any of the procedures in clauses 6.2.8.2.4.2 to 6.2.8.2.4.4.
  2. Provide GPSI via header enrichment as described in TS 29.244.
  3. Have GPSI as part of the authentication information, or via in-band signalling.
  4. At the establishment of the user plane connection between the UE Application and AF, the AF can use the procedure in clause 4.15.10 of TS 23.502 to get the GPSI.
  5. At the establishment of the user plane connection between the UE Application and a trusted AF, the AF can use the steps 3 to 8 in clause 4.15.10 of TS 23.502, where NEF is replaced by the AF, to retrieve the SUPI of the UE.
In methods 2) to 4), the AF can correlate the UE public IP address and port with the SUPI/GPSI.
Up

$  Change history  p. 320

Up   Top