[{"name":"SP-210004","title":"LS from ITU-R WP5D: LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS: Information on the completion of Recommendation ITU-R M.2150 on radio interface technologies for the terrestrial component of IMT-2020","source":"ITU-R WP5D","contact":"Uwe Loewenstein","contact-id":11941,"tdoctype":"LS in","for":"Information","abstract":"Working Party (WP) 5D thanks the RIT\/SRIT Proponents, GCS Proponents and Transposing Organizations as well as the registered Independent Evaluation Groups for their active participation in the IMT 2020 development process. It is noted that Step 8 of the process for the first release of Recommendation ITU-R M.2150 ('Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications 2020 (IMT-2020)') has been successfully concluded. Addendum 8 to the Circular Letter 5\/LCCE\/59 provides information on the completion and approval of Recommendation ITU-R M.2150. WP 5D takes this opportunity to express appreciation to the work carried out by the external organizations and would welcome further opportunity in the future to engage with the external organizations in the development of IMT.","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-01 11:22:13","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXTERNAL ORGANIZATIONS","Cc":"","lsoriginalls":"ITU-R WP 5D LS to EO on M.2150","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210004.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210005","title":"LS from ETSI ISG IPE: Liaison about ETSI ISG IPE creation and interaction with other groups","source":"ETSI ISG IPE","contact":"Latif Ladid","contact-id":61458,"tdoctype":"LS in","for":"Information","abstract":"Dear Madam, Dear Sir, ETSI has held the first meeting of the Industry Specification Group on IPv6 Enhanced Innovation on 18th - 19th January, 2021. The ETSI 'IPv6 Enhanced Innovation' Industry Specification Group (IPE ISG) is an ISG to focus on IPv6-based Use Cases and Scenarios identification, Functional Requirements identifications and e2e transport architecture definition. Gap Analysis in respect to the existing standard will be performed. Best Practices for IPv6 and IPv6 Only transition, deployment guidelines and success showcases\/PoCs identifying thereby what and where consensus and harmonization could be reached. IPE has 20 Members, 20 Participants and 1 Counsellor, representing Manufacturers, Operators, Academia, Vertical Industries and Government agencies representing all the geographical areas. We invite interest and co-operation to liaise and join in. The following Work Items have been submitted within the Kick off Meeting: - IPv6 for 5G Transport Use Cases - IPv6 for Industrial internet and Enterprise - IPv6 for datacentre and Cloud - IPv6 Only use cases and Transition Guidelines - IPv6 Gap Analysis","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-01 11:22:13","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP, oneM2M, ETSI NFV; MEC; ZSM; ENI; F5G; PDL; ETI","Cc":"","lsoriginalls":"IPE(21)000020","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210005.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210007","title":"LS from IETF: LS on port allocation for the W1 interface","source":"IETF","contact":"Magnus Westerlund","contact-id":30925,"tdoctype":"LS in","for":"Information","abstract":"The IESG apologizes for not providing a more timely reply to your liaison statement. We hope that at least the approval of the assignment of the port for the W1 interface was timely. We positively recognize that 3GPP has initiated work to figure out suitable solutions to handle port usage for network internal interfaces without the need for a static port assignment from IANA. It was further requested by the 3GPP's liaison to IETF that some additional guidance and clarifications in regards to the future possibilities for port registrations by 3GPP with IANA are desirable. Below we will attempt to provide such clarifications. We like to point to the rules and policies documented in BCP 165 (RFC6335 and RFC7605) apply to any future request. The one that is most relevant to 3GPP for any future request is the expectation that assignment of only a single port number per transport protocol will be sufficient across all the future external services, i.e. all 3GPP interfaces that 3GPP defines that use that transport protocol. This can be realized in multiple ways and is something that your own work items should address. Some example of such methods include: * When using (D)TLS one can apply for application-layer protocol negotiation (ALPN) labels (RFC7301) to identify the protocol being used within a (D)TLS session. * Multiple servers with different names can share an IP address and port number when protocols enable demultiplexing by server name. An example is (D)TLS using Server Name Indication (RFC6066). * When using HTTP-based services, use the URI namespace to efficiently separate the different services. * Other protocol-specific methods for upper layer protocol demultiplexing, such as SCTP's Payload Protocol Identifier (PPID) (RFC4960), which enable routing of individual messages to the right consumer on a server. * A 3GPP-defined service discovery solution that redirects to other ports for the individual services. In general we recommend that 3GPP completely avoid the need for port registrations in the system and user range with IANA. Service names (RFC6335) use first-come-first-served registration and have low bars for registration due to the almost unlimited size of the name space, basically only intended to prevent abuse and mass registration. Service names can be combined with DNS and SRV records to look up a service's port number or can be incorporated into a service demultiplexing solution. 3GPP is still requested to apply for a port assignment if you have a need for a port assignment in the user port range (1024-49151). These should meet the rules and policies of the port registry. Further, to enhance any future IANA requests and their handling, the IESG recommends that any future assignment request should be very clear on how this port assignment will ensure that no further port assignments to 3GPP will be necessary for that protocol and have a versioning mechanism to handle future upgrades. In case 3GPP has further questions about a potential port assignment request they are welcome to contact the Transport Area directors per email on tsv-ads@ietf.org.","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-01 11:22:13","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"The IETF Chair , The IESG , TSG RAN, gonzalo.camarillo@ericsson.com","lsoriginalls":"LS_from_IETF","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210007.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210008","title":"LS from IEEE 1588 WG: RE: Use of language in 3GPP Standards","source":"IEEE 1588 WG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"The IEEE 1588 working group has an approved Project Authorization Request (PAR) to address this issue. The P1588g PAR (https:\/\/development.standards.ieee.org\/myproject-web\/public\/view.html#pardetail\/8858) states that we would create an amendment of IEEE 1588, which specifies an option for alternate terminology to 'master' and 'slave' that could be used in profiles or implementations. The goal is that those who prefer an alternate terminology would use this recommended alternate, so that there would not be a proliferation of multiple alternate terms. Members of 3GPP are welcome to join the IEEE 1588 Working Group and help define alternate terms.","secretary_remarks":"CC#3: Left open. Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-01 11:22:13","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Puneet Jain, 3GPP Liaison Coordinator","Cc":"","lsoriginalls":"reply to 3GPP liaison inclusive language.","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210008.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210009","title":"LS from ITU-T SG13: LS\/o on Establishment of new Focus Group on Autonomous Networks","source":"ITU-T SG13","contact":"Leon Wong","contact-id":85362,"tdoctype":"LS in","for":"Information","abstract":"SG13 would kindly like to inform your Study Group\/organization that it has agreed to establish under its mandate in accordance with Recommendation ITU-T A.7 a new Focus Group on Autonomous Networks. The Focus Group will serve as an open platform for pre-standard study on autonomous networks enabling collaboration between experts in the ITU, other SDOs, industry, and academia, allowing synergy of the right talent, knowledge, and experience to address the autonomy in future networks in a timely manner. The Focus Group will explore creative intelligence techniques that leverage online evolution mechanisms, enabling adaptation as a catalyst to achieve autonomous networks. The Focus Group will explore and study approaches such as exploratory evolution, emergent behaviour, and real-time responsive experimentation to enable an autonomous network. The Focus Group lifetime is set for one year from the first meeting but extensible if necessary by decision of the parent group. The first meeting of FG-AN will be held virtually in the end of January 2021. Chairman of the Focus Group: Leon Wong (Rakuten Mobile, Japan). The ToR of the Focus Group are in found in the annex 1. SG13 appreciates your interest and collaboration on this topic.","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-01 11:22:13","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSAG, ITU-T SG2, SG3, SG5, SG9, SG11, SG12, SG15, SG16, SG17, SG20, 3GPP, GSMA, IEEE, ETSI, TMF","Cc":"","lsoriginalls":"SG13-LS187.","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210009.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210011","title":"LS from RAN WG2: LS reply on QoE Measurement Collection","source":"RAN WG2","contact":"Rajeev Kumar Tyagi","contact-id":82633,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks for SA WG5 the LS S5-205347 (R2-2100079) on QoE Measurement Collection. RAN WG2 would like to point out that RAN WG2 Rel-16 specifications were already finalized. RAN WG2 is currently discussing the requirements mentioned by SA WG5 in their LS for the QoE solution which is to be developed in Rel-17 for NR. RAN WG2 considered the different features requested to be implemented in Rel-17 for NR QoE and have the following updates: 1) Mobility support for QoE measurement: RAN WG2 acknowledges the need for area handling during the mobility for QMC support. The exact solution will be discussed in the WI phase. 2) Simultaneous QMCs in a UE: RAN WG2 agreed that 'Configuration and Reporting for multiple simultaneous QoE measurements for a UE can be supported (can determine whether there is AS impact in the WI phase)'. The means for distinguishing QoE reports by the gNB will be decided in WI. 3) Temporary stop and restart at RAN overload: RAN WG2 agreed to support pause\/resume mechanism for QoE reporting during RAN overload with RRC signalling. The exact solution detail is still under discussion.","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-01 11:22:13","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"RAN WG3, TSG SA, SA WG4, TSG RAN","lsoriginalls":"R2-2102500","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210011.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210012","title":"LS on DASH Specification Availability","source":"SA WG4","contact":"Thomas Stockhammer","contact-id":60397,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 would like to reach out to ISO\/IEC JTC1 on our long-lasting relationship on the usage of ISO technologies in 3GPP standards in particular in the area of media services. The request specifically refers to ISO\/IEC 23009-1, Dynamic Adaptive Streaming over HTTP (DASH). ISO\/IEC JTC1 SC29 WG11 (MPEG) and SA WG4 developed DASH jointly in 2010, for a slightly more detailed history refer to the Annex of this LS. To not be harmed by different publication timelines, MPEG and 3GPP both documented DASH in their own specifications, MPEG in ISO\/IEC 23009-1 and 3GPP in TS26.247. Note that 3GPP specifications are publicly available and free of charge for download. The core specifications in ISO\/IEC and 3GPP were completely aligned, and only profiles and minor extensions were specified individually. After completion of the first edition, - ISO\/IEC decided to provide the standard as publicly and freely available on ISO's publicly available website (i.e. https:\/\/standards.iso.org\/ittf\/PubliclyAvailableStandards), among others because of the joint development between ISO and 3GPP. - ISO\/IEC asked 3GPP to consider removing the duplicated text in its specification and reference MPEG-DASH in ISO\/IEC 23009-1 (details in the Annex). - 3GPP eventually decided to remove the duplicated text in its specification and referenced MPEG-DASH in ISO\/IEC 23009-1 under the assumption that the standard remains publicly and freely available (details in the Annex). Since then, ISO\/IEC extended DASH and 3GPP continued to adopt functionalities at appropriate times. 3GPP via liaison and 3GPP members contributed to new amendments and editions of DASH as part of the regular ISO process. ISO\/IEC 23009-1 has become an important specification for 5G and in particular 5G Media Streaming, also due its world-wide deployment in other ecosystems and standards such as DVB, ATSC, SCTE or DASH-IF. However, while ISO\/IEC 23009-1 remained public and freely available for the first three editions since 2012 until early 2020, the fourth edition has not been freely published for more than one year, and the almost finalized fifth edition is not expected either. Also, the earlier editions were withdrawn from ISO's publicly available website (i.e. https:\/\/standards.iso.org\/ittf\/PubliclyAvailableStandards). In particular it is stated by ISO\/IEC JTC1 SC29 WG3 (MPEG systems): On the free availability of the 4th and 5th editions of the DASH specification, we have requested that but it has not been granted because those editions no longer appear to meet the criteria of freely available specification by ISO. This means that for worldwide adopters of 3GPP specifications (and those referencing 3GPP specifications), a significant amount of information is no longer freely available, and this status harms the goal of industry alignment on a single specification. This unexpected move by ISO also somehow invalidates the agreements. Note that similar issues apply for the ISO\/IEC 14496-12 (no longer available either) and its use as a reference in 3GPP TS 26.244. Based on this we kindly request the publication of the latest editions of ISO\/IEC 23009-1 on ISO's publicly available website (i.e. https:\/\/standards.iso.org\/ittf\/PubliclyAvailableStandards). This should also hold for future editions. If ISO would not be able to fulfill this request in due time (latest by August 2021), 3GPP will consider alternatives, in particular resuming the free publication of its DASH specifications for 3GPP specification adopters. However, we remain highly committed to a strong collaboration and avoid unnecessary complexity and industry confusion. We look forward to your positive response to our request and remain open for any questions and comments meanwhile.","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-01 11:22:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ISO\/IEC JTC1","Cc":"ISO\/IEC JTC1 SC29, TSG CT, DVB, ATSC, DASH-IF, TSG CT, TSG SA","lsoriginalls":"S4-210293","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210012.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210013","title":"LS from SA WG5: Reply LS on network data analysis energy saving","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks SA WG2 for their LS reply on network data analysis energy saving and for their replies to SA WG5 questions. SA WG5 informs SA WG2 that, in TR 28.809 (Study on enhancement of management data analytics), the Management Data Analytics (MDA) provides a capability of processing and analyzing the raw data related to network and service events and status (e.g., performance measurements, Trace\/MDT\/RLF\/RCEF reports, QoE reports, alarms, configuration data, network analytical data, and service experience data from AFs, etc.) to provide analytics report (including recommended actions) to enable the necessary actions for network and service operations. The MDA, in conjunction with Artificial Intelligence (AI) and Machine Learning (ML) techniques, brings intelligence and automation to the network and service management & orchestration. Therefore, SA WG5 sees NWDAF and MDAS\/MDAF (MDA Service \/ MDA Function) as two services \/ functions potentially complementing each other in some cases or as alternative to each other in some other cases. TR 28.813 clause 4.3.2.1 (Potential solution #1: OA&M centric energy saving) describes a potential solution to the SA WG2 use case 'Network data analysis assisted energy saving' in which NWDAF and MDAF complement each other. This potential solution is divided in four phases (Observation, Analytics, Decision, Execution). MDAF collects analytics from NWDAF during the observation phase.","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-01 11:22:13","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG SA","lsoriginalls":"S5-211478","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210013.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210014","title":"LS from SA WG6: Reply to LS on APIs in EDGEAPP","source":"SA WG6","contact":"Nishant Gupta","contact-id":62473,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks CT WG3 for the reply LS on APIs for EDGEAPP. SA WG6 discussed modelling the EDGEAPP service APIs as unified APIs with multiple consumers e.g. both, EEC in the UE and the EAS in the EDN. The main intention behind having the unified service is to allow reuse of APIs by different clients regardless of where a client is initiating the API request from; as long as it (i.e. unified service) doesn't introduce unnecessary complexities such as future extensibility issues. SA WG6 debated on the advantages and disadvantages of the approach and concluded that CT groups are better suited to evaluate the benefits and make an educated decision. Therefore, SA WG6 has decided not to model the APIs where EEC along with EAS or EES are potential consumers as unified services in stage-2 TS. If required, CT groups can take a decision on unified services based on detailed analysis as part of the stage 3 API specification work.","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-01 11:22:13","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3, CT WG1","Cc":"CT WG4, TSG CT, TSG SA","lsoriginalls":"S6-210330","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210014.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210015","title":"LS from ITU-T JCA-IMT2020: LS\/o on Invitation to update the information in the IMT2020 roadmap","source":"TU-T JCA-IMT2020","contact":"Scott Mansfield","contact-id":42415,"tdoctype":"LS in","for":"Information","abstract":"The ITU-T Joint Coordination Activity for IMT2020 (JCA IMT2020) thanks all that have replied to previous requests for input on IMT-2020 and beyond related standardization work. The current online version of the roadmap is available from the JCA-IMT2020 website. The objective of the roadmap is to support IMT-2020 and beyond standardization coordination. IMT-2020 and beyond are the important topics for our industry, and many standardization-related activities are held in various entities. The JCA is progressing this work in a form of roadmap of IMT2020 and beyond standardization. JCA-IMT2020 will keep updating this roadmap, and therefore we solicit your information about updates. If you send us the latest information of your activity related to 5G and beyond as well as Network Function Virtualization (NFV), programmable networks, self-managed networks, autonomous network, slicing (including orchestration and capability exposure), fixed-mobile and satellite convergence (FMC) and Information-Centric Networking (ICN), machine learning and other activities that are strongly related to IMT 2020, we will reflect it in the next roadmap update, which will be performed online soon after the next JCA IMT2020 meeting. Please submit your updates using the template to be found in appendix below. Should you wish to communicate any additional information about your specifications and projects, we invite you to do so. In addition, if not done yet, we invite the ITU-T Study Groups, SDOs, fora to nominate a representative to this group. JCA-IMT2020 anticipates having its next meeting on 2 December 2021 alongside the ITU-T SG13 meeting 29 November - 10 December 2021, place TBC. We invite your inputs\/updates to the roadmap.","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-16 12:44:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IMT-2020 liaison partners","Cc":"","lsoriginalls":"JCA-IMT2020-O-017","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210015.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210018","title":"LS from CT WG4: LS on Information on the port number allocation solutions","source":"CT WG4","contact":"Giorgi Gulbani","contact-id":82292,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 was tasked by TSG CT (see CP-201316) to specify alternative solutions for port allocation for new 3GPP interfaces from Rel-17 onwards. CT WG4 work on FS_PortAl SID (Unique identifier: 890002) has reached the first milestone. CT WG4 will send TR 29.835 v0.4.0 for information to TSG CT plenary meeting #91e. TR 29.835 will be used as an input for another TR 29.941, which will provide guidelines for selecting solutions. CT WG4 would like to ask RAN WG2, RAN WG3, SA WG4, CT WG3 and SA WG5 WGs to kindly review TR 29.835 v0.4.0 and share their views with CT WG4. Feedback from RAN WGs will be taken into account when finalizing TR 29.835. Preferred solutions will also be documented in TR 29.941, which will be maintained.","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10140,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-16 12:44:24","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, SA WG4, CT WG3, SA WG5","Cc":"TSG SA, TSG CT, TSG RAN, SA WG2","lsoriginalls":"C4-211806","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210018.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210020","title":"LS from SA WG2: Reply LS on making PSCell ID available at the SGW of EPC","source":"SA WG2","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 thanks SA WG5 and ETSI TC LI for their guidance on making PSCell ID available at the SGW in EPC so that it can be included in the charging information. SA WG2 apologies for delay in introducing this Rel-17 change into 3GPP specifications. Due to high number of Rel-16 corrections, SA WG2 was not able to trigger the generation of Rel-17 TS versions earlier. In earlier TS versions, the awareness of PSCell ID was used for MME internal processing, but now SA WG2 has agreed the attached Rel-17 CR on TS 23.401 that adds the MME procedure for passing on the PSCell ID information to SGW. In SA WG2 understanding, corresponding 5GS CR is not necessary.","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-16 12:44:25","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TC LI, SA WG5","Cc":"TSG SA, SA WG3LI, RAN WG3","lsoriginalls":"S2-2100248","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210020.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210022","title":"LS from SA WG2: Reply to LS on New Whitepaper: Operator Platform Telco Edge proposal","source":"SA WG2","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 would like to thank GSMA OPG for their LS on the new whitepaper on the 'Operator Platform Telco Edge proposal'. SA WG2 would like to inform GSMA OPG that the FS_enh_EC study item concluded in December 2020 and the related conclusions are captured in TR 23.748. The Rel-17 eEDGE_5G normative work will be primarily captured in TS 23.548, and additional changes will be captured in TS 23.501, TS 23.502, and TS 23.503.","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-16 12:44:25","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA Operator Platform Group (OPG)","Cc":"SA WG6, TSG SA","lsoriginalls":"S2-2101060","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210022.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210023","title":"LS from SA WG2: Reply LS on initiation of new work item Q.Sig_Req_ETS_IMS_roaming 'Signalling requirements for emergency telecommunication service in IMS roaming environment'","source":"SA WG2","contact":"Antoine Mouquet","contact-id":79376,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 would like to thank ITU-T Study Group 11 for the aforementioned liaison statement. SA WG2 would like to point out that Emergency services, including in roaming cases, are specified in 3GPP TS 23.167, which is managed by SA WG2. 3GPP TS 24.229 and TS 29.228 cover the stage 3 aspects. Therefore, in order to avoid duplication of the work or diverging standards, we respectfully recommend ITU-T Study Group 11 to consider these specifications.","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-16 12:44:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITUT Study Group 11","Cc":"ITUT Study Group 2, TSG SA, TSG CT, SA WG6","lsoriginalls":"S2-2101310","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210023.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210026","title":"LS from SA WG5: LS to TM Forum on introduction of 3GPP Autonomous Network Levels","source":"SA WG5","contact":"Xi Cao","contact-id":83332,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 is now working on Autonomous Network Levels, the study output is captured in TR 28.810 (the latest version is TR 28.810 V17.0.0), and the normative work is ongoing, the output will be captured in TS 28.100 (the latest version is draft TS 28.100 V0.3.0). SA WG5 would like to inform of the following achievements that has been agreed by SA WG5 and specified in draft TS 28.100 V0.3.0. And SA WG5 would like to coordinate with TM Forum for the following 3 aspects to have common understanding. - Concepts - Autonomous network concept : the ultimate goal for autonomous network is to enable telecommunication system to be governed by itself with minimal to no human intervention. See clause 4.1 of the attached draft TS 28.100 V0.3.0 for details. - Autonomous network level concept : the term Autonomous network level is used to describe the levels of autonomy capabilities in the autonomous network to improve the efficiency for network management and control. See clause 4.2 of the attached draft TS 28.100 V0.3.0 for details. - Dimensions for evaluating autonomous network levels - Scenarios : including network and service deployment, network and service maintenance, network and service optimization. See clause 4.3.2 of the attached draft TS 28.100 V0.3.0 for details. - Management scope : including NE\/NF layer, domain network layer, cross domain network layer and communication service layer. See clause 4.3.3 of the attached draft TS 28.100 V0.3.0 for details. - Workflow : including intent handling, awareness, analysis, decision and execution. See clause 4.3.4 of the attached draft TS 28.100 V0.3.0 for details. - Framework approach for evaluating autonomous network levels : see clause 5 of the attached draft TS 28.100 V0.3.0. SA WG5 would like to inform TM Forum about the above 3 aspects and get your feedback","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10180,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-17 09:56:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TM Forum Autonomous Networks","Cc":"TSG SA, ITU-T (FG-AN), ETSI (AN initiative, ZSM, NFV, ENI, F5G), IETF","lsoriginalls":"S5-212390","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210026.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210027","title":"LS from SA WG5: Reply LS on Progressing the Multi SDO Autonomous Network coordination","source":"SA WG5","contact":"Lan Zou","contact-id":35534,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks TM Forum for their LS on S5-212026 'Progressing the Multi SDO Autonomous Network coordination' and S5-212309 'Postponement of Multi SDO Autonomous Network inter SDO strategic meeting to 15th March'. SA WG5 is currently working on Rel-17 standardization work which covers many technical topics which are closely related to autonomous networks such as autonomous networks levels, intent driven management, self-organizing network, management data analytics, close loop assurance etc. SA WG5 has discussed the LS and would like to provide the following feedback: 1. For the Inter SDO Planning work, we believe that we should first focus on the alignment of following topics: ? Multi-SDO collaboration objectives ? Business vision and motivations ? Way of capturing collaboration agreement 2. For the Technical co-ordination work, our opinion is the following: ? The Multi-SDO coordination should take into account of existing available deliverables and align the standardization work across different groups as much as possible. ? The coordination work should consider the alignment of following technical aspects: o Alignment of Autonomous networks related concepts and definitions, e.g. ? Autonomous Networks ? Intent driven interactions ? Control loops ? Autonomous Networks Levels ? Autonomous Domain ? More to be added if needed o Sharing related use cases o Coordination on the architectural framework o Coordination on the key features and related multi-players interoperable management services to be supported towards autonomous networks o Proof of Concept to show the Multi-SDO coordination achievement SA WG5 is happy to cooperate with TM Forum and other SDOs on autonomous networks, and jointly produce a harmonized view.","secretary_remarks":"Proposed Action: Noted. Block Noted at CC#3","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-17 09:56:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TM Forum","Cc":"TSG SA, ETSI (AN initiative, ZSM, NFV, ENI, F5G), GSMA, NGMN, TSG SA, ITUT, IETF, IEEE","lsoriginalls":"S5-212310","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210027.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]