[{"name":"S2-2100003","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-2008338 from S2#142E. Postponed","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22530,"status":"postponed","reservation_date":"2021-01-13 10:03:17","uploaded":"2021-01-13 14:55:02","revisionof":"S2-2008338","revisedto":"","release":"Rel-17","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_143e_Electronic\/Docs\/S2-2100003.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100013","title":"LS from RAN WG3: Reply LS on LS on signalling of satellite backhaul connection","source":"RAN WG3","contact":"Philippe Reininger","contact-id":35013,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG2 for their LS in R3-206843\/S2-2008308. The LS from SA WG2 addresses the cases where satellite connectivity is used as backhaul between terrestrial RAN nodes and terrestrial CN nodes. RAN WG3 did not discuss the satellite backhaul during the NTN Study Item and this topic is out of scope of the on-going Rel-17 RAN Work Item. RAN WG3 is not able to provide specific characteristics of the network packet delay budget as requested by SA WG2 in point 3 and 4. Then RAN WG3 is only able to provide the following general NG interface backhaul principles: - According to TS 38.411, the support of any suitable layer 1 technique - like point-to-point or point-to-multipoint techniques - shall not be prevented; - According to principles outlined in TS 38.401, NG-RAN interfaces are specified under the assumption that transport functions (TNL) are separate from NG-RAN and 5GC functions (RNL). RAN WG3 believes that the principles outlined above should provide sufficient response to the questions in the LS. Action: RAN WG3 kindly asks SA WG2 to take the information above into account.","secretary_remarks":"Revision of postponed S2-2009096 from S2#142E. Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22540,"status":"noted","reservation_date":"2021-01-13 10:03:18","uploaded":"2021-01-13 14:55:02","revisionof":"S2-2009096","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, RAN WG1","lsoriginalls":"R3-207060","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100013.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100042","title":"LS from SA WG1: LS on Satellite RATs for PLMN selection","source":"SA WG1","contact":"Francesco Pica","contact-id":57089,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks CT WG1 for their LS on satellite RATs for PLMN selection, and the questions to SA WG1: ------------ Question 1: Is there a service requirement to differentiate between 'NG-RAN' and 'satellite access to 5GC' for the purpose of PLMN selection? Question 2: 2a. Does SA WG1 intend to introduce new associated Access Technology identifier(s) for 'satellite access' for the Operator Controlled PLMN Selector list and a User Controlled PLMN Selector list (stored on the SIM\/USIM card). 2b. If yes, how many different identifiers? ------------ Regarding CT WG1 questions 1 and 2a, SA WG1 agreed the attached 22.011 CR, adding 'satellite NG-RAN' to the set of possible associated access technology identifiers. Regarding CT WG1 question 2b, the agreed CR assumes that one identifier is sufficient. SA WG1 may further discuss about finer differentiation in future meetings.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22550,"status":"noted","reservation_date":"2021-01-13 10:03:19","uploaded":"2021-01-13 14:55:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2, TSG RAN","lsoriginalls":"S1-204379","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100042.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100060","title":"LS on selecting a PLMN not allowed in the country where a UE is physically located","source":"CT WG1","contact":"Sung Hwan Won","contact-id":70307,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 is currently studying ways to make a UE select a PLMN in the context of satellite access. The details on how the UE determines what PLMN is allowed in the country where the UE is physically located, are studied in CT WG1. With respect to cases where a UE using satellite access cannot find a PLMN allowed in the country where the UE is physically located, CT WG1 would like to consult SA WG3-LI and SA WG1 to find a resolution to the following questions. Question 1: Can a UE using satellite access select a PLMN not allowed in the country where the UE is physically located? Question 2: If the answer to Question 1 is yes, what are the services that a UE can obtain by a PLMN not allowed in the country where the UE is physically located?","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22560,"status":"noted","reservation_date":"2021-01-13 10:03:19","uploaded":"2021-02-05 14:18:08","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG3-LI","Cc":"SA WG2","lsoriginalls":"C1-210437","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100060.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100061","title":"LS from CT WG1: Reply to LS on NR satellite access PLMN selection","source":"CT WG1","contact":"Chen-ho Chin","contact-id":57105,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 would like to thank SA WG2 for their LS (C1-210047\/S2-2009485) on PLMN selection in NR satellite access. In that LS SA WG2 asked the following questions to which CT WG1 would like to provide the indicated responses below. Question 1 from SA WG2: Is it possible to limit the UE's PLMN selection to consider PLMN candidates belonging to one country? Answer from CT WG1: Yes, by what is currently defined in TS 23.122 this is (technically) possible. However, CT WG1 would kindly request more information about the SA WG2's intention with this limitation in the context of PLMN selection for satellite access. Question 2 from SA WG2: Is there suitable cause value to indicate to UE in DE-REGISTRATION REQUEST and REGISTRATION REJECT messages that the UE needs to select a PLMN in different country? Answer from CT WG1: Currently, in TS 24.501, there is no suitable reject cause value that will definitively make the UE select a PLMN in a different country. CT WG1 can consider introducing a new reject cause value or amend an existing reject cause value for this purpose, but will make that decision when there is a clear SA WG2 requirement. However, CT WG1 would kindly request clarification on whether 1. the reject cause indicates that the UE is attempting to access a PLMN that is not allowed to operate at the present UE location or 2. is it meant to indicate to the UE that the UE is not allowed to select any PLMN from the same MCC(group)\/country (i.e. the Home Country of the selected PLMN) as the selected PLMN in the current geographical UE location? Depending on which interpretation is correct, there will be different consequential impacts for the PLMN selection procedures. Furthermore, CT WG1 would like to point out that if the intention of the reject cause is to create new requirements on PLMN selection, then CT WG1 would need to re-assess that requirement as CT WG1 is responsible for PLMN selection procedures. Question 3 from SA WG2: Can the AMF indicate the target MCC List (e.g. based on UE location) in DE-REGISTRATION REQUEST and REGISTRATION REJECT message, to be used as input to PLMN selection? Answer from CT WG1: Currently in TS 24.501 there is no such list of MCC in DEREGISTRATION REQUEST or REGISTRATION REJECT, but CT WG1 can introduce such a list if there is a clear SA WG2 requirement. However, before then, CT WG1 seeks clarification on what this list of MCC is supposed to signify and what are the expectations of its use. Again if the expectation is that such a list of MCC is to be used for PLMN selection, CT WG1 will need the justified requirements. CT WG1 kindly request SA WG2 to consider our answers to SA WG2's questions and would like to ask SA WG2 to answer the following questions:- i) What is the intention and scope of the reject cause? ii) Can SA WG2 clarify on the nature, intention and scope of this MCC list?. Action: Please take note of CT WG1's answers above and provide an answer to CT WG1's questions.","secretary_remarks":"Response drafted in S2-2100647. Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22570,"status":"noted","reservation_date":"2021-01-13 10:03:19","uploaded":"2021-02-05 14:18:08","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-210438","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100061.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100062","title":"LS on extraterritorial use of MCC for satellite access","source":"CT WG1","contact":"Amer Catovic","contact-id":39766,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 is working on the Study Item on PLMN selection for satellite access and seeks clarification of a certain NTN (Non-Terrestrial Network) deployment scenario. In this scenario, (see Figure 1), extra-territorial NTN PLMN X operates satellite access out of Country A but as a extra-territorial NTN covers also Country B and Country C. Question 1 to SA WG1: Is the PLMN X allowed to use the MCC corresponding to Country A as the MCC of its PLMN ID in the system info broadcast to offer service to UEs located in Country B or Country C, or must the PLMN X use an MCC in the range of 9xx? Question 2 to SA WG1: Could SA WG1 outline if there are any use cases where in such a scenario it is allowed that the PLMN X is using a country specific MCC rather then an MCC in the range of 9xx?'. Question 3 to SA WG1: Is this ITU-T E212 Annex E applicable for NTN network deployments? If yes is it recommended as general solution for extra-territorial NTN, or just under certain conditions?","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22600,"status":"noted","reservation_date":"2021-01-13 10:03:19","uploaded":"2021-02-05 14:18:08","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG3, RAN WG2, SA WG2","lsoriginalls":"C1-210439","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100062.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100098","title":"Network sharing for NR satellite access with virtualized earth station","source":"CAICT","contact":"Haijiao Liu","contact-id":89393,"tdoctype":"draftCR","for":"Approval","abstract":"When satellite with transparent playload provides coverage in multiple countries, the vitualized function is added to satellite earth station, which acts as an NG-RAN. In this situation, network could be shared in an efficient and safe way.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22610,"status":"noted","reservation_date":"2021-02-07 05:42:21","uploaded":"2021-02-19 02:55:03","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.7.0","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_143e_Electronic\/Docs\/S2-2100098.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100137","title":"LS from RAN WG1: Reply LS on AN-PDB and PER targets for satellite access","source":"RAN WG1","contact":"Xiaofeng Wang","contact-id":60286,"tdoctype":"LS in","for":"Action","abstract":"RAN WG1 would like to thank SA WG2 for the LS (R1-2100014\/S2-2009225) on AN-PDB and PER targets for satellite access. RAN WG1 understands that SA WG2 is considering if new AN-PDB and PER values for GBR 5QIs are needed for services over satellite access, e.g., GEO\/LEO\/HAPS, with transparent payload. Regarding the two questions in the LS, RAN WG1 would like to provide the following information: - The round-trip delay (RTD) between the UE and the NTN gateway can be up to 541.46 ms for GEO satellites and 25.77 ms for LEO satellites at 600 km height. The RTD for HAPS is similar to that in TN. Retransmissions may lead to a delay of multiple RTDs. - RAN WG1 is not expected to consider higher PER upper bound for NTN. Action: RAN WG1 respectfully asks SA WG2 to take the above information into account.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22620,"status":"noted","reservation_date":"2021-02-10 11:07:06","uploaded":"2021-02-10 13:19:45","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2","Cc":"RAN WG3","lsoriginalls":"R1-2102074","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100137.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100144","title":"LS from RAN WG2: Reply LS on AN-PDB and PER targets for satellite access","source":"RAN WG2","contact":"Bharat Shrestha","contact-id":85593,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for the LS on AN-PDB and PER targets for satellite access and provide following answers. SA WG2 Question 1: SA WG2 would like to ask RAN WG1, and RAN WG2 to indicate what is the expected 'lower' and 'higher' AN-PDB values when the different RAT types for satellite access is used? RAN WG2 answer: As documented in TR 38.821, the worst-case round-trip propagation delay in NTN with transparent payload is 541.46 ms for GEO, 41.77 ms for LEO at 1200km, and 25.77 ms for LEO at 600km. RAN WG2 understands the round-trip propagation delay in HAPS based NTN with transparent payload would be similar to that in terrestrial network (TN). The round-trip propagation delay can be used to determine PDB based on the number of retransmissions and value of PER. SA WG2 Question 2: SA WG2 would like to ask RAN WG1, and RAN WG2 to indicate what is the expected upper bound of PER when the different RAT types for satellite access is used? RAN WG2 answer: RAN WG2 expects the same TN upper bound of PER to be applicable in NTN. Action: RAN WG2 respectfully asks SA WG2 to take the above information into account.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22630,"status":"noted","reservation_date":"2021-02-10 11:07:06","uploaded":"2021-02-10 13:19:45","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG1","Cc":"RAN WG3","lsoriginalls":"R2-2102497","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100144.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100145","title":"LS from RAN WG2: Reply LS on SA WG2 assumptions from conclusion of study 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 would like to thank RAN WG3 for the LS reply on assumptions after conclusion of the study on architecture aspects for using satellite access in 5G. RAN WG3 approach (a): a) On Uu, SIB content corresponds to momentary coverage area of a satellite beam related to the geographically fixed areas of TAs\/Cells - irrespective of whether the beam is fixed or moving. RAN WG3 approach (b): b) The cell ID used on Uu SIB content (and probably on Xn) are decoupled from cell ID used on NG(N2). The respective mapping is performed in RAN. This requires gNB to acquire the UE's location information. RAN WG2 answer: RAN WG2 discussed the approaches (a) and (b). RAN WG2 prefers approach (b) and will continue working assuming approach (b). However, in the case of earth fixed beams, it will be possible to keep the cell IDs used on Uu and on NG\/N2 aligned. UE location aspects will be handled in a separate LS. Action: RAN WG2 kindly asks RAN WG3 and SA WG2 to take the above information into account and provide feedback, if any.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22640,"status":"noted","reservation_date":"2021-02-10 11:07:06","uploaded":"2021-02-10 13:19:45","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG2","Cc":"SA WG3LI, SA WG5","lsoriginalls":"R2-2102498","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100145.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100146","title":"LS from RAN WG2: LS on IoT-NTN basic architecture","source":"RAN WG2","contact":"Paul Simmons","contact-id":66515,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has discussed architecture options for IoT_NTN to connect to core network, and considers that the IoT-NTN RAN can connect to either an EPC or to a 5GCN. That is, both figures 1 and 2 below shall be supported in Release 17. Action: RAN WG2 kindly would like RAN WG3 and SA WG2 to confirm our understanding of the core network connections to be supported for IoT-NTN in release 17","secretary_remarks":"Response drafted in S2-2100826. Final response in S2-2101663","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22650,"status":"replied to","reservation_date":"2021-02-10 11:07:06","uploaded":"2021-02-10 13:19:45","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG2","Cc":"TSG RAN, CT WG1","lsoriginalls":"R2-2102501","lsreply":"S2-2101663","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100146.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100199","title":"Selection of CN node by NG-RAN node providing satellite access across multiple countries","source":"Ericsson, Vodafone","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The 5G-AN selects a new AMF if (it is configured to do so and) the UE accesses (e.g. Service Request) in a country different to that of its current AMF.","secretary_remarks":"Revision of (Endorsed) S2-2009486 from S2#142E. Approved","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22680,"status":"agreed","reservation_date":"2021-02-12 03:25:05","uploaded":"2021-02-18 16:35:58","revisionof":"S2-2009486","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2537.0,"crrevision":"","crcategory":"C","tsg_crp":"SP-210065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100199.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100200","title":"Identification and mobility restrictions for satellite access","source":"Xiaomi, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description for how AMF identifies 5GSAT RAT types and how mobility and access restrictsions is supported.","secretary_remarks":"Revision of (Endorsed) S2-2008310 from S2#142E. Revised to S2-2101664.","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22690,"status":"revised","reservation_date":"2021-02-12 03:25:09","uploaded":"2021-02-18 16:37:53","revisionof":"S2-2008310","revisedto":"S2-2101664","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2538.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100200.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100201","title":"QoS aspects of satellite backhaul and satellite access .","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Approval","abstract":"This contribution analyses different QoS aspects that have been discussed during the work on 5GSAT in SA WG2 but so far without conclusion. A way forward for rel-17 is proposed.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22710,"status":"noted","reservation_date":"2021-02-12 03:25:11","uploaded":"2021-02-18 16:37:53","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_143e_Electronic\/Docs\/S2-2100201.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100202","title":"Handling of long delays for satellite access and backhaul","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that the packet delay values in case of satellite access\/backhaul may be longer than the standardized PDB.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22720,"status":"noted","reservation_date":"2021-02-12 03:25:11","uploaded":"2021-02-18 16:37:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2539.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100202.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100203","title":"Handling of long delays for satellite access and backhaul","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description how PCF can use the knowledge of satellite backhaul, and add notification about satellite backhaul to AF","secretary_remarks":"Revised to S2-2101665, merging and S2-2100460","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22730,"status":"revised","reservation_date":"2021-02-12 03:25:12","uploaded":"2021-02-18 16:37:53","revisionof":"","revisedto":"S2-2101665","release":"Rel-17","crspec":"23.503","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":508.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100203.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100249","title":"Network selection for NR satellite access","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: New sub-clause is added to explain the main network selection principles via reference to other clauses \/ specifications. This CR re-uses the text of DRAFT CR S2-2008309 that was agreed in SA WG2 #141E.","secretary_remarks":"Revised to S2-2101666.","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22750,"status":"revised","reservation_date":"2021-02-15 14:35:11","uploaded":"2021-02-18 15:12:04","revisionof":"","revisedto":"S2-2101666","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2547.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100249.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100250","title":"Network selection for NR satellite access","source":"Nokia, Nokia Shanghai Bell, Qualcomm Incorporated","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For NR access, gNB gNB includes Cell ID and UE location information, if available. In order to assist the UE to register to a PLMN in the UE location country, the AMF monitors whether the PLMN the UE is accessing a PLMN that is allowed in the UE location. If the AMF, based on information received from the gNB or as the result of an earlier UE location procedure is aware that the PLMN where the UE attempts to register is not allowed in the present UE location, then the AMF rejects the NAS request and includes the country in which the UE is located referring to the MCC's that indicate the present UE location. If the AMF hasn't got sufficiently accurate UE location information for the UE, the AMF may let the NAS procedure proceed and initiate UE location request in order to determine the possible need to deregister the UE later, if it turns out that the UEs registered PLMN is not allowed in the present UE location. In addition to the MCC to country mapping specified in TS 23.122, also 900-series MCCs are considered for NR satellite access. Changes since the latest agreed version of the DRAFT CR S2-2009484: 1) EN in clause 4.2.2.2.2 is replaced by a note warning about the possible inaccuracy. 2) Similar EN removal is done also in clause 4.2.3.2. 3) EN on whether clause 4.2.3.2 needs to be changed is removed from clause 4.2.3.2. (no highlight as the EN is just removed) 4) Changes in the wording on AMF indicated MCC based on CT WG1 feedback in LS C1-210438 to use phrase 'the country in which the UE is located'. 5) The change in clause 4.2.2.3.3 step 1 should actually apply in step 2 between the AMF and UE. 6) Cover page text updates","secretary_remarks":"Revised to S2-2101667.","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22770,"status":"revised","reservation_date":"2021-02-15 14:35:12","uploaded":"2021-02-18 15:12:04","revisionof":"","revisedto":"S2-2101667","release":"Rel-17","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2482.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100250.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100254","title":"Using inclusive language in TR 23.737","source":"Thales, Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: TR 23.737 text is updated to align with the above requirement","secretary_remarks":"Confirm Spec version used - CR states 16.7.0! Revised to S2-2101668.","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22790,"status":"revised","reservation_date":"2021-02-15 14:35:14","uploaded":"2021-02-18 15:12:04","revisionof":"","revisedto":"S2-2101668","release":"Rel-17","crspec":"23.737","crspecversion":"17.1.0","workitem":[{"winame":"FS_5GSAT_ARCH"},{"winame":" TEI17"}],"crnumber":19.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100254.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100430","title":"Discussion on 'QoS with satellite backhaul'.","source":"Thales, TNO, ESA, SES, Eutelsat, Avanti, Intelsat, Sateliot, Hughes Network systems, Reliance Jio, Inmarsat, Unibo, DLR, Gatehouse SatCom A\/S, ICS, Airbus, Catapult, Novamint, Leonardo, STMicroelectronics, SnT - University of Luxembourg, CTTC, ETRI, ST EN","contact":"jean-yves fine","contact-id":87072,"tdoctype":"discussion","for":"Approval","abstract":"This contribution proposes a way forward in the standardization of the 'QoS' with satellite backhaul. A basic set of scenarios and topics are proposed to be addressed within Rel-17. The remaining scenarios and further enhancements related to 'QoS' with satellite backhaul are proposed to be studied and defined in a subsequent release.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22810,"status":"noted","reservation_date":"2021-02-17 17:37:10","uploaded":"2021-02-18 09:59:27","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_143e_Electronic\/Docs\/S2-2100430.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100458","title":"Discussion on 5QI due to satellite access and\/or satellite backhaul.","source":"XiaoMi","contact":"Dong Chen","contact-id":85557,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution proposes to analyse how to support satellite backhaul.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22820,"status":"noted","reservation_date":"2021-02-18 03:19:04","uploaded":"2021-02-18 03:38:15","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_143e_Electronic\/Docs\/S2-2100458.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100459","title":"Introduce new standardized 5QI to QoS characteristics mapping due to Satellite Access\/Satellite Backhaul","source":"XiaoMi","contact":"Dong Chen","contact-id":85557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add new standardized 5QI to QoS characteristics mapping for Satellite Access\/Satellite Backhaul","secretary_remarks":"Revision of S2-2008596 from S2#142E. Merged into S2-2101669","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22830,"status":"merged","reservation_date":"2021-02-18 03:19:04","uploaded":"2021-02-18 03:38:15","revisionof":"S2-2008596","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2579.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100459.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100460","title":"Handling of long delays for satellite access and\/or backhaul","source":"XiaoMi","contact":"Dong Chen","contact-id":85557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description on how PCF use the knowledge of satellite access and\/or satellite backhaul to decide 5QI based on satellite acess and\/or backhaul information and add notification about satellite access\/backhaul to AF","secretary_remarks":"Merged into S2-2101665","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22840,"status":"merged","reservation_date":"2021-02-18 03:19:05","uploaded":"2021-02-18 03:38:15","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":526.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100460.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100461","title":"Identification and mobility restrictions for satellite access","source":"Xiaomi, Ericsson","contact":"Dong Chen","contact-id":85557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description for how AMF identifies 5GSAT RAT types and how mobility and access restrictsions is supported.","secretary_remarks":"Revision of S2-2006591 from S2#141E. Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22850,"status":"noted","reservation_date":"2021-02-18 03:19:06","uploaded":"2021-02-18 03:38:15","revisionof":"S2-2006591","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2580.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100461.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100556","title":"PDU session establishment for NR satellite access","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During PDU session establishement procedure, the AMF verifies the location of the UE. If the UE is in different country than the selected PLMN, the AMF rejects the PDU session establishment request and initiates Network-initiated Deregistration procedures to release any existing PDU session.","secretary_remarks":"Postponed","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22860,"status":"postponed","reservation_date":"2021-02-18 08:33:30","uploaded":"2021-02-18 13:16:48","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2523.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100556.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100603","title":"Discussion of NCGI support for Emergency Services calls","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"discussion","for":"Approval","abstract":"Discusses how to continue support for emergency services calls using an NCGI corresponding to a fixed geographic area.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22870,"status":"noted","reservation_date":"2021-02-18 09:17:35","uploaded":"2021-02-18 09:54:17","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100603.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100627","title":"[DRAFT] LS on Provision of NCGI to 5GC IMS for support of emergency services calls with 5G satellite access","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3. CC: CT WG1, SA WG3-LI","secretary_remarks":"Postponed","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22880,"status":"postponed","reservation_date":"2021-02-18 09:22:22","uploaded":"2021-02-18 09:54:17","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"CT WG1, SA WG3-LI","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100627.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100644","title":"Discussion on satellite backhaul","source":"CATT, ZTE, China Mobile","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"discussion","for":"Endorsement","abstract":"This contribution proposes to focus on GEO satellite backhaul in rel 17.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22890,"status":"noted","reservation_date":"2021-02-18 09:39:23","uploaded":"2021-02-18 10:16:01","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_143e_Electronic\/Docs\/S2-2100644.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100647","title":"[DRAFT] Reply to LS on NR satellite access PLMN selection","source":"OPPO","contact":"Jingran Chen","contact-id":88895,"tdoctype":"LS out","for":"Approval","abstract":"This is a reply LS on NR satellite access PLMN selection.","secretary_remarks":"Response to S2-2100061. Revised to S2-2101662.","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22580,"status":"revised","reservation_date":"2021-02-18 09:40:02","uploaded":"2021-02-18 09:55:09","revisionof":"","revisedto":"S2-2101662","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100647.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100815","title":"5QIs for satellite access","source":"Qualcomm Incorprorated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A new non-GBR 5QI with PDB=832ms is added A NOTE is added in Table 5.7.4-1 to clarify that 5G-AN Packet delay budget is not applicable for 5QIs that require 5G-AN PDB lower than the typical propagation and scheduling delay values when LEO satellite access type is used","secretary_remarks":"Revised to S2-2101669, merging and S2-2100459","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22900,"status":"revised","reservation_date":"2021-02-18 12:16:01","uploaded":"2021-02-18 21:19:00","revisionof":"","revisedto":"S2-2101669","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2651.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100815.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100826","title":"[DRAFT] Reply LS on IoT-NTN basic architecture","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to RAN WG2 LS on NTN IoT","secretary_remarks":"Response to S2-2100146. Revised to S2-2101663.","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22660,"status":"revised","reservation_date":"2021-02-18 12:18:00","uploaded":"2021-02-18 20:19:08","revisionof":"","revisedto":"S2-2101663","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"RAN, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100826.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100875","title":"Intra NG-RAN handover via CN for NR satellite access","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that N2 based handover can be used for intra NG-RAN handover. Existing handover procedures for network sharing scenarios (in 4.9.1.3) specify that the target PLMN ID is included in the TAI in the Handover Required message. Alternative approaches based on a 'virtual gNB' concept could simply lead to 'Xn handovers between the virtual gNBs' without any change of AMF.","secretary_remarks":"Revision of S2-2008312 from S2#141E. Approved","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22920,"status":"agreed","reservation_date":"2021-02-18 13:40:19","uploaded":"2021-02-18 13:55:36","revisionof":"S2-2008312","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2575.0,"crrevision":"","crcategory":"B","tsg_crp":"SP-210065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100875.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100948","title":"Policy control based on satellite backhaul information","source":"Xiaomi","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Satellite backhaul change added as a SMF PCRT and SMF input for policy decision.","secretary_remarks":"Revision of S2-2009487 from S2#142E. Revised to S2-2101670.","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22930,"status":"revised","reservation_date":"2021-02-18 16:10:34","uploaded":"2021-02-18 18:01:35","revisionof":"S2-2009487","revisedto":"S2-2101670","release":"Rel-17","crspec":"23.503","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":539.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100948.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100965","title":"Detection of satellite backhaul based on configuration information","source":"Xiaomi","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF can determine that UE is currently over satellite backhaul and report it to the SMF over N11. UPF can determine that the PDU session is over satellite backhaul and report it to the SMF over N4.","secretary_remarks":"Revised to S2-2101671.","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22950,"status":"revised","reservation_date":"2021-02-18 17:00:24","uploaded":"2021-02-18 18:01:35","revisionof":"","revisedto":"S2-2101671","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2674.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100965.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100966","title":"Accurate UE location verification for motility restriction due to satellite access","source":"Xiaomi","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For satellite access, AMF triggers LCS procedure to verify UE location for the determination of Mobility Restrictions.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22970,"status":"noted","reservation_date":"2021-02-18 17:00:25","uploaded":"2021-02-18 18:01:35","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2675.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100966.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100967","title":"Accurate UE location required by SMF and PCF","source":"Xiaomi","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: On User Location Information, for satellite access, AMF provides UE geographical location, e.g. GNSS information, instead of Cell ID if requested by the SMF. On PRA, for satellite access, a geographical location area may be associated to a PRA Identifier. AMF invokes 5GC-NI-LR procedure defined in 6.10.1 of TS 23.273 to acquire UE geographical location if requested by PCF.","secretary_remarks":"Postponed","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22980,"status":"postponed","reservation_date":"2021-02-18 17:00:26","uploaded":"2021-02-18 18:01:35","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2676.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100967.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100968","title":"Accurate UE location required by SMF and PCF","source":"Xiaomi","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: On User Location Information, for satellite access, AMF provides UE geographical location, e.g. GNSS information, instead of Cell ID if requested by the SMF. On PRA, for satellite access, a geographical location area may be associated to a PRA Identifier. AMF invokes 5GC-NI-LR procedure defined in 6.10.1 of TS 23.273 to acquire UE geographical location if requested by SMF or PCF directly.","secretary_remarks":"Postponed","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22990,"status":"postponed","reservation_date":"2021-02-18 17:00:27","uploaded":"2021-02-18 18:01:35","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":540.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100968.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100969","title":"LCS support of satellite access","source":"Xiaomi","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the descriptions that the AMF may additionally provides the indication of satellite access to the LMF for the determination of positioning methods. Add UE connectivity state per access type and the indication of satellite access as the optional input parameters for Nlmf_Location_DetermineLocation service operation.","secretary_remarks":"Postponed","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":23000,"status":"postponed","reservation_date":"2021-02-18 17:00:28","uploaded":"2021-02-18 18:01:35","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.273","crspecversion":"16.5.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":156.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100969.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101025","title":"N3 connection maintenance when established over GEO or NGSO satellites","source":"TNO","contact":"Relja Djapic","contact-id":83525,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is possible to preserve N3 connectivity in case a satellite transport network (satellite backhaul) is having a quasi-constant transit delay. In such a case the N3 remains uninterrupted irrespective of the topology of the satellite backhaling network.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":23010,"status":"noted","reservation_date":"2021-02-18 21:40:31","uploaded":"2021-02-18 21:45:27","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2686.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101025.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101045","title":"PDB in case of long satellite backhaul latency","source":"TNO","contact":"Relja Djapic","contact-id":83525,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Make use of 'soft uper bound' interpretation of PDB (as stated in 23.501) to accommodate larger delays of satellite backhauling in case the manquements introduced by latency larger than the (CN) PDB are possible to compensate on the application layer.","secretary_remarks":"Noted","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":23020,"status":"noted","reservation_date":"2021-02-18 23:47:20","uploaded":"2021-02-18 23:52:57","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2688.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101045.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101662","title":"Reply to LS on NR satellite access PLMN selection","source":"SA WG2","contact":"Jingran Chen","contact-id":88895,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: TS 23.502 CR 2482","secretary_remarks":"Revision of S2-2100647r02. Approved","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22590,"status":"approved","reservation_date":"2021-03-11 07:58:11","uploaded":"2021-03-11 08:31:23","revisionof":"S2-2100647","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100061","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101662.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101663","title":"Reply LS on IoT-NTN basic architecture","source":"SA WG2","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3. CC: TSG RAN, CT WG1","secretary_remarks":"Revision of S2-2100826r04. Approved","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22670,"status":"approved","reservation_date":"2021-03-11 07:58:12","uploaded":"2021-03-11 08:31:23","revisionof":"S2-2100826","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100146","lsto":"RAN WG2, RAN WG3","Cc":"TSG RAN, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101663.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101664","title":"Identification and mobility restrictions for satellite access","source":"Xiaomi, Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description for how AMF identifies 5GSAT RAT types and how mobility and access restrictsions is supported.","secretary_remarks":"Revision of S2-2100200r02. Approved","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22700,"status":"agreed","reservation_date":"2021-03-11 07:58:12","uploaded":"2021-03-11 08:31:23","revisionof":"S2-2100200","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2538.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-210065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101664.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101665","title":"Handling of long delays for satellite access and backhaul","source":"Ericsson, Xiaomi","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description how PCF can use the knowledge of satellite backhaul, and add notification about satellite backhaul to AF","secretary_remarks":"Revision of S2-2100203r06, merging and S2-2100460. Approved","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22740,"status":"agreed","reservation_date":"2021-03-11 07:58:23","uploaded":"2021-03-11 08:31:23","revisionof":"S2-2100203","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":508.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-210065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101665.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101666","title":"Network selection for NR satellite access","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: New sub-clause is added to explain the main network selection principles via reference to other clauses \/ specifications. This CR re-uses the text of DRAFT CR S2-2008309 that was agreed in SA WG2 #141E.","secretary_remarks":"Revision of S2-2100249r01. Approved","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22760,"status":"agreed","reservation_date":"2021-03-11 07:58:25","uploaded":"2021-03-11 08:31:23","revisionof":"S2-2100249","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2547.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101666.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101667","title":"Network selection for NR satellite access","source":"Nokia, Nokia Shanghai Bell, Qualcomm Incorporated","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For NR access, gNB gNB includes Cell ID and UE location information, if available. In order to assist the UE to register to a PLMN in the UE location country, the AMF monitors whether the PLMN the UE is accessing a PLMN that is allowed in the UE location. If the AMF, based on information received from the gNB or as the result of an earlier UE location procedure is aware that the PLMN where the UE attempts to register is not allowed in the present UE location, then the AMF rejects the NAS request and includes the country in which the UE is located referring to the MCC's that indicate the present UE location. If the AMF hasn't got sufficiently accurate UE location information for the UE, the AMF may let the NAS procedure proceed and initiate UE location request in order to determine the possible need to deregister the UE later, if it turns out that the UEs registered PLMN is not allowed in the present UE location. In addition to the MCC to country mapping specified in TS 23.122, also 900-series MCCs are considered for NR satellite access. Changes since the latest agreed version of the DRAFT CR S2-2009484: 1) EN in clause 4.2.2.2.2 is replaced by a note warning about the possible inaccuracy. 2) Similar EN removal is done also in clause 4.2.3.2. 3) EN on whether clause 4.2.3.2 needs to be changed is removed from clause 4.2.3.2. (no highlight as the EN is just removed) 4) Changes in the wording on AMF indicated MCC based on CT WG1 feedback in LS C1-210438 to use phrase 'the country in which the UE is located'. 5) The change in clause 4.2.2.3.3 step 1 should actually apply in step 2 between the AMF and UE. 6) Cover page text updates","secretary_remarks":"Revision of S2-2100250r03. Approved","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22780,"status":"agreed","reservation_date":"2021-03-11 07:58:26","uploaded":"2021-03-11 08:31:23","revisionof":"S2-2100250","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2482.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101667.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101668","title":"Using inclusive language in TR 23.737","source":"Thales, Nokia, Nokia Shanghai Bell, Samsung","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: TR 23.737 text is updated to align with the above requirement","secretary_remarks":"Revision of S2-2100254r01. Approved","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22800,"status":"agreed","reservation_date":"2021-03-11 07:58:27","uploaded":"2021-03-11 08:31:23","revisionof":"S2-2100254","revisedto":"","release":"Rel-17","crspec":"23.737","crspecversion":"17.1.0","workitem":[{"winame":"FS_5GSAT_ARCH"},{"winame":" TEI17"}],"crnumber":19.0,"crrevision":1.0,"crcategory":"D","tsg_crp":"SP-210087","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101668.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101669","title":"5QIs for satellite access","source":"Qualcomm Incorprorated, Xiaomi","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A new non-GBR 5QI with PDB=832ms is added A NOTE is added in Table 5.7.4-1 to clarify that 5G-AN Packet delay budget is not applicable for 5QIs that require 5G-AN PDB lower than the typical propagation and scheduling delay values when LEO satellite access type is used","secretary_remarks":"Revision of S2-2100815r03, merging and S2-2100459. Approved","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22910,"status":"agreed","reservation_date":"2021-03-11 07:58:28","uploaded":"2021-03-11 08:31:23","revisionof":"S2-2100815","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2651.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-210065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101669.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101670","title":"Policy control based on satellite backhaul information","source":"Xiaomi","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Satellite backhaul change added as a SMF PCRT and SMF input for policy decision.","secretary_remarks":"Revision of S2-2100948r02. Approved","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22940,"status":"agreed","reservation_date":"2021-03-11 07:58:29","uploaded":"2021-03-11 08:31:23","revisionof":"S2-2100948","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":539.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101670.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101671","title":"Detection of satellite backhaul based on configuration information","source":"Xiaomi, Samsung","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UPF can determine a satellite backhaul with long delay is used over N3 and report it to the SMF over N4 during N4 Association Setup procedure.","secretary_remarks":"Revision of S2-2100965r03. Approved","agenda_item_sort_order":65,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22960,"status":"agreed","reservation_date":"2021-03-11 07:58:30","uploaded":"2021-03-11 08:31:23","revisionof":"S2-2100965","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2674.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-210065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101671.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]