[{"name":"R5-246211","title":"Reply LS on TS.48 updates to cover IoT eUICC and request for defining AT commands for eUICC profile management","source":"TSG WG CT1","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"CT1 thanks GSMA for their LS (C1-244035) on TS.48 updates to cover IoT eUICC and request for defining AT commands for eUICC profile management. _x000D_\nCT1 has discussed the issue and has defined the following AT commands for eUICC profile management. Please see the attached CRs for further information._x000D_\n1) The +CEUICCPD command to trigger a request to download and install a profile in an eUICC._x000D_\n2) The +CEUICCPM command to enable, disable, or delete a profile in an eUICC. _x000D_\n3) The +CEUICCPMETAI command to read and display the profile metadata information for all the profiles installed in the eUICC._x000D_\n4) The +CEUICCMERESET command to perform eUICC memory reset._x000D_\n5) The +CEUICCSMDPA command to edit a default address on the eUICC or device._x000D_\n6) The +CGEUICCID command to request the eUICC identifier from the eUICC in the device. _x000D_\n7) The +CEUICCPNM command to manage the pending notifications that are generated when a profile management operation has been successfully performed on the eUICC._x000D_\n2\tActions_x000D_\nTo GSMA _x000D_\nACTION: \tCT1 asks GSMA to take the above information into account and let 3GPP CT1 WG know of any further requirements in this regard.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":6,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":62110,"status":"noted","reservation_date":"2024-10-25 10:44:25","uploaded":"2024-10-25 12:26:14","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5__105_Orlando\/Docs\/R5-246211.zip","group":"R5","meeting":"R5-105","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-246213","title":"Reply LS on 3GPP NR TRP TRS OTA requirements","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"3GPP RAN4 would like to thank GCF CAG for their LS in R4-2407017\/CAG-24-217r3 on requirements work for 5G NR FR1 TRP TRS OTA. _x000D_\nIn Rel-18 WI, RAN4 has already concluded some requirements work on following scope [1]: _x000D_\n?\tRequirements to BHH (Beside Head and Hand) _x000D_\n?\tTRP for devices with Power Class 3_x000D_\n?\tRequirements for bands n1, n28, n41 and n78_x000D_\nMeanwhile, Rel-19 OTA Work Item as TRP_TRS_MIMO_OTA_Ph3 targets enhanced OTA test methodologies and more requirements for NR OTA, which has the following requirement working scope concluded in RAN#104 meeting, June 2024 [2]:_x000D_\n?\tMore bands for BHH and Hand only, i.e., n3, n5, n7, n8, n20, n38, n77, n79_x000D_\n?\tRequirements for device narrower than 72mm at bands n1, n28, n41, n78 _x000D_\n?\tTRP TRS requirements for UE configured with 2Tx non-coherent UL-MIMO at bands n41 and n78_x000D_\n?\t2Tx coherent UL-MIMO requirements are not precluded if commercial devices are available_x000D_\n3GPP RAN4 would like to keep collaboration with GCF CAG on FR1 TRP TRS OTA work._x000D_\n2\tActions_x000D_\nTo GCF CAG: _x000D_\nACTION: \t3GPP RAN4 respectfully asks GCF CAG to take the above feedback into account when developing 5G NR FR1 OTA antenna conformance testing.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":6,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":62130,"status":"noted","reservation_date":"2024-10-25 10:44:25","uploaded":"2024-10-25 12:26:14","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_FR1_TRP_TRS_enh"},{"winame":" TRP_TRS_MIMO_OTA_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5__105_Orlando\/Docs\/R5-246213.zip","group":"R5","meeting":"R5-105","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-246214","title":"Reply LS on Newly published data channel GSMA PRD TS.66","source":"TSG WG SA3","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"3GPP TSG SA WG3 would like to thank GSMA TSG for their LS on Newly published data channel GSMA PRD TS.66. Since GSMA has sent this LS to multiple TSG SA workgroups, SA3 addresses this response to TSG SA for TSG SA to respond back to GSMA after coordination with the rest of the TSG SA groups. _x000D_\nGSMA TSG requested SA2 and SA3 to respond to the following question._x000D_\nQuestion to SA2\/SA3: GSMA would like to ask feedback on whether work is planned or ongoing to develop security controls for IMS Data Channel (and more generally for new type of communication services)._x000D_\nSA3 would like to mention that the first phase on the  security of IMS Data Channels has been studied in Rel-18 and was specified in TS 33.328 and SA3 currently performs a Rel-19 study on Next Generation Real-Time Communication security Phase 2, the results of which are recorded in TR 33.790. The Rel-19 study includes Key Issue #3: \"Security and privacy aspects of IMS DC capability exposure\" which includes the security aspects of Key issue #1, and Key Issue #2 of the corresponding study performed by SA2 in TR 23.700-77. The Rel-19 SA3 study has not concluded yet. Moreover The Rel-19 study includes Key Issue #2: \"Key issue #2: Security of IMS based Avatar Communication\" which is a new type of service in which SA2 concluded that IMS data channels will be used.  _x000D_\nGSMA TSG requested SA3 to respond to the following question._x000D_\nQuestion to SA3: TSG kindly asks SA3 to provide feedback on any security aspects of data channel they believe should be developed and, if such aspects are to be covered by or in cooperation with GSMA to consider taking part in the GSMA activity._x000D_\nAs described above there is an SA3 Rel-19 study in progress which includes IMS Data Channel security aspects. _x000D_\n3GPP SA3 has not studied security aspects on IMS data channel API specified in GSMA TS.66 so far. _x000D_\nSA3 will update GSMA after the Rel-19 SA3 study has been concluded if there are any identified data channel security aspects. _x000D_\n2\tActions_x000D_\nTo SA (with GSMA TSG as the eventual recipient) _x000D_\nACTION:  SA3 would like to kindly thank GSMA TSG for the offered help and request GSMA TSG to take the above information in account.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":6,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":62140,"status":"noted","reservation_date":"2024-10-25 10:44:25","uploaded":"2024-10-25 12:26:14","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5__105_Orlando\/Docs\/R5-246214.zip","group":"R5","meeting":"R5-105","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-246215","title":"LS Reply on Newly Published data channel GSMA PRD TS.66","source":"TSG WG SA4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"SA4 thanks GSMA for the LS on newly published data channel GSMA PRD TS.66 (S4-241435) and would like to provide the feedback as following:_x000D_\n-\tQuestion for SA4: GSMA would like to know, if, with reference to point 4 in the body of the LS, SA4 believes that there is the need to develop JavaScript APIs to control media stream?_x000D_\nThe content of point 4 is as below:_x000D_\nVideo pipeline and GSMA IR.94 extensions (new PRD) document would be the extension of GSMA IR.94 and would provide JavaScript API allowing to manipulate programmatically video media type. This work might be of interest to 3GPP SA4._x000D_\n_x000D_\nReply: SA4 has been working on the IMS-based AR Real Time Communication (see 3GPP TS 26.264), and Avatar based on IMS network (see 3GPP TR 26.813). These services require data channel application to capture, process and transport the video media, and the service logic should be controlled by the data channel application. Therefore, SA4 think that the JavaScript API for video pipeline is valuable._x000D_\n_x000D_\n-\tQuestions for SA4 and SA6: GSMA would like to ask if there are plans to develop a reference implementation to test IMS Data Channel services._x000D_\nReply: There are no plans to develop JavaScript code in SA4._x000D_\n_x000D_\n2. Actions:_x000D_\nTo GSMA TSG:_x000D_\nACTION: SA4 kindly asks GSMA TSG to take the above into account.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":6,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":62150,"status":"noted","reservation_date":"2024-10-25 10:44:25","uploaded":"2024-10-25 12:26:14","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"IBACS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5__105_Orlando\/Docs\/R5-246215.zip","group":"R5","meeting":"R5-105","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-246216","title":"Reply LS on Newly published data channel GSMA PRD TS.66","source":"TSG SA","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"The IMS data channel was introduced in 3GPP Release-16 TS 26.114 and provides the ability to establish a real-time communication path between two endpoints to exchange any form of data and enables new types of IMS interactive services._x000D_\nRelated with this, 3GPP has received an LS from GSMA. GSMA Networks Group (NG) and GSMA Terminal Steering Group (TSG) have worked on the data channel related aspects and during the years 2021-2023 GSMA Networks Group (NG) has published two documents: GSMA PRD NG.134 \u2013 IMS Data Channel and GSMA NG.129 \u2013 IMS Data Channel White Paper._x000D_\nThis LS asks a number of questions to this feature, and below is a consolidated reply from 3GPP TSG SA to the questions targeted for the SA WGs._x000D_\nQuestion to SA2, SA3:_x000D_\nGSMA would like to ask feedback on whether work is planned or ongoing to develop security controls for IMS Data Channel (and more generally for new type of communication services)._x000D_\nReply:_x000D_\nSA3 would like to mention that the first phase on the security of IMS Data Channels has been studied in Rel-18 and was specified in TS 33.328 and SA3 currently performs a Rel-19 study on Next Generation Real-Time Communication security Phase 2, the results of which are recorded in TR 33.790. The Rel-19 study includes Key Issue #3: \"Security and privacy aspects of IMS DC capability exposure\" which includes the security aspects of Key issue #1, and Key Issue #2 of the corresponding study performed by SA2 in TR 23.700-77. The Rel-19 SA3 study has not concluded yet. Moreover the Rel-19 study includes Key Issue #2: \"Key issue #2: Security of IMS based Avatar Communication\" which is a new type of service in which SA2 concluded that IMS data channels will be used._x000D_\nQuestion to SA3:_x000D_\nTSG kindly asks SA3 to provide feedback on any security aspects of data channel they believe should be developed and, if such aspects are to be covered by or in cooperation with GSMA to consider taking part in the GSMA activity._x000D_\nReply:_x000D_\nAs described above there is an SA3 Rel-19 study in progress which includes IMS Data Channel security aspects._x000D_\n3GPP SA3 has not studied security aspects on IMS data channel API specified in GSMA TS.66 so far._x000D_\nSA3 will update GSMA after the Rel-19 SA3 study has been concluded if there are any identified data channel security aspects._x000D_\nQuestion to SA4:_x000D_\n[...]\n2\tActions_x000D_\nTo GSMA TSG_x000D_\nACTION: \t3GPP TSG SA kindly requests GSMA TSG to consider the above feedback.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":6,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":62160,"status":"noted","reservation_date":"2024-10-25 10:44:25","uploaded":"2024-10-25 12:26:14","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5__105_Orlando\/Docs\/R5-246216.zip","group":"R5","meeting":"R5-105","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-246217","title":"Reply LS on CEN's requirements for eCall over IMS","source":"TSG SA","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"SA thanks CT1 for their LS reply analyzing the gaps in the LS from CEN (in SP-240522) and for providing their findings gathered during their discussion. SA would like to provide the following answers to the finding provided by CT1._x000D_\nFinding i):\tCT1 considers that all 9 CEN cases can be aligned, but also considers that CEN case #1 on test call is of utmost urgency. Because of this urgency, CT1 has endorsed a CR in C1-245026, (see attached). _x000D_\nHowever, even with the attached CR in C1-245026, there are some outstanding issues to aligning to CEN case #1, see following findings._x000D_\n_x000D_\nQuestion 1\tIs aligning CEN requirement #1 first before aligning other CEN requirements agreeable to SA?_x000D_\nAnswer 1:\tFrom SA perspective all the main cases highlighted by CEN, i.e., cases #1 to #5, shall be implemented in Rel-19. SA does not have a view on which case among these five cases should be aligned first within Rel-19._x000D_\n_x000D_\nFinding ii)\tCT1 considers that all 9 CEN cases can be aligned. However, for now CT1 have also progressed CEN case #2, #3, #4 and #5 and have endorsed CRs in C1-245025 (for CEN case#2 and #5) and in C1-244731 (for CEN case #3 and #4)._x000D_\n_x000D_\nQuestion 2:\tCan SA inform CT1 whether CT1 should further progress CRs for CEN cases #6 to case #9?_x000D_\nQuestion 3:\tFor the attached endorsed CRs, CT1 has agreed a WID dedicated to the CEN requirements. Is it agreeable to SA to have a dedicated WI for the normative work to align CEN requirements?_x000D_\nAnswer 2:\tFrom SA perspective and based on the CEN requirements, there is a higher priority to progress on cases #1 to #5. If CT1 considers that the cases #6 to #9 require further alignment, then further work should be done on these cases in CT1 and to be reported to SA for a final decision on alignment (as done for cases #1 to #5)._x000D_\nAnswer 3:\tYes, it is agreeable from SA perspective that TSG CT has a dedicated WI. SA WGs will align their specifications based on the requirements from CEN and the identified impact using the TSG CT WI code in their alignment CRs._x000D_\n_x000D_\nFinding iii):\tOn CEN Case #1: test call is a normal IMS call based on CEN requirements. CT1 considered that using dedicated URNs can work. However, as the test call is executed as a normal IMS call, then in a home routed scenario, the home P-CSCF has to be profiled to recognise that the normal call is actually to be treated as a test emergency call else, for example, the MSD transfer would not be possible or allowed._x000D_\n_x000D_\n[...]\n2\tActions_x000D_\nTo CT1_x000D_\nACTION: \tSA kindly request CT1 to take note of the provided answers to above questions and proceed with further normative work._x000D_\nTo SA2_x000D_\nACTION: \tSA politely ask SA2 to provide answer to Question 4 from CT1 and any feedback to Question 6 from CT1._x000D_\nTo SA1 and SA2_x000D_\nACTION: \tSA kindly propose SA1 and SA2 to discuss Rel-19 impacts to address cases #1 to #5.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":6,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":62170,"status":"noted","reservation_date":"2024-10-25 10:44:25","uploaded":"2024-10-25 12:26:14","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5__105_Orlando\/Docs\/R5-246217.zip","group":"R5","meeting":"R5-105","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-246220","title":"draft RAN5#105 meeting report","source":"ETSI Secretariat","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"report","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":62200,"status":"noted","reservation_date":"2024-10-25 10:44:25","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"R5","meeting":"R5-105","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]