[RIL]: E129

[Delegate]: Ericsson (Nithin)
[Class]: 1
[Status]: ToDo
[TDoc]:

[Description]: Indicating updated flight path availability during reestablishment is not straight forward. It should be discussed how to deal with the case when UE reestablishes to a different cell (on a different gNB).

[Proposed Change]: Consider removing the conditions for the UE to check for thresholds (to trigger flightpatavailability) and should indicate flightpathavailability like a new flightpath.

38331-i00.md

@@ -10876,19 +10876,7 @@ The UE shall:
 2\> if the UE has flight path information available:
-2\> if the UE has flight path information available:
-
-3\>if the UE had not previously provided a flight path information since last entering RRC_CONNECTED state; or
-
-3\> if at least one waypoint was not previously provided; or
-
-3\> if at least one upcoming waypoint that was previously provided is being removed; or
-
-3\> if *flightPathUpdateDistanceThr* is configured and for at least one waypoint, the 3D distance between the previously provided location and the new location is more than or equal to the distance threshold configured by *flightPathUpdateDistanceThr*; or
-
-3\> if *flightPathUpdateTimeThr* is configured and for at least one waypoint, the timestamp was not previously provided but is now available, or the time between the previously provided timestamp and the new timestamp, if available, is more than or equal to the time threshold configured by *flightPathUpdateTimeThr*:
-
-4\> include *flightPathInfoAvailable*;
+3\> include *flightPathInfoAvailable*;
 NOTE: If neither *flightPathUpdateDistanceThr* nor *flightPathUpdateTimeThr* is configured, it is up to UE implementation whether to include *flightPathInfoAvailable*when updated flight path information is available.