Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

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

 

6.1.5  Analytics Exposure in Roaming Case |R18|p. 48

6.1.5.1  Generalp. 48

Based on roaming agreements (e.g. SLA), analytics may be exchanged between PLMNs (i.e. HPLMN and VPLMN of a UE served by the NWDAF analytics consumer). In this case, an NWDAF with roaming exchange capability (RE-NWDAF) is used as entry point in a PLMN to exchange analytics in roaming scenario with other PLMNs. It authorizes the analytics request according to roaming agreements, and filters the information exposed to other PLMNs. The roaming architecture is defined in clause 4.3.
The H-RE-NWDAF may provide analytics to the V-RE-NWDAF. The V-RE-NWDAF may provide analytics to the H-RE-NWDAF.
The H-RE-NWDAF or V-RE-NWDAF provides the Nnwdaf_RoamingAnalytics service for that purpose. An RE-NWDAF is the only consumer of these services, i.e. both NWDAF in HPLMN and NWDAF in VPLMN need to have the roaming exchange capability (in other words, be an H-RE-NWDAF or V-RE-NWDAF, respectively) when used as entry point or exit point to exchange analytics in roaming scenario.
V-RE-NWDAF may request or subscribe to HPLMN analytics from the H-RE-NWDAF as described in clause 6.1.5.2, and then the analytics can be leveraged by the 5GC NF in the VPLMN, for example:
  • In home routed roaming scenarios, HPLMN analytics (i.e. slice load level analytics, NF load analytics, etc.) can be leveraged by the AMF in the VPLMN for network slice selection and SMF selection for PDU Session management.
  • UE-related analytics (e.g.. service experience analytics, etc.) can include statistics or predictions for outbound roaming UEs.
H-RE-NWDAF may request or subscribe to VPLMN analytics from the V-RE-NWDAF as described in clause 6.1.5.3, and then the analytics can be leveraged by the 5GC NF in the HPLMN, for example:
  • In home routed roaming scenarios, analytics information with statistics or predictions for outbound roaming UEs can be leveraged by the H-PCF for QoS control of the PDU Session.
  • Analytics (i.e. service experience analytics, slice load level analytics, etc.) can be leveraged by the H-PCF for decision of NSSP in URSP rules provisioned to the UE roaming in the VPLMN.
Up

6.1.5.2  Analytics Exposure from HPLMN to VPLMNp. 49

Figure 6.1.5.2-1 shows the procedure where an V-RE-NWDAF requests network analytics (i.e. slice load level analytics, NF load analytics, service experience analytics, etc.) in HPLMN from a H-RE-NWDAF, upon receiving an analytics information request/subscription from a service consumer NF (e.g. AMF) in VPLMN.
Reproduction of 3GPP TS 23.288, Fig. 6.1.5.2-1: Procedure for analytics exposure from HPLMN to VPLMN
Up
Step 1.
Consumer NF in VPLMN (e.g. AMF) discovers a V-RE-NWDAF as described in clause 5.2 and sends an Analytics request/subscribe (Analytics ID, Analytics Filter Information, Target of Analytics Reporting) to V-RE-NWDAF by invoking a Nnwdaf_AnalyticsInfo_Request service operation or a Nnwdaf_AnalyticsSubscription_Subscribe service operation. For the inbound roaming UE(s) indicated in the Target of Analytics Reporting, V-RE-NWDAF determines based on operator configuration and the requested analytics whether analytics or input data from the HPLMN are required, or the analytics can be derived locally. The subsequent steps only apply if analytics from the HPLMN are required. If input data from the HPLMN are required, the procedures in clause 6.2.11 apply.
Step 2.
V-RE-NWDAF checks the roaming agreements related to analytics from HPLMN to determine if the roaming analytics request/subscribe can be accepted or must be rejected. If the request is rejected, the following steps are skipped.
V-RE-NWDAF discovers a H-RE-NWDAF as described in clause 5.2. V-RE-NWDAF sends a roaming analytics request/subscribe (Analytics ID, Analytics Filter Information, Target of Analytics Reporting) to H-RE-NWDAF by invoking a Nnwdaf_RoamingAnalytics_Request service operation or a Nnwdaf_RoamingAnalytics_Subscribe service operation, based on the Analytics request/subscribe received from the Consumer NF in VPLMN. The Target of Analytics Reporting sent by the V-RE-NWDAF to the H-RE-NWDAF only contains the inbound roaming UE(s).
Step 3a.
H-RE-NWDAF checks the roaming agreements between the HPLMN and the VPLMN, and user consent for analytics as defined in clause 6.2.9 if needed, to determine if the roaming analytics request/subscribe can be accepted or must be rejected. If the roaming analytics request/subscribe is rejected, the following steps are skipped.
If H-RE-NWDAF supports to generate the requested analytics, it collects data from the NF(s) and/or OAM in HPLMN and derives the requested analytics; otherwise steps 3b and 3c are executed.
Step 3b-3c.
[Optional] If the H-RE-NWDAF does not support to generate the requested analytics, it may request/subscribe to other NWDAF(s) in the HPLMN (if available) for the analytics and get corresponding response/notification.
Step 4.
H-RE-NWDAF sends the HPLMN analytics information to the V-RE-NWDAF using either Nnwdaf_RoamingAnalytics_Request response or Nnwdaf_RoamingAnalytics_Notify service operation, depending on the service used in step 2. The H-RE-NWDAF may restrict the exposed analytics information based on HPLMN operator polices.
Step 5.
[Optional] If the Consumer NF also indicates request or subscription of analytics information available in the VPLMN (e.g. via Target of Analytics Reporting) in step 1, V-RE-NWDAF collects data from the NF(s) and/or OAM in VPLMN and derives the requested analytics. The V-RE-NWDAF may perform analytics aggregation with the analytics information received from the H-RE-NWDAF and analytics information generated by itself, based on the analytics request or subscription.
Step 6.
V-RE-NWDAF sends the HPLMN analytics information received in step 4, or the aggregated analytics information if step 5 are performed, to the Consumer NF in VPLMN using either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify service operation, depending on the service used in step 1.
Up

