[{"name":"S2-1900003","title":"LS from CT WG1: LS on S-NSSAI(s) for SMF selection","source":"CT WG1","contact":"Sung Hwan Won","contact-id":70307,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has been working on specifying in roaming scenarios, the S-NSSAI(s) that should be used by the AMF for SMF selection when it receives the 5GMM: UL NAS TRANSPORT message including the 5GSM: PDU SESSION ESTABLISHMENT message and the following question arose: Question: If the UE in a VPLMN did not provide the AMF with any S-NSSAI in the 5GMM: UL NAS TRASNPORT message and the AMF has an S-NSSAI of the VPLMN mapped to a default S-NSSAI, should the AMF use the S-NSSAI of the VPLMN for V-SMF selection? It is CT WG1's understanding that an AMF is not mandated to use an S-NSSAI of a VPLMN for V-SMF selection. Action: CT WG1 kindly asks SA WG2 to answer the question above.","secretary_remarks":"Postponed S2-1811608 from S2#129BIS. Response drafted in S2-1901133. Final response in S2-1901251","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11080,"status":"replied to","reservation_date":"2018-12-19 08:47:10","uploaded":"2018-12-19 10:07:34","revisionof":"S2-1811608","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C1-185792","lsreply":"S2-1901251, S2-1901251","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900003.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900006","title":"LS from CT WG1: Reply LS on establishment causes","source":"CT WG1","contact":"Ivo Sedlacek","contact-id":41880,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 would like to thank RAN WG2 for the LS R2-1813465 on establishment causes. CT WG1 also studied TS 38.331 15.3.0 and TS 36.331 15.3.0 and identified that mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess establishment causes were introduced for NR connected to 5GCN but were not introduced for E-UTRA connected to 5GCN. Based on the LS R2-1813465 and TS 38.331 15.3.0 and TS 36.331 15.3.0, CT WG1 agreed the attached CR. Regarding the following question in the LS R2-1813465: Q1: Please confirm that the 'High Priority Access', 'MPS-PriorityAccess' and 'MCS-PriorityAccess' will override 'MT Access' when determining the cause value also in CT WG1 specifications for CN paging. CT WG1 response: In NR connected to 5GCN, highPriorityAccess, mps-PriorityAccess and mcs-PriorityAccess RRC establishment causes override mt-Access RRC establishment cause when determining the RRC establishment cause value for CN paging in CT WG1 specifications. In E-UTRA connected to 5GCN, - highPriorityAccess RRC establishment cause overrides mt-Access RRC establishment cause when determining the RRC establishment cause value for CN paging in CT WG1 specifications; and - for a user with access identity 1 or 2, NAS layer provides highPriorityAccess RRC establishment cause as TS 36.331 v15.3.0 does not specify mps-PriorityAccess and mcs-PriorityAccess establishment causes. See the attached CR. Regarding the following question in the LS R2-1813465: Q2: Please inform RAN WG2 if a cause value for 'Delay tolerant access' needs to be specified for NR or for LTE Resume. CT WG1 response: CT WG1 does not expect usage of delayTolerantAccess RRC establishment cause in Rel-15 5GS CT WG1 specifications. Thus, delayTolerantAccess RRC establishment cause: - does not need to be specified for NR connected to 5GCN in Rel-15 RAN WG2 specifications; and - could be marked as not used in E-UTRA connected to 5GCN in Rel-15 RAN WG2 specifications. Furthermore, CT WG1 would like to highlight that in E-UTRA connected to 5GCN, for a user with access identity 0 establishing the RRC connection for access attempt of: - access category 4 (= MO MMTel voice) or 5 (= MO MMTel video), NAS layer provides mo-VoiceCall RRC establishment cause; and - access category 6 (= MO SMS and SMSoIP), NAS layer provides mo-Data RRC establishment cause.","secretary_remarks":"Postponed S2-1811663 from S2#129BIS. Noted in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11060,"status":"noted","reservation_date":"2018-12-19 08:47:10","uploaded":"2018-12-19 10:07:34","revisionof":"S2-1811663","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG1, SA WG2","lsoriginalls":"C1-186967","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900006.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900011","title":"LS from RAN WG3: Reply LS on RRC cause in RRC reestablishment fallback","source":"RAN WG3","contact":"Feng Han","contact-id":72237,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 discussed the following question from RAN WG2, and provided the answers as follows. Q3: In the reestablishment fallback case, if the RRC establishment cause is not available at the gNB and hence cannot be able to be provided to CN, does this cause any problem RAN WG3 has chosen a protocol solution where the NGAP RRC Establishment Cause IE is mandatory in the INITIAL UE MESSAGE. This approach can also cover the case where no RRC establishment cause is available at the gNB, as outlined in the Q3, by adding an appropriate code point to the NGAP RRC Establishment Cause IE, e.g. 'RRC Establishment Cause not available'. Action: RAN WG3 kindly asks RAN WG2 and SA WG2 to inform RAN WG3 if NGAP needs to support a case where the RRC Establishment Cause is not available at the gNB.","secretary_remarks":"Postponed S2-1811677 from S2#129BIS. Postponed.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11070,"status":"postponed","reservation_date":"2018-12-19 08:47:10","uploaded":"2018-12-19 10:07:34","revisionof":"S2-1811677","revisedto":"S2-1901406","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2","Cc":"CT WG1","lsoriginalls":"R3-187082","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900011.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900016","title":"LS from SA WG5: LS on the slicing terminology and the role of S-NSSAI parameter","source":"SA WG5","contact":"Vladimir Yanover","contact-id":32260,"tdoctype":"LS in","for":"Action","abstract":"1. SA WG5 would like to ask for clarification of the slicing related terminology in the TS 23.501. The TS 23.501 sometimes is using different terms 'Network Slice' and 'Network Slice Instance' in similar situations. For example, the title of the sub-clause 5.15.2 is 'Identification and selection of a Network Slice: the S-NSSAI and the NSSAI'. However, in 5.15.5: 'It [the NSSF] selects the Network Slice instance(s) to serve the UE \u2026' 2. SA WG5 would like to ask for clarification of the slicing related terminology in the TS 38.300 as related to the terminology used in the TS 23.501. The TS 38.300 is not using the term 'Network Slice Instance'; it is the 'Network Slice' that is selected for the UE. For example in the sub-clause 16.3.1: 'NG-RAN supports the selection of the RAN part of the network slice, by assistance information provided by the UE or the 5GC \u2026'. The latter can be interpreted, as the term 'network slice' in the TS 38.300 is equivalent to the term 'network slice instance' in 23.501. 3. SA WG5 would like to ask for clarification of the role of the parameter S-NSSAI. In the TS 23.501, sub-clause 5.15.2: 'Based on the operator's operational or deployment needs, a Network Slice instance can be associated with one or more S-NSSAIs, and an S-NSSAI can be associated with one or more Network Slice instances.' In the sub-clause 16.3.1 of the TS 38.300: 'Each network slice is uniquely identified by a S-NSSAI, as defined in 3GPP TS 23.501'. Assuming that the term 'network slice' in the TS 38.300 means same as 'network slice instance' in 23.501, this sentence seems not in line with the above quotation from the TS 23.501. It seems that other RAN specifications also assume that S-NSSAI is a unique identifier of the Network Slice Instance. For example, the sub-clause 9.2.1 in the TS 38.413, shows for every PDU session one single S-NSSAI value, included into the PDU SESSION RESOURCE SETUP REQUEST message. Action: Please kindly provide clarification on the following issues: a. Which term in the TS 38.300 corresponds to the Network Slice Instance defined in the TS 23.501? b. In RAN, is it possible that a single S-NSSAI value is mapped on more than one Network Slice Instance?","secretary_remarks":"Postponed S2-1811984 from S2#129BIS. Postponed","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11110,"status":"postponed","reservation_date":"2018-12-19 08:47:10","uploaded":"2018-12-19 10:07:34","revisionof":"S2-1811984","revisedto":"S2-1901409","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2","Cc":"RAN WG3","lsoriginalls":"S5-187461","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900016.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900019","title":"LS from SA WG3: Reply LS to S2-1811543 on NSSAI in the Access Stratum","source":"SA WG3","contact":"Abhijeet Kolekar","contact-id":66157,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks SA WG2 for the reply LS S2-1811543. Regarding encryption at NAS level: SA WG3 thanks for the confirmation and updating the SA WG2 specifications. Regarding encryption at Access Stratum (AS) level: SA WG3 discussed the two CRs attached in the LS S2-1811403 and S2-1811565. SA WG3 concluded that CR S2-1811403 always provides privacy while sending NSSAI. CR S2-1811565 supports privacy in default mode. But NSSAI is allowed to be sent in cleartext, only if both HPLMN and VPLMN allow it by policy, in RRC messages for the slices that don't require privacy protection of NSSAI by cryptographic means. With the above in mind, SA WG3 leaves up to SA WG2 to choose which of the CRs is most suitable for Rel-15 5GS. Action: SA WG3 respectfully asks to take the above information into account.","secretary_remarks":"Postponed S2-1812461 from S2#129BIS. Noted in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11120,"status":"noted","reservation_date":"2018-12-19 08:47:11","uploaded":"2018-12-19 10:07:34","revisionof":"S2-1812461","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"RAN WG2, RAN WG3, TSG SA","lsoriginalls":"S3-183659","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900019.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900032","title":"LS from CT WG1: Reply LS on the applicability of service area restriction and NSSAIs to EPLMNs","source":"CT WG1","contact":"Sung Hwan Won","contact-id":70307,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 would like to thank SA WG2 for providing answers to CT WG1's questions and the discussion point in addition. CT WG1 discussed 'possible ways to more efficiently provision the Configured NSSAIs to the UE, e.g. by letting the UE be aware whether equivalent PLMNs share the slicing configuration as the serving PLMN (which may or may not be the case)' and whether to progress this. CT WG1 decided to not progress this in Rel-15. Action: CT WG1 asks SA WG2 to take the above decision into account for its further work.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11420,"status":"noted","reservation_date":"2018-12-19 11:46:38","uploaded":"2018-12-19 11:47:59","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG1","lsoriginalls":"C1-188926","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900032.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900053","title":"Slice interworking HR mode update","source":"NTT DOCOMO, Ericsson","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Propose to clarify that if a UE does not have serving PLMN configured NSSAI, the UE includes the hPMLN S-NSSAI value received from EPC in the NAS Registration Request or the HPLMN S-NSSAI value received during 5G communication with a previous PLMN. Thus, an AMF can send corresponding VPLMN S-NSSAIs values to the UE and VPLMN Configured NSSAI if required.","secretary_remarks":"Revised in parallel session to S2-1901134.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11140,"status":"revised","reservation_date":"2018-12-20 14:19:01","uploaded":"2019-01-14 10:14:12","revisionof":"","revisedto":"S2-1901134","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":733.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900053.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900054","title":"Slice interworking HR mode update","source":"NTT DOCOMO, Ericsson","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Propose to clarify that if a UE does not have serving PLMN configured NSSAI, the UE includes the hPMLN S-NSSAI value received from EPC in the NAS Registration Request or the HPLMN S-NSSAI value received during 5G communication with a previous PLMN. Thus, an AMF can send corresponding VPLMN S-NSSAIs values to the UE and VPLMN Configured NSSAI if required.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11170,"status":"not treated","reservation_date":"2018-12-20 14:21:09","uploaded":"2019-01-14 10:14:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":865.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900054.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900081","title":"UDR Selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The typo in the implementation of CR 594 is corrected in section 6.3.9 (i.e. 'UDR Group ID' is used for UDR selection rather than 'UDM Group ID'). Routing ID term in section 6.2.6 has been replaced by correct term Routing Indicator. The UDR selection function is aligned with the AUSF and UDM selection section.","secretary_remarks":"Revised in parallel session to S2-1901141.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11400,"status":"revised","reservation_date":"2019-01-11 22:12:12","uploaded":"2019-01-15 02:50:05","revisionof":"","revisedto":"S2-1901141","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":741.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900081.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900082","title":"Data Types for parameters within UE Parameter Update via Control Plane Solution","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Routing Indicator and Default Configured NSSAI are defined within Access and Mobility Data Type in section 5.2.3.3.1. In section 5.2.3.3.1, the text related to how UDM may determine new values for UDM Update Data elements is removed as this can be left out of scope of the specification. The definition of the Nudm_SDM_Notification and Nudm_SDM_Info service operations are updated to include use of this operations in relation to the delivery of the UDM Update data and also SoR and Network Slicing Subscription Change indication consistently. Also, a mistake in section 4.20.2 has been corrected (i.e. Routing Identifier used for SUCI calculation is stored at USIM not at UE). The example is removed anyway as additional parameters may be added to this procedure in the future. Finally, the TS still makes use of the term Routing ID referring to the UE's Routing Indicator as defined in TS 23.501. All occurrences of Routing ID term are replaced by Routing Indicator.","secretary_remarks":"Revised in parallel session to S2-1901137.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11300,"status":"revised","reservation_date":"2019-01-11 22:12:13","uploaded":"2019-01-15 02:50:05","revisionof":"","revisedto":"S2-1901137","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":873.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900082.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900120","title":"Correction to NSSAI logic","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The S-NSSAIs of the Default Configured NSSAI should match subscribed S-NSSAIs. Updated reference to 23.502 procedure for updating the Default Configured NSSAI. The S-NSSAIs of the Default Configured NSSAI is a valid Requested NSSAI.","secretary_remarks":"Revised in parallel session, merging S2-1900667, to S2-1901136.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11250,"status":"revised","reservation_date":"2019-01-11 22:59:10","uploaded":"2019-01-15 02:50:05","revisionof":"","revisedto":"S2-1901136","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":756.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900120.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900192","title":"SEPPs in roaming architecture","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add vSEPP and hSEPP in the roaming architectures of the policy framework.","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11530,"status":"agreed","reservation_date":"2019-01-14 02:47:15","uploaded":"2019-01-15 14:44:11","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":190.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190160","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900192.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900249","title":"Update of network slicing text on NSSAI inclusion in RRC","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added provisions that avoid contradiction among different clauses of the TS","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11130,"status":"agreed","reservation_date":"2019-01-14 12:24:41","uploaded":"2019-01-15 10:45:25","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":789.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190154","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900249.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900255","title":"Supporting early trace in AUSF","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding Trace Requirements as optional output information provided by UDM to AUSF allowing AUSF to start tracing as soon as it knows the SUPI (i.e. when UDM has translated the SUCI into a SUPI)","secretary_remarks":"Revised in parallel session to S2-1901143.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11450,"status":"revised","reservation_date":"2019-01-14 12:56:36","uploaded":"2019-01-15 11:25:59","revisionof":"","revisedto":"S2-1901143","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":791.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900255.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900259","title":"Introduce Charging Function in overall architecture","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the CHF in the non-roaming service based architecture representation and in the roaming Home routed service based architecture representation.","secretary_remarks":"Revised in parallel session to S2-1901144.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11470,"status":"revised","reservation_date":"2019-01-14 12:56:40","uploaded":"2019-01-15 11:25:59","revisionof":"","revisedto":"S2-1901144","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":793.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900259.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900266","title":"Update of configured NSSAI handling","source":"Nokia, Nokia Shanghai Bell ; Telecom Italia","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An indication from the UE is added to signal to the PLMN that the Requested NSSAI is not based on the Configured NSSAI for the Serving PLMN. Additional misalignments in the text on the conditions triggering the configured NSSAI to be provided to the UE are also fixed.","secretary_remarks":"Revised in parallel session to S2-1901138.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11180,"status":"revised","reservation_date":"2019-01-14 13:07:53","uploaded":"2019-01-15 10:48:50","revisionof":"","revisedto":"S2-1901138","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":797.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900266.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900271","title":"Update of configured NSSAI handling","source":"Nokia, Nokia Shanghai Bell ; Telecom Italia","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An indication from the UE is added in registration request to signal to the PLMN that the Requested NSSAI is not based on the Configured NSSAI for the Serving PLMN.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11240,"status":"noted","reservation_date":"2019-01-14 13:22:18","uploaded":"2019-01-15 10:48:50","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":902.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900271.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900282","title":"List of equivalent PLMNs in Registration Accept missing","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The list of equivalent PLMNs attribute is added, it is clarified that when this is present, then the allowed NSSAI in the RA applies to all equivalent PLMNs which have TAs in the RA","secretary_remarks":"Revised in parallel session to S2-1901142.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11430,"status":"revised","reservation_date":"2019-01-14 13:36:47","uploaded":"2019-01-15 11:01:55","revisionof":"","revisedto":"S2-1901142","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":904.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900282.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900284","title":"Remove at most eight S-NSSAIs limitation","source":"KDDI","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To remove ' There can be at most eight S-NSSAIs in Allowed and Requested NSSAIs sent in signalling messages between the UE and the Network.'","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11320,"status":"noted","reservation_date":"2019-01-14 13:56:50","uploaded":"2019-01-15 12:52:21","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":807.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900284.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900287","title":"Update to Network Slice availability","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Changing 'NG-RAN' to '5G-AN' to cover both 3GPP and non-3GPP access in clause 5.15.8.","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11330,"status":"agreed","reservation_date":"2019-01-14 14:21:31","uploaded":"2019-01-15 15:01:25","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":808.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190155","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900287.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900419","title":"Clarification on Establishing a PDU Session in a Network Slice","source":"Intel, Qualcomm Incorporated","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the non-existing concept. Consolidate the two possible cases as two sub-bullets.","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11340,"status":"agreed","reservation_date":"2019-01-15 04:09:21","uploaded":"2019-01-15 04:44:16","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":833.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190155","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900419.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900443","title":"Network Slice update clarification","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that AMF notify the SMF to release the PDU Session can also be due to the change of Allowed NSSAI. Remove the Allowed NSSAI is used for target AMF selection. The AMF informs all non-emergency service associated SMF(s) to release the corresponding PDU Session(s).","secretary_remarks":"Revised in parallel session to S2-1901139.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11350,"status":"revised","reservation_date":"2019-01-15 06:51:13","uploaded":"2019-01-15 14:36:26","revisionof":"","revisedto":"S2-1901139","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":933.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900443.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900497","title":"Use of S-NSSAI at interworking from EPS to 5GS","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is corrected that the UE shall use S-NSSAI information from PCO if available or if not then from 5GS","secretary_remarks":"Revision of S2-1811853 from S2#129BIS. Revised in parallel session to S2-1901140.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11380,"status":"revised","reservation_date":"2019-01-15 08:29:51","uploaded":"2019-01-15 10:00:26","revisionof":"S2-1811853","revisedto":"S2-1901140","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":700.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900497.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900541","title":"Correcting references for routing rules configuration","source":"China Telecom","contact":"Jiayifan Liu","contact-id":74811,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the related references from 'TS 23.501 [2] clause 5.8.1.2' to 'TS 23.501 [2] clause 5.8.2.2.2'","secretary_remarks":"Revised in parallel session to S2-1901145.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11500,"status":"revised","reservation_date":"2019-01-15 09:49:31","uploaded":"2019-01-15 10:07:49","revisionof":"","revisedto":"S2-1901145","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":953.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900541.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900564","title":"Permanent identifier with IMEISV format","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add IMEISV as a possible format for PEI","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11520,"status":"agreed","reservation_date":"2019-01-15 10:16:38","uploaded":"2019-01-15 14:29:46","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":875.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190155","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900564.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900567","title":"UE configuration parameters update in the Registration Accept","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that UE parameters update data can optionally be sent to the UE by piggybacking the registration accept message. Also, clarify that the UDM can provide this information as part of subscription information retrieval.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11290,"status":"noted","reservation_date":"2019-01-15 10:16:41","uploaded":"2019-01-15 14:29:46","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":959.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900567.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900667","title":"Introducing mapping information to the Default Configured NSSAI","source":"Motorola Mobility, Lenovo","contact":"Genadi Velev","contact-id":70944,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to add a notion that the S-NSSAI(s) of the Default Configured NSSAI may be associated with mapping to one or more corresponding HPLMN S-NSSAI values.","secretary_remarks":"Merged into S2-1901136.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11280,"status":"merged","reservation_date":"2019-01-15 14:31:19","uploaded":"2019-01-15 14:52:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":902.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900667.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901133","title":"[DRAFT] Reply LS on S-NSSAI(s) for SMF selection","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG4","secretary_remarks":"Created at meeting. Response to S2-1900003. Revised in parallel session to S2-1901251.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11090,"status":"revised","reservation_date":"2019-01-23 02:04:54","uploaded":"2019-01-28 09:47:54","revisionof":"","revisedto":"S2-1901251","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901133.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901134","title":"Slice interworking HR mode update","source":"NTT DOCOMO, Ericsson, Nokia, Nokia Shanghai Bell","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Propose to clarify that if a UE does not have serving PLMN configured NSSAI, the UE includes the hPMLN S-NSSAI value received from EPC in the NAS Registration Request or the HPLMN S-NSSAI value received during 5G communication with a previous PLMN. Thus, an AMF can send corresponding VPLMN S-NSSAIs values to the UE and VPLMN Configured NSSAI if required.","secretary_remarks":"Revision of S2-1900053. Revised in parallel session to S2-1901252.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11150,"status":"revised","reservation_date":"2019-01-23 02:04:54","uploaded":"2019-01-28 09:47:54","revisionof":"S2-1900053","revisedto":"S2-1901252","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":733.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901134.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901135","title":"[DRAFT] LS on Configured NSSAI handling","source":"SA WG2","contact":"Alessio Casati","contact-id":68028,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-1901252","secretary_remarks":"Created at meeting. Revised to S2-1901384.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11210,"status":"revised","reservation_date":"2019-01-23 02:04:57","uploaded":"2019-01-28 09:47:54","revisionof":"","revisedto":"S2-1901384","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901135.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901136","title":"Correction to NSSAI logic","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The S-NSSAIs of the Default Configured NSSAI should match subscribed S-NSSAIs. Updated reference to 23.502 procedure for updating the Default Configured NSSAI. The S-NSSAIs of the Default Configured NSSAI is a valid Requested NSSAI.","secretary_remarks":"Revision of S2-1900120, merging S2-1900667. Revised in parallel session to S2-1901253.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11260,"status":"revised","reservation_date":"2019-01-23 02:04:57","uploaded":"2019-01-28 09:47:54","revisionof":"S2-1900120","revisedto":"S2-1901253","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":756.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901136.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901137","title":"Data Types for parameters within UE Parameter Update via Control Plane Solution","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Routing Indicator and Default Configured NSSAI are defined within Access and Mobility Data Type in section 5.2.3.3.1. In section 5.2.3.3.1, the text related to how UDM may determine new values for UDM Update Data elements is removed as this can be left out of scope of the specification. The definition of the Nudm_SDM_Notification and Nudm_SDM_Info service operations are updated to include use of this operations in relation to the delivery of the UDM Update data and also SoR and Network Slicing Subscription Change indication consistently. Also, a mistake in section 4.20.2 has been corrected (i.e. Routing Identifier used for SUCI calculation is stored at USIM not at UE). The example is removed anyway as additional parameters may be added to this procedure in the future. Finally, the TS still makes use of the term Routing ID referring to the UE's Routing Indicator as defined in TS 23.501. All occurrences of Routing ID term are replaced by Routing Indicator.","secretary_remarks":"Revision of S2-1900082. Agreed in parallel session. This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11310,"status":"agreed","reservation_date":"2019-01-23 02:05:01","uploaded":"2019-01-28 09:47:54","revisionof":"S2-1900082","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":873.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190157","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901137.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901138","title":"Update of configured NSSAI handling","source":"Nokia, Nokia Shanghai Bell\u00a0; Telecom Italia","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An indication from the UE is added to signal to the PLMN that the Requested NSSAI is not based on the Configured NSSAI for the Serving PLMN. Additional misalignments in the text on the conditions triggering the configured NSSAI to be provided to the UE are also fixed.","secretary_remarks":"Revision of S2-1900266. Revised in parallel session to S2-1901254.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11190,"status":"revised","reservation_date":"2019-01-23 02:05:03","uploaded":"2019-01-28 09:47:55","revisionof":"S2-1900266","revisedto":"S2-1901254","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":797.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901138.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901139","title":"Network Slice update clarification","source":"Huawei, Hisillicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that AMF notify the SMF to release the PDU Session can also be due to the change of Allowed NSSAI. Remove the Allowed NSSAI is used for target AMF selection. The AMF informs all non-emergency service associated SMF(s) to release the corresponding PDU Session(s).","secretary_remarks":"Revision of S2-1900443. Revised in parallel session to S2-1901255.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11360,"status":"revised","reservation_date":"2019-01-23 02:05:05","uploaded":"2019-01-28 09:47:55","revisionof":"S2-1900443","revisedto":"S2-1901255","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":933.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901139.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901140","title":"Use of S-NSSAI at interworking from EPS to 5GS","source":"MediaTek Inc., Ericsson, Samsung","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is corrected that the UE shall use S-NSSAI information from PCO if available or if not then from 5GS","secretary_remarks":"Revision of S2-1900497. Agreed in parallel session. This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11390,"status":"agreed","reservation_date":"2019-01-23 02:05:06","uploaded":"2019-01-28 09:47:55","revisionof":"S2-1900497","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":700.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190154","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901140.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901141","title":"UDR Selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The typo in the implementation of CR 594 is corrected in section 6.3.9 (i.e. 'UDR Group ID' is used for UDR selection rather than 'UDM Group ID'). Routing ID term in section 6.2.6 has been replaced by correct term Routing Indicator. The UDR selection function is aligned with the AUSF and UDM selection section.","secretary_remarks":"Revision of S2-1900081. Agreed in parallel session. This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11410,"status":"agreed","reservation_date":"2019-01-23 02:05:09","uploaded":"2019-01-28 09:47:55","revisionof":"S2-1900081","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":741.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190154","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901141.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901142","title":"List of equivalent PLMNs in Registration Accept missing","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The list of equivalent PLMNs attribute is added, it is clarified that when this is present, then the allowed NSSAI in the RA applies to all equivalent PLMNs which have TAs in the RA","secretary_remarks":"Revision of S2-1900282. Agreed in parallel session. This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11440,"status":"agreed","reservation_date":"2019-01-23 02:05:12","uploaded":"2019-01-28 09:47:55","revisionof":"S2-1900282","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":904.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190157","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901142.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901143","title":"Supporting early trace in AUSF","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding Trace Requirements as optional output information provided by UDM to AUSF allowing AUSF to start tracing as soon as it knows the SUPI (i.e. when UDM has translated the SUCI into a SUPI)","secretary_remarks":"Revision of S2-1900255. Agreed in parallel session. This was Block approved. Revised at S2#131 in S2-1901737","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11460,"status":"revised","reservation_date":"2019-01-23 02:05:14","uploaded":"2019-01-28 09:47:55","revisionof":"S2-1900255","revisedto":"S2-1901737","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":791.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901143.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901144","title":"Introduce Charging Function in overall architecture","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the CHF in the non-roaming service based architecture representation and in the roaming Home routed service based architecture representation.","secretary_remarks":"Revision of S2-1900259. Revised in parallel session to S2-1901256.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11480,"status":"revised","reservation_date":"2019-01-23 02:05:16","uploaded":"2019-01-28 09:47:55","revisionof":"S2-1900259","revisedto":"S2-1901256","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":793.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901144.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901145","title":"Correcting references for routing rules configuration","source":"China Telecom","contact":"Jiayifan Liu","contact-id":74811,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the related references from 'TS 23.501 [2] clause 5.8.1.2' to 'TS 23.501 [2] clause 5.8.2.2.2'","secretary_remarks":"Revision of S2-1900541. Agreed in parallel session. This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11510,"status":"agreed","reservation_date":"2019-01-23 02:05:17","uploaded":"2019-01-28 09:47:55","revisionof":"S2-1900541","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":953.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190158","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901145.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901251","title":"Reply LS on S-NSSAI(s) for SMF selection","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG4","secretary_remarks":"Revision of S2-1901133. Agreed in parallel session This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11100,"status":"approved","reservation_date":"2019-01-24 13:07:22","uploaded":"2019-01-29 14:08:24","revisionof":"S2-1901133","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1900003","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901251.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901252","title":"Slice interworking HR mode update","source":"NTT DOCOMO, Ericsson, Nokia, Nokia Shanghai Bell","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Propose to clarify that if a UE does not have serving PLMN configured NSSAI, the UE includes the hPMLN S-NSSAI value received from EPC in the NAS Registration Request or the HPLMN S-NSSAI value received during 5G communication with a previous PLMN. Thus, an AMF can send corresponding VPLMN S-NSSAIs values to the UE and VPLMN Configured NSSAI if required.","secretary_remarks":"Revision of S2-1901134. This CR was agreed","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11160,"status":"agreed","reservation_date":"2019-01-24 13:07:22","uploaded":"2019-01-29 14:08:24","revisionof":"S2-1901134","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":733.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190154","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901252.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901253","title":"Correction to NSSAI logic","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The S-NSSAIs of the Default Configured NSSAI should match subscribed S-NSSAIs. Updated reference to 23.502 procedure for updating the Default Configured NSSAI. The S-NSSAIs of the Default Configured NSSAI is a valid Requested NSSAI.","secretary_remarks":"Revision of S2-1901136. This CR was agreed","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11270,"status":"agreed","reservation_date":"2019-01-24 13:07:23","uploaded":"2019-01-29 14:08:24","revisionof":"S2-1901136","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":756.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190154","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901253.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901254","title":"Update of configured NSSAI handling","source":"Nokia, Nokia Shanghai Bell\u00a0; Telecom Italia","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An indication from the UE is added to signal to the PLMN that the Requested NSSAI is not based on the Configured NSSAI for the Serving PLMN. Additional misalignments in the text on the conditions triggering the configured NSSAI to be provided to the UE are also fixed.","secretary_remarks":"Revision of S2-1901138. Agreed in parallel session. This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11200,"status":"agreed","reservation_date":"2019-01-24 13:07:24","uploaded":"2019-01-29 14:08:25","revisionof":"S2-1901138","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":797.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190155","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901254.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901255","title":"Network Slice update clarification","source":"Huawei, Hisillicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that AMF notify the SMF to release the PDU Session can also be due to the change of Allowed NSSAI. Remove the Allowed NSSAI is used for target AMF selection. The AMF informs all non-emergency service associated SMF(s) to release the corresponding PDU Session(s).","secretary_remarks":"Revision of S2-1901139. Agreed in parallel session. This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11370,"status":"agreed","reservation_date":"2019-01-24 13:07:25","uploaded":"2019-01-29 14:08:25","revisionof":"S2-1901139","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":933.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190158","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901255.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901256","title":"Introduce Charging Function in overall architecture","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the CHF in the non-roaming service based architecture representation and in the roaming Home routed service based architecture representation.","secretary_remarks":"Revision of S2-1901144. Agreed in parallel session. This was Block approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11490,"status":"agreed","reservation_date":"2019-01-24 13:07:26","uploaded":"2019-01-29 14:08:26","revisionof":"S2-1901144","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":793.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190154","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901256.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901384","title":"LS on Configured NSSAI handling","source":"SA WG2","contact":"Alessio Casati","contact-id":68028,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-1901252","secretary_remarks":"Revision of S2-1901135. Revised to S2-1901396.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11220,"status":"revised","reservation_date":"2019-01-25 12:26:14","uploaded":"2019-01-29 14:18:10","revisionof":"S2-1901135","revisedto":"S2-1901396","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901384.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901396","title":"LS on Configured NSSAI handling","source":"SA WG2","contact":"Alessio Casati","contact-id":68028,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-1901252","secretary_remarks":"Revision of S2-1901384. Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11230,"status":"approved","reservation_date":"2019-01-25 12:26:21","uploaded":"2019-01-29 14:18:12","revisionof":"S2-1901384","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901396.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]