[{"name":"S2-2210212","title":"LS from CT WG4: LS on UAV authorization container","source":"CT WG4","contact":"Waqar Zia","contact-id":99429,"tdoctype":"LS in","for":"Action","abstract":"According to TS 23.256 clause 5.2.5.2.1, the SMF re-uses UUAA-SM procedure in clause 5.2.3.2 for C2 authorization, with the following differences: i) for C2 authorization, step 0 in clause 5.2.3.2 also includes C2 Aviation Payload, and ii) the authorization result in step 4-7 in clause 5.2.3.2 also includes C2 authorization result. SMF in both the cases transparently forwards the aviation payload to USS (via UAS-NF) and the authorization result to the UE. There is currently no consensus in CT WG4 on whether the SMF needs any additional information, e.g. the type of payload (i.e. whether the message contains C2- and\/or UUAA-Aviation Payload) to perform the procedures from and towards the UE. Questions: CT WG4 would like to ask SA WG2 the following questions: 1) Does the SMF need to identify the type of payload (C2- or UUAA-Aviation Payload) to perform the procedures from and towards the UE? 2) If yes, how is this identification performed, and what are the impacted procedures?. Action: SA WG2 is requested to respond to the above question.","secretary_remarks":"Resubmission of (replied to) S2-2208104 from S2#153-e","agenda_item_sort_order":50,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":11671,"status":"available","reservation_date":"2022-10-21 13:22:36","uploaded":"2022-11-11 08:25:41","revisionof":"S2-2208104","revisedto":"S2-2300017","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"C4-223513","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154_Toulouse_2022-11\/Docs\/S2-2210212.zip","group":"S2","meeting":"S2-154","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2210350","title":"Corrections to functionality and procedure at UAS NF for C2 authorization","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UUAA-SM and C2 authorization procedures descriptions are updated to clarify that: A UUAA-SM request shall via the UAS-NF be forwarded for authorization by the USS also for the case UUAA-MM already has been granted for the UAV\/UE. This to enable a USS\/UAS specific policy to be activated on the established PDU session. The indicator that UUAA-MM has already been performed sent from the AMF to the SMF is removed since it then is not needed. That for a C2 authorization request that is not performed together with a request for UUAA-SM the UAS NF\/NEF checks that there is an active UUAA for the GPSI and that a C2 aviation payload is provided with the request and if so, forwards the received authorization request to the USS. If not, no request will be sent to the USS and the corresponding session establishment\/modification request will be rejected In chapter 5.2.5.2.2 the combined paragraph for step 4-5 was on a previous meeting split into a separate paragraph for step 4 and step 5. The combined paragraph for 4-5 was however then by mistake not removed from the document after that meeting but this is done now.","secretary_remarks":"Revision of (Postponed) S2-2208296. Revised to S2-2210930.","agenda_item_sort_order":50,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":11070,"status":"revised","reservation_date":"2022-03-11 23:27:54","uploaded":"2022-11-04 22:06:04","revisionof":"S2-2208296","revisedto":"S2-2210930","release":"Rel-17","crspec":"23.256","crspecversion":"17.4.0","workitem":[{"winame":"ID_UAS"}],"crnumber":68.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154_Toulouse_2022-11\/Docs\/S2-2210350.zip","group":"S2","meeting":"S2-154","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2210857","title":"Addition of C2 Authorization Payload to C2 Authorization request during UUAA-SM procedure in 5GS","source":"Qualcomm Incorporated","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the C2 Authorization Payload to step 4 of 5.2.5.2.1.","secretary_remarks":"Merged into S2-2210930.","agenda_item_sort_order":50,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":11090,"status":"merged","reservation_date":"2022-04-11 17:44:15","uploaded":"2022-11-04 17:46:08","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.256","crspecversion":"17.4.0","workitem":[{"winame":"ID_UAS"}],"crnumber":71.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154_Toulouse_2022-11\/Docs\/S2-2210857.zip","group":"S2","meeting":"S2-154","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2210930","title":"Corrections to functionality and procedure at UAS NF for C2 authorization","source":"Ericsson, Nokia, Nokia Shanghai Bell, Samsung","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UUAA-SM and C2 authorization procedures descriptions are updated to clarify that: A UUAA-SM request shall via the UAS-NF be forwarded for authorization by the USS also for the case UUAA-MM already has been granted for the UAV\/UE. This to enable a USS\/UAS specific policy to be activated on the established PDU session. The indicator that UUAA-MM has already been performed sent from the AMF to the SMF is removed since it then is not needed. In chapter 5.2.5.2.2 the combined paragraph for step 4-5 was on a previous meeting split into a separate paragraph for step 4 and step 5. The combined paragraph for 4-5 was however then by mistake not removed from the document after that meeting but this is done now.","secretary_remarks":"Revision of S2-2210350, merging and S2-2210857. Agreed in parallel session. Block approved","agenda_item_sort_order":50,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":11080,"status":"agreed","reservation_date":"2022-11-22 06:30:53","uploaded":"2022-11-22 07:01:15","revisionof":"S2-2210350","revisedto":"","release":"Rel-17","crspec":"23.256","crspecversion":"17.4.0","workitem":[{"winame":"ID_UAS"}],"crnumber":68.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-221075","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154_Toulouse_2022-11\/Docs\/S2-2210930.zip","group":"S2","meeting":"S2-154","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300017","title":"LS from CT WG4: LS on UAV authorization container","source":"CT WG4","contact":"Waqar Zia","contact-id":86053,"tdoctype":"LS in","for":"Action","abstract":"According to TS 23.256 clause 5.2.5.2.1, the SMF re-uses UUAA-SM procedure in clause 5.2.3.2 for C2 authorization, with the following differences: i) for C2 authorization, step 0 in clause 5.2.3.2 also includes C2 Aviation Payload, and ii) the authorization result in step 4-7 in clause 5.2.3.2 also includes C2 authorization result. SMF in both the cases transparently forwards the aviation payload to USS (via UAS-NF) and the authorization result to the UE. There is currently no consensus in CT WG4 on whether the SMF needs any additional information, e.g. the type of payload (i.e. whether the message contains C2- and\/or UUAA-Aviation Payload) to perform the procedures from and towards the UE. Questions: CT WG4 would like to ask SA WG2 the following questions: 1) Does the SMF need to identify the type of payload (C2- or UUAA-Aviation Payload) to perform the procedures from and towards the UE? 2) If yes, how is this identification performed, and what are the impacted procedures?. Action: SA WG2 is requested to respond to the above question.","secretary_remarks":"Revision of postponed S2-2210212 from S2#154. Resubmission of (replied to) S2-2208104 from S2#153-e. Noted","agenda_item_sort_order":50,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12260,"status":"noted","reservation_date":"2022-12-19 08:34:54","uploaded":"2022-12-19 08:35:58","revisionof":"S2-2210212","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"C4-223513","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300017.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300869","title":"Addressing Editor Notes","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1: There is no update needed to remove the EN under UUAA-MM procedure 2: Step 6 and step 7 to be swapped and remove the EN under PDU session modiciation for C2 communication.","secretary_remarks":"r02 agreed. Revised to S2-2302086.","agenda_item_sort_order":50,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12240,"status":"revised","reservation_date":"2023-09-01 11:18:08","uploaded":"2023-01-09 11:45:17","revisionof":"","revisedto":"S2-2302086","release":"Rel-17","crspec":"23.256","crspecversion":"17.5.0","workitem":[{"winame":"ID_UAS"}],"crnumber":73.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300869.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2302086","title":"Addressing Editor Notes","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1: There is no update needed to remove the EN under UUAA-MM procedure 2: Step 6 and step 7 to be swapped and remove the EN under PDU session modiciation for C2 communication.","secretary_remarks":"Revision of S2-2300869r02. Approved","agenda_item_sort_order":50,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12250,"status":"agreed","reservation_date":"2023-01-24 07:49:42","uploaded":"2023-01-24 08:01:09","revisionof":"S2-2300869","revisedto":"","release":"Rel-17","crspec":"23.256","crspecversion":"17.5.0","workitem":[{"winame":"ID_UAS"}],"crnumber":73.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-230041","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2302086.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]