[{"name":"S2-2411290","title":"LS on Clarification related to the QoS and QoE parameters for the support of real time UAV flight path monitoring assistance.","source":"CT WG3","contact":"Rajesh Babu Natarajan","contact-id":89232,"tdoctype":"LS in","for":"Information","abstract":"As per TS 23.255: {. . .} Question 1: What are the QoS parameters and QoE parameters to be considered, whose thresholds define the triggering events in the above mentioned use case? Question 2: How the UAS application specific server obtains\/does the measurement of these QoS and QoE parameters values?","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":19530,"status":"noted","reservation_date":"2024-10-25 13:46:53","uploaded":"2024-10-25 13:52:50","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2, CT WG1","lsoriginalls":"C3-245096","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411290.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411393","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. @ SA WG2#166 - Modify 'height' to 'altitude' to use wording of aviation industry. - Add 'optional time restriction' to NTZ assistance information. - Clarify NOTE 3 in 5.x.","secretary_remarks":"Revision of (agreed) S2-2411157. Revised in parallel session to S2-2412594.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19840,"status":"revised","reservation_date":"2024-05-11 04:02:06","uploaded":"2024-11-08 13:30:59","revisionof":"S2-2411157","revisedto":"S2-2412594","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":136.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411393.zip","group":"S2","meeting":"S2-166","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-2411427","title":"Provisioning of information about USSes to UAVs and UAS NF","source":"[Ericsson], InterDigital, [Samsung], [LG Electronics], [Huawei]","contact":"Jung Je Son","contact-id":96448,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Rev2: - clarifying that USS(es) info is stored as part of UUAA context. -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 (agreed) S2-2410856. Revised in parallel session to S2-2412591.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19740,"status":"revised","reservation_date":"2024-05-11 19:15:10","uploaded":"2024-11-08 19:59:11","revisionof":"S2-2410856","revisedto":"S2-2412591","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":142.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411427.zip","group":"S2","meeting":"S2-166","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-2411657","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: #---SA2#166--- -removing the aformentioned EN from clause 4.4.1.1.X.2 and keeping the use\/description of the Nnef_RetrieveInfoUAVFlight_Get and Nnef_UAVFlightAssistance_Create\/Notify as it has been introduced by S2-2410853 in SA WG2#165. #---SA2#165--- 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 (agreed) S2-2410853. Revised in parallel session, merging S2-2411744, to S2-2412588.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19600,"status":"revised","reservation_date":"2024-07-11 16:46:02","uploaded":"2024-11-08 22:51:24","revisionof":"S2-2410853","revisedto":"S2-2412588","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":141.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411657.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.1.1.1, 4.4.1.1.3.1, 4.4.1.1.3.2, 4.4.1.1.3.3, 4.4.1.1.3.4, 4.4.1.1.X (new), 5.13.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411658","title":"Update of procedure for UAV Triggered Network-assisted DAA","source":"[Huawei, HiSilicon, CATT], Ericsson","contact":"Shabnam Sultana","contact-id":21207,"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. In rev 2, the changes include: Updated the figure and step description. Updated the NOTE X to 'There is a possibility that between steps 3 and 4b, '. Corrected the baseline used in the CR which used draft spec version.","secretary_remarks":"Revision of (agreed) S2-2410857. Revised in parallel session to S2-2412595.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19870,"status":"revised","reservation_date":"2024-07-11 16:46:03","uploaded":"2024-11-08 22:51:24","revisionof":"S2-2410857","revisedto":"S2-2412595","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":149.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411658.zip","group":"S2","meeting":"S2-166","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-2411659","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: #---SA2#166--- -Describing the use of a NEF-provided list of UEs\/SUPIs for obtaining the requested analytics. #---SA2#165--- 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 (agreed) S2-2410858. Revised in parallel session to S2-2412593.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19820,"status":"revised","reservation_date":"2024-07-11 16:46:24","uploaded":"2024-11-08 22:51:24","revisionof":"S2-2410858","revisedto":"S2-2412593","release":"Rel-19","crspec":"23.288","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":1240.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411659.zip","group":"S2","meeting":"S2-166","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-2411660","title":"Instructing a UAV to perform its altitude reporting","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -This CR proposes two options on how the CN can configure aerial UEs for altitude reporting, considering a flight path information received from a USS\/UTM. Option A: configuration (altitude threshold values, periodicity information) is sent to an aerial UE over the application layer from the USS\/UTM after the UAS NF determines these parameters. Option B: node-level signalling using either UE-associtated signalling or non-UE-associated signalling","secretary_remarks":"Revised in parallel session to S2-2412587.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19560,"status":"revised","reservation_date":"2024-07-11 16:46:40","uploaded":"2024-11-08 22:51:24","revisionof":"","revisedto":"S2-2412587","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":150.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411660.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.X.1 (new), 5.X.2 (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411661","title":"Addressing the EN on UE's altitude reporting","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -Replacing the EN by a note stating that procedures related to reporting altitude information of aerial UEs are specified in clause 5.X of TS 23.256 [80].","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":19550,"status":"agreed","reservation_date":"2024-07-11 16:46:41","uploaded":"2024-11-08 22:51:24","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":5141.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-241493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411661.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.2.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411662","title":"Addressing the EN on security aspects of USS changeover","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -The aforementioned editor's note is deleted, and a note, basically stating that security aspects of USS changeover are defined by SA WG3, is added to the relevant clause. -In addition, with this CR we also delete an EN on whether to add a new service operation or to reuse some of the existing for triggering USS changeover. This EN is not longer relevant since the Nnef_UAVFlightAssistance_ service has been introduced (see clause 4.4.1.1.3 of TS 23.256) and used in the procedure for USS changeover.","secretary_remarks":"Revised in parallel session, including parts of S2-2411848, to S2-2412590.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19720,"status":"revised","reservation_date":"2024-07-11 16:46:42","uploaded":"2024-11-08 22:51:24","revisionof":"","revisedto":"S2-2412590","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":151.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411662.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.2.2, 5.13.1, 5.13.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411744","title":"Addressing the EN on Nnef_UAVFlightAssistance_Get service operations","source":"[Ericsson], ETRI","contact":"Seung-Ik Lee","contact-id":88159,"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. 1) The operation semantic of Nnef_UAVFlightAssistance_Notify is corrected to use Subscribe\/Notify model in cl. 4.4.1.1.1, 4.4.1.1.3.3 and 5.13.2.","secretary_remarks":"Revision of (agreed) S2-2410853. Merged into S2-2412588","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19670,"status":"merged","reservation_date":"2024-08-11 01:51:29","uploaded":"2024-11-08 02:56:10","revisionof":"S2-2410853","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":141.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411744.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.1.1.1, 4.4.1.1.3.1, 4.4.1.1.3.2, 4.4.1.1.3.3, 4.4.1.1.3.4, 4.4.1.1.X (new), 5.13.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411746","title":"Addressing the ENs on message names","source":"[Ericsson, Huawei], ETRI","contact":"Seung-Ik Lee","contact-id":88159,"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 - The operation of Nnef_UAVFlightAssistance_Notify is corrected to use Subscribe\/Notify model in cl. 5.12.3.","secretary_remarks":"Revision of (agreed) S2-2411160. Revised in parallel session to S2-2412986.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19780,"status":"revised","reservation_date":"2024-08-11 01:53:10","uploaded":"2024-11-08 02:56:10","revisionof":"S2-2411160","revisedto":"S2-2412986","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":140.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411746.zip","group":"S2","meeting":"S2-166","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-2411846","title":"Addressing the ENs on geographical description","source":"[Ericsson], Huawei","contact":"Marco Spini","contact-id":8356,"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. Added in rev3: Add another option of identifing a UAV flight path. When the USS provisions a UAV flight path to the NEF\/UAS NF, the USS may provide a list Geohash codes or a flight path ID. The network derives the geographic location based on the pre-configued mapping between Geohash code and geographic location.","secretary_remarks":"Revision of (agreed) S2-2411159. Revised in parallel session to S2-2412592.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19800,"status":"revised","reservation_date":"2024-08-11 07:21:20","uploaded":"2024-11-08 17:02:13","revisionof":"S2-2411159","revisedto":"S2-2412592","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":139.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411846.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411847","title":"Provisioning of information about USSes to UAVs and UAS NF","source":"[Ericsson, InterDigital, Samsung, LG Electronics], Huawei, HiSilicon,","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Rev 2: Clarify the impact due to the agreement of 'authorized USS(es)', that: USS may provision the address(es) and geographical area of USSes in the 'Procedure for USS changeover during a UAV flight', as Authorized USSes information for the UAV flight path. If provisioned by USS, the UAS NF maintains the authorized USSes information as part of the UUAA context. The Authorized USSes information may refer to the USSes serving the UAS flight path or the USSes which have authorized the UAV successfully. Changes in SA WG2#165: 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 (agreed) S2-2410856. 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":19760,"status":"noted","reservation_date":"2024-08-11 07:21:20","uploaded":"2024-11-08 17:02:13","revisionof":"S2-2410856","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":142.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411847.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"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-2411848","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: Rev 3: clarify the authorized USSes information used during USS changeover: If Authorized USS(es) information is stored in the UUAA context, the NEF\/UAS NF checks whether the target USS address provided by UAV matches one of the Authorized USSes information. If the target USS is among the Authorized USSes information that serves the UAV flight path, the NEF\/UAS NF will forward the UAV UUAA request toward the target USS. If the target USS is among the USSes that authorized UAV, the NEF skips the interaction with the target USS and updates the UUAA context and complete the changeover for the UAV. [below texts are from SA WG2#165]: Clarify the UUAA procedures is performed between UAV and target USS during the USS changeover.","secretary_remarks":"Revision of (agreed) S2-2411161. The new changes compared to the previously agreed CR were merged into S2-2412590. 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":19770,"status":"noted","reservation_date":"2024-08-11 07:21:21","uploaded":"2024-11-08 17:02:13","revisionof":"S2-2411161","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":146.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411848.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.13.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412179","title":"Addressing the EN on Nnef_UAVFlightAssistance_Get service operations","source":"[Ericsson], CATT","contact":"Yunjing Hou","contact-id":46707,"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. Summary of change 2: Update the procedure in clause 5.13.2 to describe how to use the Nnef_UAVFlightAssistance_Delete service operation.","secretary_remarks":"Revision of (agreed) S2-2410853. 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":19680,"status":"noted","reservation_date":"2024-08-11 14:43:38","uploaded":"2024-11-08 15:01:22","revisionof":"S2-2410853","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":141.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412179.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.1.1.1, 4.4.1.1.3.1, 4.4.1.1.3.2, 4.4.1.1.3.3, 4.4.1.1.3.4, 4.4.1.1.X (new), 5.13.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412180","title":"Update Nnef_UAVFlightAssistance_Create service operation","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the Nnef_UAVFlightAssistance_Create service operation.","secretary_remarks":"Revised in parallel session to S2-2412589.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19690,"status":"revised","reservation_date":"2024-08-11 14:43:39","uploaded":"2024-11-08 15:01:22","revisionof":"","revisedto":"S2-2412589","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":152.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412180.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.1.1.3.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412335","title":"GMLC LMF update for Ranging_SL","source":"Nokia, Nokia Shanghai Bell","contact":"Mao Cai","contact-id":89487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added reference to TS 23.586 Added LMF reference to TS 23.586 in clause 4.4.1.6 Added GMLC reference to TS 23.586 in clause 4.4.1.7 Added reference to SL operations in TS 23.586 into clause 5.3.2","secretary_remarks":"Revised in parallel session to S2-2412596.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19890,"status":"revised","reservation_date":"2024-08-11 21:53:03","uploaded":"2024-11-08 22:13:38","revisionof":"","revisedto":"S2-2412596","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":153.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412335.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 4.4.1.6, 4.4.1.7, 5.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412587","title":"Instructing a UAV to perform its altitude reporting","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -This CR proposes two options on how the CN can configure aerial UEs for altitude reporting, considering a flight path information received from a USS\/UTM. Option A: configuration (altitude threshold values, periodicity information) is sent to an aerial UE over the application layer from the USS\/UTM after the UAS NF determines these parameters. Option B: node-level signalling using either UE-associtated signalling or non-UE-associated signalling","secretary_remarks":"Revision of S2-2411660. Revised in parallel session to S2-2412756.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19570,"status":"revised","reservation_date":"2024-11-20 20:09:32","uploaded":"2024-11-25 06:41:12","revisionof":"S2-2411660","revisedto":"S2-2412756","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":150.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412587.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.X.1 (new), 5.X.2 (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412588","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: #---SA2#166--- -removing the aformentioned EN from clause 4.4.1.1.X.2 and keeping the use\/description of the Nnef_RetrieveInfoUAVFlight_Get and Nnef_UAVFlightAssistance_Create\/Notify as it has been introduced by S2-2410853 in SA WG2#165. #---SA2#165--- 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-2411657, merging S2-2411744. Revised in parallel session to S2-2412758.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19610,"status":"revised","reservation_date":"2024-11-20 20:09:33","uploaded":"2024-11-25 06:41:12","revisionof":"S2-2411657","revisedto":"S2-2412758","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":141.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412588.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412589","title":"Update Nnef_UAVFlightAssistance_Create service operation","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the Nnef_UAVFlightAssistance_Create service operation.","secretary_remarks":"Revision of S2-2412180. Revised in parallel session to S2-2412759.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19700,"status":"revised","reservation_date":"2024-11-20 20:09:33","uploaded":"2024-11-25 06:41:12","revisionof":"S2-2412180","revisedto":"S2-2412759","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":152.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412589.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.1.1.3.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412590","title":"Addressing the EN on security aspects of USS changeover","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -The aforementioned editor's note is deleted, and a note, basically stating that security aspects of USS changeover are defined by SA WG3, is added to the relevant clause. -In addition, with this CR we also delete an EN on whether to add a new service operation or to reuse some of the existing for triggering USS changeover. This EN is not longer relevant since the Nnef_UAVFlightAssistance_ service has been introduced (see clause 4.4.1.1.3 of TS 23.256) and used in the procedure for USS changeover.","secretary_remarks":"Revision of S2-2411662, including parts of S2-2411848. 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":19730,"status":"agreed","reservation_date":"2024-11-20 20:09:34","uploaded":"2024-11-25 06:41:12","revisionof":"S2-2411662","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":151.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_166_Orlando_2024-11\/Docs\/S2-2412590.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.2.2, 5.13.1, 5.13.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412591","title":"Provisioning of information about USSes to UAVs and UAS NF","source":"Ericsson, InterDigital, [Samsung], [LG Electronics], [Huawei]","contact":"Jung Je Son","contact-id":96448,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Rev2: - clarifying that USS(es) info is stored as part of UUAA context. -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-2411427. 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":19750,"status":"noted","reservation_date":"2024-11-20 20:09:35","uploaded":"2024-11-25 06:41:12","revisionof":"S2-2411427","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":142.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412591.zip","group":"S2","meeting":"S2-166","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-2412592","title":"Addressing the ENs on geographical description","source":"[Ericsson], Huawei","contact":"Marco Spini","contact-id":8356,"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. Added in rev3: Add another option of identifing a UAV flight path. When the USS provisions a UAV flight path to the NEF\/UAS NF, the USS may provide a list Geohash codes or a flight path ID. The network derives the geographic location based on the pre-configued mapping between Geohash code and geographic location.","secretary_remarks":"Revision of S2-2411846. 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":19810,"status":"noted","reservation_date":"2024-11-20 20:09:36","uploaded":"2024-11-25 06:41:12","revisionof":"S2-2411846","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":139.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412592.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412593","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: #---SA2#166--- -Describing the use of a NEF-provided list of UEs\/SUPIs for obtaining the requested analytics. #---SA2#165--- 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-2411659. 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":19830,"status":"agreed","reservation_date":"2024-11-20 20:09:37","uploaded":"2024-11-25 06:41:12","revisionof":"S2-2411659","revisedto":"","release":"Rel-19","crspec":"23.288","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":1240.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-241493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412593.zip","group":"S2","meeting":"S2-166","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-2412594","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. @ SA WG2#166 - Modify 'height' to 'altitude' to use wording of aviation industry. - Add 'optional time restriction' to NTZ assistance information. - Clarify NOTE 3 in 5.x.","secretary_remarks":"Revision of S2-2411393. Revised in parallel session to S2-2412987.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19850,"status":"revised","reservation_date":"2024-11-20 20:09:38","uploaded":"2024-11-25 06:41:12","revisionof":"S2-2411393","revisedto":"S2-2412987","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":136.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412594.zip","group":"S2","meeting":"S2-166","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-2412595","title":"Update of procedure for UAV Triggered Network-assisted DAA","source":"Huawei, HiSilicon, CATT, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"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. In rev 2, the changes include: Updated the figure and step description. Updated the NOTE X to 'There is a possibility that between steps 3 and 4b, '. Corrected the baseline used in the CR which used draft spec version.","secretary_remarks":"Revision of S2-2411658. 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":19880,"status":"agreed","reservation_date":"2024-11-20 20:09:38","uploaded":"2024-11-25 06:41:12","revisionof":"S2-2411658","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":149.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-241493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412595.zip","group":"S2","meeting":"S2-166","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-2412596","title":"GMLC LMF update for Ranging_SL","source":"Nokia, Nokia Shanghai Bell","contact":"Mao Cai","contact-id":89487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added reference to TS 23.586 Added LMF reference to TS 23.586 in clause 4.4.1.6 Added GMLC reference to TS 23.586 in clause 4.4.1.7 Added reference to SL operations in TS 23.586 into clause 5.3.2","secretary_remarks":"Revision of S2-2412335. 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":19900,"status":"agreed","reservation_date":"2024-11-20 20:09:39","uploaded":"2024-11-25 06:41:12","revisionof":"S2-2412335","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":153.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_166_Orlando_2024-11\/Docs\/S2-2412596.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412756","title":"Instructing a UAV to perform its altitude reporting","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -This CR proposes two options on how the CN can configure aerial UEs for altitude reporting, considering a flight path information received from a USS\/UTM. Option A: configuration (altitude threshold values, periodicity information) is sent to an aerial UE over the application layer from the USS\/UTM after the UAS NF determines these parameters. Option B: node-level signalling using either UE-associtated signalling or non-UE-associated signalling","secretary_remarks":"Revision of S2-2412587. Revised in parallel session to S2-2413008.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19580,"status":"revised","reservation_date":"2024-11-25 06:25:53","uploaded":"2024-11-25 06:51:08","revisionof":"S2-2412587","revisedto":"S2-2413008","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":150.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412756.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":true,"clauses_affected":"2, 5.X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412757","title":"Clarification of Nnef_RetrieveInfoUAVFlight_Get service operation","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3","secretary_remarks":"Created at meeting. Revised in parallel session to S2-2413010.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19630,"status":"revised","reservation_date":"2024-11-25 06:25:53","uploaded":"2024-11-25 06:51:08","revisionof":"","revisedto":"S2-2413010","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"UAS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412757.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412758","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: #---SA2#166--- -removing the aformentioned EN from clause 4.4.1.1.X.2 and keeping the use\/description of the Nnef_RetrieveInfoUAVFlight_Get and Nnef_UAVFlightAssistance_Create\/Notify as it has been introduced by S2-2410853 in SA WG2#165. #---SA2#165--- 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-2412588. Revised in parallel session to S2-2413009.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19620,"status":"revised","reservation_date":"2024-11-25 06:25:53","uploaded":"2024-11-25 06:51:08","revisionof":"S2-2412588","revisedto":"S2-2413009","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":141.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412758.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412759","title":"Update Nnef_UAVFlightAssistance_Create service operation","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the Nnef_UAVFlightAssistance_Create service operation.","secretary_remarks":"Revision of S2-2412589. 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":19710,"status":"noted","reservation_date":"2024-11-25 06:25:54","uploaded":"2024-11-25 06:51:08","revisionof":"S2-2412589","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":152.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412759.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.1.1.3.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412986","title":"Addressing the ENs on message names","source":"Ericsson, Huawei, ETRI","contact":"Seung-Ik Lee","contact-id":88159,"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 - The operation of Nnef_UAVFlightAssistance_Notify is corrected to use Subscribe\/Notify model in cl. 5.12.3.","secretary_remarks":"Revision of S2-2411746. 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":19790,"status":"agreed","reservation_date":"2024-11-25 06:27:13","uploaded":"2024-11-25 06:51:10","revisionof":"S2-2411746","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":140.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-241493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412986.zip","group":"S2","meeting":"S2-166","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-2412987","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. @ SA WG2#166 - Modify 'height' to 'altitude' to use wording of aviation industry. - Add 'optional time restriction' to NTZ assistance information. - Clarify NOTE 3 in 5.x.","secretary_remarks":"Revision of S2-2412594. 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":19860,"status":"agreed","reservation_date":"2024-11-25 06:27:14","uploaded":"2024-11-25 06:51:10","revisionof":"S2-2412594","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":136.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"SP-241493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412987.zip","group":"S2","meeting":"S2-166","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-2413008","title":"Instructing a UAV to perform its altitude reporting","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -This CR proposes two options on how the CN can configure aerial UEs for altitude reporting, considering a flight path information received from a USS\/UTM. Option A: configuration (altitude threshold values, periodicity information) is sent to an aerial UE over the application layer from the USS\/UTM after the UAS NF determines these parameters. Option B: node-level signalling using either UE-associtated signalling or non-UE-associated signalling","secretary_remarks":"Revision of S2-2412756. 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":19590,"status":"agreed","reservation_date":"2024-11-25 06:27:32","uploaded":"2024-11-25 06:51:10","revisionof":"S2-2412756","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":150.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"SP-241493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2413008.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":true,"clauses_affected":"2, 5.X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2413009","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: #---SA2#166--- -removing the aformentioned EN from clause 4.4.1.1.X.2 and keeping the use\/description of the Nnef_RetrieveInfoUAVFlight_Get and Nnef_UAVFlightAssistance_Create\/Notify as it has been introduced by S2-2410853 in SA WG2#165. #---SA2#165--- 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-2412758. Agreed in parallel session. Depending on the response from CT WG3, this topic may need to be revisited. 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":19630,"status":"agreed","reservation_date":"2024-11-25 06:27:32","uploaded":"2024-11-25 06:51:10","revisionof":"S2-2412758","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.0.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":141.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"SP-241493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2413009.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.1.1.1, 4.4.1.1.3.1, 4.4.1.1.3.2, 4.4.1.1.3.3, 4.4.1.1.3.4, 4.4.1.1.X (new), 5.13.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2413010","title":"Clarification of Nnef_RetrieveInfoUAVFlight_Get service operation","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3","secretary_remarks":"Revision of S2-2412757. Agreed in parallel session. Revised to S2-2413027.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19640,"status":"revised","reservation_date":"2024-11-25 06:27:33","uploaded":"2024-11-25 06:51:10","revisionof":"S2-2412757","revisedto":"S2-2413027","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"UAS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2413010.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2413027","title":"LS on Clarification of Nnef_RetrieveInfoUAVFlight_Get service operation","source":"SA WG2","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. Attachments: TS 23.256 CR#0141","secretary_remarks":"Revision of S2-2413010. This LS OUT was approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":19650,"status":"approved","reservation_date":"2024-11-25 06:27:39","uploaded":"2024-11-25 06:51:10","revisionof":"S2-2413010","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"UAS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2413027.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500072","title":"LS from SA WG6: Reply LS on clarification related to the QoS and QoE parameters for the support of real time UAV flight path monitoring assistance.","source":"SA WG6","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 would like to thank CT WG3 for requesting clarification related to the real time UAV flight path monitoring assistance procedures defined in clause 7.9 of 3GPP TS 23.255. Q1 - What are the QoS parameters and QoE parameters to be considered, whose thresholds define the triggering events in the above mentioned use case? A1 - The QoS parameters thresholds to be considered for triggering events are jitter, latency, throughput, error rate and packet loss. The QoE parameters thresholds to be considered for triggering events are the distance and the time deviation relative to the planned flight path. Q2 - How the UAS application specific server obtains\/does the measurement of these QoS and QoE parameters values? A2 - In the procedure defined in clause 7.9, the UAS application specific server does not perform measurements. The UAS application specific server provides the QoS\/QoE parameters to be considered at the UAV for triggering reports as described in clause 7.9.2.1, and receives the reports as described in clause 7.9.2.3. SA WG6 would also like to indicate that 3GPP TS 23.255 will be updated with the above clarifications, and that such clarifications have been agreed in CR S6-245617.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":17910,"status":"noted","reservation_date":"2024-12-29 10:58:23","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG2","lsoriginalls":"S6-245642","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500072.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500113","title":"Clarifications to NTZ support","source":"Qualcomm Incorporated","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies the UE procedures for NTZ enforcement in the UAV UE across NAS and AS","secretary_remarks":"r07 agreed. Revised in e-mail session to S2-2501305.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":18100,"status":"revised","reservation_date":"2025-01-08 00:14:09","uploaded":"2025-01-13 18:28:06","revisionof":"","revisedto":"S2-2501305","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":154.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500113.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500114","title":"[DRAFT] LA on NTZ support in UAV UE","source":"QUALCOMM Europe Inc. - Spain","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, RAN WG2. CC: -. Attachments: S2-2500113.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":18120,"status":"noted","reservation_date":"2025-01-08 00:16:11","uploaded":"2025-01-13 18:28:06","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"UAS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500114.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500318","title":"Clarification on reporting velocity in UAV location reporting procedure","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification is made on reporting velocity information in UAV location reporting procedure","secretary_remarks":"r01 agreed. Revised in e-mail session to S2-2501302.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":17980,"status":"revised","reservation_date":"2025-01-13 04:25:05","uploaded":"2025-01-14 08:43:34","revisionof":"","revisedto":"S2-2501302","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":155.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500318.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":true,"clauses_affected":" 5.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500385","title":"Removing EN about border-crossing point","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 5.13.2 - Remove the EN mentioned above.","secretary_remarks":"Approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":18040,"status":"agreed","reservation_date":"2025-01-13 14:17:40","uploaded":"2025-01-14 03:30:54","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":156.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-250060","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500385.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.13.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500438","title":"Addressing the EN on border-crossing point","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -replacing the term 'border-crossing point' with 'border-crossing zone'","secretary_remarks":"Postponed in e-mail session","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":17920,"status":"postponed","reservation_date":"2025-01-13 17:07:27","uploaded":"2025-01-14 21:46:10","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":162.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500438.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.1.1.3.3, 4.4.1.1.3.5, 4.4.1.1.4.2, 5.13.1, 5.13.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500439","title":"Correcting the USS changeover procedure","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -Explicitly stating in the figure and in Step 20 description that the serving USS conveys the aformentioned information over the application layer, i.e., no NAS impact.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":18050,"status":"noted","reservation_date":"2025-01-13 17:07:29","uploaded":"2025-01-14 21:46:10","revisionof":"","revisedto":"S2-2501619","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":163.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500439.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.13.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500440","title":"Indicating optional steps of the pre-flight procedure","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -Specifying in Step 6 that some of the remaining steps of the procedure are skipped in cases when the NEF determines to reject the request, but, if the NEF determines to proceed, it is specified with which steps the procedure needs to c","secretary_remarks":"Approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":18010,"status":"agreed","reservation_date":"2025-01-13 17:07:30","uploaded":"2025-01-14 21:46:10","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":164.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-250060","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500440.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.12.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500441","title":"Timestamping UAV's altitude information reports","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifying in Step 2b that a time stamp\/report ID is added\/assigned by the NG-RAN node (not provided by the UE) when it receives the UE's altitude information report.","secretary_remarks":"Not handled at CC#4. Postponed","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":18060,"status":"postponed","reservation_date":"2025-01-13 17:07:30","uploaded":"2025-01-14 21:46:10","revisionof":"","revisedto":"S2-2501620","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":165.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500441.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.16.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500475","title":"Service operation update","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update service operations to support altitude reporting.","secretary_remarks":"r01 agreed. Revised in e-mail session to S2-2501300.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":17930,"status":"revised","reservation_date":"2025-01-14 01:45:43","uploaded":"2025-01-14 07:09:23","revisionof":"","revisedto":"S2-2501300","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":167.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500475.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500476","title":"Update Namf_EventExposure","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update service operation to support altitude reporting.","secretary_remarks":"Approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":18090,"status":"agreed","reservation_date":"2025-01-14 01:45:44","uploaded":"2025-01-14 07:09:23","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.502","crspecversion":"19.2.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":5245.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-250060","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500476.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500513","title":"Altitude reporting update","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description on how to request all aerial UEs in a specifc TA(s) or NG-RAN node(s) to perform altitude reporting. Add description on how does the aerial UE decide the UE's flight altitude meets the provided altitude reporting conditi","secretary_remarks":"r03 agreed. Revised in e-mail session to S2-2501304.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":18070,"status":"revised","reservation_date":"2025-01-14 03:58:50","uploaded":"2025-01-14 07:09:23","revisionof":"","revisedto":"S2-2501304","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":171.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500513.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500828","title":"Correction on USS changeover aspects","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Following changes are proposed to clause 5.13.2 'Procedure for USS changeover during a UAV flight': add parameter 'information about the starting and ending points for the flight' in step 4. Replace the service operation 'Nnef_UAVFlight","secretary_remarks":"r01 agreed. Revised in e-mail session to S2-2501303.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":18020,"status":"revised","reservation_date":"2025-01-14 11:49:22","uploaded":"2025-01-14 12:56:26","revisionof":"","revisedto":"S2-2501303","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":175.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500828.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.13.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500829","title":"Correction on UAV service operation description","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change 1: update clause 4.4.1.1.3.3, Nnef_UAVFlightAssistance_Create service operation: Remove the 'pre-fligfht panning' from 'Input, Required'. Add parameters 'planned flight path information for each of the segment of the paths served","secretary_remarks":"r01 agreed. Revised in e-mail session to S2-2501301.","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":17950,"status":"revised","reservation_date":"2025-01-14 11:49:23","uploaded":"2025-01-14 12:56:26","revisionof":"","revisedto":"S2-2501301","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":176.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500829.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.1.1.3, 4.4.1.1.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500830","title":"Provisioning of static flight path information","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add another option of identifing a UAV flight path. When the USS provisions a UAV flight path to the NEF\/UAS NF, the USS may provide a list Geohash codes or a flight path ID. The network derives the geographic location based on the pre-","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":18000,"status":"noted","reservation_date":"2025-01-14 11:49:24","uploaded":"2025-01-14 12:56:26","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":177.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500830.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.12.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500831","title":"Clarification of USS list provisioning","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify the two case of USS list provisioning as follows: In case of in-flight monitoring, the serving USS based on the UAV flight path, determines a list of USSes that covers the geographic areas of the flight path. U","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":17970,"status":"noted","reservation_date":"2025-01-14 11:49:26","uploaded":"2025-01-14 12:56:26","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":178.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500831.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501300","title":"Service operation update","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update service operations to support altitude reporting.","secretary_remarks":"Revision of S2-2500475r01. Approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":17940,"status":"agreed","reservation_date":"2025-01-25 09:56:11","uploaded":"2025-01-28 08:51:08","revisionof":"S2-2500475","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":167.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-250060","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501300.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501301","title":"Correction on UAV service operation description","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change 1: update clause 4.4.1.1.3.3, Nnef_UAVFlightAssistance_Create service operation: Remove the 'pre-fligfht panning' from 'Input, Required'. Add parameters 'planned flight path information for each of the segment of the paths served by different USS', 'planned flight path information for each of the segment of the paths served by different USS' Change 2: update clause 4.4.1.1.4.2, Nnef_RetrieveInfoUAVFlight_Get service operation: Add parameter 'information about the starting and ending points for the flight', in the 'Input Optional'","secretary_remarks":"Revision of S2-2500829r01. Approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":17960,"status":"agreed","reservation_date":"2025-01-25 09:56:12","uploaded":"2025-01-28 08:51:08","revisionof":"S2-2500829","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":176.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-250060","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501301.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.4.1.1.3, 4.4.1.1.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501302","title":"Clarification on reporting velocity in UAV location reporting procedure","source":"China Mobile, Nokia, Nokia Shanghai Bell","contact":"Aihua Li","contact-id":58162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification is made on reporting velocity information in UAV location reporting procedure","secretary_remarks":"Revision of S2-2500318r01. Approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":17990,"status":"agreed","reservation_date":"2025-01-25 09:56:13","uploaded":"2025-01-28 08:51:08","revisionof":"S2-2500318","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":155.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-250060","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501302.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 5.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501303","title":"Correction on USS changeover aspects","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Following changes are proposed to clause 5.13.2 'Procedure for USS changeover during a UAV flight': add parameter 'information about the starting and ending points for the flight' in step 4. Replace the service operation 'Nnef_UAVFlightAssistance_Get' with 'Nnef_RetrieveInfoUAVFlight_Get' in step 5","secretary_remarks":"Revision of S2-2500828r01. Approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":18030,"status":"agreed","reservation_date":"2025-01-25 09:56:13","uploaded":"2025-01-28 08:51:08","revisionof":"S2-2500828","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":175.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-250060","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501303.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.13.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501304","title":"Altitude reporting update","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add introduction of UE altitude reporting procedure in clause 5.16.3 in clause 5.16.1. Clarify that the USS provides altitude and time stamp of altitude to UAS NF\/NEF.","secretary_remarks":"Revision of S2-2500513r03. Approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":18080,"status":"agreed","reservation_date":"2025-01-25 09:56:14","uploaded":"2025-01-28 08:51:08","revisionof":"S2-2500513","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":171.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-250060","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501304.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501305","title":"Clarifications to NTZ support","source":"Qualcomm Incorporated","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies the UE procedures for NTZ enforcement in the UAV UE.","secretary_remarks":"Revision of S2-2500113r07. Approved","agenda_item_sort_order":131,"ainumber":"19.10.2","ainame":"Phase 3 for UAS, UAV and UAM (UAS_Ph3)","tdoc_agenda_sort_order":18110,"status":"agreed","reservation_date":"2025-01-25 09:56:15","uploaded":"2025-01-28 08:51:08","revisionof":"S2-2500113","revisedto":"","release":"Rel-19","crspec":"23.256","crspecversion":"19.1.0","workitem":[{"winame":"UAS_Ph3"}],"crnumber":154.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-250060","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501305.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]