6.1.5.3  Analytics Exposure from VPLMN to HPLMNp. 51

Figure 6.1.5.3-1 shows the procedure that the H-RE-NWDAF requests network analytics (i.e. service experience analytics, slice load level analytics, etc.) in VPLMN from the V-RE-NWDAF, upon receiving an analytics information request/subscription from the NF (e.g. PCF) in HPLMN.
Reproduction of 3GPP TS 23.288, Fig. 6.1.5.3-1: Procedure for analytics exposure from VPLMN to HPLMN
Up
Step 1.
If the Consumer NF in HPLMN (e.g. H-PCF) is aware that the UE(s) indicated in Target of Analytics Reporting is/are outbound roaming UE(s) the Consumer NF discovers a H-RE-NWDAF as described in clause 5.2 and sends an Analytics request/subscribe (Analytics ID, Target of Analytics Reporting, Analytics Filter Information) to H-RE-NWDAF by invoking a Nnwdaf_AnalyticsInfo_Request service operation or a Nnwdaf_AnalyticsSubscription_Subscribe service operation. For the outbound roaming UE(s) indicated in the Target of Analytics Reporting, H-RE-NWDAF determines based on operator configuration and the requested analytics whether analytics or input data from the VPLMN are required, or the analytics can be derived locally. The subsequent steps only apply if analytics from the VPLMN are required. If input data from the VPLMN are required, the procedures in clause 6.2.10 apply.
If the Consumer NF is unaware that the Target of Analytics Reporting includes roaming UE(s) and sends the Analytics request/subscribe to a H-NWDAF which does not support roaming exchange capability, then the H-NWDAF may perform either of the following after determining that the Target of Analytics Reporting includes roaming UE(s) (e.g. by inquiring the AMF(s) serving the UE(s) at the UDM with the Nudm_UECM service):
  • forward the Analytics request/subscribe to a H-RE-NWDAF after discovering a H-RE-NWDAF as described in clause 5.2. The H-NWDAF may include the VPLMN ID in the Analytics request/subscribe; or
  • reject the Analytics request/subscribe with a proper cause value. And the following steps will not be performed.
Step 2.
If PLMN ID of the VPLMN is not included in the Analytics request/subscribe, the H-NWDAF inquires it at the UDM for the UE(s) indicated as Target of Analytics Reporting. The H-RE-NWDAF checks user consent for analytics as defined in clause 6.2.9. H-RE-NWDAF checks the roaming agreements between the HPLMN and the VPLMN to determine if the roaming analytics request/subscription can be accepted or must be rejected. If the request is rejected, the following steps are skipped.
The H-RE-NWDAF discovers the V-RE-NWDAF as described in clause 5.2.
H-RE-NWDAF sends a roaming analytics request/subscribe (Analytics ID, Analytics Filter Information, Target of Analytics Reporting, [NF ID(s)]) to V-RE-NWDAF by invoking a Nnwdaf_RoamingAnalytics_Request service operation or a Nnwdaf_RoamingAnalytics_Subscribe service operation, based on the Analytics request/subscribe received from the Consumer NF in HPLMN. The Target of Analytics Reporting sent by the H-RE-NWDAF to the V-RE-NWDAF only contains the outbound roaming user(s). The H-RE-NWDAF may obtain NF ID(s) of the NF(s) serving the roaming UE(s) in the VPLMN, e.g. AMF ID(s), SMF ID(s), from the UDM and include the NF ID(s) in the analytics request/subscribe.
Step 3a.
V-RE-NWDAF checks the roaming agreements between the HPLMN and the VPLMN, to determine if the roaming analytics request/subscribe can be accepted or must be rejected. If the roaming analytics request/subscribe is rejected, the following steps are skipped.
If V-RE-NWDAF supports to generate the requested analytics, it collects data from the NF(s) serving the roaming UE(s) and/or OAM in VPLMN and derives the analytics; otherwise steps 3b and 3c are executed. The NF(s) serving the roaming UE(s), e.g. AMF(s) or SMF(s), if indicated in step 2, can be used as data source.
Step 3b-3c.
[Optional] If the V-RE-NWDAF does not support to generate the requested analytics, it may request/subscribe to other NWDAF(s) in the VPLMN (if available) for the analytics and get corresponding response/notification(s).
Step 4.
V-RE-NWDAF sends the VPLMN analytics information to the H-RE-NWDAF using either Nnwdaf_RoamingAnalytics_Request response or Nnwdaf_RoamingAnalytics_Notify service operation, depending on the service used in step 2. The V-RE-NWDAF may restrict the exposed analytics information based on VPLMN operator polices.
Step 5.
[Optional] If the Consumer NF also indicates request or subscription of analytics information available in the HPLMN (e.g. via Target of Analytics Reporting) in step 1, H-RE-NWDAF collects data from the NF(s) and/or OAM in HPLMN and derives the analytics. These steps can be executed in parallel with steps 3-4. The H-RE-NWDAF may perform analytics aggregation with the analytics information received from the V-RE-NWDAF and analytics information generated by itself, based on the analytics request or subscription.
Step 6.
H-RE-NWDAF sends the VPLMN analytics information received in step 4, or the aggregated analytics information if step 5 are performed, to the Consumer NF in HPLMN using either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.
If the Analytics request/subscribe is forwarded to the H-RE-NWDAF by a H-NWDAF as described in step 1, the H-NWDAF forwards the analytics information received from the H-RE-NWDAF to the Consumer NF using either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.
Up

