[{"name":"S2-1904889","title":"LS from RAN WG2: LS to SA2 and SA5 on IAB impact to CN","source":"RAN WG2","contact":"Milos Tesanovic","contact-id":66723,"tdoctype":"LS in","for":"Action","abstract":"Following the successful completion of the Rel-16 Integrated Access and Backhaul (IAB) SI - results of which are captured in TR 38.874 (v16.0.0) - an IAB WI was approved for Rel-16. The following features need to be supported in the Rel-16 IAB system design (please see RP-182882 for further detail of the WID): - Multi-hop backhauling for flexible range extension for both FR1 and FR2. - Topology adaptation including redundant connectivity to optimize backhauling performance and to respond to backhaul (BH) link failure. - Mapping of UE bearers to backhaul RLC channels and QoS enforcement over backhaul RLC channels to meet E2E QoS requirements. - Scalability to a large number of UEs. - Flexible deployment allowing IAB-node operation in EN-DC mode with EPC or in SA-mode with 5GC. - Support for NR-NR DC from the UE and IAB-node perspective. - Efficient operation for both inband and out-of-band relaying. - OTA synchronization across IAB topology. - Support of Rel-15 UEs. {...} To sum up, RAN WG2 as the lead WG for IAB WI would like to inform SA WG2 and SA WG5 about impending efforts needed for IAB across RAN and CN groups. RAN WG2 would further like to inform SA WG2 and SA WG5 of the recently made RAN WG3 agreements introducing an 'IAB Authorized' IE in the INITIAL CONTEXT SETUP REQUEST\/CONTEXT MODIFICATION REQUEST messages. Action: RAN WG2 would like to kindly ask SA WG2 and SA WG5 to take these developments into account when planning their Rel-16 work, by making allowances in their schedule for any IAB impact on CN procedures until completion of Rel-16 scheduled for March 2020 - this may include considering initiating a new SA-groups based IAB-related WI or SI. Please note that an IAB-related SI has already been approved in SA WG3 (FS_NR_IAB_Sec) to study the potential security solutions for securing the wireless backhaul link.","secretary_remarks":"This will be taken into account in handling of the related WI. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10030,"status":"noted","reservation_date":"2019-04-23 11:45:51","uploaded":"2019-04-23 13:14:44","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5","Cc":"CT WG1, SA WG3, RAN WG3","lsoriginalls":"R2-1905475","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904889.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-1904946","title":"LS from ITU-T SG13: LS on information about consent of ITU-T Recommendation Y.3172 'Architectural framework for machine learning in future networks including IMT-2020'","source":"ITU-T SG13","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"ITU-T SG13 would like to inform you that the new Recommendation ITU-T Y.3172 (Y.IMT2020-ML-Arch) 'Architectural framework for machine learning in future networks including IMT-2020' (Ref. SG13-TD180\/PLEN) has been consented at the ITU-T SG13 meeting held in Victoria Falls, Zimbabwe, on 4-14 March 2019. ITU-T SG13 looks forward for future collaboration on topics related to machine learning in future networks including IMT-2020.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2019-04-30 12:41:43","uploaded":"2019-04-30 13:09:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SGs, 3GPP TSG SA, ETSI ISG ENI, IETF NMRG, ISO\/IEC JTC1\/SC42, ISO\/IEC JTC1\/SC29, NGMN","Cc":"SA WG2","lsoriginalls":"SG13-LS95.","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904946.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-1905810","title":"LS from SA WG4: LS on TS 26.501 5G Media Streaming (5GMS); General description and architecture","source":"SA WG4","contact":"Frederic Gabin","contact-id":18030,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 has concluded work on 5G Media Streaming Architecture (5GMSA), where the architecture and procedures for the UE and Network Media Functions have been defined. 5GMSA differentiates between Downlink and Uplink media streaming functions. Downlink media streaming functions allow for content to be ingested and distributed over the 5GS, while leveraging the full potential and capabilities of 5G. Uplink media streaming addresses use cases where media content is captured by the UE and streamed uplink to the network for further distribution. In addition to the network media functions, 5GMSA also breaks down the UE into its logical media functions, each of which serves a different purpose. The identified interfaces are expected to be translated into Media API(s) in the stage 3 realizations. We would like to highlight that stage 3 work is expected to define usage of existing 5GS APIs e.g. to the NEF and PCF and to specify a new northbound API for media content ingest into an MNO operated CDN with possible media processing. SA WG4 would like to kindly ask SA WG2 to review the attached draft TS 26.501, in order to ensure that it is aligned with the 5GS architecture. We appreciate your comments on the specification and thank you in advance. Action: SA WG4 kindly asks to SA WG2 to take the above information into account and to provide SA WG4 with any comments that SA WG2 might have on the draft specification.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"postponed","reservation_date":"2019-05-09 04:57:01","uploaded":"2019-05-09 05:04:38","revisionof":"","revisedto":"S2-1906842","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S4h190837","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905810.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-1905823","title":"LS from NGMN: NGMN 5G End-to-End Architecture Framework","source":"NGMN","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Intention of the LS and required Actions: NGMN is pleased to inform the recipient of this liaison statement for information sharing on the interim third version (v3.0) of the NGMN 5G End-to-End Architecture Framework that includes requirements together with descriptions and concepts associated with new topics. The new topics include: - Autonomic networking - Distributed Ledger Technology - Minimization or avoidance of tunnelling - Network automation Further enhancement, consideration, and review in the articulation of the related requirements together with updates that include security aspects, URLLC, and network data layer is planned for the final version in September 2019. This NGMN liaison is intended for information sharing in terms of the new topics that have been introduced in the attached document. Please take this into account in the 5G architecture considerations","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2019-05-13 11:08:43","uploaded":"2019-05-13 11:09:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA, SA WG2, SA WG3, SA WG5, SA WG6","Cc":"","lsoriginalls":"Liaison_NGMN_P1_to_3GPP.","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905823.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}]