[{"name":"S2-1811608","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-1810014 from S2#129. Postponed","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10580,"status":"postponed","reservation_date":"2018-10-31 19:40:32","uploaded":"2018-11-21 06:04:14","revisionof":"S2-1810014","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C1-185792","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811608.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811619","title":"LS from RAN WG2: Reply LS on initial NAS security agreements","source":"RAN WG2","contact":"Masato Kitazoe","contact-id":29801,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 would like to thank SA WG3 on their LS on initial NAS security agreements. RAN WG2 noticed SA WG3 stated that 'SA WG3 interpret the guidance given by SA plenary means that RAN specifications shall only include S-NSSAI ciphered in RRC layer'. RAN WG2 would like to inform SA WG3 that in the current RRC specifications, the list of S-NSSAIs can only be sent in RRCConnectionSetupComplete (LTE\/5GC) and RRCSetupComplete (NR), i.e. 'Msg5' during RRC connection establishment procedure, without any encryption. It should be noted that the list of S-NSSAI is included in the above messages only if upper layer provides the information to RRC. RAN WG2 also would like to point out that release-15 specification is frozen and backwards incompatible change cannot be made any more.","secretary_remarks":"Postponed S2-1811224 from S2#129. Postponed","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10800,"status":"postponed","reservation_date":"2018-10-31 19:40:32","uploaded":"2018-11-21 06:04:14","revisionof":"S2-1811224","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2, CT WG1, RAN WG3, TSG SA","lsoriginalls":"R2-1816022","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811619.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811629","title":"LS from RAN WG2: LS on agreements regarding UE behaviour in RRC_INACTIVE while going out-of-service","source":"RAN WG2","contact":"Alexander Sayenko","contact-id":47308,"tdoctype":"LS in","for":"Information","abstract":"In this LS RAN WG2 would like to inform about the following agreements made concerning UE behaviour while going out-of-service: Agreements 1 If the UE enters 'Any cell selection' the UE remains in RRC_INACTIVE 2 If the UE camps on an acceptable cell (i.e. 'Camped on any cell' state) the UE remains in RRC_INACTIVE, and then goes to IDLE when RNAU update timer expires or until the UE NAS initiates signalling.","secretary_remarks":"Postponed S2-1811229 from S2#129. Noted in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10540,"status":"noted","reservation_date":"2018-11-10 08:27:14","uploaded":"2018-11-21 06:04:48","revisionof":"S2-1811229","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"R2-1816058","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811629.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811663","title":"LS from CT WG1: Reply LS on establishment causes","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"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","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10560,"status":"postponed","reservation_date":"2018-11-16 07:43:03","uploaded":"2018-11-21 06:07:13","revisionof":"","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_129BIS_West_Palm_Beach\/Docs\/S2-1811663.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811677","title":"LS from RAN WG3: Reply LS on RRC cause in RRC reestablishment fallback","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"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","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10570,"status":"postponed","reservation_date":"2018-11-16 07:43:04","uploaded":"2018-11-21 06:07:13","revisionof":"","revisedto":"","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_129BIS_West_Palm_Beach\/Docs\/S2-1811677.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811853","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: 5GS S-NSSAI to take precedence over any corresponding S-NSSAI received from EPS i.e. when in 5GS UE preferably follows 5GS-defined behavior","secretary_remarks":"Revised in parallel session to S2-1813020.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10660,"status":"revised","reservation_date":"2018-11-19 09:47:04","uploaded":"2018-11-20 14:03:11","revisionof":"","revisedto":"S2-1813020","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":700.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811853.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811913","title":"Excluding sensitive information to be sent in clear","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that Requested NSSAI is not sent in clear i.e. UE first checks if the Requested can be sent protected, and if that is the case, then any conditions when the Requested NSSAI is to be sent applies. When the Requested NSSAI is not provided and the GUAMI is not provided or not routeable, then the AMF selection will be performed via a default AMF. Rev3: Impacts changed from RAN to ME, and minor clarification in added note.","secretary_remarks":"Revision of S2-1811403 from S2-129. Noted in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10900,"status":"noted","reservation_date":"2018-11-19 12:17:21","uploaded":"2018-11-20 13:43:50","revisionof":"S2-1811403","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":643.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811913.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811914","title":"Excluding sensitive information to be sent in clear","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that Requested NSSAI is not sent in clear i.e. UE first checks if the Requested can be sent protected, and if that is the case, then any conditions when the Requested NSSAI is to be sent applies. The AMF selection will then be performed via a default AMF, and RAN policy handling for slices will be based on Allowed NSSAI and S-NSSAIs sent by 5GC to 5G-AN. Rev2 is updated to remove aspects of protection of NAS information as covered by other CR.","secretary_remarks":"Revision of S2-1811310 from S2-129. Noted in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10910,"status":"noted","reservation_date":"2018-11-19 12:17:23","uploaded":"2018-11-20 13:43:50","revisionof":"S2-1811310","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":748.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811914.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811923","title":"EPS to 5GS with network slices","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Let the PGW-C+ SMF at PDN Connection establishment only allocate hS-NSSAI or vS-NSSAI (via mapped hS-NSSAI) that is allowed, according to the UEs subscribed S-NSSAIs.","secretary_remarks":"Revised in parallel session to S2-1813018.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10600,"status":"revised","reservation_date":"2018-11-19 12:17:30","uploaded":"2018-11-20 13:43:50","revisionof":"","revisedto":"S2-1813018","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":709.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811923.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811924","title":"EPS to 5GS with network slices","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Make the Nudm_SDM_Get (SUPI, Slice Selection Subscription data) service available also by SMF. Make the Nnssf_NSSelection_Get service available also by PGW-C+SMF. Make it possible to use subscribed S-NSSAIs as input\/output instead of 'S-NSSAIs for the HPLMN associated with established PDN connection'.","secretary_remarks":"Revised in parallel session to S2-1813019.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10630,"status":"revised","reservation_date":"2018-11-19 12:17:31","uploaded":"2018-11-20 13:43:50","revisionof":"","revisedto":"S2-1813019","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":824.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811924.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811975","title":"LS from GSMA: Cooperation on Generic Slice Template definition","source":"GSMA","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"The GSMA 5G Joint Activity would like to draw your attention to the document that defines and provides a description of the Generic Slice Template (GST). The GST is a set of attributes (e.g. supported throughput, supported functionality, provided application programming interfaces (APIs), etc.) that characterize any slice. It contains the attribute names, definitions and units. These attributes can be used by vendors, mobile network operators and slice customers, in addition to other proprietary attributes, if custom slices are desired. By filling the GST with values for all or a subset of the attributes it is possible to describe the structure of a network slice. A GST filled with values is called Network Slice Type (NEST). A NEST serves many purposes: - Vendors can use a NEST to define the features of their products - Vertical Industry customers (slice customers) can use a NEST as a reference to understand the contractual agreements with the network operator - Network operators (slice providers) can use a NEST with their roaming partners, facilitating the definition More details regarding to GST and NEST could be found at: https:\/\/www.gsma.com\/futurenetworks\/5g\/5g-network-slicing-report-august-2018\/ and in the document attached that will be taken as the baseline for a GSMA Permanent Reference Document expected to be published next year. GSMA intends to continue working in the following areas and would welcome a close cooperation with your organisation: - Generating a non-binding Permanent Reference Document (PRD) Note 1 containing the description of the GST. - Producing NEST(s) for the 3GPP defined standard slices (eMBB, URLLC, MIoT) - Producing NEST(s) for customised network slices, e.g. automotive Note: Non-Binding Permanent Reference Document (PRD) is an informational guidance and recommendations from and to members and, in some cases, to the wider industry. Actions: GSMA 5GJA would like to invite SA WG6 to review the GST attributes set and assess if they are sufficient to define a network slice type addressing public safety and railway use cases and requirements. If SA WG6 believes it is necessary to add attributes to the GST, then GSMA 5GJA endeavours to include them in the next update of the GST. Moreover, GSMA 5GJA would like to invite SA WG6 to propose values for the GST attributes so that the NEST can serve public safety use cases.","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":10550,"status":"noted","reservation_date":"2018-11-19 15:28:58","uploaded":"2018-11-21 06:07:59","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"TSG SA, SA WG1, SA WG2, SA WG3, RAN WG3, SA WG5","lsoriginalls":"5GJA05_110","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811975.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811984","title":"LS from SA WG5: _x0005_LS on the slicing terminology and the role of S-NSSAI parameter","source":"SA WG5","contact":"Maurice Pope","contact-id":648,"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","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10590,"status":"postponed","reservation_date":"2018-11-19 15:28:59","uploaded":"2018-11-21 06:07:59","revisionof":"","revisedto":"","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_129BIS_West_Palm_Beach\/Docs\/S2-1811984.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811998","title":"Options for applying the restrictions of Mutual Exclusive Access to Network Slices in Rel-15","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the NOTE according to the possible options.","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":10680,"status":"noted","reservation_date":"2018-11-19 17:10:50","uploaded":"2018-11-20 13:43:50","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":714.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811998.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812001","title":"Handling of equivalent PLMNs in slicing","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":68028,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discussed how to optimise handling of UEs using equivalent PLMNs","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":10690,"status":"noted","reservation_date":"2018-11-19 17:41:19","uploaded":"2018-11-20 13:18:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812001.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812003","title":"EPLMNs support in network slicing","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: a new clause is added in slicing clause 5.15.x describing how to support network slicing if equivalent PLMNs are used in the serving PLMN. Some changes are introduced to the reguistration to a set of network slicing to correct the issues in the reason for change.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10700,"status":"not treated","reservation_date":"2018-11-19 17:49:03","uploaded":"2018-11-20 13:18:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":715.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812003.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812006","title":"EPLMN list indication and network slicing","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: the UCU and registration procedures are updated to indicate to the Ue the EPLMNs use same network configuration.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10710,"status":"not treated","reservation_date":"2018-11-19 17:58:17","uploaded":"2018-11-20 13:18:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":829.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812006.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812009","title":"Network controlled NSSAI for SR-related Access Stratum connection establishment","source":"Nokia, Nokia Shanghai Bell, NEC, Telecom Italia, Huawei, InterDigital, AT&T, Verizon, Sprint, Orange, Qualcomm Inc","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A PLMN can instruct the UE on which behaviour to adopt when triggering a Service Request procedure, by including Access Stratum Connection Establishment NSSAI Inclusion Mode information in a Registration Accept Message that instructs the UE to: 1.- Include in Access Stratum Connection Establishment a NSSAI = Allowed NSSAI for the UE, or 2. Include in Access Stratum Connection Establishment only the S-NSSAIs of the Network Slices that trigger the RRC Connection Establishment, or 3. Include no NSSAI for Service Request and Registration Request not due to mobility or initial access. 4. Never include any NSSAI in RRC regardless of the procedure . The default UE behaviour is 4. Any other behaviour can be requested by the serving PLMN ONLY if the HPLMN allows by sending explicit indication from the UDM as part of the subscription data .","secretary_remarks":"Revised in parallel session to S2-1813024.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10820,"status":"revised","reservation_date":"2018-11-19 18:03:12","uploaded":"2018-11-20 13:18:53","revisionof":"S2-1811565","revisedto":"S2-1813024","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":656.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812009.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812010","title":"Network controlled NSSAI for SR-related Access Stratum connection establishment","source":"Nokia, Nokia Shanghai Bell, Telecom Italia, NEC, HUAWEI, InterDigital, AT&T, Verizon, Sprint, Orange, Qualcomm Inc.","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Registration procedure is updated to include the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter. The UDM indicates to the AMF it it allows the Serving AMF to indicate modes a,b,c in the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter.","secretary_remarks":"Revised in parallel session to S2-1813025.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10870,"status":"revised","reservation_date":"2018-11-19 18:05:06","uploaded":"2018-11-20 13:18:53","revisionof":"S2-1810392","revisedto":"S2-1813025","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":767.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812010.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812055","title":"Clarification on rejected S-NSSAIs and cause in Registration and UCU procedure","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add missing information in Registration Accep and UCU Command for rejected S-NSSAIs.","secretary_remarks":"Revised in parallel session to S2-1813021.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10720,"status":"revised","reservation_date":"2018-11-20 00:40:47","uploaded":"2018-11-20 06:04:56","revisionof":"","revisedto":"S2-1813021","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":832.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812055.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812142","title":"Clarification on Registration with AMF re-allocation","source":"Huawei, Hisillicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a NOTE to clarify that if the NSSF respond a list of candidate AMF, the initial AMF shall not reroute the NAS message to the target AMF via (R)AN.","secretary_remarks":"Revised in parallel session to S2-1813022.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10740,"status":"revised","reservation_date":"2018-11-20 06:25:18","uploaded":"2018-11-20 14:57:01","revisionof":"","revisedto":"S2-1813022","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":719.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812142.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812143","title":"Clarification on Registration with AMF re-allocation","source":"Huawei, Hisillicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a NOTE to clarify that if the NSSF respond a list of candidate AMF, the initial AMF shall not reroute the NAS message to the target AMF via (R)AN.","secretary_remarks":"Revised in parallel session to S2-1813023.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10770,"status":"revised","reservation_date":"2018-11-20 06:25:21","uploaded":"2018-11-20 14:57:01","revisionof":"","revisedto":"S2-1813023","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":841.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812143.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812156","title":"Discussion on support of encryption of NSSAI in AS layer","source":"NEC Europe Ltd","contact":"Kundan Tiwari","contact-id":75778,"tdoctype":"discussion","for":"Presentation","abstract":"Conclusions : In Release 15, SA WG2 should make a decision as guided by the SA WG3 LS Response (S3-183659). In Release 16, it is proposed to work on providing slice privacy during RRC connection procedure by taking one of the solution listed in the discussion paper as baseline for Rel-16 TEI with coordination with RAN WG2 and SA WG3.","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":10920,"status":"noted","reservation_date":"2018-11-20 06:27:33","uploaded":"2018-11-20 10:08:29","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812156.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812158","title":"Handling of slice based overload control at NG-RAN","source":"NEC Europe Ltd","contact":"Kundan Tiwari","contact-id":75778,"tdoctype":"discussion","for":"Presentation","abstract":"Proposal: It is proposed in Rel-16 to introduce a better mechanism to handle the slice based overload control at a NG-RAN and an UE e.g. sending wait timer per slice based. This scenario can be part of TEI16 or eNS.","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":10790,"status":"noted","reservation_date":"2018-11-20 06:29:43","uploaded":"2018-11-20 10:08:29","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812158.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812270","title":"Way forward for NAS and AS protection","source":"Samsung","contact":"Andy Bennett","contact-id":70253,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution proposes a way forward for the NAS and AS protection issue.","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":10850,"status":"noted","reservation_date":"2018-11-20 09:02:03","uploaded":"2018-11-20 11:19:08","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812270.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812393","title":"Network controlled NSSAI for SR-related Access Stratum connection establishment","source":"Nokia, Nokia Shanghai Bell, NEC, Telecom Italia, Huawei, InterDigital, AT&T, Verizon, Sprint, Orange, Samsung","contact":"Andy Bennett","contact-id":70253,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: A PLMN can instruct the UE on which behaviour to adopt when triggering a Service Request procedure, by including Access Stratum Connection Establishment NSSAI Inclusion Mode information in a Registration Accept Message that instructs the UE to: 1.- Include in Access Stratum Connection Establishment a NSSAI = Allowed NSSAI for the UE, or 2. Include in Access Stratum Connection Establishment only the S-NSSAIs of the Network Slices that trigger the RRC Connection Establishment, or 3. Include no NSSAI for Service Request and Registration Request not due to mobility or initial access. 4. Never include any NSSAI in RRC regardless of the procedure .","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10860,"status":"withdrawn","reservation_date":"2018-11-20 12:20:46","uploaded":"2018-11-20 12:24:59","revisionof":"S2-1811565","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":656.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812393.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812461","title":"LS from SA WG3: Reply LS to S2-1811543 on NSSAI in the Access Stratum","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"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","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10810,"status":"postponed","reservation_date":"2018-11-21 11:02:24","uploaded":"2018-11-21 11:04:40","revisionof":"","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_129BIS_West_Palm_Beach\/Docs\/S2-1812461.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813018","title":"EPS to 5GS with network slices","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Let the PGW-C+ SMF at PDN Connection establishment only allocate hS-NSSAI or vS-NSSAI (via mapped hS-NSSAI) that is allowed, according to the UEs subscribed S-NSSAIs.","secretary_remarks":"Revision of S2-1811923. Revised in parallel session to S2-1813285.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10610,"status":"revised","reservation_date":"2018-11-27 15:01:16","uploaded":"2018-12-03 14:18:52","revisionof":"S2-1811923","revisedto":"S2-1813285","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":709.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813018.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813019","title":"EPS to 5GS with network slices","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Make the Nudm_SDM_Get (SUPI, Slice Selection Subscription data) service available also by SMF. Make the Nnssf_NSSelection_Get service available also by PGW-C+SMF. Make it possible to use subscribed S-NSSAIs as input\/output instead of 'S-NSSAIs for the HPLMN associated with established PDN connection'.","secretary_remarks":"Revision of S2-1811924. Revised in parallel session to S2-1813286.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10640,"status":"revised","reservation_date":"2018-11-27 15:01:18","uploaded":"2018-12-03 14:18:52","revisionof":"S2-1811924","revisedto":"S2-1813286","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":824.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813019.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813020","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: 5GS S-NSSAI to take precedence over any corresponding S-NSSAI received from EPS i.e. when in 5GS UE preferably follows 5GS-defined behavior","secretary_remarks":"Revision of S2-1811853. WITHDRAWN","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10670,"status":"withdrawn","reservation_date":"2018-11-27 15:01:19","uploaded":null,"revisionof":"S2-1811853","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":700.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813021","title":"Clarification on rejected S-NSSAIs and cause in Registration and UCU procedure","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add missing information in Registration Accep and UCU Command for rejected S-NSSAIs.","secretary_remarks":"Revision of S2-1812055. 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":10730,"status":"agreed","reservation_date":"2018-11-27 15:01:22","uploaded":"2018-12-03 14:18:53","revisionof":"S2-1812055","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":832.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-181085","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813021.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813022","title":"Clarification on Registration with AMF re-allocation","source":"Huawei, Hisillicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a NOTE to clarify that if the NSSF respond a list of candidate AMF, the initial AMF shall not reroute the NAS message to the target AMF via (R)AN.","secretary_remarks":"Revision of S2-1812142. Revised off-line to S2-1813316.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10750,"status":"revised","reservation_date":"2018-11-27 15:01:24","uploaded":"2018-12-03 14:18:53","revisionof":"S2-1812142","revisedto":"S2-1813316","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":719.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813022.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813023","title":"Clarification on Registration with AMF re-allocation","source":"Huawei, Hisillicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a NOTE to clarify that if the NSSF respond a list of candidate AMF, the initial AMF shall not reroute the NAS message to the target AMF via (R)AN.","secretary_remarks":"Revision of S2-1812143. 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":10780,"status":"agreed","reservation_date":"2018-11-27 15:01:26","uploaded":"2018-12-03 14:18:53","revisionof":"S2-1812143","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":841.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-181085","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813023.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813024","title":"Network controlled NSSAI for SR-related Access Stratum connection establishment","source":"Nokia, Nokia Shanghai Bell, NEC, Telecom Italia, Huawei, InterDigital, AT&T, Verizon, Sprint, Orange, Qualcomm Inc, Broadcom","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A PLMN can instruct the UE on which behaviour to adopt when triggering a Service Request procedure, by including Access Stratum Connection Establishment NSSAI Inclusion Mode information in a Registration Accept Message that instructs the UE to: 1.- Include in Access Stratum Connection Establishment a NSSAI = Allowed NSSAI for the UE, or 2. Include in Access Stratum Connection Establishment only the S-NSSAIs of the Network Slices that trigger the RRC Connection Establishment, or 3. Include no NSSAI for Service Request and Registration Request not due to mobility or initial access. 4. Never include any NSSAI in RRC regardless of the procedure . The default UE behaviour is 4. Any other behaviour can be requested by the serving PLMN ONLY if the HPLMN allows by sending explicit indication from the UDM as part of the subscription data .","secretary_remarks":"Revision of S2-1812009. Revised in parallel session to S2-1813059.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10830,"status":"revised","reservation_date":"2018-11-27 15:01:27","uploaded":"2018-12-03 14:18:54","revisionof":"S2-1812009","revisedto":"S2-1813059","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":656.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813024.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813025","title":"Network controlled NSSAI for SR-related Access Stratum connection establishment","source":"Nokia, Nokia Shanghai Bell, Telecom Italia, NEC, HUAWEI, InterDigital, AT&T, Verizon, Sprint, Orange, Qualcomm Inc, Broadcom","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Registration procedure is updated to include the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter. The UDM indicates to the AMF it it allows the Serving AMF to indicate modes a,b,c in the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter.","secretary_remarks":"Revision of S2-1812010. Revised in parallel session to S2-1813060.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10880,"status":"revised","reservation_date":"2018-11-27 15:01:28","uploaded":"2018-12-03 14:18:54","revisionof":"S2-1812010","revisedto":"S2-1813060","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":767.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813025.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813059","title":"Network controlled NSSAI for SR-related Access Stratum connection establishment","source":"Nokia, Nokia Shanghai Bell, NEC, Telecom Italia, Huawei, InterDigital, AT&T, Verizon, Sprint, Orange, Qualcomm Inc, Broadcom, Ericsson","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A PLMN can instruct the UE on which behaviour to adopt when triggering a Service Request procedure, by including Access Stratum Connection Establishment NSSAI Inclusion Mode information in a Registration Accept Message that instructs the UE to: 1.- Include in Access Stratum Connection Establishment a NSSAI = Allowed NSSAI for the UE, or 2. Include in Access Stratum Connection Establishment only the S-NSSAIs of the Network Slices that trigger the RRC Connection Establishment, or 3. Include no NSSAI for Service Request and Registration Request not due to mobility or initial access. 4. Never include any NSSAI in RRC regardless of the procedure . The default UE behaviour is 4. Any other behaviour can be requested by the serving PLMN ONLY if the HPLMN allows by sending explicit indication from the UDM as part of the subscription data .","secretary_remarks":"Revision of S2-1813024. 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":10840,"status":"agreed","reservation_date":"2018-11-28 19:58:43","uploaded":"2018-12-03 14:24:39","revisionof":"S2-1813024","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":656.0,"crrevision":8.0,"crcategory":"F","tsg_crp":"SP-181088","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813059.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813060","title":"Network controlled NSSAI for SR-related Access Stratum connection establishment","source":"Nokia, Nokia Shanghai Bell, Telecom Italia, NEC, HUAWEI, InterDigital, AT&T, Verizon, Sprint, Orange, Qualcomm Inc, Broadcom, Ericsson","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Registration procedure is updated to include the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter. The UDM indicates to the AMF it it allows the Serving AMF to indicate modes a,b,c in the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter.","secretary_remarks":"Revision of S2-1813025. 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":10890,"status":"agreed","reservation_date":"2018-11-28 19:58:44","uploaded":"2018-12-03 14:24:40","revisionof":"S2-1813025","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":767.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-181089","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813060.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813285","title":"EPS to 5GS with network slices","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Let the PGW-C+ SMF at PDN Connection establishment only allocate hS-NSSAI or vS-NSSAI (via mapped hS-NSSAI) that is allowed, according to the UEs subscribed S-NSSAIs.","secretary_remarks":"Revision of S2-1813018. 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":10620,"status":"agreed","reservation_date":"2018-11-30 17:06:31","uploaded":"2018-12-03 14:28:36","revisionof":"S2-1813018","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":709.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-181088","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813285.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813286","title":"EPS to 5GS with network slices","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Make the Nudm_SDM_Get (SUPI, Slice Selection Subscription data) service available also by SMF. Make the Nnssf_NSSelection_Get service available also by PGW-C+SMF. Make it possible to use subscribed S-NSSAIs as input\/output instead of 'S-NSSAIs for the HPLMN associated with established PDN connection'.","secretary_remarks":"Revision of S2-1813019. 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":10650,"status":"agreed","reservation_date":"2018-11-30 17:06:33","uploaded":"2018-12-03 14:28:36","revisionof":"S2-1813019","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":824.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-181088","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813286.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813316","title":"Clarification on Registration with AMF re-allocation","source":"Huawei, Hisillicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a NOTE to clarify that if the NSSF respond a list of candidate AMF, the initial AMF shall not reroute the NAS message to the target AMF via (R)AN.","secretary_remarks":"Revision of S2-1813022. 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":10760,"status":"agreed","reservation_date":"2018-11-30 17:06:45","uploaded":"2018-12-03 14:28:45","revisionof":"S2-1813022","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":719.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-181085","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813316.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]