6.1.5.4  Contents of Analytics Exposure in roaming casep. 53

When requesting or subscribing to analytics involving one or more roaming UEs, the Consumer NF shall send the request or subscription to an RE-NWDAF belonging to the same PLMN as the Consumer NF. The Consumer NF may indicate the following parameters in the Nnwdaf_AnalyticsInfo_Request service operation or the Nnwdaf_AnalyticsSubscription_Subscribe service operation:
  • The parameters as defined in clause 6.1.3, with the following differences:
    • Parameters related to analytics aggregation, analytics transfer or ML Model selection should not be included;
    • If Target of Analytics Reporting is included and indicates specific UE(s) or a group of UEs, these UEs shall belong to the same HPLMN (if HPLMN analytics are subscribed/requested) or be served by the same VPLMN (if VPLMN analytics are subscribed/requested)
    • Additionally, the following parameters:
      • If the NWDAF service consumer in a VPLMN requests/subscribes to HPLMN analytics, in Analytics Filter Information:
        • [OPTIONAL] PLMN ID of the HPLMN;
        • [OPTIONAL] mapped S-NSSAI of the HPLMN.
        • [OPTIONAL] AOI (in the form of geographical area) in the HPLMN
      • If the NWDAF service consumer in a HPLMN requests/subscribes to VPLMN analytics, in Analytics Filter Information:
        • [OPTIONAL] PLMN ID of the VPLMN
        • [OPTIONAL] AOI (in the form of geographical area) in the VPLMN
Based on the analytics request or subscription from the NWDAF service consumer in the HPLMN, and local configuration, the H-RE-NWDAF may indicate the following parameters in the Nnwdaf_RoamingAnalytics_Request service operation or the Nnwdaf_RoamingAnalytics_Subscribe service operation to the V-RE-NWDAF, for requesting/subscribing to analytics in the VPLMN:
  • Analytics ID;
  • PLMN ID of the HPLMN;
  • Analytics Filter Information:
    • [OPTIONAL] HPLMN S-NSSAI;
    • other Analytics Filter Information (e.g. AOI in the form of geographical area in the VPLMN) as provided by NWDAF service consumer in the HPLMN, if applicable in the VPLMN.
  • [OPTIONAL] NF ID(s) of the NF(s) (e.g. AMF(s), SMF(s)) serving the roaming UE(s) in the VPLMN;
  • other parameters as provided by NWDAF service consumer in the HPLMN, if applicable in the VPLMN.
Based on the analytics request or subscription from the NWDAF service consumer in the VPLMN, and local configuration, the V-RE-NWDAF may indicate the following parameters in the Nnwdaf_RoamingAnalytics_Request service operation or the Nnwdaf_RoamingAnalytics_Subscribe service operation to the H-RE-NWDAF, for requesting/subscribing to analytics in the HPLMN:
  • Analytics ID;
  • PLMN ID of the VPLMN;
  • Analytics Filter Information:
    • [OPTIONAL] HPLMN S-NSSAI;
    • other Analytics Filter Information (e.g. AOI in the form of geographical area in the HPLMN) as provided by NWDAF service consumer in the VPLMN, if applicable in the HPLMN.
  • other parameters as provided by NWDAF service consumer in the VPLMN, if applicable in the HPLMN.
The RE-NWDAF provides the following output information to the consumer RE-NWDAF of the Nnwdaf_RoamingAnalytics_Request service operation or the Nnwdaf_RoamingAnalytics_Notify service operation:
  • The output information as defined in clause 6.1.3, with the following differences:
    • Information related to analytics aggregation (i.e. analytics metadata information) should not be included.
Up

Up   Top   ToC