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:  18.4.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.1C NWDAF Registration/Deregistration in UDM 
...

 

6.1C  NWDAF Registration/Deregistration in UDM |R17|  p. 68

6.1C.1  General  p. 68

The procedures in this clause are applicable to UE-related analytics (e.g. UE mobility analytics) for some network deployments, e.g. such with an NWDAF co-located to an AMF or SMF, where the NWDAF is configured to register in UDM for the UEs that it is serving or collecting data for and for the related Analytics ID(s). The procedures in this clause are also applicable to analytics that are not UE-related, when the NWDAF collects UE-related data. This enables NWDAF service consumers to discover the NWDAF instance that is already serving the UE for one or more Analytics ID(s).
Up

6.1C.2  NWDAF Registration in UDM  p. 69

Figure 6.1C.2-1 shows the procedures for registration of the NWDAF in UDM for UE-related analytics or UE-related data collection.
Reproduction of 3GPP TS 23.288, Fig. 6.1C.2-1: NWDAF registration in UDM
Figure 6.1C.2-1: NWDAF registration in UDM
Up
Step 1.
NWDAF triggers a registration in UDM, e.g. based on local configuration in the NWDAF, the reception of a new Analytics subscription request, start of collection of UE related data or an OAM configuration action.
Step 2.
The NWDAF registers into UDM for the served UE, by sending Nudm_UECM_Registration request (UE ID, NWDAF ID, Analytics ID(s)).
Step 3.
UDM sends a response to NWDAF.

6.1C.3  NWDAF De-registration from UDM  p. 69

Figure 6.1C.3-1 shows the procedures for deregistration of the NWDAF in UDM.
Reproduction of 3GPP TS 23.288, Fig. 6.1C.3-1: NWDAF de-registration from UDM
Figure 6.1C.3-1: NWDAF de-registration from UDM
Up
Step 1.
NWDAF triggers a de-registration from a previous registration in UDM. This trigger may be that, e.g. the NWDAF has purged the analytics context for the UE (see clause 6.1B.4) for related Analytics ID(s), the NWDAF is no longer collecting data related to the UE, or an administrative action.
Step 2.
NWDAF sends Nudm_UECM_Deregistration request (UE ID, NWDAF ID, Analytics ID(s)).
Step 3.
UDM sends a response to NWDAF.
Up

Up   Top   ToC