[{"name":"S2-2201928","title":"Reply LS on UE location aspects in NTN","source":"SA WG3","contact":"Wei Zhou","contact-id":90017,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to thank RAN WG2 for their LS on UE location aspects in NTN. SA WG3 discussed the assumption of RAN WG2, and could not agree on specific security issues caused by the UE sending location information to the gNB. However, SA WG3 believes that allowing the UE to send unprotected location information will expose the UE to more risks than not sending it. If a permanent\/temporary ID (e.g. SUPI\/IMSI, 5G GUTI) is sent together with the location information unprotected at initial access, SA WG3 is of the view that there could be a privacy issue. SA WG3 would also like to remind that the UE location information the network is relying on for AMF selection may not be reliable due to a lack of integrity protection. Therefore SA WG3 recommends that RAN WG2 defines a solution that avoids sending unprotected UE location information to the gNB. Action: SA WG3 would like RAN WG1, RAN WG2, RAN WG3, SA WG2, SA WG3-LI and CT WG1 to take the above feedback into account.","secretary_remarks":"Revision of Postponed S2-2200065 from S2#149E. Noted","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13420,"status":"noted","reservation_date":"2022-03-25 17:03:58","uploaded":"2022-03-28 08:00:13","revisionof":"S2-2200065","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1, SA WG3-LI, SA WG2, RAN WG3, RAN WG1","lsoriginalls":"S3-214360","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201928.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-2201931","title":"LS from RAN WG3: LS on RAN Initiated Release due to out-of-PLMN area condition","source":"RAN WG3","contact":"Luis Lopes","contact-id":84588,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 has agreed in principle that a gNB shall be able to trigger a context release request procedure when it detects that a connected mode UE is outside the geographical coverage area of its PLMN. RAN WG3 has agreed to add a new cause value 'UE not in PLMN serving area' in NGAP to be sent within the UE CONTEXT RELEASE REQUEST message. When receiving this cause value the AMF may consider additional actions (e.g. LCS check \/ NAS deregistration etc.) before UE context release. RAN WG3 would like SA WG2 to confirm RAN WG3's understanding. Action: RAN WG3 kindly asks SA WG2 to provide feedback on the above understanding.","secretary_remarks":"Revision of Postponed S2-2200417 from S2#149E. Responses drafted in S2-2201981, S2-2202803. Final response in S2-2203242","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13430,"status":"replied to","reservation_date":"2022-03-25 17:03:58","uploaded":"2022-03-28 08:00:13","revisionof":"S2-2200417","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, RAN WG2","lsoriginalls":"R3-221379","lsreply":"S2-2203242, S2-2203242","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201931.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-2201943","title":"LS from RAN WG2: LS on UE location during initial access in NTN","source":"RAN WG2","contact":"Nicolas Chuberre","contact-id":21633,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 had decided (see R2-2109216) that the UE may report to the NG-RAN its coarse GNSS coordinates during initial access (before AS security is activated).The reporting would be under network control (i.e. it could be disabled if\/when needed). Following liaisons from SA WG2, SA WG3 and RAN WG3 (see R2-2200145\/S2-2109337, R2-2200149\/S3-214360, R2-2202542\/S3i200056) on this, RAN WG2 is discussing how to progress and requires the views of SA WG2 and RAN WG3 to take its decision. Due to possible privacy issues indicated by SA WG3, RAN WG2 is likely to decide that UE does not report to the NG-RAN its coarse GNSS coordinates during initial access (before AS security is activated), for example, for service request and registration area update procedures. RAN WG2 assumes UE location information can be reported after AS security is activated and network has NTN specific user consent. RAN WG2 has asked SA WG3 to work on the NTN specific user consent in Rel-17. RAN WG2 also understands that, if needed, NG-RAN can reselect an AMF serving a PLMN corresponding to the available UE's current location. This location can be determined by the AMF by invoking UE location procedure (LCS) in connected mode(once AS security is activated) and provided to the NG-RAN. RAN WG2 would then like to ask SA WG2\/RAN WG3 if it's acceptable that no UE location information is reported at the NG-RAN in a NTN network during initial access. Action: RAN WG2 kindly asks SA WG2, RAN WG3 to answer the question above.","secretary_remarks":"Already replied to in S2-2201540. Noted","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13440,"status":"noted","reservation_date":"2022-03-25 17:03:58","uploaded":"2022-03-28 10:15:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3","Cc":"CT WG1, SA WG3","lsoriginalls":"R2-2202057","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201943.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-2201953","title":"LS from RAN WG2: LS on UE location in connected mode in NTN","source":"RAN WG2","contact":"Nicolas Chuberre","contact-id":21633,"tdoctype":"LS in","for":"Information","abstract":"Based on SA WG3 (see R2-2200149\/S3-214360 'Reply LS on UE location aspects in NTN' (CATT)) and SA WG2 feedbacks (see R2-2203829\/S2-2201540 'LS Response to LS on UE location during initial access in NTN' (QC)), RAN WG2 discussed an alternative solution described here below: RAN WG2 assumes a normative solution for user consent framework of TS 33.501 to specifically cover NTN will not be agreed upon in Rel-17 by SA WG3. In case other methods of obtaining user consent (e.g., subscription based) at NG-RAN would not be possible in Rel-17, RAN WG2 is then considering the solution where, upon network request, after AS security in connected mode is established, a UE can report a coarse UE location information (X most Significant Bits of its GNSS coordinates with accuracy around 2km level) to the NG-RAN without a new explicit 'NTN specific' user consent. Specifically for Rel-17, RAN WG2 is considering the implicit user consent approach where: - in connected mode, the network can request the UE to provide its coarse GNSS coordinates without receiving any prior user consent - then, if 'user consent' is available at the UE, the UE will report the information (implicitly giving the consent). If it's not present, the UE will respond that 'no coarse GNSS location available' (implicitly refusing the consent). RAN WG2 is requesting SA WG3 to check if they have any concern.","secretary_remarks":"Noted","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13450,"status":"noted","reservation_date":"2022-03-25 17:03:59","uploaded":"2022-03-28 10:15:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2, RAN WG3, CT WG1","lsoriginalls":"R2-2204257","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201953.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-2201980","title":"RAN indication that UE has moved out of PLMN serving area","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that AMF may deregister the UE due to UE moving out of PLMN service area.","secretary_remarks":"Approved, merging S2-2202805","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13510,"status":"agreed","reservation_date":"2022-03-26 00:32:59","uploaded":"2022-03-29 21:03:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3420.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220394","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201980.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-2201981","title":"Reply LS on RAN Initiated Release due to out-of-PLMN area condition","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a reply to the RAN WG3 LS on indicating that UE moved out of PLMN serviice area","secretary_remarks":"Response to S2-2201931. Merged into S2-2203242","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13460,"status":"merged","reservation_date":"2022-03-26 00:33:02","uploaded":"2022-03-29 21:03:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_NTN_solutions"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201981.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-2202235","title":"Correction of last visited TAI requirement","source":"Apple","contact":"Robert Zaus","contact-id":85311,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1+2) Terminology is corrected. 3) Sentence is reworded.","secretary_remarks":"Postponed","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13520,"status":"postponed","reservation_date":"2022-03-28 18:42:47","uploaded":"2022-03-29 11:58:50","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3597.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-2202235.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-2202236","title":"Correction of last visited TAI requirement","source":"Apple","contact":"Robert Zaus","contact-id":85311,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1+2) Terminology is corrected. 3) Sentence is reworded.","secretary_remarks":"r02 agreed. Revised to S2-2203243","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13530,"status":"revised","reservation_date":"2022-03-28 18:44:40","uploaded":"2022-03-29 11:58:50","revisionof":"","revisedto":"S2-2203243","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3436.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-2202236.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-2202281","title":"Criterion of Verification of UE location for UE registering via 5G Satellite Access","source":"Inspur","contact":"yong jiang","contact-id":95098,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Refer to TR 22.926 and define the PLMN's 'Country'. The geographical area of 'Country' is used to the verification of UE location. Other country of UE location is removed. The PLMN only verify whether or not the UE is located in the PLMN's 'Country'. Remove 'the country of the UE location' from the (de)registration rejection message.","secretary_remarks":"r01 agreed. Revised to S2-2203244","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13550,"status":"revised","reservation_date":"2022-03-29 03:18:31","uploaded":"2022-03-29 10:16:01","revisionof":"","revisedto":"S2-2203244","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3604.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-2202281.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-2202329","title":"Clarification on AMF obtaining the satellite-related information","source":"Inspur","contact":"Xiaohua Li","contact-id":94692,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Supplementary description for usage of RAT type in 5GC Adding description of AMF function to support NTN links","secretary_remarks":"r03 agreed. Revised to S2-2203245","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13570,"status":"revised","reservation_date":"2022-03-29 06:30:42","uploaded":"2022-03-29 06:35:24","revisionof":"","revisedto":"S2-2203245","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3607.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-2202329.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-2202380","title":"TAIs reporting corresponding to the Selected PLMN","source":"OPPO","contact":"Jingran Chen","contact-id":88895,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align with the description in 5.4.11.7 in 23.501 that NG-RAN provides TAI(s) corresponding to Selected PLMN when the NG-RAN broadcasts multiple TACs.","secretary_remarks":"Approved","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13590,"status":"agreed","reservation_date":"2022-03-29 07:54:12","uploaded":"2022-03-29 08:17:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3442.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220394","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202380.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-2202776","title":"LS from CT WG1: NR satellite RAT type in UE NAS","source":"CT WG1","contact":"Mikael Wass","contact-id":42217,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 is discussing extending NAS supervision timers at NR satellite access based on information on RAN delay provided in a Reply LS (C1-220079 \/ R2-2111612) and there have been discussions in CT WG1 to consider whether the NAS solution should take NR satellite RAT type into account for possible differentiation of the applied NAS timer extension. CT WG1 understands that NR satellite RAT type (LEO\/MEO\/GEO\/OTHERSAT) is provided to the AMF from the gNB via NGAP, but is not aware of any corresponding indication available to the NAS at the UE. CT WG1 would therefore like to know: - Is indication of the NR satellite RAT type available, or planned to be made available, to the NAS at the UE? - If such indication is available, or will be available, can it be trusted that the UE value corresponds to the value provided to the AMF? CT WG1 would like to make clear that there currently is no common agreement to differentiate extended NAS timers based on NR satellite RAT type even if NR satellite RAT type is available, or will be available, to the NAS at the UE.","secretary_remarks":"Noted","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13490,"status":"noted","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":"RAN WG2","Cc":"SA WG2, RAN WG3","lsoriginalls":"C1-222098","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202776.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-2202803","title":"[DRAFT] Reply LS on RAN Initiated Release due to out-of-PLMN area condition","source":"Samsung Electronics Romania","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a reply to the RAN 3 LS on RAN Initiated Release due to out-of-PLMN area condition.","secretary_remarks":"Response to S2-2201931. r01 agreed. Revised to S2-2203242, merging S2-2201981","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13470,"status":"revised","reservation_date":"2022-03-29 15:36:36","uploaded":"2022-03-29 16:10:13","revisionof":"","revisedto":"S2-2203242","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"CT WG1, RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202803.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-2202804","title":"RAN Initiated UE Context Release for UE using NR satellite access","source":"Samsung","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF may initiates deregistration of the UE using NR satellite access when it receives an N2 UE Context Release Request with cause value 'UE not in PLMN serving area' from NG-RAN.","secretary_remarks":"r02 agreed. Revised to S2-2203246","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13600,"status":"revised","reservation_date":"2022-03-29 15:40:58","uploaded":"2022-03-29 16:10:13","revisionof":"","revisedto":"S2-2203246","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3621.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-2202804.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-2202805","title":"RAN Initiated UE Context Release for UE using NR satellite access","source":"Samsung","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF initiates Network-initiated Deregistration for the UE using NR satellite access when it receives an N2 UE Context Release Request with cause value 'UE not in PLMN serving area' from NG-RAN. The AMF sends N2 UE Context Release Command after the Deregistration is completed.","secretary_remarks":"Merged into S2-2201980","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13620,"status":"merged","reservation_date":"2022-03-29 15:42:37","uploaded":"2022-03-29 16:10:13","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3454.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-2202805.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-2203242","title":"[DRAFT] Reply LS on RAN Initiated Release due to out-of-PLMN area condition","source":"Samsung Electronics Romania","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a reply to the RAN 3 LS on RAN Initiated Release due to out-of-PLMN area condition.","secretary_remarks":"Revision of S2-2202803r01, merging S2-2201981. Approved","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13480,"status":"approved","reservation_date":"2022-04-13 09:53:08","uploaded":"2022-04-13 15:41:13","revisionof":"S2-2202803","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2201931","lsto":"RAN WG3","Cc":"CT WG1, RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203242.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-2203243","title":"Correction of last visited TAI requirement","source":"Apple","contact":"Robert Zaus","contact-id":85311,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1+2) Terminology is corrected. 3) Sentence is reworded.","secretary_remarks":"Revision of S2-2202236r02. Approved","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13540,"status":"agreed","reservation_date":"2022-04-13 09:53:08","uploaded":"2022-04-14 10:51:16","revisionof":"S2-2202236","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3436.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220394","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203243.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-2203244","title":"Criterion of Verification of UE location for UE registering via 5G Satellite Access","source":"Inspur","contact":"yong jiang","contact-id":95098,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Avoid overloading an existing and well-defined term 'coutnry' in a different meaning. Indication of country of UE location is removed. The PLMN only verifies whether or not the UE is located in the PLMN's operating area. Remove 'the cou","secretary_remarks":"Revision of S2-2202281r01. Approved","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13560,"status":"agreed","reservation_date":"2022-04-13 09:53:09","uploaded":"2022-04-14 09:01:22","revisionof":"S2-2202281","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3604.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220394","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203244.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-2203245","title":"Clarification on AMF obtaining the satellite-related information","source":"Inspur","contact":"Xiaohua Li","contact-id":94692,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Supplementary description for usage of RAT type in 5GC Adding description of AMF function to support NTN linkssatellite backhaul network","secretary_remarks":"Revision of S2-2202329r03. Approved","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13580,"status":"agreed","reservation_date":"2022-04-13 09:53:11","uploaded":"2022-04-14 09:01:22","revisionof":"S2-2202329","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3607.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220394","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203245.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-2203246","title":"RAN Initiated UE Context Release for UE using NR satellite access","source":"Samsung","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF may initiates deregistration of the UE using NR satellite access when it receives an N2 UE Context Release Request with cause value 'UE not in PLMN serving area' from NG-RAN.","secretary_remarks":"Revision of S2-2202804r02. Approved","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":13610,"status":"agreed","reservation_date":"2022-04-13 09:53:12","uploaded":"2022-04-14 09:01:22","revisionof":"S2-2202804","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3621.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220394","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203246.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}]