Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.288  Word version:  18.6.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…

 

8  DCCF Services |R17|p. 301

8.1  Generalp. 301

Table 8.1-1 shows the DCCF services and DCCF service operations.
Service Name Service Operations Operation Semantics Example Consumer(s)
Ndccf_DataManagementSubscribeSubscribe / NotifyNWDAF, PCF, NSSF, AMF, SMF, NEF, AF, ADRF
UnsubscribeNWDAF, PCF, NSSF, AMF, SMF, NEF, AF, ADRF
NotifyNWDAF, PCF, NSSF, AMF, SMF, NEF, AF, ADRF
FetchRequest / ResponseNWDAF, PCF, NSSF, AMF, SMF, NEF, AF, ADRF
TransferRequest / ResponseDCCF
Ndccf_ContextManagementRegisterRequest / ResponseNWDAF, ADRF
UpdateRequest / ResponseNWDAF, ADRF
DeregisterRequest / ResponseNWDAF, ADRF
Up

8.2  Ndccf_DataManagement servicep. 301

8.2.1  Generalp. 301

Service Description:
This service enables the consumer to subscribe/unsubscribe for data or analytics via the DCCF, be notified about data or analytics exposed by the DCCF, fetch the subscribed data and have data delivered via the DCCF or via a messaging framework. Historical data, or runtime data may be obtained using this service.
When the subscription is accepted by the DCCF, the consumer NF receives from the DCCF an identifier (Subscription Correlation ID) allowing it to further manage (modify, delete) the subscription.
Up

8.2.2  Ndccf_DataManagement_Subscribe service operationp. 302

Service operation name:
Ndccf_DataManagement_Subscribe
Description:
The consumer subscribes to receive data or analytics (which is regarded as a kind of data), or if the data is already requested from the DCCF, then the subscription is updated. The subscription includes service operation specific parameters that identify the data or analytics 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 also request that data be stored in an ADRF or an NWDAF hosting ADRF functionality. When historical data is being obtained, the consumer may specify the ID of the ADRF or NWDAF containing the data.
Inputs, Required:
Service operation, Analytics Specification or Data Specification, Notification Target Address(es) (+ Notification Correlation ID (s)).
Inputs, Optional:
Time Window, NF (or NF-Set) ID, ADRF or NWDAF hosting ADRF information where collected 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.
"Service Operation" identifies the service used by the DCCF 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.
"Time Window" is the start and stop time when the requested data or analytics was or will be collected. If the Time Window includes a period in the past, then the data or analytics collection is "historical". If the Time Window includes a period in the future, the data or analytics collection is "runtime".
NF (or NF-Set) ID specifies a data source that may provide the data.
ADRF Information specifies that collected data or analytics is to be stored in an ADRF and optionally an ADRF or NWDAF ID.
Formatting Instructions and Processing Instructions are as defined in clause 5A.4.
Storage Handling Information is described in clause 5B.1.
Outputs Required:
When the subscription is accepted: Subscription Correlation ID (required for management of this 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, Storage Approach (see clause 5B.1).
Up

8.2.3  Ndccf_DataManagement_Unsubscribe service operationp. 302

Service operation name:
Ndccf_DataManagement_Unsubscribe
Description:
The consumer unsubscribes to DCCF for data or analytics.
Inputs, Required:
Subscription Correlation ID.
Inputs, Optional:
None.
Outputs, Required:
Operation execution result indication.
Outputs, Optional:
The pending (events) data that is not sent to the consumer yet.

8.2.4  Ndccf_DataManagement_Notify service operationp. 303

Service operation name:
Ndccf_DataManagement_Notify
Description:
DCCF notifies the consumer instance of the requested data or analytics (which is regarded as a kind of data) according to the request, or notifies of the availability of previously subscribed Data or Analytics when data delivery is via the DCCF. The DCCF may also notify the consumer instance when Data or Analytics is to be deleted.
Inputs, Required:
Notification Correlation Information, time stamp representing time when DCCF completed preparation of the requested data.
Inputs, Optional:
Requested Data with timestamp or Analytics with timestamp, Fetch Instructions, Termination Request, Data or Analytics Deletion Alert.
Fetch Instructions indicate whether the data or analytics are to be fetched 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).
Termination Request indicates that the DCCF requests to terminate the data management subscription, i.e. DCCF 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 DCCF 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

