Section: 4.15.6.3 Expected UE Behaviour parameters
Content: These Expected UE Behaviour parameters characterise the foreseen behaviour of a UE or a group of UEs. Sets of these parameters may be provided via the NEF to be stored as part of the subscriber data. Each parameter within the Expected UE Behaviour shall have an associated validity time. The validity time indicates when the Expected UE Behaviour parameter expires and shall be deleted by the related NFs. The validity time may be set to indicate that the particular Expected UE Behaviour parameter has no expiration time. When the validity time expires, the related NFs delete their local copy of the associated Expected UE Behaviour parameter(s). In addition, each parameter within the Expected UE Behaviour may have a confidence and/or accuracy level associated with it. The confidence level indicates a probability assertion for the associated Expected UE Behaviour parameter and the accuracy level indicates the performance of the estimator (e.g. AI/ML model) used for the prediction. The provision procedure of the Expected UE Behaviour is realized by external parameter provision procedure defined in clause 4.15.6.2. The Expected UE Behaviour parameters stored as AMF-Associated Expected UE Behaviour parameters which is per UE level and SMF-Associated Expected UE Behaviour parameters which is per PDU session level in UDM. AMF retrieves the AMF-Associated Expected UE Behaviour parameters from UDM which may related to both PDU session(s) and SMS transmission. SMF retrieves the SMF-Associated Expected UE Behaviour parameters from UDM for the specific PDU session. AMF and SMF uses the Expected UE Behaviour parameters as described in clause 5.4.6.2 of TS 23.501[ System architecture for the 5G System (5GS) ]  [2]. Table 4.15.6.3-1: Description of Expected UE Behaviour parameters The Expected UE Moving Trajectory and the Expected Time and Day of Week in Trajectory may be used by the AMF. All other parameters may be used by the AMF and by the SMF. The Scheduled Communication Type and the Traffic Profile should not be used by the AMF to release the UE when NAS Release Assistance Information from the UE is available. In the case of NB-IoT UEs, the parameters may be forwarded to the RAN to allow optimisation of Uu resource allocation for NB-IoT UE differentiation.