[{"name":"S2-184650","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":"Postponed S2-183052 from S2#127. Response drafted in S2-185303. Final response in S2-186291","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11200,"status":"replied to","reservation_date":"2018-05-04 06:13:09","uploaded":"2018-05-04 06:17:56","revisionof":"S2-183052","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5","Cc":"","lsoriginalls":"IOTTF17 Doc003","lsreply":"S2-186291","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184650.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184659","title":"LS from RAN WG2: LS on UE differentiation in NB-IoT","source":"RAN WG2","contact":"Martin Van Der Zee","contact-id":58600,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 discussed the UE differentiation information in NB-IoT, and agreed that it is useful to introduce a vendor specific UE differentiation information IE on S1-AP\/X2-AP interface for NB-IoT to exchange UE differentiation information that has been monitored in the eNB.","secretary_remarks":"Postponed S2-183076 from S2#127. Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11310,"status":"noted","reservation_date":"2018-05-04 06:13:09","uploaded":"2018-05-04 06:17:56","revisionof":"S2-183076","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"CT WG1, SA WG2","lsoriginalls":"R2-1804106","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184659.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184662","title":"LS from RAN WG3: Reply LS on EDT procedures and AS NAS interaction","source":"RAN WG3","contact":"Wang Yan","contact-id":54091,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks RAN WG2 for the LS on EDT procedures and AS NAS interaction. RAN WG3 discussed on EDT procedures, and would like to provide feedback on the following question 5 about the expected delay of steps 4, 5 and 6: 5: In order to define the correct timing between msg3 and msg4 as well as to meet the timing requirements defined for an RRC connection, RAN WG2 asks for input on the expected delay of steps 4, 5 and 6 in figure 2. RAN WG3 answer: - In case there is no DL PDU, or one buffered DL, or more than one buffered DL PDUs to be transmitted, the latency is 2 times of S1 signalling delay, e.g. 20 ms. - In case there is only one expected DL response PDU to be transmitted, the latency will be two times of backhaul delay (eNB<-->MME<-->SGW<-->PGW<-->Server) plus application server processing time.","secretary_remarks":"Postponed S2-183082 from S2#127. Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11140,"status":"noted","reservation_date":"2018-05-04 06:13:09","uploaded":"2018-05-04 06:17:56","revisionof":"S2-183082","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2, CT WG1","Cc":"SA WG3","lsoriginalls":"R3-181573","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184662.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184665","title":"LS from RAN WG2: Reply LS on EDT procedures and AS NAS interaction","source":"RAN WG2","contact":"Johan Johansson","contact-id":44956,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks CT WG1 for the Reply LS on EDT procedures and AS NAS interaction. Regarding MME awareness of EDT, RAN WG2 expects that RAN WG3 will inform on EDT agreements and assumptions related to S1, e.g. functionality to avoid excessive delay before EDT response is sent. CT WG1 asks 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? Answer to CT WG1: Yes, RAN WG2 think that RAI information in the UE is useful for the AS layer to decide whether to use EDT. RAN WG2 has not discussed whether inter-layer interaction need to be specified or not.","secretary_remarks":"Postponed S2-183093 from S2#127. Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11160,"status":"noted","reservation_date":"2018-05-04 06:13:09","uploaded":"2018-05-04 06:17:56","revisionof":"S2-183093","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"RAN WG3, SA WG2","lsoriginalls":"R2-1803885","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184665.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184667","title":"LS from RAN WG2: Reply LS to Reply LS on UE differentiation for Rel-15 NB-IoT","source":"RAN WG2","contact":"Odile Rollinger","contact-id":60606,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for their reply LS on UE differentiation for Rel-15 NB-IoT. RAN WG2 has further discussed the parameters listed by RAN WG2 in their initial LS (S2-178227\/R2-1711895) and an overview of the parameters is provided in the table below:. {...} RAN WG2 would like to provide the following answers to SA WG2 questions for the parameters included in the table. Parameters #5 and #7 RAN WG2 considers these parameters (ON\/OFF) can accurately be predefined and reliably provided as part of the subscription parameters. These parameters are static or semi-static. RAN WG2 also considers these parameters are essential parameters with no dependencies with other. Traffic related parameters #1, #3, #4 and #6 Some companies think that a number of NB-IoT applications have very predictable traffic pattern, and that for these applications, the parameters can be accurately predefined, stored in the HSS as subscription parameters and reliably provided by the CN. All the paramete","secretary_remarks":"Postponed S2-183095 from S2#127. Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11320,"status":"noted","reservation_date":"2018-05-04 06:13:09","uploaded":"2018-05-04 06:17:56","revisionof":"S2-183095","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3, CT WG1","lsoriginalls":"R2-1803821","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184667.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184671","title":"LS from SA WG5: LS Reply to SA2 on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"SA WG5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 thanks SA WG2 for their LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic. In SA WG5 charging specifications for EPC (TS 32.251), the RAT type is already specified as an information which can be used for traffic volume differentiation. Similarly as for NB-IoT, addition of a new RAT type value will allow to categorize the UEs traffic as LTE-M from charging's perspective. This solution has no impact on SA WG5 specifications, based on the assumption the '3GPP RAT Type' specified in CT WG3 TS 29.061, which is referred to for charging, is extended with this new value. Action: SA WG5 asks SA WG2 group to take the information above into account.","secretary_remarks":"Postponed S2-183863 from S2#127. Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11230,"status":"noted","reservation_date":"2018-05-04 06:13:09","uploaded":"2018-05-04 06:17:56","revisionof":"S2-183863","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3, CT WG3, CT WG4, RAN WG2","lsoriginalls":"S5-182334","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184671.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184687","title":"LS from CT WG3: LS on Security for NEF Northbound APIs","source":"CT WG3","contact":"Yali Yan","contact-id":66362,"tdoctype":"LS in","for":"Information","abstract":"CT WG3 is specifying the 5G NEF Northbound APIs (over N33 reference point) under 5GS_Ph1-CT work item, the 4G SCEF Northbound APIs (over T8 reference point) under NAPS-CT work item, and the CAPIF APIs under CAPIF-CT work item. For NEF Northbound APIs, CT WG3 has agreed that the N33 will reuse the same APIs applicable for T8 if possible, and agreed that the TLS as described in 3GPP TS 33.187 for T8 shall also be supported over N33. According to CT WG3's understanding, SA WG2 agreed that the 3rd Party application server can use T8\/N33 Northbound APIs without the support of any CAPIF related requirements (i.e. the support of CAPIF is optional for the SCEF\/NEF and application server). Delegates in CT WG3 have different understanding whether the SA WG3 CAPIF work item impacts the T8 and N33 reference points (which correspond to the CAPIF-2\/CAPIF-2e reference point). Can SA WG3 kindly provide the following clarifications: 1. Which specification under the SA WG3 remit should be referenced for","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11540,"status":"noted","reservation_date":"2018-05-04 06:13:10","uploaded":"2018-05-04 06:17:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2, SA WG6","lsoriginalls":"C3-182459","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184687.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184690","title":"LS from CT WG4: Reply LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks SA WG2 for their LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic. CT WG4 confirms that it is possible to specify a new RAT-Type value for LTE-M for the Core Network internal interfaces under CT WG4 remit. For the GTP-C interfaces, backward compatibility requires the MME to signal a new RAT Type value only to EPC entities (MME, SGW and PGW) known to support such new value, as otherwise the PDN connection establishment procedure could fail. The solution assumes PLMN wide homogenous support (MME, SGW, PGW) of the new LTE-M RAT- Type value. For Home-Routed scenarios, the legacy EUTRA RAT-Type would be sent to the PGW, unless the HPLMN asked as part of roaming agreement to send the LTE-M RAT type value. Besides, CT WG4 would also like to ask whether the Access Restriction Data in the user subscription would need to be enhanced to allow restricting access to LTE-M. Action: CT WG4 asks SA WG2 group to take the above response into account and to provide","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11240,"status":"noted","reservation_date":"2018-05-04 06:13:10","uploaded":"2018-05-04 06:17:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3, CT WG3, SA WG5","lsoriginalls":"C4-183278","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184690.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184697","title":"LS from RAN WG2: LS on GAD shape(s) for high accuracy positioning","source":"RAN WG2","contact":"Manivannan Thyagarajan","contact-id":68484,"tdoctype":"LS in","for":"Action","abstract":"As part of the work on UE Positioning Accuracy Enhancements for LTE (RP-172313), RAN WG2 has identified the need for new GAD shape or shapes to be able to report a 'high-accuracy' location estimate with finer resolution. The existing GAD shapes in TS 23.032 have a latitude\/longitude\/altitude resolution which is not suitable for 'high accuracy' location estimate requiring finer resolution. The following definition of HighAccuracy3Dpoint, which RAN WG2 agreed to include in TS 36.355 (R2-1804776), illustrates the signalling requirement for latitude\/ longitude\/altitude with finer resolution. Note that there is a need for multiple shapes definition to take in to account the different uncertainty shapes (ellipse, CEP) and also to be able to independently provide horizontal and vertical uncertainty of the 'high accuracy' location estimate. {...} RAN WG2 also attempted one possible suggested updates to TS 23.032 for coding related to HighAccuracy3Dpoint which is provided below for information.","secretary_remarks":"Postponed","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11890,"status":"postponed","reservation_date":"2018-05-04 06:13:10","uploaded":"2018-05-04 06:17:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"R2-1806492","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184697.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184698","title":"LS from RAN WG3: Response to LS on encrypting broadcasted positioning data and LS on provisioning of positioning assistance data via LPPa for broadcast","source":"RAN WG3","contact":"Luis Lopes","contact-id":47178,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG2 for their LS on 'encrypting broadcasted positioning data and LS on provisioning of positioning assistance data via LPPa for broadcast'. Discussion on this WI is ongoing in RAN WG3. RAN WG3 reviewed the CR to 23.271 attached to the afore mentioned LS and would like to confirm that this CR in line with RAN WG3 requirements, hence can be endorsed from RAN WG3 point of view. RAN WG3 understands that this baseline will be reviewed by SA WG2 once the details of broadcast support by E-UTRAN are completed in RAN. Action: RAN WG3 requests SA WG2 to take the above feedback into account.","secretary_remarks":"Postponed","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11900,"status":"postponed","reservation_date":"2018-05-04 06:13:10","uploaded":"2018-05-04 06:17:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, CT WG1, CT WG4","lsoriginalls":"R3-182409","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184698.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184700","title":"LS from RAN WG3: LS on use of SPID for EN-DC","source":"RAN WG3","contact":"Angelo Centonza","contact-id":35887,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3would like to inform SA WG2 that a decision has been taken to forward the SPID index from the MENB to the SgNB, in order to allow consistent usage of RRM policies at MN and SN in EN-DC cases. The agreed CR is attached. Action: RAN WG3 kindly asks SA WG2 to take above agreements into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11670,"status":"noted","reservation_date":"2018-05-04 06:13:10","uploaded":"2018-05-04 06:17:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"R3-182485","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184700.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184702","title":"LS from RAN WG3: Reply LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"RA WG3","contact":"Wang Yan","contact-id":54091,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to thank SA WG2 for their LSs on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic. RAN WG3 discussed how to provide such information from eNB to MME, and agreed to introduce 'LTE-M Indication' from eNB to MME in UE CAPABILITY INFO INDICATION message as the attached agreed CR. Action: RAN WG3 kindly asks SA WG2, CT WG3, CT WG4, and SA WG5 to take above into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11250,"status":"noted","reservation_date":"2018-05-04 06:13:10","uploaded":"2018-05-04 06:17:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG3, CT WG4, SA WG5","Cc":"RAN WG2","lsoriginalls":"R3-182505","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184702.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184703","title":"LS from RAN WG3: LS on UE differentiation in NB-IoT","source":"RAN WG3","contact":"Manook Soghomonian","contact-id":69668,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 has endorsed the enclosed CRs as Baseline for the NB_IOTenh2-Core work. Action: RAN WG3 kindly ask SA WG2 to take the above into account and provide feedback if needed.","secretary_remarks":"Response drafted in S2-185434. Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11330,"status":"noted","reservation_date":"2018-05-04 06:13:10","uploaded":"2018-05-04 06:17:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, SA WG3","lsoriginalls":"R3-182509","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184703.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184710","title":"LS from SA WG6: LS on V2X configuration","source":"SA WG6","contact":"Basavaraj (Basu) Pattan","contact-id":61285,"tdoctype":"LS in","for":"Action","abstract":"V2X study in SA WG6 has defined a solution for provisioning of PC5 parameters via V1 reference point (in TR 23.795 Subclause 7.6 Solution #6). SA WG2 in TS 23.285 specified multiple mechanisms for provisioning of the PC5 parameters to UE e.g. pre-configured at the UE, provisioned by the V2X control function. TS 23.285 also specifies that the parameters provisioned by the V2X Control Function take precedence over the configured parameters on the UE. However, SA WG6 believes that the precedence when PC5 parameters are provisioned via multiple mechanisms is subject to business policies. Action: SA WG6 kindly asks SA WG2 to take note of the SA WG6 position, and provide any feedback.","secretary_remarks":"Response drafted in S2-185221. Final response in S2-185692","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11810,"status":"replied to","reservation_date":"2018-05-04 06:13:10","uploaded":"2018-05-04 06:17:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S6-180721","lsreply":"S2-185692, S2-185692","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184710.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184711","title":"LS from SA WG6: Reply LS on CAPIF4xMB","source":"SA WG6","contact":"Basavaraj (Basu) Pattan","contact-id":61285,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 would like to thank SA WG4 for sending LS S6-180605 seeking clarifications regarding update to xMB reference point to make it CAPIF compliant. SA WG6 intends to provide a response during the SA WG6#24 meeting. Questions related to security impacts should be addressed by SA WG3.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11560,"status":"noted","reservation_date":"2018-05-04 06:13:10","uploaded":"2018-05-04 06:17:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4, SA WG3","Cc":"CT WG3, SA WG2","lsoriginalls":"S6-180727","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184711.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184737","title":"LS from SA WG1: Reply LS on URLLC","source":"SA WG1","contact":"Betsy Covell","contact-id":68109,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 thanks SA WG2 for their Reply LS on URLLC. After discussing the questions asked by SA WG2, SA WG1 has provided the following answers. {...} Action: SA WG1 asks SA WG2 to take the above answers into account in your work.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11730,"status":"noted","reservation_date":"2018-05-17 10:04:37","uploaded":"2018-05-17 11:14:12","revisionof":"S2-182137","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2","lsoriginalls":"S1-181657","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184737.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184830","title":"Discussion Paper on Reachability Reports","source":"Convida Wireless LLC","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses Reachability Reports and how they are used","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11580,"status":"noted","reservation_date":"2018-05-18 19:40:56","uploaded":"2018-05-21 19:12:18","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_127BIS_Newport_Beach\/Docs\/S2-184830.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184831","title":"Indicating the Reachability Report Cause","source":"Convida Wireless LLC","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updated the reporting procedures (5.6.3.3 and 5.6.8.3) to say that the Monitoring Event Report indicates if the event was caused by the UE changing to connected mode or by the UE becoming reachable for paging.  Updated section 5.7.2 to explain that the SCS\/AS may send MT data when receiving a Monitoring Event Report indicating that the event was caused by the UE changing to connected mode.  Updated the UE Reachability Reporting procedure for roaming scenarios (5.6.8.3) to say that the event is also reported when and when the UE will become reachable for paging. Thus, making it consistent with the non-roaming scenario and general description.","secretary_remarks":"Revised in parallel session to S2-185696.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11590,"status":"revised","reservation_date":"2018-05-18 19:43:24","uploaded":"2018-05-21 19:12:18","revisionof":"","revisedto":"S2-185696","release":"Rel-15","crspec":23.682,"crspecversion":"15.4.0","workitem":[{"winame":"NAPS"}],"crnumber":399.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184831.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184839","title":"Introduction of local RRM policy specific UE differentiation","source":"Ericsson, Vodafone, AT&T","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The new Local RRM UE Differentiation Information is defined and added to the procedures that are using following messages: 1) S1AP: UE INFORMATION TRANSFER (for CP solution) 2) S1AP: CONNECTION ESTABLISHMENT INDICATION (for CP solution) 3) S1AP: DOWNLINK NAS TRANSPORT(for CP solution and UP solution) 4) S1AP: INITIAL CONTEXT SETUP REQUEST (for UP solution) 5) S1AP: PATH SWITCH REQUEST ACKNOWLEDGE (for UP solution) 6) S1AP: HANDOVER REQUEST (for UP solution) 7) S1AP: UE CONTEXT RELEASE COMPLETE (for CP and UP solution) 8) S1AP: HANDOVER REQUIRED (for UP solution) Further, the new information shall be stored in the MME and forwarded at idle mode mobility between MMEs.","secretary_remarks":"Revised in parallel session to S2-185715.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11360,"status":"revised","reservation_date":"2018-05-18 20:13:43","uploaded":"2018-05-22 01:22:52","revisionof":"","revisedto":"S2-185715","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"NB_IOTenh2-Core"}],"crnumber":3431.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184839.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184859","title":"Fixing Group NIDD","source":"Ericsson, Convida Wireless LLC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Allow the SCS\/AS to configure NIDD for a UE group.  Introduce authorization of a External Group ID in HSS at NIDD configuration.  Minimize HSS signalling in clause 5.5.3 at Group Message Delivery via unicast MT NIDD by using a list stored in SCEF instead of doing an additional HSS query.","secretary_remarks":"Revision of (Withdrawn) S2-183222 from S2#127. Revised in parallel session to S2-185697.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11610,"status":"revised","reservation_date":"2018-05-18 20:22:44","uploaded":"2018-05-22 01:22:52","revisionof":"S2-183222","revisedto":"S2-185697","release":"Rel-15","crspec":23.682,"crspecversion":"15.4.0","workitem":[{"winame":"NAPS"}],"crnumber":393.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184859.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184860","title":"TLTRI and TTRI Usage","source":"Ericsson, Convida Wireless LLC?, Huawei?, Nokia?, Nokia Shanghai Bell?","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Summary of changes in SA WG2#127BIS:  The Group NIDD Delivery (5.5.3) needs TLTRI sent from the SCS\/AS.  Summary of Change 1:  Updated the definition of TLTRI so that it is assigned by the SCEF and updated all T8 procedures accordingly.  Summary of Change 2 (in the MT NIDD Procedure of 5.13.3):  Added a parameter called 'non-IP data sequence number' to the MT NIDD procedures. This value is assigned by the SCEF and can be used by the SCS\/AS to override previously buffered data instead of TTRI. Thus, the TTRI parameter functionality is no longer overloaded.  Summary of Change 3 (in the MT NIDD Procedure of 5.13.3):  Added the buffer indication to step 5.  Summary of Change 4:  TTRI is removed from all procedures since it is not used in stage 3 and not needed due to the constraints of HTTP. Also, its presence in stage 2 is misleading in the sense that it leads the reader to believe that responses can be received out of order. Also, added a note in section 4.9.2 clarifyi","secretary_remarks":"Revision of (Agreed) S2-183927 from S2#127. Confirm Sources!. Revised in parallel session to S2-185698.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11640,"status":"revised","reservation_date":"2018-05-18 20:22:45","uploaded":"2018-05-22 01:22:52","revisionof":"S2-183927","revisedto":"S2-185698","release":"Rel-15","crspec":23.682,"crspecversion":"15.4.0","workitem":[{"winame":"NAPS"}],"crnumber":392.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184860.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184885","title":"Differentiating LTE-M (eMTC) Traffic","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"This paper propose an altenative CN solution.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11260,"status":"noted","reservation_date":"2018-05-18 20:33:02","uploaded":"2018-05-22 12:49:05","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184885.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184886","title":"Differentiating LTE-M (eMTC) Traffic","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: (1) MME retrieves UE Category M (also called 'LTE-M indication' in TS 36.413) from eNB as follows: When MME request eNB to retrieve UE Radio Capablity, and eNB receives the UE Radio Capability from the UE, the eNB includes LTE-M indication IE in S1AP UE CAPABILITY INFO INDICATION (see TS36.413) if the UE category is Cat M1 or Cat-M2 (see TS 36.306, clause 4.1A).  (2) During Initial Attach or UE requested PDN connectivity procedure, if UE Category M info in LTE-M Indicaiaton IE is recevied from the eNodeB, the MME includes this info in a separate IE in Create Session Request to the SGW and then to PGW. (3) During Initial Attach, if UE Category M info is not available when Create Session Request is sent and becomes available at Modify Bearer Request, MME includes the UE Category M in Modify Bearer Request to the SGW which shall then forward the message to PGW.  (4) At inter-MME TAU or Handover, the source\/old MME transfers the UE Category M if available to the target\/n","secretary_remarks":"Noted","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11270,"status":"noted","reservation_date":"2018-05-18 20:33:02","uploaded":"2018-05-22 12:49:05","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"CIoT"},{"winame":"TEI15"}],"crnumber":3432.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184886.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184907","title":"Subscription for Aerial UE in 3GPP system","source":"Ericsson, NTT DoCoMo, Qualcomm Incorporated, Intel","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce a new subscription parameter in HSS which is transferred to MME during Attach, TAU and Change in Subscription information and MME provides the information to eNB when UE context is established. Version 3: remove service request as it is wrongly included in the following text: Support of Aerial UE function is stored in the user's subscription information in HSS. HSS transfers this information to the MME via Update Location message during Attach, Service Request and Tracking Area Update procedures.","secretary_remarks":"Revision of (Agreed) S2-184058 from S2#127. Revised in parallel session to S2-185716.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11390,"status":"revised","reservation_date":"2018-05-20 13:36:03","uploaded":"2018-05-22 01:22:52","revisionof":"S2-184058","revisedto":"S2-185716","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"LTE_Aerial"}],"crnumber":3411.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184907.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185061","title":"Identification of LTE-M (eMTC) traffic","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - When eNB receives the UE radio capability, the eNB extracts the cat-M1\/M2 information. If UE is cat-M1\/M2, the eNB provides the Cat-M1\/M2 information separately in a different IE to MME - The MME stores this information, until UE detaches. - The MME provides the Cat-M1\/M2 information to S-GW\/P-GW as a new RAT type - In case of MME change, the source MME provides the cat-M1\/M2 information to the target MME over S10.","secretary_remarks":"Revision of (Endorsed) S2-182412 from S2#126. CT WG4 dependent CR (C4-184277 ). Revised in parallel session to S2-185714.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11280,"status":"revised","reservation_date":"2018-05-21 11:41:51","uploaded":"2018-05-22 11:34:19","revisionof":"S2-182412","revisedto":"S2-185714","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"}],"crnumber":3404.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185061.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185152","title":"Early data transmission status in RAN WGs and impacts to SA2","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"tdoctype":"discussion","for":"Decision","abstract":"This contribution describes the status in RAN WGs regarding interactions between RAN and MME for early data transmission, and which are the impacts to SA WG2 specifications.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11170,"status":"noted","reservation_date":"2018-05-21 23:22:28","uploaded":"2018-05-21 23:48:33","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_127BIS_Newport_Beach\/Docs\/S2-185152.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185153","title":"Introducing Early Data Transmission for Control Plane CIoT EPS optimization","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Include EDT as possible means for UE to transmit CP data to eNB in MO data case. - Include EDT session indication in Initial UE message for Control plane data transmission. - Include MME behaviour if EDT session was received from eNB:","secretary_remarks":"Revised in parallel session to S2-185713.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11180,"status":"revised","reservation_date":"2018-05-21 23:27:18","uploaded":"2018-05-21 23:48:33","revisionof":"","revisedto":"S2-185713","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"}],"crnumber":3436.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185153.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185194","title":"Correction on Secondary RAT data usage report","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correction on the description of S1 handover procedure.  Addition of the report procedure of Secondary RAT data usage report towards PGW.","secretary_remarks":"Revised in parallel session to S2-185699.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11710,"status":"revised","reservation_date":"2018-05-22 03:06:49","uploaded":"2018-05-22 14:36:27","revisionof":"","revisedto":"S2-185699","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"EDCE5"}],"crnumber":3437.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185194.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185203","title":"Support of PC5 transmission mechanism selection using Tx Profile","source":"Qualcomm Incorporated, LG Electronics","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the Tx Profile into the policy\/parameter provisioning, and clarify the PC5 transmission operation using the Tx Profile.  Editorial changes in clause 4.4.1.1.2, i.e. fix style to B1 for  1)  Authorization policy: 2)  Radio parameters for when the UE is 'not served by E-UTRAN':","secretary_remarks":"Revised in parallel session to S2-185693.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11840,"status":"revised","reservation_date":"2018-05-22 03:15:59","uploaded":"2018-05-22 12:52:49","revisionof":"","revisedto":"S2-185693","release":"Rel-15","crspec":23.285,"crspecversion":"15.0.0","workitem":[{"winame":"LTE_eV2X-Core"}],"crnumber":44.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185203.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185221","title":"[DRAFT] Reply LS on V2X configuration","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to SA WG6 on the incoming LS on V2X configuration.","secretary_remarks":"Response to S2-184710. Revised in parallel session to S2-185692.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11820,"status":"revised","reservation_date":"2018-05-22 04:13:05","uploaded":"2018-05-22 12:54:50","revisionof":"","revisedto":"S2-185692","release":"Rel-15","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_127BIS_Newport_Beach\/Docs\/S2-185221.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185286","title":"Updates to URLLC QCIs to align with SA1's updated requirements","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The requirement for 'Electricity Distribution - high voltage' is tightened by 1ms.  The references to the 'remote control' use case are removed.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11740,"status":"agreed","reservation_date":"2018-05-22 08:30:23","uploaded":"2018-05-22 13:50:44","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.203,"crspecversion":"15.2.0","workitem":[{"winame":"EPS_URLLC"}],"crnumber":1121.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180494","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185286.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185302","title":"Radio efficient handling of large UE radio capabilities at inter-RAT and SRVCC handover","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The MME monitors the size of the source to target transparent container at inter-RAT handover to E-UTRAN and, if it is smaller than the capabilities stored in the MME, adds the UE capabilities as a new parameter in the S1-AP Handover Request message.","secretary_remarks":"Revision of (Noted) S2-184060 from S2#127. Revised in parallel session to S2-185711","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11770,"status":"revised","reservation_date":"2018-05-22 08:46:01","uploaded":"2018-05-22 13:53:17","revisionof":"S2-184060","revisedto":"S2-185711","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"LTE_CA"},{"winame":"TEI15"}],"crnumber":3423.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185302.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185303","title":"[DRAFT] LS reply on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":68028,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA Packet IoTTF, NG\/Packet. Attachments: 23.401 CR xxxx","secretary_remarks":"Response to S2-184650. Revised to S2-186291.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11210,"status":"revised","reservation_date":"2018-05-22 08:54:13","uploaded":"2018-05-22 08:57:37","revisionof":"","revisedto":"S2-186291","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Packet IoTTF, NG\/Packet","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185303.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185325","title":"Relationship between Traffic Type and Release Assistance Information","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution elaborates on the relationship between Traffic Profile and Release Assistance Information and explains why the former needs to be added to the list of Communication Pattern Parameters.","secretary_remarks":"Not Handled","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11450,"status":"not treated","reservation_date":"2018-05-22 09:26:44","uploaded":"2018-05-22 14:34:40","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_127BIS_Newport_Beach\/Docs\/S2-185325.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185326","title":"Traffic Profile for for NB-IoT UE Uu operation optimisation","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The Traffic Profile is added to the Communication Pattern parameters.","secretary_remarks":"Not Handled","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11460,"status":"not treated","reservation_date":"2018-05-22 09:26:44","uploaded":"2018-05-22 14:34:40","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.4.0","workitem":[{"winame":"NB_IOTenh2-Core"}],"crnumber":402.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185326.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185327","title":"Applicability of Service Gap Control in idle and connected mode","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to remove the misleading sentence of clause 4.3.17.9 since the same concept is already and more appropriately conveyed by the other existing sentences. The following text is removed: 'Service Gap Control applies to idle mode, i.e. it requires the UE to stay in ECM-IDLE mode for at least the whole duration of the Service Gap timer before triggering Mobile Originated user data transmission.'","secretary_remarks":"Revised in parallel session to S2-185717.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11410,"status":"revised","reservation_date":"2018-05-22 09:26:46","uploaded":"2018-05-22 14:34:40","revisionof":"","revisedto":"S2-185717","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"}],"crnumber":3438.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185327.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185328","title":"Correction of APN Rate Control for PDN connection release and re-establishment","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The descriptions of APN Rate Control, attach, detach, PDN connectivity as well as of PDN disconnection procedures have been updated to describe that the network stores the APN Rate Control status at release of the last PDN connection of a given APN and it retrieves it at a subsequent establishment of a first PDN connection for a given APN.","secretary_remarks":"Revision of (Postponed) S2-183749 from S2#127. Revised in parallel session to S2-185718.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11470,"status":"revised","reservation_date":"2018-05-22 09:26:47","uploaded":"2018-05-22 14:34:40","revisionof":"S2-183749","revisedto":"S2-185718","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"},{"winame":"CIoT"}],"crnumber":3408.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185328.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185329","title":"Correction of APN Rate Control for PDN connection release and re-establishment","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The descriptions of the T6a\/T6b Connection Establishment, MME\/SGSN Initiated T6a\/T6b Connection Release and of the SCEF Initiated T6a\/T6b Connection Release procedures have been updated to describe that the network stores the APN Rate Control status at release of the last PDN connection of a given APN and that it retrieves it at a subsequent establishment of a first PDN connection for a given APN.","secretary_remarks":"Revision of (Postponed) S2-183750 from S2#127. Revised in parallel session to S2-185793.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11510,"status":"revised","reservation_date":"2018-05-22 09:26:48","uploaded":"2018-05-22 14:34:41","revisionof":"S2-183750","revisedto":"S2-185793","release":"Rel-15","crspec":23.682,"crspecversion":"15.4.0","workitem":[{"winame":"TEI15"},{"winame":"CIoT"}],"crnumber":386.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185329.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185433","title":"Discussion paper on UE differentiation in NB-IoT","source":"Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Orange","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"discussion","for":"Decision","abstract":"Discussion paper on the Local RRM Policy Specific UE differentiation information.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11350,"status":"noted","reservation_date":"2018-05-22 12:18:51","uploaded":"2018-05-22 12:36: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_127BIS_Newport_Beach\/Docs\/S2-185433.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185434","title":"[DRAFT] Reply on UE differentiation in NB-IoT","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to RAN WG2, RAN WG3","secretary_remarks":"Response to S2-184703. Noted","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11340,"status":"noted","reservation_date":"2018-05-22 12:21:56","uploaded":"2018-05-22 12:36:15","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185434.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185452","title":"Secondary RAT Usage Reporting with multiple PDN connection","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. When eNB is requested to send NR usage reports at E-RAB level from the MME, the eNB only includes NR usage reports if there is usage report data for that specific bearer, and only includes usage report of that specific bearer.  2. Clarify that MME shall provide secondary RAT usage reports on S11 messages only for those bearers that in the scope of the PDN connection of the S11 message.","secretary_remarks":"Revised in parallel session to S2-185700.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11680,"status":"revised","reservation_date":"2018-05-22 13:18:09","uploaded":"2018-05-22 14:31:01","revisionof":"","revisedto":"S2-185700","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"EDCE5"}],"crnumber":3441.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185452.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185480","title":"LS from SA WG3: Security solution for encryption of broadcast positioning information","source":"SA WG3","contact":"Anand Palanigounder","contact-id":26706,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks RAN WG2 for their Reply LS to SA WG3 on encryption of broadcast positioning information. Based on the response, SA WG3 concluded the following: - There is no strong motivation to develop a security solution that supports the usage of hierarchical keys for the encryption of broadcasted positioning data - Reuse OMA LPPe (LPP Extensions), as described in S3-173296, for the encryption of broadcasted positioning data with following changes on how to generate D0 to avoid keystream reuse: o The value for D0 shall be different for different broadcast messages to ensure that the counters derived from C1 for any message are different to the counters for any other message for a given ciphering key. o D0 shall contain at least 16 least significant bits (LSBs) set to zero to ensure that the values of D0 differ from another by a large value. The rationale for this is that a long SIB message (or a segmented SIB message) would require the use of consecutive counter values C1 to Cn, where","secretary_remarks":"Postponed","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11910,"status":"postponed","reservation_date":"2018-05-23 05:42:42","uploaded":"2018-05-23 05:43:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3, SA WG2","lsoriginalls":"S3-181926","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185480.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185488","title":"LS from SA WG3: Reply LS to LS on Security for NEF Northbound APIs","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks CT WG3 for the LS on Security for NEF Northbound APIs. SA WG3 discussed the CT WG3 LS and provides the following clarifications: 1. Which specification under the SA WG3 remit should be referenced for the security of the 5G NEF Northbound APIs? SA WG3 answer: TS 33.501 should be referenced for the security of the 5G NEF Northbound APIs. With the agreed SA WG3 CR (S3-181877), TS 33.501 details the security mechanism for NEF with and without CAPIF support. SA WG3 would like to point out that NEF with and without CAPIF support uses TLS. 2. In SA WG3, whether the CAPIF Work item relates to the NAPS and 5GS_Ph1 work items? SA WG3 answer: The CAPIF WI in SA WG3 has no overlap with the NAPS and 5GS_Ph1 WIs. CAPIF work item will consider to harmonize the security mechanism defined for the T8 and N33 with the security mechanism defined for CAPIF-2\/2e. If CAPIF is supported, the security communication between API invoker and the AEF supports the security mechanism specified for T8 a","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11550,"status":"noted","reservation_date":"2018-05-24 06:48:45","uploaded":"2018-05-24 06:49:30","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG2, SA WG6","lsoriginalls":"S3-182014","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185488.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185506","title":"LS from RAN WG3: Reply LS on Aspects of Handling Large UE Radio Capabilities in EPC","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to thank SA WG2 for the LS on aspects of handling large UE radio capabilities in EPC RAN WG3 has considered the mechanism indicated by SA WG2 and has discussed the issue. RAN WG3 has concluded that the source eNB shall ensure that the size of the Source to Target Transparent Container does not exceed the limits that can be handled by interfaces involved in the handover (see Endorsed CRs attached). Action: RAN WG3 kindly ask SA WG2 to take the above into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11760,"status":"noted","reservation_date":"2018-05-27 13:46:18","uploaded":"2018-05-27 13:57:54","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, CT WG4","lsoriginalls":"R3-183533","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185506.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185508","title":"LS from RAN WG3: Reply LS on EDT procedures and AS NAS interaction","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks RAN WG2 for the LS on EDT procedures and AS NAS interaction. RAN WG3 discussed on EDT procedures, and would like to provide feedback on the following questions: 1: Before step 7.1, it is not clear whether the eNB needs to be informed by the MME whether the MME prefers\/requires the UE to stay connected afterwards. RAN WG3 answer: RAN WG3 agreed to introduce a two-valued 'End indicator' information element from MME, to help the eNB to make decision immediately and then reduce delay and UE power consumption. 2: If it is confirmed that the MME needs to indicate preference\/requirement as in 1, then it is not clear whether MME needs to be aware that the UE is using EDT, e.g. to use this information to expedite response to eNB. RAN WG3 answer: RAN WG3 agreed to support MME awareness of Early Data Transmission, by including an 'EDT Session' flag in Initial UE Message procedure from eNB to the MME. Action: RAN WG3 respectfully requests RAN WG2, SA WG2 and CT WG1 to take the above","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11150,"status":"noted","reservation_date":"2018-05-27 13:46:18","uploaded":"2018-05-27 13:57:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2, CT WG1","Cc":"SA WG3","lsoriginalls":"R3-183574","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185508.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185511","title":"LS from RAN WG2: Reply LS on aspects of handling large UE radio capabilities in EPC","source":"RAN WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 for the LS in R2-1806657\/S2-184605. With regards to its actions, RAN WG2 can provide the following replies. SA WG2 request: SA WG2 respectfully asks RAN WG2 and CT WG4 to take the above agreed CRs into account and provide feedback if necessary. ANSWER: After a first review of the two agreed SA WG2 CRs, RAN WG2 has not identified any direct impact on RAN WG2 protocols. SA WG2 request: SA WG2 asks RAN WG2 and RAN WG3 whether they believe that the mechanism described in S2-184060 is needed in Release 15 and indicate whether other alternative solutions may be possible\/ preferred. ANSWER: RAN WG2 appreciate any solutions which allow network interfaces to be used to avoid the eNB having to use the RRC UE Capability Transfer procedure after every such handover. The mechanism described in S2-184060 is helpful. RAN WG2 has not discussed alternative solutions. Action: RAN WG2 respectfully asks SA WG2 take the above information into account and provide feedback if necessary.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11750,"status":"noted","reservation_date":"2018-05-28 14:33:57","uploaded":"2018-05-28 14:37:54","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG4, RAN WG3","Cc":"","lsoriginalls":"R2-1809159","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185511.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185513","title":"LS from RAN WG2: Reply LS on PC5 transmission mechanism selection","source":"RAN WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 for their LS in S2-183968\/ R2-1806646 on PC5 transmission mechanism selection. RAN WG2 discussed on the information in the LS: - For 'this may be decided and handled by RAN WG2, if the contents of 'Tx Profile' is decided to be transparent to V2X layer', RAN WG2 agreed the contents of TX profile are transparent to V2X layer of the UE. - For Rel-15 PC5 PHY format (i.e. PSSCH_TXFormat) and Tx profile, RAN WG2 decided 1. No need eNB configuration for PSSCH_TXFormat and upper layer will provide it (TX profile) 2. No need for eNB configuration of TX profile. Based on the following RAN WG1 decision on Rel-15 PC5 transmission mechanism, a) Support of rate matching and TBS scaling is mandatory b) Support of 64-QAM RX is mandatory and Support of 64-QAM TX is optional RAN WG2 agreed that at least the following TX profiles are supported: A. TX profile 1: UE shall use Rel-14 compatible format B. TX profile 2: UE shall use Rel-15 format which is not compatible with Rel-14. Acti","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11870,"status":"noted","reservation_date":"2018-05-28 14:33:57","uploaded":"2018-05-28 14:37:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG1","lsoriginalls":"R2-1809166","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185513.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185514","title":"LS from RAN WG2: Reply LS to RAN WG1 on RRC parameters for V2X Phase 2","source":"RAN WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 would like to thank RAN WG1 for the LS on RRC parameters for V2X Phase 2 (R1-1805620). In the LS, RAN WG1 indicated that it is up to RAN WG2 to decide how to deal with the following parameters: ? SL_V2X_Carriers_TX ? SL_V2X_Carriers_RX ? PSSCH_TXFormat RAN WG2 has discussed the necessity of these RRC parameters, and reached the following agreements: 1. SL_V2X_Carriers_TX, SL_V2X_Carriers_RX From RAN WG2 perspective, the v2x-InterFreqInfoList as specified in Rel-14 V2X can be reused to configure the Tx and Rx carriers for Rel-15 PC5 carrier aggregation. Hence, these two new parameters provided by RAN WG1 are not necessary. 2. PSSCH_TXFormat RAN WG2 determined at least the following Tx profile are supported as below: TX profile 1: UE shall use Rel-14 compatible format TX profile 2: UE shall use Rel-15 format which is not compatible with Rel-14 Such Tx profiles are provided to AS layer for each message from upper layer. From RAN WG2 point of view, based on the Tx profiles provided","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11880,"status":"noted","reservation_date":"2018-05-28 14:33:57","uploaded":"2018-05-28 14:37:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG1","Cc":"SA WG2","lsoriginalls":"R2-1809167","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185514.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185518","title":"LS from SA WG6: Reply LS on CAPIF4xMB","source":"SA WG6","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 would like to provide further response to LS S6-180605, which is seeking clarifications regarding update to xMB reference point in order to make it CAPIF compliant. As mentioned in our initial LS response in S6-180727, questions related to security impacts should be addressed by SA WG3. [SA WG4] SA WG4 assumes that part of the xMB interface is already CAPIF-1e (the Authorization\/Authentication) compliant, and the remaining part is already CAPIF-2 compliant. Does SA WG6 confirm this assumption? [SA WG6] The utilization of CAPIF framework and the service API interaction with CAPIF core function is described in Annex B.0 of TS 23.222. In order to be compliant with CAPIF-2, there are aspects such as authentication, authorization which are required to be supported, in addition to the service API themselves. The detailed definitions of both CAPIF-1\/1e and CAPIF-2\/2e are still being specified in CT WG3 and SA WG3, and whether xMB interface is CAPIF compliant or not should be assessed i","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11570,"status":"noted","reservation_date":"2018-05-28 14:45:45","uploaded":"2018-05-28 14:47:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"CT WG3, SA WG2, SA WG3","lsoriginalls":"S6-180944","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185518.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185692","title":"Reply LS on V2X configuration","source":"SA WG2","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6","secretary_remarks":"Revision of S2-185221. Agreed in parallel session.. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11830,"status":"approved","reservation_date":"2018-05-29 21:07:00","uploaded":"2018-06-02 18:17:53","revisionof":"S2-185221","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-184710","lsto":"SA WG6","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185692.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185693","title":"Support of PC5 transmission mechanism selection using Tx Profile","source":"Qualcomm Incorporated, LG Electronics","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the Tx Profile into the policy\/parameter provisioning, and clarify the PC5 transmission operation using the Tx Profile.  Editorial changes in clause 4.4.1.1.2, i.e. fix style to B1 for  1)  Authorization policy: 2)  Radio parameters for when the UE is 'not served by E-UTRAN':","secretary_remarks":"Revision of S2-185203. Revised in parallel session to S2-185771.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11850,"status":"revised","reservation_date":"2018-05-29 21:07:00","uploaded":"2018-06-02 18:17:53","revisionof":"S2-185203","revisedto":"S2-185771","release":"Rel-15","crspec":23.285,"crspecversion":"15.0.0","workitem":[{"winame":"LTE_eV2X-Core"}],"crnumber":44.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185693.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185696","title":"Indicating the Reachability Report Cause","source":"Convida Wireless LLC, BlackBerry UK Limited","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updated the reporting procedures (5.6.3.3 and 5.6.8.3) to say that the Monitoring Event Report indicates if the event was caused by the UE changing to connected mode or by the UE becoming reachable for paging.  Updated section 5.7.2 to explain that the SCS\/AS may send MT data when receiving a Monitoring Event Report indicating that the event was caused by the UE changing to connected mode.  Updated the UE Reachability Reporting procedure for roaming scenarios (5.6.8.3) to say that the event is also reported when and when the UE will become reachable for paging. Thus, making it consistent with the non-roaming scenario and general description.","secretary_remarks":"Revision of S2-184831. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11600,"status":"agreed","reservation_date":"2018-05-29 21:07:03","uploaded":"2018-06-02 18:17:53","revisionof":"S2-184831","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.4.0","workitem":[{"winame":"NAPS"}],"crnumber":399.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185696.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185697","title":"Fixing Group NIDD","source":"Ericsson, Convida Wireless LLC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Allow the SCS\/AS to configure NIDD for a UE group.  Introduce authorization of a External Group ID in HSS at NIDD configuration.  Minimize HSS signalling in clause 5.5.3 at Group Message Delivery via unicast MT NIDD by using a list stored in SCEF instead of doing an additional HSS query.","secretary_remarks":"Revision of S2-184859. Revised in parallel session to S2-185768.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11620,"status":"revised","reservation_date":"2018-05-29 21:07:04","uploaded":"2018-06-02 18:17:53","revisionof":"S2-184859","revisedto":"S2-185768","release":"Rel-15","crspec":23.682,"crspecversion":"15.4.0","workitem":[{"winame":"NAPS"}],"crnumber":393.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185697.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185698","title":"TLTRI and TTRI Usage","source":"Convida Wireless LLC, Huawei, Nokia, Nokia Shanghai Bell, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Summary of changes in SA WG2#127BIS:  The Group NIDD Delivery (5.5.3) needs TLTRI sent from the SCS\/AS.  Summary of Change 1:  Updated the definition of TLTRI so that it is assigned by the SCEF and updated all T8 procedures accordingly.  Summary of Change 2 (in the MT NIDD Procedure of 5.13.3):  Added a parameter called 'non-IP data sequence number' to the MT NIDD procedures. This value is assigned by the SCEF and can be used by the SCS\/AS to override previously buffered data instead of TTRI. Thus, the TTRI parameter functionality is no longer overloaded.  Summary of Change 3 (in the MT NIDD Procedure of 5.13.3):  Added the buffer indication to step 5.  Summary of Change 4:  TTRI is removed from all procedures since it is not used in stage 3 and not needed due to the constraints of HTTP. Also, its presence in stage 2 is misleading in the sense that it leads the reader to believe that responses can be received out of order. Also, added a note in section 4.9.2 clarifyi","secretary_remarks":"Revision of S2-184860. Revised in parallel session to S2-185769.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11650,"status":"revised","reservation_date":"2018-05-29 21:07:05","uploaded":"2018-06-02 18:17:53","revisionof":"S2-184860","revisedto":"S2-185769","release":"Rel-15","crspec":23.682,"crspecversion":"15.4.0","workitem":[{"winame":"NAPS"}],"crnumber":392.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185698.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185699","title":"Correction on Secondary RAT data usage report","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correction on the description of S1 handover procedure.  Addition of the report procedure of Secondary RAT data usage report towards PGW.","secretary_remarks":"Revision of S2-185194. Withdrawn","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11720,"status":"withdrawn","reservation_date":"2018-05-29 21:07:06","uploaded":null,"revisionof":"S2-185194","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"EDCE5"}],"crnumber":3437.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185700","title":"Secondary RAT Usage Reporting with multiple PDN connection","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. When eNB is requested to send NR usage reports at E-RAB level from the MME, the eNB only includes NR usage reports if there is usage report data for that specific bearer, and only includes usage report of that specific bearer.  2. Clarify that MME shall provide secondary RAT usage reports on S11 messages only for those bearers that in the scope of the PDN connection of the S11 message.","secretary_remarks":"Revision of S2-185452. Revised in parallel session to S2-185804.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11690,"status":"revised","reservation_date":"2018-05-29 21:07:07","uploaded":"2018-06-02 18:17:53","revisionof":"S2-185452","revisedto":"S2-185804","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"EDCE5"}],"crnumber":3441.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185700.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185711","title":"Radio efficient handling of large UE radio capabilities at inter-RAT and SRVCC handover","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: The MME monitors the size of the source to target transparent container at inter-RAT handover to E-UTRAN and, if it is smaller than the capabilities stored in the MME, adds the UE capabilities as a new parameter in the S1-AP Handover Request message.","secretary_remarks":"Revision of S2-185302. Revised in parallel session to S2-185770.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11780,"status":"revised","reservation_date":"2018-05-29 21:07:08","uploaded":"2018-06-02 18:17:53","revisionof":"S2-185302","revisedto":"S2-185770","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"LTE_CA"}],"crnumber":3423.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185711.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185712","title":"Handling of large UE radio capabilities at inter-RAT and SR-VCC handover","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: At inter-RAT handover, the source eNB is made responsible for ensuring that the size limits of legacy interfaces are respected.","secretary_remarks":"Created in parallel session. Rel-15 mirror of CR agreed in S2-183974 at S2#127. Withdrawn","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11800,"status":"withdrawn","reservation_date":"2018-05-29 21:07:09","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"LTE_CA"}],"crnumber":3442.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185713","title":"Introducing Early Data Transmission for Control Plane CIoT EPS optimization","source":"Qualcomm Incorporated, Huawei, HiSilicon","contact":"Miguel Griot","contact-id":57486,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Include EDT as possible means for UE to transmit CP data to eNB in MO data case. - Include EDT session indication in Initial UE message for Control plane data transmission. - Include MME behaviour if EDT session was received from eNB:","secretary_remarks":"Revision of S2-185153. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11190,"status":"agreed","reservation_date":"2018-05-29 21:07:13","uploaded":"2018-06-02 18:17:53","revisionof":"S2-185153","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"}],"crnumber":3436.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-180496","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185713.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185714","title":"Identification of LTE-M (eMTC) traffic","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Verizon UK Ltd","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - When eNB receives the UE radio capability, the eNB extracts the cat-M1\/M2 information. If UE is cat-M1\/M2, the eNB provides the Cat-M1\/M2 information separately in a different IE to MME - The MME stores this information, until UE detaches. - The MME provides the Cat-M1\/M2 information to S-GW\/P-GW as a new RAT type - In case of MME change, the source MME provides the cat-M1\/M2 information to the target MME over S10.","secretary_remarks":"Revision of S2-185061. Revised in parallel session to S2-185784.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11290,"status":"revised","reservation_date":"2018-05-29 21:07:14","uploaded":"2018-06-02 18:17:53","revisionof":"S2-185061","revisedto":"S2-185784","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"}],"crnumber":3404.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185714.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185715","title":"Introduction of local RRM policy specific UE differentiation","source":"Ericsson, Vodafone, AT&T","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The new Local RRM UE Differentiation Information is defined and added to the procedures that are using following messages: 1) S1AP: UE INFORMATION TRANSFER (for CP solution) 2) S1AP: CONNECTION ESTABLISHMENT INDICATION (for CP solution) 3) S1AP: DOWNLINK NAS TRANSPORT(for CP solution and UP solution) 4) S1AP: INITIAL CONTEXT SETUP REQUEST (for UP solution) 5) S1AP: PATH SWITCH REQUEST ACKNOWLEDGE (for UP solution) 6) S1AP: HANDOVER REQUEST (for UP solution) 7) S1AP: UE CONTEXT RELEASE COMPLETE (for CP and UP solution) 8) S1AP: HANDOVER REQUIRED (for UP solution) Further, the new information shall be stored in the MME and forwarded at idle mode mobility between MMEs.","secretary_remarks":"Revision of S2-184839. Revised in parallel session to S2-185765.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11370,"status":"revised","reservation_date":"2018-05-29 21:07:15","uploaded":"2018-06-02 18:17:53","revisionof":"S2-184839","revisedto":"S2-185765","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"NB_IOTenh2-Core"}],"crnumber":3431.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185715.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185716","title":"Subscription for Aerial UE in 3GPP system","source":"Ericsson, NTT DoCoMo, Qualcomm Incorporated, Intel","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce a new subscription parameter in HSS which is transferred to MME during Attach, TAU and Change in Subscription information and MME provides the information to eNB when UE context is established. Version 3: remove service request as it is wrongly included in the following text: Support of Aerial UE function is stored in the user's subscription information in HSS. HSS transfers this information to the MME via Update Location message during Attach, Service Request and Tracking Area Update procedures.","secretary_remarks":"Revision of S2-184907. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11400,"status":"agreed","reservation_date":"2018-05-29 21:07:16","uploaded":"2018-06-02 18:17:53","revisionof":"S2-184907","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"LTE_Aerial"}],"crnumber":3411.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"SP-180497","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185716.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185717","title":"Applicability of Service Gap Control in idle and connected mode","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to remove the misleading sentence of clause 4.3.17.9 since the same concept is already and more appropriately conveyed by the other existing sentences. The following text is removed: 'Service Gap Control applies to idle mode, i.e. it requires the UE to stay in ECM-IDLE mode for at least the whole duration of the Service Gap timer before triggering Mobile Originated user data transmission.'","secretary_remarks":"Revision of S2-185327. Revised in parallel session to S2-185766.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11420,"status":"revised","reservation_date":"2018-05-29 21:07:17","uploaded":"2018-06-02 18:17:54","revisionof":"S2-185327","revisedto":"S2-185766","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"}],"crnumber":3438.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185717.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185718","title":"Correction of APN Rate Control for PDN connection release and re-establishment","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The descriptions of APN Rate Control, attach, detach, PDN connectivity as well as of PDN disconnection procedures have been updated to describe that the network stores the APN Rate Control status at release of the last PDN connection of a given APN and it retrieves it at a subsequent establishment of a first PDN connection for a given APN.","secretary_remarks":"Revision of S2-185328. Revised in parallel session to S2-185767.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11480,"status":"revised","reservation_date":"2018-05-29 21:07:18","uploaded":"2018-06-02 18:17:54","revisionof":"S2-185328","revisedto":"S2-185767","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"},{"winame":"CIoT"}],"crnumber":3408.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185718.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185765","title":"Introduction of local RRM policy specific UE differentiation","source":"Ericsson, Vodafone","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The new Local RRM UE Differentiation Information is defined and added to the procedures that are using following messages: 1) S1AP: UE INFORMATION TRANSFER (for CP solution) 2) S1AP: CONNECTION ESTABLISHMENT INDICATION (for CP solution) 3) S1AP: DOWNLINK NAS TRANSPORT(for CP solution and UP solution) 4) S1AP: INITIAL CONTEXT SETUP REQUEST (for UP solution) 5) S1AP: PATH SWITCH REQUEST ACKNOWLEDGE (for UP solution) 6) S1AP: HANDOVER REQUEST (for UP solution) 7) S1AP: UE CONTEXT RELEASE COMPLETE (for CP and UP solution) 8) S1AP: HANDOVER REQUIRED (for UP solution) Further, the new information shall be stored in the MME and forwarded at idle mode mobility between MMEs.","secretary_remarks":"Revision of S2-185715. Noted","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11380,"status":"noted","reservation_date":"2018-05-31 14:30:59","uploaded":"2018-06-02 18:17:54","revisionof":"S2-185715","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"NB_IOTenh2-Core"}],"crnumber":3431.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185765.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185766","title":"Applicability of Service Gap Control in idle and connected mode","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to remove the misleading sentence of clause 4.3.17.9 since the same concept is already and more appropriately conveyed by the other existing sentences. The following text is removed: 'Service Gap Control applies to idle mode, i.e. it requires the UE to stay in ECM-IDLE mode for at least the whole duration of the Service Gap timer before triggering Mobile Originated user data transmission.'","secretary_remarks":"Revision of S2-185717. Revised in parallel session to S2-185801.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11430,"status":"revised","reservation_date":"2018-05-31 14:31:00","uploaded":"2018-06-02 18:17:54","revisionof":"S2-185717","revisedto":"S2-185801","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"}],"crnumber":3438.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185766.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185767","title":"Correction of APN Rate Control for PDN connection release and re-establishment","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The descriptions of APN Rate Control, attach, detach, PDN connectivity as well as of PDN disconnection procedures have been updated to describe that the network stores the APN Rate Control status at release of the last PDN connection of a given APN and it retrieves it at a subsequent establishment of a first PDN connection for a given APN.","secretary_remarks":"Revision of S2-185718. Revised in parallel session to S2-185802.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11490,"status":"revised","reservation_date":"2018-05-31 14:31:01","uploaded":"2018-06-02 18:17:54","revisionof":"S2-185718","revisedto":"S2-185802","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"},{"winame":"CIoT"}],"crnumber":3408.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185767.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185768","title":"Fixing Group NIDD","source":"Ericsson, Convida Wireless LLC, Nokia","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Allow the SCS\/AS to configure NIDD for a UE group.  Introduce authorization of a External Group ID in HSS at NIDD configuration.  Minimize HSS signalling in clause 5.5.3 at Group Message Delivery via unicast MT NIDD by using a list stored in SCEF instead of doing an additional HSS query.","secretary_remarks":"Revision of S2-185697. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11630,"status":"agreed","reservation_date":"2018-05-31 14:31:03","uploaded":"2018-06-02 18:17:54","revisionof":"S2-185697","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.4.0","workitem":[{"winame":"NAPS"}],"crnumber":393.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-180493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185768.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185769","title":"TLTRI and TTRI Usage","source":"Convida Wireless LLC, Huawei, Nokia, Nokia Shanghai Bell, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Summary of changes in SA WG2#127BIS:  The Group NIDD Delivery (5.5.3) needs TLTRI sent from the SCS\/AS.  Summary of Change 1:  Updated the definition of TLTRI so that it is assigned by the SCEF and updated all T8 procedures accordingly.  Summary of Change 2 (in the MT NIDD Procedure of 5.13.3):  Added a parameter called 'non-IP data sequence number' to the MT NIDD procedures. This value is assigned by the SCEF and can be used by the SCS\/AS to override previously buffered data instead of TTRI. Thus, the TTRI parameter functionality is no longer overloaded.  Summary of Change 3 (in the MT NIDD Procedure of 5.13.3):  Added the buffer indication to step 5.  Summary of Change 4:  TTRI is removed from all procedures since it is not used in stage 3 and not needed due to the constraints of HTTP. Also, its presence in stage 2 is misleading in the sense that it leads the reader to believe that responses can be received out of order. Also, added a note in section 4.9.2 clarifyi","secretary_remarks":"Revision of S2-185698. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11660,"status":"agreed","reservation_date":"2018-05-31 14:31:04","uploaded":"2018-06-02 18:17:54","revisionof":"S2-185698","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.4.0","workitem":[{"winame":"NAPS"}],"crnumber":392.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-180493","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185769.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185770","title":"Radio efficient handling of large UE radio capabilities at inter-RAT and SRVCC handover","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Rel-15 mirror CR: Summary of change: The MME monitors the size of the source to target transparent container at inter-RAT handover to E-UTRAN and, if it is smaller than the capabilities stored in the MME, adds the UE capabilities as a new parameter in the S1-AP Handover Request message.","secretary_remarks":"Revision of S2-185711. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11790,"status":"agreed","reservation_date":"2018-05-31 14:31:05","uploaded":"2018-06-02 18:17:54","revisionof":"S2-185711","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"LTE_CA"},{"winame":"TEI15"}],"crnumber":3423.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-180471","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185770.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185771","title":"Support of PC5 transmission mechanism selection using Tx Profile","source":"Qualcomm Incorporated, LG Electronics","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the Tx Profile into the policy\/parameter provisioning, and clarify the PC5 transmission operation using the Tx Profile.  Editorial changes in clause 4.4.1.1.2, i.e. fix style to B1 for  1)  Authorization policy: 2)  Radio parameters for when the UE is 'not served by E-UTRAN':","secretary_remarks":"Revision of S2-185693. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11860,"status":"agreed","reservation_date":"2018-05-31 14:31:06","uploaded":"2018-06-02 18:17:54","revisionof":"S2-185693","revisedto":"","release":"Rel-15","crspec":23.285,"crspecversion":"15.0.0","workitem":[{"winame":"LTE_eV2X-Core"}],"crnumber":44.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180473","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185771.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185784","title":"Identification of LTE-M (eMTC) traffic","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Convida Wireless, NTT Docomo, Orange, Telstra","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - When eNB receives the UE radio capability, the eNB extracts the cat-M1\/M2 information. If UE is cat-M1\/M2, the eNB provides the Cat-M1\/M2 information separately in a different IE to MME - The MME stores this information, until UE detaches. - The MME provides the Cat-M1\/M2 information to S-GW\/P-GW as a new RAT type - In case of MME change, the source MME provides the cat-M1\/M2 information to the target MME over S10.","secretary_remarks":"Revision of S2-185714. This CR was agreed","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11300,"status":"agreed","reservation_date":"2018-06-02 16:17:14","uploaded":"2018-06-02 18:17:55","revisionof":"S2-185714","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"}],"crnumber":3404.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"SP-180496","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185784.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185793","title":"Correction of APN Rate Control for PDN connection release and re-establishment","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The descriptions of the T6a\/T6b Connection Establishment, MME\/SGSN Initiated T6a\/T6b Connection Release and of the SCEF Initiated T6a\/T6b Connection Release procedures have been updated to describe that the network stores the APN Rate Control status at release of the last PDN connection of a given APN and that it retrieves it at a subsequent establishment of a first PDN connection for a given APN.","secretary_remarks":"Revision of S2-185329. Revised in parallel session to S2-185803.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11520,"status":"revised","reservation_date":"2018-06-02 16:17:16","uploaded":"2018-06-02 18:17:55","revisionof":"S2-185329","revisedto":"S2-185803","release":"Rel-15","crspec":23.682,"crspecversion":"15.4.0","workitem":[{"winame":"TEI15"},{"winame":"CIoT"}],"crnumber":386.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185793.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185801","title":"Applicability of Service Gap Control in idle and connected mode","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to remove the misleading sentence of clause 4.3.17.9 since the same concept is already and more appropriately conveyed by the other existing sentences. The following text is removed: 'Service Gap Control applies to idle mode, i.e. it requires the UE to stay in ECM-IDLE mode for at least the whole duration of the Service Gap timer before triggering Mobile Originated user data transmission.'","secretary_remarks":"Revision of S2-185766. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11440,"status":"agreed","reservation_date":"2018-06-02 16:17:17","uploaded":"2018-06-02 18:17:55","revisionof":"S2-185766","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"}],"crnumber":3438.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-180496","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185801.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185802","title":"Correction of APN Rate Control for PDN connection release and re-establishment","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The descriptions of APN Rate Control, attach, detach, PDN connectivity as well as of PDN disconnection procedures have been updated to describe that the network stores the APN Rate Control status at release of the last PDN connection of a given APN and it retrieves it at a subsequent establishment of a first PDN connection for a given APN.","secretary_remarks":"Revision of S2-185767. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11500,"status":"agreed","reservation_date":"2018-06-02 16:17:17","uploaded":"2018-06-02 18:17:55","revisionof":"S2-185767","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"},{"winame":"CIoT"}],"crnumber":3408.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-180496","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185802.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185803","title":"Correction of APN Rate Control for PDN connection release and re-establishment","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The descriptions of the T6a\/T6b Connection Establishment, MME\/SGSN Initiated T6a\/T6b Connection Release and of the SCEF Initiated T6a\/T6b Connection Release procedures have been updated to describe that the network stores the APN Rate Control status at release of the last PDN connection of a given APN and that it retrieves it at a subsequent establishment of a first PDN connection for a given APN.","secretary_remarks":"Revision of S2-185793. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11530,"status":"agreed","reservation_date":"2018-06-02 16:17:18","uploaded":"2018-06-02 18:17:55","revisionof":"S2-185793","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.4.0","workitem":[{"winame":"TEI15"},{"winame":"CIoT"}],"crnumber":386.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-180496","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185803.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185804","title":"Secondary RAT Usage Reporting with multiple PDN connection","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. When eNB is requested to send NR usage reports at E-RAB level from the MME, the eNB only includes NR usage reports if there is usage report data for that specific bearer, and only includes usage report of that specific bearer.  2. Clarify that MME shall provide secondary RAT usage reports on S11 messages only for those bearers that in the scope of the PDN connection of the S11 message.","secretary_remarks":"Revision of S2-185700. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11700,"status":"agreed","reservation_date":"2018-06-02 16:17:19","uploaded":"2018-06-02 18:17:55","revisionof":"S2-185700","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.3.0","workitem":[{"winame":"EDCE5"}],"crnumber":3441.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180492","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185804.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186291","title":"LS reply on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"SA WG2","contact":"Alessio Casati","contact-id":68028,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA Packet IoTTF, NG\/Packet, GSMA WAS_WSOLU. Attachment: 23.401 CR3404","secretary_remarks":"Revision of S2-185303. Approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11220,"status":"approved","reservation_date":"2018-06-02 16:33:29","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185303","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-184650","lsto":"GSMA Packet IoTTF, NG\/Packet, GSMA WAS_WSOLU","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186291.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]