[{"name":"S2-2103716","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-2102081 from S2#144E. Postponed. Revised at S2-146E to S2-2105224","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":18780,"status":"postponed","reservation_date":"2021-04-21 06:59:57","uploaded":"2021-04-28 11:28:11","revisionof":"S2-2102081","revisedto":"S2-2105224","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_145E_Electronic_2021-05\/Docs\/S2-2103716.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103737","title":"LS from SA WG3-LI: Reply LS on UE location aspects in NTN","source":"SA WG3-LI","contact":"Mark Canterbury","contact-id":70749,"tdoctype":"LS in","for":"Information","abstract":"SA WG3LI thanks RAN WG2 for the following questions, asked in relation to the procedures used by the NG-RAN to perform core network selection and construction of cell IDs: - Question 1: RAN WG2 would like to ask RAN WG3, SA WG3-LI and SA WG2 to confirm whether the current functionality identified [in s3i210204] is sufficient for use in Non-Terrestrial Networks including initial registration procedure. SA WG3LI believes that the functionality described is sufficient if it provides comparable levels of assurance and granularity to terrestrial network cell sizes (as per our previous LS S3i200056). If the levels of assurance and granularity are not comparable, then it is unlikely to be sufficient. SA WG3LI would welcome further clarity from the RAN groups and SA WG2 on which is likely to be the case. - 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. SA WG3LI notes that any method which relies solely on UE-generated location information is unlikely to be considered reliable for network selection purposes. Therefore, a method such as GNSS\/A-GNSS cannot be considered as reliable or trusted unless the information provided by the UE can be verified by the network. In the event that the available location information is insufficient for the AMF to determine the UE location with comparable accuracy and reliability to terrestrial networks, SA WG3LI considers that invocation of LCS procedures via the LMF may be necessary to fulfil regulatory obligation. Separately from this discussion, and for the avoidance of doubt, LI generally requires the ability to report any location information available to the network (whether considered reliable or not), together with an indication of how the location was obtained so that the 'reliability' of the location can be determined by Law Enforcement.","secretary_remarks":"Noted","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":18790,"status":"noted","reservation_date":"2021-04-21 06:59:57","uploaded":"2021-04-28 11:28:11","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG1, SA WG2, SA WG3, CT WG1, RAN WG3, ETSI TC LI","lsoriginalls":"S3i210282","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2103737.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103749","title":"LS to ITU-T on extraterritorial use of MCC+MNC for satellite networks","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"3GPP is working on the integration of satellite access into 5G core network architecture. In relation to the related study on PLMN selection for satellite networks, CT WG1 group seeks clarification on the extraterritorial use of MCC+MNC for a satellite deployment scenario in Figure 1. In this scenario, PLMN X operates a satellite network out of Country A but the intention is also to provide service in parts of Country B and Country C. This is not a cross-border leakage scenario.","secretary_remarks":"Noted","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":18800,"status":"noted","reservation_date":"2021-04-21 06:59:58","uploaded":"2021-05-03 06:24:45","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T Study Group 2","Cc":"SA WG3LI, RAN WG2, SA WG2, SA WG1, TSG SA, TSG CT","lsoriginalls":"C1-212539","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2103749.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103761","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":"First, CT WG1 would like to thank SA WG3LI for the reply LS containing a feedback to CT WG1's request to identify services that a UE can obtain by a PLMN not allowed in the country where the UE is physically located, which is as follows: None (with the possible exception of emergency calling - this should be referred to SA WG1) With this feedback, CT WG1 would like to ask SA WG1 the following questions: 1. Should a UE, with or without a USIM, attempt to obtain emergency services from a PLMN not allowed to operate in the country of the UE's location? 2. Should a UE, with or without a USIM, always expect to obtain emergency services from a PLMN allowed to operate in the country in the UE location? 3. If the answer to any of the above questions is no, could SA WG1 provide the necessary guidance for selecting a PLMN that can provide emergency services to the UE over satellite access?","secretary_remarks":"Noted","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":18810,"status":"noted","reservation_date":"2021-05-03 05:55:58","uploaded":"2021-05-03 06:24:46","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG2, SA WG3LI","lsoriginalls":"C1-212600","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2103761.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103770","title":"LS on multiple TACs per PLMN","source":"RAN WG2","contact":"Xun Tang","contact-id":78305,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has discussed the tracking area update procedure aiming to support Earth fixed tracking area, and has made the following agreements: - The network may broadcast more than one TACs per PLMN in a cell. - When the network stops broadcasting a TAC, the UE needs to know it. - RAN WG2 assume UE does not do TAU if one of the currently broadcasted TAC belongs to UE's registration area. - RAN WG2 confirm that in NTN when TAC change in SI happens is up to network implementation, i.e. it may not exactly sync up with real-time illumination on ground. To follow the principle 'the AS shall report tracking area information to the NAS' specified in TS 38.304, RAN WG2 has discussed the following two options: - Option 1: AS still reports only one TAC for one PLMN even if more than one TACs per PLMN are broadcasted in an NTN cell. - Option 2: AS indicates all received TAC(s) for one PLMN to NAS layer. RAN WG2 would like to inform CT WG1 and SA WG2 that majority of companies think option 1 has larger RAN WG2 impact, as AS layer has to select one TAC from the broadcast ones to report to NAS layer, thus RAN WG2 has preference for option 2. RAN WG2 would then like to ask the following question to CT WG1: - Is option 2, i.e. 'AS indicates all received TAC(s) for one PLMN to NAS layer', feasible from a NAS layer perspective? Action: SA WG2 is kindly requested to take the above information into account and provide feedback, if any.","secretary_remarks":"Response drafted in S2-2104780. Final response in S2-2104891","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":18760,"status":"replied to","reservation_date":"2021-05-03 05:55:59","uploaded":"2021-05-03 06:24:45","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"RAN WG3","lsoriginalls":"R2-2104377","lsreply":"S2-2104891","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2103770.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103823","title":"RAT fallback and Emergency Service fallback to NR Satellite Access","source":"Rakuten Mobile","contact":"Kenichiro Aoyagi","contact-id":90937,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To utilize NR satellite as the target RAT for the RAT fallback in 5GS and Emergency Service fallback.","secretary_remarks":"Noted","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22310,"status":"noted","reservation_date":"2021-05-07 00:03:13","uploaded":"2021-05-10 03:22:54","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2859.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2103823.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103824","title":"RAT fallback and Emergency Service fallback to NR Satellite Access","source":"Rakuten Mobile","contact":"Kenichiro Aoyagi","contact-id":90937,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To utilize NR satellite as the target RAT for the RAT fallback in 5GS and Emergency Service fallback.","secretary_remarks":"Noted","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22320,"status":"noted","reservation_date":"2021-05-07 00:05:14","uploaded":"2021-05-10 03:22:54","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2735.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2103824.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103831","title":"Clarifications to satellite backhaul","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. clarifying the AMF determines satellite backhaul categories based on the the configuration. 3. clarifying the cases of gNBs with hybrid satellite backhauls or satellite backhaul involving inter-satellite links are out of the scope of this release","secretary_remarks":"Merged into S2-2104893","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22330,"status":"merged","reservation_date":"2021-05-07 09:16:32","uploaded":"2021-05-07 09:29:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2860.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2103831.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104277","title":"Corrections and clarification on satellite backhaul","source":"CATT","contact":"Xiaoyan Duan","contact-id":85499,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Change 'satellite category backhaul' to 'satellite backhaul category '; 2. Remove the 'non-satellite' from satellite backhaul category and modify the descriptions correspondingly; 3. Clarify that only handling of satellite backhaul with one satellite is specified in this release, and satellite backhaul category refers to the type of the involved satellite. Rev2: Add 'OTHERSAT' to satellite backhaul category to align with TS 23.501, i.e. a satellite with a type other than LEO, MEO, GEO may be used for backhaul as well as for radio access.","secretary_remarks":"Revision of (Agreed) S2-2103554. Confirm CR Revision - CR states 0! Approved","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22340,"status":"agreed","reservation_date":"2021-05-10 09:55:33","uploaded":"2021-05-10 10:16:23","revisionof":"S2-2103554","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":554.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-210342","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104277.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104314","title":"UPF selection based on the UPF ability to support satellite connection","source":"xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UPF selection needs to be based on the ability of UPF to support satellite connection if satellite backhaul is used.","secretary_remarks":"Noted","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22460,"status":"noted","reservation_date":"2021-05-10 10:35:20","uploaded":"2021-05-10 11:31:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2916.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104314.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104315","title":"PDU session establishment handling in SMF based on satellite information","source":"xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: SMF may check satellite access\/backhaul whether consistency with the network slice when receiving PDU session establishment request.","secretary_remarks":"Noted","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22470,"status":"noted","reservation_date":"2021-05-10 10:35:30","uploaded":"2021-05-10 11:34:07","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2798.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104315.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104316","title":"Satellite backhaul with long delay notification to the PCF","source":"xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This contribution aims to add description in TS23.502 in alignment with TS 23.503","secretary_remarks":"Merged into S2-2104892","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22420,"status":"merged","reservation_date":"2021-05-10 10:35:31","uploaded":"2021-05-10 11:34:07","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2799.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104316.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104317","title":"Policy Control Request Trigger condition and Eventing report modification","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add new value to Policy Control Request Trigger condition relevant for SMF and Events relevant for reporting from the PCF","secretary_remarks":"Noted","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22450,"status":"noted","reservation_date":"2021-05-10 10:35:32","uploaded":"2021-05-10 11:34:07","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":591.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104317.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104412","title":"Alternative QoS profile for satellite backhaul","source":"Samsung","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the longer PDB values for satellite backhaul can be provided to the NG-RAN by using Alternative QoS Profile when the satellite backhaul category information is provided to the PCF.","secretary_remarks":"Noted","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22350,"status":"noted","reservation_date":"2021-05-10 12:36:38","uploaded":"2021-05-10 12:47:04","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2925.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104412.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104490","title":"SMF reports satellite backhaul information to PCF during the PDU session establishment procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Satellite Backhaul Category information is added as an optional input for Npcf_SMPolicyControl_Create and Npcf_SMPolicyControl_Update Service .","secretary_remarks":"Revised to S2-2104892, merging S2-2104316.","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22360,"status":"revised","reservation_date":"2021-05-10 13:26:56","uploaded":"2021-05-10 14:47:21","revisionof":"","revisedto":"S2-2104892","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2829.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104490.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104592","title":"Removal of UPF indication of backhaul QoS to SMF","source":"Nokia, Nokia Shanghai Bell, Xiaomi","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF informs the SMF of satellite backhaul instead of the UPF.","secretary_remarks":"r07 agreed. Revised to S2-2104893, merging S2-2103831","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22380,"status":"revised","reservation_date":"2021-05-10 14:17:10","uploaded":"2021-05-10 16:47:51","revisionof":"","revisedto":"S2-2104893","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2948.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104592.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104593","title":"Satellite backhaul with long delay notification to the SMF","source":"Xiaomi, Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update PDU session establishment procedures to clarify AMF reporting satellite backhaul category to the SMF. Add change of 'satellite backhaul category' or change between satellite backhaul and non-satellite backhaul as one of events exposed by AMF. Add 'satellite backhaul category' to Nsmf_PDUSession_Create service operation.","secretary_remarks":"r04 agreed. Revised to S2-2105133.","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22430,"status":"revised","reservation_date":"2021-05-10 14:17:11","uploaded":"2021-05-10 16:47:51","revisionof":"","revisedto":"S2-2105133","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2844.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104593.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104670","title":"Determination of 5QI for satellite backhaul","source":"Xiaomi","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add descriptions on how a PCF determines the 5QI for an application carried over satellite backhaul.","secretary_remarks":"r02 agreed. Revised to S2-2104855.","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22400,"status":"revised","reservation_date":"2021-05-10 16:42:01","uploaded":"2021-05-10 17:24:12","revisionof":"","revisedto":"S2-2104855","release":"Rel-17","crspec":23.503,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":601.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104670.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104774","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 to support a Mobility Registration Update with soft TAC update are included.","secretary_remarks":"Postponed","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22480,"status":"postponed","reservation_date":"2021-05-10 21:45:04","uploaded":"2021-05-10 22:59:35","revisionof":"","revisedto":"S2-2106522","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2875.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104774.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104777","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 to support a Mobility Registration Update with soft TAC update are included.","secretary_remarks":"Revision of (withdrawn) S2-2102402. Postponed","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22490,"status":"postponed","reservation_date":"2021-05-10 21:55:25","uploaded":"2021-05-10 22:59:35","revisionof":"S2-2102402","revisedto":"S2-2106521","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2748.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104777.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104780","title":"[DRAFT] LS Response to LS on multiple TACs per PLMN","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, CT WG1. CC: RAN WG3","secretary_remarks":"","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":18770,"status":"revised","reservation_date":"2021-05-10 22:17:04","uploaded":"2021-05-10 22:59:35","revisionof":"","revisedto":"S2-2104891","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104780.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104781","title":"Support of IMS Emergency Calls over NR Satellite Access","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that UPLI can contain an indication of NR satellite access. The scope of TS 23.167 is explicitly extended to NR satellite access.","secretary_remarks":"Revision of (Postponed) S2-2102395. r07 agreed. Revised to S2-2105134.","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22500,"status":"revised","reservation_date":"2021-05-10 22:21:54","uploaded":"2021-05-10 22:59:35","revisionof":"S2-2102395","revisedto":"S2-2105134","release":"Rel-17","crspec":23.167,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":361.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104781.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104793","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":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks CT WG1 for the LS asking the following questions (taken from C1-212600): 1. Should a UE, with or without a USIM, attempt to obtain emergency services from a PLMN not allowed to operate in the country of the UE's location? 2. Should a UE, with or without a USIM, always expect to obtain emergency services from a PLMN allowed to operate in the country in the UE location? 3. If the answer to any of the above questions is no, could SA WG1 provide the necessary guidance for selecting a PLMN that can provide emergency services to the UE over satellite access? SA WG1 has investigated those questions and would like to provide the following answers: SA WG1 response to CT WG1 question 1: This depends on how the UE knows the PLMN is not allowed to operate at the UE's location. If a PLMN has indicated to the UE that it is not allowed to operate in the country of the UE's location, then this is also an indication that the PLMN is unable to provide support the various requirements related to emergency services, notably routing to a suitable PSAP. Note that it cannot be assumed that any PLMN will be able to support emergency calls for any country. However, in border areas, PLMNs and\/or PSAPs may provide some support for emergency calls from across a border. This also currently happens in terrestrial networks. It should be up to the PLMN to determine whether and to what extend cross-border support is available and emergency calls can be allowed. This implies that, in case the UE itself has determined that it is in a country the PLMN is not allowed to operate in, the UE may attempt to obtain emergency services. SA WG1 response to CT WG1 question 2: Yes. SA WG1 response to CT WG1 question 3: The UE should first determine a most suitable PLMN based on its own physical location determination. As there may be border cases where the UE cannot determine sufficiently accurate or sufficiently precise in which country it is, the UE may also still attempt to obtain (emergency) services from a PLMN that according to the UE is not allowed to operate in the country of the UE's location. If the PLMN indicates it is not allowed to operate in the country of the UE's location, the UE should not (re)-attempt emergency calls.","secretary_remarks":"Noted","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":2104793,"status":"noted","reservation_date":"2021-05-20 10:26:19","uploaded":"2021-05-20 10:29:28","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2, SA WG3LI","lsoriginalls":"S1-211319","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104793.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104855","title":"Determination of 5QI for satellite backhaul","source":"Xiaomi, Ericsson","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add descriptions on how a PCF determines the 5QI for an application carried over satellite backhaul.","secretary_remarks":"Revision of S2-2104670r02. Approved","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22410,"status":"agreed","reservation_date":"2021-06-01 06:04:15","uploaded":"2021-06-01 06:21:36","revisionof":"S2-2104670","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":601.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-210342","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104855.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104891","title":"LS Response to LS on multiple TACs per PLMN","source":"SA WG2","contact":"Stephen Edge","contact-id":84641,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, CT WG1. CC: RAN WG3","secretary_remarks":"Revision of S2-2104780r09. Approved","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22240,"status":"approved","reservation_date":"2021-06-01 06:04:50","uploaded":"2021-06-01 06:21:31","revisionof":"S2-2104780","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2103770","lsto":"RAN WG2, CT WG1","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104891.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104892","title":"SMF reports satellite backhaul information to PCF during the PDU session establishment procedure","source":"Huawei, HiSilicon, Xiaomi","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Satellite Backhaul Category information is added as an optional input for Npcf_SMPolicyControl_Create and Npcf_SMPolicyControl_Update Service .","secretary_remarks":"Revision of S2-2104490, merging S2-2104316. Approved","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22370,"status":"agreed","reservation_date":"2021-06-01 06:04:50","uploaded":"2021-06-01 06:21:36","revisionof":"S2-2104490","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2829.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210342","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104892.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104893","title":"Removal of UPF indication of backhaul QoS to SMF","source":"Nokia, Nokia Shanghai Bell, Xiaomi","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF informs the SMF of satellite backhaul instead of the UPF.","secretary_remarks":"Revision of S2-2104592r07, merging S2-2103831. Approved","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22390,"status":"agreed","reservation_date":"2021-06-01 06:04:51","uploaded":"2021-06-01 06:21:36","revisionof":"S2-2104592","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2948.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-210342","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104893.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105096","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. from 22.926: The borders of a country can be expressed in a polygone of points with lines in between these points. For some borders this is easily done, but many borders are very irregular requiring very large polygones. Furthermore, country borders are sometimes disputed between different countries and are subject to changes (e.g. regions that gain independence, settlements between countries on borders or the extend of economic zones). This makes creating and maintaining a database of all country borders with sufficient accuracy a complicated and politically sensitive task. Which country the UE location belongs to in can be determined by the UE or by the network. Note that the UE and the network may come to different conclusions. The network should have the definitive authority to determine if it wants to provide service for the location of the UE.","secretary_remarks":"Postponed","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22290,"status":"postponed","reservation_date":"2021-05-26 16:43:44","uploaded":"2021-05-26 16:44:43","revisionof":"","revisedto":"S2-2105246","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_145E_Electronic_2021-05\/Docs\/S2-2105096.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105133","title":"Satellite backhaul with long delay notification to the SMF","source":"Xiaomi, Nokia, Nokia Shanghai Bell, Samsung, Ericsson","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update PDU session establishment procedures to clarify AMF reporting satellite backhaul category to the SMF. Add 'satellite backhaul category' to Nsmf_PDUSession_Create, Nsmf_PDUSession_CreateSMContext, and Nsmf_PDUSession_UpdateSMConte","secretary_remarks":"Revision of S2-2104593r04. Approved","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22440,"status":"agreed","reservation_date":"2021-06-01 06:07:20","uploaded":"2021-06-01 06:31:38","revisionof":"S2-2104593","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":2844.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-210342","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2105133.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105134","title":"Support of IMS Emergency Calls over NR Satellite Access","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that UPLI contains an indication of NR satellite access. The scope of TS 23.167 is explicitly extended to satellite cellular access.","secretary_remarks":"Revision of S2-2104781r07. Approved","agenda_item_sort_order":59,"ainumber":"8.11","ainame":"Architecture aspects for using satellite access in 5G (5GSAT_ARCH)","tdoc_agenda_sort_order":22510,"status":"agreed","reservation_date":"2021-06-01 06:07:21","uploaded":"2021-06-01 06:31:38","revisionof":"S2-2104781","revisedto":"","release":"Rel-17","crspec":23.167,"crspecversion":"17.0.0","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":361.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"SP-210342","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2105134.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]