[{"name":"S2-1904901","title":"LS from SA WG4: Reply LS (to RAN WG2) for inclusion of Receive Only Mode MBMS service parameters in USD","source":"SA WG4","contact":"Charles Lo","contact-id":50185,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 thanks RAN WG2 for your LS (in R2-1818960\/S4-181391) on inclusion of Receive Only Mode MBMS service parameters in the USD. RAN WG2 requested SA WG4 to consider adding in the MBMS Service Announcement, or 'USD', RF information associated with the delivery of Receive Only Mode (ROM) services. Those ROM service related RF parameters include EARFCN, MBMS carrier numerology and bandwidth information. RAN WG2 indicated that this information is desirable for inclusion in the MBMS Interest Indication sent by the UE to inform the serving eNB that the UE is currently receiving, or is interested to receive, a ROM service from a different eNB, and to enable battery power savings in UE search for MBMS ROM frequencies. SA WG4 discussed this matter and agrees that such (optional) inclusion of ROM service information in the USD can be useful to the UE, for the reasons stated by RAN WG2 in their LS. As result, SA WG4 has decided to add, to the Rel-15 TS 26.346, an optional child element r15:ROMSvcRfParams under the userServiceDescription element of the USBD fragment. The r15:ROMSvcRfParams element contains a Frequency child element which in turn contains the attributes subcarrierSpacing and bandwidth. In offline discussion between SA WG4 and RAN WG2 members regarding the RAN WG2 LS, explicit and known values of those attributes should be defined. Specifically, the allowed values of subcarrierSpacing shall be one of the following numbers in kHz: 1.25, 7.5 or 15, and the allowed values of bandwidth shall be one of the following numbers in MHz: 1.4, 3, 5, 10, 15 and 20. SA WG4 asks RAN WG2 to review the Action: taken by SA WG4 towards addressing your request. We have attached the agreed CRs to the Rel-15 and Rel-16 TS 26.346 on inclusion of ROM service parameters in the USD.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2019-04-23 11:45:51","uploaded":"2019-04-23 13:14:44","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2, RAN WG1","lsoriginalls":"S4-190563","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904901.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904945","title":"LS from SA WG3LI: Response LS on reporting all Cell IDs in 5G","source":"SA WG3LI","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG3-LI would like to thank RAN WG3 for the reply LS on Reporting All Cell Ids in 5G in Tdoc R3-191111. SA WG3-LI understanding is that every change in the primary cell of secondary group will be reported by RAN to the CN. However, it was unclear to SA WG3-LI whether the primary cell of secondary group will be included as additional location information available when the Mobility Management events are handled by the MME\/AMF and that changes of the primary cell of secondary group will be handled in the MME as location update and in the AMF as mobility registration update. SA WG3-LI requires that for every UE; - Whenever the primary cell of the primary group changes (including initial attach \/ registration), both the primary cell of the primary group and the primary cell of the secondary group (if assigned) needs to be reported to the MME\/AMF. - Whenever the primary cell of the secondary group changes (including initial attach to secondary group), both the primary cell of the primary group and the primary cell of the secondary group needs to be reported to the MME\/AMF. In the LS, RAN WG3 mentions that 'There were doubts whether this solution causes excessive signalling in the RAN. A possible mitigation to this drawback is to add a flag from the Core Network to indicate whether PSCell shall be reported. This can be added as an enhancement to the current solution.' SA WG3-LI discussed this aspect and would like to highlight that, in order to preserve the non-detectability of LI, any signaling over non-LI specific interfaces shall be the same regardless of whether or not the subscriber is an LI target. Any different approach would not fulfill LI security and confidentiality requirements. While SA WG3-LI is working on draft CRs to TSs 33.107, 33.108, 33.127 and 33.128, aiming to submit them for approval to TSG SA#84, SA WG3-LI would ask RAN WG3 and SA WG2 to assess any possible implication in terms of signaling due to the above considerations. In its work, SA WG3-LI has assumed that, at least for rel-15, the new capabilities in the CN will be kept limited to the MME\/AMF without additional impacts on other CN nodes\/NFs and related interfaces. Action: SA WG3-LI asks SA WG2 to specify the capability in such as way that any signaling over non-LI specific interfaces shall be the same regardless of whether or not the subscriber is an LI target. Action: SA WG3-LI asks SA WG2 to confirm that the primary cell of secondary group will be included as additional location information available when the Mobility Management events are handled by the MME\/AMF and that changes of the primary cell of secondary group will be handled in the MME as location update and in the AMF as mobility registration update.","secretary_remarks":"Response drafted in S2-1906031. Final response in S2-1906170","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10080,"status":"replied to","reservation_date":"2019-04-30 12:41:43","uploaded":"2019-04-30 13:08:24","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG2","Cc":"SA WG3, TSG CT, CT WG1, CT WG3, ETSI TC LI, TSG SA, TSG RAN","lsoriginalls":"S3i190265","lsreply":"S2-1906170, S2-1906170","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904945.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905081","title":"Correction to Group Message Delivery","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The sequence description is corrected with respect to xMB usage. Add a note that location information in internal format of 3GPP network can be used between SCS\/AS and SCEF if allowed by SLA. A few other corrections and clarifications.","secretary_remarks":"Revised in parallel session to S2-1906032.","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10220,"status":"revised","reservation_date":"2019-05-04 13:32:21","uploaded":"2019-05-07 13:29:02","revisionof":"","revisedto":"S2-1906032","release":"Rel-15","crspec":23.682,"crspecversion":"15.8.0","workitem":[{"winame":"NAPS"},{"winame":"TEI15"}],"crnumber":450.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905081.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905082","title":"Correction to Group Message Delivery","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: The sequence description is corrected with respect to xMB usage. Add a note that location information in internal format of 3GPP network can be used between SCS\/AS and SCEF if allowed by SLA. A few other corrections and clarifications.","secretary_remarks":"Revised in parallel session to S2-1906033.","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10240,"status":"revised","reservation_date":"2019-05-04 13:32:22","uploaded":"2019-05-07 13:29:02","revisionof":"","revisedto":"S2-1906033","release":"Rel-16","crspec":23.682,"crspecversion":"16.2.0","workitem":[{"winame":"NAPS"},{"winame":"TEI15"}],"crnumber":451.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905082.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905243","title":"Location reporting of secondary cell","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduction of the principle that also the secondary cell information is reported along with the master cell Location Reporting information when it is available. The reason for this condition is that the secondary cell information cannot be provided in the case of initial message when Dual Connectivity configuration has not yet been set up.","secretary_remarks":"Revised in parallel session to S2-1906029.","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10160,"status":"revised","reservation_date":"2019-05-06 12:37:12","uploaded":"2019-05-07 12:50:32","revisionof":"","revisedto":"S2-1906029","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"LI15"},{"winame":"TEI15"}],"crnumber":1349.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905243.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905244","title":"Location reporting of secondary cell","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduction of the principle that also the secondary cell information is reported along with the master cell Location Reporting information when it is available. The reason for this condition is that the secondary cell information cannot be provided in the case of initial message when Dual Connectivity configuration has not yet been set up. The normative text on Non-3GPP case is aligned with the already existing editor's note.","secretary_remarks":"Revised in parallel session to S2-1906030.","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10190,"status":"revised","reservation_date":"2019-05-06 12:41:07","uploaded":"2019-05-07 12:50:32","revisionof":"","revisedto":"S2-1906030","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"LI15"},{"winame":"TEI15"}],"crnumber":1350.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905244.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905584","title":"Secondary Cell ID Reporting - completion and signalling efficiency","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To keep the core network updated with the secondary cell IDs, we therefore need to also cover the following cases: X2 handover into a dual connectivity configuration (i.e. add PScell ID to S1 Path Switch request message); S1 handover into a dual connectivity configuration (i.e. add PScell ID to S1 Handover Notify message); Add PSCell ID to UE Context Resume as it is plausible that the UE is resumed into a DC configuration. Add PSCell ID into Initial Context Setup Response - as the Initial Context Setup Request would be processed (and could lead to the UE entering a DC configuration) before any Location Reporting Request is received from the MME\/AMF and\/or is processed by the RAN. Add the PSCell ID to the Uplink NAS Transport message: this is useful for connected mode mobility events in the situation that 'location reporting' has not been activated by the MME\/AMF. Add the PSCell ID (and timestamp) to the UE Context Release Complete message. This is useful for the situation that the UE is disabled (e.g. battery ripped off \/ UE thrown into a river) and 'location reporting' has not been activated by the MME\/AMF.","secretary_remarks":"Revised in parallel session to S2-1906028.","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10120,"status":"revised","reservation_date":"2019-05-07 09:59:44","uploaded":"2019-05-07 13:28:09","revisionof":"","revisedto":"S2-1906028","release":"Rel-15","crspec":23.401,"crspecversion":"15.7.0","workitem":[{"winame":"EDCE5"}],"crnumber":3513.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905584.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905613","title":"Secondary Cell ID Reporting - completion and signalling efficiency","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: To keep the core network updated with the secondary cell IDs, we therefore need to also cover the following cases: a) X2 handover into a dual connectivity configuration (i.e. add PScell ID to S1 Path Switch request message); b) S1 handover into a dual connectivity configuration (i.e. add PScell ID to S1 Handover Notify message); c) Add the PSCell ID to the Uplink NAS Transport message: this is useful for connected mode mobility events in the situation that 'location reporting' has not been activated by the MME\/AMF. d) Add the PSCell ID to the UE Context Release Complete message. This is useful for the situation that the UE is disabled (e.g. battery ripped off \/ UE thrown into a river) while in a DC configuration and 'location reporting' has not been activated by the MME\/AMF. e) Add the PSCell ID to the E-RAB Release message.","secretary_remarks":"LATE DOC: Rx 17\/05 16:00. For e-mail approval. Approved","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10150,"status":"agreed","reservation_date":"2019-05-07 10:04:06","uploaded":"2019-05-19 19:47:58","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.401,"crspecversion":"16.2.0","workitem":[{"winame":"EDCE5"}],"crnumber":3514.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-190403","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905613.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906028","title":"Secondary Cell ID Reporting - completion and signalling efficiency","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To keep the core network updated with the secondary cell IDs, we therefore need to also cover the following cases: X2 handover into a dual connectivity configuration (i.e. add PScell ID to S1 Path Switch request message); S1 handover into a dual connectivity configuration (i.e. add PScell ID to S1 Handover Notify message); Add PSCell ID to UE Context Resume as it is plausible that the UE is resumed into a DC configuration. Add PSCell ID into Initial Context Setup Response - as the Initial Context Setup Request would be processed (and could lead to the UE entering a DC configuration) before any Location Reporting Request is received from the MME\/AMF and\/or is processed by the RAN. Add the PSCell ID to the Uplink NAS Transport message: this is useful for connected mode mobility events in the situation that 'location reporting' has not been activated by the MME\/AMF. Add the PSCell ID (and timestamp) to the UE Context Release Complete message. This is useful for the situation that the UE is disabled (e.g. battery ripped off \/ UE thrown into a river) while in a DC configuration and 'location reporting' has not been activated by the MME\/AMF. Add the PSCell ID to the E-RAB Release message.","secretary_remarks":"Revision of S2-1905584. Revised in parallel session to S2-1906165.","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10130,"status":"revised","reservation_date":"2019-05-15 17:17:18","uploaded":"2019-05-19 19:57:54","revisionof":"S2-1905584","revisedto":"S2-1906165","release":"Rel-15","crspec":23.401,"crspecversion":"15.7.0","workitem":[{"winame":"EDCE5"}],"crnumber":3513.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906028.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906029","title":"Location reporting of secondary cell","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduction of the principle that the AMF does not relay the secondary cell part of the ULI information further to SMF.","secretary_remarks":"Revision of S2-1905243. Revised in parallel session to S2-1906163.","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10170,"status":"revised","reservation_date":"2019-05-15 17:17:19","uploaded":"2019-05-19 19:57:54","revisionof":"S2-1905243","revisedto":"S2-1906163","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"LI15"},{"winame":"TEI15"}],"crnumber":1349.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906029.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906030","title":"Location reporting of secondary cell","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduction of the principle that the AMF does not relay the secondary cell part of the ULI information further to SMF. The normative text on Non-3GPP case is aligned with the already existing editor's note.","secretary_remarks":"Revision of S2-1905244. Revised in parallel session to S2-1906164.","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10200,"status":"revised","reservation_date":"2019-05-15 17:17:20","uploaded":"2019-05-19 19:57:54","revisionof":"S2-1905244","revisedto":"S2-1906164","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"LI15"},{"winame":"TEI15"}],"crnumber":1350.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906030.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906031","title":"[DRAFT] Response LS on reporting all Cell IDs in 5G","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3LI, RAN WG3. CC: SA WG3, TSG CT, CT WG1, CT WG3, ETSI TC LI, TSG SA, TSG RAN.","secretary_remarks":"Created in parallel session. Response to S2-1904945. Revised in parallel session to S2-1906166.","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10090,"status":"revised","reservation_date":"2019-05-15 17:17:21","uploaded":"2019-05-19 19:57:54","revisionof":"","revisedto":"S2-1906166","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"LI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3LI, RAN WG3","Cc":"SA WG3, TSG CT, CT WG1, CT WG3, ETSI TC LI, TSG SA, TSG RAN","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906031.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906032","title":"Group message delivery using MBMS via xMB","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The sequence description is corrected with respect to xMB usage. Add a note that location information in internal format of 3GPP network can be used between SCS\/AS and SCEF if allowed by SLA. A few other corrections and clarifications.","secretary_remarks":"Revision of S2-1905081. Agreed in parallel session. This was Block approved","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2019-05-15 17:17:21","uploaded":"2019-05-19 19:57:54","revisionof":"S2-1905081","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.8.0","workitem":[{"winame":"NAPS"}],"crnumber":450.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190405","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906032.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906033","title":"Group message delivery using MBMS via xMB","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: The sequence description is corrected with respect to xMB usage. Add a note that location information in internal format of 3GPP network can be used between SCS\/AS and SCEF if allowed by SLA. A few other corrections and clarifications.","secretary_remarks":"Revision of S2-1905082. Agreed in parallel session. This was Block approved","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2019-05-15 17:17:22","uploaded":"2019-05-19 19:57:54","revisionof":"S2-1905082","revisedto":"","release":"Rel-16","crspec":23.682,"crspecversion":"16.2.0","workitem":[{"winame":"NAPS"}],"crnumber":451.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-190405","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906033.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906163","title":"Location Reporting of secondary cell","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduction of the principle that the AMF does not relay the secondary cell part of the ULI information further to SMF.","secretary_remarks":"Revision of S2-1906029. Agreed in parallel session. This was Block approved","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10180,"status":"agreed","reservation_date":"2019-05-19 19:37:08","uploaded":"2019-05-19 19:57:56","revisionof":"S2-1906029","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"LI15"},{"winame":"TEI15"}],"crnumber":1349.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190404","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906163.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906164","title":"Location Reporting of secondary cell","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduction of the principle that the AMF does not relay the secondary cell part of the ULI information further to SMF. The normative text on Non-3GPP case is aligned with the already existing editor's note.","secretary_remarks":"Revision of S2-1906030. Agreed in parallel session. This was Block approved","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10210,"status":"agreed","reservation_date":"2019-05-19 19:37:09","uploaded":"2019-05-19 19:57:56","revisionof":"S2-1906030","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"LI15"},{"winame":"TEI15"}],"crnumber":1350.0,"crrevision":2.0,"crcategory":"A","tsg_crp":"SP-190404","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906164.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906165","title":"Secondary Cell ID Reporting - completion and signalling efficiency","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To keep the core network updated with the secondary cell IDs, we therefore need to also cover the following cases: X2 handover into a dual connectivity configuration (i.e. add PScell ID to S1 Path Switch request message); S1 handover into a dual connectivity configuration (i.e. add PScell ID to S1 Handover Notify message); Add the PSCell ID to the Uplink NAS Transport message: this is useful for connected mode mobility events in the situation that 'location reporting' has not been activated by the MME\/AMF. Add the PSCell ID to the UE Context Release Complete message. This is useful for the situation that the UE is disabled (e.g. battery ripped off \/ UE thrown into a river) while in a DC configuration and 'location reporting' has not been activated by the MME\/AMF. Add the PSCell ID to the E-RAB Release message.","secretary_remarks":"Revision of S2-1906028. Agreed in parallel session. This was Block approved","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10140,"status":"agreed","reservation_date":"2019-05-19 19:37:10","uploaded":"2019-05-19 19:57:56","revisionof":"S2-1906028","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.7.0","workitem":[{"winame":"EDCE5"}],"crnumber":3513.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190403","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906165.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906166","title":"[DRAFT] Response LS on reporting all Cell IDs in 5G","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3LI, RAN WG3. CC: SA WG3, TSG CT, CT WG1, CT WG3, ETSI TC LI, TSG SA, TSG RAN.","secretary_remarks":"Revision of S2-1906031. Revised in parallel session to S2-1906170.","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10100,"status":"revised","reservation_date":"2019-05-19 19:37:11","uploaded":"2019-05-19 19:57:56","revisionof":"S2-1906031","revisedto":"S2-1906170","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"LI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3LI, RAN WG3","Cc":"SA WG3, TSG CT, CT WG1, CT WG3, ETSI TC LI, TSG SA, TSG RAN","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906166.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906170","title":"Response LS on reporting all Cell IDs in 5G","source":"SA WG2","contact":"Chris Pudney","contact-id":1122,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3-LI, TSG SA. CC: TSG RAN, TSG CT, SA WG3, RAN WG3. Attachments: TS 23.401 CR 3513.","secretary_remarks":"Revision of S2-1906166. Agreed in parallel session. This was Block approved","agenda_item_sort_order":9,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10110,"status":"approved","reservation_date":"2019-05-19 19:37:58","uploaded":"2019-05-19 19:57:57","revisionof":"S2-1906166","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"LI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1904945","lsto":"SA WG3-LI, TSG SA","Cc":"TSG RAN, TSG CT, SA WG3, RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906170.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]