[{"name":"S2-1904873","title":"LS from CT WG1: Reply LS on configured NSSAI handling","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 addressing the mobility scenarios, which CT WG1 had not analysed in detail until CT WG1 received the LS. Furthermore, CT WG1 had not considered those mobility scenarios even for the case where the UE possesses configured NSSAI or allowed NSSAI for the target 5GS PLMN. According to the current CT WG1 specification, since CT WG1 has assumed that the S-NSSAI associated with a PDU session is not changed for the lifetime of the PDU session (which is aligned with Table 5.6.1-1 of 3GPP TS 23.501), the following UE and network behaviours apply: - if any of S-NSSAIs included in the requested NSSAI is allowed to the UE, the AMF includes such S-NSSAIs as-is in the allowed NSSAI; - if the UE receives allowed NSSAI not including exactly the same S-NSSAI associated with an existing PDU session, the PDU session is locally released; and - back-off timers, if available, are associated with the S-NSSAI that the UE provided during the PDU session establishment. Taking into account that Rel-15 is frozen, CT WG1 has been discussing solutions with minimized necessary impacts to the NAS protocol. However, CT WG1 could not find a solution satisfying requirements from the stage 2 specification indicated below: - PDU session attribute 'S-NSSAI' cannot be modified later during the lifetime of the PDU session; and - For the registration to a PLMN for which neither a Configured NSSAI applicable to this PLMN or an Allowed NSSAI are present, the S-NSSAIs provided in the Requested NSSAI correspond to the S-NSSAI(s) in the Default Configured NSSAI unless the UE has HPLMN S-NSSAI for established PDU Session(s) in which case the HPLMN S-NSSAI(s) shall be provided in the mapping of Requested NSSAI in the NAS Registration Request message, with no corresponding VPLMN S-NSSAI in the Requested NSSAI. Hence, CT WG1 is requesting SA WG2 to update the stage 2 specification so that it provides stage 2 requirements not conflicting with each other. And since solutions with significant\/non-backward compatible impacts to the frozen release are not desirable, CT WG1 requests SA WG2 to consider a solution targeting Rel-16 if the solution requires significant\/non-backward compatible changes to the NAS protocol. Action: CT WG1 kindly asks SA WG2 to provide feedback to what is described in Section 1.","secretary_remarks":"Response drafted in S2-1904968. Final response in S2-1906758","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10610,"status":"replied to","reservation_date":"2019-04-23 11:45:51","uploaded":"2019-04-23 13:14:44","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-192777","lsreply":"S2-1906758","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904873.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904874","title":"LS from CT WG1: LS on enabling Operator Determined Barring over 5GSM","source":"CT WG1","contact":"Lin Shu","contact-id":43310,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 observed in CT WG4 TS 29.503, Operator Determined Barring (ODB) for Packet Oriented Services (Attribute name: 'odbPacketServices') is an attribute of access and mobility subscription data (see table 6.1.6.2.4-1) rather than an attribute of session management subscription data (see table 6.1.6.2.8-1). Hence, the SMF cannot get the ODB subscription data from the UDM and thereby there is no chance for the SMF to include the 5GSM cause #8 'Operator Determined Barring' in any 5GSM message to the UE. NAS cause value 'Operator Determined Barring' was used over Session Management sublayer in 2G, 3G and EPS with following definition, e.g. in EPS: 'Cause #8 - Operator Determined Barring This ESM cause is used by the network to indicate that the requested service was rejected by the MME due to Operator Determined Barring.' CT WG1 has discussed to use NAS cause value 'Operator Determined Barring' over Mobility Management sublayer in 5GS but it will cause non-backward compatible issue at the UE which CT WG1 want to avoid as far as possible. Some operators in CT WG1 believe for a system consistency and future-proof way, the NAS cause value 'Operator Determined Barring' needs to be used over Session Management sublayer in 5GS as well. Hence, CT WG1 would like to ask CT WG4 to evaluate the following: - feasibility of additionally including the ODB as an attribute of session management subscription data to enable the SMF can include the 5GSM cause #8 'Operator Determined Barring' in a 5GSM message to the UE, - mapping of 5GSM cause #8 to charging events when PDU session needs to be rejected or released, e.g. due to rate plan expiration or low account balance.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10600,"status":"noted","reservation_date":"2019-04-23 11:45:51","uploaded":"2019-04-23 13:14:44","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2","lsoriginalls":"C1-192779","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904874.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904885","title":"LS from RAN WG2: LS on piggybacking of NAS PDUs","source":"RAN WG2","contact":"Mattias Bergstrom","contact-id":46046,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has discussed piggybacking of NAS PDUs to RRCReconfigurations in NR. RAN WG2 RRC message processing is based on joint success\/failure. That is, any piggybacked NAS messages is delivered to NAS in the UE if and only if the RRC message processing is successful. This implies that only NAS messages that are required to be delivered to NAS when DRB is set up are piggybacked, but not other messages as they can be lost if RRC procedure for DRB set up procedure fails. In NR RRC there is the following sentence regarding this: In downlink piggybacking of NAS messages is used only for bearer establishment\/modification\/release. RAN WG2 intends to clarify the above sentence to: In downlink, piggybacking of NAS messages is used only for one dependent (i.e. with joint success\/ failure) procedure: bearer establishment\/ modification\/ release. RAN WG2 requests CT WG1, CT WG4, SA WG2 and RAN WG3 to comment on RAN WG2's understanding and whether there are any concerns with the suggested rewording. Action: RAN WG2 requests CT WG1, CT WG4, SA WG2 and RAN WG3 to comment on RAN WG2's understanding and whether there are any concerns with the suggested rewording.","secretary_remarks":"Response drafted in S2-1905035. Final response in S2-1906597","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10660,"status":"replied to","reservation_date":"2019-04-23 11:45:51","uploaded":"2019-04-23 13:14:44","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4, SA WG2, RAN WG3","Cc":"","lsoriginalls":"R2-1905441","lsreply":"S2-1906597","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904885.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904894","title":"LS from RAN WG3: LS on piggy-backing of NAS PDUs in NGAP messages","source":"RAN WG3","contact":"Philippe Godin","contact-id":68843,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 has discussed the end to end requirement of in-order delivery for NAS PDUs and how it can impact NGAP when different types of NAS PDUs are included in e.g. an NGAP Initial Context Setup Request message. RAN WG3 especially discussed in the context of CT WG1 CR in C1-186969 the case where a NAS Service Accept and a NAS PDU Session Setup are piggy-backed into the NGAP Initial Context Setup. In order to evaluate any potential interoperability issue for the above case RAN WG3 would need to get answers on the following questions: Question 1: if UE sends NAS service Request, can it send a following PDU session request before receiving the NAS Service Accept? Question 2: if the NAS Service Accept is sent in a first RRC message, if a second RRC message carrying the NAS PDU Session Request is an RRC reconfiguration which fails completely, is it a problem for the UE which has received the NAS Service Accept in the first RRC message; but has not received the NAS PDU Session Request?","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10670,"status":"noted","reservation_date":"2019-04-23 11:45:51","uploaded":"2019-04-23 13:14:44","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"RAN WG2, SA WG2","lsoriginalls":"R3-192158","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904894.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904968","title":"[DRAFT] Reply LS on configured NSSAI handling","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":82456,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1.","secretary_remarks":"Response to S2-1904873. Revised in parallel session to S2-1906596.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10620,"status":"revised","reservation_date":"2019-05-03 09:05:34","uploaded":"2019-05-03 11:36:43","revisionof":"","revisedto":"S2-1906596","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904968.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904971","title":"Applicability of Allowed NSSAI to PLMNs whose TAIs are in the RA TAI list","source":"Nokia, Nokia Shanghai Bell, Ericsson,OPPO\u00a0?, Qualcomm Incorporated (?)","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the UE stores the Allowed NSSAI and its mapping to HPLMN S-NSSAI values for a PLMN when at least a TAI of the PLMN is included in the RA\/TAI list received in the registration accept or UE configuration Update command messages where the allowed NSSAI is provided.","secretary_remarks":"Confirm sources!. Revised in parallel session to S2-1906600.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10700,"status":"revised","reservation_date":"2019-05-03 09:18:32","uploaded":"2019-05-03 11:36:43","revisionof":"","revisedto":"S2-1906600, S2-1906601","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1288.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904971.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904972","title":"Clarification on S-NSSAI(s) for PDU session","source":"Nokia, Nokia Shanghai Bell; Telecom Italia, ZTE, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The Table has been updated to avoid the wrong interpetation by CT WGs that VPLMN S-NSSAI only is the one associated to the PDU session so the PDU session needs to be torn down upon PLMN change. The UE signals the HPLMN S-NSSAI and if applicable the VPLMN S-NSSAI in SM signalling and it is clarified the AMF selects the SMF based on the V-PLMN S-NSSAI. Text implying Slicing is optional is removed.","secretary_remarks":"Revised in parallel session to S2-1906602.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10790,"status":"revised","reservation_date":"2019-05-03 09:37:22","uploaded":"2019-05-03 11:36:43","revisionof":"","revisedto":"S2-1906602","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1289.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904972.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904973","title":"Clarification on S-NSSAI for PDU session in Requested NSSAI","source":"Nokia, Nokia Shanghai Bell; Telecom Italia, ZTE, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified the text to say the H-PLMN value must be present and remain the same in the Mapping information of Requested NSSAI but not the Serving PLMN value (which in inter-PLMN case changes most luikley with or without Network slicing configuration available in the UE for the target PLMN).","secretary_remarks":"Revised in parallel session to S2-1906603.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10840,"status":"revised","reservation_date":"2019-05-03 10:08:01","uploaded":"2019-05-03 11:36:43","revisionof":"","revisedto":"S2-1906603","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1290.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904973.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904974","title":"Clarification on S-NSSAI for PDU session","source":"Nokia, Nokia Shanghai Bell;Telecom Italia, ZTE, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: which S-NSSAI is used in SM messages (serving, visited, or home PLMN) is clarified","secretary_remarks":"Revised in parallel session to S2-1906604.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10880,"status":"revised","reservation_date":"2019-05-03 10:13:05","uploaded":"2019-05-03 11:36:43","revisionof":"","revisedto":"S2-1906604","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1314.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904974.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905035","title":"[DRAFT] Reply LS on piggybacking of NAS PDUs","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 reply to the question related to the changed wording of the sentence regarding downlink piggybacking of NAS messages","secretary_remarks":"Response to S2-1904885. Revised in parallel session to S2-1906597.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10680,"status":"revised","reservation_date":"2019-05-03 21:54:25","uploaded":"2019-05-07 04:32:04","revisionof":"","revisedto":"S2-1906597","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1, CT WG4, RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905035.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905036","title":"Usage of Network Slices valid in certain areas","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that the mapping information can also be used when Serving PLMN is HPLMN.","secretary_remarks":"Revised in parallel session to S2-1906605.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10920,"status":"revised","reservation_date":"2019-05-03 21:54:25","uploaded":"2019-05-07 13:27:50","revisionof":"","revisedto":"S2-1906605","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1302.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905036.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905037","title":"Alignment of Network Slice selection logic","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligns the wording and clarifies the logic for when S-NSSAI(s) marked as default in the Subscribed S-NSSAIs are used.","secretary_remarks":"Revised in parallel session to S2-1906694.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10940,"status":"revised","reservation_date":"2019-05-03 21:54:26","uploaded":"2019-05-07 13:27:50","revisionof":"","revisedto":"S2-1906694","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1303.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905037.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905207","title":"On inclusion of HPLMN S-NSSAIs only","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"discussion","for":"Agreement","abstract":"Companion document to corresponding Rel-15 CR in CT WG1. This discussion paper only summarizes the proposal in CT WG1 as a alternative to the competing proposal to introduce SST=0 as 'unknown SST' in Stage 2.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10960,"status":"noted","reservation_date":"2019-05-06 11:42:17","uploaded":"2019-05-07 11:14:27","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905207.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905304","title":"Correcting factors to consider for PCF selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding factors to consider when selecting AM and UE policies, and correcting factors to consider when selecting PCF for PDU session policies","secretary_remarks":"Revision of S2-1904491 from S2#132. Revised in parallel session to S2-1906606.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10990,"status":"revised","reservation_date":"2019-05-06 15:38:57","uploaded":"2019-05-07 13:30:29","revisionof":"S2-1904491","revisedto":"S2-1906606","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1041.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905304.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905323","title":"Conclusions on applicability of Allowed NSSAI to E-PLMNs","source":"OPPO, Qualcomm Incorporated, Ericsson","contact":"ChenHo CHIN","contact-id":80545,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the UE may create the Requested NSSAI in a PLMN using the Allowed NSSAI obtained in another PLMN that is an equivalent PLMN.","secretary_remarks":"Revision of S2-1904826 from S2#132. Merged into S2-1906690","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10770,"status":"merged","reservation_date":"2019-05-06 17:09:07","uploaded":"2019-05-07 08:20:00","revisionof":"S2-1904826","revisedto":"S2-1906599","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1031.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905323.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905324","title":"Conclusions on applicability of Allowed NSSAI to E-PLMNs","source":"OPPO, Qualcomm Incorporated, Ericsson","contact":"ChenHo CHIN","contact-id":80545,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: It is clarified that the UE may create the Requested NSSAI in a PLMN using the Allowed NSSAI obtained in another PLMN that is an equivalent PLMN.","secretary_remarks":"Revision of S2-1904827 from S2#132. Merged into S2-1906689","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10750,"status":"merged","reservation_date":"2019-05-06 17:09:08","uploaded":"2019-05-07 08:20:00","revisionof":"S2-1904827","revisedto":"S2-1906598","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1131.0,"crrevision":4.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905324.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905550","title":"Correcting factors to consider for PCF selection","source":"Huawei, Ericsson?","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding factors to consider when selecting AM and UE policies, and correcting factors to consider when selecting PCF for PDU session policies","secretary_remarks":"Not Handled","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11020,"status":"not treated","reservation_date":"2019-05-07 09:40:04","uploaded":"2019-05-07 14:31:33","revisionof":"S2-1904491","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1041.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905550.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905551","title":"Correcting factors to consider for PCF selection","source":"Huawei, Ericsson?","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Adding factors to consider when selecting AM and UE policies, and correcting factors to consider when selecting PCF for PDU session policies","secretary_remarks":"Revision of S2-1904798 from S2#132. Confirm Sources!. Revised in parallel session to S2-1906607.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11030,"status":"revised","reservation_date":"2019-05-07 09:40:05","uploaded":"2019-05-07 14:31:33","revisionof":"S2-1904798","revisedto":"S2-1906607","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1042.0,"crrevision":3.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905551.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905743","title":"Ability to only indicate HPLMN S-NSSAI values","source":"Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The standardized SST table is extended with using value 0 for unknown SST.","secretary_remarks":"Not Handled","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10970,"status":"not treated","reservation_date":"2019-05-07 11:32:47","uploaded":"2019-05-07 14:11:42","revisionof":"S2-1901570","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":928.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905743.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905744","title":"Ability to only indicate HPLMN S-NSSAI values","source":"Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: The standardized SST table is extended with using value 0 for unknown SST.","secretary_remarks":"Not Handled","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10980,"status":"not treated","reservation_date":"2019-05-07 11:32:49","uploaded":"2019-05-07 14:11:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1442.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905744.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906596","title":"[DRAFT] Reply LS on configured NSSAI handling","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":82456,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1.","secretary_remarks":"Revision of S2-1904968.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":13180,"status":"revised","reservation_date":"2019-05-15 17:20:01","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1904968","revisedto":"S2-1906697","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906596.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906597","title":"[DRAFT] Reply LS on piggybacking of NAS PDUs","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 reply to the question related to the changed wording of the sentence regarding downlink piggybacking of NAS messages","secretary_remarks":"Revision of S2-1905035. Agreed in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":13220,"status":"available","reservation_date":"2019-05-15 17:20:01","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905035","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1, CT WG4, RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906597.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906598","title":"Conclusions on applicability of Allowed NSSAI to E-PLMNs","source":"OPPO, Qualcomm Incorporated, Ericsson","contact":"ChenHo CHIN","contact-id":80545,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: It is clarified that the UE may create the Requested NSSAI in a PLMN using the Allowed NSSAI obtained in another PLMN that is an equivalent PLMN.","secretary_remarks":"Revision of S2-1905324.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":13270,"status":"reserved","reservation_date":"2019-05-15 17:20:01","uploaded":null,"revisionof":"S2-1905324","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1131.0,"crrevision":5.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906599","title":"Conclusions on applicability of Allowed NSSAI to E-PLMNs","source":"OPPO, Qualcomm Incorporated, Ericsson","contact":"ChenHo CHIN","contact-id":80545,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the UE may create the Requested NSSAI in a PLMN using the Allowed NSSAI obtained in another PLMN that is an equivalent PLMN.","secretary_remarks":"Revision of S2-1905323.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":13290,"status":"reserved","reservation_date":"2019-05-15 17:20:02","uploaded":null,"revisionof":"S2-1905323","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1031.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906600","title":"Applicability of Allowed NSSAI to PLMNs whose TAIs are in the RA TAI list","source":"Nokia, Nokia Shanghai Bell, Ericsson, OPPO, Qualcomm Incorporated","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the UE stores the Allowed NSSAI and its mapping to HPLMN S-NSSAI values for a PLMN when at least a TAI of the PLMN is included in the RA\/TAI list received in the registration accept or UE configuration Update command messages where the allowed NSSAI is provided.","secretary_remarks":"Revision of S2-1904971.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":13240,"status":"revised","reservation_date":"2019-05-15 17:20:03","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1904971","revisedto":"S2-1906689","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1288.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906600.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906601","title":"Applicability of Allowed NSSAI to PLMNs whose TAIs are in the RA TAI list","source":"Nokia, Nokia Shanghai Bell, Ericsson, OPPO, Qualcomm Incorporated","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Rel 16 mirror CR: Summary of change: It is clarified that the UE stores the Allowed NSSAI and its mapping to HPLMN S-NSSAI values for a PLMN when at least a TAI of the PLMN is included in the RA\/TAI list received in the registration accept or UE configuration Update command messages where the allowed NSSAI is provided.","secretary_remarks":"Mirror CR created in parallel session.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":13250,"status":"revised","reservation_date":"2019-05-15 17:20:04","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1904971","revisedto":"S2-1906690","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1449.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906601.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906602","title":"Clarification on S-NSSAI(s) for PDU session","source":"Nokia, Nokia Shanghai Bell; Telecom Italia, ZTE, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The Table has been updated to avoid the wrong interpetation by CT WGs that VPLMN S-NSSAI only is the one associated to the PDU session so the PDU session needs to be torn down upon PLMN change. The UE signals the HPLMN S-NSSAI and if applicable the VPLMN S-NSSAI in SM signalling and it is clarified the AMF selects the SMF based on the V-PLMN S-NSSAI. Text implying Slicing is optional is removed.","secretary_remarks":"Revision of S2-1904972.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":13310,"status":"revised","reservation_date":"2019-05-15 17:20:07","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1904972","revisedto":"S2-1906691","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1289.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906602.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906603","title":"Clarification on S-NSSAI for PDU session in Requested NSSAI","source":"Nokia, Nokia Shanghai Bell; Telecom Italia, ZTE, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified the text to say the H-PLMN value must be present and remain the same in the Mapping information of Requested NSSAI but not the Serving PLMN value (which in inter-PLMN case changes most luikley with or without Network slicing configuration available in the UE for the target PLMN).","secretary_remarks":"Revision of S2-1904973.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":13330,"status":"revised","reservation_date":"2019-05-15 17:20:07","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1904973","revisedto":"S2-1906692","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1290.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906603.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906604","title":"Clarification on S-NSSAI for PDU session","source":"Nokia, Nokia Shanghai Bell;Telecom Italia, ZTE, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: which S-NSSAI is used in SM messages (serving, visited, or home PLMN) is clarified","secretary_remarks":"Revision of S2-1904974.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":13350,"status":"revised","reservation_date":"2019-05-15 17:20:09","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1904974","revisedto":"S2-1906693","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1314.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906604.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906605","title":"Usage of Network Slices valid in certain areas","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that the mapping information can also be used when Serving PLMN is HPLMN.","secretary_remarks":"Revision of S2-1905036.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":13370,"status":"available","reservation_date":"2019-05-15 17:20:10","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905036","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1302.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906605.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906606","title":"Correcting factors to consider for PCF selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding factors to consider when selecting AM and UE policies, and correcting factors to consider when selecting PCF for PDU session policies","secretary_remarks":"Revision of S2-1905304.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":13430,"status":"revised","reservation_date":"2019-05-15 17:20:11","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905304","revisedto":"S2-1906695","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1041.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906606.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906607","title":"Correcting factors to consider for PCF selection","source":"Huawei, Ericsson?","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Adding factors to consider when selecting AM and UE policies, and correcting factors to consider when selecting PCF for PDU session policies","secretary_remarks":"Revision of S2-1905551.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":13460,"status":"revised","reservation_date":"2019-05-15 17:20:12","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905551","revisedto":"S2-1906696","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1042.0,"crrevision":4.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906607.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906632","title":"Clarification on S-NSSAI(s) for PDU session","source":"Nokia, Nokia Shanghai Bell; Telecom Italia, ZTE, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: The Table has been updated to avoid the wrong interpetation by CT WGs that VPLMN S-NSSAI only is the one associated to the PDU session so the PDU session needs to be torn down upon PLMN change. The UE signals the HPLMN S-NSSAI and if applicable the VPLMN S-NSSAI in SM signalling and it is clarified the AMF selects the SMF based on the V-PLMN S-NSSAI. Text implying Slicing is optional is removed.","secretary_remarks":"Mirror CR created at meeting. Agreed in parallel session. Qualcomm registered an objection to this CR. Agreed with objection","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10830,"status":"agreed","reservation_date":"2019-05-16 18:41:21","uploaded":"2019-05-19 20:07:55","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1450.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-190397","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906632.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906633","title":"Clarification on S-NSSAI for PDU session in Requested NSSAI","source":"Nokia, Nokia Shanghai Bell; Telecom Italia, ZTE, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Clarified the text to say the HPLMN value must be present and remain the same in the Mapping information of Requested NSSAI but not the Serving PLMN value (which in inter-PLMN case changes most luikley with or without Network slicing configuration available in the UE for the target PLMN).","secretary_remarks":"Mirror CR created at meeting. Agreed in parallel session. This was Block approved","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10870,"status":"agreed","reservation_date":"2019-05-16 18:41:23","uploaded":"2019-05-19 20:07:55","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1451.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906633.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906634","title":"Clarification on S-NSSAI for PDU session","source":"Nokia, Nokia Shanghai Bell;Telecom Italia, ZTE, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: which S-NSSAI is used in SM messages (serving, visited, or home PLMN) is clarified","secretary_remarks":"Mirror CR created at meeting. Agreed in parallel session. This was Block approved","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10910,"status":"agreed","reservation_date":"2019-05-16 18:41:25","uploaded":"2019-05-19 20:07:55","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1456.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-190402","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906634.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906689","title":"Applicability of Allowed NSSAI to PLMNs whose TAIs are in the RA TAI list","source":"Nokia, Nokia Shanghai Bell, Ericsson, OPPO, Qualcomm Inc.","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the UE stores the Allowed NSSAI and its mapping to HPLMN S-NSSAI values for a PLMN when at least a TAI of the PLMN is included in the RA\/TAI list received in the registration accept or UE configuration Update command messages where the allowed NSSAI is provided.","secretary_remarks":"Revision of S2-1906600, merging S2-1905324. Agreed in parallel session. This was Block approved","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10720,"status":"agreed","reservation_date":"2019-05-17 02:43:18","uploaded":"2019-05-19 20:07:56","revisionof":"S2-1906600","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1288.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906689.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906690","title":"Applicability of Allowed NSSAI to PLMNs whose TAIs are in the RA TAI list","source":"Nokia, Nokia Shanghai Bell, Ericsson,OPPO, Qualcomm Inc.","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: It is clarified that the UE stores the Allowed NSSAI and its mapping to HPLMN S-NSSAI values for a PLMN when at least a TAI of the PLMN is included in the RA\/TAI list received in the registration accept or UE configuration Update command messages where the allowed NSSAI is provided.","secretary_remarks":"Revision of S2-1906601, merging S2-1905323. Agreed in parallel session. This was Block approved","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10740,"status":"agreed","reservation_date":"2019-05-17 02:43:19","uploaded":"2019-05-19 20:07:56","revisionof":"S2-1906601","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1449.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906690.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906691","title":"Clarification on S-NSSAI(s) for PDU session","source":"Nokia, Nokia Shanghai Bell; Telecom Italia, ZTE, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The Table has been updated to avoid the wrong interpetation by CT WGs that VPLMN S-NSSAI only is the one associated to the PDU session so the PDU session needs to be torn down upon PLMN change. The UE signals the HPLMN S-NSSAI and if applicable the VPLMN S-NSSAI in SM signalling and it is clarified the AMF selects the SMF based on the V-PLMN S-NSSAI. Text implying Slicing is optional is removed.","secretary_remarks":"Revision of S2-1906602.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12140,"status":"revised","reservation_date":"2019-05-17 02:43:21","uploaded":"2019-05-19 20:07:56","revisionof":"S2-1906602","revisedto":"S2-1906759","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1289.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906691.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906692","title":"Clarification on S-NSSAI for PDU session in Requested NSSAI","source":"Nokia, Nokia Shanghai Bell; Telecom Italia, ZTE, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified the text to say the HPLMN value must be present and remain the same in the Mapping information of Requested NSSAI but not the Serving PLMN value (which in inter-PLMN case changes most luikley with or without Network slicing configuration available in the UE for the target PLMN).","secretary_remarks":"Revision of S2-1906603. Agreed in parallel session. This was Block approved","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10860,"status":"agreed","reservation_date":"2019-05-17 02:43:22","uploaded":"2019-05-19 20:07:56","revisionof":"S2-1906603","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1290.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906692.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906693","title":"Clarification on S-NSSAI for PDU session","source":"Nokia, Nokia Shanghai Bell;Telecom Italia, ZTE, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: which S-NSSAI is used in SM messages (serving, visited, or home PLMN) is clarified","secretary_remarks":"Revision of S2-1906604. Agreed in parallel session. This was Block approved","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10900,"status":"agreed","reservation_date":"2019-05-17 02:43:23","uploaded":"2019-05-19 20:07:56","revisionof":"S2-1906604","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1314.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190401","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906693.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906694","title":"Alignment of Network Slice selection logic","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligns the wording and clarifies the logic for when S-NSSAI(s) marked as default in the Subscribed S-NSSAIs are used.","secretary_remarks":"Revision of S2-1905037. Agreed in parallel session. This was Block approved","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10950,"status":"agreed","reservation_date":"2019-05-17 02:43:25","uploaded":"2019-05-19 20:07:56","revisionof":"S2-1905037","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1303.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906694.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906695","title":"Correcting factors to consider for PCF selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding factors to consider when selecting AM and UE policies, and correcting factors to consider when selecting PCF for PDU session policies","secretary_remarks":"Revision of S2-1906606. Agreed in parallel session. This was Block approved","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11010,"status":"agreed","reservation_date":"2019-05-17 02:43:26","uploaded":"2019-05-19 20:07:56","revisionof":"S2-1906606","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1041.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906695.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906696","title":"Correcting factors to consider for PCF selection","source":"Ericsson, Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Adding factors to consider when selecting AM and UE policies, and correcting factors to consider when selecting PCF for PDU session policies","secretary_remarks":"Revision of S2-1906607. Agreed in parallel session. This was Block approved","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11050,"status":"agreed","reservation_date":"2019-05-17 02:43:27","uploaded":"2019-05-19 20:07:56","revisionof":"S2-1906607","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1042.0,"crrevision":5.0,"crcategory":"A","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906696.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906697","title":"[DRAFT] Reply LS on configured NSSAI handling","source":"SA WG2","contact":"Alessio Casati","contact-id":82456,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1.","secretary_remarks":"Revision of S2-1906596.","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11980,"status":"revised","reservation_date":"2019-05-17 02:43:28","uploaded":"2019-05-19 20:07:56","revisionof":"S2-1906596","revisedto":"S2-1906758","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906697.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906758","title":"Reply LS on configured NSSAI handling","source":"SA WG2","contact":"Alessio Casati","contact-id":82456,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-1906759, S2-196692, S2-1906693","secretary_remarks":"Revision of S2-1906697. Agreed in parallel session. This was Block approved","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10650,"status":"approved","reservation_date":"2019-05-19 19:38:52","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906697","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1904873","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906758.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906759","title":"Clarification on S-NSSAI(s) for PDU session","source":"Nokia, Nokia Shanghai Bell; Telecom Italia, ZTE, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The Table has been updated to avoid the wrong interpetation by CT WGs that VPLMN S-NSSAI only is the one associated to the PDU session so the PDU session needs to be torn down upon PLMN change. The UE signals the HPLMN S-NSSAI and if applicable the VPLMN S-NSSAI in SM signalling and it is clarified the AMF selects the SMF based on the V-PLMN S-NSSAI. Text implying Slicing is optional is removed.","secretary_remarks":"Revision of S2-1906691. Agreed in parallel session. Qualcomm registered an objection to this CR. Agreed with objection","agenda_item_sort_order":19,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10820,"status":"agreed","reservation_date":"2019-05-19 19:38:52","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906691","revisedto":"SP-190492","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1289.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190397","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906759.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]