[{"name":"S2-2201927","title":"Reply LS on 3GPP SA1 clarifications on problematic UAV","source":"SA WG1","contact":"Edward Hall","contact-id":90585,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 thanks ACJA and SA WG2 for their liaisons. SA WG1 has discussed the questions around the 22.125 requirement [R-5.1-017], related to UTM detection of problematic UAVs and possible target scenarios (as indicated by ACJA), concluding that - there are different views and understanding on which scenarios should be applicable or not - the topic would require more investigation, and maybe further studied in future releases As such, SA WG1 have agreed a 22.125 CR, attached to this LS, clarifying that the applicability of the existing requirement should be considered FFS (for further study). Action: SA WG1 asks ACJA, SA WG2, and SA WG6 to take the above into account.","secretary_remarks":"Revision of Postponed S2-2200062 from S2#149E. Noted","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12380,"status":"noted","reservation_date":"2022-03-25 17:03:58","uploaded":"2022-03-28 08:00:13","revisionof":"S2-2200062","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6, SA WG2, GSMA-ACJA","Cc":"SA WG3","lsoriginalls":"S1-214238","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201927.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201934","title":"LS from CT WG4: LS on SMF initiated reauthorization","source":"CT WG4","contact":"Waqar Zia","contact-id":86053,"tdoctype":"LS in","for":"Action","abstract":"Clause 5.2.5.2.2 of 3GPP TS 23.256 lists service operation Nnef_Auth_ReAuth_Request, however, clause 4.4 does not list this operation for SMF-initiated reauthorization. CT WG4 further observes that the attributes listed for Nef_Auth_ReAuth_Request are a subset of the attributes of AuthenticateAuthorize service operation of Nef_Authentication service. Keeping this in view, CT WG4 does not see a need of Nnef_Auth_ReAuth_Request service operation and have used the same AuthenticateAuthorize service operation for the purpose of SMF-initiated reauthorization in 3GPP TS 29.256. Question to SA WG2: Is CT WG4's interpretation correct in this regard? Further, CT WG4 observes that clauses 5.2.5.2 and 5.2.5.3 of 3GPP TS 23.256 refer to service operations Nnef_Auth_Request and Nnef_Auth_Response at various instances, while these service operation names are not aligned with the service operations listed in clause 4.4 of 3GPP TS 23.256. Action: SA WG2 is requested to answer the question above, and update stage-2 in the light of the question and the observation above as deemed necessary.","secretary_remarks":"Revision of Postponed S2-2201270 from S2#149E. Response drafted in S2-2202361, S2-2202446. Final response in S2-2203037","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12390,"status":"replied to","reservation_date":"2022-03-25 17:03:58","uploaded":"2022-03-28 08:00:13","revisionof":"S2-2201270","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-221445","lsreply":"S2-2203037, S2-2203037","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201934.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202245","title":"Correcting errors for UAV-C address","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Faulty references corrected in 5.2.5.3. Aligning step 8 in clause 5.2.3.3 with e.g. 5.2.4.4 (UAV Re-authorization procedure in EPS) by referencing 23.401. Replaced 'IP address' with 'identifier' for pairing related E2E communication as IP addresses are not always possible to use as identifiers. NOTE: It is assumed that the term UAV-C 'identifier' should be used for pairing related E2E communication between the UAV and the USS. However, when the USS requests policies to be setup for C2 related communication in a 3GPP network, the UAV-C 'IP address' will be required. That is, when calling re-authorization procedures it should be UAV-C 'identifier' and when calling the C2 policy configuration procedures it should be UAV-C 'IP-address' that is used.","secretary_remarks":"r02 agreed. Revised to S2-2203039","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12470,"status":"revised","reservation_date":"2022-03-28 19:37:41","uploaded":"2022-03-29 21:10:21","revisionof":"","revisedto":"S2-2203039","release":"Rel-17","crspec":"23.256","crspecversion":"17.2.0","workitem":[{"winame":"ID_UAS"}],"crnumber":59.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202245.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202246","title":"Correcting terminology inconsistencies","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: There is some confusion in the TS on the naming of the transparent C2 related information that is provided from the UE to USS and vice versa. In some places the term 'C2 Aviation Payload' is used to name both the container in request messages and response messages. In other places, e.g. the C2 authorization procedures, there is a distinction in naming between request and response messages. The term in request messages is 'C2 Aviation Payload' and in response messages 'C2 Authorization Result'. The TS is aligned to use the latter naming principle.","secretary_remarks":"Merged into S2-2203040","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12490,"status":"merged","reservation_date":"2022-03-28 19:37:43","uploaded":"2022-03-29 21:10:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.256","crspecversion":"17.2.0","workitem":[{"winame":"ID_UAS"}],"crnumber":60.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202246.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202361","title":"[DRAFT] LS Reply on SMF initiated reauthorization","source":"QUALCOMM Europe Inc. - Italy","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: CT WG3","secretary_remarks":"Response to S2-2201934. Merged into S2-2203037","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12400,"status":"merged","reservation_date":"2022-03-29 07:27:30","uploaded":"2022-03-29 15:55:17","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202361.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202362","title":"Corrections to SMF-initiated and NEF-initiated re-authorization","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the name of the services to align to clause 4.4.","secretary_remarks":"Merged into S2-2203041","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12500,"status":"merged","reservation_date":"2022-03-29 07:29:13","uploaded":"2022-03-29 15:55:17","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.256","crspecversion":"17.2.0","workitem":[{"winame":"ID_UAS"}],"crnumber":61.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202362.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202367","title":"[DRAFT] LS Reply on NEF-initiated reauthorization","source":"QUALCOMM Europe Inc. - Italy","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4","secretary_remarks":"Response to S2-2202778. r01 agreed. Revised to S2-2203038","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12440,"status":"revised","reservation_date":"2022-03-29 07:33:29","uploaded":"2022-03-29 15:55:17","revisionof":"","revisedto":"S2-2203038","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202367.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202396","title":"Corrections to Naf(Nnef)_Authentication_AuthenticateAuthorize service operation","source":"LG Electronics","contact":"Jaewoo Kim","contact-id":92249,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause\u00a04.4.1.1.2.2, Clause\u00a04.4.1.2.2.2: 'Success\/Fail indication, (GPSI)' in Output, Required is moved to Output, Conditional Required. Therefore, Output, Required is changed to None. Add description to when 'Success\/Fail indication, (GPSI)' is not required.","secretary_remarks":"Approved","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12510,"status":"agreed","reservation_date":"2022-03-29 08:00:21","uploaded":"2022-03-29 12:31:14","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.256","crspecversion":"17.2.0","workitem":[{"winame":"ID_UAS"}],"crnumber":62.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220403","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202396.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202439","title":"Clarification and Correction on C2 payload","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify and correct terms about C2 payload. Replace UAV-C IP address to UAV-C identifier in UAV-C replacement procedures.","secretary_remarks":"r04 agreed. Revised to S2-2203040, merging S2-2202246","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12520,"status":"revised","reservation_date":"2022-03-29 08:40:32","uploaded":"2022-03-29 11:20:14","revisionof":"","revisedto":"S2-2203040","release":"Rel-17","crspec":"23.256","crspecversion":"17.2.0","workitem":[{"winame":"ID_UAS"}],"crnumber":63.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202439.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202446","title":"[DRAFT] LS OUT SMF initiated reauthorization; Response to S2-2201934","source":"Nokia, Nokia Shanghai Bell","contact":"Pallab Gupta","contact-id":87959,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4, CT WG3. CC:","secretary_remarks":"Response to S2-2201934. r00 agreed. Revised to S2-2203037, merging S2-2202361","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12410,"status":"revised","reservation_date":"2022-03-29 08:46:53","uploaded":"2022-03-29 12:37:18","revisionof":"","revisedto":"S2-2203037","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"ID_UAS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202446.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202447","title":"Corrections to service operation names","source":"Nokia, Nokia Shanghai Bell","contact":"Pallab Gupta","contact-id":87959,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Figure 5.2.5.2.2-1 and related procedure description in the clause 5.2.5.2.2 is corrected to reflect service operation names Nnef_Authentication_AuthenticateAuthorize and Naf_Authentication_AuthenticateAuthorize Figure 5.2.5.2.3-1 and related procedures in clause 5.2.5.2.3 is corrected to reflect the correct operation name. Figure 5.2.5.3.1-1 and related procedures in clause 5.2.5.3.1 is corrected to reflect the correct operation name. In various other clauses the Service operation names are aligned with the service operation defined in clause 4.4.1","secretary_remarks":"r01 agreed. Revised to S2-2203041, merging S2-2202362","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12540,"status":"revised","reservation_date":"2022-03-29 08:46:53","uploaded":"2022-03-29 12:37:18","revisionof":"","revisedto":"S2-2203041","release":"Rel-17","crspec":"23.256","crspecversion":"17.2.0","workitem":[{"winame":"ID_UAS"}],"crnumber":64.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202447.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202778","title":"LS from CT WG3: LS on NEF-initiated reauthorization","source":"CT WG3","contact":"Waqar Zia","contact-id":86053,"tdoctype":"LS in","for":"Action","abstract":"Clause 5.2.5.2.2 of 3GPP TS 23.256 lists service operation Naf_Auth_ReAuth_Request, however, clause 4.4 of 3GPP TS 23.256 does not list this operation for NEF-initiated reauthorization. CT WG3 further observes that the attributes listed for Naf_Auth_ReAuth_Request are a subset of the attributes of AuthenticateAuthorize service operation of Naf_Authentication service. Keeping this in view, CT WG3 does not see a need of Naf_Auth_ReAuth_Request service operation and has used the same AuthenticateAuthorize service operation for the purpose of NEF-initiated reauthorization in 3GPP TS 29.255. Question to SA WG2: Is CT WG3 interpretation correct in this regard? Further, CT WG3 observes that clauses 5.2.5.2 and 5.2.5.3 of 3GPP TS 23.256 refer to service operations Naf_Auth_Request and Naf_Auth_Response at various instances, while these service operation names are not aligned with the service operations listed in clause 4.4 of 3GPP TS 23.256. Action: SA WG2 is requested to answer the question above, and update stage-2 in the light of the question and the observation as deemed necessary.","secretary_remarks":"Response drafted in S2-2202367. Final response in S2-2203038","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12430,"status":"replied to","reservation_date":"2022-03-29 15:34:29","uploaded":"2022-03-29 17:47:55","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-221444","lsreply":"S2-2203038, S2-2203038","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202778.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203037","title":"[DRAFT] LS OUT SMF initiated reauthorization; Response to S2-2201934","source":"Nokia, Nokia Shanghai Bell","contact":"Pallab Gupta","contact-id":87959,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4, CT WG3. CC:","secretary_remarks":"Revision of S2-2202446r00, merging S2-2202361. Approved","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12420,"status":"approved","reservation_date":"2022-04-13 09:51:58","uploaded":"2022-04-13 15:41:12","revisionof":"S2-2202446","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"ID_UAS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2201934","lsto":"CT WG4, CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203037.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203038","title":"[DRAFT] LS Reply on NEF-initiated reauthorization","source":"QUALCOMM Europe Inc. - Italy","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4","secretary_remarks":"Revision of S2-2202367r01. Approved","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12450,"status":"approved","reservation_date":"2022-04-13 09:51:58","uploaded":"2022-04-13 15:41:12","revisionof":"S2-2202367","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2202778","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203038.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203039","title":"Correcting errors for UAV-C address","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Faulty references corrected in 5.2.5.3. Aligning step 8 in clause 5.2.3.3 with e.g. 5.2.4.4 (UAV Re-authorization procedure in EPS) by referencing 23.401.","secretary_remarks":"Revision of S2-2202245r02. Approved","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12480,"status":"agreed","reservation_date":"2022-04-13 09:51:58","uploaded":"2022-04-14 09:01:19","revisionof":"S2-2202245","revisedto":"","release":"Rel-17","crspec":"23.256","crspecversion":"17.2.0","workitem":[{"winame":"ID_UAS"}],"crnumber":59.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220403","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203039.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203040","title":"Clarification and Correction on C2 payload","source":"Huawei, HiSilicon, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify and correct terms about C2 payload. Replace UAV-C IP address to UAV-C identifier in UAV-C replacement procedures.","secretary_remarks":"Revision of S2-2202439r04, merging S2-2202246. Approved","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12530,"status":"agreed","reservation_date":"2022-04-13 09:51:59","uploaded":"2022-04-14 09:01:19","revisionof":"S2-2202439","revisedto":"","release":"Rel-17","crspec":"23.256","crspecversion":"17.2.0","workitem":[{"winame":"ID_UAS"}],"crnumber":63.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220403","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203040.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203041","title":"Corrections to service operation names","source":"Nokia, Nokia Shanghai Bell, Qualcomm Incorporated","contact":"Pallab Gupta","contact-id":87959,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Figure 5.2.5.2.2-1 and related procedure description in the clause 5.2.5.2.2 is corrected to reflect service operation names Nnef_Authentication_AuthenticateAuthorize and Naf_Authentication_AuthenticateAuthorize Figure 5.2.5.2.3-1 and r","secretary_remarks":"Revision of S2-2202447r01, merging S2-2202362. Approved","agenda_item_sort_order":15,"ainumber":"8.7","ainame":"Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS)","tdoc_agenda_sort_order":12550,"status":"agreed","reservation_date":"2022-04-13 09:52:00","uploaded":"2022-04-14 09:01:19","revisionof":"S2-2202447","revisedto":"","release":"Rel-17","crspec":"23.256","crspecversion":"17.2.0","workitem":[{"winame":"ID_UAS"}],"crnumber":64.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220403","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203041.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]