8.2.5  Ndccf_DataManagement_Fetch service operationp. 303

Service operation name:
Ndccf_DataManagement_Fetch
Description:
Consumer retrieves from the DCCF, data or analytics (which is regarded as a kind of data) as indicated by Ndccf_DataManagement_Notify Fetch Instructions.
Inputs, Required:
Set of Fetch Correlation ID(s).
Inputs, Optional:
None.
Outputs, Required:
Operation execution result indication.
Outputs, Optional:
Requested data or Analytics.

8.2.6  Ndccf_DataManagement_Transfer service operation |R18|p. 304

Service operation name:
Ndccf_DataManagement_Transfer
Description:
Source DCCF transfers UE data subscription context to the target DCCF.
Inputs, Required:
UE data subscription context(UE ID,Data Specification, Notification Target Address(es) (+ Notification Correlation ID(s))).
Inputs, Optional:
Service Operation, Time Window, NF (or NF-Set) ID, ADRF or NWDAF hosting ADRF information where data are to be stored.
Outputs Required:
Subscription Correlation ID, Operation execution result indication.
Outputs, Optional:
None.

8.3  Ndccf_ContextManagement servicep. 304

8.3.1  Generalp. 304

Service Description:
This service enables the consumer to register collected data or analytics with the DCCF.
When the DCCF is configured by the consumer NF, the DCCF supplies a Transaction Reference Id. The Consumer NF may use the Transaction Reference Id in subsequent transactions to update or delate the context in the DCCF.

8.3.2  Ndccf_ContextManagement_Register service operationp. 304

Service operation name:
Ndccf_ContextManagement_Register
Description:
The consumer NF uses this service operation to register data or analytics it is collecting to the DCCF. The registration includes a service operation specific Analytics/Data Specification that identifies the data or analytics that are being collected or has been collected.
Inputs, Required:
Service Operation, Analytics/Data Specification, NWDAF ID or ADRF ID.
Inputs, Optional:
None
  • "Service Operation" identifies the service used to collect the data or analytics from a Data Source (e.g. Namf_EventExposure_Subscribe or Nnwdaf_AnalyticsSubscription_Subscribe).
  • "Analytics/Data Specification" is the "Service Operation" specific required and optional input parameters that identify the collected data (i.e. Analytics ID(s) / Event ID (s), Target of Analytics Reporting or Target of Event Reporting, Analytics Filter or Event Filter, etc.). NF Service Operations and input parameters are defined in clause 7 and clause 5.2 of TS 23.502.
  • NWDAF ID or ADRF ID specify the ADRF or NWDAF with the stored data.
Outputs Required:
Transaction Reference ID(s), Operation execution result indication.
Outputs, Optional:
None.
Up

8.3.3  Ndccf_ContextManagement_Update service operationp. 304

Service operation name:
Ndccf_ContextManagement_Update
Description:
The consumer NF uses this service operation to update a registration of data or analytics to the DCCF. The registration update includes a service operation specific Analytics/Data Specification that identifies the data or analytics that is being collected or has been collected.
Inputs, Required:
Transaction Reference ID(s), Service Operation, Analytics/Data Specification
Inputs, Optional:
None
Outputs Required:
Transaction Reference ID(s), Operation execution result indication.

8.3.4  Ndccf_ContextManagement_Deregister service operationp. 305

Service operation name:
Ndccf_ContextManagement_Deregister
Description:
The consumer NF uses this service operation to delete a registration of data or analytics to the DCCF.
Inputs, Required:
Transaction Reference ID(s)
Inputs, Optional:
None
Outputs Required:
Transaction Reference ID(s), Operation execution result indication.
Outputs, Optional:
None.

Up   Top   ToC