Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.288  Word version:   16.3.0

Top   Up   Prev   Next
1…   4…   6…   6.2…   6.3…   6.4…   6.5…   6.6…   6.7…   6.7.3…   6.7.4…   6.7.5…   6.8…   6.9…   7…

 

6  Procedures to Support Network Data AnalyticsWord-p. 9
6.0  General
This clause specifies procedures to support network data analytics function.
Clause 6.1 and clause 6.2 specify generic procedures which apply to all type of analytics, while clause 6.3 and onwards specify procedures specific to some type of analytics.
6.1  Procedures for analytics exposure
6.1.1  Analytics Subscribe/Unsubscribe
6.1.1.1  Analytics subscribe/unsubscribe by NWDAF service consumer
This procedure is used by any NWDAF service consumer (e.g. including NFs/OAM) to subscribe/unsubscribe at NWDAF to be notified on analytics information, using Nnwdaf_AnalyticsSubscription service defined in clause 7.2. This service is also used by an NWDAF service consumer to modify existing analytics subscription(s). Any entity can consume this service as defined in clause 7.2.
Up
Step 1.
The NWDAF service consumer subscribes to or cancels subscription to analytics information by invoking the Nnwdaf_AnalyticsSubscription_Subscribe/ Nnwdaf_AnalyticsSubscription_Unsubscribe service operation. The parameters that can be provided by the NWDAF service consumer are listed in clause 6.1.3.
When a subscription to analytics information is received, the NWDAF determines whether triggering new data collection is needed.
If the service invocation is for a subscription modification, the NF service consumer includes an identifier (Subscription Correlation ID) to be modified in the invocation of Nnwdaf_AnalyticsSubscription_Subscribe.
Step 2.
If NWDAF service consumer subscribes to analytics information, the NWDAF notifies the NWDAF service consumer with the analytics information by invoking Nnwdaf_AnalyticsSubscription_Notify service operation, based on the request from the NWDAF service consumer, e.g. Analytics Reporting Parameters.
Up
6.1.1.2  Analytics subscribe/unsubscribe by AFs via NEF
The analytics exposure to AFs may be performed via NEF by using analytics subscription to NWDAF.
Figure 6.1.1.2-1 illustrates the interaction between AF and NWDAF performed via the NEF.
Up
Step 0.
NEF controls the analytics exposure mapping among the AF identifier with allowed Analytics ID, and associated inbound restrictions (i.e, applied to subscription of the Analytics ID for an AF) and/or outbound restrictions (i.e., applied to notification of Analytics ID to an AF).
In this Release, AF is configured with the appropriated NEF to subscribe to analytics information, the allowed Analytics ID(s), and with allowed inbound restrictions (i.e., parameters and/or parameter values) for subscription to each Analytics ID.
Step 1.
The AF subscribes to or cancels subscription to analytics information via NEF by invoking the Nnef_AnalyticsExposure_Subscribe/ Nnef_AnalyticsExposure_Unsubscribe service operation defined in TS 23.502. If the AF wants to modify an existing analytics subscription at NEF, it includes an identifier (Subscription Correlation ID) to be modified in the invocation of Nnef_AnalyticsExposure_Subscribe. If the analytics information subscription is authorized by the NEF, the NEF proceeds with the steps below.
Step 2.
Based on the request from the AF, the NEF subscribes to or cancels subscription to analytics information by invoking the Nnwdaf_AnalyticsSubscription_Subscribe/ Nnwdaf_AnalyticsSubscription_Unsubscribe service operation.
If the parameters and/or parameters values of the AF request comply with the inbound restriction in the analytics exposure mapping, NEF forwards in the subscription to NWDAF service the Analytics ID, parameters and/or parameters values from the AF request.
If the request from AF does not comply with the restrictions in the analytics exposure mapping, NEF may apply restrictions to the subscription request to NWDAF (e.g., restrictions to parameters or parameter values of the Nnwdaf_AnalyticsSubscription_Subscribe service operations), based on operator configuration and/or may apply parameter mapping (e.g. geo coordinate mapping to TA(s)/Cell-id(s)).
The NEF records the association of the analytics request from the AF and the analytics request sent to the NWDAF.
The NEF selects an NWDAF that supports analytics information requested by the AF using the NWDAF discovery procedure defined in TS 23.501.
If the AF request is for a modification of the existing analytics subscription(s), the NEF invokes Nnwdaf_AnalyticsSubscription_Subscribe to modify the analytics subscription identified by an identifier (Subscription Correlation ID) associated with the AF.
Step 3.
If the NEF has subscribed to analytics information, the NWDAF notifies the NEF with the analytics information by invoking Nnwdaf_AnalyticsSubscription_Notify service operation.
Step 4.
If the NEF receives the notification from the NWDAF, the NEF notifies the AF with the analytics information by invoking Nnef_AnalyticsExposure_Notify service operation defined in TS 23.502. NEF may apply outbound restrictions to the notifications to AFs (e.g., restrictions to parameters or parameter values of the Nnef_AnalyticsExposure_Notify service operation) based on analytics exposure mapping and may apply parameter mapping for external usage (e.g. TA(s), Cell-id(s) to geo coordinate).
Up
6.1.2  Analytics RequestWord-p. 11
6.1.2.1  Analytics request by NWDAF service consumer
This procedure is used by the NWDAF service consumer (e.g. including NFs/OAM) to request and get from NWDAF analytics information, using Nnwdaf_AnalyticsInfo service defined in clause 7.3.
Up
Step 1.
The NWDAF service consumer requests analytics information by invoking Nnwdaf_AnalyticsInfo_Request service operation. The parameters that can be provided by the NWDAF service consumer are listed in clause 6.1.3.
When a request for analytics information is received, the NWDAF determines whether triggering new data collection is needed.
Step 2.
The NWDAF responds with analytics information to the NWDAF service consumer.
Up
6.1.2.2  Analytics request by AFs via NEF
The analytics exposure to AFs may be performed via NEF by using analytics request to NWDAF.
Figure 6.1.2.2-1 illustrates the interaction between AF and NWDAF performed via the NEF.
Up
Step 0.
NEF controls the analytics exposure mapping among the AF identifier with allowed Analytics ID(s), and associated inbound restrictions (i.e., applied to the Analytics ID requested by AF, and/or outbound restrictions (i.e., applied to the response of Analytics ID to AF).
In this Release, AF is configured, e.g., via static OAM configuration, with the appropriated NEF to subscribe to analytics information, the allowed Analytics ID(s), and with allowed inbound restrictions (i.e., parameters and/or parameter values) for requesting each Analytics ID.
Step 1.
The AF requests to receive analytics information via NEF by invoking the Nnef_AnalyticsExposure_Fetch service operation defined in TS 23.502. If the analytics information request is authorized by the NEF, the NEF proceeds with the steps below.
Step 2.
Based on the request from the AF, the NEF requests analytics information by invoking the Nnwdaf_AnalyticsInfo_Request service operation.
If the parameters and/or parameters values of the AF request comply with the restriction in the analytics exposure mapping, NEF forwards in the subscription to NWDAF service the Analytics ID, parameters and/or parameters values from AF in the request to NWDAF.
If the request from AF does not comply with the restrictions in the analytics exposure mapping, NEF may apply restrictions to the request to NWDAF (e.g., restrictions to parameters or parameter values of the Nnwdaf_AnalyticsInfo_Request service operations) based on operator configuration and/or may apply parameter mapping (e.g. geo coordinate mapping to TA(s), Cell-id(s)).
The NEF records the association of the analytics request from the AF and the analytics request sent to the NWDAF.
The NEF selects an NWDAF that supports analytics information requested by the AF using the NWDAF discovery procedure defined in TS 23.501.
Step 3.
The NWDAF responds with the analytics information to the NEF.
Step 4.
The NEF responds with the analytics information to the AF. NEF may apply restrictions to the response to AFs (e.g., restrictions to parameters or parameter values of the Nnef_AnalyticsExposure_Fetch response service operation) based on operator configuration.
Up
6.1.3  Contents of Analytics ExposureWord-p. 12
The consumers of the Nnwdaf_AnalyticsSubscription or Nnwdaf_AnalyticsInfo service operations described in clause 7 provide the following input parameters listed below.
  • A list of Analytics ID(s): identifies the requested analytics.
  • Analytics Filter Information: indicates the conditions to be fulfilled for reporting Analytics Information. This set of optional parameter types and values enables to select which type of analytics information is requested. Analytics Filter Information are defined in procedures.
  • Target of Analytics Reporting: indicates the object(s) for which Analytics information is requested, entities such as specific UEs, a group of UE(s) or any UE (i.e. all UEs).
  • (Only for Nnwdaf_AnalyticsSubscription) A Notification Target Address (+ Notification Correlation ID) as defined in TS 23.502, clause 4.15.1, allowing to correlate notifications received from NWDAF with this subscription.
  • Analytics Reporting Information with the following parameters:
    • (Only for Nnwdaf_AnalyticsSubscription) Analytics Reporting Parameters as per Event Reporting parameters defined in Table 4.15.1-1, TS 23.502.
    • (Only for Nnwdaf_AnalyticsSubscription) Reporting Thresholds, which indicate conditions on the level of each requested analytics that when reached shall be notified by the NWDAF. A matching direction may be provided such as below, above, or crossed. If no matching direction is provided, the default direction is crossed.
    • Analytics target period: time interval [start..end], either in the past (both start time and end time in the past) or in the future (both start time and end time in the future). An Analytics target period in the past is a request or subscription for statistics. An Analytics target period in the future is a request or subscription for predictions. The time interval is expressed with actual start time and actual end time (e.g. via UTC time). When the Analytics Reporting Parameters indicate a periodic reporting mode, the time interval can also be expressed as positive or negative offsets to the reporting time. By setting start time and end time to the same value, the consumer of the analytics can request analytics or subscribe to analytics for a specific time rather than for a time interval.
    • Preferred level of accuracy of the analytics (e.g. Low/High).
    • (Only for Nnwdaf_AnalyticsInfo_Request) Time when analytics information is needed (if applicable). If the time is reached the consumer does not need to wait for the analytics information any longer, yet the NWDAF may send an error response to the consumer.
    • [OPTIONAL] Maximum number of objects requested by the consumer (max) to limit the number of objects in a list of analytics per Nnwdaf_AnalyticsSubscription_Notify or Nnwdaf_AnalyticsInfo_Request response.
    • [OPTIONAL] Maximum number of SUPIs (SUPImax) requested by the consumer to limit the number of SUPIs in an object. When SUPImax is not provided, the NWDAF shal return all SUPIs concerned by the analytics object. When SUPImax is set to 0, the NWDAF shall not provide any SUPI.
    NOTE:
    The feasibility of the parameter "Time when analytics are needed" will be checked by stage 3.
The NWDAF provides to the consumer of the Nnwdaf_AnalyticsSubscription or Nnwdaf_AnalyticsInfo service operations described in clause 7, the output information listed below:
  • (Only for Nnwdaf_AnalyticsSubscription) The Notification Correlation Information.
  • For each Analytics ID the analytics information in the requested Analytics target period.
  • In addition, the following additional information:
    • Timestamp of analytics generation, which allows consumers to decide until when the received information shall be used. For instance, an NF can deem a received notification from NWDAF for a given feedback as invalid based on this timestamp;
    • Validity period, which defines the time period for which the analytics information is valid.
    • Probability assertion: level of certainty, confidence in statistics/prediction.
Up

Up   Top   ToC