[{"name":"S2-181428","title":"LS from SA WG6: LS on Integration of northbound APIs with CAPIF","source":"SA WG6","contact":"Niranth Amogh","contact-id":39608,"tdoctype":"LS in","for":"Action","abstract":"As part of the CAPIF WID for Release 15, SA WG6 has specified the Common API Framework for 3GPP northbound APIs in TS 23.222. The primary objective of CAPIF is to specify a common northbound API framework to enable consistent development of northbound APIs across 3GPP, in particular towards the common aspects (e.g. onboarding, discover, publish, authentication, API management, etc.) that apply to any northbound API definition. TS 23.222 contains detailed specification of the common aspects of the API framework and the interactions with the CAPIF core function from both the API invoker and the API exposing function. TS 23.222 also includes an informative annex 'CAPIF relationship with network exposure aspects of 3GPP systems' that shows CAPIF relationship with SCEF\/NEF, and possible integration models.Your review of this annex, and any feedback would help us in identifying any missing aspects to achieve better alignment in integration of CAPIF with the specification(s) of northbound API","secretary_remarks":"Postponed S2-180051 from S2#125. 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":11170,"status":"postponed","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-01 17:35:41","revisionof":"S2-180051","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG SA, TSG CT, SA WG4, CT WG3","lsoriginalls":"S6-171851","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181428.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181432","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-181137 from S2#125. Responses drafted in S2-181860 and S2-181866. 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":11010,"status":"postponed","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-01 17:35:41","revisionof":"S2-181137","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5","Cc":"-","lsoriginalls":"IOTTF17 Doc003","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181432.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181433","title":"LS from CT WG1: LS on service gap control with resume for non-supporting UE","source":"CT WG1","contact":"Kaj Johansson","contact-id":73246,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has discussed the Service Gap Control feature for non-supporting UEs (e.g pre-15 release UEs) and the Resume connection handling captured in TS 23.401, sub clause 5.3.5A, step 3: - If there is a Service Gap timer running in the MME for the UE and the MME is not waiting for a MT paging response from the UE and the RRC Connection Establishment Cause for the Connection Resume Request is not 'mo-Signalling', the MME sends a Service Reject NAS message to the UE with a Mobility Management back-off timer corresponding to the remaining time of the current Service Gap timer and rejects the Context Resume Request with an appropriate cause indicating continued suspension. CT WG1 understanding of the above behaviour is an optimized solution instead of the use of two UE initiated procedures, i.e. 1) 'resume request' with 'resume reject' followed by 2) e.g. 'service request' with 'service reject' to provide the mobility management back off timer to the UE. This is the legacy functionality. In","secretary_remarks":"Postponed 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":10990,"status":"postponed","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-02 14:51:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"C1-180389","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181433.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181434","title":"LS from CT WG1: Reply LS on EDT procedures and AS NAS interaction","source":"CT WG1","contact":"Osama Lotfallah","contact-id":71227,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA WG2 for their reply LS on EDT procedures and AS NAS interaction from SA WG2. CT WG1 discussed the following question from SA WG2. SA WG2's question: SA WG2 would like to ask CT WG1 whether NAS Control Plane service request procedure has to be completed (with Service Accept or other DL NAS PDU) or the UE shall also treat the indication from the lower layers that the RRC connection has been released as successful completion of the procedure CT WG1's response: For the case of initiating a service request procedure for pending user data in IDLE state, the UE shall treat an indication of RRC connection release from the lower layers as successful completion of the service request procedure, see the following text in subclause 5.6.1.4.2 and Figure 5.6.1.1.2 of TS 24.301: For case b in subclause 5.6.1.1, the UE shall also treat the indication from the lower layers that the RRC connection has been released as successful completion of the procedure. The UE shall reset the servic","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":11000,"status":"noted","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-02 14:51:41","revisionof":"S2-180023","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, RAN WG3","lsoriginalls":"C1-180638","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181434.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181441","title":"LS from CT WG3: LS on Usage of Monitoring Duration","source":"CT WG3","contact":"Yali Yan","contact-id":66362,"tdoctype":"LS in","for":"Action","abstract":"In TS 23.682, subclause 5.6.0, it states: Monitoring Duration is an optional parameter that indicates the absolute time at which the related monitoring event request is considered to expire. For Monitoring Requests for a group, this parameter applies to every group member UE. It also indicates that when the Monitoring Duration is reached, the HSS shall send the aggregated event reports to the SCEF and the destination if the subscription is for group of UEs. However, there are still missing procedures. When specifying the stage 3 SCEF Northbound API for monitoring event procedure, CT WG3 discussed following options when the monitoring duration is reached: - Option 1: the HSS shall inform the MME\/SGSN to delete the monitoring event and initiate the network-imitated Monitoring event deletion procedure and also send the aggregated event reports to the SCEF and the destination 3rd party; Or - Option 2: the SCS\/AS shall send the HTTP DELETE request to delete the existing monitoring event sub","secretary_remarks":"Response drafted in S2-181969. Final response in S2-182397","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":10800,"status":"replied to","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-02 14:51:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-180286","lsreply":"S2-182397, S2-182397","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181441.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181442","title":"LS from CT WG3: LS on Requirement of Group Message Delivery via MBMS","source":"CT WG3","contact":"Yali Yan","contact-id":66362,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is specifying the T8 API for Group Message Delivery via MBMS procedures, according to stage 2 requirement in subclause 5.5.1 of TS 23.682. Those requirements seem to suggest the need for a new northbound API at the SCEF; on the southbound side the SCEF either uses the xMB interfaces as specified in TS 29.116 based on detailed requirements of SA WG4 in 3GPP TS 26.346, or the MB2 interface. However, the capabilities of the xMB interface and the MB2 interface differ, and the stage 2 seems to expose related differences also to the SCS\/AS. Even the first message to be send by the SCS\/AS differs depending on the used southbound interface. Furthermore, not all the detailed SA WG4 requirements are reflected in subclause 5.5.1. Some companies suggested to reuse the xMB API defined in 3GPP TS 29.116 as group messaging delivery API exposed by the SCEF for the scenario where the SCEF uses a xMB interface at the southbound side and to only define a new API that exposes capabilities equivalen","secretary_remarks":"Responses drafted in S2-181864 and S2-181971. Final response in S2-182398","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":10860,"status":"replied to","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-02 14:51:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG4","lsoriginalls":"C3-180292","lsreply":"S2-182398, S2-182398","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181442.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181443","title":"LS from CT WG3: LS on usage of CAPIF for xMB APIs","source":"CT WG3","contact":"Nishant Gupta","contact-id":62473,"tdoctype":"LS in","for":"Information","abstract":"CT WG3 agreed to a new WID proposal on stage-3 aspects of Common API Framework for 3GPP northbound APIs (CAPIF), following the approval of stage-2 CAPIF TS 23.222 by SA#78. The WID has identified possible impacts to 'Northbound APIs for SCEF - SCS\/AS Interworking' as described in TS 29.122, '5G NF Services provided by NEF external exposure' and xMB APIs as described in TS 29.116, due to usage of CAPIF . In this regard, CT WG3 kindly asks SA WG4 if there are any plans to use CAPIF for xMB APIs and request to provide feedback on the potential impacts to the current xMB stage-2 specification due to the use of CAPIF.","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":11180,"status":"noted","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-02 14:51:41","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG6, SA WG2","lsoriginalls":"C3-180353","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181443.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181444","title":"LS from CT WG3: LS on Resource Identifiers for T8","source":"CT WG3","contact":"Thomas Belling","contact-id":23293,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is specifying APIs for the T8 interface in TS 29.122 based on stage 2 requirements in TS 23.682. CT WG3 observed that for the different T8 APIs defined in CT WG3 the main resources correspond to long term transaction identifiers ('TLTRI') defined in stage2. However, CT WG3 decided that the TLTRI is not suitable as resource identifier as stage 2 requires that the TLTRI is assigned by the SCS\/AS, i.e. the client. However, it is preferable that the server (i.e. SCEF) assigns resource identifiers as this may impact its internal handling and its ability for resource distribution. CT WG3 thus decided to use independent server-assigned resource identifiers that are communicated to the client and used by the client in subsequent communication. To satisfy stage 2 requirements, the TLTRI can also be used as an independent client-assigned correlating identifier. However, this identifier could be regarded as redundant. One way to avoid such redundancies could be that SA WG2 decides that the","secretary_remarks":"Postponed 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":10920,"status":"postponed","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-02 14:51:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"C3-180358","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181444.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181445","title":"LS from CT WG3: LS on T8 Destination Address","source":"CT WG3","contact":"Uwe Rauschenbach","contact-id":68433,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is specifying APIs for the T8 interface in TS 29.122 based on stage 2 requirements in TS 23.682. In the pattern to subscribe to notifications via HTTP (also known as Webhooks), CT WG3 is using a scheme where the SCS\/AS provides to the SCEF a URI (corresponding to the T8 Destination Address in TS 23.682) on which the SCS\/AS is willing to accept notifications via HTTP POST. TS 23.682 clause 4.9.2 states that the T8 Destination Address is optional, and clause 5.6.3.1 states that in case it is missing, the address of the SCS\/AS is assumed as the default T8 Destination Address. This is different from the 5G service interfaces, where providing the corresponding notification address is mandatory, according to TS 23.501. In the protocol design, CT WG3 suggests to always require that the SCS\/AS provides explicitly the T8 Destination Address, to simplify the protocol as described in the design pattern of the 5G service interfaces. CT WG3 would thus like to ask SA WG2 whether it would be a","secretary_remarks":"Postponed 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":10930,"status":"postponed","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-02 14:51:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"C3-180372","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181445.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181491","title":"LS from SA WG6: LS on signalling plane registration for the MC service UE for migration scenario","source":"SA WG6","contact":"Niranth Amogh","contact-id":39608,"tdoctype":"LS in","for":"Action","abstract":"SA WG6 has specified the migration management server (see subclause 7.4.2.2.11 of TS 23.280), in the functional architecture to support MC services UE migration. Further, during SA WG6#21, SA WG6 has agreed on a procedure describing the signalling plane registration for the MC service UE to support the migration scenario (see attached CR). Action: SA WG6 asks SA WG2 to take note of the above 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":11280,"status":"noted","reservation_date":"2018-02-05 14:17:42","uploaded":"2018-02-05 15:20:40","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"S6-180223","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181491.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181840","title":"LS from SA WG4: Reply LS on FEC and ROHC for mission critical services over MBMS","source":"SA WG4","contact":"Cedric Thienot","contact-id":56306,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 would like to thank SA WG2 for its LS regarding the 'Reply LS on FEC and ROHC for mission critical services over MBMS'. SA WG4 agreed to a new WID proposal named 'FEC and ROHC Activation for GCSE over MBMS' in order to support your CR documents S2-179600, S2-179073.","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":11290,"status":"noted","reservation_date":"2018-02-19 09:33:19","uploaded":"2018-02-19 10:37:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3, SA WG6, RAN WG2, RAN WG3","lsoriginalls":"S4-180275","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181840.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181842","title":"LS from SA WG4: Reply LS on usage of CAPIF for xMB APIs","source":"SA WG4","contact":"Jean-marc Guyot","contact-id":61447,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 would like to thank CT WG3 for its LS regarding the 'usage of CAPIF for xMB APIs'. SA WG4 agreed to a new WID proposal on stage-2 aspects of xMB, that is attached to this LS. SA WG4 foresees possible impacts to the current xMB specification as described in TS 26.346 and implemented in TS 29.116. SA WG4 plan to upgrade xMB API so that it becomes CAPIF compliant. SA WG4 kindly asks CT WG3 to take this information into consideration for future version of xMB API.","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":11190,"status":"noted","reservation_date":"2018-02-19 09:33:19","uploaded":"2018-02-19 10:37:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG2, SA WG6","lsoriginalls":"S4-180315","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181842.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181858","title":"Introduction ot LTE-M RAT-type and Identification of LTE-M UE and traffic in the EPC","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: As per GSMA request this CR provides a solution to this by adding a new LTE-M RAT Type, without requiring the RAN to collect data on when CE mode A\/B is used but just relying on the UE capabilities signalled by the UE to the RAN. The RAN then conveys the information the UE RAN capabilities include LTE Cat-M1\/2 to the the information to the CN.","secretary_remarks":"Merged into S2-182362.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11020,"status":"merged","reservation_date":"2018-02-19 12:30:19","uploaded":"2018-02-19 16:14:24","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"CIoT"},{"winame":"TEI15"}],"crnumber":3402.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181858.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181860","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. CC: RAN WG3, RAN WG2, CT WG4. Attachments: 23.401 CR xxxx","secretary_remarks":"Response to S2-181432. 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":11120,"status":"not treated","reservation_date":"2018-02-19 12:38:13","uploaded":"2018-02-19 16:14:24","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA Packet IoTTF, NG\/Packet","Cc":"RAN WG3, RAN WG2, CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181860.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181862","title":"Alignment with stage-3 reporting and access restriction for unlicensed spectrum","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligns with stage-3 decisions of CT WG4 to define only one value for unlicensed spectrum data volume reporting and access restriction and not differentiate between LAA, LWA\/LWIP.","secretary_remarks":"Revised in parallel session to S2-182367.","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":"revised","reservation_date":"2018-02-19 12:53:25","uploaded":"2018-02-20 13:34:04","revisionof":"","revisedto":"S2-182367","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"USOS"}],"crnumber":3403.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181862.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181863","title":"Addition of Broadcast of Assistance Data for E-UTRAN","source":"Qualcomm Incorporated, Ericsson","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds a new procedure for transferring assistance data from an E-SMLC to an eNodeB for broadcast to target UEs. This procedure is based on current agreements in RAN but may need to be updated later after the RAN solution is finalized. Another procedure is added to enable delivery of ciphering keys to UEs by an E-SMLC via an MME using mobility management Attach and TAU procedures. Definition of new subscription data for ciphering keys is added for an HLR\/HSS. MME and E-SMLC functional description is updated.","secretary_remarks":"Revised in parallel session to S2-182368.","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":"revised","reservation_date":"2018-02-19 12:53:26","uploaded":"2018-02-20 13:34:04","revisionof":"","revisedto":"S2-182368","release":"Rel-15","crspec":23.271,"crspecversion":"14.3.0","workitem":[{"winame":"TEI15"}],"crnumber":432.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181863.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181864","title":"[DRAFT] Reply LS on Requirement of Group Message Delivery via MBMS","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"Provides response to C3-180292","secretary_remarks":"Response to S2-181442. 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":10880,"status":"noted","reservation_date":"2018-02-19 12:53:27","uploaded":"2018-02-20 13:34:04","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181864.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181865","title":"Identification of LTE-M (eMTC) traffic","source":"Qualcomm Incorporated","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 - In case of MME change, the source MME provides the cat-M1\/M2 information to the target MME over S10.","secretary_remarks":"Revised in parallel session to S2-182362.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11050,"status":"revised","reservation_date":"2018-02-19 12:53:27","uploaded":"2018-02-20 13:34:04","revisionof":"","revisedto":"S2-182362","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3404.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181865.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181866","title":"[DRAFT] Reply LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"Provdes response to GSMA Packet IoTTF and attaches CR to TS 23.401","secretary_remarks":"Response to S2-181432. 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":11130,"status":"not treated","reservation_date":"2018-02-19 12:53:28","uploaded":"2018-02-20 13:34:04","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA Packet IoTTF","Cc":"CT WG1, CT WG4, RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181866.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181867","title":"Missing identification of step in clause 5.3.8.4","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies the sequence of steps in MME","secretary_remarks":"Revised in parallel session to S2-182370.","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-02-19 12:53:28","uploaded":"2018-02-20 13:34:04","revisionof":"","revisedto":"S2-182370","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"EDCE5"}],"crnumber":3405.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181867.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181909","title":"Corrections of Group Message Delivery via NIDD","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Allow the SCEF to buffer the non-IP data for a group of UEs. 2. Clarify that the notification is sent for each UE. 3. Add Trigger Indication in Group MT NIDD Submit Indication to SCS\/AS.","secretary_remarks":"Revised in parallel session to S2-182364.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":10940,"status":"revised","reservation_date":"2018-02-19 13:34:55","uploaded":"2018-02-20 14:21:32","revisionof":"","revisedto":"S2-182364","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"},{"winame":"NAPS"}],"crnumber":384.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181909.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181910","title":"Group NIDD configuration","source":"Ericsson","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":"Postponed 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":10980,"status":"postponed","reservation_date":"2018-02-19 13:34:56","uploaded":"2018-02-20 15:30:38","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"},{"winame":"NAPS"}],"crnumber":385.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181910.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181945","title":"APN Rate Control after PDN connection release and re-establishment","source":"Huawei, HiSilicon","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"discussion","for":"Decision","abstract":"This contribution analyses an issue with the current APN Rate Control mechanism and proposes a 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":11140,"status":"noted","reservation_date":"2018-02-19 16:23:39","uploaded":"2018-02-20 13:24:49","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181945.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181946","title":"Correction of APN Rate Control for PDN connection release and re-establishment","source":"Huawei, HiSilicon","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of APN Rate Control, attach, detach, PDN connectivity as well as of PDN disconnection procedures have been updated to describe that the network and the UE store the APN Rate Control status at release of the last PDN connection of a given APN and that they retrieve it at a subsequent establishment of a first PDN connection for a given APN.","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":11150,"status":"not treated","reservation_date":"2018-02-19 16:23:39","uploaded":"2018-02-20 13:24:49","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"},{"winame":"CIoT"}],"crnumber":3408.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181946.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181947","title":"Correction of APN Rate Control for PDN connection release and re-establishment","source":"Huawei, HiSilicon","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description 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 and the UE store the APN Rate Control status at release of the last PDN connection of a given APN and that they retrieve it at a subsequent establishment of a first PDN connection for a given APN.","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":11160,"status":"not treated","reservation_date":"2018-02-19 16:23:40","uploaded":"2018-02-20 13:24:49","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"},{"winame":"CIoT"}],"crnumber":386.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181947.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181968","title":"Correction to the Usage of Monitoring Duration","source":"Huawei, HiSilicon","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When the monitoring duration expires for a continuous Monitroing Request for an individual UE or a group of UEs, the SCEF requests the HSS (for monitoring events configuraed via HSS) or MME(s)\/SGSN(s) (for monitoring events configurated directly with the MME\/SGSN) to delete the related monitoring event configuration and also deletes its associated Monitoring Event configuration.","secretary_remarks":"Revised in parallel session to S2-182374.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":10810,"status":"revised","reservation_date":"2018-02-19 16:23:42","uploaded":"2018-02-20 13:25:41","revisionof":"","revisedto":"S2-182374","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"},{"winame":"TEI15"}],"crnumber":387.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181968.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181969","title":"[DRAFT] Reply LS on Usage of Monitoring Durations","source":"Huawei, HiSilicon","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"LS out","for":"Approval","abstract":"This contribution replies the LS from the CT WG3 regarding the usage of monitoring duration.","secretary_remarks":"Response to S2-181441. Revised in parallel session to S2-182327.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":10830,"status":"revised","reservation_date":"2018-02-19 16:23:43","uploaded":"2018-02-20 13:25:41","revisionof":"","revisedto":"S2-182327","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181969.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181970","title":"Clarification of Group Message Delivery via MBMS","source":"Huawei, HiSilicon","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Unify the message to contain the parameters for MB2 or xMB respectively. 2) Correct the steps for xMB interface to activate the MBMS bearer. 3) Correct the descriptions for xMB interface to create the service.","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":10870,"status":"noted","reservation_date":"2018-02-19 16:23:43","uploaded":"2018-02-20 13:25:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"},{"winame":"TEI15"}],"crnumber":388.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181970.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181971","title":"[DRAFT] Reply LS on Group Message Delivery via MBMS","source":"Huawei, HiSilicon","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"LS out","for":"Approval","abstract":"This contribution replies the LS from the CT WG3 regarding group message delivery via MBMS.","secretary_remarks":"Response to S2-181442. Revised in parallel session to S2-182328.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":10890,"status":"revised","reservation_date":"2018-02-19 16:23:44","uploaded":"2018-02-20 13:25:41","revisionof":"","revisedto":"S2-182328","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181971.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181988","title":"Supporting Common API framework for NEF","source":"Convida Wireless LLC, Qualcomm Incorporated, Intel, AT&T, Nokia, Nokia Shanghai Bell, Samsung","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added statements to 5.20 explaining when CAPIF may be used and how it relates to the NEF.","secretary_remarks":"Revision of approved DRAFTCR S2-181353. Revised in parallel session to S2-182325.","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":"revised","reservation_date":"2018-02-19 17:40:27","uploaded":"2018-02-20 14:47:24","revisionof":"S2-181353","revisedto":"S2-182325","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":124.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181988.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182047","title":"Supporting Common API framework for SCEF","source":"Convida Wireless LLC, Qualcomm Incorporated, AT&T, Intel, Nokia, Nokia Shanghai Bell, Samsung","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that the SCEF may support the CAPIF.","secretary_remarks":"Revision of agreed CR S2-181264 from S2#125. Revised in parallel session to S2-182326.","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":"revised","reservation_date":"2018-02-20 01:58:39","uploaded":"2018-02-20 14:47:24","revisionof":"S2-181264","revisedto":"S2-182326","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":382.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182047.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182052","title":"Common API Framework (CAPIF) integration with SCEF and NEF","source":"Intel","contact":"Puneet Jain","contact-id":36283,"tdoctype":"discussion","for":"Decision","abstract":"This contribution propose Architectural principles and integration models for Common API Framework (CAPIF) integration with SCEF and NEF","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":11200,"status":"noted","reservation_date":"2018-02-20 02:35:52","uploaded":"2018-02-20 06:31:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182052.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182240","title":"CIoT Attach correction","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 5.3.4B Add a condition that MME doesn't send S1AP CONNECTION ESTABLISHMENT INDICATION message, i.e. if MME needs to send NAS Service Accept, S1AP CONNECTION ESTABLISHMENT INDICATION message will not be sent. Clause 5.11.2 For initial Attach or TAU, clarify that UE Radio Capability is sent in S1AP DOWNLINK NAS TRANSPORT message; In subseequent ECM connection, clarify that S1AP CONNECTION ESTABLISHMENT INDICATION message is only sent if MME has no NAS PDU to send in downlink after receiving S1AP INITIAL UE MESSAGE.","secretary_remarks":"Revision of approved CR S2-181371. Also provided in S2-182239. Pending RAN WG3 feedback. Merged into S2-182271.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":10790,"status":"merged","reservation_date":"2018-02-20 12:20:17","uploaded":"2018-02-20 15:02:52","revisionof":"S2-181371","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"CIoT"},{"winame":"TEI15"}],"crnumber":3390.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182240.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182242","title":"Alignment with RAN and CT WG1 on fetching of UE Radio Capability and handling of S1AP Connection Establishment Indication","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This paper proposes the necessary alignment between SA WG2 and RAN\/CT WG1 on fetching UE Radio Capability, and also proposes to revert the change in S2-181371.","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":10780,"status":"noted","reservation_date":"2018-02-20 12:25:29","uploaded":"2018-02-20 15:02:52","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_126_Montreal\/Docs\/S2-182242.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182244","title":"Introduction of LTE-M RAT type and identification of LTE-M UE and traffic in the EPS","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: As per GSMA request this CR provides a solution to this by adding a new LTE-M RAT Type, without requiring the RAN to collect data on when CE mode A\/B is used but just relying on the UE capabilities signalled by the UE to the RAN. The distinction between WB-E-UTRAN and LTE-M is brought into this TS.","secretary_remarks":"Postponed 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":11030,"status":"postponed","reservation_date":"2018-02-20 12:45:18","uploaded":"2018-02-20 13:17:21","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.203,"crspecversion":"15.1.0","workitem":[{"winame":"CIoT"},{"winame":"TEI15"}],"crnumber":1117.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182244.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182245","title":"Introduction of LTE-M RAT type and identification of LTE-M UE and traffic in the EPS","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: As per GSMA request this CR provides a solution to this by adding a new LTE-M RAT Type, without requiring the RAN to collect data on when CE mode A\/B is used but just relying on the UE capabilities signalled by the UE to the RAN. The distinction between WB-E-UTRAN and LTE-M is brought into this TS.","secretary_remarks":"Postponed 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":11040,"status":"postponed","reservation_date":"2018-02-20 12:48:06","uploaded":"2018-02-20 13:17:21","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"CIoT"},{"winame":"TEI15"}],"crnumber":389.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182245.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182246","title":"CAPIF integration with 3GPP northbound APIs","source":"Huawei, Samsung","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Decision","abstract":"Proposal for CAPIF integration with 3GPP northbound APIs","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":11210,"status":"noted","reservation_date":"2018-02-20 13:06:27","uploaded":"2018-02-20 13:11:39","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182246.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182325","title":"Supporting Common API framework for NEF","source":"Convida Wireless LLC, Qualcomm Incorporated, Intel, AT&T, Nokia, Nokia Shanghai Bell, Samsung","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added statements to 5.20 explaining when CAPIF may be used and how it relates to the NEF.","secretary_remarks":"Revision of S2-181988. Revised in parallel session to S2-182413.","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":"revised","reservation_date":"2018-02-28 13:41:17","uploaded":"2018-03-05 11:17:54","revisionof":"S2-181988","revisedto":"S2-182413","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":124.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182325.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182326","title":"Supporting Common API framework for SCEF","source":"Convida Wireless LLC, Qualcomm Incorporated, AT&T, Intel, Nokia, Nokia Shanghai Bell, Samsung","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that the SCEF may support the CAPIF.","secretary_remarks":"Revision of S2-182047. Revised in parallel session to S2-182414.","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":"revised","reservation_date":"2018-02-28 13:41:18","uploaded":"2018-03-05 11:17:54","revisionof":"S2-182047","revisedto":"S2-182414","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":382.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182326.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182327","title":"Reply LS on Usage of Monitoring Duration","source":"SA WG2","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4","secretary_remarks":"Revision of S2-181969. Revised in parallel session to S2-182397.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":10840,"status":"revised","reservation_date":"2018-02-28 13:41:19","uploaded":"2018-03-05 11:17:54","revisionof":"S2-181969","revisedto":"S2-182397","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182327.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182328","title":"Reply LS on Group Message Delivery via MBMS","source":"SA WG2","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: SA WG4","secretary_remarks":"Revision of S2-181971. Revised in parallel session to S2-182398.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":10900,"status":"revised","reservation_date":"2018-02-28 13:41:19","uploaded":"2018-03-05 11:17:54","revisionof":"S2-181971","revisedto":"S2-182398","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182328.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182362","title":"Identification of LTE-M (eMTC) traffic","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Endorsement","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 - 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-181865. Revised in parallel session to S2-182372.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11060,"status":"revised","reservation_date":"2018-03-01 18:37:36","uploaded":"2018-03-05 11:17:55","revisionof":"S2-181865","revisedto":"S2-182372","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3404.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182362.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182363","title":"[DRAFT] LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, CT WG3, CT WG4, SA WG5","secretary_remarks":"Created in parallel session. Revised in parallel session to S2-182373.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11090,"status":"revised","reservation_date":"2018-03-01 18:37:37","uploaded":"2018-03-05 11:27:55","revisionof":"","revisedto":"S2-182373","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, CT WG3, CT WG4, SA WG5","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182363.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182364","title":"Corrections of Group Message Delivery via NIDD","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Allow the SCEF to buffer the non-IP data for a group of UEs. 2. Clarify that the notification is sent for each UE. 3. Add Trigger Indication in Group MT NIDD Submit Indication to SCS\/AS.","secretary_remarks":"Revision of S2-181909. Revised in parallel session to S2-182399.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":10950,"status":"revised","reservation_date":"2018-03-01 18:37:37","uploaded":"2018-03-05 11:27:55","revisionof":"S2-181909","revisedto":"S2-182399","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"},{"winame":"NAPS"}],"crnumber":384.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182364.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182367","title":"Alignment with stage-3 reporting and access restriction for unlicensed spectrum","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligns with stage-3 decisions of CT WG4 to define only one value for unlicensed spectrum data volume reporting and access restriction and not differentiate between LAA, LWA\/LWIP.","secretary_remarks":"Revision of S2-181862. 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":11310,"status":"agreed","reservation_date":"2018-03-01 18:37:39","uploaded":"2018-03-05 11:27:55","revisionof":"S2-181862","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"USOS"}],"crnumber":3403.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180111","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182367.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182368","title":"Addition of Broadcast of Assistance Data for E-UTRAN","source":"Qualcomm Incorporated, Ericsson","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Endorsement","abstract":"Summary of change: Adds a new procedure for transferring assistance data from an E-SMLC to an eNodeB for broadcast to target UEs. This procedure is based on current agreements in RAN but may need to be updated later after the RAN solution is finalized. Another procedure is added to enable delivery of ciphering keys to UEs by an E-SMLC via an MME using mobility management Attach and TAU procedures. Definition of new subscription data for ciphering keys is added for an HLR\/HSS. MME and E-SMLC functional description is updated.","secretary_remarks":"Revision of S2-181863. For Technical Endorsement. Endorsed in parallel session. Block endorsed.","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":"endorsed","reservation_date":"2018-03-01 18:37:40","uploaded":"2018-03-05 11:27:55","revisionof":"S2-181863","revisedto":"","release":"Rel-15","crspec":23.271,"crspecversion":"14.3.0","workitem":[{"winame":"TEI15"}],"crnumber":432.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182368.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182369","title":"[DRAFT] LS on encrypting broadcasted positioning data and LS on provisioning of positioning assistance data via LPPa for broadcast","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: RAN WG3, RAN WG2, CT WG4, SA WG3","secretary_remarks":"Created in parallel session. Response to S2-181452 and S2-182826. Revised in parallel session to S2-182415.","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":"revised","reservation_date":"2018-03-01 18:37:41","uploaded":"2018-03-05 11:27:55","revisionof":"","revisedto":"S2-182415","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"RAN WG3, RAN WG2, CT WG4, SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182369.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182370","title":"Missing identification of step in clause 5.3.8.4","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies the sequence of steps in MME","secretary_remarks":"Revision of S2-181867. 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":11370,"status":"agreed","reservation_date":"2018-03-01 18:37:41","uploaded":"2018-03-05 11:27:55","revisionof":"S2-181867","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"EDCE5"}],"crnumber":3405.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180108","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182370.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182372","title":"Identification of LTE-M (eMTC) traffic","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Endorsement","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 - 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-182362. For Technical Endorsement. Revised in parallel session to S2-182412.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11070,"status":"revised","reservation_date":"2018-03-01 18:38:13","uploaded":"2018-03-05 11:27:55","revisionof":"S2-182362","revisedto":"S2-182412","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3404.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182372.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182373","title":"[DRAFT] LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, CT WG3, CT WG4, SA WG5","secretary_remarks":"Revision of S2-182363. Revised in parallel session to S2-182411.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11100,"status":"revised","reservation_date":"2018-03-01 18:38:14","uploaded":"2018-03-05 11:27:55","revisionof":"S2-182363","revisedto":"S2-182411","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, CT WG3, CT WG4, SA WG5","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182373.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182374","title":"Correction to the Usage of Monitoring Duration","source":"Huawei, HiSilicon, Convida Wireless LLC, Ericsson, Nokia, Nokia Shanghai Bell","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When the monitoring duration expires for a continuous Monitroing Request for an individual UE or a group of UEs, the SCEF requests the HSS (for monitoring events configuraed via HSS) or MME(s)\/SGSN(s) (for monitoring events configurated directly with the MME\/SGSN) to delete the related monitoring event configuration and also deletes its associated Monitoring Event configuration.","secretary_remarks":"Revision of S2-181968. 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":10820,"status":"agreed","reservation_date":"2018-03-02 14:30:01","uploaded":"2018-03-05 11:27:55","revisionof":"S2-181968","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":387.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180109","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182374.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182397","title":"Reply LS on Usage of Monitoring Duration","source":"SA WG2","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4. Attachment: CR#0387 vs. TS 23.682 (S2-182374)","secretary_remarks":"Revision of S2-182327. 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":10850,"status":"approved","reservation_date":"2018-03-02 14:31:13","uploaded":"2018-03-05 11:27:55","revisionof":"S2-182327","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-181441","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182397.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182398","title":"Reply LS on Group Message Delivery via MBMS","source":"SA WG2","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: SA WG4","secretary_remarks":"Revision of S2-182328. 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":10910,"status":"approved","reservation_date":"2018-03-02 14:31:13","uploaded":"2018-03-05 11:27:55","revisionof":"S2-182328","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-181442","lsto":"CT WG3","Cc":"SA WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182398.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182399","title":"Corrections of Group Message Delivery via NIDD","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Allow the SCEF to buffer the non-IP data for a group of UEs. 2. Clarify that the notification is sent for each UE. 3. Add Trigger Indication in Group MT NIDD Submit Indication to SCS\/AS.","secretary_remarks":"Revision of S2-182364. Revised in parallel session to S2-182416.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":10960,"status":"revised","reservation_date":"2018-03-02 14:31:13","uploaded":"2018-03-05 11:27:55","revisionof":"S2-182364","revisedto":"S2-182416","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"},{"winame":"NAPS"}],"crnumber":384.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182399.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182411","title":"LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, CT WG3, CT WG4, SA WG5. CC: RAN WG2. Attachment: S2-182412","secretary_remarks":"Revision of S2-182373. 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":11110,"status":"approved","reservation_date":"2018-03-02 14:31:16","uploaded":"2018-03-05 11:27:55","revisionof":"S2-182373","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, CT WG3, CT WG4, SA WG5","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182411.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182412","title":"Identification of LTE-M (eMTC) traffic","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Orange","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Endorsement","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 - 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-182372. Endorsed in parallel session. Block endorsed.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":11080,"status":"endorsed","reservation_date":"2018-03-02 14:31:16","uploaded":"2018-03-05 11:27:55","revisionof":"S2-182372","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3404.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182412.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182413","title":"Supporting Common API framework for NEF","source":"Convida Wireless LLC, Qualcomm Incorporated, Intel, AT&T, Nokia, Nokia Shanghai Bell, Samsung, Huawei","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added statements to 5.20 explaining when CAPIF may be used and how it relates to the NEF.","secretary_remarks":"Revision of S2-182325. Agreed in parallel session. Revised to S2-183003.","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":"revised","reservation_date":"2018-03-02 14:31:17","uploaded":"2018-03-05 11:27:55","revisionof":"S2-182325","revisedto":"S2-183003","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":124.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182413.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182414","title":"Supporting Common API framework for SCEF","source":"Convida Wireless LLC, Qualcomm Incorporated, AT&T, Intel, Nokia, Nokia Shanghai Bell, Samsung, Huawei","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that the SCEF may support the CAPIF.","secretary_remarks":"Revision of S2-182326. 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":11270,"status":"agreed","reservation_date":"2018-03-02 14:31:18","uploaded":"2018-03-05 11:27:55","revisionof":"S2-182326","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":382.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-180109","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182414.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182415","title":"LS on encrypting broadcasted positioning data and LS on provisioning of positioning assistance data via LPPa for broadcast","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3, CT WG4, CT WG1. CC: SA WG3. Attachments: S2-182368","secretary_remarks":"Revision of S2-182369. 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":11350,"status":"approved","reservation_date":"2018-03-02 14:31:20","uploaded":"2018-03-05 11:27:55","revisionof":"S2-182369","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-181452","lsto":"RAN WG2, RAN WG3, CT WG4, CT WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182415.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182416","title":"Corrections of Group Message Delivery via NIDD","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Allow the SCEF to buffer the non-IP data for a group of UEs. 2. Clarify that the notification is sent for each UE. 3. Add Trigger Indication in Group MT NIDD Submit Indication to SCS\/AS.","secretary_remarks":"Revision of S2-182399. Revised to S2-182995.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":10970,"status":"revised","reservation_date":"2018-03-02 14:37:55","uploaded":"2018-03-05 11:27:55","revisionof":"S2-182399","revisedto":"S2-182995","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"},{"winame":"NAPS"}],"crnumber":384.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182416.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182995","title":"Corrections of Group Message Delivery via NIDD","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Allow the SCEF to buffer the non-IP data for a group of UEs. 2. Clarify that the notification is sent for each UE. 3. Add Trigger Indication in Group MT NIDD Submit Indication to SCS\/AS.","secretary_remarks":"Revision of S2-182416. Revised to S2-183017.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"Rel-15 3GPP Packet Acc. Maint. - essential corrections - excl. R15 5GS","tdoc_agenda_sort_order":10971,"status":"revised","reservation_date":"2018-03-05 10:37:31","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182416","revisedto":"S2-183017","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"TEI15"},{"winame":"NAPS"}],"crnumber":384.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182995.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-183003","title":"Supporting Common API framework for NEF","source":"Convida Wireless LLC, Qualcomm Incorporated, Intel, AT&T, Nokia, Nokia Shanghai Bell, Samsung, Huawei","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added statements to 5.20 explaining when CAPIF may be used and how it relates to the NEF.","secretary_remarks":"Revision of S2-182413. 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":11241,"status":"agreed","reservation_date":"2018-03-05 10:40:14","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182413","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":124.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-180099","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-183003.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-183017","title":"Corrections of Group Message Delivery via NIDD","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Allow the SCEF to buffer the non-IP data for a group of UEs. 2. Clarify that the notification is sent for each UE. 3. Add Trigger Indication in Group MT NIDD Submit Indication to SCS\/AS.","secretary_remarks":"Revision of S2-182995. 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":10972,"status":"agreed","reservation_date":"2018-03-05 10:40:41","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182995","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":384.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-180109","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-183017.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]