[{"name":"S2-2000031","title":"LS from TSG CT: LS on Proposal to transfer the study on service-based support for SMS in 5GC to CT WGs","source":"TSG CT","contact":"Xiaobao Chen","contact-id":13274,"tdoctype":"LS in","for":"Information","abstract":"In reference to the GSMA 5GJA LS (CP-193242\/SP-190959) to TSG SA and SA WG2 to request the completion of the service-based interface for SMS in 5GC (SP-190184) to meet the operators' requirements for supporting the inter-PLMN security framework based on the SEPP and the use of the secured N32 interface, CT discussed the proposal (CP-193255) to transfer this work to CT WGs to complete the work in Release 17 timeframe. While some stage 2 work is needed, this work could be led by CT if it is agreeable to SA to offload from SA WG2 the work on Service Based Interfaces for SMS in 5GC to CT. CT would like to inform SA of the possibility of doing the study and the relative stage 2 and stage 3 normative work in the relevant CT WGs in Rel-17 with necessary coordination with SA WG2.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2019-12-18 15:23:44","uploaded":"2020-01-06 08:48:38","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, CT WG1, CT WG4","lsoriginalls":"CP-193301","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000031.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000038","title":"LS from RAN WG2: LS on dependencies on AS design for mobility management aspects of NTN in 5GS","source":"RAN WG2","contact":"Nicolas Chuberre","contact-id":21633,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for their LS in S2-1910786 on dependencies on AS design for mobility management aspects of NTN in 5GS. In the LS, SA WG2 informed RAN WG2 and RAN WG3 that the feasibility study FS_5GSAT_ARCH has been addressing some key issues related to mobility management in TR 23.737. However, SA WG2 has focused only on SA WG2 aspects and has not considered impacts of RAN solutions on the 5GS architecture mobility management procedures. SA WG2 will wait to see the results of the RAN WG2 and RAN WG3 work and may modify some of the conclusions and solutions accordingly, or take these results duly into account during the normative phase, as required. ? SA WG2 asked RAN WG2 and RAN WG3 to inform SA WG2 of their solutions selected for the NTN mobility (e.g. cell selection and re-selection) as soon as they may be available. NTN mobility management has been studied in RAN WG2. The results of this study can be found in clause 7.3.1 Idle mode mobility enhancements and clause 7.3.2 Connected mode mobility enhancements of TR 38.821. Action: RAN WG2 requests SA WG2 to take the above information into account.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"postponed","reservation_date":"2019-12-18 15:23:44","uploaded":"2020-01-06 08:48:38","revisionof":"","revisedto":"S2-2001738, S2-2001779","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3","Cc":"CT WG1","lsoriginalls":"R2-1916470","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000038.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000039","title":"LS from RAN WG2: LS on inter-RAT HO from SA to EN-DC","source":"RAN WG2","contact":"Ting Zhang","contact-id":70189,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 discussed the support of inter-RAT HO from NR SA to EN-DC in Rel-16 and agreed that: - The NR SA to EN-DC handover shall be supported in Rel-16 - Assume a new UE capability is needed RAN WG2 kindly asks all the involved groups to take above RAN WG2 decisions into account and update specifications accordingly if any.","secretary_remarks":"This LS was postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"postponed","reservation_date":"2019-12-18 15:23:44","uploaded":"2020-01-06 08:48:38","revisionof":"","revisedto":"S2-2001739, S2-2001780","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, RAN WG4","Cc":"SA WG2, CT WG1","lsoriginalls":"R2-1916600","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000039.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000040","title":"LS from RAN WG2: LS on LS on system level design assumptions for satellite in 5GS","source":"RAN WG2","contact":"Nicolas Chuberre","contact-id":21633,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for their LS in S2-1910787 on system level design assumptions for satellite in 5GS. In the LS, SA WG2 informed RAN WG2 and RAN WG3 that the feasibility study FS_5GSAT_ARCH has been addressing some key issues related to mobility management. Specifically, SA WG2 has considered a solution called 'distributed gNB for NGSO satellites', as described in section 6.9 of TR 23.737. Briefly, such solution assumes that a constellation of NGSO satellites and the corresponding Ground stations appear as a single gNB to both the UE and the CN (AMF and UPF), independently of how many satellites are in the constellation. Such distributed gNB has a single Tracking Area visible to the UE: - this is achieved by having the beams that the satellites project moving depending on the location of the satellites; once a serving satellite would become out of reach it will switch off the beam related to the given TA. To ensure continuity of service, the TA would be served by a new satellite already in reach of the TA; - when possible, each of the beams (from different satellites) that are related to the same TA are using the same radio characteristics, i.e. the same radio frequencies, the same cell information, the same SIB, etc. Thus, the UE will not be aware of which satellites it is connected to; - The solution assumes that the NGSO satellite constellation and ground stations can support multiple distributed gNBs and the corresponding distinct stationary TAs ? 'SA WG2 kindly asks RAN WG2 and RAN WG3 to review and evaluate the design of distributed gNB for NGSO satellite networks and provide feedback as needed.' The architectures and solutions considered by RAN WG2 and RAN WG3 are captured in TR 38.821. No further study on NTN is expected in Rel-16 in RAN WG2. Action: RAN WG2 requests SA WG2 to take the above information into account.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"postponed","reservation_date":"2019-12-18 15:23:44","uploaded":"2020-01-06 08:48:38","revisionof":"","revisedto":"S2-2001740, S2-2001781","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3","Cc":"CT WG1","lsoriginalls":"R2-1916620","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000040.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000058","title":"LS from SA WG5: Reply LS on 5G Cell ID(s) in the 3GPP SA WG5 billing system, related to Retained Data regulations","source":"SA WG5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks ETSI TC LI for their reply LS on 5G Cell ID(s) in the SA WG5 billing system related to Retained Data regulations. Based on the confirmation from ETSI TC LI on their need to introduce the PSCell Id in CHF CDRs for AMF in addition to the PCELL, SA WG5 has approved the Rel-16 pCR S5-197113 on the draft TS 32.256 '5G connection and mobility domain charging; Stage 2', to support the new CDR field. The mechanism by which this information can be made available in the CDR is also described in this TS 32.256 specification. In EPC, no solution is available today for introduction of the PSCell IDs in EPC CDRs. If a solution is developed by SA WG2 based on secondary RAT data Usage Reports, it would then be possible for SA WG5 to specify SGW CDR accordingly.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2019-12-18 15:23:45","uploaded":"2020-01-06 08:48:38","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TC LI","Cc":"TSG SA, SA WG3LI, SA WG2, RAN WG3","lsoriginalls":"S5-197481","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000058.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000064","title":"LS from TSG SA: Reply LS to Transfer the study on service-based support for SMS in 5GC to CT WGs","source":"TSG SA","contact":"Xiaobao Chen","contact-id":13274,"tdoctype":"LS in","for":"Information","abstract":"TSG SA would like to thank TSG CT for the LS on Proposal to transfer the study on service-based support for SMS in 5GC to CT WGs (SP-191281\/CP-193301). In reference to the proposal from TSG CT on the way forward in this LS, TSG SA agrees with the TSG CT's proposal to transfer the work on the definition of service-based interfaces for SMS in 5GC to CT WGs. It is TSG SA's understanding that the work in TSG CT on this topic will have no or minimal impact on the foreseen SA WG2 workload for Release 17.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2019-12-18 15:23:45","uploaded":"2020-01-06 08:48:38","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT","Cc":"SA WG2, SA WG3, CT WG1, CT WG4","lsoriginalls":"SP-191362","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000064.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000071","title":"Alignment of TR skeletons with the architectural principle on modularity.","source":"Orange, Sprint, KPN, Charter, AT&T, NTT Docomo, T-Mobile USA, Vodafone, China Mobile, Deutsche Telekom","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"discussion","for":"Endorsement","abstract":"This contribution proposes to update the skeleton of each Rel-17 ongoing TRs to align them with the architectural principle on modularity.","secretary_remarks":"Revised to S2-2001353.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"revised","reservation_date":"2019-12-20 09:12:41","uploaded":"2020-01-02 14:37:56","revisionof":"","revisedto":"S2-2001353","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000071.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000505","title":"Discussion on QoS Flow Binding correction.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Agreement","abstract":"This discussion paper aims at explaining the issues of current QoS Flow Binding mechanism and proposes to have a solution accordingly.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2020-01-06 18:03:59","uploaded":"2020-01-07 14:16:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000505.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000947","title":"LS from ATIS: Correspondence from ATIS to SA WG2 Regarding a Slice Service Type","source":"ATIS","contact":"Brian K. Daly","contact-id":13316,"tdoctype":"LS in","for":"Action","abstract":"Dear Mr. Puneet Jain (SA WG2 Chairman) and Mr. Maurice Pope (SA WG2 secretary), The Alliance for Telecommunications Industry Solutions (ATIS) launched an IoT Categorization Focus Group in late 2017 to address how the burgeoning growth in the IoT ecosystem is driving a wide range of new uses and requirements on the network infrastructure. Several recent industry initiatives have examined the main features of IoT applications to better understand the requirements posed by each. The objective of ATIS' work is to explore the multidimensional characteristics of IoT across devices, applications, subscription type and technology as well as regulatory and market drivers. This work is instrumental in identifying design features relevant to the standardization of 5G. Attached please find a whitepaper entitled 'IoT Categorization: Exploring the Need for Standardizing Additional Network Slices.' The purpose of this whitepaper is to aid service providers' efforts to build networks that support a full range of IoT devices and services. We believe that in order to achieve these efforts a new Slice Service Type (SST) needs to be defined by SA WG2 in TS 23.501 in order to meet the described IoT characteristics matrix. We kindly ask that SA WG2 review this whitepaper and provide us with feedback at your earliest convenience, but no later than February 7, 2020. Further action (e.g., CRs) will be taken by Individual Member companies in SA WG2#137. If you have any questions, please do not hesitate to contact us. Sincerely, Brian Daly (AT&T), ATIS TOPS Council IoT-CAT Focus Group Co-Leader Farrokh Khatibi (Qualcomm), ATIS TOPS Council IoT-CAT Focus Group Co-Leader Carroll Gray-Preston (ATIS), ATIS TOPS Council IoT-CAT Focus Group Technical Lead","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"postponed","reservation_date":"2020-01-09 06:34:15","uploaded":"2020-01-09 06:35:51","revisionof":"","revisedto":"S2-2001745, S2-2001786","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"IoT_CAT_Liaison_Letter_to_SA2","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000947.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001353","title":"Alignment of TR skeletons with the architectural principle on modularity.","source":"Orange, Sprint, KPN, Charter, AT&T, NTT Docomo, T-Mobile USA, Vodafone, China Mobile, Deutsche Telekom","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"discussion","for":"Endorsement","abstract":"This contribution proposes to update the skeleton of each Rel-17 ongoing TRs to align them with the architectural principle on modularity.","secretary_remarks":"Revision of S2-2000071. Endorsed as a template for TRs.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"endorsed","reservation_date":"2020-01-14 20:14:42","uploaded":"2020-01-18 01:57:51","revisionof":"S2-2000071","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001353.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]