[{"name":"S2-2409619","title":"LS from ETSI TC ERM: Progress of the harmonised standard of relevant components of ECC Decision (22)07 on 'Harmonised framework on aerial UE usage in MFCN harmonised bands'","source":"ETSI TC ERM","contact":"Holger Butscheidt","contact-id":26309,"tdoctype":"LS in","for":"Information","abstract":"Dear Christoph, ETSI TC MSG\/TFES is currently developing a new harmonised standard of relevant components of ECC Decision (22)07 on 'harmonised framework on aerial UE usage in MFCN harmonised bands'. Details on the scope and progress of the aerial UE harmonised standard can be found here. TC MSG\/TFES would like to share via this LS the progress done on the abovementioned work and on how requirements in ECC LS ERM(22)78b012 would be addressed in the aerial UE harmonised standard. Below are the ECC requirements, captured in ECC LS ERM(22)78b012, followed by TC MSG\/ TFES response. {. . .}","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20540,"status":"noted","reservation_date":"2024-09-23 09:35:14","uploaded":"2024-10-08 07:13:52","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ECC PT1","Cc":"CT WG1, SA WG2, ETSI TC MSG\/TFES","lsoriginalls":"ERM(24)83b017r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409619.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409669","title":"Support of No-Transmit Zones","source":"LG Electronics, Qualcomm Incorporated, Ericsson, Futurewei, Samsung","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 2 - Add ECC Decision (22)07. 3.1 - Add NTZ. 3.2 - Add NTZ 5.x (new) - Describe support of NTZ.","secretary_remarks":"Revised in parallel session to S2-2410850.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20550,"status":"revised","reservation_date":"2024-09-27 07:44:44","uploaded":"2024-10-04 14:36:02","revisionof":"","revisedto":"S2-2410850","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":136.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409669.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"2, 3.1, 3.2, 5.x (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409699","title":"Solve the FFS related to network-assisted DAA","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Solve the FFS related to positioning signalling reduction.","secretary_remarks":"Merged into S2-2410857","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20800,"status":"merged","reservation_date":"2024-09-29 10:20:27","uploaded":"2024-09-29 10:56:34","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":137.0,"crrevision":"","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-2409699.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.14.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409700","title":"Update the USS triggered network-assisted DAA","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the USS triggered network-assisted DAA procedure to add the feature of using relative location of UAVs provided by Ranging service to enable NWDAA.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20810,"status":"noted","reservation_date":"2024-09-29 10:20:27","uploaded":"2024-09-29 10:56:34","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":138.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409700.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.14.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409993","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.","secretary_remarks":"Revised in parallel session to S2-2410852.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20620,"status":"revised","reservation_date":"2024-02-10 19:04:47","uploaded":"2024-10-04 22:06:03","revisionof":"","revisedto":"S2-2410852","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":139.0,"crrevision":"","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-2409993.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 5.12.1, 5.13.2, 4.4.1.1.3.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409994","title":"Addressing the ENs on message names","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -Updating the message names (where required) using Nnef_UAVFlightAssistance and Nnef_RetrieveInfoUAVFlight_Get service operations, -correcting the description of some steps","secretary_remarks":"Revised in parallel session, merging S2-2410449, to S2-2410854.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20660,"status":"revised","reservation_date":"2024-02-10 19:04:48","uploaded":"2024-10-04 22:06:03","revisionof":"","revisedto":"S2-2410854","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":140.0,"crrevision":"","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-2409994.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.12.2, 5.12.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409995","title":"Addressing the EN on Nnef_UAVFlightAssistance_Get service operations","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following (main) chages have been made by this CR: 1) replacing 'Nnef_UAVFlightAssistance_Get' with 'Nnef_RetrieveInfoUAVFlight_Get' in such as way creating a new NEF service (incl. updating the service description and USS changeover procedure accordingly) 2) Clarifying for the Nnef_UAVFlightAssistance_Create service operation that the request creates the explicit subscriptions to get notified about the following events, when applicable, (1) the UAS NF\/NEF determines that UAV will leave a geographical area served by the USS, (2) the UAV enters a TA\/Cell with a border-crossing point to another USS, and (3) the UAV deviates from the assigned flight plan. 3) Adding new service operation, i.e., Nnef_RetrieveInfoUAVFlight_Delete; 4) clarifying in the description of the USS changeover procedure (clause 5.13.2) that step 2a and Step 12 are over the application layer; 5) Adding Step 22 in the USS changeover procedure so that the new USS could inform the UAS NF about new Notification Target Address; 6) deleted the EN about a new AMF event filter, as the corresponding CR has been agreed at SA WG2#164 (see S2-2409514)","secretary_remarks":"Revised in parallel session to S2-2410853.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20690,"status":"revised","reservation_date":"2024-02-10 19:04:49","uploaded":"2024-10-04 22:06:03","revisionof":"","revisedto":"S2-2410853","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":141.0,"crrevision":"","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-2409995.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.1.1.3, 4.4.1.1.2, 4.4.1.1.X (new), 5.13.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409996","title":"Provisioning of information about USSes to UAVs and UAS NF","source":"Ericsson, InterDigital, Samsung, LG Electronics","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -clarifying that information about USSes contains not only a list of USS addresses but also the description of geographical areas that the USSes serve -specifying that the USS may send the USS information to the UAV using the UUAA Authorization Payload -add that The USS may send to the NEF\/UAS NF the information about relevant USSes in the Naf_Authentication_AuthenticateAuthorize Response message and include it to the UUAA Authorization Payload.","secretary_remarks":"Revised in parallel session, merging S2-2410451, to S2-2410856.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20740,"status":"revised","reservation_date":"2024-02-10 19:04:49","uploaded":"2024-10-04 22:06:03","revisionof":"","revisedto":"S2-2410856","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":142.0,"crrevision":"","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-2409996.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.1.2.2.2, 4.4.2, 5.2.2.2, 5.2.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409997","title":"Adding a list of UEs as input for NWDAF analytics","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updating the description of relevant clauses so that a 'list of UEs' provided by the consumer could be used as 'Target for Analytics Reporting'","secretary_remarks":"Revised in parallel session to S2-2410858.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20770,"status":"revised","reservation_date":"2024-02-10 19:04:50","uploaded":"2024-10-04 22:06:03","revisionof":"","revisedto":"S2-2410858","release":"Rel-19","crspec":"23.288","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":1240.0,"crrevision":"","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-2409997.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 6.9.1, 6.9.2, 6.9.4, 6.21.1, 6.21.2, 6.21.3, 6.21.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409998","title":"Updates to Network-Based\/Assisted DAA Procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The changes include: Added description about use of previously obtained location estimate of the target UE at GMLC for NWDAF analytics to the procedures for UAV triggered and USS triggered Network-assisted DAA, and removed the EN. Corrected errors in the figures and procedures.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20790,"status":"agreed","reservation_date":"2024-02-10 19:04:51","uploaded":"2024-10-04 22:06:03","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":143.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-241493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409998.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.14.2, 5.14.3, 5.14.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409999","title":"Adding C2 Communication Reliability with Redundant User Plane Paths to Annex","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The changes include: Added content on C2 communication reliability with redundant user plane paths to Annex in TS 23.256.","secretary_remarks":"Revised in parallel session, merging S2-2410452, to S2-2410851.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20580,"status":"revised","reservation_date":"2024-02-10 19:04:52","uploaded":"2024-10-04 22:06:03","revisionof":"","revisedto":"S2-2410851","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":144.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409999.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":false,"clauses_affected":"A.X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410000","title":"Updates to Relative Proximity Analytics","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The changes include: Added sub-predictions under Time To Collision for Collision shape and Collision direction.","secretary_remarks":"Revised in parallel session to S2-2410859.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20840,"status":"revised","reservation_date":"2024-02-10 19:04:52","uploaded":"2024-10-04 22:06:03","revisionof":"","revisedto":"S2-2410859","release":"Rel-19","crspec":"23.288","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":1241.0,"crrevision":"","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-2410000.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.19.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410449","title":"Correction to support of UAV flight planning and monitoring","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing the editor's note by clarifying: When USS provides UAV flight path(s) to 5G network, the flight path is represented by the taking-off location and one or multiple airpaces. The airspace is expressed by shape of polygon, defined in TS 23.032.","secretary_remarks":"Merged into S2-2410854","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20650,"status":"merged","reservation_date":"2024-04-10 11:51:43","uploaded":"2024-10-04 16:00:48","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":145.0,"crrevision":"","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-2410449.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 5.12.1, 5.12.2, 5.12.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410450","title":"Update to multiple USS serving different geographical areas","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add how to perform the UUAA procedures during the USS changeover.","secretary_remarks":"Revised in parallel session to S2-2410855.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20710,"status":"revised","reservation_date":"2024-04-10 11:51:44","uploaded":"2024-10-04 16:00:48","revisionof":"","revisedto":"S2-2410855","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":146.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410450.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410451","title":"Correction to USS discovery in multiple USS deployment","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The UAS NF should take the UAV location into account in multiple USS deployment during the UUAA procedure.","secretary_remarks":"Merged into S2-2410856","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20760,"status":"merged","reservation_date":"2024-04-10 11:51:44","uploaded":"2024-10-04 16:00:48","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":147.0,"crrevision":"","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-2410451.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.2, 5.2.2.2, 5.2.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410452","title":"Correction to support of C2 communication reliability","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add C2 communication reliability principles in sol#14 into Annex X.","secretary_remarks":"Merged into S2-2410851","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20610,"status":"merged","reservation_date":"2024-04-10 11:51:45","uploaded":"2024-10-04 16:00:48","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":148.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410452.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":false,"clauses_affected":" Annex A.2(new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410453","title":"Update of procedure for UAV Triggered Network-assisted DAA","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a note to addres the editor's note: there is a possibility that after step 6, GMLC receives concurrent location requests from NEF and NWDAF, and GMLC may decide to combine the concurrent location requests by fully executing one of the requests and using the ensuing location estimate result(s) to satisfy the other request(s) without fully executing the latter, as defiend in TS 23.273. Remove the option that USS can be a LCS client.","secretary_remarks":"Revised in parallel session, merging S2-2409699, to S2-2410857.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20820,"status":"revised","reservation_date":"2024-04-10 11:51:46","uploaded":"2024-10-04 16:00:48","revisionof":"","revisedto":"S2-2410857","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":149.0,"crrevision":"","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-2410453.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.14.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410850","title":"Support of No-Transmit Zones","source":"LG Electronics, Qualcomm Incorporated, Ericsson, Futurewei, Samsung, Nokia, Nokia Shanghai Bell, Deutsche Telekom, SHARP","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 2 - Add ECC Decision (22)07. 3.1 - Add NTZ. 3.2 - Add NTZ 5.x (new) - Describe support of NTZ.","secretary_remarks":"Revision of S2-2409669. Revised in parallel session to S2-2411157.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20560,"status":"revised","reservation_date":"2024-10-15 06:48:53","uploaded":"2024-10-20 10:31:13","revisionof":"S2-2409669","revisedto":"S2-2411157","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":136.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410850.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410851","title":"Adding C2 Communication Reliability with Redundant User Plane Paths to Annex","source":"Ericsson, Huawei","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The changes include: Added content on C2 communication reliability with redundant user plane paths to Annex in TS 23.256.","secretary_remarks":"Revision of S2-2409999, merging S2-2410452. Revised in parallel session to S2-2411158.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20590,"status":"revised","reservation_date":"2024-10-15 06:48:53","uploaded":"2024-10-20 10:31:13","revisionof":"S2-2409999","revisedto":"S2-2411158","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":144.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410851.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"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},
{"name":"S2-2410853","title":"Addressing the EN on Nnef_UAVFlightAssistance_Get service operations","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following (main) chages have been made by this CR: 1) replacing 'Nnef_UAVFlightAssistance_Get' with 'Nnef_RetrieveInfoUAVFlight_Get' in such as way creating a new NEF service (incl. updating the service description and USS changeover procedure accordingly) 2) Clarifying for the Nnef_UAVFlightAssistance_Create service operation that the request creates the explicit subscriptions to get notified about the following events, when applicable, (1) the UAS NF\/NEF determines that UAV will leave a geographical area served by the USS, (2) the UAV enters a TA\/Cell with a border-crossing point to another USS, and (3) the UAV deviates from the assigned flight plan. 3) Adding new service operation, i.e., Nnef_RetrieveInfoUAVFlight_Delete; 4) clarifying in the description of the USS changeover procedure (clause 5.13.2) that step 2a and Step 12 are over the application layer; 5) Adding Step 22 in the USS changeover procedure so that the new USS could inform the UAS NF about new Notification Target Address; 6) deleted the EN about a new AMF event filter, as the corresponding CR has been agreed at SA WG2#164 (see S2-2409514) Clarified Report ID use because Transaction Reference ID usually is used for Create\/Update, but here we just need to id that can be used to distinguish two set of retrieved information it can be a time stamp, or anything else which to be determined by stage 3.","secretary_remarks":"Revision of S2-2409995. Agreed in parallel session. Block approved. Revised at S2-166 in S2-2411657","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20700,"status":"revised","reservation_date":"2024-10-15 06:49:11","uploaded":"2024-10-20 10:31:13","revisionof":"S2-2409995","revisedto":"S2-2411657, S2-2411744, S2-2412179","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":141.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-2410853.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410854","title":"Addressing the ENs on message names","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -Updating the message names (where required) using Nnef_UAVFlightAssistance and Nnef_RetrieveInfoUAVFlight_Get service operations, -correcting the description of some steps","secretary_remarks":"Revision of S2-2409994, merging S2-2410449. Revised in parallel session to S2-2411160.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20670,"status":"revised","reservation_date":"2024-10-15 06:49:12","uploaded":"2024-10-20 10:31:13","revisionof":"S2-2409994","revisedto":"S2-2411160","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":140.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-2410854.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410855","title":"Update to multiple USS serving different geographical areas","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the UUAA procedures is performed between UAV and target USS during the USS changeover.","secretary_remarks":"Revision of S2-2410450. Revised in parallel session to S2-2411161.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20720,"status":"revised","reservation_date":"2024-10-15 06:49:13","uploaded":"2024-10-20 10:31:13","revisionof":"S2-2410450","revisedto":"S2-2411161","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":146.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-2410855.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410856","title":"Provisioning of information about USSes to UAVs and UAS NF","source":"Ericsson, InterDigital, Samsung, LG Electronics, Huawei","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -clarifying that information about USSes contains not only a list of USS addresses but also the description of geographical areas that the USSes serve -specifying that the USS may send the USS information to the UAV using the UUAA Authorization Payload -add that The USS may send to the NEF\/UAS NF the information about relevant USSes in the Naf_Authentication_AuthenticateAuthorize Response message and include it to the UUAA Authorization Payload. -Add from S2-2410451","secretary_remarks":"Revision of S2-2409996, merging S2-2410451. Agreed in parallel session. Block approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20750,"status":"agreed","reservation_date":"2024-10-15 06:49:13","uploaded":"2024-10-20 10:31:13","revisionof":"S2-2409996","revisedto":"S2-2411427, S2-2411847","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":142.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-241493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410856.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410857","title":"Update of procedure for UAV Triggered Network-assisted DAA","source":"Huawei, HiSilicon, CATT","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a note to addres the editor's note: there is a possibility that after step 6, GMLC receives concurrent location requests from NEF and NWDAF, and GMLC may decide to combine the concurrent location requests by fully executing one of the requests and using the ensuing location estimate result(s) to satisfy the other request(s) without fully executing the latter, as defiend in TS 23.273.","secretary_remarks":"Revision of S2-2410453, merging S2-2409699. Agreed in parallel session. Block approved. Revised at S2-166 in S2-2411658","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20830,"status":"revised","reservation_date":"2024-10-15 06:49:14","uploaded":"2024-10-20 10:31:13","revisionof":"S2-2410453","revisedto":"S2-2411658","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":149.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-2410857.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410858","title":"Adding a list of UEs as input for NWDAF analytics","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updating the description of relevant clauses so that a 'list of UEs' provided by the consumer could be used as 'Target for Analytics Reporting'","secretary_remarks":"Revision of S2-2409997. Agreed in parallel session. Block approved. Revised at S2-166 in S2-2411659","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20780,"status":"revised","reservation_date":"2024-10-15 06:49:15","uploaded":"2024-10-20 10:31:13","revisionof":"S2-2409997","revisedto":"S2-2411659","release":"Rel-19","crspec":"23.288","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":1240.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-2410858.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410859","title":"Updates to Relative Proximity Analytics","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The changes include: Added sub-predictions under Time To Collision for Collision space and Collision direction.","secretary_remarks":"Revision of S2-2410000. Agreed in parallel session. Block approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20850,"status":"agreed","reservation_date":"2024-10-15 06:49:16","uploaded":"2024-10-20 10:31:13","revisionof":"S2-2410000","revisedto":"","release":"Rel-19","crspec":"23.288","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":1241.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-241493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410859.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411157","title":"Support of No-Transmit Zones","source":"LG Electronics, Qualcomm Incorporated, Ericsson, Futurewei, Samsung, Nokia, Nokia Shanghai Bell, Deutsche Telekom, SHARP","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 2 - Add ECC Decision (22)07. 3.1 - Add NTZ. 3.2 - Add NTZ 5.x (new) - Describe support of NTZ.","secretary_remarks":"Revision of S2-2410850. Agreed in parallel session. Block approved. Revised at S2-166 in S2-2411393","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20570,"status":"revised","reservation_date":"2024-10-18 02:16:25","uploaded":"2024-10-20 10:31:15","revisionof":"S2-2410850","revisedto":"S2-2411393","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":136.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2411157.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411158","title":"Adding C2 Communication Reliability with Redundant User Plane Paths to Annex","source":"Ericsson, Huawei","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The changes include: Added content on C2 communication reliability with redundant user plane paths to Annex in TS 23.256.","secretary_remarks":"Revision of S2-2410851. Agreed in parallel session. Block approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20600,"status":"agreed","reservation_date":"2024-10-18 02:16:27","uploaded":"2024-10-20 10:31:15","revisionof":"S2-2410851","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":144.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"SP-241493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2411158.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411159","title":"Addressing the ENs on geographical description","source":"Ericsson, Huawei","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-2410852. Agreed in parallel session. Block approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20640,"status":"agreed","reservation_date":"2024-10-18 02:16:28","uploaded":"2024-10-20 10:31:15","revisionof":"S2-2410852","revisedto":"S2-2411846","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":139.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-241493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2411159.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411160","title":"Addressing the ENs on message names","source":"Ericsson, Huawei","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -Updating the message names (where required) using Nnef_UAVFlightAssistance and Nnef_RetrieveInfoUAVFlight_Get service operations, -correcting the description of some steps","secretary_remarks":"Revision of S2-2410854. Agreed in parallel session. Block approved. Revised at S2-166 in S2-2411746","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20680,"status":"revised","reservation_date":"2024-10-18 02:16:29","uploaded":"2024-10-20 10:31:15","revisionof":"S2-2410854","revisedto":"S2-2411746","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":140.0,"crrevision":2.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-2411160.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411161","title":"Update to multiple USS serving different geographical areas","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the UUAA procedures is performed between UAV and target USS during the USS changeover.","secretary_remarks":"Revision of S2-2410855. Agreed in parallel session. Block approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":20730,"status":"agreed","reservation_date":"2024-10-18 02:16:30","uploaded":"2024-10-20 10:31:15","revisionof":"S2-2410855","revisedto":"S2-2411848","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":146.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-241493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2411161.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]