[{"name":"S2-180001","title":"Draft Agenda for SA WG2#125","source":"SA WG2 Chairman","contact":"Frank Mademann","contact-id":6821,"tdoctype":"agenda","for":"Approval","abstract":"The meeting agenda.","secretary_remarks":"Approved","agenda_item_sort_order":2,"ainumber":"2","ainame":"Approval of the agenda","tdoc_agenda_sort_order":10000,"status":"approved","reservation_date":"2017-12-18 16:42:22","uploaded":"2018-01-16 12:36:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180001.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180002","title":"Draft Report of SA WG2 meeting #124","source":"SA WG2 Secretary","contact":"Maurice Pope","contact-id":648,"tdoctype":"report","for":"Approval","abstract":"Draft Report of meeting #124 for approval","secretary_remarks":"Revised to S2-180769.","agenda_item_sort_order":4,"ainumber":"3","ainame":"Meeting reports","tdoc_agenda_sort_order":10010,"status":"revised","reservation_date":"2017-12-18 16:42:22","uploaded":"2018-01-16 06:41:26","revisionof":"","revisedto":"S2-180769","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180002.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180003","title":"LS from CT WG1: LS on 5G service request procedure","source":"CT WG1","contact":"Lin Shu","contact-id":43310,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 is under defining the service request procedure in stage 3 TR 24.890 for 5GS. During the discussion, CT WG1 identified some questions need to check with SA WG2. CT WG1 observed in TS 23.501 subclause 5.6.8 (Selective activation of UP connection of existing PDU session), to re-activate PDU session(s) associated with non-3GPP access for a UE registered in both 3GPP and non-3GPP accesses and is in CM-IDLE in non-3GPP access, the AMF handles in different based on the CM mode in 3GPP access: - For CM-IDLE in 3GPP access, the AMF sends a paging message to the UE including an access type information, based on which the UE includes PDU session ID(s) associated with non-3GPP access for which the UE decides to re-activate over 3GPP access in the Service Request message. - For CM-CONNECTED in 3GPP access, the AMF sends a notification message to the UE including PDU session ID(s), based on which the UE includes an indication on whether the PDU session can be re-activated over 3GPP access in","secretary_remarks":"Postponed S2-178214 from SA WG2#124. Response drafted in S2-180592. Final response in S2-181028","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18470,"status":"replied to","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178214","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"C1-173750","lsreply":"S2-181028","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180003.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180004","title":"LS from SA WG6: Reply LS on QCI values for MC Video","source":"SA WG6","contact":"Cuili Ge","contact-id":64432,"tdoctype":"LS in","for":"Action","abstract":"SA WG6 wishes to thank SA WG2 for the LS (S2-174856, S6-171142) on QCI values for MC Video. SA WG6 has discussed the QCI value for MC Video service based on the questions from SA WG2. SA WG6 provides answers to the questions as below: Q1: SA WG2 is seeking SA WG6 guidance on whether the current set of standardized QCI assignments, as specified in Table 6.1.7 of TS 23.203, are sufficient for supporting MC Video service. A1: SA WG6 believes that a new QCI is needed for MC Video media plane. The control signalling for MC Video can use the existing QCI=69 defined for Mission Critical delay sensitive signalling (e.g., MCPTT signalling). Q2: If SA WG6 perceives the need for new QCI value(s) for MC Video, SA WG2 requests guidance in how the desired QoS characteristics are different from existing standardized QCI values (e.g., relative to the current QoS characteristics for QCI=2, Conversational Video). In the context of Question Q2, particular consideration should be given related to any prop","secretary_remarks":"Postponed S2-178224 from SA WG2#124. Noted in parallel session","agenda_item_sort_order":9,"ainumber":"5.2","ainame":"QoS and PCC Maintenance","tdoc_agenda_sort_order":10770,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178224","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG4, CT WG1","lsoriginalls":"S6-171485","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180004.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180005","title":"LS from SA WG4: Reply LS on QCI values for MC Video","source":"SA WG4","contact":"Kyunghun Jung","contact-id":38881,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 thanks SA WG2 for the LS on QCI values for MC Video and answer the following question: Q4: SA WG2 is seeking SA WG4 guidance on whether the current set of standardized QCI assignments, as specified for QCI=2 (Conversational Video) in Table 6.1.7 of TS 23.203, offer sufficient resiliency for handling of MC Video packets (e.g., due to potential packet loss characteristics). The required error resiliency of MC Video may differ depending on its use cases, especially the latency aspects of the services. QCI=2 is often paired with QCI=1 for real-time conversational services such as MTSI. If MC Video is used for such applications, then use of QCI=2 will be appropriate. If MC Video is used for applications with more relaxed latency requirements than MTSI, such as remote surveillance, then higher quality and error resiliency may be achieved, by assigning a QCI that allows a larger latency than with QCI=2 and a comparable or lower packet error loss rate, as the additional delay may be exp","secretary_remarks":"Postponed S2-178225 from SA WG2#124. Noted in parallel session","agenda_item_sort_order":9,"ainumber":"5.2","ainame":"QoS and PCC Maintenance","tdoc_agenda_sort_order":10780,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178225","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, CT WG3, SA WG6","lsoriginalls":"S4-170969","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180005.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180006","title":"LS from RAN WG3: LS on the need for EPS Bearer ID knowledge in NG-RAN for inter-system handover from 5GS to EPS","source":"RAN WG3","contact":"Lixiang Xu","contact-id":50973,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 has studied thoroughly the indirect data forwarding for inter system handover from 5GS to EPS and come to the following conclusions: - Only indirect data forwarding is supported. - PDU session information at the serving NG-RAN node contains mapping information per QoS Flow to a corresponding E-RAB. - At handover preparation, the source NG-RAN node shall decide which mapped E-RABs are proposed to be subject to data forwarding and provide this information in the source-to-target container to the target eNB. - The target eNB assigns forwarding TEID\/TNL address(es) for the E-RAB(s) for which it accepts data forwarding. - A single data forwarding tunnel is established between the source NG-RAN node and UPF per PDU session for which at least data for a single QoS Flow is subject to data forwarding. Then the UPF maps data received from the per PDU session data forwarding tunnel(s) to the mapped EPS bearer(s). Therefore, RAN WG3 would like to kindly update SA WG2 that the NG-RAN needs","secretary_remarks":"Postponed S2-178226 from SA WG2#124. Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17810,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178226","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"R3-174226","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180006.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180007","title":"LS from RAN WG2: LS on usage of user plane integrity protection for DRB","source":"RAN WG2","contact":"Keiichi Kubota","contact-id":43471,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has discussed the technical challenge for the support of integrity protection for DRBs and would like to share RAN WG2 view on the support of integrity protection for DRBs. In RAN WG2#99 Berlin meeting, RAN WG2 made the following agreement: - UP integrity protection can be configured on a per radio bearer (i.e. per DRB) basis. - MAC-I field is not present for a DRB for which integrity protection is not configured. As stated in the RAN WG2 agreements, one Data Radio Bearer (DRB) could be configured to support data integrity protection, which means the MAC-I field would be present after the PDCP payload. Therefore, the transmitter should process the PDCP SDU with the granularity packet by packet to perform data integrity protection. Support of data integrity for user plane over Uu interface causes 1) additional OTA overhead and impacts UE and system throughput performance; and 2) increased need for computation in both UE and network. According to our study on the SA WG3 specifica","secretary_remarks":"Postponed S2-178230 from SA WG2#124. This LS was postponed. Revised at S2#126 in S2-181419.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13870,"status":"revised","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178230","revisedto":"S2-181419","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"-","lsoriginalls":"R2-1712051","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180007.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180008","title":"LS from RAN WG2: LS on details of network identifiers","source":"RAN WG2","contact":"Malik Wahaj Arshad","contact-id":72857,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 is currently standardizing E-UTRA connectivity to 5G CN, as outlined in the WID 'LTE connectivity to 5GCN', RP-171432. In RRC signalling in LTE, a set of 5G system identifiers will be included that are not specified by RAN WG2. This is in correspondence to RRC signalling when connected to 5GC: 1. 5G-S-TMSI - Used in RRC connection setup procedures and for paging. For E-UTRA connected to EPC, S-TMSI was a 40-bit long identifier. As some messages that includes S-TMSI are bit-constrained in terms of size, RAN WG2 would request CT WG4 to provide the length of 5G-S-TMSI along with its constituent identifiers including AMF Set ID, AMF Pointer and 5G-TMSI. RAN 2 would also request CT WG4 to provide the length of AMF Region ID. 2. In case E-UTRA connected to both EPC and 5GC, there would be UEs having either S-TMSI or 5G-S-TMSI in the same cell\/RAN. Considering a specific cell, if the S-TMSI allocated by EPC to one UE and 5G-S-TMSI allocated by 5GC to another UE have the same value and","secretary_remarks":"Postponed S2-178235 from SA WG2#124. Response drafted in S2-180687. Final response in S2-181262","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12260,"status":"replied to","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178235","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, SA WG2","Cc":"","lsoriginalls":"R2-1712068","lsreply":"S2-181262","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180008.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180009","title":"LS from GSMA: Liaison Statement on defining a common value for SPID for Unmanned Aircraft","source":"GSMA","contact":"Barbara Pareglio","contact-id":63010,"tdoctype":"LS in","for":"Information","abstract":"Summary: The GSMA Drone Interest Group, part of the IoT Programme, has studied different possibilities on how to be able to support the identification of Unmanned Aircraft (UA) by leveraging existing capabilities of mobile networks. A primary goal is to enable the mobile operators to provide the right quality of services for UA operations, which would enable them to support their customers. Introduction Mobile operators might need to recognise and distinguish a UA from a traditional device mainly in order to provide the right service optimisation for proper operation of the UA and to ensure the least interference to the other users. Description The GSMA Drone Interest Group that using a commonly defined value of the Subscriber Profile ID (SPID) would facilitate Mobile Network Operators (MNO) to recognise a device being an Unmanned Aircraft. When a user acquires a Subscriber Identity Module (SIM) with the intention of using it in a UA, or when a cellular module with an embedded SIM is i","secretary_remarks":"Postponed S2-178308 from SA WG2#124. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:35:40","revisionof":"S2-178308","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2, RAN WG3","Cc":"","lsoriginalls":"DIG Doc 003","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180009.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180010","title":"LS from SA WG4: LS on Mapping of Conversational Services to 5G System","source":"SA WG4","contact":"Ozgur Oyman","contact-id":44803,"tdoctype":"LS in","for":"Action","abstract":"As part of the FS_5G_MEDIA_MTSI Rel-15 study item, SA WG4 is currently investigating the media handling aspects of conversational services in 5G, taking as baseline the Stage-1 requirements developed in TS 22.261, as well as the Stage-2 architecture for 5G systems developed in TS 23.501. TR 26.919 is under development toward documenting the findings and conclusions of this study item. Among the objectives of this study item is to understand the mapping of IMS-based 3GPP conversational services, including the Multimedia Telephony Service over IMS (MTSI) in TS 26.114 and IMS-based Telepresence Service in TS 26.223, to the 5G system. In that regard, the control-plane and user-plane functionality of a network slice on MTSI and IMS-based telepresence are of interest and how these would map to the 5G system architecture. SA WG4 has considered this question and concluded that the IMS functional blocks relevant for MTSI and IMS-based Telepresence services, including Application Server (AS), S-","secretary_remarks":"Postponed S2-178386 from SA WG2#124. Response drafted in S2-180455. Final response in S2-180865","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16590,"status":"replied to","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178386","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG1","lsoriginalls":"S4-171278","lsreply":"S2-180865","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180010.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180011","title":"LS from SA WG4: Latest Technical Specification on Framework for Live Uplink Streaming","source":"SA WG4","contact":"Nikolai Leung","contact-id":38562,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 would like to thank SA WG2 for their response LS to SA WG4's initial LS on the status and progress of the Live Uplink Streaming (FLUS) work item, including your initial assessment that no immediate issues have been identified in the FLUS technical specification TS 26.238 v0.1.1. During the S4#96 meeting, SA WG4 completed the FLUS technical spec (v0.3.0) as attached in this LS. Given that the SA WG2 LS requested SA WG4 to keep SA WG2 informed on further progress of the FLUS work as appropriate, we are providing the latest version of the specification for your information, and would like to request any comments from SA WG2 on this document. Action: SA WG4 kindly asks SA WG2 to take the above information into account, and provide any inputs on the Rel-15 TS 26.238.","secretary_remarks":"Postponed S2-178388 from SA WG2#124. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178388","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG1, CT WG1","lsoriginalls":"S4-171395","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180011.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180012","title":"Reply LS on Certification\/License and Identification of Aerial Vehicles","source":"SA WG1","contact":"Edward Hall","contact-id":43958,"tdoctype":"LS in","for":"Action","abstract":"As part of a liaison exchange between RAN WG2 and SA WG2, SA WG1 has observed the following question by RAN WG2 and answer by SA WG2: RAN WG2 Question: Specifically, for certification\/license\/authorization issue, RAN WG2 thinks that is out of the RAN WG2 expertise and would kindly like to consult SA WG2 whether it is feasible to signal 'certificate\/licence\/authorization' information of a UE to be used as an aerial UE from CN to the eNB. SA WG2 Response: Certification\/licensing aspects related to devices, SA WG2 understands that it is not SA WG2 responsibility. SA WG2 can provide means to indicate if a user is allowed to have such devices, if such devices are identified as a 3GPP 'UE' belonging to a subscriber associated with an operator's PLMN. Such information, depending on RAN WG2 investigation and its requirement(s) can be provided as part of user's subscription information but the actual certification\/licensing aspects are outside of SA WG2 expertise. SA WG1 discussed this topic an","secretary_remarks":"Postponed S2-178408 from SA WG2#124. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178408","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2","Cc":"SA WG3, GSMA IoT Drone Interest Group","lsoriginalls":"S1-174512","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180012.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180013","title":"LS on NR Idle Mode procedures","source":"SA WG1","contact":"Edward Hall","contact-id":43958,"tdoctype":"LS in","for":"Action","abstract":"As part of a liaison exchange between RAN WG2, SA WG2, and CT WG1, SA WG1 was asked the following question by CT WG1: CT WG1 asks SA WG1 group to confirm that there is a service requirement for the UE to perform PLMN selection when the UE is in the RRC inactive state at the Access Stratum. In this liaison exchange, other groups have previously commented: RAN WG2 assumption 3: RAN WG2 also concluded that AS support for PLMN selection (i.e. providing available PLMNs to NAS) is feasible in RRC_INACTIVE mode. However, it should be confirmed by SA WG2 and CT WG1 whether PLMN selection is supported in RRC_INACTIVE mode. SA WG2 answer 3: From overall system design perspective, SA WG2 believes PLMN selection in RRC_INACTIVE should be supported. However, SA WG2 recognizes that PLMN selection procedures are defined by CT WG1, and would like CT WG1 to confirm. CT WG1 answer: CT WG1 position is that it is desirable for the UE in 5GMM-CONNECTED (CM-CONNECTED) with RRC inactive to perform some form","secretary_remarks":"Postponed S2-178410 from SA WG2#124. Noted in parallel session","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16410,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178410","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2, CT WG1","Cc":"RAN WG3","lsoriginalls":"S1-174314","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180013.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180014","title":"LS from SA WG3: LS on inclusion of the Security Edge Protection Proxy into the 5G architecture","source":"SA WG3","contact":"Hans Christian Rudolph","contact-id":72672,"tdoctype":"LS in","for":"Action","abstract":"At its last meeting SA WG3 has agreed on certain security principles for Release 15 regarding the notion of a Service Based Architecture (SBA). One core element was the inclusion of a network edge proxy for interconnection, c.f. example Figure 1, whose functional aspects are currently being defined in SA WG3. In order to assure a secure and consistent solution for 5G, SA WG3 would like to request SA WG2 to include said network element, proposed to be called Security Edge Protection Proxy (SEPP), into their architecture description. Action: SA WG3 kindly asks SA WG2 to take above information into account and to include the Security Edge Protection Proxy into its architecture.","secretary_remarks":"Postponed S2-178411 from SA WG2#124. Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14110,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178411","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S3-173437","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180014.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180015","title":"LS from RAN WG2: LS on maximum data rate of user plane integrity protected data","source":"RAN WG2","contact":"Keiichi Kubota","contact-id":43471,"tdoctype":"LS in","for":"Information","abstract":"As RAN WG2 LS (R2-1712051) mentioned, RAN WG2 sees a need to limit the use-cases of the user plan integrity protection only for DRB, whose traffic is of low data rate (such as IoT application but not for eMBB). Then RAN WG2 has further discussed the potential maximum data rate of integrity protected data in RAN WG2#100 Reno meeting. This time, RAN WG2 made the following agreement: 1 UE capability to be added for the maximum aggregate data rate per UE of user plane integrity protected data for DRBs. 2 Lowest possible value for the data rate is 64 kbps  Question to SA WG3: Does SA WG3 see any problem with the RAN WG2 agreed lowest possible value for the user plane integrity protected data rate? Please note that there is consensus at RAN plenary that features with hardware impact need to be completed by December 2017. Therefore we would greatly appreciate if the question is answered in this meeting week so that RAN WG2 can finalize the UE requirement by then.","secretary_remarks":"Postponed S2-178412 from SA WG2#124. This LS was postponed. Revised at S2#126 in S2-181420.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13880,"status":"revised","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178412","revisedto":"S2-181420","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2","lsoriginalls":"R2-1714125","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180015.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180016","title":"LS from SA WG3: Reply LS on security handling for EPS-5GC interworking","source":"SA WG3","contact":"Nagendra Bykampadi","contact-id":69265,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks SA WG2 for their LS on security handling for EPC-5GC interworking. SA WG3 is still in the process of defining specifications for security of EPC-5GC interworking. Following answers assumes a legacy MME. 1. Does SA WG3 assume support for 5G to 4G and\/or 4G to 5G security context mapping during Idle and connected mode mobility between EPC and 5GC? Yes. SA WG3 has agreed to support use of mapped security context for interworking between 4G and 5G for both idle mode and connected mode mobility scenarios. 2. Does SA WG3 see the need for supporting reuse of a native security context (if available) in case the UE returns to EPC and\/or 5GC, respectively? SA WG3 sees no need for reuse of a native security context in case the UE returns to EPC. In scenarios where the UE returns to 5GC, SA WG3 believes that reuse of an existing native 5G security context is beneficial. 3. For the case that the UE performs a mobility registration update in 5GC after being connected to EPC: how is the","secretary_remarks":"Postponed S2-178416 from SA WG2#124. Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17520,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178416","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S3-173508","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180016.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180017","title":"LS from SA WG4: LS on clarifying video-related V2X use cases","source":"SA WG4","contact":"Kyunghun Jung","contact-id":38881,"tdoctype":"LS in","for":"Information","abstract":"WITHDRAWN: As introduced in S1-173118, SA WG4 started an SI 'Study on V2X Media Handling and Interaction', to analyse media-related use cases for advanced driving and consider approaches for their realizations using media compression and transport mechanisms available or under development. After a review of works that have been done in SA WG1 and other 3GPP WGs, SA WG4 began studying the use cases. However, application of SA WG4's stage-3 view to the eV2X use cases did not yet reach a clear understanding of their backgrounds and underlying principles that would have been discussed and agreed at SA WG1. The questions and comments made in SA WG4#96 are outlined in the attached tdoc. Although handling of media has been the speciality of SA WG4, their applications have been for the conversational and entertainment uses. Therefore SA WG4 agreed consultation with SA WG1 as one of the key objectives in this study. The coming SA WG1#81 and SA WG4#97 seem to be a good opportunity for both WGs t","secretary_remarks":"Postponed S2-178932 from SA WG2#124. Withdrawn (not to SA WG2)","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24100,"status":"withdrawn","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178932","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, 5GAA WG1, 5GAA WG2","Cc":"5GAA WG5","lsoriginalls":"S4-171358","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180017.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180018","title":"LS from GSMA: LS Reply to SA WG2 on Status Icon related to 5G","source":"GSMA","contact":"Dongwook Kim","contact-id":66121,"tdoctype":"LS in","for":"Action","abstract":"1 Introduction GSMA Future Networks Programme thanks SA WG2 for the inquiry on requirements and granularity of Service indicators and\/or RAT indicators related to 5G (S2-175303). GSMA Future Networks Programme is conducting a project aimed to analyse possible paths for operators in introducing and migrating from 3GPP 4G network to 5G network from technical, economic and strategic perspective. The inquiry is timely and appropriate for the discussion within 5G Introduction project. The operator members of the 5G Introduction project have discussed the request and the results are provided below. Operators agree that it would be beneficial to have consistency across device OEMs of the RAT indicated to the user. 2 Operator Requirement Survey and discussion among operator members of the 5G Introduction project indicates that four configurations should be supported for deciding when to present a 5G status icon. The configurations are presented from the most restrictive to the most relaxed, th","secretary_remarks":"Postponed S2-178933 from SA WG2#124. Noted","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11200,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178933","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2","Cc":"TSG SA, SA WG1, TSG RAN, CT WG1, TSG CT","lsoriginalls":"LS reply to 3GPP SA2 on StatusIcon","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180018.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180019","title":"LS from GSMA NG SIGNAL: LS on interworking between networks with different 5G deployments options in a roaming scenario","source":"GSMA NG SIGNAL","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"GSMA NG SIGNAL is discussing the impact of the different 5G deployment options and of a new signalling protocol for 5G in the context of roaming. GSMA NG SIGNAL would like to ask clarification on how the roaming interworking is envisaged between 5G networks with NGC and 5G networks with EPC.","secretary_remarks":"Postponed S2-178937 from SA WG2#124. Response drafted in S2-180739. Final response in S2-180810","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17360,"status":"replied to","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178937","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG4","Cc":"","lsoriginalls":"SIGNAL99 Doc 104","lsreply":"S2-180810","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180019.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180020","title":"LS from RAN WG2: Reply LS on unified Access Control for 5G NR","source":"RAN WG2","contact":"Sudeep Palat","contact-id":63872,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks SA WG1 for the LS response on unified Access Control for 5G NR. RAN WG2 further discussed the attached SA WG1 CR and has some additional follow up questions. Q1: In the SA WG1 CR S1-173548, AC11-15 use the same category, i.e. Access category 1. RAN WG2 would like to check with SA WG1 if access barring needs to differentiate each of AC 11-15, similarly to handling of AC11-15 in LTE AC (e.g., one flag is signalled for each of AC11-15 for the network to prioritize AC11-15 over the other access categories). Q2: RAN WG2 would like to clarify whether both SMS and SMS over IP use same category 7. RAN WG2 would also like to check with SA WG1 whether different access barring behaviour needs to be supported for SMS and SMS over IP. Q3: RAN WG2 would like to ask SA WG1 if the UAC mechanism requires for AC11-15 UEs separate sets of barring control parameters associated to access attempts for MO data, MO signalling, MMTEL voice and MMTEL video, respectively (similar to that defined f","secretary_remarks":"Postponed S2-179126 from SA WG2#124. Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12210,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-179126","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"CT WG1, SA WG2, CT WG6","lsoriginalls":"R2-1714013","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180020.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180021","title":"LS from 5GAA WG2: LS on V1 and V2 reference points","source":"5GAA WG2","contact":"Heejin Kim","contact-id":71611,"tdoctype":"LS in","for":"Information","abstract":"5GAA WG2 discussed how to provision PC5 parameters for V2X operations using 3GPP LTE Rel-14 standards, and have reached the consensus that, in addition to the methods currently specified in 3GPP standards, it is beneficial to support an option for a V2X application server to provision PC5 parameters via V1 interface. 5GAA understands that the current 3GPP standards do not support this option, and would like to recommend making corresponding specification support. 5GAA WG2 have also reached the consensus that, in addition to the methods currently specified in 3GPP standards, it is beneficial to support an option for a V2X application server to provision PC5 parameters to the V2X Control Function via V2 interface. 5GAA understands that the current 3GPP standards do not support this option, and would like to recommend making corresponding specification support. It is 5GAA WG2's understanding that a UE is configured with a single set of PC5 parameters at a given time, either using V1 or V3","secretary_remarks":"This LS was postponed. Revised at S2#126 in S2-181421.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10710,"status":"revised","reservation_date":"2017-12-19 11:54:35","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181421","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, SA WG6, TSG CT","lsoriginalls":"5GAA_A-170278","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180021.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180022","title":"LS from NGNM Alliance: LS reply to ETSI ISG NFV on lifecycle management for 3GPP service based architecture","source":"NGNM Alliance","contact":"Dan Wang","contact-id":72661,"tdoctype":"LS in","for":"Information","abstract":"In March 2017 the NGMN Alliance approved the work item for 'Service-based architecture in 5G', with the objective to investigate the SBA approach from an operational perspective and to document the high-level requirements of the SBA approach, the related use cases, and guidelines for operators to leverage a service-based architecture in 5G. NGMN would like to thank ETSI ISG NFV for the feedback with questions. NGMN 5G SBA program has discussed the questions and the answers are shown below ETSI ISG NFV Q1) In NGMN view, is a 3GPP NF Service deployed only as part of a VNF (e.g. Location service as part of AMF), or is a 3GPP NF Service expected to be deployed independently, as a single VNF? a. If the Service is deployed as part of a VNF, do you require that some (or all) LCM operations to be performed independently of the other 3GPP 5GC NF Services that are composing that VNF, or not? NGMN SBA Answer: NGMN expects that 3GPP NF Services can be deployed independently, as a single VNF. NGMN","secretary_remarks":"Moved to 7.1 session. This LS was postponed. Revised at S2#126 in S2-181422.","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23080,"status":"revised","reservation_date":"2017-12-19 11:54:35","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181422","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI ISG NFV","Cc":"SA WG5, SA WG2","lsoriginalls":"NGNM-171124","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180022.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180023","title":"LS from CT WG1: Reply LS on EDT procedures and AS NAS interaction","source":"CT WG1","contact":"Marko Niemi","contact-id":16608,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks RAN WG2 for LS on EDT procedures and AS NAS interaction from RAN WG2. CT WG1 has discussed on 'Identified Potential Issues in RAN WG3, CT WG1 or SA WG2 domain' RAN WG2 listed in the attachment of the LS. Regarding issue#1 and #2 on additional eNB-MME interaction, CT WG1 expects it's up to RAN WG3\/SA WG2 to decide whether additional interaction between eNB and MME is needed, however, CT WG1 assumes the MME should not need to know whether the UE is using EDT or not. Regarding issue#3 on EDT use cases, CT WG1 agrees with RAN WG2's decision that the intention to use EDT should be for data only and not for NAS signalling. CT WG1 would like to ask RAN WG2 the following question: Question to RAN WG2: For the case when Control Plane CIoT optimization is used, would the RAI (Release Assistance Information) from NAS to AS in the UE indicating whether more UL data is expected, be useful for the AS layer to decide whether to use EDT? Regarding issue#4 on AS\/NAS interaction: CT WG1 ha","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10940,"status":"noted","reservation_date":"2017-12-19 11:54:35","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181434","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, SA WG2","Cc":"-","lsoriginalls":"C1-175072","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180023.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180024","title":"LS from CT WG1: Reply LS on Early Data Transmission","source":"CT WG1","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA WG2 for their LS on Early Data Transmission. CT WG1 has discussed SA WG2's request for CT WG1 to indicate whether the MME expects to receive indication for UEs capability for 'ce-ModeB' at every NAS signalling connection from 'MME's lower layers' or whether it is possible this indication for UE's capability for 'ce-ModeB' to be stored in UE context at MME e.g. upon Attach\/TAU and then later avoid the UE to have to send it at every RRC signalling connection. CT WG1 would like to inform SA WG2 that CT WG1 has agreed C1-175388 clarifying that the MME shall store the indication of support of CE mode B for a UE received by the MME from the lower layers. Action: CT WG1 asks SA WG2 to take the information above into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10950,"status":"noted","reservation_date":"2017-12-19 11:54:35","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2","Cc":"RAN WG3, SA WG3","lsoriginalls":"C1-175310","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180024.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180025","title":"LS from CT WG1: LS on timers for the network-requested PDU session modification procedure and SSC mode 3","source":"CT WG1","contact":"Christian Herrero-Veron","contact-id":45210,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 have analyzed the stage 2 requirements on the network-requested PDU session modification procedure and 'SSC mode 3' in TS 23.502 subclause 4.3.5.2. CT WG1 has identified several issues with the stage 2 text and has several questions regarding the motivation, the objectives and the proposed solution, as follows: 1. What is the purpose of the PDU session release timer provided to the UE? The timer is signalled in the NAS message, but in the CT WG1 view, the NAS layer in the UE has no use for this timer. If the timer is to be used by upper layers, why is it signalled as an IE in a NAS message? NAS layer in the UE layer has no means of controlling the transfer of IP flows between PDU sessions unless, e.g., a release indication from upper layer is received. Therefore, the NAS layer can either initiate PDU session release of the old session or release it locally or perform no action, without the need for a timer from the network. NAS layer will not check what is occurring in the user-","secretary_remarks":"Responses drafted in S2-180167, S2-180289 and S2-180307. Final response in S2-181280","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":12960,"status":"replied to","reservation_date":"2017-12-19 11:54:35","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-175378","lsreply":"S2-181280","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180025.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180026","title":"LS from CT WG1: LS on session management congestion control","source":"CT WG1","contact":"Yanchao Kang","contact-id":72631,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has discussed the DNN based congestion control and S-NSSAI based congestion control. CT WG1 would like SA WG2 to answer the following questions: CT WG1 has noticed that the DNN based congestion control is very similar to the APN based congestion control in EPS system. Question 1: Shall the UE run the same timer for DNN based congestion control in 5GS and APN based congestion control in EPS? If yes, shall the UE keep the timer running upon inter-system change? Question 2: Can a network with slicing also apply DNN based congestion control, or will such network apply only S-NSSAI based congestion control? If a network with slicing can also apply DNN based congestion control, how does the SMF determine whether a DNN is congested for a UE when the UE has PDU sessions to that DNN via multiple slices? If a network with slicing can also apply DNN-based congestion control, please consider the following scenario: The UE attempts to establish a PDU session X with S-NSSAI#1 and a DNN#1 comb","secretary_remarks":"Responses drafted in S2-180238 and S2-180538. Final response in S2-181263","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12370,"status":"replied to","reservation_date":"2017-12-19 11:54:35","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-175379","lsreply":"S2-181263","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180026.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180027","title":"LS from CT WG1: LS on Mobility management congestion control","source":"CT WG1","contact":"Lalith Kumar","contact-id":60520,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has discussed the NAS level congestion control as captured in 3GPP TS 23.501, sub clause 5.19.7.2. CT WG1 is not clear for some of the requirements and hence request SA WG2 to answer following questions: Question 1: Is it possible that AMF can give Mobility Management back-off timer over non-3GPP access? Question 2: In case of the same PLMN for both 3GPP access and non-3GPP access, if Mobility Management back-off timer is running, is UE not allowed to initiate NAS signalling on both 3GPP access and non-3GPP access? Or is the Mobility Management back-off timer applicable per access on which UE received the timer? Question 3: If 3GPP access and non-3GPP access are connected to different core networks (different PLMNs) but those are ePLMNs, and if the Mobility Management back-off timer is running, is the UE not allowed to initiate NAS signalling on both 3GPP access and non-3GPP access? Or is the Mobility Management back-off timer applicable per access on which UE received the timer","secretary_remarks":"Responses drafted in S2-180237, S2-180358 and S2-180682. This LS was postponed. Revised at S2#126 in S2-181423.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12420,"status":"revised","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181423","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"C1-175413","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180027.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180028","title":"LS from CT WG1: LS on indication of preferred CIoT network behaviour","source":"CT WG1","contact":"Mikael Wass","contact-id":40034,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has identified an issue with the indication of preferred CIoT network behaviour, as defined in stage 3, as the UE can indicate preference for CP CIoT optimization and\/or UP CIoT optimization (a.k.a. RRC suspend\/resume). CT WG1 understands that the MME needs this information in attach and TAU to establish the preferred type of PDN connection (CP or UP), either directly in combination with an attach procedure or at a later point in time. It is however a valid option that a CIoT supporting UE can support user plane (S1-u data transfer) without supporting indication of UP CIoT optimization. Additionally, UP-CIoT optimization, is a network initiated feature triggered by the network once user plane exists. RRC suspend\/resume cannot be initiated by the UE. Based on the above, CT WG1 discussed an update of the indication of preferred CIoT network behaviour to replace UP CIoT optimization indication with S1-U data transfer for indication of preference for UP data. The CT WG1 CR to 24.301","secretary_remarks":"Responses drafted in S2-180157 and S2-180384. Final response in S2-180920","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10870,"status":"replied to","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"C1-175414","lsreply":"S2-180920","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180028.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180029","title":"LS from CT WG3: LS on Clarification on Npcf_SMPolicyControl service","source":"CT WG3","contact":"Fuencisla Garcia Azorero","contact-id":43873,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 has different interpretations of Npcf_SMPolicyControl service defined in TS 23.502 subclause 5.2.5.4 and different understandings of how it is used in the procedures and flows described for the policy framework in TS 23.502 subclause 4.16. Specifically, CT WG3 has identified the following potential options: - Option 1 The Npcf_SMPolicyControl_Get service operation can be invoked by the SMF after the PDU session establishment during the PDU session lifetime (e.g. at PDU session modification) to request policies from the PCF or to update PDU session information in the PCF, as the current Npcf_SMPolicyControl_Get service operation description allows, or - Option 2 Subsequent interactions from the SMF to the PCF to request policies or to update PDU session information in the PCF only take place by invoking Nsmf_EventExposure_Notify service operation, or - Option 1 in combination with Option 2 is also possible. Action: CT WG3 asks SA WG2 to kindly indicate which of the options above","secretary_remarks":"Response drafted in S2-180234. This LS was postponed. Revised at S2#126 in S2-181424.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14500,"status":"revised","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181424","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"C3-176376","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180029.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180030","title":"LS from CT WG3: LS on the information exposed to the SCS\/AS for AS session establishment","source":"CT WG3","contact":"Wenliang Xu","contact-id":67079,"tdoctype":"LS in","for":"Action","abstract":"For Rel-15, CT WG3 is specifying the northbound (i.e. external) T8 interface of the SCEF to 4G networks in TS 29.122 based on stage 2 requirements in TS 23.682. For 'Setting up an AS session with required QoS procedure' and 'Change the chargeable party at session set-up or during the session procedure', there is one input data for the SCEF called 'Description of the application flows'. Currently, CT WG3 is not sure if such flow description can contain QoS information and if such flow description can also relate to IMS or MCPTT media information in deriving policy information in aforementioned two procedures. Note: 'Setting up an AS session with required QoS' contains a QoS reference which can refer to a locally configured QoS information, but not for 'Change the chargeable party at session set-up or during the session'. Question 1: Does this 'Description of the application flows' contains only information to identify the application (e.g. IP flow filter, Application ID)? Or this 'Descr","secretary_remarks":"Response drafted in S2-180233. Final response in S2-181378","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10990,"status":"replied to","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG6","lsoriginalls":"C3-176379","lsreply":"S2-181378","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180030.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180031","title":"LS from CT WG4: Reply LS on Standardised Slice Service Types","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks SA WG2 for their LS on Standardised Slice Service Types, asking CT WG4 to clarify the range for each of the standardised and the non-standardised SSTs. CT WG4 has specified the definition of the S-NSSAI in the attached 23.003 CR. There is a total of 256 standardized and non-standardized SSTs, with half of the range assigned to standardized and non-standardised values respectively. Action: CT WG4 kindly asks SA WG2 group to take the above response into account.","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":11550,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG1","lsoriginalls":"C4-176299","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180031.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180032","title":"LS from CT WG4: Reply LS on PLMN and RAT selection policies for roaming","source":"CT WG4","contact":"Peter Schmitt","contact-id":13753,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 thanks CT WG1 for their reply LS on PLMN and RAT selection policies for roaming. CT WG4 has discussed the information provided in the CT WG1 and SA WG3 LS. CT WG4 would like to provide CT WG1 and SA WG3 feedback and provide input on: - The service in the HPLMN that will originate the steering of roaming messages. In CT WG4 understanding the list of preferred PLMN\/access technology combinations is part of the subscription data and therefore belongs to the UDM. From CT WG4 perspective, this is seen as a normal service offered by the UDM to the AMF, and will use the same service operations used for downloading and updating the user profile to the AMF. Whether these data need to be secured is seen as a decision which should be taken by SA WG3.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12500,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG3","Cc":"CT WG3, SA WG2","lsoriginalls":"C4-176362","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180032.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180033","title":"LS from CT WG6: LS on a potential USIM solution for PLMN and RAT selection policies for roaming","source":"CT WG6","contact":"Tim Evans","contact-id":49202,"tdoctype":"LS in","for":"Action","abstract":"In LS S2-175286, SA WG2 have defined the following new requirements for PLMN and RAT selection policies for roaming: - a control plane solution is used from the HPLMN to the UE. - VPLMN is able to relay this information to the UE. - VPLMN shall not be able to alter the information sent by the HPLMN; i.e. UE needs to be able to check the integrity of the information provided to it. - UE shall be able to detect if VPLMN alter or remove those information and act accordingly. CT WG6 would like to indicate that the existing mechanism for USIM OTA (defined in TS 31.115 and TS 31.116) and that provides integrity protection, cyphering and replay protection, is a generic protocol that can be adapted to many transports.The USIM OTA also allows the operator to immediately send a REFRESH command for steering of roaming (see TS 31.111) to trigger the steering of roaming procedure. CT WG6 would be happy to work with the relevant groups to extend the OTA transport to the control plane, if this become","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12510,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, CT WG1, CT WG4","Cc":"SA WG1","lsoriginalls":"C6-170696","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180033.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180034","title":"LS from RAN WG2: LS on Reliability for eV2X","source":"RAN WG2","contact":"Marco Belleschi","contact-id":61839,"tdoctype":"LS in","for":"Action","abstract":"In RAN WG2#99-bis, RAN WG2 agreed to support sidelink packet duplication in the PDCP layer with the intent to increase the reliability of V2X packet transmissions. Duplicated PDCP PDUs are submitted to two different RLC entities and associated to two different logical channels. The MAC layer makes sure to transmit duplicated packets in different sidelink carriers. RAN WG2 view is that it is beneficial to enable sidelink packet duplication at the AS layer, on the basis of the reliability requirements of the different V2X service types. However, RAN WG2 understanding from the current TS 36.300 below, is that the AS layer is only aware of the PPPP value associated to a V2X packet, and of the PDB that can be determined from the PPPP. Based on PPPP defined in Rel-14, the AS layer currently cannot be aware of the reliability values associated to V2X packets. From TS 36.300: - The Access Stratum (AS) is provided with the PPPP of a protocol data unit transmitted over PC5 interface by higher la","secretary_remarks":"Response drafted in S2-181089. Final response in S2-181368","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11100,"status":"replied to","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"R2-1714187","lsreply":"S2-181368","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180034.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180035","title":"LS from RAN WG2: Reply LS on supported features by 5GC for E-UTRA connected to 5G CN","source":"RAN WG2","contact":"Manivannan Thyagarajan","contact-id":68484,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 would like to thank SA WG5 for the reply LS on supported features by 5GC for E-UTRA connected to 5G CN. RAN WG2 would like to point out that in the RAN WG2 reply LS R2-1712041 sent to RAN WG3 and copied to SA WG5 after the RAN WG2#99bis meeting it was already communicated that for LTE connected to 5GC, from pure radio interface perspective, MDT could be supported with the same functionality as that of LTE connected to EPC but MDT is not part of the Rel-15 NR WID scope. As for QMC streaming, from RAN WG2 point of view, the E-UTRA radio interface functionality for QMC streaming would be the same for EPC and 5GC and hence can be supported. It is up to other groups to indicate if it can be supported from their perspective.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12520,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"SA WG1, SA WG2, CT WG1, RAN WG3","lsoriginalls":"R2-1714203","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180035.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180036","title":"LS from RAN WG2: Reply LS on LS on default values for 5GS QoS averaging window for standardised 5QIs","source":"RAN WG2","contact":"Benoist SEBIRE","contact-id":68461,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has discussed the averaging window for standardised 5QIs and understands that the suggested default values of 2s and 3s are generally fine but views were also expressed that in some cases the window would either need to be shorter (in the order of a few PDBs for services with tight delay requirements) or longer (up to 10s for services with infrequent data transmissions). RAN WG2 also understands that the default value can always be overwritten through configuration. For URLLC, RAN WG2 also believes that a maximum burst size should be introduced for GBR resources. The maximum burst size would define the largest amount of data that the application can expect to be transmitted within the radio portion of the PDB. Action: RAN WG2 respectfully asks SA WG2 to take the above response into account.","secretary_remarks":"This LS was postponed. Revised at S2#126 in S2-181425.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14140,"status":"revised","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181425","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG4, SA WG6, CT WG1","lsoriginalls":"R2-1714245","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180036.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180037","title":"LS from RAN WG2: Reply LS on Certification\/License and Identification of Aerial Vehicles","source":"RAN WG2","contact":"Dawid Koziol","contact-id":68362,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 and SA WG1 for their LSs related to certification\/license and identification of Aerial Vehicles. Based on the provided feedback, RAN WG2 has further discussed this topic and agreed the attached Text Proposal for UE Identification for TR 36.777. In particular, it was agreed that: Permission for a user to function as an aerial UE in the 3GPP network can be identified via subscription information. This subscription information is passed to RAN via S1 signalling from the MME. The eNB may use this information together with capability indication to identify an aerial UE, perform the necessary control and apply the relevant functions. RAN WG2 understanding is that signalling mentioned above would be an authorization information, similar to the one provided for ProSe or V2X. Based on SA WG1 feedback, RAN WG2's understanding is that in Rel-15 this information would be limited to subscription related information while aspects relating to certification\/licensing","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG1, RAN WG3","Cc":"-","lsoriginalls":"R2-1714248","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180037.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180038","title":"LS from RAN WG3: Reply LS on radio capabilities handling upon inter-system mobility","source":"RAN WG3","contact":"Xipeng Zhu","contact-id":41170,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 has not yet discussed the UE radio capability handling for NG-RAN. From RAN WG3 point of view, there is no showstopper to follow the same principle as in LTE and option 3\/3a\/3x for the case of option 2, 5, and 7 (assuming that RAN WG2 also follows the same principle). Action: RAN WG3 kindly asks SA WG2 and RAN WG2 to take above information into consideration.","secretary_remarks":"Noted","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11210,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2","Cc":"-","lsoriginalls":"R3-175025","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180038.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180039","title":"LS from RAN WG3: Reply LS on Paging failures for CE Capable UEs","source":"RAN WG3","contact":"Luis Lopes","contact-id":47178,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG2 for the received LS which describes the problem whereby the MME does not have the 'UE Radio Capability for Paging Information' in the UE context, either because of idle mode mobility from 2\/3G, or from RAN areas where the RAN did not provide this information to MME. RAN WG3 discussed the respective scenarios, and the associated paging behaviour of the eNB, during RAN WG3#97bis and RAN WG3#98. It is RAN WG3's understanding that the eNB may receive two related IEs within the S1-AP PAGING MESSAGE, specifically: - The UE Radio Capability for Paging IE, which is transparently relayed by the MME and may contain information on UE support of CE modes (or otherwise) - The Assistance Data for CE Capable UEs IE, which contains information on the CE level and last serving cell as reported by the previously serving eNB. In general, the eNB should consider paging the UE in MPDCCH based on the information included in either of these IEs in the paging message. RAN WG3 assumes tha","secretary_remarks":"This LS was postponed. Revised at S2#126 in S2-181426.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10250,"status":"revised","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181426","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2","Cc":"-","lsoriginalls":"R3-175045","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180039.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180040","title":"LS from RAN WG4: Response LS on simultaneous transmission and\/or reception over EPC\/E-UTRAN and 5GC\/NR","source":"RAN WG4","contact":"Yang Tang","contact-id":56725,"tdoctype":"LS in","for":"Action","abstract":"RAN WG4 would like to thank SA WG2 for the LS on simultaneous transmission and\/or reception over EPC\/E-UTRAN and 5GC\/NR. RAN WG4 has discussed questions below: SA WG2 kindly asks RAN WG1, RAN WG2 and RAN WG4 to provide their views on the feasibility, necessary conditions and potential restrictions for UE's to operate in Dual Rx\/Tx and Dual Rx modes with respect to EPC\/E-UTRA and 5GC\/NR, in particular in absence of tight coordination at RAN level between the two systems. RAN WG4 concluded that - It is feasible to operate in Dual Rx\/Tx and Dual Rx modes by introducing LTE power management related power back off procedure in NR to handle the potential power management issue. - It is feasible to operate in Dual Rx\/Tx and Dual Rx modes with respect to EPC\/E-UTRA and 5GC\/NR subject to the restriction of supported LTE and NR bands which support transmission and\/or reception over EPC\/E-UTRAN and 5GC\/NR. Action: RAN WG4 respectfully asks SA WG2 to take the above information into account in thei","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18090,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG1, RAN WG2","lsoriginalls":"R4-1714539","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180040.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180041","title":"LS from SA WG1: LS on Removal of over LTE limitation from Mission Critical Specifications","source":"SA WG1","contact":"Kees Verweij","contact-id":12756,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 would like to inform SA WG2, SA WG3, SA WG4, SA WG5, SA WG6, CT WG1, CT WG3, CT WG4, CT WG6, RAN WG1, RAN WG2, RAN WG3, RAN WG4, RAN WG5 and RAN WG6 that SA WG1 has agreed on the attached CRs that - change the titles of the stage 1 specifications for Mission Critical Services, removing 'over LTE'; and - apply related updates to the wording in the specifications to clarify that the requirements are applicable from LTE onwards. The background of the changes is that Mission Critical user organisations intend to take advantage of the continuous evolution of 3GPP systems while enhancing MC Services, i.e. MCPTT, MCVideo and MCData, and adding new mission critical services over such continuously evolving 3GPP systems. The changes in the attached CRs should make it clear that the requirements specified in 3GPP stage 1 Technical Specifications of MC Services are not restricted to LTE. Action: 1 To update references to release 15 3GPP stage 1 Technical Specifications of MC Services. 2 To","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10860,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, SA WG4, SA WG5, SA WG6, CT WG1, CT WG3, CT WG4, CT WG6, RAN WG1, RAN WG2, RAN WG3, RAN WG4, RAN WG5, RAN WG6","Cc":"TSG SA, TSG CT, TSG RAN","lsoriginalls":"S1-174542","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180041.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180042","title":"LS from SA WG1: Reply LS on selectively disabling legacy radio access","source":"SA WG1","contact":"Betsy Covell","contact-id":68109,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks SA WG3 for their LS selective disabling of legacy radio. In response, SA WG1 has agreed the attached CR to introduce the service requirements for selectively disabling a radio access technology at the UE.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13860,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2, CT WG1, RAN WG2","lsoriginalls":"S1-174601","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180042.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180043","title":"LS from SA WG1: Reply LS on clarification on Restricted Operator Services","source":"SA WG1","contact":"Betsy Covell","contact-id":68109,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 thanks SA WG2 for its LS on clarification on Restricted Operator Services. SA WG1 is pleased to provide the following clarifications. - Whether it can be assumed that an UE (authenticated or unauthenticated) is always aware that its request is for a Restricted Local Operator Service, hence the UE shall indicate it to the network. SA WG1 Response: SA WG1 agrees that it cannot be assumed that a UE is always aware that its request is for a Restricted Local Operator Service (RLOS). A UE that is accessing an RLOS may know that it is an RLOS attempt, and may be provisioned to send an RLOS indication to the serving network. Alternatively, as in the case of a manual roaming service, the UE may not have that awareness and may not be provisioned to provide an RLOS indication to the serving network. SA WG1 has agreed the attached CR which includes a requirement that a UE includes the RLOS indicator when it knows it is accessing RLOS. - Whether it can be assumed that authentication is alway","secretary_remarks":"Response drafted in S2-181000. Final response in S2-181407","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22600,"status":"replied to","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181000","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG3","lsoriginalls":"S1-174604","lsreply":"S2-181407","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180043.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180044","title":"LS from SA WG1: Reply LS on requirements on unified access control for 5GS","source":"SA WG1","contact":"Betsy Covell","contact-id":68109,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks CT WG1 for their reply LS on unified Access Control for 5G NR. SA WG1 is pleased to provide the following clarifications. Question 1: In EPS, according to TS 22.011, a UE configured for EAB initiating an emergency call shall ignore any EAB information that is broadcast by the network. Is CT WG1's understanding correct that according to TS 22.261 the priority between access category 2 (delay tolerant service) and access category 3 (emergency) has been reverted, i.e. a UE configured for delay tolerant service initiating an emergency call shall use access category 2 (instead of 3)? SA WG1 reply 1: SA WG1 has agreed the attached CR which clarifies that the emergency access category takes precedence over the access category for a delay tolerant service. Question 2: What is the relationship between the terms 'configured for EAB' and 'configured for delay tolerant service'? Are they equivalent terms or are they referring to exactly the same configuration'? SA WG1 reply 2: SA WG1","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12200,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2, CT WG6, RAN WG2","lsoriginalls":"S1-174623","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180044.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180045","title":"LS from SA WG1: Reply LS on unified access control for 5G NR","source":"SA WG1","contact":"Krister S\u00e4llberg","contact-id":11978,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks RAN WG2 for their LS on unified access control for 5G System. SA WG1 provides answers below and informs that SA WG1 has agreed the attached CR. RAN WG2 Question 1: In the SA WG1 CR S1-173548, AC11-15 use the same category, i.e. Access category 1. RAN WG2 would like to check with SA WG1 if access barring needs to differentiate each of AC 11-15, similarly to handling of AC11-15 in LTE AC (e.g., one flag is signalled for each of AC11-15 for the network to prioritize AC11-15 over the other access categories). SA WG1 Response: SA WG1 has agreed to document this differently in the attached CR to make it clearer. In addition, SA WG1 see a need to extend to separately give priority handling for MPS and MCS respectively. RAN WG2 Question 2: RAN WG2 would like to clarify whether both SMS and SMS over IP use same category 7. RAN WG2 would also like to check with SA WG1 whether different access barring behaviour needs to be supported for SMS and SMS over IP. SA WG1 Response: SA WG1 d","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12220,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1, SA WG2, CT WG6","lsoriginalls":"S1-174624","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180045.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180046","title":"LS from SA WG3: LS on Emergency call support for EDCE5","source":"SA WG3","contact":"Adrian Escott","contact-id":24089,"tdoctype":"LS in","for":"Action","abstract":"During the work on EDCE5, the issues of using EDCE5 bearers during unauthenticated emergency calls was raised. SA WG3 did not find an issue with supporting emergency with the main impact being the limiting the use of the NULL integrity algorithm for the SRB between UE and SgNB for only the case of unauthenticated emergency calls. SA WG3 will keep other groups informed if a later problem is found. SA WG3 are not clear whether they are requirements or support for EDCE5 bearers during unauthenticated emergency calls. Hence SA WG3 are asking SA WG1, SA WG2 and RAN WG2 if they have issues in supporting EDCE5 bearers during unauthenticated emergency calls. In the absence of a response raising such issues, SA WG3 will continue to work on specifying the use of EDCE5 bearers during unauthenticated emergency calls. Action: SA WG3 asks SA WG1, SA WG2 and RAN WG2 group to inform SA WG3 if they have issues with using EDCE5 bearers in unauthenticated emergency calls","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11060,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, RAN WG2","Cc":"-","lsoriginalls":"S3-173414","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180046.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180047","title":"LS from SA WG3: Reply LS on encrypting broadcasted positioning data","source":"SA WG3","contact":"Pasi Saarinen","contact-id":70201,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks RAN WG2 for their reply and additionally for the LS on provisioning of positioning assistance data via LPPa for broadcast. SA WG3 has previously decided that the E-SMLC and UEs belonging to one subscription group share a symmetric key. Distribution of keys to UEs is left to SA WG2 with the requirement that it is done in a confidentiality protected message. SA WG3 understands that SA WG3 is expected to suggest an encryption scheme for binary blobs (octet strings) where additional metadata might be used to facilitate encryption and key selection. SA WG3 has considered two ways forward on devising a solution. - Re-use the security solution from OMA LPP-e as described in S3-173296 - Create a new solution based on the ideas presented in S3-173373 SA WG3 thinks both solutions can provide security to assistance data broadcast. To aid SA WG3 decision on the way forward SA WG3 kindly asks RAN WG2 to evaluate the two solutions based on RAN WG2 requirements. SA WG3 notes that it is","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10750,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3, SA WG2","lsoriginalls":"S3-173439","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180047.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180048","title":"LS from SA WG3: Reply LS on Early Data Transmission","source":"SA WG3","contact":"Prajwol Kumar Nakarmi","contact-id":64718,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks RAN WG2 for their LS R2-1711978 (S3-173019) on 'Early Data Transmission'. SA WG3 likes to provide following answers to the five questions addressed to SA WG3. 2) Is there any security issue on using NAS security for UL data transmission in Msg3 for control plane CIoT EPS optimisation? Answer to 2): No security issues are identified. 3) Is there any security issue on using NAS security for DL data transmission in Msg4 for control plane CIoT EPS optimisation? Answer to 3): No security issues are identified. 4) Is there any security issue on providing NCC to UE during the previous connection for the purpose of using this for UL data transmission in Msg3 for user plane CIoT EPS optimisation? Answer to 4): No security issues are identified. It is SA WG3's understanding that the said NCC would be sent in the last RRC Connection Suspend\/Release message used for suspension of the previous connection. 5) Is there any security issue on providing NCC to UE during the previous connec","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10980,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3, SA WG2, CT WG1","lsoriginalls":"S3-173472","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180048.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180049","title":"LS from SA WG3: LS on User Plane Security Policy","source":"SA WG3","contact":"Ahmad Muhanna","contact-id":73852,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 has discussed the use of UP security policy and agreed that UP security policy is communicated from SMF to the gNB for enforcement. In addition, SA WG3 understands that user plane security policy can be statically configured in SMF or downloaded dynamically during PDU session setup. For Rel-15, SA WG3 expects the user plane security policy to at least include whether UP integrity protection is required or not. Further information may be added in future releases. SA WG3 would like SA WG2 and RAN WG3 to consider the option of allowing the SMF to dynamically download the UP security policy. In addition, SA WG3 would like to ask SA WG2 and RAN WG3 the following questions. SA WG3 Questions: 1. SA WG3 would like to know whether the SMF will be able to dynamically download the user plane security policy. 2. SA WG3 would like to know whether the SMF will be able to statically configure the user plane security policy. 3. SA WG3 would like to ask whether the SMF will be able to dynamicall","secretary_remarks":"Responses drafted in S2-180056, S2-180189, S2-180410 and S2-180594. This LS was postponed. Revised at S2#126 in S2-181427.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13890,"status":"revised","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181427","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3","Cc":"CT WG3","lsoriginalls":"S3-173520","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180049.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180050","title":"LS from SA WG5: Reply to LS from CT WG4 to SA WG5 on Reply LS on 5G Charging Study Phase 1 on N4","source":"SA WG5","contact":"Robert T\u00f6rnkvist","contact-id":35172,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to inform that the study TR 32.899 on charging aspects of 5G system architecture phase 1 has now been completed, and will be sent for approval to the next plenary SA#78. The result of the study shows no new requirements compared to Sx. The current conclusion in the study has one solution using a subset of the current Sx.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14530,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2","lsoriginalls":"S5-176369","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180050.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180051","title":"LS from SA WG6: LS on Integration of northbound APIs with CAPIF","source":"SA WG6","contact":"Niranth Amogh","contact-id":39608,"tdoctype":"LS in","for":"Action","abstract":"As part of the CAPIF WID for Release 15, SA WG6 has specified the Common API Framework for 3GPP northbound APIs in TS 23.222. The primary objective of CAPIF is to specify a common northbound API framework to enable consistent development of northbound APIs across 3GPP, in particular towards the common aspects (e.g. onboarding, discover, publish, authentication, API management, etc.) that apply to any northbound API definition. TS 23.222 contains detailed specification of the common aspects of the API framework and the interactions with the CAPIF core function from both the API invoker and the API exposing function. TS 23.222 also includes an informative annex 'CAPIF relationship with network exposure aspects of 3GPP systems' that shows CAPIF relationship with SCEF\/NEF, and possible integration models.Your review of this annex, and any feedback would help us in identifying any missing aspects to achieve better alignment in integration of CAPIF with the specification(s) of northbound API","secretary_remarks":"Response drafted in S2-180659. This LS was postponed. Revised at S2#126 in S2-181428.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18930,"status":"revised","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181428","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG SA, TSG CT, SA WG4, CT WG3","lsoriginalls":"S6-171851","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180051.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180052","title":"LS from TSG SA: Response LS on voice service continuity from 5G to 2\/3G","source":"TSG SA","contact":"Gongying Gao","contact-id":65733,"tdoctype":"LS in","for":"Action","abstract":"TSG SA thanks SA WG1 for their 'LS on voice service continuity from 5G to 2\/3G'. TSG SA discussed the requirements and agreed that for some operators and scenarios there could be impact on the user experience if voice service continuity from the 5G System to UTRAN CS is not supported. TSG SA plenary has agreed that voice service continuity from 5GS to UTRAN CS should be supported in Rel-16 excluding: - Voice continuity from GERAN\/UTRAN CS to 5GS - Voice continuity from 5GS to GERAN - Video service continuity between 5GS and GERAN\/UTRAN - IP address preservation for PS service when UE moves between 5GS and GERAN\/UTRAN - Service continuity between 5GS and CDMA2000. Accordingly, TSG SA plenary approved a new work item (see attachment) to introduce corresponding Stage 1 requirements in 3GPP TS 22.261. SA plenary encourages SA WG2 to investigate solutions to support single radio voice continuity from 5GS to UTRAN. Action: Please take the above into consideration.","secretary_remarks":"Noted","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23060,"status":"noted","reservation_date":"2017-12-23 10:57:05","uploaded":"2017-12-23 10:57:29","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, SA WG3","Cc":"TSG RAN, SA WG3LI","lsoriginalls":"SP-171078","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180052.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180053","title":"LS from TSG SA: LS on URLLC","source":"TSG SA","contact":"Adrian Neal","contact-id":31227,"tdoctype":"LS in","for":"Action","abstract":"TSG SA thanks SA WG2 for their LS on QCIs for URLLC. TSG SA understands that there is urgency to determine whether the SA WG1 requirements of 1 ms latency with 1-10-6 Reliability for packets up to 256 Octets should form the basis for the definition of a URLL service characteristic, or the RAN request that one URLLC service with PDB of 1ms with reliability of 10-5 Packet error and loss rate for packets of maximum size of 32 octets is defined, in alignment with the ITU-R target for IMT-2020. TSG SA has decided that for Release 15 the KPIs for URLLC defined in TS 22.261 need to be reconciled with the expected RAN capabilities and system capabilities. TS 22.278 will also be impacted. TSG SA has identified that service requirements for EPS are in TS 22.278. TSG SA requests that SA WG1 documents the KPIs to be supported by EPS (including 5G Option 3) into TS 22.278. RAN has indicated that at the late stage of Release 15 completion, their design targets will not be able to be changed, and the","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2017-12-23 10:57:07","uploaded":"2017-12-23 10:57:29","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2","Cc":"TSG RAN, RAN WG1, RAN WG2","lsoriginalls":"SP-171079","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180053.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180054","title":"23.501: Configuration information the UE may exchange with the SMF during the lifetime of a PDU session","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: . - 5.6.10.1: add information the UE may exchange (via PCO) with the SMF during the lifetime of a PDU session","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13620,"status":"not treated","reservation_date":"2018-01-06 09:27:40","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"S2-181456, S2-181458","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180054.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180055","title":"23.501: Updates to the security clause (User Plane Security Policy)","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The SEAF functionality described in TS 33.501 [29] is supported by the AMF","secretary_remarks":"Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13960,"status":"not treated","reservation_date":"2018-01-06 09:27:40","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180055.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180056","title":"[draft] Reply LS on User Plane Security Policy","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on User Plane Security Policy","secretary_remarks":"Response to S2-180049. Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14010,"status":"not treated","reservation_date":"2018-01-06 09:27:40","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG3, CT WG3, RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180056.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180057","title":"23.502: Clean-up of the registration procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. At registration: The SUPI may only be provided by the UE in case of an Emergency Registration 2. \u00a74.2.2.2.1:transform the EN 'Aspects related to dual registration in 3GPP and non-3GPP access is FFS' into a reference to \u00a74.12 3. \u00a74.2.2.2.2 step 14: If the serving NF removal reason indicated by the UDM is Initial Registration, then the old AMF does not invoke the Namf_EventExposure_Notify but invokes the Nsmf_PDUSession_ReleaseSMContext (SUPI, PDU Session ID) service operation towards all the associated SMFs  4. \u00a74.2.2.2.2 Step 18 : clarify that 'when the AMF has changed the new AMF notifies the SMF for each PDU sessions that it has taken over the responsibility of the signalling path towards the UE: the new AMF invokes the Nsmf_PDUSession_UpdateSMContext service operation using SMF information received from the old AMF at step 5. It also indicates whether the 'PDU Session(s) is to be re-activated' 5. \u00a74.2.2.2.2  requires miscellaneous corrections \/ clarifications;","secretary_remarks":"Revised, merging S2-180641 and S2-180660, to S2-181191.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12570,"status":"revised","reservation_date":"2018-01-06 09:27:41","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"S2-181191","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180057.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180058","title":"23.726: FS_ETSUN \/ 23.726 Scope","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"pCR","for":"Approval","abstract":"FS_ETSUN \/ 23.726 Scope, references and abbreviations","secretary_remarks":"Revised in parallel session to S2-180953.","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21650,"status":"revised","reservation_date":"2018-01-06 09:27:41","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"S2-180953","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180058.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180059","title":"23.726: FS_ETSUN \/ 23.726 Skeleton","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"pCR","for":"Approval","abstract":"FS_ETSUN \/ 23.726 Skeleton \/ TOC","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21640,"status":"approved","reservation_date":"2018-01-06 09:27:41","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180059.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180060","title":"23.726: FS_ETSUN \/ 23.726 Key Issue: Support of the preservation of a PDU session while the UE moves out of an SMF service area","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"pCR","for":"Approval","abstract":"FS_ETSUN \/ 23.726 Key Issue: Support of the preservation of a PDU session while the UE moves out of an SMF service area","secretary_remarks":"Revised in parallel session, merging S2-180413, S2-180351 and S2-180551, to S2-180954.","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21680,"status":"revised","reservation_date":"2018-01-06 09:27:41","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"S2-180954","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180060.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180061","title":"23.726: FS_ETSUN \/ 23.726 Key Issue: enhance the capabilities for a UPF to be controlled by multiple SMF's","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"pCR","for":"Approval","abstract":"FS_ETSUN \/ 23.726 Key Issue: enhance the capabilities for a UPF to be controlled by multiple SMF's","secretary_remarks":"Merged into S2-180956","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21750,"status":"merged","reservation_date":"2018-01-06 09:27:41","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180061.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180062","title":"23.502: Updates to PDU session establishment procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. in \u00a7 4.3.1, the V-SMF needs to handle the PDU Type (based on the SA WG2 agreement in Reno); It also needs to handle UE addressing information (allocated IPv4 address, interface identifier) for legal reasons + Wording clarification: 'Information that is not visible to the V-SMF' refers to information that the V-SMF is to relay between N1 and N16 (and that it may store in CDR) but that the V-SMF is not assumed to process otherwise. 2. in \u00a7 4.3.2.3 and 5.2.8.2.3: clarify the HR case for DN authentication \/ authorization of the UE 3.  \u00a7 4.3.2.2.1 Step14, \u00a74.3.3.2 step 7a: In case the (R)AN rejects QFI(s) the SMF is responsible of updating the QoS rules in the UE accordingly; in case of HR roaming it is the H-SMF that is responsible of updating the QoS rules in the UE as the impossibility to set-up some QFI(s) may have impacts on QoS rules of other QFI; when RAN rejects some QFI(s), this rejection has to be propagated to H-SMF (not possible with current Call flow) + co","secretary_remarks":"Revised to S2-181171.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13570,"status":"revised","reservation_date":"2018-01-06 09:27:41","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"S2-181171","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180062.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180063","title":"23.502: Usage of NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco, Verizon?, Deutsche Telecom?","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Specify a flow ( 4.17.X (new) ) for UPF discovery using the NRF. 2. Update NRF services so as to group NFStatusSubscribe and Nnrf_NFDiscoveryRequest in the same service as they handle the same data and clients (NF using NRF to get info on other NF) 3. Update NRF service operations with UPF related information such as UPF Discovery Information.","secretary_remarks":"Revision of Postponed P-CR S2-179325 from S2#124. Confirm Sources! Revised to S2-181271.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13740,"status":"revised","reservation_date":"2018-01-06 09:27:41","uploaded":"2018-01-16 14:42:26","revisionof":"S2-179325","revisedto":"S2-181271","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180063.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180064","title":"23.502\/\u00a7 4.3.6 : case of applications that do not support application mobility","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - at the creation of the contexts related with the PDU session in the UPF: the SMF requests application\/traffic detection in mute mode (the feature exists already) - at UPF mobility : the SMF asks the (old) UPF the status of the different application\/traffic detection contexts - the SMF moves to local switching at the new UPF (DNAI of the new UPF) the application\/traffic detection contexts for which there was no on-going traffic at the old UPF - the SMF takes care that the application\/traffic detection contexts for which there was on-going traffic at the old UPF remain served by the old DNAI until the application stops o when the application stops the SMF instructs the new UPF to direct new flows of this application to the new DNAI (new application instance)","secretary_remarks":"Revised to S2-181166.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13440,"status":"revised","reservation_date":"2018-01-06 09:27:41","uploaded":"2018-01-16 15:00:51","revisionof":"S2-179331","revisedto":"S2-181166","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180064.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180065","title":"23.502: Clarifying inclusion of TAU messages in Registration Request","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies that TAU message is only included in Registration Request in case of idle mode mobility. Also reorganizes the text to clearly separate idle mode related aspects from aspects of the registration request that apply to both idle and connected mode.","secretary_remarks":"Revised in parallel session to S2-180776.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17540,"status":"revised","reservation_date":"2018-01-06 09:27:41","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"S2-180776","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180065.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180066","title":"23.502: Corrections to SMF selection","source":"Telecom Italia, ZTE, Oracle, NTT DOCOMO","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Updated labels in figures 4.3.2.2.3.2-1, 4.3.2.2.3.3-1 and 4.3.2.2.3.3-2 with the correct service operation names, where the notation 'operation_name|xxx' indicates the intended service operation and its actual semantics. - Updated the text below the figures 4.3.2.2.3.2-1, 4.3.2.2.3.3-1 and 4.3.2.2.3.3-2 with the correct service operation names (same notation as in the figures). - Added missing parameters. - Added text to steps in 3(A) and 3(B) of Option 2 to align with steps 7-8 of Option 1 for SMF selection. - Removed steps in 3(C) of Option 2 for SMF selection. - Minor editorial changes","secretary_remarks":"Revised in parallel session, merging S2-180756, to S2-181120","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13680,"status":"revised","reservation_date":"2018-01-10 07:46:39","uploaded":"2018-01-16 07:56:28","revisionof":"","revisedto":"S2-181120","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180066.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180067","title":"23.502: Correction to UE Registration","source":"Telecom Italia, ZTE, Oracle","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Fixed the optionallity of the Mapping Of Requested NSSAI in clause 4.2.2.2.2. - Updated labels in figure 4.2.2.2.3-1 with the correct service operation names, where the notation 'operation_name|xxx' indicates the intended service operation and its actual semantics. - Updated the text below the figure 4.2.2.2.3-1 with the correct service operation names (same notation as in the figure). - Fixed the misaligment between clauses 4.2.2.2.3 and 5.2.16.2.1 adding the indication if a Subscribed S-NSSAI is marked as default S-NSSAI and a reference clause 5.2.16.2.1 for other input parameters not mentioned here.","secretary_remarks":"Revised in parallel session to S2-181121","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11780,"status":"revised","reservation_date":"2018-01-10 07:52:13","uploaded":"2018-01-16 07:56:43","revisionof":"","revisedto":"S2-181121","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180067.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180068","title":"23.502: Corrections to NRF and NSSF services","source":"Telecom Italia, ZTE, Oracle","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Fixed the misaligment between clauses 4.2.2.2.3, 4.3.2.2.3, 4.17.5, 5.2.7.3 and 5.2.16. - Resolved the Editor's note on NRF as NSSF consumer. - Minor editorial change.","secretary_remarks":"Revised, merging part of S2-180666, to S2-181126.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19180,"status":"revised","reservation_date":"2018-01-10 07:56:35","uploaded":"2018-01-16 07:56:55","revisionof":"","revisedto":"S2-181126","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180068.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180069","title":"LS from TSG RAN: LS on interworking mechanisms between 5G System and legacy RATs","source":"TSG RAN","contact":"Hans Van der Veen","contact-id":62851,"tdoctype":"LS in","for":"Action","abstract":"TSG RAN plenary has identified that Rel-15 interworking mechanisms between the 5G System and legacy RATs should be clarified. To avoid possible confusion between Working Groups, TSG RAN plenary wishes to repeat its earlier decision that no interworking is expected in Rel-15 between the 5G System (5GS) and 2G (GSM)\/3G (UMTS). This means: - No NAS interworking mechanisms between 5GS and GSM\/UMTS - No Access-Stratum interworking mechanisms between GSM\/UMTS and 5G NR. - For E-UTRA deployments with 5GC (i.e. deployment Options 5 and 7), Access-Stratum interworking between GSM\/UMTS and E-UTRA continues to be possible without changes to GSM\/UMTS\/E-UTRAN specifications, enabling: - Idle mode cell reselection - Connected mode measurements to support redirection at RRC connection release, CS call release, TBF release once in idle mode - For EN-DC (i.e. deployment Option 3), legacy EPS\/E-UTRA interworking with GSM\/UMTS shall be fully supported. Note that even without AS interworking mechanisms it","secretary_remarks":"Noted","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23050,"status":"noted","reservation_date":"2018-01-10 12:13:48","uploaded":"2018-01-10 12:14:08","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, RAN WG2, RAN WG3, RAN WG4, RAN WG5, RAN WG6","Cc":"TSG SA, TSG CT","lsoriginalls":"RP-172823","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180069.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180070","title":"LS from TSG RAN: LS on the number of data bearers","source":"TSG RAN","contact":"Alexander Sayenko","contact-id":47308,"tdoctype":"LS in","for":"Information","abstract":"TSG RAN received several LS documents - from RAN WG2, CT WG1, CT WG4 and SA WG2 - regarding the feasibility of having extended number of data bearers for LTE. Following the preference from SA WG2, TSG RAN will initiate the normative work to support 15 data bearers in LTE with the target completion date of June 2018.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15","ainame":"WID on increasing the maximum number of LTE bearers (INOBEAR)","tdoc_agenda_sort_order":22520,"status":"noted","reservation_date":"2018-01-10 12:13:48","uploaded":"2018-01-10 12:14:08","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG CT","Cc":"RAN WG2, RAN WG3, SA WG2, CT WG1, CT WG4","lsoriginalls":"RP-172836","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180070.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180071","title":"23.502: NEF service for background data transfer","source":"KDDI, Convida Wireless LLC, TOYOTA ITC, Huawei","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update of NEF service for background data transfer. Re-wrote the interaction between the NEF and AF as a service.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19280,"status":"endorsed","reservation_date":"2018-01-10 16:08:23","uploaded":"2018-01-16 13:03:13","revisionof":"","revisedto":"S2-181502, S2-181504","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180071.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180072","title":"23.502: Update of NEF server for PFD management","source":"KDDI, China Unicom","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update of NEF service for PFD management. Re-wrote the interaction between the NEF and AF as a service. Added the Transaction Reference ID for T8 interface.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19320,"status":"endorsed","reservation_date":"2018-01-10 16:29:34","uploaded":"2018-01-16 12:59:22","revisionof":"","revisedto":"S2-181503, S2-181505","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180072.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180073","title":"Phase-2 study on Network Slicing","source":"ZTE, Oracle, Telecom Italia, ETRI, NTT DoCoMo, Nokia, Nokia Shanghai Bell","contact":"Tricci So","contact-id":44974,"tdoctype":"SID new","for":"Approval","abstract":"In Rel-15, there are several open issues which were agreed to be deferred from Rel-15. In addition, SA WG1 is studying additional requirements to support different business role models for network slicing for Rel-16 in FS_BMNS. The intent of the study is to consolidate these outstanding open issues and possible new requirements from FS_BMNS into one common study on Network Slicing in Rel-16.","secretary_remarks":"This was postponed.","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23270,"status":"postponed","reservation_date":"2018-01-11 04:10:42","uploaded":"2018-01-16 08:02:47","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_125_Gothenburg\/Docs\/S2-180073.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180074","title":"Discussion paper for 5G Phase-2 Network Slicing study","source":"ZTE TX Inc., Oracle, Telecom Italia, ETRI, NTT DoCoMo","contact":"Tricci So","contact-id":44974,"tdoctype":"discussion","for":"Information","abstract":"This paper provides the justifications for the new study items to work on the open issues on network slicing that has not been fully addressed in Rel-15 and also to address the upcoming requirements from SA WG1 for network slicing enhancement to support different business role models.","secretary_remarks":"Not Handled","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23260,"status":"not treated","reservation_date":"2018-01-11 04:16:12","uploaded":"2018-01-16 08:02:47","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_125_Gothenburg\/Docs\/S2-180074.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180075","title":"23.501: Update Establishing a PDU session in a Network Slice in various scenario","source":"China Telecommunications","contact":"Peirong Xie","contact-id":58969,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: This contribution propose to update Establishing a PDU session in a Network Slice in various scenario.","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24090,"status":"withdrawn","reservation_date":"2018-01-11 08:35:34","uploaded":"2018-01-11 09:04:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180075.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180076","title":"23.503: BSF storing the selected PCF Address in UDR Structured data should be optional.","source":"Cisco Systems","contact":"Ravi Shekhar","contact-id":71185,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifyed that storage of binding information in UDR should be optional for BSF.","secretary_remarks":"Merged into S2-181005","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15570,"status":"merged","reservation_date":"2018-01-11 09:02:48","uploaded":"2018-01-16 10:41:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"PCC"}],"crnumber":"","crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180076.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180077","title":"23.501: Correction of E-UTRA - 5GC procedures","source":"Samsung","contact":"Andy Bennett","contact-id":70253,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In sub-clause 5.17.1.1, NOTE1 is removed to avoid a misleading statement that a UE shall always select the 5GC NAS procedure when camping on a E-UTRA cell connected to 5GC.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17420,"status":"postponed","reservation_date":"2018-01-11 09:39:37","uploaded":"2018-01-16 12:56:19","revisionof":"","revisedto":"S2-182096","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180077.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180078","title":"23.501: Moving Network Analytics functionality into 23.501","source":"Ericsson, KDDI, AT&T","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding the network analytics architecture in clause 6.2.9 and moving NWDAF description into 23.501.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15970,"status":"not treated","reservation_date":"2018-01-11 15:47:34","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-181643","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180078.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180079","title":"23.502: Moving Network Analytics functionality into 23.501","source":"Ericsson, AT&T","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding the Analytics Type ID and Context ID and then define that in Rel-15 Analytics Type ID corresponds to Load Level and the Context ID corresponds to Network Slice Instance. Only one Analytics Type ID is defined. Defining one Nwdaf service that includes subscribe\/notify and request\/reponse.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15980,"status":"not treated","reservation_date":"2018-01-11 15:47:34","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-181647","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180079.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180080","title":"23.503: Moving Network Analytics functionality into 23.501","source":"Ericsson, KDDI, AT&T","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Moving NWDAF to 23.501. Include NWDAF in the LBO architecture. Define the feature for policy control using analytics.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15990,"status":"not treated","reservation_date":"2018-01-11 15:47:34","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-181646","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180080.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180081","title":"23.501: Resource reservation for services sharing priority","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update clause 5.22 to indicate that the service layer can provide instructions on how to perform pre-emption of media flows when no resources are available.","secretary_remarks":"Revised in parallel session to S2-180995.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15420,"status":"revised","reservation_date":"2018-01-11 15:47:34","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-180995","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180081.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180082","title":"23.503: Resource reservation for services sharing priority","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: PCF functional description of resource reservation for service sharing priority is updated to align with the functional description of this feature in TS 23.203.","secretary_remarks":"Revised in parallel session to S2-180996.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15440,"status":"revised","reservation_date":"2018-01-11 15:47:34","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-180996","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180082.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180083","title":"23.715: Update to Architectural Assumptions","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes an update to architectural assumptions to scope PARLOS to limit the solutions space.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22640,"status":"noted","reservation_date":"2018-01-11 15:48:48","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180083.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180084","title":"23.715: Update to Key issue IMS#1","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes an update to key issue IMS#1 to align more with the SA WG1 requirements and TR 22820 issued by SA WG1 in support of RLOS services","secretary_remarks":"Revised in parallel session to S2-181002.","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22670,"status":"revised","reservation_date":"2018-01-11 15:48:48","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-181002","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180084.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180085","title":"23.715: Update to Key issue EPC#3","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This contribution clarifies the scope of support for unauthenticated UEs for Key issue EPC#3 to access RLOS services only.","secretary_remarks":"Revised in parallel session to S2-181003.","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22690,"status":"revised","reservation_date":"2018-01-11 15:48:48","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-181003","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180085.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180086","title":"23.715: Removal of Key issue EPC#5","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes removing key issue EPC#5 since this aspect is more of an implementation, as opposed to a key issue, for restricting access to RLOS","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22710,"status":"approved","reservation_date":"2018-01-11 15:48:48","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180086.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180087","title":"23.715: Solution to Key issue #EPC-1","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a solution to key issue #EPC-1.","secretary_remarks":"Not Handled","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22770,"status":"not treated","reservation_date":"2018-01-11 15:48:48","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180087.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180088","title":"23.715: Solution to Key issue #EPC-3","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a solution to key issue #EPC-3","secretary_remarks":"Not Handled","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22780,"status":"not treated","reservation_date":"2018-01-11 15:48:48","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180088.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180089","title":"23.715: Solution to Key issue IMS-1, IMS-2, and IMS-3","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a solution to key issue #IMS-1, #IMS-2, and #IMS-3","secretary_remarks":"Not Handled","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22800,"status":"not treated","reservation_date":"2018-01-11 15:48:48","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180089.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180090","title":"Inclusion of the Ms reference point","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the Ms reference point to 23.002","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":16,"ainumber":"6.4","ainame":"Rel-15 IMS-Related Maintenance- essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11190,"status":"agreed","reservation_date":"2018-01-11 15:48:48","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.002,"crspecversion":"14.1.0","workitem":[{"winame":"TEI15"}],"crnumber":303.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180113","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180090.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180091","title":"23.502: Editorial correction to section 4.12.8","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Consolidate steps 4 and 5 in step 3 to match the corresponding figure","secretary_remarks":"Revised in parallel session to S2-180928.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18340,"status":"revised","reservation_date":"2018-01-11 15:48:49","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-180928","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180091.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180092","title":"23.502: Update to Registration Procedure to generalize AMF handling of a registration associated with any access type","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Make the text flexible enough to deal with various accesses","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18360,"status":"noted","reservation_date":"2018-01-11 15:48:49","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180092.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180093","title":"23.502: 23.501 handling of Location Update in case of mobility from 5GS to EPS.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the processsing of Location Update procedure during mobility from 5GS to EPS as described above.","secretary_remarks":"Not Handled","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17990,"status":"not treated","reservation_date":"2018-01-11 15:48:49","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180093.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180094","title":"23.502 handling of Location Update in case of mobility from 5GS to EPS.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove the MME inclusion of the Single-Registration-Indication when Update Location is sent to HSS +UDM. Update the processsing of Location Update procedure during mobility from 5GS to EPS accordingly and as described above.","secretary_remarks":"Merged into S2-180785","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18000,"status":"merged","reservation_date":"2018-01-11 15:48:49","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180094.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180095","title":"23.794: Architectural Assumptions","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This document proposes architectural assumptions for FS_eIMS5G","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22260,"status":"noted","reservation_date":"2018-01-11 15:48:49","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180095.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180096","title":"23.794: New Key issue : Cx Replacement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This document proposes a new key issue for FS_eIMS5G.","secretary_remarks":"Revised in parallel session to S2-180937.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22380,"status":"revised","reservation_date":"2018-01-11 15:48:49","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-180937","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180096.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180097","title":"23.794: Key Issue on IMS use of NRF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This document proposes a new key issue for FS_eIMS5G","secretary_remarks":"Revised in parallel session to S2-180939.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22410,"status":"revised","reservation_date":"2018-01-11 15:48:49","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-180939","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180097.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180098","title":"23.794: New Key Issue : Sh Replacement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This document proposes a new key issue for FS_eIMS5G","secretary_remarks":"Revised in parallel session to S2-180940.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22430,"status":"revised","reservation_date":"2018-01-11 15:48:49","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-180940","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180098.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180099","title":"23.502: Alignment of terminology and general cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following changes are done:  - Reqistration Request\/Accept used as NAS message names for Registration procedure  - Figure 4.2.3.2-1: NAS: Service Request changed to Service Request in step 1 and 2.  - Service Request used as NAS message name for Service Request procedure.  - Changed format of underlined text  - Some N11 message still not explicitly mentioned.  - RAN changed to NG-RAN or (R)AN - Figure 4.3.5.7-1: RAN changed to (R)AN - Figure 4.12.8-1 RAN changed to NG-RAN - Except for e.g. Master and Secondary RAN Nodes  - Use CN Tunnel Info and AN Tunnel Info as Ies for N3 tunnel information  - Remove misplaced heading in EN.  - Corrected editorial issue in title of clause 4.16.2.1.  - Figure 4.3.2.2.1-1: Namf changed to Nsmf in steps 3a and 5.  - Some corrections of a SMF to an SMF, and an UPF to a UPF.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11450,"status":"approved","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 14:55:57","revisionof":"","revisedto":"S2-181633","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180099.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180100","title":"23.502 EN resolution","source":"Ericsson (Rapporteur)","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This paper summarizes and proposes a way forward for the remaining ENs in TS 23.502","secretary_remarks":"This proposal for handling editor's notes was endorsed in parallel session.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11440,"status":"endorsed","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 14:35:13","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_125_Gothenburg\/Docs\/S2-180100.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180101","title":"23.502: Resolution of ENs in Connection, Registration and Mobility Management procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following ENs are resolved: Editor's note: Aspects related to dual registration in 3GPP and non-3GPP access is FFS. Aspects for dual registration have been described in the registration call flow as well e.g. in 4.12.8. It is proposed to remove the EN and add a reference from 4.2.2.2.1 to 4.12.8.  Editor's note: It is FFS if HO attach indication is to be added. So far no need for handover indication been identified e.g. same AMF used for 3GPP and non-3GPP access. It is proposed to remove the EN.  Editor's note: It is FFS how UE Radio capabilities are provided.  Different cases exist, e.g. for Initial Registration and when the AMF does not have any UE Radio Capability stored, then the AMF should obtain the UE Radio Capability information by sending the N2 message (INITIAL CONTEXT SETUP REQUEST without UE Radio Capability information included to the NG-RAN. This triggers the NG-RAN to request the UE Radio Capability from the UE and upload it to the AMF in the N2 in","secretary_remarks":"Revised to S2-181192.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12600,"status":"revised","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 14:52:43","revisionof":"","revisedto":"S2-181192","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180101.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180102","title":"23.501: Slice selection cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The S-NSSAIs used by the UE when moving from EPS to 5GS are clarified.","secretary_remarks":"Revised to S2-181161.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12000,"status":"revised","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-181161","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180102.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180103","title":"23.502: Slice selection cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following changes are done:  - Clarifying what the S-NSSAIs relate to e.g. PLMN  -Adding Mapping Of Allowed NSSAI to the UE MM Context table  - The S-NSSAI corresponding to the PDU Session stored in the UE Context is the one valid for the serving PLMN (i.e. the same as used in the Allowed NSSAI).  - Adding S-NSSAI and optionally NSI ID as IEs for the Nnwdaf_EventsSubscription service  - Adding DNN sent back to the UE at PDU Session Establishment  - Removing S-NSSAI sent to the UE at PDU Session Establishment","secretary_remarks":"Revised, merging S2-180712 and S2-180707, to S2-181157.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11850,"status":"revised","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-181157","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180103.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180104","title":"23.501: Idle and connected state terminology cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following terminology is applied:  - Idle mode and Connected mode changed to idle state and connected state, while using idle mode mobility and connected mode mobility. Some additional cleanup e.g. usage of dash and 'CM-'.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12680,"status":"approved","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-181617","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180104.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180105","title":"23.502: Idle and connected state terminology cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following terminology is applied:  - Idle mode and Connected mode changed to idle state and connected state, while using idle mode mobility and connected mode mobility. Some additional cleanup e.g. usage of dash and 'CM-'.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12690,"status":"approved","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-181629","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180105.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180106","title":"Network slicing and Interworking with EPS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Approval","abstract":"Investigates current and alternative solutions for handover from EPS to a 5GS network slicing supporting network, and intra-5GS inter-PLMN HO. An evaluation and comparison of the solutions is presented. Proposal for a way forward is given.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12090,"status":"not treated","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 13:18:57","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_125_Gothenburg\/Docs\/S2-180106.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180107","title":"23.501: Network slicing and Interworking with EPS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The AMF initially selected by the MME,  a) selects a network slice supporting target AMF based on information recieved in a transparent container from the UE via the MME or alternatively resolving the S-NSSAI values from the SMF, and  b) relays the initial signalling from the source MME to the target AMF. Target AMF responds directly to the source MME.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12100,"status":"not treated","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180107.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180108","title":"23.502: Network slicing and Interworking with EPS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The AMF initially selected by the MME, selects a network slice supporting target AMF and relays the initial signalling from the source MME to the target AMF. Target AMF responds directly to the source MME.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12120,"status":"not treated","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180108.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180109","title":"23.401: Network slicing and Interworking with EPS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The UE shall provide the serving MME with a transparent container including a pair of 'EPS Bearer ID for the default bearer of the PDN connection', and associated S-NSSAI per each created PDN connection. This shall be done at establishment of a new PDN connection and whenever the UE registers to a new MME. At handover to a slice supporting target 5GS the MME may include the transparent container in the Forward Relocation Request message.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12140,"status":"not treated","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180109.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180110","title":"23.501: Slice and AMF selection at HO procedure","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The AMF initially selected at HO, selects a network slice supporting target AMF and relays the initial signalling from the source AMF to the target AMF. Target AMF responds directly to the source AMF.","secretary_remarks":"Revised to S2-181160.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11970,"status":"revised","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-181160","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180110.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180111","title":"23.502: Slice and AMF selection at HO procedure","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The AMF initially selected at HO, selects a network slice supporting target AMF and relays the initial signalling from the source AMF to the target AMF. Target AMF responds directly to the source AMF.","secretary_remarks":"This was postponed in parallel session.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11990,"status":"postponed","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180111.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180112","title":"23.503: Correction for background data transfer","source":"KDDI","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change to Npcf_BDTPolicyControl_Get","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15710,"status":"not treated","reservation_date":"2018-01-11 17:18:37","uploaded":"2018-01-16 13:08:52","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180112.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180113","title":"23.503: Use NSI ID in TS 23.503","source":"KDDI","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN:","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23970,"status":"withdrawn","reservation_date":"2018-01-11 17:24:06","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180114","title":"NEF northbound API development in 5GC","source":"AT&T GNS Belgium SPRL","contact":"James Hu","contact-id":59481,"tdoctype":"discussion","for":"Discussion","abstract":"Discussion on how to work and organize Northbound NEF APIs for 5G","secretary_remarks":"Noted","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23310,"status":"noted","reservation_date":"2018-01-11 19:55:42","uploaded":"2018-01-12 18:02:46","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_125_Gothenburg\/Docs\/S2-180114.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180115","title":"Requirements on EPC and 5GC Identifiers","source":"Cisco","contact":"Irfan Ali","contact-id":74090,"tdoctype":"discussion","for":"Agreement","abstract":"Discussing the requirements for the identifiers","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12300,"status":"noted","reservation_date":"2018-01-12 02:02:46","uploaded":"2018-01-16 01:34:49","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_125_Gothenburg\/Docs\/S2-180115.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180116","title":"23.501: Requirements on EPC and 5GC Identifiers","source":"Cisco","contact":"Irfan Ali","contact-id":74090,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Captures the requirements on EPC and 5GC Identifiers.","secretary_remarks":"Not Handled","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12310,"status":"not treated","reservation_date":"2018-01-12 02:02:46","uploaded":"2018-01-16 01:34:49","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180116.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180117","title":"[draft] Reply LS on details of network identifiers","source":"Cisco","contact":"Irfan Ali","contact-id":74090,"tdoctype":"LS out","for":"Approval","abstract":"Replies to RAN WG2 question that there is no collision in paging identities when eNB is connected to both EPC and 5GC","secretary_remarks":"Not Handled","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12320,"status":"not treated","reservation_date":"2018-01-12 02:02:46","uploaded":"2018-01-16 01:34:49","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180117.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180118","title":"23.501: Update Establishing a PDU session in a Network Slice in various scenario","source":"China Telecom,Huawei","contact":"Peirong Xie","contact-id":58969,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution propose to update Establishing a PDU session in a Network Slice in various scenario.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12160,"status":"not treated","reservation_date":"2018-01-12 02:51:49","uploaded":"2018-01-12 02:55:50","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180118.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180119","title":"23.502: MME and AMF registration in HSS+UDM","source":"Cisco","contact":"Irfan Ali","contact-id":74090,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: For no-N26 procedures, the MME and AMF explicitly includes 'Dual MME\/AMF registration indicator' to the HSS+UDM.  If HSS does not support dual MME\/AMF registration it does not indicate support of this in the ULA 'supported features' AVP. If this indication is not present the MME or AMF knows that dual-registration is not allowed and should not provide the 'no-N26 support' indication to the UE.","secretary_remarks":"Revised in parallel session, merging S2-180094, to S2-180785.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17960,"status":"revised","reservation_date":"2018-01-12 04:34:16","uploaded":"2018-01-16 01:34:49","revisionof":"","revisedto":"S2-180785","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180119.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180120","title":"23.793: Key Issue update for Traffic Splitting over Multi-access","source":"ZTE, Oracle","contact":"Tricci So","contact-id":44974,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes update to the key issue studying the traffic splitting over multi-access in ATSSS by referring to the real-life use case of MPTCP support by iOS.","secretary_remarks":"Revised in parallel session to S2-180984.","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20430,"status":"revised","reservation_date":"2018-01-12 05:09:17","uploaded":"2018-01-16 08:06:16","revisionof":"","revisedto":"S2-180984","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180120.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180121","title":"23.501: AMF initiated DNN based congestion control","source":"Vivo","contact":"Yanchao Kang","contact-id":72631,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Upon receipt of the NAS Transport Error message including a back-off timer and the associated DNN, the UE will not send any NAS SM signalling for the specific DNN","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12490,"status":"noted","reservation_date":"2018-01-12 07:40:53","uploaded":"2018-01-16 08:55:21","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180121.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180122","title":"23.501: Clarification on definition of Session Continuity","source":"Huawei","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: Modify the definition of Session Continulity to support mobility between 5GS and EPS.","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23930,"status":"withdrawn","reservation_date":"2018-01-12 09:24:48","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180123","title":"23.502: Clarifcation on IP preservation continuity w\/o N26","source":"Huawei","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: Clarify an indication which indicates that the PDU session supports IP address preservation should be send to UE for the without N26 interface scenrio.","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23940,"status":"withdrawn","reservation_date":"2018-01-12 09:24:48","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180124","title":"23.502: Update the SM procedure for interworking","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the descripiton for providing the PDN connection parameters or EPS QoS parameters to UE in corresponding clauses.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17920,"status":"postponed","reservation_date":"2018-01-12 09:24:48","uploaded":"2018-01-16 11:38:48","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180124.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180125","title":"23.501: Generating EPS PDN Connection parameters from 5G PDU Session parameters","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Proposes a new annex about how to generate the EPS PDN connection parameters from the 5G PDU Session parameters in PGW-C+SMF.","secretary_remarks":"Revised in parallel session to S2-180796.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17930,"status":"revised","reservation_date":"2018-01-12 09:24:48","uploaded":"2018-01-16 11:38:48","revisionof":"","revisedto":"S2-180796","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180125.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180126","title":"23.502: N4 reporting for PDU Session Inactivity","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Adding a reporting trigger in N4 reporting procedure for PDU Session Inactivity. 2. Editorial change:PDU Session has no data activity->PDU Session has no data transfer","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13670,"status":"not treated","reservation_date":"2018-01-12 09:24:48","uploaded":"2018-01-16 11:38:48","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180126.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180127","title":"23.501: Clarification on Allowed NSSAI when registered over several accesses simultaneously","source":"Huawei, Hisilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarify the behaviour of the UE when registering over several accesses. When UE receives the Allowed NSSAI from AMF as part of the registration over one access, UE treats the Allowed NSSAI applicable to all accesses it is currently registered to. 2. Clarify that some Network Slices can be restricted to certain accesses.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11590,"status":"not treated","reservation_date":"2018-01-12 09:24:48","uploaded":"2018-01-16 11:38:48","revisionof":"","revisedto":"S2-182181","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180127.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180128","title":"23.501: Editorial Changes on Network Slice to Support Multiple Access Networks","source":"Huawei, Hisilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Some editorial changes to support Non-3GPP.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11460,"status":"not treated","reservation_date":"2018-01-12 09:24:48","uploaded":"2018-01-16 11:38:48","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180128.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180129","title":"23.503: Description of components in URSP","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Filling the description of the components. 2. Multiple Route Selection Descriptors in one URSP rule.  3. Non-Seamless Offload indication doesn't coexist with other component.","secretary_remarks":"Revised in parallel session, merging S2-180404, to S2-180966.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14610,"status":"revised","reservation_date":"2018-01-12 09:24:48","uploaded":"2018-01-16 11:38:48","revisionof":"","revisedto":"S2-180966","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180129.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180130","title":"23.503: Additional PDU Session Type in Route Selection Descriptor","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the PDU Type as a component in the URSP rule.","secretary_remarks":"Revised in parallel session to S2-180967.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14640,"status":"revised","reservation_date":"2018-01-12 09:24:48","uploaded":"2018-01-16 11:38:48","revisionof":"","revisedto":"S2-180967","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180130.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180131","title":"23.502: Improvements on the specification of the subscription to Network Exposure","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. \u00a7 4.15.1: adding target UE in the table 2. 5.2.2.3.2: add 'any UE' as target of AMF event subscription + Notification target address provided by Consumer NF \/ Subscription Correlation ID provided by Event Provider 3. Clarifying Notification target address and Subscription Correlation ID throughout all Event related services  4. Splitting up throughout all Nxxx Subscription services between Event Id (Mandatory, defined as part of the Nxxx service) and Event Filter information (Maximum number of reports, \u2026) where reference to 4.15.1 is made","secretary_remarks":"Revised, merging S2-180255, S2-180643, S2-180152 and S2-180151, to S2-181125.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19120,"status":"revised","reservation_date":"2018-01-12 09:35:56","uploaded":"2018-01-16 14:42:26","revisionof":"","revisedto":"S2-181125","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180131.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180132","title":"23.503: Remove EN related with Session binding","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. \u00a7 6.1.3.2.2: Session Binding applies only for PDU Sessions of IP type 2. \u00a7 6.1.1.2: remove the EN and add that S-NSSAI is part of the data used for session binding 3. Clarifications and Editorials:.","secretary_remarks":"Revised in parallel session, merging S2-180076, to S2-181005.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15630,"status":"revised","reservation_date":"2018-01-12 09:35:56","uploaded":"2018-01-16 09:24:47","revisionof":"","revisedto":"S2-181005","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180132.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180133","title":"23.502: Npcf_Policy Authorization Create Service Definition Correction","source":"Cisco Systems, Inc","contact":"Ravi Shekhar","contact-id":71185,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the description of the Npcf_PolicyAuthorization_Create service operation to include  a list of information elements in the optional output section","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15920,"status":"not treated","reservation_date":"2018-01-12 10:48:41","uploaded":"2018-01-16 10:50:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180133.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180134","title":"23.502: Npcf_Policy Authorization Delete Service Definition Correction","source":"Cisco Systems, Inc","contact":"Ravi Shekhar","contact-id":71185,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the description of the Npcf_PolicyAuthorization_Delete service operation to include a list of information elements in the optional output section.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15930,"status":"not treated","reservation_date":"2018-01-12 10:52:21","uploaded":"2018-01-16 10:50:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180134.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180135","title":"23.502: Npcf_SMPolicyControl -Addition of Missing Policy Service Update","source":"Cisco Systems","contact":"Ravi Shekhar","contact-id":71185,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: Defines a new service for PCF -initiated SMpolicy Update triggered by Npcf_Policy Authorization Create\/Update Services","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23910,"status":"withdrawn","reservation_date":"2018-01-12 10:55:08","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180136","title":"23.731: Key Issue: Reduce the UE overhead for LCS","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue to consider to reduce the UE overhead for LCS","secretary_remarks":"Revised in parallel session to S2-180909.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22070,"status":"revised","reservation_date":"2018-01-12 11:16:43","uploaded":"2018-01-16 07:13:51","revisionof":"","revisedto":"S2-180909","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180136.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180137","title":"EBI allocation in the NW supporting INOBEAR","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"discussion","for":"Agreement","abstract":"This paper proposes a interwoking issue: when the non-extended EBI runs out, how to gurantee the new coming high priority service can be switched to the NW not supporting INOBEAR w\/o impact the existing bearer in the NW supporting INOBEAR.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15","ainame":"WID on increasing the maximum number of LTE bearers (INOBEAR)","tdoc_agenda_sort_order":22580,"status":"noted","reservation_date":"2018-01-12 11:16:43","uploaded":"2018-01-16 07:13:51","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_125_Gothenburg\/Docs\/S2-180137.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180138","title":"23.501: Correction to Providing AF request to multiple PCFs","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This paper makes clarificaiton and correction in clauses 5.6.7 and 6.3.7.2 so that the solution in 6.3.7.2 is applicable to AF requests that target non-specific PDU Sessions of a single UE.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15740,"status":"not treated","reservation_date":"2018-01-12 16:24:15","uploaded":"2018-01-16 02:31:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180138.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180139","title":"23.501: Editorial modification to AF influence on traffic routing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This paper proposes to clean up the notes and correct wordings for consistency and clarificaiton.","secretary_remarks":"Revised to S2-181167.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13460,"status":"revised","reservation_date":"2018-01-12 16:24:15","uploaded":"2018-01-16 02:31:56","revisionof":"","revisedto":"S2-181167","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180139.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180140","title":"23.724: FS_CIoT_5G Key Issue: Support Multiple QoS Flows for Unstructured PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue to study solutions to support multiple QoS flows in one Unstructured PDU Session.","secretary_remarks":"Not Handled","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21160,"status":"not treated","reservation_date":"2018-01-12 16:27:55","uploaded":"2018-01-16 14:09:42","revisionof":"","revisedto":"S2-181955","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180140.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180141","title":"23.791: FS_eNA Key Issue: NWDA-Assisted Traffic Routing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue to study solutions to support traffic routing using statistical information from NWDAF.","secretary_remarks":"Revised in parallel session to S2-180864.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21530,"status":"revised","reservation_date":"2018-01-12 16:27:55","uploaded":"2018-01-16 14:09:42","revisionof":"","revisedto":"S2-180864","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180141.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180142","title":"23.791: FS_eNA Key Issue: Network Information Exposure to UEs","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue to study solutions utilizing NWDA-assisted information to support UE achieving better QoS experience and improve network resource utilization.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21570,"status":"postponed","reservation_date":"2018-01-12 16:27:55","uploaded":"2018-01-16 14:09:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180142.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180143","title":"Study proposal for 5G multicast-broadcast services","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Discussion","abstract":"This slide set provides justification for the SI proposal on 5G multicast-broadcast services","secretary_remarks":"Not Handled","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23150,"status":"not treated","reservation_date":"2018-01-12 16:30:18","uploaded":"2018-01-16 13:57:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180143.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180144","title":"Study of architectural enhancements for 5G Multicast-Broadcast Services","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"SID new","for":"Approval","abstract":"This proposes a new SI for 5G mutlicast\/broadcast services","secretary_remarks":"Revision of postponed S2-178888 from S2#124. This was left for off-line discussion for a further proposal to a future meeting. This was then postponed","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23160,"status":"postponed","reservation_date":"2018-01-12 16:30:18","uploaded":"2018-01-16 13:57:23","revisionof":"S2-178888","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180144.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180145","title":"23.786: New Key Issue: eV2X QoS Support","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue for eV2XARC SI, to investigate the necessary QoS enhancements to support eV2X requirements","secretary_remarks":"Revised in parallel session, merging part of S2-180478 to S2-181079.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19600,"status":"revised","reservation_date":"2018-01-12 16:30:18","uploaded":"2018-01-16 13:57:23","revisionof":"","revisedto":"S2-181079","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180145.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180146","title":"23.786: Solution for eV2X QoS Support Key Issue","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution addresses the first aspect of the proposed Key Issue on eV2X QoS Support (i.e., investigate whether or not the current 5G QoS characteristics defined in TS 23.501 are sufficient to represent the eV2X QoS profiles)","secretary_remarks":"Not Handled","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19840,"status":"not treated","reservation_date":"2018-01-12 16:30:18","uploaded":"2018-01-16 13:57:23","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180146.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180147","title":"23.786: New Key Issue: Network Slicing for eV2X","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue for eV2XARC SI, to clarify the relationship within 5GS among eV2X services, the required supporting features and Network Slicing","secretary_remarks":"Revised in parallel session to S2-181082.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19690,"status":"revised","reservation_date":"2018-01-12 16:30:18","uploaded":"2018-01-16 13:57:23","revisionof":"","revisedto":"S2-181082","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180147.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180148","title":"23.786: Key issue_eV2X message transmission & reception for V2V\/V2P Service","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contributions proposes a key issue to identify and evaluate how to support the eV2X message transmission & reception in the 5G system","secretary_remarks":"Revised in parallel session to S2-181085.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19770,"status":"revised","reservation_date":"2018-01-12 16:30:18","uploaded":"2018-01-16 13:57:23","revisionof":"","revisedto":"S2-181085","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180148.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180149","title":"Discussion on the Reliability for Rel-15 eV2X","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Approval","abstract":"RAN WG2 asked SA WG2 about the possibility for the AS layer to obtain reliability information associated to V2X packets to be transmitted over the PC5, and to provide feedback on how that can be achieved. This contribution discusses possible way forwards.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11140,"status":"noted","reservation_date":"2018-01-12 16:30:18","uploaded":"2018-01-16 13:57:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180149.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180150","title":"23.502: Correction to Application Triggering Procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The Application Trigger procedure is corrected to let NEF query UDM instead of UDR. The interaction with UDM is a 2 step process. To get the SMSF address, Nudm_UECM_Get is used. To get the GPSI to SUPI mapping Nudm_SDM_Get is used. Additionally changes to Nudm_UECM_Get and Nudm_SDM_Get service operations are also specified to align with the changes done in Application Trigger procedure.","secretary_remarks":"Merged into S2-181131","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19390,"status":"merged","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180150.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180151","title":"23.502: Correction to Event Filter","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The mention of parameters like maximum number of reports, maximum duration of reporting etc are moved to be along with Event filter parameter mentioning with a reference to clause 4.15.1","secretary_remarks":"Merged into S2-181125.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19250,"status":"merged","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180151.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180152","title":"23.502: Clarification on Network Capability Exposure for Analytics","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to remove this procedure from the specification.","secretary_remarks":"Merged into S2-181125.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19170,"status":"merged","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180152.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180153","title":"23.502: Correction to RAN Initiated QoS Flow Mobility Procedure for Dual Connectivity","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The N11 messages in clause 4.14.1 are replaced with service operations.","secretary_remarks":"Revised to S2-181169.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13520,"status":"revised","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"S2-181169","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180153.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180154","title":"23.501: Clarification on Area of Interest for Presence Area Reporting","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify how area of interest can be used for subscribing and getting notified of UE location change into or out of a Presence Reporting Area. The proposal is as follows 1. When PCF subscribes to SMF event notification, the PCF provides PRA ID(s) or a UE specific PRA list (e.g list of TAs). 2. SMF subscribes to AMF for UE location change event notification on area of interest by providing the PRA ID and\/or the list of TAs \/ cell IDs as the area of interest. 3. For core-network predefined PRA, the configuration of the PRA ID to list of TAs \/ cell IDs \/ NG-RAN node IDs is at the AMF. Use of priorities and overload control of PRA reporting by setting some low priority PRAs as inactive, is done at the AMF.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15870,"status":"postponed","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180154.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180155","title":"23.502: Clarification on Use of List of Parameter Values to Match in Event Filters","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarify how 'list of parameter values to match' in the Event Filter can be used for some example events like area of interest, location change notification and AN type change notification. 2. For the UE reachability status event the words 'along with optional list of sessions to be activated' is removed. The reason is this was added during SA WG2#121 during which time Service Request call flow modelling was discussed through use of Namf_EventExposure_Notify. However in later meetings it has been agreed to use Nsmf_PDUSession_UpdateSMContext for this purpose. Hence there is no need to notify 'optional list of sessions to be activated' when UE becomes reachable.","secretary_remarks":"Revised to S2-181128.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19260,"status":"revised","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"S2-181128","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180155.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180156","title":"23.503: Resolve the Editor's Note on Presence Reporting Area","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Remove the Editor's Note on PRA and Area of Interest relation. 2. Add a clarification with reference to TS 23.502 \/ TS 23.501 on how area of interest is used in relation to PRA. 3. Normative text in NOTE2 is moved as normative paragraph. 4. Move the text related to event triggers from AMF to PCF that are not session related from clause 6.1.3.5 to clause 6.1.2.X","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15880,"status":"postponed","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180156.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180157","title":"[DRAFT] LS response on Indication of preferred CIoT network behaviour","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Alignment of CIoT Preferred Network Behaviour with stage 3","secretary_remarks":"Response to S2-180028. Not Handled","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10900,"status":"not treated","reservation_date":"2018-01-12 17:57:57","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180157.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180158","title":"Alignment of CIoT Preferred Network Behavior with stage 3","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updating one of the bullets in the Preferred and Supported Network Behaviour information.","secretary_remarks":"Not Handled","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10890,"status":"not treated","reservation_date":"2018-01-12 17:57:57","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"},{"winame":"CIoT"}],"crnumber":3377.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180158.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180159","title":"23.724: Architectural assumptions","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Architectural assumptions and principles for this study","secretary_remarks":"Revised in parallel session to S2-180825.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20640,"status":"revised","reservation_date":"2018-01-12 17:57:58","uploaded":"2018-01-16 13:32:49","revisionof":"","revisedto":"S2-180825","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180159.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180160","title":"23.724: Adding small data infrequent communication key issue","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Small data infrequent communication key issue","secretary_remarks":"Merged into S2-180826","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20710,"status":"merged","reservation_date":"2018-01-12 17:57:58","uploaded":"2018-01-16 13:53:15","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180160.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180161","title":"23.724: Adding small data frequent communication key issue","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Small data frequent communication key issue","secretary_remarks":"Revised in parallel session, merging S2-180453, to S2-180827.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20730,"status":"revised","reservation_date":"2018-01-12 17:57:58","uploaded":"2018-01-16 13:53:15","revisionof":"","revisedto":"S2-180827","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180161.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180162","title":"23.724: Adding High latency key issue","source":"Ericsson, CATT, Convida Wireless, Samsung","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"High latency key issue","secretary_remarks":"Revised in parallel session, merging S2-180327, to S2-180828.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20800,"status":"revised","reservation_date":"2018-01-12 17:57:58","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"S2-180828","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180162.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180163","title":"23.502 Clarification of mobility procedure from EPS to 5GS without N26 interface","source":"Orange","contact":"Thouraya Toukabri","contact-id":66374,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: addition that Notify message MME > HSS shall be sent when when the subscription data indicates that the user is allowed use 5G as a RAT type in order to handle EPS to 5GS handover.","secretary_remarks":"Revised in parallel session to S2-180792.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18100,"status":"revised","reservation_date":"2018-01-12 18:14:15","uploaded":"2018-01-16 14:23:21","revisionof":"","revisedto":"S2-180792","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180163.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180164","title":"23.501 Clarification of interworking procedures without N26 interface","source":"Orange","contact":"Thouraya Toukabri","contact-id":66374,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: clarifications on the principles of interworking without N26 and the way they are fulfilled","secretary_remarks":"Revised in parallel session to S2-180790.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18270,"status":"revised","reservation_date":"2018-01-12 18:20:10","uploaded":"2018-01-16 14:23:21","revisionof":"","revisedto":"S2-180790","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180164.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180165","title":"23.501: Clarification on the use of indicators for the support of interworking without N26 and interworking with N26","source":"Orange","contact":"Thouraya Toukabri","contact-id":66374,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Indication that interworking with N26 is supported is sent to the device Conditions for the UE to be in dual registration are clarified","secretary_remarks":"Revised in parallel session to S2-180793.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18150,"status":"revised","reservation_date":"2018-01-12 18:33:40","uploaded":"2018-01-16 14:23:21","revisionof":"","revisedto":"S2-180793","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180165.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180166","title":"Discussion on optimization for PCF services","source":"Oracle Corporation, ZTE","contact":"Uri Baniel","contact-id":58644,"tdoctype":"discussion","for":"Agreement","abstract":"This discussion paper evaluates the basic operation of the PCF services in conjunction with the SMF\/AMF event exposure related services. It identifies several key issues and proposes optimization for PCF services.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14830,"status":"noted","reservation_date":"2018-01-12 18:50:55","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180166.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180167","title":"[Draft] Reply LS on timers for the network-requested PDU session modification procedure and 'SSC mode 3'","source":"Qualcomm Europe Inc.(Italy)","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-18abcd","secretary_remarks":"Response to S2-180025 Revised, merging S2-180289 and S2-180307, to S2-181104.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13050,"status":"revised","reservation_date":"2018-01-12 19:01:27","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"S2-181104","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180167.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180168","title":"23.502: Update of Npcf_SMPolicyControl service","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes the addition of event subscription and event notification to the Npcf_SMPolicyControl service to address the concerns raised above. NOTE: This does NOT impact the Nsmf_EventExposure Service! AMF, AF\/NEF and\/or any other consumer can still use this service as is, as long as the SMF simply notifies subscribers of events in a 'fire and forget' fashion. Update 23.502 Npcf_SMPolicyControl service to enable the PCF to subscribe to event notifications and to receive event notifications from the SMF:  - Update the optional input parameters of the Npcf_SMPolicyControl_Get service operation to provide event notification (in the case of SMF initiated modifications). - Update the optional output parameters of the Npcf_SMPolicyControl_Get service operation to subscribe to event triggers. - Update the optional input parameters of the Npcf_SMPolicyControl_UpdateNotify service operation with subscription to event triggers.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180969.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14840,"status":"revised","reservation_date":"2018-01-12 19:08:52","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180969","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180168.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180169","title":"23.502: SSS mode 3 timeout NAS timer replacement with a PCO lifetime value","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to align the logic of 'timer' and 'lifetime value' of procedures in 4.3.5.2 and 4.3.5.3 to address CT WG1 concerns in their LS in S2-180025, by not providing a PDU session Release timer as a NAS timer in 4.3.5.2, and instead provide a PDU Session Address Lifetime value to the UE upper layers in the PCO.","secretary_remarks":"Merged into S2-181105","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":12980,"status":"merged","reservation_date":"2018-01-12 19:12:10","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180169.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180170","title":"23.502: Update of Npcf_AMPolicyControl service","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes the addition of event subscription and event notification to the Npcf_AMPolicyControl service to address the concerns raised above. NOTE: This does NOT impact the Namf_EventExposure Service! SMF, AF\/NEF, UDM, GMLC and\/or any other consumer can still use this service as is, as long as the AMF simply notifies subscribers of events in a 'fire and forget' fashion.  Update 23.502 Npcf_AMPolicyControl service to enable the PCF to subscribe to event notifications and to receive event notifications from the AMF:  - Update the optional input parameters of the Npcf_AMPolicyControl_Get service operation to provide event notification (in the case of AMF initiated modifications). - Update the optional output parameters of the Npcf_AMPolicyControl_Get service operation to subscribe to event triggers. - Update the optional input parameters of the Npcf_AMPolicyControl_UpdateNotify service operation with subscription to event triggers.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180970.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14870,"status":"revised","reservation_date":"2018-01-12 19:17:15","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180970","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180170.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180171","title":"23.502: Update of Session Management Policy Establishment procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Session Management Policy Establishment procedure based on the Npcf_SMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_SMPolicyControl service.doc'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the SMF by using the Npcf_SMPolicyControl service. This can be done in step 5. Consequently steps 6 and 7 are not needed, and so are removed from the procedure.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180971.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14900,"status":"revised","reservation_date":"2018-01-12 19:24:06","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180971","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180171.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180172","title":"23.502: Removal of editor's note on mapping of security context for IW EPC\/5GC","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove the editor's note.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17530,"status":"approved","reservation_date":"2018-01-12 19:26:23","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180172.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180173","title":"23.502: Update of Session Management Policy Modification procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Session Management Policy Modification procedure based on the Npcf_SMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_SMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the SMF by using the Npcf_SMPolicyControl service. Specifically event notification from SMF to PCF can be done in step 1a by using the Npcf_SMPolicyControl_Get service operation. Step 2a may include subscription by the PCF to Event Triggers by using the response to the Npcf_SMPolicyControl_Get service operation. Similarly, Step 5 may include subscription by the PCF to Event Triggers by using the pcf_SMPolicyControl_UpdateNotify service operation.Consequently steps 7 and 8 are not needed, and so are removed from the procedure. On top of that it makes more sense now to split the procedure into two procedures: Session Management Policy Modifi","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180972.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14930,"status":"revised","reservation_date":"2018-01-12 19:31:50","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180972","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180173.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180174","title":"23.502: Update of Policy Association Establishment during Registration procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Association Establishment during Registration procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. This can be done in step 3. Consequently steps 6 and 7 are not needed, and so are removed from the procedure.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180973.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14960,"status":"revised","reservation_date":"2018-01-12 19:39:00","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180973","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180174.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180175","title":"23.502: Update of Policy Association Establishment during AMF relocation procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Association Establishment during AMF relocation procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. This can be done in step 3. Consequently steps 5 and 6 are not needed, and so are removed from the procedure.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180974.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14980,"status":"revised","reservation_date":"2018-01-12 19:46:58","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180974","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180175.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180176","title":"23.502: Update of Policy Association Modification for Mobility Policy procedure","source":"Oracle, ZTE, Ericsson? ,Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Associationt Modification for Mobility Policy procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. This can be done in steps 1(receive event notifications) and 2(subscribe to event notifications) respectively. Consequently steps 4 and 5 are not needed, and so are removed from the procedure. The policy decision is made right after step 1, and is denoted as step 2. Thus original step 2 is now step 3.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180975.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15000,"status":"revised","reservation_date":"2018-01-12 19:53:25","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180975","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180176.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180177","title":"23.502: Update of Policy Association Modification for UE Policy and Access and Mobility control procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Association Modification for UE Policy and Access and Mobility control procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. Consequently, the procedure is split up into two procedures: 1. Update of Policy Association Modification for UE Policy and Access and Mobility control procedure triggered by the AMF 2. Update of Policy Association Modification for UE Policy and Access and Mobility control procedure triggered by the PCF. As part of it section numbers and step numbers were adjusted.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180976.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15020,"status":"revised","reservation_date":"2018-01-12 19:58:08","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180976","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180177.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180178","title":"TS 23.502: Change to Required Inputs for Update service operation","source":"OTD","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses the need for a change to the required input field for the NF Management Update service operation of the 5G architecture.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19330,"status":"noted","reservation_date":"2018-01-12 21:47:01","uploaded":"2018-01-16 13:56:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180178.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180179","title":"23.502: Update Service operation required imputs","source":"OTD","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Specifies that the NF profile of the consumer NF be used as a required input for the NFUpdate service operation and removed as an optional parameter for the 'Inputs, Optional' field.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19340,"status":"approved","reservation_date":"2018-01-12 21:53:42","uploaded":"2018-01-16 13:56:28","revisionof":"","revisedto":"S2-181684","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180179.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180180","title":"TS 23.501: Clarification for Combo Node in 5GS","source":"OTD","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"discussion","for":"Discussion","abstract":"This paper provides further clarification for the Combo Nodes used for the interworking between 5GC and EPC.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17470,"status":"noted","reservation_date":"2018-01-12 21:56:35","uploaded":"2018-01-16 13:56:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180180.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180181","title":"23.501: Clarification for Combo Node in 5GS","source":"OTD","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Define the term 'Combo nodes' for nodes combining both EPC and 5GC commumnication procedures.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17480,"status":"noted","reservation_date":"2018-01-12 22:01:09","uploaded":"2018-01-16 13:56:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180181.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180182","title":"23.502: Handling of AMF and PCF interaction when there is a PLMN change during AMF relocation.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the registration procedure to reflect that when there is AMF relocation and the new AMF is in a different PLMN, the old AMF does not transfer the PCF ID nor the AM policy information and the event triggers subscribed by the PCF. The old AMF terminates the policy association to the PCF.","secretary_remarks":"Revised in parallel session to S2-180990.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15270,"status":"revised","reservation_date":"2018-01-12 22:43:26","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"S2-180990","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180182.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180183","title":"23.502: Cleanup of NamfEventExposure and NsmfEventExposure services","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Definition of a services, Namf_EventExposure and Nsmf_EventExposure are clarified.","secretary_remarks":"Revised in parallel session to S2-180992.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15330,"status":"revised","reservation_date":"2018-01-12 22:43:26","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"S2-180992","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180183.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180184","title":"23.501: Provision from NEF of policy requirements that apply to multiple UE and hence to multiple PCF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: Make consistent how to provision from NEF of policy requirements that apply to multiple UE and hence to multiple PCF","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23980,"status":"withdrawn","reservation_date":"2018-01-12 22:43:26","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180185","title":"23.716: Hybrid Access Transport Model for key issue 5.2.10","source":"Intel","contact":"Ellen C. Liao","contact-id":54895,"tdoctype":"pCR","for":"Approval","abstract":"In order to provide connectivity via hybrid access and corresponding traffic mobility management, this paper proposes to study hybrid access transport models in key issue 5.2.10. Further, a solution is proposed to include three options of hybrid transport models by referring to BBF TR-348.","secretary_remarks":"Not Handled","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20350,"status":"not treated","reservation_date":"2018-01-12 23:43:04","uploaded":"2018-01-16 06:40:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180185.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180186","title":"Discussion on way forward for support of integrity protection for user plane","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"discussion","for":"Agreement","abstract":"The paper addresses the issues raised in LSs from RAN WG2 (S2-180007 and S2-180015, both postponed from SA WG2 #124) and from SA WG3 (S2-180049) and proposes a solution for UP security policy determination and delivery to the NG-RAN","secretary_remarks":"Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13900,"status":"not treated","reservation_date":"2018-01-12 23:50:38","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180186.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180187","title":"23.501: Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation\/modification of a PDU session, or upon user plane establishment for a PDU session, determined the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Revised to S2-181198.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13920,"status":"revised","reservation_date":"2018-01-12 23:53:18","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"S2-181198","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180187.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180188","title":"23.502: Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation\/modification of a PDU session, or upon user plane establishment for a PDU session, determined the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13970,"status":"not treated","reservation_date":"2018-01-12 23:55:38","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180188.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180189","title":"[Draft] LS response on User Plane Security Policy","source":"Qualcomm Europe Inc.(Italy)","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"The LS address the aspects raised in the SA WG3 LS and raised also in RAN WG2 LS on the use of UP integrity protections.","secretary_remarks":"Response to S2-180049 Revised to S2-181197.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14020,"status":"revised","reservation_date":"2018-01-12 23:59:23","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"S2-181197","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG2, RAN WG3","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180189.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180190","title":"23.501: Clarifying the combined ePDG\/N3IWF selection mechanisms","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The proposed changes address fours points: - Introduction of a combined gateway selection information to be used in all scenarios (stand-alone and combined), to ensure that when algorithms defined for ePDG selection and based on determining (a list of) candidate PLMN(s) as defined in TS 23.402 clause 4.5.4.5, a prioritized list can be returned considering both ePDG and N3IWF information, instead of two separate lists if separate epDG and N3IWF configuration information exist. When the UE performs stand-alone selection, ePDG information is disregarded - Attempt automatic alignment of the node selection with the CN used over 3GPP access (if any), e.g. if UE is connected to EPC\/5GC respectively, it attempts ePDG\/N3IWF first respectively - Enable incremental deployments by allowing the MNO to push a UE to an ePDG or an N3IWF (when service preference allows it) depending on local preferences\/availability","secretary_remarks":"Merged into S2-180931","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18430,"status":"merged","reservation_date":"2018-01-13 00:01:46","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180190.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180191","title":"Enabling ePDG selection using 5GS TAI information","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduces the use of Tracking\/Location Area IdentityFQDNs for ePDG based on NG-RAN Tracking\/Location Area Identity.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18440,"status":"agreed","reservation_date":"2018-01-13 00:04:31","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.402,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2984.0,"crrevision":"","crcategory":"B","tsg_crp":"SP-180094","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180191.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180192","title":"23.501: Clarifying the use of DNNs\/APNs for slicing and interworking","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: For sake of simplicity it is assumed that for this release of the specification DNNs are unique and that the same DNN is not re-used for different slices. Also, for PDU sessions corresponding to a specific slice and a specific DN, the DNN used in 5GC is equal to the APN used on the EPC.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12080,"status":"not treated","reservation_date":"2018-01-13 00:16:17","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180192.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180193","title":"Emergency ePDG selection for UE without UICC","source":"Qualcomm Europe Inc.(Italy)","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align the text is TS 23.402 indicating that for ePDG selection for emergency services when no UIC is present, the UE may construct the Operator Identifier FQDN format based on a PLMN ID obtained via implementation specific means.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":10,"ainumber":"5.3","ainame":"Non-3GPP Access Maintenance","tdoc_agenda_sort_order":10820,"status":"agreed","reservation_date":"2018-01-13 00:55:12","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"","release":"Rel-14","crspec":23.402,"crspecversion":"14.6.0","workitem":[{"winame":"SEW2"}],"crnumber":2985.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180087","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180193.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180194","title":"Emergency ePDG selection for UE without UICC","source":"Qualcomm Europe Inc.(Italy)","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: Align the text is TS 23.402 indicating that for ePDG selection for emergency services when no UIC is present, the UE may construct the Operator Identifier FQDN format based on a PLMN ID obtained via implementation specific means.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":10,"ainumber":"5.3","ainame":"Non-3GPP Access Maintenance","tdoc_agenda_sort_order":10830,"status":"agreed","reservation_date":"2018-01-13 00:59:14","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.402,"crspecversion":"15.2.0","workitem":[{"winame":"SEW2"}],"crnumber":2986.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-180087","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180194.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180195","title":"23.787: Architectural Assumptions for ENTRADE","source":"Qualcomm incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes architectural assumptions for ENTRADE","secretary_remarks":"Revised in parallel session to S2-180960.","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21250,"status":"revised","reservation_date":"2018-01-13 01:23:37","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"S2-180960","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180195.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180196","title":"23.787: ENTRADE: Key Issue On Encrypted Traffic Detection for Applications with Tight Relation to the MNO","source":"Qualcomm incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue studying the encrypted traffic detection for applications that are integrated with an MNO network and rely on an SLA and interfacing between the AS and the operator MNO.","secretary_remarks":"Merged into S2-180961","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21350,"status":"merged","reservation_date":"2018-01-13 01:25:59","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180196.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180197","title":"23.787: ENTRADE: Key Issue On Encrypted Traffic Detection for Applications without SLA between MNO and AS","source":"Qualcomm incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"pCR","for":"Approval","abstract":"Abstract of the contribution: This contribution proposes a key issue studying the encrypted traffic detection for applications that are not 'integrated' with an MNO network and cannot rely on an SLA and interfacing between the AS and the operator MNO","secretary_remarks":"Revised in parallel session to S2-180963.","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21360,"status":"revised","reservation_date":"2018-01-13 01:28:51","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"S2-180963","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180197.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180198","title":"23.716: Solution for Key Issue 5.3.1-Registration for trusted non-3GPP access","source":"Intel","contact":"Ellen C. Liao","contact-id":54895,"tdoctype":"pCR","for":"Approval","abstract":"This PCR proposed a solution for the architecture for key issue 5.3.1.","secretary_remarks":"Not Handled","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20370,"status":"not treated","reservation_date":"2018-01-13 01:30:48","uploaded":"2018-01-16 06:40:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180198.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180199","title":"23.716: Update to key issue 5.2.9 with two use cases","source":"Intel","contact":"Ellen C. Liao","contact-id":54895,"tdoctype":"pCR","for":"Approval","abstract":"This contribution updates the key issue 5.2.9 to study the end user devices for two cases.","secretary_remarks":"Revised to S2-181179.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20140,"status":"revised","reservation_date":"2018-01-13 01:37:23","uploaded":"2018-01-16 06:40:53","revisionof":"","revisedto":"S2-181179","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180199.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180200","title":"23.716: Solution of Key Issue 5.2.9 for CPE\/RG as a UE-to-Network Relay","source":"Intel","contact":"Ellen C. Liao","contact-id":54895,"tdoctype":"pCR","for":"Approval","abstract":"This proposal addresses solution for key issue in clause 5.2.9 TR 23.716.","secretary_remarks":"Not Handled","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20340,"status":"not treated","reservation_date":"2018-01-13 01:39:57","uploaded":"2018-01-16 06:40:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180200.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180201","title":"23.501: Network sharing prioritised PLMN handling","source":"Ericsson, Qualcomm Inc.","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding support for prioritized PLMN selection at UE for idle mode mobility and and at interworking with EPS. Also clarified that 23.122 does not define all cases where multiple MNCs used within a country.","secretary_remarks":"Revised to S2-181077.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11250,"status":"revised","reservation_date":"2018-01-13 16:13:27","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"S2-181077","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180201.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180202","title":"23.502: Network sharing prioritised PLMN handling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying PLMN selection related to shared networks in combination with interworking and access changes.","secretary_remarks":"Revised, merging S2-180438, to S2-181099.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11320,"status":"revised","reservation_date":"2018-01-13 16:13:27","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"S2-181099, S2-181742","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180202.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180203","title":"23.501: EPS Fallback for voice","source":"Ericsson, Charter Communications","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding support for redirect to EPS in case of EPS Fallback for voice and for rejecting the PDU Session modification that setups the QoS flow for voice.","secretary_remarks":"Revised in parallel session, merging S2-180286, S2-180553 and S2-180554, to S2-180884.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16670,"status":"revised","reservation_date":"2018-01-13 16:13:27","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"S2-180884","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180203.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180204","title":"23.502: EPS Fallback for voice","source":"Ericsson, Charter Communications","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding support for redirect to EPS in case of EPS Fallback for voice.","secretary_remarks":"Revised in parallel session to S2-180885.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16700,"status":"revised","reservation_date":"2018-01-13 16:13:27","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"S2-180885","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180204.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180205","title":"23.502: Complete of IMS Emergency support in 5G including slice and local numbers","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: Emergency support further clarifications","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24000,"status":"withdrawn","reservation_date":"2018-01-13 16:13:27","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180206","title":"23.501: Correction\/cleanup of IMS Emergency support","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: -Indicate which entity determines the fallback, align with 23.502 on the decision of fallback and indicate the use case is for E-UTRA not connected to 5GC","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17040,"status":"noted","reservation_date":"2018-01-13 16:13:27","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180206.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180207","title":"23.502: Correction\/cleanup of IMS Emergency support","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the 23.167 applicability correctly for all cases and add one additional case for 5G NR case.","secretary_remarks":"Revised in parallel session to S2-180866.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17050,"status":"revised","reservation_date":"2018-01-13 16:13:27","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"S2-180866","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180207.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180208","title":"23.786: EV2X architecture reference model for 5G","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Propose 5G V2X architecture option","secretary_remarks":"Revised in parallel session, merging S2-180550, to S2-181086.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19800,"status":"revised","reservation_date":"2018-01-13 16:13:27","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"S2-181086","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180208.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180209","title":"Support of Reliable transmission over PC5 using extended PPPP","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To allow for the UE to indicate reliability information an additional indication is added to allow the V2X application in the UE to provide reliability information that may be used by AS layer to differentiate between different V2X packets.","secretary_remarks":"Revised in parallel session, merging S2-180249, to S2-181088.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11150,"status":"revised","reservation_date":"2018-01-13 16:13:27","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"S2-181088","release":"Rel-15","crspec":23.285,"crspecversion":"14.5.0","workitem":[{"winame":"LTE_eV2X-Core"}],"crnumber":37.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180209.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180210","title":"23.502: Add Nocs_SpendingLimitControl service, service operations and information flows","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding OCS service and service operations to transfer subscriber spending limits from OCS to the NF consumer. Information flows are also added.","secretary_remarks":"Technically endorsed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15660,"status":"endorsed","reservation_date":"2018-01-13 16:42:57","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-181627","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180210.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180211","title":"23.503: Add Nocs service in service base representation architecture","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding Nocs service in service base representation architecture of PCC framework for the 5GS.","secretary_remarks":"Technically endorsed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15670,"status":"endorsed","reservation_date":"2018-01-13 16:42:58","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-181635","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180211.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180212","title":"23.791: Discussion on big data and 5G","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution triggers discussion on big data analytic and 5G system.","secretary_remarks":"Revised in parallel session to S2-180861.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21490,"status":"revised","reservation_date":"2018-01-14 08:50:58","uploaded":"2018-01-16 11:26:31","revisionof":"","revisedto":"S2-180861","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180212.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180213","title":"23.791: Scope of TR 23.791","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the scope of the TR 23.791 for FS_eNA.","secretary_remarks":"Revised in parallel session to S2-180859.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21420,"status":"revised","reservation_date":"2018-01-14 08:50:58","uploaded":"2018-01-16 11:26:31","revisionof":"","revisedto":"S2-180859","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180213.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180214","title":"23.791: Architecture Requirement of TR 23.791","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes architecture requirement section of the TR 23.791 for FS_eNA.","secretary_remarks":"Revised in parallel session to S2-180860.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21450,"status":"revised","reservation_date":"2018-01-14 08:50:58","uploaded":"2018-01-16 11:26:31","revisionof":"","revisedto":"S2-180860","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180214.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180215","title":"23.791: FS_eNA skeleton","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the skeleton for the TR 23.791 of FS_eNA.","secretary_remarks":"Revised in parallel session to S2-180858.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21400,"status":"revised","reservation_date":"2018-01-14 08:50:58","uploaded":"2018-01-16 11:26:31","revisionof":"","revisedto":"S2-180858","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180215.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180216","title":"23.791: Key issue on how to get service information from AF","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to a key issue on how to get service information from the service applications.","secretary_remarks":"Revised in parallel session to S2-180862.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21580,"status":"revised","reservation_date":"2018-01-14 10:57:36","uploaded":"2018-01-16 12:07:10","revisionof":"","revisedto":"S2-180862","release":"Rel-16","crspec":23.791,"crspecversion":"16.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180216.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180217","title":"23.724: Key Issue on infrequent small data transmission in efficient way","source":"China Mobile, CATT","contact":"Aihua Li","contact-id":58162,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue for infrequent small data transmission","secretary_remarks":"Merged into S2-180826","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20720,"status":"merged","reservation_date":"2018-01-14 11:01:09","uploaded":"2018-01-16 12:07:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"16.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180217.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180218","title":"23.724: Solution on infrequent small data transmission in efficient way","source":"China Mobile, CATT","contact":"Aihua Li","contact-id":58162,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a solution to address KI 'infrequent small data transmission in efficient way'","secretary_remarks":"Not Handled","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21190,"status":"not treated","reservation_date":"2018-01-14 11:05:51","uploaded":"2018-01-16 12:07:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"16.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180218.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180219","title":"Traffic mapping information that disallows uplink packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"This paper proposes solutions how to handle DL only QoS Flow in 5GS","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14180,"status":"noted","reservation_date":"2018-01-14 14:36:23","uploaded":"2018-01-16 13:38:49","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180219.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180220","title":"23.501: Traffic mapping information that disallows uplink packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In clause 5.7.1.4, refer to clause 5.7.6.1 for the definition of Packet Filter Set to ensure the consistency. In clause 5.7.1.5, clarify that a QoS rule containing Packet Filter Set with no UL filter means no UL packets allowed for the QoS Flow associated with that QoS rule. In clause 5.7.6.1, add a note when the DL filter may be needed by the UE.","secretary_remarks":"Revised to S2-181151.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14190,"status":"revised","reservation_date":"2018-01-14 14:36:23","uploaded":"2018-01-16 13:38:49","revisionof":"","revisedto":"S2-181151","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180220.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180221","title":"23.502: Traffic mapping information that disallows uplink packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In clause 4.11.1.1, clarify how SMF+PGW-C generates TFT for EPS bearer mapped from downly only QoS Flow.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14230,"status":"endorsed","reservation_date":"2018-01-14 14:36:23","uploaded":"2018-01-16 13:38:49","revisionof":"","revisedto":"S2-181626","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180221.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180222","title":"23.503: Traffic mapping information that disallows uplink packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In clause 6.1.3.9, replace the reference specification from TS23.501 with TS23.502.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15940,"status":"not treated","reservation_date":"2018-01-14 14:36:23","uploaded":"2018-01-16 13:38:49","revisionof":"","revisedto":"S2-181644","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180222.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180223","title":"Update of the Procedures Specified in TS 23.060 for CUPS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"This document propose update to clause 6.3.4 and how to update.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10600,"status":"noted","reservation_date":"2018-01-14 14:36:23","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"","release":"Rel-14","crspec":23.214,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180223.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180224","title":"Update of the Procedures Specified in TS 23.060","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Note that the following changes are clarification and correction but not adding new functionality.  Clause 6.3.4.1.1 Change 'Part 1' and 'Part 2' in the figure caption to 'Group 1' and 'Group 2'. Add Group 1 and Group 2 in the text description before the Figures to improve readability Add the steps specific for S4SGSN in the text description before the Figures. Group 1:  Add HLR in the figure Add steps specific for S4SGSN in Figure 6.3.4.1.1-1 when applicable. Add step 2c which triggers step 3a\/3b. Add new steps 3d\/3e (i.e. two CPF-UPF interactions for SGW) for the existing PDN connection deletion. In step 5a\/5b SGW-C and SGW-U interaction, change the dashed line to solid line.  In step 10, change 'SGSN-initiated Bearer Deactivation Procedure' to 'SGSN-initiated PDP Context Deactivation Procedure' where Figure 76 is included.  Group 2: In Figure 6.3.4.1.1-2, step 4, add S4SGSN specifics. Correct use of 'May' for CPF-UPF interaction  Clause 6.3.4.1.2 Change 'Part 1' a","secretary_remarks":"Revised in parallel session to S2-180895.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10610,"status":"revised","reservation_date":"2018-01-14 14:36:23","uploaded":"2018-01-16 13:45:42","revisionof":"","revisedto":"S2-180895","release":"Rel-14","crspec":23.214,"crspecversion":"14.5.0","workitem":[{"winame":"CUPS"}],"crnumber":59.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180224.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180225","title":"Update of the Procedures Specified in TS 23.060","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: Note that the following changes are clarification and correction but not adding new functionality.  Clause 6.3.4.1.1 Change 'Part 1' and 'Part 2' in the figure caption to 'Group 1' and 'Group 2'. Add Group 1 and Group 2 in the text description before the Figures to improve readability Add the steps specific for S4SGSN in the text description before the Figures. Group 1:  Add HLR in the figure Add steps specific for S4SGSN in Figure 6.3.4.1.1-1 when applicable. Add step 2c which triggers step 3a\/3b. Add new steps 3d\/3e (i.e. two CPF-UPF interactions for SGW) for the existing PDN connection deletion. In step 5a\/5b SGW-C and SGW-U interaction, change the dashed line to solid line.  In step 10, change 'SGSN-initiated Bearer Deactivation Procedure' to 'SGSN-initiated PDP Context Deactivation Procedure' where Figure 76 is included.  Group 2: In Figure 6.3.4.1.1-2, step 4, add S4SGSN specifics. Correct use of 'May' for CPF-UPF interaction  Clause 6.3.4.1.2","secretary_remarks":"Revised in parallel session to S2-180896.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10630,"status":"revised","reservation_date":"2018-01-14 14:36:24","uploaded":"2018-01-16 13:45:42","revisionof":"","revisedto":"S2-180896","release":"Rel-15","crspec":23.214,"crspecversion":"15.1.0","workitem":[{"winame":"CUPS"}],"crnumber":60.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180225.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180226","title":"Update to Procedures Specified in TS 23.401","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 6.3.1.7,  Steps 8&9 and steps 11&12 of, add Sx Session Termination Request\/Response for the scenario of the PDN connection deactivation.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10650,"status":"agreed","reservation_date":"2018-01-14 14:36:25","uploaded":"2018-01-16 13:45:42","revisionof":"","revisedto":"","release":"Rel-14","crspec":23.214,"crspecversion":"14.5.0","workitem":[{"winame":"CUPS"}],"crnumber":61.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180086","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180226.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180227","title":"Update to Procedures Specified in TS 23.401","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: In clause 6.3.1.7,  Steps 8&9 and steps 11&12 of, add Sx Session Termination Request\/Response for the scenario of the PDN connection deactivation.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10660,"status":"agreed","reservation_date":"2018-01-14 14:36:25","uploaded":"2018-01-16 13:45:42","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.214,"crspecversion":"15.1.0","workitem":[{"winame":"CUPS"}],"crnumber":62.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-180086","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180227.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180228","title":"23.501: Replacing PUI with GPSI","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Replace PUI with GPSI","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11470,"status":"approved","reservation_date":"2018-01-14 14:36:26","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-181616","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180228.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180229","title":"23.502: Replacing PUI with GPSI","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Replace PUI with GPSI","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11480,"status":"approved","reservation_date":"2018-01-14 14:36:26","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-181625","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180229.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180230","title":"23.502: LCS Correction of identities","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Usage of SUPI, GPSI and PEI as UE identity corrected. Correct spelling of USIM. Use correct wording for emergency registration. Pointer to figure 4.10.2-1 corrected to 4.13.5.1-1. Aligned information flow figures to template in Annex A.3.","secretary_remarks":"Revised in parallel session to S2-180870.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17280,"status":"revised","reservation_date":"2018-01-14 14:44:12","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-180870","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180230.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180231","title":"Discussion on EPS fallback for voice","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"discussion","for":"Decision","abstract":"The contribution analyses EPS fallback options (UE-based, network-based, mixed) and proposes a way forward.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16640,"status":"noted","reservation_date":"2018-01-14 18:58:41","uploaded":"2018-01-16 14:50:35","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_125_Gothenburg\/Docs\/S2-180231.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180232","title":"23.502: Proposed resolution of Editor\u00b4s Notes in 23.502","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The proposal to resolve 1) above is to remove the Editor\u00b4s note. The reason is that the Access and Mobility related policy control the V-PCF generates the service area restrictions, those are not received from H-PCF as defined in clause 6.2.1.4 in TS 23.503.  The proposal to resolve 2) above is to remove the Editor\u00b4s note. The reason is that the functional description of the AF interactions described in 23.501 and 23.503 are either related to request for resources, prioritization of services, requires to steer to traffic to a DNAI(s), or request to charge traffic to the sponsor. These features require to provision PCC Rules to SMF.  The proposal to resolve 3) above is to extend the number of scenarios when the policy association termination procedure applies to include the notification of the removal of the policy profile from UDR. In addition, it is proposed to add a new procedure for (policy) session management termination when the UDR notifies the PCF that the pol","secretary_remarks":"Revised in parallel session to S2-181052.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15200,"status":"revised","reservation_date":"2018-01-14 18:59:39","uploaded":"2018-01-16 14:40:25","revisionof":"","revisedto":"S2-181052","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180232.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180233","title":"[DRAFT] LS reply on the information exposed to the SCS\/AS for AS session establishment","source":"Ericsson","contact":"Belen Pancorbo","contact-id":66867,"tdoctype":"LS out","for":"Approval","abstract":"Reply to CT WG3 LS on the information exposed to the SCS\/AS for AS session establishment","secretary_remarks":"Response to S2-180030. Revised in parallel session to S2-181239.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11000,"status":"revised","reservation_date":"2018-01-14 18:59:39","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"S2-181239","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG6","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180233.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180234","title":"[DRAFT] LS reply on Clarification on Npcf_SMPolicyControl service","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply to CT WG3 LS proposing to select Option 1, i.e. use Npcf_SMPolicyControlGet to report modification of the association between the SMF and the PCF","secretary_remarks":"Response to S2-180029 Revised in parallel session to S2-180977.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14510,"status":"revised","reservation_date":"2018-01-14 18:59:39","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"S2-180977","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180234.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180235","title":"23.501: EPS fallback for voice","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Implements the UE-based option described in S2-180231 as Alt1.","secretary_remarks":"Not Handled","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16770,"status":"not treated","reservation_date":"2018-01-14 19:10:20","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180235.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180236","title":"23.502: EPS fallback for voice","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Implements the UE-based option described in S2-180231 as Alt1.","secretary_remarks":"Not Handled","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16780,"status":"not treated","reservation_date":"2018-01-14 19:12:15","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180236.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180237","title":"[Draft] Reply LS on Mobility management congestion control","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 answers to CT WG1 questions on NAS MM congestion control in LS S2-180027.","secretary_remarks":"Response to S2-180027. Merged into S2-181189","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12430,"status":"merged","reservation_date":"2018-01-14 21:18:22","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180237.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180238","title":"[Draft] Reply LS on session management congestion control","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 answers to CT WG1 questions on NAS SM congestion control in LS S2-180026.","secretary_remarks":"Response to S2-180026. Merged into S2-181188","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12380,"status":"merged","reservation_date":"2018-01-14 21:18:22","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180238.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180239","title":"23.501: NAS congestion control update","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarified the usage of 5G-AN and NG-RAN.  Clarified that the AMF can apply the general NAS level congestion control towards UEs using any of the 5G-ANs.   Clarified that 5G-AN change does not stop the back-off timers.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11490,"status":"endorsed","reservation_date":"2018-01-14 21:18:22","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"S2-181618","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180239.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180240","title":"23.501: Updates to the Security Edge Protection Proxy description","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying that the message filtering and policing by the SEPP is achieved without requiring updates of SLAs between the two PLMNs.","secretary_remarks":"Revised to S2-181184.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14070,"status":"revised","reservation_date":"2018-01-14 21:18:22","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"S2-181184","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180240.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180241","title":"23.501: Usage of NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco, Verizon?, Deutsche Telecom?","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Split the UPF selection between a step of Discovery of available UPF(s) and a step of selection of an UPF for a PDU Session and refer to N4 Node Level Procedures where the UPF and the SMF may exchange information such as the support of optional functionalities and capabilities 2. The discovery (OAM or NRF) allows to get the N4 address of the UPF 3. The SMF area allows the operators to partition SMF and UPF into regional clusters that are managed by different teams within the operator","secretary_remarks":"Confirm Sources! Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13790,"status":"not treated","reservation_date":"2018-01-14 21:32:10","uploaded":"2018-01-16 14:42:26","revisionof":"","revisedto":"S2-181457, S2-181459","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180241.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180242","title":"23.501: Clarification on UDR","source":"Samsung, Deutsche Telekom","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: First change. Update the figure 4.2.5-2 to add oval representation over the Nudr reference point to make sure the Nudr has a service-based interface. In addition, some editorial update using the agreed terminologies (i.e. NF Service Consumer) for service based interface. Second change. To make a consistency for what is inside the UDR. In other words, the figure contains four types of data (i.e. subscription data, policy data, structured data for data exposure, and application data) and the description for what the UDR includes are stated as follows: As depicted in Figure 4.2.5-2, the 5G System architecture allows the UDM, PCF and NEF to store data in the UDR, including subscription data and policy data by UDM and PCF, structured data for exposure and application data (including Packet Flow Descriptions (PFDs) for application detection, application request information for multiple UEs) by the NEF To make them consistent, it is proposed to replace 'application request","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19430,"status":"endorsed","reservation_date":"2018-01-15 01:23:54","uploaded":"2018-01-16 07:04:46","revisionof":"","revisedto":"S2-181654","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180242.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180243","title":"23.501: NF Service Discovery","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. It is proposed to make sure that the NRF returns the HTTP URL-style endpoint address for the discovered NF service instances 2. NF Service Discovery is also service-based 3. NRF discovers the UPF's N4 reference point address.","secretary_remarks":"Revised to S2-181135.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19500,"status":"revised","reservation_date":"2018-01-15 01:35:35","uploaded":"2018-01-16 07:04:46","revisionof":"","revisedto":"S2-181135","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180243.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180244","title":"23.502: NF Service Discovery Corrections in 23.502","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: First Change (in clause 4.3.2.2.3.2) and Second Changes (in clause 4.17.5) make sure to include the endpoint address (i.e. HTTP URLs) for the discovered NF services as a result of NF\/NF Service Discovery from the NRF.","secretary_remarks":"Revised to S2-181127.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19210,"status":"revised","reservation_date":"2018-01-15 01:40:38","uploaded":"2018-01-16 07:04:46","revisionof":"","revisedto":"S2-181127","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180244.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180245","title":"23.501: Corrections on UE Location change notification","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: First change. Name of the notification - proposal is to use 'UE location change notification' instead of 'UE mobility event Notification' Second change. Use 'UE presence in LADN' and its descriptions Third change. Add 'SMF enable downlink data notification or not' on receiving the notification And more minor changes including editorial changes.","secretary_remarks":"Revised to S2-181109.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13140,"status":"revised","reservation_date":"2018-01-15 01:48:49","uploaded":"2018-01-16 07:04:46","revisionof":"","revisedto":"S2-181109","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180245.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180246","title":"23.501: QFI in N9","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add N9 reference point to relay RQI to the RAN.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14390,"status":"approved","reservation_date":"2018-01-15 01:55:46","uploaded":"2018-01-16 07:04:46","revisionof":"","revisedto":"S2-181655","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180246.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180247","title":"23.501: LADN support for RRC Inactive","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: First change It is proposed to use the agreed termilogy (i.e. the UE presence in LADN; IN, OUT or UNKNOWN) instead of using 'the relationship between UE location and a LADN service area. It is proposed to correct the description of the AMF behaviour when it is subscribed for LADN, that is. 'the AMF tracks the UE location with considering CM state and RRC state and determines the UE presence in LADN and notifies the information to the SMF' Second change In case of the deployment that RRC inactive state can be enabled, the AMF triggers N2 Notification procedure to track the UE presence in LADN even when the UE transits to the RRC Inactive state.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13320,"status":"not treated","reservation_date":"2018-01-15 01:59:43","uploaded":"2018-01-16 07:04:46","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180247.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180248","title":"Discussion on Reliability Information Provision for V2X Messages","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discusses the indication of Reliability Characteristic for V2X Messages.","secretary_remarks":"Wrong WI code. Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11170,"status":"noted","reservation_date":"2018-01-15 03:44:45","uploaded":"2018-01-16 10:07:42","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180248.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180249","title":"Reliability Information Provision for V2X Messages","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description that The application layer provides the reliability information for each V2X message when passing it to lower layer for transmission.","secretary_remarks":"Wrong WI code. Merged into S2-181088","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11180,"status":"merged","reservation_date":"2018-01-15 03:49:52","uploaded":"2018-01-16 10:01:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.285,"crspecversion":"14.5.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":38.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180249.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180250","title":"23.502: Selecting a common PCF for UE and Session Policies","source":"Cisco Systems, Inc","contact":"Ravi Shekhar","contact-id":71185,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Optionally, passing the selected PCF Id by AMF to SMF.","secretary_remarks":"Revised in parallel session to S2-180997.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15470,"status":"revised","reservation_date":"2018-01-15 04:12:49","uploaded":"2018-01-16 10:41:13","revisionof":"","revisedto":"S2-180997","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180250.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180251","title":"Key decisions for INOBEAR","source":"Telstra","contact":"Robert Ropolyi","contact-id":73241,"tdoctype":"discussion","for":"Agreement","abstract":"The paper lists key issues connected to INOBEAR, with proposed decisions. It also provides examples for the required changes in impacted procedures, subject to the decisions.","secretary_remarks":"Revised in parallel session to S2-180894.","agenda_item_sort_order":39,"ainumber":"6.15","ainame":"WID on increasing the maximum number of LTE bearers (INOBEAR)","tdoc_agenda_sort_order":22530,"status":"revised","reservation_date":"2018-01-15 05:32:51","uploaded":"2018-01-16 13:01:10","revisionof":"","revisedto":"S2-180894","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_125_Gothenburg\/Docs\/S2-180251.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180252","title":"23.501: QoS rule generation","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify if dynamic PCC is deployed, each QoS rule provided by SMF is generated from a PCC rule. The default QoS rule is generated by SMF based on the authorized default 5QI and ARP received from PCF, if a Packet Filter Set is included in the default QoS rule, the SMF may set the Packet Filter Set based on local policy or by the instruction of PCF.","secretary_remarks":"Merged into S2-181152.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14290,"status":"merged","reservation_date":"2018-01-15 05:44:54","uploaded":"2018-01-16 11:52:46","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180252.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180253","title":"23.503: QoS rule generation","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify each QoS rule provided by SMF is generated from a PCC rule. The default QoS rule is generated by SMF based on the authorized default 5QI and ARP received from PCF, if a Packet Filter Set is included in the default QoS rule, the PCF may provide a default Packet Filter Set in the PDU Session related policy information to SMF. Clarify for a PDU session of unstructured type, no PCC Rule is provided to SMF. SMF generates the default QoS rule based on the authorized default 5QI and ARP received in the PDU Session related policy information.","secretary_remarks":"Revised in parallel session to S2-180994.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15390,"status":"revised","reservation_date":"2018-01-15 05:50:51","uploaded":"2018-01-16 11:52:46","revisionof":"","revisedto":"S2-180994","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180253.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180254","title":"23.502: Correction for event trigger report from SMF","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify the affected PCC rules and the QoS request for specific SDFs received from UE may be included in the Nsmf_EventExposure_Notify service","secretary_remarks":"Revised in parallel session to S2-181007.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15750,"status":"revised","reservation_date":"2018-01-15 05:54:06","uploaded":"2018-01-16 11:52:46","revisionof":"","revisedto":"S2-181007","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180254.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180255","title":"23.502: Clarification on Event co-relation ID","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify each Event co-relation ID assoiates to one event; Add Event co-relation ID in the Nudm_EventExposure and Nnef_EventExposure service","secretary_remarks":"Merged into S2-181125.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19150,"status":"merged","reservation_date":"2018-01-15 05:57:55","uploaded":"2018-01-16 11:52:46","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180255.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180256","title":"23.502: UE presence in LADN for RRC Inactive","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In case that the RRC Inactive state applies to the NG-RAN, the UE Presence in LADN is defined as follows: - IN: - if the UE is inside the LADN service area and if the UE is in CM-CONNECTED state (with RRC Connected state in case that the RRC Inactive state applies to the NG-RAN); or- if the UE is inside a Registration Area which is contained within the LADN service area, and if the UE is in CM-IDLE state or in CM-CONNECTED with RRC Inactive state in case that the RRC Inactive state applies to NG-RAN. - OUT: - if the UE is outside the LADN service area but within a Registration Area where the LADN is available, and if the UE is in CM-CONNECTED state (with RRC Connected state in case that the RRC Inactive state applies to the NG-RAN); or - if UE is inside a Registration Area where the LADN is not available. - UNKNOWN  -  if the UE is inside a Registration Area where the LADN is available and the LADN service area does not contain the whole Registration Area, and  -  if","secretary_remarks":"Revised in parallel session to S2-180877.","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16570,"status":"revised","reservation_date":"2018-01-15 06:05:00","uploaded":"2018-01-16 07:04:46","revisionof":"","revisedto":"S2-180877","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180256.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180257","title":"23.716: Supporting MBMS in 5WWC Hybrid Access","source":"Telstra","contact":"Robert Ropolyi","contact-id":73241,"tdoctype":"pCR","for":"Approval","abstract":"The document adds a new key issue to study how MBMS services can be supported in hybrid access","secretary_remarks":"Not Handled","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20380,"status":"not treated","reservation_date":"2018-01-15 06:16:43","uploaded":"2018-01-16 13:01:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180257.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180258","title":"23.501: T8 support in TS 23.501","source":"KDDI","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add description for T8 support. The description in TS 23.501 is similar with the one in TS 23.682.","secretary_remarks":"Not Handled","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19070,"status":"not treated","reservation_date":"2018-01-15 06:21:50","uploaded":"2018-01-16 13:38:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180258.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180259","title":"23.502: T8 support in TS 23.502","source":"KDDI Corporation","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN:","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24030,"status":"withdrawn","reservation_date":"2018-01-15 06:24:12","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180260","title":"23.787: FS_ENTRADE - Skeleton of TR 23.787","source":"China Unicom","contact":"Chi Ren","contact-id":72309,"tdoctype":"pCR","for":"Approval","abstract":"The skeleton of TR 23.787 Study on encrypted traffic detection and verification","secretary_remarks":"Revised in parallel session to S2-180958.","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21210,"status":"revised","reservation_date":"2018-01-15 06:51:40","uploaded":"2018-01-16 06:34:34","revisionof":"","revisedto":"S2-180958","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180260.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180261","title":"23.787: FS_ENTRADE - Scope of TR 23.787","source":"China Unicom, OPPO","contact":"Chi Ren","contact-id":72309,"tdoctype":"pCR","for":"Approval","abstract":"The scope of TR 23.787 Study on encrypted traffic detection and verification.","secretary_remarks":"Revised in parallel session to S2-180959.","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21230,"status":"revised","reservation_date":"2018-01-15 07:03:19","uploaded":"2018-01-16 06:34:34","revisionof":"","revisedto":"S2-180959","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180261.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180262","title":"23.787: Key Issue - Management of encrypted traffic detection and verification information","source":"China Unicom, OPPO","contact":"Chi Ren","contact-id":72309,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue (i.e. management of encrypted traffic detection and verification information) for FS_ENTRADE.","secretary_remarks":"Revised in parallel session, merging S2-180610 and S2-180196, to S2-180961.","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21280,"status":"revised","reservation_date":"2018-01-15 07:12:05","uploaded":"2018-01-16 06:34:34","revisionof":"","revisedto":"S2-180961","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180262.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180263","title":"23.502: Correction on PDU Session Establishment procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Change 'Namf_PDUSession_CreateSMContext Request' into 'Nsmf_PDUSession_CreateSMContext Request\/ Nsmf_PDUSession_UpdateSMContext Request' in step 3a of Figure 4.3.2.2.1-1, and Change 'Namf_PDUSession_CreateSMContext Response' into 'Nsmf_PDUSession_CreateSMContext Response\/ Nsmf_PDUSession_UpdateSMContext Response'in step 5 of Figure 4.3.2.2.1-1. 2. Move the step'First Downlink Data' to step 16b bebow in Figure 4.3.2.2.1-1 to align with Figure 4.3.2.2.2-1. 3. Replace 'Access Technology Type' into 'Access Type' in discrption of step1. 4. Add 'or switching between 3GPP access and non-3GPP access' in discrption of step 2. 5. Editorial modify 'For' into 'for 'in 'Subscription For PDU Session Status Notification' in discrption of step 3, and editorial modify 'then' into 'that' in discrption of step 3. 6. Add 'as described in TS 23.501 [2] clause 6.3.7' in discrption of step 7a. 7. Remove the overlap step number mark 9.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13600,"status":"not treated","reservation_date":"2018-01-15 07:31:03","uploaded":"2018-01-16 11:42:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180263.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180264","title":"23.502: Update PDU Session Modification procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add step 1e in 4.3.3.3 PDU Session Modification for home-routed roaming.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13610,"status":"not treated","reservation_date":"2018-01-15 07:31:03","uploaded":"2018-01-16 11:42:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180264.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180265","title":"23.502: Correction on AF influence on traffic routing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Addition of the removal of AF request in Processing AF requests to influence traffic routing  2) Addition of modification (update or delete) the AF request in NEF Transferring an AF request to the relevant PCF","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13480,"status":"endorsed","reservation_date":"2018-01-15 07:31:03","uploaded":"2018-01-16 11:42:53","revisionof":"","revisedto":"S2-181550","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180265.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180266","title":"Scope of solution for voice service continuity between 5G and 3G","source":"China Unicom, Huawei, OPPO","contact":"Chi Ren","contact-id":72309,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discusses the scope of potential solutions for voice service continuity from 5G to UTRAN.","secretary_remarks":"Not Handled","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23100,"status":"not treated","reservation_date":"2018-01-15 08:22:19","uploaded":"2018-01-16 06:36:27","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_125_Gothenburg\/Docs\/S2-180266.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180267","title":"New SID - Study for single radio voice continuity from 5G to 3G","source":"China Unicom, Huawei","contact":"Chi Ren","contact-id":72309,"tdoctype":"SID new","for":"Approval","abstract":"This contribution proposes a new SI for single radio voice continuity from 5G to 3G","secretary_remarks":"This was left for further consideration and was postponed.","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23070,"status":"postponed","reservation_date":"2018-01-15 08:29:41","uploaded":"2018-01-16 06:36:27","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_125_Gothenburg\/Docs\/S2-180267.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180268","title":"23.724: KI: Overload Control","source":"Sony, InterDigital Inc., NEC, Intel","contact":"Lars Nord","contact-id":58638,"tdoctype":"pCR","for":"Approval","abstract":"Discuss the legacy solution and propose open key issues for overload control that needs to be studied.","secretary_remarks":"Revised in parallel session to S2-180832.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20950,"status":"revised","reservation_date":"2018-01-15 08:35:22","uploaded":"2018-01-16 14:41:36","revisionof":"","revisedto":"S2-180832","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180268.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180269","title":"23.501: Add the description on the support of PRA","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: PRA is defined the same as in TS 23.401\/5.9.2.2, and the only difference is that PCF subscribes the event of PRA change from the AMF directly in the context of SBA.  It also clarifies that the area of interest and Presence Reporting Area are equivalent for AMF.  For acquiring AMF address if the AMF is not controlled by the PCF, it is proposed that the SMF stores the AMF address to the UDM during the PDU session establishment, and the PCF responsible for the PCC control of the UE PDU session fetches the AMF address from the UDM for the subscription of PRA change.   When the AMF is changed, the subscription of PRA change is transferred from the old AMF to the new AMF and the new AMF notifies the PCF with the current status related to the subscription of PRA change.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15850,"status":"postponed","reservation_date":"2018-01-15 08:36:04","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"S2-181796","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180269.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180270","title":"23.724: KI: Enhanced Coverage","source":"Sony, Ericsson, Huawei, HiSilicon, Intel","contact":"Lars Nord","contact-id":58638,"tdoctype":"pCR","for":"Approval","abstract":"Discuss the background for CN functionality supporting RAN feature Enhanced Coverage and propose aspects to be studied.","secretary_remarks":"Revised in parallel session to S2-180831.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20930,"status":"revised","reservation_date":"2018-01-15 08:38:37","uploaded":"2018-01-16 14:41:36","revisionof":"","revisedto":"S2-180831","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180270.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180271","title":"23.716: Support of Trusted Non-3GPP Access","source":"Motorola Mobility, Lenovo, Broadcom","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"pCR","for":"Approval","abstract":"In order to enable support of Trusted Non-3GPP Access Networks in the 5G system, changes are proposed to TR 23.716","secretary_remarks":"Not Handled","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20360,"status":"not treated","reservation_date":"2018-01-15 08:42:13","uploaded":"2018-01-16 14:45:30","revisionof":"","revisedto":"S2-181581","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180271.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180272","title":"23.716: Support for RGs that do not support NAS","source":"Motorola Mobility, Lenovo, Broadcom","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"pCR","for":"Approval","abstract":"In order to enable Residential Gateways (RGs) that do not implement the NAS MM\/SM protocols to register to 5GC (as per key issue #2), changes are proposed to TR 23.716","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19850,"status":"noted","reservation_date":"2018-01-15 08:43:30","uploaded":"2018-01-16 14:45:30","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180272.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180273","title":"23.793: Establishment of MA-PDU Sessions","source":"Motorola Mobility, Lenovo","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"pCR","for":"Approval","abstract":"This document proposes to add a new solution in TR 23.793 that addresses Key Issue#5: Multi-access PDU sessions (Un-trusted access). The solution aims at supporting Multi-Access PDU sessions, which can be a key enabler for the ATSSS feature.","secretary_remarks":"Revised in parallel session to S2-180987.","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20520,"status":"revised","reservation_date":"2018-01-15 08:46:33","uploaded":"2018-01-16 14:45:31","revisionof":"","revisedto":"S2-180987","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180273.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180274","title":"23.503: Clarification on the PRA support","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Removed the PRA change event triger from the SMF event table and removed description on management of PRA in the SMF for PCF subscribing the PRA change.  Clarified that PRA and area of interest are equivalent.  Added the description on how a PCF get the AMF address for subscribing event notification.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15860,"status":"postponed","reservation_date":"2018-01-15 08:49:12","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180274.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180275","title":"23.503: Update on the event subscription","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: All the event reporting are subject to NF consumer subscription. And the column 'Conditions for reporting' is removed.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15780,"status":"postponed","reservation_date":"2018-01-15 08:56:10","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180275.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180276","title":"23.503: Add content for Management of packet flow descriptions","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the content of PFD management requirments to 4.2.4","secretary_remarks":"Merged into S2-180989","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15260,"status":"merged","reservation_date":"2018-01-15 09:09:56","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180276.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180277","title":"23.503: Remove some ENs","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove the above referred ENs.","secretary_remarks":"Revised in parallel session to S2-180988.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15220,"status":"revised","reservation_date":"2018-01-15 09:13:10","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"S2-180988","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180277.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180278","title":"23.501: Clarification on enforcement of Application Detection","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Description is added for Application Detection and Control.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15690,"status":"not treated","reservation_date":"2018-01-15 09:26:26","uploaded":"2018-01-16 13:10:37","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180278.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180279","title":"23.503: Clarification on enforcement of Application Detection Control","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Correction on description related to Application detection and control.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15700,"status":"not treated","reservation_date":"2018-01-15 09:26:26","uploaded":"2018-01-16 13:10:37","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180279.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180280","title":"23.401: Clarification on PRA reporting in ECM-IDLE state","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: A NOTE is added to clarify the behaviour of MME\/SGSN upon receiving request for change of UE presence in PRA reporting when UE is in CM-IDLE state.","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24050,"status":"withdrawn","reservation_date":"2018-01-15 09:26:26","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180281","title":"23.401: Clarification on Dual Connectivity with NR","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: Indication of UE support for Dual Connectivity with NR is provided by MME towards PCRF.","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24060,"status":"withdrawn","reservation_date":"2018-01-15 09:26:26","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"EDCE5"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180282","title":"23.203: Clarification on Dual Connectivity with NR","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: (related to NGA087)","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24070,"status":"withdrawn","reservation_date":"2018-01-15 09:26:26","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.203,"crspecversion":"15.1.0","workitem":[{"winame":"EDCE5"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180283","title":"23.501: Clarification on usage of additional Priority Level","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The additional Priority Level parameter together with the standardized 5QI is replaced with ARP priority level.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14490,"status":"noted","reservation_date":"2018-01-15 09:26:26","uploaded":"2018-01-16 13:10:37","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180283.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180284","title":"23.503: Influence of additional non-standardized QoS parameters on QoS Flow Binding","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The additional AW\/MDBV added into PCC Rule information and considered during QoS Flow Binding.","secretary_remarks":"Revised in parallel session to S2-180993.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15360,"status":"revised","reservation_date":"2018-01-15 09:26:26","uploaded":"2018-01-16 13:10:38","revisionof":"","revisedto":"S2-180993","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180284.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180285","title":"Discussion for UE vs network based EPS Fallback","source":"Huawei, ZTE, CATR, vivo, OPPO, China Unicom, China Telecom, CATT, China Mobile?","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Approval","abstract":"This paper discusses the EPS fallback solutions and proposes way forward.","secretary_remarks":"Confirm Sources! Noted in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16620,"status":"noted","reservation_date":"2018-01-15 09:37:18","uploaded":"2018-01-16 12:21:46","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180285.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180286","title":"23.501: Clarification of EPS or RAT fallback feature","source":"Huawei, HiSilcon, ZTE, China Unicom, OPPO, CATR, Qualcomm Incorporated, China Telecom, CATT, vivo, China Mobile?","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add a new sub clause to TS 23.501 to describe network based EPS Fallback feaure","secretary_remarks":"Confirm Sources! Merged into S2-180884","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16660,"status":"merged","reservation_date":"2018-01-15 09:37:18","uploaded":"2018-01-16 12:21:47","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180286.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180287","title":"23.791: Key issue of FS-eNA on service based resource management","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution is to propose a key issue for FS-eNA that how the eNA feature can be used to do service based resource management.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21610,"status":"postponed","reservation_date":"2018-01-15 09:37:18","uploaded":"2018-01-16 12:21:47","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180287.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180288","title":"23.501: Editorial on support for LADN","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Editorial modifications.","secretary_remarks":"Merged into S2-181111.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13250,"status":"merged","reservation_date":"2018-01-15 10:05:31","uploaded":"2018-01-16 13:10:38","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180288.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180289","title":"[DRAFT] LS Response on PDU session release timers in 'SSC mode 3'","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"This contribution proposes to answer the LS from CT WG1 .","secretary_remarks":"Response to S2-180025. Merged into S2-181104.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13030,"status":"merged","reservation_date":"2018-01-15 10:05:31","uploaded":"2018-01-16 13:10:38","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180289.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180290","title":"23.502: Clarification on PDU Session Release timer provided to the UE for 'SSC mode 3'","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Provide the release timer to the UE by transparent means.","secretary_remarks":"Revised, merging S2-180169 and S2-180373, to S2-181105.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13000,"status":"revised","reservation_date":"2018-01-15 10:05:31","uploaded":"2018-01-16 13:10:38","revisionof":"","revisedto":"S2-181105","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180290.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180291","title":"23.731: Key issues for eLCS on support high accuracy positioning","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution discusses and proposes key issue for support high accuracy positioning.","secretary_remarks":"Merged into S2-180907","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22030,"status":"merged","reservation_date":"2018-01-15 10:12:51","uploaded":"2018-01-16 11:28:08","revisionof":"","revisedto":"S2-180908","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180291.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180292","title":"23.502: 502: clarification UDR usage in MM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that UDM\/PCF may invoke UDR services are clarified.","secretary_remarks":"Revised to S2-181252.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12700,"status":"revised","reservation_date":"2018-01-15 10:13:02","uploaded":"2018-01-16 14:55:18","revisionof":"","revisedto":"S2-181252","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180292.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180293","title":"Emergency Services Support indication per RAT","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discusses whether Emergency Service Support indication per RAT is needed","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16790,"status":"noted","reservation_date":"2018-01-15 10:18:38","uploaded":"2018-01-16 10:01:54","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180293.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180294","title":"23.502: 502: Correction of UDR usage in SM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that UDM\/PCF may invoke UDR services are clarified.","secretary_remarks":"Revised to S2-181272.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13720,"status":"revised","reservation_date":"2018-01-15 10:19:34","uploaded":"2018-01-16 14:55:18","revisionof":"","revisedto":"S2-181272","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180294.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180295","title":"23.793 Key issue update on traffic switching","source":"BT Plc","contact":"Weng Chooi","contact-id":71520,"tdoctype":"pCR","for":"Approval","abstract":"This contribution considers current 'basic' support for traffic steering & switching in 5GS Ph1 and provides update to key issue on traffic switching","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20420,"status":"noted","reservation_date":"2018-01-15 10:22:22","uploaded":"2018-01-16 14:14:44","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180295.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180296","title":"23.501: Emergency Services Support indication per RAT","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove the editor note and clarify the related description. Editor's note: need for per RAT indicated will need to be confirmed.","secretary_remarks":"Revised in parallel session to S2-180887.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16800,"status":"revised","reservation_date":"2018-01-15 10:28:03","uploaded":"2018-01-16 10:01:54","revisionof":"","revisedto":"S2-180887","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180296.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180297","title":"23.793: Key Issue 1 for ATSSS","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"pCR","for":"Approval","abstract":"This contribution discusses key issue 1 for ATSSS","secretary_remarks":"Revised in parallel session to S2-180983.","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20390,"status":"revised","reservation_date":"2018-01-15 10:34:37","uploaded":"2018-01-16 10:01:54","revisionof":"","revisedto":"S2-180983","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180297.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180298","title":"23.793: Key Issue 4 for ATSSS","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"pCR","for":"Approval","abstract":"This contribution discusses key issue 4 for ATSSS","secretary_remarks":"Revised in parallel session to S2-180985.","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20460,"status":"revised","reservation_date":"2018-01-15 10:43:35","uploaded":"2018-01-16 10:01:54","revisionof":"","revisedto":"S2-180985","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180298.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180299","title":"23.502: Clarification related to Subscription data type","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Alignment the descriptions with the Table 5.2.3.3.1-1 - Adding an new type 'Slice Selection Subscription data' into the Table 5.2.3.3.1-1  It can be used for the Registration with AMF re-allocation. Instead of getting whole subscription data, get  only information for slice selection. - Adding an additional field (UE context for a PDU session) for SMF Selection Subscription data into the  Table 5.2.3.3.1-1  It was an agreement during non-3GPP related session at SA#124 that the UE context for a PDU session  stored in UDM can be used for the H-SMF selection in HR roaming, in case of the handover to 3GPP  access from N3GPP access via different PLMN. - Adding an additional field (Static IP address\/prefix) for Session Management Subscription data into the  Table 5.2.3.3.1-1.","secretary_remarks":"Revised, merging S2-180471 and S2-180684, to S2-181190.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12530,"status":"revised","reservation_date":"2018-01-15 10:45:23","uploaded":"2018-01-16 10:46:05","revisionof":"","revisedto":"S2-181190","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180299.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180300","title":"23.502: Clarification on SMS related Subscription data","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Adding the SMS Subscription data type as a new type into the Table 5.2.3.3.1-1. - Updating the Registration procedures for SMS over NAS, about AMF retrieval (step 2) and SMSF retrieval (step 7) respectively. - Removing the descriptions about SMSF selection in order to transfer them into the new clause of TS 23.501.","secretary_remarks":"Revised in parallel session to S2-180868.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17150,"status":"revised","reservation_date":"2018-01-15 10:45:23","uploaded":"2018-01-16 10:46:05","revisionof":"","revisedto":"S2-180868","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180300.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180301","title":"23.501: Adding the new clause about SMSF selection","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding the new clause about SMSF Selection Basically, it is transferred from the existing text of clause 4.13.3.1 (Registration procedures for SMS over NAS) of TS 23.502, with minor updates.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17180,"status":"approved","reservation_date":"2018-01-15 10:45:23","uploaded":"2018-01-16 10:46:05","revisionof":"","revisedto":"S2-181501","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180301.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180302","title":"Discussion on PCF","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"discussion","for":"Decision","abstract":"This paper shows the questions and issues about PCF. Based on the agreements about these issues, we need to agree the draft CRs.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15040,"status":"noted","reservation_date":"2018-01-15 10:45:24","uploaded":"2018-01-16 10:46:05","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_125_Gothenburg\/Docs\/S2-180302.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180303","title":"23.501: Clarification on PCF selection","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Updating the PCF selection with the following proposals - The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF. - The SMF sends the PCF selected by the AMF to the SMF during the PDU session establishment procedure Fixing the typo in the clause 6.3.7.0","secretary_remarks":"Revised in parallel session to S2-180978.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15050,"status":"revised","reservation_date":"2018-01-15 10:45:24","uploaded":"2018-01-16 10:46:05","revisionof":"","revisedto":"S2-180978","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180303.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180304","title":"23.502: Clarification on PCF association","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 4.2.2.2.2-1: Registration, step 5: Removing 'PCF ID' because it is already included in UE context exchanged for inter-AMF mobility. Step 16: change 'PCF ID' into '(V-)PCF ID' - 4.16.1.2: Policy Association Establishment during Registration, step 2: proposal for the roaming case: The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF - 4.16.1.3: Policy Association Establishment during AMF relocation, step 2: proposal for the roaming case: The V-PCF receiving the PCF ID from old AMF shall include the H-PCF ID in the Npcf_AMPolicyControl Get operation. - 4.16.3.2: AMF-initiated Policy Association Termination, step 1: removing the unnecessary text based on the agreement at SA WG2#124. - 5.2.2.2.2: Table 5.2.2.2.2-1: UE Context in AMF - adding 'PCF ID' based on the agreement at SA WG2#124, and additionally 'H-PCF ID' based on the proposal on V\/H-PCF selection by AMF","secretary_remarks":"Revised in parallel session, merging S2-180644, to S2-180979.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15090,"status":"revised","reservation_date":"2018-01-15 10:45:24","uploaded":"2018-01-16 10:46:05","revisionof":"","revisedto":"S2-180979","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180304.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180305","title":"23.503: Clarification PCF interaction","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 4.2.2: general clarification - 5.3.3: general clarification - 5.3.4: clarification on unclear description about roaming options, LBO and HR. HR or LBO should be referring to a particular PDU session instead of per UE. \u00e8 Proposing two alternatives. One should be selected. - 6.1.2.1: removing the unnecessary text based on the agreement at SA WG2#124. - 6.1.2.2, 6.1.2.2.1: general clarification","secretary_remarks":"Revised in parallel session to S2-180980.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15120,"status":"revised","reservation_date":"2018-01-15 10:45:24","uploaded":"2018-01-16 10:46:05","revisionof":"","revisedto":"S2-180980","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180305.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180306","title":"23.502: Clarifications on EPS to 5GS handover procedure using N26","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The two ENs are to be removed","secretary_remarks":"Revised in parallel session to S2-180779.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17640,"status":"revised","reservation_date":"2018-01-15 10:54:58","uploaded":"2018-01-16 12:07:10","revisionof":"","revisedto":"S2-180779","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180306.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180307","title":"[DRAFT] LS reply on timers for the network-requested PDU session modification procedure and 'SSC mode 3'","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"Proposed reply to incoming LS in S2-180025","secretary_remarks":"Response to S2-180025. Merged into S2-181104.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13040,"status":"merged","reservation_date":"2018-01-15 12:21:04","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180307.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180308","title":"23.502: Correction on Notification control for GBR QoS flow","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the handling about the case when QoS targets can be fulfilled again to the PDU session modification procedure.","secretary_remarks":"Revised to S2-181193.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14400,"status":"revised","reservation_date":"2018-01-15 13:02:47","uploaded":"2018-01-16 14:11:54","revisionof":"","revisedto":"S2-181193","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180308.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180309","title":"23.503: Correction on Notification control for GBR QoS flow","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Add the case when applicable, access network sends a new notification informing SMF that GFBR can be fulfilled again. And the SMF sends the new notification to PCF which will be sent to AF. 2. Update access independent event trigger 'QoS targets of the QoS Flow cannot be fulfilled' to 'QoS targets of the QoS Flow cannot be fulfilled or can be fulfilled again' .","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14420,"status":"approved","reservation_date":"2018-01-15 13:02:47","uploaded":"2018-01-16 14:11:54","revisionof":"","revisedto":"S2-181569","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180309.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180310","title":"23.502: Reflective QoS Timer transmission during PDU Session establishment","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the PCF(if applied) and SMF should provide Reflective QoS Timer during PDU Session establishment procedures.","secretary_remarks":"Revised to S2-181155.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14300,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:54","revisionof":"","revisedto":"S2-181155","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180310.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180311","title":"23.503: Addition of Reflective QoS Timer in PDU session related policy information","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the Reflective QoS Timer as part of PDU Session related policy information..","secretary_remarks":"Revised to S2-181156.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14320,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:54","revisionof":"","revisedto":"S2-181156","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180311.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180312","title":"23.501: Corrections and clarifications for the usage of Packet Filter Set","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The direction of the packet filters in the Packet Filter Set is clarified in some places. For the description of the interaction with the UPF, SDF template is replaced by PDR. The QoS Flow mapping description is restructured and the corresponding figure updated.","secretary_remarks":"Revised to S2-181152, merging S2-180252.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14210,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:54","revisionof":"","revisedto":"S2-181152","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180312.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180313","title":"23.503: Clean up for BSF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Revise all the PCF Binding Support Functionality to Binding Support Function. 2) Delete the S-NSSAI in the tuple of selected PCF discovery. 3) Delete the EN: 'Additional information needed by the network functionality, e.g. for network slicing, is FFS.'","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15550,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:55","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180313.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180314","title":"23.501: Clean up for BSF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add BSF description and service in TS 23.501. Delete the EN: 'Potential relation with slicing are FFS.'","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15560,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:55","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180314.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180315","title":"Discussion on Session Binding Mechanism for non-IP PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution proposes to discuss how to support Session Binding Mechanism for non-IP PDU Sessions.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15600,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:55","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_125_Gothenburg\/Docs\/S2-180315.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180316","title":"23.503: Session Binding mechanism for non-IP PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The PCF uses the MAC address of the UE, the UE identity (e.g. SUPI), if present and DNN, if present to enforce the Session Binding. Add the access independent event trigger 'UE MAC address change' .","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15610,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180316.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180317","title":"23.501: Session Binding mechanism for non-IP PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: To be able to provide traffic detection information to the UPF, the SMF shall request the detection of UE MAC address allocation\/deactivation and reporting from the UPF. The UPF shall store the MAC addresses, detected in the UL traffic received from the UE, and report those for the PDU Session. The UPF shall remove a UE MAC address when there is no corresponding UL traffic for a specified Inactivity period (provided by the SMF) and report the deactivation.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15620,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180317.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180318","title":"23.502: Clean up for PCC related flows","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) General description instead of parameters for PCF to SMF. 2) Add the exact clause. 3) Add correct service description.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15910,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180318.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180319","title":"23.502: UE Policy Delivery","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Store the UE Policy status in the UDR. Update the UDR services.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14800,"status":"noted","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180319.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180320","title":"23.503: UE Policy Delivery","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Store the UE Policy status in the UDR. There is no need to add a UE Policy ID.","secretary_remarks":"Revised in parallel session to S2-180926.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14810,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"S2-180926","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180320.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180321","title":"23.502: Correction on the Policy association procedure during AMF relocation","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Reclassified the Policy Association Establishment procedure into two cases: a) Policy Association Establishment procedure with new PCF (No UE context); b) Policy Association Establishment procedure with old PCF (Has UE context). 2. Update the existing description for the procedure that old PCF is used. 3. Update the description about the Policy Association Establishment procedure in registration.","secretary_remarks":"Revised in parallel session to S2-180991.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15290,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"S2-180991","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180321.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180322","title":"23.502: PCF selection for AMF during inter NG-RAN node N2 based handover","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: During the inter NG-RAN node N2 handover procedure, the S-AMF should provides the PCF ID to T-AMF for PCF selection.","secretary_remarks":"Revised in parallel session to S2-180998.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15500,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"S2-180998","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180322.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180323","title":"23.502: Correction on PCF selection in SMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Add description about the AMF provide PCF information to SMF for PCF selection in PDU session management related procedures. 2. Correct the service name of step 3a and 5 in figure 4.3.2.2.1.","secretary_remarks":"Revised in parallel session to S2-180999.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15520,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"S2-180999","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180323.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180324","title":"23.503: Removal of editor's notes and addition of references to empty sections","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to remove those editor's notes.  The following empty sections are proposed to be filled with a description or reference to a description in TS 23.203:  - 4.2.4 Management of packet flow descriptions,  - 6.1.3.16 3GPP PS Data Off,  - 6.2.4 Unified Data Repository,  - 6.2.7 Network Exposure Function.","secretary_remarks":"Revised in parallel session, merging S2-180276, to S2-180989.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15240,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:57","revisionof":"","revisedto":"S2-180989","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180324.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180325","title":"23.503: Update of event trigger section","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to clarify that the RAT Type is reported together with the Access Type if applicable, i.e. the Access Type supports one or more RAT Types. Further relevant description from 23.203 is proposed to be added into the event trigger section","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15770,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180325.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180326","title":"23.724: Key Issue on infrequent small data transmission","source":"Huawei, HiSilicon, InterDigital Inc, AT&T, Convida, Intel, Motorola Mobility, Lenovo","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue for small data transmission","secretary_remarks":"Revised in parallel session, merging S2-180160 and S2-180217, to S2-180826.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20670,"status":"revised","reservation_date":"2018-01-15 13:08:38","uploaded":"2018-01-16 13:57:23","revisionof":"","revisedto":"S2-180826","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180326.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180327","title":"23.724: Key Issue on High Latency Communication","source":"Huawei, HiSilicon, Intel, AT&T","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue for high latency communication","secretary_remarks":"Merged into S2-180828.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20840,"status":"merged","reservation_date":"2018-01-15 13:08:38","uploaded":"2018-01-16 12:24:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180327.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180328","title":"23.724: Key Issue on Power Saving Functions","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"WITHDRAWN: This contribution proposes a key issue to study solutions to power saving","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24040,"status":"withdrawn","reservation_date":"2018-01-15 13:08:38","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180329","title":"23.724: Solution for Infrequent Small Data Transfer","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a solution to support infrequent small data transfer","secretary_remarks":"Not Handled","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21180,"status":"not treated","reservation_date":"2018-01-15 13:08:38","uploaded":"2018-01-16 13:57:23","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180329.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180330","title":"23.502: Update of handover cancel procedure","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: the SBA service (e.g. Nsmf_PDUSession_UpdateSMContext request\/response in the N11 interface) shall be used 5G system. Change 2: AMF is not involved in the delete of indirect data forwarding tunnel in 5G system. And also the figure 4.11.1.2.3-1 is updated. Change 3: 'handover cancel indication' is added into the handover cancel procedure.","secretary_remarks":"Revised to S2-181138.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16010,"status":"revised","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:56","revisionof":"","revisedto":"S2-181138","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180330.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180331","title":"23.501: Clarification of the interworking between 5G and GERAN\/UTRAN\/E-UTRAN when UE is in RRC-inactive state.","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: If a UE in CM-CONNECTED with RRC Inactive state performs cell selection to the GERAN\/UTRAN, as the 5G does not interwork with 3G\/2G system, the UE shall trigger the initial attach to the 2G\/3G network.  If a UE in CM-CONNECTED with RRC Inactive state performs cell selection to the E-UTRAN, the UE may trigger TAU or 'handover' attach to the the 4G network as described in section 5.17 'Interworking and Migration'.","secretary_remarks":"Revised in parallel session to S2-180876.","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16500,"status":"revised","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:56","revisionof":"","revisedto":"S2-180876","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180331.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180332","title":"23.501: Update of CM-CONNECTED state description considering RRC Inactive state","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: This contribution makes some update on the CM-CONNECTED state description in section 5.3.3 considering RRC Inactive state","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23960,"status":"withdrawn","reservation_date":"2018-01-15 13:20:29","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180333","title":"23.502: Align the UE location presence status of LADN Session into Network Triggered Service Request procedure","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: for the LADN PDU session, if UE presence in LADN is Unknown status and DL data arrives, the SMF may not trigger a notification to the AMF.","secretary_remarks":"Revised to S2-181108.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13120,"status":"revised","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:56","revisionof":"","revisedto":"S2-181108","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180333.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180334","title":"23.501: UE specific DRX parameter negotiation between UE and AMF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revised to S2-181253.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12720,"status":"revised","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"S2-181253","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180334.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180335","title":"23.502: UE specific DRX parameter negotiaction between UE and AMF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revised to S2-181254.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12790,"status":"revised","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"S2-181254","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180335.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180336","title":"23.502: Clarification on Communication Pattern and Expected UE behaviour","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add the Communication Pattern parameters into the parameter list of Expected UE Behaviour.","secretary_remarks":"Revised to S2-181124.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19090,"status":"revised","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"S2-181124","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180336.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180337","title":"TS 23.502_Discussion on Communication Pattern and Expected UE behaviour","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Approval","abstract":"This contribution deals with the communication pattern provisioning.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19080,"status":"noted","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180337.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180338","title":"23.501: Funtionalities mapping between CAPIF and NEF architecture","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add a new reference to TS 23.222 in the references part.  Add the CAPIF into abbreviation part.  Add a new sentence refer the role NEF in the CAPIF framework in clause 6.2.5.","secretary_remarks":"Not Handled","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18980,"status":"not treated","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180338.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180339","title":"Funtionalities mapping between CAPIF and SCEF architecture","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a new reference to TS 23.222 in the references part.  Add the CAPIF into abbreviation part.  Add a new sentence refer the role SCEF in the CAPIF framework in clause 4.4.8, and clarify that in a CAPIF, some of the functionalities of SCEF listed above are provided by the CAPIF core function as specified in TS 23.222[43], and that take precedence over the ones listed above when SCEF and CAPIF are both deployed..","secretary_remarks":"Not Handled","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18950,"status":"not treated","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":377.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180339.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180340","title":"23.501: Clarification on the Location reporting procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: The current location reporting procedure for the type of 'area of interest' when UE is in RRC Inactive or CM-CONNECTED status is not clear. This CR aims at clarifying this problem.","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23990,"status":"withdrawn","reservation_date":"2018-01-15 13:20:30","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180341","title":"TS 23.502_Discussion on alignment the timers inside UE when in RRC Inactive","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Agreement","abstract":"RAN may provide an elapsed time to AMF when RAN initiates UE context release indicating UE unreachable. However, such mechanism may cause the synchronization problem between AMF and UE. This contribution aims at dealing with this problem.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16520,"status":"noted","reservation_date":"2018-01-15 13:20:30","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180341.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180342","title":"23.502: Alignment the timers inside UE when in RRC Inactive","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Delete the related description of 'elapsed time' feature.","secretary_remarks":"Withdrawn in parallel session.","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16530,"status":"withdrawn","reservation_date":"2018-01-15 13:20:30","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180342.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180343","title":"23.502: Clarification on the services for External Parameter Provisioning","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Modify the original figure of 4.15.6.2-1, and related descriptions in clause 4.15.6.2 to reflect the proposals mentioned above.","secretary_remarks":"Revised to S2-181129.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19290,"status":"revised","reservation_date":"2018-01-15 13:20:30","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"S2-181129","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180343.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180344","title":"23.786: New key issue for 5G System architectures for V2X services","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a new key issue on 5G System architectures for V2X services for study in TR 23.786.","secretary_remarks":"Revised in parallel session to S2-181091.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19570,"status":"revised","reservation_date":"2018-01-15 13:23:41","uploaded":"2018-01-16 09:50:48","revisionof":"","revisedto":"S2-181091","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180344.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180345","title":"23.501: Clarification of UE Requested NSSAI","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that UE include S-NSSAI of established PDU sessions (PDN connections) into UE requested NSSAI.","secretary_remarks":"Revised to S2-181158.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11880,"status":"revised","reservation_date":"2018-01-15 13:37:06","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"S2-181158","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180345.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180346","title":"23.502: Cleanup of the service request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Per above reason of changes, the related clarification and changes are updated.","secretary_remarks":"Revised to S2-181164.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13350,"status":"revised","reservation_date":"2018-01-15 13:37:06","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"S2-181164","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180346.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180347","title":"23.501: Updates to network slicing and interworking with EPS","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. To clarify that for the HR romaing case, the PGW-C+SMF need map the S-NSSAI to the S-NSSAI of the serving PLMN per SLA.  2. To add 'default bearer ID of PDN connection' into the registration request sent from UE after UE moves to 5GS from EPS in 5.15.7.2 3. To clarify that V-SMF is selected based on S-NSSAI recived from UE for interworking without N26.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12050,"status":"postponed","reservation_date":"2018-01-15 13:37:06","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180347.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180348","title":"How multiple PDU sessions to same DN are transferred to EPS","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discusses how multiple PDU sessions to the same DN are transferred to EPS","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18010,"status":"noted","reservation_date":"2018-01-15 13:37:06","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180348.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180349","title":"23.501: Mobility of PDU sessions with same DNN from NGS to EPS","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In order that an appropriate PDU session of the same DNN is chosen, during the PDU Session establishment procedure, the UE sends a 'handover priority' to SMF via PCO. SMF notify it to UDM.  For deployment scenario without N26:  - When UE moves to EPS, the UE chooses the PDU session with highest 'handover priority', and send PDN connection establishment request to MME.  - For a DNN, the HSS+UDM sends the PGW-C+SMF ID with highest 'handover priority' to MME. - The PDN connection can be established in EPS correspondingly. For deployment scenario with N26: - AMF retrieves EPS bearer context from SMF, SMF returns the 'handover priority' of each EPS bearer context (i.e. PDU session) to AMF. - The AMF choose the PDU session with highest 'handover priority' and forward the EPC Bearer context to MME - So that PDU session with highest 'handover priority' will be transferred to EPS correspondingly.","secretary_remarks":"Not Handled","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18020,"status":"not treated","reservation_date":"2018-01-15 13:37:06","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180349.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180350","title":"23.501: Mobility of PDU sessions with same DNN from NGS to EPS","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In order that all PDU Session can be transferred to EPC network, the PGW-C\/UPF generate the temporary APN and notify it to the UE and UDM+HSS. UDM+HSS generated the temporary subscription data based on the DNN subscription data.  When the UE move to the EPC network, the APN sent by the PGW-C+SMF via the PCO is used to indicate which PDU Session is to be transferred to EPC network.","secretary_remarks":"Not Handled","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18030,"status":"not treated","reservation_date":"2018-01-15 13:37:06","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180350.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180351","title":"23.726: Key Issue Proposal: SMF and UPF Insert\/Relocation due to distributed DC deployment","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"In this contribution, it is proposed a new key issue to study the SMF and UPF insert or relocation due to distributed DC deployment.","secretary_remarks":"Merged into S2-180954","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21740,"status":"merged","reservation_date":"2018-01-15 13:37:06","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180351.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180352","title":"23.501: Release of PDN connection that cannot handover to 5G","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: Clarify that if a PDN connection cannot be handover to 5G, the AMF request the SMF+PGW-C serving PDN connection to release the resource.","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24010,"status":"withdrawn","reservation_date":"2018-01-15 13:37:06","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180353","title":"Release of PDN connection that cannot handover to 5G","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Approval","abstract":"WITHDRAWN: Clarify that if a PDN connection cannot be handover to 5G, the AMF request the SMF+PGW-C serving PDN connection to release the resource.","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24020,"status":"withdrawn","reservation_date":"2018-01-15 13:37:06","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180354","title":"23.502: AMF service consumer correction","source":"China Mobile","contact":"Jiang Yi","contact-id":56358,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: SMSF is added as a consumer of Namf_MT service operation.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17190,"status":"approved","reservation_date":"2018-01-15 14:03:25","uploaded":"2018-01-16 13:05:37","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180354.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180355","title":"23.502: SMSF address deactivation and activation in AMF","source":"China Mobile","contact":"Jiang Yi","contact-id":56358,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Theregistration and de-registration procedures are modified to clarify AMF handling of SMSF address in UE context if it is not deleted.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17200,"status":"approved","reservation_date":"2018-01-15 14:03:25","uploaded":"2018-01-16 13:05:37","revisionof":"","revisedto":"S2-181599","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180355.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180356","title":"23.502: Correction on SMSF Nsmsf_SMService_Activate service operation","source":"China Mobile","contact":"Jiang Yi","contact-id":56358,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: NF ID is added as input parameter of Nsmsf_SMService_Activate service operation","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17210,"status":"approved","reservation_date":"2018-01-15 14:03:25","uploaded":"2018-01-16 13:05:37","revisionof":"","revisedto":"S2-181600","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180356.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180357","title":"23.503: Clarification on AF using legacy Rx binding with relevant PCF","source":"China Mobile","contact":"Jiang Yi","contact-id":56358,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: New texts are added to clarify DRA is used to address and query BSF for relevant PCF, and to store binding information, for AFs using legacy Rx interface.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15590,"status":"noted","reservation_date":"2018-01-15 14:03:25","uploaded":"2018-01-16 13:05:37","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180357.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180358","title":"[DRAFT] Reply LS on Mobility management congestion control","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to CT WG1 LS in C1-175413\/S2-180027 on MM congestion control. This LS pertains to the handling of MM back-off timer across 3GPP systems","secretary_remarks":"Response to S2-180027 Revised, merging S2-180237 and S2-180682, to S2-181189.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12440,"status":"revised","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"S2-181189","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180358.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180359","title":"23.501: Draft CR 23.501 Correction of the definitions of Allowed NSSAI and Configured NSSAI","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Rephrasing: 'S-NSSAIs values the UE may use' - Rephraseing: 'applicable to one or more PLMNs'","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11560,"status":"endorsed","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180359.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180360","title":"Allowed NSSAI and Access Type","source":"MediaTek Inc., Nokia, Nokia Shanghai Bell, Intel","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discusses and clarifies the use of Allowed NSSAI when the UE is registered both for 3GPP access and for N3GPP access.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11600,"status":"not treated","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09: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_125_Gothenburg\/Docs\/S2-180360.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180361","title":"23.501: Draft CR 23.501 Allowed NSSAI and Access Type","source":"MediaTek Inc., Nokia, Nokia Shanghai Bell, Intel Corporation","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The Access Type is indicated whenever required Misc. other corrections","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11610,"status":"not treated","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180361.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180362","title":"23.501: Draft CR 23.501 Correction to rejected NSSAI","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 'Permanently' is removed - UE behaviour when a rejected S-NSSAI becomes allowed again is defined","secretary_remarks":"Revised in parallel session to S2-181122","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11830,"status":"revised","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"S2-181122","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180362.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180363","title":"23.501: Draft CR 23.501 Correction to Emergency Fallback","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Rephrasing to alllow emergency session over untrusted N3GPP access if the emergency session could not be established via 3GPP access - Indications are mutually exclusive - Misc. editorial corrections (Emergency Services)","secretary_remarks":"Revised in parallel session to S2-180888.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16820,"status":"revised","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"S2-180888","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180363.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180364","title":"23.501: Draft CR 23.501 Clarification of SUCI","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: A new sub-clause is added (after SUPI) including a simple definition (quote from TS 33.501) and a reference to TS 33.501","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11410,"status":"approved","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180364.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180365","title":"23.501: Draft CR 23.501 Miscellaneous editorial corrections (capitalization, messages, procedures etc.)","source":"MediaTek Inc., Nokia, Nokia Shanghai Bell","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Inconsistencies removed Misc. editorials corrected (e.g. 'In this Release of the specification' used consistently, Non-breaking spaces) \u00a75.4.6.3 heading is properly formatted","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11500,"status":"endorsed","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180365.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180366","title":"UE Impact of Reflective QoS","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"discussion","for":"Agreement","abstract":"This discussion paper follows discussions that took place in CT WG1 and that need conclusions in SA WG2 regarding mitigation of UE impact of RQoS","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14340,"status":"noted","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09: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_125_Gothenburg\/Docs\/S2-180366.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180367","title":"23.501: Draft CR 23.501 Number of QoS rules and packet filters","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Number of concurrent QoS rules and packet filters is defined through a ref. to TS 24.501.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14350,"status":"noted","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180367.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180368","title":"23.501: Draft CR 23.501 Reflective QoS support indication at PDU Session Establishment \/ Modification","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - The UE supporting RQoS functionality selectively indicates whether RQoS is supported for a PDU Session - The UE triggers a PDU Session Modification to limit the further use of RQoS for a PDU Session.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14360,"status":"postponed","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180368.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180369","title":"23.502: Draft CR 23.502 Reflective QoS support indication at PDU Session Establishment \/ Modification","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The UE triggers a PDU Session Modification to limit the further use of RQoS for a PDU Session.","secretary_remarks":"Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14370,"status":"not treated","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180369.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180370","title":"23.502: Mobility restrictions (service area) when roaming","source":"NEC","contact":"Sivasubramaniam Ramanan","contact-id":28064,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 4.16.1.2 step 3; Npcf_AMPolicyControl_Get response for Policy Association Establishment during Registration 4.16.1.3 step 3; Npcf_AMPolicyControl_Get response for Policy Association Establishment during AMF relocation 4.16.2.1 subclause title; minor correction 4.16.2.2; Npcf_AMPolicyControl_UpdateNotify in case of roaming scenario","secretary_remarks":"Revised in parallel session to S2-181039.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15820,"status":"revised","reservation_date":"2018-01-15 14:25:22","uploaded":"2018-01-16 10:59:04","revisionof":"","revisedto":"S2-181039","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180370.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180371","title":"23.501: Draft CR 23.501 Corrections to RQoS logic when receiving DL packet with RQI","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The condition of QFI change is set after the re-start of the RQ Timer.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14380,"status":"approved","reservation_date":"2018-01-15 14:26:27","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180371.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180372","title":"23.501: Remaining IP address\/prefix lifetime with SSC mode 3","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies how the network signals the remaining lifetime for a PDU Session in case of SSC mode 3 with multiple PDU Sessions and with Multi-homed IPv6 PDU Session.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":12970,"status":"approved","reservation_date":"2018-01-15 14:36:26","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"S2-181507","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180372.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180373","title":"23.502: Remaining IP address\/prefix lifetime with SSC mode 3","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Aligns the text in clause 4.3.5.2 with the text in clause 4.3.5.3.","secretary_remarks":"Merged into S2-181105","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":12990,"status":"merged","reservation_date":"2018-01-15 14:38:03","uploaded":"2018-01-16 14:50:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180373.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180374","title":"Clarification on HO with unchanged eNB - DP","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"discussion","for":"Approval","abstract":"This paper is to clarify that the source and target RAN node id may be the same for HO procedure","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17020,"status":"noted","reservation_date":"2018-01-15 14:48:34","uploaded":"2018-01-16 10:16:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180374.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180375","title":"23.502: Clarification on HO with unchanged eNB - CR","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) The target id is the same as source id and this is a normal case. Since the LTE cell identity is blind to CN type and cell identity is composed of eNB id + cell id, the eNB id will not be changed when UE changes its access from 5GC to EPC or vice versa. 2) The target to source container does not need to be transferred via handover required\/handover relocation\/handover request as figure-1 shows, and also the Target to Source container is not need.  Actually, it will help the eNB to process Inter-node RRC message (the source to target container) as defined in 3x.331in parallel with handover preparation time so as to accelerate handover procedure.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17030,"status":"noted","reservation_date":"2018-01-15 15:02:33","uploaded":"2018-01-16 10:16:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180375.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180376","title":"23.787: Solution for UE assisted enrypted traffic detection","source":"OPPO. China Unicom","contact":"Yang Xu","contact-id":63572,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a solution for encrypted traffic detection and verification.","secretary_remarks":"Revised in parallel session to S2-180964.","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21380,"status":"revised","reservation_date":"2018-01-15 15:07:02","uploaded":"2018-01-16 10:16:02","revisionof":"","revisedto":"S2-180964","release":"Rel-16","crspec":23.787,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180376.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180377","title":"23.502: LADN Signalling to SMF","source":"Sony","contact":"Svante Aln\u00e5s","contact-id":62551,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) In the signalling from AMF to SMF include sufficient information to SMF regarding LADN so that SMF are able to process the request directly 2) Add GPSI in the corresponding interface to SMF","secretary_remarks":"Revised, merging S2-180751, to S2-181114.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13270,"status":"revised","reservation_date":"2018-01-15 15:08:41","uploaded":"2018-01-16 14:33:43","revisionof":"","revisedto":"S2-181114","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180377.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180378","title":"23.787: Key Issue interworking for encrypted traffic detection","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"pCR","for":"Approval","abstract":"This proposes a KI for ENTRADE study","secretary_remarks":"Revised in parallel session to S2-180962.","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21320,"status":"revised","reservation_date":"2018-01-15 15:11:51","uploaded":"2018-01-16 10:16:02","revisionof":"","revisedto":"S2-180962","release":"Rel-16","crspec":23.787,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180378.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180379","title":"23.502: Different configured NSSAI based on device type","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add UE device type in term of SST (UE supported SST) in initial registration request and AMF may trigger UEconfiguration update procedure to update the Configured NSSAI.","secretary_remarks":"Revised in parallel session to S2-181119.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11690,"status":"revised","reservation_date":"2018-01-15 15:16:35","uploaded":"2018-01-16 10:16:02","revisionof":"","revisedto":"S2-181119","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180379.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180380","title":"Updating UE Route Selection Policy - DP","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"discussion","for":"Approval","abstract":"Discussion the proposals to further update URSP","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14540,"status":"noted","reservation_date":"2018-01-15 15:23:43","uploaded":"2018-01-16 10:16:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180380.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180381","title":"CN selection in redirection for connected UE - DP","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"discussion","for":"Approval","abstract":"How to make UE select to the correct CN when performing RRC redirection","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18220,"status":"noted","reservation_date":"2018-01-15 15:27:23","uploaded":"2018-01-16 10:16:02","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_125_Gothenburg\/Docs\/S2-180381.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180382","title":"Alignment CR for for storing CE mode B UE capability in MME","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligns the table in TS 23.401 cl. 5.7.2 with the decision to store the UEs CE ModeB capability","secretary_remarks":"Revised in parallel session to S2-181238.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10960,"status":"revised","reservation_date":"2018-01-15 15:28:27","uploaded":"2018-01-16 13:33:56","revisionof":"","revisedto":"S2-181238","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3378.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180382.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180383","title":"Use of Preferred Network Behaviour","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"discussion","for":"Approval","abstract":"Analyses LS C1-175414 on the indication for Preferreed Network Behaviour and proposes a way forward.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10880,"status":"noted","reservation_date":"2018-01-15 15:28:28","uploaded":"2018-01-16 13:33:56","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_125_Gothenburg\/Docs\/S2-180383.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180384","title":"[DRAFT] Reply LS on indication of preferred CIoT network behaviour","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"Answer LS C1-175414","secretary_remarks":"Response to S2-180028 Revised in parallel session to S2-180843.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10910,"status":"revised","reservation_date":"2018-01-15 15:28:28","uploaded":"2018-01-16 13:36:37","revisionof":"","revisedto":"S2-180843","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180384.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180385","title":"Removal of hanging Editor's Note on support for deferred location","source":"Qualcomm Incorporated, Huawei, HiSilicon","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removes hanging Editor's Note from clause 9.1.1 of TS 23.271 that leaves the impression that deferred location request is not defined in this release of the specification","secretary_remarks":"Revised in parallel session to S2-180841.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10490,"status":"revised","reservation_date":"2018-01-15 15:28:28","uploaded":"2018-01-16 13:33:56","revisionof":"","revisedto":"S2-180841","release":"Rel-14","crspec":23.271,"crspecversion":"14.3.0","workitem":[{"winame":"CIoT_Ext"},{"winame":"TEI15"}],"crnumber":430.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180385.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180386","title":"Removal of hanging Editor's Note on support for deferred location","source":"Qualcomm Incorporated, Huawei, HiSilicon","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: Removes hanging Editor's Note from clause 9.1.1 of TS 23.271 that leaves the impression that deferred location request is not defined in this release of the specification","secretary_remarks":"Revised in parallel session to S2-180842.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10510,"status":"revised","reservation_date":"2018-01-15 15:28:29","uploaded":"2018-01-16 13:33:56","revisionof":"","revisedto":"S2-180842","release":"Rel-15","crspec":23.271,"crspecversion":"14.3.0","workitem":[{"winame":"CIoT_Ext"},{"winame":"TEI15"}],"crnumber":431.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180386.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180387","title":"23.502: Preservation of GBR QoS Flows upon redirection","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Proposes to rename the cause code for AN release from 'inter-system redirection' to 'UE redirection'.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16050,"status":"approved","reservation_date":"2018-01-15 15:28:30","uploaded":"2018-01-16 13:33:56","revisionof":"","revisedto":"S2-181871","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180387.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180388","title":"Voice fallback (normal voice calls)","source":"Qualcomm Incorporated, Huawei, ZTE","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"discussion","for":"Approval","abstract":"Identifies some issues related to voice fallback for normal voice calls.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16630,"status":"noted","reservation_date":"2018-01-15 15:28:30","uploaded":"2018-01-16 13:33:56","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_125_Gothenburg\/Docs\/S2-180388.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180389","title":"23.715: Solution for Restricted IMS Local Operator Services","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"pCR","for":"Approval","abstract":"Discusses the system impacts for providing access to IMS Restricted Local Operator Services (RLOS).","secretary_remarks":"Not Handled","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22750,"status":"not treated","reservation_date":"2018-01-15 15:28:30","uploaded":"2018-01-16 13:33:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180389.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180390","title":"23.739: Applicability of SSC mode 3 for mobility with Low Latency Communication","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"pCR","for":"Approval","abstract":"Discusses the applicability of SSC mode 3 for mobility with LLC.","secretary_remarks":"Revised in parallel session to S2-180850.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22940,"status":"revised","reservation_date":"2018-01-15 15:28:30","uploaded":"2018-01-16 13:33:56","revisionof":"","revisedto":"S2-180850","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180390.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180391","title":"23.739: Lack of support for IPv6 multihoming in EPC","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"pCR","for":"Approval","abstract":"Discusses the requirements for PDN types and IP versions supported for FS_LLC_mob.","secretary_remarks":"Revised in parallel session to S2-180854.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22970,"status":"revised","reservation_date":"2018-01-15 15:28:30","uploaded":"2018-01-16 13:33:56","revisionof":"","revisedto":"S2-180854","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180391.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180392","title":"23.501: Subscriber Permanent and Concealed Identifiers","source":"Orange, Telecom Italia, AT&T","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Addition of a definition of SUCI in clause 5.9.2, referring to TS 33.501. Extention of the requirement to contain the address of the home network to SUCI. 2) Removal of the second bullet in clause 5.9.2 and clarification of the following paragraph.","secretary_remarks":"Revised to S2-181102.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11420,"status":"revised","reservation_date":"2018-01-15 15:37:49","uploaded":"2018-01-16 14:45:22","revisionof":"","revisedto":"S2-181102","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180392.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180393","title":"23.501: CN selection in redirection for connected UE - CR","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: clarify that the redirection is used only for system interworking","secretary_remarks":"Not Handled","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18230,"status":"not treated","reservation_date":"2018-01-15 15:43:01","uploaded":"2018-01-16 10:16:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180393.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180394","title":"Selection of MME for a UE supporting NR","source":"ORANGE","contact":"Thouraya Toukabri","contact-id":66374,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: add the requirement that makes the eNB able to select an MME based on the UE NR capability","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11070,"status":"noted","reservation_date":"2018-01-15 15:44:07","uploaded":"2018-01-16 14:23:21","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"EDCE5"}],"crnumber":3379.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180394.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180395","title":"23.501: Slicing configuration update","source":"Motorola Mobility, Lenovo","contact":"Genadi Velev","contact-id":70944,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution proposes to update the Newtork Slice configuration description implementing the Prosals 1 - 4 from the 'Reason for change'.","secretary_remarks":"Revised to S2-181163.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11650,"status":"revised","reservation_date":"2018-01-15 15:44:21","uploaded":"2018-01-16 14:45:40","revisionof":"","revisedto":"S2-181163","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180395.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180396","title":"23.502: update Nnrf_NFDiscovery service based on the UE IP address","source":"China Mobile","contact":"Wei Chen","contact-id":57801,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: New texts are added to clarify that UE IP address can be a opitional input parameter in Nnrf_NFDiscovery service to allow NEF to discover the BSF with the input of UE IP address.  Besides, BSF is added into the cosumers list of Nnrf_NFManagement_NFRegister service to make NRF to store the BSF service information.","secretary_remarks":"Revised to S2-181130.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19350,"status":"revised","reservation_date":"2018-01-15 15:47:37","uploaded":"2018-01-16 14:29:21","revisionof":"","revisedto":"S2-181130","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180396.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180397","title":"23.724: Restricted connectivity to allow initial IoT UE remote provisioning","source":"Motorola Mobility, Lenovo","contact":"Genadi Velev","contact-id":70944,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new Key Issue on the restricted connectivity to allow initial IoT UE remote provisioning.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21150,"status":"postponed","reservation_date":"2018-01-15 15:47:41","uploaded":"2018-01-16 14:45:40","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180397.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180398","title":"Discussion to Enhancements of Service-Based Architecture in R16","source":"China Mobile, Sprint","contact":"Tao Sun","contact-id":54129,"tdoctype":"discussion","for":"Approval","abstract":"Provide discussion on the enhancement of SBA in R16","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23170,"status":"noted","reservation_date":"2018-01-15 15:49:33","uploaded":"2018-01-16 14:55:18","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_125_Gothenburg\/Docs\/S2-180398.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180399","title":"23.501: Clarification on interworking without N26 is supported","source":"LG Electronics, Orange","contact":"Jinsook Ryu","contact-id":39022,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to clarify 'dual registration mode indication' to 'interworking without N26 is supported'.","secretary_remarks":"Merged into S2-180791","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18330,"status":"merged","reservation_date":"2018-01-15 15:57:05","uploaded":"2018-01-16 11:13:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180399.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180400","title":"23.502: Clarification for dual registration regarding HO process - 23.502","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to solve this problem using following method: Interworking from 5GS ->EPS: When UE is in connected mode and RAN sends handover required to AMF\/MME to trigger inter-system handover, the AMF will send Relocation request to MME. If UE already attached to EPS, the MME shall reject the Relocation request with a cause indicating the UE attached to MME already. Then, the AMF send the rejection to NG-RAN. Based on the rejection and the cause, NG-RAN triggers RRC redirection as depicted in clause 5.17.2.3.4 in TS 23.501. Interworking from EPS ->5GS: A vice-versa procedure to 5GS->EPS shall be used.","secretary_remarks":"Not Handled","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18250,"status":"not treated","reservation_date":"2018-01-15 15:58:18","uploaded":"2018-01-16 10:16:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180400.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180401","title":"23.502: Clarification on interworking without N26 is supported","source":"LG Electronics, Orange","contact":"Jinsook Ryu","contact-id":39022,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to clarify 'interworking without N26' to 'interworking without N26 is supported'","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18290,"status":"noted","reservation_date":"2018-01-15 16:01:03","uploaded":"2018-01-16 11:13:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180401.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180402","title":"23.501: Clarification for dual registration regarding HO process -23.501","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change:  It is proposed to solve this problem using following method: Interworking from 5GS ->EPS: When UE is in connected mode and RAN sends handover required to AMF\/MME to trigger inter-system handover, the AMF will send Relocation request to MME. If UE already attached to EPS, the MME shall reject the Relocation request with a cause indicating the UE attached to MME already. Then, the AMF send the rejection to NG-RAN. Based on the rejection and the cause, NG-RAN triggers RRC redirection as depicted in clause 5.17.2.3.4 in TS 23.501. Interworking from EPS ->5GS: A vice-versa procedure to 5GS->EPS shall be used.","secretary_remarks":"Opened in parallel session. Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18240,"status":"noted","reservation_date":"2018-01-15 16:02:19","uploaded":"2018-01-16 10:16:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"2.0.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180402.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180403","title":"23.501: Clarification on SMF selection for interworking","source":"LG Electronics","contact":"Jinsook Ryu","contact-id":39022,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is clarified that AMF shall select same SMF for multiple PDU sessios to support interworking with EPS.","secretary_remarks":"Revised in parallel session to S2-180786.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18040,"status":"revised","reservation_date":"2018-01-15 16:03:54","uploaded":"2018-01-16 11:13:53","revisionof":"","revisedto":"S2-180786","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180403.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180404","title":"23.503: Updating UE Route Selection Policy - CR","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Updating the RSD table for URSP Rule structure to introduce the Index parameter and how to use it - Proposing to update URSP in Policy\/Rule\/RSD level - Describe how to prioritize the rule to use considering both precedence and rule id - Describing UE can try to establish PDU Session based on rejection cause","secretary_remarks":"Merged into S2-180966","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14550,"status":"merged","reservation_date":"2018-01-15 16:07:56","uploaded":"2018-01-16 10:16:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180404.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180405","title":"23.501: Further RRC Inactive assitance information","source":"NEC","contact":"Iskren Ianev","contact-id":59515,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following new assistance information is added to the RRC Inactive assistance information from the AMF to the gNB: - UE stationary indication. If the AMF is aware the connecting UE is stationary (e.g. from the UE mobility pattern in the AMF, see clause 5.3.4.2), the AMF may include in the 'RRC Inactive assistance information' an UE stationary indication to help with the NG RAN decision on whether to move the UE in RRC Inactive state and if so, what RNA to configure for it (e.g. the size of RNA); - UE moving trajectory information. If the AMF is aware of the connecting UE's moving trajectory (e.g. from the UE mobility pattern in the AMF, see clause 5.3.4.2), the AMF may include in the 'RRC Inactive assistance information' an UE moving trajectory information (e.g. the list of cells that are overlapped with the UE moving trajectory) to help with the NG-RAN decision on what RNA to configure for the UE in case the UE is moved to RRC Inactive state (e.g. the size and\/or","secretary_remarks":"Revised in parallel session to S2-180874.","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16440,"status":"revised","reservation_date":"2018-01-15 16:15:45","uploaded":"2018-01-16 11:50:48","revisionof":"","revisedto":"S2-180874","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180405.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180406","title":"Discussion on unsynchronized UE parameter during Service Request","source":"LG Electronics, Huawei","contact":"Jinsook Ryu","contact-id":39022,"tdoctype":"discussion","for":"Agreement","abstract":"This paper concerns the necessity of triggering of re-registration with service reject.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16060,"status":"noted","reservation_date":"2018-01-15 16:34:32","uploaded":"2018-01-16 11:24:17","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180406.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180407","title":"23.502: Removal of re-registration cause\/indication for service reject","source":"LG Electronics, Huawei","contact":"Jinsook Ryu","contact-id":39022,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) It is proposed that when the Service Request is rejected due to unsynchronized UE parameter (e.g. Service area restriction is not updated since the UE is in MICO) between the UE and AMF, the AMF shall perform UE Configuration Update procedure as specified in clause 4.2.4 to provide UE parameter before the UE is sent to CM-IDLE state. 2) It is proposed to remove indicating re-registration cause\/indication in Service Reject.","secretary_remarks":"Revised to S2-181140.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16070,"status":"revised","reservation_date":"2018-01-15 16:34:32","uploaded":"2018-01-16 11:24:17","revisionof":"","revisedto":"S2-181140","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180407.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180408","title":"23.503: Corrections to description of session management related policy enforcement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Move description of non-session management related event triggesr from 6.1.3 to 6.1.2.  2) Remove duplicate definition\/reference of SDF filter and correct the description for Ethernet PDU Session type 3) Add a description of predefined vs dynamic PCC rules (in line with definitojn in 23.203)","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15790,"status":"not treated","reservation_date":"2018-01-15 17:00:05","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"S2-181645, S2-181935","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180408.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180409","title":"23.502: User plane security policy","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Addition of User Plane Security Policy in the N2 SM info provided to RAN during UP connection activation.  The UP Sec. Policy is optionally provided by PCF to SMF, in case dynamic PCC is supported.","secretary_remarks":"Revised to S2-181199.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13980,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:41:41","revisionof":"","revisedto":"S2-181199","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180409.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180410","title":"[draft] Reply LS on User Plane Security Policy","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a reply to the SA WG3 LS on User Plane Security Policy","secretary_remarks":"Response to S2-180049. Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14050,"status":"not treated","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:52:43","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG3","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180410.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180411","title":"23.716: Adding Architectural Principles for Wireline Access","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Proposes a set of architectural principles for the 5WWC work","secretary_remarks":"Revised to S2-181172.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19870,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"S2-181172","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180411.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180412","title":"23.716: Registration Procedure for N1 capable CPE on Wireline Access","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Proposes a registration procedure for wireline access","secretary_remarks":"Not Handled","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20310,"status":"not treated","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180412.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180413","title":"23.726: ETSUN Key Issues","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a set of key issues, including use cases, for FS_ETSUN","secretary_remarks":"Merged into S2-180954","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21730,"status":"merged","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180413.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180414","title":"23.726: ETSUN Solution","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a solution for FS_ETSUN","secretary_remarks":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21850,"status":"not treated","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180414.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180415","title":"23.501: Corrections to UPF selection and resolution of related Editor's Note","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Marge into a single list. Generalize the topological aspects that may be taken into account by the SMF. Remove editor's note.","secretary_remarks":"Revised to S2-181273.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13800,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"S2-181273","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180415.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180416","title":"23.502: Clarifying setup of the security context in RAN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying that AMF sets up the security context in RAN only when user plane resources are setup.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12820,"status":"noted","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180416.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180417","title":"23.501: Clarifying provision of RRC Inactive assistance information to RAN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying that AMF supporting CM-CONNECTED with RRC Inactive shall provide RRC Inactive assistance information to RAN in relevant procedures.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16420,"status":"postponed","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180417.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180418","title":"23.502: RRC Inactive assistance information not provided to RAN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying that AMF supporting CM-CONNECTED with RRC Inactive shall provide RRC Inactive assistance information to RAN in relevant procedures. Removal of the RRC Inactive usage dependency to reception of the RRC Inactive assistance information.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16430,"status":"postponed","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180418.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180419","title":"23.503: UE policies granularity and UE assistance for policy evaluation.","source":"Ericsson, NEC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that a URSP\/WLANSP rule contains an identifier and that the PCF can perform operations (add\/delete\/replace) per individual URSP\/WLANSP rule. The UE sends at initial registration the list of UE policies currently stored in the device and the PCF uses this information as input for policy decisitions.","secretary_remarks":"Revised in parallel session, merging S2-180619 and S2-180564, to S2-180924.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14560,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-180924","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180419.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180420","title":"23.502: UE assisted UE policies calculation in PCF","source":"Ericsson, NEC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The UE includes in the Initial Registration procedure a list of ruleIds identifying the UE Policy rules (WLANSP and URSP rules) stored in the UE. At initial registration the PCF calculates the UE policy rules that apply to the UE in the current conditions and compares this information with the one received from the UE to determine the UE policy rules that need to be downloaded to the UE (avoiding the sending of duplicated UE policy rules to the UE).","secretary_remarks":"Revised in parallel session, merging S2-180618 and S2-180566, to S2-180965.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14740,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-180965","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180420.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180421","title":"Default QoS Rule discussion","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"Discussion on the Default QoS implications","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14240,"status":"noted","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 15:04:15","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_125_Gothenburg\/Docs\/S2-180421.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180422","title":"23.501: Introduction of 'Maximum Data Burst Volume for all GBR flows","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In last meeting it was agreed that a new QoS characteristics Parameter, Maximum Data Burst Volume', is introduced for GBR flows with PDB<20 ms. However, there is also a need to specify what data volume can be served for GBR flows with higher PDB. In S2-178049 values for Default Averaging Window are proposed for the standardized GBR 5QI's. The values are rather large, 2, and 3 s long, which correspond to unreasonable high requirements for the instantaneous bitrate in RAN. The instantaneous bitrate needed in RAN in order to serve the largest bursts that are within the GFBR requirement can be estimated by: GFBR*AW\/PDB The table below shows the largest burst size within the GFBR requirement, and the instantaneous bitrate that would be required in RAN to serve it within the PDB. 5QI PDB Averaging Window (AW) Largest data burst within GFBR Instantaneous bitrate 1 100 ms 2 s 2 * GFBR 20 * GFBR 2 150 ms 2 s 2 * GFBR 13 * GFBR 3 50 ms 3 s 3 * GFBR 60 * GFBR 4 300 ms 3 s 3 * G","secretary_remarks":"Revised to S2-181150.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14150,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:45:17","revisionof":"","revisedto":"S2-181150","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180422.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180423","title":"23.501: ARP usage clean-ups","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The characteristics may be signalled, in two cases: - A special 5QI is used where all characteristics are signalled. - For any 5QI, the parameters priority, Averaging window, and\/or Maximum Data Burst Volume may be signalled in order to override the default values. In section 5.7.1.2 it is stated: 'The 5QI value may indicate that a QoS flow have signalled QoS characteristics, and if so, the QoS characteristics are included in the QoS profile.' This text does not cover the second alternative, and should be re-formulated in order to avoid confusion. Proposal 1: Reformulate text, so that all signaled characteristics parameters are included","secretary_remarks":"Revised to S2-181194.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14430,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:45:17","revisionof":"","revisedto":"S2-181194","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180423.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180424","title":"23.501: Homogeneous support for IMS voice over PS Session supported indication","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding note on that a TA supports 'IMS Voice over PS Sessions' if the serving AMF indicates IMS voice over PS Session Supported Indication over 3GPP access to the UE, as described in clause 5.16.3.3.","secretary_remarks":"TS version is wrong in the coversheet. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17070,"status":"approved","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-181613","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180424.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180425","title":"EPS Fallback for Voice analysis","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"Discussion paper supporting options for EPS fallback for voice","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16650,"status":"noted","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:27:19","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_125_Gothenburg\/Docs\/S2-180425.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180426","title":"Adding 5GS to the Network Architecture","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a reference to 5GS.","secretary_remarks":"Revised to S2-181103.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11520,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:27:19","revisionof":"","revisedto":"S2-181103","release":"Rel-15","crspec":23.002,"crspecversion":"14.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":304.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180426.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180427","title":"23.724: Key Issue on Monitoring","source":"Convida Wireless LLC","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper an introduces a Key Issue on Monitoring for the FS_CIoT_5G TR","secretary_remarks":"Revised in parallel session to S2-180882.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21090,"status":"revised","reservation_date":"2018-01-15 17:09:46","uploaded":"2018-01-16 12:06:20","revisionof":"","revisedto":"S2-180882","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180427.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180428","title":"23.724: Key Issue on Support of Reliable Communication","source":"Convida Wireless LLC, Intel","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a Key Issue for FS_CIoT_5G related to Support for Reliable Communication.","secretary_remarks":"Revised in parallel session to S2-180878.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20970,"status":"revised","reservation_date":"2018-01-15 17:13:02","uploaded":"2018-01-16 12:06:20","revisionof":"","revisedto":"S2-180878","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180428.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180429","title":"23.724: Key Issue on Support of common north-bound APIs for EPC-5GC Interworking","source":"Convida Wireless LLC, AT&T","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes some architectural assumptions and a Key Issue for FS_CIoT_5G related to Support of common north-bound APIs for EPC-5GC Interworking","secretary_remarks":"Revised in parallel session to S2-180879.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21000,"status":"revised","reservation_date":"2018-01-15 17:16:01","uploaded":"2018-01-16 12:06:19","revisionof":"","revisedto":"S2-180879","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180429.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180430","title":"23.724: Key Issue on Network Parameter Configuration API via NEF","source":"Convida Wireless LLC, Intel","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a Key Issue on Network Parameter Configuration API via NEF for the FS_CIoT_5G TR","secretary_remarks":"Revised in parallel session to S2-180880.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21030,"status":"revised","reservation_date":"2018-01-15 17:22:15","uploaded":"2018-01-16 12:06:19","revisionof":"","revisedto":"S2-180880","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180430.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180431","title":"23.724: Key Issue on Support of equivalent overall functionalities as provided by SCEF for CIoT\/MTC","source":"Convida Wireless LLC, Qualcomm Incorporated","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a Key Issue on Support of equivalent overall functionalities as provided by SCEF for CIoT\/MTC for FS_CIoT_5G.","secretary_remarks":"Revised in parallel session to S2-180881.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21060,"status":"revised","reservation_date":"2018-01-15 17:26:03","uploaded":"2018-01-16 12:06:20","revisionof":"","revisedto":"S2-180881","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180431.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180432","title":"23.501: Supporting Common API framework for NEF","source":"Convida Wireless LLC, Qualcomm Incorporated","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies that functionality such as authentication, authorization and service capability API discovery are supported by the NEF based on the Common API Framework (CAPIF).","secretary_remarks":"Revised in parallel session to S2-181265","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18990,"status":"revised","reservation_date":"2018-01-15 17:53:09","uploaded":"2018-01-16 12:06:20","revisionof":"","revisedto":"S2-181265","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180432.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180433","title":"EPC support for mobility with low latency communication: discussion and solution proposal","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"discussion","for":"Approval","abstract":"Proposes an architecture principle and a procedure for make-before-break PDN connection mobility and proposes to either endorse them or document in the TR","secretary_remarks":"Revised in parallel session to S2-180849.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22900,"status":"revised","reservation_date":"2018-01-15 19:08:32","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"S2-180849","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_125_Gothenburg\/Docs\/S2-180433.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180434","title":"Discussion on PCC support of EPC IWK","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"discussion","for":"Discussion","abstract":"This paper evaluates the options on policy control for EPC IWK with the proposals.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15150,"status":"noted","reservation_date":"2018-01-15 19:19:33","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180434.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180435","title":"23.501: Clarification on PCC support of EPC IWK","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: AMF unsubscribes the policy notification when UE doesn't camp on 5GS.  The combined PCF\/PCRF needs to provide PCC rule or policy information applied to EPC only in addition.  The combined SMF\/PGW-C performs the PCC rule or policy adaptation so that only the PCC rules or policy applied to either EPC or 5GC are enforced.","secretary_remarks":"Revised in parallel session to S2-180981.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15160,"status":"revised","reservation_date":"2018-01-15 19:24:08","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"S2-180981","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180435.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180436","title":"23.503: Remove EN related with EPC IWK","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Removes the EN in 6.1.3.5 2. Removes the EN in 6.3.1 and adds a NOTE to the removed attibutes for the clarification that they are provided for EPC IWK in Table 6.3.1 3. Adds 6.1.3.18 for the description on EPC IWK","secretary_remarks":"Revised in parallel session to S2-180982.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15180,"status":"revised","reservation_date":"2018-01-15 19:27:17","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"S2-180982","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180436.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180437","title":"23.501: Network Sharing and Interworking with EPS- TS 23.501","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Delete the network behaviour description from clause 5.18.3. Clarify how NG-RAN selects the target PLMN in the order of (1) PLMN in use, (2) Prioritized list of PLMN IDs, (3) EPLMN list during the handover within 5GS. Add corresponding description on how UE selects the network during mobility between 5GS and EPS in case of network sharing and interworking with EPS. Add reference in clause 5.17 to address how network selection is performed by UE during Idle Mode mobility between 5GS and EPS for the single registration mode in case of network sharing.","secretary_remarks":"Revised to S2-181078.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11290,"status":"revised","reservation_date":"2018-01-15 19:47:31","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"S2-181078","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180437.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180438","title":"23.502: Clarification on N26 based HO procedure for the case of Network Sharing and Interworking with EPS- TS 23.502","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Delete the description on E-UTRAN and MME impacts for the N26 based handover between EPS and 5GS from 23.502. Add reference to 23.501 for the network selection in NG-RAN during handover procedure with N26 between EPS and 5GS in case of network sharing","secretary_remarks":"Merged into S2-181099.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11350,"status":"merged","reservation_date":"2018-01-15 19:47:31","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180438.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180439","title":"E-UTRAN and MME impacts during N26 based HO in the case of Network Sharing and Interworking with 5GS- TS 23.401","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Describe the impacts to E-UTRAN and MME for the N26 based handover between EPS and 5GS. Add the last used 5GS PLMN ID into the table of MME information storage in clause 5.7.2.","secretary_remarks":"Revised to S2-181100.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11360,"status":"revised","reservation_date":"2018-01-15 19:47:31","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"S2-181100","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3380.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180439.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180440","title":"23.502: Clarification on AMF behavior due to Subscriber Data Change in UDM","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add description and reference to clause 4.2.4.2, align the terminology used in clause 4.2.4.2 with clause 4.5.1. Add the Configured NSSAI into the UE Configuration Update Command message.","secretary_remarks":"Revised to S2-181251.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12660,"status":"revised","reservation_date":"2018-01-15 19:47:32","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"S2-181251","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180440.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180441","title":"23.501: Clarification in LADN clause 5.6.5 - TS 23.501","source":"Intel, ZTE, ETRI, KDDI","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The AMF and SMF know whether a DNN is a LADN DNN based on the UE subscription information received from the UDM. AMF indicates to UE whether a DNN is a LADN DNN. AMF indicates to UE that the LADN is not available in the UE's current Registration Area. Align the terms with 23.502 to 'UE presence in a LADN'. Add missing SMF behaviour when the UE presence in a LADN is OUT. Remove the redundant description for SMF behaviour when the UE presence in a LADN is IN or UNKNOWN.","secretary_remarks":"Revised, merging S2-180288 and S2-180545, to S2-181111.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13180,"status":"revised","reservation_date":"2018-01-15 19:47:32","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"S2-181111","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180441.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180442","title":"23.502: Clarification on LADN related aspects - TS 23.502","source":"Intel, ZTE, ETRI, KDDI","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify the SMF behaviour on rejecting the request when UE's presence in a LADN is OUT for the procedure of General Registration, UE Triggered Service Request, UE Requested PDU Session Establishment and Modification. Clarify how AMF updates UE about the LADN information change and UE behaviour when the LADN service area information is empty. Correct the wording of 'UE presence in LADN' to 'UE presence in a LADN' in clause 4.15.4. Add the detail on how the LADN DNN is indicated from UDM to AMF and SMF in clause 5.2.3.3.1.","secretary_remarks":"Revised to S2-181112.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13200,"status":"revised","reservation_date":"2018-01-15 19:47:32","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"S2-181112","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180442.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180443","title":"23.786: New key issue of Service Authorization for eV2X","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue of service authorization for eV2X in 5G system","secretary_remarks":"Revised in parallel session to S2-181081.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19670,"status":"revised","reservation_date":"2018-01-15 19:47:32","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"S2-181081","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180443.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180444","title":"Current 3GPP PS DATA OFF Feature Analysis and Potential Enhancement to 5GS","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution introduces the current PS Data Off feature introduced in LTE and analyzes the corresponding work needed for 5GS","secretary_remarks":"Revised off-line to S2-181076.","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23200,"status":"revised","reservation_date":"2018-01-15 19:47:32","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"S2-181076","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180444.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180445","title":"New WID on 5G PS Data Off","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"WID new","for":"Approval","abstract":"WID proposal for 5G PS Data Off","secretary_remarks":"Noted","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23220,"status":"noted","reservation_date":"2018-01-15 19:47:32","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180445.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180446","title":"23.501: 3GPP PS Data Off - TS 23.501","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add a new clause to support 3GPP PS Data Off","secretary_remarks":"Not Handled","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23230,"status":"not treated","reservation_date":"2018-01-15 19:47:32","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180446.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180447","title":"23.502: 3GPP PS Data Off - TS 23.501","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Support reporting 3GPP PS Data Off status from UE to SMF via PCO and further report from SMF to PCF if PCF is deployed. Indicate the 3GPP PS Data Off feature support from SMF to UE via PCO.","secretary_remarks":"Not Handled","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23240,"status":"not treated","reservation_date":"2018-01-15 19:47:32","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180447.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180448","title":"23.503: Clarification on PS Data Off status reporting - TS 23.401","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add a new clause to define the behaviour of SMF and PCF for supporting 3GPP PS Data Off feature.","secretary_remarks":"Not Handled","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23250,"status":"not treated","reservation_date":"2018-01-15 19:47:32","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180448.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180449","title":"23.793: UE Requested Multi-access PDU Session Establishment","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"pCR","for":"Approval","abstract":"Solution proposal for UE-requested Multi-access PDU Session establishment.","secretary_remarks":"Not Handled","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20540,"status":"not treated","reservation_date":"2018-01-15 21:20:40","uploaded":"2018-01-16 14:36:58","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180449.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180450","title":"23.793: Update on ATSSS Key Issue #2","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"pCR","for":"Approval","abstract":"Update to ATSSS Key Issue#2 for relationship between ATSSS policies and URSP.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20410,"status":"approved","reservation_date":"2018-01-15 21:21:30","uploaded":"2018-01-16 14:36:58","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180450.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180451","title":"23.502: Update to UCU and Registration procedure","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Deletion of indication that current 5G-GUTI is invalid from the AMF in UCU  2. Configured NSSAI may be included by the AMF in the UCU message","secretary_remarks":"Revised to S2-181200.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12640,"status":"revised","reservation_date":"2018-01-15 21:27:14","uploaded":"2018-01-16 14:36:58","revisionof":"","revisedto":"S2-181200","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180451.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180452","title":"23.501: Correction for the usage of RQI bit","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It replaces the conditions whether RQI is included to conditions whether RQI bit is set.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14450,"status":"endorsed","reservation_date":"2018-01-15 21:28:07","uploaded":"2018-01-16 14:36:58","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180452.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180453","title":"23.724: KI: Efficient frequent small data transmission","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"pCR","for":"Approval","abstract":"Propose key issues on the frequent small data transmission.","secretary_remarks":"Merged into S2-180827","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20790,"status":"merged","reservation_date":"2018-01-15 21:30:38","uploaded":"2018-01-16 14:36:58","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180453.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180454","title":"23.501: 5_16_6_Mission Critical Services - Editorial Changes","source":"FirstNet, AT&T, Motorola Solutions, Airwave","contact":"Ihab Guirguis","contact-id":65302,"tdoctype":"draftCR","for":"Approval","abstract":"This contribution provides editorial updates for clause 5.16.6 as well as clarifying that the scope of this clause extends to include other commercial services that require priority treatment.","secretary_remarks":"Should be a DRAFTCR Revised in parallel session (as DraftCR) to S2-180871.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17300,"status":"revised","reservation_date":"2018-01-15 22:01:01","uploaded":"2018-01-15 22:31:34","revisionof":"","revisedto":"S2-180871","release":"Rel-15","crspec":23.501,"crspecversion":"2.0.1","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_125_Gothenburg\/Docs\/S2-180454.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180455","title":"[DRAFT] LS reply on Mapping of Conversational Services to 5G System","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"Proposes LS reply to SA WG4 for their LS on mapping of conversational services to 5G System in S4-171278 \/ S2-180010.","secretary_remarks":"Response to S2-180010 Revised in parallel session to S2-180865.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16600,"status":"revised","reservation_date":"2018-01-15 22:04:53","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"S2-180865","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180455.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180456","title":"23.501: 5_16_6_Mission Critical Services - Reference Update","source":"FirstNet, AT&T, Motorola Solutions, Airwave","contact":"Ihab Guirguis","contact-id":65302,"tdoctype":"draftCR","for":"Approval","abstract":"This contribution corrects the reference for the MCX Services description.","secretary_remarks":"Should be a DRAFTCR Revised in parallel session (as DraftCR) to S2-180872.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17330,"status":"revised","reservation_date":"2018-01-15 22:05:10","uploaded":"2018-01-15 22:31:34","revisionof":"","revisedto":"S2-180872","release":"Rel-15","crspec":23.501,"crspecversion":"2.0.1","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_125_Gothenburg\/Docs\/S2-180456.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180457","title":"23.503: Support for MCX Services in the PCC of 5G System","source":"FirstNet, AT&T, Motorola Solutions, Airwave","contact":"Ihab Guirguis","contact-id":65302,"tdoctype":"draftCR","for":"Approval","abstract":"This contribution proposes new subclause '6.1.3.xx Mission Critical Services support' to describe the support for MCX Services in the PCC of 5G System.","secretary_remarks":"Should be a DRAFTCR Revised in parallel session to S2-180927.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15890,"status":"revised","reservation_date":"2018-01-15 22:12:47","uploaded":"2018-01-15 22:31:34","revisionof":"","revisedto":"S2-180927","release":"Rel-15","crspec":23.503,"crspecversion":"1.0.0","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_125_Gothenburg\/Docs\/S2-180457.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180458","title":"Emergency services over 5GC via untrusted non-3GPP access","source":"Nokia, Nokia Shanghai Bell","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The case emergency sessions over 5GC via non-3GPP untrusted access is added to existing clauses 4.3.1 and 4.4.  A new annex for this case is added.","secretary_remarks":"Revised in parallel session to S2-180951.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18870,"status":"revised","reservation_date":"2018-01-15 22:16:23","uploaded":"2018-01-16 14:38:08","revisionof":"","revisedto":"S2-180951","release":"Rel-15","crspec":23.167,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":320.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180458.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180459","title":"23.502: Removal of editor's notes in clause 4.12","source":"Nokia, Nokia Shanghai Bell","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Editor's note in 4.12 is removed. Details of PDU Session Release Request and Command are documented and aligned to 3GPP access corresponding procedure.","secretary_remarks":"Revised in parallel session to S2-180944.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18570,"status":"revised","reservation_date":"2018-01-15 22:16:24","uploaded":"2018-01-16 14:38:08","revisionof":"","revisedto":"S2-180944","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180459.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180460","title":"23.502: Alignment of non-3GPP registration to 3GPP registration","source":"Nokia, Nokia Shanghai Bell","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - The N3IWF key is removed from the N2 message in step 9a; - The NAS SMC Response message is carried by the IKE_AUTH Req message 9c; - On reception of the IKE_AUTH Req message, the NAS message is transferred to the AMF; - The AMF replies with a N2 message, which includes the N3IWF key. And in case of failure, AMF sends a N2 Release Command to N3IWF, which can send EAP-Failure at EAP-5G layer.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18370,"status":"postponed","reservation_date":"2018-01-15 22:16:24","uploaded":"2018-01-16 14:38:08","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180460.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180461","title":"23.715: Update of RLOS architectural assumptions","source":"Nokia, Nokia Shanghai Bell, Verizon","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes modifications to RLOS architectural assumptions, based on the recent response from SA WG1 in LS S1-174602","secretary_remarks":"Revised in parallel session to S2-181001.","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22650,"status":"revised","reservation_date":"2018-01-15 22:16:24","uploaded":"2018-01-16 14:38:08","revisionof":"","revisedto":"S2-181001","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180461.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180462","title":"23.715: Update of RLOS key issues","source":"Nokia, Nokia Shanghai Bell, Verizon","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes modifications to RLOS key issues, based on the recent response from SA WG1 in LS S1-174602.","secretary_remarks":"Revised in parallel session to S2-181004.","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22720,"status":"revised","reservation_date":"2018-01-15 22:16:24","uploaded":"2018-01-16 14:38:08","revisionof":"","revisedto":"S2-181004","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180462.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180463","title":"23.715: Solution: EPC procedures for RLOS","source":"Nokia, Nokia Shanghai Bell, Verizon","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"pCR","for":"Approval","abstract":"As the UE may not always be aware that the user is requesting RLOS (based on response LS from SA WG1), this paper proposes a solution for attach and non-IMS restricted local operator services, with network-based RLOS detection and RLOS-APN.","secretary_remarks":"Not Handled","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22790,"status":"not treated","reservation_date":"2018-01-15 22:16:24","uploaded":"2018-01-16 14:38:08","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180463.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180464","title":"23.715: Solution: IMS procedures for RLOS","source":"Nokia, Nokia Shanghai Bell, Verizon","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a solution for IMS restricted local operator services, for both Rel-15 and legacy UEs","secretary_remarks":"Not Handled","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22810,"status":"not treated","reservation_date":"2018-01-15 22:16:24","uploaded":"2018-01-16 14:38:08","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180464.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180465","title":"New SID on Enhanced support of Vertical and URLLC Services","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"SID new","for":"Approval","abstract":"The objective is to study enhancements to 5GS that are required to fulfill the objectives of normative Vertical and URLLLC service requirements, agreed by SA WG1 as part of the 2 study items concluded in SA WG1: FS_CAV and FS_5GLAN.","secretary_remarks":"Revised to S2-181075.","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23280,"status":"revised","reservation_date":"2018-01-15 23:24:43","uploaded":"2018-01-16 14:57:02","revisionof":"","revisedto":"S2-181075","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180465.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180466","title":"23.501: Updates to TS 23.501 Scope","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that 23.503 covers Policy control and charging. Since 23.501 includes some aspects of PCC (e.g. overall arch includes PCF, PCF selection etc), the first reference to policy control is not deleted. In any case, that is just a hint to the contents. However a reference to 23.503 is added to show that it covers PCF architecture (in detail). Also, updated existing statement to hint that this is not a complete set of features.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11220,"status":"approved","reservation_date":"2018-01-15 23:28:15","uploaded":"2018-01-16 14:57:01","revisionof":"","revisedto":"S2-181752","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180466.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180467","title":"23.501: Fixes for Emergency Services and Emergency Services using Fallback","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) It is proposed to remove the EN that was added to confirm RAT based ES support indication. 2) It is proposed to clarify the UE requirement when it moves to 'emergency registered' (= limited services) state and remove the corresponding EN. Editor's note: How the 5GC reacts to existing services via normal registration, and how new services via normal registration operate when an Emergency Registration has occurred is FFS. 3) When AMF initiates redirection request, it needs to provide some hints to the RAN to help determine whether RAT fallback or System fallback will be performed. 'In the N2 procedure, the AMF may indicate the target CN for the RAN node to know whether inter-RAT fallback or inter-system fallback is to be performed.'","secretary_remarks":"Should be a DRAFTCR Revised in parallel session (as DraftCR) to S2-180890.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16890,"status":"revised","reservation_date":"2018-01-15 23:34:56","uploaded":"2018-01-16 14:57:01","revisionof":"","revisedto":"S2-180890","release":"Rel-15","crspec":23.501,"crspecversion":"2.0.1","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_125_Gothenburg\/Docs\/S2-180467.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180468","title":"23.501: EPC to 5GC Migration fixes for Option 7","source":"Nokia, Nokia Shanghai Bell, AT&T","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Propose to reflect the necessary requirement for CN selection in case of Option 7 architecture: UE AS layer should indicate to the RAN whether it is requesting EPS access or 5GS access","secretary_remarks":"Revised in parallel session, merging S2-180491, to S2-180775.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17430,"status":"revised","reservation_date":"2018-01-15 23:41:45","uploaded":"2018-01-16 14:57:01","revisionof":"","revisedto":"S2-180775","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180468.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180469","title":"23.502: UE polices ack from UE","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following solution is proposed:  - - The UE sends back to the AMF a NAS message acknowledging the reception and storage of the UE policies.  - - In addition, to cover those error cases where the UE receives the NAS message from the AMF but has some error in the storing of the UE policies information, the UE may include in the ACK message with additional information about the error. If this optional IE is present in the ACK message, the AMF will send this error to the PCF (stage 3 will decide the message) and this will handle the error, e.g. updating UE context in the PCF accordingly and reattempting the sending of UE policies later on.","secretary_remarks":"Revised in parallel session to S2-180925.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14760,"status":"revised","reservation_date":"2018-01-15 23:43:16","uploaded":"2018-01-16 14:52:43","revisionof":"","revisedto":"S2-180925","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180469.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180470","title":"23.502: Application Trigger procedure updates","source":"Ericsson, Convida Wireless LLC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The usage of Nudm_SDM_Get operation is described including new Subscription Data type: 'Identity translation'. This new Subscription Data type requires GPSI as access key, instead of SUPI. Nnef_Trigger service operation names are updated to reflect better the functionality performed.","secretary_remarks":"Revised, merging S2-180150, to S2-181131.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19400,"status":"revised","reservation_date":"2018-01-15 23:43:16","uploaded":"2018-01-16 14:30:19","revisionof":"","revisedto":"S2-181131","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180470.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180471","title":"23.502: SMF dynamically allocated subscription data","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 'SMF dynamically allocated subscription data' is defined to be accessed using Nudm_SDM service. At AMF registration to UDM, the AMF is required to read newly defined 'SMF dynamically allocated subscription data'.","secretary_remarks":"Merged into S2-181190","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12560,"status":"merged","reservation_date":"2018-01-15 23:43:16","uploaded":"2018-01-16 14:30:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180471.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180472","title":"23.501: UDM discovery clarifications","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove Editor's note Remove example for discovery based on GPSI for PCF.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14120,"status":"approved","reservation_date":"2018-01-15 23:43:16","uploaded":"2018-01-16 14:30:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180472.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180473","title":"23.502: Nudm SDM service Subscription Data types updates","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Data items are added\/removed for multiple Subscription Data types for the Nudm SDM service. Added information:  - UE Usage Type for EPC interworking - LADN indicator per DNN - Priority services indicator (MPS) Removed information: -Homogeneous VoIP support indicator is provided by AMF to UDM since it is required for internal UDM processing, but it is not part of 'Access and Mobility Subscription data' required by AMF. -Default APN is not used by SMF.","secretary_remarks":"Revised to S2-181132.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19460,"status":"revised","reservation_date":"2018-01-15 23:43:16","uploaded":"2018-01-16 14:30:19","revisionof":"","revisedto":"S2-181132","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180473.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180474","title":"23.501: 5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) PDB\/PER - clarify the condition for adding the packet to the PER. Current text is a bit ambiguous as it uses GBR as a boundary condition. It is ambiguous for implementation to determine the exact condition for considering the packets as lost and adding it to the PER. 2) Maximum Data Burst Volume - State the conditions for enforcing it in the UE for UL and UPF for DL. Otherwise, there is a possibility that huge amount of packets are sent \/ received causing the RAN not to be able to meet the necessary latency and relaibility requirement for delay critical 5QIs. 3) 5QI table - remove the 1ms note as it is not necessary to assume 1ms backhaul delay just for certain set of 5QIs, also removing reference to PCEF. 4) QoS characeteristics for Non-standardized 5QI is expected to be provided dynamically over signaling. Thus the minimum allowed ranges need not be specified. It is proposed to simply remove the EN.","secretary_remarks":"Revised to S2-181195.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14460,"status":"revised","reservation_date":"2018-01-15 23:44:35","uploaded":"2018-01-16 14:57:01","revisionof":"","revisedto":"S2-181195","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180474.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180475","title":"UE providing assistance information to PCF for UE Policy decision & delivery","source":"Motorola Mobility, Lenovo","contact":"Dimitrios Karampatsis","contact-id":70692,"tdoctype":"discussion","for":"Approval","abstract":"Addresses the open point from SA WG2#124 on UE Policy provisioning. Namely, UE providing information to assist the PCF to determine whether a UE requires updated UE Policies.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14680,"status":"noted","reservation_date":"2018-01-15 23:53:49","uploaded":"2018-01-16 10:35:00","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_125_Gothenburg\/Docs\/S2-180475.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180476","title":"Discussion paper: UE Wi-Fi MAC Address in WLAN Measurement Information","source":"Comtech Telecommunications Incorporated, AT&T, Cisco, Qualcomm","contact":"Khiem Tran","contact-id":60055,"tdoctype":"discussion","for":"Discussion","abstract":"Abstract of the contribution: This contribution discusses required changes in LPP of including UE WLAN MAC address to support Emergency Services location. It includes a proposed way forward by attaching an included LS from SA WG2 to RAN WG2.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2018-01-16 00:09:13","uploaded":"2018-01-16 00:55:05","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180476.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180477","title":"23.786: New key issue for edge computing","source":"LG Electronics, NTT DOCOMO","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a new key issue on edge computing for study in TR 23.786.","secretary_remarks":"Revised in parallel session to S2-181083.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19720,"status":"revised","reservation_date":"2018-01-16 00:32:41","uploaded":"2018-01-16 09:50:48","revisionof":"","revisedto":"S2-181083","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180477.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180478","title":"23.786: New key issue for URLLC","source":"LG Electronics, NTT DOCOMO","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a new key issue for URLLC into TR 23.786.","secretary_remarks":"Merged into S2-181079 and S2-181080","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19660,"status":"merged","reservation_date":"2018-01-16 00:40:11","uploaded":"2018-01-16 09:50:48","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180478.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180479","title":"23.502: NEF service definitions for AF influence","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add NEF service defintions to support AF influence. This paper relates to S2-180139 and S2-180480","secretary_remarks":"Revised to S2-181136.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19530,"status":"revised","reservation_date":"2018-01-16 01:03:55","uploaded":"2018-01-16 02:31:56","revisionof":"","revisedto":"S2-181136","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180479.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180480","title":"23.501: Update to AF influence on traffic routing","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. This paper proposes to optionally include an application identifier in the PDU Session setup\/modification request to allow AF influence to be applied before application traffic starts. 2. This paper proposes to use AF transaction ID for the AF to correlate AF request and SMF notification.","secretary_remarks":"Revised to S2-181168.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13490,"status":"revised","reservation_date":"2018-01-16 01:03:56","uploaded":"2018-01-16 02:31:56","revisionof":"","revisedto":"S2-181168","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180480.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180481","title":"23.731: Key issue: positioning via user plane","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes new key issue 'positioning via user plane'.","secretary_remarks":"Revised in parallel session to S2-180906.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22000,"status":"revised","reservation_date":"2018-01-16 01:23:09","uploaded":"2018-01-16 11:29:49","revisionof":"","revisedto":"S2-180906","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180481.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180482","title":"23.731: Key issue: support of hybrid positioning","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes new key issue 'support of hybrid positioning'.","secretary_remarks":"Revised in parallel session to S2-180910.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22100,"status":"revised","reservation_date":"2018-01-16 01:23:10","uploaded":"2018-01-16 11:29:49","revisionof":"","revisedto":"S2-180910","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180482.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180483","title":"23.731: Key issue: position service exposure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes new key issue 'position service exposure'.","secretary_remarks":"Revised in parallel session to S2-180912.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22150,"status":"revised","reservation_date":"2018-01-16 01:23:10","uploaded":"2018-01-16 11:29:49","revisionof":"","revisedto":"S2-180912","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180483.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180484","title":"Clarification on PRA reporting in ECM-IDLE state","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the behaviour of MME\/S4-SGSN upon receiving request for notification of change of UE presence in PRA when UE is in CM-IDLE state.","secretary_remarks":"Revised in parallel session to S2-181029.","agenda_item_sort_order":9,"ainumber":"5.2","ainame":"QoS and PCC Maintenance","tdoc_agenda_sort_order":10790,"status":"revised","reservation_date":"2018-01-16 01:49:05","uploaded":"2018-01-16 13:10:38","revisionof":"","revisedto":"S2-181029","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3381.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180484.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180485","title":"Clarification on Dual Connectivity with NR","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Indication of UE support for Dual Connectivity with NR is provided from MME to the PCRF.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11080,"status":"noted","reservation_date":"2018-01-16 01:49:06","uploaded":"2018-01-16 14:55:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"EDCE5"}],"crnumber":3382.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180485.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180486","title":"Clarification on Dual Connectivity with NR","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Indication of UE support for Dual Connectivity with NR is provided from MME to the PCRF.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11090,"status":"noted","reservation_date":"2018-01-16 01:49:07","uploaded":"2018-01-16 14:55:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.203,"crspecversion":"15.1.0","workitem":[{"winame":"EDCE5"}],"crnumber":1115.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180486.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180487","title":"Discussion on Control of the Messages triggering Paging at AMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discusses the mechanism for the AMF to control the messages triggerring the Paging message to RAN","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16120,"status":"noted","reservation_date":"2018-01-16 02:16:38","uploaded":"2018-01-16 12:24:13","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180487.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180488","title":"23.501: CR Control of the Messages triggering Paging at AMF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: AMF and other network functions together control the quantity of messages that require the AMF to page the UE. In addition to SMF control, if additional requests received while waiting for a UE response to the Paging Request message, the AMF may determines to reject it. Proposal 1: AMF and other network functions shall together control the quantity of messages that require the AMF to page the UE. Proposal 2: If the AMF has sent two Paging Messages to RAN node, the AMF shall reject the subsequent messages with a No Response to Previous Paging Indication. Proposal 3: If the AMF has a Paging Messages to RAN node, the AMF shall reject the subsequent messages without a higher priority.","secretary_remarks":"Revised to S2-181141.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16130,"status":"revised","reservation_date":"2018-01-16 02:16:38","uploaded":"2018-01-16 12:24:14","revisionof":"","revisedto":"S2-181141","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180488.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180489","title":"23.502: CR Control of the Messages triggering Paging at AMF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: AMF and other network functions together control the quantity of messages that require the AMF to page the UE. In addition to SMF control, if additional requests received while waiting for a UE response to the Paging Request message, the AMF may determines to reject it. Proposal 1: AMF and other network functions shall together control the quantity of messages that require the AMF to page the UE. Proposal 2: If the AMF has sent two Paging Messages to RAN node, the AMF shall reject the subsequent messages with a No Response to Previous Paging Indication. Proposal 3: If the AMF has a Paging Messages to RAN node, the AMF shall reject the subsequent messages without a higher priority.","secretary_remarks":"Revised to S2-181142.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16150,"status":"revised","reservation_date":"2018-01-16 02:16:38","uploaded":"2018-01-16 12:26:35","revisionof":"","revisedto":"S2-181142","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180489.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180490","title":"23.501: CR Relation between the SSC mode the PDU type","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In this release, SSC mode 3 only apply to IP PDU type.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13710,"status":"approved","reservation_date":"2018-01-16 02:16:38","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"S2-181554","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180490.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180491","title":"23.501: CR Network disable UE 5GC selection in case no roaming agreement","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Change the 5GC NAS capability indication to 5GC selected indication.  2. It should be possible for network to disable UE 5GC selection. When the 5GC selection is disabled, UE should not indicate that indicator at the AS layer. 3. Remove the unnecssary EN.  4. Clarify how the UE is steered from 5GC to EPC network.","secretary_remarks":"Merged into S2-180775","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17460,"status":"merged","reservation_date":"2018-01-16 02:16:38","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180491.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180492","title":"23.794: Key Issues for FS_eIMS5G Localized UPF","source":"T-Mobile USA INC","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Proposes two key issues related to localized UPF and IMS","secretary_remarks":"Revised in parallel session to S2-180935.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22280,"status":"revised","reservation_date":"2018-01-16 02:33:56","uploaded":"2018-01-16 03:05:04","revisionof":"","revisedto":"S2-180935","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/s2-180492.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180493","title":"23.794: Baseline References and Definitions for eIMS5g TR","source":"T-Mobile USA INC","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Provides some initial text for Reference and Definition clauses of eIMS5G TR","secretary_remarks":"Revised in parallel session to S2-180933.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22210,"status":"revised","reservation_date":"2018-01-16 02:36:41","uploaded":"2018-01-16 03:05:04","revisionof":"","revisedto":"S2-180933","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/s2-180493.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180494","title":"23.794: Key Issue for FS_eIMS5G Service Based Interfaces","source":"T-Mobile USA INC","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Proposes a key issue related to IMS and 5G Service Based Interfaces","secretary_remarks":"This was withdrawn.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22460,"status":"withdrawn","reservation_date":"2018-01-16 02:39:03","uploaded":"2018-01-16 03:05:04","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/s2-180494.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180495","title":"23.794: Scope and Architectural Assumptions of eIMS5G Study","source":"T-Mobile USA INC","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Proposes text for the scope and architectural assumptions clauses of the eIMS5G report.","secretary_remarks":"Revised in parallel session to S2-180934.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22230,"status":"revised","reservation_date":"2018-01-16 02:42:52","uploaded":"2018-01-16 03:05:04","revisionof":"","revisedto":"S2-180934","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/s2-180495.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180496","title":"23.794: New Key Issues: Support of Network Slicing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes some new key issues for eIMS5G SI, in order to investigate the necessary IMS enhancements to better support 5GC network slicing.","secretary_remarks":"Merged into S2-180936","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22310,"status":"merged","reservation_date":"2018-01-16 02:45:44","uploaded":"2018-01-16 13:10:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180496.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180497","title":"23.794: New Key Issues: Support of Service Based Interfaces","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes new key issues for eIMS5G SI, in order to investigate the necessary IMS enhancements to support SBI provided by 5GC.","secretary_remarks":"Revised in parallel session, merging S2-180713, to S2-180938.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22470,"status":"revised","reservation_date":"2018-01-16 02:45:44","uploaded":"2018-01-16 13:10:39","revisionof":"","revisedto":"S2-180938","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180497.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180498","title":"23.793: New KI and Alternative architecture framework for ATSSS","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue and an alternative architecture framework for ATSSS.","secretary_remarks":"Revised in parallel session to S2-180986.","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20490,"status":"revised","reservation_date":"2018-01-16 02:45:44","uploaded":"2018-01-16 13:10:39","revisionof":"","revisedto":"S2-180986","release":"Rel-16","crspec":23.793,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180498.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180499","title":"23.794: Key Issues for FS_eIMS5G slicing","source":"T-Mobile USA INC","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Proposes a key issue related to network slicing and IMS","secretary_remarks":"Revised in parallel session, merging S2-180496, S2-180562, S2-180714 and S2-180748, to S2-180936.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22320,"status":"revised","reservation_date":"2018-01-16 02:46:09","uploaded":"2018-01-16 03:05:04","revisionof":"","revisedto":"S2-180936","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/s2-180499.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180500","title":"23.682: Correction to cancelled monitoring Event in the network parameter configuration via SCEF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: Correct the cancelled monitoring event procedure in the network parameter configuration via SCEF. Decouple the procedures of Monitoring related procedure and network parameter configuration related procedure.","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24080,"status":"withdrawn","reservation_date":"2018-01-16 02:47:16","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180501","title":"LADN handling in PDU session establishment procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Approval","abstract":"In this contribution,how to handle LADN session in PDU establishment procedure is discussed.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13340,"status":"not treated","reservation_date":"2018-01-16 02:47:16","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180501.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180502","title":"23.501: Clarification on LADN PDU Session establishment handling","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Add explicit description that DNN include information on whether the DNN is LADN. 2) AMF can reject the PDU Session establishment request.","secretary_remarks":"Revised to S2-181115.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13160,"status":"revised","reservation_date":"2018-01-16 02:47:16","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"S2-181115","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180502.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180503","title":"TR Skeleton for FS_eIMS5G","source":"T-Mobile USA Inc.","contact":"Christopher Joul","contact-id":31136,"tdoctype":"draft TR","for":"Approval","abstract":"WITHDRAWN: Proposes skeleton to TR 23.794 for FS_eIMS5G","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24110,"status":"withdrawn","reservation_date":"2018-01-16 02:48:25","uploaded":"2018-01-16 03:05:06","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/s2-180503.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180504","title":"23.726: Key Issue for allocating IP addresses for complex topologies","source":"T-Mobile USA INC","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Describes a new key issue for regarding the allocation of IP addresses for complex SMF and UPF topologies","secretary_remarks":"Revised in parallel session, merging S2-180061, to S2-180956.","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21780,"status":"revised","reservation_date":"2018-01-16 02:50:55","uploaded":"2018-01-16 03:05:07","revisionof":"","revisedto":"S2-180956","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/s2-180504.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180505","title":"Correction to cancelled monitoring Event in the network parameter configuration via SCEF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Decouple the procedures of Monitoring related procedure and network parameter configuration related procedure. If the HSS cancelled a monitoring event in step 4 and the cancelled monitoring event is subscribed by the SCEF which is the same as the one sending the Set Suggested Network Configuration Request, Cancelled SCEF Reference ID is included in the response and set to the SCEF Reference ID of the cancelled Monitoring Event. If the HSS cancelled a monitoring event in step 4 and the cancelled monitoring event is subscribed by the SCEF which is different from the SCEF sending the Set Suggested Network Configuration Request, HSS sends the Monitoring Indication message towards the SCEF which subscribed the cancelled monitoring event and includes SCEF Reference ID of a cancelled Monitoring Event. If the SCEF received Cancelled SCEF Reference ID in step 10\/10a, the steps 2-5 of Network-initiated Explicit Monitoring Event Deletion procdure defined in subclause 5.6.9 are","secretary_remarks":"Revised in parallel session to S2-180917.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11030,"status":"revised","reservation_date":"2018-01-16 02:51:54","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"S2-180917","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":378.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180505.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180506","title":"Discussion on Dealing with reduction in bearers at mobility","source":"T-Mobile USA INC","contact":"Christopher Joul","contact-id":31136,"tdoctype":"discussion","for":"Discussion","abstract":"Discusses when moving between area supporting 15 bearers to an area supporting fewer.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15","ainame":"WID on increasing the maximum number of LTE bearers (INOBEAR)","tdoc_agenda_sort_order":22570,"status":"noted","reservation_date":"2018-01-16 02:53:05","uploaded":"2018-01-16 03:05:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/s2-180506.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180507","title":"23.502: Update 5GS and EPS handover procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1.Some descriptions corrections in 4.11.1.2.1 2. Align parameters N2 SM Information in step 7 and step 9 in 4.11.1.2.2.2 to N2 SM Information (PDU Session ID, QFI(s), QoS Profile(s), EPS Bearer Setup List ,V-CN Tunnel Info).","secretary_remarks":"Not Handled","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17800,"status":"not treated","reservation_date":"2018-01-16 02:57:27","uploaded":"2018-01-16 11:42:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180507.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180508","title":"23.502: Correction on Secondary authorization\/authentication procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution clarifies duiring PDU session establishment, how secondary authorization\/authentication is performed, especially on authorization\/authentication without using UPF. There are also some corrections on Figure 4.3.2.3-1 and some other descriptions.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13630,"status":"not treated","reservation_date":"2018-01-16 02:57:27","uploaded":"2018-01-16 11:42:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180508.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180509","title":"23.794: Proposed Skeleton for TR 23.794","source":"T-Mobile USA Inc.","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Proposed document skeleton TR 23.794.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22200,"status":"approved","reservation_date":"2018-01-16 03:09:45","uploaded":"2018-01-16 03:14:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/s2-180509.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180510","title":"23.786: Key issues for support of eV2X QoS enhancements","source":"Qualcomm Incorporated, Intel","contact":"Hong Cheng","contact-id":25668,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue for supporting the QoS for eV2X requirements.","secretary_remarks":"Revised in parallel session, merging part of S2-180478, to S2-181080.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19630,"status":"revised","reservation_date":"2018-01-16 03:32:54","uploaded":"2018-01-16 04:01:23","revisionof":"","revisedto":"S2-181080","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180510.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180511","title":"23.786: Key issues for support of unicast\/multicat for Extended Sensors","source":"Qualcomm Incorporated,","contact":"Hong Cheng","contact-id":25668,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue for supporting the Extended Sensor requirement from stage 1.","secretary_remarks":"Revised in parallel session to S2-181084.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19750,"status":"revised","reservation_date":"2018-01-16 03:36:47","uploaded":"2018-01-16 04:01:37","revisionof":"","revisedto":"S2-181084","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180511.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180512","title":"23.731: Key Issue on Scalability for 5GC Location Enhancement","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"pCR","for":"Approval","abstract":"This contribution provides a P-CR to add a key issue to TR 23.731 on scalability for 5GC location enhancement.","secretary_remarks":"Revised in parallel session to S2-180911.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22130,"status":"revised","reservation_date":"2018-01-16 03:44:12","uploaded":"2018-01-16 04:01:52","revisionof":"","revisedto":"S2-180911","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180512.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180513","title":"23.731: Key Issue on Latency for 5GC Location Enhancement","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"pCR","for":"Approval","abstract":"This contribution provides a P-CR to add a key issue to TR 23.731 on latency for 5GC location enhancement.","secretary_remarks":"Revised in parallel session, merging S2-180291, to S2-180907.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22050,"status":"revised","reservation_date":"2018-01-16 03:47:58","uploaded":"2018-01-16 04:02:06","revisionof":"","revisedto":"S2-180907","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180513.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180514","title":"23.731: Key Issue on IoT UEs for 5GC Location Enhancement","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"pCR","for":"Approval","abstract":"This contribution provides a P-CR to add a key issue to TR 23.731 on IoT UEs for 5GC location enhancement.","secretary_remarks":"Revised in parallel session to S2-180913.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22170,"status":"revised","reservation_date":"2018-01-16 03:52:29","uploaded":"2018-01-16 04:02:20","revisionof":"","revisedto":"S2-180913","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180514.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180515","title":"23.501: Fixes for CP protocol stack","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Clarify that LCS is a protocol that will be supported as part of NAS signalling","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11230,"status":"approved","reservation_date":"2018-01-16 04:12:44","uploaded":"2018-01-16 14:57:01","revisionof":"","revisedto":"S2-181753","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180515.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180516","title":"23.502: Fixes for UDM\/UDR services","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Fix the UDM service operation 2) Fix the UDR service name 3) Update subscription data table for Registration and MM subscription data type as PEI (i.e. IMEI), Homogenous support of IMS voice over PS Sessions are paramers sent by AMF to UDM and it need not be sent in the other direction.","secretary_remarks":"Revised to S2-181133.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19440,"status":"revised","reservation_date":"2018-01-16 04:16:04","uploaded":"2018-01-16 14:57:01","revisionof":"","revisedto":"S2-181133","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180516.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180517","title":"5G System Reference point #s","source":"Nokia, Nokia Shanghai Bell (Rapporteur)","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion paper proposes how to handle and allocate Reference point #s. It is proposed to endorse the allocation of an independent block of reference points for TS 23.501 and TS 23.503: 1) Reference point #s 31 - 40 for new reference point # proposals to TS 23.501 2) Reference point #s 41 - 50 for new reference point # proposals to TS 23.503 It is proposed to endorse the allocation of an independent block of reference points for TS 23.501 and TS 23.503:","secretary_remarks":"This proposal was endorsed","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11240,"status":"endorsed","reservation_date":"2018-01-16 04:25:57","uploaded":"2018-01-16 14:57:01","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_125_Gothenburg\/Docs\/S2-180517.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180518","title":"Discussion on Paging for non-3GPP access","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution is proposed to discuss about paging for a PDU Session associated with non-3GPP access. Currently, AMF behaviour is not clear when it receives multiple messages associated with 3GPP and non-3GPP PDU Sessions while UE is in CM-IDLE in both accesses. Two candidate solutions are suggested and it is proposed to agree first solution.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18610,"status":"noted","reservation_date":"2018-01-16 04:37:54","uploaded":"2018-01-16 10:45:50","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180518.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180519","title":"23.502: Clarification on paging when it is related with both 3GPP and non-3GPP PDU Session","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarify that if the AMF receives multiple request associated with 3GPP and non-3GPP access at the same time, the AMF sends a Paging message with associated access 'non-3GPP' to RAN node(s) via 3GPP access.  2. Clarify that the AMF behaviour when it receives another message for 3GPP (or non-3GPP) PDU Session while waiting for a UE response for the non-3GPP (or 3GPP) PDU Session.  3. Clarify that the UE initiates UE Triggered Service Request procedure when it receives paging request for a PDU Session associated with non-3GPP access even if there is no PDU Session that can be re-activated over the 3GPP access.","secretary_remarks":"Revised in parallel session to S2-180945.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18620,"status":"revised","reservation_date":"2018-01-16 04:42:33","uploaded":"2018-01-16 10:45:50","revisionof":"","revisedto":"S2-180945","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180519.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180520","title":"23.502: Clarification on handover applicability between 3GPP and non-3GPP accesses","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify how the AMF decides whether a PDU Session can be handed over to the other access when a PDU Session is established as a Home Routed mode.","secretary_remarks":"Revised in parallel session to S2-180947.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18670,"status":"revised","reservation_date":"2018-01-16 04:46:31","uploaded":"2018-01-16 10:45:50","revisionof":"","revisedto":"S2-180947","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180520.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180521","title":"23.502: Clarification on RAT type indication during handover procedure","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the RAN provides N2 parameters (e.g. PLMN ID, Location Information, Cell Identity and the RAT type) to the AMF and the AMF notifies such information to the SMF during handover procedure.","secretary_remarks":"Revised to S2-181143.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16190,"status":"revised","reservation_date":"2018-01-16 04:51:19","uploaded":"2018-01-16 10:45:50","revisionof":"","revisedto":"S2-181143","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180521.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180522","title":"23.501: Removing Editor's Note in clause 6.3.8 (UDM discovery function)","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Removing Editor's Note on whether SUCI needs to be considered during the UDM discovery depends on the conclusion of SA WG3 work.","secretary_remarks":"Covered by S2-180472. Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14130,"status":"noted","reservation_date":"2018-01-16 04:54:13","uploaded":"2018-01-16 10:45:51","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180522.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180523","title":"5G System Temporary Identifier(s)","source":"Nokia, Nokia Shanghai Bell (Rapporteur)","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion paper is about analyzing the size of 5G System Temporary Identifier(s), considering also Option 5\/7 architecture, EPS Interworking.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12330,"status":"noted","reservation_date":"2018-01-16 04:57:56","uploaded":"2018-01-16 14:57:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180523.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180524","title":"Clarification of the Connection Establishment Indication message in CP optimization","source":"NTT DOCOMO INC.","contact":"Kenichiro Aoyagi","contact-id":73277,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the Connection Establishment Indication message shall be used only for Control Plane CIoT EPS optimization.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10410,"status":"noted","reservation_date":"2018-01-16 04:58:21","uploaded":"2018-01-16 06:16:19","revisionof":"","revisedto":"","release":"Rel-13","crspec":23.401,"crspecversion":"13.13.0","workitem":[{"winame":"CIoT_Ext"}],"crnumber":3383.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180524.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180525","title":"23.501: Clarification on mobility event subscription transfer","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the new AMF notiifes current status only when the new AMF does not know the last reported status.","secretary_remarks":"Revised to S2-181165.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13410,"status":"revised","reservation_date":"2018-01-16 04:59:31","uploaded":"2018-01-16 10:45:51","revisionof":"","revisedto":"S2-181165","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180525.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180526","title":"Clarification of the Connection Establishment Indication message in CP optimization","source":"NTT DOCOMO INC.","contact":"Kenichiro Aoyagi","contact-id":73277,"tdoctype":"CR","for":"Approval","abstract":"Rel-14 mirror CR: Summary of change: Clarify that the Connection Establishment Indication message shall be used only for Control Plane CIoT EPS optimization.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10420,"status":"noted","reservation_date":"2018-01-16 05:01:46","uploaded":"2018-01-16 06:16:19","revisionof":"","revisedto":"","release":"Rel-14","crspec":23.401,"crspecversion":"14.6.0","workitem":[{"winame":"CIoT_Ext"}],"crnumber":3384.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180526.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180527","title":"Clarification of the Connection Establishment Indication message in CP optimization","source":"NTT DOCOMO INC.","contact":"Kenichiro Aoyagi","contact-id":73277,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: Clarify that the Connection Establishment Indication message shall be used only for Control Plane CIoT EPS optimization.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10430,"status":"noted","reservation_date":"2018-01-16 05:03:57","uploaded":"2018-01-16 06:16:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"CIoT_Ext"}],"crnumber":3385.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180527.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180528","title":"23.793: ATSSS Solution - Capability negotiation","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes solution for ATSSS capability negotiation procedure.","secretary_remarks":"Not Handled","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20570,"status":"not treated","reservation_date":"2018-01-16 05:05:38","uploaded":"2018-01-16 10:45:51","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180528.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180529","title":"23.501: Clarification on modification of the set of network slices for a UE","source":"LG Electronics","contact":"Jinsook Ryu","contact-id":39022,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) clarify Generic UE Configuration update \u00e0 UE Configuration update 2) the explanation for immediate & delayed release is removed 3) clarify the AMF shall release any association with serving SMFs & AMF","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12150,"status":"not treated","reservation_date":"2018-01-16 05:05:51","uploaded":"2018-01-16 11:50:49","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180529.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180530","title":"23.793: ATSSS Solution - Differentiation of 3GPP RATs in ATSSS Rule","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes structure of ATSSS rule to solve Key Issue 6: Differentiation of 3GPP RATs in ATSSS rule.","secretary_remarks":"Not Handled","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20580,"status":"not treated","reservation_date":"2018-01-16 05:08:34","uploaded":"2018-01-16 10:45:51","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180530.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180531","title":"23.724: Solution proposal for 5G CIoT 'Adjustable periodic Registration Update'","source":"LG Electronics","contact":"Jinsook Ryu","contact-id":39022,"tdoctype":"pCR","for":"Approval","abstract":"This paper propose solution 'Adjustable periodic Registration Update' for further UE power saving.","secretary_remarks":"Not Handled","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21200,"status":"not treated","reservation_date":"2018-01-16 05:12:58","uploaded":"2018-01-16 14:14:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180531.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180532","title":"23.502: Fixes for Emergency Services using Fallback procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Ensure that the AS procedure performed by the AN to redirect the UE is secure","secretary_remarks":"Revised in parallel session to S2-180891.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16910,"status":"revised","reservation_date":"2018-01-16 05:15:10","uploaded":"2018-01-16 14:57:01","revisionof":"","revisedto":"S2-180891","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180532.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180533","title":"Discussion related to LS from 5GAA on LS on V1 and V2 reference points (S2-180021)","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses requests from 5GAA on PC5 parameters from V2X Application Server (S2-180021).","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10720,"status":"noted","reservation_date":"2018-01-16 05:18:24","uploaded":"2018-01-16 09:53:42","revisionof":"","revisedto":"","release":"Rel-14","crspec":23.285,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180533.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180534","title":"Clarification on PC5 parameters from V2X Application Server","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Currently, V2X USD(s) for receiving MBMS based V2X traffic may be provisioned to the UE from the V2X Application Server via V1 reference point. In addition, V2X Control Function may obtain V2X USD(s) for the UE to receive MBMS based V2X traffic through the V2 reference point from the V2X Application Server.  Therefore, it is clarified that  1) The parameters for V2X communications over PC5 reference point may be also provisioned to the UE from the V2X Application Server via V1. 2) The parameters for V2X communications over PC5 reference point may be also provided to the V2X Control Function from from the V2X Application Server via V2. 3) If the UE receives a set of data for V2X communications over PC5 reference point from V2X Application Server then the UE uses the data set provided by V2X Application Server for V2X communications over PC5 reference point.","secretary_remarks":"Revised in parallel session to S2-181087.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10730,"status":"revised","reservation_date":"2018-01-16 05:22:37","uploaded":"2018-01-16 09:53:42","revisionof":"","revisedto":"S2-181087","release":"Rel-14","crspec":23.285,"crspecversion":"14.5.0","workitem":[{"winame":"V2XARC"}],"crnumber":39.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180534.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180535","title":"23.501: Adding CN sharing to network sharing","source":"NICT","contact":"Stanislav Filin","contact-id":41055,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clause 5.18: Remove limitation that only 5G MOCN is defined and add CN sharing.","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":11380,"status":"noted","reservation_date":"2018-01-16 05:24:07","uploaded":"2018-01-16 05:27:14","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180535.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180536","title":"Emergency Support\/ Emergency Support using FB and UE behavior","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution clarify emergency Support per TA per RAT and Emergency Support using fallback","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16930,"status":"noted","reservation_date":"2018-01-16 05:27:34","uploaded":"2018-01-16 10:23:45","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_125_Gothenburg\/Docs\/S2-180536.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180537","title":"23.501: Emergency Support Indicator & indication of Emergency Support using fallback","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Separate the Emergency Support Indicatior and the info of supporting type. - The Emergency Support Indicatior is purely to indicate whether the UE can setup emergency PDU session - The info of supporting type is per TA per RAT is to give the informantion to avoid cheating. Correct the description of Emergency Support Indicator and indication of supporting emergency using fallback to make the two decoupled.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16940,"status":"noted","reservation_date":"2018-01-16 05:27:34","uploaded":"2018-01-16 10:23:45","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180537.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180538","title":"DRAFT Reply LS on session management congestion control","source":"Qualcomm Europe Inc.(France)","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-180026 Revised, merging S2-180238, to S2-181188.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12390,"status":"revised","reservation_date":"2018-01-16 05:33:42","uploaded":"2018-01-16 11:31:38","revisionof":"","revisedto":"S2-181188","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180538.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180539","title":"23.502: PDU session ID in PDU session management procedure","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. PDU session ID is included in N1 SM NAS message in UE requested PDU session establishement\/modification\/release procedure. 2. PDU session ID is removed from Nsmf_PDUSession_CreateSMContext service operation. 3. cleanup the PDU session ID transmission for SSC mode 3 PDU session.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13660,"status":"endorsed","reservation_date":"2018-01-16 05:46:11","uploaded":"2018-01-16 11:31:38","revisionof":"","revisedto":"S2-182093","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180539.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180540","title":"23.501: Clarification on including an additional GUTI in the Registration request for connected-mode mobility from EPC to 5GC in single-registration mode","source":"LG Electronics, Nokia","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is clarified that including the native 5G-GUTI as an additional GUTI in the Registration request is also applied for connected-mode mobility from EPC to 5GC in single-registration mode.","secretary_remarks":"Merged into S2-180777","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17590,"status":"merged","reservation_date":"2018-01-16 05:46:25","uploaded":"2018-01-16 10:25:27","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180540.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180541","title":"23.502: LADN PDU session deactivation in N2 HO procedure","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. T-AMF does not request the SM context during HO preparation if the target cell is out of the LADN service area. 2. T-AMF includes the LADN PDU session in the non-accepted PDU session list.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13400,"status":"noted","reservation_date":"2018-01-16 05:49:18","uploaded":"2018-01-16 11:31:38","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180541.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180542","title":"23.501: Network sharing for supporting RRC redirection procedure","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Network selection for supporting RRC connection release with redirect to a shared network is specified in clause 5.18.4","secretary_remarks":"Revised to S2-181101.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11390,"status":"revised","reservation_date":"2018-01-16 05:52:16","uploaded":"2018-01-16 11:31:38","revisionof":"","revisedto":"S2-181101","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180542.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180543","title":"23.502: Clarification on 5G-GUTI in EPS to 5GS Mobility Registration Procedure using N26","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) The following clarification is made regarding in step 2 when the UE includes the native 5G-GUTI and the GUAMI part of the native 5G-GUTI in the Registration request and RRC, respectively: When the native 5G-GUTI is assigned during a Registration procedure performed over a non-3GPP access, the UE includes the native 5G-GUTI as an additional GUTI in the Registration Request and for idle mode mobility the GUAMI part of the native 5G-GUTI in RRC only if the 3GPP access that the UE registers is in the same PLMN for the non-3GPP access that the UE is registered.  2) Re-wording is made for clarity in steps 17-18 regarding when the UE uses the updated 5G-GUTI in the Registration Accept:","secretary_remarks":"Revised in parallel session to S2-180950.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18810,"status":"revised","reservation_date":"2018-01-16 05:55:47","uploaded":"2018-01-16 10:25:27","revisionof":"","revisedto":"S2-180950","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180543.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180544","title":"23.502: Adding missing text about UE policies related to Service Request including the List Of Allowed PDU Sessions","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding 'if allowed by UE policies' to the description related to the UE Triggered Service Request procedure in response to paging indicating non-3GPP access in step 6 of clause 4.2.3.3","secretary_remarks":"Revised in parallel session to S2-180948.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18690,"status":"revised","reservation_date":"2018-01-16 06:01:01","uploaded":"2018-01-16 10:25:27","revisionof":"","revisedto":"S2-180948","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180544.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180545","title":"23.501: SMF behaviour when UE is out of LADN service area","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the description on SMF notification to the UPF and the SMF rejection of user plane establishment to make TS 23.501 aligned with TS 23.502.","secretary_remarks":"Merged into S2-181111.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13260,"status":"merged","reservation_date":"2018-01-16 06:03:58","uploaded":"2018-01-16 08:13:45","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180545.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180546","title":"23.502: SMF behaviour based on LADN notification","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the SMF shall perform as defined in the TS 23.501 section 5.6.5 when it is notified about UE presence in the LADN service area during the Registration, UE Triggered Service Request, AN Release and Handover procedures. Clarify that Downlink Data Notification is disabled by the SMF when UE is out of LADN service area during the Service Request procedures.","secretary_remarks":"Handover part endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13390,"status":"endorsed","reservation_date":"2018-01-16 06:03:58","uploaded":"2018-01-16 08:13:45","revisionof":"","revisedto":"S2-181493","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180546.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180547","title":"23.502: Clarification on Internal Event Exposure","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarification on system behaviour in case of mobility event notification happens, and which procedure may trigger the mobility event notification.","secretary_remarks":"Revised to S2-181116.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13300,"status":"revised","reservation_date":"2018-01-16 06:03:58","uploaded":"2018-01-16 08:13:45","revisionof":"","revisedto":"S2-181116","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180547.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180548","title":"23.501: Paging Policy Differentiation correction","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Several changes are made for the Paging Policy Differentiation: 1. The indication of the corresponding QoS Flow is removed from the SMF buffering downlink data packet case. 2. PPI is removed from the paging message. 3. Clarify that NG-RAN determines the PPI based on the DSCP in TOS (IPv4) \/ TC (IPv6) value from the IP header of the received downlink data packet from the UPF for the UE in RRC Inactive state.","secretary_remarks":"Revised to S2-181144.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16210,"status":"revised","reservation_date":"2018-01-16 06:03:58","uploaded":"2018-01-16 08:13:45","revisionof":"","revisedto":"S2-181144","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180548.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180549","title":"23.502: Paging Policy Differentiation correction","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Two changes are made for the Paging Policy Differentiation: 1. The indication of the corresponding QoS Flow is removed from the SMF buffering downlink data packet case. 2. PPI is removed from the N2 SM Information.","secretary_remarks":"Revised to S2-181145.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16240,"status":"revised","reservation_date":"2018-01-16 06:03:58","uploaded":"2018-01-16 08:13:45","revisionof":"","revisedto":"S2-181145","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180549.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180550","title":"23.786: PC5 based eV2X architecture reference model","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes to document the PC5 based eV2X architecture reference model into TR 23.786.","secretary_remarks":"Merged into S2-181086","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19830,"status":"merged","reservation_date":"2018-01-16 06:03:58","uploaded":"2018-01-16 08:13:45","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180550.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180551","title":"23.726: Key Issue on I-SMF selection","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes the key issue on I-SMF selection.","secretary_remarks":"Merged into S2-180954","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21800,"status":"merged","reservation_date":"2018-01-16 06:03:58","uploaded":"2018-01-16 08:13:45","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180551.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180552","title":"23.502: Clarification on UP activation for non-3GPP PDU Session related to DL data","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Regarding the case explained in Reason for change, description is added to step 6 of clause 4.2.3.3 so that UP activation is performed for the PDU Session related to downlink data but not included in the received Service Request via non-3GPP access.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18710,"status":"noted","reservation_date":"2018-01-16 06:04:02","uploaded":"2018-01-16 10:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180552.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180553","title":"23.501 Network-based EPS fallback without N26","source":"ZTE, Huwei","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding a new bulletin\/condition that If the NG-RAN is able to trigger RRC release with redirection to EPS at QoS Flow establishment for voice.","secretary_remarks":"Merged into S2-180884","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16730,"status":"merged","reservation_date":"2018-01-16 06:18:47","uploaded":"2018-01-16 13:44:40","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180553.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180554","title":"23.502 RRC release with redirection for voice","source":"ZTE, Huawei","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding description taht the NG-RAN is able to trigger RRC release with redirection to EPS at QoS Flow establishment for voice.","secretary_remarks":"Merged into S2-180884","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16740,"status":"merged","reservation_date":"2018-01-16 06:18:47","uploaded":"2018-01-16 13:44:40","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180554.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180555","title":"23.502 Clarification on the Emergency HO indication for EPS fallback","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding an Note the NG-RAN decide whether to continue EPS Fallback procedures with PS HO or to initiate redirection. NG-RAN may forward the Emergency indication to the target eNB in the Source to Target Transparent Container.","secretary_remarks":"Revised in parallel session to S2-180892.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16950,"status":"revised","reservation_date":"2018-01-16 06:18:47","uploaded":"2018-01-16 13:44:40","revisionof":"","revisedto":"S2-180892","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180555.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180556","title":"23.502 clarification on the SM EPS bearer Contexts from the V-SMF","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Removing the notes 'In roaming scenario, the UE's SM EPS Contexts are obtained from the V-SMF.' Adding the v-SMF caches the UE's SM EPS Contexts.","secretary_remarks":"Not Handled","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18060,"status":"not treated","reservation_date":"2018-01-16 06:18:47","uploaded":"2018-01-16 13:44:40","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180556.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180557","title":"23.502: Clarification and alignment on the intra-5G handover and inter-system handover.","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding handover can be triggered due to IMS emergency service, AMF forwarding the rejection from NG-RAN to SMF. The reference is modified to 23.401","secretary_remarks":"Not Handled","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18070,"status":"not treated","reservation_date":"2018-01-16 06:18:47","uploaded":"2018-01-16 13:44:40","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180557.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180558","title":"23.501: Clean up on the interworking without 26 indication","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clean up, replace dual registration mode indication with interworking without N26 indication","secretary_remarks":"Revised in parallel session, merging S2-180704 and S2-180399, to S2-180791.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18300,"status":"revised","reservation_date":"2018-01-16 06:18:47","uploaded":"2018-01-16 13:44:40","revisionof":"","revisedto":"S2-180791","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180558.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180559","title":"23.502: Keeping EBI transfer alignment","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding allocated EBI information to UE context in the Namf_Communication_UEContextTransfer service operation. Update the Nsmf_PDUSession_Update SM Context service operation description","secretary_remarks":"Revised in parallel session to S2-180780.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17680,"status":"revised","reservation_date":"2018-01-16 06:18:47","uploaded":"2018-01-16 13:44:40","revisionof":"","revisedto":"S2-180780","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180559.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180560","title":"23.401: Transfer PDU session ID in the EPS","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: UE provides PDU session ID in the Attach and UE requested PDN connectivity procedure","secretary_remarks":"Revised in S2-180615. WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23900,"status":"withdrawn","reservation_date":"2018-01-16 06:18:47","uploaded":null,"revisionof":"","revisedto":"S2-180615","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180561","title":"23.502: Clarification on the EPS to 5GS Mobility without N26","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add condition that the UE recieves ' the interworking without N26' indication. Add S-NSSAI received from PGW-C\/SMF in PDU session establishment request message","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23890,"status":"withdrawn","reservation_date":"2018-01-16 06:18:47","uploaded":"2018-01-16 13:44:40","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180561.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180562","title":"23.794: New key issue on the IMS and 5G slicing","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"pCR","for":"Approval","abstract":"This paper discusses relation between IMS and 5G slicing and proposes a key issue on this.","secretary_remarks":"Merged into S2-180936","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22350,"status":"merged","reservation_date":"2018-01-16 06:18:47","uploaded":"2018-01-16 13:44:40","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180562.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180563","title":"Handling of Policy synchronization between UE and PCF using policy ID","source":"Qualcomm Inc","contact":"Miguel Griot","contact-id":57486,"tdoctype":"discussion","for":"Approval","abstract":"This paper proposes a way forward for policy sync between UE and PCF using policy ID.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14710,"status":"noted","reservation_date":"2018-01-16 06:19:50","uploaded":"2018-01-16 06:35:00","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_125_Gothenburg\/Docs\/S2-180563.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180564","title":"23.503: Policy ID definition and handling proposal to split UE policies in sections","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduce Policy ID = Policy Section ID + Sectoin Version ID Describe the handling of policy sections and partial modification of policies in the PCF and UE.","secretary_remarks":"Merged into S2-180924.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14720,"status":"merged","reservation_date":"2018-01-16 06:24:06","uploaded":"2018-01-16 06:35:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180564.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180565","title":"Paging failure for CE capable UEs after 2G\/3G - > 4G idle-mode mobility","source":"Intel, NTT DOCOMO","contact":"Puneet Jain","contact-id":36283,"tdoctype":"discussion","for":"Agreement","abstract":"This paper proposes a solution to solve the issue of paging failure CE-capable UEs on idle-mode mobility from 2G\/3G to 4G.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2018-01-16 06:24:22","uploaded":"2018-01-16 09:27:00","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180565.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180566","title":"23.502: Including uplink aspects of UE policy signalling between UE and PCF","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduce UE uplink policy signalling requesting UE policy synchrnizatoin from UE transparently transported over NAS, and from AMF to PCF.","secretary_remarks":"Merged into S2-180965.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14730,"status":"merged","reservation_date":"2018-01-16 06:27:30","uploaded":"2018-01-16 06:35:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180566.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180567","title":"23.716: Update for Key Issue 5.7-Policy","source":"Intel","contact":"Ellen C. Liao","contact-id":54895,"tdoctype":"pCR","for":"Approval","abstract":"This PCR proposes to modify key issue of 5.7 for Policy framework with the study of both use cases.","secretary_remarks":"Revised to S2-181177.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20060,"status":"revised","reservation_date":"2018-01-16 06:29:20","uploaded":"2018-01-16 06:55:12","revisionof":"","revisedto":"S2-181177","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180567.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180568","title":"Paging failure for CE-capable UEs after 2G\/3G to 4G idle-mode mobility","source":"Intel, NTT DOCOMO","contact":"Puneet Jain","contact-id":36283,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the network supports CE-Capable UEs (see TS 36.300) after the 'first TAU in-idle mode following the RAT change', the MME may initiate UE Radio Capability Match Request procedure indicating to eNB that update to UE's Radio capability is needed. The eNB based on 'update needed' indicator requests the UE for its radio capability and provides it to the MME.","secretary_remarks":"Revised in parallel session to S2-180836.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10270,"status":"revised","reservation_date":"2018-01-16 06:31:11","uploaded":"2018-01-16 09:27:00","revisionof":"","revisedto":"S2-180836","release":"Rel-13","crspec":23.401,"crspecversion":"13.13.0","workitem":[{"winame":"TEI13"}],"crnumber":3386.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180568.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180569","title":"23.501: Editorial corrections in clause 5.3.2.4 Support of a UE registered over both 3GPP and Non-3GPP access","source":"ETRI","contact":"Yooah Kang","contact-id":63871,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution proposes editorial updates in clause 5.3.2.4 to support a Implicit Deregistration timer for either 3GPP or non-3GPP access.","secretary_remarks":"Revised in parallel session to S2-180929.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18380,"status":"revised","reservation_date":"2018-01-16 06:33:46","uploaded":"2018-01-16 06:42:29","revisionof":"","revisedto":"S2-180929","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180569.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180570","title":"Paging failure for CE-capable UEs after 2G\/3G to 4G idle-mode mobility","source":"Intel, NTT DOCOMO","contact":"Puneet Jain","contact-id":36283,"tdoctype":"CR","for":"Approval","abstract":"Rel-14 mirror CR: Summary of change: If the network supports CE-Capable UEs (see TS 36.300) after the 'first TAU in-idle mode following the RAT change', the MME may initiate UE Radio Capability Match Request procedure indicating to eNB that update to UE's Radio capability is needed. The eNB based on 'update needed' indicator requests the UE for its radio capability and provides it to the MME.","secretary_remarks":"Revised in parallel session to S2-180837.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10300,"status":"revised","reservation_date":"2018-01-16 06:35:30","uploaded":"2018-01-16 09:27:00","revisionof":"","revisedto":"S2-180837","release":"Rel-14","crspec":23.401,"crspecversion":"14.6.0","workitem":[{"winame":"TEI13"}],"crnumber":3387.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180570.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180571","title":"23.502: Updating Network Triggered Service Request to support selective re-activation of PDU session over non-3GPP access","source":"ETRI","contact":"Yooah Kang","contact-id":63871,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution proposes to update Network Triggered Service Request procedure to support selective re-activation of PDU session over non-3GPP access.","secretary_remarks":"Revised in parallel session to S2-180949.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18720,"status":"revised","reservation_date":"2018-01-16 06:36:44","uploaded":"2018-01-16 06:42:42","revisionof":"","revisedto":"S2-180949","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180571.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180572","title":"Paging failure for CE-capable UEs after 2G\/3G to 4G idle-mode mobility","source":"Intel, NTT DOCOMO","contact":"Puneet Jain","contact-id":36283,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: If the network supports CE-Capable UEs (see TS 36.300) after the 'first TAU in-idle mode following the RAT change', the MME may initiate UE Radio Capability Match Request procedure indicating to eNB that update to UE's Radio capability is needed. The eNB based on 'update needed' indicator requests the UE for its radio capability and provides it to the MME.","secretary_remarks":"Revised in parallel session to S2-180838.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10330,"status":"revised","reservation_date":"2018-01-16 06:41:02","uploaded":"2018-01-16 09:27:00","revisionof":"","revisedto":"S2-180838","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI13"}],"crnumber":3388.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180572.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180573","title":"[DRAFT] Reply LS on Paging failures for CE Capable UEs","source":"Intel","contact":"Puneet Jain","contact-id":36283,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Paging failures for CE Capable UEs after 2G\/3G - > 4G idle-mode mobility","secretary_remarks":"Response to S2-175972 at S2-122BIS (already replied to in S2-176685) Revised in parallel session to S2-180839.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10370,"status":"revised","reservation_date":"2018-01-16 06:50:25","uploaded":"2018-01-16 09:27:00","revisionof":"","revisedto":"S2-180839","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180573.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180574","title":"23.716: Update KI #7 on Policy","source":"Huawei, HiSilicon, Telstra","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to revise the KI on policy for taking into account whether policy are provision via URSP or TR-069 or both","secretary_remarks":"Merged into S2-181178","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20120,"status":"merged","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:33:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180574.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180575","title":"23.716: New KI on Emergency Service support","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to add a KI on whether and how support ES","secretary_remarks":"Revised to S2-181182.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20220,"status":"revised","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:33:31","revisionof":"","revisedto":"S2-181182","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180575.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180576","title":"23.716: New KI on LADN, SSC Mode, Location Reporting","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to add new KIs on LADN, SSC Modes and Location reporting.","secretary_remarks":"Revised to S2-181183.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20240,"status":"revised","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:33:31","revisionof":"","revisedto":"S2-181183","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180576.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180577","title":"23.716: New KI on Network Function selection","source":"Huawei, HiSilicon, Telstra","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to add new KIs Network Function Selection","secretary_remarks":"Not Handled","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20270,"status":"not treated","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:33:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180577.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180578","title":"23.716: Solution for KI#1 on NAS transport","source":"Huawei, HiSilicon, Telstra","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to add a solution for KI#1 on NAS transport","secretary_remarks":"Not Handled","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20290,"status":"not treated","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:33:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180578.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180579","title":"[draft] LS to BBF on NAS transport solution","source":"Huawei, Hisilicon, Telstra","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"This LS proposes to inform BBF about the solution adopted for NAS transport in Access Network","secretary_remarks":"Response to S2-180772. Not Handled","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20300,"status":"not treated","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:33:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180579.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180580","title":"23.716: Definition and terminology","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to add definition and terminology and modify the text according to the new definitions.","secretary_remarks":"Revised to S2-181174.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19930,"status":"revised","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:33:31","revisionof":"","revisedto":"S2-181174","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180580.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180581","title":"23.716: Access Type definition","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution introduce the applicability of Access Type concept for 5RG connected to wireline AN","secretary_remarks":"Revised to S2-181175.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19980,"status":"revised","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:33:31","revisionof":"","revisedto":"S2-181175","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180581.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180582","title":"23.716: KI5: handover solution for wireline AN","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to solution for support of Handover for the scenario of 5RG and RG connected via wireline AN in KI5","secretary_remarks":"Not Handled","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20330,"status":"not treated","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:33:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180582.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180583","title":"23.716: Architecture solution revision","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes revised the architecture definition introducing the element within the Access Network","secretary_remarks":"Not Handled","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20280,"status":"not treated","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:33:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180583.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180584","title":"23.716: KI5: PDU session procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to add PDU session procedure for 5RG connected via wireline AN.","secretary_remarks":"Not Handled","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20320,"status":"not treated","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:33:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180584.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180585","title":"23.716: Update KI #3 on Security","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution propose to clarify security Key issue for 5WWC","secretary_remarks":"Revised to S2-181176.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20030,"status":"revised","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:30:37","revisionof":"","revisedto":"S2-181176","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180585.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180586","title":"23.716: Revision on KI10 ATSSS in Hybrid Access","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution propose to update the KI10 for 5WWC","secretary_remarks":"Revised to S2-181180.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20160,"status":"revised","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:30:37","revisionof":"","revisedto":"S2-181180","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180586.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180587","title":"23.716: Key issue for IPTV Support","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution propose the key issue of IPTV for 5WWC","secretary_remarks":"Revised to S2-181181.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20190,"status":"revised","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:30:37","revisionof":"","revisedto":"S2-181181","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180587.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180588","title":"23.501: Clarification on emergency services for non-3GPP access","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarify that if the 3GPP access become available after UE has establish the emergency session over the non-3GPP, whether UE transfers the emergency session to the 3GPP access depends on UE decision that are implementation dependent.  2. Remove the sentence 'For emergency registered UEs on untrusted Non-3GPP access, the UE is only reachable in CM-CONNECTED state: since the UE has initiated an emergency registration over untrusted Non-3GPP access only when it is not possible over 3GPP access, 3GPP access is assumed to be unavailable for paging the UE'.","secretary_remarks":"Revised in parallel session to S2-180952.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18910,"status":"revised","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:30:37","revisionof":"","revisedto":"S2-180952","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180588.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180589","title":"Discussion on the Network triggered SR Procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution give a discussion relates to the LS received from CT WG1 on '5G service request procedure'","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18480,"status":"noted","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:30:37","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180589.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180590","title":"23.502: Revision on Service Request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Propose that UE can start the Service Request Procedure even none of the PDU sessions can be transferred to 3GPP access.","secretary_remarks":"Revised in parallel session to S2-180941.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18490,"status":"revised","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:30:37","revisionof":"","revisedto":"S2-180941","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180590.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180591","title":"23.501: Alignment with TS23.502 on Service Request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It has been replaced the optional indication of the PDU session to be reactivated with the mandatory list of PDU session to be reactivated","secretary_remarks":"Revised in parallel session to S2-180942.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18750,"status":"revised","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:30:37","revisionof":"","revisedto":"S2-180942","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180591.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180592","title":"[draft] Reply LS to CT WG1 on 5G service request procedure","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"LS Reply to CT WG1 to response the issue of 5G service request procedure","secretary_remarks":"Response to S2-180003 Revised in parallel session to S2-180943.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18530,"status":"revised","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:30:37","revisionof":"","revisedto":"S2-180943","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180592.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180593","title":"Discussion on the LS sent by SA WG3","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution give a discussion relates to the LS received from CT WG1 on '5G service request procedure'","secretary_remarks":"Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13910,"status":"not treated","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:30:37","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180593.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180594","title":"[draft] Reply LS to SA WG3 on User Plane Security Policy","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"LS Reply to CT WG1 to response the issue of UP security policy","secretary_remarks":"Response to S2-180049. Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14060,"status":"not treated","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:30:37","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG3","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180594.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180595","title":"23.501: Clarification on location reporting for LADN in RRC Inactive clause 5.3.3.2.5","source":"ETRI","contact":"Dongmyoung Kim","contact-id":65275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: When location reporting with area of interest is configured, the NG-RAN node report whether the UE in IN or OUT or UNKNOWN whenever it detects the event. For the UE in RRC Inactive mode, according to the allocated RNA and the area of interested, UNKNOWN state can be sent to the CN. The proposed operation is aligned with the UE location change notification served by AMF.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16540,"status":"approved","reservation_date":"2018-01-16 06:59:35","uploaded":"2018-01-16 11:14:49","revisionof":"","revisedto":"S2-182048","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180595.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180596","title":"Discussion on MT SMS domain selection by SMSF for clarification","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses MT SMS domain selection by SMSF for clarification.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17220,"status":"noted","reservation_date":"2018-01-16 07:00:11","uploaded":"2018-01-16 10:25:28","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_125_Gothenburg\/Docs\/S2-180596.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180597","title":"23.502: Location reporting procedure for LADN in RRC Inactive state - TS 23.502","source":"ETRI","contact":"Dongmyoung Kim","contact-id":65275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: When location reporting with area of interest is configured, the NG-RAN node report whether the UE in IN or OUT or UNKNOWN whenever it detects the event. For the UE in RRC Inactive mode, according to the allocated RNA and the area of interested, UNKNOWN state can be sent to the CN. The proposed operation is aligned with the UE location change notification served by AMF.","secretary_remarks":"Revised in parallel session to S2-181235.","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16550,"status":"revised","reservation_date":"2018-01-16 07:02:09","uploaded":"2018-01-16 11:14:49","revisionof":"","revisedto":"S2-181235","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180597.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180598","title":"23.501: Clarification on MT SMS domain selection by SMSF","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add interface between SMSF and MME to all architectures for SMS over NAS. For simplicity, adding '\/MME' into the existing 'to\/from SGs MSC' is proposed rather than adding a separate interface (line) so that 'to\/from SGs MSC' will be updated to 'to\/from SGs MSC\/MME'.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17230,"status":"postponed","reservation_date":"2018-01-16 07:06:13","uploaded":"2018-01-16 10:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180598.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180599","title":"23.502: Clarification on MT SMS domain selection by SMSF","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Clarification is made that SMSF does not perform MT SMS domain selection (i.e. re-attempting MT SMS delivery to other entity) when it received the MT SMS from IP-SM-GW which means re-attempting MT SMS delivery is on-going in the IP-SM-GW.  2) Clarification is made that the SMSF forwards the MT SMS to the chosen SMS entity if the chosen entity is reachable.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17240,"status":"postponed","reservation_date":"2018-01-16 07:09:29","uploaded":"2018-01-16 10:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180599.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180600","title":"MT SMS domain selection by IP-SM-GW","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: SMSF is added as a possible SMS entity for MT SMS delivery.","secretary_remarks":"Agreed in parallel session. Block Approved. Revised at S2#126 in S2-181597","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17250,"status":"revised","reservation_date":"2018-01-16 07:12:52","uploaded":"2018-01-16 10:25:28","revisionof":"","revisedto":"S2-181597","release":"Rel-15","crspec":23.204,"crspecversion":"14.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":109.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180600.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180601","title":"23.716: QoS interworking for an RG and a UE behind the RG","source":"Telstra","contact":"Robert Ropolyi","contact-id":73241,"tdoctype":"pCR","for":"Approval","abstract":"The pCR adds a new aspect to the key issue on QoS support in 5WWC: how to combine\/interwork the policies for both the RG and the UE behind RG.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20130,"status":"approved","reservation_date":"2018-01-16 07:22:03","uploaded":"2018-01-16 13:01:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180601.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180602","title":"23.501: Update on Traffic Detection Information","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Replacing PDU session ID with CN tunnel info as one of the traffic detection parameters.","secretary_remarks":"Revised to S2-181170.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13540,"status":"revised","reservation_date":"2018-01-16 07:31:11","uploaded":"2018-01-16 14:20:35","revisionof":"","revisedto":"S2-181170","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180602.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180603","title":"23.501: Proposal of Specifying Packet Detection Rule","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Proposed detailed descriptions of Packet Detection Rule.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13560,"status":"endorsed","reservation_date":"2018-01-16 07:31:11","uploaded":"2018-01-16 14:20:35","revisionof":"","revisedto":"S2-181553","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180603.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180604","title":"Proposal of Sequence Number Marking in the User Plane Function","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Approval","abstract":"It is proposed to marking user plane packet with sequence number in the packet header by user plane function.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13640,"status":"not treated","reservation_date":"2018-01-16 07:31:11","uploaded":"2018-01-16 14:20:36","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180604.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180605","title":"23.501: Proposal of Sequence Number Marking in the User Plane Function","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Propose a solution to achieve sequence number marking on user plane packet.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13650,"status":"not treated","reservation_date":"2018-01-16 07:31:11","uploaded":"2018-01-16 14:20:36","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180605.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180606","title":"23.501: Clarification on UDM service consumption order of UECM and SDM","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the texts describing\/implying the UDM service operation order description","secretary_remarks":"Revised to S2-181134.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19480,"status":"revised","reservation_date":"2018-01-16 07:31:11","uploaded":"2018-01-16 14:20:36","revisionof":"","revisedto":"S2-181134","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180606.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180607","title":"Correction of SDF Filter Description in PDR Table","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that one or more SDF filters can be included in a PDR.","secretary_remarks":"Revised in parallel session to S2-180897.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10670,"status":"revised","reservation_date":"2018-01-16 07:31:11","uploaded":"2018-01-16 14:20:36","revisionof":"","revisedto":"S2-180897","release":"Rel-14","crspec":23.214,"crspecversion":"14.5.0","workitem":[{"winame":"CUPS"}],"crnumber":63.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180607.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180608","title":"Correction of SDF Filter Description in PDR Table","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: Clarify that one or more SDF filters can be included in a PDR.","secretary_remarks":"Revised in parallel session to S2-180898.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10690,"status":"revised","reservation_date":"2018-01-16 07:31:12","uploaded":"2018-01-16 14:20:36","revisionof":"","revisedto":"S2-180898","release":"Rel-15","crspec":23.214,"crspecversion":"15.1.0","workitem":[{"winame":"CUPS"}],"crnumber":64.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180608.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180609","title":"23.726: Key Issue Proposal: SMF and UPF Insert\/Relocation due to UE Mobility","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"In this contribution, it is proposed a new key issue to study the SMF and UPF insert or relocation due to UE mobility.","secretary_remarks":"Revised in parallel session to S2-180955.","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21810,"status":"revised","reservation_date":"2018-01-16 07:31:13","uploaded":"2018-01-16 14:20:36","revisionof":"","revisedto":"S2-180955","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180609.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180610","title":"23.787: Key Issue Proposal: Encrypted Traffic Verification","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"In this contribution, it is proposed a new key issue to study encrypted data verification.","secretary_remarks":"Merged into S2-180961","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21340,"status":"merged","reservation_date":"2018-01-16 07:31:13","uploaded":"2018-01-16 14:20:35","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180610.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180611","title":"23.502: Establishment Cause for Non-3GPP Access","source":"Motorola Mobility, Lenovo","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Specify the contents of AN Parameters (including the Establishment Cause) when sent over non-3GPP access.","secretary_remarks":"Revised in parallel session to S2-180930.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18410,"status":"revised","reservation_date":"2018-01-16 07:33:58","uploaded":"2018-01-16 14:45:31","revisionof":"","revisedto":"S2-180930","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180611.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180612","title":"23.501: Corrections to Combined N3IWF\/ePDG Selection","source":"Motorola Mobility, Lenovo","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The Combined N3IWF\/ePDG Selection procedure is clarified. Also, we believe that the use of the 'preference' parameter is enough for selecting between N3IWF and ePDG and therefore the relevant EN is deleted.","secretary_remarks":"Revised in parallel session, merging S2-180190, to S2-180931.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18450,"status":"revised","reservation_date":"2018-01-16 07:39:55","uploaded":"2018-01-16 14:45:30","revisionof":"","revisedto":"S2-180931","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180612.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180613","title":"23.502: Clean up FFSs in 4.11.1.2.2","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1 SSC mode is sent to UE during the PDN Connection Establishment procedure. 2 change the 5G security context mapping from an EN to a Note. 3 add description between SMF and UPF","secretary_remarks":"Revised in parallel session to S2-180782.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17700,"status":"revised","reservation_date":"2018-01-16 08:05:42","uploaded":"2018-01-16 11:26:32","revisionof":"","revisedto":"S2-180782","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180613.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180614","title":"23.724: KI - Power Saving Functions","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"pCR","for":"Approval","abstract":"This paper discusses an FS_CIoT_5G Key Issue on Power Savings Functions","secretary_remarks":"Revised in parallel session to S2-180830.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20890,"status":"revised","reservation_date":"2018-01-16 08:06:27","uploaded":"2018-01-16 10:01:54","revisionof":"","revisedto":"S2-180830","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180614.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180615","title":"Transfer PDU session ID in the EPS","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UE provides PDU session ID in the Attach and UE requested PDN connectivity procedure.","secretary_remarks":"Revision of S2-180560. Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17600,"status":"noted","reservation_date":"2018-01-16 08:11:57","uploaded":"2018-01-16 13:44:40","revisionof":"S2-180560","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3389.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180615.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180616","title":"23.794: Adding architecture assumption on multiple slicing","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes adding an architecture assumption that the different IMS service can be provided on different slice simultaneously","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22270,"status":"noted","reservation_date":"2018-01-16 08:11:58","uploaded":"2018-01-16 13:44:40","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180616.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180617","title":"23.502: Clarification on Network data analytics procedure","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove the Nnwdaf_Analytics_Info_Response service","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":16000,"status":"not treated","reservation_date":"2018-01-16 08:12:07","uploaded":"2018-01-16 12:07:10","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180617.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180618","title":"23.502: UE providing assistance information for UE Policy decision and delivery","source":"Motorola Mobility, Lenovo","contact":"Dimitrios Karampatsis","contact-id":70692,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: UE includes in initial registration request the version ID of the UE Policies installed. The version ID is sent transparently by the AMF to the PCF using the Policy association establishment procedure. The PCF decides, based on feedback from the UDR, if the policies installed at the UE, are still applicable. If new Policies are required, the PCF and\/or V-PCF in the roaming case, provides new policies by using the UE Policy Delivery mechanism. The new policies include a new version ID for new ANDSP and\/or a new version ID for new URSP policies.","secretary_remarks":"Merged into S2-180965.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14690,"status":"merged","reservation_date":"2018-01-16 08:14:03","uploaded":"2018-01-16 10:35:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180618.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180619","title":"23.503: UE providing assistance information for UE Policy decision & delivery","source":"Motorola Mobility, Lenovo","contact":"Dimitrios Karampatsis","contact-id":70692,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: UE includes in initial registration request the version ID of the UE Policies installed. The version ID is sent transparently by the AMF to the PCF using the Policy association establishment procedure. The PCF decides, based on feedback from the UDR, if the policies installed at the UE, are is still applicable. If new Policies are required, the PCF and\/or V-PCF in the roaming case, provides new policies by using the UE Policy Delivery mechanism. The new policies include a new version ID for new ANDSP and new version ID for new URSP policies.","secretary_remarks":"Merged into S2-180924.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14700,"status":"merged","reservation_date":"2018-01-16 08:19:47","uploaded":"2018-01-16 10:35:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180619.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180620","title":"23.793: Update to KI#5: Multi-access PDU sessions (untrusted access)","source":"ITRI","contact":"Chia-lin Lai","contact-id":60383,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to clarify the scenarios in Multi-access PDU sessions in TR 23.793.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20480,"status":"noted","reservation_date":"2018-01-16 08:27:48","uploaded":"2018-01-16 09:09:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180620.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180621","title":"23.716: Clarify of Key issue #5: Mobility management","source":"ITRI","contact":"Chia-lin Lai","contact-id":60383,"tdoctype":"pCR","for":"Approval","abstract":"Abstract of the contribution: This contribution proposes to update to KI#5 for Mobility Management in TR 23.716.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20050,"status":"postponed","reservation_date":"2018-01-16 08:29:26","uploaded":"2018-01-16 09:09:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180621.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180622","title":"23.502: UE context removal in UDM during deregistration procedure","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: SMF invoke Nudm_SDM_Unsubscribe and Nudm_UECM_Deregistration service operations at Step 5 for the UDM to remove the corresponding subscription and UE context.","secretary_remarks":"Revised in S2-180658","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12830,"status":"revised","reservation_date":"2018-01-16 08:32:33","uploaded":"2018-01-16 08:49:16","revisionof":"","revisedto":"S2-180658","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180622.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180623","title":"SMS reachability monitoring correction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The change in TS 23.682 CR 0228 is partially reversed.","secretary_remarks":"Revised in parallel session to S2-180914.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10530,"status":"revised","reservation_date":"2018-01-16 08:35:22","uploaded":"2018-01-16 12:48:35","revisionof":"","revisedto":"S2-180914","release":"Rel-13","crspec":23.682,"crspecversion":"13.9.0","workitem":[{"winame":"MONTE"}],"crnumber":379.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180623.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180624","title":"SMS reachability monitoring correction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Rel-14 mirror CR: Summary of change: The change in TS 23.682 CR 0228 is partially reversed.","secretary_remarks":"Revised in parallel session to S2-180915.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10560,"status":"revised","reservation_date":"2018-01-16 08:37:47","uploaded":"2018-01-16 12:48:35","revisionof":"","revisedto":"S2-180915","release":"Rel-14","crspec":23.682,"crspecversion":"14.6.0","workitem":[{"winame":"MONTE"}],"crnumber":380.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180624.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180625","title":"23.502: Removal of Nudm_UECM_DeregistrationNotification ACK message","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Nudm_UECM_DeregistrationNotification ACK is removed from the step 3. 2. Step 4 box is extended to the UDM side.","secretary_remarks":"Revised in S2-180660","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12860,"status":"revised","reservation_date":"2018-01-16 08:39:51","uploaded":"2018-01-16 08:49:16","revisionof":"","revisedto":"S2-180660","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180625.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180626","title":"SMS reachability monitoring correction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: The change in TS 23.682 CR 0228 is partially reversed.","secretary_remarks":"Revised in parallel session to S2-180916.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10580,"status":"revised","reservation_date":"2018-01-16 08:39:57","uploaded":"2018-01-16 12:48:35","revisionof":"","revisedto":"S2-180916","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"MONTE"}],"crnumber":381.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180626.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180627","title":"23.502: UE context retrival to select a proper SMF during handover b\/w 3GPP and non-3GPP","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: During handover when the AMF does not know the PDU Session ID to handover, it retrieve the PDU Session Info from the UDM, using Nudm_UECM_Get.","secretary_remarks":"Revised in S2-180684","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18790,"status":"revised","reservation_date":"2018-01-16 08:43:05","uploaded":"2018-01-16 08:49:16","revisionof":"","revisedto":"S2-180684","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180627.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180628","title":"CIoT Attach correction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of the option that conflicts with TS 36.300.","secretary_remarks":"Revised in parallel session to S2-180840.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10440,"status":"revised","reservation_date":"2018-01-16 08:43:23","uploaded":"2018-01-16 12:48:34","revisionof":"","revisedto":"S2-180840","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"CIoT"},{"winame":"TEI15"}],"crnumber":3390.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180628.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180629","title":"23.502: Service Request procedure corrections","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: As above.","secretary_remarks":"Revised to S2-181146.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16280,"status":"revised","reservation_date":"2018-01-16 08:43:51","uploaded":"2018-01-16 13:01:20","revisionof":"","revisedto":"S2-181146","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180629.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180630","title":"Non-roaming Architecture for Network Exposure Function in reference point representation","source":"Intel","contact":"Puneet Jain","contact-id":36283,"tdoctype":"discussion","for":"Agreement","abstract":"This paper proposes to introduce Non-roaming Architecture for Network Exposure Function in reference point representation.","secretary_remarks":"Not Handled","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19030,"status":"not treated","reservation_date":"2018-01-16 08:44:52","uploaded":"2018-01-16 09:27:00","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_125_Gothenburg\/Docs\/S2-180630.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180631","title":"23.502: Non-geographically assigned GUAMI delivery in RRC for for AMF selection","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In idle mode mobility from EPC to 5GC, it is proposed that when the UE has a native 5G-GUTI only if the 5G-GUTI is geo-graphically assigned, its GUAMI part is included in the RRC message.","secretary_remarks":"Revised in S2-180686","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18850,"status":"revised","reservation_date":"2018-01-16 08:45:17","uploaded":"2018-01-16 08:49:16","revisionof":"","revisedto":"S2-180686","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180631.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180632","title":"Addition of EC restriction parameter in S1 AP PAGING message","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The requested EC Restriction parameter is added in the S1 AP PAGING message","secretary_remarks":"Revised in parallel session to S2-180834.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10190,"status":"revised","reservation_date":"2018-01-16 08:47:04","uploaded":"2018-01-16 12:48:34","revisionof":"","revisedto":"S2-180834","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"CIoT_Ext"},{"winame":"TEI15"}],"crnumber":3391.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180632.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180633","title":"23.791: Key issue on customized mobility management","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue on customizing mobility management based on NWDA output.","secretary_remarks":"Revised in parallel session to S2-180863.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21620,"status":"revised","reservation_date":"2018-01-16 08:47:43","uploaded":"2018-01-16 09:55:46","revisionof":"","revisedto":"S2-180863","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180633.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180634","title":"23.502: Correction of Npcf_BDTPolicyControl (background data transfer)","source":"KDDI","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Added the Background Data Transfer policy reference ID and the description for step 9","secretary_remarks":"Revised in parallel session to S2-181008.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15720,"status":"revised","reservation_date":"2018-01-16 08:48:01","uploaded":"2018-01-16 13:16:34","revisionof":"","revisedto":"S2-181008","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180634.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180635","title":"23.502: Service Request procedure and near-simultaneous multiple PDN activation","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Text is added to clarify that multiple Service Request procedures can run in parallel.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16310,"status":"postponed","reservation_date":"2018-01-16 08:48:47","uploaded":"2018-01-16 13:00:15","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180635.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180636","title":"[DRAFT] Reply LS on Paging in case of Enhanced Coverage Restriction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to explain that EC Restricted parameter is included in S1 PAGING alreary in Rel-14.","secretary_remarks":"Response to S2-180729 Revised in parallel session to S2-180835.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10210,"status":"revised","reservation_date":"2018-01-16 08:50:44","uploaded":"2018-01-16 12:48:34","revisionof":"","revisedto":"S2-180835","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180636.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180637","title":"Discussion on EPC to 5GC interworking","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"discussion","for":"Approval","abstract":"This contribution discuss an open issue for mobility from EPC to 5GC and provide a solution to address it. It is proposed that 1) for IDLE mode mobility from EPC to 5GC, the AMF selects a default V-SMF.2) Remove the PDU Session ID and the S-NSSAI from the Registration Request message; 3) SMF+PGW-C returns the S-NSSAI to AMF so the AMF can know the S-NSSAI of the PDU session","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":12060,"status":"noted","reservation_date":"2018-01-16 08:52:19","uploaded":"2018-01-16 10:21:01","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_125_Gothenburg\/Docs\/S2-180637.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180638","title":"TS 23.501 mobility from EPC to 5GC","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The proposed solution is following 1)  For IDLE mode mobility from EPC to 5GC, the AMF selects a default V-SMF. 2)  Remove the PDU Session ID and the S-NSSAI from the Registration Request message 3)  SMF+PGW-C returns the S-NSSAI to AMF so the AMF can know the S-NSSAI of the PDU session","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12110,"status":"not treated","reservation_date":"2018-01-16 08:52:26","uploaded":"2018-01-16 10:21:01","revisionof":"","revisedto":"S2-181541","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180638.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180639","title":"23.502: Mobility from EPC to 5GC","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The proposed solution is following 1)  For IDLE mode mobility from EPC to 5GC, the AMF selects a default V-SMF. 2)  Remove the PDU Session ID and the S-NSSAI from the Registration Request message 3)  SMF+PGW-C returns the S-NSSAI to AMF so the AMF can know the S-NSSAI of the PDU session There are two other changes: 1)  In Preparation phase the SMF+PGW-C sends the S-NSSAI in the N2 SM Information 2)  EPS to 5GS Mobility Registration Procedure, the steps for context transfer between MME and AMF are not needed for CONNECTED mode, therefore it is optional.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12130,"status":"not treated","reservation_date":"2018-01-16 08:52:26","uploaded":"2018-01-16 10:21:01","revisionof":"","revisedto":"S2-181542","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180639.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180640","title":"23.502: Slicing handling for EPS to 5GS Mobility without N26","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add condition that the UE recieves ' the interworking without N26' indication. Add S-NSSAI received from PGW-C\/SMF in PDU session establishment request message","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18210,"status":"approved","reservation_date":"2018-01-16 08:52:26","uploaded":"2018-01-16 10:21:01","revisionof":"","revisedto":"S2-181536","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180640.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180641","title":"23.501: Removal redundant text in Registration procedure","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove the redundant sentence","secretary_remarks":"Merged into S2-181191.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12620,"status":"merged","reservation_date":"2018-01-16 08:52:26","uploaded":"2018-01-16 10:21:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180641.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180642","title":"23.502: Alignment of Namf_MT_EnableUEReachability service operation","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove reference to clause 4.2.3.4 and clause 4.2.2.3.3. Remove the NEF,PCF,SMF,UDM from known consumers of Namf_MT_EnableUEReachability in table 5.2.2.1-1 and add SMSF.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12880,"status":"endorsed","reservation_date":"2018-01-16 08:52:26","uploaded":"2018-01-16 10:21:01","revisionof":"","revisedto":"S2-181540","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180642.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180643","title":"23.502: Clarification on Event co-relation ID","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the Event co-relation ID is per event notification subscription.","secretary_remarks":"Merged into S2-181125.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19160,"status":"merged","reservation_date":"2018-01-16 08:52:26","uploaded":"2018-01-16 10:21:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180643.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180644","title":"23.502: Clarification on PCF ID during AMF relocation","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In registration procedure a new trigger to perform Policy Association Establishment to the PCF is added. The PCF ID is added in UE context so it can be reused for handover.","secretary_remarks":"Merged in a 6.5.6 session into S2-180979.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12630,"status":"merged","reservation_date":"2018-01-16 08:52:26","uploaded":"2018-01-16 10:21:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180644.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180645","title":"23.501: Slicing support for roaming","source":"Samsung, SK Telecom","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: If Requested NSSAI was not provided, the Allowed NSSAI includes default S-NSSAIs only but the mapping information includes all S-NSSAIs that the UE is allowed to use in the serving PLMN. The UE uses the mapping information when it constructs Reqeusted NSSAI afterwards. Companion draftCR for TS 23.502, S2-180648, is also provided.","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":11770,"status":"noted","reservation_date":"2018-01-16 08:52:31","uploaded":"2018-01-16 11:09:06","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180645.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180646","title":"Correction to the speed encoding","source":"Nokia, Nokia Shanghai Bell, NextNav","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The superscript in the bit field value is restored back to what it is in the earlier versions of this TS.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10760,"status":"agreed","reservation_date":"2018-01-16 08:54:27","uploaded":"2018-01-16 12:48:35","revisionof":"","revisedto":"","release":"Rel-14","crspec":23.032,"crspecversion":"14.0.0","workitem":[{"winame":"TEI14"}],"crnumber":14.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180089","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180646.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180647","title":"MME re-negotiation of specific APN","source":"Nokia, Nokia Shanghai Bell, Verizon","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The PDN connection establishment is enhanced by the MME capability to not only fill in the default APN when no APN is requested by the UE, but also to re-negotiate a specific APN that is explicitly requested by the UE based on subscription data.","secretary_remarks":"This was postponed.","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23320,"status":"postponed","reservation_date":"2018-01-16 08:57:55","uploaded":"2018-01-16 12:48:35","revisionof":"","revisedto":"S2-182235","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3392.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180647.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180648","title":"23.501: Slicing support for roaming","source":"Samsung, SK Telecom","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change the Mapping Of Allowed NSSAI to the Mapping Of NSSAI.  The Mapping Of NSSAI is the mapping of each available S-NSSAI for the serving PLMN to the S-NSSAIs of the Configured NSSAI for the HPLMN. Companion draftCR for TS 23.501, S2-180645, is also provided.","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":11730,"status":"noted","reservation_date":"2018-01-16 09:00:41","uploaded":"2018-01-16 11:09:06","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180648.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180649","title":"23.502: Sending EBI to the NG-RAN","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Updating the Service Request procedure to provide EBI to NG-RAN. 2 Clarify only the mapping between EBI(s) and QFI(s) needs to be provided to the NG-RAN.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17820,"status":"approved","reservation_date":"2018-01-16 09:04:01","uploaded":"2018-01-16 09:55:46","revisionof":"","revisedto":"S2-181511","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180649.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180650","title":"23.502: Correction on the usage of ARP during EBI allocation procedure","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Adding a new optional parameter for EBI assignment, and clarify how to use it; 2. Removing the editor notes on how to use ARP in the 'Namf_Communication_EBIAssignment' service.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17830,"status":"noted","reservation_date":"2018-01-16 09:04:01","uploaded":"2018-01-16 09:55:46","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180650.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180651","title":"23.502: Clarification on keeping NAS signaling connection","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarifying the active flag is only triggered by MO data or signaling.  2. Clarifying the MME can keep the NAS signaling connection based on the existing indication from the UE.","secretary_remarks":"Not Handled","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18080,"status":"not treated","reservation_date":"2018-01-16 09:04:01","uploaded":"2018-01-16 09:55:46","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180651.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180652","title":"23.502: Indirect data forwarding in home routed roaming case","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarifying that, in home routed roaming case, the V-SMF is responsible for handling indirect data forwarding during the handover procedure from 5GS to EPS. 2 Similar clarfication for the handover procedure from EPS to 5GS. 3. Removing the FFS on the indirect data forwarding in home routed roaming.","secretary_remarks":"Revised in parallel session to S2-180784.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17860,"status":"revised","reservation_date":"2018-01-16 09:04:01","uploaded":"2018-01-16 09:55:46","revisionof":"","revisedto":"S2-180784","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180652.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180653","title":"23.502: Interaction between SMF and UPF during the inter-system change","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarifying that the PGW-C+SMF sends both of Sx and N4 session management messages to the UPF+PGW-U. 2 removing the related FFS.","secretary_remarks":"Revised in parallel session to S2-180783.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17890,"status":"revised","reservation_date":"2018-01-16 09:04:01","uploaded":"2018-01-16 09:55:46","revisionof":"","revisedto":"S2-180783","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180653.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180654","title":"23.503: 503 NSSP clarification","source":"Samsung","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Proposed to clarify that NSSP is an association of the matching applications and Subscribed S-NSSAIs","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14670,"status":"not treated","reservation_date":"2018-01-16 09:07:57","uploaded":"2018-01-16 11:09:06","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180654.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180655","title":"23.501: Non-roaming Architecture for Network Exposure Function in reference point representation","source":"Intel","contact":"Puneet Jain","contact-id":36283,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Non-roaming architecture for Network Exposure Function reference point representation corresponding to service based interface between NEF and AF is added.","secretary_remarks":"Revised in parallel session to S2-181266","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19040,"status":"revised","reservation_date":"2018-01-16 09:12:03","uploaded":"2018-01-16 09:27:00","revisionof":"","revisedto":"S2-181266","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180655.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180656","title":"23.502: Update to BSF operations","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. . \u00a7: add that S-NSSAI is part of the data used for session binding 2. Clarifications and Editorials:.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15580,"status":"postponed","reservation_date":"2018-01-16 09:18:02","uploaded":"2018-01-16 09:24:47","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180656.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180657","title":"23.501: Location information needed for UPF selection","source":"Nokia, Nokia Shanghai Bell,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13840,"status":"not treated","reservation_date":"2018-01-16 09:18:02","uploaded":"2018-01-16 14:42:26","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180657.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180658","title":"23.502: UE context removal in UDM during deregistration procedure","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: SMF invoke Nudm_SDM_Unsubscribe and Nudm_UECM_Deregistration service operations at Step 5 for the UDM to remove the corresponding subscription and UE context.","secretary_remarks":"Revision of S2-180622 Revised to S2-181255.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12840,"status":"revised","reservation_date":"2018-01-16 09:18:19","uploaded":"2018-01-16 09:49:45","revisionof":"S2-180622","revisedto":"S2-181255","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180658.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180659","title":"[DRAFT] Reply LS on Integration of northbound APIs with CAPIF","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6","secretary_remarks":"Response to S2-180051. Not Handled","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19020,"status":"not treated","reservation_date":"2018-01-16 09:19:35","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180659.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180660","title":"23.502: Removal of Nudm_UECM_DeregistrationNotification ACK message","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Nudm_UECM_DeregistrationNotification ACK is removed from the step 3. 2. Step 4 box is extended to the UDM side.","secretary_remarks":"Revision of S2-180625. Merged into S2-181191","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12870,"status":"merged","reservation_date":"2018-01-16 09:22:19","uploaded":"2018-01-16 09:49:45","revisionof":"S2-180625","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180660.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180661","title":"Supporting Common API framework for SCEF","source":"Qualcomm Incorporated, Convida Wireless LLC","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that SCEF functionality including authentication, authorization and service capability API discovery are supported via T8 based on the Common API Framework (CAPIF).","secretary_remarks":"Revised in parallel session to S2-181264.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18960,"status":"revised","reservation_date":"2018-01-16 09:23:53","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"S2-181264","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":382.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180661.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180662","title":"23.501: Update Roaming reference architectures","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: For the service-based interfaces architectures of roaming, the NSSF in the HPLMN should be deleted in the local breakout roaming architecture and added in the home routed roaming architecture","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11510,"status":"not treated","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:27","revisionof":"","revisedto":"S2-182179","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180662.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180663","title":"23.501: Clarify NSSF discovery","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The NSSF discovery function shall utilize an appropriate configured NRF to discover the NSSF instance(s) unless NSSF information is available by other means, e.g. local configuration, and select a NSSF instance based on the obtained NSSF information.","secretary_remarks":"Revised to S2-181159.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11930,"status":"revised","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:27","revisionof":"","revisedto":"S2-181159","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180663.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180664","title":"23.501: Align the terms of mapping of Requested NSSAI and Configured NSSAI for the HPLMN","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: The AMF or the NSSF shall perform the mapping between Allowed NSSAI and Configured NSSAI for the HPLMN to align with the description in the Registration procedure of TS 23.502. Change 2: If AMF queries the NSSF during PDU Session Establishment procedure, the AMF provides S-NSSAI of the Allowed NSSAI and the S-NSSAI with the corresponding value from the Configured NSSAI for the HPLMN if provided by UE to the NSSF.","secretary_remarks":"Open, check whether the wanted clarification is already somewhere. Revised off-line to S2-181344.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11740,"status":"revised","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"S2-181344","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180664.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180665","title":"23.502: Update Registration and registration with AMF re-allocation","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Add the rejected S-NSSAI(s) in the Registration Accept message of the Registration procedure which is described in the clause 5.15.4.1 of TS 23.501. 2. Clarify the Mapping Of Requested NSSAI and Subscribed S-NSSAIs included in the step 4a of the registration with AMF re-allocation. 3. Replace the Silce Selection Request message and NF discovery Request message with the service-based invocation as described in the TS 23.502. 4. Clarify NF consumer (e.g. AMF) discover NSSF as described in the S2-180663.","secretary_remarks":"Part on services merged into S2-181121. Revised in parallel session to S2-181123","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11810,"status":"revised","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"S2-181123","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180665.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180666","title":"23.502: Update SMF selection","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Replace the Silce Selection Request message with the service-based invocation as described in the TS 23.502. 2. Add the S-NSSAI from the Configured NSSAI for the HPLMN in the request sent from AMF to NSSF during PDU Session Establishment procedure  3. Update NSSF Services described in the TS 23.502. Mapping of Requested NSSAI should be included in the input optionally. 4. Clarify NF consumer (e.g. AMF) discover NSSF as described in the S2-180663.","secretary_remarks":"NSSAI mapping part merged into S2-181126.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19230,"status":"merged","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180666.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180667","title":"23.501: Add UNKNOWN status to UE location change","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding UNKNOWN status to UE Location change notification subclause.","secretary_remarks":"Revised to S2-181106.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13100,"status":"revised","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"S2-181106","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180667.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180668","title":"23.502: Generalize exposure of Mobility Events from AMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Generalize 'Exposure of Mobility Events from AMF' to cover both LADN and other cases.","secretary_remarks":"Revised to S2-181107.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13080,"status":"revised","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"S2-181107","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180668.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180669","title":"23.501: Clarification on editor's note related with LADN","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Delete the editor's note and clarify the UE determines whether a DNN is a LADN DNN based on URSP.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13330,"status":"not treated","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180669.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180670","title":"23.502: Operation type in Nsmf_PDUSession_UpdateSMContext Request","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: (1) Change the 'Cause' in Nsmf_PDUSession_Update SM Context Request during procedures of clause 4.2 to 4.12 to 'Operation type'. (2) Change 'Nsmf_PDUSession_UpdateSMContext Ack' in clause 4.2.6 and 4.12.4.2 to 'Nsmf_PDUSession_UpdateSMContext Response'. (3) Change the 'SM N2 Information' to 'N2 SM Information', 'MM N2 SM Information' to 'N2 MM Information'.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13850,"status":"not treated","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180670.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180671","title":"23.502: Rejection of PDU session establishment when authentication or authorization fails","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: (1) Clarify that the SMF should reject the PDU Session Establishment Request from the UE with an appropriate cause when the PDU Session cannot be established. (2) Correct wrong step number (step 19->step 20) in step 6.  (3) Editorial modificaiton in the service name in step 3a and 5 the Figure 4.3.2.2.1-1.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13590,"status":"not treated","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180671.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180672","title":"Discussion - Clarify policy update from PCF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discuss the issue of session management policy modification procedure.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15800,"status":"not treated","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"","crspec":23.502,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180672.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180673","title":"23.502: Clarify policy update procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: (1) Make alignments between clause 4.3.5.4 to 4.3.5.7 and clause 4.16.5. This part is hightlighted in green color. (2) Clarify the PCF behaviour in clause 4.16.5. This part is highlighted in blue color. (3) Correct wrong references in clause 5.2.5.4 and 5.2.8.3","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15810,"status":"not treated","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180673.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180674","title":"23.503: Add LADN indicator to DNN selection policy","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add an indicator in DNN selection policy to indicate a DNN is a LADN DNN.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14660,"status":"not treated","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180674.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180675","title":"23 501: Update Paging Policy Differentiation","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1. Clarify that in case of UPF buffering downlink data packet, the SMF determines PPI based on the DSCP received from the UPF. Change 2. Clarify QoS Flow indication is not needed for SMF determining PPI in case of SMF buffering downlink data packet. Change 3. Clarify how UPF handles the QoS Flows with different paging differentiation requirements and how RAN enforces paging policies in order to make it much clearer.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16230,"status":"approved","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"S2-181578","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180675.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180676","title":"23.502: Update Paging Policy Differentiation in Network triggered Service Request procedure","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1. Clarify UPF should send information to identify the QoS Flow for the DL data packet instead of information to identify QFI in the step 2a Change 2. Clarify information to identify the QoS Flow is not needed for SMF determining PPI in case of SMF buffering downlink data packet.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16270,"status":"endorsed","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"S2-181579","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180676.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180677","title":"23.502: Clarification for Area of validity in NW triggered SR procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: (1) Add a clarification in step 4 of clause 4.2.3.2 that step 4-11 can be skipped for the above case. (2) Editorial modification to change 'Area of validity for the N2 information' to 'Area of validity for the N2 SM information'. This part is highlighted in blue colour. (3) Delete redundant text in 4.2.3.2. This part is highlighted in green colour.","secretary_remarks":"Revised to S2-181147.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16320,"status":"revised","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"S2-181147","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180677.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180678","title":"23.502: Update Handover procedures in clause 4.11.1.2","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Correction on the procedure of 5GS to EPS handover using N26 interface in which the AMF sends the Handover Command to the source NG-RAN including (Transparent container (radio aspect parameters that the target eNB has set-up in the preparation phase), CN tunnel info for data forwarding per PDU Session, QoS flows for Data Forwarding). 2. Correction on the procedure of EPS to 5GS handover using N26 interface in which SMF+PGW-C initiates an N4 Session Modification procedure before SMF+PGW-C responses to AMF.","secretary_remarks":"Revised in parallel session to S2-180794.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17730,"status":"revised","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:29","revisionof":"","revisedto":"S2-180794","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180678.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180679","title":"Gap analysis for URLLC services in 5GC","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion try to give a gap analysis on URLLC services in 5GC.","secretary_remarks":"Noted","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23110,"status":"noted","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:29","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180679.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180680","title":"New SID: Enhancement of URLLC supporting in 5G","source":"Huawei, China Telecom, CATR, Telecom Italia, InterDigital, CATT, China Mobile, China Unicom, HiSilicon, III","contact":"Runze Zhou","contact-id":60945,"tdoctype":"SID new","for":"Approval","abstract":"This new SID proposal proposes a SI for enhancement of URLLC supporting in 5G","secretary_remarks":"Revision of postponed S2-178940 from S2#124 Revised to S2-181074.","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23120,"status":"revised","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:29","revisionof":"S2-178940","revisedto":"S2-181074","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180680.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180681","title":"Integration of northbound APIs with CAPIF","source":"Qualcomm Incorporated, Convida Wireless LLC","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"discussion","for":"Agreement","abstract":"This paper discusses how to incorporate CAPIF into SA WG2's work on northbound API specifications.","secretary_remarks":"Not Handled","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18940,"status":"not treated","reservation_date":"2018-01-16 09:31:50","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180681.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180682","title":"[DRAFT] Reply LS on mobility management congestion control","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-180027. Merged into S2-181189","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12470,"status":"merged","reservation_date":"2018-01-16 09:38:20","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180682.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180683","title":"Network identifier issues for E-UTRA connected to EPC and 5GC","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"discussion","for":"Agreement","abstract":"This paper discusses network identifier issues for E-UTRA connected to EPC and 5GC based on the related LS from RAN WG2 in R2-1712068.","secretary_remarks":"Not Handled","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12360,"status":"not treated","reservation_date":"2018-01-16 09:43:21","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180683.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180684","title":"23.502: UE context retrival to select a proper SMF during handover b\/w 3GPP and non-3GPP","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: During handover when the AMF does not know the PDU Session ID to handover, it retrieve the PDU Session Info from the UDM, using Nudm_UECM_Get.","secretary_remarks":"Revision of S2-180627. Merged into S2-181190","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18800,"status":"merged","reservation_date":"2018-01-16 09:43:25","uploaded":"2018-01-16 09:49:45","revisionof":"S2-180627","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180684.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180685","title":"23.502: Update Network Triggered Service Request Procedure","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Solve FFS in Network Triggered Service Request procedure in section 4.2.3.3.","secretary_remarks":"First changed was endorsed in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16340,"status":"endorsed","reservation_date":"2018-01-16 09:44:21","uploaded":"2018-01-16 10:54:32","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180685.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180686","title":"23.502: Non-geographically assigned GUAMI delivery in RRC for for AMF selection","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In idle mode mobility from EPC to 5GC, it is proposed that when the UE has a native 5G-GUTI only if the 5G-GUTI is geo-graphically assigned, its GUAMI part is included in the RRC message.","secretary_remarks":"Revision of S2-180631. Noted in parallel session","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18860,"status":"noted","reservation_date":"2018-01-16 09:46:26","uploaded":"2018-01-16 09:49:45","revisionof":"S2-180631","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180686.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180687","title":"[DRAFT] Reply LS on details of network identifiers","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2","secretary_remarks":"Response to S2-180008 Revised to S2-181186.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12270,"status":"revised","reservation_date":"2018-01-16 09:47:02","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"S2-181186","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180687.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180688","title":"23.716: Architecture principles for trusted non-3GPP access","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the architecture principles for trusted non-3GPP access.","secretary_remarks":"Revised to S2-181173.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19900,"status":"revised","reservation_date":"2018-01-16 09:47:41","uploaded":"2018-01-16 10:54:32","revisionof":"","revisedto":"S2-181173","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180688.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180689","title":"23.793: Multi-access PDU session support for Non-IP type PDU sessions","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to solve the question of whether a non-IP session type PDU session can take advantage of the multi-access PDU session feature in key issue #5.","secretary_remarks":"Not Handled","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20550,"status":"not treated","reservation_date":"2018-01-16 09:50:18","uploaded":"2018-01-16 10:54:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180689.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180690","title":"Structuring the work for Objectives 1-3","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"discussion","for":"Information","abstract":"Structuring the work for Objectives 1-3","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20590,"status":"noted","reservation_date":"2018-01-16 10:00:57","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180690.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180691","title":"23.724: TR skeleton","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"pCR","for":"Approval","abstract":"TR 23.724 V0.0.0 skeleton","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20610,"status":"approved","reservation_date":"2018-01-16 10:06:48","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180691.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180692","title":"23.724: TR Scope","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes the scope for TR 23.724.","secretary_remarks":"Revised in parallel session to S2-180824.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20620,"status":"revised","reservation_date":"2018-01-16 10:10:10","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"S2-180824","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180692.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180693","title":"23.501: Use of identifiers for mobility between GERAN\/UTRAN and 5GS","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies that upon mobility to the 5G System the UE may use a 5G-GUTI in the Registration procedure if it has a valid 5G-GUTI.  NOTE: the use of identifiers for mobility from the 5G System is clarified in TS 23.060.","secretary_remarks":"Revised to S2-181256.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12890,"status":"revised","reservation_date":"2018-01-16 10:12:18","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"S2-181256","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180693.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180694","title":"Documenting key issues, architectural requirements and potential baselines","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"discussion","for":"Information","abstract":"This paper summarizes the initial list of key issues for FS_CIoT_5G and identifies volunteers for providing initial key issue descriptions, architectural requirements and concise summaries of the baseline for each key issue (if applicable).","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20600,"status":"noted","reservation_date":"2018-01-16 10:13:17","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180694.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180695","title":"23.731: TR Skelton for eLCS","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Propose TR Skelton for enhanced location services.","secretary_remarks":"Revised in parallel session to S2-180901.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21860,"status":"revised","reservation_date":"2018-01-16 10:15:19","uploaded":"2018-01-16 10:37:09","revisionof":"","revisedto":"S2-180901","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180695.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180696","title":"23.731: TR Scope for eLCS","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Propose TR Scope for enhanced location services.","secretary_remarks":"Revised in parallel session to S2-180902.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21880,"status":"revised","reservation_date":"2018-01-16 10:15:19","uploaded":"2018-01-16 10:37:09","revisionof":"","revisedto":"S2-180902","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180696.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180697","title":"23.731: Architecture Assumption for eLCS","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Propose Archtecture Assmuption for enhanced Location services.","secretary_remarks":"Revised in parallel session to S2-180903.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21910,"status":"revised","reservation_date":"2018-01-16 10:15:19","uploaded":"2018-01-16 10:37:09","revisionof":"","revisedto":"S2-180903","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180697.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180698","title":"23.731: Architecture Requirements for eLCS","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Propose Archtecture Requirements for enhanced Location services.","secretary_remarks":"Revised in parallel session to S2-180904.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21940,"status":"revised","reservation_date":"2018-01-16 10:15:19","uploaded":"2018-01-16 10:37:09","revisionof":"","revisedto":"S2-180904","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180698.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180699","title":"23.731: Add Reference TR\/TS into the TR23.731","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Adding some TR\/TS reference","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21900,"status":"approved","reservation_date":"2018-01-16 10:15:19","uploaded":"2018-01-16 10:37:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180699.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180700","title":"23.731: Key Issue X: Indentify New Functionality and Distributions","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Define a Key issue X: Indentify New Functionality and Distributions","secretary_remarks":"Revised in parallel session to S2-180905.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21970,"status":"revised","reservation_date":"2018-01-16 10:15:19","uploaded":"2018-01-16 10:37:09","revisionof":"","revisedto":"S2-180905","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180700.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180701","title":"Use of identifiers for mobility between GERAN\/UTRAN and 5GS","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that upon mobility from the 5G System the UE may use a P-TMSI in the GPRS Attach procedure if it has a valid P-TMSI.  NOTE: the use of identifiers for mobility to the 5G System is clarified in TS 23.501.","secretary_remarks":"Revised to S2-181257.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12910,"status":"revised","reservation_date":"2018-01-16 10:15:42","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"S2-181257","release":"Rel-15","crspec":23.06,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2035.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180701.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180702","title":"23.724: Key Issue on Inter RAT idle mode mobility to\/from NB-IoT","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes some architectural assumptions and a Key Issue for FS_CIoT_5G related to Inter RAT idle mode mobility to\/from NB-IoT.","secretary_remarks":"Revised in parallel session to S2-180883.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21120,"status":"revised","reservation_date":"2018-01-16 10:16:58","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"S2-180883","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180702.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180703","title":"23.724: Key Issue on Group communication and messaging","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a Key Issue for FS_CIoT_5G related to Group Communication and messaging.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21080,"status":"noted","reservation_date":"2018-01-16 10:18:55","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180703.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180704","title":"23.501: Correcting erroneous indication name for interworking without N26","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Changed the indication name to align it with the rest of the specification text.","secretary_remarks":"Merged into S2-180791","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18320,"status":"merged","reservation_date":"2018-01-16 10:19:48","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180704.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180705","title":"23.501: Clarifications on Network Slicing aspects","source":"Nokia, Nokia Shanghai Bell, Telecom Italia","contact":"Alessio Casati","contact-id":68028,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: A Note intended to say no coexistence rules are supported in rel-15 is made clear.  It is clarified the mapping of Allowed NSSAI to configrured NSSAI of HPLMN is provided in roaming case.  It is clarified the configured NSSAI for a PLMN need not be configured only by HPLMN  The clause on Registration to a set of network slices is fixed.  Some editorials also in all affected clauses.","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12180,"status":"not treated","reservation_date":"2018-01-16 10:27:56","uploaded":"2018-01-16 11:07:14","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180705.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180706","title":"23.502: Updates of NSSF Services","source":"NTT DOCOMO","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Generalizing the rejected S-NSSAI, and not to restrict the rejected S-NSSAI to be only a part of Requested NSSAI","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19240,"status":"endorsed","reservation_date":"2018-01-16 10:37:45","uploaded":"2018-01-16 10:58:18","revisionof":"","revisedto":"S2-181702","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180706.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180707","title":"23.502: Removing EN for the UE Requested PDU Session Establishment procedure","source":"NTT DOCOMO","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove Editor's Note and do not add any texts for clarification of this Editor's Note, since texts as described in step#3a of clause 4.3.2.2.2 already aligns with TS23.501.","secretary_remarks":"Merge into S2-181157","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11580,"status":"merged","reservation_date":"2018-01-16 10:40:19","uploaded":"2018-01-16 10:58:18","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180707.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180708","title":"23.502: EPS bearer ID allocation update","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: If a SMF received a failure notification for EBI assignment request, the SMF can subscribe for EBI allocation availability notification, e.g. whenever any EBI mapped flow of a PDU session has been release for a UE. New service operations for EBI availability subscription, notification, unsubsription are added.  'S-NSSAI' and 'Released EBI list' are added as input parameters for Namf_Communication_EBIAssignment service operation (5.2.2.2.13). The S-NSSAI is described in the procedure in 4.11.1.4.1 but is missing from the service definition. The Released EBI list is explained in the service description but is missing from the service definition. The ARP list is changed to be mandatory input parameter for Namf_Communication_EBIAssignment Request, the parameter is needed to indicate the amount of requested EBIs. The corresponding EN is removed.  A new clause 4.11.1.4.x is added to describe a procedure for EPS bearer ID revokation when the EBI needs to be released e.g. wh","secretary_remarks":"Revised in parallel session to S2-180781.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17840,"status":"revised","reservation_date":"2018-01-16 11:03:34","uploaded":"2018-01-16 14:52:39","revisionof":"","revisedto":"S2-180781","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180708.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180709","title":"23.724: Key Issue on Power Saving Functions","source":"Qualcomm Inc., Convida Wireless LLC, Huawei, HiSilicon, Verizon Wireless","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes some architectural assumptions and a Key Issue for FS_CIoT_5G related to power saving functions.","secretary_remarks":"Revised in parallel session to S2-180829.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20850,"status":"revised","reservation_date":"2018-01-16 11:07:16","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"S2-180829","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180709.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180710","title":"23.501: Clarification on NAS level congestion control","source":"LG Electronics","contact":"Sang Min Park","contact-id":62105,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Specified SMF's behaviour on notifying DNN congestion to the AMF.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12480,"status":"noted","reservation_date":"2018-01-16 11:14:06","uploaded":"2018-01-16 11:36:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180710.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180711","title":"23.502: Rejecting Service Request for UP reactivation","source":"LG Electronics","contact":"Sang Min Park","contact-id":62105,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Signalling connection indicator is introduced for the UE to inform its purpose of SR trigerring, and specified additional condition when the AMF can send Service Reject instead of Service Accept.","secretary_remarks":"Revised to S2-181148.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16350,"status":"revised","reservation_date":"2018-01-16 11:18:49","uploaded":"2018-01-16 11:36:56","revisionof":"","revisedto":"S2-181148","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180711.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180712","title":"23:502: Removing the editor's note in 4.3.2.2.2 on S-NSSAI of slice roaming in PDU session establishment","source":"China Mobile","contact":"Wei Chen","contact-id":57801,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Removing the editor's note in 4.3.2.2.2 on PDU Session Establishment in home-routed case. That is because slice roaming solution for non-standardized S-NSSAI is already defined in TS 23.501.","secretary_remarks":"Merge into S2-181157","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11570,"status":"merged","reservation_date":"2018-01-16 11:22:45","uploaded":"2018-01-16 14:30:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180712.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180713","title":"23.794: Key issue of P-CSCF supporting N5 and legacy Rx simultaneously","source":"China Mobile","contact":"Jiang Yi","contact-id":56358,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue of P-CSCF supporting N5 and legacy Rx simultaneously.","secretary_remarks":"Merged into S2-180938","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22500,"status":"merged","reservation_date":"2018-01-16 11:46:48","uploaded":"2018-01-16 13:05:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180713.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180714","title":"23.794: Key issue of P-CSCF discovery for UE accessing to multiple IMS network via a network slice","source":"China Mobile","contact":"Jiang Yi","contact-id":56358,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue of P-CSCF discovery enhancement for UE to access multiple IMS network via a single 5GS network slice.","secretary_remarks":"Merged into S2-180936","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22360,"status":"merged","reservation_date":"2018-01-16 11:46:48","uploaded":"2018-01-16 13:05:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180714.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180715","title":"23.502: Update on UE context in AMF to support T-ADS query","source":"China Mobile","contact":"Jiang Yi","contact-id":56358,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Removing the editor's note in 4.3.2.2.2 on PDU Session Establishment in home-routed case. That is because slice roaming solution for non-standardized S-NSSAI is already defined in TS 23.501.","secretary_remarks":"Revised in parallel session to S2-180867.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17080,"status":"revised","reservation_date":"2018-01-16 11:46:48","uploaded":"2018-01-16 13:05:37","revisionof":"","revisedto":"S2-180867","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180715.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180716","title":"23.739: Skeleton for TR 23.739","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the skeleton for TR 23.739 'Study on EPC support for Mobility with Low Latency Communication'","secretary_remarks":"Revised in parallel session to S2-180844.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22820,"status":"revised","reservation_date":"2018-01-16 11:58:43","uploaded":"2018-01-16 12:38:08","revisionof":"","revisedto":"S2-180844","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180716.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180717","title":"23.739: Scope","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the Scope for TR 23.739 'Study on EPC support for Mobility with Low Latency Communication'","secretary_remarks":"Revised in parallel session to S2-180845.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22850,"status":"revised","reservation_date":"2018-01-16 12:01:13","uploaded":"2018-01-16 12:39:59","revisionof":"","revisedto":"S2-180845","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180717.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180718","title":"Plan of work for INOBEAR","source":"Samsung","contact":"Andy Bennett","contact-id":70253,"tdoctype":"discussion","for":"Information","abstract":"Outline of expected work plan for INOBEAR","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15","ainame":"WID on increasing the maximum number of LTE bearers (INOBEAR)","tdoc_agenda_sort_order":22590,"status":"noted","reservation_date":"2018-01-16 12:03:50","uploaded":"2018-01-16 12:24:11","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_125_Gothenburg\/Docs\/S2-180718.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180719","title":"23.739: Architecture Requirements, Assumptions, and Baseline","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes some text for the Architectural Requirements, Assumptions and Baseline for TR 23.739 'Study on EPC support for Mobility with Low Latency Communication'","secretary_remarks":"Revised in parallel session to S2-180846.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22990,"status":"revised","reservation_date":"2018-01-16 12:03:54","uploaded":"2018-01-16 12:34:40","revisionof":"","revisedto":"S2-180846","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180719.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180720","title":"23.501: Clarifying conditions for UE to enter CM-IDLE","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Current text describing conditions for UE to enter CM-IDLE when it is in CM-CONNECTED with RRC-Inactive state in 5.3.3.2.5 can be interpreted in two ways: - (1) If the periodic RAN Notification Area Update timer expires and UE cannot perform resume procedure due to lack of radio coverage then the UE shall enter CM-IDLE, or - (2) If the periodic RAN Notification Area Update timer expires and the RRC resume procedure fails, then UE enters CM-IDLE.  It is the understanding of the sourcing company that the correct behaviour is according to the 2nd case, i.e. RRC resume procedure fails. Lack of radio coverage might be temporary and it is possible and probable that even if there is no radio coverage when the the periodic RAN Notification Area Update timer expires, then once the radio coverage is regained, the RRC resume procedure might be successfully conducted due the the fact that RAN kept the N2 association for longer time period than the duration of the RAN Notificatio","secretary_remarks":"Revised in parallel session to S2-180875.","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16480,"status":"revised","reservation_date":"2018-01-16 12:05:26","uploaded":"2018-01-16 14:33:01","revisionof":"","revisedto":"S2-180875","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180720.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180721","title":"23.501: Clarification on UE specific DRX parameter from old AMF to new AMF","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove description 'The UE specific DRX Parameters are sent from the old AMF to the new AMF as part of the MM context information during the AMF change mobility' in clause 5.4.5.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12780,"status":"approved","reservation_date":"2018-01-16 12:05:51","uploaded":"2018-01-16 12:25:18","revisionof":"","revisedto":"S2-181496","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180721.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180722","title":"23.739: Key Issues","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes key issues for TR 23.739 'Study on EPC support for Mobility with Low Latency Communication'","secretary_remarks":"Revised in parallel session to S2-180852.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":23030,"status":"revised","reservation_date":"2018-01-16 12:06:33","uploaded":"2018-01-16 12:42:18","revisionof":"","revisedto":"S2-180852","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180722.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180723","title":"23.502: Multiple request of Location Reporting for Area of Interest","source":"Samsung Electronics Polska","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"draftCR","for":"Approval","abstract":"WITHDRAWN: AMF includes Request Reference ID in the Location Report Control message to identify the request for the area of interest.","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23920,"status":"withdrawn","reservation_date":"2018-01-16 12:10:36","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180724","title":"23.501: Management of service area restriction","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Service Area Restrictions that are sent to a UE consist of a single type of information, i.e., either Allowed Area or Non-Allowed Area.","secretary_remarks":"Revised to S2-181258.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12930,"status":"revised","reservation_date":"2018-01-16 12:10:46","uploaded":"2018-01-16 12:26:19","revisionof":"","revisedto":"S2-181258","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180724.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180725","title":"23.502: Multiple request of Location Reporting for Area of Interest","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: AMF includes Request Reference ID in the Location Report Control message to identify the request for the area of interest. The AMF may include Request Reference ID which indicates the requested Location Reporting Control for the area of interest, so that the NG-RAN should terminate location reporting for the request for a given UE.","secretary_remarks":"Revised to S2-181149.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16380,"status":"revised","reservation_date":"2018-01-16 12:12:08","uploaded":"2018-01-16 12:25:18","revisionof":"","revisedto":"S2-181149","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180725.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180726","title":"23.724: Key Issue on non3gpp access support","source":"Samsung Electronics Polska","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"pCR","for":"Approval","abstract":"WITHDRAWN: WITHDRAWN: This contribution for the FS_CIoT_5G study item proposes a key issue for non3gpp access support","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23950,"status":"withdrawn","reservation_date":"2018-01-16 12:16:37","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180727","title":"23.724: Key Issue on non3gpp access support","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"pCR","for":"Approval","abstract":"This contribution for the FS_CIoT_5G study item proposes a key issue for non3gpp access support","secretary_remarks":"Not Handled","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21170,"status":"not treated","reservation_date":"2018-01-16 12:17:15","uploaded":"2018-01-16 12:25:18","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180727.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180728","title":"23.502: UE Context Retrieval for dual registration mode","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: During the PDU session establishment procedure for mobility from EPS to 5GS, AMF retieves UE context information from UDM if it receives an unknown DNN\/APNs with 'Existing PDU Session' indication from the UE that has performed registration in 5GS with 'EPS to 5GS mobility' indication. Also, some editorail changes are proposed: . 4G-GUTI -> EPS-GUTI . a native 5G-GUTI or SUPI -> a native 5G-GUTI if available (otherwise, UE provides SUPI)","secretary_remarks":"Not Handled","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18260,"status":"not treated","reservation_date":"2018-01-16 12:18:25","uploaded":"2018-01-16 12:26:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180728.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180729","title":"LS from RAN WG3: LS on Paging in case of Enhanced Coverage Restriction","source":"RAN WG3","contact":"Hakon Helmers","contact-id":69127,"tdoctype":"LS in","for":"Action","abstract":"In the scope of SA WG2's feature 'Authorization of use of Coverage Enhancement' (TS 23.401 CR#3135r4), RAN WG3 introduced the Enhanced Coverage Restricted IE to S1AP messages for connected mode (TS 36.413 CR#1506). It is RAN WG3's understanding that if the UE is CE restricted, the eNB should not page the UE in MPDCCH. In order to convey the restriction information from the MME to the eNB during paging, it seems that SA WG2 foresaw a different approach based on presence of Information for Enhanced Coverage. However, according to RAN WG3's specification the eNB may receive two related IEs within the S1-AP PAGING message, specifically: - The UE Radio Capability for Paging IE, which is transparently relayed by the MME and may contain information on UE support of CE modes (or otherwise) - The Assistance Data for CE Capable UEs IE, which contains information on the CE level and last serving cell as reported by the previously serving eNB. RAN WG3 would like to confirm with SA WG2, if SA WG2","secretary_remarks":"Response drafted in S2-180636. Final response in S2-181236","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10160,"status":"replied to","reservation_date":"2018-01-16 12:21:05","uploaded":"2018-01-16 12:22:19","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2","lsoriginalls":"R3-175078","lsreply":"S2-181236","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180729.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180730","title":"23.502: Request Type in PDN connectivity request for SRM interworking","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change the related text: If the TAU was rejected in Step 2 the IP address preservation is not provided. In this case the UE provides IMSI in the Attach Request, and provides a Request Type 'initial request' in the PDN CONNECTIVITY Request if included in the Attach Request.","secretary_remarks":"Revised in parallel session to S2-180788.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18180,"status":"revised","reservation_date":"2018-01-16 12:24:03","uploaded":"2018-01-16 12:26:19","revisionof":"","revisedto":"S2-180788","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180730.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180731","title":"23.501: Complete of IMS Emergency support in 5G including slice and local numbers","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In case of Limited Service state, no slice info to be provided","secretary_remarks":"Revised in parallel session to S2-180893.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16990,"status":"revised","reservation_date":"2018-01-16 12:27:02","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"S2-180893","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180731.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180732","title":"23.502: Corrections to the Inter-system mobility procedures","source":"NTT DOCOMO, LG Electronics","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. In 4.11.1.3.3, the AMF takes the SMF address from UDM, not from EPS bearer context. The AMF provides the PDU Session ID (and not the EBI) to the SMF in the CreateSMContext. The SMF responds with the allocated EBI information, and AMF stores the allocated EBI(s) associated to the PDU Session ID. In 4.11.1.1 (with N26) and 4.11.2.1 (without N26) it is clarified the PGW-C+SMF registers the PDU Session ID - SMF ID association to the UDM for PDN connections established in EPC. In 5.2.8.2.2 and 5.2.8.2.5, the Allocated EBI information is added as an optional output parameter in the Create service operations.  2. In 4.11.1.2.2.2, 4.11.1.3.3 and 4.11.1.4.2 replace the UpdateSMContext with CreateSMContext. In 5.2.8.2.2 and 5.2.8.2.5, the PDU Session ID is changed as an optional input parameter in the Create service operations, and in it is changed 5.2.8.2.6 mandatory for Update operation. 3. In 4.11.1.3.3, the active flag setting is changed to the 'PDU Session(s) to be re-","secretary_remarks":"Moved to 6.5.9 Revised in parallel session to S2-180787.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17750,"status":"revised","reservation_date":"2018-01-16 12:35:20","uploaded":"2018-01-16 14:52:39","revisionof":"","revisedto":"S2-180787","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180732.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180733","title":"Finding the H-SMF address in AMF when the UE moves from EPC","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"discussion","for":"Discussion","abstract":"This paper identifies a possible issue with current interworking procedures for what concern determining the SMF address during mobility from EPC to 5GC. Current specifications assume that the SMF address (IP address or FQDN) is the same as the PGW-C address in EPC. This assumption may not hold.","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":12070,"status":"noted","reservation_date":"2018-01-16 12:40:02","uploaded":"2018-01-16 14:52:39","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_125_Gothenburg\/Docs\/S2-180733.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180734","title":"SA WG2 Work Planning Worksheet","source":"SA WG2 Chairman (Huawei)","contact":"Frank Mademann","contact-id":6821,"tdoctype":"other","for":"Information","abstract":"A revision of this document will capture agreements during work planning as SA WG2 preparations for TSG SA and\/or for future SA WG2 meetings.","secretary_remarks":"Not Handled","agenda_item_sort_order":46,"ainumber":"7.2","ainame":"Review of the Work Plan","tdoc_agenda_sort_order":23330,"status":"not treated","reservation_date":"2018-01-16 12:43:02","uploaded":"2018-01-16 13:10:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180734.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180735","title":"23.501: Correction in clause 5.15.5.3 Establishing a PDU Session in a Network Slice","source":"ETRI","contact":"Jeong Yun Kim","contact-id":34277,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution proposes to replace 'Subscribed S-NSSAI' to 'S-NSSAI of the Configured NSSAI' in clause 5.15.5.3.","secretary_remarks":"Consider merging with S2-180664. Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12170,"status":"not treated","reservation_date":"2018-01-16 12:43:58","uploaded":"2018-01-16 12:47:42","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180735.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180736","title":"23.501: References to access stratum procedures for EPS-5GS interworking","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Added references to RAN specifications.  NOTE: some of the listed references currently do not include full list of access stratum mechanisms, whereas others have not yet been updated by the RAN groups.","secretary_remarks":"Not Handled","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17490,"status":"not treated","reservation_date":"2018-01-16 12:47:37","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180736.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180737","title":"23.501: Update of Mobility Restrictions","source":"Lenovo, Motorola Mobility","contact":"Zhuoyun Zhang","contact-id":67292,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarification of Service area restrictions in clause 5.3.4.1.1. 2. Changing 'Paging Area Update' to 'RAN Notification Area Update' in clause 5.4.2.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16400,"status":"approved","reservation_date":"2018-01-16 12:48:14","uploaded":"2018-01-16 13:06:25","revisionof":"","revisedto":"S2-182221","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180737.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180738","title":"Rel-16 timeline and work","source":"SA WG2 Chairman (Huawei)","contact":"Frank Mademann","contact-id":6821,"tdoctype":"other","for":"Information","abstract":"Provides some considerations on how the ongoing work fits into the R16 timeline and that some actions may be needed with regard to available meeting resources. Proposal: - Continue in Feb with 1 TU per ongoing SI\/WI and high TU allocation for maintenance - Monitor in Jan and Feb how the R15 maintenance effort develops - Consider during Feb work planning how much resources can ramp up in Q2 for ongoing SI\/WI - Evaluate plausibility of the resources requested per SI\/WI - Consider stretching the timeline for SI\/WI - If not sufficient, possibly some prioritization exercise in Feb.","secretary_remarks":"It was agreed that the agenda for meeting #126 will be similar to the agenda for this meeting. Noted","agenda_item_sort_order":46,"ainumber":"7.2","ainame":"Review of the Work Plan","tdoc_agenda_sort_order":23340,"status":"noted","reservation_date":"2018-01-16 12:48:36","uploaded":"2018-01-16 13:31:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180738.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180739","title":"[draft] Reply LS to GSMA NG SIGNAL on Interworking between networks with different 5G deployments","source":"Vodafone","contact":"Susana Sabater","contact-id":31269,"tdoctype":"LS out","for":"Decision","abstract":"To: GSMA NG SIGNAL","secretary_remarks":"Response to S2-180019 Revised in parallel session to S2-180774.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17380,"status":"revised","reservation_date":"2018-01-16 12:48:53","uploaded":"2018-01-16 14:14:41","revisionof":"","revisedto":"S2-180774","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG SIGNAL","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180739.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180740","title":"Discussing the interworking of core networks in roaming scenarios","source":"Vodafone","contact":"Susana Sabater","contact-id":31269,"tdoctype":"discussion","for":"Discussion","abstract":"Discussing the interworking of core networks in roaming scenarios","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17370,"status":"noted","reservation_date":"2018-01-16 12:51:44","uploaded":"2018-01-16 14:14:40","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_125_Gothenburg\/Docs\/S2-180740.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180741","title":"Clarification on additional IP address","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removes the example with deprecated I-WLAN.  Clarifies that in this release the additional IP address that can be used as contact address in additional IMS registration can only come from another system (i.e. outside of EPS in Annex E; outside of 5GS in Annex Y).","secretary_remarks":"Revised in parallel session to S2-180932.","agenda_item_sort_order":11,"ainumber":"5.4","ainame":"IMS and IMS-Related Maintenance","tdoc_agenda_sort_order":10840,"status":"revised","reservation_date":"2018-01-16 12:55:26","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"S2-180932","release":"Rel-15","crspec":23.228,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI15"}],"crnumber":1187.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180741.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180742","title":"23.716: Modifying the Key Issue #7 Policy","source":"China Mobile","contact":"Wei Chen","contact-id":57801,"tdoctype":"pCR","for":"Approval","abstract":"This proposal aims to modify the key issue #7 policy to study the feasibility for PCF to support the policy of wireline network.","secretary_remarks":"Revised, merging S2-180574, to S2-181178.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20080,"status":"revised","reservation_date":"2018-01-16 12:56:21","uploaded":"2018-01-16 14:30:52","revisionof":"","revisedto":"S2-181178","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180742.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180743","title":"23.501: Draft CR 23.501 Correction to handling of S-NSSAI mapping information","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Storage \/ deletion of S-NSSAI mapping information is completed - Any stored mapping information is deleted - Mapping information is stored - Mapping information is stored when the UE is turned off","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11760,"status":"approved","reservation_date":"2018-01-16 12:56:58","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180743.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180744","title":"23.502: Update of Reachability procedures","source":"Lenovo, Motorola Mobility","contact":"Zhuoyun Zhang","contact-id":67292,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Adding step 2b in Figure 4.2.5.2-1. 2. Clarify step 4 in Figure 4.2.5.2-1. 3. Adding description of step 2b in clause 4.2.5.3.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12950,"status":"endorsed","reservation_date":"2018-01-16 12:58:15","uploaded":"2018-01-16 13:06:25","revisionof":"","revisedto":"S2-182229","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180744.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180745","title":"Clarification on notify message in the mobility procedure from EPS to 5GS without N26 interface","source":"ORANGE","contact":"Thouraya Toukabri","contact-id":66374,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Additing that Notify message MME > HSS to update the PGW-C+SMF shall be sent when when the subscription data indicates that the user is allowed use 5G as a RAT type in order to handle EPS to 5GS handover.","secretary_remarks":"Not Handled","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18140,"status":"not treated","reservation_date":"2018-01-16 13:18:55","uploaded":"2018-01-16 14:23:21","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3393.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180745.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180746","title":"T-ADS with dual registered UE, discussion","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"discussion","for":"Discussion","abstract":"In SA WG2#124 it was recognized that there are issues with handling T-ADS query for dual registered UE. In general the issue is to keep IMS updated on access change when the UE is dual registered. This paper compares a CN-based solution and a UE-based solution and concludes that CN based solution is preferable.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17100,"status":"noted","reservation_date":"2018-01-16 13:19:04","uploaded":"2018-01-16 14:52:39","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_125_Gothenburg\/Docs\/S2-180746.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180747","title":"23.501: T-ADS with dual registered UE","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. In clause 5.16.3.6, include text to describe the proposed CN-based solution: - Solution proposed for issue 1: after receiving a T-ADS query from IMS, UDM\/HSS queries the PGW-C\/SMF to determine on which system (EPS or 5GS) the IMS PDU session is located (a PDU session to DNN = 'IMS'); after that, UDM\/HSS sends the T-ADS query only to the system where the IMS session is located. E.g. only the MME is queried if the IMS session is in EPS. UDM\/HSS makes the query for each SMF ID that is registered for an IMS DNN in the subscription profile in HSS. - Solution proposed for issue 2: IMS includes the UE's IP address of the relevant IMS session in the T-ADS query to UDM\/HSS. UDM\/HSS provides the IP address to PGW-C\/SMF in the query for the location of IMS session (see solution to issue 1). PGW-C\/SMF compares the IP address with the IP addresses bound to the IMS sessions this PGW-C\/SMF is responsible for, and if there is a match, it returns to UDM\/HSS the current system for","secretary_remarks":"Not Handled","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17110,"status":"not treated","reservation_date":"2018-01-16 13:25:08","uploaded":"2018-01-16 14:52:39","revisionof":"","revisedto":"S2-181936","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180747.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180748","title":"23.794: New Key Issue: IMS enhancements for 5GC network slicing","source":"Nokia, Nokia Shanghai Bell","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a key issue related to IMS enhancements for 5GC network slicing","secretary_remarks":"Merged into S2-180936","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22370,"status":"merged","reservation_date":"2018-01-16 13:25:38","uploaded":"2018-01-16 14:48:06","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180748.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180749","title":"System level solution aspects for Ultra Reliability","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"discussion","for":"Approval","abstract":"The aim of this document is to address 2 issues: 1) Highlight the need for system-wide consideration when developing the needed specifications for URLLC in 3GPP. 2) To show a possible way forward for 3GPP to solve Ultra Reliability.","secretary_remarks":"Noted","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23140,"status":"noted","reservation_date":"2018-01-16 13:43:45","uploaded":"2018-01-16 13:54:56","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_125_Gothenburg\/Docs\/S2-180749.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180750","title":"23.501: 5G-GUTI, 5G-S-TMSI definition and mapping rules","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Based on considerations in S2-1780523, we propose the following mapping rules: 1) MMEGI = AMF Region ID (no change here) 2) MMEC = AMF SET ID 3) M-TMSI = AMF Pointer + 5G-M-TMSI Furthermore, it has been agreed that S-TMSI is unique across AMF Sets thus the AMF pointer value can be stated as optional and this can help avoid GUTI reallocations by AMF.","secretary_remarks":"Revised to S2-181187.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12340,"status":"revised","reservation_date":"2018-01-16 13:55:54","uploaded":"2018-01-16 14:57:01","revisionof":"","revisedto":"S2-181187","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180750.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180751","title":"23.502: LADN service area and SMF","source":"NEC","contact":"Taka Yoshizawa","contact-id":40702,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to update TS 23.502 clause 4.3.2.2: 'UE Requested PDU Session Establishment' step 3 'From AMF to SMF' to include this indication (named as 'LADN_Status) to indicate current relationship between UE location and a LADN service area (i.e. IN, OUT, UNKNOWN). Additionally, based on step 3, it updates step 4 to allow SMF check the validity of the UE request: it checks: (If the DNN corresponds to an LADN), whether the UE is located IN, OUT, UNKNOWN to the LADN service area based on, LADN_Status and the UE location reporting from the AMF.","secretary_remarks":"Merged into S2-181114.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13290,"status":"merged","reservation_date":"2018-01-16 13:57:13","uploaded":"2018-01-16 14:41:08","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180751.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180752","title":"EPC support for Mobility with Low Latency Communication","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"WID new","for":"Information","abstract":"Unmodified SA WG2 agreed WID as in S2-175934. Submitted for information, e.g. to aid discussion of draft Scope statement of the TR","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22890,"status":"noted","reservation_date":"2018-01-16 13:59:32","uploaded":"2018-01-16 14:00:52","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_125_Gothenburg\/Docs\/S2-180752.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180753","title":"Handling of Allowed NSSAI for more than one Access Type","source":"InterDigital Communications","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"discussion","for":"Approval","abstract":"Discussion on Allowed NSSAI when UE is using more than one Access Type","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11620,"status":"not treated","reservation_date":"2018-01-16 14:10:52","uploaded":"2018-01-16 14:53:23","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_125_Gothenburg\/Docs\/S2-180753.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180754","title":"23.501: Handling of Allowed NSSAI for more than one Access Type","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: When a UE registers to both 3GPP and N3GPP, the relevant associated Access Type per S-NSSAI is communicated to the UE when the AMF provides the Allowed NSSAI","secretary_remarks":"Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11640,"status":"not treated","reservation_date":"2018-01-16 14:12:25","uploaded":"2018-01-16 14:53:23","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180754.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180755","title":"23.502: Correction of UDR usage in specific Service related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that UDM\/PCF may invoke UDR services in specific services are corrected.","secretary_remarks":"Revised in parallel session to S2-180869.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17260,"status":"revised","reservation_date":"2018-01-16 14:25:21","uploaded":"2018-01-16 14:55:18","revisionof":"","revisedto":"S2-180869","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180755.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180756","title":"23.501: Aligning clause 4.3.2.2.3.1 with TS 23.501 with regards to the absence concept of 5GC not supporting slicing","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Removal of text suggesting that network slicing is optional and simplification of the conditions around that. 2) Clarification that the decision to use one option of the other in 4.3.2.2.3.3 is based on SLA only, not on what the networks have deployed.","secretary_remarks":"Merged into S2-181120","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12190,"status":"merged","reservation_date":"2018-01-16 14:26:37","uploaded":"2018-01-16 14:55:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180756.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180757","title":"23.502: Correction of UDR usage in policy related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that PCF invoke UDR services are clarified in policy related procedures.","secretary_remarks":"Revised in parallel session to S2-181009.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15950,"status":"revised","reservation_date":"2018-01-16 14:28:10","uploaded":"2018-01-16 15:29:38","revisionof":"","revisedto":"S2-181009","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180757.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180758","title":"23.726: KI-Study UPF capabilities to be controlled by multiple UPFs","source":"Samsung","contact":"Jayshree Bharatia","contact-id":63826,"tdoctype":"pCR","for":"Approval","abstract":"Suggests inclusion of KI which is related to the UPF controlled by multiple SMFs.","secretary_remarks":"Revised in parallel session to S2-180957.","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21760,"status":"revised","reservation_date":"2018-01-16 14:29:12","uploaded":"2018-01-16 14:34:11","revisionof":"","revisedto":"S2-180957","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180758.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180759","title":"23.715: Solution for initial RLOS access","source":"Motorola Mobility, Lenovo","contact":"Genadi Velev","contact-id":70944,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a solution for initial RLOS access targeting to resolve Key Issues EPC-1 and EPC-2.","secretary_remarks":"Not Handled","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22760,"status":"not treated","reservation_date":"2018-01-16 14:30:23","uploaded":"2018-01-16 14:45:40","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180759.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180760","title":"Discussion on Access and Congestion Control","source":"KPN N.V.","contact":"Toni Dimitrovski","contact-id":66437,"tdoctype":"discussion","for":"Discussion","abstract":"Access and Congestion Control","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12230,"status":"noted","reservation_date":"2018-01-16 14:33:49","uploaded":"2018-01-16 14:35:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180760.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180761","title":"23.794: High-level solution proposals for routing of IMS traffic via a localised UPF","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"pCR","for":"Approval","abstract":"Proposes high-level solution proposals for routing of IMS traffic via a localized UPF.","secretary_remarks":"Not Handled","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22510,"status":"not treated","reservation_date":"2018-01-16 14:37:03","uploaded":"2018-01-16 14:58:47","revisionof":"","revisedto":"S2-181609","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180761.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180762","title":"23.502: QoS clarifications for EPC interworking","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the UE and the network need to store the association between the PDU Session ID and the default EBI, and the association between the QoS flow and the mapped EPS QoS parameters, and association between EBI and the 5G QoS Rules.","secretary_remarks":"Revised in parallel session to S2-180778.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17610,"status":"revised","reservation_date":"2018-01-16 14:43:27","uploaded":"2018-01-16 14:52:39","revisionof":"","revisedto":"S2-180778","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180762.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180763","title":"23.501: EPS Interworking: 5G-S-TMSI derivation and context retrieval","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: If the UE has 5G-GUTI, it must derive S-TMSI from 5G-GUTI. Also, AMF can retrieve security context from another AMF (reducing the need to perform re-authentication), enabling security separation (as agreed in the last meeting).","secretary_remarks":"Revised in parallel session, merging S2-180540, to S2-180777.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17560,"status":"revised","reservation_date":"2018-01-16 14:50:29","uploaded":"2018-01-16 14:57:02","revisionof":"","revisedto":"S2-180777","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180763.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180764","title":"23.501: Additional text in 5.6.7","source":"NEC","contact":"Taka Yoshizawa","contact-id":40702,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adds text in Sec. 5.6.7 to clarify that AF is able to register and receive policies for traffic treatment and gets notified about any updated policies through previous subscription.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13510,"status":"noted","reservation_date":"2018-01-16 14:54:00","uploaded":"2018-01-16 14:58:18","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180764.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180765","title":"23.793: UE Requested Multi-access PDU Session Establishment","source":"ETRI","contact":"Yooah Kang","contact-id":63871,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes UE requested Multi-access PDU session Establishment procedure.","secretary_remarks":"LATE DOC: Rx 16\/01, 16:50. Not Handled","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20560,"status":"not treated","reservation_date":"2018-01-16 14:54:45","uploaded":"2018-01-16 15:51:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180765.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180766","title":"23.501: Clarification of signalling with higher priority","source":"KPN","contact":"Toni Dimitrovski","contact-id":66437,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify UEs behaviour related to initiating higher priority signalling.","secretary_remarks":"Revised to S2-181185.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12240,"status":"revised","reservation_date":"2018-01-16 14:56:19","uploaded":"2018-01-16 14:59:55","revisionof":"","revisedto":"S2-181185","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180766.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180767","title":"23.502: Correction for UE location in Xn based HO procedure","source":"Samsung","contact":"Jayshree Bharatia","contact-id":63826,"tdoctype":"draftCR","for":"Approval","abstract":"This contribution provides correction in Xn based handover procedure pertaining to UE location mentioned in step 2.","secretary_remarks":"Should be a DRAFTCR Revised to S2-181139.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16030,"status":"revised","reservation_date":"2018-01-16 14:57:40","uploaded":"2018-01-16 15:00:19","revisionof":"","revisedto":"S2-181139","release":"Rel-15","crspec":23.502,"crspecversion":"2.0.0","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_125_Gothenburg\/Docs\/S2-180767.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180768","title":"Enhancements to Service Based Architecture","source":"Deutsche Telekom, China Mobile, AT&T, NTT Docomo, Sprint, Vodafone","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"discussion","for":"Discussion","abstract":"Objective: The scope of this study is to study potential enhancement to the Release 15 Service-Based Architecture in order to provide higher flexibility and better modularization of the 5G System for the easier definition of different network slices and enable better re-use of the defined services.  The potential enhancements to be studied are:  1) Make services fully self-contained if they are not already,  - study stateless service operation to avoid long-living UE-specific bindings between service instances - to achieve independent lifecycle management - to allow multi-vendor service interoperability,  - to enhance flexibility for e.g. network slicing, Time-to-market, operational efficiency - to achieve higher granular independent services and better re-usability 3) Feasibility study of extend the service concept from 5GC control plane to user plane functions.  4) Study the support of a communication enablement platform that can enhance e.g.  - message routing & forwarding  - servic","secretary_remarks":"Revised to S2-181117.","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23180,"status":"revised","reservation_date":"2018-01-16 14:58:59","uploaded":"2018-01-16 15:03:25","revisionof":"","revisedto":"S2-181117","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_125_Gothenburg\/Docs\/S2-180768.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180769","title":"Draft Report of SA WG2 meeting #124","source":"SA WG2 Secretary","contact":"Maurice Pope","contact-id":648,"tdoctype":"report","for":"Approval","abstract":"Draft Report of meeting #124 for approval","secretary_remarks":"Revision of S2-180002. LATE DOC: Rx 17\/01, 11:53. Approved","agenda_item_sort_order":4,"ainumber":"3","ainame":"Meeting reports","tdoc_agenda_sort_order":10020,"status":"approved","reservation_date":"2018-01-17 10:47:13","uploaded":"2018-01-17 10:52:38","revisionof":"S2-180002","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180769.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180770","title":"23.501: Default QoS Rule cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: A note that UE does not need to know which QoS rule is","secretary_remarks":"LATE DOC: Rx 19\/01, 22:30 Revised to S2-181153.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14250,"status":"revised","reservation_date":"2018-01-17 13:42:29","uploaded":"2018-01-20 06:52:09","revisionof":"","revisedto":"S2-181153","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180770.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180771","title":"23.502: Default QoS Rule cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introducing sending an indication which EBI refer to the default EPS bearer","secretary_remarks":"LATE DOC: Rx 19\/01, 22:30 Revised to S2-181154.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14270,"status":"revised","reservation_date":"2018-01-17 13:42:29","uploaded":"2018-01-20 06:52:09","revisionof":"","revisedto":"S2-181154","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180771.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180772","title":"LS from BBF: 5G-FMC - First release of BBF study results","source":"BBF","contact":"Michael Fargano","contact-id":57382,"tdoctype":"LS in","for":"Action","abstract":"Dear colleagues, BBF has progressed its study of converged wireline-wireless networks that use the 5G Core Network (5GC). BBF SD-420, attached to this liaison, contains a first set of results from the BBF study (an extract of SD-406 and SD-407 which may impact 3GPP), including principle\/architectural design guidelines, key issues, preliminary gap analysis for architectural models identified regarding identifiers, functions and procedures concerning the 5G AN-CN interfaces N1, N2, N3 and N4. We are interested in your feedback as we develop resolution of the issues identified. According to the understanding of the joint 3GPP-BBF Workshop in February 2017 and in line with our ongoing cooperation on 5G-FMC, we are sharing these outcomes to facilitate 5G system architectural and functional integration. We recommend that 3GPP considers these results in related studies and specification work. Where the outcomes of the BBF study identify aspects of concern to the BBF, including the fixed broad","secretary_remarks":"Response drafted in S2-180579. Postponed in parallel session. Revised at S2#126 in S2-181429.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19860,"status":"revised","reservation_date":"2018-01-18 09:10:46","uploaded":"2018-01-18 09:11:14","revisionof":"","revisedto":"S2-181429","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"SA WG5","lsoriginalls":"BBF LIAISE-120","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180772.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180773","title":"LS from GSMA PACKET: LS on the definition of the Mx functionality in support of the S8HR architecture","source":"GSMA PACKET","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"GSMA NG PACKET thanks SA WG2 and CT WG1 for their LS replies on using the Mx reference point for SRVCC in S8HR architecture. Following the discussion on this option, GSMA NG PACKET has identified the need for defining SRVCC for S8HR (MSC server enhanced and ATCF) based on the Mx reference point. Action: GSMA PACKET kindly requests SA WG2 to specify stage 2 details for SRVCC using the Mx reference point in support of the S8HR architecture (MSC server enhanced and ATCF) and CT WG1 to define the stage 3 details in the relevant specifications.","secretary_remarks":"This LS was postponed. Revised at S2#126 in S2-181430.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"revised","reservation_date":"2018-01-19 11:26:56","uploaded":"2018-01-19 11:27:22","revisionof":"","revisedto":"S2-181430","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"-","lsoriginalls":"PACKET_96_113","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180773.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180774","title":"[draft] Reply LS to GSMA NG SIGNAL on Interworking between networks with different 5G deployments","source":"SA WG2","contact":"Susana Sabater","contact-id":31269,"tdoctype":"LS out","for":"Decision","abstract":"To: GSMA NG SIGNAL","secretary_remarks":"Revision of S2-180739. Revised in parallel session to S2-180798.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17390,"status":"revised","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180739","revisedto":"S2-180798","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG SIGNAL","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180774.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180775","title":"23.501: EPC to 5GC Migration fixes for Option 7","source":"Nokia, Nokia Shanghai Bell, AT&T","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Propose to reflect the necessary requirement for CN selection in case of Option 7 architecture: UE AS layer should indicate to the RAN whether it is requesting EPS access or 5GS access","secretary_remarks":"Revision of S2-180468, merging S2-180491. Revised in parallel session to S2-180797.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17440,"status":"revised","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180468","revisedto":"S2-180797","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180775.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180776","title":"23.502: Clarifying inclusion of TAU messages in Registration Request","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies that TAU message is only included in Registration Request in case of idle mode mobility. Also reorganizes the text to clearly separate idle mode related aspects from aspects of the registration request that apply to both idle and connected mode.","secretary_remarks":"Revision of S2-180065. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17550,"status":"approved","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180065","revisedto":"S2-181642","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180776.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180777","title":"23.501: EPS Interworking: 5G-S-TMSI derivation and context retrieval","source":"Nokia, Nokia Shanghai Bell, LG Electronics","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: If the UE has 5G-GUTI, it must derive S-TMSI from 5G-GUTI. Also, AMF can retrieve security context from another AMF (reducing the need to perform re-authentication), enabling security separation (as agreed in the last meeting).","secretary_remarks":"Revision of S2-180763, merging S2-180540. Revised in parallel session to S2-180799.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17570,"status":"revised","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180763","revisedto":"S2-180799","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180777.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180778","title":"23.502: QoS clarifications for EPC interworking","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the UE and the network need to store the association between the PDU Session ID and the default EBI, and the association between the QoS flow and the mapped EPS QoS parameters, and association between EBI and the 5G QoS Rules.","secretary_remarks":"Revision of S2-180762. Revised in parallel session to S2-180800.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17620,"status":"revised","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180762","revisedto":"S2-180800","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180778.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180779","title":"23.502: Clarifications on EPS to 5GS handover procedure using N26","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The two ENs are to be removed","secretary_remarks":"Revision of S2-180306. Revised in parallel session to S2-180801.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17650,"status":"revised","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180306","revisedto":"S2-180801","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180779.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180780","title":"23.502: Keeping EBI transfer alignment","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding allocated EBI information to UE context in the Namf_Communication_UEContextTransfer service operation. Update the Nsmf_PDUSession_Update SM Context service operation description","secretary_remarks":"Revision of S2-180559. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17690,"status":"approved","reservation_date":"2018-01-24 06:42:25","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180559","revisedto":"S2-181537","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180780.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180781","title":"23.502: EPS bearer ID allocation update","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: If a SMF received a failure notification for EBI assignment request, the SMF can subscribe for EBI allocation availability notification, e.g. whenever any EBI mapped flow of a PDU session has been release for a UE. New service operations for EBI availability subscription, notification, unsubsription are added.  'S-NSSAI' and 'Released EBI list' are added as input parameters for Namf_Communication_EBIAssignment service operation (5.2.2.2.13). The S-NSSAI is described in the procedure in 4.11.1.4.1 but is missing from the service definition. The Released EBI list is explained in the service description but is missing from the service definition. The ARP list is changed to be mandatory input parameter for Namf_Communication_EBIAssignment Request, the parameter is needed to indicate the amount of requested EBIs. The corresponding EN is removed.  A new clause 4.11.1.4.x is added to describe a procedure for EPS bearer ID revokation when the EBI needs to be released e.g. wh","secretary_remarks":"Revision of S2-180708. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17850,"status":"approved","reservation_date":"2018-01-24 06:42:25","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180708","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180781.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180782","title":"23.502: Clean up FFSs in 4.11.1.2.2","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1 SSC mode is sent to UE during the PDN Connection Establishment procedure. 2 change the 5G security context mapping from an EN to a Note. 3 add description between SMF and UPF","secretary_remarks":"Revision of S2-180613. Revised in parallel session to S2-180812.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17710,"status":"revised","reservation_date":"2018-01-24 06:42:25","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180613","revisedto":"S2-180812","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180782.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180783","title":"23.502: Interaction between SMF and UPF during the inter-system change","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarifying that the PGW-C+SMF sends both of Sx and N4 session management messages to the UPF+PGW-U. 2 removing the related FFS.","secretary_remarks":"Revision of S2-180653. Revised in parallel session to S2-180806.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17900,"status":"revised","reservation_date":"2018-01-24 06:42:25","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180653","revisedto":"S2-180806","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180783.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180784","title":"23.502: Indirect data forwarding in home routed roaming case","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarifying that, in home routed roaming case, the V-SMF is responsible for handling indirect data forwarding during the handover procedure from 5GS to EPS. 2 Similar clarfication for the handover procedure from EPS to 5GS. 3. Removing the FFS on the indirect data forwarding in home routed roaming.","secretary_remarks":"Revision of S2-180652. Revised in parallel session to S2-180805.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17870,"status":"revised","reservation_date":"2018-01-24 06:42:25","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180652","revisedto":"S2-180805","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180784.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180785","title":"23.502: MME and AMF registration in HSS+UDM","source":"Cisco","contact":"Irfan Ali","contact-id":74090,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: For no-N26 procedures, the MME and AMF explicitly includes 'Dual MME\/AMF registration indicator' to the HSS+UDM.  If HSS does not support dual MME\/AMF registration it does not indicate support of this in the ULA 'supported features' AVP. If this indication is not present the MME or AMF knows that dual-registration is not allowed and should not provide the 'no-N26 support' indication to the UE.","secretary_remarks":"Revision of S2-180119, merging S2-180094. Revised in parallel session to S2-180804.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17970,"status":"revised","reservation_date":"2018-01-24 06:42:25","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180119","revisedto":"S2-180804","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180785.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180786","title":"23.501: Clarification on SMF selection for interworking","source":"LG Electronics, Intel","contact":"Jinsook Ryu","contact-id":39022,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is clarified that AMF shall select same SMF for multiple PDU sessios to support interworking with EPS.","secretary_remarks":"Revision of S2-180403. Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18050,"status":"noted","reservation_date":"2018-01-24 06:42:25","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180403","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180786.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180787","title":"23.502: Corrections to the Inter-system mobility procedures","source":"NTT DOCOMO, LG Electronics","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. In 4.11.1.3.3, the AMF takes the SMF address from UDM, not from EPS bearer context. The AMF provides the PDU Session ID (and not the EBI) to the SMF in the CreateSMContext. The SMF responds with the allocated EBI information, and AMF stores the allocated EBI(s) associated to the PDU Session ID. In 4.11.1.1 (with N26) and 4.11.2.1 (without N26) it is clarified the PGW-C+SMF registers the PDU Session ID - SMF ID association to the UDM for PDN connections established in EPC. In 5.2.8.2.2 and 5.2.8.2.5, the Allocated EBI information is added as an optional output parameter in the Create service operations.  2. In 4.11.1.2.2.2, 4.11.1.3.3 and 4.11.1.4.2 replace the UpdateSMContext with CreateSMContext. In 5.2.8.2.2 and 5.2.8.2.5, the PDU Session ID is changed as an optional input parameter in the Create service operations, and in it is changed 5.2.8.2.6 mandatory for Update operation. 3. In 4.11.1.3.3, the active flag setting is changed to the 'PDU Session(s) to be re-","secretary_remarks":"Revision of S2-180732. Revised in parallel session to S2-180795.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17760,"status":"revised","reservation_date":"2018-01-25 14:56:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180732","revisedto":"S2-180795","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180787.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180788","title":"23.502: Request Type in PDN connectivity request for SRM interworking","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change the related text: If the TAU was rejected in Step 2 the IP address preservation is not provided. In this case the UE provides IMSI in the Attach Request, and provides a Request Type 'initial request' in the PDN CONNECTIVITY Request if included in the Attach Request.","secretary_remarks":"Revision of S2-180730. Revised in parallel session to S2-180809.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18190,"status":"revised","reservation_date":"2018-01-25 14:56:04","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180730","revisedto":"S2-180809","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180788.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180789","title":"[DRAFT] LS on CN selection using RRC redirection","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2","secretary_remarks":"Created in parallel session. Noted in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17350,"status":"noted","reservation_date":"2018-01-25 14:56:04","uploaded":"2018-01-26 18:07:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180789.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180790","title":"23.501 Clarification of interworking procedures without N26 interface","source":"Secretary of SA WG2","contact":"Thouraya Toukabri","contact-id":66374,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: clarifications on the principles of interworking without N26 and the way they are fulfilled","secretary_remarks":"Revision of S2-180164. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18280,"status":"approved","reservation_date":"2018-01-25 14:56:04","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180164","revisedto":"S2-182260, S2-182281","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180790.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180791","title":"23.501: Clean up on the interworking without 26 indication","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clean up, replace dual registration mode indication with interworking without N26 indication","secretary_remarks":"Revision of S2-180558, merging S2-180704 and S2-180399. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18310,"status":"approved","reservation_date":"2018-01-25 14:56:04","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180558","revisedto":"S2-181538","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180791.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180792","title":"23.502 Clarification of mobility procedure from EPS to 5GS without N26 interface","source":"Orange","contact":"Thouraya Toukabri","contact-id":66374,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: addition that Notify message MME > HSS shall be sent when when the subscription data indicates that the user is allowed use 5G as a RAT type in order to handle EPS to 5GS handover.","secretary_remarks":"Revision of S2-180163. Revised in parallel session to S2-180808.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18110,"status":"revised","reservation_date":"2018-01-25 14:56:04","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180163","revisedto":"S2-180808","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180792.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180793","title":"23.501: Clarification on the use of indicators for the support of interworking without N26 and interworking with N26","source":"Orange","contact":"Thouraya Toukabri","contact-id":66374,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Indication that interworking with N26 is supported is sent to the device Conditions for the UE to be in dual registration are clarified","secretary_remarks":"Revision of S2-180165. Revised in parallel session to S2-180814.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18160,"status":"revised","reservation_date":"2018-01-25 14:56:04","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180165","revisedto":"S2-180814, S2-182263","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180793.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180794","title":"23.502: Update Handover procedures in clause 4.11.1.2","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Correction on the procedure of 5GS to EPS handover using N26 interface in which the AMF sends the Handover Command to the source NG-RAN including (Transparent container (radio aspect parameters that the target eNB has set-up in the preparation phase), CN tunnel info for data forwarding per PDU Session, QoS flows for Data Forwarding). 2. Correction on the procedure of EPS to 5GS handover using N26 interface in which SMF+PGW-C initiates an N4 Session Modification procedure before SMF+PGW-C responses to AMF.","secretary_remarks":"Revision of S2-180678. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17740,"status":"approved","reservation_date":"2018-01-25 14:56:04","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180678","revisedto":"S2-181592","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180794.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180795","title":"23.502: Corrections to the Inter-system mobility procedures","source":"NTT DOCOMO, LG Electronics","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. In 4.11.1.3.3, the AMF takes the SMF address from UDM, not from EPS bearer context. The AMF provides the PDU Session ID (and not the EBI) to the SMF in the CreateSMContext. The SMF responds with the allocated EBI information, and AMF stores the allocated EBI(s) associated to the PDU Session ID. In 4.11.1.1 (with N26) and 4.11.2.1 (without N26) it is clarified the PGW-C+SMF registers the PDU Session ID - SMF ID association to the UDM for PDN connections established in EPC. In 5.2.8.2.2 and 5.2.8.2.5, the Allocated EBI information is added as an optional output parameter in the Create service operations.  2. In 4.11.1.2.2.2, 4.11.1.3.3 and 4.11.1.4.2 replace the UpdateSMContext with CreateSMContext. In 5.2.8.2.2 and 5.2.8.2.5, the PDU Session ID is changed as an optional input parameter in the Create service operations, and in it is changed 5.2.8.2.6 mandatory for Update operation. 3. In 4.11.1.3.3, the active flag setting is changed to the 'PDU Session(s) to be re-","secretary_remarks":"Revision of S2-180787. interworking related aspects postponed Revised in parallel session to S2-180802.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17770,"status":"revised","reservation_date":"2018-01-25 14:56:19","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180787","revisedto":"S2-180802","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180795.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180796","title":"23.501: Generating EPS PDN Connection parameters from 5G PDU Session parameters","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Proposes a new annex about how to generate the EPS PDN connection parameters from the 5G PDU Session parameters in PGW-C+SMF.","secretary_remarks":"Revision of S2-180125. Revised in parallel session to S2-180807.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17940,"status":"revised","reservation_date":"2018-01-25 14:56:19","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180125","revisedto":"S2-180807","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180796.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180797","title":"23.501: EPC to 5GC Migration fixes for Option 7","source":"Nokia, Nokia Shanghai Bell, AT&T","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Propose to reflect the necessary requirement for CN selection in case of Option 7 architecture: UE AS layer should indicate to the RAN whether it is requesting EPS access or 5GS access","secretary_remarks":"Revision of S2-180775. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17450,"status":"approved","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180775","revisedto":"S2-181754","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180797.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180798","title":"[draft] Reply LS to GSMA NG SIGNAL on Interworking between networks with different 5G deployments","source":"SA WG2","contact":"Susana Sabater","contact-id":31269,"tdoctype":"LS out","for":"Decision","abstract":"To: GSMA NG SIGNAL","secretary_remarks":"Revision of S2-180774. Revised in parallel session to S2-180810.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17400,"status":"revised","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180774","revisedto":"S2-180810","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG SIGNAL","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180798.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180799","title":"23.501: EPS Interworking: 5G-S-TMSI derivation and context retrieval","source":"Nokia, Nokia Shanghai Bell, LG Electronics","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: If the UE has 5G-GUTI, it must derive S-TMSI from 5G-GUTI. Also, AMF can retrieve security context from another AMF (reducing the need to perform re-authentication), enabling security separation (as agreed in the last meeting).","secretary_remarks":"Revision of S2-180777. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17580,"status":"approved","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180777","revisedto":"S2-181755","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180799.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180800","title":"23.502: QoS clarifications for EPC interworking","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the UE and the network need to store the association between the PDU Session ID and the default EBI, and the association between the QoS flow and the mapped EPS QoS parameters, and association between EBI and the 5G QoS Rules.","secretary_remarks":"Revision of S2-180778. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17630,"status":"approved","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180778","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180800.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180801","title":"23.502: Clarifications on EPS to 5GS handover procedure using N26","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The two ENs are to be removed","secretary_remarks":"Revision of S2-180779. Revised in parallel session to S2-180811.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17660,"status":"revised","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180779","revisedto":"S2-180811","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180801.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180802","title":"23.502: Corrections to the Inter-system mobility procedures","source":"NTT DOCOMO, LG Electronics","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. In 4.11.1.3.3, the AMF takes the SMF address from UDM, not from EPS bearer context. The AMF provides the PDU Session ID (and not the EBI) to the SMF in the CreateSMContext. The SMF responds with the allocated EBI information, and AMF stores the allocated EBI(s) associated to the PDU Session ID. In 4.11.1.1 (with N26) and 4.11.2.1 (without N26) it is clarified the PGW-C+SMF registers the PDU Session ID - SMF ID association to the UDM for PDN connections established in EPC. In 5.2.8.2.2 and 5.2.8.2.5, the Allocated EBI information is added as an optional output parameter in the Create service operations.  2. In 4.11.1.2.2.2, 4.11.1.3.3 and 4.11.1.4.2 replace the UpdateSMContext with CreateSMContext. In 5.2.8.2.2 and 5.2.8.2.5, the PDU Session ID is changed as an optional input parameter in the Create service operations, and in it is changed 5.2.8.2.6 mandatory for Update operation. 3. In 4.11.1.3.3, the active flag setting is changed to the 'PDU Session(s) to be re-","secretary_remarks":"Revision of S2-180795. Revised in parallel session to S2-180813.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17780,"status":"revised","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180795","revisedto":"S2-180813","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180802.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180803","title":"Capturing EPC specifications impacts for 5GC interworking","source":"Irfan (Cisco)","contact":"Maurice Pope","contact-id":648,"tdoctype":"discussion","for":"Endorsement","abstract":"-","secretary_remarks":"Created in parallel session Revised in parallel session to S2-180815.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17500,"status":"revised","reservation_date":"2018-01-26 13:51:49","uploaded":"2018-01-26 18:07:54","revisionof":"","revisedto":"S2-180815","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180803.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180804","title":"23.502: MME and AMF registration in HSS+UDM","source":"Cisco","contact":"Irfan Ali","contact-id":74090,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: For no-N26 procedures, the MME and AMF explicitly includes 'Dual MME\/AMF registration indicator' to the HSS+UDM.  If HSS does not support dual MME\/AMF registration it does not indicate support of this in the ULA 'supported features' AVP. If this indication is not present the MME or AMF knows that dual-registration is not allowed and should not provide the 'no-N26 support' indication to the UE.","secretary_remarks":"Revision of S2-180785. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17980,"status":"approved","reservation_date":"2018-01-26 13:51:49","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180785","revisedto":"S2-181806","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180804.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180805","title":"23.502: Indirect data forwarding in home routed roaming case","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarifying that, in home routed roaming case, the V-SMF is responsible for handling indirect data forwarding during the handover procedure from 5GS to EPS. 2 Similar clarfication for the handover procedure from EPS to 5GS. 3. Removing the FFS on the indirect data forwarding in home routed roaming.","secretary_remarks":"Revision of S2-180784. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17880,"status":"approved","reservation_date":"2018-01-26 13:51:49","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180784","revisedto":"S2-181512","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180805.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180806","title":"23.502: Interaction between SMF and UPF during the inter-system change","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarifying that the PGW-C+SMF sends both of Sx and N4 session management messages to the UPF+PGW-U. 2 removing the related FFS.","secretary_remarks":"Revision of S2-180783. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17910,"status":"approved","reservation_date":"2018-01-26 13:51:49","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180783","revisedto":"S2-181513","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180806.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180807","title":"23.501: Generating EPS PDN Connection parameters from 5G PDU Session parameters","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Proposes a new annex about how to generate the EPS PDN connection parameters from the 5G PDU Session parameters in PGW-C+SMF.","secretary_remarks":"Revision of S2-180796. Endorsed in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17950,"status":"endorsed","reservation_date":"2018-01-26 13:51:49","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180796","revisedto":"S2-181594","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180807.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180808","title":"23.502 Clarification of mobility procedure from EPS to 5GS without N26 interface","source":"Orange","contact":"Thouraya Toukabri","contact-id":66374,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: addition that Notify message MME > HSS shall be sent when when the subscription data indicates that the user is allowed use 5G as a RAT type in order to handle EPS to 5GS handover.","secretary_remarks":"Revision of S2-180792. For e-mail approval. e-mail revision 1 approved. Revised to S2-181404.","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18120,"status":"revised","reservation_date":"2018-01-26 13:51:49","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180792","revisedto":"S2-181404, S2-182251","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180808.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180809","title":"23.502: Request Type in PDN connectivity request for SRM interworking","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change the related text: If the TAU was rejected in Step 2 the IP address preservation is not provided. In this case the UE provides IMSI in the Attach Request, and provides a Request Type 'initial request' in the PDN CONNECTIVITY Request if included in the Attach Request.","secretary_remarks":"Revision of S2-180788. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18200,"status":"approved","reservation_date":"2018-01-26 13:51:49","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180788","revisedto":"S2-182090","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180809.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180810","title":"Reply LS to GSMA NG SIGNAL on Interworking between networks with different 5G deployments","source":"SA WG2","contact":"Susana Sabater","contact-id":31269,"tdoctype":"LS out","for":"Decision","abstract":"To: GSMA NG SIGNAL","secretary_remarks":"Revision of S2-180798. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17410,"status":"approved","reservation_date":"2018-01-26 13:51:49","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180798","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180019","lsto":"GSMA NG SIGNAL","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180810.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180811","title":"23.502: Clarifications on EPS to 5GS handover procedure using N26","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The two ENs are to be removed","secretary_remarks":"Revision of S2-180801. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17670,"status":"approved","reservation_date":"2018-01-26 13:51:49","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180801","revisedto":"S2-182089","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180811.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180812","title":"23.502: Clean up FFSs in 4.11.1.2.2","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1 SSC mode is sent to UE during the PDN Connection Establishment procedure. 2 change the 5G security context mapping from an EN to a Note. 3 add description between SMF and UPF","secretary_remarks":"Revision of S2-180782. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17720,"status":"approved","reservation_date":"2018-01-26 13:51:49","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180782","revisedto":"S2-181593","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180812.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180813","title":"23.502: Corrections to the Inter-system mobility procedures","source":"NTT DOCOMO, LG Electronics","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. In 4.11.1.3.3, the AMF takes the SMF address from UDM, not from EPS bearer context. The AMF provides the PDU Session ID (and not the EBI) to the SMF in the CreateSMContext. The SMF responds with the allocated EBI information, and AMF stores the allocated EBI(s) associated to the PDU Session ID. In 4.11.1.1 (with N26) and 4.11.2.1 (without N26) it is clarified the PGW-C+SMF registers the PDU Session ID - SMF ID association to the UDM for PDN connections established in EPC. In 5.2.8.2.2 and 5.2.8.2.5, the Allocated EBI information is added as an optional output parameter in the Create service operations.  2. In 4.11.1.2.2.2, 4.11.1.3.3 and 4.11.1.4.2 replace the UpdateSMContext with CreateSMContext. In 5.2.8.2.2 and 5.2.8.2.5, the PDU Session ID is changed as an optional input parameter in the Create service operations, and in it is changed 5.2.8.2.6 mandatory for Update operation. 3. In 4.11.1.3.3, the active flag setting is changed to the 'PDU Session(s) to be re-","secretary_remarks":"Revision of S2-180802. Agreed in parallel session. Block Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17790,"status":"approved","reservation_date":"2018-01-26 13:51:49","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180802","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180813.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180814","title":"23.501: Clarification on the use of indicators for the support of interworking without N26 and interworking with N26","source":"Orange","contact":"Thouraya Toukabri","contact-id":66374,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Indication that interworking with N26 is supported is sent to the device Conditions for the UE to be in dual registration are clarified","secretary_remarks":"Revision of S2-180793. Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18170,"status":"approved","reservation_date":"2018-01-26 13:51:50","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180793","revisedto":"S2-182282","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180814.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180815","title":"Capturing EPC specifications impacts for 5GC interworking","source":"Irfan (Cisco)","contact":"Maurice Pope","contact-id":648,"tdoctype":"discussion","for":"Endorsement","abstract":"-","secretary_remarks":"Revision of S2-180803. Endorsed in parallel session","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":17510,"status":"endorsed","reservation_date":"2018-01-26 13:52:02","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180803","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180815.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180816","title":"Reserved for Irfan's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23710,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180817","title":"Reserved for Irfan's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23720,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180818","title":"Reserved for Irfan's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23730,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180819","title":"Reserved for Irfan's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23740,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180820","title":"Reserved for Irfan's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23750,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180821","title":"Reserved for Irfan's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23760,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180822","title":"Reserved for Irfan's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23770,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180823","title":"Reserved for Irfan's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23780,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180824","title":"23.724: TR Scope","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes the scope for TR 23.724.","secretary_remarks":"Revision of S2-180692. Agreed in parallel session. Block Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20630,"status":"approved","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180692","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180824.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180825","title":"23.724: Architectural assumptions","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Architectural assumptions and principles for this study","secretary_remarks":"Revision of S2-180159. Revised in parallel session to S2-180921.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20650,"status":"revised","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180159","revisedto":"S2-180921","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180825.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180826","title":"23.724: Key Issue on infrequent small data transmission","source":"Huawei, HiSilicon, InterDigital Inc, AT&T, Convida, Intel, Motorola Mobility, Lenovo","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue for small data transmission","secretary_remarks":"Revision of S2-180326, merging S2-180160 and S2-180217. Revised in parallel session to S2-180922.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20680,"status":"revised","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180326","revisedto":"S2-180922","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180826.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180827","title":"23.724: Adding small data frequent communication key issue","source":"Ericsson, InterDigital Inc.","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Small data frequent communication key issue","secretary_remarks":"Revision of S2-180161, merging S2-180453. Revised in parallel session to S2-180923.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20740,"status":"revised","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180161","revisedto":"S2-180923","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180827.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180828","title":"23.724: Adding High latency key issue","source":"Ericsson, CATT, Convida Wireless, Samsung, Huawei, HiSilicon, Intel, AT&T, Qualcomm, LG Electronics","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"High latency key issue","secretary_remarks":"Revision of S2-180162, merging S2-180327. Revised in parallel session to S2-181201.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20810,"status":"revised","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180162","revisedto":"S2-181201","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180828.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180829","title":"23.724: Key Issue on Power Saving Functions","source":"Qualcomm Inc., Convida Wireless LLC, Huawei, HiSilicon, Verizon Wireless, Interdigital, China Mobile","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes some architectural assumptions and a Key Issue for FS_CIoT_5G related to power saving functions.","secretary_remarks":"Revision of S2-180709. Revised in parallel session to S2-181202.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20860,"status":"revised","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180709","revisedto":"S2-181202","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180829.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180830","title":"23.724: KI - Power Saving Functions","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"pCR","for":"Approval","abstract":"This paper discusses an FS_CIoT_5G Key Issue on Power Savings Functions","secretary_remarks":"Revision of S2-180614. Revised in parallel session to S2-181203.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20900,"status":"revised","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180614","revisedto":"S2-181203","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180830.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180831","title":"23.724: KI: Enhanced Coverage","source":"Sony, Ericsson, Huawei, HiSilicon, Intel","contact":"Lars Nord","contact-id":58638,"tdoctype":"pCR","for":"Approval","abstract":"Discuss the background for CN functionality supporting RAN feature Enhanced Coverage and propose aspects to be studied.","secretary_remarks":"Revision of S2-180270. Agreed in parallel session. Block Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20940,"status":"approved","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180270","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180831.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180832","title":"23.724: KI: Overload Control","source":"Sony, InterDigital Inc., NEC, Intel","contact":"Lars Nord","contact-id":58638,"tdoctype":"pCR","for":"Approval","abstract":"Discuss the legacy solution and propose open key issues for overload control that needs to be studied.","secretary_remarks":"Revision of S2-180268. Agreed in parallel session. Block Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20960,"status":"approved","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180268","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180832.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180833","title":"Addition of EC restriction parameter in S1 AP PAGING message","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The requested EC Restriction parameter is added in the S1 AP PAGING message","secretary_remarks":"Created in parallel session Revised in parallel session to S2-180918.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10170,"status":"revised","reservation_date":"2018-01-23 13:27:36","uploaded":"2018-01-26 18:07:52","revisionof":"","revisedto":"S2-180918","release":"Rel-14","crspec":23.401,"crspecversion":"14.6.0","workitem":[{"winame":"CIoT_Ext"}],"crnumber":3394.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180833.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180834","title":"Addition of EC restriction parameter in S1 AP PAGING message","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The requested EC Restriction parameter is added in the S1 AP PAGING message","secretary_remarks":"Revision of S2-180632. Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10200,"status":"agreed","reservation_date":"2018-01-23 13:27:43","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180632","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"CIoT_Ext"}],"crnumber":3391.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-180085","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180834.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180835","title":"[DRAFT] Reply LS on Paging in case of Enhanced Coverage Restriction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to explain that EC Restricted parameter is included in S1 PAGING alreary in Rel-14.","secretary_remarks":"Revision of S2-180636. Revised in parallel session to S2-180919.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10220,"status":"revised","reservation_date":"2018-01-23 13:27:44","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180636","revisedto":"S2-180919","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180835.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180836","title":"Paging failure for CE-capable UEs after 2G\/3G to 4G idle-mode mobility","source":"Intel, NTT DOCOMO","contact":"Puneet Jain","contact-id":36283,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the network supports CE-Capable UEs (see TS 36.300) after the 'first TAU in-idle mode following the RAT change', the MME may initiate UE Radio Capability Match Request procedure indicating to eNB that update to UE's Radio capability is needed. The eNB based on 'update needed' indicator requests the UE for its radio capability and provides it to the MME.","secretary_remarks":"Revision of S2-180568. Revised in parallel session to S2-181240.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10280,"status":"revised","reservation_date":"2018-01-23 13:27:44","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180568","revisedto":"S2-181240","release":"Rel-13","crspec":23.401,"crspecversion":"13.13.0","workitem":[{"winame":"TEI13"}],"crnumber":3386.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180836.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180837","title":"Paging failure for CE-capable UEs after 2G\/3G to 4G idle-mode mobility","source":"Intel, NTT DOCOMO","contact":"Puneet Jain","contact-id":36283,"tdoctype":"CR","for":"Approval","abstract":"Rel-14 mirror CR: Summary of change: If the network supports CE-Capable UEs (see TS 36.300) after the 'first TAU in-idle mode following the RAT change', the MME may initiate UE Radio Capability Match Request procedure indicating to eNB that update to UE's Radio capability is needed. The eNB based on 'update needed' indicator requests the UE for its radio capability and provides it to the MME.","secretary_remarks":"Revision of S2-180570. Revised in parallel session to S2-181241.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10310,"status":"revised","reservation_date":"2018-01-23 13:27:45","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180570","revisedto":"S2-181241","release":"Rel-14","crspec":23.401,"crspecversion":"14.6.0","workitem":[{"winame":"TEI13"}],"crnumber":3387.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180837.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180838","title":"Paging failure for CE-capable UEs after 2G\/3G to 4G idle-mode mobility","source":"Intel, NTT DOCOMO","contact":"Puneet Jain","contact-id":36283,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: If the network supports CE-Capable UEs (see TS 36.300) after the 'first TAU in-idle mode following the RAT change', the MME may initiate UE Radio Capability Match Request procedure indicating to eNB that update to UE's Radio capability is needed. The eNB based on 'update needed' indicator requests the UE for its radio capability and provides it to the MME.","secretary_remarks":"Revision of S2-180572. Revised in parallel session to S2-181242.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10340,"status":"revised","reservation_date":"2018-01-23 13:27:46","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180572","revisedto":"S2-181242","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI13"}],"crnumber":3388.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180838.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180839","title":"[DRAFT] Reply LS on Paging failures for CE Capable UEs","source":"Intel","contact":"Puneet Jain","contact-id":36283,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Paging failures for CE Capable UEs after 2G\/3G - > 4G idle-mode mobility","secretary_remarks":"Revision of S2-180573. Revised in parallel session to S2-181243.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10380,"status":"revised","reservation_date":"2018-01-23 13:27:47","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180573","revisedto":"S2-181243","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180839.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180840","title":"CIoT Attach correction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of the option that conflicts with TS 36.300.","secretary_remarks":"Revision of S2-180628. Revised to S2-181371.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10450,"status":"revised","reservation_date":"2018-01-23 13:27:47","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180628","revisedto":"S2-181371","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"CIoT"},{"winame":"TEI15"}],"crnumber":3390.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180840.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180841","title":"Removal of hanging Editor's Note on support for deferred location","source":"Qualcomm Incorporated, Huawei, HiSilicon","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removes hanging Editor's Note from clause 9.1.1 of TS 23.271 that leaves the impression that deferred location request is not defined in this release of the specification","secretary_remarks":"Revision of S2-180385. Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10500,"status":"agreed","reservation_date":"2018-01-23 13:27:48","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180385","revisedto":"","release":"Rel-14","crspec":23.271,"crspecversion":"14.3.0","workitem":[{"winame":"CIoT_Ext"}],"crnumber":430.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180085","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180841.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180842","title":"Removal of hanging Editor's Note on support for deferred location","source":"Qualcomm Incorporated, Huawei, HiSilicon","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: Removes hanging Editor's Note from clause 9.1.1 of TS 23.271 that leaves the impression that deferred location request is not defined in this release of the specification","secretary_remarks":"Revision of S2-180386. Agreed in parallel session. Block Approved. No Rel-15 TS exists, so this CR is not required. Noted","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10520,"status":"noted","reservation_date":"2018-01-23 13:27:49","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180386","revisedto":"","release":"Rel-15","crspec":23.271,"crspecversion":"14.3.0","workitem":[{"winame":"CIoT_Ext"},{"winame":"TEI15"}],"crnumber":431.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180842.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180843","title":"[DRAFT] Reply LS on indication of preferred CIoT network behaviour","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"Answer LS C1-175414","secretary_remarks":"Revision of S2-180384. Revised in parallel session to S2-180920.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10920,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180384","revisedto":"S2-180920","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180843.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180844","title":"23.739: Skeleton for TR 23.739","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the skeleton for TR 23.739 'Study on EPC support for Mobility with Low Latency Communication'","secretary_remarks":"Revision of S2-180716. Revised in parallel session to S2-180848.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22830,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180716","revisedto":"S2-180848","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180844.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180845","title":"23.739: Scope","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the Scope for TR 23.739 'Study on EPC support for Mobility with Low Latency Communication'","secretary_remarks":"Revision of S2-180717. Revised in parallel session to S2-180847.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22860,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180717","revisedto":"S2-180847","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180845.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180846","title":"23.739: Architecture Requirements, Assumptions, and Baseline","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes some text for the Architectural Requirements, Assumptions and Baseline for TR 23.739 'Study on EPC support for Mobility with Low Latency Communication'","secretary_remarks":"Revision of S2-180719. Revised in parallel session to S2-180853.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":23000,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180719","revisedto":"S2-180853","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180846.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180847","title":"23.739: Scope","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the Scope for TR 23.739 'Study on EPC support for Mobility with Low Latency Communication'","secretary_remarks":"Revision of S2-180845. Revised in parallel session to S2-180857.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22870,"status":"revised","reservation_date":"2018-01-23 13:28:14","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180845","revisedto":"S2-180857","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180847.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180848","title":"23.739: Skeleton for TR 23.739","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the skeleton for TR 23.739 'Study on EPC support for Mobility with Low Latency Communication'","secretary_remarks":"Revision of S2-180844. Agreed in parallel session. Block Approved","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22840,"status":"approved","reservation_date":"2018-01-23 13:28:14","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180844","revisedto":"","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180848.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180849","title":"EPC support for mobility with low latency communication: discussion and solution proposal","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"discussion","for":"Approval","abstract":"Proposes an architecture principle and a procedure for make-before-break PDN connection mobility and proposes to either endorse them or document in the TR","secretary_remarks":"Revision of S2-180433. Revised in parallel session to S2-180851.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22910,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180433","revisedto":"S2-180851","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_125_Gothenburg\/Docs\/S2-180849.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180850","title":"23.739: Applicability of SSC mode 3 for mobility with Low Latency Communication","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"pCR","for":"Approval","abstract":"Discusses the applicability of SSC mode 3 for mobility with LLC.","secretary_remarks":"Revision of S2-180390. Revised in parallel session to S2-180856.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22950,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180390","revisedto":"S2-180856","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180850.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180851","title":"EPC support for mobility with low latency communication: discussion and solution proposal","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"discussion","for":"Approval","abstract":"Proposes an architecture principle and a procedure for make-before-break PDN connection mobility and proposes to either endorse them or document in the TR","secretary_remarks":"Revision of S2-180849. Revised in parallel session to S2-180855.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22920,"status":"revised","reservation_date":"2018-01-23 13:28:14","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180849","revisedto":"S2-180855","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_125_Gothenburg\/Docs\/S2-180851.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180852","title":"23.739: Key Issues","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes key issues for TR 23.739 'Study on EPC support for Mobility with Low Latency Communication'","secretary_remarks":"Revision of S2-180722. Agreed in parallel session. Block Approved","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":23040,"status":"approved","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180722","revisedto":"","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180852.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180853","title":"23.739: Architecture Requirements, Assumptions, and Baseline","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes some text for the Architectural Requirements, Assumptions and Baseline for TR 23.739 'Study on EPC support for Mobility with Low Latency Communication'","secretary_remarks":"Revision of S2-180846. Revised in parallel session to S2-181209.","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":23010,"status":"revised","reservation_date":"2018-01-23 13:28:14","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180846","revisedto":"S2-181209","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180853.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180854","title":"23.739: Lack of support for IPv6 multihoming in EPC","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"pCR","for":"Approval","abstract":"Discusses the requirements for PDN types and IP versions supported for FS_LLC_mob.","secretary_remarks":"Revision of S2-180391. Agreed in parallel session. Block Approved","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22980,"status":"approved","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180391","revisedto":"","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180854.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180855","title":"EPC support for mobility with low latency communication: discussion and solution proposal","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"discussion","for":"Approval","abstract":"Proposes an architecture principle and a procedure for make-before-break PDN connection mobility and proposes to either endorse them or document in the TR","secretary_remarks":"Revision of S2-180851. Agreed in parallel session. Block Approved","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22930,"status":"approved","reservation_date":"2018-01-23 13:28:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180851","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_125_Gothenburg\/Docs\/S2-180855.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180856","title":"23.739: Applicability of SSC mode 3 for mobility with Low Latency Communication","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"pCR","for":"Approval","abstract":"Discusses the applicability of SSC mode 3 for mobility with LLC.","secretary_remarks":"Revision of S2-180850. Agreed in parallel session. Block Approved","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22960,"status":"approved","reservation_date":"2018-01-23 13:28:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180850","revisedto":"","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180856.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180857","title":"23.739: Scope","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the Scope for TR 23.739 'Study on EPC support for Mobility with Low Latency Communication'","secretary_remarks":"Revision of S2-180847. Agreed in parallel session. Block Approved","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":22880,"status":"approved","reservation_date":"2018-01-23 13:28:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180847","revisedto":"","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180857.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180858","title":"23.791: FS_eNA skeleton","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the skeleton for the TR 23.791 of FS_eNA.","secretary_remarks":"Revision of S2-180215. Agreed in parallel session. Block Approved","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21410,"status":"approved","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180215","revisedto":"","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180858.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180859","title":"23.791: Scope of TR 23.791","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the scope of the TR 23.791 for FS_eNA.","secretary_remarks":"Revision of S2-180213. Revised in parallel session to S2-181228.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21430,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180213","revisedto":"S2-181228","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180859.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180860","title":"23.791: Architecture Requirement of TR 23.791","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes architecture requirement section of the TR 23.791 for FS_eNA.","secretary_remarks":"Revision of S2-180214. Revised in parallel session to S2-181229.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21460,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180214","revisedto":"S2-181229","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180860.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180861","title":"23.791: Discussion on big data and 5G","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution triggers discussion on big data analytic and 5G system.","secretary_remarks":"Revision of S2-180212. Revised in parallel session to S2-181230.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21500,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180212","revisedto":"S2-181230","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180861.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180862","title":"23.791: Key issue on how to get service information from AF","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to a key issue on how to get service information from the service applications.","secretary_remarks":"Revision of S2-180216. Revised in parallel session to S2-181232.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21590,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180216","revisedto":"S2-181232","release":"Rel-16","crspec":23.791,"crspecversion":"16.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180862.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180863","title":"23.791: Key issue on customized mobility management","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue on customizing mobility management based on NWDA output.","secretary_remarks":"Revision of S2-180633. Agreed in parallel session. Block Approved","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21630,"status":"approved","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180633","revisedto":"","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180863.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180864","title":"23.791: FS_eNA Key Issue: NWDA-Assisted Traffic Routing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue to study solutions to support traffic routing using statistical information from NWDAF.","secretary_remarks":"Revision of S2-180141. Revised in parallel session to S2-181231.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21540,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180141","revisedto":"S2-181231","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180864.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180865","title":"LS reply on Mapping of Conversational Services to 5G System","source":"SA WG2","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4. CC: SA WG1","secretary_remarks":"Revision of S2-180455. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16610,"status":"approved","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180455","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180010","lsto":"SA WG4","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180865.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180866","title":"23.502: Correction\/cleanup of IMS Emergency support","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the 23.167 applicability correctly for all cases and add one additional case for 5G NR case.","secretary_remarks":"Revision of S2-180207. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17060,"status":"approved","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180207","revisedto":"S2-181628","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180866.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180867","title":"23.502: Update on UE context in AMF to support T-ADS query","source":"China Mobile","contact":"Jiang Yi","contact-id":56358,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Removing the editor's note in 4.3.2.2.2 on PDU Session Establishment in home-routed case. That is because slice roaming solution for non-standardized S-NSSAI is already defined in TS 23.501.","secretary_remarks":"Revision of S2-180715. Postponed in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17090,"status":"postponed","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180715","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180867.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180868","title":"23.502: Clarification on SMS related Subscription data","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Adding the SMS Subscription data type as a new type into the Table 5.2.3.3.1-1. - Updating the Registration procedures for SMS over NAS, about AMF retrieval (step 2) and SMSF retrieval (step 7) respectively. - Removing the descriptions about SMSF selection in order to transfer them into the new clause of TS 23.501.","secretary_remarks":"Revision of S2-180300. Revised in parallel session to S2-181217.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17160,"status":"revised","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180300","revisedto":"S2-181217","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180868.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180869","title":"23.502: Correction of UDR usage in specific Service related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that UDM\/PCF may invoke UDR services in specific services are corrected.","secretary_remarks":"Revision of S2-180755. Endorsed in parallel session.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17270,"status":"endorsed","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180755","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180869.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180870","title":"23.502: LCS Correction of identities","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Usage of SUPI, GPSI and PEI as UE identity corrected. Correct spelling of USIM. Use correct wording for emergency registration. Pointer to figure 4.10.2-1 corrected to 4.13.5.1-1. Aligned information flow figures to template in Annex A.3.","secretary_remarks":"Revision of S2-180230. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17290,"status":"approved","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180230","revisedto":"S2-181630","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180870.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180871","title":"23.501: 5_16_6_Mission Critical Services - Editorial Changes","source":"FirstNet, AT&T, Motorola Solutions, Airwave","contact":"Ihab Guirguis","contact-id":65302,"tdoctype":"draftCR","for":"Approval","abstract":"This contribution provides editorial updates for clause 5.16.6 as well as clarifying that the scope of this clause extends to include other commercial services that require priority treatment.","secretary_remarks":"Revision of S2-180454. Revised in parallel session to S2-181218.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17310,"status":"revised","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180454","revisedto":"S2-181218","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180871.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180872","title":"23.501: 5_16_6_Mission Critical Services - Reference Update","source":"FirstNet, AT&T, Motorola Solutions, Airwave","contact":"Ihab Guirguis","contact-id":65302,"tdoctype":"draftCR","for":"Approval","abstract":"This contribution corrects the reference for the MCX Services description.","secretary_remarks":"Revision of S2-180456. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17340,"status":"approved","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180456","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180872.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180873","title":"[Draft] LS OUT on IMS registration for Dual-Registered UE","source":"SA WG2","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG4","secretary_remarks":"Created in parallel session Revised in parallel session to S2-181219.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17120,"status":"revised","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"","revisedto":"S2-181219","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180873.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180874","title":"23.501: Further RRC Inactive assitance information","source":"NEC, Sony","contact":"Iskren Ianev","contact-id":59515,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following new assistance information is added to the RRC Inactive assistance information from the AMF to the gNB: - UE stationary indication. If the AMF is aware the connecting UE is stationary (e.g. from the UE mobility pattern in the AMF, see clause 5.3.4.2), the AMF may include in the 'RRC Inactive assistance information' an UE stationary indication to help with the NG RAN decision on whether to move the UE in RRC Inactive state and if so, what RNA to configure for it (e.g. the size of RNA); - UE moving trajectory information. If the AMF is aware of the connecting UE's moving trajectory (e.g. from the UE mobility pattern in the AMF, see clause 5.3.4.2), the AMF may include in the 'RRC Inactive assistance information' an UE moving trajectory information (e.g. the list of cells that are overlapped with the UE moving trajectory) to help with the NG-RAN decision on what RNA to configure for the UE in case the UE is moved to RRC Inactive state (e.g. the size and\/or","secretary_remarks":"Revision of S2-180405. Revised in parallel session to S2-181234.","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16450,"status":"revised","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180405","revisedto":"S2-181234","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180874.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180875","title":"23.501: Clarifying conditions for UE to enter CM-IDLE","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Current text describing conditions for UE to enter CM-IDLE when it is in CM-CONNECTED with RRC-Inactive state in 5.3.3.2.5 can be interpreted in two ways: - (1) If the periodic RAN Notification Area Update timer expires and UE cannot perform resume procedure due to lack of radio coverage then the UE shall enter CM-IDLE, or - (2) If the periodic RAN Notification Area Update timer expires and the RRC resume procedure fails, then UE enters CM-IDLE.  It is the understanding of the sourcing company that the correct behaviour is according to the 2nd case, i.e. RRC resume procedure fails. Lack of radio coverage might be temporary and it is possible and probable that even if there is no radio coverage when the the periodic RAN Notification Area Update timer expires, then once the radio coverage is regained, the RRC resume procedure might be successfully conducted due the the fact that RAN kept the N2 association for longer time period than the duration of the RAN Notificatio","secretary_remarks":"Revision of S2-180720. Withdrawn in parallel session (not provided).","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16490,"status":"withdrawn","reservation_date":"2018-01-24 06:42:53","uploaded":null,"revisionof":"S2-180720","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180876","title":"23.501: Clarification of the interworking between 5G and GERAN\/UTRAN\/E-UTRAN when UE is in RRC-inactive state.","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: If a UE in CM-CONNECTED with RRC Inactive state performs cell selection to the GERAN\/UTRAN, as the 5G does not interwork with 3G\/2G system, the UE shall trigger the initial attach to the 2G\/3G network.  If a UE in CM-CONNECTED with RRC Inactive state performs cell selection to the E-UTRAN, the UE may trigger TAU or 'handover' attach to the the 4G network as described in section 5.17 'Interworking and Migration'.","secretary_remarks":"Revision of S2-180331. Agreed in parallel session. Block Approved","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16510,"status":"approved","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180331","revisedto":"S2-181562, S2-182238","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180876.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180877","title":"23.502: UE presence in LADN for RRC Inactive","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In case that the RRC Inactive state applies to the NG-RAN, the UE Presence in LADN is defined as follows: - IN: - if the UE is inside the LADN service area and if the UE is in CM-CONNECTED state (with RRC Connected state in case that the RRC Inactive state applies to the NG-RAN); or- if the UE is inside a Registration Area which is contained within the LADN service area, and if the UE is in CM-IDLE state or in CM-CONNECTED with RRC Inactive state in case that the RRC Inactive state applies to NG-RAN. - OUT: - if the UE is outside the LADN service area but within a Registration Area where the LADN is available, and if the UE is in CM-CONNECTED state (with RRC Connected state in case that the RRC Inactive state applies to the NG-RAN); or - if UE is inside a Registration Area where the LADN is not available. - UNKNOWN  -  if the UE is inside a Registration Area where the LADN is available and the LADN service area does not contain the whole Registration Area, and  -  if","secretary_remarks":"Revision of S2-180256. Withdrawn in parallel session (not provided).","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16580,"status":"withdrawn","reservation_date":"2018-01-24 06:42:53","uploaded":null,"revisionof":"S2-180256","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180878","title":"23.724: Key Issue on Support of Reliable Communication","source":"Convida Wireless LLC, Intel","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a Key Issue for FS_CIoT_5G related to Support for Reliable Communication.","secretary_remarks":"Revision of S2-180428. Revised in parallel session to S2-181204.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20980,"status":"revised","reservation_date":"2018-01-24 07:00:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180428","revisedto":"S2-181204","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180878.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180879","title":"23.724: Key Issue on Support of common north-bound APIs for EPC-5GC Interworking","source":"Convida Wireless LLC, AT&T","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes some architectural assumptions and a Key Issue for FS_CIoT_5G related to Support of common north-bound APIs for EPC-5GC Interworking","secretary_remarks":"Revision of S2-180429. Revised in parallel session to S2-181205.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21010,"status":"revised","reservation_date":"2018-01-24 07:00:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180429","revisedto":"S2-181205","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180879.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180880","title":"23.724: Key Issue on Network Parameter Configuration API via NEF","source":"Convida Wireless LLC, Intel","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a Key Issue on Network Parameter Configuration API via NEF for the FS_CIoT_5G TR","secretary_remarks":"Revision of S2-180430. Agreed in parallel session Revised to S2-181379.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21040,"status":"revised","reservation_date":"2018-01-24 07:00:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180430","revisedto":"S2-181379","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180880.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180881","title":"23.724: Key Issue on Support of equivalent overall functionalities as provided by SCEF for CIoT\/MTC","source":"Convida Wireless LLC, Qualcomm Incorporated","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a Key Issue on Support of equivalent overall functionalities as provided by SCEF for CIoT\/MTC for FS_CIoT_5G.","secretary_remarks":"Revision of S2-180431. This was withdrawn.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21070,"status":"withdrawn","reservation_date":"2018-01-24 07:00:44","uploaded":null,"revisionof":"S2-180431","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180882","title":"23.724: Key Issue on Monitoring","source":"Convida Wireless LLC","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper an introduces a Key Issue on Monitoring for the FS_CIoT_5G TR","secretary_remarks":"Revision of S2-180427. Revised in parallel session to S2-181206.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21100,"status":"revised","reservation_date":"2018-01-24 07:00:45","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180427","revisedto":"S2-181206","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180882.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180883","title":"23.724: Key Issue on Inter RAT idle mode mobility to\/from NB-IoT","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes some architectural assumptions and a Key Issue for FS_CIoT_5G related to Inter RAT idle mode mobility to\/from NB-IoT.","secretary_remarks":"Revision of S2-180702. Revised in parallel session to S2-181207.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21130,"status":"revised","reservation_date":"2018-01-24 07:00:45","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180702","revisedto":"S2-181207","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180883.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180884","title":"23.501: EPS Fallback for voice","source":"Ericsson, Charter Communications, Comcast, Huawei","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding support for redirect to EPS in case of EPS Fallback for voice and for rejecting the PDU Session modification that setups the QoS flow for voice.","secretary_remarks":"Revision of S2-180203, merging S2-180286, S2-180553 and S2-180554. Revised in parallel session to S2-181210.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16680,"status":"revised","reservation_date":"2018-01-24 13:38:19","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180203","revisedto":"S2-181210","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180884.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180885","title":"23.502: EPS Fallback for voice","source":"Ericsson, Charter Communications, Comcast, Huawei","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding support for redirect to EPS in case of EPS Fallback for voice.","secretary_remarks":"Revision of S2-180204. Revised in parallel session to S2-181211.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16710,"status":"revised","reservation_date":"2018-01-24 13:38:19","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180204","revisedto":"S2-181211","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180885.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180886","title":"[DRAFT] LS on EPS Fallback for voice","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Created in parallel session Revised in parallel session to S2-181212.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16750,"status":"revised","reservation_date":"2018-01-24 13:38:19","uploaded":"2018-01-26 18:07:53","revisionof":"","revisedto":"S2-181212","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180886.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180887","title":"23.501: Emergency Services Support indication per RAT","source":"OPPO, Nokia, Nokia Shanghai Bell","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove the editor note and clarify the related description. Editor's note: need for per RAT indicated will need to be confirmed.","secretary_remarks":"Revision of S2-180296. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16810,"status":"approved","reservation_date":"2018-01-24 13:38:19","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180296","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180887.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180888","title":"23.501: Draft CR 23.501 Correction to Emergency Fallback","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Rephrasing to alllow emergency session over untrusted N3GPP access if the emergency session could not be established via 3GPP access - Indications are mutually exclusive - Misc. editorial corrections (Emergency Services)","secretary_remarks":"Revision of S2-180363. Revised in parallel session to S2-181215.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16830,"status":"revised","reservation_date":"2018-01-24 13:38:19","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180363","revisedto":"S2-181215","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180888.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180889","title":"Handling of emergency sessions over untrusted N3GPP access in 5GS","source":"MediaTek Inc.","contact":"Maurice Pope","contact-id":648,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - The requirement is introduced","secretary_remarks":"Revised in parallel session to S2-181216.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16860,"status":"revised","reservation_date":"2018-01-24 10:28:30","uploaded":"2018-01-26 18:07:53","revisionof":"","revisedto":"S2-181216","release":"Rel-15","crspec":23.167,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":321.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180889.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180890","title":"23.501: Fixes for Emergency Services and Emergency Services using Fallback","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) It is proposed to remove the EN that was added to confirm RAT based ES support indication. 2) It is proposed to clarify the UE requirement when it moves to 'emergency registered' (= limited services) state and remove the corresponding EN. Editor's note: How the 5GC reacts to existing services via normal registration, and how new services via normal registration operate when an Emergency Registration has occurred is FFS. 3) When AMF initiates redirection request, it needs to provide some hints to the RAN to help determine whether RAT fallback or System fallback will be performed. 'In the N2 procedure, the AMF may indicate the target CN for the RAN node to know whether inter-RAT fallback or inter-system fallback is to be performed.'","secretary_remarks":"Revision of S2-180467. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16900,"status":"approved","reservation_date":"2018-01-24 13:38:19","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180467","revisedto":"S2-181756","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180890.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180891","title":"23.502: Fixes for Emergency Services using Fallback procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Ensure that the AS procedure performed by the AN to redirect the UE is secure","secretary_remarks":"Revision of S2-180532. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16920,"status":"approved","reservation_date":"2018-01-24 14:19:37","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180532","revisedto":"S2-181757","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180891.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180892","title":"23.502 Clarification on the Emergency HO indication for EPS fallback","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding an Note the NG-RAN decide whether to continue EPS Fallback procedures with PS HO or to initiate redirection. NG-RAN may forward the Emergency indication to the target eNB in the Source to Target Transparent Container.","secretary_remarks":"Revision of S2-180555. Revised in parallel session to S2-181213.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16960,"status":"revised","reservation_date":"2018-01-24 14:19:37","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180555","revisedto":"S2-181213","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180892.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180893","title":"23.501: Complete of IMS Emergency support in 5G including slice and local numbers","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In case of Limited Service state, no slice info to be provided","secretary_remarks":"Revision of S2-180731. Revised in parallel session to S2-181214.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17000,"status":"revised","reservation_date":"2018-01-24 14:19:37","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180731","revisedto":"S2-181214","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180893.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180894","title":"Key decisions for INOBEAR","source":"Telstra","contact":"Robert Ropolyi","contact-id":73241,"tdoctype":"discussion","for":"Agreement","abstract":"The paper lists key issues connected to INOBEAR, with proposed decisions. It also provides examples for the required changes in impacted procedures, subject to the decisions.","secretary_remarks":"Revision of S2-180251. Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15","ainame":"WID on increasing the maximum number of LTE bearers (INOBEAR)","tdoc_agenda_sort_order":22540,"status":"noted","reservation_date":"2018-01-24 14:19:37","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180251","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_125_Gothenburg\/Docs\/S2-180894.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180895","title":"Update of the Procedures Specified in TS 23.060","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Note that the following changes are clarification and correction but not adding new functionality.  Clause 6.3.4.1.1 Change 'Part 1' and 'Part 2' in the figure caption to 'Group 1' and 'Group 2'. Add Group 1 and Group 2 in the text description before the Figures to improve readability Add the steps specific for S4SGSN in the text description before the Figures. Group 1:  Add HLR in the figure Add steps specific for S4SGSN in Figure 6.3.4.1.1-1 when applicable. Add step 2c which triggers step 3a\/3b. Add new steps 3d\/3e (i.e. two CPF-UPF interactions for SGW) for the existing PDN connection deletion. In step 5a\/5b SGW-C and SGW-U interaction, change the dashed line to solid line.  In step 10, change 'SGSN-initiated Bearer Deactivation Procedure' to 'SGSN-initiated PDP Context Deactivation Procedure' where Figure 76 is included.  Group 2: In Figure 6.3.4.1.1-2, step 4, add S4SGSN specifics. Correct use of 'May' for CPF-UPF interaction  Clause 6.3.4.1.2 Change 'Part 1' a","secretary_remarks":"Revision of S2-180224. Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10620,"status":"agreed","reservation_date":"2018-01-24 13:38:19","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180224","revisedto":"","release":"Rel-14","crspec":23.214,"crspecversion":"14.5.0","workitem":[{"winame":"CUPS"}],"crnumber":59.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180086","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180895.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180896","title":"Update of the Procedures Specified in TS 23.060","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: Note that the following changes are clarification and correction but not adding new functionality.  Clause 6.3.4.1.1 Change 'Part 1' and 'Part 2' in the figure caption to 'Group 1' and 'Group 2'. Add Group 1 and Group 2 in the text description before the Figures to improve readability Add the steps specific for S4SGSN in the text description before the Figures. Group 1:  Add HLR in the figure Add steps specific for S4SGSN in Figure 6.3.4.1.1-1 when applicable. Add step 2c which triggers step 3a\/3b. Add new steps 3d\/3e (i.e. two CPF-UPF interactions for SGW) for the existing PDN connection deletion. In step 5a\/5b SGW-C and SGW-U interaction, change the dashed line to solid line.  In step 10, change 'SGSN-initiated Bearer Deactivation Procedure' to 'SGSN-initiated PDP Context Deactivation Procedure' where Figure 76 is included.  Group 2: In Figure 6.3.4.1.1-2, step 4, add S4SGSN specifics. Correct use of 'May' for CPF-UPF interaction  Clause 6.3.4.1.2","secretary_remarks":"Revision of S2-180225. Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10640,"status":"agreed","reservation_date":"2018-01-24 13:38:20","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180225","revisedto":"","release":"Rel-15","crspec":23.214,"crspecversion":"15.1.0","workitem":[{"winame":"CUPS"}],"crnumber":60.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-180086","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180896.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180897","title":"Correction of SDF Filter Description in PDR Table","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that one or more SDF filters can be included in a PDR.","secretary_remarks":"Revision of S2-180607. Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10680,"status":"agreed","reservation_date":"2018-01-24 13:38:21","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180607","revisedto":"","release":"Rel-14","crspec":23.214,"crspecversion":"14.5.0","workitem":[{"winame":"CUPS"}],"crnumber":63.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180086","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180897.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180898","title":"Correction of SDF Filter Description in PDR Table","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: Clarify that one or more SDF filters can be included in a PDR.","secretary_remarks":"Revision of S2-180608. Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10700,"status":"agreed","reservation_date":"2018-01-24 13:38:21","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180608","revisedto":"","release":"Rel-15","crspec":23.214,"crspecversion":"15.1.0","workitem":[{"winame":"CUPS"}],"crnumber":64.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-180086","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180898.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180899","title":"INOBEAR assumptions, key issues and way forward","source":"Samsung","contact":"Maurice Pope","contact-id":648,"tdoctype":"discussion","for":"Discussion","abstract":"Assumptions, key issues and way forward for the INOBEAR work, to form the basis for the solution that will be implemented by CR(s).","secretary_remarks":"Created in parallel session Revised in parallel session to S2-181208.","agenda_item_sort_order":39,"ainumber":"6.15","ainame":"WID on increasing the maximum number of LTE bearers (INOBEAR)","tdoc_agenda_sort_order":22550,"status":"revised","reservation_date":"2018-01-24 14:19:37","uploaded":"2018-01-26 18:07:53","revisionof":"","revisedto":"S2-181208","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_125_Gothenburg\/Docs\/S2-180899.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180900","title":"[DRAFT] LS on applicability of Connection Establishment Indication procedure after the establishment of S1 logical connection","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3","secretary_remarks":"Created in parallel session. For e-mail approval. e-mail revision 2 approved. Revised to S2-181392.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10470,"status":"revised","reservation_date":"2018-01-24 13:38:22","uploaded":"2018-01-26 18:07:53","revisionof":"","revisedto":"S2-181392","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180900.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180901","title":"23.731: TR Skelton for eLCS","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Propose TR Skelton for enhanced location services.","secretary_remarks":"Revision of S2-180695. Agreed in parallel session. Block Approved","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21870,"status":"approved","reservation_date":"2018-01-25 11:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180695","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180901.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180902","title":"23.731: TR Scope for eLCS","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Propose TR Scope for enhanced location services.","secretary_remarks":"Revision of S2-180696. Agreed in parallel session. Block Approved","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21890,"status":"approved","reservation_date":"2018-01-25 11:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180696","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180902.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180903","title":"23.731: Architecture Assumption for eLCS","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Propose Archtecture Assmuption for enhanced Location services.","secretary_remarks":"Revision of S2-180697. Revised in parallel session to S2-181221.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21920,"status":"revised","reservation_date":"2018-01-25 11:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180697","revisedto":"S2-181221","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180903.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180904","title":"23.731: Architecture Requirements for eLCS","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Propose Archtecture Requirements for enhanced Location services.","secretary_remarks":"Revision of S2-180698. Revised in parallel session to S2-181222.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21950,"status":"revised","reservation_date":"2018-01-25 11:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180698","revisedto":"S2-181222","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180904.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180905","title":"23.731: Key Issue X: Indentify New Functionality and Distributions","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Define a Key issue X: Indentify New Functionality and Distributions","secretary_remarks":"Revision of S2-180700. Revised in parallel session to S2-181223.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21980,"status":"revised","reservation_date":"2018-01-25 11:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180700","revisedto":"S2-181223","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180905.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180906","title":"23.731: Key issue: positioning via user plane","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes new key issue 'positioning via user plane'.","secretary_remarks":"Revision of S2-180481. Revised in parallel session to S2-181224.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22010,"status":"revised","reservation_date":"2018-01-25 11:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180481","revisedto":"S2-181224","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180906.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180907","title":"23.731: Key Issue on Latency for 5GC Location Enhancement","source":"Qualcomm Incorporated, Huawei, AT&T","contact":"Hong Cheng","contact-id":25668,"tdoctype":"pCR","for":"Approval","abstract":"This contribution provides a P-CR to add a key issue to TR 23.731 on latency for 5GC location enhancement.","secretary_remarks":"Revision of S2-180513, merging S2-180291. Agreed in parallel session. Block Approved","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22060,"status":"approved","reservation_date":"2018-01-25 11:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180513","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180907.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180908","title":"23.731: Key issues for eLCS on support high accuracy positioning","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution discusses and proposes key issue for support high accuracy positioning.","secretary_remarks":"Revision of S2-180291. Withdrawn (not provded, S2-180291 was merged into S2-180907)","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22040,"status":"withdrawn","reservation_date":"2018-01-25 11:34:30","uploaded":null,"revisionof":"S2-180291","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180909","title":"23.731: Key Issue: Reduce the UE overhead for LCS","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue to consider to reduce the UE overhead for LCS","secretary_remarks":"Revision of S2-180136. Revised in parallel session to S2-181225.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22080,"status":"revised","reservation_date":"2018-01-25 11:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180136","revisedto":"S2-181225","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180909.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180910","title":"23.731: Key issue: support of hybrid positioning","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes new key issue 'support of hybrid positioning'.","secretary_remarks":"Revision of S2-180482. Revised in parallel session to S2-181226.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22110,"status":"revised","reservation_date":"2018-01-25 11:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180482","revisedto":"S2-181226","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180910.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180911","title":"23.731: Key Issue on Scalability for 5GC Location Enhancement","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"pCR","for":"Approval","abstract":"This contribution provides a P-CR to add a key issue to TR 23.731 on scalability for 5GC location enhancement.","secretary_remarks":"Revision of S2-180512. Agreed in parallel session. Block Approved","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22140,"status":"approved","reservation_date":"2018-01-25 11:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180512","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180911.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180912","title":"23.731: Key issue: position service exposure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes new key issue 'position service exposure'.","secretary_remarks":"Revision of S2-180483. Agreed in parallel session. Block Approved","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22160,"status":"approved","reservation_date":"2018-01-25 11:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180483","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180912.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180913","title":"23.731: Key Issue on IoT UEs for 5GC Location Enhancement","source":"Qualcomm Incorporated, AT&T","contact":"Hong Cheng","contact-id":25668,"tdoctype":"pCR","for":"Approval","abstract":"This contribution provides a P-CR to add a key issue to TR 23.731 on IoT UEs for 5GC location enhancement.","secretary_remarks":"Revision of S2-180514. Revised in parallel session to S2-181227.","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22180,"status":"revised","reservation_date":"2018-01-25 11:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180514","revisedto":"S2-181227","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180913.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180914","title":"SMS reachability monitoring correction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The change in TS 23.682 CR 0228 is partially reversed.","secretary_remarks":"Revision of S2-180623. Revised in parallel session to S2-181237.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10540,"status":"revised","reservation_date":"2018-01-25 11:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180623","revisedto":"S2-181237","release":"Rel-13","crspec":23.682,"crspecversion":"13.9.0","workitem":[{"winame":"MONTE"}],"crnumber":379.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180914.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180915","title":"SMS reachability monitoring correction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Rel-14 mirror CR: Summary of change: The change in TS 23.682 CR 0228 is partially reversed.","secretary_remarks":"Revision of S2-180624. Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10570,"status":"agreed","reservation_date":"2018-01-25 11:34:31","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180624","revisedto":"","release":"Rel-14","crspec":23.682,"crspecversion":"14.6.0","workitem":[{"winame":"MONTE"}],"crnumber":380.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-180084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180915.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180916","title":"SMS reachability monitoring correction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: The change in TS 23.682 CR 0228 is partially reversed.","secretary_remarks":"Revision of S2-180626. Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10590,"status":"agreed","reservation_date":"2018-01-25 11:34:32","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180626","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"MONTE"}],"crnumber":381.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-180084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180916.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180917","title":"Correction to cancelled monitoring Event in the network parameter configuration via SCEF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Decouple the procedures of Monitoring related procedure and network parameter configuration related procedure. If the HSS cancelled a monitoring event in step 4 and the cancelled monitoring event is subscribed by the SCEF which is the same as the one sending the Set Suggested Network Configuration Request, Cancelled SCEF Reference ID is included in the response and set to the SCEF Reference ID of the cancelled Monitoring Event. If the HSS cancelled a monitoring event in step 4 and the cancelled monitoring event is subscribed by the SCEF which is different from the SCEF sending the Set Suggested Network Configuration Request, HSS sends the Monitoring Indication message towards the SCEF which subscribed the cancelled monitoring event and includes SCEF Reference ID of a cancelled Monitoring Event. If the SCEF received Cancelled SCEF Reference ID in step 10\/10a, the steps 2-5 of Network-initiated Explicit Monitoring Event Deletion procdure defined in subclause 5.6.9 are","secretary_remarks":"Revision of S2-180505. For e-mail approval. e-mail revision 2 approved. Revised to S2-181394.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11040,"status":"revised","reservation_date":"2018-01-25 11:34:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180505","revisedto":"S2-181394","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":378.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180917.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180918","title":"Addition of EC restriction parameter in S1 AP PAGING message","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The requested EC Restriction parameter is added in the S1 AP PAGING message","secretary_remarks":"Revision of S2-180833. Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10180,"status":"agreed","reservation_date":"2018-01-25 11:34:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180833","revisedto":"","release":"Rel-14","crspec":23.401,"crspecversion":"14.6.0","workitem":[{"winame":"CIoT_Ext"}],"crnumber":3394.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180085","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180918.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180919","title":"[DRAFT] Reply LS on Paging in case of Enhanced Coverage Restriction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to explain that EC Restricted parameter is included in S1 PAGING alreary in Rel-14.","secretary_remarks":"Revision of S2-180835. Revised in parallel session to S2-181236.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10230,"status":"revised","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180835","revisedto":"S2-181236","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180919.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180920","title":"Reply LS on indication of preferred CIoT network behaviour","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"Answer LS C1-175414","secretary_remarks":"Revision of S2-180843. Agreed in parallel session. Block Approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10930,"status":"approved","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180843","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180028","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180920.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180921","title":"23.724: Architectural assumptions","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Architectural assumptions and principles for this study","secretary_remarks":"Revision of S2-180825. Agreed in parallel session. Block Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20660,"status":"approved","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180825","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180921.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180922","title":"23.724: Key Issue on infrequent small data transmission","source":"Huawei, HiSilicon, InterDigital Inc, AT&T, Convida, Intel, Motorola Mobility, Lenovo, China Mobile, KPN","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue for small data transmission","secretary_remarks":"Revision of S2-180826. Revised in parallel session to S2-181244.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20690,"status":"revised","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180826","revisedto":"S2-181244","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180922.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180923","title":"23.724: Adding small data frequent communication key issue","source":"Ericsson, InterDigital Inc.","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Small data frequent communication key issue","secretary_remarks":"Revision of S2-180827. Revised in parallel session to S2-181245.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20750,"status":"revised","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180827","revisedto":"S2-181245","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180923.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180924","title":"23.503: UE policies granularity and UE assistance for policy evaluation.","source":"Ericsson, NEC, Lenovo","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that a URSP\/WLANSP rule contains an identifier and that the PCF can perform operations (add\/delete\/replace) per individual URSP\/WLANSP rule. The UE sends at initial registration the list of UE policies currently stored in the device and the PCF uses this information as input for policy decisitions.","secretary_remarks":"Revision of S2-180419, merging S2-180619 and S2-180564. Revised in parallel session, merging S2-180926, to S2-181040.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14570,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180419","revisedto":"S2-181040","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180924.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180925","title":"23.502: UE polices ack from UE","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following solution is proposed:  - - The UE sends back to the AMF a NAS message acknowledging the reception and storage of the UE policies.  - - In addition, to cover those error cases where the UE receives the NAS message from the AMF but has some error in the storing of the UE policies information, the UE may include in the ACK message with additional information about the error. If this optional IE is present in the ACK message, the AMF will send this error to the PCF (stage 3 will decide the message) and this will handle the error, e.g. updating UE context in the PCF accordingly and reattempting the sending of UE policies later on.","secretary_remarks":"Revision of S2-180469. Revised in parallel session to S2-180968.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14770,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180469","revisedto":"S2-180968","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180925.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180926","title":"23.503: UE Policy Delivery","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Store the UE Policy status in the UDR. There is no need to add a UE Policy ID.","secretary_remarks":"Revision of S2-180320. Merged into S2-181040. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14820,"status":"withdrawn","reservation_date":"2018-01-23 13:27:51","uploaded":null,"revisionof":"S2-180320","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180927","title":"23.503: Support for MCX Services in the PCC of 5G System","source":"FirstNet, AT&T, Motorola Solutions, Airwave","contact":"Ihab Guirguis","contact-id":65302,"tdoctype":"draftCR","for":"Approval","abstract":"This contribution proposes new subclause '6.1.3.xx Mission Critical Services support' to describe the support for MCX Services in the PCC of 5G System.","secretary_remarks":"Revision of S2-180457. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15900,"status":"approved","reservation_date":"2018-01-25 14:56:19","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180457","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180927.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180928","title":"23.502: Editorial correction to section 4.12.8","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Consolidate steps 4 and 5 in step 3 to match the corresponding figure","secretary_remarks":"Revision of S2-180091. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18350,"status":"approved","reservation_date":"2018-01-23 13:27:51","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180091","revisedto":"S2-181623","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180928.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180929","title":"23.501: Editorial corrections in clause 5.3.2.4 Support of a UE registered over both 3GPP and Non-3GPP access","source":"ETRI","contact":"Yooah Kang","contact-id":63871,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution proposes editorial updates in clause 5.3.2.4 to support a Implicit Deregistration timer for either 3GPP or non-3GPP access.","secretary_remarks":"Revision of S2-180569. Revised in parallel session to S2-181014.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18390,"status":"revised","reservation_date":"2018-01-23 13:27:51","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180569","revisedto":"S2-181014","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180929.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180930","title":"23.502: Establishment Cause for Non-3GPP Access","source":"Motorola Mobility, Lenovo","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Specify the contents of AN Parameters (including the Establishment Cause) when sent over non-3GPP access.","secretary_remarks":"Revision of S2-180611. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18420,"status":"approved","reservation_date":"2018-01-23 13:27:51","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180611","revisedto":"S2-181640","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180930.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180931","title":"23.501: Corrections to Combined N3IWF\/ePDG Selection","source":"Motorola Mobility, Lenovo, Qualcomm Incorporated","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The Combined N3IWF\/ePDG Selection procedure is clarified. Also, we believe that the use of the 'preference' parameter is enough for selecting between N3IWF and ePDG and therefore the relevant EN is deleted.","secretary_remarks":"Revision of S2-180612, merging S2-180190. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18460,"status":"approved","reservation_date":"2018-01-23 13:27:51","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180612","revisedto":"S2-181641","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180931.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180932","title":"Clarification on additional IP address","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removes the example with deprecated I-WLAN.  Clarifies that in this release the additional IP address that can be used as contact address in additional IMS registration can only come from another system (i.e. outside of EPS in Annex E; outside of 5GS in Annex Y).","secretary_remarks":"Revision of S2-180741. Agreed in parallel session. Block Approved","agenda_item_sort_order":11,"ainumber":"5.4","ainame":"IMS and IMS-Related Maintenance","tdoc_agenda_sort_order":10850,"status":"agreed","reservation_date":"2018-01-23 16:34:27","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180741","revisedto":"","release":"Rel-15","crspec":23.228,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1187.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180094","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180932.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180933","title":"23.794: Baseline References and Definitions for eIMS5g TR","source":"T-Mobile USA INC","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Provides some initial text for Reference and Definition clauses of eIMS5G TR","secretary_remarks":"Revision of S2-180493. Agreed in parallel session. Block Approved","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22220,"status":"approved","reservation_date":"2018-01-23 16:34:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180493","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180933.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180934","title":"23.794: Scope and Architectural Assumptions of eIMS5G Study","source":"T-Mobile USA INC, Ericsson","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Proposes text for the scope and architectural assumptions clauses of the eIMS5G report.","secretary_remarks":"Revision of S2-180495. Revised in parallel session to S2-181032.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22240,"status":"revised","reservation_date":"2018-01-23 16:34:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180495","revisedto":"S2-181032","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180934.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180935","title":"23.794: Key Issues for FS_eIMS5G Localized UPF","source":"T-Mobile USA INC, Intel, AT&T","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Proposes two key issues related to localized UPF and IMS","secretary_remarks":"Revision of S2-180492. Revised in parallel session to S2-181033.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22290,"status":"revised","reservation_date":"2018-01-23 16:34:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180492","revisedto":"S2-181033","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180935.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180936","title":"23.794: Key Issues for FS_eIMS5G slicing","source":"T-Mobile USA INC, Huawei, HiSilicon, ZTE, China Mobile, Nokia, Nokia Shanghai Bell","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Proposes a key issue related to network slicing and IMS","secretary_remarks":"Revision of S2-180499, merging S2-180496, S2-180562, S2-180714 and S2-180748. Revised in parallel session to S2-181034.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22330,"status":"revised","reservation_date":"2018-01-23 16:34:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180499","revisedto":"S2-181034","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180936.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180937","title":"23.794: New Key issue : Cx Replacement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This document proposes a new key issue for FS_eIMS5G.","secretary_remarks":"Revision of S2-180096. Revised in parallel session to S2-181035.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22390,"status":"revised","reservation_date":"2018-01-23 16:34:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180096","revisedto":"S2-181035","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180937.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180938","title":"23.794: New Key Issues: Support of Service Based Interfaces","source":"Huawei, HiSilicon, China Mobile","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes new key issues for eIMS5G SI, in order to investigate the necessary IMS enhancements to support SBI provided by 5GC.","secretary_remarks":"Revision of S2-180497, merging S2-180713. Revised in parallel session to S2-181037.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22480,"status":"revised","reservation_date":"2018-01-23 16:34:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180497","revisedto":"S2-181037","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180938.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180939","title":"23.794: Key Issue on IMS use of NRF","source":"Ericsson, Huawei","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This document proposes a new key issue for FS_eIMS5G","secretary_remarks":"Revision of S2-180097. Agreed in parallel session. Block Approved","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22420,"status":"approved","reservation_date":"2018-01-23 16:34:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180097","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180939.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180940","title":"23.794: New Key Issue : Sh Replacement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This document proposes a new key issue for FS_eIMS5G","secretary_remarks":"Revision of S2-180098. Revised in parallel session to S2-181036.","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22440,"status":"revised","reservation_date":"2018-01-23 16:34:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180098","revisedto":"S2-181036","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180940.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180941","title":"23.502: Revision on Service Request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Propose that UE can start the Service Request Procedure even none of the PDU sessions can be transferred to 3GPP access.","secretary_remarks":"Revision of S2-180590. Revised in parallel session to S2-181015.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18500,"status":"revised","reservation_date":"2018-01-23 16:34:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180590","revisedto":"S2-181015","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180941.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180942","title":"23.501: Alignment with TS23.502 on Service Request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It has been replaced the optional indication of the PDU session to be reactivated with the mandatory list of PDU session to be reactivated","secretary_remarks":"Revision of S2-180591. Revised in parallel session to S2-181017.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18760,"status":"revised","reservation_date":"2018-01-23 16:34:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180591","revisedto":"S2-181017","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180942.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180943","title":"[draft] Reply LS to CT WG1 on 5G service request procedure","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"LS Reply to CT WG1 to response the issue of 5G service request procedure","secretary_remarks":"Revision of S2-180592. Revised in parallel session to S2-181016.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18540,"status":"revised","reservation_date":"2018-01-23 16:34:28","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180592","revisedto":"S2-181016","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180943.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180944","title":"23.502: Removal of editor's notes in clause 4.12","source":"Nokia, Nokia Shanghai Bell","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Editor's note in 4.12 is removed. Details of PDU Session Release Request and Command are documented and aligned to 3GPP access corresponding procedure.","secretary_remarks":"Revision of S2-180459. Revised in parallel session to S2-181018.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18580,"status":"revised","reservation_date":"2018-01-23 16:34:29","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180459","revisedto":"S2-181018","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180944.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180945","title":"23.502: Clarification on paging when it is related with both 3GPP and non-3GPP PDU Session","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarify that if the AMF receives multiple request associated with 3GPP and non-3GPP access at the same time, the AMF sends a Paging message with associated access 'non-3GPP' to RAN node(s) via 3GPP access.  2. Clarify that the AMF behaviour when it receives another message for 3GPP (or non-3GPP) PDU Session while waiting for a UE response for the non-3GPP (or 3GPP) PDU Session.  3. Clarify that the UE initiates UE Triggered Service Request procedure when it receives paging request for a PDU Session associated with non-3GPP access even if there is no PDU Session that can be re-activated over the 3GPP access.","secretary_remarks":"Revision of S2-180519. Revised in parallel session to S2-181019.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18630,"status":"revised","reservation_date":"2018-01-23 16:34:29","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180519","revisedto":"S2-181019","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180945.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180946","title":"[DRAFT] LS on UE behaviour when it received paging associated with non-3GPP access","source":"SA WG2","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-180945","secretary_remarks":"Created in parallel session Revised in parallel session to S2-181020.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18650,"status":"revised","reservation_date":"2018-01-23 16:34:29","uploaded":"2018-01-26 18:07:53","revisionof":"","revisedto":"S2-181020","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180946.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180947","title":"23.502: Clarification on handover applicability between 3GPP and non-3GPP accesses","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify how the AMF decides whether a PDU Session can be handed over to the other access when a PDU Session is established as a Home Routed mode.","secretary_remarks":"Revision of S2-180520. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18680,"status":"approved","reservation_date":"2018-01-23 16:34:29","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180520","revisedto":"S2-181508","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180947.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180948","title":"23.502: Adding missing text about UE policies related to Service Request including the List Of Allowed PDU Sessions","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding 'if allowed by UE policies' to the description related to the UE Triggered Service Request procedure in response to paging indicating non-3GPP access in step 6 of clause 4.2.3.3","secretary_remarks":"Revision of S2-180544. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18700,"status":"approved","reservation_date":"2018-01-23 16:34:29","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180544","revisedto":"S2-181498","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180948.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180949","title":"23.502: Updating Network Triggered Service Request to support selective re-activation of PDU session over non-3GPP access","source":"ETRI","contact":"Yooah Kang","contact-id":63871,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution proposes to update Network Triggered Service Request procedure to support selective re-activation of PDU session over non-3GPP access.","secretary_remarks":"Revision of S2-180571. Revised in parallel session to S2-181021.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18730,"status":"revised","reservation_date":"2018-01-23 16:34:29","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180571","revisedto":"S2-181021","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180949.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180950","title":"23.502: Clarification on 5G-GUTI in EPS to 5GS Mobility Registration Procedure using N26","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) The following clarification is made regarding in step 2 when the UE includes the native 5G-GUTI and the GUAMI part of the native 5G-GUTI in the Registration request and RRC, respectively: When the native 5G-GUTI is assigned during a Registration procedure performed over a non-3GPP access, the UE includes the native 5G-GUTI as an additional GUTI in the Registration Request and for idle mode mobility the GUAMI part of the native 5G-GUTI in RRC only if the 3GPP access that the UE registers is in the same PLMN for the non-3GPP access that the UE is registered.  2) Re-wording is made for clarity in steps 17-18 regarding when the UE uses the updated 5G-GUTI in the Registration Accept:","secretary_remarks":"Revision of S2-180543. Revised in parallel session to S2-181022.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18820,"status":"revised","reservation_date":"2018-01-23 16:34:29","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180543","revisedto":"S2-181022","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180950.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180951","title":"Emergency services over 5GC via untrusted non-3GPP access","source":"Nokia, Nokia Shanghai Bell","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The case emergency sessions over 5GC via non-3GPP untrusted access is added to existing clauses 4.3.1 and 4.4.  A new annex for this case is added.","secretary_remarks":"Revision of S2-180458. Revised in parallel session to S2-181023.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18880,"status":"revised","reservation_date":"2018-01-23 16:34:29","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180458","revisedto":"S2-181023","release":"Rel-15","crspec":23.167,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":320.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180951.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180952","title":"23.501: Clarification on emergency services for non-3GPP access","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarify that if the 3GPP access become available after UE has establish the emergency session over the non-3GPP, whether UE transfers the emergency session to the 3GPP access depends on UE decision that are implementation dependent.  2. Remove the sentence 'For emergency registered UEs on untrusted Non-3GPP access, the UE is only reachable in CM-CONNECTED state: since the UE has initiated an emergency registration over untrusted Non-3GPP access only when it is not possible over 3GPP access, 3GPP access is assumed to be unavailable for paging the UE'.","secretary_remarks":"Revision of S2-180588. Noted in parallel session","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18920,"status":"noted","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180588","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180952.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180953","title":"23.726: FS_ETSUN \/ 23.726 Scope","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"pCR","for":"Approval","abstract":"FS_ETSUN \/ 23.726 Scope, references and abbreviations","secretary_remarks":"Revision of S2-180058. Revised in parallel session to S2-181046.","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21660,"status":"revised","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180058","revisedto":"S2-181046","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180953.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180954","title":"23.726: FS_ETSUN \/ 23.726 Key Issue: Support of the preservation of a PDU session while the UE moves out of an SMF service area","source":"Nokia, Nokia Shanghai Bell, Ericsson (0413)?, CATT (0551)?, Huawei (0351)?","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"pCR","for":"Approval","abstract":"FS_ETSUN \/ 23.726 Key Issue: Support of the preservation of a PDU session while the UE moves out of an SMF service area","secretary_remarks":"Revision of S2-180060, merging S2-180413, S2-180351 and S2-180551. Revised in parallel session to S2-181048.","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21690,"status":"revised","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180060","revisedto":"S2-181048","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180954.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180955","title":"23.726: Key Issue Proposal: SMF and UPF Insert\/Relocation due to UE Mobility","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"In this contribution, it is proposed a new key issue to study the SMF and UPF insert or relocation due to UE mobility.","secretary_remarks":"Revision of S2-180609. Revised in parallel session to S2-181047.","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21820,"status":"revised","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180609","revisedto":"S2-181047","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180955.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180956","title":"23.726: Key Issue for allocating IP addresses for complex topologies","source":"T-Mobile USA INC, Nokia, Nokia Shanghai Bell, Cisco","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Describes a new key issue for regarding the allocation of IP addresses for complex SMF and UPF topologies","secretary_remarks":"Revision of S2-180504, merging S2-180061. Agreed in parallel session. Block Approved","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21790,"status":"approved","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180504","revisedto":"","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180956.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180957","title":"23.726: KI-Study UPF capabilities to be controlled by multiple UPFs","source":"Samsung","contact":"Jayshree Bharatia","contact-id":63826,"tdoctype":"pCR","for":"Approval","abstract":"Suggests inclusion of KI which is related to the UPF controlled by multiple SMFs.","secretary_remarks":"Revision of S2-180758. Agreed in parallel session. Block Approved","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21770,"status":"approved","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180758","revisedto":"","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180957.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180958","title":"23.787: FS_ENTRADE - Skeleton of TR 23.787","source":"China Unicom","contact":"Chi Ren","contact-id":72309,"tdoctype":"pCR","for":"Approval","abstract":"The skeleton of TR 23.787 Study on encrypted traffic detection and verification","secretary_remarks":"Revision of S2-180260. Agreed in parallel session. Block Approved","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21220,"status":"approved","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180260","revisedto":"","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180958.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180959","title":"23.787: FS_ENTRADE - Scope of TR 23.787","source":"China Unicom, OPPO","contact":"Chi Ren","contact-id":72309,"tdoctype":"pCR","for":"Approval","abstract":"The scope of TR 23.787 Study on encrypted traffic detection and verification.","secretary_remarks":"Revision of S2-180261. Agreed in parallel session. Block Approved","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21240,"status":"approved","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180261","revisedto":"","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180959.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180960","title":"23.787: Architectural Assumptions for ENTRADE","source":"Qualcomm incorporated, Motorola Mobility, Lenovo","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes architectural assumptions for ENTRADE","secretary_remarks":"Revision of S2-180195. Revised in parallel session to S2-181030.","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21260,"status":"revised","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180195","revisedto":"S2-181030","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180960.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180961","title":"23.787: Key Issue - Management of encrypted traffic detection and verification information","source":"China Unicom, OPPO","contact":"Chi Ren","contact-id":72309,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue (i.e. management of encrypted traffic detection and verification information) for FS_ENTRADE.","secretary_remarks":"Revision of S2-180262, merging S2-180610 and S2-180196. Revised in parallel session, merging S2-180962, to S2-181031.","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21290,"status":"revised","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180262","revisedto":"S2-181031","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180961.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180962","title":"23.787: Key Issue interworking for encrypted traffic detection","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"pCR","for":"Approval","abstract":"This proposes a KI for ENTRADE study","secretary_remarks":"Revision of S2-180378. Merged into S2-181031","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21330,"status":"merged","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180378","revisedto":"","release":"Rel-16","crspec":23.787,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180962.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180963","title":"23.787: ENTRADE: Key Issue On Encrypted Traffic Detection for Applications without SLA between MNO and AS","source":"Qualcomm incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"pCR","for":"Approval","abstract":"Abstract of the contribution: This contribution proposes a key issue studying the encrypted traffic detection for applications that are not 'integrated' with an MNO network and cannot rely on an SLA and interfacing between the AS and the operator MNO","secretary_remarks":"Revision of S2-180197. Agreed in parallel session. Block Approved","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21370,"status":"approved","reservation_date":"2018-01-24 06:42:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180197","revisedto":"","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180963.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180964","title":"23.787: Solution for UE assisted enrypted traffic detection","source":"OPPO. China Unicom","contact":"Yang Xu","contact-id":63572,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a solution for encrypted traffic detection and verification.","secretary_remarks":"Revision of S2-180376. Withdrawn in parallel session (not provided).","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21390,"status":"withdrawn","reservation_date":"2018-01-24 06:42:53","uploaded":null,"revisionof":"S2-180376","revisedto":"","release":"Rel-16","crspec":23.787,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180965","title":"23.502: UE assisted UE policies calculation in PCF","source":"Ericsson, NEC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The UE includes in the Initial Registration procedure a list of ruleIds identifying the UE Policy rules (WLANSP and URSP rules) stored in the UE. At initial registration the PCF calculates the UE policy rules that apply to the UE in the current conditions and compares this information with the one received from the UE to determine the UE policy rules that need to be downloaded to the UE (avoiding the sending of duplicated UE policy rules to the UE).","secretary_remarks":"Revision of S2-180420, merging S2-180618 and S2-180566. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14750,"status":"approved","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180420","revisedto":"S2-181888","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180965.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180966","title":"23.503: Description of components in URSP","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Filling the description of the components. 2. Multiple Route Selection Descriptors in one URSP rule.  3. Non-Seamless Offload indication doesn't coexist with other component.","secretary_remarks":"Revision of S2-180129, merging S2-180404. Revised in parallel session to S2-181041.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14620,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180129","revisedto":"S2-181041","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180966.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180967","title":"23.503: Additional PDU Session Type in Route Selection Descriptor","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the PDU Type as a component in the URSP rule.","secretary_remarks":"Revision of S2-180130. Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14650,"status":"postponed","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180130","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180967.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180968","title":"23.502: UE polices ack from UE","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following solution is proposed:  - - The UE sends back to the AMF a NAS message acknowledging the reception and storage of the UE policies.  - - In addition, to cover those error cases where the UE receives the NAS message from the AMF but has some error in the storing of the UE policies information, the UE may include in the ACK message with additional information about the error. If this optional IE is present in the ACK message, the AMF will send this error to the PCF (stage 3 will decide the message) and this will handle the error, e.g. updating UE context in the PCF accordingly and reattempting the sending of UE policies later on.","secretary_remarks":"Revision of S2-180925. Revised in parallel session to S2-181042.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14780,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180925","revisedto":"S2-181042","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180968.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180969","title":"23.502: Update of Npcf_SMPolicyControl service","source":"Oracle, ZTE, Ericsson, Sandvine, Openet","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes the addition of event subscription and event notification to the Npcf_SMPolicyControl service to address the concerns raised above. NOTE: This does NOT impact the Nsmf_EventExposure Service! AMF, AF\/NEF and\/or any other consumer can still use this service as is, as long as the SMF simply notifies subscribers of events in a 'fire and forget' fashion. Update 23.502 Npcf_SMPolicyControl service to enable the PCF to subscribe to event notifications and to receive event notifications from the SMF:  - Update the optional input parameters of the Npcf_SMPolicyControl_Get service operation to provide event notification (in the case of SMF initiated modifications). - Update the optional output parameters of the Npcf_SMPolicyControl_Get service operation to subscribe to event triggers. - Update the optional input parameters of the Npcf_SMPolicyControl_UpdateNotify service operation with subscription to event triggers.","secretary_remarks":"Revision of S2-180168. Revised in parallel session to S2-181010.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14850,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180168","revisedto":"S2-181010","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180969.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180970","title":"23.502: Update of Npcf_AMPolicyControl service","source":"Oracle, ZTE, Ericsson, Sandvine, Openet","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes the addition of event subscription and event notification to the Npcf_AMPolicyControl service to address the concerns raised above. NOTE: This does NOT impact the Namf_EventExposure Service! SMF, AF\/NEF, UDM, GMLC and\/or any other consumer can still use this service as is, as long as the AMF simply notifies subscribers of events in a 'fire and forget' fashion.  Update 23.502 Npcf_AMPolicyControl service to enable the PCF to subscribe to event notifications and to receive event notifications from the AMF:  - Update the optional input parameters of the Npcf_AMPolicyControl_Get service operation to provide event notification (in the case of AMF initiated modifications). - Update the optional output parameters of the Npcf_AMPolicyControl_Get service operation to subscribe to event triggers. - Update the optional input parameters of the Npcf_AMPolicyControl_UpdateNotify service operation with subscription to event triggers.","secretary_remarks":"Revision of S2-180170. Revised in parallel session to S2-181011.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14880,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180170","revisedto":"S2-181011","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180970.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180971","title":"23.502: Update of Session Management Policy Establishment procedure","source":"Oracle, ZTE, Ericsson, Sandvine, Openet","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Session Management Policy Establishment procedure based on the Npcf_SMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_SMPolicyControl service.doc'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the SMF by using the Npcf_SMPolicyControl service. This can be done in step 5. Consequently steps 6 and 7 are not needed, and so are removed from the procedure.","secretary_remarks":"Revision of S2-180171. Revised in parallel session to S2-181012.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14910,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180171","revisedto":"S2-181012","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180971.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180972","title":"23.502: Update of Session Management Policy Modification procedure","source":"Oracle, ZTE, Ericsson, Sandvine, Openet","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Session Management Policy Modification procedure based on the Npcf_SMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_SMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the SMF by using the Npcf_SMPolicyControl service. Specifically event notification from SMF to PCF can be done in step 1a by using the Npcf_SMPolicyControl_Get service operation. Step 2a may include subscription by the PCF to Event Triggers by using the response to the Npcf_SMPolicyControl_Get service operation. Similarly, Step 5 may include subscription by the PCF to Event Triggers by using the pcf_SMPolicyControl_UpdateNotify service operation.Consequently steps 7 and 8 are not needed, and so are removed from the procedure. On top of that it makes more sense now to split the procedure into two procedures: Session Management Policy Modifi","secretary_remarks":"Revision of S2-180173. Revised in parallel session to S2-181013.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14940,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180173","revisedto":"S2-181013","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180972.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180973","title":"23.502: Update of Policy Association Establishment during Registration procedure","source":"SA WG2","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Association Establishment during Registration procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. This can be done in step 3. Consequently steps 6 and 7 are not needed, and so are removed from the procedure.","secretary_remarks":"Revision of S2-180174. Postponed in parallel session.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14970,"status":"postponed","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180174","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180973.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180974","title":"23.502: Update of Policy Association Establishment during AMF relocation procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Association Establishment during AMF relocation procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. This can be done in step 3. Consequently steps 5 and 6 are not needed, and so are removed from the procedure.","secretary_remarks":"Revision of S2-180175. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14990,"status":"withdrawn","reservation_date":"2018-01-24 10:28:33","uploaded":null,"revisionof":"S2-180175","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180975","title":"23.502: Update of Policy Association Modification for Mobility Policy procedure","source":"Oracle, ZTE, Ericsson? ,Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Associationt Modification for Mobility Policy procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. This can be done in steps 1(receive event notifications) and 2(subscribe to event notifications) respectively. Consequently steps 4 and 5 are not needed, and so are removed from the procedure. The policy decision is made right after step 1, and is denoted as step 2. Thus original step 2 is now step 3.","secretary_remarks":"Revision of S2-180176. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15010,"status":"withdrawn","reservation_date":"2018-01-24 10:28:33","uploaded":null,"revisionof":"S2-180176","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180976","title":"23.502: Update of Policy Association Modification for UE Policy and Access and Mobility control procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Association Modification for UE Policy and Access and Mobility control procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. Consequently, the procedure is split up into two procedures: 1. Update of Policy Association Modification for UE Policy and Access and Mobility control procedure triggered by the AMF 2. Update of Policy Association Modification for UE Policy and Access and Mobility control procedure triggered by the PCF. As part of it section numbers and step numbers were adjusted.","secretary_remarks":"Revision of S2-180177. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15030,"status":"withdrawn","reservation_date":"2018-01-24 10:28:33","uploaded":null,"revisionof":"S2-180177","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180977","title":"[DRAFT] LS reply on Clarification on Npcf_SMPolicyControl service","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply to CT WG3 LS proposing to select Option 1, i.e. use Npcf_SMPolicyControlGet to report modification of the association between the SMF and the PCF","secretary_remarks":"Revision of S2-180234. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14520,"status":"withdrawn","reservation_date":"2018-01-24 10:28:33","uploaded":null,"revisionof":"S2-180234","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180978","title":"23.501: Clarification on PCF selection","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Updating the PCF selection with the following proposals - The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF. - The SMF sends the PCF selected by the AMF to the SMF during the PDU session establishment procedure Fixing the typo in the clause 6.3.7.0","secretary_remarks":"Revision of S2-180303. Revised in parallel session to S2-181043.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15060,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180303","revisedto":"S2-181043","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180978.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180979","title":"23.502: Clarification on PCF association","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 4.2.2.2.2-1: Registration, step 5: Removing 'PCF ID' because it is already included in UE context exchanged for inter-AMF mobility. Step 16: change 'PCF ID' into '(V-)PCF ID' - 4.16.1.2: Policy Association Establishment during Registration, step 2: proposal for the roaming case: The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF - 4.16.1.3: Policy Association Establishment during AMF relocation, step 2: proposal for the roaming case: The V-PCF receiving the PCF ID from old AMF shall include the H-PCF ID in the Npcf_AMPolicyControl Get operation. - 4.16.3.2: AMF-initiated Policy Association Termination, step 1: removing the unnecessary text based on the agreement at SA WG2#124. - 5.2.2.2.2: Table 5.2.2.2.2-1: UE Context in AMF - adding 'PCF ID' based on the agreement at SA WG2#124, and additionally 'H-PCF ID' based on the proposal on V\/H-PCF selection by AMF","secretary_remarks":"Revision of S2-180304, merging S2-180644. Revised in parallel session to S2-181050.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15100,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180304","revisedto":"S2-181050","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180979.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180980","title":"23.503: Clarification PCF interaction","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 4.2.2: general clarification - 5.3.3: general clarification - 5.3.4: clarification on unclear description about roaming options, LBO and HR. HR or LBO should be referring to a particular PDU session instead of per UE. \u00e8 Proposing two alternatives. One should be selected. - 6.1.2.1: removing the unnecessary text based on the agreement at SA WG2#124. - 6.1.2.2, 6.1.2.2.1: general clarification","secretary_remarks":"Revision of S2-180305. Revised in parallel session to S2-181051.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15130,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180305","revisedto":"S2-181051","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180980.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180981","title":"23.501: Clarification on PCC support of EPC IWK","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: AMF unsubscribes the policy notification when UE doesn't camp on 5GS.  The combined PCF\/PCRF needs to provide PCC rule or policy information applied to EPC only in addition.  The combined SMF\/PGW-C performs the PCC rule or policy adaptation so that only the PCC rules or policy applied to either EPC or 5GC are enforced.","secretary_remarks":"Revision of S2-180435. Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15170,"status":"noted","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180435","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180981.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180982","title":"23.503: Remove EN related with EPC IWK","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Removes the EN in 6.1.3.5 2. Removes the EN in 6.3.1 and adds a NOTE to the removed attibutes for the clarification that they are provided for EPC IWK in Table 6.3.1 3. Adds 6.1.3.18 for the description on EPC IWK","secretary_remarks":"Revision of S2-180436. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15190,"status":"approved","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180436","revisedto":"S2-181790","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180982.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180983","title":"23.793: Key Issue 1 for ATSSS","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"pCR","for":"Approval","abstract":"This contribution discusses key issue 1 for ATSSS","secretary_remarks":"Revision of S2-180297. Approved","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20400,"status":"approved","reservation_date":"2018-01-24 15:03:36","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180297","revisedto":"","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180983.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180984","title":"23.793: Key Issue update for Traffic Splitting over Multi-access","source":"ZTE, Oracle, Convida Wireless","contact":"Tricci So","contact-id":44974,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes update to the key issue studying the traffic splitting over multi-access in ATSSS by referring to the real-life use case of MPTCP support by iOS.","secretary_remarks":"Revision of S2-180120. Revised to S2-181361.","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20440,"status":"revised","reservation_date":"2018-01-24 15:03:36","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180120","revisedto":"S2-181361","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180984.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180985","title":"23.793: Key Issue 4 for ATSSS","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"pCR","for":"Approval","abstract":"This contribution discusses key issue 4 for ATSSS","secretary_remarks":"Revision of S2-180298. For e-mail approval. WITHDRAWN","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20470,"status":"withdrawn","reservation_date":"2018-01-24 15:03:36","uploaded":null,"revisionof":"S2-180298","revisedto":"","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180986","title":"23.793: New KI and Alternative architecture framework for ATSSS","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue and an alternative architecture framework for ATSSS.","secretary_remarks":"Revision of S2-180498. Revised to S2-181362.","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20500,"status":"revised","reservation_date":"2018-01-24 15:03:36","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180498","revisedto":"S2-181362","release":"Rel-16","crspec":23.793,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180986.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180987","title":"23.793: Establishment of MA-PDU Sessions","source":"Motorola Mobility, Lenovo","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"pCR","for":"Approval","abstract":"This document proposes to add a new solution in TR 23.793 that addresses Key Issue#5: Multi-access PDU sessions (Un-trusted access). The solution aims at supporting Multi-Access PDU sessions, which can be a key enabler for the ATSSS feature.","secretary_remarks":"Revision of S2-180273. Approved","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20530,"status":"approved","reservation_date":"2018-01-24 15:03:36","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180273","revisedto":"","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180987.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180988","title":"23.503: Remove some ENs","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove the above referred ENs.","secretary_remarks":"Revision of S2-180277. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15230,"status":"approved","reservation_date":"2018-01-25 06:55:17","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180277","revisedto":"S2-181791","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180988.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180989","title":"23.503: Removal of editor's notes and addition of references to empty sections","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to remove those editor's notes.  The following empty sections are proposed to be filled with a description or reference to a description in TS 23.203:  - 4.2.4 Management of packet flow descriptions,  - 6.1.3.16 3GPP PS Data Off,  - 6.2.4 Unified Data Repository,  - 6.2.7 Network Exposure Function.","secretary_remarks":"Revision of S2-180324, merging S2-180276. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15250,"status":"approved","reservation_date":"2018-01-25 06:55:17","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180324","revisedto":"S2-181576","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180989.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180990","title":"23.502: Handling of AMF and PCF interaction when there is a PLMN change during AMF relocation.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the registration procedure to reflect that when there is AMF relocation and the new AMF is in a different PLMN, the old AMF does not transfer the PCF ID nor the AM policy information and the event triggers subscribed by the PCF. The old AMF terminates the policy association to the PCF.","secretary_remarks":"Revision of S2-180182. Merged into S2-181054","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15280,"status":"merged","reservation_date":"2018-01-25 06:55:17","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180182","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180990.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180991","title":"23.502: Correction on the Policy association procedure during AMF relocation","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Reclassified the Policy Association Establishment procedure into two cases: a) Policy Association Establishment procedure with new PCF (No UE context); b) Policy Association Establishment procedure with old PCF (Has UE context). 2. Update the existing description for the procedure that old PCF is used. 3. Update the description about the Policy Association Establishment procedure in registration.","secretary_remarks":"Revision of S2-180321. Revised in parallel session, merging S2-180990, to S2-181054.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15300,"status":"revised","reservation_date":"2018-01-25 06:55:17","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180321","revisedto":"S2-181054","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180991.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180992","title":"23.502: Cleanup of NamfEventExposure and NsmfEventExposure services","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Definition of a services, Namf_EventExposure and Nsmf_EventExposure are clarified.","secretary_remarks":"Revision of S2-180183. Revised to S2-181387.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15340,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180183","revisedto":"S2-181387","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180992.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180993","title":"23.503: Influence of additional non-standardized QoS parameters on QoS Flow Binding","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The additional AW\/MDBV added into PCC Rule information and considered during QoS Flow Binding.","secretary_remarks":"Revision of S2-180284. Revised in parallel session to S2-181055.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15370,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180284","revisedto":"S2-181055","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180993.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180994","title":"23.503: QoS rule generation","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify each QoS rule provided by SMF is generated from a PCC rule. The default QoS rule is generated by SMF based on the authorized default 5QI and ARP received from PCF, if a Packet Filter Set is included in the default QoS rule, the PCF may provide a default Packet Filter Set in the PDU Session related policy information to SMF. Clarify for a PDU session of unstructured type, no PCC Rule is provided to SMF. SMF generates the default QoS rule based on the authorized default 5QI and ARP received in the PDU Session related policy information.","secretary_remarks":"Revision of S2-180253. Revised in parallel session to S2-181056.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15400,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180253","revisedto":"S2-181056","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180994.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180995","title":"23.501: Resource reservation for services sharing priority","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update clause 5.22 to indicate that the service layer can provide instructions on how to perform pre-emption of media flows when no resources are available.","secretary_remarks":"Revision of S2-180081. Endorsed","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15430,"status":"endorsed","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180081","revisedto":"S2-181615","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180995.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180996","title":"23.503: Resource reservation for services sharing priority","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: PCF functional description of resource reservation for service sharing priority is updated to align with the functional description of this feature in TS 23.203.","secretary_remarks":"Revision of S2-180082. Agreed in parallel session.  Wrong document uploaded. Revised to S2-181391","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15450,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180082","revisedto":"S2-181391","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180996.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180997","title":"23.502: Selecting a common PCF for UE and Session Policies","source":"Cisco Systems, Inc","contact":"Ravi Shekhar","contact-id":71185,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Optionally, passing the selected PCF Id by AMF to SMF.","secretary_remarks":"Revision of S2-180250. For e-mail approval. e-mail revision 1 approved. Revised to S2-181401.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15480,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180250","revisedto":"S2-181401","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180997.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180998","title":"23.502: PCF selection for AMF during inter NG-RAN node N2 based handover","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: During the inter NG-RAN node N2 handover procedure, the S-AMF should provides the PCF ID to T-AMF for PCF selection.","secretary_remarks":"Revision of S2-180322. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15510,"status":"approved","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180322","revisedto":"S2-181574","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180998.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180999","title":"23.502: Correction on PCF selection in SMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Add description about the AMF provide PCF information to SMF for PCF selection in PDU session management related procedures. 2. Correct the service name of step 3a and 5 in figure 4.3.2.2.1.","secretary_remarks":"Revision of S2-180323. Revised to S2-181388.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15530,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180323","revisedto":"S2-181388","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180999.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181000","title":"[DRAFT] Reply LS on clarification on Restricted Operator Services","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG1, SA WG3. CC: CT WG1","secretary_remarks":"Created in parallel session. Response to S2-180043. Revised in parallel session to S2-181045.","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22610,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180043","revisedto":"S2-181045","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG3","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181000.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181001","title":"23.715: Update of RLOS architectural assumptions","source":"Nokia, Nokia Shanghai Bell, Verizon","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes modifications to RLOS architectural assumptions, based on the recent response from SA WG1 in LS S1-174602","secretary_remarks":"Revision of S2-180461. Agreed in parallel session. Block Approved","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22660,"status":"approved","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180461","revisedto":"","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181001.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181002","title":"23.715: Update to Key issue IMS#1","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes an update to key issue IMS#1 to align more with the SA WG1 requirements and TR 22820 issued by SA WG1 in support of RLOS services","secretary_remarks":"Revision of S2-180084. Agreed in parallel session. Block Approved","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22680,"status":"approved","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180084","revisedto":"","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181002.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181003","title":"23.715: Update to Key issue EPC#3","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This contribution clarifies the scope of support for unauthenticated UEs for Key issue EPC#3 to access RLOS services only.","secretary_remarks":"Revision of S2-180085. Agreed in parallel session. Block Approved","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22700,"status":"approved","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180085","revisedto":"","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181003.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181004","title":"23.715: Update of RLOS key issues","source":"Nokia, Nokia Shanghai Bell, Verizon","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes modifications to RLOS key issues, based on the recent response from SA WG1 in LS S1-174602.","secretary_remarks":"Revision of S2-180462. Revised in parallel session to S2-181044.","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22730,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180462","revisedto":"S2-181044","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181004.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181005","title":"23.503: Remove EN related with Session binding","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. \u00a7 6.1.3.2.2: Session Binding applies only for PDU Sessions of IP type 2. \u00a7 6.1.1.2: remove the EN and add that S-NSSAI is part of the data used for session binding 3. Clarifications and Editorials:.","secretary_remarks":"Revision of S2-180132, merging S2-180076. Revised to S2-181389.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15640,"status":"revised","reservation_date":"2018-01-25 14:56:19","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180132","revisedto":"S2-181389","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181005.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181006","title":"LS on the definition of the Nocs spending limit report service","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG5. CC: CT WG3. Attachments: S2-180211, S2-180210","secretary_remarks":"Created in parallel session. For e-mail approval. Noted","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15680,"status":"noted","reservation_date":"2018-01-25 14:56:19","uploaded":"2018-01-26 18:07:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181006.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181007","title":"23.502: Correction for event trigger report from SMF","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify the affected PCC rules and the QoS request for specific SDFs received from UE may be included in the Nsmf_EventExposure_Notify service","secretary_remarks":"Revision of S2-180254. This was withdrawn.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15760,"status":"withdrawn","reservation_date":"2018-01-25 14:56:19","uploaded":null,"revisionof":"S2-180254","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181008","title":"23.502: Correction of Npcf_BDTPolicyControl (background data transfer)","source":"KDDI","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Added the Background Data Transfer policy reference ID and the description for step 9","secretary_remarks":"Revision of S2-180634. This was endorsed.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15730,"status":"endorsed","reservation_date":"2018-01-25 14:56:19","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180634","revisedto":"S2-181480","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181008.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181009","title":"23.502: Correction of UDR usage in policy related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that PCF invoke UDR services are clarified in policy related procedures.","secretary_remarks":"Revision of S2-180757. This was endorsed.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15960,"status":"endorsed","reservation_date":"2018-01-25 14:56:19","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180757","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181009.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181010","title":"23.502: Update of Npcf_SMPolicyControl service","source":"Oracle, ZTE, Ericsson, Sandvine, Openet","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes the addition of event subscription and event notification to the Npcf_SMPolicyControl service to address the concerns raised above. NOTE: This does NOT impact the Nsmf_EventExposure Service! AMF, AF\/NEF and\/or any other consumer can still use this service as is, as long as the SMF simply notifies subscribers of events in a 'fire and forget' fashion. Update 23.502 Npcf_SMPolicyControl service to enable the PCF to subscribe to event notifications and to receive event notifications from the SMF:  - Update the optional input parameters of the Npcf_SMPolicyControl_Get service operation to provide event notification (in the case of SMF initiated modifications). - Update the optional output parameters of the Npcf_SMPolicyControl_Get service operation to subscribe to event triggers. - Update the optional input parameters of the Npcf_SMPolicyControl_UpdateNotify service operation with subscription to event triggers.","secretary_remarks":"Revision of S2-180969. Postponed in parallel session.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14860,"status":"postponed","reservation_date":"2018-01-25 14:56:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180969","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181010.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181011","title":"23.502: Update of Npcf_AMPolicyControl service","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes the addition of event subscription and event notification to the Npcf_AMPolicyControl service to address the concerns raised above. NOTE: This does NOT impact the Namf_EventExposure Service! SMF, AF\/NEF, UDM, GMLC and\/or any other consumer can still use this service as is, as long as the AMF simply notifies subscribers of events in a 'fire and forget' fashion.  Update 23.502 Npcf_AMPolicyControl service to enable the PCF to subscribe to event notifications and to receive event notifications from the AMF:  - Update the optional input parameters of the Npcf_AMPolicyControl_Get service operation to provide event notification (in the case of AMF initiated modifications). - Update the optional output parameters of the Npcf_AMPolicyControl_Get service operation to subscribe to event triggers. - Update the optional input parameters of the Npcf_AMPolicyControl_UpdateNotify service operation with subscription to event triggers.","secretary_remarks":"Revision of S2-180970. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14890,"status":"withdrawn","reservation_date":"2018-01-25 14:56:31","uploaded":null,"revisionof":"S2-180970","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181012","title":"23.502: Update of Session Management Policy Establishment procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Session Management Policy Establishment procedure based on the Npcf_SMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_SMPolicyControl service.doc'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the SMF by using the Npcf_SMPolicyControl service. This can be done in step 5. Consequently steps 6 and 7 are not needed, and so are removed from the procedure.","secretary_remarks":"Revision of S2-180971. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14920,"status":"withdrawn","reservation_date":"2018-01-25 14:56:31","uploaded":null,"revisionof":"S2-180971","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181013","title":"23.502: Update of Session Management Policy Modification procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Session Management Policy Modification procedure based on the Npcf_SMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_SMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the SMF by using the Npcf_SMPolicyControl service. Specifically event notification from SMF to PCF can be done in step 1a by using the Npcf_SMPolicyControl_Get service operation. Step 2a may include subscription by the PCF to Event Triggers by using the response to the Npcf_SMPolicyControl_Get service operation. Similarly, Step 5 may include subscription by the PCF to Event Triggers by using the pcf_SMPolicyControl_UpdateNotify service operation.Consequently steps 7 and 8 are not needed, and so are removed from the procedure. On top of that it makes more sense now to split the procedure into two procedures: Session Management Policy Modifi","secretary_remarks":"Revision of S2-180972. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14950,"status":"withdrawn","reservation_date":"2018-01-25 14:56:31","uploaded":null,"revisionof":"S2-180972","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181014","title":"23.501: Editorial corrections in clause 5.3.2.4 Support of a UE registered over both 3GPP and Non-3GPP access","source":"ETRI","contact":"Yooah Kang","contact-id":63871,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution proposes editorial updates in clause 5.3.2.4 to support a Implicit Deregistration timer for either 3GPP or non-3GPP access.","secretary_remarks":"Revision of S2-180929. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18400,"status":"approved","reservation_date":"2018-01-25 18:14:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180929","revisedto":"S2-182116","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181014.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181015","title":"23.502: Revision on Service Request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Propose that UE can start the Service Request Procedure even none of the PDU sessions can be transferred to 3GPP access.","secretary_remarks":"Revision of S2-180941. Revised in parallel session to S2-181026.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18510,"status":"revised","reservation_date":"2018-01-25 18:14:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180941","revisedto":"S2-181026","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181015.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181016","title":"[draft] Reply LS to CT WG1 on 5G service request procedure","source":"SA WG2","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-181026,  S2-181027","secretary_remarks":"Revision of S2-180943. Revised in parallel session to S2-181028.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18550,"status":"revised","reservation_date":"2018-01-25 18:14:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180943","revisedto":"S2-181028","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181016.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181017","title":"23.501: Alignment with TS23.502 on Service Request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It has been replaced the optional indication of the PDU session to be reactivated with the mandatory list of PDU session to be reactivated","secretary_remarks":"Revision of S2-180942. Revised in parallel session to S2-181027.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18770,"status":"revised","reservation_date":"2018-01-25 18:14:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180942","revisedto":"S2-181027","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181017.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181018","title":"23.502: Removal of editor's notes in clause 4.12","source":"Nokia, Nokia Shanghai Bell","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Editor's note in 4.12 is removed. Details of PDU Session Release Request and Command are documented and aligned to 3GPP access corresponding procedure.","secretary_remarks":"Revision of S2-180944. Revised in parallel session to S2-181024.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18590,"status":"revised","reservation_date":"2018-01-25 18:14:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180944","revisedto":"S2-181024","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181018.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181019","title":"23.502: Clarification on paging when it is related with both 3GPP and non-3GPP PDU Session","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarify that if the AMF receives multiple request associated with 3GPP and non-3GPP access at the same time, the AMF sends a Paging message with associated access 'non-3GPP' to RAN node(s) via 3GPP access.  2. Clarify that the AMF behaviour when it receives another message for 3GPP (or non-3GPP) PDU Session while waiting for a UE response for the non-3GPP (or 3GPP) PDU Session.  3. Clarify that the UE initiates UE Triggered Service Request procedure when it receives paging request for a PDU Session associated with non-3GPP access even if there is no PDU Session that can be re-activated over the 3GPP access.","secretary_remarks":"Revision of S2-180945. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18640,"status":"approved","reservation_date":"2018-01-25 18:14:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180945","revisedto":"S2-181509","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181019.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181020","title":"LS on UE behaviour when it received paging associated with non-3GPP access","source":"SA WG2","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-181019","secretary_remarks":"Revision of S2-180946. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18660,"status":"approved","reservation_date":"2018-01-25 18:14:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180946","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181020.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181021","title":"23.502: Updating Network Triggered Service Request to support selective re-activation of PDU session over non-3GPP access","source":"ETRI","contact":"Yooah Kang","contact-id":63871,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution proposes to update Network Triggered Service Request procedure to support selective re-activation of PDU session over non-3GPP access.","secretary_remarks":"Revision of S2-180949. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18740,"status":"approved","reservation_date":"2018-01-25 18:14:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180949","revisedto":"S2-182119","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181021.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181022","title":"23.502: Clarification on 5G-GUTI in EPS to 5GS Mobility Registration Procedure using N26","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) The following clarification is made regarding in step 2 when the UE includes the native 5G-GUTI and the GUAMI part of the native 5G-GUTI in the Registration request and RRC, respectively: When the native 5G-GUTI is assigned during a Registration procedure performed over a non-3GPP access, the UE includes the native 5G-GUTI as an additional GUTI in the Registration Request and for idle mode mobility the GUAMI part of the native 5G-GUTI in RRC only if the 3GPP access that the UE registers is in the same PLMN for the non-3GPP access that the UE is registered.  2) Re-wording is made for clarity in steps 17-18 regarding when the UE uses the updated 5G-GUTI in the Registration Accept:","secretary_remarks":"Revision of S2-180950. Agreed in parallel session Revised to S2-181380.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18830,"status":"revised","reservation_date":"2018-01-25 18:14:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180950","revisedto":"S2-181380","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181022.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181023","title":"Emergency services over 5GC via untrusted non-3GPP access","source":"Nokia, Nokia Shanghai Bell","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The case emergency sessions over 5GC via non-3GPP untrusted access is added to existing clauses 4.3.1 and 4.4.  A new annex for this case is added.","secretary_remarks":"Revision of S2-180951. Revised in parallel session to S2-181025.","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18890,"status":"revised","reservation_date":"2018-01-25 18:14:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180951","revisedto":"S2-181025","release":"Rel-15","crspec":23.167,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":320.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181023.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181024","title":"23.502: Removal of editor's notes in clause 4.12","source":"Nokia, Nokia Shanghai Bell","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Editor's note in 4.12 is removed. Details of PDU Session Release Request and Command are documented and aligned to 3GPP access corresponding procedure.","secretary_remarks":"Revision of S2-181018. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18600,"status":"approved","reservation_date":"2018-01-25 18:14:40","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181018","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181024.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181025","title":"Emergency services over 5GC via untrusted non-3GPP access","source":"Nokia, Nokia Shanghai Bell","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The case emergency sessions over 5GC via non-3GPP untrusted access is added to existing clauses 4.3.1 and 4.4.  A new annex for this case is added.","secretary_remarks":"Revision of S2-181023. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18900,"status":"agreed","reservation_date":"2018-01-25 18:14:40","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181023","revisedto":"","release":"Rel-15","crspec":23.167,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":320.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-180094","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181025.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181026","title":"23.502: Revision on Service Request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Propose that UE can start the Service Request Procedure even none of the PDU sessions can be transferred to 3GPP access.","secretary_remarks":"Revision of S2-181015. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18520,"status":"approved","reservation_date":"2018-01-25 18:14:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181015","revisedto":"S2-181566","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181026.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181027","title":"23.501: Alignment with TS23.502 on Service Request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It has been replaced the optional indication of the PDU session to be reactivated with the mandatory list of PDU session to be reactivated","secretary_remarks":"Revision of S2-181017. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18780,"status":"approved","reservation_date":"2018-01-25 18:14:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181017","revisedto":"S2-181567","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181027.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181028","title":"Reply LS to CT WG1 on 5G service request procedure","source":"SA WG2","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-181026, S2-181027","secretary_remarks":"Revision of S2-181016. Agreed in parallel session. Block Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18560,"status":"approved","reservation_date":"2018-01-25 18:14:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181016","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180003","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181028.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181029","title":"Clarification on PRA reporting in ECM-IDLE state","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the behaviour of MME\/S4-SGSN upon receiving request for notification of change of UE presence in PRA when UE is in CM-IDLE state.","secretary_remarks":"Revision of S2-180484. For e-mail approval. Revision 1 approved. Revised to S2-181393.","agenda_item_sort_order":9,"ainumber":"5.2","ainame":"QoS and PCC Maintenance","tdoc_agenda_sort_order":10800,"status":"revised","reservation_date":"2018-01-25 18:14:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180484","revisedto":"S2-181393","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3381.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181029.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181030","title":"23.787: Architectural Assumptions for ENTRADE","source":"Qualcomm incorporated, Motorola Mobility, Lenovo","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes architectural assumptions for ENTRADE","secretary_remarks":"Revision of S2-180960. Agreed in parallel session. Block Approved","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21270,"status":"approved","reservation_date":"2018-01-25 18:14:42","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180960","revisedto":"","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181030.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181031","title":"23.787: Key Issue - Management of encrypted traffic detection and verification information","source":"China Unicom, OPPO","contact":"Chi Ren","contact-id":72309,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue (i.e. management of encrypted traffic detection and verification information) for FS_ENTRADE.","secretary_remarks":"Revision of S2-180961, merging S2-180962. Revised in parallel session to S2-181038.","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21300,"status":"revised","reservation_date":"2018-01-25 18:14:42","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180961","revisedto":"S2-181038","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181031.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181032","title":"23.794: Scope and Architectural Assumptions of eIMS5G Study","source":"T-Mobile USA INC, Ericsson","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Proposes text for the scope and architectural assumptions clauses of the eIMS5G report.","secretary_remarks":"Revision of S2-180934. Approved","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22250,"status":"approved","reservation_date":"2018-01-25 18:14:42","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180934","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181032.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181033","title":"23.794: Key Issues for FS_eIMS5G Localized UPF","source":"T-Mobile USA INC, Intel, AT&T","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Proposes two key issues related to localized UPF and IMS","secretary_remarks":"Revision of S2-180935. Agreed in parallel session. Block Approved","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22300,"status":"approved","reservation_date":"2018-01-25 18:14:42","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180935","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181033.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181034","title":"23.794: Key Issues for FS_eIMS5G slicing","source":"T-Mobile USA INC, Huawei, HiSilicon, ZTE, China Mobile, Nokia, Nokia Shanghai Bell","contact":"Christopher Joul","contact-id":31136,"tdoctype":"pCR","for":"Approval","abstract":"Proposes a key issue related to network slicing and IMS","secretary_remarks":"Revision of S2-180936. Approved","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22340,"status":"approved","reservation_date":"2018-01-25 18:14:42","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180936","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181034.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181035","title":"23.794: New Key issue : Cx Replacement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This document proposes a new key issue for FS_eIMS5G.","secretary_remarks":"Revision of S2-180937. Agreed in parallel session. Block Approved","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22400,"status":"approved","reservation_date":"2018-01-25 18:14:42","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180937","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181035.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181036","title":"23.794: New Key Issue : Sh Replacement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"This document proposes a new key issue for FS_eIMS5G","secretary_remarks":"Revision of S2-180940. Agreed in parallel session. Block Approved","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22450,"status":"approved","reservation_date":"2018-01-25 18:14:42","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180940","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181036.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181037","title":"23.794: New Key Issues: Support of Service Based Interfaces","source":"Huawei, HiSilicon, China Mobile","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes new key issues for eIMS5G SI, in order to investigate the necessary IMS enhancements to support SBI provided by 5GC.","secretary_remarks":"Revision of S2-180938. Agreed in parallel session. Block Approved","agenda_item_sort_order":38,"ainumber":"6.14","ainame":"Study on Enhanced IMS to 5GC Integration (FS_eIMS5G)","tdoc_agenda_sort_order":22490,"status":"approved","reservation_date":"2018-01-25 18:14:42","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180938","revisedto":"","release":"Rel-16","crspec":23.794,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eIMS5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181037.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181038","title":"23.787: Key Issue - Management of encrypted traffic detection and verification information","source":"China Unicom, OPPO","contact":"Chi Ren","contact-id":72309,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue (i.e. management of encrypted traffic detection and verification information) for FS_ENTRADE.","secretary_remarks":"Revision of S2-181031. Agreed in parallel session. Block Approved","agenda_item_sort_order":34,"ainumber":"6.","ainame":"Study on encrypted traffic detection and verification (FS_ENTRADE)","tdoc_agenda_sort_order":21310,"status":"approved","reservation_date":"2018-01-25 18:14:54","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181031","revisedto":"","release":"Rel-16","crspec":23.787,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ENTRADE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181038.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181039","title":"23.502: Mobility restrictions (service area) when roaming","source":"NEC","contact":"Sivasubramaniam Ramanan","contact-id":28064,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 4.16.1.2 step 3; Npcf_AMPolicyControl_Get response for Policy Association Establishment during Registration 4.16.1.3 step 3; Npcf_AMPolicyControl_Get response for Policy Association Establishment during AMF relocation 4.16.2.1 subclause title; minor correction 4.16.2.2; Npcf_AMPolicyControl_UpdateNotify in case of roaming scenario","secretary_remarks":"Revision of S2-180370. Revised in parallel session to S2-181053.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15830,"status":"revised","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180370","revisedto":"S2-181053","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181039.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181040","title":"23.503: UE policies granularity and UE assistance for policy evaluation.","source":"Ericsson, NEC, Lenovo","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that a URSP\/WLANSP rule contains an identifier and that the PCF can perform operations (add\/delete\/replace) per individual URSP\/WLANSP rule. The UE sends at initial registration the list of UE policies currently stored in the device and the PCF uses this information as input for policy decisitions.","secretary_remarks":"Revision of S2-180924, merging S2-180926. Revised to S2-181386.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14580,"status":"revised","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180924","revisedto":"S2-181386","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181040.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181041","title":"23.503: Description of components in URSP","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Filling the description of the components. 2. Multiple Route Selection Descriptors in one URSP rule.  3. Non-Seamless Offload indication doesn't coexist with other component.","secretary_remarks":"Revision of S2-180966. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14630,"status":"approved","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180966","revisedto":"S2-181580","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181041.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181042","title":"23.502: UE polices ack from UE","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following solution is proposed:  - - The UE sends back to the AMF a NAS message acknowledging the reception and storage of the UE policies.  - - In addition, to cover those error cases where the UE receives the NAS message from the AMF but has some error in the storing of the UE policies information, the UE may include in the ACK message with additional information about the error. If this optional IE is present in the ACK message, the AMF will send this error to the PCF (stage 3 will decide the message) and this will handle the error, e.g. updating UE context in the PCF accordingly and reattempting the sending of UE policies later on.","secretary_remarks":"Revision of S2-180968. This was withdrawn.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14790,"status":"withdrawn","reservation_date":"2018-01-26 07:39:41","uploaded":null,"revisionof":"S2-180968","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181043","title":"23.501: Clarification on PCF selection","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Updating the PCF selection with the following proposals - The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF. - The SMF sends the PCF selected by the AMF to the SMF during the PDU session establishment procedure Fixing the typo in the clause 6.3.7.0","secretary_remarks":"Revision of S2-180978. Revised in parallel session to S2-181049.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15070,"status":"revised","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180978","revisedto":"S2-181049","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181043.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181044","title":"23.715: Update of RLOS key issues","source":"Nokia, Nokia Shanghai Bell, Verizon","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes modifications to RLOS key issues, based on the recent response from SA WG1 in LS S1-174602.","secretary_remarks":"Revision of S2-181004. Agreed in parallel session. Block Approved","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22740,"status":"approved","reservation_date":"2018-01-26 10:04:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181004","revisedto":"","release":"Rel-16","crspec":23.715,"crspecversion":"0.1.1","workitem":[{"winame":"FS_PARLOS_SA2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181044.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181045","title":"Reply LS on clarification on Restricted Operator Services","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG1, SA WG3. CC: CT WG1","secretary_remarks":"Revision of S2-181000. For e-mail approval. e-mail revision 5 approved. Revised to S2-181407.","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22620,"status":"revised","reservation_date":"2018-01-26 10:04:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181000","revisedto":"S2-181407","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG3","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181045.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181046","title":"23.726: FS_ETSUN \/ 23.726 Scope","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"pCR","for":"Approval","abstract":"FS_ETSUN \/ 23.726 Scope, references and abbreviations","secretary_remarks":"Revision of S2-180953. Agreed in parallel session. Block Approved","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21670,"status":"approved","reservation_date":"2018-01-26 10:04:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180953","revisedto":"","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181046.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181047","title":"23.726: Key Issue Proposal: SMF and UPF Insert\/Relocation due to UE Mobility","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"In this contribution, it is proposed a new key issue to study the SMF and UPF insert or relocation due to UE mobility.","secretary_remarks":"Revision of S2-180955. Revised to S2-181374.","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21830,"status":"revised","reservation_date":"2018-01-26 10:04:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180955","revisedto":"S2-181374","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181047.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181048","title":"23.726: FS_ETSUN \/ 23.726 Key Issue: Support of the preservation of a PDU session while the UE moves out of an SMF service area","source":"Nokia, Nokia Shanghai Bell, Ericsson, CATT, Huawei?","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"pCR","for":"Approval","abstract":"FS_ETSUN \/ 23.726 Key Issue: Support of the preservation of a PDU session while the UE moves out of an SMF service area","secretary_remarks":"Revision of S2-180954. Revised to S2-181375.","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21700,"status":"revised","reservation_date":"2018-01-26 10:04:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180954","revisedto":"S2-181375","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181048.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181049","title":"23.501: Clarification on PCF selection","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Updating the PCF selection with the following proposals - The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF. - The SMF sends the PCF selected by the AMF to the SMF during the PDU session establishment procedure Fixing the typo in the clause 6.3.7.0","secretary_remarks":"Revision of S2-181043. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15080,"status":"approved","reservation_date":"2018-01-26 13:52:02","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181043","revisedto":"S2-181500","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181049.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181050","title":"23.502: Clarification on PCF association","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 4.2.2.2.2-1: Registration, step 5: Removing 'PCF ID' because it is already included in UE context exchanged for inter-AMF mobility. Step 16: change 'PCF ID' into '(V-)PCF ID' - 4.16.1.2: Policy Association Establishment during Registration, step 2: proposal for the roaming case: The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF - 4.16.1.3: Policy Association Establishment during AMF relocation, step 2: proposal for the roaming case: The V-PCF receiving the PCF ID from old AMF shall include the H-PCF ID in the Npcf_AMPolicyControl Get operation. - 4.16.3.2: AMF-initiated Policy Association Termination, step 1: removing the unnecessary text based on the agreement at SA WG2#124. - 5.2.2.2.2: Table 5.2.2.2.2-1: UE Context in AMF - adding 'PCF ID' based on the agreement at SA WG2#124, and additionally 'H-PCF ID' based on the proposal on V\/H-PCF selection by AMF","secretary_remarks":"Revision of S2-180979. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15110,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180979","revisedto":"S2-181528, S2-182163","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181050.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181051","title":"23.503: Clarification PCF interaction","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 4.2.2: general clarification - 5.3.3: general clarification - 5.3.4: clarification on unclear description about roaming options, LBO and HR. HR or LBO should be referring to a particular PDU session instead of per UE. \u00e8 Proposing two alternatives. One should be selected. - 6.1.2.1: removing the unnecessary text based on the agreement at SA WG2#124. - 6.1.2.2, 6.1.2.2.1: general clarification","secretary_remarks":"Revision of S2-180980. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15140,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180980","revisedto":"S2-181499","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181051.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181052","title":"23.502: Proposed resolution of Editor\u00b4s Notes in 23.502","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The proposal to resolve 1) above is to remove the Editor\u00b4s note. The reason is that the Access and Mobility related policy control the V-PCF generates the service area restrictions, those are not received from H-PCF as defined in clause 6.2.1.4 in TS 23.503.  The proposal to resolve 2) above is to remove the Editor\u00b4s note. The reason is that the functional description of the AF interactions described in 23.501 and 23.503 are either related to request for resources, prioritization of services, requires to steer to traffic to a DNAI(s), or request to charge traffic to the sponsor. These features require to provision PCC Rules to SMF.  The proposal to resolve 3) above is to extend the number of scenarios when the policy association termination procedure applies to include the notification of the removal of the policy profile from UDR. In addition, it is proposed to add a new procedure for (policy) session management termination when the UDR notifies the PCF that the pol","secretary_remarks":"Revision of S2-180232. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15210,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180232","revisedto":"S2-181632","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181052.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181053","title":"23.502: Mobility restrictions (service area) when roaming","source":"NEC","contact":"Sivasubramaniam Ramanan","contact-id":28064,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 4.16.1.2 step 3; Npcf_AMPolicyControl_Get response for Policy Association Establishment during Registration 4.16.1.3 step 3; Npcf_AMPolicyControl_Get response for Policy Association Establishment during AMF relocation 4.16.2.1 subclause title; minor correction 4.16.2.2; Npcf_AMPolicyControl_UpdateNotify in case of roaming scenario","secretary_remarks":"Revision of S2-181039. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15840,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181039","revisedto":"S2-181676","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181053.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181054","title":"23.502: Correction on the Policy association procedure during AMF relocation","source":"Huawei, HiSilicon,Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Reclassified the Policy Association Establishment procedure into two cases: a) Policy Association Establishment procedure with new PCF (No UE context); b) Policy Association Establishment procedure with old PCF (Has UE context). 2. Update the existing description for the procedure that old PCF is used. 3. Update the description about the Policy Association Establishment procedure in registration.","secretary_remarks":"Revision of S2-180991, merging S2-180990. For e-mail approval. e-mail revision 2 approved. Revised to S2-181400.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15310,"status":"revised","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-29 10:17:52","revisionof":"S2-180991","revisedto":"S2-181400","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181054.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181055","title":"23.503: Influence of additional non-standardized QoS parameters on QoS Flow Binding","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The additional AW\/MDBV added into PCC Rule information and considered during QoS Flow Binding.","secretary_remarks":"Revision of S2-180993. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15380,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180993","revisedto":"S2-181577","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181055.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181056","title":"23.503: QoS rule generation","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify each QoS rule provided by SMF is generated from a PCC rule. The default QoS rule is generated by SMF based on the authorized default 5QI and ARP received from PCF, if a Packet Filter Set is included in the default QoS rule, the PCF may provide a default Packet Filter Set in the PDU Session related policy information to SMF. Clarify for a PDU session of unstructured type, no PCC Rule is provided to SMF. SMF generates the default QoS rule based on the authorized default 5QI and ARP received in the PDU Session related policy information.","secretary_remarks":"Revision of S2-180994. Agreed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15410,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180994","revisedto":"S2-181604","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181056.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181057","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23540,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181058","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23550,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181059","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23560,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181060","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23570,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181061","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23580,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181062","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23590,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181063","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23600,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181064","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23610,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181065","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23620,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181066","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23630,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181067","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23640,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181068","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23650,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181069","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23660,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181070","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23670,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181071","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23680,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181072","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23690,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181073","title":"Reserved for Krisztian's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23700,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181074","title":"New SID: Enhancement of URLLC supporting in 5G","source":"Huawei, China Telecom, CATR, Telecom Italia, InterDigital, CATT, China Mobile, China Unicom, HiSilicon, III, Deutsche Telekom, NEC, Orange, NTT Docomo, Sprint, AT&T, Verizon, KDDI, ITRI","contact":"Runze Zhou","contact-id":60945,"tdoctype":"SID new","for":"Approval","abstract":"This new SID proposal proposes a SI for enhancement of URLLC supporting in 5G","secretary_remarks":"Revision of S2-180680. This was postponed.","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23130,"status":"postponed","reservation_date":"2018-01-23 13:27:51","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180680","revisedto":"S2-181674, S2-181913","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181074.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181075","title":"New SID on Enhanced support of Vertical and URLLC Services","source":"Nokia, Nokia Shanghai Bell, Qualcomm, SK Telecom, Telecom Italia, Siemens, Robert Bosch GmbH, Charter Communications, AT&T","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"SID new","for":"Approval","abstract":"The objective is to study enhancements to 5GS that are required to fulfill the objectives of normative Vertical and URLLLC service requirements, agreed by SA WG1 as part of the 2 study items concluded in SA WG1: FS_CAV and FS_5GLAN.","secretary_remarks":"Revision of S2-180465. Revised off-line to S2-181382.","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23290,"status":"revised","reservation_date":"2018-01-23 13:27:51","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180465","revisedto":"S2-181382","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181075.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181076","title":"Current 3GPP PS DATA OFF Feature Analysis and Potential Enhancement to 5GS","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution introduces the current PS Data Off feature introduced in LTE and analyzes the corresponding work needed for 5GS","secretary_remarks":"Revision of S2-180444. Noted","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23210,"status":"noted","reservation_date":"2018-01-23 13:27:51","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180444","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181076.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181077","title":"23.501: Network sharing prioritised PLMN handling","source":"Ericsson, Qualcomm Inc.","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding support for prioritized PLMN selection at UE for idle mode mobility and and at interworking with EPS. Also clarified that 23.122 does not define all cases where multiple MNCs used within a country.","secretary_remarks":"Revision of S2-180201. Revised to S2-181313.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11260,"status":"revised","reservation_date":"2018-01-23 13:27:51","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180201","revisedto":"S2-181313","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181077.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181078","title":"23.501: Network Sharing and Interworking with EPS- TS 23.501","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Delete the network behaviour description from clause 5.18.3. Clarify how NG-RAN selects the target PLMN in the order of (1) PLMN in use, (2) Prioritized list of PLMN IDs, (3) EPLMN list during the handover within 5GS. Add corresponding description on how UE selects the network during mobility between 5GS and EPS in case of network sharing and interworking with EPS. Add reference in clause 5.17 to address how network selection is performed by UE during Idle Mode mobility between 5GS and EPS for the single registration mode in case of network sharing.","secretary_remarks":"Revision of S2-180437. Revised to S2-181350.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11300,"status":"revised","reservation_date":"2018-01-23 13:27:51","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180437","revisedto":"S2-181350","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181078.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181079","title":"23.786: New Key Issue: eV2X QoS Support","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue for eV2XARC SI, to investigate the necessary QoS enhancements to support eV2X requirements","secretary_remarks":"Revision of S2-180145, merging part of S2-180478. Revised in parallel session to S2-181094.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19610,"status":"revised","reservation_date":"2018-01-24 13:38:22","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180145","revisedto":"S2-181094","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181079.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181080","title":"23.786: Key issues for support of eV2X QoS enhancements","source":"Qualcomm Incorporated, Intel","contact":"Hong Cheng","contact-id":25668,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue for supporting the QoS for eV2X requirements.","secretary_remarks":"Revision of S2-180510, merging part of S2-180478. Revised in parallel session to S2-181090.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19640,"status":"revised","reservation_date":"2018-01-24 13:38:22","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180510","revisedto":"S2-181090","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181080.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181081","title":"23.786: New key issue of Service Authorization for eV2X","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue of service authorization for eV2X in 5G system","secretary_remarks":"Revision of S2-180443. Agreed in parallel session. Block Approved","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19680,"status":"approved","reservation_date":"2018-01-24 13:38:22","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180443","revisedto":"","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181081.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181082","title":"23.786: New Key Issue: Network Slicing for eV2X","source":"Huawei, HiSilicon, CMCC","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue for eV2XARC SI, to clarify the relationship within 5GS among eV2X services, the required supporting features and Network Slicing","secretary_remarks":"Revision of S2-180147. Revised in parallel session to S2-181095.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19700,"status":"revised","reservation_date":"2018-01-24 13:38:22","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180147","revisedto":"S2-181095","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181082.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181083","title":"23.786: New key issue for edge computing","source":"LG Electronics, NTT DOCOMO, KPN, InterDigital","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a new key issue on edge computing for study in TR 23.786.","secretary_remarks":"Revision of S2-180477. Revised in parallel session to S2-181096.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19730,"status":"revised","reservation_date":"2018-01-24 13:38:22","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180477","revisedto":"S2-181096","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181083.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181084","title":"23.786: Key issues for support of unicast\/multicat for Extended Sensors","source":"Qualcomm Incorporated,","contact":"Hong Cheng","contact-id":25668,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue for supporting the Extended Sensor requirement from stage 1.","secretary_remarks":"Revision of S2-180511. Agreed in parallel session. Block Approved","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19760,"status":"approved","reservation_date":"2018-01-24 13:38:22","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180511","revisedto":"","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181084.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181085","title":"23.786: Key issue_eV2X message transmission & reception for V2V\/V2P Service","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contributions proposes a key issue to identify and evaluate how to support the eV2X message transmission & reception in the 5G system","secretary_remarks":"Revision of S2-180148. Revised in parallel session to S2-181097.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19780,"status":"revised","reservation_date":"2018-01-24 13:38:22","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180148","revisedto":"S2-181097","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181085.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181086","title":"23.786: EV2X architecture reference model for 5G","source":"Ericsson, CATT","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Propose 5G V2X architecture option","secretary_remarks":"Revision of S2-180208, merging S2-180550. Revised in parallel session to S2-181098.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19810,"status":"revised","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180208","revisedto":"S2-181098","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181086.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181087","title":"Clarification on PC5 parameters from V2X Application Server","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Currently, V2X USD(s) for receiving MBMS based V2X traffic may be provisioned to the UE from the V2X Application Server via V1 reference point. In addition, V2X Control Function may obtain V2X USD(s) for the UE to receive MBMS based V2X traffic through the V2 reference point from the V2X Application Server.  Therefore, it is clarified that  1) The parameters for V2X communications over PC5 reference point may be also provisioned to the UE from the V2X Application Server via V1. 2) The parameters for V2X communications over PC5 reference point may be also provided to the V2X Control Function from from the V2X Application Server via V2. 3) If the UE receives a set of data for V2X communications over PC5 reference point from V2X Application Server then the UE uses the data set provided by V2X Application Server for V2X communications over PC5 reference point.","secretary_remarks":"Revision of S2-180534. Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10740,"status":"agreed","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180534","revisedto":"","release":"Rel-14","crspec":23.285,"crspecversion":"14.5.0","workitem":[{"winame":"V2XARC"}],"crnumber":39.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180088","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181087.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181088","title":"Support of Reliable transmission over PC5 using extended PPPP","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To allow for the UE to indicate reliability information an additional indication is added to allow the V2X application in the UE to provide reliability information that may be used by AS layer to differentiate between different V2X packets.","secretary_remarks":"Revision of S2-180209, merging S2-180249. Agreed in parallel session. Block Approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11160,"status":"agreed","reservation_date":"2018-01-25 06:55:22","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180209","revisedto":"","release":"Rel-15","crspec":23.285,"crspecversion":"14.5.0","workitem":[{"winame":"LTE_eV2X-Core"}],"crnumber":37.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-180114","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181088.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181089","title":"[DRAFT] Reply LS on Reliability for eV2X","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: CT WG1","secretary_remarks":"Created in parallel session. Response to S2-180034 Revised in parallel session to S2-181092.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11110,"status":"revised","reservation_date":"2018-01-25 06:55:23","uploaded":"2018-01-26 18:07:53","revisionof":"","revisedto":"S2-181092","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181089.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181090","title":"23.786: Key issues for support of eV2X QoS enhancements","source":"Qualcomm Incorporated, Intel","contact":"Hong Cheng","contact-id":25668,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue for supporting the QoS for eV2X requirements.","secretary_remarks":"Revision of S2-181080. Agreed in parallel session. Block Approved","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19650,"status":"approved","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181080","revisedto":"","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181090.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181091","title":"23.786: New key issue for 5G System architectures for V2X services","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a new key issue on 5G System architectures for V2X services for study in TR 23.786.","secretary_remarks":"Revision of S2-180344. Revised in parallel session to S2-181093.","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19580,"status":"revised","reservation_date":"2018-01-25 18:14:54","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180344","revisedto":"S2-181093","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181091.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181092","title":"[DRAFT] Reply LS on Reliability for eV2X","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: CT WG1","secretary_remarks":"Revision of S2-181089. Revised to S2-181368.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11120,"status":"revised","reservation_date":"2018-01-26 10:04:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181089","revisedto":"S2-181368","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181092.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181093","title":"23.786: New key issue for 5G System architectures for V2X services","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a new key issue on 5G System architectures for V2X services for study in TR 23.786.","secretary_remarks":"Revision of S2-181091. Agreed in parallel session. Block Approved","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19590,"status":"approved","reservation_date":"2018-01-26 10:04:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181091","revisedto":"","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181093.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181094","title":"23.786: New Key Issue: eV2X QoS Support","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue for eV2XARC SI, to investigate the necessary QoS enhancements to support eV2X requirements","secretary_remarks":"Revision of S2-181079. Agreed in parallel session. Block Approved","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19620,"status":"approved","reservation_date":"2018-01-26 10:04:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181079","revisedto":"","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181094.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181095","title":"23.786: New Key Issue: Network Slicing for eV2X","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue for eV2XARC SI, to clarify the relationship within 5GS among eV2X services, the required supporting features and Network Slicing","secretary_remarks":"Revision of S2-181082. Agreed in parallel session. Block Approved","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19710,"status":"approved","reservation_date":"2018-01-26 10:04:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181082","revisedto":"","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181095.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181096","title":"23.786: New key issue for edge computing","source":"LG Electronics, NTT DOCOMO, KPN, InterDigital","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a new key issue on edge computing for study in TR 23.786.","secretary_remarks":"Revision of S2-181083. Agreed in parallel session. Block Approved","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19740,"status":"approved","reservation_date":"2018-01-26 10:04:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181083","revisedto":"","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181096.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181097","title":"23.786: Key issue_eV2X message transmission & reception for V2V\/V2P Service","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contributions proposes a key issue to identify and evaluate how to support the eV2X message transmission & reception in the 5G system","secretary_remarks":"Revision of S2-181085. Approved","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19790,"status":"approved","reservation_date":"2018-01-26 10:04:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181085","revisedto":"","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181097.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181098","title":"23.786: EV2X architecture reference model for 5G","source":"Ericsson, CATT","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Propose 5G V2X architecture option","secretary_remarks":"Revision of S2-181086. Agreed in parallel session. Block Approved","agenda_item_sort_order":30,"ainumber":"6.6","ainame":"Study on architecture enhancements for 3GPP support of advanced V2X services (FS_eV2XARC)","tdoc_agenda_sort_order":19820,"status":"approved","reservation_date":"2018-01-26 10:04:32","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181086","revisedto":"","release":"Rel-16","crspec":23.786,"crspecversion":"0.2.0","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181098.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181099","title":"23.502: Network sharing prioritised PLMN handling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying PLMN selection related to shared networks in combination with interworking and access changes.","secretary_remarks":"Revision of S2-180202, merging S2-180438. Revised to S2-181349.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11330,"status":"revised","reservation_date":"2018-01-23 13:27:51","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180202","revisedto":"S2-181349","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181099.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181100","title":"E-UTRAN and MME impacts during N26 based HO in the case of Network Sharing and Interworking with 5GS- TS 23.401","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Describe the impacts to E-UTRAN and MME for the N26 based handover between EPS and 5GS. Add the last used 5GS PLMN ID into the table of MME information storage in clause 5.7.2.","secretary_remarks":"Revision of S2-180439. This was withdrawn.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11370,"status":"withdrawn","reservation_date":"2018-01-23 13:27:51","uploaded":null,"revisionof":"S2-180439","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3380.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181101","title":"23.501: Network sharing for supporting RRC redirection procedure","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Network selection for supporting RRC connection release with redirect to a shared network is specified in clause 5.18.4","secretary_remarks":"Revision of S2-180542. Agreed in parallel session. Block Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11400,"status":"approved","reservation_date":"2018-01-23 13:27:52","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180542","revisedto":"S2-182094, S2-182095","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181101.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181102","title":"23.501: Subscriber Permanent and Concealed Identifiers","source":"Orange, Telecom Italia, AT&T","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Addition of a definition of SUCI in clause 5.9.2, referring to TS 33.501. Extention of the requirement to contain the address of the home network to SUCI. 2) Removal of the second bullet in clause 5.9.2 and clarification of the following paragraph.","secretary_remarks":"Revision of S2-180392. This was postponed.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11430,"status":"postponed","reservation_date":"2018-01-23 13:27:52","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180392","revisedto":"S2-182264","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181102.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181103","title":"Adding 5GS to the Network Architecture","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a reference to 5GS.","secretary_remarks":"Revision of S2-180426. Revised to S2-181317.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11530,"status":"revised","reservation_date":"2018-01-23 13:27:52","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180426","revisedto":"S2-181317","release":"Rel-15","crspec":23.002,"crspecversion":"14.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":304.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181103.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181104","title":"[Draft] Reply LS on timers for the network-requested PDU session modification procedure and 'SSC mode 3'","source":"Qualcomm Europe Inc.(Italy)","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-18abcd","secretary_remarks":"Revision of S2-180167, merging S2-180289 and S2-180307. Revised to S2-181280.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13060,"status":"revised","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180167","revisedto":"S2-181280","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181104.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181105","title":"23.502: Clarification on PDU Session Release timer provided to the UE for 'SSC mode 3'","source":"Huawei, HiSilicon, Intel, Qualcomm Incorporated","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Provide the release timer to the UE by transparent means.","secretary_remarks":"Revision of S2-180290, merging S2-180169 and S2-180373. Revised to S2-181278.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13010,"status":"revised","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180290","revisedto":"S2-181278","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181105.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181106","title":"23.501: Add UNKNOWN status to UE location change","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding UNKNOWN status to UE Location change notification subclause.","secretary_remarks":"Revision of S2-180667. Postponed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13110,"status":"postponed","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180667","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181106.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181107","title":"23.502: Generalize exposure of Mobility Events from AMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Generalize 'Exposure of Mobility Events from AMF' to cover both LADN and other cases.","secretary_remarks":"Revision of S2-180668. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13090,"status":"approved","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180668","revisedto":"S2-181548","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181107.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181108","title":"23.502: Align the UE location presence status of LADN Session into Network Triggered Service Request procedure","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: for the LADN PDU session, if UE presence in LADN is Unknown status and DL data arrives, the SMF may not trigger a notification to the AMF.","secretary_remarks":"Revision of S2-180333. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13130,"status":"approved","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180333","revisedto":"S2-181549","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181108.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181109","title":"23.501: Corrections on UE Location change notification","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: First change. Name of the notification - proposal is to use 'UE location change notification' instead of 'UE mobility event Notification' Second change. Use 'UE presence in LADN' and its descriptions Third change. Add 'SMF enable downlink data notification or not' on receiving the notification And more minor changes including editorial changes.","secretary_remarks":"Revision of S2-180245. Postponed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13150,"status":"postponed","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180245","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181109.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181110","title":"LS from NGNM:  NGMN White Paper on Service-based Architecture in 5G","source":"NGNM","contact":"Klaus Moschner","contact-id":59428,"tdoctype":"LS in","for":"Information","abstract":"Intention of the LS and required actions: NGMN is pleased to inform the recipients of this liaison statement that the White Paper of the NGMN Service-based Architecture in 5G has been published. The deliverable has been created by NGMN Mobile Network Operator-Partners. The document describes a service framework including service registration, service authorization, and service discovery. Service-based Architecture for 5G is designed in a forward-looking manner, such that the functionalities in 5G Core Network (CN) consist of services, the interface between Control Plane (CP) and User Plane (UP) should be Service Based Interface (SBI) and the Data Service should be used. The deployment aspects of SBA are explored along with the gap analysis and recommendations for related SDOs. NGMN kindly requests the recipients of this liaison to take the content of this White Paper and the recommendations into account for their ongoing work on the industry-wide 5G architecture.","secretary_remarks":"This LS was postponed. Revised at S2#126 in S2-181431.","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23090,"status":"revised","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"","revisedto":"S2-181431","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5, ETSI ISG NFV, GSMA","Cc":"TSG SA, SA WG3, TSG CT, CT WG4","lsoriginalls":"180105 Liaison NGMN","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181110.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181111","title":"23.501: Clarification in LADN clause 5.6.5 - TS 23.501","source":"Intel, ZTE, ETRI, KDDI, Huawei","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The AMF and SMF know whether a DNN is a LADN DNN based on the UE subscription information received from the UDM. AMF indicates to UE whether a DNN is a LADN DNN. AMF indicates to UE that the LADN is not available in the UE's current Registration Area. Align the terms with 23.502 to 'UE presence in a LADN'. Add missing SMF behaviour when the UE presence in a LADN is OUT. Remove the redundant description for SMF behaviour when the UE presence in a LADN is IN or UNKNOWN.","secretary_remarks":"Revision of S2-180441, merging S2-180288 and S2-180545. Noted","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13190,"status":"noted","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180441","revisedto":"S2-181535","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181111.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181112","title":"23.502: Clarification on LADN related aspects - TS 23.502","source":"Intel, ZTE, ETRI, KDDI","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify the SMF behaviour on rejecting the request when UE's presence in a LADN is OUT for the procedure of General Registration, UE Triggered Service Request, UE Requested PDU Session Establishment and Modification. Clarify how AMF updates UE about the LADN information change and UE behaviour when the LADN service area information is empty. Correct the wording of 'UE presence in LADN' to 'UE presence in a LADN' in clause 4.15.4. Add the detail on how the LADN DNN is indicated from UDM to AMF and SMF in clause 5.2.3.3.1.","secretary_remarks":"Revision of S2-180442. This was withdrawn.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13210,"status":"withdrawn","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180442","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181112.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181113","title":"Key Open Issues of LADN Principles","source":"Drafting group","contact":"Maurice Pope","contact-id":648,"tdoctype":"discussion","for":"Discussion","abstract":"Drafted based on the discussion during LADN Drafting Session","secretary_remarks":"Created in parallel session Revised to S2-181274.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13220,"status":"revised","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"","revisedto":"S2-181274","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_125_Gothenburg\/Docs\/S2-181113.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181114","title":"23.502: LADN Signalling to SMF","source":"Sony, NEC","contact":"Svante Aln\u00e5s","contact-id":62551,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) In the signalling from AMF to SMF include sufficient information to SMF regarding LADN so that SMF are able to process the request directly 2) Add GPSI in the corresponding interface to SMF","secretary_remarks":"Revision of S2-180377, merging S2-180751. Postponed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13280,"status":"postponed","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180377","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181114.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181115","title":"23.501: Clarification on LADN PDU Session establishment handling","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Add explicit description that DNN include information on whether the DNN is LADN. 2) AMF can reject the PDU Session establishment request.","secretary_remarks":"Revision of S2-180502. This was withdrawn.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13170,"status":"withdrawn","reservation_date":"2018-01-23 13:27:53","uploaded":null,"revisionof":"S2-180502","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181116","title":"23.502: Clarification on Internal Event Exposure","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarification on system behaviour in case of mobility event notification happens, and which procedure may trigger the mobility event notification.","secretary_remarks":"Revision of S2-180547. Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13310,"status":"endorsed","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180547","revisedto":"S2-181494","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181116.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181117","title":"Enhancements to Service Based Architecture","source":"Deutsche Telekom, China Mobile, AT&T, NTT Docomo, Sprint, Vodafone, KDDI, Verizon, CATT, BT Plc, Interdigital, Telecom Italia","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"discussion","for":"Discussion","abstract":"Objective: The scope of this study is to study potential enhancement to the Release 15 Service-Based Architecture (SBA) in order to provide higher flexibility and better modularization of the 5G System for the easier definition of different network slices and enable better re-use of the defined services. Moreover, the study should consider enhancements to the SBA in order to support high reliability of network function(s). The potential enhancements to be studied are: 1) Make services fully self-contained if they are not already, - study stateless service operation to avoid long-living UE-specific bindings between service instances - to achieve independent lifecycle management - to allow multi-vendor service interoperability, - to enhance flexibility for e.g. network slicing, Time-to-market, operational efficiency - to achieve higher granular independent services and better re-usability 2) Feasibility study of extend the service concept from 5GC control plane to include user plane 3) S","secretary_remarks":"Revision of S2-180768. Noted","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23190,"status":"noted","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180768","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_125_Gothenburg\/Docs\/S2-181117.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181118","title":"Created at meeting - Title TBD","source":"Drafting group","contact":"Maurice Pope","contact-id":648,"tdoctype":"discussion","for":"Discussion","abstract":"-","secretary_remarks":"Created in parallel session. withdrawn (not provided)","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11630,"status":"withdrawn","reservation_date":"2018-01-23 13:27:53","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181119","title":"23.502: Different configured NSSAI based on device type","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add UE device type in term of SST (UE supported SST) in initial registration request and AMF may trigger UEconfiguration update procedure to update the Configured NSSAI.","secretary_remarks":"Revision of S2-180379. Revised to S2-181291.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11700,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180379","revisedto":"S2-181291","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181119.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181120","title":"23.502: Corrections to SMF selection","source":"Telecom Italia, ZTE, Oracle, NTT DOCOMO, Vodafone?, Orange?, Huawei?, Ericsson?","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Updated labels in figures 4.3.2.2.3.2-1, 4.3.2.2.3.3-1 and 4.3.2.2.3.3-2 with the correct service operation names, where the notation 'operation_name|xxx' indicates the intended service operation and its actual semantics. - Updated the text below the figures 4.3.2.2.3.2-1, 4.3.2.2.3.3-1 and 4.3.2.2.3.3-2 with the correct service operation names (same notation as in the figures). - Added missing parameters. - Added text to steps in 3(A) and 3(B) of Option 2 to align with steps 7-8 of Option 1 for SMF selection. - Removed steps in 3(C) of Option 2 for SMF selection. - Minor editorial changes","secretary_remarks":"Revision of S2-180066, merging S2-180756. Revised to S2-181277.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13690,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180066","revisedto":"S2-181277","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181120.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181121","title":"23.502: Correction to UE Registration","source":"Telecom Italia, ZTE, Oracle, Huawei","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Fixed the optionallity of the Mapping Of Requested NSSAI in clause 4.2.2.2.2. - Updated labels in figure 4.2.2.2.3-1 with the correct service operation names, where the notation 'operation_name|xxx' indicates the intended service operation and its actual semantics. - Updated the text below the figure 4.2.2.2.3-1 with the correct service operation names (same notation as in the figure). - Fixed the misaligment between clauses 4.2.2.2.3 and 5.2.16.2.1 adding the indication if a Subscribed S-NSSAI is marked as default S-NSSAI and a reference clause 5.2.16.2.1 for other input parameters not mentioned here.","secretary_remarks":"Revision of S2-180067. Revised to S2-181289.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11790,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180067","revisedto":"S2-181289","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181121.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181122","title":"23.501: Draft CR 23.501 Correction to rejected NSSAI","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 'Permanently' is removed - UE behaviour when a rejected S-NSSAI becomes allowed again is defined","secretary_remarks":"Revision of S2-180362. Agreed in parallel session. Block Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11840,"status":"approved","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180362","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181122.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181123","title":"23.502: Update Registration and registration with AMF re-allocation","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Add the rejected S-NSSAI(s) in the Registration Accept message of the Registration procedure which is described in the clause 5.15.4.1 of TS 23.501. 2. Clarify the Mapping Of Requested NSSAI and Subscribed S-NSSAIs included in the step 4a of the registration with AMF re-allocation. 3. Replace the Silce Selection Request message and NF discovery Request message with the service-based invocation as described in the TS 23.502. 4. Clarify NF consumer (e.g. AMF) discover NSSF as described in the S2-180663.","secretary_remarks":"Revision of S2-180665. WITHDRAWN","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11820,"status":"withdrawn","reservation_date":"2018-01-23 13:27:54","uploaded":null,"revisionof":"S2-180665","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181124","title":"23.502: Clarification on Communication Pattern and Expected UE behaviour","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add the Communication Pattern parameters into the parameter list of Expected UE Behaviour.","secretary_remarks":"Revision of S2-180336. Endorsed in parallel session Revised to S2-181377.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19100,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180336","revisedto":"S2-181377","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181124.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181125","title":"23.502: Improvements on the specification of the subscription to Network Exposure","source":"Nokia, Nokia Shanghai Bell, Huawei, CATT, ZTE, Hisilicon,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. \u00a7 4.15.1: adding target UE in the table 2. 5.2.2.3.2: add 'any UE' as target of AMF event subscription + Notification target address provided by Consumer NF \/ Subscription Correlation ID provided by Event Provider 3. Clarifying Notification target address and Subscription Correlation ID throughout all Event related services  4. Splitting up throughout all Nxxx Subscription services between Event Id (Mandatory, defined as part of the Nxxx service) and Event Filter information (Maximum number of reports, \u2026) where reference to 4.15.1 is made","secretary_remarks":"Revision of S2-180131, merging S2-180255, S2-180643, S2-180152 and S2-180151. Revised in parallel session to S2-181268","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19130,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180131","revisedto":"S2-181268","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181125.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181126","title":"23.502: Corrections to NRF and NSSF services","source":"Telecom Italia, ZTE, Oracle, Huawei","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Fixed the misaligment between clauses 4.2.2.2.3, 4.3.2.2.3, 4.17.5, 5.2.7.3 and 5.2.16. - Resolved the Editor's note on NRF as NSSF consumer. - Minor editorial change.","secretary_remarks":"Revision of S2-180068, merging part of S2-180666. Revised in parallel session to S2-181267","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19190,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180068","revisedto":"S2-181267","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181126.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181127","title":"23.502: NF Service Discovery Corrections in 23.502","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: First Change (in clause 4.3.2.2.3.2) and Second Changes (in clause 4.17.5) make sure to include the endpoint address (i.e. HTTP URLs) for the discovered NF services as a result of NF\/NF Service Discovery from the NRF.","secretary_remarks":"Revision of S2-180244. Endorsed in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19220,"status":"endorsed","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180244","revisedto":"S2-181657","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181127.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181128","title":"23.502: Clarification on Use of List of Parameter Values to Match in Event Filters","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarify how 'list of parameter values to match' in the Event Filter can be used for some example events like area of interest, location change notification and AN type change notification. 2. For the UE reachability status event the words 'along with optional list of sessions to be activated' is removed. The reason is this was added during SA WG2#121 during which time Service Request call flow modelling was discussed through use of Namf_EventExposure_Notify. However in later meetings it has been agreed to use Nsmf_PDUSession_UpdateSMContext for this purpose. Hence there is no need to notify 'optional list of sessions to be activated' when UE becomes reachable.","secretary_remarks":"Revision of S2-180155. Agreed in parallel session. Block Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19270,"status":"approved","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180155","revisedto":"S2-181555","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181128.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181129","title":"23.502: Clarification on the services for External Parameter Provisioning","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Modify the original figure of 4.15.6.2-1, and related descriptions in clause 4.15.6.2 to reflect the proposals mentioned above.","secretary_remarks":"Revision of S2-180343. Revised to S2-181355.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19300,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180343","revisedto":"S2-181355","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181129.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181130","title":"23.502: update Nnrf_NFDiscovery service based on the UE IP address","source":"China Mobile","contact":"Wei Chen","contact-id":57801,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: New texts are added to clarify that UE IP address can be a opitional input parameter in Nnrf_NFDiscovery service to allow NEF to discover the BSF with the input of UE IP address.  Besides, BSF is added into the cosumers list of Nnrf_NFManagement_NFRegister service to make NRF to store the BSF service information.","secretary_remarks":"Revision of S2-180396. Agreed in parallel session. China mobile raise an issue with there being no IP address included. Revised to S2-181383.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19360,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180396","revisedto":"S2-181383","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181130.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181131","title":"23.502: Application Trigger procedure updates","source":"Ericsson, Convida Wireless LLC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The usage of Nudm_SDM_Get operation is described including new Subscription Data type: 'Identity translation'. This new Subscription Data type requires GPSI as access key, instead of SUPI. Nnef_Trigger service operation names are updated to reflect better the functionality performed.","secretary_remarks":"Revision of S2-180470, merging S2-180150. Revised to S2-181357.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19410,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180470","revisedto":"S2-181357","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181131.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181132","title":"23.502: Nudm SDM service Subscription Data types updates","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Data items are added\/removed for multiple Subscription Data types for the Nudm SDM service. Added information:  - UE Usage Type for EPC interworking - LADN indicator per DNN - Priority services indicator (MPS) Removed information: -Homogeneous VoIP support indicator is provided by AMF to UDM since it is required for internal UDM processing, but it is not part of 'Access and Mobility Subscription data' required by AMF. -Default APN is not used by SMF.","secretary_remarks":"Revision of S2-180473. Agreed in parallel session. Block Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19470,"status":"approved","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180473","revisedto":"S2-181624","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181132.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181133","title":"23.502: Fixes for UDM\/UDR services","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Fix the UDM service operation 2) Fix the UDR service name 3) Update subscription data table for Registration and MM subscription data type as PEI (i.e. IMEI), Homogenous support of IMS voice over PS Sessions are paramers sent by AMF to UDM and it need not be sent in the other direction.","secretary_remarks":"Revision of S2-180516. Agreed in parallel session. Block Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19450,"status":"approved","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180516","revisedto":"S2-181758","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181133.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181134","title":"23.501: Clarification on UDM service consumption order of UECM and SDM","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the texts describing\/implying the UDM service operation order description","secretary_remarks":"Revision of S2-180606. This was endorsed.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19490,"status":"endorsed","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180606","revisedto":"S2-181557","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181134.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181135","title":"23.501: NF Service Discovery","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. It is proposed to make sure that the NRF returns the HTTP URL-style endpoint address for the discovered NF service instances 2. NF Service Discovery is also service-based 3. NRF discovers the UPF's N4 reference point address.","secretary_remarks":"Revision of S2-180243. Revised in parallel session to S2-181269","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19510,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180243","revisedto":"S2-181269","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181135.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181136","title":"23.502: NEF service definitions for AF influence","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add NEF service defintions to support AF influence. This paper relates to S2-180139 and S2-180480","secretary_remarks":"Revision of S2-180479. Revised in parallel session to S2-181270","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19540,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180479","revisedto":"S2-181270","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181136.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181137","title":"LS from GSMA Packet IoTTF: LS reply to SA WG2 on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"GSMA Packet IoTTF","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"GSMA Packet IoTTF thanks SA WG2 for reply liaison statement on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic. IoTTF intended to: - Identify traffic coming from Cat. M1\/M2 LTE UEs regardless if they initiate\/receive traffic with or without any means of CIOT optimisations. The following identifications are out of scope: - Identify the volume of data sent in Coverage Enhancement Mode A and Coverage Enhancement Mode B regardless of the UE category that supports the Coverage Enhancement Mode, IoTTF understood that Coverage Enhancement Mode A, Coverage Enhancement Mode B, and Low Access Priority Indicator could not differentiate LTE-M traffic because they could be used for non-IoT UEs. GSMA needs to differentiate Mobile IoT traffic, both LTE-M and NB-IoT, from traditional user traffic. This is motivated by the operators' desire to apply different charging models to traffic from LTE-M devices and NB-IoT devices plus the requirements for identification and transparency wh","secretary_remarks":"This LS was postponed Revised at S2#126 in S2-181432.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"","revisedto":"S2-181432","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5","Cc":"-","lsoriginalls":"IOTTF17 Doc003","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181137.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181138","title":"23.502: Update of handover cancel procedure","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: the SBA service (e.g. Nsmf_PDUSession_UpdateSMContext request\/response in the N11 interface) shall be used 5G system. Change 2: AMF is not involved in the delete of indirect data forwarding tunnel in 5G system. And also the figure 4.11.1.2.3-1 is updated. Change 3: 'handover cancel indication' is added into the handover cancel procedure.","secretary_remarks":"Revision of S2-180330. Agreed in parallel session. Block Approved","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16020,"status":"approved","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180330","revisedto":"S2-181561","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181138.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181139","title":"23.502: Correction for UE location in Xn based HO procedure","source":"Samsung","contact":"Jayshree Bharatia","contact-id":63826,"tdoctype":"draftCR","for":"Approval","abstract":"This contribution provides correction in Xn based handover procedure pertaining to UE location mentioned in step 2.","secretary_remarks":"Revision of S2-180767. Agreed in parallel session. Block Approved","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16040,"status":"approved","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180767","revisedto":"S2-181938","release":"Rel-15","crspec":23.502,"crspecversion":"2.0.0","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_125_Gothenburg\/Docs\/S2-181139.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181140","title":"23.502: Removal of re-registration cause\/indication for service reject","source":"LG Electronics, Huawei","contact":"Jinsook Ryu","contact-id":39022,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) It is proposed that when the Service Request is rejected due to unsynchronized UE parameter (e.g. Service area restriction is not updated since the UE is in MICO) between the UE and AMF, the AMF shall perform UE Configuration Update procedure as specified in clause 4.2.4 to provide UE parameter before the UE is sent to CM-IDLE state. 2) It is proposed to remove indicating re-registration cause\/indication in Service Reject.","secretary_remarks":"Revision of S2-180407. Revised to S2-181305.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16080,"status":"revised","reservation_date":"2018-01-23 13:27:55","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180407","revisedto":"S2-181305","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181140.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181141","title":"23.501: CR Control of the Messages triggering Paging at AMF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: AMF and other network functions together control the quantity of messages that require the AMF to page the UE. In addition to SMF control, if additional requests received while waiting for a UE response to the Paging Request message, the AMF may determines to reject it. Proposal 1: AMF and other network functions shall together control the quantity of messages that require the AMF to page the UE. Proposal 2: If the AMF has sent two Paging Messages to RAN node, the AMF shall reject the subsequent messages with a No Response to Previous Paging Indication. Proposal 3: If the AMF has a Paging Messages to RAN node, the AMF shall reject the subsequent messages without a higher priority.","secretary_remarks":"Revision of S2-180488. Agreed in parallel session. Block Approved","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16140,"status":"approved","reservation_date":"2018-01-23 13:27:55","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180488","revisedto":"S2-181563","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181141.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181142","title":"23.502: CR Control of the Messages triggering Paging at AMF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: AMF and other network functions together control the quantity of messages that require the AMF to page the UE. In addition to SMF control, if additional requests received while waiting for a UE response to the Paging Request message, the AMF may determines to reject it. Proposal 1: AMF and other network functions shall together control the quantity of messages that require the AMF to page the UE. Proposal 2: If the AMF has sent two Paging Messages to RAN node, the AMF shall reject the subsequent messages with a No Response to Previous Paging Indication. Proposal 3: If the AMF has a Paging Messages to RAN node, the AMF shall reject the subsequent messages without a higher priority.","secretary_remarks":"Revision of S2-180489. Revised to S2-181306.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16160,"status":"revised","reservation_date":"2018-01-23 13:27:55","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180489","revisedto":"S2-181306","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181142.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181143","title":"23.502: Clarification on RAT type indication during handover procedure","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the RAN provides N2 parameters (e.g. PLMN ID, Location Information, Cell Identity and the RAT type) to the AMF and the AMF notifies such information to the SMF during handover procedure.","secretary_remarks":"Revision of S2-180521. Withdrawn in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16200,"status":"withdrawn","reservation_date":"2018-01-23 13:27:55","uploaded":null,"revisionof":"S2-180521","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181144","title":"23.501: Paging Policy Differentiation correction","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Several changes are made for the Paging Policy Differentiation: 1. The indication of the corresponding QoS Flow is removed from the SMF buffering downlink data packet case. 2. PPI is removed from the paging message. 3. Clarify that NG-RAN determines the PPI based on the DSCP in TOS (IPv4) \/ TC (IPv6) value from the IP header of the received downlink data packet from the UPF for the UE in RRC Inactive state.","secretary_remarks":"Revision of S2-180548. Agreed in parallel session. Block Approved","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16220,"status":"approved","reservation_date":"2018-01-23 13:27:55","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180548","revisedto":"S2-181495","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181144.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181145","title":"23.502: Paging Policy Differentiation correction","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Two changes are made for the Paging Policy Differentiation: 1. The indication of the corresponding QoS Flow is removed from the SMF buffering downlink data packet case. 2. PPI is removed from the N2 SM Information.","secretary_remarks":"Revision of S2-180549. Revised to S2-181307.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16250,"status":"revised","reservation_date":"2018-01-23 13:27:55","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180549","revisedto":"S2-181307","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181145.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181146","title":"23.502: Service Request procedure corrections","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: As above.","secretary_remarks":"Revision of S2-180629. Revised to S2-181308.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16290,"status":"revised","reservation_date":"2018-01-23 13:27:55","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180629","revisedto":"S2-181308","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181146.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181147","title":"23.502: Clarification for Area of validity in NW triggered SR procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: (1) Add a clarification in step 4 of clause 4.2.3.2 that step 4-11 can be skipped for the above case. (2) Editorial modification to change 'Area of validity for the N2 information' to 'Area of validity for the N2 SM information'. This part is highlighted in blue colour. (3) Delete redundant text in 4.2.3.2. This part is highlighted in green colour.","secretary_remarks":"Revision of S2-180677. Agreed in parallel session. Block Approved","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16330,"status":"approved","reservation_date":"2018-01-23 13:27:55","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180677","revisedto":"S2-181565","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181147.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181148","title":"23.502: Rejecting Service Request for UP reactivation","source":"LG Electronics","contact":"Sang Min Park","contact-id":62105,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Signalling connection indicator is introduced for the UE to inform its purpose of SR trigerring, and specified additional condition when the AMF can send Service Reject instead of Service Accept.","secretary_remarks":"Revision of S2-180711. Revised to S2-181309.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16360,"status":"revised","reservation_date":"2018-01-23 13:27:55","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180711","revisedto":"S2-181309","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181148.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181149","title":"23.502: Multiple request of Location Reporting for Area of Interest","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: AMF includes Request Reference ID in the Location Report Control message to identify the request for the area of interest. The AMF may include Request Reference ID which indicates the requested Location Reporting Control for the area of interest, so that the NG-RAN should terminate location reporting for the request for a given UE.","secretary_remarks":"Revision of S2-180725. Approved","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16390,"status":"approved","reservation_date":"2018-01-23 13:27:55","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180725","revisedto":"S2-181492","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181149.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181150","title":"23.501: Introduction of 'Maximum Data Burst Volume for all GBR flows","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In last meeting it was agreed that a new QoS characteristics Parameter, Maximum Data Burst Volume', is introduced for GBR flows with PDB<20 ms. However, there is also a need to specify what data volume can be served for GBR flows with higher PDB. In S2-178049 values for Default Averaging Window are proposed for the standardized GBR 5QI's. The values are rather large, 2, and 3 s long, which correspond to unreasonable high requirements for the instantaneous bitrate in RAN. The instantaneous bitrate needed in RAN in order to serve the largest bursts that are within the GFBR requirement can be estimated by: GFBR*AW\/PDB The table below shows the largest burst size within the GFBR requirement, and the instantaneous bitrate that would be required in RAN to serve it within the PDB. 5QI PDB Averaging Window (AW) Largest data burst within GFBR Instantaneous bitrate 1 100 ms 2 s 2 * GFBR 20 * GFBR 2 150 ms 2 s 2 * GFBR 13 * GFBR 3 50 ms 3 s 3 * GFBR 60 * GFBR 4 300 ms 3 s 3 * G","secretary_remarks":"Revision of S2-180422. Revised to S2-181196.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14160,"status":"revised","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180422","revisedto":"S2-181196","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181150.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181151","title":"23.501: Traffic mapping information that disallows uplink packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In clause 5.7.1.4, refer to clause 5.7.6.1 for the definition of Packet Filter Set to ensure the consistency. In clause 5.7.1.5, clarify that a QoS rule containing Packet Filter Set with no UL filter means no UL packets allowed for the QoS Flow associated with that QoS rule. In clause 5.7.6.1, add a note when the DL filter may be needed by the UE.","secretary_remarks":"Revision of S2-180220. Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14200,"status":"approved","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180220","revisedto":"S2-181620","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181151.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181152","title":"23.501: Corrections and clarifications for the usage of Packet Filter Set","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The direction of the packet filters in the Packet Filter Set is clarified in some places. For the description of the interaction with the UPF, SDF template is replaced by PDR. The QoS Flow mapping description is restructured and the corresponding figure updated.","secretary_remarks":"Revision of S2-180312, merging S2-180252. Endorsed in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14220,"status":"endorsed","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180312","revisedto":"S2-181572","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181152.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181153","title":"23.501: Default QoS Rule cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: A note that UE does not need to know which QoS rule is","secretary_remarks":"Revision of S2-180770. WITHDRAWN","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14260,"status":"withdrawn","reservation_date":"2018-01-23 16:34:30","uploaded":null,"revisionof":"S2-180770","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181154","title":"23.502: Default QoS Rule cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introducing sending an indication which EBI refer to the default EPS bearer","secretary_remarks":"Revision of S2-180771. WITHDRAWN","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14280,"status":"withdrawn","reservation_date":"2018-01-23 16:34:30","uploaded":null,"revisionof":"S2-180771","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181155","title":"23.502: Reflective QoS Timer transmission during PDU Session establishment","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the PCF(if applied) and SMF should provide Reflective QoS Timer during PDU Session establishment procedures.","secretary_remarks":"Revision of S2-180310. Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14310,"status":"approved","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180310","revisedto":"S2-181570","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181155.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181156","title":"23.503: Addition of Reflective QoS Timer in PDU session related policy information","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the Reflective QoS Timer as part of PDU Session related policy information..","secretary_remarks":"Revision of S2-180311. Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14330,"status":"approved","reservation_date":"2018-01-23 16:34:31","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180311","revisedto":"S2-181571","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181156.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181157","title":"23.502: Slice selection cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following changes are done:  - Clarifying what the S-NSSAIs relate to e.g. PLMN  -Adding Mapping Of Allowed NSSAI to the UE MM Context table  - The S-NSSAI corresponding to the PDU Session stored in the UE Context is the one valid for the serving PLMN (i.e. the same as used in the Allowed NSSAI).  - Adding S-NSSAI and optionally NSI ID as IEs for the Nnwdaf_EventsSubscription service  - Adding DNN sent back to the UE at PDU Session Establishment  - Removing S-NSSAI sent to the UE at PDU Session Establishment","secretary_remarks":"Revision of S2-180103, merging S2-180712 and S2-180707. Revised to S2-181345.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11860,"status":"revised","reservation_date":"2018-01-23 16:34:31","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180103","revisedto":"S2-181345","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181157.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181158","title":"23.501: Clarification of UE Requested NSSAI","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that UE include S-NSSAI of established PDU sessions (PDN connections) into UE requested NSSAI.","secretary_remarks":"Revision of S2-180345. Revised to S2-181290.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11890,"status":"revised","reservation_date":"2018-01-23 16:34:31","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180345","revisedto":"S2-181290","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181158.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181159","title":"23.501: Clarify NSSF discovery","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The NSSF discovery function shall utilize an appropriate configured NRF to discover the NSSF instance(s) unless NSSF information is available by other means, e.g. local configuration, and select a NSSF instance based on the obtained NSSF information.","secretary_remarks":"Revision of S2-180663. Revised to S2-181315.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11940,"status":"revised","reservation_date":"2018-01-23 16:34:31","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180663","revisedto":"S2-181315","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181159.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181160","title":"23.501: Slice and AMF selection at HO procedure","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The AMF initially selected at HO, selects a network slice supporting target AMF and relays the initial signalling from the source AMF to the target AMF. Target AMF responds directly to the source AMF.","secretary_remarks":"Revision of S2-180110. This was withdrawn in parallel session (not provided).","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11980,"status":"withdrawn","reservation_date":"2018-01-23 16:34:31","uploaded":null,"revisionof":"S2-180110","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181161","title":"23.501: Slice selection cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The S-NSSAIs used by the UE when moving from EPS to 5GS are clarified.","secretary_remarks":"Revision of S2-180102. Revised to S2-181316.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12010,"status":"revised","reservation_date":"2018-01-23 16:34:31","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180102","revisedto":"S2-181316","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181161.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181162","title":"Slicing interworking principles","source":"Drafting group","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"Agreement","abstract":"Drafting session outcome","secretary_remarks":"Created in parallel session. Not Handled","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12040,"status":"not treated","reservation_date":"2018-01-24 06:42:56","uploaded":"2018-01-26 18:07: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_125_Gothenburg\/Docs\/S2-181162.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181163","title":"23.501: Slicing configuration update","source":"Motorola Mobility, Lenovo","contact":"Genadi Velev","contact-id":70944,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution proposes to update the Newtork Slice configuration description implementing the Prosals 1 - 4 from the 'Reason for change'.","secretary_remarks":"Revision of S2-180395. Revised to S2-181318.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11660,"status":"revised","reservation_date":"2018-01-24 06:42:56","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180395","revisedto":"S2-181318","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181163.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181164","title":"23.502: Cleanup of the service request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Per above reason of changes, the related clarification and changes are updated.","secretary_remarks":"Revision of S2-180346. Revised to S2-181275.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13360,"status":"revised","reservation_date":"2018-01-24 06:42:56","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180346","revisedto":"S2-181275","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181164.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181165","title":"23.501: Clarification on mobility event subscription transfer","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the new AMF notiifes current status only when the new AMF does not know the last reported status.","secretary_remarks":"Revision of S2-180525. Revised to S2-181276.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13420,"status":"revised","reservation_date":"2018-01-24 06:42:56","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180525","revisedto":"S2-181276","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181165.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181166","title":"23.502\/\u00a7 4.3.6 : case of applications that do not support application mobility","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - at the creation of the contexts related with the PDU session in the UPF: the SMF requests application\/traffic detection in mute mode (the feature exists already) - at UPF mobility : the SMF asks the (old) UPF the status of the different application\/traffic detection contexts - the SMF moves to local switching at the new UPF (DNAI of the new UPF) the application\/traffic detection contexts for which there was no on-going traffic at the old UPF - the SMF takes care that the application\/traffic detection contexts for which there was on-going traffic at the old UPF remain served by the old DNAI until the application stops o when the application stops the SMF instructs the new UPF to direct new flows of this application to the new DNAI (new application instance)","secretary_remarks":"Revision of S2-180064. WITHDRAWN","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13450,"status":"withdrawn","reservation_date":"2018-01-24 06:42:57","uploaded":null,"revisionof":"S2-180064","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181167","title":"23.501: Editorial modification to AF influence on traffic routing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This paper proposes to clean up the notes and correct wordings for consistency and clarificaiton.","secretary_remarks":"Revision of S2-180139. Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13470,"status":"endorsed","reservation_date":"2018-01-24 06:42:57","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180139","revisedto":"S2-181583","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181167.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181168","title":"23.501: Update to AF influence on traffic routing","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. This paper proposes to optionally include an application identifier in the PDU Session setup\/modification request to allow AF influence to be applied before application traffic starts. 2. This paper proposes to use AF transaction ID for the AF to correlate AF request and SMF notification.","secretary_remarks":"Revision of S2-180480. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13500,"status":"approved","reservation_date":"2018-01-24 06:42:57","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180480","revisedto":"S2-181582","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181168.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181169","title":"23.502: Correction to RAN Initiated QoS Flow Mobility Procedure for Dual Connectivity","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The N11 messages in clause 4.14.1 are replaced with service operations.","secretary_remarks":"Revision of S2-180153. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13530,"status":"approved","reservation_date":"2018-01-24 06:42:57","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180153","revisedto":"S2-181551","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181169.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181170","title":"23.501: Update on Traffic Detection Information","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Replacing PDU session ID with CN tunnel info as one of the traffic detection parameters.","secretary_remarks":"Revision of S2-180602. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13550,"status":"approved","reservation_date":"2018-01-24 06:42:57","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180602","revisedto":"S2-181552","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181170.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181171","title":"23.502: Updates to PDU session establishment procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. in \u00a7 4.3.1, the V-SMF needs to handle the PDU Type (based on the SA WG2 agreement in Reno); It also needs to handle UE addressing information (allocated IPv4 address, interface identifier) for legal reasons + Wording clarification: 'Information that is not visible to the V-SMF' refers to information that the V-SMF is to relay between N1 and N16 (and that it may store in CDR) but that the V-SMF is not assumed to process otherwise. 2. in \u00a7 4.3.2.3 and 5.2.8.2.3: clarify the HR case for DN authentication \/ authorization of the UE 3.  \u00a7 4.3.2.2.1 Step14, \u00a74.3.3.2 step 7a: In case the (R)AN rejects QFI(s) the SMF is responsible of updating the QoS rules in the UE accordingly; in case of HR roaming it is the H-SMF that is responsible of updating the QoS rules in the UE as the impossibility to set-up some QFI(s) may have impacts on QoS rules of other QFI; when RAN rejects some QFI(s), this rejection has to be propagated to H-SMF (not possible with current Call flow) + co","secretary_remarks":"Revision of S2-180062. Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13580,"status":"endorsed","reservation_date":"2018-01-24 06:42:57","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180062","revisedto":"S2-181454","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181171.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181172","title":"23.716: Adding Architectural Principles for Wireline Access","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Proposes a set of architectural principles for the 5WWC work","secretary_remarks":"Revision of S2-180411. Revised to S2-181283.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19880,"status":"revised","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180411","revisedto":"S2-181283","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181172.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181173","title":"23.716: Architecture principles for trusted non-3GPP access","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the architecture principles for trusted non-3GPP access.","secretary_remarks":"Revision of S2-180688. Revised to S2-181282.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19910,"status":"revised","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180688","revisedto":"S2-181282","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181173.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181174","title":"23.716: Definition and terminology","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to add definition and terminology and modify the text according to the new definitions.","secretary_remarks":"Revision of S2-180580. Revised to S2-181284.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19940,"status":"revised","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180580","revisedto":"S2-181284","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181174.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181175","title":"23.716: Access Type definition","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution introduce the applicability of Access Type concept for 5RG connected to wireline AN","secretary_remarks":"Revision of S2-180581. Revised to S2-181285.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19990,"status":"revised","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180581","revisedto":"S2-181285","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181175.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181176","title":"23.716: Update KI #3 on Security","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution propose to clarify security Key issue for 5WWC","secretary_remarks":"Revision of S2-180585. Agreed in parallel session. Block Approved","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20040,"status":"approved","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180585","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181176.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181177","title":"23.716: Update for Key Issue 5.7-Policy","source":"Intel","contact":"Ellen C. Liao","contact-id":54895,"tdoctype":"pCR","for":"Approval","abstract":"This PCR proposes to modify key issue of 5.7 for Policy framework with the study of both use cases.","secretary_remarks":"Revision of S2-180567. Agreed in parallel session. Block Approved","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20070,"status":"approved","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180567","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181177.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181178","title":"23.716: Modifying the Key Issue #7 Policy","source":"China Mobile, Huawei, HiSilicon","contact":"Wei Chen","contact-id":57801,"tdoctype":"pCR","for":"Approval","abstract":"This proposal aims to modify the key issue #7 policy to study the feasibility for PCF to support the policy of wireline network.","secretary_remarks":"Revision of S2-180742, merging S2-180574. Revised to S2-181286.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20090,"status":"revised","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180742","revisedto":"S2-181286","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181178.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181179","title":"23.716: Update to key issue 5.2.9 with two use cases","source":"Intel","contact":"Ellen C. Liao","contact-id":54895,"tdoctype":"pCR","for":"Approval","abstract":"This contribution updates the key issue 5.2.9 to study the end user devices for two cases.","secretary_remarks":"Revision of S2-180199. Agreed in parallel session. Block Approved","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20150,"status":"approved","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180199","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181179.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181180","title":"23.716: Revision on KI10 ATSSS in Hybrid Access","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution propose to update the KI10 for 5WWC","secretary_remarks":"Revision of S2-180586. Revised to S2-181287.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20170,"status":"revised","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180586","revisedto":"S2-181287","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181180.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181181","title":"23.716: Key issue for IPTV Support","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution propose the key issue of IPTV for 5WWC","secretary_remarks":"Revision of S2-180587. Revised to S2-181288.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20200,"status":"revised","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180587","revisedto":"S2-181288","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181181.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181182","title":"23.716: New KI on Emergency Service support","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to add a KI on whether and how support ES","secretary_remarks":"Revision of S2-180575. Agreed in parallel session. Block Approved","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20230,"status":"approved","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180575","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181182.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181183","title":"23.716: New KI on LADN, SSC Mode, Location Reporting","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to add new KIs on LADN, SSC Modes and Location reporting.","secretary_remarks":"Revision of S2-180576. Revised to S2-181339.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20250,"status":"revised","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180576","revisedto":"S2-181339","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181183.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181184","title":"23.501: Updates to the Security Edge Protection Proxy description","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying that the message filtering and policing by the SEPP is achieved without requiring updates of SLAs between the two PLMNs.","secretary_remarks":"Revision of S2-180240. Revised to S2-181366.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14080,"status":"revised","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180240","revisedto":"S2-181366","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181184.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181185","title":"23.501: Clarification of signalling with higher priority","source":"KPN","contact":"Toni Dimitrovski","contact-id":66437,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify UEs behaviour related to initiating higher priority signalling.","secretary_remarks":"Revision of S2-180766. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12250,"status":"approved","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180766","revisedto":"S2-182159","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181185.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181186","title":"[DRAFT] Reply LS on details of network identifiers","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2","secretary_remarks":"Revision of S2-180687. Revised to S2-181262.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12280,"status":"revised","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180687","revisedto":"S2-181262","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181186.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181187","title":"23.501: 5G-GUTI, 5G-S-TMSI definition and mapping rules","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Based on considerations in S2-1780523, we propose the following mapping rules: 1) MMEGI = AMF Region ID (no change here) 2) MMEC = AMF SET ID 3) M-TMSI = AMF Pointer + 5G-M-TMSI Furthermore, it has been agreed that S-TMSI is unique across AMF Sets thus the AMF pointer value can be stated as optional and this can help avoid GUTI reallocations by AMF.","secretary_remarks":"Revision of S2-180750. WITHDRAWN","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12350,"status":"withdrawn","reservation_date":"2018-01-24 13:38:23","uploaded":null,"revisionof":"S2-180750","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181188","title":"DRAFT Reply LS on session management congestion control","source":"SA WG2","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-180538, merging S2-180238. Revised to S2-181263.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12400,"status":"revised","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180538","revisedto":"S2-181263","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181188.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181189","title":"[DRAFT] Reply LS on Mobility management congestion control","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to CT WG1 LS in C1-175413\/S2-180027 on MM congestion control. This LS pertains to the handling of MM back-off timer across 3GPP systems","secretary_remarks":"Revision of S2-180358, merging S2-180237 and S2-180682. Revised to S2-181343.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12450,"status":"revised","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180358","revisedto":"S2-181343","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181189.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181190","title":"23.502: Clarification related to Subscription data type","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Alignment the descriptions with the Table 5.2.3.3.1-1 - Adding an new type 'Slice Selection Subscription data' into the Table 5.2.3.3.1-1  It can be used for the Registration with AMF re-allocation. Instead of getting whole subscription data, get  only information for slice selection. - Adding an additional field (UE context for a PDU session) for SMF Selection Subscription data into the  Table 5.2.3.3.1-1  It was an agreement during non-3GPP related session at SA#124 that the UE context for a PDU session  stored in UDM can be used for the H-SMF selection in HR roaming, in case of the handover to 3GPP  access from N3GPP access via different PLMN. - Adding an additional field (Static IP address\/prefix) for Session Management Subscription data into the  Table 5.2.3.3.1-1.","secretary_remarks":"Revision of S2-180299, merging S2-180471 and S2-180684. Revised to S2-181340.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12540,"status":"revised","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180299","revisedto":"S2-181340","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181190.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181191","title":"23.502: Clean-up of the registration procedure","source":"Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. At registration: The SUPI may only be provided by the UE in case of an Emergency Registration 2. \u00a74.2.2.2.1:transform the EN 'Aspects related to dual registration in 3GPP and non-3GPP access is FFS' into a reference to \u00a74.12 3. \u00a74.2.2.2.2 step 14: If the serving NF removal reason indicated by the UDM is Initial Registration, then the old AMF does not invoke the Namf_EventExposure_Notify but invokes the Nsmf_PDUSession_ReleaseSMContext (SUPI, PDU Session ID) service operation towards all the associated SMFs  4. \u00a74.2.2.2.2 Step 18 : clarify that 'when the AMF has changed the new AMF notifies the SMF for each PDU sessions that it has taken over the responsibility of the signalling path towards the UE: the new AMF invokes the Nsmf_PDUSession_UpdateSMContext service operation using SMF information received from the old AMF at step 5. It also indicates whether the 'PDU Session(s) is to be re-activated' 5. \u00a74.2.2.2.2  requires miscellaneous corrections \/ clarifications;","secretary_remarks":"Revision of S2-180057, merging S2-180641 and S2-180660. Revised to S2-181310.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12580,"status":"revised","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180057","revisedto":"S2-181310","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181191.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181192","title":"23.502: Resolution of ENs in Service Request procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following ENs are resolved: Editor's note: Aspects related to dual registration in 3GPP and non-3GPP access is FFS. Aspects for dual registration have been described in the registration call flow as well e.g. in 4.12.8. It is proposed to remove the EN and add a reference from 4.2.2.2.1 to 4.12.8.  Editor's note: It is FFS if HO attach indication is to be added. So far no need for handover indication been identified e.g. same AMF used for 3GPP and non-3GPP access. It is proposed to remove the EN.  Editor's note: It is FFS how UE Radio capabilities are provided.  Different cases exist, e.g. for Initial Registration and when the AMF does not have any UE Radio Capability stored, then the AMF should obtain the UE Radio Capability information by sending the N2 message (INITIAL CONTEXT SETUP REQUEST without UE Radio Capability information included to the NG-RAN. This triggers the NG-RAN to request the UE Radio Capability from the UE and upload it to the AMF in the N2 in","secretary_remarks":"Revision of S2-180101. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12610,"status":"approved","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180101","revisedto":"S2-181622","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181192.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181193","title":"23.502: Correction on Notification control for GBR QoS flow","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the handling about the case when QoS targets can be fulfilled again to the PDU session modification procedure.","secretary_remarks":"Revision of S2-180308. Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14410,"status":"approved","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180308","revisedto":"S2-181568","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181193.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181194","title":"23.501: ARP usage clean-ups","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The characteristics may be signalled, in two cases: - A special 5QI is used where all characteristics are signalled. - For any 5QI, the parameters priority, Averaging window, and\/or Maximum Data Burst Volume may be signalled in order to override the default values. In section 5.7.1.2 it is stated: 'The 5QI value may indicate that a QoS flow have signalled QoS characteristics, and if so, the QoS characteristics are included in the QoS profile.' This text does not cover the second alternative, and should be re-formulated in order to avoid confusion. Proposal 1: Reformulate text, so that all signaled characteristics parameters are included","secretary_remarks":"Revision of S2-180423. Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14440,"status":"approved","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180423","revisedto":"S2-181621","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181194.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181195","title":"23.501: 5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) PDB\/PER - clarify the condition for adding the packet to the PER. Current text is a bit ambiguous as it uses GBR as a boundary condition. It is ambiguous for implementation to determine the exact condition for considering the packets as lost and adding it to the PER. 2) Maximum Data Burst Volume - State the conditions for enforcing it in the UE for UL and UPF for DL. Otherwise, there is a possibility that huge amount of packets are sent \/ received causing the RAN not to be able to meet the necessary latency and relaibility requirement for delay critical 5QIs. 3) 5QI table - remove the 1ms note as it is not necessary to assume 1ms backhaul delay just for certain set of 5QIs, also removing reference to PCEF. 4) QoS characeteristics for Non-standardized 5QI is expected to be provided dynamically over signaling. Thus the minimum allowed ranges need not be specified. It is proposed to simply remove the EN.","secretary_remarks":"Revision of S2-180474. Revised to S2-181281.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14470,"status":"revised","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180474","revisedto":"S2-181281, S2-181759","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181195.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181196","title":"23.501: Introduction of 'Maximum Data Burst Volume for all GBR flows","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In last meeting it was agreed that a new QoS characteristics Parameter, Maximum Data Burst Volume', is introduced for GBR flows with PDB<20 ms. However, there is also a need to specify what data volume can be served for GBR flows with higher PDB. In S2-178049 values for Default Averaging Window are proposed for the standardized GBR 5QI's. The values are rather large, 2, and 3 s long, which correspond to unreasonable high requirements for the instantaneous bitrate in RAN. The instantaneous bitrate needed in RAN in order to serve the largest bursts that are within the GFBR requirement can be estimated by: GFBR*AW\/PDB The table below shows the largest burst size within the GFBR requirement, and the instantaneous bitrate that would be required in RAN to serve it within the PDB. 5QI PDB Averaging Window (AW) Largest data burst within GFBR Instantaneous bitrate 1 100 ms 2 s 2 * GFBR 20 * GFBR 2 150 ms 2 s 2 * GFBR 13 * GFBR 3 50 ms 3 s 3 * GFBR 60 * GFBR 4 300 ms 3 s 3 * G","secretary_remarks":"Revision of S2-181150. Postponed in parallel session.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14170,"status":"postponed","reservation_date":"2018-01-24 14:19:37","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181150","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181196.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181197","title":"[Draft] LS response on User Plane Security Policy","source":"SA WG2","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, RAN WG2, RAN WG3. CC: CT WG3. Attachments: S2-181198, S2-181199","secretary_remarks":"Revision of S2-180189. Revised to S2-181259.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14030,"status":"revised","reservation_date":"2018-01-24 15:03:36","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180189","revisedto":"S2-181259","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG2, RAN WG3","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181197.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181198","title":"23.501: Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation\/modification of a PDU session, or upon user plane establishment for a PDU session, determined the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Revision of S2-180187. Revised to S2-181260.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13930,"status":"revised","reservation_date":"2018-01-24 15:03:36","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180187","revisedto":"S2-181260","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181198.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181199","title":"23.502: User plane security policy","source":"Ericsson, Qualcomm Incorporated","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Addition of User Plane Security Policy in the N2 SM info provided to RAN during UP connection activation.  The UP Sec. Policy is optionally provided by PCF to SMF, in case dynamic PCC is supported.","secretary_remarks":"Revision of S2-180409. Revised to S2-181261.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13990,"status":"revised","reservation_date":"2018-01-24 15:03:36","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180409","revisedto":"S2-181261","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181199.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181200","title":"23.502: Update to UCU and Registration procedure","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Deletion of indication that current 5G-GUTI is invalid from the AMF in UCU  2. Configured NSSAI may be included by the AMF in the UCU message","secretary_remarks":"Revision of S2-180451. Withdrawn in parallel session (not provided).","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12650,"status":"withdrawn","reservation_date":"2018-01-25 06:55:52","uploaded":null,"revisionof":"S2-180451","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181201","title":"23.724: Adding High latency key issue","source":"Ericsson, CATT, Convida Wireless, Samsung, Huawei, HiSilicon, Intel, AT&T, Qualcomm, LG Electronics","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"High latency key issue","secretary_remarks":"Revision of S2-180828. Revised in parallel session to S2-181246.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20820,"status":"revised","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180828","revisedto":"S2-181246","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181201.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181202","title":"23.724: Key Issue on Power Saving Functions","source":"Qualcomm Inc., Convida Wireless LLC, Huawei, HiSilicon, Verizon Wireless, Interdigital, China Mobile","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes some architectural assumptions and a Key Issue for FS_CIoT_5G related to power saving functions.","secretary_remarks":"Revision of S2-180829. Revised in parallel session to S2-181247.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20870,"status":"revised","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180829","revisedto":"S2-181247","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181202.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181203","title":"23.724: KI - Power Saving Functions","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"pCR","for":"Approval","abstract":"This paper discusses an FS_CIoT_5G Key Issue on Power Savings Functions","secretary_remarks":"Revision of S2-180830. Revised in parallel session to S2-181248.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20910,"status":"revised","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180830","revisedto":"S2-181248","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181203.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181204","title":"23.724: Key Issue on Support of Reliable Communication","source":"Convida Wireless LLC, Intel","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a Key Issue for FS_CIoT_5G related to Support for Reliable Communication.","secretary_remarks":"Revision of S2-180878. Agreed in parallel session. Block Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20990,"status":"approved","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180878","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181204.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181205","title":"23.724: Key Issue on Support of common north-bound APIs for EPC-5GC Interworking","source":"Convida Wireless LLC, AT&T","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes some architectural assumptions and a Key Issue for FS_CIoT_5G related to Support of common north-bound APIs for EPC-5GC Interworking","secretary_remarks":"Revision of S2-180879. Agreed in parallel session. Block Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21020,"status":"approved","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180879","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181205.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181206","title":"23.724: Key Issue on Monitoring","source":"Convida Wireless LLC","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper an introduces a Key Issue on Monitoring for the FS_CIoT_5G TR","secretary_remarks":"Revision of S2-180882. Agreed in parallel session. Block Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21110,"status":"approved","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180882","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181206.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181207","title":"23.724: Key Issue on Inter RAT idle mode mobility to\/from NB-IoT","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes some architectural assumptions and a Key Issue for FS_CIoT_5G related to Inter RAT idle mode mobility to\/from NB-IoT.","secretary_remarks":"Revision of S2-180883. Agreed in parallel session. Block Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21140,"status":"approved","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180883","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181207.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181208","title":"INOBEAR assumptions, key issues and way forward","source":"Rapporteur (Samsung)","contact":"Maurice Pope","contact-id":648,"tdoctype":"discussion","for":"Discussion","abstract":"Assumptions, key issues and way forward for the INOBEAR work, to form the basis for the solution that will be implemented by CR(s).","secretary_remarks":"Revision of S2-180899. Endorsed","agenda_item_sort_order":39,"ainumber":"6.15","ainame":"WID on increasing the maximum number of LTE bearers (INOBEAR)","tdoc_agenda_sort_order":22560,"status":"endorsed","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180899","revisedto":"S2-182211","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_125_Gothenburg\/Docs\/S2-181208.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181209","title":"23.739: Architecture Requirements, Assumptions, and Baseline","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes some text for the Architectural Requirements, Assumptions and Baseline for TR 23.739 'Study on EPC support for Mobility with Low Latency Communication'","secretary_remarks":"Revision of S2-180853. Agreed in parallel session. Block Approved","agenda_item_sort_order":41,"ainumber":"6.17","ainame":"Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob)","tdoc_agenda_sort_order":23020,"status":"approved","reservation_date":"2018-01-25 11:34:35","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180853","revisedto":"","release":"Rel-16","crspec":23.739,"crspecversion":"0.0.0","workitem":[{"winame":"FS_LLC_Mob"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181209.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181210","title":"23.501: EPS Fallback for voice","source":"Ericsson, Charter Communications, Comcast, Huawei, ZTE","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding support for redirect to EPS in case of EPS Fallback for voice and for rejecting the PDU Session modification that setups the QoS flow for voice.","secretary_remarks":"Revision of S2-180884. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16690,"status":"approved","reservation_date":"2018-01-25 14:56:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180884","revisedto":"S2-181636","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181210.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181211","title":"23.502: EPS Fallback for voice","source":"Ericsson, Charter Communications, Comcast, Huawei, ZTE, Nokia","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding support for redirect to EPS in case of EPS Fallback for voice.","secretary_remarks":"Revision of S2-180885. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16720,"status":"approved","reservation_date":"2018-01-25 14:56:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180885","revisedto":"S2-181637","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181211.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181212","title":"LS on EPS Fallback for voice","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachment: S2-181211","secretary_remarks":"Revision of S2-180886. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16760,"status":"approved","reservation_date":"2018-01-25 14:56:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180886","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181212.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181213","title":"23.502 Clarification on the Emergency HO indication for EPS fallback","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding an Note the NG-RAN decide whether to continue EPS Fallback procedures with PS HO or to initiate redirection. NG-RAN may forward the Emergency indication to the target eNB in the Source to Target Transparent Container.","secretary_remarks":"Revision of S2-180892. Revised in parallel session to S2-181220.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16970,"status":"revised","reservation_date":"2018-01-25 14:56:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180892","revisedto":"S2-181220","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181213.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181214","title":"23.501: Complete of IMS Emergency support in 5G including slice and local numbers","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In case of Limited Service state, no slice info to be provided","secretary_remarks":"Revision of S2-180893. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17010,"status":"approved","reservation_date":"2018-01-25 14:56:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180893","revisedto":"S2-181619","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181214.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181215","title":"23.501: Draft CR 23.501 Correction to Emergency Fallback","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Rephrasing to alllow emergency session over untrusted N3GPP access if the emergency session could not be established via 3GPP access - Indications are mutually exclusive - Misc. editorial corrections (Emergency Services)","secretary_remarks":"Revision of S2-180888. Revised to S2-181372.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16840,"status":"revised","reservation_date":"2018-01-25 14:56:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180888","revisedto":"S2-181372","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181215.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181216","title":"Handling of emergency sessions over untrusted N3GPP access in 5GS","source":"MediaTek Inc.","contact":"Maurice Pope","contact-id":648,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - The requirement is introduced","secretary_remarks":"Revision of S2-180889. Agreed in parallel session Revised to S2-181390.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16870,"status":"revised","reservation_date":"2018-01-25 14:56:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180889","revisedto":"S2-181390","release":"Rel-15","crspec":23.167,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":321.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181216.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181217","title":"23.502: Clarification on SMS related Subscription data","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Adding the SMS Subscription data type as a new type into the Table 5.2.3.3.1-1. - Updating the Registration procedures for SMS over NAS, about AMF retrieval (step 2) and SMSF retrieval (step 7) respectively. - Removing the descriptions about SMSF selection in order to transfer them into the new clause of TS 23.501.","secretary_remarks":"Revision of S2-180868. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17170,"status":"approved","reservation_date":"2018-01-25 14:56:35","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180868","revisedto":"S2-181521","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181217.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181218","title":"23.501: 5_16_6_Mission Critical Services - Editorial Changes","source":"FirstNet, AT&T, Motorola Solutions, Airwave","contact":"Ihab Guirguis","contact-id":65302,"tdoctype":"draftCR","for":"Approval","abstract":"This contribution provides editorial updates for clause 5.16.6 as well as clarifying that the scope of this clause extends to include other commercial services that require priority treatment.","secretary_remarks":"Revision of S2-180871. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17320,"status":"approved","reservation_date":"2018-01-25 14:56:35","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180871","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181218.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181219","title":"[DRAFT] LS OUT on IMS registration for Dual-Registered UE","source":"SA WG2","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, CT WG4","secretary_remarks":"Revision of S2-180873. Revised to S2-181373.","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17130,"status":"revised","reservation_date":"2018-01-25 14:56:35","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180873","revisedto":"S2-181373","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181219.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181220","title":"23.502 Clarification on the Emergency HO indication for EPS fallback","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding an Note the NG-RAN decide whether to continue EPS Fallback procedures with PS HO or to initiate redirection. NG-RAN may forward the Emergency indication to the target eNB in the Source to Target Transparent Container.","secretary_remarks":"Revision of S2-181213. Agreed in parallel session. Block Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16980,"status":"approved","reservation_date":"2018-01-25 14:56:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181213","revisedto":"S2-181539","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181220.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181221","title":"23.731: Architecture Assumption for eLCS","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Propose Archtecture Assmuption for enhanced Location services.","secretary_remarks":"Revision of S2-180903. Agreed in parallel session. Block Approved","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21930,"status":"approved","reservation_date":"2018-01-25 18:14:54","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180903","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181221.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181222","title":"23.731: Architecture Requirements for eLCS","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Propose Archtecture Requirements for enhanced Location services.","secretary_remarks":"Revision of S2-180904. Agreed in parallel session. Block Approved","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21960,"status":"approved","reservation_date":"2018-01-25 18:14:54","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180904","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181222.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181223","title":"23.731: Key Issue X: Indentify New Functionality and Distributions","source":"CATT","contact":"Ming Ai","contact-id":40862,"tdoctype":"pCR","for":"Approval","abstract":"Define a Key issue X: Indentify New Functionality and Distributions","secretary_remarks":"Revision of S2-180905. Agreed in parallel session. Block Approved","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":21990,"status":"approved","reservation_date":"2018-01-25 18:14:54","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180905","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181223.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181224","title":"23.731: Key issue: positioning via user plane","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes new key issue 'positioning via user plane'.","secretary_remarks":"Revision of S2-180906. For e-mail approval. Approved","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22020,"status":"approved","reservation_date":"2018-01-25 18:14:54","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180906","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181224.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181225","title":"23.731: Key Issue: Reduce the UE overhead for LCS","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue to consider to reduce the UE overhead for LCS","secretary_remarks":"Revision of S2-180909. Agreed in parallel session. Block Approved","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22090,"status":"approved","reservation_date":"2018-01-25 18:14:54","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180909","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181225.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181226","title":"23.731: Key issue: support of hybrid positioning","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes new key issue 'support of hybrid positioning'.","secretary_remarks":"Revision of S2-180910. Agreed in parallel session. Block Approved","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22120,"status":"approved","reservation_date":"2018-01-25 18:14:54","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180910","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181226.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181227","title":"23.731: Key Issue on IoT UEs for 5GC Location Enhancement","source":"Qualcomm Incorporated, AT&T","contact":"Hong Cheng","contact-id":25668,"tdoctype":"pCR","for":"Approval","abstract":"This contribution provides a P-CR to add a key issue to TR 23.731 on IoT UEs for 5GC location enhancement.","secretary_remarks":"Revision of S2-180913. Agreed in parallel session. Block Approved","agenda_item_sort_order":37,"ainumber":"6.13","ainame":"Study on Enhancement to the 5GC Location Services (FS_eLCS)","tdoc_agenda_sort_order":22190,"status":"approved","reservation_date":"2018-01-25 18:14:54","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180913","revisedto":"","release":"Rel-16","crspec":23.731,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181227.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181228","title":"23.791: Scope of TR 23.791","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the scope of the TR 23.791 for FS_eNA.","secretary_remarks":"Revision of S2-180859. Agreed in parallel session. Block Approved","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21440,"status":"approved","reservation_date":"2018-01-25 18:14:55","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180859","revisedto":"","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181228.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181229","title":"23.791: Architecture Requirement of TR 23.791","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes architecture requirement section of the TR 23.791 for FS_eNA.","secretary_remarks":"Revision of S2-180860. Revised in parallel session to S2-181233.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21470,"status":"revised","reservation_date":"2018-01-25 18:14:55","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180860","revisedto":"S2-181233","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181229.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181230","title":"23.791: Discussion on big data and 5G","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution triggers discussion on big data analytic and 5G system.","secretary_remarks":"Revision of S2-180861 Revised in parallel session to S2-181250.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21510,"status":"revised","reservation_date":"2018-01-25 18:14:55","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180861","revisedto":"S2-181250","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181230.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181231","title":"23.791: FS_eNA Key Issue: NWDA-Assisted Traffic Routing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue to study solutions to support traffic routing using statistical information from NWDAF.","secretary_remarks":"Revision of S2-180864. Revised in parallel session to S2-181319.","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21550,"status":"revised","reservation_date":"2018-01-25 18:14:55","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180864","revisedto":"S2-181319","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181231.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181232","title":"23.791: Key issue on how to get service information from AF","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to a key issue on how to get service information from the service applications.","secretary_remarks":"Revision of S2-180862. Agreed in parallel session. Block Approved","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21600,"status":"approved","reservation_date":"2018-01-25 18:14:55","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180862","revisedto":"","release":"Rel-16","crspec":23.791,"crspecversion":"16.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181232.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181233","title":"23.791: Architecture Requirement of TR 23.791","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes architecture requirement section of the TR 23.791 for FS_eNA.","secretary_remarks":"Revision of S2-181229. Agreed in parallel session. Block Approved","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21480,"status":"approved","reservation_date":"2018-01-25 18:15:07","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181229","revisedto":"","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181233.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181234","title":"23.501: Further RRC Inactive assitance information","source":"NEC, Sony","contact":"Iskren Ianev","contact-id":59515,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following new assistance information is added to the RRC Inactive assistance information from the AMF to the gNB: - UE stationary indication. If the AMF is aware the connecting UE is stationary (e.g. from the UE mobility pattern in the AMF, see clause 5.3.4.2), the AMF may include in the 'RRC Inactive assistance information' an UE stationary indication to help with the NG RAN decision on whether to move the UE in RRC Inactive state and if so, what RNA to configure for it (e.g. the size of RNA); - UE moving trajectory information. If the AMF is aware of the connecting UE's moving trajectory (e.g. from the UE mobility pattern in the AMF, see clause 5.3.4.2), the AMF may include in the 'RRC Inactive assistance information' an UE moving trajectory information (e.g. the list of cells that are overlapped with the UE moving trajectory) to help with the NG-RAN decision on what RNA to configure for the UE in case the UE is moved to RRC Inactive state (e.g. the size and\/or","secretary_remarks":"Revision of S2-180874. For e-mail approval. e-mail revision 1 approved. Revised to S2-181403.","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16460,"status":"revised","reservation_date":"2018-01-25 18:15:07","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180874","revisedto":"S2-181403","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181234.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181235","title":"23.502: Location reporting procedure for LADN in RRC Inactive state - TS 23.502","source":"ETRI","contact":"Dongmyoung Kim","contact-id":65275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: When location reporting with area of interest is configured, the NG-RAN node report whether the UE in IN or OUT or UNKNOWN whenever it detects the event. For the UE in RRC Inactive mode, according to the allocated RNA and the area of interested, UNKNOWN state can be sent to the CN. The proposed operation is aligned with the UE location change notification served by AMF.","secretary_remarks":"Revision of S2-180597. Agreed in parallel session. Block Approved","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16560,"status":"approved","reservation_date":"2018-01-25 18:15:07","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180597","revisedto":"S2-182051","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181235.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181236","title":"Reply LS on Paging in case of Enhanced Coverage Restriction","source":"SA WG2","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: RAN WG2. Attachment: S2-180918","secretary_remarks":"Revision of S2-180919. Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10240,"status":"approved","reservation_date":"2018-01-25 18:15:07","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180919","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180729","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181236.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181237","title":"SMS reachability monitoring correction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The change in TS 23.682 CR 0228 is partially reversed.","secretary_remarks":"Revision of S2-180914. Agreed in parallel session. Block Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10550,"status":"agreed","reservation_date":"2018-01-25 18:15:07","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180914","revisedto":"","release":"Rel-13","crspec":23.682,"crspecversion":"13.9.0","workitem":[{"winame":"MONTE"}],"crnumber":379.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181237.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181238","title":"Alignment CR for for storing CE mode B UE capability in MME","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligns the table in TS 23.401 cl. 5.7.2 with the decision to store the UEs CE ModeB capability","secretary_remarks":"Revision of S2-180382. Agreed in parallel session. Block Approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":10970,"status":"agreed","reservation_date":"2018-01-25 18:15:09","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180382","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3378.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180113","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181238.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181239","title":"LS reply on the information exposed to the SCS\/AS for AS session establishment","source":"SA WG2","contact":"Belen Pancorbo","contact-id":66867,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: SA WG6","secretary_remarks":"Revision of S2-180233. Agreed in parallel session Revised to S2-181378.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11010,"status":"revised","reservation_date":"2018-01-25 18:15:10","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180233","revisedto":"S2-181378","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG6","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181239.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181240","title":"Paging failure for CE-capable UEs after 2G\/3G to 4G idle-mode mobility","source":"Intel, NTT DOCOMO","contact":"Puneet Jain","contact-id":36283,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the network supports CE-Capable UEs (see TS 36.300) after the 'first TAU in-idle mode following the RAT change', the MME may initiate UE Radio Capability Match Request procedure indicating to eNB that update to UE's Radio capability is needed. The eNB based on 'update needed' indicator requests the UE for its radio capability and provides it to the MME.","secretary_remarks":"Revision of S2-180836. Noted","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10290,"status":"noted","reservation_date":"2018-01-25 18:15:10","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180836","revisedto":"","release":"Rel-13","crspec":23.401,"crspecversion":"13.13.0","workitem":[{"winame":"TEI13"}],"crnumber":3386.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181240.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181241","title":"Paging failure for CE-capable UEs after 2G\/3G to 4G idle-mode mobility","source":"Intel, NTT DOCOMO","contact":"Puneet Jain","contact-id":36283,"tdoctype":"CR","for":"Approval","abstract":"Rel-14 mirror CR: Summary of change: If the network supports CE-Capable UEs (see TS 36.300) after the 'first TAU in-idle mode following the RAT change', the MME may initiate UE Radio Capability Match Request procedure indicating to eNB that update to UE's Radio capability is needed. The eNB based on 'update needed' indicator requests the UE for its radio capability and provides it to the MME.","secretary_remarks":"Revision of S2-180837. Noted","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10320,"status":"noted","reservation_date":"2018-01-25 18:15:11","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180837","revisedto":"","release":"Rel-14","crspec":23.401,"crspecversion":"14.6.0","workitem":[{"winame":"TEI13"}],"crnumber":3387.0,"crrevision":2.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181241.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181242","title":"Paging failure for CE-capable UEs after 2G\/3G to 4G idle-mode mobility","source":"Intel, NTT DOCOMO","contact":"Puneet Jain","contact-id":36283,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: If the network supports CE-Capable UEs (see TS 36.300) after the 'first TAU in-idle mode following the RAT change', the MME may initiate UE Radio Capability Match Request procedure indicating to eNB that update to UE's Radio capability is needed. The eNB based on 'update needed' indicator requests the UE for its radio capability and provides it to the MME.","secretary_remarks":"Revision of S2-180838. Revised to S2-181369.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10350,"status":"revised","reservation_date":"2018-01-25 18:15:12","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180838","revisedto":"S2-181369","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI13"}],"crnumber":3388.0,"crrevision":2.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181242.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181243","title":"[DRAFT] Reply LS on Paging failures for CE Capable UEs","source":"SA WG2","contact":"Puneet Jain","contact-id":36283,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, RAN WG2. Attachment: CR#3386 (Rel-13) vs. TS 23.401","secretary_remarks":"Revision of S2-180839. Revised to S2-181370.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10390,"status":"revised","reservation_date":"2018-01-25 18:15:13","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180839","revisedto":"S2-181370","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181243.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181244","title":"23.724: Key Issue on infrequent small data transmission","source":"Huawei, HiSilicon, InterDigital Inc, AT&T, Convida, Intel, Motorola Mobility, Lenovo, China Mobile, KPN","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue for small data transmission","secretary_remarks":"Revision of S2-180922. Agreed in parallel session. Block Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20700,"status":"approved","reservation_date":"2018-01-26 10:04:32","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180922","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181244.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181245","title":"23.724: Adding small data frequent communication key issue","source":"Ericsson, InterDigital Inc.","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Small data frequent communication key issue","secretary_remarks":"Revision of S2-180923. Revised in parallel session to S2-181249.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20760,"status":"revised","reservation_date":"2018-01-26 10:04:32","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180923","revisedto":"S2-181249","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181245.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181246","title":"23.724: Adding High latency key issue","source":"Ericsson, CATT, Convida Wireless, Samsung, Huawei, HiSilicon, Intel, AT&T, Qualcomm, LG Electronics","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"High latency key issue","secretary_remarks":"Revision of S2-181201. Agreed in parallel session. Block Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20830,"status":"approved","reservation_date":"2018-01-26 10:04:32","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181201","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181246.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181247","title":"23.724: Key Issue on Power Saving Functions","source":"Qualcomm Inc., Convida Wireless LLC, Huawei, HiSilicon, Verizon Wireless, Interdigital, China Mobile","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes some architectural assumptions and a Key Issue for FS_CIoT_5G related to power saving functions.","secretary_remarks":"Revision of S2-181202. Agreed in parallel session. Block Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20880,"status":"approved","reservation_date":"2018-01-26 10:04:32","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181202","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181247.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181248","title":"23.724: KI - Power Saving Functions","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"pCR","for":"Approval","abstract":"This paper discusses an FS_CIoT_5G Key Issue on Power Savings Functions","secretary_remarks":"Revision of S2-181203. Agreed in parallel session. Block Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20920,"status":"approved","reservation_date":"2018-01-26 10:04:32","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181203","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181248.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181249","title":"23.724: Adding small data frequent communication key issue","source":"Ericsson, InterDigital Inc.","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Small data frequent communication key issue","secretary_remarks":"Revision of S2-181245. Agreed in parallel session. Revised to S2-181376.","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20770,"status":"revised","reservation_date":"2018-01-26 10:04:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181245","revisedto":"S2-181376","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181249.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181250","title":"23.791: Discussion on big data and 5G","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution triggers discussion on big data analytic and 5G system.","secretary_remarks":"Revision of S2-181230. Approved","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21520,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181230","revisedto":"","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181250.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181251","title":"23.502: Clarification on AMF behavior due to Subscriber Data Change in UDM","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add description and reference to clause 4.2.4.2, align the terminology used in clause 4.2.4.2 with clause 4.5.1. Add the Configured NSSAI into the UE Configuration Update Command message.","secretary_remarks":"Revision of S2-180440. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12670,"status":"approved","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180440","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181251.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181252","title":"23.502: 502: clarification UDR usage in MM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that UDM\/PCF may invoke UDR services are clarified.","secretary_remarks":"Revision of S2-180292. Endorsed in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12710,"status":"endorsed","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180292","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181252.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181253","title":"23.501: UE specific DRX parameter negotiation between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revision of S2-180334. Revised to S2-181311.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12730,"status":"revised","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180334","revisedto":"S2-181311","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181253.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181254","title":"23.502: UE specific DRX parameter negotiaction between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revision of S2-180335. Revised to S2-181312.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12800,"status":"revised","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180335","revisedto":"S2-181312","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181254.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181255","title":"23.502: UE context removal in UDM during deregistration procedure","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: SMF invoke Nudm_SDM_Unsubscribe and Nudm_UECM_Deregistration service operations at Step 5 for the UDM to remove the corresponding subscription and UE context.","secretary_remarks":"Revision of S2-180658. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12850,"status":"approved","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180658","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181255.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181256","title":"23.501: Use of identifiers for mobility between GERAN\/UTRAN and 5GS","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies that upon mobility to the 5G System the UE may use a 5G-GUTI in the Registration procedure if it has a valid 5G-GUTI.  NOTE: the use of identifiers for mobility from the 5G System is clarified in TS 23.060.","secretary_remarks":"Revision of S2-180693. Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12900,"status":"approved","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180693","revisedto":"S2-181506","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181256.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181257","title":"Use of identifiers for mobility between GERAN\/UTRAN and 5GS","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that upon mobility from the 5G System the UE may use a P-TMSI in the GPRS Attach procedure if it has a valid P-TMSI.  NOTE: the use of identifiers for mobility to the 5G System is clarified in TS 23.501.","secretary_remarks":"Revision of S2-180701. This CR was agreed","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12920,"status":"agreed","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180701","revisedto":"","release":"Rel-15","crspec":23.06,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2035.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181257.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181258","title":"23.501: Management of service area restriction","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Service Area Restrictions that are sent to a UE consist of a single type of information, i.e., either Allowed Area or Non-Allowed Area.","secretary_remarks":"Revision of S2-180724. Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12940,"status":"approved","reservation_date":"2018-01-25 06:55:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180724","revisedto":"S2-182088","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181258.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181259","title":"[Draft] LS response on User Plane Security Policy","source":"SA WG2","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, RAN WG2, RAN WG3. CC: CT WG3. Attachments: S2-181198, S2-181199","secretary_remarks":"Revision of S2-181197. This LS was postponed in parallel session.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14040,"status":"postponed","reservation_date":"2018-01-25 06:56:08","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181197","revisedto":"S2-182012","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG2, RAN WG3","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181259.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181260","title":"23.501: Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Qualcomm Incorporated, Nokia, Nokia Shangai Bell","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation\/modification of a PDU session, or upon user plane establishment for a PDU session, determined the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Revision of S2-181198. Revised to S2-181304.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13940,"status":"revised","reservation_date":"2018-01-25 06:56:08","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181198","revisedto":"S2-181304","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181260.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181261","title":"23.502: User plane security policy","source":"Ericsson, Qualcomm Incorporated, Nokia, Nokia Shangai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Addition of User Plane Security Policy in the N2 SM info provided to RAN during UP connection activation.  The UP Sec. Policy is optionally provided by PCF to SMF, in case dynamic PCC is supported.","secretary_remarks":"Revision of S2-181199. Principles of this proposal were endorsed. Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14000,"status":"noted","reservation_date":"2018-01-25 06:56:08","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181199","revisedto":"S2-182009","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181261.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181262","title":"Reply LS on details of network identifiers","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2","secretary_remarks":"Revision of S2-181186. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12290,"status":"approved","reservation_date":"2018-01-25 06:56:08","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181186","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180008","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181262.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181263","title":"Reply LS on session management congestion control","source":"SA WG2","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-181188. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12410,"status":"approved","reservation_date":"2018-01-25 06:56:08","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181188","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180026","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181263.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181264","title":"Supporting Common API framework for SCEF","source":"Qualcomm Incorporated, Convida Wireless LLC","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that SCEF functionality including authentication, authorization and service capability API discovery are supported via T8 based on the Common API Framework (CAPIF).","secretary_remarks":"Revision of S2-180661. This CR was agreed. Revised at S2#126 in S2-182047","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18970,"status":"revised","reservation_date":"2018-01-25 06:56:08","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180661","revisedto":"S2-182047","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":382.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181264.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181265","title":"23.501: Supporting Common API framework for NEF","source":"Convida Wireless LLC, Qualcomm Incorporated","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies that functionality such as authentication, authorization and service capability API discovery are supported by the NEF based on the Common API Framework (CAPIF).","secretary_remarks":"Revision of S2-180432. Revised to S2-181353.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19000,"status":"revised","reservation_date":"2018-01-25 06:56:09","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180432","revisedto":"S2-181353","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181265.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181266","title":"23.501: Non-roaming Architecture for Network Exposure Function in reference point representation","source":"Intel","contact":"Puneet Jain","contact-id":36283,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Non-roaming architecture for Network Exposure Function reference point representation corresponding to service based interface between NEF and AF is added.","secretary_remarks":"Revision of S2-180655. Revised to S2-181354.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19050,"status":"revised","reservation_date":"2018-01-25 06:56:09","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180655","revisedto":"S2-181354","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181266.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181267","title":"23.502: Corrections to NRF and NSSF services","source":"Telecom Italia, ZTE, Oracle, Huawei","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Fixed the misaligment between clauses 4.2.2.2.3, 4.3.2.2.3, 4.17.5, 5.2.7.3 and 5.2.16. - Resolved the Editor's note on NRF as NSSF consumer. - Minor editorial change.","secretary_remarks":"Revision of S2-181126. Agreed in parallel session. Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19200,"status":"approved","reservation_date":"2018-01-25 06:56:09","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181126","revisedto":"S2-181847","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181267.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181268","title":"23.502: Improvements on the specification of the subscription to Network Exposure","source":"Nokia, Nokia Shanghai Bell, Huawei, CATT, ZTE, Hisilicon,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. \u00a7 4.15.1: adding target UE in the table 2. 5.2.2.3.2: add 'any UE' as target of AMF event subscription + Notification target address provided by Consumer NF \/ Subscription Correlation ID provided by Event Provider 3. Clarifying Notification target address and Subscription Correlation ID throughout all Event related services  4. Splitting up throughout all Nxxx Subscription services between Event Id (Mandatory, defined as part of the Nxxx service) and Event Filter information (Maximum number of reports, \u2026) where reference to 4.15.1 is made","secretary_remarks":"Revision of S2-181125. Agreed in parallel session. Block Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19140,"status":"approved","reservation_date":"2018-01-25 06:56:09","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181125","revisedto":"S2-181453, S2-181804","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181268.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181269","title":"23.501: NF Service Discovery","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. It is proposed to make sure that the NRF returns the HTTP URL-style endpoint address for the discovered NF service instances 2. NF Service Discovery is also service-based 3. NRF discovers the UPF's N4 reference point address.","secretary_remarks":"Revision of S2-181135. Agreed in parallel session. Block Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19520,"status":"approved","reservation_date":"2018-01-25 06:56:09","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181135","revisedto":"S2-181656","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181269.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181270","title":"23.502: NEF service definitions for AF influence","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add NEF service defintions to support AF influence. This paper relates to S2-180139 and S2-180480","secretary_remarks":"Revision of S2-181136. Revised to S2-181356.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19550,"status":"revised","reservation_date":"2018-01-25 06:56:09","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181136","revisedto":"S2-181356","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181270.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181271","title":"23.502: Usage of NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Specify a flow ( 4.17.X (new) ) for UPF discovery using the NRF. 2. Update NRF services so as to group NFStatusSubscribe and Nnrf_NFDiscoveryRequest in the same service as they handle the same data and clients (NF using NRF to get info on other NF) 3. Update NRF service operations with UPF related information such as UPF Discovery Information.","secretary_remarks":"Revision of S2-180063. Revised off-line to S2-181360","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13750,"status":"revised","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180063","revisedto":"S2-181360","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181271.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181272","title":"23.502: 502: Correction of UDR usage in SM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that UDM\/PCF may invoke UDR services are clarified.","secretary_remarks":"Revision of S2-180294. Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13730,"status":"endorsed","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180294","revisedto":"S2-181989","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181272.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181273","title":"23.501: Corrections to UPF selection and resolution of related Editor's Note","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Marge into a single list. Generalize the topological aspects that may be taken into account by the SMF. Remove editor's note.","secretary_remarks":"Revision of S2-180415. Revised to S2-181365.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13810,"status":"revised","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180415","revisedto":"S2-181365","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181273.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181274","title":"Key Open Issues of LADN Principles","source":"Drafting group","contact":"Changhong Shan","contact-id":45586,"tdoctype":"discussion","for":"Discussion","abstract":"Drafted based on the discussion during LADN Drafting Session","secretary_remarks":"Revision of S2-181113. Revised to S2-181358.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13230,"status":"revised","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181113","revisedto":"S2-181358","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_125_Gothenburg\/Docs\/S2-181274.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181275","title":"23.502: Cleanup of the service request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Per above reason of changes, the related clarification and changes are updated.","secretary_remarks":"Revision of S2-181164. Revised to S2-181279.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13370,"status":"revised","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181164","revisedto":"S2-181279","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181275.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181276","title":"23.501: Clarification on mobility event subscription transfer","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the new AMF notiifes current status only when the new AMF does not know the last reported status.","secretary_remarks":"Revision of S2-181165. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13430,"status":"approved","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181165","revisedto":"S2-181510","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181276.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181277","title":"23.502: Corrections to SMF selection","source":"Telecom Italia, ZTE, Oracle, NTT DOCOMO, Vodafone, Orange, Huawei, Ericsson","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Updated labels in figures 4.3.2.2.3.2-1, 4.3.2.2.3.3-1 and 4.3.2.2.3.3-2 with the correct service operation names, where the notation 'operation_name|xxx' indicates the intended service operation and its actual semantics. - Updated the text below the figures 4.3.2.2.3.2-1, 4.3.2.2.3.3-1 and 4.3.2.2.3.3-2 with the correct service operation names (same notation as in the figures). - Added missing parameters. - Added text to steps in 3(A) and 3(B) of Option 2 to align with steps 7-8 of Option 1 for SMF selection. - Removed steps in 3(C) of Option 2 for SMF selection. - Minor editorial changes","secretary_remarks":"Revision of S2-181120. This was Endorsed.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13700,"status":"endorsed","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181120","revisedto":"S2-181850","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181277.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181278","title":"23.502: Clarification on PDU Session Release timer provided to the UE for 'SSC mode 3'","source":"Huawei, HiSilicon, Intel, Qualcomm Incorporated","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Provide the release timer to the UE by transparent means.","secretary_remarks":"Revision of S2-181105. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13020,"status":"approved","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181105","revisedto":"S2-181547","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181278.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181279","title":"23.502: Cleanup of the service request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Per above reason of changes, the related clarification and changes are updated.","secretary_remarks":"Revision of S2-181275. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13380,"status":"approved","reservation_date":"2018-01-25 09:04:47","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181275","revisedto":"S2-181558","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181279.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181280","title":"Reply LS on timers for the network-requested PDU session modification procedure and 'SSC mode 3'","source":"SA WG2","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-181278","secretary_remarks":"Revision of S2-181104. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13070,"status":"approved","reservation_date":"2018-01-25 09:04:47","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181104","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180025","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181280.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181281","title":"23.501: 5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) PDB\/PER - clarify the condition for adding the packet to the PER. Current text is a bit ambiguous as it uses GBR as a boundary condition. It is ambiguous for implementation to determine the exact condition for considering the packets as lost and adding it to the PER. 2) Maximum Data Burst Volume - State the conditions for enforcing it in the UE for UL and UPF for DL. Otherwise, there is a possibility that huge amount of packets are sent \/ received causing the RAN not to be able to meet the necessary latency and relaibility requirement for delay critical 5QIs. 3) 5QI table - remove the 1ms note as it is not necessary to assume 1ms backhaul delay just for certain set of 5QIs, also removing reference to PCEF. 4) QoS characeteristics for Non-standardized 5QI is expected to be provided dynamically over signaling. Thus the minimum allowed ranges need not be specified. It is proposed to simply remove the EN.","secretary_remarks":"Revision of S2-181195. Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14480,"status":"approved","reservation_date":"2018-01-25 11:34:50","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181195","revisedto":"S2-181737","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181281.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181282","title":"23.716: Architecture principles for trusted non-3GPP access","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes the architecture principles for trusted non-3GPP access.","secretary_remarks":"Revision of S2-181173. Agreed in parallel session. Block Approved","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19920,"status":"approved","reservation_date":"2018-01-25 11:34:50","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181173","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181282.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181283","title":"23.716: Adding Architectural Principles for Wireline Access","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Proposes a set of architectural principles for the 5WWC work","secretary_remarks":"Revision of S2-181172. Agreed in parallel session. Block Approved","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19890,"status":"approved","reservation_date":"2018-01-25 11:34:50","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181172","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181283.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181284","title":"23.716: Definition and terminology","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to add definition and terminology and modify the text according to the new definitions.","secretary_remarks":"Revision of S2-181174. Revised to S2-181292.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19950,"status":"revised","reservation_date":"2018-01-25 11:34:50","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181174","revisedto":"S2-181292","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181284.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181285","title":"23.716: Access Type definition","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution introduce the applicability of Access Type concept for 5RG connected to wireline AN","secretary_remarks":"Revision of S2-181175. Revised to S2-181293.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20000,"status":"revised","reservation_date":"2018-01-25 11:34:51","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181175","revisedto":"S2-181293","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181285.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181286","title":"23.716: Modifying the Key Issue #7 Policy","source":"China Mobile, Huawei, HiSilicon","contact":"Wei Chen","contact-id":57801,"tdoctype":"pCR","for":"Approval","abstract":"This proposal aims to modify the key issue #7 policy to study the feasibility for PCF to support the policy of wireline network.","secretary_remarks":"Revision of S2-181178. Agreed in parallel session Revised to S2-181381.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20100,"status":"revised","reservation_date":"2018-01-25 11:34:51","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181178","revisedto":"S2-181381","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181286.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181287","title":"23.716: Revision on KI10 ATSSS in Hybrid Access","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution propose to update the KI10 for 5WWC","secretary_remarks":"Revision of S2-181180. Approved","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20180,"status":"approved","reservation_date":"2018-01-25 11:34:51","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181180","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181287.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181288","title":"23.716: Key issue for IPTV Support","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution propose the key issue of IPTV for 5WWC","secretary_remarks":"Revision of S2-181181. Agreed in parallel session. Block Approved","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20210,"status":"approved","reservation_date":"2018-01-25 11:34:51","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181181","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181288.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181289","title":"23.502: Correction to UE Registration","source":"Telecom Italia, ZTE, Oracle, Huawei","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Fixed the optionallity of the Mapping Of Requested NSSAI in clause 4.2.2.2.2. - Updated labels in figure 4.2.2.2.3-1 with the correct service operation names, where the notation 'operation_name|xxx' indicates the intended service operation and its actual semantics. - Updated the text below the figure 4.2.2.2.3-1 with the correct service operation names (same notation as in the figure). - Fixed the misaligment between clauses 4.2.2.2.3 and 5.2.16.2.1 adding the indication if a Subscribed S-NSSAI is marked as default S-NSSAI and a reference clause 5.2.16.2.1 for other input parameters not mentioned here.","secretary_remarks":"Revision of S2-181121. Endorsed in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11800,"status":"endorsed","reservation_date":"2018-01-25 11:34:51","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181121","revisedto":"S2-181849","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181289.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181290","title":"23.501: Clarification of UE Requested NSSAI","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that UE include S-NSSAI of established PDU sessions (PDN connections) into UE requested NSSAI.","secretary_remarks":"Revision of S2-181158. Revised to S2-181314.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11900,"status":"revised","reservation_date":"2018-01-25 11:34:51","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181158","revisedto":"S2-181314","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181290.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181291","title":"23.502: Different configured NSSAI based on device type","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add UE device type in term of SST (UE supported SST) in initial registration request and AMF may trigger UEconfiguration update procedure to update the Configured NSSAI.","secretary_remarks":"Revision of S2-181119. Revised to S2-181352.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11710,"status":"revised","reservation_date":"2018-01-25 11:34:51","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181119","revisedto":"S2-181352","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181291.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181292","title":"23.716: Definition and terminology","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to add definition and terminology and modify the text according to the new definitions.","secretary_remarks":"Revision of S2-181284. Revised to S2-181384.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19960,"status":"revised","reservation_date":"2018-01-25 11:35:04","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181284","revisedto":"S2-181384","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181292.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181293","title":"23.716: Access Type definition","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution introduce the applicability of Access Type concept for 5RG connected to wireline AN","secretary_remarks":"Revision of S2-181285. Revised to S2-181385.","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20010,"status":"revised","reservation_date":"2018-01-25 11:35:04","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181285","revisedto":"S2-181385","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181293.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181294","title":"Reserved forLaeYoung's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23790,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181295","title":"Reserved forLaeYoung's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23800,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181296","title":"Reserved forLaeYoung's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23810,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181297","title":"Reserved forLaeYoung's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23820,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181298","title":"Reserved forLaeYoung's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23830,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181299","title":"Reserved forLaeYoung's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23840,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181300","title":"Reserved forLaeYoung's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23850,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181301","title":"Reserved forLaeYoung's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23860,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181302","title":"Reserved forLaeYoung's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23870,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181303","title":"Reserved forLaeYoung's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23880,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181304","title":"23.501: Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Qualcomm Incorporated, Nokia, Nokia Shangai Bell, Ericsson","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation\/modification of a PDU session, or upon user plane establishment for a PDU session, determined the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Revision of S2-181260. This was Endorsed.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13950,"status":"endorsed","reservation_date":"2018-01-25 14:56:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181260","revisedto":"S2-181677","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181304.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181305","title":"23.502: Removal of re-registration cause\/indication for service reject","source":"LG Electronics, Huawei","contact":"Jinsook Ryu","contact-id":39022,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) It is proposed that when the Service Request is rejected due to unsynchronized UE parameter (e.g. Service area restriction is not updated since the UE is in MICO) between the UE and AMF, the AMF shall perform UE Configuration Update procedure as specified in clause 4.2.4 to provide UE parameter before the UE is sent to CM-IDLE state. 2) It is proposed to remove indicating re-registration cause\/indication in Service Reject.","secretary_remarks":"Revision of S2-181140. Noted","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16090,"status":"noted","reservation_date":"2018-01-25 14:56:48","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181140","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181305.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181306","title":"23.502: CR Control of the Messages triggering Paging at AMF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: AMF and other network functions together control the quantity of messages that require the AMF to page the UE. In addition to SMF control, if additional requests received while waiting for a UE response to the Paging Request message, the AMF may determines to reject it. Proposal 1: AMF and other network functions shall together control the quantity of messages that require the AMF to page the UE. Proposal 2: If the AMF has sent two Paging Messages to RAN node, the AMF shall reject the subsequent messages with a No Response to Previous Paging Indication. Proposal 3: If the AMF has a Paging Messages to RAN node, the AMF shall reject the subsequent messages without a higher priority.","secretary_remarks":"Revision of S2-181142. For e-mail approval. e-mail revision 5 approved. Revised to S2-181402.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16170,"status":"revised","reservation_date":"2018-01-25 14:56:48","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181142","revisedto":"S2-181402","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181306.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181307","title":"23.502: Paging Policy Differentiation correction","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Two changes are made for the Paging Policy Differentiation: 1. The indication of the corresponding QoS Flow is removed from the SMF buffering downlink data packet case. 2. PPI is removed from the N2 SM Information.","secretary_remarks":"Revision of S2-181145. WITHDRAWN","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16260,"status":"withdrawn","reservation_date":"2018-01-25 14:56:48","uploaded":null,"revisionof":"S2-181145","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181308","title":"23.502: Service Request procedure corrections","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: As above.","secretary_remarks":"Revision of S2-181146. Approved","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16300,"status":"approved","reservation_date":"2018-01-25 14:56:48","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181146","revisedto":"S2-182010, S2-182011","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181308.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181309","title":"23.502: Rejecting Service Request for UP reactivation","source":"LG Electronics","contact":"Sang Min Park","contact-id":62105,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Signalling connection indicator is introduced for the UE to inform its purpose of SR trigerring, and specified additional condition when the AMF can send Service Reject instead of Service Accept.","secretary_remarks":"Revision of S2-181148. Noted","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16370,"status":"noted","reservation_date":"2018-01-25 14:56:48","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181148","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181309.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181310","title":"23.502: Clean-up of the registration procedure","source":"Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. At registration: The SUPI may only be provided by the UE in case of an Emergency Registration 2. \u00a74.2.2.2.1:transform the EN 'Aspects related to dual registration in 3GPP and non-3GPP access is FFS' into a reference to \u00a74.12 3. \u00a74.2.2.2.2 step 14: If the serving NF removal reason indicated by the UDM is Initial Registration, then the old AMF does not invoke the Namf_EventExposure_Notify but invokes the Nsmf_PDUSession_ReleaseSMContext (SUPI, PDU Session ID) service operation towards all the associated SMFs  4. \u00a74.2.2.2.2 Step 18 : clarify that 'when the AMF has changed the new AMF notifies the SMF for each PDU sessions that it has taken over the responsibility of the signalling path towards the UE: the new AMF invokes the Nsmf_PDUSession_UpdateSMContext service operation using SMF information received from the old AMF at step 5. It also indicates whether the 'PDU Session(s) is to be re-activated' 5. \u00a74.2.2.2.2  requires miscellaneous corrections \/ clarifications;","secretary_remarks":"Revision of S2-181191. Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12590,"status":"approved","reservation_date":"2018-01-25 14:56:48","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181191","revisedto":"S2-181455","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181310.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181311","title":"23.501: UE specific DRX parameter negotiation between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revision of S2-181253. Revised to S2-181341.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12740,"status":"revised","reservation_date":"2018-01-25 14:56:48","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181253","revisedto":"S2-181341","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181311.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181312","title":"23.502: UE specific DRX parameter negotiaction between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revision of S2-181254. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12810,"status":"approved","reservation_date":"2018-01-25 14:56:48","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181254","revisedto":"S2-181560","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181312.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181313","title":"23.501: Network sharing prioritised PLMN handling","source":"Ericsson, Qualcomm Inc.","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding support for prioritized PLMN selection at UE for idle mode mobility and and at interworking with EPS. Also clarified that 23.122 does not define all cases where multiple MNCs used within a country.","secretary_remarks":"Revision of S2-181077. Revised to S2-181348.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11270,"status":"revised","reservation_date":"2018-01-25 18:15:13","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181077","revisedto":"S2-181348","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181313.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181314","title":"23.501: Clarification of UE Requested NSSAI","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that UE include S-NSSAI of established PDU sessions (PDN connections) into UE requested NSSAI.","secretary_remarks":"Revision of S2-181290. Revised off-line to S2-181342.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11910,"status":"revised","reservation_date":"2018-01-25 18:15:26","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181290","revisedto":"S2-181342","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181314.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181315","title":"23.501: Clarify NSSF discovery","source":"Huawei, Hisilicon, Telecom Italia","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The NSSF discovery function shall utilize an appropriate configured NRF to discover the NSSF instance(s) unless NSSF information is available by other means, e.g. local configuration, and select a NSSF instance based on the obtained NSSF information.","secretary_remarks":"Revision of S2-181159. Revised to S2-181346.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11950,"status":"revised","reservation_date":"2018-01-25 18:15:26","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181159","revisedto":"S2-181346","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181315.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181316","title":"23.501: Slice selection cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The S-NSSAIs used by the UE when moving from EPS to 5GS are clarified.","secretary_remarks":"Revision of S2-181161. Revised to S2-181347.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12020,"status":"revised","reservation_date":"2018-01-25 18:15:26","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181161","revisedto":"S2-181347","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181316.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181317","title":"Adding 5GS to the Network Architecture","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a reference to 5GS.","secretary_remarks":"Revision of S2-181103. Agreed in parallel session. Block Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11540,"status":"agreed","reservation_date":"2018-01-25 18:15:26","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181103","revisedto":"","release":"Rel-15","crspec":23.002,"crspecversion":"14.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":304.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"SP-180094","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181317.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181318","title":"23.501: Slicing configuration update","source":"Motorola Mobility, Lenovo","contact":"Genadi Velev","contact-id":70944,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution proposes to update the Newtork Slice configuration description implementing the Prosals 1 - 4 from the 'Reason for change'.","secretary_remarks":"Revision of S2-181163. Revised to S2-181351.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11670,"status":"revised","reservation_date":"2018-01-25 18:15:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181163","revisedto":"S2-181351","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181318.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181319","title":"23.791: FS_eNA Key Issue: NWDA-Assisted Traffic Routing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a key issue to study solutions to support traffic routing using statistical information from NWDAF.","secretary_remarks":"Revision of S2-181231. Approved","agenda_item_sort_order":35,"ainumber":"6.11","ainame":"Study of enablers for Network Automation for 5G (FS_eNA)","tdoc_agenda_sort_order":21560,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181231","revisedto":"","release":"Rel-16","crspec":23.791,"crspecversion":"0.0.0","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181319.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181320","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23350,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181321","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23360,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181322","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23370,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181323","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23380,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181324","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23390,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181325","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23400,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181326","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23410,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181327","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23420,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181328","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23430,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181329","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23440,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181330","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23450,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181331","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23460,"status":"withdrawn","reservation_date":"2018-01-26 20:07:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181332","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23470,"status":"withdrawn","reservation_date":"2018-01-26 20:07:26","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181333","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23480,"status":"withdrawn","reservation_date":"2018-01-26 20:07:26","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181334","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23490,"status":"withdrawn","reservation_date":"2018-01-26 20:07:26","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181335","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23500,"status":"withdrawn","reservation_date":"2018-01-26 20:07:26","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181336","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23510,"status":"withdrawn","reservation_date":"2018-01-26 20:07:26","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181337","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23520,"status":"withdrawn","reservation_date":"2018-01-26 20:07:26","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181338","title":"Reserved for Puneet's parallel sessions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"Withdrawn - Not used","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":23530,"status":"withdrawn","reservation_date":"2018-01-26 20:07:26","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181339","title":"23.716: New KI on LADN, SSC Mode, Location Reporting","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to add new KIs on LADN, SSC Modes and Location reporting.","secretary_remarks":"Revision of S2-181183. Approved","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20260,"status":"approved","reservation_date":"2018-01-25 18:15:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181183","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181339.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181340","title":"23.502: Clarification related to Subscription data type","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Alignment the descriptions with the Table 5.2.3.3.1-1 - Adding an new type 'Slice Selection Subscription data' into the Table 5.2.3.3.1-1  It can be used for the Registration with AMF re-allocation. Instead of getting whole subscription data, get  only information for slice selection. - Adding an additional field (UE context for a PDU session) for SMF Selection Subscription data into the  Table 5.2.3.3.1-1  It was an agreement during non-3GPP related session at SA#124 that the UE context for a PDU session  stored in UDM can be used for the H-SMF selection in HR roaming, in case of the handover to 3GPP  access from N3GPP access via different PLMN. - Adding an additional field (Static IP address\/prefix) for Session Management Subscription data into the  Table 5.2.3.3.1-1.","secretary_remarks":"Revision of S2-181190. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12550,"status":"approved","reservation_date":"2018-01-25 18:15:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181190","revisedto":"S2-181527","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181340.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181341","title":"23.501: UE specific DRX parameter negotiation between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revision of S2-181311. Revised to S2-181363.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12750,"status":"revised","reservation_date":"2018-01-25 18:15:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181311","revisedto":"S2-181363","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181341.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181342","title":"23.501: Clarification of UE Requested NSSAI","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that UE include S-NSSAI of established PDU sessions (PDN connections) into UE requested NSSAI.","secretary_remarks":"Revision of S2-181314. Noted in parallel session","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11920,"status":"noted","reservation_date":"2018-01-25 18:15:39","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181314","revisedto":"S2-182183","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181342.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181343","title":"[DRAFT] Reply LS on Mobility management congestion control","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to CT WG1 LS in C1-175413\/S2-180027 on MM congestion control. This LS pertains to the handling of MM back-off timer across 3GPP systems","secretary_remarks":"Revision of S2-181189. This was postponed.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12460,"status":"postponed","reservation_date":"2018-01-25 18:15:39","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181189","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181343.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181344","title":"23.501: Align the terms of mapping of Requested NSSAI and Configured NSSAI for the HPLMN","source":"Huawei, Hisilicon, Telecom Italia, ETRI","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: The AMF or the NSSF shall perform the mapping between Allowed NSSAI and Configured NSSAI for the HPLMN to align with the description in the Registration procedure of TS 23.502. Change 2: If AMF queries the NSSF during PDU Session Establishment procedure, the AMF provides S-NSSAI of the Allowed NSSAI and the S-NSSAI with the corresponding value from the Configured NSSAI for the HPLMN if provided by UE to the NSSF.","secretary_remarks":"Revision of S2-180664. This was Endorsed.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11750,"status":"endorsed","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180664","revisedto":"S2-181586","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181344.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181345","title":"23.502: Slice selection cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following changes are done:  - Clarifying what the S-NSSAIs relate to e.g. PLMN  -Adding Mapping Of Allowed NSSAI to the UE MM Context table  - The S-NSSAI corresponding to the PDU Session stored in the UE Context is the one valid for the serving PLMN (i.e. the same as used in the Allowed NSSAI).  - Adding S-NSSAI and optionally NSI ID as IEs for the Nnwdaf_EventsSubscription service  - Adding DNN sent back to the UE at PDU Session Establishment  - Removing S-NSSAI sent to the UE at PDU Session Establishment","secretary_remarks":"Revision of S2-181157. Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11870,"status":"approved","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181157","revisedto":"S2-181631","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181345.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181346","title":"23.501: Clarify NSSF discovery","source":"Huawei, Hisilicon, Telecom Italia","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The NSSF discovery function shall utilize an appropriate configured NRF to discover the NSSF instance(s) unless NSSF information is available by other means, e.g. local configuration, and select a NSSF instance based on the obtained NSSF information.","secretary_remarks":"Revision of S2-181315. Agreed in parallel session. Block Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11960,"status":"approved","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181315","revisedto":"S2-181585","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181346.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181347","title":"23.501: Slice selection cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The S-NSSAIs used by the UE when moving from EPS to 5GS are clarified.","secretary_remarks":"Revision of S2-181316. Agreed in parallel session. Block Approved","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":12030,"status":"approved","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181316","revisedto":"S2-181614","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181347.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181348","title":"23.501: Network sharing prioritised PLMN handling","source":"Ericsson, Qualcomm Inc., Intel, AT&T, Vodafone","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding support for prioritized PLMN selection at UE for idle mode mobility and and at interworking with EPS. Also clarified that 23.122 does not define all cases where multiple MNCs used within a country.","secretary_remarks":"Revision of S2-181313. This was Endorsed.","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11280,"status":"endorsed","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181313","revisedto":"S2-181639","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181348.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181349","title":"23.502: Network sharing prioritised PLMN handling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying PLMN selection related to shared networks in combination with interworking and access changes.","secretary_remarks":"Revision of S2-181099. WITHDRAWN","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11340,"status":"withdrawn","reservation_date":"2018-01-26 10:04:47","uploaded":null,"revisionof":"S2-181099","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181350","title":"23.501: Network Sharing and Interworking with EPS- TS 23.501","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Delete the network behaviour description from clause 5.18.3. Clarify how NG-RAN selects the target PLMN in the order of (1) PLMN in use, (2) Prioritized list of PLMN IDs, (3) EPLMN list during the handover within 5GS. Add corresponding description on how UE selects the network during mobility between 5GS and EPS in case of network sharing and interworking with EPS. Add reference in clause 5.17 to address how network selection is performed by UE during Idle Mode mobility between 5GS and EPS for the single registration mode in case of network sharing.","secretary_remarks":"Revision of S2-181078. WITHDRAWN","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11310,"status":"withdrawn","reservation_date":"2018-01-26 10:04:47","uploaded":null,"revisionof":"S2-181078","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181351","title":"23.501: Slicing configuration update","source":"Motorola Mobility, Lenovo","contact":"Genadi Velev","contact-id":70944,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution proposes to update the Newtork Slice configuration description implementing the Prosals 1 - 4 from the 'Reason for change'.","secretary_remarks":"Revision of S2-181318. For e-mail approval. WITHDRAWN","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11680,"status":"withdrawn","reservation_date":"2018-01-26 10:04:47","uploaded":null,"revisionof":"S2-181318","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181352","title":"23.502: Different configured NSSAI based on device type","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add UE device type in term of SST (UE supported SST) in initial registration request and AMF may trigger UEconfiguration update procedure to update the Configured NSSAI.","secretary_remarks":"Revision of S2-181291. For e-mail approval. WITHDRAWN","agenda_item_sort_order":18,"ainumber":"6.5.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":11720,"status":"withdrawn","reservation_date":"2018-01-26 10:04:47","uploaded":null,"revisionof":"S2-181291","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181353","title":"23.501: Supporting Common API framework for NEF","source":"Convida Wireless LLC, Qualcomm Incorporated","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies that functionality such as authentication, authorization and service capability API discovery are supported by the NEF based on the Common API Framework (CAPIF).","secretary_remarks":"Revision of S2-181265. Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19010,"status":"approved","reservation_date":"2018-01-26 10:04:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181265","revisedto":"S2-181988","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181353.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181354","title":"23.501: Non-roaming Architecture for Network Exposure Function in reference point representation","source":"Intel","contact":"Puneet Jain","contact-id":36283,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Non-roaming architecture for Network Exposure Function reference point representation corresponding to service based interface between NEF and AF is added.","secretary_remarks":"Revision of S2-181266. This was endorsed.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19060,"status":"endorsed","reservation_date":"2018-01-26 10:04:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181266","revisedto":"S2-181696","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181354.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181355","title":"23.502: Clarification on the services for External Parameter Provisioning","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Modify the original figure of 4.15.6.2-1, and related descriptions in clause 4.15.6.2 to reflect the proposals mentioned above.","secretary_remarks":"Revision of S2-181129. Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19310,"status":"approved","reservation_date":"2018-01-26 10:04:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181129","revisedto":"S2-181556","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181355.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181356","title":"23.502: NEF service definitions for AF influence","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add NEF service defintions to support AF influence. This paper relates to S2-180139 and S2-180480","secretary_remarks":"Revision of S2-181270. Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19560,"status":"approved","reservation_date":"2018-01-26 10:04:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181270","revisedto":"S2-181584","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181356.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181357","title":"23.502: Application Trigger procedure updates","source":"Ericsson, Convida Wireless LLC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The usage of Nudm_SDM_Get operation is described including new Subscription Data type: 'Identity translation'. This new Subscription Data type requires GPSI as access key, instead of SUPI. Nnef_Trigger service operation names are updated to reflect better the functionality performed.","secretary_remarks":"Revision of S2-181131. Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19420,"status":"approved","reservation_date":"2018-01-26 10:04:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181131","revisedto":"S2-181638","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181357.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181358","title":"Key Open Issues of LADN Principles","source":"Drafting group","contact":"Changhong Shan","contact-id":45586,"tdoctype":"discussion","for":"Discussion","abstract":"Drafted based on the discussion during LADN Drafting Session","secretary_remarks":"Revision of S2-181274. Conclusions endorsed in parallel session.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13240,"status":"endorsed","reservation_date":"2018-01-26 10:04:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181274","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_125_Gothenburg\/Docs\/S2-181358.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181359","title":"[DRAFT] LS on Unsynchronized UE parameter during Service Request","source":"SA WG2","contact":"Jinsook Ryu","contact-id":39022,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Created at meeting Revised to S2-181367.","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16100,"status":"revised","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"","revisedto":"S2-181367","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181359.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181360","title":"23.502: Usage of NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Specify a flow ( 4.17.X (new) ) for UPF discovery using the NRF. 2. Update NRF services so as to group NFStatusSubscribe and Nnrf_NFDiscoveryRequest in the same service as they handle the same data and clients (NF using NRF to get info on other NF) 3. Update NRF service operations with UPF related information such as UPF Discovery Information.","secretary_remarks":"Revision of S2-181271. Revised to S2-181364.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13760,"status":"revised","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181271","revisedto":"S2-181364","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181360.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181361","title":"23.793: Key Issue update for Traffic Splitting over Multi-access","source":"ZTE, Oracle","contact":"Tricci So","contact-id":44974,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes update to the key issue studying the traffic splitting over multi-access in ATSSS by referring to the real-life use case of MPTCP support by iOS.","secretary_remarks":"Revision of S2-180984. Approved","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20450,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-30 10:57:54","revisionof":"S2-180984","revisedto":"","release":"Rel-16","crspec":23.793,"crspecversion":"0.1.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181361.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181362","title":"23.793: New KI and Alternative architecture framework for ATSSS","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes a new key issue and an alternative architecture framework for ATSSS.","secretary_remarks":"Revision of S2-180986. Approved","agenda_item_sort_order":32,"ainumber":"6.8","ainame":"Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture (FS_ATSSS)","tdoc_agenda_sort_order":20510,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180986","revisedto":"","release":"Rel-16","crspec":23.793,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181362.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181363","title":"23.501: UE specific DRX parameter negotiation between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revision of S2-181341 For e-mail approval. e-mail revision 6 approved. Revised to S2-181395.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12760,"status":"revised","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181341","revisedto":"S2-181395","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181363.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181364","title":"23.502: Usage of NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Specify a flow ( 4.17.X (new) ) for UPF discovery using the NRF. 2. Update NRF services so as to group NFStatusSubscribe and Nnrf_NFDiscoveryRequest in the same service as they handle the same data and clients (NF using NRF to get info on other NF) 3. Update NRF service operations with UPF related information such as UPF Discovery Information.","secretary_remarks":"Revision of S2-181360. For e-mail approval. e-mail revision 2 approved. Revised to S2-181396.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13770,"status":"revised","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181360","revisedto":"S2-181396","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181364.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181365","title":"23.501: Corrections to UPF selection and resolution of related Editor's Note","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Marge into a single list. Generalize the topological aspects that may be taken into account by the SMF. Remove editor's note.","secretary_remarks":"Revision of S2-181273. For e-mail approval. e-mail revision 1 approved. Revised to S2-181397.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13820,"status":"revised","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181273","revisedto":"S2-181397","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181365.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181366","title":"23.501: Updates to the Security Edge Protection Proxy description","source":"Ericsson, Telecom Italia","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying that the message filtering and policing by the SEPP is achieved without requiring updates of SLAs between the two PLMNs.","secretary_remarks":"Revision of S2-181184. For e-mail approval. e-mail revision 3 approved. Revised to S2-181398.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14090,"status":"revised","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181184","revisedto":"S2-181398","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181366.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181367","title":"[DRAFT] LS on Unsynchronized UE parameter during Service Request","source":"SA WG2","contact":"Jinsook Ryu","contact-id":39022,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-181359. For e-mail approval. Noted","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16110,"status":"noted","reservation_date":"2018-01-26 17:55:39","uploaded":"2018-01-29 10:17:52","revisionof":"S2-181359","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181367.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181368","title":"Reply LS on Reliability for eV2X","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: CT WG1. Attachment: S2-181088 (TS 23.285 CR#0037)","secretary_remarks":"Revision of S2-181092. Approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11130,"status":"approved","reservation_date":"2018-01-26 17:55:39","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181092","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180034","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181368.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181369","title":"Paging failure for CE-capable UEs after 2G\/3G to 4G idle-mode mobility","source":"Intel, NTT DOCOMO","contact":"Puneet Jain","contact-id":36283,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the network supports CE-Capable UEs (see TS 36.300) after the 'first TAU in-idle mode following the RAT change', the MME may initiate UE Radio Capability Match Request procedure indicating to eNB that update to UE's Radio capability is needed. The eNB based on 'update needed' indicator requests the UE for its radio capability and provides it to the MME.","secretary_remarks":"Revision of S2-181242. This CR was agreed. Ericsson objected to the agreement of this CR. Revised at S2#126 in S2-182322","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10360,"status":"revised","reservation_date":"2018-01-26 17:55:39","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181242","revisedto":"S2-181711","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3388.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181369.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181370","title":"Reply LS on Paging failures for CE Capable UEs","source":"SA WG2","contact":"Puneet Jain","contact-id":36283,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, RAN WG2. Attachment: S2-181369 - CR#3388 (Rel-15) vs. TS 23.401","secretary_remarks":"Revision of S2-181243. Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10400,"status":"approved","reservation_date":"2018-01-26 17:55:40","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181243","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-175972","lsto":"RAN WG3, RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181370.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181371","title":"CIoT Attach correction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of the option that conflicts with TS 36.300.","secretary_remarks":"Revision of S2-180840. This CR was agreed. Revised at S2#126 in S2-182239 and S2-182240. This was unagreed at SA WG2#126.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10460,"status":"noted","reservation_date":"2018-01-26 17:55:40","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180840","revisedto":"S2-182239, S2-182240","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"CIoT"},{"winame":"TEI15"}],"crnumber":3390.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181371.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181372","title":"23.501: Draft CR 23.501 Correction to Emergency Fallback","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Rephrasing to alllow emergency session over untrusted N3GPP access if the emergency session could not be established via 3GPP access - Indications are mutually exclusive - Misc. editorial corrections (Emergency Services)","secretary_remarks":"Revision of S2-181215. For e-mail approval. Approved","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16850,"status":"approved","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181215","revisedto":"S2-181773","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181372.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181373","title":"[DRAFT] LS OUT on IMS registration for Dual-Registered UE","source":"SA WG2","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, CT WG4","secretary_remarks":"Revision of S2-181219. For e-mail approval. WITHDRAWN","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":17140,"status":"withdrawn","reservation_date":"2018-01-26 17:55:41","uploaded":null,"revisionof":"S2-181219","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181374","title":"23.726: Key Issue Proposal: SMF and UPF Insert\/Relocation due to UE Mobility","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"In this contribution, it is proposed a new key issue to study the SMF and UPF insert or relocation due to UE mobility.","secretary_remarks":"Revision of S2-181047. For e-mail approval. Approved","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21840,"status":"approved","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181047","revisedto":"","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181374.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181375","title":"23.726: FS_ETSUN \/ 23.726 Key Issue: Support of the preservation of a PDU session while the UE moves out of an SMF service area","source":"Nokia, Nokia Shanghai Bell, Ericsson, CATT, Huawei","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"pCR","for":"Approval","abstract":"FS_ETSUN \/ 23.726 Key Issue: Support of the preservation of a PDU session while the UE moves out of an SMF service area","secretary_remarks":"Revision of S2-181048. For e-mail approval. e-mail revision 2 approved. Revised to S2-181406.","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21710,"status":"revised","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181048","revisedto":"S2-181406","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181375.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181376","title":"23.724: Adding small data frequent communication key issue","source":"Ericsson, InterDigital Inc.","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"pCR","for":"Approval","abstract":"Small data frequent communication key issue","secretary_remarks":"Revision of S2-181249. Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":20780,"status":"approved","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181249","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181376.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181377","title":"23.502: Clarification on Communication Pattern and Expected UE behaviour","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add the Communication Pattern parameters into the parameter list of Expected UE Behaviour.","secretary_remarks":"Revision of S2-181124. For e-mail approval. WITHDRAWN","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19110,"status":"withdrawn","reservation_date":"2018-01-26 17:55:41","uploaded":null,"revisionof":"S2-181124","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181378","title":"LS reply on the information exposed to the SCS\/AS for AS session establishment","source":"SA WG2","contact":"Belen Pancorbo","contact-id":66867,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: SA WG6","secretary_remarks":"Revision of S2-181239. Approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11020,"status":"approved","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181239","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180030","lsto":"CT WG3","Cc":"SA WG6","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181378.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181379","title":"23.724: Key Issue on Network Parameter Configuration API via NEF","source":"Convida Wireless LLC, Intel","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"pCR","for":"Approval","abstract":"This paper proposes a Key Issue on Network Parameter Configuration API via NEF for the FS_CIoT_5G TR","secretary_remarks":"Revision of S2-180880. Approved","agenda_item_sort_order":33,"ainumber":"6.9","ainame":"Study on Cellular IoT support and evolution for the 5G System (FS_CIoT_5G)","tdoc_agenda_sort_order":21050,"status":"approved","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180880","revisedto":"","release":"Rel-16","crspec":23.724,"crspecversion":"0.0.0","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181379.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181380","title":"23.502: Clarification on 5G-GUTI in EPS to 5GS Mobility Registration Procedure using N26","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) The following clarification is made regarding in step 2 when the UE includes the native 5G-GUTI and the GUAMI part of the native 5G-GUTI in the Registration request and RRC, respectively: When the native 5G-GUTI is assigned during a Registration procedure performed over a non-3GPP access, the UE includes the native 5G-GUTI as an additional GUTI in the Registration Request and for idle mode mobility the GUAMI part of the native 5G-GUTI in RRC only if the 3GPP access that the UE registers is in the same PLMN for the non-3GPP access that the UE is registered.  2) Re-wording is made for clarity in steps 17-18 regarding when the UE uses the updated 5G-GUTI in the Registration Accept:","secretary_remarks":"Revision of S2-181022. Approved","agenda_item_sort_order":28,"ainumber":"6.5.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":18840,"status":"approved","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181022","revisedto":"S2-181497","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181380.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181381","title":"23.716: Modifying the Key Issue #7 Policy","source":"China Mobile, Huawei, HiSilicon","contact":"Wei Chen","contact-id":57801,"tdoctype":"pCR","for":"Approval","abstract":"This proposal aims to modify the key issue #7 policy to study the feasibility for PCF to support the policy of wireline network.","secretary_remarks":"Revision of S2-181286. Approved","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20110,"status":"approved","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181286","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181381.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181382","title":"New SID on Enhanced support of Vertical and URLLC Services","source":"Nokia, Nokia Shanghai Bell, Qualcomm, SK Telecom, Telecom Italia, Siemens, Robert Bosch GmbH, Charter Communications, AT&T, Comcast, NTT DoCoMo, KDDI, Samsung","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"SID new","for":"Approval","abstract":"The objective is to study enhancements to 5GS that are required to fulfill the objectives of normative Vertical and URLLLC service requirements, agreed by SA WG1 as part of the 2 study items concluded in SA WG1: FS_CAV and FS_5GLAN.","secretary_remarks":"Revision of S2-181075. This was postponed.","agenda_item_sort_order":45,"ainumber":"7.1","ainame":"New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals","tdoc_agenda_sort_order":23300,"status":"postponed","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181075","revisedto":"S2-181767","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181382.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181383","title":"23.502: update Nnrf_NFDiscovery service based on the UE IP address","source":"China Mobile","contact":"Wei Chen","contact-id":57801,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: New texts are added to clarify that UE IP address can be a opitional input parameter in Nnrf_NFDiscovery service to allow NEF to discover the BSF with the input of UE IP address.  Besides, BSF is added into the cosumers list of Nnrf_NFManagement_NFRegister service to make NRF to store the BSF service information.","secretary_remarks":"Revision of S2-181130. For e-mail approval. e-mail revision 2 approved. Revised to S2-181405.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19370,"status":"revised","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181130","revisedto":"S2-181405","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181383.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181384","title":"23.716: Definition and terminology","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution proposes to add definition and terminology and modify the text according to the new definitions.","secretary_remarks":"Revision of S2-181292. Approved","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":19970,"status":"approved","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181292","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181384.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181385","title":"23.716: Access Type definition","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"pCR","for":"Approval","abstract":"This contribution introduce the applicability of Access Type concept for 5RG connected to wireline AN","secretary_remarks":"Revision of S2-181293. Approved","agenda_item_sort_order":31,"ainumber":"6.7","ainame":"Study on the Wireless and Wireline Convergence for the 5G system architecture (FS_5WWC)","tdoc_agenda_sort_order":20020,"status":"approved","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181293","revisedto":"","release":"Rel-16","crspec":23.716,"crspecversion":"0.1.0","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181385.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181386","title":"23.503: UE policies granularity and UE assistance for policy evaluation.","source":"Ericsson, NEC, Lenovo","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that a URSP\/WLANSP rule contains an identifier and that the PCF can perform operations (add\/delete\/replace) per individual URSP\/WLANSP rule. The UE sends at initial registration the list of UE policies currently stored in the device and the PCF uses this information as input for policy decisitions.","secretary_remarks":"Revision of S2-181040. For e-mail approval. e-mail revision 4 approved. Revised to S2-181399.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14590,"status":"revised","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-29 07:57:53","revisionof":"S2-181040","revisedto":"S2-181399","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181386.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181387","title":"23.502: Cleanup of NamfEventExposure and NsmfEventExposure services","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Definition of a services, Namf_EventExposure and Nsmf_EventExposure are clarified.","secretary_remarks":"Revision of S2-180992. For e-mail approval. Noted","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15350,"status":"noted","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-29 13:27:54","revisionof":"S2-180992","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181387.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181388","title":"23.502: Correction on PCF selection in SMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Add description about the AMF provide PCF information to SMF for PCF selection in PDU session management related procedures. 2. Correct the service name of step 3a and 5 in figure 4.3.2.2.1.","secretary_remarks":"Revision of S2-180999. For e-mail approval. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15540,"status":"approved","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-29 10:17:52","revisionof":"S2-180999","revisedto":"S2-181575, S2-182169","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181388.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181389","title":"23.503: Remove EN related with Session binding","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. \u00a7 6.1.3.2.2: Session Binding applies only for PDU Sessions of IP type 2. \u00a7 6.1.1.2: remove the EN and add that S-NSSAI is part of the data used for session binding 3. Clarifications and Editorials:.","secretary_remarks":"Revision of S2-181005. For e-mail approval. Postponed","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15650,"status":"postponed","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:55","revisionof":"S2-181005","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181389.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181390","title":"Handling of emergency sessions over untrusted N3GPP access in 5GS","source":"MediaTek Inc.","contact":"Maurice Pope","contact-id":648,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - The requirement is introduced","secretary_remarks":"Revision of S2-181216. For e-mail approval. This CR was agreed","agenda_item_sort_order":26,"ainumber":"6.5.8","ainame":"Specific services support","tdoc_agenda_sort_order":16880,"status":"agreed","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:55","revisionof":"S2-181216","revisedto":"","release":"Rel-15","crspec":23.167,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":321.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180094","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181390.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181391","title":"23.503: Resource reservation for services sharing priority","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: PCF functional description of resource reservation for service sharing priority is updated to align with the functional description of this feature in TS 23.203.","secretary_remarks":"Revision of S2-180996. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15460,"status":"approved","reservation_date":"2018-01-30 08:49:39","uploaded":"2018-01-30 08:57:58","revisionof":"S2-180996","revisedto":"S2-181634","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181391.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181392","title":"LS on applicability of Connection Establishment Indication procedure after the establishment of S1 logical connection","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. Attachment: S2-181371","secretary_remarks":"e-mail revision 2 of S2-180900. Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10480,"status":"approved","reservation_date":"2018-02-02 10:04:21","uploaded":"2018-02-02 10:30:31","revisionof":"S2-180900","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181392.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181393","title":"Clarification on PRA reporting in ECM-IDLE state","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the behaviour of MME\/S4-SGSN upon receiving request for notification of change of UE presence in PRA when UE is in CM-IDLE state.","secretary_remarks":"e-mail revision 1 of S2-181029. This CR was agreed","agenda_item_sort_order":9,"ainumber":"5.2","ainame":"QoS and PCC Maintenance","tdoc_agenda_sort_order":10810,"status":"agreed","reservation_date":"2018-02-02 10:04:21","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181029","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3381.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180113","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181393.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181394","title":"Correction to cancelled monitoring Event in the network parameter configuration via SCEF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Decouple the procedures of Monitoring related procedure and network parameter configuration related procedure. If the HSS cancelled a monitoring event in step 4 and the cancelled monitoring event is subscribed by the SCEF which is the same as the one sending the Set Suggested Network Configuration Request, Cancelled SCEF Reference ID is included in the response and set to the SCEF Reference ID of the cancelled Monitoring Event. If the HSS cancelled a monitoring event in step 4 and the cancelled monitoring event is subscribed by the SCEF which is different from the SCEF sending the Set Suggested Network Configuration Request, HSS sends the Monitoring Indication message towards the SCEF which subscribed the cancelled monitoring event and includes SCEF Reference ID of a cancelled Monitoring Event. If the SCEF received Cancelled SCEF Reference ID in step 10\/10a, the steps 2-5 of Network-initiated Explicit Monitoring Event Deletion procdure defined in subclause 5.6.9 are","secretary_remarks":"e-mail revision 2 of S2-180917. This CR was agreed","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maintenance. - essential corrections - excluding Rel-15 5GS","tdoc_agenda_sort_order":11050,"status":"agreed","reservation_date":"2018-02-02 10:04:23","uploaded":"2018-02-02 10:30:31","revisionof":"S2-180917","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":378.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180109","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181394.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181395","title":"TS 23.501: UE-specific DRX parameter negotiation between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"e-mail revision 6 of S2-181363. Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12770,"status":"approved","reservation_date":"2018-02-02 10:04:24","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181363","revisedto":"S2-181559","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181395.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181396","title":"23.502: Usage of NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Specify a flow ( 4.17.X (new) ) for UPF discovery using the NRF. 2. Update NRF services so as to group NFStatusSubscribe and Nnrf_NFDiscoveryRequest in the same service as they handle the same data and clients (NF using NRF to get info on other NF) 3. Update NRF service operations with UPF related information such as UPF Discovery Information.","secretary_remarks":"e-mail revision 2 of S2-181364. Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13780,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181364","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181396.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181397","title":"23.501: Corrections to UPF selection and resolution of related Editor's Note","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Marge into a single list. Generalize the topological aspects that may be taken into account by the SMF. Remove editor's note.","secretary_remarks":"e-mail revision 1 of S2-181365. Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13830,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181365","revisedto":"S2-181610","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181397.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181398","title":"23.501: Updates to the Security Edge Protection Proxy description","source":"Ericsson, Telecom Italia","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying that the message filtering and policing by the SEPP is achieved without requiring updates of SLAs between the two PLMNs.","secretary_remarks":"e-mail revision 3 of S2-181366. Approved","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14100,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181366","revisedto":"S2-181611","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181398.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181399","title":"23.503: UE policies granularity and UE assistance for policy evaluation.","source":"Ericsson, NEC, Lenovo","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that a URSP\/WLANSP rule contains an identifier and that the PCF can perform operations (add\/delete\/replace) per individual URSP\/WLANSP rule. The UE sends at initial registration the list of UE policies currently stored in the device and the PCF uses this information as input for policy decisitions.","secretary_remarks":"e-mail revision 4 of S2-181386. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14600,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181386","revisedto":"S2-181612","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181399.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181400","title":"23.502: Correction on the Policy association procedure during AMF relocation","source":"Huawei, HiSilicon,Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Reclassified the Policy Association Establishment procedure into two cases: a) Policy Association Establishment procedure with new PCF (No UE context); b) Policy Association Establishment procedure with old PCF (Has UE context). 2. Update the existing description for the procedure that old PCF is used. 3. Update the description about the Policy Association Establishment procedure in registration.","secretary_remarks":"e-mail revision 2 of S2-181054. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15320,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181054","revisedto":"S2-181573","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181400.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181401","title":"23.502: Selecting a common PCF for UE and Session Policies","source":"Cisco Systems, Inc","contact":"Ravi Shekhar","contact-id":71185,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Optionally, passing the selected PCF Id by AMF to SMF.","secretary_remarks":"e-mail revision 1 of S2-180997. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15490,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-180997","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181401.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181402","title":"23.502: CR Control of the Messages triggering Paging at AMF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: AMF and other network functions together control the quantity of messages that require the AMF to page the UE. In addition to SMF control, if additional requests received while waiting for a UE response to the Paging Request message, the AMF may determines to reject it. Proposal 1: AMF and other network functions shall together control the quantity of messages that require the AMF to page the UE. Proposal 2: If the AMF has sent two Paging Messages to RAN node, the AMF shall reject the subsequent messages with a No Response to Previous Paging Indication. Proposal 3: If the AMF has a Paging Messages to RAN node, the AMF shall reject the subsequent messages without a higher priority.","secretary_remarks":"e-mail revision 5 of S2-181306. Approved","agenda_item_sort_order":24,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16180,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181306","revisedto":"S2-181564","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181402.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181403","title":"23.501: CN assistance information enhancement","source":"NEC, Sony","contact":"Iskren Ianev","contact-id":59515,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following new assistance information is added to the RRC Inactive assistance information from the AMF to the gNB: - UE stationary indication. If the AMF is aware the connecting UE is stationary (e.g. from the UE mobility pattern in the AMF, see clause 5.3.4.2), the AMF may include in the 'RRC Inactive assistance information' an UE stationary indication to help with the NG RAN decision on whether to move the UE in RRC Inactive state and if so, what RNA to configure for it (e.g. the size of RNA); - UE moving trajectory information. If the AMF is aware of the connecting UE's moving trajectory (e.g. from the UE mobility pattern in the AMF, see clause 5.3.4.2), the AMF may include in the 'RRC Inactive assistance information' an UE moving trajectory information (e.g. the list of cells that are overlapped with the UE moving trajectory) to help with the NG-RAN decision on what RNA to configure for the UE in case the UE is moved to RRC Inactive state (e.g. the size and\/or","secretary_remarks":"e-mail revision 1 of S2-181234. Approved","agenda_item_sort_order":25,"ainumber":"6.5.7.5","ainame":"RRC_inactive related","tdoc_agenda_sort_order":16470,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181234","revisedto":"S2-181679","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181403.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181404","title":"23.502 Clarification of mobility procedure from EPS to 5GS without N26 interface","source":"Orange","contact":"Thouraya Toukabri","contact-id":66374,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: addition that Notify message MME > HSS shall be sent when when the subscription data indicates that the user is allowed use 5G as a RAT type in order to handle EPS to 5GS handover.","secretary_remarks":"e-mail revision 1 of S2-180808. Approved","agenda_item_sort_order":27,"ainumber":"6.5.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":18130,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-180808","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181404.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181405","title":"23.502: update Nnrf_NFDiscovery service based on the UE IP address","source":"China Mobile","contact":"Wei Chen","contact-id":57801,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: New texts are added to clarify that UE IP address can be a opitional input parameter in Nnrf_NFDiscovery service to allow NEF to discover the BSF with the input of UE IP address.  Besides, BSF is added into the cosumers list of Nnrf_NFManagement_NFRegister service to make NRF to store the BSF service information.","secretary_remarks":"e-mail revision 2 of S2-181383. Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19380,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181383","revisedto":"S2-181783","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181405.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181406","title":"23.726: FS_ETSUN \/ 23.726 Key Issue: Support of the preservation of a PDU session while the UE moves out of an SMF service area","source":"Nokia, Nokia Shanghai Bell, Ericsson, CATT, Huawei","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"pCR","for":"Approval","abstract":"FS_ETSUN \/ 23.726 Key Issue: Support of the preservation of a PDU session while the UE moves out of an SMF service area","secretary_remarks":"e-mail revision 2 of S2-181375. Approved","agenda_item_sort_order":36,"ainumber":"6.12","ainame":"Study on Enhancing Topology of SMF and UPF in 5G Networks (FS_ETSUN)","tdoc_agenda_sort_order":21720,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181375","revisedto":"","release":"Rel-16","crspec":23.726,"crspecversion":"0.0.0","workitem":[{"winame":"FS_ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181406.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181407","title":"Reply LS on clarification on Restricted Operator Services","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG1, SA WG3. CC: CT WG1","secretary_remarks":"e-mail revision 5 of S2-181045. Approved","agenda_item_sort_order":40,"ainumber":"6.16","ainame":"Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (FS_PARLOS_SA2)","tdoc_agenda_sort_order":22630,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181045","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180043","lsto":"SA WG1, SA WG3","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181407.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181408","title":"Chairmans Notes at close of meeting (Frank Mademann)","source":"SA WG2 Chairman","contact":"Maurice Pope","contact-id":648,"tdoctype":"report","for":"Information","abstract":"ChairmansNotes_Frank_01-26-1800 final","secretary_remarks":"Provided by MCC for information. Not Handled","agenda_item_sort_order":4,"ainumber":"3","ainame":"Meeting reports","tdoc_agenda_sort_order":10030,"status":"not treated","reservation_date":"2018-02-02 10:57:41","uploaded":"2018-02-02 10:58:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181408.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181409","title":"Chairmans Notes at close of parallel sessions (Krisztian Kiss)","source":"Convenor (Apple)","contact":"Maurice Pope","contact-id":648,"tdoctype":"report","for":"Information","abstract":"ChairmansNotes_Krisztian_01-26-1255","secretary_remarks":"Provided by MCC for information. Not Handled","agenda_item_sort_order":4,"ainumber":"3","ainame":"Meeting reports","tdoc_agenda_sort_order":10040,"status":"not treated","reservation_date":"2018-02-02 10:57:41","uploaded":"2018-02-02 10:58:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181409.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181410","title":"Chairmans Notes at close of parallel sessions (Puneet Jain)","source":"Convenor (Intel)","contact":"Maurice Pope","contact-id":648,"tdoctype":"report","for":"Information","abstract":"ChairmansNotes_Puneet_01-26-1130","secretary_remarks":"Provided by MCC for information. Not Handled","agenda_item_sort_order":4,"ainumber":"3","ainame":"Meeting reports","tdoc_agenda_sort_order":10050,"status":"not treated","reservation_date":"2018-02-02 10:57:41","uploaded":"2018-02-02 10:58:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181410.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181411","title":"Chairmans Notes at close of parallel sessions (LaeYoung Kim)","source":"Convenor (LGE)","contact":"Maurice Pope","contact-id":648,"tdoctype":"report","for":"Information","abstract":"ChairmansNotes_LaeYoung_01-26-0920","secretary_remarks":"Provided by MCC for information. Not Handled","agenda_item_sort_order":4,"ainumber":"3","ainame":"Meeting reports","tdoc_agenda_sort_order":10060,"status":"not treated","reservation_date":"2018-02-02 10:57:41","uploaded":"2018-02-02 10:58:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181411.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181412","title":"Chairmans Notes at close of parallel sessions (Irfan Ali)","source":"Convenor (Cisco)","contact":"Maurice Pope","contact-id":648,"tdoctype":"report","for":"Information","abstract":"ChairmansNotes_Irfan_01-26-1245","secretary_remarks":"Provided by MCC for information. Not Handled","agenda_item_sort_order":4,"ainumber":"3","ainame":"Meeting reports","tdoc_agenda_sort_order":10070,"status":"not treated","reservation_date":"2018-02-02 10:57:41","uploaded":"2018-02-02 10:58:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181412.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181413","title":"Reserved for e-mail approval revisions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24120,"status":"withdrawn","reservation_date":"2018-02-02 10:57:41","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181414","title":"Reserved for e-mail approval revisions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24130,"status":"withdrawn","reservation_date":"2018-02-02 10:57:41","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181415","title":"Reserved for e-mail approval revisions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24140,"status":"withdrawn","reservation_date":"2018-02-02 10:57:41","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181416","title":"Reserved for e-mail approval revisions","source":"-","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"","abstract":"-","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":50,"ainumber":"99","ainame":"Withdrawn and reserved documents","tdoc_agenda_sort_order":24150,"status":"withdrawn","reservation_date":"2018-02-02 10:57:41","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]