Section: X.8.2.1 Policies configured locally in Roaming entry NWDAF producer
Content: Figure X.8.2.1-1: Protection of analytics exchange when policies configured locally in Roaming entry NWDAF Pre-requisites: - Roaming entry NWDAF producer, i.e. NWDAFp shall be pre-configured with a list of allowed analytics per PLMN. - If token-based authorization is used, NWDAFc shall have acquired an access token from the PLMN2 to consume the services exposed in Nwdaf_RoamingAnalytics_Subscribe/Request APIs. Step 1: NWDAFc sends Nnwdaf_RoamingAnalytics_Subscribe/Request message to NWDAFp to request analytics. Step 2: The roaming entry NWDAFp shall verify the service request, including verifying token and the visited PLMN ID and determine whether the requested analytics are allowed to be exposed to NWDAFc in PLMN1 by pre-configured policies. Step 3: The roaming entry NWDAFp shall apply the security policies per consumer (PLMN) to the requested analytics and decide on their anonymization, restriction or desensitization based on operator’s policy. NOTE: The anonymization, restriction or desensitization mechanisms of analytics are left for implementation. Step 4: NWDAFp returns the requested and processed analytics to NWDAFc.