[{"name":"S2-2410852","title":"Addressing the ENs on geographical description","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In regards of the first note (i.e., polygon for the representation of flight paths), polygon, as per definition in clause 6.1.6.2.9 of 3GPP TS 29.572, contain 2D information without height\/altitude component. Therefore, it is not suitable for this purpose, instead it can be used to represent a border-crossing point. Considering the above, cuboids (or a set on cuboids) are more suitable (than, for instance, changing the definition of the polygon data type to include the height component) for representing a flight path. Hence, to address the EN on flight path representation, -adding a note to clarifty that: It is expected that the USS\/UTM provides flight path information using a set of cuboids and, if available, corresponding timestamps\/time schedule. Each of the cuboids is identified, e.g., by a set of the lowest\/highest latitude, lowest\/highest longitude and lowest\/highest height above the sea level in which the UAV is supposed to fly from its starting point to its next point in the assigned flight path. In order to address the EN about border-crossing point representation: - adding a NOTE stating that: (i) destination point (or a next point in the flight path) can be represented using the exisiting data type, specifically, PointAltitudeUncertainty data type as specified in clause 6.1.6.2.11 of 3GPP TS 29.572; (ii) border-crossing point can be represented using using the Polygon data type (clause 6.1.6.2.9 of 3GPP TS 29.572); no height information needs to be considered\/included. Additionally, -there is a need to add clarification\/restriction that, when it comes to bordering tracking areas and border-crossing points, not more than one border-crossing point per TA is considered, otherwise, the 5GC will not be able to determine which border-crossing point will be used for the USS changeover when the UAV enters a bordering TA, imposng additional mechanisms to be added (or existing to be reused) to 5GC. Therefore, the proposal is to add a NOTE clarifying that, for the USS changeover purposes, there is not more than one border-crossing point per tracking area in this realease of the specification. -bullet#2 in clause 5.12 needs to be rephrased\/corrected to emphasize that NEF does not derive a flight plan for a UAV, but it exploits the existing network analytics to collect the data and expose them to the USS\/UTM for pre-flight planning. The USS\/UTM makes the fligh planning. #---r01--- -replacing R2 reference with TS 23.032 where SA WG2 defines GAD shapes and making the corresponding changes in NOTE X2, X4 - in NOTE X1: replacing 'a cuboid' with '4-point polygon' etc.","secretary_remarks":"Revision of S2-2409993. Revised in parallel session to S2-2411159.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20630,"status":"revised","reservation_date":"2024-10-15 06:49:10","uploaded":"2024-10-20 10:31:13","revisionof":"S2-2409993","revisedto":"S2-2411159","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":139.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410852.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]