[{"name":"S2-2106993","title":"LS from CT WG1: LS reply on multiple TACs per PLMN","source":"CT WG1","contact":"Sung Hwan Won","contact-id":70307,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 would like to thank RAN WG2 for their question in the LS R2-2104377\/C1-212840. Here is the answer from CT WG1: Option 2 is feasible and with Option 2 the following impact to the NAS layer (non-exhaustive) is expected: - A TAI from the multiple TAIs will need to be selected as the current TAI. However, it is not clear to CT WG1 how the NAS layer selects a TAI from the multiple TAIs. CT WG1 will consider further impacts and make clarification according to feedback from RAN WG2 and SA WG2. CT WG1 needs further analyses to consider how the network gets to know the selected TAI. In addition, CT WG1 would like to ask what should be considered for TAI selection. In the LS R2-2104377\/C1-212840, only the registration area is mentioned. Action: CT WG1 respectfully asks SA WG2 to provide, if any, feedback on the TAI selection in case of multiple TACs broadcast per PLMN.","secretary_remarks":"Revision of postponed S2-2105251 from S2#146E. Postponed","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17540,"status":"postponed","reservation_date":"2021-09-24 11:25:12","uploaded":"2021-09-24 16:05:51","revisionof":"S2-2105251","revisedto":"S2-2108252","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2","Cc":"RAN WG3","lsoriginalls":"C1-213965","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2106993.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106997","title":"LS from RAN WG2: Reply LS on PDB for new 5QI","source":"RAN WG2","contact":"Xiaodong Yang","contact-id":70365,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for sending their LS on PDB for new 5QI. According to TR 38.821, the max round trip delay (propagation delay only) for GEO satellite access with transparent payload is 541.46 ms. Thus, the AN PDB of 812 ms is about 1.5 RTT of the maximum round trip delay. RAN WG2 understands the procedure considered by SA WG2 is UE sends scheduling request to gNB, then gNB provides UL-Grant to UE, finally UE sends uplink data. Thus, for initial data transmission, no HARQ\/RLC retransmission is counted in 1.5 RTT. The PER of 10-6 while meeting a PDB of about 1.5 RTT will be challenging and will require more resources and thus lead to lower spectral efficiency. Action: RAN WG2 respectfully requests SA WG2 to take the above into account.","secretary_remarks":"Revision of postponed S2-2105268 from S2#146E. Noted","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17460,"status":"noted","reservation_date":"2021-09-24 11:25:12","uploaded":"2021-09-24 16:05:51","revisionof":"S2-2105268","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3, RAN WG1","lsoriginalls":"R2-2106533","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2106997.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107002","title":"LS from SA WG3: Reply LS on UE location aspects in NTN","source":"SA WG3","contact":"Anja Jerichow","contact-id":68341,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks RAN WG2 and SA WG3-LI for the LS on UE location aspects in NTN (R2-2102055\/ S3i210282). - Question 2: RAN WG2 would like to ask SA WG3 and SA WG3-LI to confirm whether A-GNSS based UE location information, i.e. computed at network using A-GNSS based measurements provided by UE, or computed by UE, can be considered reliable e.g. for lawful interception. In general, SA WG3 shares the same view with SA WG3-LI. For giving more concrete answers with better understanding, SA WG3 would like to ask the following questions for clarification: - What is the purpose of sending A-GNSS based measurements after AS security has been established? Is it for core network reselection after initial core network selection? - Are the A-GNSS based measurements used by the applied UE positioning method during LCS procedure or used in a different procedure? SA WG3 would appreciate if RAN WG2 could provide feedback to the above questions or any additional information if necessary for further discussion. Action: RAN WG2 is kindly requested to answer the above questions. SA WG2, SA WG3-LI, RAN WG3 are kindly requested to take the above information into account.","secretary_remarks":"Revision of postponed S2-2105295 from S2#146E. Postponed","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17510,"status":"postponed","reservation_date":"2021-09-24 11:25:13","uploaded":"2021-09-24 16:05:51","revisionof":"S2-2105295","revisedto":"S2-2108255","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2, SA WG3LI, RAN WG3","Cc":"CT WG1","lsoriginalls":"S3-212306","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107002.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107015","title":"LS from RAN WG2: Response LS on Multiple TACs per PLMN","source":"RAN WG2","contact":"Jedrzej Stanczak","contact-id":68469,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank CT WG1 and SA WG2 for their response LSs, submitted in C1-213965 and S2-2104891, respectively. RAN WG2 has taken into account the feedback provided and confirms Option 2 (AS indicates all received TAC(s) for one PLMN to NAS layer) has been adopted by RAN WG2. As a consequence of this decision and to provide feedback requested by CT WG1, RAN WG2 has further discussed what factors can be helpful at NAS layer in TAI selection. RAN WG2 indicates that TACs in NTN are fixed to geographical location on Earth. Furthermore, RAN WG2 thinks that UE's location information could be used for TAI selection. RAN WG2 respects the final decision on which criteria to apply (e.g. UE location information or other) is up to CT WG1 and SA WG2 judgement. CT WG1 and SA WG2 may consider also other factors, specific to NAS layer. Action: RAN WG2 respectfully asks CT WG1 and SA WG2 to work on the solution for selecting a single TAC from the list of multiple TACs per PLMN indicated by the AS layer, possibly considering the feedback provided by RAN WG2.","secretary_remarks":"Revision of postponed S2-2105375 from S2#146E. Postponed","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17530,"status":"postponed","reservation_date":"2021-09-24 11:25:14","uploaded":"2021-09-24 16:05:51","revisionof":"S2-2105375","revisedto":"S2-2108260","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG2, RAN WG3","Cc":"","lsoriginalls":"R2-2108888","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107015.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107025","title":"LS from CT WG1: LS on extended NAS supervision timers at satellite access","source":"CT WG1","contact":"Mikael Wass","contact-id":42217,"tdoctype":"LS in","for":"Information","abstract":"In the SA WG2 study on 5GSat it was concluded for KI#3 (Delay in satellite) that NAS supervision timers need to be extended to handle the additional delay added at satellite access compared to existing NG-RAN. It was also captured in the study that final determination of extended timer values is left for stage 3. In the analysis of NAS timer extension at satellite access, CT WG1 would need additional information from RAN WG2 to determine possible updates to normative stage 3 specification. As the NAS supervision timers control triggering of NAS message re-transmission and determination of NAS procedure failure, updated timing for NAS message transport in AS compared to current NG-RAN needs to be considered. Therefore, CT WG1 would appreciate answers to the following questions: - For all satellite access types (LEO, MEO, GEO) where AS timing is updated, what is the worst-case delay in AS for transport of NAS messages via satellite access, including potential delays due to GNSS fix acquisition: 1) For initial NAS messages in the UL direction; 2) For non-initial NAS messages in the UL direction; and 3) For NAS messages in the DL direction.","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":17470,"status":"noted","reservation_date":"2021-09-24 11:25:15","uploaded":"2021-09-24 16:23:50","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2, RAN WG3","lsoriginalls":"C1-215074","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107025.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107048","title":"LS from RAN WG2: Reply LS on UE location aspects in NTN","source":"RAN WG2","contact":"Bharat Shrestha","contact-id":85593,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 would like to thank RAN WG3 for the LS reply and provide answers to the following questions. Question 1: RAN WG3 would like RAN WG2 to confirm whether the gNB will be able to acquire UE location information with an accuracy comparable to TN cell granularity (e.g. GNSS information or otherwise) after AS security, and also to confirm whether it is possible to provide any level of UE location information (i.e. finer than NTN Uu cell accuracy) before AS security. RAN WG2 answer: RAN WG2 has made following agreements: - UE coarse location information refers to coarse GNSS coordinates (FFS on the details, e.g. X MSB bits out of 24 bits of longitude\/latitude or GNSS coordinates with ~2km accuracy). - if SA WG3 has no concern reporting coarse location during initial access, the coarse location information is reported in Msg5, i.e., via RRCSetupComplete\/RRCResumeComplete message. - After AS security is established, gNB can obtain a GNSS-based location information from the UE using existing signalling method, i.e., by configuring includeCommonLocationInfo in the corresponding reportConfig. It is up to SA WG3 to decide whether User Consent is required before NW acquires location information from the UE in NTN. Question 3: RAN WG3 welcomes any feedback from RAN WG2 on the described case (i.e. the gNB to trigger inter-AMF handover when crossing country borders). RAN WG2 answer: RAN WG2 understands it is up to other working groups to decide on triggering of the N2-based Handover to change the AMF based on available information such as UE location information, if available and reported by UE Question 4: RAN WG3 requests RAN WG2, CT WG1 and SA WG2 to provide any feedback on above issue (i.e. which TAC should be reported by the gNB in case of multiple broadcast TAC). RAN WG2 answer: RAN WG2 may be able to provide feedback on this later.","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":17480,"status":"noted","reservation_date":"2021-09-24 11:25:15","uploaded":"2021-09-27 06:28:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2, CT WG1, SA WG3","lsoriginalls":"R2-2109216","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107048.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107049","title":"LS from RAN WG2: Reply LS on UE location aspects in NTN","source":"RAN WG2","contact":"Xun Tang","contact-id":78305,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks SA WG3 for the following questions: - What is the purpose of sending A-GNSS based measurements after AS security has been established? Is it for core network reselection after initial core network selection? RAN WG2 believes that this is for potential core network reselection after initial core network selection. After AS security has been established, LCS procedure via LMF can be initiated to verify UE's location and check whether UE has selected a PLMN that is allowed to operate in the country of the UE location. - Are the A-GNSS based measurements used by the applied UE positioning method during LCS procedure or used in a different procedure? RAN WG2 believes that A-GNSS based measurements are parts of A-GNSS positioning method, and it is during LCS procedure. Additionally, RAN WG2 has also discussed and agreed to use UE location reporting to gNB for the purpose of UE-specific TA pre-compensation (if no concern is raised by SA WG3), but in RAN WG2 understanding it is not relevant to A-GNSS positioning method.","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":17490,"status":"noted","reservation_date":"2021-09-24 11:25:15","uploaded":"2021-09-27 06:28:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"CT WG1, SA WG2, SA WG3LI, RAN WG3","lsoriginalls":"R2-2109217","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107049.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107076","title":"LS from RAN WG1: Reply LS on PDB for new 5QI","source":"RAN WG1","contact":"Xingqin Lin","contact-id":67645,"tdoctype":"LS in","for":"Action","abstract":"RAN WG1 would like to thank SA WG2 for sending their LS on PDB for the new 5QI. RAN WG1 notices that the new 5QI has a AN PDB of 812 ms and a PER of 10-6 for QoS flow of type Non-GBR. A AN PDB of 812 ms is about 1.5 RTT of the maximum round trip delay in GEO satellite access with transparent payload. RAN WG1 understands that services using Non-GBR QoS Flows should be prepared to experience congestion-related packet drops and delays. In uncongested scenarios, 98 percent of the packets should not experience a delay exceeding the 5QI's PDB. The PDB for Non-GBR denotes a 'soft upper bound' in the sense that an 'expired' packet, e.g. a link layer SDU that has exceeded the PDB, does not need to be discarded and is not added to the PER. However, there are different views in RAN WG1 whether the new 5QI is reasonable. Some companies hold the view that it is possible to satisfy the new 5QI with proper network configuration and implementation. Some companies hold the view that satisfying the new 5QI will cause severe drop in network spectral efficiency due to conservative link adaptation and significantly longer delay for retransmissions to reach PER of 10-6, and thus the new 5QI can only be satisfied in ideal conditions and recommend that SA WG2 consider higher PDB and\/or higher PER for this new 5QI. In general, RAN WG1 holds the view that, if RTT is X and PER is Y, where Y is as small as 10-6, Y can be met with a delay that is multiple times of the RTT. Action: RAN WG1 respectfully requests SA WG2 to take the above into account.","secretary_remarks":"Revision of postponed S2-2105264 from S2#146E. Postponed","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17520,"status":"postponed","reservation_date":"2021-09-24 11:25:17","uploaded":"2021-09-28 15:08:57","revisionof":"S2-2105264","revisedto":"S2-2108274","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3, RAN WG2","lsoriginalls":"R1-2106331","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107076.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107230","title":"UE location verification handling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enhance description in 23.501 to allow it to be used as common reference for UE location verification","secretary_remarks":"Revision of (Noted) S2-2105528 from S2#146E. r04 agreed. Revised to S2-2107835","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17640,"status":"revised","reservation_date":"2021-10-08 15:35:31","uploaded":"2021-10-11 17:22:49","revisionof":"S2-2105528","revisedto":"S2-2107835","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3030.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107230.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107231","title":"UE location verification handling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align description for how AMF can verify UE location for satellite access by moving the several times repeated UE location verification procedure description to TS 23.501 clause 5.4.11.1 and refer to 23.501 where applicable","secretary_remarks":"Revision of (Noted) S2-2105529 from S2#146E. Approved","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17660,"status":"agreed","reservation_date":"2021-10-08 15:35:36","uploaded":"2021-10-11 17:22:49","revisionof":"S2-2105529","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2930.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211284","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107231.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107232","title":"TA handling with satellite access.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discusses TA handling for satellite access.","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":17550,"status":"noted","reservation_date":"2021-10-08 15:35:37","uploaded":"2021-10-11 17:22:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107232.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107233","title":"TA handling in satellite access","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify UE, NG-RAN and 5GC handling of Tracking Areas in NTN with moving cells, and how mobility restrictions can be applied. Two mutually exclusive alternatives are described in the CR: - Yellow part, for the case where Soft TAC is supported in rel-17 (i.e. multiple TACs may be broadcast per PLMN in a cell). - Cyan part, for the case where only single TAC per PLMN and cell is supported in rel-17 (i.e. Hard TAC switching)","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":17560,"status":"postponed","reservation_date":"2021-10-08 15:35:37","uploaded":"2021-10-11 17:22:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3262.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107233.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107333","title":"Editorial correction in TS 23.501","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align description for verification of UE location for satellite access and refer to 23.501 where applicable. Add satellite backhaul category description in its debut clause.","secretary_remarks":"r01 agreed. Revised to S2-2107836","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17680,"status":"revised","reservation_date":"2021-10-11 06:29:26","uploaded":"2021-10-11 14:09:56","revisionof":"","revisedto":"S2-2107836","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3284.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107333.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107334","title":"Editorial correction in TS 23.502","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align the description of UE location verification in 23.501 and 23.502","secretary_remarks":"r01 agreed. Revised to S2-2107837","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17700,"status":"revised","reservation_date":"2021-10-11 06:29:28","uploaded":"2021-10-11 14:09:56","revisionof":"","revisedto":"S2-2107837","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3161.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107334.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107335","title":"Editorial correction in TS 23.503","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Either satellite backhaul or non-satellite backhaul is reported when the satellite backhaul category change event was met.","secretary_remarks":"r01 agreed. Revised to S2-2107838","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17720,"status":"revised","reservation_date":"2021-10-11 06:29:29","uploaded":"2021-10-11 14:09:56","revisionof":"","revisedto":"S2-2107838","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":659.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107335.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107345","title":"Clarification on Tracking Area configuration in case of satellite access","source":"Rakuten Mobile, Inc","contact":"Kenichiro Aoyagi","contact-id":90937,"tdoctype":"CR","for":"Approval","abstract":"Clarify that a Tracking Area does not contain different RAT Types. And also in case the RAT type is not supported, Clarify the Tracking Area does not contain both satellite access and non satellite access","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17620,"status":"withdrawn","reservation_date":"2021-10-11 07:22:22","uploaded":"2021-10-11 08:14:56","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3288.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107345.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107361","title":"Clarification on RTD and Terminology Alignment","source":"Tencent, Tencent Cloud","contact":"Yixue Lei","contact-id":78221,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change RTD into two way propagation delay. Add LEO, MEO and GEO into abbreviations part.","secretary_remarks":"r01 agreed. Revised to S2-2107839","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17740,"status":"revised","reservation_date":"2021-10-11 07:58:18","uploaded":"2021-10-11 15:11:45","revisionof":"","revisedto":"S2-2107839","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3290.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107361.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107366","title":"Clarification on Verification of UE Location","source":"Tencent, Tencent Cloud","contact":"Yixue Lei","contact-id":78221,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the UE location request procedure and add clarification that external entity can also verify UE location with LR procedure.","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":17670,"status":"noted","reservation_date":"2021-10-11 08:14:16","uploaded":"2021-10-11 15:11:45","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3291.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107366.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107446","title":"Support of selecting a single TAI","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifying that UE selects a single TAC from the broadcasted TAC list and doesn't perform registration update even the TAC is not within the registration area.","secretary_remarks":"Postponed. Revised at S2#148E to S2-2108530 (noted)","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17630,"status":"revised","reservation_date":"2021-10-11 09:47:51","uploaded":"2021-10-11 10:01:58","revisionof":"","revisedto":"S2-2108530","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3301.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107446.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107503","title":"Discussion on Mobility Registration Update when broadcasting more than one TACs.","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"discussion","for":"Agreement","abstract":"Discuss whether there is an anomaly handling on Mobility Registration Update when broadcasting more than one TACs","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":17570,"status":"noted","reservation_date":"2021-10-11 10:54:46","uploaded":"2021-10-11 14:09:56","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107503.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107568","title":"Limited service PLMN selection for emergency","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If a UE in limited service state is aware of its location, then it should attempt to select a PLMN that can operate in the same country as the present UE location. This cannot be a 'shall' level mandate, as the same LS from SA WG1 admits that there are cases when some other PLMN might need to be selected. While selection of emergency PLMN in the country of the present UE location is highly desirable, if that is not possible, the UE is allowed to select some other PLMN as secondary option.","secretary_remarks":"Approved. Revised at S2#148E to S2-2108513","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17760,"status":"revised","reservation_date":"2021-10-11 11:50:01","uploaded":"2021-10-11 12:30:11","revisionof":"","revisedto":"S2-2108513","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3318.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107568.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107618","title":"Discussion on Supporting Multiple TACs for Satellite Access.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion paper aims at solving the issue on multiple TACs for satellite access and proposes gNB sends ULI to AMF after AS security is established.","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":17590,"status":"noted","reservation_date":"2021-10-11 12:50:33","uploaded":"2021-10-11 14:02:14","revisionof":"","revisedto":"S2-2108746","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107618.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107619","title":"Support multiple TACs for Satellite access","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If AMF receives multipel TACs during initial Registration procedure or UE triggered Service Request procedure when UE is in IDLE, the AMF proceeds the NAS procedure when one of the multiple TACs is not in Forbidden Area or non-allowed area. Add a NOTE on UE behaviour that if UE receives multiple TACs and is rejected by AMF due to UE is in Forbidden Area or non-allowed area, UE re-attempt to initiate signallign with AMF based on UE implementation, e.g. after a period, after moving over a distance. When NG-RAN is aware of accurate UE location (e.g. rather than multiple TACs for NR satellite access), the NG-RAN sends the accurate UE location to AMF.","secretary_remarks":"Postponed. Revised at S2#148E to S2-2108747","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17600,"status":"revised","reservation_date":"2021-10-11 12:50:33","uploaded":"2021-10-11 14:02:14","revisionof":"","revisedto":"S2-2108747","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3323.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107619.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107620","title":"Support multiple TACs for Satellite access","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. During the initial Registration procedure or Service Request procedure when UE is in IDLE, the location information sent by NG-RAN to AMF may include multiple TACs. 2. When NG-RAN is aware of accurate UE location (e.g. rather than multiple TACs for NR satellite access), the NG-RAN sends the accurate UE location to AMF.","secretary_remarks":"Postponed. Revised at S2#148E to S2-2108748 (noted)","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17610,"status":"revised","reservation_date":"2021-10-11 12:50:36","uploaded":"2021-10-11 14:02:14","revisionof":"","revisedto":"S2-2108748","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3197.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107620.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107750","title":"[DRAFT] Reply LS on UE location aspects in NTN","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"Provides additional feedback to SA WG3, on top of RAN WG2's feedback","secretary_remarks":"Response to S2-2107049. Postponed","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17500,"status":"postponed","reservation_date":"2021-10-11 18:27:11","uploaded":"2021-10-11 19:50:57","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG2","Cc":"CT WG1, SA WG3-LI, RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107750.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107779","title":"Resolution of Tracking Area Indication in the NGAP ULI for Moving Cells","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"discussion","for":"Agreement","abstract":"Looks at previous and new alternatives for selecting a TAC for the NGAP ULI where cells are moving and identifies solutions with improved performance.","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":17580,"status":"noted","reservation_date":"2021-10-11 22:20:07","uploaded":"2021-10-11 23:10:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107779.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107835","title":"UE location verification handling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enhance description in 23.501 to allow it to be used as common reference for UE location verification","secretary_remarks":"Revision of S2-2107230r04. Approved. Revised at S2#148E to S2-2108329","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17650,"status":"revised","reservation_date":"2021-10-25 06:06:34","uploaded":"2021-10-26 12:41:14","revisionof":"S2-2107230","revisedto":"S2-2108329","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3030.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107835.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107836","title":"Editorial correction in TS 23.501","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add satellite backhaul category description in its debut clause.","secretary_remarks":"Revision of S2-2107333r01. Approved. Revised at S2#148E to S2-2108325","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17690,"status":"revised","reservation_date":"2021-10-25 06:06:36","uploaded":"2021-10-25 12:51:14","revisionof":"S2-2107333","revisedto":"S2-2108325","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3284.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107836.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107837","title":"Editorial correction in TS 23.502","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align the description of 'country of UE location' sending to the UE as optional information Adding Satellite backhaul category in the PDU session update request sending from V-SMF to H-SMF","secretary_remarks":"Revision of S2-2107334r01. Approved. Revised at S2#148E to S2-2108326","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17710,"status":"revised","reservation_date":"2021-10-25 06:06:38","uploaded":"2021-10-25 12:51:14","revisionof":"S2-2107334","revisedto":"S2-2108326","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3161.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107837.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107838","title":"Editorial correction in TS 23.503","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Either satellite backhaul or non-satellite backhaul is reported when the satellite backhaul category change event was met.","secretary_remarks":"Revision of S2-2107335r01. Approved. Revised at S2#148E to S2-2108327","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17730,"status":"revised","reservation_date":"2021-10-25 06:06:40","uploaded":"2021-10-25 12:51:14","revisionof":"S2-2107335","revisedto":"S2-2108327","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":659.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107838.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2107839","title":"Clarification on RTD and Terminology Alignment","source":"Tencent, Tencent Cloud","contact":"Yixue Lei","contact-id":78221,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change RTD into two way propagation delay. Add LEO, MEO and GEO into abbreviations part.","secretary_remarks":"Revision of S2-2107361r01. Approved","agenda_item_sort_order":19,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":17750,"status":"agreed","reservation_date":"2021-10-25 06:06:41","uploaded":"2021-10-25 12:51:14","revisionof":"S2-2107361","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3290.0,"crrevision":1.0,"crcategory":"D","tsg_crp":"SP-211284","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_147E_Electronic_2021-10\/Docs\/S2-2107839.zip","group":"S2","meeting":"S2-147-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]