Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.288  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   4…   5…   5A…   6…   6.1.4…   6.1.4.4…   6.1A…   6.1B…   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.2A…   6.2B…   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…   7…   8…   9…   10…

 

6.2A  Procedure for ML Model Provisioning |R17|p. 93

6.2A.0  Generalp. 93

This clause presents the procedure for the ML Model provisioning.
In this Release of the specification an NWDAF containing AnLF is locally configured with (a set of) IDs of NWDAFs containing MTLF and the Analytics ID(s) supported by each NWDAF containing MTLF to retrieve trained ML models. An NWDAF containing AnLF may use NWDAF discovery for NWDAF containing MTLF within the set of configured IDs of NWDAFs containing MTLF, if necessary. An NWDAF containing MTLF may determine that further training for an existing ML model is needed when it receives the ML model subscription or the ML model request.
Up

6.2A.1  ML Model Subscribe/Unsubscribep. 93

The procedure in Figure 6.2A.1-1 is used by an NWDAF service consumer, i.e. an NWDAF containing AnLF to subscribe/unsubscribe at another NWDAF, i.e. an NWDAF containing MTLF, to be notified when ML Model Information on the related Analytics becomes available, using Nnwdaf_MLModelProvision services as defined in clause 7.5. The ML Model Information is used by an NWDAF containing AnLF to derive analytics. The service is also used by an NWDAF to modify existing ML Model Subscription(s). An NWDAF can be at the same time a consumer of this service provided by other NWDAF(s) and a provider of this service to other NWDAF(s).
Reproduction of 3GPP TS 23.288, Fig. 6.2A.1-1: ML Model for analytics subscribe/unsubscribe
Up
Step 1.
The NWDAF service consumer (i.e. an NWDAF containing AnLF) subscribes to, modifies, or cancels subscription for a (set of) trained ML Model(s) associated with a (set of) Analytics ID(s) by invoking the Nnwdaf_MLModelProvision_Subscribe / Nnwdaf_MLModelProvision_Unsubscribe service operation. The parameters that can be provided by the NWDAF service consumer are listed in clause 6.2A.2.
When a subscription for a trained ML model associated with an Analytics ID is received, the NWDAF containing MTLF may:
  • determine whether an existing trained ML Model can be used for the subscription; or
  • determine whether triggering further training for an existing trained ML models is needed for the subscription.
If the NWDAF containing MTLF determines that further training is needed, this NWDAF may initiate data collection from NFs, (e.g. AMF/DCCF/ADRF), UE Application (via AF) or OAM as described in clause 6.2, to generate the ML model.
If the service invocation is for a subscription modification or subscription cancelation, the NWDAF service consumer includes an identifier (Subscription Correlation ID) to be modified in the invocation of Nnwdaf_MLModelProvision_Subscribe.
Step 2.
If the NWDAF service consumer subscribes to a (set of) trained ML model(s) associated to a (set of) Analytics ID(s), the NWDAF containing MTLF notifies the NWDAF service consumer with the trained ML Model Information (containing a (set of) file address of the trained ML model) by invoking Nnwdaf_MLModelProvision_Notify service operation. The content of trained ML Model Information that can be provided by the NWDAF containing MTLF is specified in clause 6.2A.2.
The NWDAF containing MTLF also invokes the Nnwdaf_MLModelProvision_Notify service operation to notify an available re-trained ML model when the NWDAF containing MTLF determines that the previously provided trained ML Model required re-training at step 1.
When the step 1 is for a subscription modification (i.e., including Subscription Correlation ID), the NWDAF containing MTLF may provide either a new trained ML model different to the previously provided one, or re-trained ML model by invoking Nnwdaf_MLModelProvision_Notify service operation.
Up

6.2A.2  Contents of ML Model Provisioningp. 94

The consumers of the ML model provisioning services (i.e. an NWDAF containing AnLF) as described in clause 7.5 and clause 7.6 may provide the input parameters as listed below:
  • Information of the analytics for which the requested ML model is to be used, including:
    • A list of Analytics ID(s): identifies the analytics for which the ML model is used.
    • [OPTIONAL] ML Model Filter Information: enables to select which ML model for the analytics is requested, e.g. S-NSSAI, Area of Interest. Parameter types in the ML Model Filter Information are the same as parameter types in the Analytics Filter Information which are defined in procedures.
    • [OPTIONAL] Target of ML Model Reporting: indicates the object(s) for which ML model is requested, e.g. specific UEs, a group of UE(s) or any UE (i.e. all UEs).
    • ML Model Reporting Information with the following parameters:
      • (Only for Nnwdaf_MLModelProvision_Subscribe) ML Model Reporting Information Parameters as per Event Reporting Information Parameter defined in Table 4.15.1-1, TS 23.502.
    • [OPTIONAL] ML Model Target Period: indicates time interval [start, end] for which ML model for the Analytics is requested. The time interval is expressed with actual start time and actual end time (e.g. via UTC time).
    • A Notification Target Address (+ Notification Correlation ID) as defined in TS 23.502, clause 4.15.1, allowing to correlate notifications received from the NWDAF containing MTLF with this subscription.
The NWDAF containing MTLF provides to the consumer of the ML model provisioning service operations as described in clause 7.5 and clause 7.6, the output information as listed below:
  • (Only for Nnwdaf_MLModelProvision_Notify) The Notification Correlation Information.
  • ML Model Information, which includes the ML model file address (e.g. URL or FQDN) for the Analytics ID(s).
  • [OPTIONAL] Validity period: indicates time period when the provided ML Model Information applies.
  • [OPTIONAL] Spatial validity: indicates Area where the provided ML Model Information applies.
Up

6.2A.3  ML Model requestp. 95

The procedure in Figure 6.2A.3-1 is used by an NWDAF service consumer, i.e. an NWDAF containing AnLF to request and get from another NWDAF, i.e. an NWDAF containing MTLF ML Model Information, using Nnwdaf_MLModelInfo services as defined in clause 7.6. The ML Model Information is used by an NWDAF containing AnLF to derive analytics. An NWDAF can be at the same time a consumer of this service provided by other NWDAF(s) and a provider of this service to other NWDAF(s).
Reproduction of 3GPP TS 23.288, Fig. 6.2A.3-1: ML model Request
Up
Step 1.
The NWDAF service consumer (i.e., an NWDAF containing AnLF) requests a (set of) ML Model(s) associated with a (set of) Analytics ID(s) by invoking Nnwdaf_MLModelInfo_Request service operation. The parameters that can be provided by the NWDAF Service Consumer are listed in clause 6.2A.2.
When a request to an ML Model Information for the Analytics is received, the NWDAF containing MTLF may:
  • determine whether an existing trained ML Model can be used for the request; or
  • determine whether triggering further training for an existing trained ML models is needed for the request.
If the NWDAF containing MTLF determines that further training is needed, this NWDAF may initiate data collection from NFs, (e.g. AMF/DCCF/ADRF), UE Application (via AF) or OAM as described in clause 6.2, to generate the ML model.
Step 2.
The NWDAF containing MTLF responds with the ML Model Information (containing a (set of) file address of the trained ML model) to the NWDAF service consumer by invoking Nnwdaf_MLModelInfo_Request response service operation. The content of ML Model Information that can be provided by the NWDAF containing MTLF is specified in clause 6.2A.2.
Up

Up   Top   ToC