[{"name":"S2-2105224","title":"LS from RAN WG2: LS Reply on SA WG2 assumptions on architecture aspects for using satellite access in 5G","source":"RAN WG2","contact":"Bharat Shrestha","contact-id":85593,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 for the LS on SA WG2 assumptions on architecture aspects for using satellite access in 5G. RAN WG2 discussed the question in the LS and would like to provide the following feedback. SA WG2 question: - SA WG2 has discussed whether cells, as core network sees them, are earth-moving or earth-fixed. Currently in terrestrial networks a Cell ID determined and provided by RAN is used to represent UE location in different services and systems (e.g. to route emergency calls to a suitable PSAP). For satellite coverage e.g. with moving beams, would the Cell ID received by CN still correspond to an earth-fixed area? - In case of earth-fixed cells (as seen from the CN), how the RAN node connected to 5GCN (e.g. CU or gNB) maps the radio component of the cell that can potentially have moving coverage (e.g. in case of NGSO satellite) to earth-fixed cells represented by CGI would be up to RAN WGs to decide. RAN WG2 feedback: - RAN WG2 has identified that radio cells for NTN can be permanently fixed, temporarily fixed or continuously moving. A moving radio cell covers different earth area over time and system information including Cell ID moves with the radio cell. RAN WG2 thinks any potential solution to mapping earth area to cell ID seen by the CN is out of scope of RAN WG2. Action: RAN WG2 respectfully requests SA WG2 to take the above information into account and provide feedback if any.","secretary_remarks":"Revision of postponed S2-2103716 from S2-145E. Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24250,"status":"noted","reservation_date":"2021-06-24 14:38:55","uploaded":"2021-06-25 10:42:11","revisionof":"S2-2103716","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, RAN WG3","lsoriginalls":"R2-2008229","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105224.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105246","title":"LS from SA WG1: Reply LS on selecting a PLMN not allowed in the country where a UE is physically located","source":"SA WG1","contact":"Toon Norp","contact-id":8605,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 would like to thank CT WG1 for the LS on selecting a PLMN not allowed in the country where a UE is physically located. SA WG1 would like to refer to related considerations in 22.926 Guidelines for extraterritorial 5G Systems (FS_5GET study). E.g. f","secretary_remarks":"Revision of postponed S2-2105096 from S2-145E. Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":23980,"status":"noted","reservation_date":"2021-06-24 14:38:56","uploaded":"2021-06-25 10:42:11","revisionof":"S2-2105096","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2, SA WG3LI","lsoriginalls":"S1-211503","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105246.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105251","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":"Response drafted in S2-2105800. Postponed","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24090,"status":"postponed","reservation_date":"2021-06-24 14:38:56","uploaded":"2021-06-25 10:42:11","revisionof":"","revisedto":"","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_146E_Electronic_2021-08\/Docs\/S2-2105251.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105264","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":"Postponed","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24210,"status":"postponed","reservation_date":"2021-06-24 14:38:57","uploaded":"2021-06-25 10:42:12","revisionof":"","revisedto":"","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_146E_Electronic_2021-08\/Docs\/S2-2105264.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105268","title":"LS from RAN WG2: Reply LS on PDB for new 5QI","source":"RAN WG2","contact":"Robert Karlsson","contact-id":75012,"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":"Postponed","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24220,"status":"postponed","reservation_date":"2021-06-24 14:38:57","uploaded":"2021-06-25 10:42:12","revisionof":"","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_146E_Electronic_2021-08\/Docs\/S2-2105268.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105270","title":"LS from RAN WG2: New LS on UE location aspects in NTN","source":"RAN WG2","contact":"Jianxiang Li","contact-id":84441,"tdoctype":"LS in","for":"Action","abstract":"As a follow-up information on top of what already indicated in the previous LS in R2-2102055 on UE location aspects in NTN, RAN WG2 would like to inform RAN WG3, SA WG2, SA WG3, SA WG3-LI and CT WG1 that RAN WG2 will be discussing a solution to ensure that the CGI constructed by NG-RAN corresponds to a fixed geographical area with a size comparable with a TN cell with a radius of ~2km or more for both connected mode and during initial access. In other words, RAN WG2 intends to develop a solution, to report the UE location to the gNB, with a guaranteed accuracy of an area of ~2km radius (and no better than that). This '~2km' is not to be understood as a recommended cell size for NTN, but rather as an achievable accuracy for initial UE location estimation for this particular use case. Action: RAN WG2 kindly asks the above groups to take the above information into account and provide any feedback if needed.","secretary_remarks":"Responses drafted in S2-2105619 and S2-2106071. Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":23950,"status":"noted","reservation_date":"2021-06-24 14:38:57","uploaded":"2021-06-25 10:42:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG2, SA WG3, SA WG3LI, CT WG1","Cc":"","lsoriginalls":"R2-2106543","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105270.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105276","title":"LS from RAN WG3: Reply LS to LS on IoT-NTN basic architecture","source":"RAN WG3","contact":"Luis Lopes","contact-id":84588,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to thank RAN WG2 and SA WG2 for the received LS on IoT-NTN basic architecture. RAN WG3 would like to clarify that the NG interface is always terminated in NG-RAN, i.e. in Fig.2 of the RAN WG2 LS, 'E-UTRAN' shall be replaced by 'NG-RAN'. As specified in TS 38.300, NG-RAN nodes can provide either NR or E-UTRA user plane and control plane terminations towards the UE. RAN WG3 assumes that RAN WG2 is considering NTN for the following: - Support of eMTC\/NB-IOT device connectivity to EPC - Support of eMTC\/NB-IOT device connectivity to 5GC Regarding 5GC connectivity, support for this configuration is not currently planned. The current NG-RAN work for NTN can be taken as a baseline, but since the NTN architecture aspects are only applicable to NR cells, for which IoT functionality is not defined, it is unclear at this time how much such aspects from current Rel-17 work can be re-used or new functionality needed. Regarding EPC connectivity, RAN WG3 has currently no planned work on this topic. RAN WG3 expects that it may be feasible to take the NG-RAN work as a model and transpose it to E-UTRAN, however, as mentioned above, it is currently unclear how much from current Rel-17 work can be reused. RAN WG3 would like also to comment that a decision to start work on IoT-NTN support, and the respective 3GPP Release, depends on TSG RAN's decision. Action: RAN WG3 kindly asks the above groups to take the above information into account.","secretary_remarks":"Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24260,"status":"noted","reservation_date":"2021-06-24 14:38:57","uploaded":"2021-06-25 10:42:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2","Cc":"TSG RAN, CT WG1","lsoriginalls":"R3-212806","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105276.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105282","title":"LS from RAN WG3: Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G","source":"RAN WG3","contact":"Alexander Vesely","contact-id":10078,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to thank RAN WG2 for the reply LS on assumptions on architecture aspects for satellite access in 5G. RAN WG3 would like to inform RAN WG2 and SA WG2 that RAN WG3 has agreed the BL CR to support approach b). Action: RAN WG3 asks RAN WG2 and SA WG2 group to take the above into account.","secretary_remarks":"Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24270,"status":"noted","reservation_date":"2021-06-24 14:38:57","uploaded":"2021-06-25 10:42:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2","Cc":"SA WG3LI, SA WG5","lsoriginalls":"R3-212916","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105282.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105283","title":"LS from RAN WG3: Reply LS on UE location aspects in NTN","source":"RAN WG3","contact":"Luis Lopes","contact-id":84588,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to thank RAN WG2 for the received LS on UE location aspects in NTN, and also SA WG2 and SA WG3-LI for their replies already received. Regarding the question posed in the LS: - Question: RAN WG2 would like to ask RAN WG3, SA WG3-LI and SA WG2 to confirm whether the current functionality identified above is sufficient for use in Non-Terrestrial Networks including initial registration procedure. Answer from RAN WG3: RAN WG3 understands from the RAN WG2 response that only the serving NTN Uu cell ID (broadcast cell ID of the serving cell) and the broadcast TAC(s) would be available at initial access. As a consequence, RAN WG3 assumes that at initial access the gNB is typically not able to provide in the ULI a CGI (Earth fixed) with location granularity similar to the ULI provided in TN; and also at initial access, the CGI provided in the ULI may represent a geographical area spanning multiple TACs. Based on the previous reply from SA WG2 on this topic, RAN WG3 also assumes that this is acceptable at system level. Regarding NNSF (and e.g. country selection), RAN WG3 understands that there may be cases where the NG-RAN is not able to guarantee the selection of the correct CN at initial access without more precise location information, and this would need to be corrected later by the NG-RAN or the CN. Minimizing the number of actions (e.g. by providing some level of additional location information at initial access) seems useful, if at all possible, and RAN WG3 would like to ask RAN WG2 to check such feasibility. After AS security is setup, RAN WG3 understands from the RAN WG2 LS that the NG-RAN will be able to obtain the UE's location information (e.g. GNSS information or otherwise), and thereby construct a CGI provided in the ULI satisfying accuracy requirements comparable to those for TN. 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. Question 2: RAN WG3 requests SA WG2 to confirm that it is acceptable that, in some cases, the CGI contained in the ULI at initial access may represent a geographical area larger than typical TN cell coverage areas, and which may possibly span the area of multiple TACs. In addition to the above, RAN WG3 would like to draw RAN WG2's attention to the scenario in which a RRC_CONNECTED UE moves across a country border but remains in the same NTN cell. To enable triggering of the N2-based Handover to change the AMF, RAN WG3 agreed that the gNB is expected to know from the UE, when the UE moves across the country border (to some reasonable level of precision), in case the serving NTN cell serves more than one country. This is linked to a requirement in TS 23.502. RAN WG3 assumes that this scenario may be covered by functionality needed for CGI mapping. 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 WG3 has also considered the related question of TAC reporting in the ULI, taking into account RAN WG2's agreement to support broadcast of multiple TACs per PLMN in a cell [see LS in R2-2104377]. RAN WG3 is not clear on which of the broadcast TACs the gNB will indicate to the CN in ULI, and RAN WG3 also noted that one or more of the broadcast TAIs might not be consistent with the UE's Registration Area. 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). Action: RAN WG3 kindly asks the above groups to take the above information into account, and provide any feedback if needed, and RAN WG2, SA WG2 and CT WG1 to provide feedback on the questions rais","secretary_remarks":"Responses drafted in S2-2105969 and S2-2106524. Final response in S2-2106651","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":23960,"status":"replied to","reservation_date":"2021-06-24 14:38:57","uploaded":"2021-06-25 10:42:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2, SA WG3-LI, SA WG3, CT WG1","Cc":"","lsoriginalls":"R3-212917","lsreply":"S2-2106651","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105283.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105295","title":"LS from SA WG3: Reply LS on UE location aspects in NTN","source":"SA WG3","contact":"Longhua Guo","contact-id":80179,"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":"Postponed","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":23970,"status":"postponed","reservation_date":"2021-06-25 10:32:22","uploaded":"2021-06-25 10:42:13","revisionof":"","revisedto":"","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_146E_Electronic_2021-08\/Docs\/S2-2105295.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105375","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":"Postponed","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24100,"status":"postponed","reservation_date":"2021-07-26 05:56:17","uploaded":"2021-08-24 13:27:16","revisionof":"","revisedto":"","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_146E_Electronic_2021-08\/Docs\/S2-2105375.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105376","title":"LS from CT WG1: Indication of country of UE location and its use in PLMN selection","source":"CT WG1","contact":"Chen-ho Chin","contact-id":57105,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 would be aware that SA WG3-LI has for FS_5GSAT_ARCH, indicated the requirement that 'Any solution shall support the ability to enforce the use of a Core Network of PLMN in the country where the UE is physically located ' - see attached S3i200056 To this requirement, SA WG2 has introduced a solution wherein should the Core Network having determined where the UE is located is a location in which the PLMN is not allowed to provide service to the UE, will reject the UE with an appropriate reject cause and optionally indicate 'the country of the UE location using the MCC(s) assigned to that country' (formulation used in one place of the CR) and 'the country of the UE location' (formulation used in other places of the CR) - see attached 23.502CR2482r1 (S2-2101667). CT WG1 is working on the stage 3 changes needed to realize the SA WG2 agreed solution and has for the last few CT WG1 eMeetings been unable to reach a consensus on how to interpret and implement the SA WG2 solution. To assist CT WG1 to make progress, CT WG1 seeks guidance from SA WG1 for the following:- 1) Should the indication of UE location represent a 'country' in the manner a 'country' is defined in TS 23.122, or should the 'country' be the TR 22.926 definition of 'a country is defined as the area embedded within a set of borders and for which a unique set of regulations applies for the provision of communication services through mobile networks'? Further CT WG1 would like to ask SA WG1's guidance on the usage\/applicability, if at all, of the indicated country of UE location, in the subsequent PLMN selection, i.e. shall it be considered by the UE: 2) that the UE is not allowed in the current geographical position to select any PLMN which does not correspond to the indicated country of UE location; or 3) the UE might select available and allowable PLMNs of that indicated country and other countries.","secretary_remarks":"Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24120,"status":"noted","reservation_date":"2021-07-26 05:56:17","uploaded":"2021-08-25 07:47:03","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG3-LI, SA WG2","lsoriginalls":"C1-214778","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105376.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105527","title":"PDB value for 5QI 10","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove editor's note. Extend PDB value to be 2xRTT (i.e. PDB = 1100ms)","secretary_remarks":"r02 agreed. Revised to S2-2106653","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24230,"status":"revised","reservation_date":"2021-08-06 18:04:49","uploaded":"2021-08-10 13:16:41","revisionof":"","revisedto":"S2-2106653","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3029.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105527.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105528","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":"Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24190,"status":"noted","reservation_date":"2021-08-06 18:04:50","uploaded":"2021-08-10 13:16:41","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3030.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105528.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105529","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 and refer to 23.501 where applicable","secretary_remarks":"Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24200,"status":"noted","reservation_date":"2021-08-06 18:04:51","uploaded":"2021-08-10 13:16:41","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2930.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105529.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105530","title":"TA handling for moving cells .","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Approval","abstract":"This contribution discusses TA handling for NTN with moving cells.","secretary_remarks":"Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24130,"status":"noted","reservation_date":"2021-08-06 18:04:52","uploaded":"2021-08-10 13:16:41","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_146E_Electronic_2021-08\/Docs\/S2-2105530.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105531","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.","secretary_remarks":"Merged into S2-2106652","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24140,"status":"merged","reservation_date":"2021-08-06 18:04:52","uploaded":"2021-08-10 13:16:41","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3031.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105531.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105619","title":"[DRAFT] Reply to New LS on UE location aspects in NTN","source":"THALES","contact":"jean-yves fine","contact-id":87072,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: SA WG3-LI, RAN WG3, SA WG3, CT WG1","secretary_remarks":"Response to S2-2105270. Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":23990,"status":"noted","reservation_date":"2021-08-09 09:32:58","uploaded":"2021-08-10 13:08:47","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG3-LI, RAN WG3, SA WG3, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105619.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105675","title":"Clarification on SMF determines satellite backhaul and PCF reports satellite backhaul category change event","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that SMF determines whether or not a satellite backhaul is used based on report of AMF and SMF shall subscribe to the AMF for reports on Satellite backhaul category change. Rewording of PCF notifys AF on 'Satellite backhaul category change'.","secretary_remarks":"r01 agreed. Revised to S2-2106654, merging S2-2106341","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24280,"status":"revised","reservation_date":"2021-08-09 12:58:47","uploaded":"2021-08-10 13:38:24","revisionof":"","revisedto":"S2-2106654","release":"Rel-17","crspec":23.503,"crspecversion":"17.1.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":618.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105675.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105800","title":"[DRAFT] Reply LS on multiple TACs per PLMN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This LS informs CT WG1, RAN WG2 and RAN WG3 about progress in SA WG2 regarding support for multiple TACs for moving cells.","secretary_remarks":"Response to S2-2105251. Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24110,"status":"noted","reservation_date":"2021-08-09 18:39:02","uploaded":"2021-08-10 13:16:41","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, RAN WG2, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105800.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105884","title":"PDU session establishment for NR satellite access","source":"ASUSTeK","contact":"Lider Pan","contact-id":56728,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In the sub-clause 4.3.2.2.1, the description of 'the UE shall not trigger a PDU Session establishment for a PDU session if the S-NSSAI corresponding to the PDU session is not applicable to the RAT Type for NR satellite access' is added.","secretary_remarks":"Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24330,"status":"noted","reservation_date":"2021-08-10 02:38:58","uploaded":"2021-08-10 02:50:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3005.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105884.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105969","title":"[DRAFT] Reply LS on UE location aspects in NTN","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS from RAN WG3 on UE location aspects in NTN","secretary_remarks":"Response to S2-2105283. Merged into S2-2106651","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24010,"status":"merged","reservation_date":"2021-08-10 07:09:59","uploaded":"2021-08-10 12:09:33","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2, SA WG3-LI, SA WG3, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105969.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105970","title":"Remove Editor's note in clause 5.4.11.1 in TS 23.501","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add high level description of NR satellite access functionality and remove the corresponding Editor's note in clause 5.4.11.1","secretary_remarks":"CC#4: r01 + changes agreed. Revised to S2-2106676.","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24340,"status":"revised","reservation_date":"2021-08-10 07:09:59","uploaded":"2021-08-10 12:09:33","revisionof":"","revisedto":"S2-2106676","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3119.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105970.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105971","title":"Discussion of Registration Update under NR Satellite Access.","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"discussion","for":"Approval","abstract":"Describe the issue that UE is unaware of TAC change and cannot initiates RA update. Discuss and evaluate alternative solutions to solve such issue.","secretary_remarks":"Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24360,"status":"noted","reservation_date":"2021-08-10 07:10:00","uploaded":"2021-08-10 12:09:33","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_146E_Electronic_2021-08\/Docs\/S2-2105971.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105972","title":"Registration Update under NR Satellite Access","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF determines the TA in which the UE is geographically located isn't part of UE's RA and triggers the UE to initiate Registration Update procedure to update RA to include such TA.","secretary_remarks":"Postponed","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24370,"status":"postponed","reservation_date":"2021-08-10 07:10:00","uploaded":"2021-08-10 12:09:33","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3022.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105972.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105976","title":"Discussion of Soft TAC issues to support NR Satellite Access.","source":"OPPO","contact":"Jingran Chen","contact-id":88895,"tdoctype":"discussion","for":"Approval","abstract":"Discusses how the soft TAC mode impacts the NAS and how the AMF supports the NR satellite access.","secretary_remarks":"Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24150,"status":"noted","reservation_date":"2021-08-10 07:14:46","uploaded":"2021-08-10 10:22:49","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_146E_Electronic_2021-08\/Docs\/S2-2105976.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105981","title":"Verification of UE location to support multiple TACs for 5G Satellite Access","source":"OPPO","contact":"Jingran Chen","contact-id":88895,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add to verification of UE location with multiple TACs case.","secretary_remarks":"Postponed","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24160,"status":"postponed","reservation_date":"2021-08-10 07:26:02","uploaded":"2021-08-10 10:22:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3122.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105981.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106070","title":"Discussion on Location aspects for NTN.","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"discussion","for":"Decision","abstract":"This contribution proposes to discuss how to handle the LS from RAN WG2","secretary_remarks":"Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24020,"status":"noted","reservation_date":"2021-08-10 09:06:35","uploaded":"2021-08-10 10:16:05","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_146E_Electronic_2021-08\/Docs\/S2-2106070.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106071","title":"[DRAFT] Reply LS on UE location aspects in NTN","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"LS out","for":"Approval","abstract":"This contribution proposes to reply the LS on UE location aspects in NTN","secretary_remarks":"Response to S2-2105270. Merged with S2-2105619 (noted). Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24000,"status":"noted","reservation_date":"2021-08-10 09:06:35","uploaded":"2021-08-10 10:16:05","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"SA WG3, SA WG3-LI, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106071.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106215","title":"Satellite RAT Type in LMF selection","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: NR(LEO), NR(MEO), NR(GEO) and NR(Othersate) RAT Type can be used in LMF selection.","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24380,"status":"withdrawn","reservation_date":"2021-08-10 11:43:19","uploaded":"2021-08-10 13:36:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.273,"crspecversion":"17.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":188.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106215.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106341","title":"SMF subscribes Satellite backhaul category backhaul change from AMF","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, SMF shall subscribe to AMF for reports on Satellite backhaul category change. 2, SMF also sends the new backhaul category to the PCF when the Satellite backhaul category change was met. 3, editorial change that SMF determines satellite backhaul is used or not based on notification from AMF rather than based on the Network Instance.","secretary_remarks":"Merged into S2-2106654","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24300,"status":"merged","reservation_date":"2021-08-10 14:20:31","uploaded":"2021-08-10 14:51:06","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.1.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":647.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106341.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106342","title":"SMF subscribes Satellite backhaul category backhaul change from AMF","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If AMF is aware that satellite backhaul category changes and SMF has subscribed satellite backhaul category change, AMF reports the current satellite backhaul category and indicates the satellite backhaul category change to SMF.","secretary_remarks":"r02 agreed. Revised to S2-2106655","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24310,"status":"revised","reservation_date":"2021-08-10 14:20:32","uploaded":"2021-08-10 14:51:06","revisionof":"","revisedto":"S2-2106655","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3199.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106342.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106517","title":"Clarification of Initiation of UE Location for country verification for NR satellite access","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For NR satellite access, changes are added to clarify that UE location would be initiated to verify the country for the UE location after an MM or SM procedure is complete. Changes are added to clarify that an AMF verifies whether the serving PLMN is allowed to operate in the country for the UE location.","secretary_remarks":"Noted. Covered by (noted) S2-2105528","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24170,"status":"noted","reservation_date":"2021-08-10 22:30:24","uploaded":"2021-08-10 23:13:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3233.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106517.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106518","title":"Clarification of Initiation of UE Location for country verification for NR satellite access","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For NR satellite access, changes are added for the registration procedure, service request procedure and the PDU Session Establishment procedure to clarify that UE location is initiated after the procedure is complete to verify the country for the UE location. Changes are added to clarify that an AMF verifies whether the serving PLMN is allowed to operate in the country for the UE location. It is also clarified that that the AMF returns an MCC to the UE to indicate the country of the UE when the UE is in the wrong country. This is already implied by NOTE 5 in clause 4.2.2.2.2 which becomes confusing if the AMF does not return an MCC.","secretary_remarks":"Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24180,"status":"noted","reservation_date":"2021-08-10 22:35:05","uploaded":"2021-08-10 23:13:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3120.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106518.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106519","title":"Discussion of Tracking Area Support with Hard and Soft TAC Update.","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"discussion","for":"Agreement","abstract":"Discusses how tracking areas, service areas and forbidden areas can be supported where satellite cells broadcast support for one TAC (hard TAC update) or several TACs (soft TAC update) per PLMN.","secretary_remarks":"Noted","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24050,"status":"noted","reservation_date":"2021-08-10 22:39:45","uploaded":"2021-08-10 23:13: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_146E_Electronic_2021-08\/Docs\/S2-2106519.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106521","title":"Support of Mobility Registration Update for 5G Satellite Access","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Changes are included to support a Mobility Registration Update with broadcast of multiple TACs per PLMN and to add a note on an associated paging implication.","secretary_remarks":"Revision of (Postponed) S2-2104777 from S2-145E. r01 agreed. Revised to S2-2106652, merging S2-2105531","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24060,"status":"revised","reservation_date":"2021-08-10 22:44:56","uploaded":"2021-08-10 23:13:39","revisionof":"S2-2104777","revisedto":"S2-2106652","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2748.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106521.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106522","title":"Support of Mobility Registration Update for 5G Satellite Access","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Changes are included to support a Mobility Registration Update with broadcast of multiple TACs per PLMN.","secretary_remarks":"Revision of (Postponed) S2-2104774 from S2-145E. Approved","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24080,"status":"agreed","reservation_date":"2021-08-10 22:48:26","uploaded":"2021-08-10 23:13:39","revisionof":"S2-2104774","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2875.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-210916","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106522.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106524","title":"[DRAFT] LS Response to Reply LS on UE location aspects in NTN","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, CT WG1. CC: RAN WG2","secretary_remarks":"Response to S2-2105283. r05 agreed. Revised to S2-2106651, merging S2-2105969","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24030,"status":"revised","reservation_date":"2021-08-10 22:56:05","uploaded":"2021-08-10 23:13:39","revisionof":"","revisedto":"S2-2106651","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, CT WG1","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106524.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106651","title":"LS Response to Reply LS on UE location aspects in NTN","source":"SA WG2","contact":"Stephen Edge","contact-id":84641,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, RAN WG2, CT WG1","secretary_remarks":"Revision of S2-2106524r05, merging S2-2105969. Approved","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24040,"status":"approved","reservation_date":"2021-09-01 09:14:52","uploaded":"2021-09-01 14:31:25","revisionof":"S2-2106524","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2105283","lsto":"RAN WG3, RAN WG2, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106651.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106652","title":"Support of Mobility Registration Update for 5G Satellite Access","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Changes are included to support a Mobility Registration Update with broadcast of multiple TACs per PLMN.","secretary_remarks":"Revision of S2-2106521r01, merging S2-2105531. Approved","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24070,"status":"agreed","reservation_date":"2021-09-01 09:14:52","uploaded":"2021-09-01 14:31:25","revisionof":"S2-2106521","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2748.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"SP-210916","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106652.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106653","title":"PDB value for 5QI 10","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove editor's note. Extend PDB value to be 2xRTT (i.e. PDB = 1100ms)","secretary_remarks":"Revision of S2-2105527r02. Approved","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24240,"status":"agreed","reservation_date":"2021-09-01 09:14:54","uploaded":"2021-09-01 14:31:25","revisionof":"S2-2105527","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3029.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-210916","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106653.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106654","title":"Clarification on SMF determines satellite backhaul and PCF reports satellite backhaul category change event","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that SMF determines whether or not a satellite backhaul is used based on report of AMF. Rewording of PCF notifys AF on 'Satellite backhaul category change'.","secretary_remarks":"Revision of S2-2105675r01, merging S2-2106341. Approved","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24290,"status":"agreed","reservation_date":"2021-09-01 09:14:56","uploaded":"2021-09-01 14:31:25","revisionof":"S2-2105675","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.1.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":618.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210916","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106654.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106655","title":"SMF subscribes Satellite backhaul category backhaul change from AMF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If AMF is aware that satellite backhaul category changes, AMF reports the current satellite backhaul category and indicates the satellite backhaul category change to SMF.","secretary_remarks":"Revision of S2-2106342r02. Approved","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24320,"status":"agreed","reservation_date":"2021-09-01 09:14:58","uploaded":"2021-09-01 14:31:25","revisionof":"S2-2106342","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3199.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210916","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106655.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106676","title":"Remove Editor's note in clause 5.4.11.1 in TS 23.501","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add high level description of NR satellite access functionality and remove the corresponding Editor's note in clause 5.4.11.1","secretary_remarks":"Revision of S2-2105970r01 + changes. Approved","agenda_item_sort_order":58,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":24350,"status":"agreed","reservation_date":"2021-09-01 09:15:20","uploaded":"2021-09-01 14:31:25","revisionof":"S2-2105970","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":3119.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210916","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106676.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]